RE: Cancel sessions

I've never liked the jobs that hold the queues or do controlled ends and
then wait a bit and then assume everything has finished. Far better to
do the holds/controlled ends and then start monitoring.  Some sort of
process like:

0. Hold job queues/do controlled ends on the subsystems.
1. Delay for a minute or so.  
2. Check the subsystems for active jobs.  Use Rob's method, other APIs,
or WRKACTJOB to a SPLF that you parse.  It doesn't really matter.
2a. If none exist, go to step 4.
2b. Otherwise increment a counter.
3. Check the counter.
3a. If the counter < your threshold (say, 30 minutes), go to step 1.
3b. If you require a backup, do a forced end of the jobs/subsystems,
monitoring for completion, and go to step 4.
3c. If you don't require the backup, or if you cannot cancel the jobs
(as they update critical tables), go to step 5.
4. Do the backup.
5. Release queues/restart subsystems.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] 
Sent: Friday, April 15, 2005 8:17 AM
To: Midrange Systems Technical Discussion
Subject: Re: Cancel sessions

We use a series of api's to look for object locks.
For example the api that is like WRKOBJLCK can be used to get a list of
jobs that have a lock on the library in question.  Then you can proceed
to cancel those jobs.  We've already held the job queues and since we
have a kick a$$ machine it doesn't take long for any batch jobs to have
finished. 
 So, all that is left, are some interactive jobs that our routine blows
to kingdom come.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Goinsc24@xxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/14/2005 09:48 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Cancel sessions






We submit batch jobs to run at night that require saving files to tape. 
Occasionally, a session is left "hanging" out on the system even though 
there are 
no active users.  This results in a system message that the file is
active 
and 
the saves are halted until the session can be canceled.  Is it possible
to 

check the system prior to running nightly batch jobs and automatically 
cancel 
all sessions?
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in the future then please respond to the sender to this effect.