Page 1 of 1

Backup issues after upgrade to zOS 2.2

PostPosted: Mon Feb 25, 2019 12:51 pm
by netcrawler
Hi experts,

I have encountered an backup issue after upgrading zOS2.2. The backup job was successfully completed but a lot of misleading messages generated.

My JCL for Backup:

//BACKUP1 JOB ((7000)),'SYSPROG',CLASS=A,MSGLEVEL=(1,1),
// MSGCLASS=J,REGION=0M,NOTIFY=&SYSUID
//*
//* NOTE: ALL DSN NAME NEED TO START WITH PREFIX BKC.**
//*
//BACKUP EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//TAPE1 DD UNIT=CART,DISP=(NEW,CATLG),LABEL=(1,SL),
// DSN=BKC.ACPT.ASMF.D101218
//DASD1 DD UNIT=CART
DUMP OUTDDNAME(TAPE1) -
DS(INCL(SYSSUP.AAM311B.D181208.S00003.TRS -
SYSSUP.AAM311B.D181209.S00006.TRS)) -
TOL (ENQF)
/*



The backup generated below messages although job not abended :

IEC705I TAPE ON 1103,DU0489,SL,COMP,BACKUP1,BACKUP,BKC.ACPT.ASMF.D101218,MEDIA2
IGD306I UNEXPECTED ERROR DURING CBRXVOL PROCESSING 029
RETURN CODE 4 REASON CODE 0
THE MODULE THAT DETECTED THE ERROR IS IGDTVRSG
SMS MODULE TRACE BACK - TVRSG TVR00 SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD12770

 

Any idea what are these message?


Read more: http://ibmmainframes.com/viewtopic.php? ... z5gWctp4Fp

Re: Backup issues after upgrade to zOS 2.2

PostPosted: Mon Feb 25, 2019 3:02 pm
by NicC
They are informational messages - IRC705I
Have you tried looking up the messages in the Messages and Codes manuals?

Re: Backup issues after upgrade to zOS 2.2

PostPosted: Tue Feb 26, 2019 7:45 am
by netcrawler
Hi NicC,

Thanks for reply. Although it's informational and backup still ended successfully but it given a wrong impression
that the backup may have error. These message didn't appear before we upgrade the zOS 2.2. From the manual,
The return code 4 for CBRVOL is

4 Request not executed For tape volume record creation, a tape volume record with the same volume serial number is already present in the TCDB. For tape volume record update, replacement, or deletion, the requested tape volume record is not present in the TCDB. For tape volume record retrieval, the TCDB does not exist, the tape volume record is not present in the TCDB, or the tape volume record is present in the TCDB but is for an up-level volume. To distinguish between the latter two cases, flag VCP_UPLEVEL_TDSI is set if the volume record contains up-level TDSI information. For sequential tape-volume record retrieval, there are no (more) records to retrieve or the TCDB does not exist.

Don't quite understand the manual, anyone can guide?

Re: Backup issues after upgrade to zOS 2.2

PostPosted: Wed Mar 13, 2019 2:06 pm
by netcrawler
If We code VOL=(,RETAIN,,100) in DD statement, the error message would be generated. Any advise why need to code
VOL=(,RETAIN,,100) to suppress the message

Re: Backup issues after upgrade to zOS 2.2

PostPosted: Wed Mar 13, 2019 3:36 pm
by NicC
Please check your posts before submitting.

You state that using VOL=(,RETAIN,,100) as a parameter the message is issued. You then say that using that same parameter suppresses the message. It cannot be both. So which is it? And does the volume count have to be exactly 100?

Re: Backup issues after upgrade to zOS 2.2

PostPosted: Fri Mar 15, 2019 9:00 am
by netcrawler
Sorry, should be if I coded VOL=(,RETAIN,,100), the message wouldn't be generated. Any Idea?

Re: Backup issues after upgrade to zOS 2.2

PostPosted: Fri Mar 15, 2019 9:08 am
by steve-myers
netcrawler wrote:Sorry, should be if I coded VOL=(,RETAIN,,100), the message wouldn't be generated. Any Idea?
Your VOL parameter sets a limit of 100 volumes for the data set. Without the 100 in the VOL parameter the limit is much smaller. I think - though I'm not certain - the default limit is 5 volumes. Now, of course, you do not need to actually fill all 100 volumes. It just means there are slots to store 100 volume serial numbers.