RE: IBM Save 21 -- MIDRANGE-L

I haven't encountered the writer situation mentioned when the system is in
restricted state. Then again, we rarely use save 21...

Go save 21 requires a person. Additionally, a batch program cannot end the
system to a restricted state. However, I wrote a CL program that ends to a
restricted state and performs the steps we wanted from a save 21 (save
*NONSYS, save DLO, save IFS). Additionally I wrote an AT command (similar to
the unix AT) that we run from our console. On Friday (we do this on the
weekend), our check list says to sign on and run the AT command for the
weekly backup. The console is left signed on and counts down to 0; at 5:00
Sat morning, the system ends to restricted state and performs the backup.
When finished, the controlling subsystem restarts and the terminal is signed
off.

We don't have TAA tools, so if there's an AT-type function, we just
duplicated it. 

We've run this for a while without incident. If anyone wants, I can send the
source.

Loyd

-----Original Message-----
From: Olliges, James [mailto:JOLLIGES@SMURFIT.COM]
Sent: Tuesday, December 26, 2000 10:09 AM
To: MIDRANGE-L@midrange.com
Subject: RE: IBM Save 21


Al,

  Why not use the OA (Operational Assistant) GO BACKUP menu instead?  It
does the ENDSBS processing, Change QSYSOPR message queue notification, etc.
under the covers from one menu.

James A. Olliges
Smurfit-Stone ITD Chicago
jolliges@smurfit.com


-----Original Message-----
From: Al Barsa, Jr. [mailto:barsa2@ibm.net]
Sent: Saturday, December 23, 2000 6:17 PM
To: MIDRANGE-L@midrange.com
Subject: Re: IBM Save 21


At 02:20 AM 12/23/00 -0500, you wrote:
>We run IBM Save 21 every nite.
>
>Our steps are to bring all user activity to an end one way or another, then
>run ENDSBS, then do the Save 21 with its end all activities.  We do the
extra
>ENDSBS because if printers are active, there are some system objects that
>cannot be saved, which leads to error messages that are difficult to
>decipher.  We prefer a clean save with no hassles with any error messages.
If you have to do any extra steps, I consider this a bug which should be 
reported.

Al




+--------------------------------------------------+
| Please do not send private mail to this address. |
| Private mail should go to barsa@ibm.net.         |
+--------------------------------------------------+

Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:          914-251-1234
Fax:            914-251-9406
http://www.barsaconsulting.com
http://www.taatool.com
+---
| 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
+---
+---
| 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
+---
+---
| 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
+---