It appears as if 1.13 has closed a loophole which you have unknowingly been
taking advantage of on previous versions.  One possible solution would be to
change the PROC by adding a step on each side of the ADRDSSU step:

     The step prior would be a simple IDCAMS to create a small dataset on
the volume.  (For example, copy a record or two out of SYS1.MACLIB(OPEN).)
This would insure that you never have an empty or missing file.

     The step after would delete the dataset insuring that tomorrow's job
won't fail due to duplicate DSN.

:>: -----Original Message-----
:>: From: IBM Mainframe Discussion List [mailto:[email protected]] On
:>: Behalf Of Jake anderson
:>: Sent: Thursday, December 06, 2012 10:06 PM
:>: To: [email protected]
:>: Subject: Conditional Statement during Backup - Clarification
:>:
:>: Hi,
:>:
:>: My question is going to be very general. Our shop has the policy of
:>: running
:>: daily back up from Mon-friday on a incremental basis(Volume Level). So
:>: we
:>: have been using this Keyword at sysin control card : DATASET(INCLUDE(**)
:>: BY(DSCHA,EQ,YES), which means that the backup would take place only if
:>: any
:>: changes have been occurred on a specific Volume. Recently in our Z/OS
:>: 1.13
:>: Testing box we ended with Below error.
:>:
:>: ADR049E (001)-STEND(01), 2012.340 15:29:13 DFSMSDSS FUNCTION TASK
:>: ABEND RECOVERY ROUTINE WAS ENTERED. SYSTEM ABEND CODE=0A13 REASON
:>: CODE=0010
:>:
:>: and also followed by the below error :
:>:
:>: IEC151I A13-
:>: 10,IFG0195H,TS1IN4$,STEP01,TAPE1,0890,TS1IN4,BACKUP.INC.MTWK05
:>:
:>:
:>: IEC151I
:>:
:>:
:>: Explanation: The error occurred during processing of an OPEN macro
:>: instruction for a data set on magnetic tape.
:>: In the message text:
:>:
:>: rc
:>: Associates this message with system completion code A13 and with the
:>: return code.
:>: jjj
:>: The job name.
:>: sss
:>: The step name.
:>: ddname[-#]
:>: DDname (followed by a concatenation number if it is part of a
:>: concatenation and not the first DD statement in the concatenation).
:>: dev
:>: The device number.
:>: ser
:>: The volume serial number.
:>: mod
:>: The name of the module in which the error occurred.
:>: dsname
:>: The data set name.
:>: The explanation for the hex return code is as follows:
:>:
:>:
:>: Return Code Explanation:
:>: 10
:>: A tape mark was read instead of a HDR1 label while forward spacing to
:>: the desired file on an SL or AL tape. Thus, the multifile tape ends
:>: before the desired file. When positioning to the end of file 1, this
:>: means the vol label is followed by a tape mark. Probable user error.
:>: Check the file sequence number and volume serial numbers and that the
:>: job that wrote the tape wrote all the files
:>:
:>:
:>: I believe that when there is no dataset on a particular Label then it
:>: will
:>: not proceed with the other LABEL and would end up with above error
:>: message.
:>: We have never had this issue in past even if a particular LABEL does not
:>: have a dataset and it obviously moves on to next label for backup.  I
:>: hope
:>: as per the design it should work and I am totally confused by the above
:>: reply.
:>:
:>: The JCL which we are using like below :
:>:
:>: //STEP01   EXEC PGM=ADRDSSU PARM='TYPRUN=NORUN'
:>: //SYSPRINT DD  SYSOUT=*
:>: //DASD1    DD UNIT=3390,VOL=SER=&VOL,DISP=SHR
:>: //TAPE1    DD UNIT=890,VOL=(,RETAIN,SER=&TAPE),DISP=(NEW,KEEP),
:>: //            DSNAME=BACKUP.INC.&VOL,LABEL=(&LBL,SL)
:>: //SYSIN    DD DSN=JAKE.TEST.CNTL(CARD),DISP=SHR
:>: //BACKUP   PEND
:>: //DASD01   EXEC BACKUP,VOL=TVX3A1,TAPE=TS1IN4,LBL=01
:>: //DASD02   EXEC BACKUP,VOL=TVX3A2,TAPE=TS1IN4,LBL=02
:>: //DASD03   EXEC BACKUP,VOL=MTWK05,TAPE=TS1IN4,LBL=03
:>:
:>: Any suggestion are highly appreciated.
:>:
:>: Jake
:>:
:>: ----------------------------------------------------------------------
:>: For IBM-MAIN subscribe / signoff / archive access instructions,
:>: send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to