What causes TLMSII-CRASH-PROTECTED dataset names when viewing a volume.

Document ID : KB000045464
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue/Problem/Symptoms: 

What causes TLMSII-CRASH-PROTECTED dataset names when viewing a volume.

Environment:  

All versions of CA TLMS.

Cause: 

CA TLMS automatically provides extended tape data set protection against catastrophic system failure for all tape data sets at OPEN for output time:

§     CA TLMS changes the scratch status to NONSCRATCH and the data set name to TLMSII-CRASH-PROTECTED in the Volume Master File at OPEN for output time.

§     The data set name is changed to the actual data set name when the data set is closed and normal CA TLMS updates are made. By updating in this sequence, volumes mounted for output data sets are marked NONSCRATCH when processing starts. If an operating system failure occurs during the processing of the jobs, the volumes currently in use are protected against reuse when the operating system is restarted. The same job (job name) will be allowed to use the volumes for output without changing the scratch status of the volume.

§     The special identity inserted in the data set name aids in identifying volumes in use when a system failure occurs. These volumes must be manually changed to SCRATCH status before they can be reused for output by another job.

 

Resolution/Workaround:

1. If the volume in question is still being created,  there is no action needed. The final close of the volume will be updated with the proper DSN.

2. If the volume was a part of a job abend or system failure, scratch the volume via PROC CATINQR or via CA TLMS ISPF interface.

Additional Information:

Refer to the CA TLMS Configuration guide,  section: Extended System Failure Protection.