Tweet
It is actually not necessary to be done, but I believe that it is a good practice. Each workstation also has an attached message queue, and these things can proliferate and take up a great deal of space if not controlled. OTOH if you don't clean up, the system will still function. Dave
-
-
QPADEV* entries
Doug, I use a quick and simple CL for this from the job scheduler each week. Here's the flow: 1. Use DSPOBJD to create a file of QPAD devices in QTEMP 2. Read each record in a loop. 3. Use RTVCFGSTS check the configuration status. If the status is between 20 & 59 or 80 & 109, vary off the device. 4. Repeat the cycle of reading each record in a loop. 5. Use RTVCFGSTS check the configuration status. If the status is between 0 & 19, delete the device. If you're not sure how to put this together, send me an email at dabayman@hotmail.com and I'll send you the source listing. Regards, Carl -
QPADEV* entries
I'm wondering what the benefits of cleanup are since the devices are reused as people sigh off and others sign on?Comment
-
QPADEV* entries
It is still a good idea to do this little admin task. Any devices that have been varied off due to password violations will not be reused. One of my sites with 50 or so users had accumulated over 400 devices by the time I noticed. (Nobody in California seems to be able to remember a password ;-) )Comment
-
QPADEV* entries
Any devices that have been varied off due to password violations will not be reused
That explains why we would sometimes reach the QAUTOVRT sysval limit.Comment
-
QPADEV* entries
California is not unique in this aspect. DaveComment
-
QPADEV* entries
I remember reading many years ago that it was a good practice to periodically clean up the QPADEV* devices created by Client Access, and set the QSYSVALs to a specific setting to aid in this. My questions are: 1. Do I remember correctly? 2. Does this practice still need to be done at V5R2 and higher? 3. Are there any performance impacts associated with not running the cleanup? Our system has defined QINTER, QINTER2, QINTER3, QINTER4, and QINTER5. Does anyone know if the system is creating these? The WSE for most of these is QPADEV*, so I am assuming that as new WSIDs are created, and the SUBS gets filled up the system is automatically creating the new subsystems to handle the load. Is that correct? 4. In searching for QPADEV* on mcpressonline, I see one solution is to periodically checking the last used date for QPADEV* objects, and deleting the objects, based on their age. Is that still applicable? Is that all that needs to be done? Anyone else experiencing this? Thank you, DougComment
-
QPADEV* entries
Based on more than 20 requests I've received for the source, here it is. Regards, Carl
ZAPDEVC.CLPComment
Comment