104

The address of the hashing routine is not contained in the TMC/AUDIT I/O parameter list. Issue a TMMOPTMC macro before any of the other TMC/AUDIT I/O macros can be processed.

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

108

The opcode being processed is greater than what is allowed.

Use only standard CA 1 macros for direct access to the TMC. For instructions on using the appropriate macros, see the Programming Guide.

112

The TMMPUTVL macro is being used to update a Control record.

The TMMPUTVL macro is used to update Volume records. For instructions on using TMSUDSNB to update Control records see the Utilities and Reports Reference Guide.

116

An opcode greater than 48 is being processed.

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

120

An opcode less than 36 is being processed.

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

124

A TMMPUTDB macro has been issued and the record to write is not a DSNB.

See the Programming Guide for details on using the TMMPUTDB macro.

128

The IBM conversion routine was unable to convert a relative track address to an absolute track address for the AUDIT data set.

If the Audit data set has been damaged due to an I/O error or other problems such as during a TMSFORMT of the Audit, it failed with a SD37 abend. CTL#4 was showing more allocated Audit records than physically exist. Reformat the Audit file and restart TMSINIT.

136

An opcode greater than 8 is being processed.

For assistance, contact Technical Support at http://ca.com/support.

140

A program calling CA 1 TMC/AUDIT I/Os, other than TMSINIT, is requesting initialization.

Only TMSINIT is authorized to activate CA 1. For instructions on using TMSINIT, see the Utilities and Reports Reference Guide.

144

The IBM conversion routine was unable to convert a relative track address to an absolute track address for the TMC data set.

Execute TMSPTRS to ensure the integrity of the TMC data set. The error can be caused due to an unnoticed SD37 abend during a TMSCOPY RESTORE, TMSFORMT EXTEND, or a TMSXTEND to a preallocated TMC. The TMC control records indicate that more TMC records are allocated than physically exist.

148

The IBM conversion routine was unable to convert a relative track address to an absolute track address for the Audit data set.

If the Audit data set has been damaged due to I/O or other problems, see the discussion on the TMSFORMT utility in the Utilities and Reports Reference Guide. If not, execute TMSCOPY to backup the TMC and Audit records written since the previous TMSCOPY execution to allow the Audit data set pointers to be reset.

152

TMSINIT was started without CTAPOPTN to bypass CAI.CTAPOPTN processing to deactivate CA 1 and then U was entered in response to IEFTMS0.

Execute TMSINIT and respond to IEFTMS0 with the CA 1 system password to deactivate CA 1. See TMSINIT in the Utilities and Reports Reference Guide.

160

An invalid parameter list was passed to the CA 1 SVC from a program requesting I/O to the TMC or Audit. The parameter list was from a Version 4 level request.

A preceding message, IEFTMS20, identifies the program in question. Adjust the program to pass an r11 or above version of the parameter list or there is some type of STEPLIB or link list concatenation problem.

164

The TMOIADDR from the parameter list that is passed to the CA 1 SVC is hex zeros. The state is invalid.

The wrong level of CA 1 macros are being issued. Ensure all exits/interfaces have been reassembled and relinked with the 5.2 macro library.