SARTPI42 Tape allocation failed ERR=9704 error loading archived file.
Article ID: 264420
Updated On:
Products
Issue/Introduction
Recall job gets:
SARTPI42 Tape allocation failed ERR=9704 INFO=0000 DSN=xxxx...SARTAPE.T0000415
SARTPI44 DUPLEX Tape does not exist or does not contain file - TSQ=415
The tape dataset is still cataloged but the tape in question is in scratch status:
VOLSER = P42640 ACTVOL= SMSMC= BLANKS
DSN = xxxx....SARTAPE.T0000415 DSN17= .SARTAPE.T0000415
EXPDT = 2023/090 ACCT= HEXZEROS
FLAG1 = 14 FLAG2 = C0 FLAG3 = 00 BATCHID= 54 = TMSSCR
FLAG4 = 00 FLAG5 = 00 FLAG6 = 00 HOOKID = FE =
EDMID = WMC = 00000 WWID = - -
CDATE = 2023/090 CJOB = SAR1 CTIME = 0600 CPGM = SARSTC
LDATE = 2023/090 LJOB = SAR1 LTIME = 0600 LPGM = SARSTC
CSTEP = SAR1 CDDNAME= SYS41507 CUNIT = 0BE8 LUNIT = 0BE8
OUTDATE= ZEROS OUTCODE= SLOT = 0000000 TRERRC = 00000
BTHDATE= 2018/162 VENDOR = BLANKS COUNT = 00185 TWERRC = 00000
DATECLN= ZEROS USECLN = 00000 CLNCNT = 000 TRERRI = 00000
VOLSEQ = 0001 ROBTY = VIBM ROBID = 000 TWERRI = 00000
1STVOL = NEXTVOL= PREVVOL= PRERRC = 00000
NUMDSNB= 00000 1STDSNB= 00000000 LSTDSNB= 00000000 PWERRC = 00000
LABEL = SL DEN = 38KC TRTCH = 36TK PRERRI = 00000
RECFM = U LRECL = 032760 BLKSIZE= 032760 PWERRI = 00000
AUDATE = 2023/090 AUTIME = 0704 BESKEY = 00000 BLKCNT = 0000086746
AUCODE = 00 AUFLAG1= 00 CPUID = PNB2 USERID = SBTPGMN0
VOLPERC= 001 FILPERC= 001 COMPRES= 000 BYTEPRC= 000 CTLGCNT= 001
Looking at the SAR tapes, some have an expiration date and some have CATALOG as the expiration date. I'm not sure why the difference.
Environment
View, 14.0, CA1
Cause
An I/O error had been received when the View backup process was creating the tape:
IOS051I INTERFACE TIMEOUT DETECTED ON 0BE8,C8,DB,**02,PCHID=01A1
IOS051I INTERFACE TIMEOUT DETECTED ON 0BE8,A9,**,**02,PCHID=010D
SARTPO49 Permanent I/O error writing backup media, restart OPT=NEW
IOS000I 0BE8,C8,SIM,**,**06,,**,P42640,SAR1
CCSR081I SARSDAPI DUMP COMPLETED
IOS000I 0BE8,**,SIM,**,**06,,**,P42640,SAR1
IOS000I 0BE8,**,SIM,**,**06,,**,P42640,SAR1
SARTPO49 Permanent I/O error writing backup media, restart OPT=NEW
IDI0034I Fault analysis skipped due to: EXCLUDE option specification (FAST)
IEA995I SYMPTOM DUMP OUTPUT 637
USER COMPLETION CODE=0049
TIME=06.10.58 SEQ=08007 CPU=0000 ASID=00DC
PSW AT TIME OF ERROR 478C1000 9D676C3A ILC 2 INTC 0D
ACTIVE MODULE ADDRESS=00000000_1D672000 OFFSET=00004C3A
NAME=SARTPO
DATA AT PSW 1D676C34 - 00181610 0A0D1FFF 58E0D004
GR 0: C0000000 1: C0000031
2: 00000018 3: 00000000
4: 00000000 5: 00000000
6: 00000000 7: 00036310
8: 00008C68 9: 1D677230
A: 000060C8 B: 00035310
C: 1D676BD8 D: 1D71A198
E: 9D676C2A F: 00000000
END OF SYMPTOM DUMP
IEC215I 714-0C,IFG0200Z,SAR1,SAR1,SYS41507,0BE8,P42640, 638
PUMG0.SA1.DSYS1.SARTAPE.T0000415
IOS000I 0BE8,**,SIM,**,**06,,**,P42640,SAR1
IOS000I 0BE8,**,SIM,**,**06,,**,P42640,SAR1
IOS000I 0BE8,**,SIM,**,**06,,**,P42640,SAR1
IEC999I IFG0TC0A,IFG0TC0B,SAR1 ,SAR1
IEF450I SAR1 SAR1 - ABEND=S000 U0049 REASON=00000000 646
TIME=06.11.02
IEF234E K 0BE8,P42640,PVT,SAR1,SAR1
IEF404I SAR1 - ENDED - TIME=06.11.02
* Because of the i/o error, our CA1 Abnormal Termination (ABTERM) routines kicked in, and as a result of having ABE=0 in CA1, the tape was marked for scratch even though there were VALID View reports successfully written to the tape.
Resolution
* After reviewing the SARTCP and SARTSLST outputs, VOLSER=P42640 has not been overwritten, appears to be intact, and sync's up with the View database. The 11306 reports that are on tape sequence number T0000415 should all be available!
- Because the tape and it's contents are intact you can use the SARTCP utility to create a new "xxxx...SARTAPE.T0000415" tape, as outlined below:
1. Copy the tape receiving SARTPI42 error (VOLSER=P42640) using the following sample JCL:
//TAPECOPY JOBCARD...
//STEP1 EXEC PGM=SARTCP,PARM='COPYASIS'
//STEPLIB DD DSN=your.view.CVDELOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//TAPEIN DD DSN=xxxxx.SARTAPE.T0000415,
// DISP=(OLD,UNCATLG)
//TAPEOUT DD DSN=xxxxx.SARTAPE.T0000415,
// DISP=(,CATLG),UNIT=(3490,,DEFER),
// LABEL=(,SL,EXPDT=99000)
//SYSIN DD DUMMY
//
* Note that when PARM='COPYASIS' is specified, the new output tape will NOT contain the data location blockids used for fast positioning, and which are required if using EAS.
2. Run SARTCP tape map JCL against the new output tape to confirm all reports were copied and no errors are received when running the SARTCP tape map job.
3. If all 11306 files were copied successfully, and these are the only files on the new tape, you should then run SARPAC against this new tape. SARPAC will add new data location blockids for these sysouts.
If you create a new xxxxx...SARTAPE.T0000415 tape, it's cataloged, and your tape management system reflects the new tape as having catalog retention, the SARTPI42 Tape allocation failed ERR=9704 problem should be be resolved.
Feedback
