Backup Daily job it fails with abend S806-04 , looking for TLMSDISK load module . TLMSDISK load module is located in the CA-TLMS load library which is not concatenated to the steplib of the failing job .
During the job which calls the TLMSDISK module we get the following message:
ADSTH005*0501 NO DATA SETS WRITTEN TO ARCHIVE DATA SET.. as on the first job when the TLMSDISK was called.
So on the first job which got a 806 regarding the TLMSDISK we got the following message:
OB14212 BLLU83:DD=ARCHIVE0 VOL=H34446 DSN=XXXXXXX
04.38.21 JOB14212 IEC205I ARCHIVE0,SGB08TDT,DMS,FILESEQ=1, COMPLETE VOLUME LIS
04.38.21 JOB14212 CSV003I REQUESTED MODULE TLMSDISK NOT FOUND
ADSTH005*0501 NO DATA SETS WRITTEN TO ARCHIVE DATA SET VOLUME=VVVVVV KEY=VVVVVV
Last update October 2, 2015
NO DATA SETS WRITTEN TO ARCHIVE DATA SET VOLUME= (vvv) KEY= (kkk)
The archive volume (vvv) has had no data written to it. The data set name (ddd) is the name of the archive data set. The key (kkk) is for the FDS ARCHVOLS subfile.
This condition usually occurs if CA Disk is requested to archive only one data set and encounters an I/O or serialization error while processing it. If the output archive volume is a tape, it is returned to scratch status. If it is a disk volume, the unused output data is deleted.
>>> in this case as the volume returned in scratch status, the TLMSDISK is called to give the information to TLMS to scratch the volume too.
It shouldn’t happen very often but it can so the TLMSDISK module needs to be available to Backup/Archive as it is for Ixmaint.
Insure that the CA TLMS load library is concatenated to the STEPLIBS for the CA Disk jobs steplibs if CTAPLINK is not in the LNKLST; or add CTAPLINK in the LINKLIST.