Re: Re[2]:re: complete save via cl command -- MIDRANGE-L

I have a program which does what option 21 does, (along with 
some additional logging).  However, it should be ran in a 
restricted state.  And that is the rub.  Running it in a 
restricted state.  This would probably not work from the job 
scheduler.  Because wouldn't doing an ENDSBS *ALL *IMMED kill 
the job?  A work around might be to sign on to the system 
console and execute a program which would do this.  Have the 
program pause on a data queue.  And have the job scheduler fill 
the data queue.

mreinkemeyer@mbsbooks.com on 05/03/2000 05:01:49 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re[2]:re: complete save via cl command

I won't ask you to publish the method of restarting the controlling subsystem
(althoug, now I am curious).  

I am confused.  I am not sure if I am not making myself clear or if maybe I am
just more ignorant on this than I thought?  I only go into the office once a
week (Mondays) so I want the systems to be set up to automatically do complete
saves each Friday night/Saturday morning.  Is it possible to set a delay on the
complete save that is that lengthy (4-5 days away) and reoccurs every week
without having to be set up each week (in case I miss a Monday)?  I have done
delays of a few hrs, but never days and haven't seen a parameter that allows
this to be reoccuring.  Thus the hope of a CL command via a job scheduled entry.
____________________Reply Separator____________________
Subject:    Re:re: complete save via cl command  
Author: <MIDRANGE-L@midrange.com>
Date:       5/3/00 4:10 PM

At 02:35 PM 05/03/2000 -0500, you wrote:

In V4R1, IBM added a delay parameter to the GO SAVE option 21 screen, so I 
think that would have worked.

If you are into CL masochism, you can retrieve the CL source for QMNSAVE, 
which is what option 21 uses.  Warning, this is not for the CL 101 programmer.

Regardless of whatever you do, it must be done from the console, and a 
restricted state is required for SAVSYS and SAVLIB(*NONSYS).  I once met a 
guy who developed a technique to restart the controlling subsystem (and NO, 
I will not publish it), and it turned out that his SAVSYS media was not good!

Al

>You didn't sign, so I have no idea who you are, but this is what I was looking
>for (I think)...thank you sooo much!
>
>Michele R
>
>____________________Reply Separator____________________
>Subject:    re: complete save via cl command
>Author: <MIDRANGE-L@midrange.com>
>Date:       5/3/00 1:27 PM
>
>                                 : Wed, 26 Apr 2000 09:46:33 -0500
>Michele Reinkemeyer wrote I was told (when I first started dealing with the
>AS/400 and still barely knew how to spell it) that there is a way to run a
>complete system save using a CL command through a job scheduled entry.  Is
>anyone familiar with this?  If so, would you be willing to share that CL
>command?  I want to implement such on 3 of my AS/400's since I am an hr and
>a half from office and don't care to drive in each weekend.
>
>
>I was sure Al was going to give you the answer on the complete system save.
>Here is what we have done in the past.  We have a profile setup to be used
>only for the weekend backup.  This profile signs on the console on
>Friday...which runs in QCTL or the controlling subsystem.  The profile has
>an initial program - nothing else happens except the console can no longer
>be used.   The DLYCMD is part of TAATOOLS
>The initial program includes the following command.  This delays the job so
>that it will start running  on day 2 which will be Sunday.
>Like this...
>   DLYCMD     CMD(LDSAVSYSB) TIME(215999) DATE(*DAY2) +
>              TEXT('save system weekly ') +
>              RSTDSTATE(*YES)  +
>              SIGNOFF(*YES)
>RSTDSTATE (*YES) means to put the box in restricted state.  The command is
>one I have written that does everything option 21 does.
>If you have taatools read the description for the DLYCMD.   I believe you
>can figure it all out from there.
>+---
>| 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
>+---
>
>
>

+--------------------------------------------------+
| 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
+---

Received: from uucphost.mcs.net [192.160.127.93] by ccmgate.mbsbooks.com 
(ccMail Link to SMTP R8.31.00.5)
        ; Wed, 03 May 2000 15:36:51 -0500
Return-Path: <midrange-l-owner@uucphost.mcs.net>
Received: (from uucp@localhost)
        by uucphost.mcs.net (8.9.3/8.9.3) with UUCP id PAA31948;
        Wed, 3 May 2000 15:36:21 -0500 (CDT)
        (envelope-from midrange-l-owner)
Received: (from majordom@localhost)
        by linux.midrange.com (8.9.3/8.8.7) id PAA15875
        for midrange-l-outgoing; Wed, 3 May 2000 15:22:05 -0500
Received: (from uucp@localhost)
        by linux.midrange.com (8.9.3/8.8.7) with UUCP id PAA15867
        for MIDRANGE-L@midrange.com; Wed, 3 May 2000 15:22:03 -0500
Received: from FIREWALL.barsaconsulting.com ([209.101.126.66])
        by uucphost.mcs.net (8.9.3/8.9.3) with SMTP id PAA29449
        for <MIDRANGE-L@midrange.com>; Wed, 3 May 2000 15:17:58 -0500 (CDT)
        (envelope-from barsa2@ibm.net)
Received: from barsa1.barsaconsulting.com by FIREWALL.barsaconsulting.com id 
QAA007.51; Wed, 3 May 2000 16:16:25 GMT
Received: from ALBARSAJR([192.168.100.111]) by BARSA1.BARSACONSULTING.COM (IBM 
OS/400 SMTP V04R04M00) with TCP; Wed,  3 May 2000 16:16:24 -0500
Message-Id: <4.2.0.58.20000503160445.00a40600@pop4.attglobal.net>
X-Sender: barsa2@pop4.attglobal.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Wed, 03 May 2000 16:10:06 -0400
To: MIDRANGE-L@midrange.com
From: "Al Barsa, Jr." <barsa2@ibm.net>
Subject: Re:re: complete save via cl command 
In-Reply-To: <0005039573.AA957382194@ccmgate.mbsbooks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-midrange-l@midrange.com
Precedence: bulk
Reply-To: MIDRANGE-L@midrange.com
Errors-To: list-errors@midrange.com
X-List-Name: Midrange Systems Mailing List (MIDRANGE-L@midrange.com)