104

The resident module indicates a different relative address for the first DSNB than that indicated in Control Record 2.

Execute TMSINIT. Verify that all CPUs point to the same TMC.

108

The resident module indicates a different number of DSNBs generated than that indicated in Control Record 2.

Execute TMSINIT. Verify that all CPUs are using the same TMC.

112

The next available DSNB pointed to by Control Record 2 is a used DSNB.

Execute TMSPTRS to provide information on the chaining error and use CA 1 batch or online facilities to correct the chain.

116

DSNB 0, which does not exist, is being processed.

If this is the case (for example, realtime tape processing or TMSINIT processing), contact Technical Support at http://ca.com/support for assistance. for assistance. (See the Programming Guide. If not, correct the user program that is incorrectly calling the SVC.

120

The DSNB being processed is greater than the number of DSNBs allocated.

If this abend did not occur due to an invalid online or batch inquiry or a chaining error which can be identified by TMSPTRS, contact Technical Support at http://ca.com/support for assistance. (See the Programming Guide.

124

An active DSNB is being deleted, but the number of active DSNBs in the USED field of Control Record 2 is already zero.

Run TMSPTRS to determine the true number of active DSNBs. Use TMSUDSNB to correct the USED field in Control Record 2.