Re: Interactive Subsystem Ending

Jim,

I actually tried the "security" angle first, but this got me nowhere.  They've 
been running a certain way for years without having an incident and didn't want 
to listen to a contractor about hypothetical what-ifs.  However, as the user 
requirements take us closer and closer to needing 24x7 up-time, I was able to 
get the change approved.

I read your post regarding the inactivity job.  Unfortunately, I was already 
half-way through creating a similar utility  or I probably would have used what 
you posted (although I did get some ideas from your code).  I added 
functionality to include giving each user or job their own inactivity interval. 
 The default is 90 minutes, but a user or job can be changed from 5 - 300 
minutes or *NOMAX.  Also, each user / job can specify to *ENDJOB or *DSCJOB.

Thanks,

<<<<<<snip>>>>>>

IBM's redbook "More Cool Things ..." recommends no more than 300 devices in
any one subsystem. I would go for the QINACTIV (the users bitch & moan, but
I usually phrase it as a security issue, and get management to back me). I
posted a pgm couple weeks ago that monitors the queue, and lets you choose
to not cancel or disconnect a job, based on either device id or user id.
This way I protect the users with more clout than me. Let me know if you
want a copy of the clp/RPG.
Jim Franz

<<<<<<snip>>>>>>

Todd Kidwell (Netstar)
AS/400 System Administrator
(313) 224-0578

+---
| 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: david@midrange.com
+---