|
Hi, I should have been more clear. I was making two points: 1. ENDSBS *ALL *IMMED does the job fine from IBM's perspective. 2 IBM reissues the command not to make it work faster, but to determine when they achieve a restricted state. Looking for the message in QSYSOPR or QHST is unreliable and difficult to do. Instead, IBM just issues the command, looking to see if the get the CPF1035 escape message. When they no longer get the message they know that they achieved a restricted state. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Jim Damato <jdamato@dollarge neral.com> To Sent by: "'Midrange Systems Technical midrange-l-bounce Discussion'" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 11/24/2003 04:04 Subject PM RE: Ending TCP/IP, FTP jobs in QSYSWRK Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> We're not running SAVE menu option 21. We've set up custom procedures so that we can break up the SAVLIB *NONSYS portion of the full save and split it out to three 3590's. We execute ENDSBS *ALL *IMMED then the operators wait for the restricted state before continuing on with various SAV* commands. According to QHST these QTFTPxxxxx jobs take 25 - 90 minutes to end. I'm not sure what you're saying. Would repeated ENDSBS *ALL *IMMED commands bring down the jobs in QSYSWRK any faster than the single execution we're performing? -Jim -----Original Message----- From: Al Barsa [mailto:barsa@xxxxxxxxxxxxxxxxxxx] Sent: Monday, November 24, 2003 2:57 PM To: Midrange Systems Technical Discussion Subject: Re: Ending TCP/IP, FTP jobs in QSYSWRK GO SAVE option 21, sits in a loop issuing the ENDSBS *ALL *IMMED command. It issues it every "n" seconds (last time I looked it was 15, but that was many releases ago), and then re-issues the same command. On the re-issue, it monitors for CPF1035, and when it doesn't get that message, it knows that the system has achieved a restricted state, and goes for the SAVSYS. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com What's the best way to bring down the system for IPL or full system save? We've been running ENDSBS *ALL *IMMED, but we've had intermittent problems with TCP/IP jobs in QSYSWRK taking forever to end. Occasionally some QTFTPxxxxx jobs will hang on for an hour and a half (or more). I was thinking of trying ENDTCP OPTION(*IMMED) ENDSVR(*YES) or ENDTCPSVR SERVER(*FTP) or ENDTCPSVR SERVER(*ALL) before our ENDSBS *ALL. We don't have a lot of opportunities to experiment, so I thought I'd ask around. Much thanks in advance... -Jim James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@xxxxxxxxxxxxxxxxx> _______________________________________________ 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-2025 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.