04

There is an invalid opcode or a programming error.

If the abend occurred in a user-written program, correct the logic error. If it occurred in a CA 1 program, contact Technical Support at http://ca.com/support for assistance.

08

Either the TMC or Audit data set (or both) is dynamically allocated, and a ddname has been found in TIOT. This is disallowed under dynamic allocation.

Remove the TMC/AUDIT DD statement(s) from the JCL. For an example of the correct JCL, see the Utilities and Reports Reference Guide.

0C

CA 1 is not active.

This program requires that CA 1 be either active or batch active in order to execute.

10

The ddname is not TMC, AUDIT or, in the case of CA Earl, TAPEDB. This indicates a programming error for dynamic allocation.

User-written routines that utilize TMSSIO cannot dynamically allocate data sets other than the TMC or Audit. Correct the programming error. If the problem occurs in a CA 1 program, contact Technical Support at http://ca.com/support for assistance.

14

Dynamic allocation failed. The file is no longer cataloged, is cataloged to the wrong device type, or is unavailable for allocation (held by a different job). Register 14 contains the SVC99 return code.

Determine the cause and take the necessary corrective action.

18

A DCB was opened for OUTPUT processing, but the TMMTMDCB macro was not defined as OUTPUT.

For information on the use of the TMMTMDCB macro, see the Programming Guide.

1C

During CLOSE processing by TMSSIO, the access module deletion failed.

For the reason of failure, see the IBM MVS Message Library: System Messages.

20

Either the TMC or Audit data set has been moved (that is, compressed or defragmented) since the last reinitialization of TMSINIT.

Ensure the correct position of the TMC and Audit data sets. If either has been moved, execute TMSINIT.

24

A CLOSE was done for a DD statement that was never opened.

Ensure the calling program has opened the file before attempting to CLOSE it.

28

You executed TMSINIT during the execution of TMSXTEND.

Execute TMSINIT after TMSXTEND has completed successfully.