I have done that before, and it works when I need to
do system level things. But in some cases there may
be another user who I want to keep on, or I may want
to log on to other tubes while the system is in a pseudo
Normally, this is only done for data wide level things.
There is a procedure that we run that purges our database
of old records and moves them to history. While this is
run no one can be using the files (for obvious reasons)
and normally this is done after hours. Sometimes it is done
during hours (during lunch hour if we can) and at that
point it is easiest to just kick everyone off the system and
keep them out 'til the job finishes. But, there are a few other
people in MIS who may be doing something that need to
stay on during this period. Or I may need to do things during
By kicking everyone off and just locking the initial program,
anyone "in the know" can still log into the system. I am sure
I could do it programmatically (have the initial program check a
data area for a flag or something) but this is just easier.
Chris Beck wrote:
> Why not just "TFRJOB QCTL"
> Then "ENDSBS QINTER *IMMED"
> Much easier and quicker since you already have to kick every one off. it will
>do it for you.
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: email@example.com
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact