Re: D3 Phantom Logoff/on nightly process
- From: dbenedict99@xxxxxxxxx
- Date: Thu, 10 Jul 2008 11:25:49 -0700 (PDT)
On Jul 10, 8:42 am, Tony Gravagno
<address.is.in.po...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
It took me a few times to understand the issue. It sounds like your
users aren't logging of the port at the end of the day, so you're
doing a logoff from the phantom so that it can restart your nightly
process. But it also sounds like you're saying a logoff command from
a phantom fails, compared to a logoff executed from a PIB which might
(?) have better success.
Have you considered breaking fingers of users who don't logoff a
critical device at the end of the evening? (That's my italian
heritage again...)
Is that the Sicilian side??? ;-)
Have you considered making it a regular process for the person at that
station to run the nightly job? This seems to have worked for
file-saves for a few decades.
What's the OS and release? Maybe peeps here can try this at home.
My big question would be: why does this process need to be logged off
so brutally all the time? Is the end-users running some intensive
process before walking out the door? If you're sure the tube is idle
and Logoff doesn't work then I would come back to trying to figure out
if this is phantom-specific. That leads to checking D3 release notes
to see if this issue has been fixed since your release was issued.
Finally, can you explain why this process needs to be monitored
visually? This sounds like one of those "we do this because of that",
and it's the "that" that needs fixing more than "this".
HTH
T
Marshall wrote:
I have a nightly process that I run on a terminal and would like to
keep it on a terminal so that it can be monitored visually. Problem
is the terminal is used during the day and if it is logged on the
Phantom has trouble logging it off remotely. What I need it to do is:
LOGOFF {port}
LOGON {port} NIGHTLY
When the port logs on to that user it automatically starts the nightly
process.
It simply won't logoff the terminal from the Phantom.
Any ideas?
Marshall
Tony does have a fix, have the user start the nightly process. This
works until the user is sick.
If you need to monitor things, depending on what is happening, you
could update the program to print a log of milestones. If the process
halts/stalls/crashes you will have a bit of work figuring out where
things stopped.
Another thing you could do is write out to a file a few records of the
details that are being worked on. Combine this with the last idea,
and your search is greatly reduced but the disk activity could be
high. If you use only a handful of record id's for this detail such
that you only keep the detail that was last successful, and the
current detail being worked upon actual disk activity will be low, as
most writes will be cached. Do be careful not to include these sorts
of writes within a transaction that needs to be committed, otherwise
you'll fill the disk with pending updates.
Donno if these ideas are worth anything,
Dale
.
- References:
- D3 Phantom Logoff/on nightly process
- From: Marshall
- Re: D3 Phantom Logoff/on nightly process
- From: Tony Gravagno
- D3 Phantom Logoff/on nightly process
- Prev by Date: Re: D3 Phantom Logoff/on nightly process
- Next by Date: Re: D3 Phantom Logoff/on nightly process
- Previous by thread: Re: D3 Phantom Logoff/on nightly process
- Next by thread: Re: D3 Phantom Logoff/on nightly process
- Index(es):
Relevant Pages
|
|
