Utilities › TMSPTRS Utility—Maintain Multivolume, Multi-Data Set Chains

TMSPTRS Utility—Maintain Multivolume, Multi-Data Set Chains

Use the TMSPTRS maintenance report program to detect invalid internal CA 1 multivolume and multi-data set chains, or errors that exist in the free chain of unused DSNBs.

Invalid or broken chains may occur as a result of invalid manual updates, abnormal termination of jobs, a system failure during CA 1 processing, or if the TMC could not be restored with all available Audit data (as in a disaster recovery). Volumes in delete or scratch status are not processed.

TMSPTRS should be regularly executed to analyze and report on any invalid pointers. Chaining errors left unresolved may result in CA 1 abends of tape jobs or invalid results from CA 1 batch jobs. A completion code of 12 is issued if any errors are detected. A code of zero indicates no errors were found. A case study can be found later in this discussion.

TMSPTRS can also be used to initialize TMC fields which were not available with previous CA 1 versions. It should be run for this purpose immediately after conversion from a lower version. Parameter ONLYTMC or ONLYDSNB must not be specified for this purpose.

The following fields are processed:

• DSNB field DSNBFVSN, pointing to the volume the DSNB file starts on.
• TMC FLAG3 bit TMULTIF, indicating the existence of DSNBs on the volume or in the multivolume chain.

Update control statements for these fields are generated automatically if the appropriate DD statements are found.

Important! These updates are highly sensitive to the structure of multifile/multivolume chains. Do not perform updates until all other pointer errors have been resolved manually and TMSPTRS has been rerun to ensure that correct update statements are generated.

TMSPTRS can be run without issuing a RESERVE against the TMC. A copy of the TMC is made and then updated by applying all changes from the Audit data set that have occurred because the copy operation began. Because it is necessary to apply the Audit records, TMSPTRS should not be run while other CA 1 batch utilities, such as TMSCLEAN and TMSEXPDT, are running.

If the ENQ parameter is specified, the active TMC is RESERVEd for the duration of the copy operation.

CA 1 must be active or batch active to run TMSPTRS.

A S213-10 abend occurs if run with a SYSUT3 allocated with DSNTYPE=LARGE.

In the event TMSPTRS terminates with U0999 abend, R15 will indicate the cause:

• 08 - The Audit data set did not contain Control Record #4 as the first record.
• 12 - A Type 5 Audit record was encountered indicating a structural modification to the TMC was made after it was copied to SYSUT3.
• 16 - A valid Control Record #2 was not found on the TMC.
• 20 - An open error occurred on TMSUPDTE or TMSUDSNB DD.

Note: If a "BLOCKSET Audit" is being used (refer to RO42220 for details on this new formatting option) and TMSPTRS is run without a PARM of ENQ, then on rare occasions you may receive an ERR24, ERR41, or ERR44 that do not actually exist. Running TMSAPEC (recommended) or TMSPTRS with PARM=ENQ eliminates these false errors.