|
Ending QINTER is not sufficient. Work gets into the system through lots of other avenues. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Jan Rockstedt" <jan.rockstedt@av inova.se> To Sent by: "Midrange Systems Technical midrange-l-bounce Discussion" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 09/27/2005 10:24 Subject AM RE: SAVLIB & SAVCHGOBJ ... Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Why not end the Qinter sbs and start it again when the backup is ending? Regards Jan Rockstedt Avinova AB nic-hdl: JR1543-RIPE -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bill Francis Sent: Tuesday, September 27, 2005 4:07 PM To: midrange-l@xxxxxxxxxxxx Subject: SAVLIB & SAVCHGOBJ ... We are a 9-5 shop and ages ago I created a CL program with DLYJOB to do SAVCHGOBJ & SAVLIB at night while nobody should be using programs/files. However, as the business has grown and more users have been added it's becoming a problem that users sometimes forget to sign-off and sit in a program overnight causing certain files to not be saved. Does anyone know how I can stop this from happening? Since I don't want to maintain a user-id file my initial idea was to find a way to output user devices to a file. That way I could use the file to issue HLDCMNDEV to suspend any signed on users before the save and then issue RLSCMNDEV to release the suspended devices after the save thus eliminating my problem. Is this the best way to make sure my saves complete in full? How can I get a device list to a usable file because DSPCTLSTS does not have a TO *FILE option? -Bill -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.