RE: Backup before release update

The funny thing is, I skip the RCL's on the weekends we are doing 
unload/reloads.  Seems that we are in too much of a time crunch then and 
we want to shave off a few hours.  But if you can do it in the am, more 
power to you.

Some people go ballistic about running a RCLSTG before a recent save. I've 
never had an issue.  But I have had saves abort because it needed the 
RCL's done.

There is one nasty thing in the GO SAVE option 21.  If you get damaged 
data queues in QMPGDATA, (which has occurred to us on more than one 
system), RCLSTG doesn't clean them up.  You can just delete them and they 
will rebuild.  Anyway, the save will abort and automatically take a C 
option.  CPF3763 which in turn generates CPF3777.  That's when you'll know 
if you'll have to clean them up.  No big deal, just telling you if it 
happens you don't have to call IBM like I did and wait to see if blasting 
them is ok.  You can always do the GO SAVE again and tell it to prompt for 
commands and F3 out of the options, take the G option to continue, until 
you get the prompt screen for the command after the SAVLIB *NONSYS.  Yes 
the SAVLIB *NONSYS did finish the rest of the libraries as you can see by 
the times on the messages below.  (Last weekend was so much fun.)

The rest of this email is just stuff for archive searching:

MSGID      TYPE                    SEV  DATE      TIME             FROM 
PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
CPF3763    Diagnostic              20   09/17/04  23:38:48.832912 QSRSVPRE 
    QSYS        0F0F     QSRSVPRE    QSYS        0F0F
Message . . . . :   DTAQ QPMJ57T037 in library QMPGDATA previously 
damaged. 
Cause . . . . . :   DTAQ QPMJ57T037 in library QMPGDATA was damaged on the 
 
  system before the save or restore operation. One of the following 
occurred: 
  -- If this is a save operation, the object was not saved. -- If this is 
a 
  restore operation and the object can be deleted by the system, it will 
be 
  restored automatically. -- If this is a restore operation and the object 
can
  not be deleted by the system, message CPF3819 will appear, and the 
object 
  will not be restored. Recovery  . . . :   Do one of the following: -- If 
you

MSGID      TYPE                    SEV  DATE      TIME             FROM 
PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
CPF3777    Escape                  30   09/18/04  01:10:08.675520 QSRSLCP2 
    QSYS        05D5     RCL_SAVCL   ROUTINES    0421
Message . . . . :   2935 libraries saved, 1 partially saved, 0 not saved.  
 
Cause . . . . . :   2935 libraries were saved, 1 libraries were partially  
 
  saved, and 0 libraries were not saved at 09/17/04 21:41:22. The save  
  operation ended on volume DTGL01. Recovery  . . . :   Display the job 
log 
  (DSPJOBLOG command) to see the previously listed messages.  Correct any  
 
  errors and try the request again. If the save operation was completed 
but 
  one or more libraries were not saved, you can use the Save Library 
(SAVLIB)
  command to save only the libraries that were not saved.  


Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/22/2004 10:35 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Backup before release update






> I use a program that does all the commands from go save, 21. 
> Prior to that it also RCLSTG, RCLDLO, RGZDLO.

That's a good idea.  I will do that Friday AM.

-- 
Jeff Crosby
Dilgard Frozen Foods, Inc.
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.



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