Maintaining the Volume Master File › Understanding VMF Chaining › Chaining Errors

Chaining Errors

The following conditions are probable causes of chaining errors.

Missing operating system intercepts

Missing OPEN and CLOSE operating system intercepts can cause chaining errors that are compounded if the condition is not corrected. A missing operating system intercept allows multiple chaining on the same volume.

Non-CA TLMS controlled volume in a CA TLMS controlled chain

A chaining pointer could not be established because a non-CA TLMS controlled volume was used in a multivolume chain output.

System or CA TLMS catastrophic failure

A hard z/OS system failure or abend affecting CA TLMS would not allow proper closing of a data set chain.

A tape volume is currently being used and has not gone through CLOSE processing

The tape is open for output and CLOSE information has not been posted. When examining the CATVCVS report, ensure that the tape is not currently being used.

TLMSII.DUMMY.DSN is a chained data set

CA TLMS re-chains when a multivolume or multi-data set is read as input. This is not a true chaining error.

Note: For information on the INPUT system option, see the section INPUT System Option—Input Data Set Processing Requirements.

Application is not processing normal IBM OPEN and CLOSE logic

If certain application data sets are continually listed on the CATVCVS report, they may be bypassing standard IBM OPEN and CLOSE logic. Contact CA for assistance. See the chapter in this guide titled "Troubleshooting" for further instructions.