108

The second record in the TMC is not Control Record 2 (TMSCTL#2). This occurs during the allocation of a free DSNB (TMMNEWDB).

This is usually the result of the TMC being corrupted by I/O or related problems (such as pack defragmentation if the TMC was not allocated as DSORG=PSU). Follow the procedures for restoring the TMC with TMSCOPY.

112

The first record on the Audit data set is not Control Record 4 (TMSCTL#4). This occurs during the allocation of a free DSNB (TMMNEWDB).

This is usually the result of the Audit being corrupted by I/O or related problems (such as pack defragmentation if the Audit was not allocated as DSORG=PSU). Follow the procedures for restoring the Audit TMMPUTAU macro with TMSFORMT.

116

The first record on the TMC is not Control Record 1 (TMSCTL#1). This occurs during initialization.

If this is the first time CA 1 is being used, it is usually a result of the TMC not having been formatted with TMSFORMT. Otherwise, this is usually the result of the TMC being corrupted by I/O or related problems (such as pack defragmentation if the TMC was not allocated as DSORG=PSU). Follow the procedures for restoring the TMC with TMSCOPY.

120

The third record on the TMC is not Control Record 3 (TMSCTL#3). This occurs during initialization.

If this is the first time CA 1 is being used, it is usually a result of the TMC not having been formatted with TMSFORMT. Otherwise, this is usually the result of the TMC being corrupted by I/O or related problems (such as pack defragmentation if the TMC was not allocated as DSORG=PSU). Follow the procedures for restoring the TMC with TMSCOPY.

124

The second record on the TMC is not Control Record 2 (TMSCTL#2). This occurs during initialization.

If this is the first time CA 1 is being used, it is usually a result of the TMC not having been formatted with TMSFORMT. Otherwise, this is usually the result of the TMC being corrupted by I/O or related problems (such as pack defragmentation if the TMC was not allocated as DSORG=PSU). Follow the procedures for restoring the TMC with TMSCOPY.

128

The first record on the Audit data set is not Control Record 4 (TMSCTL#4). This occurs during initialization.

If this is the first time CA 1 is being used, it is usually a result of the Audit not having been formatted with TMSFORMT. Otherwise, this is usually the result of the Audit being corrupted by I/O or related problems (such as pack defragmentation if the Audit was not allocated as DSORG=PSU). Follow the procedures for restoring the Audit with TMSFORMT.

132

The first record in the TMC, TMSCTL#1, has no ranges defined.

This is commonly a result of having executed the TMSCONTM conversion program with PARM='TYPE=NORMAL,TEST'. For CA 1 to initialize, a valid, formatted TMC must be available. Execute TMSFORMT to format a new TMC, or if needed, run the RESTORE function of TMSCOPY.

136

During initialization it was determined that either TMSXITE or TMSXITU or both were not compatible with the TMC being selected.

Review libraries to decide why exits are added, missing, or different from when TMC was formatted.

138

The second record from an extended TMC is not control record 2, (TMSCTL#2). This occurs during initialization.

If this is the first time a new CA 1 TMC is being used, this is the result of the TMC not being formatted with TMSBLDVR or TMSFORMT. Otherwise, this is the result of the TMC being corrupted by I/O or related problems (such as pack defragmentation if the TMC was not allocated as DSORG=PSU). If this error is obtained following a TMC conversion using the TMC Extend utility TMSXTEND, contact Technical Support at http://ca.com/support for assistance, otherwise follow the procedures for restoring the TMC with TMSCOPY.

140

The pointer to the first volume definition record in Control Record 2 (TMSCTL#2)does not point to a volume definition record,it points to is a Volume record. This occurs during initialization.

This is usually the result of the TMC being corrupted by I/O or related problems (such as pack defragmentation if the TMC was not allocated as DSORG=PSU). If this error is obtained following a TMC conversion using the TMC Extend utility TMSXTEND, contact support, otherwise follow the procedures for restoring the TMC with TMSCOPY.

142

The pointer to the first volume definition record in Control Record 2 (TMSCTL#2) does not point to a volume definition record, it points to a DSNB record. This occurs during initialization.

This is usually the result of the TMC being corrupted by I/O or related problems (such as pack defragmentation if the TMC was not allocated as DSORG=PSU). If this error is obtained following a TMC conversion using the TMC Extend utility TMSXTEND, contact Technical Support at http://ca.com/support for assistance, otherwise follow the procedures for restoring the TMC with TMSCOPY.

144

With a BLOCKSET audit file, an attempt was made to add more than 32 CPUs(LPARs) to Control Record 5 (TMSCTL#5).

Use TMSUDSNB to remove an unused CPU from Control Record 5. Replace the BCPInn and BCPRnn of the unused CPU with the values in BCPI32 and BCPR32. Then change the BCPI32 to ‘ ‘ and BCPR32 to ‘0000’. This will allow another CPU to be added to TMSCTL#5.