RE: Locking Interactive Users Out of Fil

Brian Johnson (brian@helpsystems.com) wrote:

>After the ALCOBJ commands, do a DLYJOB.  Specify the number of seconds to
>wait (DLY) or a time to resume (RSMTIME) so that your job stays active
>until you have a chance to check things out.
>
>From:  Karen Bellecci
>
>>I need to lock my interactive users out of the data files in
>>a certain library during the nightly batch run, until I can check
>>the nightly batch run the next morning to see if there were any
>>problems with the run, because I may need to restore files
>>and rerun, etc.
>>When I run a job that ALCOBJs on these certain files, they are
>>deallocated as soon as my job ends (which is about 7 seconds).

Karen,

Just be careful if the ALCOBJ job is in the same queue as the rest of
the overnight run, that the queue is not single threaded, or the entire
run will sit and wait for the DLYJOB to expire. In any case the job will
be taking up one of the threads available to the queue unless the
queue's entry is set to *NOMAX. QCTL is often a better subsystem for
running jobs with a long DLYJOB than QBATCH.

Dave Kahn - TCO, Tengiz, Kazakstan
=========

e-mail:  kahn@tengizchevroil.com    (until August 5th)
         dkahn@cix.compulink.co.uk  (from  August 6th)

Note new e-mail address in Kazakstan
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *