G–J

This group includes messages for the Control-M for z/OS (including Control-M/Assist, Control-M/Links for z/OS and Control-M/Restart), Control-D, Control-V and IOA products.

GIX MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages GIX0 through GIX0xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

GIX000I CONTROL-V GLOBAL INDEX utilityName STARTEDLink copied to clipboard

Explanation: This information message indicates that the utilityName Global Index utility started.

Corrective Action: No action is required.

GIX001I CONTROL-V GLOBAL INDEX utilityName ENDED OKLink copied to clipboard

Explanation: This information message indicates that the utilityName Global Index utility finished successfully.

Corrective Action: No action is required.

GIX003I USER PARAMETERS: parm_1. . . parm_nLink copied to clipboard

Explanation: This information message identifies the input parameters for the CTVUPGDB or CTDDBPRT utility.

Corrective Action: No action is required.

GIX004E INVALID DO= FUNCTION SPECIFIEDLink copied to clipboard

Explanation: The function specified in a DO statement is not valid.

The current utility stops.

Corrective Action: Correct the function name in the DO statement and rerun the job.

GIX005E INVALID PARAMETER: parmLink copied to clipboard

Explanation: The parm input parameter for the CTVUPGDB or CTDDBPRT utility is not valid.

The utility stops.

Corrective Action: Correct the invalid input parameter and rerun the job.

GIX006E REDUNDANT PARAMETER: parmLink copied to clipboard

Explanation: The parm input parameter for the CTVUPGDB or CTDDBPRT utility has already been specified. The same parameter is specified twice.

The utility stops.

Corrective Action: Delete the extra input parameter from the JCL and rerun the job.

GIX007E ERROR IN PARAMETERS: FODATE IS HIGHER THAN TODATELink copied to clipboard

Explanation: The specified starting order date (FODATE) is later than the specified ending order date (TODATE).

The utility stops.

Corrective Action: Correct the value of either FODATE or TODATE in the JCL and rerun the job

GIX008E INVALID DATE SPECIFIED: dateLink copied to clipboard

Explanation: Either the starting order date (FODATE) or the ending order date (TODATE) is invalid. The correct format is DD/MM/YY.

In this message, date is the problematic FODATE or TODATE date.

The utility stops.

Corrective Action: Correct the value of the incorrect ODATE parameter and rerun the job.

GIX00BE INVALID PARAMETERSLink copied to clipboard

Explanation: A parameter in the SYSIN stream for the CTVUPGDB utility is invalid. The error was detected during analysis of input parameters.

The CTVUPGDB utility stops.

Corrective Action: Examine other messages relating to the CTVUPGDB utility to identify and fix the problem, and rerun the utility.

GIX00CE THE PARAMETER parm MUST BE SPECIFIEDLink copied to clipboard

Explanation: The parm input parameter for the CTVUPGDB utility is missing. The CTVUPGDB utility requires the parm parameter.

The CTVUPGDB utility stops.

Corrective Action: Insert the missing parameter in the JCL and rerun the job.

GIX00DE ERROR OPENING GLOBAL INDEX DATABASE. RC=rcLink copied to clipboard

Explanation: The current utility or IOA application server could not open the Global Index database.

Global Index processing stops.

Corrective Action: Do the following:

  • If rc is 0 (meaning OK), examine the file names for the DAGIR and DAGIRI DD statements. Correct them, if necessary, and rerun the job.

  • If rc is not 0, for possible return code values and their meanings, see:

  • if the Global Index is an IOA Access Method file, the GIX010E message

  • if the Global Index is a DB2 database, the CTDGI0S message

  • Examine the IOA log for messages clarifying the error.

Correct the problem, and rerun the job.

  • If the problem persists, contact your INCONTROL administrator.

GIX010E SET PATH FAILED. RC=rcLink copied to clipboard

Explanation: The Global Index function could not establish a path for retrieving values. The required path does not exist in the Global Index database.

In this message, rc is the internal return code from the Global Index interface routine.

The explanations of the possible values of rc depend on whether the Global Index database is an IOA Access Method file or a DB2 database. These explanations appear in the following tables.

rc

IOA Access Method Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Incorrect input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

rc

DB2 Database Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The current utility stops.

Corrective Action: Do the following:

  1. Examine the return code to identify the problem.

  2. Examine the IOA log for messages clarifying the error.

  3. Correct the problem.

  4. Rerun the current utility or restart the IOA Application server.

  5. If necessary, contact your INCONTROL administrator.

GIX014E ERROR OPENING {SORTIN | SORTOUT} FILELink copied to clipboard

Explanation: The current utility could not open the SORTIN or SORTOUT temporary sorting file.

The current utility ends with a return code of 08.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

GIX015E ERROR ALLOCATING STORAGE FOR utilityNameLink copied to clipboard

Explanation: While executing the utilityName utility, the GETMAIN request failed. The GETMAIN request fails when there is not enough storage.

The utilityName utility ends with a return code of 08.

Corrective Action: Increase the region size in the appropriate JCL JOB or EXEC statement and rerun the utility.

GIX016E ERROR FREEING STORAGE FOR utilityName RC=rcLink copied to clipboard

Explanation: While executing the utilityName utility, the FREEMAIN request failed. FREEMAIN failed to free storage that GETMAIN allocated.

For an explanation of the return code (rc) in this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The utilityName utility ends with a return code of 08.

Corrective Action: No action is required.

GIX017E DYNAMIC ALLOCATION OF fileName FAILED, RC=rc, REASON CODE=rsnLink copied to clipboard

Explanation: Dynamic allocation failed. This error occurred when the CTVUPGDB utility tried to allocate the fileName file.

For an explanation of the internal return code (rc) and the reason code (rsn) in this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Use the information provided by the return and reason codes to correct the problem. If necessary, contact your system programmer.

GIX018E DYNAMIC DEALLOCATION OF fileName FAILED, RC=rc, REASON CODE=rsnLink copied to clipboard

Explanation: Dynamic deallocation failed. This error occurred when the CTVUPGDB utility tried to deallocate the fileName file.

For an explanation of the return code (rc) and the reason code (rsn) in this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: No action is required.

GIX019E INTERNAL ERROR - PATH TREE NOT FOUNDLink copied to clipboard

Explanation: The internal routine of the CTVUPGDB utility that scans the index tree encountered an empty path.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

GIX020E INTERNAL ERROR - ORPHAN SUBINDEXLink copied to clipboard

Explanation: The internal routine of the CTVUPGDB utility that scans lower level index trees encountered an empty parent path.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

GIX022E SORT FAILED RC=rcLink copied to clipboard

Explanation: The sort routine invoked by the CTVUPGDB utility ended with errors. The CTVUPGDB utility issues this message whenever the sort routine it invokes ends with a return code other than 0.

For an explanation of the return code value rc, refer to the documentation for your SORT utility.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Examine the return code rc to identify the problem.

  2. Correct the problem.

  3. Rerun the current utility or restart the IOA Application server.

  4. If necessary, contact your system programmer for assistance.

GIX023E CTVGDB FAILED RC=rcLink copied to clipboard

Explanation: The CTVGDB routine invoked by the CTVUPGDB utility ended with errors. The CTVUPGDB utility issues this message whenever the CTVGDB routine it invokes ends with a return code other than 0.

Possible values for the internal return code from CTVGDB (rc) are explained in the following table:

rc

Explanation

04

No values for subindex.

08

Error during open.

12

Error during close.

16

Error during GETMAIN operation.

20

Error during FREEMAIN operation.

24

Error during dynamic allocation.

28

Error during dynamic deallocation.

32

Error during load.

36

User Report List file access error.

40

Internal error in path tree.

44

Internal error during OPENSUB operation.

48

Internal error. Path not found for sort record.

52

Sort failed.

56

Global Index database access error.

60

Two paths with the same name and different lengths.

64

Sort file is full.

68

IOAMEM error.

72

CHKPTID member in use by another job.

80

Path not found in the CTDGIDB2 member.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error and rerun the CTVUPGDB utility.

  3. If necessary, contact your INCONTROL administrator.

GIX024E parm PARAMETER INVALID. ONLY YES OR NO IS VALIDLink copied to clipboard

Explanation: The value of the parm input parameter is invalid. The value of the parm parameter must be YES or NO.

The current utility stops.

Corrective Action: Correct parm in the JCL and rerun the utility.

GIX025W MAXIMUM NUMBER OF PROCESSED INDEXES procIndex REACHED. PROCESSING STOPPEDLink copied to clipboard

Explanation: The CTVUPGDB utility tried to add another main index to the Global Index database when it had already added the maximum number for this run. The MAXINDX parameter defines the maximum number of indexes that may be added to the Global Index database in each run of the CTVUPGDB utility.

The utility adds MAXINDX main indexes and ends with a return code of 04. Other indexes will be added during the next run of the CTVUPGDB utility.

Corrective Action: Increase the value of the MAXINDX parameter and run the CTVUPGDB utility again.

GIX026E parm PARAMETER INVALID. ONLY YES, NO OR ALL IS VALIDLink copied to clipboard

Explanation: The value of the parm input parameter is invalid.

Valid values for the parm parameter are:

  • YES

  • NO

  • ALL

The current utility stops.

Corrective Action: Correct the parm input parameter in the JCL, and rerun the utility.

GIX027E JOBID PARAMETER INVALID. SHOULD BE Jnnnnn or JnnnnnnnLink copied to clipboard

Explanation: The JOBID input parameter is invalid. The format of the parameter name must be the character J followed by five or seven digits, depending on how your system is set up.

The utility stops.

Corrective Action: Correct the JOBID input parameter in the JCL, and rerun the utility.

GIX028W INDEX EXISTS IN GLOBAL INDEX DATABASE, USE FORCE PARAMETER TO ADD IT AGAINLink copied to clipboard

Explanation: The CTVUPGDB utility is trying to add an index that is already in the Global Index database. The GIX029I message, which follows the current message, provides details about the index that caused the error.

The index is not processed.

Corrective Action: To replace values in an existing index, run the CTVUPGDB utility with the FORCE input parameter set to YES.

GIX029I USER userName, REPORT reportName, JOBNAME jobName, JOBID jobId, ODATE orderDateLink copied to clipboard

Explanation: This information message provides detailed information about the situation that caused the GIX028W message to be issued.

Corrective Action: No action is required.

GIX02AI INDEX: index DSNAME: dsnLink copied to clipboard

Explanation: This information message is issued by the CTVUPGDB utility before the GIX017E error message and displays the index name and data set name of the index file for which the dynamic allocation error occurs.

The variables in this message are:

  • index - the index name of the problematic index file

  • dsn - the data set name of the problematic index file

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: See the description of the GIX017E message.

GIX02BE CHKPTID MEMBER memName IS IN USELink copied to clipboard

Explanation: The memName CHECKPOINT member is in use by the CTVUPGDB utility, which has been invoked by another user.

The CTVUPGDB utility ends with a return code of 00.

Corrective Action: Try to run the utility again later.

GIX02CI WAITING FOR GLOBAL INDEX DATABASE indexLink copied to clipboard

Explanation: The index Global Index file is being used by another task for writing data.

The CTVUPGDB utility checks the Global Index file every 30 seconds until its use by the other task ends and the file is released. The CTVUPGDB utility then starts.

Corrective Action: No action is required.

GIX02DE LIST=DB2 OR LIST=ONLY SHOULD BE SPECIFIEDLink copied to clipboard

Explanation: The required LIST parameter is not specified or an incorrect value is specified.

The utility stops.

Corrective Action: Add the missing LIST parameter or set it to a valid value then rerun the job.

GIX02EW PATH NOT FOUND IN CTDGIDB2: pathNameLink copied to clipboard

Explanation: The pathName Index path was not found in the CTDGIDB2 member, which contains a list of index path names

This message is only issued if the LIST input parameter of the CTVUPGDB utility is set to DB2.

The CTVUPGDB utility does not unload the values of the pathName Index path into the sequential file from which they can be copied into the DB2 table.

Corrective Action: No action is required.

GIX02FE RECORD KEY vsaKeyLink copied to clipboard

Explanation: This information message follows the CTD908S message. The GIX02FE message identifies the VSA key of the record that was being accessed when the error occurred that caused the CTD908S message to be issued.

In this message, vsaKey is the VSA key of the problematic record.

The CTVUPGDB utility ends with a return code of 08.

Corrective Action: No action is required.

GIX031I TO GLOBAL INDEX DATABASE WERE ADDED: reportsQuantity REPORTS, indexQuantity INDEXES, indexValueNum INDEX VALUESLink copied to clipboard

Explanation: This information message identifies the data that was added to the Global Index database.

Corrective Action: No action is required.

GIX034S INTERNAL ERROR CREATING TABLE tableNameLink copied to clipboard

Explanation: An internal error occurred in the CTVUPGDB utility. CTVUPGDB did not find the SYSDATA entry in the internal table.

The CTVUPGDB utility ends with a return code of 8.

Corrective Action: Contact your INCONTROL administrator.

GIX035E INDEX tableName HAS INCORRECT LENGTHLink copied to clipboard

Explanation: The CTVUPGDB utility tried to add a path that was already in the Global Index database with different length parameters. This message occurs during an attempt to change the length of the index value in the definition of the decollation mission for a path that is already in the Global Index database.

The CTVUPGDB utility continues without adding the values in the indicated path to the Global Index database.

Corrective Action: Either change the length of the index value in the definition of the decollation mission that is causing the incorrect path or delete the old path from the Global Index database.

GIX036I GLOBAL INDEX HOUSEKEEPING UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started.

Corrective Action: No action is required.

GIX037I GLOBAL INDEX HOUSEKEEPING UTILITY ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility ended.

Corrective Action: No action is required.

GIX038I SEARCHING THE ACTIVE AND MIGRATED USER FILESLink copied to clipboard

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started searching ACTIVE and MIGRATED user files. This message makes it easier to calculate how long it takes to run each stage of the housekeeping utility.

Corrective Action: No action is required.

GIX039I DELETING VSA ENTRIESLink copied to clipboard

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started deleting VSA entries from the Global Index database. This message makes it easier to calculate how long it takes to run each stage of the housekeeping utility.

Corrective Action: No action is required.

GIX03CE ERROR IN PARAMETERSLink copied to clipboard

Explanation: The CTVGICL Global Index housekeeping utility detected one or more invalid parameters. CTVGICL detected the error while it was analyzing parameters.

The CTVGICL utility stops.

Corrective Action: Examine other messages relating to the job to identify and correct any errors, and rerun the utility.

GIX03DE IOAMEM ERROR func memName, RC rc, REASON CODE rsnLink copied to clipboard

Explanation: The CTVUPGDB Global Index utility could not read the specified library member of the CTD PARM library. CTVUPGDB was trying to read GLOBIDB or the member specified by the CHKPTID input parameter to see if the member needed to be restarted from the checkpoint as a result of an earlier abnormal ending.

The CTVUPGDB utility starts from the beginning to try to write the member.

Corrective Action: If there are no other messages, and the utility ended normally, no action is required. This message may be triggered by the first run of the CTVUPGDB utility. Otherwise, examine the other error messages and respond accordingly.

If the problem persists, report the information returned in the message to your INCONTROL administrator.

GIX03EI INDEX PATH: pathNameLink copied to clipboard

Explanation: This information message is issued for each loaded Index Path by loading the Global Index immediately during decollation mission run.

In this message, pathName is the name of the loaded Index Path.

Corrective Action: No action is required.

GIX03FE DELRPT FUNCTION FAILED. RC=rcLink copied to clipboard

Explanation: The CTVGICL Global Index utility could not finish processing the DELRPT function. The CTVGICL utility invokes the DELRPT function to delete reports.

In this message, rc is the internal return code from the Global Index interface routine.

The explanations of the possible values of rc depend on whether the Global Index database is an IOA Access Method file or a DB2 database. These explanations appear in the following tables.

rc

IOA Access Method Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Incorrect input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

rc

DB2 Database Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The CTVGICL utility stops.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error.

  3. Rerun the CTVGICL utility.

  4. If necessary contact your INCONTROL administrator.

GIX03GI reportsQuantity REPORTS WERE SELECTED FROM file USER FILELink copied to clipboard

Explanation: This information message indicates the number of reports selected for checking from the ACTIVE or MIGRATED user file by the CTVGICHK utility.

The variables in the message are:

  • reportsQuantity - the number of selected reports.

  • file - the type of Control-D user file. Can be ACTIVE or MIGRATED.

Corrective Action: No action is required.

GIX03HW NO REPORTS WERE SELECTEDLink copied to clipboard

Explanation: No reports were selected by the CTVGICHK utility for checking.

The CTVGICHK utility ends with a return code of 4.

Corrective Action: Correct the input selection parameters in the JCL member and rerun the utility.

GIX040E DELPATH FUNCTION FAILED. RC=rcLink copied to clipboard

Explanation: The CTVGICL Global Index housekeeping utility could not finish processing the DELPATH function. The CTVGICL utility invokes the DELPATH function to delete paths.

In this message, rc is the internal return code from the Global Index interface routine. Possible values are explained in the following table.

rc

Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Invalid input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

The CTVGICL utility stops.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error.

  3. Rerun the CTVGICL utility.

  4. If necessary contact your INCONTROL administrator.

GIX041I USER PARAMETERS FOR GLOBAL INDEX CLEAR parmListLink copied to clipboard

Explanation: This information message displays the parameters specified for the CTVGICL Global Index housekeeping utility.

Corrective Action: No action is required.

GIX042I PATH DELETED: pathNameLink copied to clipboard

Explanation: This information message indicates that the CTVGICL Global Index utility deleted the pathName path from the Global Index database.

Corrective Action: No action is required.

GIX043E ERROR IN DELPATH FOR pathName RC rcLink copied to clipboard

Explanation: The DELPATH Global Index function could not delete the pathName path. The CTVGICL utility invokes the DELPATH function to delete paths.

A possible cause for this error is that the PATH to be deleted was in use when DELPATH tried to delete it.

The variables in this message are:

  • pathName - the problematic path

  • rc - the return codeValid values are shown in the following table:

     

     

    rc

    Explanation

    00

    OK

    04

    End of file. Key not found.

    12

    Invalid function.

    20

    Not enough storage.

    24

    Not enough storage in GIR file.

    28

    Not enough storage in GIRI file.

    32

    There is no DBO block.

    40

    Invalid LRECL or KEYLEN in data or index file. Invalid input parameter.

    48

    SETPATH was not issued.

    100 through 199

    DBS error codes.

    200 through 299

    DBI error codes.

DELPATH skips the path that caused the error and continues to delete the next path.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error.

  3. Rerun the CTVGICL utility.

  4. If necessary contact your INCONTROL administrator.

GIX044E parm PARAMETER INVALID. SHOULD BE AFTER PATH PARAMETERLink copied to clipboard

Explanation: The parm input parameter for the CTVUPGDB Global Index housekeeping utility is in the wrong position. The ALT and BASELEN parameters may be specified only once each and must appear after the PATH parameter because they refer to a specific path.

The CTVUPGDB utility stops.

Corrective Action: Correct the input parameters in the JCL and rerun the job.

GIX045W NO RECORDS WERE ADDED TO THE GLOBAL INDEX DATABASELink copied to clipboard

Explanation: The CTVUPGDB Global Index housekeeping utility did not add any records to the Global Index database.

The CTVUPGDB utility continues processing.

Corrective Action: To add records to the Global Index database, correct the input parameters in the JCL for the CTVUPGDB utility and rerun it.

GIX046I LIST OF DELETED REPORTS:Link copied to clipboard

Explanation: This information message is the header for a list of reports that the DELRPT function of the CTVGICL Global Index housekeeping utility deleted. The GIX046I message is followed by one or more instances of the GIX047I message.

Corrective Action: No action is required.

GIX047I USER userName JOBNAME jobName KEY vsaKey - entryNum ENTRIESLink copied to clipboard

Explanation: This information message identifies a report that was deleted by the CTVGICL utility. The first GIX047I message in a series is preceded by either the GIX046I or the GIX04II message.

The variables in this message are:

  • userName - the identity of the user of the report

  • jobName - the identity of the job

  • vsaKey - the identity of the VSA record

  • entryNum - the number of deleted Global Index entries related to the specified report

Corrective Action: No action is required.

GIX048I FROM GLOBAL INDEX DATA BASE WERE DELETED: nr REPORTS, ne ENTRIES.Link copied to clipboard

Explanation: This information message provides the number of reports and Global Index entries deleted by the current run of the CTVGICL utility.

The variables in this message are:

  • nr - the number of reports deleted

  • ne - the number of index entries deleted

Corrective Action: No action is required.

GIX049E file_typ USER FILE READ ERROR, RC=rcLink copied to clipboard

Explanation: An error occurred while reading the User report list file.

The variables in this message are:

  • file_typ - the type of User report list file, that is, ACTIVE or MIGRATED

  • rc - the internal return code from the IOA Access Method interface routine

Valid values for rc are:

rc

Explanation

004

  • Read operation: EOF.

  • Add index operation: Duplicate Key.

  • Update operation: Record was changed.

008

Duplicate key.

012

Incorrect record for update.

016

The record was not found (probably deleted), or an invalid record was read, or the function is not correct.

020

Insufficient memory to open an IOA Access Method file.

024

Not enough space in data file.

028

Not enough space in index file.

032

The current call terminates because the previous open failed.

036

Incorrect record length.

040

Internal error.

044

Internal error.

052

Invalid key fields.

056

Key is too long.

058

For future use.

060

Index record does not match data record.

064

Wish WD1164 setting does not match file contents.

068

Incorrect parameter for Interface routine.

072

Incorrect file type.

106

Record not found.

108

Record not found. Invalid extent number.

109

Record not found. Invalid block number.

110

Internal error. Record not found. Invalid extent number.

111

Internal error. Record not found. Invalid block number.

112

Insufficient memory for internal buffers.

113

Open failed for database file.

114

RDJFCB failed for database file.

116

Corrupted free list.

118

Corrupted record.

119

Record not found.

120

Invalid QNAME.

121

Bad record in free list.

122

Invalid data set name in control record.

124

Invalid function.

128

IOAPARM load failed.

132

Add failed. Record too long.

136

I/O error.

144

EXCP init error.

146

For future use.

148

Invalid data set name or DD name is too long.

150

Locate failed.

152

SVC 99 allocate failed.

154

SVC 99 unallocate failed.

156

Dual database not up to date - aborting.

158

For future use.

160

Link of IOADBF failed.

164

A dynamic allocation error occurred (for example, out of space condition, security problems). See dynamic allocation error messages in the job log.

166

Control record cannot be updated because it is not enqueued.

168

Update failed. Record too long. No room in block.

170

IOADBSB# load failed.

172

READQ failed. Another block is already enqueued.

174

Function OPEN0 (exclusively) failed.

176

Function UPDATE0 failed. Data corrupted.

178

Function UPDATE0 failed. No appropriate enq.

180

Buffering not initialized. Internal error.

182

ENQ error.

184

Error during record compression / decompression.

186

Attempted to write the wrong extent of a multi-extent data set.

204

Record not found.

208

Error accessing the file.

212

Insufficient memory for internal buffers.

216

Internal error.

218

The structure of the index tree is corrupted. A key on a higher level of the tree does not match the last key on a lower level.

219

The structure of the index tree is corrupted. The indicated key value, or a higher value, was not found in the block.

220

Invalid function.

224

Invalid timestamp

284

Invalid chain of index elements - rebuild index and rerun process.

The CTVGICL utility ends with a return code of 16.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error and rerun the CTVGICL utility.

  3. If necessary contact your INCONTROL administrator.

GIX04AE GLOBAL INDEX READ ERROR, RC=rcLink copied to clipboard

Explanation: An error occurred while reading data from the Global Index database.

In this message, rc is the return code from the Global Index interface routine.

The explanations of the possible values of rc depend on whether the Global Index database is an IOA Access Method file or a DB2 database. These explanations appear in the following tables.

rc

IOA Access Method Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Incorrect input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

rc

DB2 Database Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The Global Index request is not performed.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error.

  3. Restart the IOA application server or rerun the job.

  4. If necessary contact your INCONTROL administrator.

GIX04BE DELETE REPORT FROM DB2 TABLE tableName FAILED, RC=rcLink copied to clipboard

Explanation: An attempt to delete report entries from a DB2 table failed.

The variables in this message are:

  • tableName - the identity of the DB2 table

  • rc - the internal return code from the DB2 Global Index interface routine

Possible values for rc are:

Return Code

Explanation

12

Invalid function

20

Not enough storage

48

SETPATH was not issued before value accessing

56

Error opening the CTDGIDB2 member

60

Invalid parameter found in the CTDGIDB2 member

64

Obligatory parameter missing from the CTDGIDB2 member

68

Duplicate parameter found in the CTDGIDB2 member

72

More than 10 fields found in a PATH description in the CTDGIDB2 member.

76

DB2 open error

80

Accessing path not present in the CTDGIDB2 member

84

SQL error

85

SQL error if time-out occurs

88

Error in loading the DB2 interface module

The CTVGICL utility ends with a return code of 16.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error.

  3. Rerun the CTVGICL utility.

  4. If necessary contact your INCONTROL administrator.

GIX04CW REQUEST IS REJECTED. PLEASE TRY AGAIN LATERLink copied to clipboard

Explanation: A request to retrieve data from the Global Index DB2 database is rejected because the corresponding DB2 table is in use by another job that is loading or deleting data. This message is directed to the WebAccess user who issued the request.

The Global Index request is not performed.

Corrective Action: Reissue the request later.

GIX04DE DELVAL FUNCTION FAILED, RC=rcLink copied to clipboard

Explanation: An error occurred while deleting an index value from the Global Index IOA Access Method database file.

In this message, rc is the internal return code from the Global Index interface routine. Possible values are explained in the following table.

rc

Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Invalid input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

The CTVGICL utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Search the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error.

  3. Rerun the CTVGICL utility.

  4. If necessary contact your INCONTROL administrator.

GIX04EE PARAMETER DELPATH IS MISSING FOR DELVAL FUNCTIONLink copied to clipboard

Explanation: The CTVGICL utility detected that the DO Control-D input parameter was set to DELVAL, but the DELPATH input parameter that is mandatory in this case was not found.

The CTVGICL utility ends with a return code of 08.

Corrective Action: Insert the DELPATH parameter in the JCL and rerun the job.

GIX04FE ERROR DELETING VALUE: indexValue, RC=rcLink copied to clipboard

Explanation: An error occurred while deleting an index value from the Global Index IOA Access Method database file.

The variables in this message are:

  • indexValue - the problematic index value

  • rc - the internal return code from the Global Index interface routine.

Possible values for rc are:

rc

Explanation

00

OK

04

End of file. Key not found.

12

Invalid function.

20

Not enough storage.

24

Not enough storage in GIR file.

28

Not enough storage in GIRI file.

32

There is no DBO block.

40

Invalid LRECL or KEYLEN in data or index file. Invalid input parameter.

48

SETPATH was not issued.

100 through 199

DBS error codes.

200 through 299

DBI error codes.

The CTVGICL utility ends with a return code of 08.

Corrective Action: Do the following:

  1. Examine the IOA Log file and the relevant job log for messages clarifying the source of the error.

  2. Correct the error.

  3. Rerun the CTVGICL utility.

  4. If necessary contact your INCONTROL administrator.

GIX04GI VALUE DELETED: indexValueLink copied to clipboard

Explanation: This information message identifies the index value which is being deleted when you invoke the DO=DELVAL function of the CTVGICL utility.

In this message, indexValue is the identity of the index value that is being deleted.

Corrective Action: No action is required.

GIX04II FROM DB2TABLE tableNameLink copied to clipboard

Explanation: This information message identifies the DB2 table name from which the reports were deleted. This message is followed by one or several instances of messages GIX047I.

Corrective Action: No action is required.

GIX04JE REQEST REJECTED. INDEX NAME/VALUE CANNOT BE SPECIFIED AS A MASKLink copied to clipboard

Explanation: The index name or index value specified in the Control-D Web/Access Filter window contains a mask character (* or ?).

The request is rejected.

Corrective Action: Specify the index name or index value in the Filter in full, without any mask character, and reissue the request.

GIX04KE DB2 TABLE tableName READ ERROR, RC=rcLink copied to clipboard

Explanation: An attempt to read data from a DB2 table failed.

The variables in this message are:

  • tableName - the identity of the DB2 table

  • rc - the internal return code from the DB2 Global Index interface routine

Possible values for rc are:

rc

Explanation

76

DB2 open error

84

SQL error

85

SQL error if timeout occurred

The CTVGICL utility skips this DB2 table and continues to work with other tables specified in the parameters.

Corrective Action: Do the following:

  1. Examine the IOA Log file for messages clarifying the source of the error.

  2. Correct the error and if the specified DB2 table should be cleaned, rerun the utility

GIX04LI FROM DB2 TABLE tableName WERE DELETED number ENTRIESLink copied to clipboard

Explanation: This information message provides the number of entries deleted from the tableName DB2 table.

The variables in this message are:

  • tableName - the name of the DB2 table

  • number - the number of deleted entries

Corrective Action: No action is required.

GIX04NI USER userName JOBNAME jobName KEY key - entryLink copied to clipboard

Explanation: This information message identifies a report that was deleted by the CTVGICL utility.

The variables in this message are:

  • userName - the identity of the user of the deleted report

  • jobName - the identity of the job that created the deleted report

  • key - entry - the identity of the VSA record key of the deleted report

Corrective Action: No action is required.

GTM messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages GTM0 through GTM0xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

GTM001W taskName : COMMUNICATION IS NOT ACTIVELink copied to clipboard

Explanation: Communication with the Enterprise Manager gateway was disconnected. IOAGATE reported the disconnection to the application server of Control-M. The taskName task of the application server issues this message.

The application server waits until communication is connected again.

Corrective Action: Check IOAGATE messages to identify and fix the communication problem.

GTM002W taskName : NO RESPONSE RECEIVED WITHIN EXPECTED TIME INTERVALLink copied to clipboard

Explanation: The Enterprise Manager gateway did not respond to an IOAGATE transmission within the time allowed.

The Control-M application server waits for a message from the Enterprise Controlstation gateway.

Corrective Action: Check the Enterprise Manager gateway to find out why it is not responding.

GTM003E taskName : COMMUNICATION SLOWDOWN ENCOUNTEREDLink copied to clipboard

Explanation: IOAGATE buffers are full. IOAGATE can not accept any new messages from the Control-M application server. IOAGATE informs the application server. The taskName task of the application server tries to transmit again several times and, if it does not succeed, issues this message.

The Control-M application server stops.

Corrective Action: Check IOAGATE messages to try to identify and fix the problem. If necessary, contact BMC Customer Support.

GTM004E taskName : MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: funcName RC=rcLink copied to clipboard

Explanation: An internal error occurred in the MBX API.

The Control-M application server terminates.

Corrective Action: Contact BMC Customer Support.

GTW messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages GTWG00 through GTWGxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

GTWG00I ENTERPRISE/CS MAINFRAME GATEWAY STARTEDLink copied to clipboard

Explanation: This information message indicates a normal start of MVS Gateway for Enterprise Controlstation.

Corrective Action: No action is required.

GTWG01I ENTERPRISE/CS MAINFRAME GATEWAY TRACE LEVEL IS SET TO debugLevelLink copied to clipboard

Explanation: This information message indicates that the Enterprise Controlstation Mainframe Gateway DEBUG level was set by an operator modify command (F).

The TRACE level is set to a new level. Each TRACE level activates the trace option on different components of the Enterprise Controlstation Mainframe Gateway.

Corrective Action: No action is required.

GTWG02E ENTERPRISE/CS MAINFRAME GATEWAY NOT APF-AUTHORIZEDLink copied to clipboard

Explanation: The Enterprise Controlstation Mainframe Gateway is not APF-authorized. The CTWGTW module is not in an APF-authorized library or does not have the AC=1 attribute.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Either add the library name in which CTWGTW resides to the IEAAPF00 member in SYS1.PARMLIB, or relink the module with the AC=1 attribute.

GTWG03E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:Link copied to clipboard

Explanation: An operator modify command (F) passed an erroneous parameter to the Enterprise Controlstation Mainframe Gateway. One or more GTWG25I messages are displayed on the operator console after this message, each containing a valid modify parameter.

The modify command is rejected.

Corrective Action: Enter a valid modify parameter.

GTWG04E BLDL/ATTACH FAILED FOR TASK modNameLink copied to clipboard

Explanation: Initialization of an IOAGATE internal task failed. The system code indicating the exact reason can be found in the system log. Possible causes are:

  • The modName module is not in the IOAGATE Load library.

  • Insufficient storage is available for the IOAGATE.

The IOAGATE shuts down.

Corrective Action: Call your system programmer for assistance. If necessary, increase the IOAGATE REGION size.

GTWG05E UNRECOVERABLE ERROR ENCOUNTEREDLink copied to clipboard

Explanation: An unrecoverable error occurred in the operation of the Enterprise Controlstation Mainframe Gateway. The IOA Log, or the Enterprise Controlstation Mainframe Gateway JES messages file or SYSPRINT file, should contain a message with more details about the error. See also, GTWA01W.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.

GTWG06E ONE OF THE SUBTASKS HAS ABENDEDLink copied to clipboard

Explanation: One of MVS Gateway for Enterprise Controlstation’s internal subtasks has abended.

MVS Gateway for Enterprise Controlstation shuts down with user abend 0006. A dump of the abending task is included in the SYSABEND output file.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

GTWG07I SHUT DOWN UPON REQUEST FROM OPERATORLink copied to clipboard

Explanation: This information message confirms that an operator command (P) was issued, requesting shutdown of MVS Gateway for Enterprise Controlstation. This message is followed by message GTWG20I, indicating completion of the shutdown.

MVS Gateway for Enterprise Controlstation starts to shut down.

Corrective Action: No action is required.

GTWG10E TRACE LEVEL MUST BE A NUMBER BETWEEN 0 AND 255Link copied to clipboard

Explanation: An invalid TRACE level was entered, either in the operator modify command (F) or in the operator start command (S). When activating the Enterprise Controlstation trace facilities, specify a number from 0 through 255, inclusive, for the TRACE level. 0 specifies no tracing.

Corrective Action: Issue the command again with the correct TRACE level. The required TRACE level should be supplied by BMC Customer Support.

IOAGATE continues executing

GTWG11I SERVICE ID "id " IS {ENABLED | DISABLED}Link copied to clipboard

Explanation: This information message confirms the current enable or disable status of service ID, after the operator has issued an operator modify command (F) that enables or disables it.

Corrective Action: No action is required.

GTWG20I CONTROL-M NJE GATEWAY SHUTTING DOWNLink copied to clipboard

Explanation: This information message is issued when the Control-M NJE Gateway shuts down, either as a result of an operator command (P), or due to internal Control-M NJE Gateway events. The Control-M NJE Gateway log, the Control-M NJE Gateway JES messages file, or the SYSPRINT file usually contain additional messages concerning the reason for the shutdown.

The Control-M NJE Gateway shuts down.

Corrective Action: No action is required.

GTWG21S CONTROL-M NJE GATEWAY ENDED WITH ERRORSLink copied to clipboard

Explanation: The Control-M NJE Gateway ended with an error. The Control-M NJE Gateway log, the Control-M NJE Gateway messages file, or the SYSPRINT file usually contain additional messages about the specific error.

The Control-M NJE Gateway shuts down.

Corrective Action: Check the Control-M NJE Gateway log or the system log for the reason. Call your system programmer for assistance if needed. Try to restart the Control-M NJE Gateway.

GTWG23I CONTROL-M NJE GATEWAY INTERVAL IS SET TO nn SECONDSLink copied to clipboard

Explanation: This information message displays the current NJE Gateway sleeping interval after it is set by an operator Modify command (F).

The NJE Gateway wakes up every nn seconds to check what it must do.

Corrective Action: No action is required.

GTWG24E INTERVAL MUST BE A TWO-DIGIT NUMBER BETWEEN 03 AND 99 SECONDSLink copied to clipboard

Explanation: Invalid Enterprise Controlstation Mainframe Gateway sleeping interval specified in an operator modify command (F). The Enterprise Controlstation Mainframe Gateway sleeping interval must be a 2-digit number from 03 to 99 seconds.

The modify command is rejected.

Corrective Action: Enter a valid sleeping interval.

GTWG25I validParmLink copied to clipboard

Explanation: This information message accompanies message GTWG03E, which indicates that an invalid modify parameter was specified. This message contains a valid modify parameter. This message may appear more than once. Each occurrence lists another valid modify parameter.

Corrective Action: No action is required.

GTWG30E CTGPUT FAILED. TASKID=taskId PUTID=putId RC=rcLink copied to clipboard

Explanation: Control-M NJE Gateway detected an internal error. Internal CTWPUT operation that was issued by PUTID putId, under subtask number taskId, failed with return code rc. If the return code was 20, a GETMAIN failure occurred above the 16M line.

For some errors, Control-M NJE Gateway shuts down. For other errors, operation continues.

Corrective Action: If Control-M NJE Gateway shuts down, contact BMC Customer Support. If rc was 20, increase the region size.

GTWG31W YOUR IOA GATEWAY IS ALREADY ACTIVE. QNAME qNameLink copied to clipboard

Explanation:Highlighted, unrollable message.

An attempt was made to start an Control-M NJE Gateway that was already active. Two Control-M NJE Gateways with the same QNAME cannot run at the same time in the same MVS. If resources are shared by more than one MVS, this restriction applies to every MVS that shares these resources.

The newly started Control-M NJE Gateway shuts down.

Corrective Action: No action is required.

GTWG34E UNABLE TO OPEN DACONN PARAMETER FILELink copied to clipboard

Explanation: The Control-M NJE Gateway main task failed to open the DACONN DD statement at startup. The DD statement is probably missing.

The started NJE Gateway task stops.

Corrective Action: Correct the problem, and restart the job.

GTWG35E EMPTY PARAMETER FILELink copied to clipboard

Explanation: The Control-M NJE Gateway main task read an empty parameter file at startup.

The started NJE Gateway task stops.

Corrective Action: Correct the problem, and restart the job.

GTWG36E INVALID CARD nnnn. DATA=dataLink copied to clipboard

Explanation: At startup, the specified statement in the parameter file was not valid.

The started Control-M NJE Gateway task stops.

Corrective Action: Correct the problem, and restart the job.

GTWG37E DUPLICATE CARD nnnn. DATA=dataLink copied to clipboard

Explanation: At startup, the specified statement in the parameter file occurred twice.

The started Control-M NJE Gateway task stops.

Corrective Action: Correct the problem, and restart the job.

GTWG38E IN-COMPLETE MFCONNECTION. THREE CARDS MUST BE PROVIDEDLink copied to clipboard

Explanation: At startup, the MFCONNECTION was defined incorrectly. The MFCONNECTION description must include one MFCONNECTION statement, and two HOST descriptor statements.

The started Control-M NJE Gateway task stops.

Corrective Action: Review installation instructions, correct the problem, and restart the job.

GTWG39E INVALID HOST DESCRIPTOR CARD nnnn. DATA=dataLink copied to clipboard

Explanation: At startup, the MFCONNECTION definition was not valid. Either the syntax of one of the two statements following MFCONNECTION is not valid, or the definition names a host system that was not specified.

The started Control-M NJE Gateway task stops.

Corrective Action: Review installation instructions, correct the problem, and restart the job.

GTWG40E INVALID MF CONNECTION CARD nnnn. DATA=dataLink copied to clipboard

Explanation: At startup, the syntax of the MFCONNECTION statement was not valid.

The started Control-M NJE Gateway task stops.

Corrective Action: Review installation instructions, correct the problem, and restart the job.

GTWG41E DUPLICATE MF CONNECTION CARD nnnn. DATA=dataLink copied to clipboard

Explanation: At startup, the MFCONNECTION statement in the specified statement was already defined earlier. During comparison of MFCONNECTION statements, the order of the host arguments on the statement is not significant.

The started Control-M NJE Gateway task stops.

Corrective Action: Correct the problem, and restart the job.

GTWG42E MAINFRAME OR WORKSTATION CONNECTION MISSINGLink copied to clipboard

Explanation: At startup, there was no MFCONNECTION definition in the parameter file. The parameter file must contain at least one MFCONNECTION definition.

The started Control-M NJE Gateway task stops.

Corrective Action: Correct the problem, and restart the job.

GTWG43E INVALID EXEC PARMLink copied to clipboard

Explanation: At startup, the EXEC PGM parameter specified in the started task of the NJE Gateway was not valid.

The started Control-M NJE Gateway task stops.

Corrective Action: Review installation instructions, correct the problem, and restart the job.

GTWG44E HOST AND PARTNER NAMES CANNOT BE THE SAMELink copied to clipboard

Explanation: At startup, the HOST and CONNECT initialization parameters were identical. The HOST parameter identifies the local host, and the CONNECT parameter identifies a partner host. They cannot be the same.

The main Control-M NJE Gateway task stops.

Corrective Action: Correct the HOST and CONNECT parameters, and restart the job.

GTWG45E ECAGATE INTERNAL ERROR. CODE=rc, USER=userIdLink copied to clipboard

Explanation: Due to an internal error, an internal call (ECAPUT) failed with return code rc. In this message, userId identifies the user from whom the message was received.

The message causing the error is ignored.

Corrective Action: Contact BMC Customer Support.

ILY messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

Messages ILY400 through ILY4xxLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

ILY411S OPEN OF DDNAME "DAPROG" FAILED.Link copied to clipboard

Explanation: This message is issued by the New Day procedure. The data set described by the DAPROG DD statement contains a list of programs to be activated by the New Day procedure. Possible causes are:

  • The DAPROG DD statement is missing.

  • The data set described by the DAPROG DD statement cannot be opened for sequential read.

For more details, see the chapter that discusses implementation issues in the appropriate user guide.

The New Day procedure stops executing.

Corrective Action: Correct the JCL for the job and rerun it.

ILY412I DAILY STARTED IN mode MODELink copied to clipboard

Explanation: This general information message is issued when the Control-D monitor starts the DAILY (New Day) process in one of the following modes:

  • INT - internal mode. The Control-D monitor executes simultaneously with the New Day procedure.

  • EXT - external mode. The Control-D monitor starts the New Day procedure, and then shuts down the Control-D monitor.

Corrective Action: No action is required.

ILY413E PROGRAM pgm WAS NOT FOUNDLink copied to clipboard

Explanation: The pgm program was not in the load list of the Daily subsystem. The DAPROG DD statement describes a data set that contains a list of programs to be activated as part of the Daily subsystem.

The Daily subsystem terminates with errors.

Corrective Action: Check whether IOA Load library is concatenated as STEPLIB to the Daily subsystem. Correct the JCL and consult your system programmer about running the Daily subsystem again.

ILY414E INVALID CONDITION CODE FOR PROGRAM pgmLink copied to clipboard

Explanation: The pgm Control-M or Control-D internal program that was activated by New Day processing finished with a return code higher than the maximum allowed in the program list. Positions 10-11 in the program list indicate the highest return code that is still considered OK for this program.

Corrective Action: No action is required.

ILY415I PROGRAM pgm IS BEING INVOKEDLink copied to clipboard

Explanation: This information message indicates that the pgm internal Control-M or Control-D program was activated by New Day processing.

Corrective Action: No action is required.

ILY416I {CTMILY | CTDILY} ENDEDLink copied to clipboard

Explanation: This information message indicates that New Day processing is finished.

Corrective Action: No action is required.

ILY417E UNRECOGNIZED PARAMETER ON EXEC STATEMENT: expressionLink copied to clipboard

Explanation: The CTMTDAY procedure was executed with an unsupported or invalid NEWDAY parameter value expression. (For more information on the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”)

The CTMTDAY procedure is not executed.

Corrective Action: Correct and re-execute the CTMTDAY procedure.

ILY418E UNRECOGNIZED PARAMETER ON EXEC STATEMENT: expressionLink copied to clipboard

Explanation: The CTMTDAY procedure was executed with the following NEWDAY parameter: date. However, the date format or contents are invalid. For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”

The CTMTDAY procedure is not executed.

Corrective Action: Correct and re-execute the CTMTDAY procedure.

ILY419I PROCESSING MODE IS modeLink copied to clipboard

Explanation: The CTMTDAY procedure was executed with one the following NEWDAY mode parameters:

  • ORDERONLY[,date]

  • FORMATONLY

Special NEWDAY processing will be performed according to the mode (FORMATONLY or ORDERONLY) specified in the procedure. (For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”)

Corrective Action: No response is required.

ILY41AW DATE IGNORED IN 'FORMATONLY' REQUEST: xxxxxxxLink copied to clipboard

Explanation: The CTMTDAY procedure is executed with the following NEWDAY parameter:

FORMATONLY,xxxxxx

where the operator probably intended xxxxxx as a date value. (A date is not valid with the FORMATONLY mode.)

Special NEWDAY processing is performed according to the FORMATONLY mode, ignoring xxxxxx. (For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”)

Corrective Action: No response is required.

IOA messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages IOA0 through IOA0xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA001E INVALID PARAMETERLink copied to clipboard

Explanation: An invalid parameter was passed to IOAZAP on the EXEC statement. The PARM parameter in the JCL EXEC statement was manually modified incorrectly.

The program stops execution with a condition code of 08. All the zaps that follow will be bypassed.

Corrective Action: Restore the original JCL job stream as follows:

  1. Using the documentation provided as part of the IOA Monthly Maintenance Upgrade System, transfer the JCL job stream from the diskette to the mainframe.

  2. Modify the JCL as specified in the documentation.

  3. Submit the job.

You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.

IOA003I dd/mm/yy IOAZAP PROCESSING STARTED FOR CONTROL-x release VERSION versionLink copied to clipboard

Explanation: This information message is the normal start message produced by the IOA automatic zap application program.

Corrective Action: No action is required.

IOA004I dd/mm/yy IOAZAP PROCESSING COMPLETED FOR CONTROL- x rel VERSION verLink copied to clipboard

Explanation: This information message is the normal termination message produced by the IOA automatic zap application program.

Corrective Action: No action is required.

IOA005S OPEN OF DDNAME ddName FAILEDLink copied to clipboard

Explanation: The automatic zap application program failed to open the ddName DD statement. Possible causes are:

  • The ddName DD statement is missing.

  • The data set described by the ddName DD statement does not exist.

The program stops execution with a condition code of 08.

Corrective Action: The JCL was probably modified incorrectly. Restore the original JCL job stream, as follows:

  1. Using the documentation provided as part of the IOA Monthly Maintenance Upgrade system, transfer the JCL job stream from the diskette to the mainframe.

  2. Modify the JCL as specified in the documentation.

  3. Submit the job.

You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.

IOA007S AMASPZAP REPORTED ERROR IN STEP stepName FOR ZAP descLink copied to clipboard

Explanation: The AMASPZAP utility reported that an error occurred in the zap.

The program stops execution with a condition code of 08. All zaps that follow are bypassed.

Corrective Action: Check the report produced by the AMASPZAP utility to determine the cause of the problem. The zap was probably modified incorrectly. Restore the original JCL job stream, as follows:

  1. Using the documentation provided as part of the IOA Monthly Maintenance Upgrade system, transfer the JCL job stream from the diskette to the mainframe.

  2. Modify the JCL as specified in the documentation.

  3. Submit the job.

You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.

If the problem is not due to a user modification of the zap, contact BMC Customer Support for assistance. Your representative will need the report produced by the AMASPZAP utility to resolve the problem.

IOA008S SYNTAX ERROR ON LINE lineNum IN STEP stepName FOR ZAP descLink copied to clipboard

Explanation: The automatic zap application program found that statement number lineNum in JCL step stepName is not valid. The problem is caused by an incorrect manual modification of the zap.

This message is followed by message IOA015S, which displays the statement in error in the damaged JCL job stream.

The program stops execution with a condition code of 08. All zaps that follow will be bypassed.

Corrective Action: Restore the original JCL job stream as follows:

  1. Using the documentation provided as part of the IOA Monthly Maintenance Upgrade system, transfer the JCL job stream from the diskette to the mainframe. The job stream contains both the JCL and zaps.

  2. Modify the JCL job stream as specified in the documentation.

  3. Submit the job.

You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.

IOA009S INVALID REP ON LINE lineNum IN STEP stepName FOR ZAP descLink copied to clipboard

Explanation: The automatic zap application program found that statement number lineNum in JCL step stepName is not valid. The problem is caused by incorrect manual modification of the zap.

This message is followed by message IOA015S, which displays the statement in error in the damaged JCL job stream.

The program stops execution with a condition code of 08. All the zaps that follow will be bypassed.

Corrective Action: Restore the original JCL job stream, as follows:

  1. Using the documentation provided as part of the IOA Monthly Maintenance Upgrade system, transfer the JCL job stream from the diskette to the mainframe. The job stream contains both the JCL and zaps.

  2. Modify the JCL job stream as specified in the documentation.

  3. Submit the job.

You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.

IOA010S TOO MANY INPUT CARDS FOR ONE ZAPLink copied to clipboard

Explanation: Too many statements were added to the zap. Message IOA013I can be used to determine which zap caused the problem.

The program stops execution with a condition code of 08. All zaps that follow will be bypassed.

Corrective Action: Restore the original JCL job stream, as follows:

  1. Using the documentation provided as part of the IOA Monthly Maintenance Upgrade system, transfer the JCL job stream from the diskette to the mainframe. The job stream contains both the JCL and zaps.

  2. Modify the JCL job stream as specified in the documentation.

  3. Submit the job.

You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.

IOA011I ZAP ALREADY APPLIED - PROCESSING CONTINUESLink copied to clipboard

Explanation: This information message indicates that the zap was previously applied, and is being bypassed by the IOA automatic zap application program. This message is preceded by message IOA013I, which can be used to determine which zap was bypassed.

The processing of the rest of the zaps continues.

Corrective Action: No action is required.

IOA011S LINKAGE FAILED ON STEP stepLink copied to clipboard

Explanation: An attempt to relink a module during maintenance failed at the step indicated in the message.

The job stops processing at the failed step. The cause of the problem is indicated in the job output.

Corrective Action: Check the job output for the cause of the problem, and correct accordingly; then rerun the job. If you cannot correct the problem, notify BMC Customer Support.

IOA012I SUCCESSFUL APPLICATION OF ZAP descLink copied to clipboard

Explanation: This information message indicates that the Zap desc was successfully applied.

The processing of the rest of the zaps continues.

Corrective Action: No action is required.

IOA013I IOAZAP STEP stepName PROCESSING STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOA automatic zap application program, which is executing at step stepName, started to process the zap.

Corrective Action: No action is required.

IOA014I IOAZAP STEP stepName PROCESSING COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the IOA automatic zap application program, which is executing at the stepName step, finished successfully.

The processing of the rest of the zaps continues.

Corrective Action: No action is required.

IOA015S LINE IN ERROR: stmtLink copied to clipboard

Explanation: Incorrect manual modification of a zap.

In this message, stmt is the statement that was incorrectly modified.

The IOA automatic zap application program ends with errors.

Corrective Action: Refer to previous messages, which describe the type of error.

IOA017I date FORMAT OF databaseLink copied to clipboard

Explanation: This information message indicates that one of the IOA databases was formatted. The format procedure writes an audit trail message to the IOA maintenance log.

Corrective Action: No action is required.

IOA018I SUCCESSFUL LINKAGE EXECUTION "zapText"Link copied to clipboard

Explanation: This information message indicates that the IOAZAP utility successfully relinked a module. Occasionally, it is necessary to relink a module for maintenance purposes.

Corrective Action: No action is required.

IOA019W ZAP IS NOT REQUIRED - PROCESSING BYPASSEDLink copied to clipboard

Explanation: This message indicates that the zap is not required by this installation. IOA maintenance can support various configurations, including enhancement tapes. For this reason, not all zaps supplied are required by your installation.

Corrective Action: No action is required.

IOA020E IOAZAP STEP stepName PROCESSING COMPLETED WITH ERRORLink copied to clipboard

Explanation: This error message indicates that IOAZAP maintenance step stepName failed to complete. Possible causes are:

  • There is an error in the zap, possibly a typing error.

  • The load library needs to be compressed.

  • You do not have the necessary security authorization to apply zaps.

Corrective Action: If possible, correct the error and rerun the step. Otherwise, contact BMC Customer Support.

IOA036E LOAD-INDEX API FAILED, RC: rc REASON: rsnLink copied to clipboard

Explanation: An internal error occurred in CTMAPI.

The following return codes are possible:

Return Code

Meaning

0

Load-Index API ended successfully.

4

Load-Index API ended with warning.

8

Load-Index API ended with error.

12

Load-Index API ended with fatal error.

Corrective Action: The following table provides troubleshooting guidelines for various possible reason codes. For any other reason code, contact BMC Support.

Reason Code

Issue

Corrective Action

24

Cannot allocate the WLI file.

Check if the WLI file exists.

28

The Workload Policy does not exist in the WLI file.

Fix the Workload Policy name and try again.

32

Insufficient storage space; could not allocate memory.

Add more storage space.

36

Failed to open the WLI file.

Contact BMC Support.

48

Failed to close the WLI file.

Contact BMC Support.

60

Failed to read the WLI file.

Contact BMC Support.

64

Failed to write the WLI file.

Contact BMC Support.

96

WLI file has invalid format.

Check the WLI file and try again.

100

WLI file header is invalid.

Check the WLI file and try again.

IOA046S BLDL/LOAD FAILED FOR THE MODULE modNameLink copied to clipboard

Explanation: Loading of the modName module failed.

Possible causes are:

  • The IOA Load library is not in the load modules search list (STEPLIB + Linklist).

  • There is insufficient memory.

  • There is some other system-oriented reason, which may be found in the syslog.

Execution might stop.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

IOA049I NEW HISTORY JOBS FILE SUCCESSFULLY CREATEDLink copied to clipboard

Explanation: This information message indicates that the CTMHCOP utility successfully created a new History Jobs file from the old one.

Corrective Action: No action is required.

Messages IOA100 through IOA1xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA100I srvr - IOA ARCHIVE SERVER INITIALIZATION STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server has started and is currently building the required internal environment.

Corrective Action: No action is required.

IOA101E srvr - IOA ARCHIVE SERVER INITIALIZATION FAILED RC rc IN STEP stepLink copied to clipboard

Explanation: The IOA Archive Server encountered an internal error.

The cross-memory environment could not be established.

The IOA Archive Server shuts down.

Corrective Action: Activate the Control-D subsystem. If it is already active, deactivate then reactivate it. Try to reactivate the IOA Archive server. If this does not help, check for other system messages that might clarify the cause of the problem and precede accordingly. If these measures are of no avail, record the return code, step name and all other related messages and contact BMC Customer Support.

IOA102E srvr - IOA ARCHIVE SERVER NOT APF-AUTHORIZEDLink copied to clipboard

Explanation: The IOA Archive Server is not APF (Authorized Programming Facility) authorized. The IOASSRV module is not in an APF authorized library or does not have attribute AC=1.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Add the name of the library in which the IOASSRV module resides to the IEAAPF00 member in the SYS1.PARMLIB library.

IOA103E srvr - COMMAND FAILED - cmdTextLink copied to clipboard

Explanation: An invalid command or parameter was passed to the IOA Archive Server by an operator MODIFY command. This message is accompanied by another message that indicates why the command failed.

The MODIFY command is not executed.

Corrective Action: See the accompanying message, which indicates why the command failed.

IOA104S srvr BLDL/LOAD FAILED FOR THE MODULE modNameLink copied to clipboard

Explanation: Loading of the modName module failed. Possible causes are:

  • Insufficient memory.

  • Another system-oriented cause may be found in the system log.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Check the system job log for more information. If the problem persists, contact BMC Customer Support.

IOA105S srvr - UNRECOVERABLE ERROR ENCOUNTEREDLink copied to clipboard

Explanation: An unrecoverable error occurred in the operation of the IOA Archive Server.

The IOA Log file should contain a previous message about the error.

The IOA Archive Server shuts down.

Corrective Action: Check the accompanying message in the IOA Log file. Contact your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

IOA106S srvr - MEDIA mediaName HAS ABENDEDLink copied to clipboard

Explanation: An IOA Archive Server internal subtask abended.

The IOA Log file and system log should contain previous messages about this error.

The IOA Archive Server issues an implicit START command for this media. Attempts are made to initialize media mediaName and continue normal processing. If these attempts fail, the IOA Archive Server sets the status of the abended media to never active and this media becomes unavailable for use by the IOA Archive Server.

Corrective Action: Check the IOA Log file and system log for additional messages which may indicate why media mediaName abended. If the problem is not resolved, contact BMC Customer Support.

IOA107I srvr - SHUT DOWN UPON REQUEST FROM OPERATORLink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server is shutting down upon operator’s request.

Corrective Action: No action is required.

IOA108E srvr - REASON: COMMAND IS INVALIDLink copied to clipboard

Explanation: An invalid command was passed to the IOA Archive Server. This message follows message IOA103E or SRV103E, which contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section that describes the IOA Archive Server in the Control-D and Control-V User Guide. Enter a valid MODIFY command.

IOA109S srvr - MEDIA TYPE media_type IS INVALID OR NOT SUPPORTEDLink copied to clipboard

Explanation: The IOA Archive Server encountered an invalid or unsupported media type specified in the IOASPRM member (IOA Archive Server Installation Parameters).

The media type specified in the IOASPRM member should match one of the supported media types specified in the IOA Archive Server Program List (the IOASPROG member).

The IOA Archive Server terminates with a return code of 8.

Corrective Action: For more information about currently supported media types, refer to the section on how to set IOA Archive Server Installation Parameters in the INCONTROL for z/OS Installation Guide. Correct the media_type in the IOASPRM member (IOA Archive Server Installation Parameters). Start the IOA Archive Server again. If the problem is not resolved, contact BMC Customer Support.

IOA10AS srvr - SERVER NAME IS NOT EQUAL TO THE PROCNAME SPECIFIED IN IOASPRMLink copied to clipboard

Explanation:Highlighted, unrollable message.

The name of IOA Archive Server does not match the value of the PROCNAME parameter in the IOASPRM member. The name of the IOA Archive Server must be the same as the value of the PROCNAME IOA Archive Server Installation Parameter in the IOASPRM member.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Use the correct IOA Archive Server name or correct the value of the PROCNAME parameter. Restart the IOA Archive Server.

IOA10BI srvr - IOA ARCHIVE SERVER SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the IOA Archive Server is shutting down due to operator command or due to internal events.

The IOA Log file should contain additional messages about the reason for shutting down the IOA Archive Server.

The IOA Archive Server shuts down.

Corrective Action: No action is required.

IOA10CS srvr - IOA ARCHIVE SERVER ENDED WITH ERRORLink copied to clipboard

Explanation: An error caused the IOA Archive Server to terminate. The IOA Log file and system log file should contain additional messages identifying the specific error.

The IOA Archive Server shuts down.

Corrective Action: Check the IOA Log file and the system log for the reason. Contact your system programmer for assistance if needed.

IOA10DW srvr - YOUR IOA ARCHIVE SERVER IS ALREADY ACTIVE. QNAME qNameLink copied to clipboard

Explanation:Highlighted, unrollable message.

An attempt was made to start an IOA Archive Server which is already active. It is impossible to run two IOA Archive Servers with the same qName at the same time.

The newly-started IOA Archive Server with the same qName shuts down.

Corrective Action: No action is required.

IOA10EE srvr - REASON: PARAMETER IS INVALIDLink copied to clipboard

Explanation: An invalid parameter was passed to the IOA Archive Server by operator command MODIFY. This message follows the IOA103E or SRV103E message, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more details, refer to the section that describes the IOA Archive Server in the Control-D and Control-V User Guide. Reissue the MODIFY command with valid parameters.

IOA110E srvr - INSUFFICIENT STORAGE FOR INITIALIZATION RC=rcLink copied to clipboard

Explanation: There is insufficient memory to initiate or operate the IOA Archive Server.

The IOA Archive Server shuts down.

Corrective Action: Increase the IOA Archive Server REGION size. If the problem persists, record the return code and contact BMC Customer Support.

IOA114S srvr - BLDL/ATTACH FAILED FOR MODULE modNameLink copied to clipboard

Explanation: Initialization of an IOA Archive Server internal task failed.

Possible causes are:

  • Insufficient memory to attach the task.

  • The modName module does not exist in the LOAD library.

The IOA Archive Server terminates.

Corrective Action: Check the system log for additional messages which clarify the situation. Try one of the following:

  • If the attach failed because of lack of memory, increase the REGION size in the IOA Archive Server procedure.

  • If the IOA LOAD library does not contain the modName module, contact BMC Customer Support.

IOA115E srvr - OPEN OF DDNAME ddName FAILEDLink copied to clipboard

Explanation: Open of the ddName DD statement failed.

Possible causes are:

  • The ddName DD statement is missing.

  • The data set referenced by the ddName DD statement does not exist.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Correct the JCL and rerun the job.

IOA116W srvr - ALL MEDIA ARE INACTIVELink copied to clipboard

Explanation:Highlighted, unrollable message.

The IOA Archive Server issues this message when it determines that no active media are allocated to it.

Every media was terminated due to operator request or internal error. This message disappears when a START command is issued for any media.

The IOA Archive Server continues processing.

Corrective Action: If information about the status of a media is needed, issue a DISPLAY command.

IOA117I srvr - IOA ARCHIVE SERVER INITIALIZATION COMPLETELink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server was successfully initialized.

Corrective Action: No action is required.

IOA118E srvr - REASON: MEDIA mediaName IS INCORRECTLink copied to clipboard

Explanation: The media was specified in a MODIFY operator command, but was not defined in the IOASPRM member, which defines the IOA Archive Server Installation Parameters. This message follows message IOA103E or SRV103E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more details, refer the section that describes the IOA Archive Server in the Control-D and Control-V User Guide. Reissue the MODIFY command with the correct media name.

IOA11AE srvr - REASON: MEDIA mediaName ALREADY INACTIVELink copied to clipboard

Explanation: An attempt was made to stop media mediaName which was already inactive. This message follows message IOA103E or SRV103E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: No action is required.

IOA11BE srvr - REASON: MEDIA mediaName ALREADY ACTIVELink copied to clipboard

Explanation: An attempt was made to start media mediaName which was already active. This message follows message IOA103Eor SRV103E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: No action is required.

IOA11CE srvr - INITIALIZATION OF ALL MEDIA FAILEDLink copied to clipboard

Explanation: During initialization, the IOA Archive Server determined that initialization failed for all media specified in the IOASPRM member (IOA Archive Server Installation Parameters).

Every media was terminated due to an unrecoverable error. The IOA Log file should contain additional messages concerning specific errors.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Check the IOA Log file and the system log for messages describing the error. Contact the system programmer for assistance if needed. Start the IOA Archive Server again. If the problem is not resolved, contact BMC Customer Support.

IOA11DW srvr - nn CYCLES PERFORMED WHILE WAITING FOR MEDIA INITIALIZATION TO BE COMPLETEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

The IOA Archive Server cannot complete the initialization phase. During IOA Archive Server initialization, a period of time equal to nn cycles elapsed before any media specified for use by the IOA Archive Server completed the initialization process. Each cycle is one IOA Archive Server sleeping interval, whose value in hundredths of a second is defined in the INTERVAL parameter in the IOASPRM member in the IOA Archive Server Installation Parameters.

The initialization of the IOA Archive Server is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If the IOA Archive Server waits a long time for media to complete initialization, and the reason for the delay cannot be determined, issue the CANCEL command to stop the IOA Archive Server. Restart the IOA Archive Server. If the problem is not resolved, contact BMC Customer Support.

IOA11EW srvr - nn CYCLES PERFORMED WHILE WAITING FOR MEDIA TO TERMINATELink copied to clipboard

Explanation: The IOA Archive Server cannot complete the termination phase. During IOA Archive Server termination, a period of time equal to nn cycles elapsed before the media specified for use by the IOA Archive Server completed the termination process. Each cycle is one IOA Archive Server sleeping interval, whose value in hundredths of a second is defined in the INTERVAL parameter in the IOASPRM member in the IOA Archive Server Installation Parameters.

The termination of the IOA Archive Server is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If the IOA Archive Server waits a long time for media to complete termination, and the reason for the delay cannot be determined, issue operator command CANCEL to stop the IOA Archive Server. If the problem is not resolved, contact BMC Customer Support.

IOA11FW srvr - REASON: MEDIA mediaName IS BUSYLink copied to clipboard

Explanation: A command cannot be passed to media mediaName for execution because the media has not finished executing a previous command. This message follows message IOA103E or SRV103E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: Reissue the MODIFY command later.

IOA120S srvr - INTERNAL ERROR RC=rcLink copied to clipboard

Explanation: The IOA Archive Server encountered an internal error.

The IOA Archive Server terminates with abend code 0006. The output includes a dump of the abend.

Corrective Action: Report the message ID and return code to BMC Customer Support.

IOA121E srvr - REASON: MEDIA mediaName INACTIVELink copied to clipboard

Explanation: An attempt was made to start a device assigned to media mediaName while that media was inactive. Media mediaName must be started before issuing a START command for a device assigned to it. This message follows message IOA103E or SRV103E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: Issue an operator command to start media mediaName, as follows: F IOASMON,START MEDIA=mediaName

After media mediaName is initialized successfully, issue the MODIFY command to start a device. For more details, refer to the section that describes the IOA Archive Server in the Control-D and Control-V User Guide.

IOA122W srvr - IOA ARCHIVE SERVER PARAMETERS CONTAIN NO MEDIA OR ONLY MEDIA TYPE DASDLink copied to clipboard

Explanation: During the initialization phase, the IOA Archive Server determined that the IOASPRM member does not include a definition for any media or only includes definitions for media of the DASD type. Possible causes are:

  • The IOASPRM member in the IOA PARM library does not define any media.

  • The IOASPRM member in the IOA PARM library has definitions for only DASD media.

Do not activate the IOA Archive Server unless a media type other than DASD is defined in the IOASPRM member.

The IOA Archive Server shuts down.

Corrective Action: If the services of the IOA Archive Server are required, add appropriate media to the IOASPRM member in the IOA Archive Server Installation Parameters, and restart the IOA Archive Server.

IOA123W cdam_srvr_name - GETMAIN FAILED DURING SESSION OPENING OF USER userIdLink copied to clipboard

Explanation: An attempt to access a migrated index failed because there is insufficient memory in the IOA Archive server to open a session. A session is opened in the IOA Archive server when accessing a migrated index. This error occurs when there is not enough memory in the IOA Archive server to hold the RBA range table of the user, and the index record for that index.

The session is not opened and the migrated index cannot be viewed.

Corrective Action: Increase the region of the IOA Archive server.

IOA124W cdam_srvr_name - OSE TYPE PASSED TO SERVER BY USERID userId IS INVALIDLink copied to clipboard

Explanation: An internal error occurred when accessing a migrated index. A session is opened in the IOA Archive Server when accessing a migrated index.

The session is not opened and the migrated index cannot be viewed.

Corrective Action: Print the user record and index records of the report. Record the last actions of the user before the error occurred. Supply this information to BMC Customer Support.

IOA127E srvr - DEBUG LEVEL MUST BE A NUMBER BETWEEN 0-255Link copied to clipboard

Explanation: The MODIFY operator command to activate the IOA Archive Server debug facility contains an invalid DEBUG level. Valid DEBUG levels are between 0 and 255. Zero specifies no debugging.

The MODIFY command is not executed. The DEBUG facility is not activated.

Corrective Action: Reissue the operator command with the correct debug level. The required debugging level should be supplied by BMC Customer Support.

IOA128I srvr - DEBUG LEVEL IS SET TO lvlLink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server debug level has been set to nnn by a MODIFY operator command.

Each debug level activates the trace option on different components of the IOA Archive Server.

The DEBUG level is set to level nnn.

Corrective Action: No action is required.

IOA130E mediaName - REASON: DEVICE deviceId IS NOT ASSIGNED TO THIS MEDIALink copied to clipboard

Explanation: An attempt was made to reference device deviceId, which currently is not assigned to media mediaName. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more details, refer to the section that describes the IOA Archive Server in the Control-D and Control-V User Guide. Issue a DISPLAY command to obtain information about each media and its resources that are known to the IOA Archive Server. Reissue the MODIFY operator command with the correct deviceId number.

IOA131E mediaName - REASON: DEVICE deviceId ALREADY INACTIVELink copied to clipboard

Explanation: An attempt was made to stop device deviceId, which is currently inactive. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: No action is required.

IOA132E mediaName - REASON: DEVICE deviceId ALREADY ACTIVELink copied to clipboard

Explanation: An attempt was made to start device deviceId, which is currently active. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: No action is required.

IOA133W mediaName - nn CYCLES PERFORMED WHILE WAITING FOR MEDIA INITIALIZATION TO BE COMPLETEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName cannot complete the initialization phase.

During initialization, the media waits for devices which have been started to complete their initialization process. No responses were received from these devices. Each “cycle” is one IOA Archive Server sleeping interval whose value (in hundredths of a second) is defined in the INTERVAL parameter in the IOASPRM member in the IOA Archive Server Installation Parameters.

The initialization of media mediaName is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If media mediaName waits a long time for devices to complete initialization and the reason for the delay cannot be determined, issue a CANCEL operator command to stop the IOA Archive Server. Start the IOA Archive Server again. If the problem is not resolved, contact BMC Customer Support.

IOA134E mediaName - MEDIA SHUT DOWN - INITIALIZATION OF ALL DEVICES FAILEDLink copied to clipboard

Explanation: The initialization process for all devices assigned to media mediaName failed.

Media mediaName is terminated and becomes unavailable for use by the IOA Archive Server.

Corrective Action: Check the IOA Log file and system log for messages about the initialization failure. Issue an operator command to restart media mediaName. If the problem is not resolved, contact BMC Customer Support.

IOA135W mediaName - nn CYCLES PERFORMED WHILE WAITING FOR DEVICE TO TERMINATELink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName cannot complete the termination phase.

During termination, media mediaName waits for devices to terminate. Each “cycle” is one IOA Archive Server sleeping interval whose value (in hundredths of a second) is defined in the INTERVAL parameter in the IOASPRM member in the IOA Archive Server Installation Parameters.

The termination of media mediaName is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If media mediaName waits a long time for devices to complete termination and the reason for the delay cannot be determined, issue a CANCEL operator command stop the IOA Archive Server. If the problem is not resolved, contact BMC Customer Support.

IOA136E mediaName - REASON: LENGTH OF DEVICE NUMBER IN DEVICE= deviceId IS INCORRECTLink copied to clipboard

Explanation: The DEVICE parameter was specified with an invalid length. The length of the DEVICE parameter in the MODIFY operator command should be four digits.

This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: Reissue the MODIFY command with a correct DEVICE parameter.

IOA137E mediaName - COMMAND FAILED cmdTextLink copied to clipboard

Explanation: An invalid command or parameter was passed to media mediaName by a MODIFY operator command. This message is followed by other messages that clarify why the operator command failed.

The MODIFY command is not executed.

Corrective Action: Check the system log for a message that indicates why the command failed. Correct the problem, and reissue the MODIFY operator command.

IOA138E mediaName - REASON: PARAMETER IS INVALIDLink copied to clipboard

Explanation: An invalid parameter was passed to media mediaName by the MODIFY operator command. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Enter a MODIFY command with valid parameters.

IOA139I mediaName - MEDIA SHUT DOWN UPON REQUEST FROM OPERATORLink copied to clipboard

Explanation: This information message indicates that media mediaName is shutting down upon the operator’s request.

Corrective Action: No action is required.

IOA13AI mediaName - MEDIA SHUT DOWN UPON REQUEST OF MAIN TASKLink copied to clipboard

Explanation: This information message indicates that media mediaName is shutting down upon the IOA Archive Server’s request.

Possible causes are:

  • The IOA Archive Server is shutting down due to operator request.

  • The IOA Archive Server encountered an unrecoverable error.

The IOA Archive Server shuts down the media before it shuts down. The IOA Log file and system log should contain additional messages concerning the situation.

Media mediaName shuts down.

Corrective Action: Check the IOA Log file and system log for messages explaining the situation. Contact the system programmer for assistance, if needed.

IOA13BE mediaName - REASON: VALUE SPECIFIED IN DEVICE= PARAMETER IS INVALIDLink copied to clipboard

Explanation: The DEVICE parameter was specified in a modify operator command without specifying its value. This message follows message IOA137E or MDT137E, which indicates that the modify operator command failed, and contains the text of the failed command.

MODIFY is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Reissue the MODIFY command with a valid DEVICE parameter.

IOA13DE mediaName - REASON: DEVICE= PARAMETER IS INVALID FOR DYNAMIC DEVICESLink copied to clipboard

Explanation: An attempt to start a specific device by operator command failed because the devices used by the IOA Archive Server are allocated dynamically. This message follows message IOA137E/MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

MODIFY is not executed.

Corrective Action: For more information about how to control the device, refer to the section on media and resource management in the Control-D and Control-V User Guide. Reissue the MODIFY command with appropriate parameters.

IOA13FW mediaName - REASON: ALL DEVICES ARE ALREADY ACTIVELink copied to clipboard

Explanation: An attempt to start one or more devices by issuing a MODIFY operator command failed, because all devices were already active.

This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command. The operator cannot increase the number of devices the IOA Archive Server can use to more than the maximum quantity defined in the IOASPRM member in the IOA Archive Server Installation Parameters.

The MODIFY command is not executed.

Corrective Action: Issue a DISPLAY command to get information about each media and its resources that are allocated to the IOA Archive Server. For more information about how to control devices, refer to the section on media and resource management in the Control-D and Control-V User Guide.

IOA140S mediaName - BLDL/ATTACH/LOAD FAILED FOR THE MODULE modNameLink copied to clipboard

Explanation: Initialization of the mediaName media failed.

Possible causes are:

  • The Control-V LOAD library is not in the load modules search list (STEPLIB + LinkList).

  • Insufficient memory is available to attach the task.

  • The modName module is not in the LOAD library.

The IOA Archive Server shuts down.

Corrective Action: Check the system log for additional messages which clarify the situation. Try one of the following:

  • If the attach failed because of lack of memory, increase the REGION size in the IOA Archive Server procedure.

  • If the modName module does not exist in the IOA LOAD library, contact BMC Customer Support.

IOA141I mediaName - INITIALIZATION STARTEDLink copied to clipboard

Explanation: This information message indicates that media mediaName has started and is building the required internal environment.

Corrective Action: No action is required.

IOA142I mediaName - INITIALIZATION SUCCESSFULLY COMPLETEDLink copied to clipboard

Explanation: This information message indicates that media mediaName was successfully initialized.

Corrective Action: No action is required.

IOA143W mediaName - REASON: ALL DEVICES ARE ALREADY INACTIVELink copied to clipboard

Explanation: An attempt to stop one or more devices by issuing a MODIFY operator command failed, because all the devices were already inactive. This message follows message IOA137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Issue a DISPLAY command to get information about each media and its resources that are allocated to the IOA Archive Server.

IOA144S mediaName - INSUFFICIENT STORAGE FOR INITIALIZATIONLink copied to clipboard

Explanation:Highlighted, unrollable message.

Insufficient memory is available to initiate media mediaName.

Media mediaName shuts down. The IOA Archive Server shuts down.

Corrective Action: Increase the IOA Archive Server REGION size.

IOA145E mediaName - FREEMAIN ERROR ENCOUNTEREDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName encountered an internal error.

The media mediaName task terminates with User Abend 0007. The IOA Archive Server terminates with User Abend code 0006. The output includes a dump of the abend.

Corrective Action: Contact your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

IOA146E mediaName - MEDIA INITIALIZATION FAILEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName encountered an internal error.

This message is preceded by other messages which clarify the situation.

Media mediaName shuts down.

Corrective Action: Check the IOA Log file and the system log for messages describing the error. Contact your system programmer for assistance, if needed. If the problem is not resolved, contact BMC Customer Support.

IOA147S mediaName - INTERNAL ERROR DURING INITIALIZATION - MEDIA INITIALIZATION FAILEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

The mediaName media encountered an internal error.

The mediaName media abends with User Abend 0007. The IOA Archive Server shuts down with User Abend 0006. The output includes a dump of the abend.

Corrective Action: Contact your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

IOA148S mediaName - INTERNAL ERROR RC=rcLink copied to clipboard

Explanation: Media mediaName encountered an internal error.

One of the following actions occurs, depending on severity of the internal error:

  • Media mediaName terminates and IOA Archive Server continues processing.

  • Media mediaName abends with User Abend 0007. The IOA Archive Server terminates with User Abend 0006. The output includes a dump of the abend.

Corrective Action: Check the IOA Log file and system log for messages describing the error. Contact your system programmer for assistance. If the problem is not resolved, report the rc to BMC Customer Support.

IOA149E mediaName - REASON: COMMAND IS INVALIDLink copied to clipboard

Explanation: An invalid command was passed to media mediaName by the MODIFY operator command. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Enter a valid MODIFY command.

IOA14AE mediaName - REASON: VALUE SPECIFIED IN DEVQTY= PARAMETER IS INVALIDLink copied to clipboard

Explanation: An invalid value was specified for the DEVQTY parameter. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command. Possible causes are:

  • The value for the DEVQTY parameter is missing in the MODIFY operator command.

  • The length of the DEVQTY parameter exceeds the maximum allowable length.

  • The value of the DEVQTY parameter is invalid. Valid values are numeric or the character string ALL.

  • The value of the DEVQTY parameter is greater than the maximum quantity defined in the IOASPRM member in the IOA Archive Server Installation Parameters.

  • The value of the DEVQTY parameter is greater than the number of active devices allocated to the IOA Archive Server.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Issue a DISPLAY command to get information about each media and its resources that are allocated the IOA Archive Server. Reissue the MODIFY command with a valid DEVQTY parameter.

IOA14BE mediaName - LOCATE ERROR FOR dsn RC=rcLink copied to clipboard

Explanation: A CDAM data set cannot be found in the catalog.

The user requested a report which resides on a CDAM file which is uncataloged or does not exist.

The request is ignored.

Corrective Action: Catalog the file or take other corrective action and try again.

IOA14CI mediaName - MEDIA SHUTTING DOWNLink copied to clipboard

Explanation: This information message indicates that media mediaName is shutting down.

Corrective Action: No action is required.

IOA14DS mediaName - DEVICE deviceId ABENDEDLink copied to clipboard

Explanation: A media internal subtask abended.

Media mediaName issues an implicit start command for device deviceId. Attempts are made to initialize this device and continue normal processing. If these attempts fail, media mediaName sets the status of the designated device to NEVER ACTIVE and this device becomes unavailable for use by the IOA Archive Server.

Corrective Action: Check the IOA Log file and system log for additional messages which indicate why device deviceId abended.

IOA14ES mediaName - PARAMETER DEVADDR NUMBER nnnn DEFINED IN IOASPRM INSTALLATION PARAMETERS IS INVALIDLink copied to clipboard

Explanation: The DEVADDR parameter contains an invalid value.

The format of the device number specified in the DEVADDR parameter in the IOASPRM member (IOA Archive Server Installation Parameters) must be four digits.

Initialization of media mediaName fails. The IOA Archive Server shuts down with a return code of 08.

Corrective Action: Set the DEVADDR parameter to a valid numeric value and restart the IOA Archive Server.

IOA14FI mediaName - ALL DEVICES WERE DEFINED AS INACTIVE IN IOASPRM INSTALLATION PARAMETERSLink copied to clipboard

Explanation: This information message indicates that mediaName is inactive because all devices which belong to it are defined as inactive in the IOASPRM member (IOA Archive Server Installation Parameters).

Corrective Action: If necessary, issue operator MODIFY commands to start the media and the devices.

IOA150E mediaName - DYNAMIC ALLOCATION ERROR FOR DDNAME=SORTIN RC=rc, REASON CODE=rsnLink copied to clipboard

Explanation: An error occurred while trying to allocate an OSS Extract Database file.

This error causes the dynamic allocation of the SORTIN DD statement to fail.

For information on the return code (rc), see the IBM manual MVS Programming: Authorized Assembler Services Guide.

Media mediaName is terminated.

Corrective Action: Use the return code (rc) and reason code (rsn) to determine the problem and correct it. If you cannot resolve the problem, record the DD statement, return code, and reason code, and contact BMC Customer Support.

IOA151S sort_prog - SORT OF OSS EXTRACT DATABASE FILE FAILED, RC=rcLink copied to clipboard

Explanation: The internal sort of the OSS Extract Database file failed.

In this message, sort_prog activates the regular sort program at the site.

The system log usually contains additional messages about specific errors.

sort_prog is terminated.

Corrective Action: Check the system log for messages describing the error. Contact the system programmer for assistance, if needed. If the problem is not resolved, contact BMC Customer Support.

IOA170I mediaName - DEVICE deviceId - IS STARTINGLink copied to clipboard

Explanation: This information message indicates that IOA Archive Server deviceId device allocated to the mediaName media started.

Corrective Action: No action is required.

IOA171I mediaName - DEVICE deviceId - SHUT DOWN UPON REQUEST OF MAIN TASKLink copied to clipboard

Explanation: This information message indicates that the main task requested shutting down the IOA Archive Server deviceId device allocated to the mediaName media.

Corrective Action: No action is required.

IOA17AI mediaName - DEVICE deviceId - UNABLE TO ALLOCATE DEDICATED DEVICELink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server could not allocate device deviceId even though it is dedicated to the Server explicitly by means of the DEVADDR parameter or implicitly by a quantity of a unit name in the DEVQTY parameter.

If dedicated explicitly, the device possibly is disconnected.

If dedicated implicitly, probably no device in the device group specified in the IOASPRM member for mediaName media is available.

See messages DVT190E or IOA190E and DVT192E or IOA192E in the IOA Log file for the error code and info code.

The Server tries to allocate the device at 3-minute intervals until stopped by a MODIFY command.

Corrective Action: Use the error code and information code to determine why the allocation failed. For a description of the return code, see the IBM manual MVS Programming: Authorized Assembler Services Guide. Ask the operator to correct the problem and restart the device.

IOA17BI mediaName - DEVICE deviceId - UNABLE TO ALLOCATE DEVICE DYNAMICALLYLink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server could not allocate the deviceId device which should be allocated dynamically. Probably none of the devices in the device group specified in the IOASPRM member for the mediaName media is available.

For the error code and information code, see the DVT190E or IOA190E and DVT192E or IOA192E messages in the IOA Log file. For a description of the return code, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The Archive Server tries to allocate the device five times, at 2-minute intervals. If it does not succeed, device deviceId is terminated.

Corrective Action: Use the error code and information code to determine why the allocation failed. Ask the operator to correct the problem and restart the device.

IOA17CI mediaName - DEVICE deviceId - SHUT DOWN BECAUSE OF INTERNAL ERRORLink copied to clipboard

Explanation:Highlighted, unrollable message.

This message indicates that an internal error occurred while accessing device deviceId.

The cache request that generated the error is ignored. The activity that used this device is restarted.

Corrective Action: Notify your INCONTROL administrator.

IOA17DI mediaName - DEVICE deviceId - SHUT DOWN BECAUSE OF ABEND SnnnLink copied to clipboard

Explanation: Highlighted, unrollable message.

This message indicates that an abend occurred while accessing the deviceId device.

The cache request which caused the abend is ignored. The activity which used this device will be restarted.

Corrective Action: Notify your INCONTROL administrator.

IOA180S mediaName - DEVICE deviceId - UNABLE TO ACQUIRE STORAGE FOR blockId, RC IS rcLink copied to clipboard

Explanation: IOA Archive Server device deviceId is unable to acquire storage space for a BLKLST, FDB, CMP, CACHE or RDBUF block. See accompanying message DVT178I or IOA178I for the name of the requested file.

Execution of the task on device deviceId is terminated.

Corrective Action: Restart the IOA Archive Server. Re-IPL if necessary. Notify your INCONTROL administrator.

IOA181S mediaName - DEVICE deviceId - UNABLE TO xxQ ON vol / platter / device, RC IS rcLink copied to clipboard

Explanation: The IOA Archive Server for device deviceId was unable to ENQ or DEQ on a key volume, platter, or device.

Execution of the task on device deviceId is terminated.

Corrective Action: Restart the IOA Archive Server. Re-IPL if necessary. Notify your INCONTROL administrator.

IOA190E mediaName - DEVICE deviceId - UNABLE TO ALLOCATE UNIT unitLink copied to clipboard

Explanation: A file could not be dynamically allocated on mediaName media by the deviceId IOA Archive Server device.

For the error code and info code, see message DVT192E or IOA192E. For information on these codes, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The request is ignored.

Corrective Action: Use the error code and info code to determine why the allocation failed. Correct the problem. Restart the IOA Archive Server.

IOA191E mediaName - DEVICE deviceId - UNABLE TO DEALLOCATELink copied to clipboard

Explanation: The specified file could not be deallocated on the specified media when switching to another file in the IOA Archive Server device task.

For the error code and info code, see message DVT192E or IOA192E.

The next request and all future requests are ignored until deallocation succeeds.

Corrective Action: Use the error code and info code to determine why deallocation failed. Correct the problem. Restart the IOA Archive Server.

IOA192E mediaName - DEVICE deviceId - ERR + INFO CODE IS err+info_codeLink copied to clipboard

Explanation: This message accompanies messages IOA190E or DVT190E and IOA191E or DVT191E. It provides the error code and info code for a failed dynamic allocation or deallocation.

Corrective Action: Use the error code and info code to determine the problem and correct it.

IOA193E mediaName - DEVICE deviceId - I/O ERROR errorLink copied to clipboard

Explanation: The I/O error identified in this message occurred.

The request that caused the I/O error is ignored.

Corrective Action: Correct the problem in the file. Retry.

IOA194E mediaName - DEVICE deviceId - UNABLE TO OPEN FILE dsnLink copied to clipboard

Explanation: The deviceId IOA Archive Server device could not open the dsn file.

The request is ignored.

Corrective Action: Verify that the dsn file exists and can be accessed.

IOA195I mediaName - DEVICE deviceId - PLEASE MOUNT REQUIRED VOLUME, OR ANSWER NOLink copied to clipboard

Explanation: This information message indicates that a request was issued to mount a tape volume on the deviceId device, and that the requested tape volume was not mounted. The previous tape mount message was issued after an attempt to open a file on a tape volume that was not mounted on the device.

If this WTOR is answered NO, the mount request is canceled and the user request is ignored.

Corrective Action: If the requested volume cannot be mounted, or to cancel the mount request for any reason, reply NO to this WTOR. Otherwise, mount the requested volume.

IOA1A0I mediaName - NUMBER OF DEVICES = num1 NUMBER OF ACTIVE DEVICES = num2Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command to indicate the following:

  • num1 devices are assigned to mediaName media.

  • num2 active devices are assigned to mediaName media.

This message is preceded by message IOA1A1I or DSP1A1I, which supplies the IOA Archive Server name and media name for which the DISPLAY message was issued.

Corrective Action: No action is required.

IOA1A1I srvr - MEDIA mediaName STATUS DISPLAY:Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. This message is the header for messages that provide information about the status of mediaName media.

Corrective Action: No action is required.

IOA1A2I mediaName - MEDIA TYPE = media_type SYSTEM UNIT NAME = nameLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. This message identifies the media type and system unit name defined in the IOASPRM member in the IOA Archive Server Installation Parameters.

Corrective Action: No action is required.

IOA1A3I mediaName - STATUS = statusLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command to provide information about the current status of media mediaName.

Corrective Action: No action is required.

IOA1A4I mediaName - NUMBER OF PENDING REQUESTS = numLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command to provide information about the number of pending requests for mediaName media.

Corrective Action: No action is required.

IOA1A5I mediaName - DEVICE STATUS PLATTER VOLSER DSNLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. It is the header for IOA1A6I or DSP1A6I messages, which provide information about the status of each device assigned to media mediaName.

Corrective Action: No action is required.

IOA1A6I mediaName - device status platter volser dsnLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. Each message describes a device assigned to mediaName media.

This message follows message IOA1A5I or DSP1A5I, which provides the header for each field.

The variables in this message are:

  • device - the name of the assigned device

  • status - Active, Inactive or Idle

  • platter - <<FIX>>

  • volser - the serial number of the volume on which the data set is found

  • dsn - the data set name

Corrective Action: No action is required.

IOA1A7I mediaName - DEVICE USE STATUS VOLSER DSNLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. It is the header for IOA1A8I or DSP1A8I messages, which provide information about the status of each device assigned to mediaName media.

Corrective Action: No action is required.

IOA1A8I mediaName - device use status userId volser dsnLink copied to clipboard

Explanation: This information message is sent by the IOA Archive server to the console in response to a DISPLAY command. It follows message IOA1A7I, which provides the header for each field. Each occurrence of this message describes a device assigned to mediaName media.

The variables in this message are:

  • device - the name of the assigned device

  • use - Dedicated or Dynamic

  • status - Active, Inactive or Idle

  • userId - the user ID of the owner of the data set being retrieved by the device

  • volser - the serial number of the volume on which the data set is found

  • dsn - the data set name

The userId, vol, and dsn fields contain values only when the device is active.

Corrective Action: No action is required.

IOA1A9I mediaName - DEVICE STATUS USER-ID DSNLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. This message is the header for message IOA1AAI, which provides information about the status of each device assigned to the media identified in the message.

Corrective Action: No action is required.

IOA1AAI mediaName - deviceStatus userId dsnLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command.

Each message provides information about a device assigned to the mediaName media. A message is issued for each device defined in the MAXCONN parameter in IOASPRM. These messages are preceded by message IOA1A9I, which provides the header for each field.

Possible values of deviceStatus are:

deviceStatus

Meaning

INACTIVE

The device is not yet activated.

ACTIVE

The device is retrieving data requested by the userId user from the dsn data set.

IDLE

The device is ACTIVE, but currently not working on any request.

Corrective Action: No action is required.

IOA1AEI mediaName - TVL: OWNER-ID deviceStatus, NUM OF REQUESTS - num DSN dsnLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command to provide information about the current status of media mediaName.

Corrective Action: No action is required.

Messages IOA200 through IOA2xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA200I Function function_name is Starting Level level_id APAR:apar_idLink copied to clipboard

Explanation: This information message is issued when the Control-M JCL Verify monitor starts executing REFRESH, REMOVE, or REMOVEF processing. For more information see Chapter 13, "Improving performance," in the Contrl-M/JCL Verify User Guide.

Corrective Action: No action is required.

IOA282I text (userId)Link copied to clipboard

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT facility. The user ID is for the job order requesting the SHOUT.

Corrective Action: No action is required.

Messages IOA400 through IOA4xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA409E A KEYSTROKE REPORT ENDED WITH ERROR(S)Link copied to clipboard

Explanation: Syntax/execution error during processing of a report.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Look for the error in the report listing (the DAKSLOUT DD statement).

IOA41AW MAXCOMMAND 0 OR UNLIMIT SPECIFIED. LOOP DETECTION INACTIVATEDLink copied to clipboard

Explanation: This message is issued by KSL when it executes one of the following commands:

  • MAXCOMMAND 0

  • COMMAND UNLIMIT

These commands specify that KSL should not limit the number of commands executed by a script. By default, the maximum number of commands that can be executed by a KSL script is 400, in order to intercept runaway scripts. This number can be increased by using the MAXCOMMAND limit command.

If a KSL script expects to execute an unlimited number of commands because it runs in an endless loop until requested to stop, then the MAXCOMMAND 0 or UNLIMIT command can be specified in the script.

The script is not limited (loop detection is inactivated).

Corrective Action: Verify that the loop detection has been intentionally inactivated.

IOA482S OPEN OF USER DATE CONTROL-RECORD FAILED. DDNAME "DACHK"Link copied to clipboard

Explanation: Opening of the file containing the User Dates Control record failed (the DACHK DD statement). This message is issued by the New Day procedure.

This is due to one of the following:

  • The DACHK DD statement is missing.

  • The data set (member) described by the DACHK DD statement does not exist.

The New Day procedure stops executing.

Corrective Action: Correct the JCL for the job/CLIST.

IOA484I POST DAILY CHECKPOINT WRITTENLink copied to clipboard

Explanation: This information message indicates that Post-daily checkpoint was written.

Corrective Action: Indicates that the New Day procedure ended normally.

Messages IOA500 through IOA5xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA555S OID=orderId INSUFFICIENT STORAGE. INCREASE THE REGION SIZELink copied to clipboard

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

IOA5A0W mediaName - DEVICE num - CONNECT ERROR. STORAGE MACHINE: st.maName, SUBSYSTEM: smName, RC: rcLink copied to clipboard

Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to connect to the Filetek storage machine because the CONNECT function failed.

The probable cause for this failure is that the maximum number of connections to the storage machine was reached.

The variables in this message are:

  • mediaName - Name of the Filetek storage machine media as defined in IOASPRM.

  • num - Number of the IOASMON device in which the error occurred.

  • st.maName - Name of the Filetek storage machine. When it does not appear in the message, the name used is that of the storage machine as defined in the storage machine configuration member.

  • smName - SM subsystem name.

  • rc - Return code from the CONNECT function.

If an IOASMON monitor fails, the monitor continually retries to connect until it succeeds, or until the device task is brought down. If a migration job or CTVCLMIG failed, it terminates with errors.

Corrective Action: Check the return code of the CONNECT function against the Filetek documentation, and correct the problem accordingly. This might require reducing the number of active device tasks to reduce the number of connections to the storage machine. If a migration job or CTVCLMIG failed, rerun the job or utility.

IOA5A1E mediaName - DEVICE num - ERROR ALLOCATING FILE fileName, RC: rcLink copied to clipboard

Explanation: The migration job failed to allocate a file in the Filetek storage machine because the CREATOPEN function failed.

The variables in this message are:

  • mediaName - Name of Filetek storage machine media defined in IOASPRM.

  • num - Presently not in use.

  • fileName - Name of the file that the migration job failed to allocate.

  • rc - Return code from the CREATOPEN function.

The migration job skips the bad file, and processes the next file.

Corrective Action: Check the return code of the CREATEOPEN function against the Filetek documentation, and correct the problem accordingly.

IOA5A2E mediaName - DEVICE num - ERROR IN CLOSE. FILE fileName, RC: rcLink copied to clipboard

Explanation: The migration job failed to close a file in the Filetek storage machine because the CLOSE function failed.

The variables in this message are:

  • mediaName - Name of Filetek storage machine media defined in IOASPRM.

  • num - Presently not in use.

  • fileName - Name of the file that the migration job fails to close.

  • rc - Return code from the CLOSE function.

The migration job skips the bad file, and processes the next file.

Corrective Action: Check the return code of the CLOSE function against the Filetek documentation, and correct the problem accordingly.

IOA5A3I mediaName - DEVICE num - EMSG msgText, RC: rcLink copied to clipboard

Explanation: This information message is issued when a message is received from the Filetek storage machine subsystem.

The variables in this message are:

  • mediaName - Name of Filetek storage machine media defined in IOASPRM.

  • num - Presently not in use.

  • msgText - Message received from the storage machine.

  • rc - Return code from the function.

Corrective Action: No action is required.

IOA5A4E mediaName - DEVICE num - EMSG FAILED. RC: rcLink copied to clipboard

Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to receive a message from the Filetek storage machine because the EMSG function failed.

The variables in this message are:

  • mediaName - Name of Filetek storage machine media defined in IOASPRM.

  • num - Number of the IOASMON device in which the error occurred.

  • rc - Return code from the EMSG function.

The IOASMON monitor, migration job, or the CTVCLMIG utility continues processing.

Corrective Action: Check the return code of the EMSG function against the Filetek documentation, and correct the problem accordingly.

IOA5A5E mediaName - DEVICE num - ERROR IN DISCONNECT TO STORAGE MACHINE: st.ma.-name,SUB SYSTEM smName, RC: rcLink copied to clipboard

Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to disconnect from the Filetek storage machine because the DISCONNECT function failed.

The variables in this message are:

  • mediaName - Name of the Filetek storage machine media as defined in IOASPRM.

  • num - Number of the IOASMON device in which the error occurred.

  • st.ma.- name - The Filetek storage machine name. When it is omitted, the name of the storage machine defined in the storage machine configuration member is used.

  • smName - SM subsystem name.

  • rc - Return code from the DISCONNECT function.

The connection remains active. In the case of a migration job, or the CTVCLMIG utility failure to disconnect, the job or utility terminate with errors.

Corrective Action: Check the return code of the DISCONNECT function against the Filetek documentation, and correct the problem accordingly. In the case of failure of a migration job or the CTVCLMIG utility, rerun the job or utility correspondingly.

IOA5AIE MEDIANM mediaName - DEVICE device_num - ERROR READING FILE fileName, RC: rcLink copied to clipboard

Explanation: The migration job failed to read from a FileTek storage machine because the READ-RECORD function failed.

The variables in this message are:

  • mediaName - FileTek storage machine media defined in the IOASPRM member.

  • device_num - Number of the IOASMON device in which the error occurred.

  • fileName - Name of the file for which the error occurred.

  • rc - Return code from the READ-RECORD function.

The migration job skips the bad file, and processes the next file.

Corrective Action: Check the return code from the READ-RECORD function in the FileTek documentation. Correct the problem accordingly.

IOA5D0E mediaName - DEVICE deviceName - ERROR IN ACCESS TO OAM. RC = rc REASON CODE = rsnLink copied to clipboard

Explanation: IBM macro OSREQ was unable to carry out ACCESS for the specified OAM.

The variables in this message are:

  • mediaName - the OAM media name as defined in IOASPRM Blanks are indicated if issued by means of a migration process.

  • deviceName - The task ID that issued the message Blanks are indicated if the ID was issued by means of a migration process.

  • rc - the return code

  • rsn - the reason code

The system terminates any activity with OAM.

Corrective Action: Refer to IBM documentation. Consult either the OAM Programmer’s Reference or the DFSMSdfp Diagnosis Reference.

IOA5D1E mediaName - DEVICE deviceName - ERROR IN UNACCESS TO OAM. RC = rc REASON CODE = rsnLink copied to clipboard

Explanation: IBM macro OSREQ was unable to carry out UNACCESS for the specified OAM.

The variables in this message are:

  • mediaName - the OAM media name defined in IOASPRM. Blanks indicated that it was issued by a migration process.

  • deviceName - the ID of the task that issued the message Blanks indicate that the ID was issued by a migration process.

  • rc - the OSREQ return code

  • rsn - the OSREQ reason code

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D2W WARNINIG RECEIVED DURING READ OF 1ST BLOCK - collName RC=rc REASON CODE=rsnLink copied to clipboard

Explanation: IBM macro OSREQ requested a RETRIEVE of the first object in collection collName. OSREQ returned a warning.

The variables in this message are:

  • collName - Transformed name of the CDAM file being migrated.

  • rc - Return code issued by OAM.

  • rsn - Reason code issued by OAM.

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D3E ERROR DURING READ OF 1ST BLOCK - collName RC=rc REASON CODE=rsnLink copied to clipboard

Explanation: IBM macro OSREQ was unable to carry out a RETRIEVE of the 1st object in the collection collName.

The variables in this message are:

  • collName - Transformed name of the CDAM file being migrated.

  • rc - Return code issued by OAM.

  • reason - Reason code issued by OAM.

Migration stops.

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D4W WARNING IN QUERY - objName collName RC=rc REASON CODE=rsnLink copied to clipboard

Explanation: IBM macro OSREQ requested QUERY on object objName in collection collName and issued a warning.

The variables in this message are:

  • objName - the object requested by OSREQ (and in collection collName)

  • collName - the transformed name of the CDAM file being migrated

  • rc - the return code issued by OAM

  • rsn - the reason code issued by OAM

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D5E ERROR DURING QUERY - objNamecollName RC=rc REASON CODE=rsnLink copied to clipboard

Explanation: IBM macro OSREQ was unable to QUERY object objName in collection collName.

The variables in this message are:

  • objName - Object requested by OSREQ (and in collection collName).

  • collName - Transformed name of the CDAM file being migrated.

  • rc - Return code issued by OAM.

  • rsn - Reason code issued by OAM.

The system action depends on who issued the message, as follows:

  • If the migration job issues the message, LOCATE for collName fails, and collName does not migrate.

  • If IOASMON issues the message, collName is not retrieved for viewing or printing.

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D6E INCOMPLETE OAM FILE - oamfilLink copied to clipboard

Explanation: A migration job detected an incomplete OAM file. During most multistage migrations, OAM file oamfil migrates from OAM to another media. However, the migration job detected that oamfil was incomplete.

In this message, oamfil is the name of the incomplete OAM file.

The file does not migrate.

Corrective Action: Check oamfil in OAM, and attempt to determine the cause.

IOA5D7W WARNING IN DELETE - objName collName RC=rc REASON CODE= rsnLink copied to clipboard

Explanation: IBM macro OSREQ requested DELETE for object objName in collection collName, and produced a warning return code.

The variables in this message are:

  • objName - the object requested by OSREQ and in collection collName

  • collName - the transformed name of the CDAM file being migrated

  • rc - the return code issued by OAM

  • rsn - the reason code issued by OAM

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D8E ERROR IN DELETE - objName collName RC=rc REASON CODE= rsnLink copied to clipboard

Explanation: IBM macro OSREQ was unable to DELETE object objName in collection collName.

The variables in this message are:

  • objName - the object requested by OSREQ and in collection collName

  • collName - the transformed name of the CDAM file being migrated

  • rc - the return code issued by OAM

  • rsn - the reason code issued by OAM

The system terminates any activity associated with file collName. If this error occurs during migration, the collName is not migrated.

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D9E ERROR FROM DB2 SYNC . RC=rc REASON CODE=rsnLink copied to clipboard

Explanation: DB2 SYNC service generated an error during processing, after updating OAM data. If the update of OAM was successful, DB2 performs a DB2 SYNC after each action that updates the OAM data. ABORT is performed if the update fails.

The variables in this message are:

  • rc - the DB2 return code

  • rsn - the DB2 reason code

Current activity stops.

Corrective Action: Refer to DB2 documentation for an explanation of the return code and the reason code in the message. Determine the status of files in OAM after the migration. Verify that all updates were correctly performed in OAM.

IOA5DBW WARNING IN STORE - objName collName RC=rc REASON CODE=rsnLink copied to clipboard

Explanation: The message relays a warning message returned from IBM macro OSREQ. IBM macro OSREQ was called with a request to STORE object objName in collection collName.

The variables in this message are:

  • objName - the name of the object to be stored in collection collName

  • collName - the name of the collection where the object name resides

  • rc - the OSREQ return code

  • rsn - the OSREQ reason code

Corrective Action: See IBM documentation for an explanation of the return and reason codes in this message. Use OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DCE ERROR IN STORE - objName collName RC=rc REASON CODE=rsnLink copied to clipboard

Explanation: There was a request to STORE object objName in collection collName. However, IBM macro OSREQ returned an invalid return code.

The variables in this message are:

  • objName - the name of the specified object

  • collName - the name of the collection indicated as containing the specified object

  • rc - the OSREQ return code

  • rsn - the OSREQ reason code

Migration for file collName halts. In the next migration run, when the migration program discovers that the collection was not completed, all migrated objects are deleted, and the migration for this file is retried.

Corrective Action: Refer to IBM documentation for an explanation of the return and reason codes in this message. Use OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DDW WARNING IN RETRIEVE - objName collName RC = rc REASON CODE = rsnLink copied to clipboard

Explanation: The user requested that IBM macro OSREQ RETRIEVE object objName in collection collName. A warning code was returned by the macro.

The variables in this message are:

  • objName - the name of the specified object

  • collName - the name of collection indicated as containing the specified object

  • rc - the OSREQ return code

  • rsn - the OSREQ reason code

Corrective Action: Refer to IBM documentation for an explanation of the return code and the reason code specified in this message. Use OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DEE MEDIANM - DEVICE taskId - ERROR IN RETRIEVE - objName collName RC=rc REASON CODE = rsnLink copied to clipboard

Explanation: IBM macro OSREQ was unable to RETRIEVE object objName in collection collName.

The variables in this message are:

  • mediaName - the OAM media name defined in IOASPRM Blank if issued from a migration process.

  • taskId - the ID of the task that issued the message Blank if issued from a migration process.

  • objName - the name of the specified object

  • collName - the name of collection specified as containing objName

  • rc - the OSREQ return code

  • rsn - the OSREQ reason code

The system action depends on who issued the message, as follows:

  • If this message is issued by IOASMON, the read from the OAM migrated file fails, and this message is displayed on the user screen.

  • If this message is issued by a Multistage migration job, the migration of file collName stops, and a migration failure message is issued.

Corrective Action: Record the return code and reason code and refer to IBM documentation. Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DFI MEDIANM DEVICE deviceName - DB2 MSG RECEIVED - db2msgLink copied to clipboard

Explanation: This information message relays a message returned from DB2 while processing IBM macro OSREQ.

The variables in this message are:

  • deviceName - the ID of the media device

  • db2msg - the message returned from DB2 by means of OSREQ

Corrective Action: Refer to IBM documentation for an explanation of DB2 messages.

IOA5DGS OAM IS NOT ACTIVE IN SYSTEMLink copied to clipboard

Explanation: IBM OAM software was not active. Control-V attempted to initiate a connection to OAM.

The system terminates the action attempted by Control-V.

Corrective Action: Activate OAM.

IOA5DJE DB2 TABLES CORRUPTED - COLLECTION MATCHED AN OLD OBJECT objName collNameLink copied to clipboard

Explanation: An IBM OAM utility attempted to store an object over a different object with the same name. During migration to OAM, an OAM utility detected an object with the same name but different content. OAM DB2 tables may have been deleted by the user, and objects in the deleted tables may be connected to new collections. Message MIG5CUE immediately follows this message.

The variables in this message are:

  • objName - the object name that caused the error

  • collName - the name of the collection where the original objName resides

The system stops migration for objNamecollName. DB2 undoes migration actions performed for this collection. A LOCATE Failed Error message is issued for the OAM migrated file.

Corrective Action: Consult your DB2 administrator. Check and fix the DB2 tables.

IOA5E3I CLIP_ID=clipIdLink copied to clipboard

Explanation: This information message is issued for each Centera clip created during Control-V migration to the EMC Centera storage system.

The variable in this message is:

  • clipId - the name of the clip

Corrective Action: No action is required.

IOA5E4E CENTERA INIT ERROR: RC=rc, REASON CODE=rsnLink copied to clipboard

Explanation: Connection to EMC Centera cannot be established. This message is followed by message IOA5E9I, which issues the Centera pool value used for connection.

The variables in this message are:

  • rc - return code from the EMC Centera API.

  • rsn - reason code from the EMC Centera API.

IOA Archive Server skips the reading of data from Centera and continues processing with reading data from other media.

Corrective Action: Refer to EMC Centera documentation for a description of the received reason code.

Check the pool value printed in the accompanying MIG5E9I message. If the IP addresses are not correct, update them in parameters POOL1-POOL4 in the IOASPRM member.

Restart the IOA Archive Server after the reason for the problem is eliminated.

IOA5E6E CENTERA READ ERROR: RC=rc,REASON CODE=rsn,DSN=dsn,BLN=blk,L=lenLink copied to clipboard

Explanation: An error was detected while reading a block from the EMC Centera clip. This message is followed by message IOA5E31, which issues the problematic Centera clip name.

The variables in this message are:

  • rc - return code from the EMC Centera API

  • rsn - reason code from the EMC Centera API

  • dsn - the name of the migrated dataset

  • blk - error block number

  • len - returned block length

The migrated dsn dataset is not read.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

IOA5E8E CENTERA TERMINATE ERROR- RC=rc, REASON CODE= rsnLink copied to clipboard

Explanation: An error was detected during termination of the EMC Centera device.

The variables in this message are:

  • rc - return code from the EMC Centera API

  • rsn - reason code from the EMC Centera API

The EMC Centera connection is not terminated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

IOA5E9I POOL=poolLink copied to clipboard

Explanation: This information message follows message IOA5E4E.

In this message, pool represents the pool value specified in parameters POOL1-POOL4 in the IOASPRM member.

Corrective Action: No action is required.

Messages IOA600 through IOA6xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA631S INVALID FORMAT OF INPUT PARAMETERSLink copied to clipboard

Explanation: While the IOA Online facility was being initialized, a severe syntax error was found in one of the keywords in one of the ALC members. ALC members contain keywords that reference data sets to be allocated during initialization. The line in which the erroneous keyword appears is displayed in the IOAD81I message that follows this message.

IOA Online facility terminates with errors.

Corrective Action: Correct the erroneous keyword displayed in message IOAD81I, and reactivate the IOA Online facility.

IOA684E DSN dsn IN USE (DISP=OLD)Link copied to clipboard

Explanation: The dsn data set is held exclusively by another user.

Possible causes are:

  • Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).

  • IOA Online facility - schedule, calendar or rule definition.

  • Control-O initialization.

  • CMEM initialization.

The system action depends on the cause, as follows:

  • AutoEdit facility - job submission stops.

  • IOA Online facility - reading or updating of the table, calendar or rule is not performed.

  • Control-O is not started.

  • CMEM is not started.

Corrective Action: Try again.

IOA686E DSN dsn NOT IN CATALOGLink copied to clipboard

Explanation: The requested data set name is not in the catalog.

Possible causes are:

  • Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).

  • IOA Online facility - schedule, calendar or rule definition.

  • New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.

The system action depends on the cause, as follows:

  • AutoEdit facility - job submission stops.

  • IOA Online facility - reading or updating of the table, calendar or rule is not performed.

  • New Day procedure ends with errors.

Corrective Action: The appropriate response depends on the cause, as follows:

  1. AutoEdit facility - correct the JCL for the job and rerun it.

  2. Online facility - correct the library name and retry.

  3. New Day procedure - correct the New Day procedure and retry.

Messages IOA700 through IOA7xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA704E MISSING/INVALID PARAMETER IN THE PARM FIELD. VALID PARAMETERS ARE: IOA, CTM, CTD, CTR, CTO, CTB, ECSLink copied to clipboard

Explanation: Only one subsystem parameter should be specified in the PARM field of the IOAINS program. The IOAINS installation program can install only one of the above products at a time. The product code should be specified in the PARM field of the IOAINS EXEC statement.

The IOAINS installation program terminates with a condition code of 08.

Corrective Action: Correct the PARM field and resubmit the job.

IOA705I {START | END} MODIFYING OF LINES FOR MEM=memName, LIB=libLink copied to clipboard

Explanation: This information message indicates that statements contained in the specified library or member will be (START) or were (END) modified depending on the operation. This message is issued at the start and after modification of each member by IOAINS.

Corrective Action: No action is required.

IOA706I LINE BEFORE CHANGE: stmtLink copied to clipboard

Explanation: This information message displays each statement before it is modified.

Corrective Action: No action is required.

IOA707I LINE AFTER CHANGE: stmtLink copied to clipboard

Explanation: This information message displays each statement after it is modified.

Corrective Action: No action is required.

IOA708E OPEN OF DDNAME ddName FAILEDLink copied to clipboard

Explanation: The specified DD name could not be opened. This message is issued when errors occur during an attempt to open the mandatory DD names of the IOAINS and IOAIN1 installation programs.

The IOAINS or IOAIN1 installation program terminates with a condition code of 08.

Corrective Action: Correct the error and resubmit the job.

IOA709E INVALID PARMS IN stmtLink copied to clipboard

Explanation: In the IOAINS program, this message is issued as a result of an unrecognized parameter in the DEFPARMx member, where x represents the IOA product. In the IOAIN1 program, this message is issued as a result of an unrecognized parameter in the member pointed to by the DAINS DD statement. In both cases, the statement content follows.

The DEFPARMx member or the DAINS DD statement contains installation variables to replace constants throughout the product libraries. However one of the variables was not recognized by IOAINS or IOAIN1.

The IOAINS or IOAIN1 installation program terminates with a condition code of 08.

Corrective Action: Check the statement content. Do not modify the text between the percent signs. If needed, restore the relevant library from the original tape to determine the original variable value.

IOA70AE ERROR ALLOCATING MEM=memName LIB= libLink copied to clipboard

Explanation: The specified library or member could not be allocated. The DALIBS DD name contains a list of libraries and members in which modification of the product Installation Parameters takes place. If the member is blank, the entire library can not be allocated.

The IOAINS installation program continues with the next library and member as specified under the DD name DALIBS.

Corrective Action: Determine the reason the library or member could not be allocated. Then resubmit IOAINS while DALIBS contains only the problematic library and member specifications.

IOA70BE MISSING PARAMETERS IN THE PARM FIELDLink copied to clipboard

Explanation: Incorrect or missing PARM value in the IOAIN1 installation program. The PARM field of the IOAIN1 installation program should contain the type of run (1, 2, 3, 4, 5, or 6), followed by the product suffix, and a series of variables to be modified by the program. However, this PARM value was missing or incorrect.

The IOAIN1 installation program terminates with a condition code of 08.

Corrective Action: Check the PARM field in the IOAIN1 installation program, correct the error, and resubmit the job.

IOA70CE INVALID "OS" PARAMETER. EXPECTED VALUES: MVS, MSPLink copied to clipboard

Explanation:Highlighted, unrollable message.

An invalid OS parameter was passed to the IOAIN1 installation program, with run type 4. When running the IOAIN1 installation program with run type 4, the OS parameter should be MVS or MSP.

The IOAIN1 installation program terminates with a condition code of 08.

Corrective Action: Check the PARM field in the IOAIN1 installation program, correct the error, and resubmit the job.

IOA70DE MODIFYING OF LINES ENDED, DD=ddNameLink copied to clipboard

Explanation: This information message indicates that the IOAIN1 installation program successfully completed modification of the lines in the member pointed to by the ddName DD statement. This message is issued for each DD statement of the format DAINS xxx.

Corrective Action: No action is required.

IOA70EE "parm" PARAMETER VALUE EXCEEDS 44 CHARACTERS. PROGRAM TERMINATEDLink copied to clipboard

Explanation: The value assigned to the parm parameter, which was coded in the DEFPARMx member and should be substituted by the IOAINS installation program, exceeded 44 characters. Since the maximum length for a parameter value is 44, the program cannot perform variable substitution.

The program stops executing with a return code of 08. No substitution is performed by this step of IOAINS.

Corrective Action: Correct the value of parm and rerun the job.

IOA712E INVALID PARAMETER IN SYSIN FILE RSN:05Link copied to clipboard

Explanation:The IOAFTR installation program is used for tailoring members during the copying process from one library to another.

This message is issued by IOAFTR if the SYSIN statement includes the same input and output libraries pointed to by the INDD and OUTDD statements and the same member name for input and output.

The IOAFTR installation program terminates with a reason code of 05.

Corrective Action: Check the settings or change the name of one of the members to: xxxxxxx1 and rerun the process.

IOA717E CALENDAR CONTAINS INVALID DATALink copied to clipboard

Explanation: The IOACLB utility displays this message if a calendar contains invalid data. For example, a regular calendar can have a value of Y/N/+/-/blank in the months. If another value is present, this error message will be displayed. Note that the previous message identifies the calendar that contains the error. The XML output file will not contain this calendar.

Corrective Action: Check the calendar, correct the values that are invalid, and rerun the IOACLB utility.

IOA71EI PROCESSING CALENDAR calendar nameLink copied to clipboard

Explanation: This message is produced for each calendar that is processed by the IOACLB utility.

Corrective Action: No action is required.

IOA720I UTILITY util STARTEDLink copied to clipboard

Explanation: This information message is issued by CTMAPI, and indicates that the utility identified in the message has started.

CTMAPI issues this message before calling the application that handles the appropriate action code.

Corrective Action: No action is required.

IOA721I UTILITY util ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message is issued by CTMAPI, and indicates that the utility identified in the message has ended with a return code of 0.

Corrective Action: No action is required.

IOA722I UTILITY util ENDED UNSUCCESSFULLY REASON rcLink copied to clipboard

Explanation: This information message indicates that the specified utility identified in the message has ended with a return code other than 0.

In this message, rc is the return code.

Corrective Action: Use the contents of any messages issued by the utility, together with the return code, to determine the cause of the problem and take appropriate corrective action.

IOA723I API ENDED UNSUCCESSFULLY REASON rcLink copied to clipboard

Explanation: This message is issued whenever CTMAPI fails to perform an action, for example, failing to load an application.

In this message, rc is the reason code, the meaning of which is identical to the reason codes issued by the CTMBAPI DSECT, which can be found in the CTMBAPI member in the IOA MAC library.

The reason codes are listed below:

rc

Description

200

SYNTAX ERROR

204

ERROR IN OPENING DAAPI file

208

DUPLICATE ERROR

212

UNRECOGNIZED COMMAND IN BAPI DSECT

216

CTMAPQ INTERNAL ERROR

220

IF statement NOT SATISFIED

224

AJF OPEN ERROR

228

GETMAIN ERROR

232

INVALID RBA

236

QNAME ERROR

240

QNAME ERROR

244

READ OF RECORD 0 FAILED

248

MIT WAS NOT FOUND

252

CTMUCK INITialization FAILED

256

RESOURCE FILE OPEN ERROR

262

RESOURCE NOT FOUND

266

NOT A Control-M FILE

270

DYNAMIC ALLOCATION FAILED

274

LOAD OF PROGRAM FAILED

278

NEW DAY IN PROCESS

282

TOO MANY TAGS DEFINED

286

BAPI DID NOT RETURN ALL LINES

290

NO VALUE SUPPLIED IN SET GLOBAL

294

GLOBAL ACTION FAILED

298

GLOBAL ACTION FAILED

302

GLOBAL ACTION FAILED

306

ILLEGAL JOBID FORMAT

310

JOB FORMAT CONVERSION ERROR

314

JOB NOT HELD

318

JOB NOT BUILT - CTMJOB ERROR

322

SAVED JOB SIZE INCORRECT

326

ERROR DURING JOB SAVE

330

Control-M MONITOR NOT ACTIVE

334

CTMUCK RETRY LIMIT REACHED

Corrective Action: No action is required.

IOA724E NO KEYWORD FOUNDLink copied to clipboard

Explanation: A valid action code was specified, but no other mandatory keywords were supplied. Therefore CTMAPI cannot perform the action that was requested.

For further information on mandatory keywords, see the CTMAPI appendix in the Control-M for z/OS User Guide.

The action is not performed.

Corrective Action: Correct the request by inserting the mandatory keywords.

IOA725E DUPLICATE KEYWORDLink copied to clipboard

Explanation: The same keyword was specified more than once.

The action that was requested is rejected.

Corrective Action: Correct the request by removing the duplicate keyword specifications, and resubmit the request.

IOA726E EXPECTED VALUE FOR TOKENLink copied to clipboard

Explanation: In an action request, a keyword was specified that requires a value, but no value was found.

For example, the keyword DSNAME was specified, but no data set name was specified.

The request is rejected.

Corrective Action: Correct the syntax of the command, and reissue the request.

IOA727E ILLEGAL VALUE LENGTHLink copied to clipboard

Explanation: A parameter was set to a value that exceeds the maximum valid length.

The request is rejected.

Corrective Action: Correct the command to ensure that the lengths of the values of all parameters are valid.

IOA728I inputTextLink copied to clipboard

Explanation: This information message serves as an echo line, showing the input to CTMAPI.

Corrective Action: No action is required.

IOA729E ILLEGAL COMMANDLink copied to clipboard

Explanation: A CTMAPI request was issued, but the action requested is not one defined by CTMAPI.

The request is rejected.

Corrective Action: Correct the command so as to ensure that only valid actions are requested.

IOA72AI action SUCCESSFULLink copied to clipboard

Explanation: This information message indicates that CTMAPI successfully performed a SEARCH or IF action.

Corrective Action: No action is required.

IOA72BI action NOT SUCCESSFULLink copied to clipboard

Explanation: This information message indicates that CTMAPI was unsuccessful in performing a SEARCH or IF action.

Corrective Action: No action is required.

IOA72CE SYNTAX ERRORLink copied to clipboard

Explanation: CTMAPI could not perform the action that was requested because of a syntax error in the request.

This message is usually accompanied by other messages that clarify the nature of the error.

The request is rejected.

Corrective Action: Examine the request and correct the error.

IOA72DE UNRECOVERABLE ERROR OCCURRED DURING SEARCHLink copied to clipboard

Explanation: An internal error occurred while CTMAPI was performing the SEARCH AJF command. Possible causes are such problems as failure to get memory, failure to find the AJF that was specified, and so on.

Usually this message is accompanied by other messages issued by CTMAPI or CTMAPQ.

The command is rejected.

Corrective Action: Examine any accompanying messages, and take appropriate corrective action.

IOA72JE AJF ACTION NOT PERFORMEDLink copied to clipboard

Explanation: An AJF action that was requested was not performed. Usually, this message is accompanied by other messages that explain the reason.

The AJF action is not performed.

Corrective Action: Examine the accompanying messages to ascertain the nature of the problem, and take appropriate corrective action.

IOA72KE NEWDAY IN PROCESSLink copied to clipboard

Explanation: An AJF action that was requested could not be performed, because the New Day procedure is holding the AJF. No action can be performed on the AJF until the New Day procedure releases it.

The AJF action is not performed.

Corrective Action: Wait for a time, until the New Day procedure ends, and reissue the request.

IOA72LE MISSING ON PGMST LINE DEFINITIONLink copied to clipboard

Explanation: This message is issued when a user edited a job definition in the Job Scheduling Definition screen (Screen 2), and

  • defined two ON PGMST statements connected by a Boolean connector (AND or OR)

  • failed to complete the details of the second ON PGMST statement

  • attempted to save the job

Corrective Action: Correct the problematic ON PGMST statement.

IOA72MI ACTION action ON JOB jobId ORDERID orderIdLink copied to clipboard

Explanation: This message describes the action taken by CTMAPI on a job in the Active Jobs file.

The variables in this message are:

  • action - the action that was taken

  • jobId - the identity of the relevant job

  • orderId - the order ID of the job

CTMAPI performs the action and issues this message. This message is followed by one of the following messages:

  • IOA72AI - issued when the return code resulting from the action signifies successful completion of the action

  • IOA72BI - issued when the return code resulting from the action signifies unsuccessful completion of the action

Corrective Action: Verify that the action identified in this message was performed on the correct job.

IOA72QE ACTION FAILED rsn: action ON JOB jobName ORDERID orderIdLink copied to clipboard

Explanation: The CTMAPI utility failed to perform the requested action on the jobName job, whose order ID is orderId. The reason for the failure is described by the following rsn codes:

rsn

Description

4

Invalid request (or parameters)

8

Request to delete non-held entry

Request to free non-held entry

Request to change non-held entry

12

Open of AJF (ddname DACHKPT) failed

16

ENQUE failed

20

MIT phase changed

24

No room on AJF for more changes

28

Request to act on deleted entry

32

Request to rerun an unfinished job

36

Request to free while still requested change

40

Request for AJF action while still in process

44

Request to delete while *p request active

48

Security violation

52

Rerun desicion was changed - rerun not performed

56

Restart decision was changed - restart not performed

60

Job not waiting for confirmation

64

Restart decision was deleted - restart not performed

68

Request to react an undisappeared job

72

FORCE OK not performed - job already running

76

FORCE OK not performed - job already rerun

80

FORCE OK not performed - job already ended "OK"

84

FORCE OK not performed - cyclic job

88

Exit did the work by itself

92

Load/init of CTMHCP failed

96

Setup failed by CTMHCP

100

Copy failed by CTMHCP

104

Commit failed by CTMHCP

108

Bypass not performed - job not WAIT SCHED

112

KILL not performed - job not executing

116

KILL not performed - job is STC

120

KILL not performed - job is NJE

Corrective Action: No action is required.

IOA72SW ERROR IN TIMEZONE: DUPLICATE TIME ZONE NAME . LINE IGNOREDLink copied to clipboard

Explanation: A duplicate time zone designation was detected in the TIMEZONE member of the CTM PARM library. The time zone in question is listed in message IOA72ZI, which follows message IOA72SW.

Corrective Action: Correct the TIMEZONE member.

The duplicate entry is ignored.Link copied to clipboard

IOA72TI SEARCH COMPLETE. NUMBER OF ENTRIES FOUND: n

Explanation: This information message indicates the number of entries found for a requested search.

Corrective Action: No action is required.

IOA72UI JOB jobName ORDERID orderId EXCLUDED FROM EM DOWNLOADLink copied to clipboard

Explanation: This information message indicates that the jobName job, whose order ID is orderId, is marked to be excluded from the next downloading of jobs from the AJF to Control-M/EM. This is a response to the CTMAPI command EMDOWNLD EXCLUDE LIST, which lists the jobs currently excluded from the download process.

Corrective Action: No action is required.

IOA72VI NO JOBS EXCLUDED FROM EM DOWNLOADLink copied to clipboard

Explanation: This information message appears in response to the CTMAPI command EMDOWNLD EXCLUDE LIST, which lists the jobs currently excluded from the download process. No jobs with such a status were found on the AJF.

Corrective Action: No action is required.

IOA72XI JOB jobName IS A GROUP ENTITY -- ALL JOBS IN GROUP WIL BE PROCESSEDLink copied to clipboard

Explanation: This information message indicates that a request to exclude the jobName job from downloading is being processed, and the job was found to be a group entity. As a result, all jobs in the group are marked as excluded from downloading.

Corrective Action: No action is required.

IOA72ZI textLink copied to clipboard

Explanation: This information message contains the timezone entry and description text.

Corrective Action: See message IOA72SW.

IOA734E ERROR DURING UPDATE REASON CODE=rsnLink copied to clipboard

Explanation: An error was encountered during an update of scheduling definitions or jobs by the CTMTBUPD Control-M utility.

Corrective Action: Use the information provided below for reason codes that you might be able to address. For any other reason code, contact BMC Support.

Reason Code

Description

0228

GETMAIN ERROR

Region size too small. See KA000369827.

0256

RESOURCE FILE OPEN ERROR

0262

RESOURCE NOT FOUND

0278

NEW DAY IN PROCESS

0282

TOO MANY TAGS DEFINED

0290

NO VALUE SUPPLIED IN SET GLOBAL

0294

GLOBAL ACTION FAILED

0298

GLOBAL ACTION FAILED

0302

GLOBAL ACTION FAILED

0314

JOB NOT HELD

0318

JOB NOT BUILT - CTMJOB ERROR

See also KA000316389.

0322

SAVED JOB SIZE INCORRECT

0326

ERROR DURING JOB SAVE

See also KA000230176.

0330

CONTROL-M MONITOR NOT ACTIVE

0338

CHANGING PROTECTED FIELD ERROR

0342

ERROR DURING CONFIRM UPDATE

0350

INDEX NOT FOUND

0358

INDEX NOT OVERRIDEN

0362

INDEX MEASURED BY CONTROL-M

0366

USER NOT AUTORIZED

0370

REMOTE FORCE JOB ERROR

IOA740E MEMBER MemName IS IN USE, PLEASE TRY LATERLink copied to clipboard

Explanation:The MemName member is not available and cannot be overwritten.

Corrective Action: Check/release the MemName member.

IOA741E PROBLEMS WITH BASE LIBRARY basepref.INSTALL errorLink copied to clipboard

Explanation: The install library specified in the message does not exist, or has an invalid DSNAME.

The variables in this message are:

  • basepref - the base prefix of the missing install library

  • error - a description of the error

A prompt is issued for the base prefix.

Corrective Action: Check if the library was installed, or if the prefix was misspelled, and correct accordingly.

IOA742E PROBABLY NOT A BASE LIBRARY IOAIC00A errorLink copied to clipboard

Explanation: The basepref.INSTALL parameter points to a data set that is not a base library. A base library must contain the IOAIC00A member.

A prompt is issued for a base prefix.

Corrective Action: Specify the correct base library prefix.

IOA743E ENVIRONMENT TABLE PROBLEMS[. APPLICATION TERMINATED]Link copied to clipboard

Explanation: The Environment table was not found in the specified install library.

The ICE application terminates.

Corrective Action: Reload the required install library from the installation tape.

IOA744E UNABLE TO ALLOCATE THE ENVIRONMENT lib LIBRARY DATASET NAME: dsnLink copied to clipboard

Explanation: The application failed to allocate the dsn dataset name in the environment’s lib library.

Corrective Action: Consult your system administrator to check for an MVS allocation problem.

IOA746I NO ENVIRONMENT EXISTS OR SELECTED [FOR CLONING]Link copied to clipboard

Explanation: This information message indicates that no environment exists or is selected. Either this is the first time ICE was activated, or no current environment exits. The system cannot proceed with any activity other than ENVIRONMENTS.

Corrective Action: In the ICE Main Menu, select Installation and then select the ENVIRONMENTS activity. If needed, define an environment; select a defined environment.

IOA747E UNKNOWN OR MISSING PRODUCT IDLink copied to clipboard

Explanation: An invalid product ID was specified. Product ID is a three letter abbreviation of an IOA product, for example, CTM for Control-M.

Corrective Action: Specify a valid product ID.

IOA748E ENFORCE STEP ORDER MUST BE YES OR NOLink copied to clipboard

Explanation: A value other than YES or NO was specified in the Enforce step order parameter.

Corrective Action: Specify YES or NO.

IOA749E THIS ACTIVITY CANNOT BE PERFORMED FOR THIS PRODUCT IDLink copied to clipboard

Explanation: The user specified a product and an activity that cannot be specified together. Certain activities are valid only when installing certain products. For example, activities INSTALL, COPY IOA, and MAINTENANCE are valid only for product ID IOA.

Corrective Action: Specify another activity (or change the product ID).

IOA74AE THIS ACTIVITY CANNOT BE SELECTED FOR productLink copied to clipboard

Explanation: The user selected an activity that is not valid when installing a product which is not product.

Corrective Action: Change the activity or the product ID.

IOA74BE THIS ACTIVITY IS NOT SUPPORTED FOR A CLONED ENVIRONMENTLink copied to clipboard

Explanation:The message is displayed when one of the following SMP/E processes is attempted on a cloned environment:

  • applying a maintenance upgrade (ICE Main Menu=>Maintain your Environment=>Maintenance)

  • applying ad hoc PTFs (ICE Main Menu=>Maintain your Environment=>APPLY PTFs)

These processes cannot be performed since cloned environments do not include the SMP/E installation utilities.

Corrective Action: Avoid selecting the above ICE options on cloned environments.

IOA74CE THIS ACTIVITY IS NOT VALID FOR AN ENVIRONMENT CREATED FROM TAPELink copied to clipboard

Explanation: The user requested activity COPY IOA for an environment created from the product tape. This is not permitted.

Corrective Action: If this message was issued in a Default or an IOA cloned installation, see the INCONTROL for z/OS Installation Guide, “Customizing INCONTROL Products.”

If this message was issued in a customized installation, select the ENVIRONMENTS activity and then select an environment whose CREATE FROM parameter is an environment ID.

IOA74DE PFMSMF: Value PFMSMF MUST BE ZERO OR BETWEEN 128 AND 255Link copied to clipboard

Explanation: This error message indicates that the value of the parameter PFMSMF is incorrect.

Corrective Action: Set the value of the parameter PFMSMF to 0 or a number between 128 and 255.

IOA750E THE ENVIRONMENT NAME MUST BEGIN WITH A LETTERLink copied to clipboard

Explanation: The first position of the environment name is not an alphabetic character.

A prompt is issued for the environment name parameter.

Corrective Action: Specify a value in the environment name parameter with an alphabetic character in the first position.

IOA751E PREFIX MUST BE DIFFERENT FROM THE BASE PREFIXLink copied to clipboard

Explanation: The same prefix is specified for the base and for the environment. The same prefix cannot be used for both the environment data sets and for the base data sets.

A prompt is issued for the environment prefix parameter.

Corrective Action: Specify an environment prefix different from the base prefix.

IOA752E NOT A VALID DSNAME SYNTAX OR EMPTYLink copied to clipboard

Explanation: A DSNAME that does not conform to DSNAME syntax rules is specified or the field was left blank. The DSNAME must conform to DSNAME syntax rules and cannot be empty.

A prompt is issued for the DSNAME.

Corrective Action: No action is required.

IOA753E EITHER DEFINE BOTH UNIT AND VOLSER OR LEAVE BOTH OF THEM BLANKLink copied to clipboard

Explanation: The unit or volume names are missing. Both the unit and volume names must be supplied.

A prompt requests the missing parameter.

Corrective Action: Specify the missing name.

IOA754E ENVIRONMENT ID CANNOT BE TAPE or EPDLink copied to clipboard

Explanation: The environment ID is specified as TAPE or EPD. The environment ID can be any string, up to eight characters, except the strings TAPE or EPD.

A prompt is issued for the environment ID parameter.

Corrective Action: Specify an environment ID other than TAPE or EPD.

IOA755E DUPLICATION IS NOT ALLOWEDLink copied to clipboard

Explanation: An attempt to define a new environment uses the name/installation prefix of a previously defined environment. The name of an environment/installation prefix must be unique.

A prompt is issued for the environment name/installation prefix parameter.

Corrective Action: Specify a name for the environment/installation prefix which does not match the name/installation prefix of another environment.

IOA756I ENVIRONMENT environmentID DELETEDLink copied to clipboard

Explanation: This information message indicates that the specified environment was deleted as required.

The entry in the environment table was deleted. The libraries were not deleted.

Corrective Action: No action is required.

IOA757E THE COPY FROM ENVIRONMENT environmentID DOES NOT EXISTLink copied to clipboard

Explanation: There was an attempt to create a new environment from an existing environment, but the environmentID source environment does not exist.

A prompt is issued for the environment ID parameter.

Corrective Action: Change the source environment ID to one that already exists.

IOA758E ONLY ONE ENVIRONMENT CAN BE INSTALLED FROM TAPELink copied to clipboard

Explanation: An attempt to install, in a single base, more than one environment from the product tape failed. Only one environment, per base library, can be installed from the same product tape.

Corrective Action: Select another environment from which to install the new environment.

IOA760E COULD NOT LOAD ISPLINK MODULELink copied to clipboard

Explanation: The installation application failed to load the ISPLINK module. ICE requires the use of the ISPF ISPLINK module, and therefore loads the module during installation.

Corrective Action: Consult your system administrator who should check the ISPF installation.

IOA761E MEMBER memName NOT FOUNDLink copied to clipboard

Explanation: The memName member does not exist.

A prompt is issued for the member parameter.

Corrective Action: Check that the member name and library are specified correctly.

IOA762E INVALID ACTIONLink copied to clipboard

Explanation: An invalid action code was specified. The valid action codes appear on each screen.

Corrective Action: Specify a valid action.

IOA763E CANNOT SELECT STEP. PRIOR STEP NOT COMPLETEDLink copied to clipboard

Explanation: A major or a minor step was selected, but previous steps were optional, excluded, or not completed. If ENFORCE STEP ORDER is specified as YES, the application checks the prior steps.

Corrective Action: Complete prior steps, or specify ENFORCE STEP ORDER=NO.

IOA764I BROWSE MODE - VIEW ONLYLink copied to clipboard

Explanation: This information message indicates that the current screen is in browse mode.

Corrective Action: No action is required.

IOA765E CANNOT MARK STEP AS COMPLETE. SOME MINOR STEPS ARE NOT COMPLETEDLink copied to clipboard

Explanation: An attempt to mark a major step as completed when at least one mandatory minor step was not completed failed. A major step can be marked as completed only when all mandatory minor steps have been completed.

Corrective Action: Complete the mandatory minor steps.

IOA766E CANNOT ALLOCATE HELP FILELink copied to clipboard

Explanation: The online help file cannot be allocated. The online help file is allocated when the help is requested, or EXTERNAL STEP is selected.

Corrective Action: Check that the IOAIMxxx member, where xxx is the Product ID, appears in the basepref.INSTALL library.

IOA767E KEYWORD keyName WAS NOT FOUND IN MEMBER memNameLink copied to clipboard

Explanation: The keyword keyName in Special Edit (Data * type step) does not appear in the specified member. The Special Edit process searches for the keyword in the target member and, if requested, in the reference member. If the keyword is not found in either one of these members, this messages is issued.

Corrective Action: If the identified member is the reference member, choose another member, or specify N to relinquish the use of a reference. If the specified member is the target member, copy it from the base library into the target member.

IOA768E TARGET AND DISTRIBUTION ZONE NAMES CANNOT BE GLOBALLink copied to clipboard

Explanation: An attempt to specify the name of a target or distribution zone as GLOBAL failed. In SMP/E, GLOBAL is reserved for the name of the global zone.

A prompt is issued for the target or distribution zone parameter.

Corrective Action: Specify another name for the zone in question.

IOA769E TARGET AND DISTRIBUTION ZONE NAMES MUST BE DIFFERENTLink copied to clipboard

Explanation: Identical names were specified for the target and distribution zones. Target and distribution zone names must be unique.

A prompt is issued for the target or distribution zone parameter.

Corrective Action: Change either the target or distribution zone name.

IOA76AE TARGET PREFIX MUST BE DIFFERENT FROM GLOBAL PREFIXLink copied to clipboard

Explanation: Identical prefixes were specified for the target and global prefixes. Target and global prefixes must be unique.

A prompt is issued for the target or prefix parameter.

Corrective Action: Change the target prefix.

IOA76BE DISTRIBUTION PREFIX MUST BE DIFFERENT FROM GLOBAL PREFIXLink copied to clipboard

Explanation: Identical prefixes were specified for the distribution and global prefixes. Distribution and global prefixes must be unique.

A prompt is issued for the distribution prefix parameter.

Corrective Action: Change the distribution prefix.

IOA76CE DISTRIBUTION AND TARGET PREFIXES MUST BE DIFFERENTLink copied to clipboard

Explanation: Identical prefixes were specified for the distribution and target prefixes. Distribution and target prefixes must be unique.

Corrective Action: Change either the distribution or target prefix.

IOA76DE The step can be marked as COMPLETE only after being selectedLink copied to clipboard

Explanation: This step can be marked as COMPLETE only after being selected at least once.

Corrective Action: Select this member, and then mark it as COMPLETE.

IOA76EE Step can not be marked as COMPLETE, the process did not finish okLink copied to clipboard

Explanation: The step can be marked as COMPLETE only after the process finishes OK.

Corrective Action: Make sure that the process finishes OK, and than mark it as COMPLETE.

IOA770E MISSING VALUES FOR : parmsLink copied to clipboard

Explanation: There was an attempt to mark the Data Type minor step as completed, but at least one of its mandatory parameter values was not specified. The names of the problematic parameters are listed in the message.

The step is not marked as completed.

Corrective Action: Select the step again and specify the missing values.

IOA771E varName MUST BE NUMERIC AND WHOLE NUMBER ONLYLink copied to clipboard

Explanation: A non-numeric or non-integer value was specified for the varName variable.

A prompt is issued for the variable.

Corrective Action: Specify a numeric value for the variable.

IOA772E ParmName MUST BE ALPHANUMERIC [AND FIRST CANNOT BE NUMERIC]Link copied to clipboard

Explanation: An invalid value was specified for the ParmName parameter.

The word "Parameters" is a valid value for the ParmName parameter.

Corrective Action: Specify a valid value for the parameter.

IOA773E varName MUST BE AT LEAST charNum CHARACTERS LONGLink copied to clipboard

Explanation: The input value for the variable identified in the message was too short.

A prompt is issued for the variable.

Corrective Action: Specify a character string for the variable that contains at least the minimum number of characters indicated in the message.

IOA774E varName MUST BE AT MOST charNum {CHARACTERS | DIGITS} LONGLink copied to clipboard

Explanation: The input value for the variable identified in the message was too long.

A prompt is issued for the variable.

Corrective Action: Specify a character string for the variable that does not exceed the maximum length indicated in the message.

IOA775E varName MUST BE val OR LESSLink copied to clipboard

Explanation: The input value for the variable identified in the message was too large.

A prompt is issued for the variable.

Corrective Action: Specify a number for the variable that is less than the value indicated in the message.

IOA776E varName MUST BE val OR GREATERLink copied to clipboard

Explanation: The input value for the variable identified in the message was too small.

A prompt is issued for the variable.

Corrective Action: Specify a number for the variable that exceeds the value indicated in the message.

IOA777E varName VALUE SHOULD BE BETWEEN val1 AND val2Link copied to clipboard

Explanation: The input value for the variable identified in the message was not in the indicated range.

A prompt is issued for the variable.

Corrective Action: Specify a number for the variable within the range specified in the message.

IOA778E varName VALUE IS ONE OF: val1 val2 ... val6Link copied to clipboard

Explanation: The input value for the variable identified in the message was not one of a number of valid values.

A prompt is issued for the variable.

Corrective Action: Specify for the variable one of the valid codes indicated in the message.

IOA779E varName IS MANDATORYLink copied to clipboard

Explanation: A mandatory variable has no value.

A prompt is issued for the variable.

Corrective Action: Specify a value for the variable.

IOA77AE varName HAS INVALID DSNAME SYNTAX OR EMPTYLink copied to clipboard

Explanation: The DSNAME for the variable does not conform to DSNAME syntax rules or is empty. The DSNAME must conform to DSNAME syntax rules.

A prompt is issued for the variable.

Corrective Action: Correct the DSNAME.

IOA77BE varName FAILED VALIDITY CHECKS. PLEASE CONSULT THE INSTALLATION MANUALLink copied to clipboard

Explanation: The value of the specified variable is invalid.

A prompt is issued for the variable.

Corrective Action: Refer to the INCONTROL for z/OS Installation Guide for the valid format and values of the variable.

IOA77CE SIGN OF varName MUST BE - OR +Link copied to clipboard

Explanation: There is no minus sign - or plus sign + before the identified field.

A prompt is issued for the variable.

Corrective Action: Insert a minus sign - or a plus sign + at the beginning of the field.

IOA77DE HOUR MUST BE BETWEEN 00 AND 23Link copied to clipboard

Explanation: An invalid value specifies the hour of the day. The hour value must be between 00 and 23.

A prompt is issued for the variable.

Corrective Action: Specify an hour value between 00 and 23.

IOA77EE MINUTE MUST BE BETWEEN 00 AND 59Link copied to clipboard

Explanation: An invalid value specifies the minute of the day. The minute value must be between 00 and 59.

A prompt is issued for the variable.

Corrective Action: Specify a minute value between 00 and 59.

IOA77FE varName MUST BE IN HEXADECIMAL DIGITSLink copied to clipboard

Explanation: A non-hexadecimal value was specified for the specified variable. The value must be either 0 to 9, or A to F.

A prompt is issued for the variable.

Corrective Action: Specify a hexadecimal value.

IOA780W DO NOT PROCEED. CANNOT INSTALL prod1 WHEN prod2 IS NOT INSTALLEDLink copied to clipboard

Explanation: An attempt to install product prod1 before concluding the installation of the prerequisite product prod2 failed.

Some products can be installed only after other products have been installed. For example, IOA must be installed before all other IOA products.

Corrective Action: Complete all the installation steps of the prerequisite product.

IOA781E varName1: val1 MUST BE DIFFERENT FROM varName2 [in xxxPARM]Link copied to clipboard

Explanation: The values for variable 1 and variable 2 in xxxPARM are identical. If in xxxPARM is missing variable 1 and variable 2 are in the same member.

Corrective Action: Choose another value for one of the variables.

IOA782W CTM:val1 CTD:val2 CTD OR CTM MUST BE "Y"Link copied to clipboard

Explanation: The values of the CTM or CTD parameter were not specified as Y.

Corrective Action: Specify CTM or CTD as Y.

IOA783E var: MAX. TWO QUALIFIERS ALLOWEDLink copied to clipboard

Explanation: The var variable can contain only two qualifiers (only one dot is allowed).

Corrective Action: Correct the var variable to contain only two qualifiers (with only one dot).

IOA784E SMF:valSMF = NO, OR SMF BETWEEN 128 AND 255Link copied to clipboard

Explanation: An invalid value is specified for SMF. Valid values for SMF are either NO, or a numeric value in the range 128-255.

Corrective Action: Change the value of the SMF parameter to NO, or a number between 128 and 255.

IOA785W DUALVOL:volser
DUAL FILE SHOULD BE PLACED ON A DIFFERENT DISK THAN THE REST OF IOA CORELink copied to clipboard

Explanation: When installing IOA, installation of a dual database was requested by specifying Y in the DUALDB parameter. For improved performance and recovery capability, place the dual file on a different disk and (preferably) on a different disk controller than the rest of the IOA Core:

  • DBVOLA — the volume serial number for IOA Core

  • DUALVOL— the volume on which the dual database is to be allocated

Corrective Action: Specify different volumes for the IOA Core and dual files.

IOA786E DUALUNIT:NONE
IF DUALDB IS "Y" THEN DUALUNIT CANNOT BE NONE
DUALVOL: NONE
IF DUALDB IS "Y" THEN DUALVOL CANNOT BE NONELink copied to clipboard

Explanation: When installing IOA, installation of a dual database was requested by specifying Y in the DUALDB parameter. However, one or both of the following parameters were specified NONE (rather than a valid value):

  • DUALUNIT— the unit on which the dual database is to be allocated

  • DUALVOL— the volume on which the dual database is to be allocated

Corrective Action: Either change the DUALDB field to N or make sure that both a valid unit number is specified for DUALUNIT and a valid volume is specified for DUALVOL.

IOA787E MAXDAYS MAXRUNS CANNOT BE BOTH NULLSLink copied to clipboard

Explanation: No value is specified for either MAXDAYS or MAXRUNS. A value must be specified for at least one of these parameters.

Corrective Action: Specify a value in the MAXDAYS parameter, or the MAXRUNS parameter, or both.

IOA788E COMM: {SNA | TCP}{APPLID= | PORT=} MUST BE SUPPLIED IF COMM = {SNA | TCP}Link copied to clipboard

Explanation: No value is specified for the APPLID parameter when COMM is set to SNA, or there is no value specified for the PORT parameter when COMM is set to TCP.

Corrective Action: Specify a valid value in the APPLID or PORT accordingly.

IOA789E PROCPRFA: procprfa_val, PROCLIB: DONTCOPY SITEPROC: DONTCOPY. WHEN BOTH PROCLIB AND SITEPROC ARE DONTCOPY THEN PROCPRFA MUST BE IOALink copied to clipboard

Explanation:This is one of two messages with the same ID, but different text.

DONTCOPY is specified in the PROCLIB and SITEPROC parameters but an invalid value is specified in the PROCPRFA parameter.

Corrective Action: Change the value of the PROCPRFA parameter to IOA as indicated in the message.

IOA789E CLISTNMJ: clistnmj_val, SYSPROCA: DONTCOPY. WHEN SYSPROCA IS DONTCOPY THEN CLISTNMJ MUST BE CTJXVERLink copied to clipboard

Explanation:This is one of two messages with the same ID, but different text.

DONTCOPY is specified in the SYSPROCA parameter, but an invalid value is specified in the CLISTNMJ parameter.

Corrective Action: Change the value of the CLISTNMJ parameter to CTJXVER as indicated in the message.

IOA78AE varName: val DATASET NOT FOUNDLink copied to clipboard

Explanation: The value of the ISPF libraries prefix of the O.S. and/or the value of the ISPF language suffix (as set by the ISPFPREF and ISPFLANG variables, respectively) are invalid. An ISPF library with the supplied prefix and language suffix does not exist in the system.

Note that the language value must be one of the following: ENU, DES, DEU, JPN, or ENP

Corrective Action: Check and correct the ISPFPREF and ISPFLANG parameters according your system ISPF libraries.

IOA78AW varName: val DATASET NOT FOUNDLink copied to clipboard

Explanation: The supplied non-IOA data set name does not exist or is not cataloged. A data set name was specified to which an IOA data set is to be copied.

Corrective Action: Check that the specified data set name is correct.

IOA78BE IF IOAID 1 THEN SHRQNM MUST BE DIFFERENT FROM QNAME AND NOT NULLLink copied to clipboard

Explanation: The SHRQNM field is blank or has the same value as the QNAME field, when the value of the IOAID field is greater than one. When the IOAID is greater than one, a unique name must be specified for the shared queue.

Corrective Action: Specify a unique name in the SHRQNM field.

IOA78CE CTO DAYTIME: val1 CTM DAYTIME: val2. CTO DAYTIME MUST BE EQUAL TO CTM DAYTIMELink copied to clipboard

Explanation: A DAYTIME value is specified for Control-O that is different from the DAYTIME value of Control-M, which was installed earlier.

Corrective Action: Change Control-O DAYTIME to match that of Control-M.

IOA78DE HSTSIZE: val1 AJFSIZE: val2. HSTSIZE CANNOT BE LESS THAN AJFSIZELink copied to clipboard

Explanation: The HSTSIZE value cannot be less than the AJFSIZE value.

Corrective Action: Change the Control-M HSTSIZE parameter or the AJFSIZE parameter values.

IOA78EE PARALLEL: val1 MODET:val2. FOR PARALLEL=S, MODET MUST BE "TEST"Link copied to clipboard

Explanation: When the Control-M/Tape PARALLEL parameter is specified as "S", the MODET parameter must be "TEST".

Corrective Action: Change the Control-M/Tape PARALLEL parameter or the MODET parameter values.

IOA78FE DYNDS: val1 DYNVOL:val2. WHEN DYNDS=N, DYNVOL CANNOT CONTAIN "Y"Link copied to clipboard

Explanation: When the Control-M/Tape DYNDS parameter is specified as "N", the DYNVOL parameter cannot be "Y".

Corrective Action: Change the Control-M/Tape DYNDS parameter or the DYNVOL parameter values.

IOA78GE JS3CHRS: val1 textLink copied to clipboard

Explanation: The val1 value entered for the JS3CHRS parameter is invalid. The text field contains the explanation.

Corrective Action: Change parameter JS3CHRS as required.

IOA78HE AJFTYPE: val1 AJFSIZE: val2 AJFTYPE MUST BE LARGE OR EXTENDED TO SUPPORT MORE THAN 2,000,000 AJF RECORDS.Link copied to clipboard

Explanation: If the AJFSIZE is greater than 2,000,000 the AJFTYPE parameter must be LARGE or EXTENDED to support more than 2,000,000 AJF records (65,535 tracks).

Corrective Action: Change the Control-M AJFTYPE parameter or the AJFSIZE parameter values.

IOA78IE HSTTYPE: val1 HSTSIZE: val2 HSTTYPE MUST BE LARGE OR EXTENDED TO SUPPORT MORE THAN 2,000,000 HISTORY RECORDS.Link copied to clipboard

Explanation: If the HSTSIZE is greater than 2,000,000 the HSTTYPE parameter must be LARGE or EXTENDED to support more than 2,000,000 history records (65,535 tracks).

Corrective Action: Change the Control-M HSTTYPE parameter or the HSTSIZE parameter values.

IOA790E COULD NOT FIND OR OPEN FILE : dsn MEMBER : memNameLink copied to clipboard

Explanation: The installation application could not find or open the specified file.

Corrective Action: Check that the DSNAME and library name are specified correctly.

IOA791E NUMBER OF JOBS SPECIFIED IS NOT NUMERICLink copied to clipboard

Explanation: The user specified a non-numeric value for the number of jobs.

Corrective Action: Specify a numeric value for the number of jobs.

IOA792E NUMBER OF RULES SPECIFIED IS NOT NUMERICLink copied to clipboard

Explanation: A non-numeric value is specified for the number of rules.

Corrective Action: Specify a numeric value for the number of rules.

IOA793E NUMBER OF RETENTION DAYS IS NOT NUMERIC OR OUT OF RANGELink copied to clipboard

Explanation: A non-numeric value or a number that exceeds the maximum is specified for the number of retention days.

Corrective Action: In the case of a non-numeric value, specify a numeric value for the number of retention days. If the number of retention days is too large, reduce it.

IOA794E AT LEAST ONE INPUT VALUE HAS TO BE ENTEREDLink copied to clipboard

Explanation: No values are specified.

Corrective Action: Specify at least one value.

IOA795E RESPONSE SHOULD BE Y OR NLink copied to clipboard

Explanation: The specified value is neither Y (Yes) nor N (No).

Corrective Action: Specify either Y or N.

IOA796E INPUT CHANGED. CHECK AND RE-ENTER Y OR NLink copied to clipboard

Explanation: After value was changed in the screen, there was an attempt to exit without confirmation.

Corrective Action: Specify Y to save the changes, or N to cancel the changes.

IOA797E INPUT IS NOT NUMERIC OR EXCEEDS - max_vol_numLink copied to clipboard

Explanation: Either a non-numeric value for the number of volumes or a number that exceeded the maximum was specified.

Corrective Action: Specify a numeric value that does not exceed the limit.

IOA798E FIELD MUST BE NON-EMPTY AND NUMERIC ONLYLink copied to clipboard

Explanation: A non-numeric value was specified or the field was left empty.

Corrective Action: Specify a numeric value only.

IOA799E BLOCK SIZE MUST BE NUMERIC AND MUST BE IN RANGELink copied to clipboard

Explanation: A non-numeric block size or a number that was outside the range was specified.

Corrective Action: Specify a numeric value that is within the specified range.

IOA79AE CANNOT CALCULATE SPACE BECAUSE OF HUGE NUMBERSLink copied to clipboard

Explanation: The quantities are too large to be handled by the space calculation program.

Corrective Action: Reduce one or more quantities.

IOA79BE FIELD MUST BE NON-EMPTY AND NUMERIC ONLYLink copied to clipboard

Explanation: A non-numeric value was specified or the field was left empty.

Corrective Action: Specify a numeric value only.

IOA79CE VALID VALUE FOR EXTEND IS A OR MLink copied to clipboard

Explanation: A value other than A (Automatic) or M (Manual) was specified for EXTEND. Only A or M is a valid value in the EXTEND parameter.

Corrective Action: Specify either A or M for EXTEND.

IOA79DE PERCENT MUST NOT BE BLANK AND HAS TO BE NUMERICLink copied to clipboard

Explanation: No numeric value is specified for the PERCENT parameter.

Corrective Action: Specify a numeric value in the PERCENT parameter.

IOA79EE DEVICE TYPE IS NOT ONE OF 3350,3380,3390,9345Link copied to clipboard

Explanation: The specified device type is not supported.

Corrective Action: Specify one of the listed device types in the DEVICE TYPE parameter.

IOA79FE VOLUME PARAMETERS INCORRECTLY ENTEREDLink copied to clipboard

Explanation: One or more volume parameters is specified incorrectly. One VOLUME parameter is mandatory. It must be specified in the first VOLUME field. Any additional VOLUME parameters must be specified consecutively in the subsequent fields, without leaving gaps between them.

Corrective Action: Specify the VOLUME parameters as described above.

IOA7A0E NUMBER OF BLOCKS EXCEEDED 65535. INCREASE BLOCK SIZELink copied to clipboard

Explanation: The specified number of blocks exceeds the maximum allowed.

Corrective Action: Decrease the number of blocks or enlarge the block size.

IOA7A1E INPUT MUST CONFORM TO VOLUME SERIAL NUMBER RULESLink copied to clipboard

Explanation: The specified volume serial number contains an invalid character or the field was left blank.

Corrective Action: Correct the volume serial number specified for invalid characters or make sure that the field is not empty.

IOA7A2E WHEN SPECIFYING DUAL=N THIS FIELD MUST BE BLANK OR NLink copied to clipboard

Explanation: DUAL=N is specified, but the field on which the cursor is positioned is neither blank nor N. When DUAL=N is specified by the user, the field in question must either be left empty, or be filled in with an N.

Corrective Action: Either blank out the field or specify N.

IOA7B0E dsn(memName) DATASET OR MEMBER NOT FOUNDLink copied to clipboard

Explanation: The specified member was not found in the specified library.

Corrective Action: Check the member and library name, and correct if necessary.

IOA7B1I DATA INSERTED INTO colLink copied to clipboard

Explanation: This information message indicates that the data specified was successfully incorporated into the specified column.

Corrective Action: No action is required.

IOA7B2I varName IN TABLE tableName CLEAREDLink copied to clipboard

Explanation: This information message indicates that the specified variable in the identified table was reset as required.

Corrective Action: No action is required.

IOA7B3E RESPONSE SHOULD BE YES OR NOLink copied to clipboard

Explanation: The specified value is invalid.

Corrective Action: Specify either YES or NO.

IOA7B4W NO CONFIRMATION TO OVERRIDELink copied to clipboard

Explanation: This warning message requests confirmation for copying parameter values from a previous IOA installation to a new installation. The message “Confirm erasing and replacing all entered data” appears on the screen with a default of NO to prevent accidental override of new installation values with old ones.

Corrective Action: To override the parameter values in the new installation with those of the previous installation, specify YES in the “Confirm erasing and replacing all entered data” field.

IOA7B5E NO REFERENCE INSERTED. RETURN CODE rcLink copied to clipboard

Explanation: An internal error occurred. As a result no reference value was inserted into the table.

In this message, rc is the return code issued by ISPF. Valid values are:

Return Code

Explanation

12

Table is not open

16

Truncation occurred when reading a table

20

A severe error occurred when reading a table

24

Dynamic allocation of a library and member failed

Corrective Action: Check the return code specified in the message in ISPF documentation, and correct accordingly. Rerun the activity or step.

IOA7B6E ACTION NOT PERFORMED. RETURN CODE rcLink copied to clipboard

Explanation: An internal error occurred, and as a result the requested action was not performed.

In this message, rc is the return code issued by ISPF. Valid values are:

Return Code

Explanation

12

Table is not open

16

Truncation occurred when reading a table

20

A severe error occurred when reading a table

24

Dynamic allocation of a library and member failed

Corrective Action: Check the return code specified in the message in ISPF documentation, and correct accordingly. Rerun the activity or step.

IOA7B7I REFERENCE AND VALUE REMAIN UNCHANGEDLink copied to clipboard

Explanation: This information message indicates that there is no reference data in either of the columns in the screen.

Corrective Action: No action is required.

IOA7B8I ICE TABLES REPLACEDLink copied to clipboard

Explanation: This information message indicates that the existing ICE tables were replaced by a new set. The values and the step status were copied from the old table to the new.

Corrective Action: No action is required.

IOA7B9E MULTIPLE SELECTIONS IS NOT ALLOWED WHEN "A" IS SELECTEDLink copied to clipboard

Explanation: You cannot select more than one row when selecting a row with "A".

Corrective Action: Make sure that only one row is selected. Clear all but one selected row.

IOA7B9I tableName colName CLEAREDLink copied to clipboard

Explanation: This information message indicates that all the values in the specified column of the ICE table were cleared in response to a clear request.

Corrective Action: No action is required.

IOA7BAE THE IOA RELEASE, release, IS NOT SUPPORTED FOR ADAPTATIONLink copied to clipboard

Explanation: The IOA release, release, is not supported for adaptation.

Corrective Action: Consider upgrading to IOA release release.

IOA7BBE SAME LIBRARIES USED FOR INPUT AND OUTPUTLink copied to clipboard

Explanation: The same names were used for the input and output libraries.

Corrective Action: Change the names so that they are different.

IOA7BCE REFERENCE LIBRARIES PREFIX MUST BE SET TO PERFORM THE ADAPTATIONLink copied to clipboard

Explanation: The Reference Libraries Prefix is missing.

Corrective Action: Provide the Reference Libraries Prefix to continue with the Express Upgrade process.

IOA7BEE REFERENCE LIBRARY CAN NOT BE EMPTYLink copied to clipboard

Explanation: In the environment definition panel of ICE, the user asked that the values of the referenced environment will be used in the new environment being referenced. However, the user left the References Libraries Prefix field, which points to the referenced environment, empty.

ICE displays the environment definition panel again.

Corrective Action: Specify a valid prefix in the References Libraries Prefix field and point to the referenced environment. Alternatively, you can set the Insert references into current values field in the panel to No. This means that the values will not be inserted in the current environment.

IOA7E0I textLink copied to clipboard

Explanation: The text describes the step that was performed during the Express installation.

Corrective Action: No action is required.

IOA7E1E IOA: This IOA environment already exists.Link copied to clipboard

Explanation: The given prefixes for installation, operation, SMP/E, or databases for the IOA environment already exist. The installation stops and the IOA7E0I message is displayed.

Corrective Action: Return to the long parameters panel and change the prefixes.

IOA7E2E product_name: The Product is already installed, please deselect it.Link copied to clipboard

Explanation: The given prefixes for installation, operation, or databases for the product are already allocated. The installation stops and the IOA7E0I message is displayed.

Corrective Action: Either return to the long parameters panel and change the prefixes or deselect this product from the Products and Sizes panel.

IOA7E3E product_name: textLink copied to clipboard

Explanation: This is a verification error. First the step where the error occurred is indicated and then the error itself is described. The installation stops.

Corrective Action: Fix the parameter and resume the installation.

IOA7E4E product_name: textLink copied to clipboard

Explanation: This is an installation error. First the step where the error occurred is indicated and then the error itself is described. The installation stops.

Corrective Action:Analyze the problem to determine if it is a job or a process failure.

IOA7E5I The Installation ended with ==> SuccessLink copied to clipboard

Explanation: The installation ended successfully.

Corrective Action: Proceed to the post installation steps.

IOA7U0I textLink copied to clipboard

Explanation: The text describes an action that was performed during the Express Upgrade process.

Corrective Action: No action is required.

IOA7U0E Express Upgrade error messageLink copied to clipboard

Explanation:This tracking error message can contain one of the following messages:

  • The ExecName exec terminated with Rc Rc

  • The job JobName(JobId) failed. Analyze the job and, after correcting the problem, rerun the step.

  • The Product product has an existing prefix in the DataSetName library.

  • The Product product has an existing procedure in the DataSetName library.

  • Error at: Copy new started tasks

  • The Switch step has FAILED

  • Error at: Updating QNAMEs in repositories of new products

  • The FALLBACK process has FAILED

  • Error at: Backup the site libraries

  • Reference values from release prior to 6.0.00 is not supported.

  • Error at step analyze. Check the ICELOG and, after correcting the problem, rerun the step.

  • Error during LMINIT Lib Rc Rc

  • Failed to Save Parameters Save Product Parameters into Installation Library ended NOT-OK. Check the ICELOG and, after correcting the problem, rerun the step.

  • The OLD environment has at least one installed product that is missing in the NEW environment. Please refer to the Limitations in the Express Upgrade section of the Installation Guide.

  • ICE failed to check availability to copy stc/proc to system library. Check that the Lib library is available for processing.

  • The Environment Prefix Pref doesn't exist in the table DataSetName (IOAITENV)

  • ICE of the OLD environment is not available. An internal error occurred. As a result, ICE failed to open one of the OLD environment tables. Check the ICELOG for an additional IOAI0BE error message for complete information about the error. After correcting the problem, rerun the step.

  • The OLD environment with this ILPREFA is already being upgraded to the NEW environment EnvironmentPrefix. The same OLD environment cannot be simultaneously upgraded to more than one NEW environment.

  • Error at: Adjust xxxSET members in the PROCLIB library.

  • Error at: - Adjust started tasks in the site library.

Corrective Action: Analyze the failure, correct the cause of the problem, and then continue with the Express Upgrade process.

IOA7U0W Express Upgrade warning messageLink copied to clipboard

Explanation:This tracking warning message can contain one of the following messages:

  • Adaptation process was canceled by the user

  • Changing parameters has been canceled by the user

  • Differences were found between the OLD and NEW environments. Either correct the differences and rerun the step, or confirm the differences.

Corrective Action: No action is required.

Messages IOA800 through IOA8xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA830S PASSWORD CHECK FAILEDLink copied to clipboard

Explanation: The CTTINIT procedure discovered an error in the Control-M/Tape password.

This messages follows other messages that detail the error and password.

The CTTINIT procedure stops.

Corrective Action: Check the job log of CTTINIT for previous messages that refer to this failure, and proceed accordingly.

Messages IOA900 through IOA9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOA913S OPEN OF DDNAME "SYSPRINT" FAILEDLink copied to clipboard

Explanation: The opening of a print file failed.

Possible causes are:

  • The SYSPRINT DD statement is missing.

  • The data set described by the SYSPRINT DD statement cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

IOA915S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: An error was detected during an attempt to open the file referenced by the SYSPRINT DD statement.

The file referenced by the SYSPRINT DD statement is not opened.

Corrective Action: Check the system job log, and correct the problem accordingly. Rerun the job.

IOA946S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: The IOADII utility detected an error when opening the file referenced by the SYSPRINT DD statement.

The file referenced by the SYSPRINT DD statement is not opened.

Corrective Action: Check the system job log, and correct the problem accordingly. Rerun the job.

IOA951S RELEASE OF LOG FILE NOT SUPPORTED BY THIS RELEASE OF IOA.Link copied to clipboard

Explanation: Release of Log file is not supported by this release of IOA

This could be due to one of the following:

  • The release of IOA has been changed, and you are working on a file of a different release.

  • Your Log file has been corrupted.

Access to the IOA Log is prevented. An “OPEN OF LOG FILE FAILED” message will appear.

Corrective Action: Correct the allocation of your Log file (the DALOG DD statement).

IOA952S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed (the DALOG DD statement). Possible causes are:

  • The DALOG DD statement is missing.

  • The file allocated to the DALOG DD statement is not the IOA Log file.

  • The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA installation.

Termination of the requested function.

Corrective Action: Look on the computer log or job log SYSOUT for additional messages that clarify the reason for the failure. Then, correct the JCL for the job, or the allocations of the CLIST.

IOA954S IOA LOG FILE - WRITE ERRORLink copied to clipboard

Explanation: I/O error while writing to IOA Log file. Possible causes are:

  • The file allocated to the DALOG DD statement is not the IOA Log file.

  • Real I/O error on the Log file.

Corrective Action: Check the contents of the computer log for additional messages which may clarify the situation, or logon again.

IOA957S FILE ALLOCATED TO DDNAME "ddName" IS NOT YOUR IOA LOGLink copied to clipboard

Explanation: The data set described by the specified DD statement is not the IOA Log file of this IOA installation. It is an IOA Log file, but it is of a different QNAME. It belongs to another IOA installation.

Corrective Action: Correct the JCL for the job or CLIST.

IOA958S FILE ALLOCATED TO DDNAME "ddname" IS NOT AN IOA LOGLink copied to clipboard

Explanation: The data set described by the specified DD statement is not an IOA Log file.

Corrective Action: Correct the JCL for the job or CLIST.

IOA959S IOA LOG FILE IS FORMATTED. IOABLG PROBABLY ABENDEDLink copied to clipboard

Explanation: The IOABLG program, which formats the IOA Log file, probably abended.

Corrective Action: Check the IOA Log format job output to see why the IOABLG program abended. Delete the file and recreate it using the INCONTROL Installation and Customization Engine (ICE).

IOA95AE UNABLE TO SYNCRONIZE THE LOG FILELink copied to clipboard

Explanation: Internal synchronization of the Log file failed, probably because another process in the same address space has been holding the Log file for a long time. A record might be missing in the IOA Log file.

The Log operation fails.

Corrective Action: Take a dump of the failing address space. When the dump completes, stop and restart it to release the internal lock. Have your system programmer call your IOA representative for assistance.

IOA960S MISSING INPUT PARAMETERSLink copied to clipboard

Explanation: No input parameters were specified for utility IOADUL.

The IOADUL utility ends with a return code of 32.

Corrective Action: Rerun the IOADUL utility using valid input parameters. See the IOADUL utility in the INCONTROL for z/OS Utilities Guide for valid parameters.

IOA963S FORMATTING IOA LOG - WRITE I/O ERRORLink copied to clipboard

Explanation: An I/O error occurred while formatting the IOA Log file. This error may occur when there is incompatibility between the definition of the Log file in the Installation Parameters (IOAPARM) and the JCL SPACE and DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters.

IOA964I FORMATTING OF IOA LOG FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOA Log file format process has started.

Corrective Action: No action is required.

IOA965I FORMATTING OF IOA LOG FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOA Log file format process has terminated normally.

Corrective Action: No action is required.

IOA966S IOA LOG FILE WAS NOT BUILTLink copied to clipboard

Explanation: Formatting of the IOA Log file failed.

Corrective Action: Look in the job log or SYSPRINT for error messages that describe the type of error.

IOA9A0I action OF IOA LOG STARTEDLink copied to clipboard

Explanation: This information message is a normal start message of the IOACPLOG utility. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

Corrective Action: No action is required.

IOA9A1I action OF IOA LOG ENDEDLink copied to clipboard

Explanation: This information message is a normal termination message of the IOACPLOG utility. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

Corrective Action: No action is required.

IOA9A2S action OF IOA LOG ENDED WITH ERRORS.Link copied to clipboard

Explanation: The IOACPLOG utility failed to copy the IOA Log file. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

The IOACPLOG utility ended with a condition code of 08 or 12.

Corrective Action: Check the preceding error messages in the job log or in the SYSPRINT sysout, correct the problem, and rerun the job.

Messages IOAA00 through IOAAxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAA80E INVALID PARM LIST OR NO PARM LISTLink copied to clipboard

Explanation: An invalid parameter was passed to the IOALOC program. The IOALOC program accepts either ALLOC or FREE as input parameters.

The IOALOC program stops executing.

Corrective Action: Supply the correct input parameter.

IOAAINI SSCT=add1,SSVT=add2,SWT=add3, SWT LENGTH=lenLink copied to clipboard

Explanation: This is one of the messages issued when either the Control-O monitor or the CMEM monitor starts, to provide information for use in case of any problem.

Corrective Action: No action is required.

Messages IOAB00 through IOABxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAB10E INTERNAL ERROR - INVALID TYPELink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB11E INTERNAL ERROR - PREVIOUS WORK AREAS NOT FREELink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB12E ERROR TRYING TO READ FORMAT MEMBERLink copied to clipboard

Explanation: An error occurred while reading a Display Type definition member. The required format member, $$xxx, probably does not exist in the MSG library.

The User Report List is not displayed.

Corrective Action: Make sure that the required format member, $$xxx, exists in the MSG library.

IOAB13E INTERNAL ERROR - MEMORY ALLOCATION FAILEDLink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB14I INVALID DEFINITION OF "ID=" KEYWORDLink copied to clipboard

Explanation: This information message indicates that an invalid value for the ID keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. For more information, see the INCONTROL for z/OS Installation Guide.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the ID keyword in the Display Type definition member.

IOAB15I INVALID DEFINITION OF "LTH=" KEYWORDLink copied to clipboard

Explanation: This information message indicates that an invalid value for the LTH keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. For more information, see the INCONTROL for z/OS Installation Guide.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the LTH keyword in the Display Type definition member.

IOAB16I VALUE OF "LTH=" KEYWORD NOT NUMERICLink copied to clipboard

Explanation: This information message indicates that a non-numeric value for the LTH keyword was specified in the Display Type definitions member. The LTH keyword must contain numeric characters only and a non-numeric character was detected. For more information, see the INCONTROL for z/OS Installation Guide.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the LTH keyword in the Display Type definition member to a numeric value.

IOAB17E INTERNAL ERROR (FFU)Link copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB18E INTERNAL ERROR IN GETSTLLink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB19I INVALID DEFINITION OF "LINES=" KEYWORDLink copied to clipboard

Explanation: This information message indicates that an invalid value for the LINES keyword was specified in the Display Type definition member. The lines before this error message contain the problematic entry. Check the keyword in these lines for the invalid value. For more information, see the INCONTROL for z/OS Installation Guide.

The display type definitions syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the LINES keyword in the Display Type definition member.

IOAB1AI VALUE OF "LINES=" KEYWORD NOT NUMERICLink copied to clipboard

Explanation: A non-numeric value for the LINES keyword was detected in the Display Type definitions member. The LINES keyword must contain numeric characters only and a non-numeric character was detected. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the LINES keyword in the Display Type definition member to a numeric value.

IOAB1BI VALUE OF "LTH=" KEYWORD NOT 80 OR 132Link copied to clipboard

Explanation: An invalid value for the LTH keyword was specified in the Display Type definition member. Valid values for the LTH keyword are 80 or 132. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the LTH keyword in the Display Type definition member to 80 or 132.

IOAB1CI THIS FORMAT ALREADY EXISTSLink copied to clipboard

Explanation: The specified type ID, TYPE and CLASS combination was previously defined on a @STYLE line in the Display Type definition member. A Display Type ID cannot be defined twice. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Change one of the Display Type IDs, or delete one of the Display Types.

IOAB1DE INTERNAL ERROR IN GETHDRLink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB1EI NO CURRENT VALID STYLELink copied to clipboard

Explanation: A @HEADER line was specified, but no valid preceding @STYLE exists. A @STYLE line must exist when a @HEADER line is specified. See the INCONTROL for z/OS Installation Guide for more information.

The display type definition syntax check bypasses the current @HEADER line.

Corrective Action: Add the @STYLE keyword or delete the @HEADER keyword in the Display Type definition member.

IOAB1FE INTERNAL ERROR IN GETLNELink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB20I INVALID VALUE FOR "NAME=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the NAME keyword was detected in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the NAME keyword in the Display Type definition member.

IOAB21I FIELD CANNOT BE "DATA" AND "NAME"Link copied to clipboard

Explanation: Both DATA and NAME keywords were specified on a @FIELD line, in the Display Type definition member. DATA and NAME keywords cannot be specified on the same @FIELD line. See the INCONTROL for z/OS Installation Guide for information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Delete either the DATA or the NAME keyword from the @FIELD line in the Display Type definition member.

IOAB22I FIELD IS NOT "DATA" OR "NAME"Link copied to clipboard

Explanation: Neither DATA nor NAME keywords were specified on a @FIELD line, in the Display Type definition member. Either DATA or NAME keyword must be specified on a @FIELD line. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Add either the DATA or the NAME keyword to the @FIELD line in the Display Type definition member.

IOAB23E INTERNAL ERROR - ALLOCATION FAILED FOR "DATA"Link copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB24E INTERNAL ERROR IN GETFLDLink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB25E INTERNAL ERROR - ALLOCATION FAILED FOR "DFLT"Link copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB26I NO CURRENT VALID LINELink copied to clipboard

Explanation: A @FIELD line was specified, but no valid preceding @LINE exists. When a @FIELD line is specified, a @LINE must precede it. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Add a @LINE after the @FIELD line or delete the @FIELD line in the Display Type definition member.

IOAB27I FIELD IS NOT EDITABLELink copied to clipboard

Explanation: The EDIT=YES keyword was specified on a field that is not editable in the Display Type definition member. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Delete the EDIT=YES keyword for this field in the Display Type definition member.

IOAB28I FIELD IS NOT DEFAULT-EDITABLELink copied to clipboard

Explanation: The DFLTEDIT=YES keyword was specified on a field that is not editable in the Display Type definition member. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Delete the DFLTEDIT=YES keyword for this field in the Display Type definition member.

IOAB29I VALUE OF "LTH=" KEYWORD IS AT LEAST 2Link copied to clipboard

Explanation: An invalid value for the LTH keyword was detected in the Display Type definition member. The value for the LTH keyword should be at least 2, to accommodate the attribute byte and a data byte. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the LTH keyword value to at least 2 in the Display Type definition member.

IOAB2AI FIELD STARTS AFTER END OF LINELink copied to clipboard

Explanation: The current field starts after the logical end of line. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the current field start in the Display Type definition member.

IOAB2BI FIELD ENDS AFTER END OF LINELink copied to clipboard

Explanation: The current field ends after the logical end of line. See the section on customizing IOA display format members in the INCONTROL for z/OS Administrator Guide.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the current field end in the Display Type definition member.

IOAB2CI INVALID DEFINITION OF "DFLT=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the DFLT keyword was detected in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the DFLT keyword in the Display Type definition member.

IOAB2DI INVALID DEFINITION OF "DATA=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the DATA keyword was detected in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the DATA keyword in the Display Type definition member.

IOAB2EI INVALID DEFINITION OF "NAME=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the NAME keyword was detected in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the NAME keyword in the Display Type definition member.

IOAB30I INVALID DEFINITION OF "DLM=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the DLM keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @DLM line.

Corrective Action: Correct the invalid value for the DLM keyword in the Display Type definition member.

IOAB31I INVALID DEFINITION OF "COLOR=/COLORA=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the COLOR or COLORA keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE, @LINE or @FIELD line.

Corrective Action: Correct the invalid value specified for the COLOR or COLORA keyword in the Display Type definition member.

IOAB32I INVALID VALUE FOR "COLOR=/COLORA=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the COLOR or COLORA keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE, @LINE or @FIELD line.

Corrective Action: Correct the invalid value specified for the COLOR or COLORA keyword in the Display Type definition member.

IOAB33I INVALID DEFINITION OF "HIGH=/HIGHA=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the HIGH or HIGHA keyword was specified in the Display Type definition member. The lines preceding this message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE, @LINE or @FIELD line.

Corrective Action: Correct the invalid value specified for the HIGH or HIGHA keyword in the Display Type definition member.

IOAB34I INVALID VALUE FOR "HIGH=/HIGHA=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the HIGH or HIGHA keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE, @LINE or @FIELD line.

Corrective Action: Correct the invalid value specified for the HIGH or HIGHA keyword in the Display Type definition member.

IOAB35I FORMAT CANNOT HAVE A BLANK IDLink copied to clipboard

Explanation: The specified type ID has a blank value. The Display Type ID cannot be defined with a blank value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Enter a Display Type ID value other than blank.

IOAB36I INVALID DEFINITION OF "PREF=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the PREF keyword was specified in the Display Type definition member. The lines before this message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the PREF keyword in the Display Type definition member.

IOAB37I INTERNAL ERROR - ALLOCATION FAILED FOR "PREF"Link copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB38I PREFIX LENGTH TOO LONG - MUST LEAVE ROOM FOR DATALink copied to clipboard

Explanation: The specified PREF value is too long. The prefix length should be short enough to accommodate at least one data character in the field. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Shorten the PREF value to accommodate for at least one data character in the field in the Display Type definition member.

IOAB39E LINE TYPE BLANK IS NOT AFTER CONTINUATION MARKLink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB3AE INVALID LINE TYPELink copied to clipboard

Explanation: An invalid line type was specified in the Display Type definition member. In the Display Type definition member, the line type is determined according to the first ten characters of the line. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check stops. The User Report List is not displayed.

Corrective Action: Correct the invalid line type.

IOAB3BE CONTINUATION LINE SHOULD BE WITH BLANK TYPELink copied to clipboard

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Notify BMC Customer Support.

IOAB3CI NUMBER OF LINES IN FORMAT EXCEEDS MAXIMUM. LINE IGNOREDLink copied to clipboard

Explanation: Too many lines were specified for the current @STYLE keyword. The number of lines specified for the @STYLE keyword exceeded the maximum number of lines that can be defined. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @LINE line.

Corrective Action: Correct the number of lines in the @STYLE keyword in the Display Type definition member to a value that does not exceed the allowable maximum.

IOAB50I INVALID DEFINITION OF "IDLIKE=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the IDLIKE keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the IDLIKE keyword in the Display Type definition member.

IOAB51I INVALID DEFINITION OF "TYPELIKE=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the TYPELIKE keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the TYPELIKE keyword in the Display Type definition member.

IOAB52I INVALID DEFINITION OF "CLASSLIKE=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the CLASSLIKE keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the CLASSLIKE keyword in the Display Type definition member.

IOAB53I "IDLIKE=", "TYPELIKE=" AND "CLASSLIKE=" MUST ALL BE PRESENTLink copied to clipboard

Explanation: One of the keywords IDLIKE, TYPELIKE or CLASSLIKE, was specified and at least one of the other keywords was not present. When specifying one of the keywords IDLIKE, TYPELIKE or CLASSLIKE, the other two keywords must also be present. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Add the other missing keywords to the Display Type definition member.

IOAB54I INVALID DEFINITION OF "EDIT=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the EDIT keyword was specified in the Display Type definition member. There is an invalid value specified for the EDIT keyword in the Display Type definition member. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the EDIT keyword in the Display Type definition member.

IOAB55I INVALID VALUE FOR "EDIT=" KEYWORD. SHOULD BE YES/NOLink copied to clipboard

Explanation: An invalid value for the EDIT keyword was specified in the Display Type definition member. Valid values for the EDIT keyword are Y, YES, N, or NO. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the EDIT keyword value to Y, YES, N, or NO in the Display Type definition member.

IOAB56I INVALID DEFINITION OF "DEFAULTEDIT=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the DEFAULTEDIT keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the DEFAULTEDIT keyword in the Display Type definition member.

IOAB57I INVALID VALUE FOR "DEFAULTEDIT=" KEYWORD. SHOULD BE YES/NOLink copied to clipboard

Explanation: An invalid value for the DEFAULTEDIT keyword was specified in the Display Type definition member. Valid values for the DEFAULTEDIT keyword are Y, YES, N, or NO. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the DEFAULTEDIT keyword value to Y, YES, N, or NO in the Display Type definition member.

IOAB58I INVALID DEFINITION OF "AFORCE=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the AFORCE keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the AFORCE keyword in the Display Type definition member.

IOAB59I INVALID VALUE FOR "AFORCE=" KEYWORD. SHOULD BE YES/NOLink copied to clipboard

Explanation: An invalid value for the AFORCE keyword was specified in the Display Type definition member. Valid values for the AFORCE keyword are Y, YES, N, or NO. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the AFORCE keyword value to Y, YES, N, or NO in the Display Type definition member.

IOAB5AI INVALID DEFINITION OF "LONG=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the LONG keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the LONG keyword in the Display Type definition member.

IOAB5BI INVALID VALUE FOR "LONG=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the LONG keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the LONG keyword in the Display Type definition member.

IOAB5CI INVALID DEFINITION OF "INTENS=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the INTENS keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE, @LINE or @FIELD line.

Corrective Action: Correct the invalid value specified for the INTENS keyword in the Display Type definition member.

IOAB5DI INVALID VALUE FOR "INTENS=" KEYWORD. SHOULD BE YES/NOLink copied to clipboard

Explanation: An invalid value for the INTENS keyword was specified in the Display Type definition member. Valid values for the INTENS keyword are Y, YES, N, or NO. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE, @LINE or @FIELD line.

Corrective Action: Correct the INTENS keyword value to Y, YES, N, or NO in the Display Type definition member.

IOAB5EI INVALID DEFINITION OF "KANJI=" KEYWORDLink copied to clipboard

Explanation: An invalid value for the KANJI keyword was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the KANJI keyword in the Display Type definition member.

IOAB5FI INVALID VALUE FOR "KANJI=" KEYWORD. SHOULD BE YES/NOLink copied to clipboard

Explanation: An invalid value for the KANJI keyword was specified in the Display Type definition member. Valid values for the KANJI keyword member are Y (Yes) and N (No).

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the KANJI keyword value to either Y or N in the Display Type definition member.

IOAB60I INVALID DEFINITION OF "SHOWBLINE=" KEYWORDLink copied to clipboard

Explanation: An invalid value for keyword SHOWBLINE was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the SHOWBLINE keyword in the Display Type definition member.

IOAB61I INVALID VALUE FOR "SHOWBLINE=" KEYWORDLink copied to clipboard

Explanation: An invalid value for keyword SHOWBLINE was specified in the Display Type definition member. Valid values for the SHOWBLINE keyword member are Y (Yes) and N (No).

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the SHOWBLINE keyword value to either Y or N in the Display Type definition member.

IOAB62I INVALID DEFINITION OF "OFFSET=" KEYWORDLink copied to clipboard

Explanation: An invalid value for keyword OFFSET was specified in the Display Type definition member. The lines preceding this error message contain the problematic entry. Check the keyword in these lines for the invalid value. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the OFFSET keyword in the Display Type definition member.

IOAB63I VALUE OF "OFFSET=" KEYWORD NOT NUMERICLink copied to clipboard

Explanation: A non-numeric value for keyword OFFSET was detected in the Display Type definition member. The OFFSET keyword must contain numeric characters only and a non-numeric character was detected. See the INCONTROL for z/OS Installation Guide for more information.

The Display Type definition syntax check bypasses the current @STYLE line.

Corrective Action: Correct the invalid value for the OFFSET keyword in the Display Type definition member to a numeric value.

IOAB64I OFFSET VALUE IS OUT OF BOUNDSLink copied to clipboard

Explanation: The value specified for the OFFSET keyword exceeds the maximum length of the current field. The value of the OFFSET keyword should be less than the length of the field.

The Display Type definition syntax check bypasses the current @FIELD line.

Corrective Action: Correct the invalid value for the current field’s OFFSET keyword in the Display Type definition member.

Messages IOAC00 through IOACxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAC01I ENTER "M", "C", "CC" OR "MM" LINE COMMANDSLink copied to clipboard

Explanation: An A or B location command was specified without a corresponding copy or move type command when using the IOA Edit Environment in a definition screen. A copy or move command must accompany each location command.

Corrective Action: Specify a copy or move type command.

IOAC02I ENTER "A" OR "B" LINE COMMANDSLink copied to clipboard

Explanation: A copy or move type command was specified without a corresponding A or B location command when using the IOA Edit Environment in a definition screen. A location command must be specified in conjunction with copy or move commands.

Corrective Action: Specify an A or B location command.

IOAC03I ENTER A MATCHING "xx" COMMAND TO COMPLETE THE BLOCK COMMAND PAIRLink copied to clipboard

Explanation: An unmatched CC, MM, RR or DD command was specified when using the IOA Edit Environment in a definition screen. To perform multiple line functions, the required lines block must be delimited by two Multiple Lines Editing commands CC, MM, RR or DD.

Corrective Action: Specify a matching CC, MM, RR or DD command.

IOAC04E INVALID INPUT PARAMETERS FOR IOAEDIT ROUTINELink copied to clipboard

Explanation: An internal IOA error occurred when using the IOA Edit Environment in a definition screen.

Corrective Action: Contact BMC Customer Support.

IOAC05E "xx" IS NOT A VALID LINE COMMAND. CORRECT IT OR BLANK IT OUT.Link copied to clipboard

Explanation: An invalid Line Editing command was specified when using the IOA Edit Environment in a definition screen.

Corrective Action: Enter a valid Line Editing command.

IOAC06E "xx" COMMAND CONFLICTS WITH THE PRIOR SPECIFICATION. DELETE ONE.Link copied to clipboard

Explanation: When using the IOA Edit Environment in a definition screen, a Line Editing command was specified that conflicts with a previously specified Line Editing command.

Corrective Action: Remove the conflicting specification.

IOAC07E INVALID RETURN CODE FROM IOAEDIT ROUTINELink copied to clipboard

Explanation: An internal IOA error occurred when using the IOA Edit Environment in a definition screen.

Corrective Action: Contact BMC Customer Support.

IOAC08E ENTER "xx" TO COMPLETE A BLOCK PAIR BEFORE ENTERING OTHER COMMANDSLink copied to clipboard

Explanation: An A or B location command was specified within a lines block delimited by Multiple Lines Editing commands CC, MM, RR or DD, when using the IOA Edit Environment in a definition screen. A location command may not be specified within a multiple lines block.

Corrective Action: Remove the conflicting specification.

IOAC09E INTERNAL ERROR IN IOAEDIT ROUTINELink copied to clipboard

Explanation: An internal IOA error occurred when using the IOA Edit Environment in a definition screen.

Corrective Action: Contact BMC Customer Support.

IOAC11E REQUESTED EDIT FUNCTION NOT VALID FOR THIS LINELink copied to clipboard

Explanation: When using the IOA Edit Environment in a definition screen, a Line Editing command was specified which, if executed, would result in an invalid definition. When a Line Editing command is entered, Automatic Syntax Checking is performed to ensure that the definition remain syntactically correct after editing.

The requested edit action is not performed.

Corrective Action: Enter a valid Line Editing command.

IOAC12E COMMAND NOT SUPPORTED YETLink copied to clipboard

Explanation: When using the IOA Edit Environment in a definition screen, a Line Editing command was specified which is not supported in the current IOA release.

Corrective Action: Enter a valid Line Editing command.

IOAC13E INSUFFICIENT MEMORY FOR EDIT MODELink copied to clipboard

Explanation: The EDIT command was entered on a definition screen in order to access the IOA Edit Environment, but insufficient storage was available.

Corrective Action: Suggested actions:

  • Log on again using a larger SIZE parameter.

  • If you are using many IOA screens concurrently, exit from some of them using the END command.

IOAC21E KANJI IS NOT ALLOWED IN THIS FIELDLink copied to clipboard

Explanation: User-specified KANJI symbols, which use double bytes, were specified in a field which must contain single bytes only. Only certain fields support double-byte specification.

Corrective Action: Remove the double bytes from the field.

IOAC39I SECURITY FOR product IS {ACTIVE | INACTIVE}Link copied to clipboard

Explanation: This information message gives the security status (either ACTIVE or INACTIVE) for a specific product.

In this message, product is IOA, Control-M, Control-D, Control-O, Control-M/Tape, or Control-M/Analyzer.

Corrective Action: No action is required.

Messages IOAD00 through IOADxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAD01I EXTERNAL TRACE LEVELS SET AS FOLLOWS:Link copied to clipboard

Explanation: This information message indicates that either a TRACE modify command was issued or a TRACE request was received from a DATRCIN/DATRCBF input data stream for external trace, and the trace parameters are successfully processed. It is a header for subsequent IOAD02I messages.

Corrective Action: No action is required.

IOAD02I lvl1[:lvl2] - TURNED statusLink copied to clipboard

Explanation: This information message follows messages IOAD01I (or IOAT0CI followed by IOAT0DI) and indicates the specific trace level or number of levels following one after another that are set to either ON or OFF status. Sometimes, more than one IOAD02I messages are issued.

The variables in this message are:

  • lvl1 - a specific trace level that is set to status status. In cases when : lvl2 also appears in a message, it is a starting trace level set to status status.

  • lvl2 - the string : lvl2 may or may not appear in a message. In cases when : lvl2 also appears in a message, lvl1 and lvl2 indicate an interval of trace levels from lvl1 through lvl2 that is set to status status.

  • status - may be either ON or OFF:

    • ON--trace was activated

    • OFF--trace was deactivated

Corrective Action: No action is required.

IOAD03I THE FOLLOWING LEVELS ARE SET FOR xtrace :Link copied to clipboard

Explanation:xtrace can equal EXTERNAL TRACE or TRACE BUFFER: bufid. This message is issued as a result of command TRACE=SHOW or TRACE=DISP. It is a header for subsequent IOAD04I messages.

Corrective Action: No action is required.

IOAD04I lvl1:lvl2 - statusLink copied to clipboard

Explanation: This information message follows messages IOAD03I and indicates specific trace level or number of levels following one after another that are in either ON or OFF status.

The variables in this message are:

  • lvl1 - a specific trace level that is in status status. In cases when : lvl2 also appears in a message, its starting trace level is set to status status.

  • lvl2 - the string : lvl2 may or may not appear in a message. In cases when : lvl2 also appears in a message, lvl1 and lvl2 indicate an interval of trace levels from lvl1 through lvl2 that is set to status status.

  • status - may be either ON or OFF.

Several IOAD04I messages may be issued for a single IOAD03I message.

Corrective Action: No action is required.

IOAD45E AT LEAST ONE VALID COND MUST BE SPECIFIED IN THE ISCPARM MEMBERLink copied to clipboard

Explanation: No conditions to be passed to the other CPU were specified in the ISCPARM member allocated to one of the Control-M monitors. The DAISCPRM DD statement should point to a library containing the ISCPARM member. This member should contain at least one COND= cond statement, where cond is a condition name up to 20 characters. Masking characters * and ? are allowed. Only these conditions are passed to the other CPU.

CTMISR routine returns a return code of 24 to the calling IOA Exit 7. No conditions are passed to the other CPU.

Corrective Action: Add at least one COND=cond statement in the ISCPARM member and then shut down and restart the monitor. COND=* is valid for passing all the conditions.

IOAD46S CTMBLT ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTMBLT utility ended due to errors. CTMBLT creates Control-M scheduling tables. If CTMBLT ended with errors, messages in the Error Messages file DAPRINT DD statement explain the reasons. The Error Table Definitions file DATABERR DD statement contains the input definition statements that have the errors.

The utility ends with a non-zero return code.

Corrective Action: Correct all problems, and rerun the job.

IOAD48I CTMBLT ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTMBLT utility ended normally. The CTMBLT utility creates Control-M scheduling tables.

Corrective Action: No action is required.

IOAD90E INVALID PARM WAS PASSED TO IOALLOCLink copied to clipboard

Explanation: Invalid parameters were passed to load the IOALLOC module.

The IOA session is ended.

Corrective Action: No action is required.

IOAD91E UNABLE TO OBTAIN ENQ FOR IOALLOCLink copied to clipboard

Explanation: The IOALLOC module was unable to obtain an exclusive lock for processing.

The IOA session is ended.

Corrective Action: No action is required.

IOAD92E DAPARM DD STATEMENT MISSINGLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because the DAPARM DD statement is missing.

The IOA session is ended.

Corrective Action: No action is required.

IOAD93E GETMAIN FAILED, INSUFFICIENT STORAGELink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because of a storage shortage.

The IOA session is ended.

Corrective Action: No action is required.

IOAD94E IOALLOC BUFFERS ARE EXHAUSTEDLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because of a storage shortage.

The IOA session is ended.

Corrective Action: No action is required.

IOAD95E IOAPRS INITIALIZATION FAILEDLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because the initialization of IOAPRS module failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD96E PARSE ERROR OR MANDATORY PARAMETER IS MISSING, LINE lineNum MEMBER memNameLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because there is an incorrect member memName in line lineNum.

The IOA session is ended.

Corrective Action: No action is required.

IOAD97E PARSING ERROR IN LINE : num MEMBER : memNameLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because there is an incorrect member memName in line lineNum.

The IOA session is ended.

Corrective Action: No action is required.

IOAD98E EITHER DDNAME OR DSNAME WAS NOT SUPPLIED FOR KEY keyNameLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because of an incorrect key.

The IOA session is ended.

Corrective Action: No action is required.

IOAD99E UNABLE TO CREATE TOKENLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because the creation of a token failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9AE INVALID RECORD FOUND IN ALC MEMBER memName- LINE lineNumLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because of an incorrect member memName in line lineNum.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9BE REQUESTED KEY keyName WAS NOT FOUND IN IOADSN/IOADSNLLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because of a missing key in the IOADSN or IOADSNL members.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9CE ALLOCATION FAILED FOR DDNAME : ddNameLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because the allocation of DDNAME ddName failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9DE DD "DAALOCIN" IS MISSING OR CONTAINS A NON PDS DATASETLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because the allocation of a DD NAME failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9FE MEMBER memName WAS NOT FOUND IN THE "DAPARM" DD STATEMENT CONCATENATIONLink copied to clipboard

Explanation: The IOALLOC module is unable to continue its processing because the memName member is missing in the DAPARM DD concatenation.

The IOA session is ended.

Corrective Action: No action is required.

IOADB1E PARAMETER parm WAS NOT FOUND BY IOADEFP (CALLER: progName)Link copied to clipboard

Explanation: The progName program failed to find the parm parameter.

The action fails. Additional error messages follow.

Corrective Action: Make sure that:

  • The DAPARM dd statement points to the correct IOA.PARM library.

  • The parm parameter is defined correctly in the DEFPARM member in IOA PARM.

IOADB2E IOADEFP FOR parm FAILED WITH RC=rc (CALLER: progName MCT: address)Link copied to clipboard

Explanation: The IOADEFP service failed when it was requested to retrieve the value of the parm DEFPARM parameter.

The variables in this message are:

  • parm - the name of the DEFPARM parameter

  • rc - the return code

  • progName - the name of the calling program

  • address - the address of the IOA main control block

The action fails. Additional error messages follow.

Corrective Action: Contact BMC Customer Support for assistance.

IOADJ1E COMMAND IS NOT RECOGNIZEDLink copied to clipboard

Explanation: An invalid line command was issued.

Corrective Action: Correct the command.

IOADJ2E COMMAND CONFLICTLink copied to clipboard

Explanation: A conflicting line command was issued. For example, a block was marked for copying, and an M (Move) command was then issued.

The system waits for the command to be corrected.

Corrective Action: Erase the conflicting line command.

IOADJ3E UNABLE TO OBTAIN ENOUGH STORAGE FOR EDITING THE MEMBERLink copied to clipboard

Explanation: There is insufficient storage available to edit the requested member.

Access is denied.

Corrective Action: Contact your INCONTROL administrator.

IOADJ4I MEMBER SAVEDLink copied to clipboard

Explanation: This information message is issued when a member has been saved.

Corrective Action: No action is required.

IOADJ5I MEMBER NOT SAVEDLink copied to clipboard

Explanation: This information message is issued when the user exits the EDIT screen without editing the member.

Corrective Action: No action is required.

IOADJ6E MEMBER NAME HAS NOT BEEN SUPPLIEDLink copied to clipboard

Explanation: An edit command was issued, but the name of the member to be edited was not supplied.

Access is denied.

Corrective Action: Supply a member name.

IOADJ7E DSNAME HAS NOT BEEN SUPPLIED OR IS NOT ALLOCATEDLink copied to clipboard

Explanation: The library name was not supplied.

Access is denied.

Corrective Action: Supply a library name.

IOADJ8E BLOCK COMMAND INCOMPLETELink copied to clipboard

Explanation: In a block command (CC, MM, RR, DD), only one line was marked. Two lines must be marked.

The system waits for the command to be corrected.

Corrective Action: Complete the block definition.

IOADJ9E COPY/MOVE IS PENDINGLink copied to clipboard

Explanation: A block copy or move command was issued with a line or block marked, but with no target line specified.

The system waits for the command to be corrected.

Corrective Action: Identify the target line, using the command A (After) or B (Before).

IOADJAS INTERNAL ERRORLink copied to clipboard

Explanation: An internal error has occurred.

Access is denied.

Corrective Action: Contact BMC Customer Support.

IOADJBI MEMBER NOT COPIEDLink copied to clipboard

Explanation: This information message is issued when a request to copy a member is cancelled.

Corrective Action: No action is required.

IOADJCE ACCESS DENIED TO THE REQUESTED LIBRARY AND/OR MEMBERLink copied to clipboard

Explanation: A request was made to access a member, but the user is not authorized to access the member.

Access is denied.

Corrective Action: If you consider that you ought to be authorized to access the library or member, contact your INCONTROL security administrator.

IOADJDE WRONG PARAMETERSLink copied to clipboard

Explanation: An internal error has occurred.

Access is denied.

Corrective Action: Contact BMC Customer Support.

IOADJEE NUMBER IS NOT ALLOWEDLink copied to clipboard

Explanation: An attempt was made to type numbers in a line command in which numbers are not allowed.

The system waits for the line command to be corrected.

Corrective Action: Remove the numbers from the line command.

IOADJFE CONFLICTING NUMBERSLink copied to clipboard

Explanation: A block command was issued, but with different repetition, for example, RR4 and RR5.

The system waits for the block command to be corrected.

Corrective Action: Correct the block command so as to specify the same repetition.

IOADJGE THE REQUESTED MEMBER IS IN USE BY ANOTHER USERLink copied to clipboard

Explanation: The user tried to edit a member, but that member is held by another user.

Access is denied.

Corrective Action: Try again later. If the problem persists, try to identify the user holding the member.

Messages IOAE00 through IOAExxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAE00E OPTIONS "S", "I", "J", "B", "F/O" AND "D" CANNOT BE MIXEDLink copied to clipboard

Explanation: The options line commands S, I, J, B, F/O, and D cannot be requested simultaneously. Only one option type can be selected at a time.

None of the options selected is performed.

Corrective Action: Select options one at a time.

IOAE01E OPTIONS "S", "I", "J", "B" AND "G" CANNOT APPEAR ON MULTIPLE LINESLink copied to clipboard

Explanation: The options line commands S, I, J, B, and G cannot be selected simultaneously on multiple lines. Only one of the options can be selected at a time.

None of the options selected is performed.

Corrective Action: Select the options one at a time.

IOAE02I FORCED BROWSE AS TABLE IN USE BY ANOTHER USERLink copied to clipboard

Explanation: There was an attempt to select a table that is in use by another user. As a result, access is automatically given to the table in Browse mode only. No jobs may be added or deleted, and no changes may be made to existing jobs, when a table is accessed in Browse mode.

The Job List screen is displayed in Browse mode.

Corrective Action: If the required action cannot be performed when the table is in Browse mode, exit, and try again later. If required, contact your INCONTROL administrator to modify your User Profile definition to specify that the Table List screen remains displayed when an attempt is made to select a table that is in use.

IOAE03E OPTIONS "D" AND "I" ARE INVALID UNDER BROWSELink copied to clipboard

Explanation: An invalid request was specified while accessing a table in Browse mode. The D (Delete) and I (Insert) options are not valid when a table is accessed in Browse mode. A list of options valid in Browse mode is at the bottom of the screen.

The requested option is not performed.

Corrective Action: In order to delete or insert entries, exit the Job List screen and re-enter by specifying the S (Select) option.

IOAE04E FIELD MUST BE BLANK, OR NUMERIC WITH LEADING ZEROESLink copied to clipboard

Explanation: An invalid value was specified for the field. This field must be blank (in some cases) or must contain a numeric value that includes leading zeroes.

No action is taken until a valid value is specified in the field, or until the screen is reset.

Corrective Action: Enter a valid value in the field, or reset the screen (if possible).

IOAE05E INVALID OPTION (TRY "Y", "N" OR BLANK)Link copied to clipboard

Explanation: A value other than Y, N or blank was specified in a Yes/No field.

No action is taken until a valid value is specified in the field, or until the screen is reset or cancelled.

Corrective Action: Specify Y, N or blank in the field, or reset or cancel the screen, if possible.

IOAE06S ERROR WHILE PREPARING FORMATSLink copied to clipboard

Explanation: Syntax errors were detected in the Display Type definition member. The Display Type definition member was loaded and analyzed and syntax errors were detected. Specific errors were previously displayed with the erroneous source lines.

The panel is not displayed.

Corrective Action: Correct the Display Type definition errors in the $$XXX member in the IOA MSG library and try to re-enter.

IOAE07S INTERNAL ERROR IN CTMTJOB RC=rcLink copied to clipboard

Explanation: An internal error occurred while attempting to display the error messages that resulted from the syntax check of the Display Type definitions.

The error messages are not displayed.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

IOAE08E "OPT" FIELD MUST EXIST IN FORMATLink copied to clipboard

Explanation: An attempt was made to specify an option, for example, Insert, Update, and the like. However, the OPTION field is not present in the current Display Type. The OPTION field must be defined in a Display Type in order to specify a required operation option.

No operations are performed.

Corrective Action: Add the OPTION field to the Display Type.

IOAE09E INVALID OPTIONLink copied to clipboard

Explanation: Invalid option specified in the field.

Corrective Action: Correct the option, and try again.

IOAE0AE USER NOT AUTHORIZEDLink copied to clipboard

Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.

Corrective Action: Check with your system security administrator.

IOAE0CE INTERNAL ERROR WHILE SETTING HEADER RC=rcLink copied to clipboard

Explanation: An internal error occurred while attempting to place the Display Type header in the screen.

The screen is not displayed.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

IOAE0DE YOU MUST GIVE A ONE LETTER DISPLAY TYPE NAMELink copied to clipboard

Explanation: No valid Display Type code was specified when entering the DISPLAY command. The DISPLAY command requires a one letter Display Type parameter. This parameter must indicate an existing Display Type.

The current Display Type is not changed.

Corrective Action: Specify a valid Display Type with the DISPLAY command.

IOAE0EE DISPLAY TYPE NAME SHOULD BE ONE LETTER ONLYLink copied to clipboard

Explanation: More than one letter was specified for the Display Type code when entering the DISPLAY command. The DISPLAY command requires a one letter Display Type parameter. This parameter must indicate an existing Display Type.

The current Display Type is not changed.

Corrective Action: Specify a valid, one letter Display Type with the DISPLAY command.

IOAE0FE DISPLAY TYPE "X" NOT FOUNDLink copied to clipboard

Explanation: Display of an invalid Display Type was requested. Only Display Types that are defined in appropriate $$ xxx files in IOA MSG libraries are valid, for example, Default Display Type D.

The requested Display Type is not displayed.

Corrective Action: Specify a valid Display Type.

IOAE0GE RECORD LENGTH OF THE LIBRARY IS NOT 80Link copied to clipboard

Explanation: Record length of the requested data set is not 80.

Corrective Action: Make sure you chose the correct library.

IOAE0KE ONLY ONE CALENDAR TYPE CAN BE SPECIFIEDLink copied to clipboard

Explanation: Both calendar types, Regular/Periodic and Rule-Based (RBC) (in screen 8), have been selected. Only one is allowed.

Corrective Action: Select one of the calendar types.

IOAE0LE SELECT CALENDAR TYPELink copied to clipboard

Explanation: Neither the Regular/Periodic nor the Rule-Based (RBC) calendar type (in screen 8) has been selected.

Corrective Action: Select either the Regular/Periodic or the Rule-Based (RBC) calendar type (in screen 8).

IOAE10E INVALID VALUE, USE "Y" OR "N"Link copied to clipboard

Explanation: Invalid value specified in the field. The cursor points to the field that contains the invalid value.

Corrective Action: Select Y for yes, or N for no.

IOAE11E ONLY TRAILING BLANKS ALLOWED IN FIELDLink copied to clipboard

Explanation: The field contains a leading blank, or two strings separated by blanks. Leading blanks and embedded blanks are not allowed in this field.

The cursor points to the first blank.

Corrective Action: Correct the field contents.

IOAE12E ERROR IN DEFINITION, DEFINITION SCREEN CANNOT BE BUILTLink copied to clipboard

Explanation: The entry contains invalid data. Possible causes are:

  • The entry requested does not contain definition data.

  • The entry requested contains definition data but has been incorrectly modified (by means of an editor or program) and now its contents do not conform to IOA standards.

Corrective Action: If the contents of the entry were modified, try to restore the entry to its original state. If you cannot or if this is not the problem, have your system programmer call BMC Customer Support.

IOAE13S ERROR IN COMMAND MEMBER - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Each IOA screen is controlled by an external command member that contains a list of all commands and synonyms supported under the screen. Command members reside in IOA Parameter Libraries. They should be named TscrCMD1, where scr is the screen name. The Parameters library should be allocated to the DACMDxx DD statement, where xx is the application ID. Possible causes are:

  • Somebody incorrectly changed the contents of the command member.

  • The DACMDxxx DD statement is allocated to the wrong library.

For more information about Command Members, see the section on defining new application types in the IOA Installation Considerations section of the INCONTROL for z/OS Installation Guide.

The screen is locked.

Corrective Action: To exit, press PA1 a few times. Ask your INCONTROL administrator for assistance.

IOAE14E INVALID SCROLL AMOUNTLink copied to clipboard

Explanation: Invalid scroll amount specified. Valid scroll amounts are: PAGE, HALF, CRSR, and MAX.

Corrective Action: Correct the scroll amount field.

IOAE15S INSUFFICIENT STORAGE. INCREASE SIZELink copied to clipboard

Explanation: Insufficient memory to perform the task.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter, or exit one of the screens using an END command.

IOAE16S LOADING OF IOA INSTALLATION PARAMETERS FAILEDLink copied to clipboard

Explanation: Loading of IOA or Control- x Installation Parameters failed.

The function requested is terminated.

Corrective Action: Look on the system log for additional messages.

IOAE17E IOA SUBSYSTEM subsys IS ACTIVE FOR ENVIRONMENT (IOA QNAME)Link copied to clipboard

Explanation: The subsys subsystem is already active for another IOA environment. The same subsystem name cannot be used for two IOA environments in parallel.

IOA subsystem initialization fails for the subsys subsystem.

Corrective Action: Either choose another subsystem name for the current environment of the IOA products, or deactivate the IOA online monitor and all the subsystem components of the old IOA environment and restart the subsystem.

IOAE18S SUBSYSTEM NAME subsys DOES NOT EXIST IN THE MVS TABLESLink copied to clipboard

Explanation: If OPTION was set to D for IOASINIT, the subsystem name does not exist. If OPTION was set to M for IOASINIT, or Control-O is started, the subsystem name does not exist and dynamic allocation of the MVS subsystem tables is not allowed.

If OPTION was set to D for IOASINIT, possible causes are:

  • There is a mismatch between the name specified in the AMNAME parameter in Control-D Installation Parameters and the name specified in the IEFSSNxx member on SYS1.PARMLIB.

  • The IEFSSNxx member on SYS1.PARMLIB was not modified to include the subsystem name.

If OPTION was set to M for IOASINIT, or Control-O is started, possible causes are:

  • There is a mismatch between the name specified in the SSNAME parameter in the IOA Installation Parameters and the name specified in the IEFSSNxx member on SYS1.PARMLIB, and dynamic allocation for the subsystem tables is not allowed (SSALLOC=N).

  • The IEFSSNxx member on SYS1.PARMLIB was not modified to include the subsystem name, and dynamic allocation for the MVS subsystem tables is not allowed (SSALLOC=N).

Initialization of the subsystem fails.

Corrective Action: Define the subsystem name in the MVS table.

If OPTION was set to D for IOASINIT, see the section on Control-D Operational Parameters for details about the AMNAME parameter. See the section on installing the Compressed Dataset Access Method (CDAM) in the Control-D chapter of the INCONTROL for z/OS Installation Guide for details about defining the subsystem name in MVS tables.

If OPTION was set to M for IOASINIT, or Control-O is started, see the following:

  • The section on IOA Operational Parameters for details about the SSNAME and SSALLOC parameters.

  • The section that describes how to install the IOA Subsystem in the IOA chapter of the INCONTROL for z/OS Installation Guide.

  • The section on installing the Control-M Event Manager Subsystem (CMEM) in the Control-M chapter of the INCONTROL for z/OS Installation Guide for details about defining the subsystem name in the MVS tables.

IOAE19E OPTIONS "D", "C" CANNOT BE MIXEDLink copied to clipboard

Explanation: Options D (Delete) and C (Change) were specified together. Options D and C cannot be mixed. Only one of these option types can be specified at a time.

Corrective Action: Remove conflicting options, and request one option type at a time. After one option type has been performed, request the other option type.

IOAE1AE OPTIONS "A", "E" CANNOT BE MIXEDLink copied to clipboard

Explanation: Options A (Add) and E (Erase) were specified together. Options A and E cannot be mixed. Only one of these option types can be specified at a time.

Corrective Action: Remove conflicting options and request one option type at a time. After one option type has been performed, request the other option type.

IOAE1BS OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed (the DALOG DD statement). Possible causes are:

  • The DALOG DD statement is missing.

  • The file allocated to the DALOG DD statement is not the IOA Log file.

  • The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA installation.

The requested function ends.

Corrective Action: Look on the computer log for additional messages that clarify the reason for the failure. Then, correct the JCL for the job, or the allocations of the CLIST.

IOAE1CE INSUFFICIENT STORAGE TO BUILD LIST - USE ANOTHER SELECTION CRITERIALink copied to clipboard

Explanation: There is insufficient storage available to insert a new entry in the list.

A new entry is not added.

Corrective Action: Increase the REGION size, exit any open screens, and retry the operation. An alternative is to reduce the number of generations.

IOAE1DI PLEASE FILL IN THE ENTRY DATALink copied to clipboard

Explanation: No data entered in an obligatory field.

Corrective Action: Fill in all obligatory fields.

IOAE1EI ENTRY ADDEDLink copied to clipboard

Explanation: Normal message of the I (Insert) option when a new entry is added successfully.

Corrective Action: No action is required.

IOAE1FI SOME REPORTS WERE HIDDEN BY USER SECURITY EXITLink copied to clipboard

Explanation: This information message indicates that for security reasons, one or more entries was not displayed. Control-M/Analyzer security exit CTBX003 determined that the user is not authorized to look at some entries.

One or more entries will be hidden from the user.

Corrective Action: No action is necessary. All entries for which there is authorization will be displayed. To change authorization settings, call your INCONTROL administrator.

IOAE1UE INVALID VALUE, USE "Y", "N", "P", OR "C"Link copied to clipboard

Explanation: An invalid value was entered in the SEND WITH CC field.

Valid values for the SEND WITH CC field are:

  • Y - Yes

  • N - No

  • P - Page Break

  • C - Page Break + CC

The cursor points to the field that contains the invalid value.

Corrective Action: Correct the value in the field.

IOAE1VE INVALID VALUE, USE "Y", "N", "L", OR "R"Link copied to clipboard

Explanation: An invalid value was entered in the CONVERT TO ASCII field.

Valid values for the CONVERT TO ASCII field are:

  • Y - Yes

  • N - No

  • L - Convert to ASCII and add line separator CRLF

  • R - Convert to ASCII and add line separator CR or CRLF

The cursor points to the field that contains the invalid value.

Corrective Action: Correct the value in the field.

IOAE20E AN ENTRY DELETED CANNOT BE HELDLink copied to clipboard

Explanation: A HOLD request was specified for an entry that was deleted. Once an entry is deleted it cannot be held.

Corrective Action: No action is required.

IOAE21E ENTRY ALREADY HELD. NO ACTION TAKENLink copied to clipboard

Explanation: A HOLD request was specified for an entry that is already being held. If an entry is already held, a new HOLD request in invalid.

The option is not performed.

Corrective Action: No action is required.

IOAE22E CANNOT PERFORM "FREE" OPTION. ENTRY IS NOT HELDLink copied to clipboard

Explanation: A FREE request was specified for an entry that is not being held. Only an entry that is held can be freed.

The option is not performed.

Corrective Action: No action is required.

IOAE23E "DELETE" OPTION SUPPORTED ONLY WHEN ENTRY IS HELDLink copied to clipboard

Explanation: A DELETE request was entered for an entry that is not being held. Only an entry that is held can be deleted.

The option is not performed.

Corrective Action: No action is required.

IOAE24E ENTRY HAS ALREADY BEEN DELETEDLink copied to clipboard

Explanation: A DELETE request was specified for an entry that was already deleted. Once an entry is deleted, it cannot be deleted again.

Corrective Action: No action is required.

IOAE25E AN ENTRY DELETED CANNOT BE FREEDLink copied to clipboard

Explanation: A FREE request was specified for an entry that was already deleted. Once an entry is deleted it cannot be freed.

Corrective Action: No action is required.

IOAE26S SECURITY VIOLATION FOR OPTION optLink copied to clipboard

Explanation: An option was rejected by a security or user exit. Each option request by a user is sent to both the security exit and the user exit, if any. Either can reject the option.

The option is not performed.

Corrective Action: To get authorization to perform this function, contact your INCONTROL administrator.

IOAE27E "WHY" OPTION VALID ONLY WHEN ENTRY IS IN "WAIT ACTIVATION" STATELink copied to clipboard

Explanation: The Why option ? was specified for an entry that does not have a WAIT ACTIVATION status. The Why option shows why an entry has a WAIT ACTIVATION status. The option is invalid if the entry has a different status.

Corrective Action: No action is required.

IOAE28E INVALID TIMELink copied to clipboard

Explanation: An invalid TIME FROM and/or TO value was specified. Specified TIME values must be valid times based on a 24 hour clock, in format hhmm, where hh is hours and mm is minutes.

Corrective Action: Correct the specified TIME values.

IOAE29S UNABLE TO LOAD MODULE modNameLink copied to clipboard

Explanation: Loading of the modName module failed. Possible causes are:

  • The IOA Load library is not in the load modules search list.

  • Insufficient storage available to load the module.

  • The modName module does not exist in the IOA Load library.

  • The IOA Load library was updated while you were working and the position of modName module has changed.

The function requested is terminated.

Corrective Action: Look on the system log for additional messages that clarify the problem. Suggested actions:

  • If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.

  • If the loading failed due to lack of storage then for batch jobs, increase the REGION size, and for TSO, try to log on again using a larger SIZE parameter. If you are using many IOA screens concurrently, try to exit a few using the END command. This can release storage that is used by the screens.

  • Add the modName module to the Load library.

  • If the IOA Load library was modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again. If the IOA Load library is in the Linklist, a refresh to the LLA is needed.

IOAE2AE INSUFFICIENT STORAGE TO INSERT NEW MEMBERLink copied to clipboard

Explanation: Insufficient storage available to insert a new entry.

Corrective Action: Suggested actions:

  • Log on again using a larger SIZE parameter.

  • If you are using many IOA screens concurrently, exit some of them using the END command.

IOAE2BE DEFINITION IS TOO LARGE AND SHOULD BE SPLITLink copied to clipboard

Explanation: Definition member is too large to be handled by IOA. Possible causes are:

  • Insufficient storage available to process the definition member.

  • The definition member is too large.

Corrective Action: Suggested actions:

  • Log on again using a larger SIZE parameter.

  • If you are using many IOA screens concurrently, exit some of them using the END command.

  • Split the definition member into two.

IOAE2CE INSUFFICIENT STORAGE TO SHOW DEFINITIONLink copied to clipboard

Explanation: Insufficient storage available to enter the definition screen.

Corrective Action: Suggested actions:

  • Log on again using a larger SIZE parameter.

  • If you are using many IOA screens concurrently, exit some of them using the END command.

IOAE2DE INSUFFICIENT STORAGE TO PROCESS CHANGES TO DEFINITION. CHANGES IGNOREDLink copied to clipboard

Explanation: Insufficient storage available to process the changes in the definition screen. All changes are ignored, and the user returns to the list screen. You can still try to save the entry.

Corrective Action: Do one of the following:

  • Log on again using a larger SIZE parameter.

  • If you are using many IOA screens concurrently, exit some of them using the END command.

IOAE2EE NO ENTRIES FOUND IN THE LIBRARY. PLEASE SPECIFY AN ENTRY NAMELink copied to clipboard

Explanation: IOA did not build the entry list as no entries were found in the library.

Corrective Action: Enter new entry name.

IOAE2FS INTERNAL PROGRAM ERROR. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal IOA error while processing an entry. Possible causes are:

  • The entry requested is not a valid IOA entry, although its structure is very similar to one.

  • The entry requested is a valid IOA entry but the entry was incorrectly modified by an editor or program, and now its contents do not conform to IOA standards.

  • Internal IOA program error.

Corrective Action: If the contents of the entry were modified, try to restore the entry to its original state. If you cannot, or if this is not the problem, have your system programmer call BMC Customer Support.

IOAE30E HELP CODE NOT FOUND, CODE = line_codeLink copied to clipboard

Explanation: Code line_code could not be found in the help member. A HELP request was entered, but the line-sensitive help data could not be retrieved.

The Help screen displayed is the beginning of the help member of the screen, instead of the information relevant specifically to the line at which the cursor is located.

Corrective Action: Have your INCONTROL administrator inform BMC Customer Support of this message and the code displayed.

IOAE31E ENTRY DOES NOT CONTAIN A VALID DEFINITIONLink copied to clipboard

Explanation: The requested entry is not a valid IOA definition member.

Possible causes are:

  • The entry requested is not a valid IOA definition member.

  • The member requested is a valid IOA definition member, but the entry was incorrectly modified by an editor or program, and now its contents do not conform to IOA standards.

Corrective Action: Enter a valid IOA definition. If the specified entry was incorrectly modified, try to restore it to its original state.

IOAE32E ENTRY IS IN USE BY ANOTHER USERLink copied to clipboard

Explanation: Another IOA user is currently working on the entry. Two users cannot work on the same entry simultaneously. The other user may be using the entry through either the IOA Online Facility or the ISPF editor.

Corrective Action: Try again later.

IOAE33E INSUFFICIENT STORAGE TO LOAD DEFINITIONLink copied to clipboard

Explanation: Insufficient storage available to load the definition member.

Corrective Action: Do one of the following:

  • Log on again using a larger SIZE parameter.

  • If you are using many IOA screens concurrently, exit some of them using the END command.

  • Split the entry into two.

IOAE34E MORE THAN num ENTRIES - CURRENT MAXIMUM EXCEEDEDLink copied to clipboard

Explanation: Too many entries in the definition member. The maximum number of entries permitted is number. This variable is site modifiable, and has a default of 500.

Corrective Action: Split the IOA definition member into two. If necessary, contact your INCONTROL administrator to increase the maximum number of entries permitted.

IOAE35E EXIT IOAX028 MSG - rcLink copied to clipboard

Explanation: This message is displayed from user exit IOAX028. The code displayed is an internal user code. Exit IOAX028 is invoked from certain IOA definition screens. For more information, refer to IOAX028 in the SAMPEXIT library.

Corrective Action: If necessary, contact your INCONTROL administrator for further information.

IOAE36E EXIT IOAX028 WAS CALLED MORE THAN 10 TIMES ONE AFTER ANOTHERLink copied to clipboard

Explanation: This message indicates that user exit IOAX028 was called more than ten times consecutively between ENTER commands. This exit was modified and activated so that for each invocation it enforces a new check of the screen, and after each check of the screen the exit is invoked again before the user regains control of the screen. This probably indicates an inner loop.

After the tenth time exit IOAX028 is called in a row, it is not called again, and the user regains control of the screen.

Corrective Action: Notify your INCONTROL administrator of the occurrence of this message.

IOAE37E MEMBER $$SPACE MAY NOT BE DELETEDLink copied to clipboard

Explanation: An attempt was made to delete the $$SPACE member in one of the directory lists. The $$SPACE member is a not an IOA member. It is a member of PDSMAN, and therefore, user access to it is restricted. The IOA delete option is invalid for deleting non IOA members like $$SPACE.

The $$SPACE member is not deleted.

Corrective Action: No action is required.

IOAE38I cpuSmfId ENTRY memName LIBRARY libfuncLink copied to clipboard

Explanation: This information message indicates that the memName member was:

  • Deleted from an IOA definition library. Whenever a user deletes a member , the action is recorded in the IOA Log file.

  • Sorted in an IOA definition library. The action may be recorded in the IOA Log file, depending on the TABUADT parameter in the IOAPARM member.

  • Created in an IOA definition library. The action may be recorded in the IOA Log file, depending on the TABUADT parameter in the IOAPARM member.

In this message, cpuSmfId is the SMFID of the CPU on which the session is active.

Corrective Action: No action is required.

IOAE39E MAXIMUM num. CANNOT ADD MORE ENTRIESLink copied to clipboard

Explanation: The definition member is full. The maximum number of entries in an IOA definition member is number. This variable is site-modifiable, and has a default of 500.

Corrective Action: Split the IOA definition member into two. If necessary, ask your INCONTROL administrator to increase the maximum number of entries permitted.

IOAE3AE PLEASE FILL IN LIBRARY NAMELink copied to clipboard

Explanation: Missing library name. The LIBRARY field is required.

Corrective Action: Fill in the name of the IOA definition library.

IOAE3BE ONE (AND ONLY ONE) EXIT OPTION MUST BE MARKED AS "Y" OR "N"Link copied to clipboard

Explanation: Two exit options are marked. Only one exit option may be marked with Y or N.

Corrective Action: Fill in Y or N in only one of the exit options.

IOAE3CI ENTRY HAS BEEN SAVED/CREATEDLink copied to clipboard

Explanation: This information message indicates that an IOA definition entry was saved or created. In some of the IOA entry definition lists this message is displayed after a definition entry is saved or created.

Corrective Action: No action is required.

IOAE3DS ERROR IN COMMAND MEMBER - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: The command member could not be accessed. Each IOA screen is controlled by an external command member. The Parameters library should be allocated to the DACMDxx DD statement, where xx is the application ID.

Possible causes are:

  • The contents of the command member were incorrectly changed.

  • The DACMDxx DD statement points to the wrong library.

The screen is locked.

Corrective Action: To exit, press PA1 a few times. Call your system programmer for assistance.

IOAE3EE NAME MUST BE FILLED INLink copied to clipboard

Explanation: No value was specified for the NAME parameter. The NAME parameter is mandatory.

Corrective Action: Specify a valid name.

IOAE3FE INVALID MODE. USE "P" - PROD, "T" - TESTLink copied to clipboard

Explanation: An invalid value was specified in the MODE field. The MODE parameter enables the user to determine whether specific actions are really performed, or only recorded and not implemented. Valid modes are P (Prod) and T (Test). In mode P, actions are implemented normally. In mode T, actions that would have been performed in mode P are merely recorded and not implemented.

Corrective Action: Specify a valid mode.

IOAE40E PLEASE FILL IN OWNERLink copied to clipboard

Explanation: An OWNER value was not specified. The OWNER parameter is mandatory. It identifies the ID of the user who requests IOA services.

Corrective Action: Specify a valid OWNER (user ID).

IOAE41E FIELD SHOULD BE NUMERICLink copied to clipboard

Explanation: A non-numeric value was specified in a numeric field.

Corrective Action: Specify a numeric value.

IOAE42E INTERNAL ERROR IN modName RC=rcLink copied to clipboard

Explanation: An internal error occurred during preparation or transmission of a panel for display on the screen. The name of the module in which the error occurred, and the return code, appear in the message.

The panel is not displayed.

Corrective Action: If modName is IOADAS and RC=000016, check the IOA LOG for message CTDE12E. If CTDE12E was issued, see “CTDE12E RESOURCE LIBRARY HAS AN INCORRECT FORMAT”.

Try to reenter the online environment after logging out and reconnecting. If this is unsuccessful, call BMC Customer Support with the information in the message.

IOAE43E INVALID NAMELink copied to clipboard

Explanation: An invalid name was specified in the NAME field. A valid name must begin with an alphabetic character or with one of the following characters: $, # or @. All other characters must be alphabetic, numeric or one of the following: $, #, @, ., _ or %. Characters * and ? are valid only for mask representations.

Corrective Action: Correct the name specification.

IOAE44E INVALID DATELink copied to clipboard

Explanation: An invalid date was specified. The date must be a valid date in the format set by the DATETYP parameter in the IOAPARM installation member. Valid formats are ddmmyy, mmddyy, or yymmdd. In some date fields, four digits (no yy year) or eight digits with a 4-digit year (ddmmyyyy, mmddyyyy or yyyymmdd) are valid.

Corrective Action: Specify a valid date.

IOAE45E "FROM" VALUE CANNOT EXCEED "TO" VALUELink copied to clipboard

Explanation: User specified an invalid range in FROM and TO fields. The FROM value cannot exceed the TO value.

Corrective Action: Specify a valid range or a mask, if a mask is valid in the FROM field.

IOAE46E FILL IN THE REQUESTED FIELDLink copied to clipboard

Explanation: The cursor is positioned in a required field but the field was not filled in.

Corrective Action: Fill in the field.

IOAE47S INTERNAL ERROR IN SENDMSG ROUTINELink copied to clipboard

Explanation: The IOA Online Facility sent a message to the screen but the message cannot be displayed due to an internal program error.

Corrective Action: Call BMC Customer Support for assistance.

IOAE48E REDUNDANT "ON" STATEMENT AFTER AN EMPTY AND/OR/NOT OPTIONLink copied to clipboard

Explanation: An ON statement is not linked to the preceding ON statement by the AND/OR/NOT parameter. When more than one ON statement is specified, the relationship between them must be defined. The AND/OR/NOT field for an ON statement cannot be blank if another ON statement follows.

Valid AND/OR/NOT field values are:

  • A (AND)

  • O (OR)

  • N (NOT).

Corrective Action: Fill in a valid AND/OR/NOT parameter, or delete the unlinked ON statement.

IOAE4AE FIELD MUST BE ENTIRELY FILLED INLink copied to clipboard

Explanation: The field is not entirely filled in. The field specifies data that is valid only if all character positions are used. In some cases these fields may receive masked values.

Corrective Action: Fill in the field entirely.

IOAE4BE VALID OPTIONS ARE "A", "O", "N" AND " "Link copied to clipboard

Explanation: An invalid value was specified in the AND/OR/NOT field. AND/OR/NOT parameter links ON statements. The AND/OR/NOT field for an ON statement cannot be blank if another ON statement follows.

Valid values: A (AND), O (OR), N (NOT) and blank (no more ON statements).

Corrective Action: Specify a valid AND/OR/NOT field value.

IOAE4CE AT LEAST ONE "ON" STATEMENT MUST BE FILLED INLink copied to clipboard

Explanation: No ON statement was specified. At least one ON statement must be defined in the Rule Definition.

Corrective Action: Specify at least one ON statement.

IOAE4DE VALID OPTIONS ARE "A", "O" AND " "Link copied to clipboard

Explanation: An invalid value was specified in the AND/OR field.

Valid values for the AND/OR field are:

  • A (AND)

  • O (OR)

  • Blank (no connection with following statement).

Corrective Action: Specify a valid value in the AND/OR field.

IOAE4EE PLEASE FILL IN THE PREREQUISITE CONDITION NAMELink copied to clipboard

Explanation: A prerequisite condition name is missing in a DO COND statement.

At least one condition must be specified in a DO COND statement.

Corrective Action: Specify a prerequisite condition name.

IOAE4FE INVALID DATE REFERENCELink copied to clipboard

Explanation: An invalid date or date reference was specified in the date field. The date reference should be a valid date in the format determined by Installation Parameters: mmdd or ddmm. In some date reference fields, the following values are also valid: PREV, DATE, NEXT, ODAT, *** * or $$$$. For details, refer to the appropriate user guide.

Corrective Action: Specify a valid date reference.

IOAE4GE INTERNAL ERROR RC=XXXXXXXX, RS=XXXXXXXX, DG=XXXXXXXXLink copied to clipboard

Explanation: The common API for the condition file failed.

Execution stops.

Corrective Action: Contact your IOA administrator for assistance.

IOAE4IE Control-M IS NOT INSTALLED."CONDITION" MUST BE "Y"Link copied to clipboard

Explanation: Control-M is not installed and the CONDITION option has not been marked as Y.

Mark at the CONDITION option as Y.

Corrective Action: No action is required.

IOAE4LE MODE ADMIN NOT AVAILABLE FOR IOAVAR WITH ACTIVE CMEM/CONTROL-O MONITORLink copied to clipboard

Explanation: You attempted to open the IOAVAR database in ADMIN mode through the Variable Database Definition Facility (IV screen). However, the system is live, that is, the CMEM or Control-O monitor is active, and you cannot access the IV screen for IOAVAR.

Corrective Action: To manage variables in the IOAVAR database, use Control-M SET operations (SET VAR in the Job Scheduling Definition, %%SET in the JCL) or the IOAGLV utility.

IOAE50E MISSING/INVALID CONDITION OPTION. USE "+" (ADD) OR "-" (DELETE)Link copied to clipboard

Explanation: The condition option is invalid or missing. Use condition option + (plus) to add a condition to the IOA Conditions file, or - (minus) to delete a condition from the IOA Conditions file.

Corrective Action: Specify + (plus) or - (minus) in the condition option field.

IOAE51E INTERNAL ERROR. WINDOW IS OUTSIDE OF SCREENLink copied to clipboard

Explanation: The screen window requested by the IOA Online Facility cannot be displayed because of an internal program error.

Corrective Action: Re-enter the information. Notify BMC Customer Support if the error occurs again.

IOAE52E INVALID PARAMETERS FOR ZIP ROUTINELink copied to clipboard

Explanation: The screen window requested by the IOA Online Facility cannot be displayed because of an internal program error.

Corrective Action: Contact BMC Customer Support.

IOAE53E THERE IS NO DATA TO DISPLAYLink copied to clipboard

Explanation: The screen that is being prepared for display does not contain any data.

The screen which is being prepared is not displayed. The previous screen is displayed with the error message.

Corrective Action: Consider one or more of the following:

  • If no reports meet the selection criteria, this is an informational message.

  • If CTDTREE was recently changed (for example, if a new Recipient was added), make sure that CTDTREE was reloaded. For more information on loading the Recipient Tree, see the INCONTROL for z/OS Administrator Guide.

  • If the SHOW command is available, use it to check whether or not the SHOW settings are affecting the display. If the SHOW command is not available, change the selection or Show criteria, and then re-enter.

IOAE54E INVALID SHOUT DESTINATION CODELink copied to clipboard

Explanation: An invalid SHOUT destination code was specified.

Corrective Action: Correct the SHOUT destination field. For valid destinations, refer to the appropriate user guide.

IOAE55E INVALID URGENCY. USE "R" - REGULAR, "U" - URGENT OR "V" - VERY URGENT’Link copied to clipboard

Explanation: An invalid SHOUT urgency was specified. Valid SHOUT urgency values are R (Regular), U (Urgent), or V (Very urgent). For details, refer to the appropriate user guide.

Corrective Action: Specify R, U, or V in the SHOUT urgency field.

IOAE56E FIELD MUST BE FILLED INLink copied to clipboard

Explanation: The mandatory field in which the cursor is positioned was not filled in.

Corrective Action: Fill in the field.

IOAE57E ONLY CODE OPTION "- " ALLOWED FOR DATE REFERENCE $$$$/****Link copied to clipboard

Explanation: Code option + (plus) was specified for a generic date reference. The Add condition option + cannot be specified with generic date references ($$$$/****).

Corrective Action: Specify - (minus) as the code option, or use a different date reference.

IOAE58E PLEASE FILL IN THE "QUANTITATIVE" RESOURCE NAMELink copied to clipboard

Explanation: A quantitative resource quantity was specified without a corresponding quantitative resource name.

Corrective Action: Fill in the quantitative resource name.

IOAE59E STYLE IS RESERVED FOR SYSTEM PURPOSESLink copied to clipboard

Explanation: The specified style ID on a @STYLE line in the Display Type definition member is reserved by the IOA Online Facility for system purposes. See the INCONTROL for z/OS Installation Guide for more information.

Corrective Action: Specify another style ID.

IOAE5AE A DATE WHICH HAS PASSED CANNOT BE SPECIFIEDLink copied to clipboard

Explanation: A date that passed was specified in a DATE field. Only the current date or a future date can be specified in the DATE field.

Corrective Action: Specify the current date or a future date.

IOAE5BE PLEASE FILL IN A VALID AUTOEDIT STATEMENTLink copied to clipboard

Explanation: An invalid AutoEdit statement or expression was specified in the DO SET statement.

Corrective Action: Specify a valid AutoEdit statement. For an explanation of the AutoEdit Facility, see the appropriate user guide.

IOAE5CE INVALID ACTIONLink copied to clipboard

Explanation: An invalid action was specified in a DO statement.

Corrective Action: Correct the DO action field. For valid actions, refer to the appropriate user guide.

IOAE5DE INVALID SIGN. USE "<", ">", OR BLANKLink copied to clipboard

Explanation: An invalid character has been specified in the SHIFT field. Valid values are < (Shift back), > (Shift forward) or blank (do not shift).

Corrective Action: Specify a valid value.

IOAE5EI TOP OF DEFINITION LISTLink copied to clipboard

Explanation: This information message indicates that the current entry is the first entry in the entry list. This message can be displayed if a PREV command (PF10) is specified in a list screen when the first entry of the list is already displayed.

Corrective Action: No action is required.

IOAE5FI BOTTOM OF DEFINITION LISTLink copied to clipboard

Explanation: This information message indicates that the current entry is the last entry in the entry list. This message can be displayed if a NEXT command (PF11) is specified in a list screen when the last entry of the list is already displayed.

Corrective Action: No action is required.

IOAE60E LOGICAL ERROR ON CONTROL-M/TAPE MDBLink copied to clipboard

Explanation: A logical error was detected in the Control-M/Tape Media Database (MDB) when reading a record. Probable causes:

  • There is a data set record in the MDB, but the corresponding volume record does not exist.

  • One of the volumes of a multivolume data set is not found in the MDB.

Corrective Action: Notify your system administrator.

IOAE61E INVALID SIGN. USE "<" OR ">"Link copied to clipboard

Explanation: The user has specified an invalid sign preceding a numeric value.

Corrective Action: Specify the correct sign: < or >.

IOAE62E A NEW "ON" STATEMENT MUST BE FILLED IN AFTER AND/OR/NOT IS SPECIFIEDLink copied to clipboard

Explanation: An AND/OR/NOT parameter was used without a subsequent ON statement. The AND/OR/NOT parameter links a subsequent ON statement with the preceding ON statement. Every AND/OR/NOT value must be followed by an ON statement.

Corrective Action: Either delete the value in the AND/OR/NOT field, or enter the missing ON statement.

IOAE63E A RANGE IS INVALID WHEN A MASK IS USEDLink copied to clipboard

Explanation: A TO value cannot be specified if the FROM field contains a mask. A group is specified by a mask in the FROM field, or by filling in the TO field to specify a range. However, these methods cannot be combined.

Corrective Action: Clear the TO field, or do not specify a mask in the FROM field.

IOAE64E TOO MANY DIGITS SPECIFIED IN FIELDLink copied to clipboard

Explanation: Too many digits were specified in a field. When a numeric value is specified in this field, a limited number of digits or columns can be filled in. This may occur when the field receives different types of data, for example a date or a four digit number.

Corrective Action: Decrease the number of digits specified in the field.

IOAE66I ENTRY LOCATION CHANGED IN TABLE AFTER SORTLink copied to clipboard

Explanation: This information message indicates that changes in the definition screen or Entry List caused the entry to change location in the table after exit from the definition screen and return to the Entry List Panel. Automatic sort of the table is active. The sort criteria of an entry changed in the particular definition screen or in the Entry List.

The order of entries in the table is changed.

Corrective Action: No action is required.

IOAE67I AN UNSORTED TABLE WAS SORTED ON ENTRY TO LISTLink copied to clipboard

Explanation: This information message indicates that an unsorted table member was sorted on entry to list of entries in a table.

Automatic sort of the table is active. If the sort changed the order of entries in the table, this message is issued. This situation may occur when selecting tables that were created by conversion utilities, or if sort was previously inactive when modifying the table.

The order of entries in the table is changed.

Corrective Action: No action is required.

IOAE68E INVALID FORMAT OF CHANGE COMMANDLink copied to clipboard

Explanation: The CHANGE command was issued using an invalid format. Valid format of the CHANGE command is:

CHANGE string_in_definition replacement_string

Corrective Action: Reissue the command using the valid format.

IOAE69E PF9 RCHANGE IS VALID ONLY AFTER SUCCESSFUL CHANGELink copied to clipboard

Explanation: The RCHANGE could not be performed because the original CHANGE command was not successfully completed.

Corrective Action: Use the CHANGE command to substitute a string in an IOA definition with another string.

IOAE6AI FIELD CHANGED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CHANGE command was used to change the value of a certain string in an IOA definition to the value of another string.

Corrective Action: No action is required.

IOAE6BI NO FIELDS FOUND TO MATCH CHANGE STRINGLink copied to clipboard

Explanation: This information message indicates that the user issued a CHANGE command to change the value of a string in an IOA definition to another string’s value. However, no matching string was found in any of the fields of the definition.

The requested string substitution does not take place.

Corrective Action: No action is required.

IOAE6CE CHANGE OF FIELD WILL CAUSE AN ERRORLink copied to clipboard

Explanation: The change requested by means of the CHANGE command is not performed because it would cause an error in the IOA definition. Before performing the requested change, a validity check is performed to ensure that the field will not grow beyond its boundaries, and that its contents remain valid for the IOA definition.

The requested change is not performed.

Corrective Action: No action is required.

IOAE6FE CANNOT DISPLAY A MONTH OUTSIDE THE SPECIFIED RANGELink copied to clipboard

Explanation: The user requested the Online Scheduling Plan for a specific range of dates and then attempted to view the job scheduling dates for a month that is outside the defined date range.

Corrective Action: To view the scheduling plan for the requested month, exit the current display of the plan, define a new range, and reenter.

IOAE70E VALID SORT OPTIONS ARE "J"-JOB, "G"-GROUP OR "A-APPLICATION"Link copied to clipboard

Explanation: An invalid sort option or no sort option was requested when activating the SORT command from the scheduling job list.

Corrective Action: Specify one of the valid sort options shown in the message when activating the SORT command.

IOAE71E INVALID CODELink copied to clipboard

Explanation: An invalid return code, abend code or reference was entered in one of the IOA definition panels.

Corrective Action: Enter a valid code. For information on valid codes, see the appropriate product guide.

IOAE72E INVALID COMMAND NUMBERLink copied to clipboard

Explanation: A command was activated that was incorrectly defined in the Command member of the current screen. The number of a command defined in the Command member of the current screen must be positive, but less than 45.

The command is not executed.

Corrective Action: Correct the corresponding Command member in the IOA Parameter Library. See the section on defining new application types in the section on IOA installation considerations of the INCONTROL for z/OS Installation Guide.

IOAE73E OPERANDS "","","N" ARE INVALID FOR THIS TYPE OF CODELink copied to clipboard

Explanation: One of these operands, which are invalid for this type of code, was specified.

Corrective Action: Use only valid operands for this type of code.

IOAE74E SIGN OF QUANTITY MUST BE EITHER "+","-" OR BLANKLink copied to clipboard

Explanation: An invalid sign was specified for quantity change in the CHANGE window.

Valid quantity signs are:

  • - (minus) - Subtract the amount from the maximum available quantity.

  • + (plus) - Add the amount to the maximum available quantity

  • blank - Set a new quantity.

Corrective Action: Specify one of the above quantity signs.

IOAE75E COMMENT LINE CANNOT BE INSERTED HERELink copied to clipboard

Explanation: An attempt was made to open a comment line in an IOA definition. However a comment line cannot be inserted before the line on which the cursor is positioned.

Corrective Action: Try to open the comment on a different line.

IOAE76E OPTION INVALID FOR INSERTED RECORDLink copied to clipboard

Explanation: An invalid option or command was entered in an IOA list. The current list of valid options or commands appears at bottom of the screen.

Corrective Action: Enter a valid option.

IOAE77E TOO MANY PARMSLink copied to clipboard

Explanation: The specified command contained too many parameters.

The command is not issued.

Corrective Action: Delete parameters until the remaining ones are accepted.

IOAE78E INVALID cmd PARAMETER - parmLink copied to clipboard

Explanation: The parameter specified is not a valid parameter of the command.

The command is not issued.

Corrective Action: Either delete the parameter or replace it with a valid one.

IOAE79E REQUESTED FILTER filterName NOT FOUNDLink copied to clipboard

Explanation: Command SHOW filterName was entered to activate predefined selection criteria, but the filter specified was not in the user profile member or in the global profile member ($PROFILE).

The command is not issued.

Corrective Action: Edit and save this filter as a new filter using the EDIT keyword, or specify an existing filter with the command. If the fields of the specified filter match those of the DEFAULT filter, the filter is not saved in the user profile member.

IOAE7AE AT LEAST ONE OF THE FOLLOWING FIELDS MUST BE "Y"Link copied to clipboard

Explanation: All Y/N fields in a logical group of fields in the SHOW window are set to N. At least one must be set to Y; otherwise no lines will be displayed.

The selection criteria of the SHOW window are not activated.

Corrective Action: Set at least one field to Y.

IOAE7BE FILTER filterName IS A GLOBAL FILTER WHICH CANNOT BE SAVEDLink copied to clipboard

Explanation: A request to save a GLOBAL filter defined in the $PROFILE member failed because a GLOBAL filter cannot be saved by a user.

The filter is not saved.

Corrective Action: Specify a filter name that is not defined in the $PROFILE member.

IOAE7CE MISSING FILTER NAME TO BE SAVEDLink copied to clipboard

Explanation: The SAVE field on the SHOW WINDOW was set to Y, but no filter name was specified. SAVE can be performed only on a specific filter.

SAVE is not performed.

Corrective Action: Specify a filter name.

IOAE7DE FILTER filterName HAS BEEN CHANGED. ENTER Y/N OR "RESET" PFKEYLink copied to clipboard

Explanation: The currently edited filter in the SHOW window was changed, but the SAVE field was left empty.

Corrective Action: Suggested actions:

  • Enter Y in the SAVE field to save the changes and activate the new selection criteria.

  • Enter N in the SAVE field to activate the new selection criteria without saving them.

  • Press the RESET key (PF4 is the installation default) to restore the original values to what they were upon entering the SHOW command, and reactivate the original selection criteria.

IOAE7EE INSUFFICIENT MEMORY TO SAVE FILTER filterNameLink copied to clipboard

Explanation: A request to save changes made to a filter failed because there is not enough memory available. When filter fields are changed, the changed values are first saved in memory. Because the current region is used up, changes cannot be saved.

The changes are not saved.

Corrective Action: Exit the SHOW window without saving the changes by specifying N in the save field, or by pressing the RESET key (PF4 is the installation default). To enable saving a new filter, or changes to an existing filter, either exit some open online applications, or increase the value of the REGION parameter.

IOAE7FE COMMAND "x" CANNOT BE ISSUED FOR A SMART TABLELink copied to clipboard

Explanation: The x line command is supported for job entries, but not SMART tables.

The command is not executed.

Corrective Action: No action is required.

IOAE7GE VALID SORT OPTIONS ARE "R"-RULE, "T"-TYPELink copied to clipboard

Explanation: An invalid sort option or no sort option was requested when activating the SORT command from the rule definition list

Corrective Action: Specify either R or T when activating the SORT command.

IOAE7HI cpuSmfId DEFINITION defn IN lib(memName) funcLink copied to clipboard

Explanation: This information message indicates that the defn definition was:

  • Deleted from a member of an IOA definition library. The action may be recorded in the IOA Log file, depending on the TABUADT parameter in the IOAPARM member.

  • Changed into a member of an IOA definition library. The action may be recorded in the IOA Log file, depending on the TABUADT parameter in the IOAPARM member.

  • Created into member of an IOA definition library. The action may be recorded in the IOA Log file, depending on the TABUADT parameter in the IOAPARM member.

  • Copied from a member of an IOA definition library to another member. The action may be recorded in the IOA Log file, depending on the TABUADT parameter in the IOAPARM member.

In this message, cpuSmfId is the SMFID of the CPU on which the session is active.

Corrective Action: No action is required.

IOAE7KE ROUTCODE route_code OF parameter PARAMETER IS INVALIDLink copied to clipboard

Explanation: This message is issued when the error occurred during parsing the IOADEST member of the IOA PARM library. The ROUTCODE of parameter parameter is invalid. A valid value of ROUTCODE is a number between 1 and 15.

Corrective Action: Update the route_code with the correct value.

IOAE80S STATEMENT PARSING ERROR. RC= rc. EXECUTION WILL TERMINATELink copied to clipboard

Explanation:Highlighted, unrollable message.

An internal error occurred while building the online environment.

The online environment is not started.

Corrective Action: Try to reenter the online environment after logging out and reconnecting. If this is unsuccessful, contact BMC Customer Support with the information in the message.

IOAE81E OPERATION NOT GRANTEDLink copied to clipboard

Explanation: A user exit or security exit did not allow performance of the specified operation in the online environment.

The operation is not performed.

Corrective Action: Contact your IOA security administrator to get authorization to perform this operation.

IOAE83E JOB WILL NOT BE SCHEDULED DURING THIS PERIODLink copied to clipboard

Explanation: The selected job or SMART table is not scheduled to run within the specified time period. Option P on the Job List screen of the Job Schedule Definition facility (2.P) shows when the selected job or SMART table will run in the specified time period.

The system waits for a response from the operator.

Corrective Action: Press the PF3 key to continue.

IOAE84I ENTRY MODIFIEDLink copied to clipboard

Explanation: This information messages indicates that an entry in an IOA list has been modified.

Corrective Action: No action is required.

IOAE85E DUPLICATE RBC rbcNameLink copied to clipboard

Explanation: Two rule-based calendar entries with the same name were defined in the SMART Table Entity. Rule-based calendar names must be unique within a SMART Table Entity.

Corrective Action: Change one of the rule-based calendar names so that all the rule-based calendar names in the SMART Table Entity are unique.

IOAE86E PLEASE FILL IN AT LEAST ONE RBC ENTRYLink copied to clipboard

Explanation: An attempt to exit a SMART Table Entity definition for which no rule-based calendar name was defined failed. At least one rule-based calendar entry must be defined in a SMART Table Entity.

Corrective Action: Specify at least one rule-based calendar name in the SMART Table Entity.

IOAE88E INVALID HEXADECIMAL DIGITLink copied to clipboard

Explanation: When specifying the WHEN string (x‘######’) in hexadecimal format the user used an invalid digit. Valid hexadecimal digits are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F.

Corrective Action: Correct the WHEN string to contain valid digits only.

IOAE89E HEXADECIMAL STRING MUST CONTAIN AN EVEN NUMBER OF DIGITSLink copied to clipboard

Explanation: An odd number of hexadecimal digits was specified in the WHEN string, for example, x‘40A12’. The WHEN string must contain an even number of digits since each pair of digits represents one byte.

Corrective Action: Correct the WHEN string to contain an even number of valid digits.

IOAE8AW FILTER filterName WILL NOT BE SAVED - IDENTICAL TO "DEFAULT" FILTERLink copied to clipboard

Explanation: An attempt was made to save a filter that is identical to the default filter. A user filter can be saved only if its filtering criteria are different from the default filter criteria (filter DEFAULT).

Corrective Action: Change some of the criteria in the current filter, or use filter DEFAULT whenever these criteria are desired.

IOAE8BS IOATDRV RC=rc ID/TYP/CLS=id/type/class CALL=func PGM=pgmName #=numLink copied to clipboard

Explanation: The main screen formatting routine encountered an internal error or an environmental or access error.

For a screen formatting error, the ID, type, and class are specified as three characters in the message. The first character represents the ID, the second character represents the type, and the third character represents the class.

The screen is not displayed, or displayed incorrectly.

Corrective Action: Save the contents of the message. After several minutes, try to reenter the environment. If the problem persists, save the IOA log and the SYSLOG and contact BMC Support.

IOAE8CE CHARACTERS '*' AND '?' ARE INVALID IN RBC NAMELink copied to clipboard

Explanation: In a SMART Table Entity scheduling definition, an invalid character has been typed in the RBC field. The RBC field may contain any displayable characters except for '*' and '?'.

The SMART Table Entity scheduling definition cannot be saved.

Corrective Action: Remove invalid characters from the RBC field.

IOAE8DE THIS OPTION MUST BE THE LAST ENTEREDLink copied to clipboard

Explanation: An option that must be the last option entered in the screen was requested. No other option can be entered on any line after this line.

The request is ignored.

Corrective Action: Either delete the option that must be the last in the screen, or delete all options that follow it.

IOAE8EE THIS OPTION MUST STAND ALONELink copied to clipboard

Explanation: An option that cannot be combined with any other option was requested. No other option can be entered on any other line.

The request is ignored.

Corrective Action: Either delete the option that must be specified alone, or delete all other options.

IOAE8FE THIS COMMAND IS ONLY ALLOWED IN SCROLLABLE SCREENLink copied to clipboard

Explanation: An UP, DOWN, FIND, or LOCATE command was entered in a nonscrollable screen.

The requested command is not performed.

Corrective Action: No action is required.

IOAE8GE ILLEGAL FIRST CHARACTERLink copied to clipboard

Explanation: The first character is used for the exclude sign, therefore the RBC name cannot start with that character.

Corrective Action: Change the first character in the RBC name to a different character.

IOAE8LE FIRST CHARACTER CANNOT BE "x"Link copied to clipboard

Explanation: The first character is used for the exclude sign, therefore the RBC name cannot start with that character.

Corrective Action: Change the first character in the RBC name to a different character.

IOAE8ME INVALID COMPARISON OPERATOR Link copied to clipboard

Explanation: An invalid comparison operator was specified in the WHEN string.

Corrective Action: Correct the WHEN string to contain one of the following comparison operators: GT, LT, GE, LE, EQ, GL, or NE

IOAE8RE FIRST CHARACTER CANNOT BE "!"Link copied to clipboard

Explanation: Even when the Exclude RBC feature is turned off (EXCLURBC=N in CTMPARM), new RBCs cannot have a name starting with "!".

However, existing CTM-level RBCs with such names can be used, but will be processed according to the setting of EXCLURBC. If EXCLURBC=N, the CTM-level RBCs will be processed as regular (Include) RBCs. If EXCLURBC=Y, the CTM-level RBCs will be processed as reference to Exclude RBCs (without the “!” and will result with a message of missing RBC).

When editing a SMART table RBC section, an existing Table level RBC with a name starts with “!”, will be treated according to the value of EXCLURBC. With EXCLURBC=N, it will be treated as an include RBC, while with EXCLURBC=Y, it will be treated as an Exclude RBC.

Corrective Action:Change the name of the RBC so it starts with a character other than "!", and make sure that all jobs referring to this RBC are updated with the new name (and do not use “!” as the first character of the name).

IOAE90E THE DATE RANGE ALLOWED IS UP TO 3 YEARSLink copied to clipboard

Explanation: The date range in the scheduling plan of a job or group entity in calendar format exceeds 3 years.

The requested command or option is not performed.

Corrective Action: Correct the date range and press Enter.

IOAE91E CALENDAR CONTAINS A DUPLICATE YEAR. RESET WINDOW IN ORDER TO FIX ITLink copied to clipboard

Explanation: An attempt was made to define a calendar that duplicated an existing calendar.

The duplicate calendar is not saved.

Corrective Action: Enter N (No) in the Save window.

IOAE92E USER IS NOT AUTHORIZED TO USE OPTIONLink copied to clipboard

Explanation: The current attempt to run a job or enter a command is not authorized. This error message is issued when there is an attempt to perform an operation that is not allowed. For example, someone tried to use an IOA Online option without the necessary authority.

The operation terminates.

Corrective Action: Notify your INCONTROL administrator.

IOAE93E THE COMMAND ENTERED REQUIRES AN OPERANDLink copied to clipboard

Explanation: A command that requires an operand was entered without an operand.

The command is not performed.

Corrective Action: Reenter the command with the operand.

IOAE95E COMPLETE THE INSERT OPERATION BEFORE USING OTHER COMMANDSLink copied to clipboard

Explanation: A new line or record was inserted, but no other step was taken before another command was entered.

When a new line or record is inserted, no other command can be performed until either the new line or record is deleted, or data is entered in the new line or record.

Corrective Action: Either delete the newly inserted line or record, or type some data into the newly inserted line or record and press Enter.

IOAEA0E GETMAIN FAILEDLink copied to clipboard

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter, or exit one of the screens.

IOAEA1E TOKEN CREATE/RETRIEVE FAILEDLink copied to clipboard

Explanation: An error occurred during the initialization of an INCONTROL product. The CREATE or RETRIEVE service failed, and the related IBM Module (IEANTCR or IEANTRT) ended with a nonzero return code.

Corrective Action: Refer to the relevant IBM publication.

IOAEA2E TOKEN MUST EXIST FOR SERV/TERM FUNCTIONLink copied to clipboard

Explanation: An internal error occurred during the initialization of an INCONTROL product.

Corrective Action: Contact BMC Customer Support.

IOAEA3E IOALDPRM FOR PARAMETER MEMBER parm FAILED[: MODULE modName NOT FOUND]Link copied to clipboard

Explanation: During IOA environment initialization, processing of the parm source parameter failed. Sometimes the optional part of the message is displayed, indicating that the modName module was needed to process the parm parameter, but the module was not found in a load library.

This message is usually preceded by a message detailing either a READ error or a syntax error.

The program stops.

Corrective Action: Check and correct the parm member in the IOA PARM library. BMC recommends that you use the ICE Customization option to correct this member.

IOAEA4E INIT FOR SERVICE serv FAILEDLink copied to clipboard

Explanation: During IOA environment initialization, the initialization of the module that provides the serv service failed.

Valid values for serv are:

  • IOALOGR - read or write to the IOA LOG file

  • MESSAGES - message retrieval

  • WISHES - optional wishes retrieval

  • TRACE - IOA trace facility

  • IOALLOC - IOA dynamic allocation facility

This message is usually preceded by a message issued by the service module, which usually describes the problem.

The probable source of the problem is either the IOADSN or the allocation members in the libraries referenced by DD name DAPARM.

The program stops.

Corrective Action: Attempt to solve the problem described in the service module message.

IOAEA5E UNABLE TO OBTAIN ENQ FOR IOAENVLink copied to clipboard

Explanation: An internal error occurred during the initialization of an INCONTROL product.

Initialization stops.

Corrective Action: Contact BMC Customer Support.

IOAEA6E JES NOT RECOGNIZEDLink copied to clipboard

Explanation: No value was set for the JESTYPE parameter, and the IOAENV module could not identify the type of JES in use.

The program stops.

Corrective Action: Check and correct the JESTYPE parameter in the IOAPARM member in the IOA PARM library.

IOAEA7E INVALID FUNCTION PASSEDLink copied to clipboard

Explanation: An internal error occurred during the initialization of an INCONTROL product.

Initialization stops.

Corrective Action: Contact BMC Customer Support.

IOAEA8E SUBPOOL NOT EQUAL TO THE MCT SUBPOOLLink copied to clipboard

Explanation: An internal error occurred during the initialization of an INCONTROL product.

Initialization stops.

Corrective Action: Contact BMC Customer Support.

IOAEA9E DAPARM DD STATEMENT MISSING. PROCESS ENDEDLink copied to clipboard

Explanation: The initialization of the desired environment could not be completed because the DAPARM DD statement was not found.

The session ends.

Corrective Action: Add the DAPARM DD statement to the relevant JCL.

IOAEAAE CALL TO IOALOC FAILEDLink copied to clipboard

Explanation: An internal error occurred during the initialization of an INCONTROL product.

Initialization stops.

Corrective Action: Contact BMC Customer Support.

IOEEABE LOAD/LINK FOR MODULE modName FAILEDLink copied to clipboard

Explanation: The IOAENV module could not load the modName module.

Initialization stops.

Corrective Action: Contact BMC Customer Support.

IOAEB1E ROUTINE rtn-name FAILED. RC=rc REASON=rsnLink copied to clipboard

Explanation: The IOA/Control-M routine, rtn-name, failed with a return code of rc and a reason code of rsn.

When the rtn-name is CTMBAPI and the rc=8, refer to the explanation in message IOA723I for a complete list of all the reason codes and their meaning.

When the rtn-name is CTMBAPI and rc=4, and rsn=0 the meaning is that an internal request to the Control-M application interface program (CTMAPI) to Search for a specific job in the AJF failed because the job was not present in the AJF.

Corrective Action: Take action based on the rc and rsn. Contact BMC Customer Support if you are unable to determine an appropriate course of action.

Messages IOAF00 through IOAFxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAF00I UTILITY IOADBF STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOADBF utility has started. The IOADBF utility allocates and formats an IOA Access Method file component primary or secondary extent.

Corrective Action: No action is required.

IOAF01I FORMATTING ENDED WITH RETURN CODE rcLink copied to clipboard

Explanation: This information message indicates that the IOADBF utility ended with a return code of rc.

Possible values of rc are listed in message CTD908S.

The IOADBF utility terminates.

Corrective Action: If rc is not zero, check the IOA Log file and the system log for additional messages that describe the error. Correct the problem before rerunning the IOADBF utility.

IOAF01S INSUFFICIENT STORAGE FOR TRANSFER SUBTASKLink copied to clipboard

Explanation: Insufficient storage to initialize the File Transfer task.

The file transfer task is not started.

Corrective Action: Increase the REGION size in the File Transfer monitor procedure. Stop and restart the File Transfer monitor.

IOAF02E SPECIFIED NUMBER OF RECORDS IS NOT CORRECT. UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation: This message is issued in two cases:

  • The IOADBF utility was unable to allocate an IOA Access Method file component. The number of blocks specified in the SPACE parameter of the IOA Access Method file Definition statements member is invalid.

  • The IOADBF utility EXTEND function was unable to allocate an IOA Access Method file component. The number of secondary blocks is not specified in the SPACE parameter of the IOA Access Method file Definition statements member.

The SPACE parameter specifies the number of primary and secondary blocks to be allocated. Primary and secondary SPACE parameter values must be a number from 2 through 65535. Database file definition statements are usually located in a member of the IOA INSTWORK library.

The IOADBF utility terminates.

Corrective Action: Do the following:

  1. Modify the DEFxxx member to allocate secondary blocks.

  2. Allocate IOA Access Method file components by running the IOADBF utility twice, as follows:

    • the first time, with the FUNC parameter set to CHANGE

    • the second time, with the FUNC parameter set to EXTEND

For more information on the IOADBF utility, see the INCONTROL for z/OS Utilities Guide.

IOAF02S ERROR IN DYNALLOC FUNCTION: func rsn RC=rcLink copied to clipboard

Explanation: The File Transfer monitor could not dynamically allocate a file to be transferred. The function that failed, ALLOC, DEALLOC, or CONCATENATE, the reason code, and the return code from SVC 99 are displayed in the message.

The File Monitor continues processing other files.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for an explanation of the reason code and return code in the message.

IOAF03I FILES ARE NOT TRANSMITTED. USER usr IPA=ipAddLink copied to clipboard

Explanation: This information message indicates that one or more files listed in the Active Transfer file cannot be transmitted to the specified IP address.

The task continues processing other files. The status of the entry in the Active Transfer file is set to WAIT TRANSMIT.

Corrective Action: Check if the server with the specified IP address is active.

IOAF03S INDEX FILE BLKSIZE AND LRECL MUST BE EQUAL. UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation: The BLKSIZE and LRECL parameters specified in the IOA Access Method file Definition statements member for an IOA Access Method file index component are not equal. The logical record length and block size of IOA Database file index components must be equal. Database file Definition statements are usually located in a member of the IOA INSTWORK library.

The IOADBF utility terminates.

Corrective Action: Delete the LRECL parameter to set the logical record length to the value of the BLKSIZE parameter, and rerun the IOADBF utility.

IOAF04S UTILITY IOADBF UNABLE TO OPEN FILE. REFORMAT FAILEDLink copied to clipboard

Explanation: The IOADBF utility could not open an IOA Access Method (IAM) file component for reformatting. During reformatting of an IAM file index or data component, the IOADBF utility failed to open and read the file control record from the first extent.

The IOADBF utility terminates.

Corrective Action: Check the IOA Log file and system log for additional messages that describe the error. Correct the problem before rerunning the IOADBF utility.

IOAF05S ERROR IN OPENING SYSPRINT FILE. UTILITY IOADBF UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation:This is one of two messages with the same ID, but different text.

The IOADBF utility could not open the SYSOUT file or the data set referenced by the SYSPRINT DD statement. The IOADBF utility encountered an error while opening the file referenced by the SYSPRINT DD statement. This file is used to write message output during utility execution.

The IOADBF utility terminates.

Corrective Action: Check the IOA Log file and system log for additional messages that describe the error. Correct the problem before rerunning the IOADBF utility.

IOAF05S textLink copied to clipboard

Explanation:This is one of two messages with the same ID, but different text.

An error occurred during transmission of a file to the PC. The message text describes the reason for the problem.

The file is not transmitted.

Corrective Action: Correct the problem, and restart the File Transfer monitor.

IOAF06I FILES ARE TRANSMITTED OK FOR USER userName IPA=ipAddPort FILE=fileName.CDMLink copied to clipboard

Explanation: This information message indicates that the specified files were successfully transmitted to the PC. The message specifies

  • userName - the user name

  • ipAddPort - the IP address and port

  • fileName - the file name

Corrective Action: No action is required.

IOAF06S INSUFFICIENT STORAGE FOR RUNNING UTILITY IOADBFLink copied to clipboard

Explanation: The IOADBF utility could not obtain the memory required for execution. The IOADBF utility received a non-zero return code from macro GETMAIN.

The IOADBF utility terminates.

Corrective Action: Take the following steps:

  1. Check the IOA Log file and system log for additional messages that describe the error

  2. Correct the problem, or increase the REGION size

  3. Rerun the IOADBF utility

IOAF07E INCONSISTENT PARAMETERS. UTILITY IOADBF UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation: The IOADBF utility detected inconsistent parameters for formatting an IOA Access Method file in the member that contains the IOA Access Method definition statements. The parameters that were passed to the IOADBF utility were not of the type required for formatting the file.

The IOADBF utility terminates.

Corrective Action: Take the following steps:

  1. In the case of Control-M/Tape, verify that

    • DUAL was set to N

    • EXTEND was set to M

    • TYPE was not set to V

    • the SPACE parameter for this index file had no secondary allocation

  2. In the case of Control-M/Analyzer, verify that

    • EXTEND was set to M, or was not set

    • TYPE was not set to V

    • BUFL was set to 0

    • the SPACE parameter had no secondary allocation

  3. Correct the member that contains the IOA Access Method definition statements.

  4. Rerun the utility.

IOAF08S KEYLEN IS NOT DEFINED FOR INDEX FILELink copied to clipboard

Explanation: The KEYLEN mandatory parameter was not specified in the IOA Access Method (IAM) file definition statements member for the IAM file index component being processed. The KEYLEN parameter is mandatory when allocating and formatting an IAM file index component. IAM file definition statements are usually located in a member of the IOA INSTWORK library.

The IOADBF utility terminates.

Corrective Action: Set the value of the KEYLEN parameter to the value required for the IAM file index component being processed. Rerun the utility.

IOAF09S REMOVE LRECL FROM THE INDEX FILE DEFINITION STATEMENTS MEMBERLink copied to clipboard

Explanation: The LRECL parameter is specified in the IOA Access Method (IAM) file definition statements member for the IAM file index component being processed. The internal structure of the Database file index component being processed requires that each block consist of one record. Therefore, the LRECL parameter is not applicable and may not be specified. IAM file definition statements are usually located in a member of the IOA INSTWORK library.

The IOADBF utility terminates.

Corrective Action: Remove the LRECL parameter from the member. Rerun the program.

IOAF0AI FILE TRANSFER STARTED. FOR USER userId IPA=ipAdd:port FILE=fileName.CDMLink copied to clipboard

Explanation: This information message is issued when the File Transfer monitor starts to transfer a package to the identified IP address.

The variables in this message are:

  • userId - the identity of the user to whom the report belongs

  • ipAdd - the IP address

  • port - the port number

  • fileName - the name of the file being transferred

Corrective Action: No action is required.

IOAF0CI UNRECOVERABLE ERROR ENCOUNTERED.Link copied to clipboard

Explanation: During the operation of the File Transfer monitor, an unrecoverable error occurred when access was attempted to the Active Transfer file.

The File Transfer monitor shuts down.

Corrective Action: Contact your INCONTROL administrator.

IOAF0DS SECURITY VIOLATION IN THE FILE TRANSFER MONITOR.Link copied to clipboard

Explanation: A serious error occurred while the File Transfer monitor was working. The transfer of the package was rejected by a security exit, or by User Exit 23.

Every transfer request is sent to both the security exit and the user exit, if they exist. Either exit can reject a transfer request.

The package is not transferred.

Corrective Action: If you consider that you ought to have authority to transfer the package, contact your INCONTROL administrator.

IOAF0EW ATF IS REFRESHED. SUBTASK IPA=IPaddress IS CLOSED.Link copied to clipboard

Explanation: This warning message is issued when the transfer process fails because the status of the corresponding record in the ATF can not be updated. It can occur if a package, whose time has come for transfer, can not find the corresponding record in the ATF because it was reformatted and refreshed during the NEWDAY process.

CTDFTM continues to work and the subtask with the specified IPaddress is closed.

Corrective Action: If the package remains at the status NOT TRANSMITTED, reorder the package.

IOAF10S REMOVE KEYLEN FROM THE DATA FILE DEFINITION STATEMENTS MEMBERLink copied to clipboard

Explanation: The KEYLEN parameter should not be specified in the IOA Access Method (IAM) file definition statements member for IAM file data components. Key fields are only applicable to IAM file index components. The KEYLEN parameter should not be specified for an IAM file data component. IAM file definition statements are usually located in a member of the IOA INSTWORK library.

The IOADBF utility terminates.

Corrective Action: Remove the KEYLEN parameter from the member. Rerun the program.

IOAF11S SET VALUE FOR PARAMETER TYPE TO I, F OR VLink copied to clipboard

Explanation: The value specified for the TYPE parameter in the IOA Access Method (IAM) file definition statements member is invalid. Database file definition statements are usually located in a member of the IOA INSTWORK library.

Possible TYPE parameter values are:

  • I - IAM file index components

  • F - IAM file data components containing fixed length records

  • V - IAM file data components containing variable length records

The IOADBF utility terminates.

Corrective Action: Specify a valid TYPE parameter in the member. Rerun the program.

IOAF12S QUANTUM IS NOT CORRECT IN THE DEFINITION STATEMENTS MEMBERLink copied to clipboard

Explanation: The value specified for the QUANT1, QUANT2, or QUANT3 parameter in the IOA Access Method (IAM) file definition statements member for the IAM file component being processed is invalid. The QUANT1, QUANT2 and QUANT3 parameters are used with variable record length IAM file components for managing free space areas when new records are written. These parameters must correlate with the BLKSIZE parameter as follows:

QUANT1 < QUANT2 < QUANT3 < BLKSIZE

IAM file definition statements are usually located in a member of the IOA INSTWORK library.

The IOADBF utility terminates.

Corrective Action: The QUANT1, QUANT2, and QUANT3 parameters are for internal use only. Do not modify them without prior consent of BMC Customer Support. When appropriate values are approved, specify valid QUANT1, QUANT2, and QUANT3 parameters in the member, and rerun the utility.

IOAF13S BLKSIZE VALUE IS TOO SMALLLink copied to clipboard

Explanation: The block size specified in the IOA Access Method (IAM) file definition statements member is less than the length of the control record of the IAM file component being processed. The BLKSIZE parameter of the IAM file definition statements member for the IAM file component being processed must not be less than the length of the control record of the component. IAM file definition statements are usually located in a member of the IOA INSTWORK library.

The IOADBF utility terminates.

Corrective Action: For IAM file components containing variable length records, change the relevant definition statements member to increase the BLKSIZE value or reduce the number of blocks specified in the SPACE parameter. For IAM file components containing fixed length records, the BLKSIZE parameter should be more than 255.

IOAF14S ERROR IN DYNALLOC OF DATABASE FILE RC=rcLink copied to clipboard

Explanation: An attempt to dynamically allocate or deallocate an IOA Access Method (IAM) file component failed. IAM Database processing routines received a non-zero return code from an allocation or deallocation request using SVC 99. The data set name of the IAM file component is specified in message IOAF20S.

The IOADBF utility terminates.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the return code and reason code received. If the problem remains unresolved, contact BMC Customer Support.

IOAF15S ERROR IN OPENING DATABASE FILELink copied to clipboard

Explanation: During processing of an IOA Access Method (IAM) file index or data component, the IOADBF utility could not open and read the file control record from the first extent.

The IOADBF utility terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF16S ERROR IN READING CONTROL RECORDLink copied to clipboard

Explanation: The IOADBF utility could not read an IOA Access Method (IAM) file component header record. During processing of an IAM file index or data component, an attempt to read the file control record from the first extent failed.

The IOADBF utility terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF17S ERROR IN UPDATE OF DB0 (CONTROL RECORD)Link copied to clipboard

Explanation: The IOADBF utility could not update an IOA Access Method (IAM) file component control record. During processing of an IAM file index or data component, an attempt to update the file control record in the first extent failed.

The IOADBF utility terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF18S ERROR IN CLOSING DATABASE FILELink copied to clipboard

Explanation: The IOADBF utility could not close an IOA Access Method (IAM) file index or data component.

The IOADBF utility terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF19S parm PARAMETER IS NOT CORRECTLink copied to clipboard

Explanation: An invalid parameter was passed to the IOADBF utility. A parameter specified in the IOA Access Method (IAM) file definition statements member or the FUNC parameter specified in the JCL procedure is invalid.

The IOADBF utility terminates.

Corrective Action: Set the parameter in error to a valid value. Rerun the program.

IOAF20S DATASET NAME: dsnLink copied to clipboard

Explanation: A dynamic allocation or deallocation error occurred when processing data set dsn. This message indicates the name of the IOA Access Method (IAM) file component that could not be allocated or deallocated. The preceding IOAF14S message indicates the return code received from the allocation or deallocation request using SVC 99.

The IOADBF utility terminates.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the return code and reason code received. If the problem remains unresolved, contact BMC Customer Support.

IOAF21S SPECIFIED FILE NAME IS TOO LONGLink copied to clipboard

Explanation: The length of the name of the IOA Access Method (IAM) file component being processed exceeds the 44-character maximum for data set names. The IAM file component data set name includes the value assigned to the DSN parameter in the IAM file definition member, plus the data set extent number suffix appended automatically by IOA. IAM file definition statements are usually located in a member of the IOA INSTWORK library.

The program terminates.

Corrective Action: Set the DSN parameter to a value defined by 39 characters or less, and rerun the program.

IOAF22S OPENING OF PARAMETER LIST FAILEDLink copied to clipboard

Explanation: During processing of an IAM file index or data component, an attempt to open and read the IAM file definition statements member failed. IAM file definition statements are usually located in a member of the IOA INSTWORK library.

The program terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF23S REQUESTED OPERATION IS RESTRICTED BY EXIT ROUTINELink copied to clipboard

Explanation: Access was denied by IOA Access Method (IAM) allocation and formatting exit routine IOAX036. An attempt to allocate, format or extend an IAM file component was denied, because exit routine IOAX036 returned a non-zero return code.

The program terminates.

Corrective Action: If the executing program should have been granted access to process the IAM file, contact your system or security administrator for assistance.

IOAF24I INPUT PARAMETERS FOR THE FORMATLink copied to clipboard

Explanation: This information message is the header for IOA Access Method (IAM) file definition statement parameter settings that follow.

Processing continues. IAM file definition statement parameter settings are displayed in message IOAF25I.

Corrective Action: No action is required.

IOAF25I parmLink copied to clipboard

Explanation: This information message displays the setting of an IOA Access Method (IAM) file definition statement parameter.

Corrective Action: No action is required.

IOAF26S INTERNAL ERROR. FILE FORMATTING FAILEDLink copied to clipboard

Explanation: An internal error occurred while attempting to format an IOA Access Method (IAM) file component. Formatting of an IAM file component could not be completed because an internal error was encountered by an IAM service routine.

The program terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF27S NUMBER OF RECORDS IN BLOCK IS MORE THAN 256.Link copied to clipboard

Explanation: During formatting of an IOA Access Method Data File type F, the IOADBF utility issues this message when the number of records per block in the IOA Access Method Data File type F exceeds 256.

The IOADBF utility terminates.

Corrective Action: Correct the LRECL and BLKSIZE parameters in the corresponding member in the installation library to provide no more than 256 records per block in IOA Access Method Data File type F. Rerun the IOADBF utility.

IOAF2CS IOADBE: INVALID FUNCTIONLink copied to clipboard

Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.

I/O request fails.

Corrective Action: Notify your INCONTROL administrator.

IOAF2DS IOADBE: INVALID BLKSIZE SUPPLIEDLink copied to clipboard

Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.

I/O request fails.

Corrective Action: Notify your INCONTROL administrator.

IOAF2ES IOADBE: INVALID BUFFER ADDRESS SUPPLIEDLink copied to clipboard

Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.

I/O request fails.

Corrective Action: Notify your INCONTROL administrator.

IOAF2FS IOADBE: TRKCALC FAILED. RC=rcLink copied to clipboard

Explanation: Function TRKCALC returned a non-zero return code.

The I/O operation fails. Further action depends on the current IOA function.

Corrective Action: Contact BMC Customer Support.

IOAF30S IOADBE: TTR OUTSIDE FILE EXTENTS - rbaLink copied to clipboard

Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.

I/O request fails.

Corrective Action: Notify your INCONTROL administrator.

IOAF31S IOADBE: I/O ERROR. CC: cc STAT: status SENSE: sense RESIDUAL COUNT: countLink copied to clipboard

Explanation: An I/O error occurred while trying to access an IOA Access Method file. This message can be the result of a software or hardware error.

The I/O operation fails. Further action depends on the current IOA function.

Corrective Action: Check if there are any hardware problems with the disk on which the IOA Access Method file resides. If the problem seems to be a software problem, contact BMC Customer Support.

IOAF40I DATABASE PRINT UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOADPT utility started. The IOADPT utility prints IOA Access Method (IAM) file component records in dump format.

Corrective Action: No action is required.

IOAF41I DATABASE PRINT UTILITY ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOADPT utility ended.

Corrective Action: If the IOADPT utility ended with a non-zero return code, check the system log for additional messages that describe the error. Correct the problem before rerunning the IOADPT utility. If the problem remains unresolved, contact BMC Customer Support.

IOAF42S INVALID INPUT STATEMENT stmtLink copied to clipboard

Explanation: An invalid parameter or sequence of parameters was passed to an IOA Access Method (IAM) print the IOADPT utility.

The IOADPT utility terminates.

Corrective Action: Correct the parameter or parameter sequence. Rerun the utility.

IOAF43S ERROR IN SYSPRINT OPENINGLink copied to clipboard

Explanation: The IOADPT utility could not open the SYSOUT file or the data set referenced by the SYSPRINT DD statement, which writes message output during program execution.

The IOADPT utility terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF44S OPERATION opn FAILED DUE TO INTERNAL ERROR IN IOADBS. RC=rcLink copied to clipboard

Explanation: An IAM service routine encountered an internal error while attempting to access an IOA Access Method (IAM) file component.

The utility terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the utility. If the problem remains unresolved, contact BMC Customer Support.

IOAF45S OPERATION opn FAILED DUE TO INTERNAL ERROR IN IOADBI. RC=rcLink copied to clipboard

Explanation: An IAM service routine encountered an internal error while attempting to access an IOA Access Method (IAM) file index component.

The utility terminates.

Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the utility. If the problem remains unresolved, contact BMC Customer Support.

IOAF46E INVALID PARAMETER "FUNC"Link copied to clipboard

Explanation: The FUNC parameter specified in the JCL procedure of the IOADPT utility is invalid.

Valid FUNC values are:

  • 1 - Print IAM file index and data component records.

  • 0 - Print IAM file index component records only.

  • DB0 - Print IAM file data control record.

The IOADPT utility terminates.

Corrective Action: Set the FUNC parameter to a valid value, and rerun the utility.

IOAF47S PARAMETER ERROR. PARAMETERS ARE NOT SPECIFIEDLink copied to clipboard

Explanation: An empty parameter string was passed to the IOADPT program.

The IOADPT program terminates.

Corrective Action: Specify needed parameters, and rerun the program. Refer to the INCONTROL for z/OS Utilities Guide for more information.

IOAF48I NUMBER OF PROCESSED RECORDS WAS numberLink copied to clipboard

Explanation: This information message indicates the number of records printed by the IOADPT program.

The IOADPT program terminates.

Corrective Action: No action is required.

IOAF49W NO RECORDS WERE FOUND IN THE REQUESTED RANGELink copied to clipboard

Explanation: No record was found in the key range that the customer used.

The IOADPT program continues.

Corrective Action: Validate that the key range (set by parameters KEYFROM and KEYTO in job IOALOGXD in the IOA JCL library) are correct. If not, change them and resubmit the job.

IOAF70I database err descr - line 1Link copied to clipboard

Explanation: Processing of an IOA Access Method (IAM) file component cannot be completed because an internal error was encountered by an IAM service routine. Messages IOAF70I and IOAF71I display information describing the internal error that occurred while attempting to process an IAM file component.

The program terminates. Additional diagnostic messages may precede or follow this message.

Corrective Action: Check the IOA Log or the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF71I database err descr - line 2Link copied to clipboard

Explanation: Processing of an IOA Access Method (IAM) file component cannot be completed because an internal error was encountered by an IAM service routine. Messages IOAF70I and IOAF71I display information describing the internal error that occurred while attempting to process an IAM file Component.

The program terminates. Additional diagnostic messages may precede or follow this message.

Corrective Action: Check the IOA Log or the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

IOAF72W WARNING: PROBLEMS WITH DUAL DATABASE - USING MAIN DB ONLYLink copied to clipboard

Explanation: Mirror database file is not identical to the main database file. If the database files have mirror files, during each database access request, IOA Access Method programs check that the main and mirror files are identical. If they are not, this message is issued, and only the main database file is used.

IOA Access Method uses only the main file.

Corrective Action: Reformat the mirror database file, and copy the main database file into it, using the IOADCPY utility.

IOAF74E NO MEMORY FOR ERROR MESSAGE ROUTINE HANDLE - ERROR MESSAGE IS NOT PRODUCEDLink copied to clipboard

Explanation: An attempt to obtain storage for message edit processing failed because not enough memory was available to edit and issue an error message from the IOA Access Method.

Processing continues if the unissued message was for a noncritical event.

Corrective Action: Increase the REGION size. If the problem remains unresolved, contact BMC Customer Support.

IOAF80I XCF COMMUNICATION IS ACTIVE, GROUP=grp, MEMBER=memLink copied to clipboard

Explanation: This information message indicates that XCF communication is supported under this implementation of Control-O. Control-O is joined to the grp XCF group as member mem.

Corrective Action: No action is required.

IOAF82S IOAXCF ACTION xcf_cmd FAILED. RC=rc, RSN=rsnLink copied to clipboard

Explanation: An error was detected while issuing XCF command xcf_cmd. The return code is rc. The reason code is rsn.

Possible values of xcf_cmd and the XCF macro indicated by each:

  • QUERY - IXCQUERY macro

  • JOIN - IXCJOIN macro

  • SEND - IXCMSGO macro

  • LEAVE - IXCLEAVE macro

Return code rc and reason code rsn are documented separately for each XCF macro in the IBM manual MVS Programming: Authorized Assembler Services Guide.

Corrective Action: Fix the problem according to the specific xcf_cmd/XCF MACRO.

IOAF83I IOAXCF-GUI MODULE NOT ACTIVATEDLink copied to clipboard

Explanation: This information message indicates that Control-O did not initialize the XCF Group User Interface module under the current installation.

Corrective Action: No action is required.

IOAF84E STORAGE ALLOCATION FOR COMMUNICATION FAILED, MODULE modName RC=rcLink copied to clipboard

Explanation: During initialization of the modName communication module, storage allocation for the Control-O communication facility failed because the communication component could not obtain sufficient working storage for processing. The return code rc is obtained from register R15 of the STORAGE OBTAIN macro.

XCF communication is not activated. Processing continues.

Corrective Action: Check current memory usage for unknown problems. Based on the return code, fix the problem and restart Control-O to activate XCF support.

IOAF85I IOAXCF-SUI MODULE NOT ACTIVATEDLink copied to clipboard

Explanation: This information message indicates that the XCF Statistic User Interface module was not activated. During its initialization, Control-O did not initialize the Statistic User Interface.

Corrective Action: No action is required.

IOAF86E IOAXCF CANNOT INITIALIZE WITHOUT MUI MODULE-modNameLink copied to clipboard

Explanation: Control-O attempted to initialize the XCF Message User Interface (MUI) module and failed. In this message, modName is the name of the Message User Interface module that Control-O attempted to initialize.

XCF support is not activated.

Corrective Action: Verify that the modName MUI module is in the STEPLIB. Restart the last XCF operation. If the problem persists, contact BMC Customer Support.

IOAF87I XCF COMMUNICATION IS DOWN, GROUP=grp, MEMBER=memNameLink copied to clipboard

Explanation: This information message indicates that Control-O communication by means of XCF is down. The memName Control-O XCF member from the grp group is down.

Corrective Action: No action is required.

IOAF88S IOAXCF INTERNAL ERROR OCCURRED.RC=g_rc,RET=s_rc, RSN=rsnLink copied to clipboard

Explanation: During XCF processing, Control-O detected an internal error. The IOAXCF module failed with general return code g_rc, specific return code s_rc, and reason code rsn.

Corrective Action: Restart the last XCF operation. If the problem persists, contact BMC Customer Support.

IOAF91E ERROR DURING PROCESSINGLink copied to clipboard

Explanation: The IOA housekeeping routine found an unexpected error during one of its cycles.

The Control-O or CMEM monitor terminates. Other monitors may behave differently.

Corrective Action: Use earlier messages to determine the cause of the failure.

IOAF95S ERROR WHILE PROCESSING REQUESTSLink copied to clipboard

Explanation: The XES housekeeping routine found an error while it was either processing a request that was queued by an XES exit, or while it was checking an XES control block. The XES housekeeping routine processes requests that are queued by asynchronous execution of XES SRB exits.

The Control-O or CMEM monitor terminates. Other monitors may behave differently.

Corrective Action: Send the sysout files for your monitor to BMC Customer Support.

IOAF96S INTERNAL ERRORLink copied to clipboard

Explanation: An internal error occurred during internal chaining. An internal chaining mechanism queues requests as they pass from one component to another, for example, from SRB exits from XES to the housekeeping task. This mechanism detected an internal error that may result from a programming error.

The Control-O or CMEM monitor terminates. Other monitors may behave differently.

Corrective Action: Send the SVCDUMP of the address space issuing the message and the sysout files for your monitor to BMC Customer Support for analysis.

IOAFA0I XES HOUSEKEEPING TASK STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-O or CMEM started initialization of the subtask that performs XES housekeeping.

Corrective Action: No action is required.

IOAFA1E XES HOUSEKEEPING ERROR DURING PROCESSINGLink copied to clipboard

Explanation: The subtask of Control-O or CMEM that performs XES housekeeping found an unexpected error during one of its cycles.

Both the subtask and Control-O or CMEM terminate.

Corrective Action: Use earlier messages to determine the cause of the failure.

IOAFA2I XES HOUSEKEEPING TASK ENDEDLink copied to clipboard

Explanation: This information message indicates that Control-O or CMEM finished initializing the subtask that performs XES housekeeping.

Corrective Action: No action is required.

IOAFB1I IOACMI STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOA initialization routine started initializing XES activities, and is currently in control.

Corrective Action: No action is required.

IOAFB2I IOACMI ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOA initialization routine stopped initializing XES activities. It does not indicate whether or not all activities were completed successfully.

The routine that initializes XES activities passes control back to the caller.

Corrective Action: No action is required.

IOAFB3S IOACMI RECEIVED AN INVALID PARAMETER LISTLink copied to clipboard

Explanation: The IOA initialization routine for XES activities received an invalid list of parameters from the caller.

The Control-O or CMEM monitor terminates. Other monitors may behave differently.

Corrective Action: Send the sysout files for your monitor to BMC Customer Support for analysis.

IOAFB4E IOACMI - NOT ENOUGH STORAGELink copied to clipboard

Explanation: The IOA initialization routine for XES failed to get enough storage space. The routine could not GETMAIN one of the chunks of storage needed to process the XES request.

The Control-O or CMEM monitor terminates. Other monitors may behave differently.

Corrective Action: Review calculations of storage requirements for Control-O or CMEM (private, E/CSA). If you cannot find the problem, send the sysout files for your monitor to BMC Customer Support for analysis.

IOAFB5E IOACMI - PROBLEM INITIALIZING XES AUTOEDIT SUPPORTLink copied to clipboard

Explanation: The IOA initialization routine for XES failed to get enough resources for the XAE (SYSPLEX-wide AutoEdit) facility of Control-O or CMEM. Initialization of the XAE facility requires resources, such as storage, programs and calculations.

The Control-O or CMEM monitor terminates.

Corrective Action: Use earlier messages to determine the cause of the failure.

IOAFB6E IOACMI - PROBLEM CONNECTING XES STRUCTURES RELATED TO AUTOEDIT (XAE)Link copied to clipboard

Explanation: Connection to one of the required XAE structures produced a nonzero return code. A list, a cache, and a lock structure must be allocated for the XAE (SYSPLEX-wide AutoEdit) facility on Coupling facility units. This error indicates that one of these structures could not be allocated or connected.

The Control-O or CMEM monitor terminates.

Corrective Action: Check the following:

  • The definition of the structures in the CFRM.

  • The space allocated for each structure.

  • The contents of the IOAPLEX member.

  • The number of XAE databases in the DAGLBLST member of CTO prefix.PARM or in the IOAGLBVL member of IOA prefix.IOAENV and the contents of each database.

IOAFB7E IOACMI - PROBLEM TERMINATING XES STRUCTURES RELATED TO AUTOEDIT (XAE)Link copied to clipboard

Explanation: Disconnection from one of the required XAE structures produced a nonzero return code. A list, a cache, and a lock are allocated for the XAE (SYSPLEX-wide AutoEdit) facility on Coupling facility units. This error indicates that one of these structures could not be released or disconnected.

The Control-O or CMEM monitor continues with its other actions, without performing the action that caused this error.

Corrective Action: Check the messages that precede this error. If you cannot find the problem, send the sysout files for your monitor to BMC Customer Support for analysis.

IOAFB8E IOACMI - PROBLEM ESTABLISHING RESOURCE MANAGERSLink copied to clipboard

Explanation: The RESMGR service macro of MVS produced a nonzero return code. XES requires MVS resource managers to protect the system from unexpected EOT or EOM events before disconnection from structures is completed.

The Control-O or CMEM monitor terminates.

Corrective Action: Send the sysout files for your monitor to BMC Customer Support for analysis.

IOAFB9E IOACMI - PROBLEMS DURING TERMINATION OF XESLink copied to clipboard

Explanation: Termination of XES facilities produced an error. Some resources, such as programs or memory, could not be released.

Termination of XES facilities stops. The Control-O or CMEM monitor continues with its other actions.

Corrective Action: Send the sysout files for your monitor to BMC Customer Support for analysis.

IOAFBAE CONNECT TO STRUCTURE structureName FAILED. REASON: rsnLink copied to clipboard

Explanation: Control-O or CMEM failed to connect to the structure.

Control-O or CMEM fails to start.

Corrective Action: Check the reason in the message to see why the connection failed, and whether this can be solved by changes to the CF or IOA parameters. If not, contact BMC Customer Support for assistance.

IOAFBBI CONNECT TO STRUCTURE structureName WILL BE RETRIED.Link copied to clipboard

Explanation: This information message indicates that Control-O or CMEM failed to connect to the structure because a system-managed process is currently in progress.

Control-O or CMEM waits for a short time and tries to connect again. After 10 retries, Control-O or CMEM ends.

Corrective Action: If Control-O or CMEM ends, and there is a system-managed process in progress, wait until it ends and start Control-O or CMEM. Otherwise, contact BMC Customer Support for assistance.

IOAFBBW CONNECT TO STRUCTURE structureName IS TEMPORARILY PREVENTED BY XESLink copied to clipboard

Explanation: This message indicates that Control-O or CMEM failed to connect to the structure because a system-managed process is currently in progress.

Control-O or CMEM issues message IOAFBCW and waits until the structure becomes available, or the operator responds to message IOAFBCW.

Corrective Action: See message IOAFBCW.

IOAFBCW monitor IS WAITING UNTIL CONNECT IS ALLOWED. TO CANCEL THEWAIT REPLY 'CANCEL'Link copied to clipboard

Explanation: This message follows message IOAFBBW and lets the operator decide whether to let Control-O or CMEM wait until the structure is available, or cancel Control-O or CMEM and start it later.

If the operator replies CANCEL, Control-O or CMEM will terminate. Otherwise, Control-O or CMEM waits for the structure to become available, connects to the structure and continues the initialization process.

Corrective Action: Check the status of Control-O or CMEM structures and the status of the coupling facility to determine the reason why the connection was prevented. Decide whether to reply CANCEL, or let Control-O or CMEM wait until the structure is available.

IOAFBDW ENFREQ LISTEN/DELETE FOR EVENT 35 FAILED WITH RC X'rc'Link copied to clipboard

Explanation: The ENFREQ LISTEN or DELETE request for event 35 failed. If LISTEN failed, Control-O or CMEM will not be able to wait after connection to a structure is prevented, to be notified when the structure becomes available for connection.

For the LISTEN request, if connection to the XAE structures is allowed, Control-O or CMEM will work normally. If connection to the XAE structures is prevented, Control-O or CMEM will not wait to be notified when the structure is available, but will fail. For the DELETE request, Control-O or CMEM will continue to work normally.

Corrective Action: Contact BMC Customer Support for assistance.

IOAFE1I STRUCTURE structureName IS UNAVAILABLE DUE TO SYSTEM-MANAGED REBUILDLink copied to clipboard

Explanation: This information message indicates that a system-managed rebuild started for the structureName structure. Requests issued for this structure will be deferred until the system-managed rebuild ends, and the structure becomes available again. This will cause delays in accesses to IOA Global variables.

Corrective Action: No action is required.

IOAFE2I SYSTEM-MANAGED REBUILD ALLOCATED STRUCTURE structureName IN COUPLING FACILITY cfnameLink copied to clipboard

Explanation: This information message indicates that the structureName structure created by the system-managed rebuild was allocated on the cfname coupling facility.

Corrective Action: No action is required.

IOAFE3I STRUCTURE structureName IS AVAILABLELink copied to clipboard

Explanation: This information message indicates that the system-managed rebuild or duplex rebuild finished processing the structure, and it is available again. Requests to the structure will be processed by XES.

Corrective Action: If this message is preceded by message IOAF2EI or IOAFE5I, the system-managed process ended successfully. Otherwise, the system-managed process was stopped or failed. See the system log (syslog) for details about the system-managed process.

IOAFE4I STRUCTURE structureName IS UNAVAILABLE DUE TO SYSTEM-MANAGED DUPLEX REBUILDLink copied to clipboard

Explanation: This information message indicates that the system-managed duplex rebuild started for this structure. Requests issued for this structure will be deferred until the system-managed duplex rebuild ends and the structure becomes available again. This will cause delays in accesses to IOA Global variables.

Corrective Action: No action is required.

IOAFE5I STRUCTURE structureName IS IN mode MODELink copied to clipboard

Explanation: This information message provides information about the structure mode. The message is issued when:

  • Control-O or CMEM connects to a structure that is duplexed. Mode will be DUPLEX.

  • System-managed duplex rebuild was performed for the structure. Mode will be DUPLEX.

  • System-managed duplexing was stopped for the structure. Mode will be SIMPLEX. In this case, this message should be preceded by message IOAFE6W.

Corrective Action: No action is required.

IOAFE6W SYSTEM-MANAGED DUPLEXING HAS BEEN STOPPED FOR STRUCTURE structureNameLink copied to clipboard

Explanation: System-managed duplexing was stopped for this structure. There are several instances when structure duplexing is stopped:

  • The operator issued the SETXCF STOP,REBUILD,DUPLEX... MVS command for the structure.

  • The structure definition was changed to DUPLEX (DISABLED).

  • Connection to one of the coupling facilities holding a version of the structure was lost.

Corrective Action: If duplexing is required for this structure, check the system log for messages explaining why duplexing was stopped, and act accordingly.

IOAFE7W STRUCTURE structureName IS UNAVAILABLE DUE TO *UNKNOWN* PROCESS (code)Link copied to clipboard

Explanation: The structureName structure is unavailable, but the reason is unknown. Requests for this structure will not be honored by XES until the structure becomes available again.

Corrective Action: Contact BMC Customer Support for assistance.

IOAFE8E RESPONSE TO EVENT eventCode FOR STRUCTURE structureName FAILED. REASON: rsnLink copied to clipboard

Explanation: Control-O or CMEM failed to respond to an XES event.

Detailed information is written to DATRACE.

Corrective Action: If the error causes problems in the interface to XES, restart Control-O or CMEM. Contact BMC Customer Support for assistance.

Messages IOAG00 through IOAGxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAG00I UTILITY IOADCPY STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOADCPY utility has started.

Corrective Action: No action is required.

IOAG01E ERROR OPENING SYSPRINT FILE. UTILITY IOADCPY UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation: The IOADCPY utility was unable to open the sysprint file.

The IOADCPY utility terminates with a return code of 4.

Corrective Action: Check that the SYSPRINT DD statement exists in the IOADCPY procedure in the PROCLIB library, and that the sysprint file is correctly specified in it. Rerun the IOADCPY utility.

IOAG02E UTILITY IOADCPY UNABLE TO OPEN INPUT FILELink copied to clipboard

Explanation: The IOADCPY utility was unable to open the input file.

The IOADCPY utility terminates with a return code of 8.

Corrective Action: Check that the DAIN DD statement exists in the IOADCPY procedure in the PROCLIB library, and that it references the undamaged file. Rerun the IOADCPY utility.

IOAG03E INVALID IOA NAMELink copied to clipboard

Explanation: The file referenced by the DAIN DD statement was not an IOA Access Component file. The name of the file as it appears in the block of the file is not a valid name for an IOA Access Method file.

The IOADCPY utility terminates with a return code of 12.

Corrective Action: Correct the DAIN DD statement in the IOADCPY procedure in the PROCLIB library to reference a file that is the IOA Access Method file. Rerun the IOADCPY utility.

IOAG04E SPECIFIED FILE NAME IS TOO LONGLink copied to clipboard

Explanation: The name of the file referenced by DAIN DD statement was too long.

The IOADCPY utility terminates with a return code of 16.

Corrective Action: Correct the file name referenced by the DAIN DD statement in the IOADCPY procedure in the PROCLIB library, and rerun the IOADCPY utility.

IOAG05E ERROR IN DYNALLOC OF FILE RC=rcLink copied to clipboard

Explanation: The IOADCPY utility could not dynamically allocate a file. This message is followed by message IOAG06I that details the file name. The return code specified in the message is that returned by SVC 99.

The IOADCPY utility terminates with a return code of 20.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the reason of return codes received. After correcting the problem, rerun the utility.

IOAG06I FILE NAME: fileNameLink copied to clipboard

Explanation: This information message details the name of the file that the IOADCPY utility could not dynamically allocate. This message follows message IOAG05E informing of the dynamic allocation error.

Corrective Action: No action is required.

IOAG07E UTILITY IOADCPY ENDED WITH ERRORSLink copied to clipboard

Explanation: The IOADCPY utility ended after detecting one or more errors. This message follows a message or messages that detail the errors that occurred.

Corrective Action: Check for previous messages and correct the problem accordingly. Rerun the IOADCPY utility.

IOAG08I UTILITY IOADCPY ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the IOADCPY utility ended without errors.

Corrective Action: No action is required.

IOAG09E INSUFFICIENT STORAGE FOR RUNNING UTILITY IOADCPYLink copied to clipboard

Explanation: The IOADCPY utility could not obtain sufficient storage to run.

The IOADCPY utility terminates with a return code of 28.

Corrective Action: Increase the REGION size for the IOADCPY utility and rerun it.

IOAG0AE UTILITY IOADCPY UNABLE TO OPEN OUTPUT FILELink copied to clipboard

Explanation: The IOADCPY utility could not open the input file.

The IOADCPY utility terminates with a return code of 8.

Corrective Action: Check for messages in the sysout of the IOADCPY utility and in the system log, and correct accordingly. Rerun the IOADCPY utility.

IOAG0BI IOA ACCESS METHOD COMPONENT FILE IN USELink copied to clipboard

Explanation: The IOADCPY utility discovered that the IOA Access Method file to be used to restore the damaged file was in use.

The IOADCPY utility waits until the file becomes free.

Corrective Action: No action is required.

IOAG0CE UNIT NAME SUPPLIED IS INVALID.Link copied to clipboard

Explanation: The unit name supplied as a parameter to the IOADCPY utility is invalid.

The dynamic allocation of the IOA Access Method file fails and the IOADCPY utility terminates with an error.

Corrective Action: Check the input parameters to the utility. See the IOAG05E message that follows this error message for the dynamic allocation return code. Correct the parameters accordingly, and rerun the utility.

Messages IOAI00 through IOAIxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAI01E ProdName1 can not be set to Y unless ProdName2 was set to YLink copied to clipboard

Explanation: Product ProdName1 is dependent on product ProdName2. Therefore, ProdName1 cannot be installed unless ProdName2 is also installed.

Corrective Action: First set ProdName2 to Y and then set ProdName1 to Y.

IOAI02E The STEPLIB parameter was set to a non library (PDS) fileLink copied to clipboard

Explanation: The specified Load library dsname is not a PDS or PDSE library.

Corrective Action: Check the file and make sure it is a partioned data set.

IOAI03E The STEPLIB library that was set does not existLink copied to clipboard

Explanation: The specified Load library dsname has not been allocated.

Corrective Action: Check the file and make sure it is allocated and populated.

IOAI04E The STEPLIB library RECFM is not "U"Link copied to clipboard

Explanation: The specified Load library dsname has a record format that is not U.

Corrective Action: Check the file and make sure that attribute U has been allocated in the RECFM parameter.

IOAI05E The STEPLIB library that was set is emptyLink copied to clipboard

Explanation: The specified Load library is empty.

Corrective Action: Check that the specified Load library exists. If it does, check why the library is empty.

IOAI06E The reference Library is not found or unavailable: datasetNameLink copied to clipboard

Explanation: The specified datasetName reference library dsname does not exist or is unavailable for processing.

Corrective Action: Check the file and make sure it is allocated and is available for processing.

IOAI07E Base library prefix can not be one qualifier onlyLink copied to clipboard

Explanation: The specified BASE library prefix has only one qualifier.

Corrective Action: The BASE library prefix must have at leas two qualifiers.

IOAI08E Low level qualifier of Base library prefix MUST be BASELink copied to clipboard

Explanation: The specified low level qualifier of the BASE library prefix is not BASE.

Corrective Action: Change the low level qualifier to BASE.

IOAI09E ICELOG data set DsName is missingLink copied to clipboard

Explanation: ICE or a utility failed to allocate the DsName data set in ilprefa.ICELOG. As a result, messages cannot be written to ICELOG.

Corrective Action: If the data set does not exist, allocate a new ICELOG data set. If it does exist, but it is in use, release it. Then run the tool again.

IOAI0AE Failed to Action DsNameLink copied to clipboard

Explanation: ICE or a utility failed to perform the specified Action on the DsName data set. The Action can be one of the following:

  • allocate

  • write to

  • read from

Corrective Action: Check that the DsName data set exists and is available for performing the specified Action.

IOAI0BE Failed to Action the table TblNameLink copied to clipboard

Explanation: ICE or a utility failed to perform the specified Action on the TblName table. The Action can be one of the following:

  • open

  • create

  • get from

  • skip

  • add to

  • put into

  • update

  • save

  • close

Corrective Action: Check that the TblName table is available for performing the specified Action.

IOAI0CE Invalid parameter ParmNameLink copied to clipboard

Explanation: The value of the parameter ParmName is invalid.

Corrective Action: Change the value of the parameter ParmName to a valid value. Refer to the ICE Online Help or the INCONTROL for z/OS Installation Guide: Installing for information regarding the valid values for the ParmName parameter.

IOAI0DE One of Cloning tools is already runningLink copied to clipboard

Explanation: An instance of one of the cloning tools is already running.

Corrective Action: Wait until the running instance of the cloning tool terminates before invoking the cloning tool.

IOAI0EE Failed to Action the Characteristic of ParmNameLink copied to clipboard

Explanation: ICE or a utility failed to perform the specified Action on the Characteristic of the ParmName parameter.

The Action can be one of the following:

  • get

  • update

The Characteristic can be one of the following:

  • value

  • description

Corrective Action: Check that the utility is invoked according to the information provided in the INCONTROL for z/OS Utilities Guide.

IOAI0FE The environment EnvId does not existLink copied to clipboard

Explanation: ICE or a utility failed to locate the EnvId environment.

Corrective Action: Check that the specified EndId environment exists. If the message is issued by a utility, check that the utility is invoked according to the information provided in the INCONTROL for z/OS Utilities Guide and the value of the ENVID parameter for the utility is correct.

IOAI0GE The environment origin must be EPDLink copied to clipboard

Explanation: The origin of specified environment is not EPD.

Corrective Action: Check that the specified environment origin is EPD. If the message is issued by a utility, check that the utility is invoked according to the information provided in the INCONTROL for z/OS Utilities Guide and the value of the ENVID parameter for the utility is correct.

IOAI0HW Invalid syntax at the line LineNumLink copied to clipboard

Explanation: The file-based Express Installation process failed because of a syntax error in the LineNum line of the input member.

Corrective Action: Fix the syntax error in the LineNum line of the input member of the file-based Express Installation. For more detailed information, please refer to the “Express Install” chapter in the INCONTROL for z/OS Installation Guide: Installing.

IOAI0II Checking the parameter ParmNameLink copied to clipboard

Explanation: ICE or a utility checks the validity of the ParmName parameter.

Corrective Action: No action is required.

IOAI0JI ParmName = ParmValueLink copied to clipboard

Explanation: ICE or a utility assigns the ParmValue value to the ParmName parameter.

Corrective Action: No action is required.

IOAI0KI Action Entity Direction NameLink copied to clipboard

Explanation: ICE or a utility performs an I/O operation.

The Action can be one of the following:

  • reading

  • writing

The Entity can be one of the following:

  • parameters

  • definitions

The Direction can be one of the following:

  • to

  • from

The Name is the name of a data set, or a data set and a member.

Corrective Action: No action is required.

IOAI0LE ExecName can run only in the TSO/ISPF environmentLink copied to clipboard

Explanation: The ExecName EXEC was invoked in an incompatible system environment.

Corrective Action: Invoke the ExecName EXEC in the TSO/ISPF environment.

IOAI0ME ExecName should be invoked from the IOA INSTALL libraryLink copied to clipboard

Explanation: The ExecName EXEC was invoked in an inappropriate library.

Corrective Action: Invoke the ExecName EXEC from the IOA INSTALL library.

IOAI0NE Failed to establish TSO ALTLIB DsNameLink copied to clipboard

Explanation: ICE or a utility failed to allocate the DsName data set.

Corrective Action: Check that the DsName data set exists and it is the IOA LOAD library.

IOAI0OI The exec ExecName terminated with RC= RetCodeLink copied to clipboard

Explanation: The ExecName EXEC terminated with a return code of RetCode.

Corrective Action: No user response is required if RetCode is zero. If it is not, please refer to the INCONTROL for z/OS Utilities Guide for further information regarding the return codes of the ExecName utility.

IOAI0PE Failed to create the member MemNameLink copied to clipboard

Explanation: ICE or a utility failed to create the ilprefa.INSTWORK(MemName) member.

Corrective Action: Compress the ilprefa.INSTWORK data set and ensure that the ilprefa.INSTWORK(MemName) member is not open. Then rerun the utility.

IOAI0QI The exec ExecName startedLink copied to clipboard

Explanation: The ExecName EXEC was invoked and the execution started.

Corrective Action: No action is required.

IOAI0RI The member MemName createdLink copied to clipboard

Explanation: The MemName member was created by ICE or a utility.

Corrective Action: No action is required.

IOAI0SW Used space is over nn% in DsNameLink copied to clipboard

Explanation: The Renaming tool failed to write to the DsName data set, because the data set is almost full.

Corrective Action: Free some space in the data set or enlarge the data set. Compress the data set and rerun the Renaming tool.

IOAI0TE ENVID value is not specifiedLink copied to clipboard

Explanation: The value of the mandatory ENVID parameter is not specified.

Corrective Action: Specify the value of the mandatory ENVID parameter.

IOAI0UW The parameter ParmName is ignoredLink copied to clipboard

Explanation: The value of the superfluous ParmName parameter is ignored.

Corrective Action: No action is required.

IOAI0VE Failed to identify the data set DsNameLink copied to clipboard

Explanation: The Renaming tool failed to identify the DsName data set which is specified in the ilprefa.INSTWORK(IOACDDSL) Data Set List.

Corrective Action: Fix the ilprefa.INSTWORK(IOACDDSL) Data Set List and rerun the Renaming tool.

IOAI0WI Processing data set DsNameLink copied to clipboard

Explanation: The Renaming tool is processing the DsName data set.

Corrective Action: No action is required.

IOAI0XI Setting up ProdLink copied to clipboard

Explanation: The Renaming tool is setting up the Prod product.

Corrective Action: No action is required.

IOAI0YE Failed to Action ProdLink copied to clipboard

Explanation: The Renaming tool failed to perform the Action operation on the Prod product.

The Action can be one of the following:

  • setup

  • post-clone

Corrective Action: Please examine the messages in the ilprefa.ICELOG data set to identify the reason of the failure.

IOAI0ZI Data set DsName already existsLink copied to clipboard

Explanation: The Renaming tool is invoked with the parameter MODE(ALLOC) and the DsName data set is listed in the ilprefa.INSTWORK(IOACDDSL) Data Set List. The tool will not allocate the DsName data set because the data set already exists.

Corrective Action: No action is required.

IOAI10E OPTION R IS INVALID, SINCE THE REFERENCE ENVIRONMENT WAS NOT SPECIFIEDLink copied to clipboard

Explanation: Specifying the R option for the capacity of a product refers the installation to the reference environment. If no reference environment was specified, the R option is meaningless.

Corrective Action: Specify the capacity using an available option or specify the reference environment.

IOAI11E SMP/E data sets are not exclusively owned by this IOALink copied to clipboard

Explanation: The SMP/E CSI of this IOA environment contains other (non-INCONTROL) products, or other IOA instances. SMP/E Enabled IOA Cloning is not supported in this case.

Corrective Action: For more information, see the Limitations section of the "Cloning an IOA environment" chapter in the INCONTROL for z/OS Installation Guide: Installing.

IOAI12E SMP/E Cloning can be done using ICE only.Link copied to clipboard

Explanation: Cloning can only be performed using ICE.

Corrective Action: Perform the cloning from ICE.

IOAI20E ECAPARMx validation error messageLink copied to clipboard

Explanation: Where ECAPARMx validation error message can be one of the following:

  • Application Appl cannot share a channel with application C

  • Application Appl cannot share a channel with application F

  • Application C cannot share its channel with other applications

  • Application F cannot share its channel with other applications

  • Application F must have TCP protocol

  • Applications D, F must have MULTCONN channel

  • Channel ChanID is not used by any application

  • Channel ChanID not defined for APPL Appl

  • Control-M (M) must have TCP DUALCONN channel

  • Control-M/CM COMTASK should be left null or set to 1

  • Control-M/CM must have TCP MULTCONN channel

  • Control-M/CM UPERTASK should be left null or set to 1

  • Control-O (O) must have MULTCONN channel

  • Errors found. ECAPARMx was not built

  • Join of applications is not supported. APPL= Appl

  • Mixed TCP vendors. Channel: TCPVendorChanID - Channel: TCPVendorChanID

  • No application was defined

  • No channel was defined

  • Only one Control-M (M) allowed in ECAPARM

  • Only one Control-M/CM allowed in ECAPARM

  • Only one Control-O (O) allowed in ECAPARM

  • Only one PATROL (P) allowed in ECAPARM

  • PATROL (P) must have TCP MULTCONN channel

  • The APPLID Appl in channel ChanID is already used

  • The channel ChanID must have Node and Map parameters

  • The port PortNum in channel ChanID is already used

Corrective Action:Correct the problem and run the Renaming tool again.

IOAI21I Renaming tool informative messageLink copied to clipboard

Explanation: Where Renaming tool informative message can be one of the following:

  • Active Balancing File Space Calculation

  • Activity File Space Calculation

  • Adjust CTV members in CTD JCL data set

  • Adjust members in CTD SKL data set

  • Build ECAPARMC

  • Build ECAPARMD for APPL=(D)

  • Build ECAPARMD for APPL=(F)

  • Build ECAPARMM

  • Build the IOAKPRM parameters member

  • Build the IOARULES member

  • Build the IOASPRM parameters member

  • Build the IOAXPRM parameters member

  • Build the SECPARM member

  • Copy Prod procedures

  • Copy Prod started tasks

  • Format IOA Data Base

  • Group File Space Calculation

  • IOA Log File Space Calculation

  • Media Database Space Calculation

  • Post-clone Prod

  • Report File Space Calculation

  • Resolve Prod libraries

  • Save Parameters

  • Space Calculation for ACTive User File

  • Space Calculation for Columns File

  • Space Calculation for Databases File

  • Space Calculation for HiSTory User File

  • Space Calculation for MIGrated User File

  • Space Calculation for PeRManent User File

  • Space Calculation for Variables File

  • Stacking Database Space Calculation

  • Trace File Space Calculation

  • Update Global Index File parameters

  • Validate Prod parameters

  • Vars Definition File Space Calculation

  • Vars Generations File Space Calculation

Corrective Action: No action is required.

IOAI22E Failed to process data set DsNameLink copied to clipboard

Explanation: The Renaming tool failed to process the DsName data set.

Corrective Action: Examine the informative message IOAI23I that follows to obtain more information about how to correct the problem.

IOAI23I Renaming tool informative messageLink copied to clipboard

Explanation: This informative message can be issued either independently or following the IOAI22E error message, providing more detailed information about the failure. The Renaming tool informative message can be one of the following:

  • RC= Rc Routine

  • The job JobName (JobID) failed

(Only issued when the failure was caused by a job.)

Corrective Action: If necessary, make the necessary correction, using the information provided, and run the Renaming tool again.

IOAI25E Renaming tool error messageLink copied to clipboard

Explanation: Where Renaming tool error message can be one of the following:

  • Active Balancing File Space Calculation Failed

  • Activity File Space Calculation Failed

  • Failed to Adjust CTV members in CTD JCL data set

  • Failed to Adjust members in CTD PARM data set

  • Failed to Adjust members in CTD SKL data set

  • Failed to Build ECAPARMC

  • Failed to Build ECAPARMD for APPL=(D)

  • Failed to Build ECAPARMD for APPL=(F)

  • Failed to Build ECAPARMM

  • Failed to build the IOAKPRM parameters member

  • Failed to build the IOARULES member

  • Failed to Build the IOASPRM parameters member

  • Failed to build the IOAXPRM parameters member

  • Failed to build the SECPARM member

  • Failed to copy Prod procedures

  • Failed to copy Prod started tasks

  • Failed to Format IOA Data Base

  • Failed to save Parameters

  • Failed to Update Global Index File parameters

  • Group File Space Calculation Failed

  • IOA Log File Space Calculation Failed

  • Media Database Space Calculation Failed

  • Report File Space Calculation Failed

  • Space Calculation for ACTive User File Failed

  • Space Calculation for Columns File Failed

  • Space Calculation for Databases File Failed

  • Space Calculation for HiSTory User File Failed

  • Space Calculation for MIGrated User File Failed

  • Space Calculation for PeRManent User File Failed

  • Space Calculation for Variables File Failed

  • Stacking Database Space Calculation Failed

  • Trace File Space Calculation Failed

  • Vars Definition File Space Calculation Failed

  • Vars Generations File Space Calculation Failed

Corrective Action: Correct the problem and run the Renaming tool again.

IOAI26W DataSetName (MemberName)Link copied to clipboard

Explanation: The format of the member differs in the two versions of IOA involved in the Express Upgrade process.

Corrective Action: Continue with the Express Upgrade. After performing the “Complete the Upgrade” step, check that no problems exist with the functionality of the products. If there are no problems, the message can be ignored and no further action is required.

IOAI27E Renaming tool cannot be invoked in this environment when the MODE is different from ALLOCLink copied to clipboard

Explanation: The message is issued when the Renaming Tool is invoked on the base environment with the MODE=FULL or MODE=ADJUST.

Corrective Action: Set the MODE to ALLOC and then invoke the Renaming tool.

IOAI98W DsName is not used in DFDSS mode.Link copied to clipboard

Explanation: An old format Renaming Definitions data set basepref.RNM was detected by the Renaming tool running in the DFDSS mode on a cloned IOA environment. The data set is not used by the Renaming tool in DFDSS mode.

Corrective Action: Ensure that you are using the new cloning process, in which all cloning parameters are specified in ICE screens and are validated using the ICE processes, instead of manually editing the Renaming Definitions data set basepref.RNM.

IOAI99W FULL mode is obsolete. Use DFDSS mode instead.Link copied to clipboard

Explanation: The Renaming tool was invoked in FULL mode, which is obsolete.

Corrective Action: Use the DFDSS mode for Renaming tool invocation, instead of FULL mode.

Messages IOAJ00 through IOAJxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAJ01I CONDITION WAS ADDED AT LOC=rba DATE=date NAME=name BY USER=userId J=jobName (jobId)

Explanation: A condition was successfully added to the IOA Conditions file. This message is issued only when condition change logging is active. In a monitor address space, this message will be preceded by message IOAJ59I. The variables in this message are:

  • rba - The location in the Conditions file where the condition was stored (used for diagnostic purposes only).

  • date - The date in local format of the condition that was added.

  • name - The name of the condition that was added.

  • userId - The user ID that is associated with the operation.

  • jobName - The name of the job, started task, or TSO user address space associated with the operation.

  • jobId - The JES job ID of the address space associated with the operation.

Logging of changes to the IOA Conditions file is controlled by the CNDLOG parameter in the IOAPARM member of the IOA PARM library. In ICE, you can specify the CNDLOG parameter, as follows:

  1. From the IOA Installation Menu, select Customization.

  2. Select the environment to customize.

  3. In the Customization screen, set Product ID to IOA and select Product Customization.

  4. Select Major Step 2, “Customize IOA Dataset Parameters.”

  5. Select Minor Step 3, “Conditions File(s) Parameters.”

Corrective Action: No action is required.

IOAJ02I CONDITION WAS DELETED AT LOC=rba DATE=date NAME=name BY USER=userId J=jobName (jobId)Link copied to clipboard

Explanation: A condition was successfully deleted from the IOA Conditions file. This message is issued only when condition change logging is active. In a monitor address space, this message will be preceded by message IOAJ59I.

The variables in this message are:

  • rba - The location in the Conditions file where the condition was stored prior to being deleted (used for diagnostic purposes only).

  • date - The date in local format of the condition that was deleted.

  • name - The name of the condition that was deleted.

  • userId - The user ID that is associated with the operation.

  • jobName - The name of the job, started task or TSO user address space associated with the operation.

  • jobId - The JES job ID of the address space associated with the operation.

Logging of changes to the IOA Conditions file is controlled by the CNDLOG parameter in the IOAPARM member of the IOA PARM library. In ICE, you can specify the CNDLOG parameter, as follows:

  1. From the IOA Installation Menu, select Customization.

  2. Select the environment to customize.

  3. In the Customization screen, set Product ID to IOA and select Product Customization.

  4. Select Major Step 2, “Customize IOA Dataset Parameters.”

  5. Select Minor Step 3, “Conditions File(s) Parameters.”

Corrective Action: No action is required.

IOAJ10E NO PLACE TO ADD CONDITION USER=userId DATE=date NAME=nameLink copied to clipboard

Explanation: A condition was not added to the IOA Conditions file because there was no available space in the relevant records of the file. Note that the IOA Conditions file is divided into records according to the day of the month within the condition date; therefore, it is possible that other conditions with different dates can still be added even though conditions for a particular day of the month cannot.

The variables in this message are:

  • userId - The user ID that is associated with the operation.

  • date - The date in local format of the condition that was attempted to be added.

  • name - The name of the condition that was attempted to be added.

The operation is not carried out. The IOA Conditions file is left unchanged, but the address space requesting the operation may terminate as a result.

Corrective Action: In order to maintain production flow, try to add the condition from IOA online screen 4. If the problem persists, you may free up some space by deleting conditions that are not needed, that have the same day of the month as the condition that was not added. For example, if the date of the condition that was not added is 0312, and your dates are in European format, then you may try deleting other conditions whose day is 03, such as those with date 0301, 0302 etc. If the date is STAT then you may try deleting other conditions with date STAT.

If the problem is not due to a large number of conditions that were mistakenly added, contact your IOA administrator to seek a long-term solution. The IOAVERFY utility can be used to analyze the current capacity of the file and to see the distribution of conditions among the days of the month. The Control-M New Day procedure can be used to delete conditions from the IOA Conditions file on a daily basis, and the IOACLCND utility can also be used to periodically delete unneeded conditions. If necessary, the IOA Conditions file may be reallocated and reformatted with a higher number of blocks per day, using the IOABCN utility. In that case, the DUAL IOA Conditions file (//DAALTCND) and/or the Control-M JOURNAL Condition file may need to be reallocated as well. Note that when reformatting the file, all of the conditions that have been added to the file will be lost.

IOAJ10W CONDITION FILE IS prc% FULL. PLEASE NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation:Highlighted, unrollable message.

The IOA Conditions file is nearly full. In order to prevent the IOAJ10E message the Control-x alerts the user if the IOA Conditional file is over 90% full for particular day.

The prc% in this message is the percent of day file space usage. Processing continues.

Corrective Action: Notify the INCONTROL administrator. Probably the IOA Condition File size should be increased. For more information, see the description of the IOAJ10E message.

IOAJ20S DACNDF QNAME=file_shrqnam WHILE IOAPARM SHRQNAM=parm_shrqnamLink copied to clipboard

Explanation: The IOA Conditions file is not accessible due to an integrity check failure. The file may be corrupted, or it may have been formatted by the IOABCN utility with a shared resource QNAME which is different from the current shared resource QNAME. It is possible that an attempt was made to access an IOA Conditions file that belongs to another installation.

Access to the IOA Conditions failed. The address space requesting to access the IOA Conditions file may terminate as a result.

The variables in this message are:

  • file_shrqnam - The shared resource QNAME inside the file, corresponding to the shared resource QNAME which was defined at the time that the IOA Conditions file was formatted.

  • parm_shrqnam - The current shared resource QNAME, as defined in the IOA PARM library.

The shared resource QNAME is defined by the SHRQNAM parameter. In a customized installation, you specify SHRQNAM in ICE step 4.2. In a Default or Cloning installation, you specify SHRQNAM on panel (DI.4.0).

Corrective Action: Verify that the correct IOA Conditions file is being used. If the correct file is used, contact your IOA administrator to check if the file needs to be restored or reformatted. Note that when reformatting the file, all of the conditions that have been added to the file will be lost.

IOAJ21S DACNDF NOT FORMATTED AS CONDITION FILE, FILE ID=fidLink copied to clipboard

Explanation: The IOA Conditions file is not accessible due to an integrity check failure. The file may be corrupted, or it may have not been formatted by the IOABCN utility. It is possible that an incorrect file is allocated to DDNAME //DACNDF.

In this message, fid is the three-letter internal file ID that is marked in the first record of the file (this should be SNC for an IOA Conditions file).

Access to the IOA Conditions failed. The address space requesting to access the IOA Conditions file may terminate as a result.

Corrective Action: Verify that the correct IOA Conditions file is being used. The name of the IOA Conditions file usually has a low level qualifier of CND, such as IOA.CND. If the correct file is used, contact your IOA administrator to check if the file needs to be restored or reformatted. Note that when reformatting the file, all of the conditions that have been added to the file will be lost.

IOAJ22S DACNDF IS NOT AVAILABLE, FILE STATUS=statusLink copied to clipboard

Explanation: The IOA Conditions file is not accessible due to an integrity check failure. The file may be corrupted, or it may have been partially formatted by the IOABCN utility. It is possible that an attempt was made to access an IOA Conditions file that began formatting but failed before completing.

In this message, status is the six-letter internal status that is marked in the first record of the file (should be FREE for a properly formatted IOA Conditions file).

Access to the IOA Conditions file failed. The address space requesting to access the IOA Conditions file may terminate as a result.

Corrective Action: Verify that the correct IOA Conditions file is being used. If the correct file is used, contact your IOA administrator to check if the file needs to be restored or reformatted. Note that when reformatting the file, all of the conditions that have been added to the file will be lost.

IOAJ23S DACNDF BLOCKS PER DAY=file_cndrec_num WHILE IOAPARM CNDREC#=parm_cndrec_numLink copied to clipboard

Explanation: The IOA Conditions file is not accessible due to an integrity check failure. The file may be corrupted, or it may have been formatted by the IOABCN utility with a number of blocks per day which is different from the current number of blocks per day. It is possible that an attempt was made to access an IOA Conditions file that belongs to another installation.

Access to the IOA Conditions file failed. The address space requesting to access the IOA Conditions file may terminate as a result.

The variables in this message are:

  • file_cndrec_num - The number of blocks per day inside the file, corresponding to the number of blocks per day which was defined at the time that the IOA Conditions file was formatted.

  • parm_cndrec_num - The current number of blocks per day, as defined in the IOA PARM library.

The number of blocks per day is defined by the CNDREC# parameter. In ICE, you can specify the CNDREC# parameter, as follows:

  1. From the IOA Installation Menu, select Customization.

  2. Select the environment to customize.

  3. In the Customization screen, set Product ID to IOA and select Product Customization.

  4. Select Major Step 2, “Customize IOA Dataset Parameters.”

  5. Select Minor Step 3, “Conditions File(s) Parameters.”

Corrective Action: Verify that the correct IOA Conditions file is being used. If the correct file is used, contact your IOA administrator to check if the file needs to be restored or reformatted. Note that when reformatting the file, all of the conditions that have been added to the file will be lost.

IOAJ2AS DACNDF R0 BLOCK ID= SNC_id IS INVALID AT RBA rbaLink copied to clipboard

Explanation: The IOA Conditions file is not accessible due to an integrity check failure. The SNC record was not placed in the correct block of the file. The file may be corrupted, or it is possible that an attempt was made to access an IOA Conditions file that belongs to another installation.

Access to the IOA Conditions file failed. As a result, the address space attempting to access the IOA Conditions file may terminate.

The variables in this message are:

  • SNC_id - SNC record identifier (0–3)

  • rba - Number of block in the file

Corrective Action: Verify that the correct IOA Conditions file is being used. If the correct file is being used, contact your IOA administrator to check whether the file needs to be restored or reformatted. Note that when reformatting the file, all of the conditions that have been added to the file will be lost.

IOAJ2BS DACNDF NUMBER OF R0 BLOCKS SNC_num IS INVALID. THE CORRECT VALUE IS SNC_num_cndrecLink copied to clipboard

Explanation: The IOA Conditions file is not accessible due to an integrity check failure. The number of SNC records does not match the current number of blocks per day, as defined in the IOA PARM library. The file may be corrupted, or it is possible that an attempt was made to access an IOA Conditions file that belongs to another installation.

Access to the IOA Conditions file failed. As a result, the address space attempting to access the IOA Conditions file may terminate.

The variables in this message are:

  • SNC_num - Number of SNC records (0–3)

  • SNC_num_cndrec - Number of SNC records calculated from the CNDREC# parameter defined in the IOA PARM library

Corrective Action: Verify that the correct IOA Conditions file is being used. If the correct file is being used, contact your IOA administrator to check whether the file needs to be restored or reformatted. Note that when reformatting the file, all of the conditions that have been added to the file will be lost.

IOAJ51W CONDITION NOT ADDED - ALREADY EXISTS. USER=userId DATE=date NAME=nameLink copied to clipboard

Explanation: A condition was not added to the IOA Conditions file. The same condition, with the same name and same date, already exists in the file. The operation cannot be performed because the IOA Conditions file can contain only one instance of each condition.

The variables in this message are:

  • userId - The user ID that is associated with the operation.

  • date - The date in local format of the condition that was attempted to be added.

  • name - The name of the condition that was attempted to be added.

The operation is not carried out. The IOA Conditions file is left unchanged, and the address space requesting the operation continues functioning.

Corrective Action: No action is required. However, if the message repeats then you may reconsider whether adding the condition under these circumstances is really necessary.

IOAJ52W CONDITION NOT DELETED - DOES NOT EXIST. USER=userId DATE=date NAME=nameLink copied to clipboard

Explanation: A condition was not deleted from the IOA Conditions file. A condition with the same name and same date does not exist in the file. The operation cannot be performed because only conditions that are contained in the IOA Conditions file can be deleted.

The variables in this message are:

  • userId - The user ID that is associated with the operation.

  • date - The date in local format of the condition that was attempted to be deleted.

  • name - The name of the condition that was attempted to be deleted.

The operation is not carried out. The IOA Conditions file is left unchanged, and the address space requesting the operation continues functioning.

Corrective Action: No action is required. However, if the message repeats then you may reconsider whether deleting the condition under these circumstances is really necessary.

IOAJ53E INVALID CONDITION DATE=date FUNC=func USER=userID NAME=nameLink copied to clipboard

Explanation: An invalid DATE was specified in a call for condition services.

The variables in this message are:

  • date - the invalid date provided in the call

  • func - the internal function code representing the request type

  • userID - the USERID associated with the request

  • name - the condition name

The service is not performed. The caller of the service may decide to terminate or shut down.

Corrective Action: If the cause is not attributable to user error, contact BMC Customer Support.

IOAJ54E INVALID CONDITION NAME. FUNC=func USER=userID DATE=date NAME=nameLink copied to clipboard

Explanation: An invalid CONDITION NAME was specified in a call for condition services.

The variables in this message are:

  • func - the internal function code representing the request type

  • userID - the USERID associated with the request

  • date - the date in local format provided in the call

  • name - the invalid condition name

The service is not performed. The caller of the service may decide to terminate or shut down.

Corrective Action: If the cause is not attributable to user error, contact BMC Customer Support.

IOAJ55E INVALID CONDITION LEN=length. FUNC=func USER=userID DATE=date NAME=nameLink copied to clipboard

Explanation: An invalid CONDITION length was specified in a call for condition services.

The variables in this message are:

  • length - the invalid length of the condition specified in the call

  • func - the internal function code representing the request type

  • userID - the USERID associated with the request

  • date - the date in local format provided in the call

  • name - the condition name

The service is not performed. The caller of the service may decide to terminate or shut down.

Corrective Action: If the cause is not attributable to user error, contact BMC Customer Support.

IOAJ57S IOACND INTERNAL ERROR. FUNC=func DIAG=diagLink copied to clipboard

Explanation: An internal error occurred in a call for condition services.

The variables in this message are:

  • func - the internal function code representing the request type

  • diag - the diagnostic code identifying the exact internal error code. This value is used by BMC to locate the exact place and circumstances of the error.

An SVC DUMP is taken, or a SNAP DUMP is written to //DACNDDMP. The caller of the service may decide to terminate execution.

Corrective Action: Review the job log and look for additional error messages with a prefix of IOAJ, such as IOAJ23S or a similar message, which were issued shortly before this message. If such a message is found, review the documentation for that message for a possible explanation of the source of the problem. If this does not help, or if no such preceding messages are found, save the job log and the DUMP which was produced, and contact BMC Customer Support.

IOAJ58S IOACND UNKNOWN INTERNAL ERROR. FUNC=func DIAG=diagLink copied to clipboard

Explanation: An unidentified internal error occurred in a call for condition services.

The variables in this message are:

  • func - the internal function code representing the request type

  • diag - the diagnostic code identifying the internal error code. This value is used by BMC to locate the exact place and circumstances of the error.

An SVC DUMP is taken, or a SNAP DUMP is written to //DACNDDMP. The caller of the service may decide to terminate execution.Link copied to clipboard

Corrective Action: Review the job log and look for additional error messages with a prefix of IOAJ, such as IOAJ23S or a similar message, which were issued shortly before this message. If such a message is found, review the documentation for that message for a possible explanation of the source of the problem. If this does not help, or if no such preceding messages are found, save the job log and the DUMP which was produced, and contact BMC Customer Support.

IOAJ59I CONDITION LOGGING IS ACTIVE. DESTINATION=log_destLink copied to clipboard

Explanation: Logging of changes to the IOA Conditions file is active. Note that this message only appears in monitor address spaces, not in batch jobs and not during online sessions.

For each condition that will be added to or deleted from the current address space, message IOAJ01I or IOAJ02I will be issued respectively.

In this message, log_dest is the destination where logging messages IOAJ01I and IOAJ02I will be issued, in either IOALOG or SYSLOG. This corresponds to the setting of the CNDLOG parameter in the IOAPARM member of the IOA PARM library.

Logging of changes to the IOA Conditions file is controlled by the CNDLOG parameter in the IOAPARM member of the IOA PARM library. In ICE, you can specify the CNDLOG parameter, as follows:

  1. From the IOA Installation Menu, select Customization.

  2. Select the environment to customize.

  3. In the Customization screen, set Product ID to IOA and select Product Customization.

  4. Select Major Step 2, “Customize IOA Dataset Parameters.”

  5. Select Minor Step 3, “Conditions File(s) Parameters.”

Corrective Action: No action is required.

IOAJ5AI CONDITION LOGGING IS INACTIVELink copied to clipboard

Explanation: Logging of changes to the IOA Conditions file is inactive. Note that this message only appears in monitor address spaces, not in batch jobs and not during online sessions. No logging with messages IOAJ01I or IOAJ02I will be done for conditions that are going to be added to or deleted from the current address space.

Logging of changes to the IOA Conditions file is controlled by the CNDLOG parameter in the IOAPARM member of the IOA PARM library. In ICE, you can specify the CNDLOG parameter, as follows:

  1. From the IOA Installation Menu, select Customization.

  2. Select the environment to customize.

  3. In the Customization screen, set Product ID to IOA and select Product Customization.

  4. Select Major Step 2, “Customize IOA Dataset Parameters.”

  5. Select Minor Step 3, “Conditions File(s) Parameters.”

Corrective Action: No action is required.

IOAJ5BE GETMAIN IN ECSA AREA FAILED. FUNC=func DIAG=diagLink copied to clipboard

Explanation: A GETMAIN request in ECSA failed in a call to condition services.

The variables in this message are:

  • func - the internal function code representing the request type

  • diag - the diagnostic code identifying the internal error code. This value is used by BMC to locate the exact place and circumstances of the error.

An SVC DUMP is taken, or a SNAP DUMP is written to //DACNDDMP. The caller of the service may decide to terminate execution.

Corrective Action: Review the job log and system log and look for other error messages which may help identify the source of the problem, not necessarily related to the IOA Conditions infrastructure. Review and adjust the appropriate storage limitations for the system or for the specific address space as necessary. If this does not help, save the job log, the relevant part of the system log and DUMP which was produced, and contact BMC Customer Support.

IOAJ5CE GETMAIN IN PRIVATE AREA FAILED. FUNC=func DIAG=diagLink copied to clipboard

Explanation: A GETMAIN request in private area failed in a call to condition services.

The variables in this message are:

  • func - the internal function code representing the request type

  • diag - the diagnostic code identifying the internal error code. This value is used by BMC to locate the exact place and circumstances of the error.

An SVC DUMP is taken, or a SNAP DUMP is written to //DACNDDMP. The caller of the service may decide to terminate execution.

Corrective Action: Review the job log and system log and look for other error messages which may help identify the source of the problem, not necessarily related to the IOA Conditions infrastructure. Review and adjust the appropriate storage limitations for the system or for the specific address space as necessary. If this does not help, save the job log, the relevant part of the system log and DUMP which was produced, and contact BMC Customer Support.

IOAJ5DS IOACND INTERNAL ERROR DURING INITIALIZATION. DIAG=diagLink copied to clipboard

Explanation: An internal error occurred during condition services initialization.

In this message, diag is the diagnostic code identifying the exact internal error code. This value is used by BMC to locate the exact place and circumstances of the error.

The condition services initialization fails. The caller of the service may decide to terminate execution.

Corrective Action: Contact BMC Customer Support.

IOAJ5EI CONDITION LOGGING IS SUPPRESSEDLink copied to clipboard

Explanation: Logging of changes to the IOA Conditions file is inactive. It is possible that logging of changes to the IOA Conditions file was requested by the CNDLOG parameter in the IOAPARM member of the IOA PARM library; however, the program accessing the IOA Conditions file requested that logging be suppressed. Note that this message only appears in monitor address spaces, not in batch jobs and not during online sessions.

No logging with messages IOAJ01I or IOAJ02I will be done for conditions that are going to be added to or deleted from the current address space.

Corrective Action: No action is required.

IOAJ5FI WRITING TO DUAL CONDITIONS FILE (DAALTCND) IS ACTIVELink copied to clipboard

Explanation: Mirroring of changes to the IOA Conditions file is active. Each change that is done to the IOA Conditions file (//DACNDF) will also be mirrored to the alternate IOA Conditions file (//DAALTCND). Note that this message only appears in monitor address spaces, not in batch jobs and not during online sessions.

For each record of the IOA Conditions file that is going to be updated from the current address space, the same data will be updated in the corresponding record in the alternate IOA Conditions file.

Mirroring of changes to the IOA Conditions file is controlled by the DUALDB parameter in the IOAPARM member of the IOA PARM library. In ICE, you can specify the DUALDB parameter, as follows:

  1. From the IOA Installation Menu, select Customization.

  2. Select the environment to customize.

  3. In the Customization screen, set Product ID to IOA and select Product Customization.

  4. Select Major Step 2, “Customize IOA Dataset Parameters.”

  5. Select Minor Step 3, “Conditions File(s) Parameters.”

Corrective Action: No action is required.

IOAJ5GE CONDITION NOT ADDED - NOT AUTHORIZED. USER=userID DATE=date NAME=nameLink copied to clipboard

Explanation: A call to add a condition has not been authorized by the security interface.

The variables in this message are:

  • userID - the USERID associated with the request

  • date - the date in local format provided in the call

  • name - the condition name

The condition is not added.

Corrective Action: Determine whether the user should be authorized to add the condition and if not, why an unauthorized user tried to add the condition.

If any variable in the message is invalid and the cause is not attributable to user error, contact BMC Customer Support.

IOAJ5HE CONDITION NOT DELETED - NOT AUTHORIZED. USER=userID DATE=date NAME=nameLink copied to clipboard

Explanation: A call to delete a condition has not been authorized by the security interface.

The variables in this message are:

  • userID - the USERID associated with the request

  • date - the date in local format provided in the call

  • name - the condition name

The condition is not deleted.

Corrective Action: Determine whether the user should be authorized to delete the condition and if not, why an unauthorized user tried to delete the condition.

If any variable in the message is invalid and the cause is not attributable to user error, contact BMC Customer Support.

IOAJ5IE CONDITION CHECK NOT AUTHORIZED. USER=userID DATE=date NAME=nameLink copied to clipboard

Explanation: A call to check the status of a condition has not been authorized by the security interface.

The variables in this message are:

  • userID - the USERID associated with the request

  • date - the date in local format provided in the call

  • name - the condition name

The status of the condition is not returned and the operation fails.

Corrective Action: Determine whether the user should be authorized to check the condition and if not, why an unauthorized user tried to check the condition status.

If any variable in the message is invalid and the cause is not attributable to user error, contact BMC Customer Support.

IOAJ5JI NO CONDITION DELETED - NONE FOUND. USER=useID FROM=fromDate TO=toDate DATE=date NAME=nameLink copied to clipboard

Explanation: This information message indicates that a call to delete all conditions according to given criteria has not found any condition matching the criteria.

The variables in this message are:

  • userID - the USERID associated with the request

  • fromDate - start of the date range provided in the call

  • toDate - end of the date range provided in the call

  • date - additional specific date (such as STAT, 0101) to delete provided in the call

  • name - the condition name

Corrective Action: No action is required.

IOAJ5KI NO CONDITION DELETED - NONE FOUND. USER=useID FROM=fromDate TO=toDate NAME=nameLink copied to clipboard

Explanation: This information message indicates that a call to delete all conditions according to given criteria has not found any condition matching the criteria.

The variables in this message are:

  • userID - the USERID associated with the request

  • fromDate - start of the date range provided in the call

  • toDate - end of the date range provided in the call

  • name - the condition name

Corrective Action: No action is required.

IOAJ5LI NO CONDITION DELETED - NONE FOUND. USER=useID DATE=date NAME=nameLink copied to clipboard

Explanation: This information message indicates that a call to delete all conditions according to given criteria has not found any condition matching the criteria.

The variables in this message are:

  • userID - the USERID associated with the request

  • date - specific date (STAT, 0101, or mask) to delete provided in the call

  • name - the condition name

Corrective Action: No action is required.

IOAJ5MI NO MATCHING CONDITION DELETED - ALL IGNORED. USER=useID FROM=fromDate TO=toDate DATE=date NAME=nameLink copied to clipboard

Explanation: This information message indicates that a call to delete all conditions according to given criteria has found some condition matching the criteria, but the caller requested to skip the deletion of each found condition.

The variables in this message are:

  • userID - the USERID associated with the request

  • fromDate - start of the date range provided in the call

  • toDate - end of the date range provided in the call

  • date - additional specific date (such as STAT, 0101) to delete provided in the call

  • name - the condition name

Corrective Action: No action is required.

IOAJ5NI NO MATCHING CONDITION DELETED - ALL IGNORED. USER=useID FROM=fromDate TO=toDate NAME=nameLink copied to clipboard

Explanation: This information indicates that a call to delete all conditions according to given criteria has found some condition matching the criteria, but the caller requested to skip the deletion of each found condition.

The variables in this message are:

  • userID - the USERID associated with the request

  • fromDate - start of the date range provided in the call

  • toDate - end of the date range provided in the call

  • name - the condition name

Corrective Action: No action is required.

IOAJ5OI NO MATCHING CONDITION DELETED - ALL IGNORED. USER=useID DATE=date NAME=nameLink copied to clipboard

Explanation: This information message indicates that a call to delete all conditions according to given criteria has found some condition matching the criteria, but the caller requested to skip the deletion of each found condition.

The variables in this message are:

  • userID - the USERID associated with the request

  • date - the specific date in local format or date mask provided in the call

  • name - the condition name

Corrective Action: No action is required.

IOAJ60I WRITING TO DUAL CONDITIONS FILE (DAALTCND) IS SUPPRESSEDLink copied to clipboard

Explanation: Mirroring of changes to the IOA Conditions file is inactive. Changes that are done to the IOA Conditions file (//DACNDF) will not be mirrored to the alternate IOA Conditions file (//DAALTCND). It is possible that mirroring of changes to the IOA Conditions file was requested by the DUALDB parameter in the IOAPARM member of the IOA PARM library; however, the program accessing the IOA Conditions file requested that mirroring be suppressed. Note that this message only appears in monitor address spaces, not in batch jobs and not during online sessions.

Corrective Action: No action is required.

IOAJ70E PARAMETER IS NOT SUPPORTED PLEASE TRY AGAIN.PROGRAM TERMINATEDLink copied to clipboard

Explanation: An invalid parameter was entered for the IOAPCP3 utility .

The wrong parameter is logged with a return code of 20.

Corrective Action: Change the parameter to a valid value.

IOAJ71E ENVIRONMENT INITIALIZATION FAILED, IOAENV RC=rcLink copied to clipboard

Explanation: The IOAPCP3 utility could not initiate an environment.

Additional error messages are displayed prior to this message. The program terminates with a return code of 16.

Corrective Action: Correct the preceding error messages, and rerun the job.

IOAJ72E GETMAIN FOR INPUT DDNAME DASACND FAILED.Link copied to clipboard

Explanation: The IOAPCP3 utility could not allocate an area of virtual storage for the input step.

The system informs the user which of the steps did not execute, and exits with a return code of 16.

Corrective Action: Increase the region size, and rerun the job.

IOAJ73E GETMAIN FOR OUTPUT DDNAME DASACND FAILED.Link copied to clipboard

Explanation: The IOAPCP3 utility could not allocate an area of virtual storage for the output step.

The system informs the user which of the steps did not execute, and exits with a return code of 16.

Corrective Action: Increase the region size, and rerun the job.

IOAJ74E OPEN INPUT DDNAME DASACND FAILED.Link copied to clipboard

Explanation: The IOAPCP3 utility could not open the file from which it had to read.

The system informs the user which of the steps did not execute, and exits with a return code of 12.

Corrective Action: Verify that the file exists, there is no problem accessing the file, and that nobody else is currently using the same file.

IOAJ75E OPEN OUTPUT DDNAME DASACND FAILED.Link copied to clipboard

Explanation: The program could not open the file from which it had to read.

The system tells the user know which of the steps did not execute and exits with a return code of 12.

Corrective Action: Verify that the file exists, there is no problem accessing the file, and that nobody else is currently using the same file.

IOAJ76E ERROR AT IOACND INTERNAL FUNCTION= FUNCTION, SEE IOACND FAILURE.Link copied to clipboard

Explanation: A failure occurred in the IOACND member.

The system tells the user know which of the steps did not execute and exits with a return code of 8.

Corrective Action: Check the return code with the IOACND error message for further response.

IOAJZ1I IOA CONDITIONS SNAP DUMP (IOAJ57S) BY user RSN=rsn DIAG=diag ICTP@=addrLink copied to clipboard

Explanation: A SNAP DUMP is written to //DACNDDMP because the condition file service failed. Further information about the reason for the failure is in the next message (IOAJ57S).

The variables in this message are:

  • user - the user session ID

  • rsn - the internal reason code

  • diag - the diagnostic code identifying the internal error code. This value is used by BMC to locate the exact place and circumstances of the error.

  • addr - the internal data address

Corrective Action: Review the job log and look for additional error messages with a prefix of IOAJ, such as IOAJ23S or a similar message, which were issued shortly before this message. If such a message is found, review the documentation for that message for a possible explanation of the source of the problem. If this does not help, or if no such preceding messages are found, save the job log and the DUMP that was produced and contact BMC Software Customer Support.

Messages IOAJV00 through IOAJVxxLink copied to clipboard

IOAJV0E INVALID VALUE, USEvalid_valueLink copied to clipboard

Explanation: An invalid value was specified for a DO ARRANGE statement. The cursor points to the field that contains the invalid value.

Valid values for

  • ON JOB is JOB

  • ON EXEC is EXEC

  • ON DD is either DD or DCB

Corrective Action: Correct the invalid value.

IOAJV1E INVALID VALUE, USEvalid_valueLink copied to clipboard

Explanation: An invalid value was specified for a verification criteria. The cursor points to the field that contains the invalid value.

Valid values for

  • JES SYNTAX are Y/N/D

  • DATASET VERIFICATION are Y/N/S/U/D

  • DATASET AUTHORIZATION are Y/N/D

  • PROGRAM EXISTENCE are Y/N/D

  • RESOLVE CONTROL-M AUTO-EDIT VARIABLE are Y/N/D

  • SITE STANDARDS RULES are Y/N/D

  • UTILITIES VALIDATION are Y/N/D

  • MESSAGES LEVEL are I/W/E/D

    where

    • D - DEFAULT

    • E - ERROR

    • I - INFORMATION

    • N - NEVER CHECK

    • S - NO SPACE CHECK

    • U - DATASET VERIFICATION FOR UTILITIES

    • W - WARNING

    • Y - ALWAYS CHECK

Corrective Action: Correct invalid value.

IOAJV2E INVALID OPTION FOR SMART TABLELink copied to clipboard

Explanation: "E" (JCL VERIFY) option was entered for table entity.

Corrective Action: Use valid option.

IOAJV3E INVALID VALUE. RULE CAN CONTAIN ONE TYPE OF "ON"Link copied to clipboard

Explanation: Related ON statement has more than one type.

Corrective Action: Delete invalid ON statement, by filling in a valid type or setting blank the O/N option of the previous ON statement.

IOAJV4E INVALID VALUE, USEvalid_valueLink copied to clipboard

Explanation: An invalid value was specified for either the O/N or SHOW ORIGINAL fields. Valid values for

  • the O/N field is O for an OR relationship, N for a NOT relationship, or blank for no additional line

  • the SHOW ORIGINAL field is Y for printing the original statement in the report, or either N or blank for not printing the original statement

Corrective Action: Fill in a valid value or leave blank.

IOAJV5E INVALID NESTING OF IF-ELSE-ENDIF. PLEASE CHECKLink copied to clipboard

Explanation: Rule definition contains invalid nesting of DO IF, DO ELSE and DO ENDIF statements.

Corrective Action: Correct nesting.

IOAJV6E INVALID NESTING. 'IF' EXPECTED PRIOR TO 'ENDIF'Link copied to clipboard

Explanation: Rule definition contains invalid nesting. DO ENDIF statement preceded DO IF statement.

Corrective Action: Correct nesting.

IOAJV7E INVALID NESTING. 'IF' EXPECTED PRIOR TO 'ELSE'Link copied to clipboard

Explanation: Rule definition contains invalid nesting. DO ELSE statement preceded DO IF statement.

Corrective Action: Correct nesting.

IOAJV8E INVALID SYNTAX - textLink copied to clipboard

Explanation: An invalid syntax is specified in a DO SET, MSG, IF, IBEFORE, IAFTER, REXX, or ENFORCE statement. The text variable contains the reason of the error.

Corrective Action: Correct the syntax error.

IOAJV9E FIRST CHARACTER CANNOT BE NUMERICLink copied to clipboard

Explanation: The first column in the field contains a numeric value, instead of an alphabetic value.

Corrective Action: Correct the value in the field so that it is an alphabetic value.

IOAJVAE INVALID VALUE, USE "I", "W" OR "E"Link copied to clipboard

Explanation: An invalid type of message was specified. The valid type is "I" for Information messages, "W" for Warning messages, or "E" for Error messages.

Corrective Action: Specify a valid message type.

IOAJVBE ONLY ONE FIELD CAN BE FILLEDLink copied to clipboard

Explanation: Only one parameter, either PGM or PROC, can be specified for an ON EXEC statement.

Corrective Action: Fill in only one field.

IOAJVCE INVALID 'ON' TYPELink copied to clipboard

Explanation: An invalid ON statement is specified in a Control-M JCL Verify rule. The valid ON types are issued by the ONOPT command of the Rule Definition screen.

Corrective Action: Specify a valid ON statement.

IOAJVDE INVALID VALUE. USE 'NEW', 'OLD', 'MOD' OR 'SHR'Link copied to clipboard

Explanation: An invalid value is specified in the DISP field of an ON DD statement.

Corrective Action: Specify a valid value for the ON DD statement.

IOAJVEE INVALID VALUE. USE 'KEEP', 'DELETE', 'UNCATLG' OR 'CATLG'Link copied to clipboard

Explanation: An invalid value is specified in the DISP field of an ON DD field.

Corrective Action: Specify a valid value.

IOAJVFE FIELD SHOULD BE EMPTY BECAUSE LIBRARY NAME IS MISSINGLink copied to clipboard

Explanation: The MEMBER field of the LIBRARY statement is specified, but the LIBRARY field is empty.

Corrective Action: Fill in the LIBRARY field, or erase the value in the MEMBER field.

IOAJVHE INVALID 'DO' TYPELink copied to clipboard

Explanation: An invalid DO statement is specified in a Control-M JCL Verify rule. The valid DO types are issued by the DOOPT command of the Rule definition screen.

Corrective Action: Specify a valid DO statement

IOAJVIE "FROM" CANNOT BE GREATER THAN "TO"Link copied to clipboard

Explanation: A value specified in the FROM field is more than a value specified in the TO field

Corrective Action: Specify correct values.

IOAJVKE FIELD MUST CONTAIN ONLY ALPHANUMERIC CHARACTERSLink copied to clipboard

Explanation: An invalid value is specified in the CLASS field of the ON JOB statement. The valid values are A-Z, 0-9, @, #, and $.

Corrective Action: Specify valid values.

IOAJVLE field_nameCAN BEstart_range_value-end_range_valueLink copied to clipboard

Explanation: An invalid value is specified in a field to which the cursor points. The valid values for the

  • PRIORITY field of the RULE statement is 1-99

  • PRTY field of the ON JOB statement is 1-99

  • FROM field of the DO COMMENT statement is 40-71

  • FROM field of the DO KEYWORDS/POS statements is 15-68

  • FROM field of the DO CONT statement is 4-15

  • FROM field of the DO ONTYPE statement is 12-16

  • TO field of the DO KEYWORDS/POS statements is 18-71

Corrective Action: Specify a correct value.

IOAJVME NESTING OF DO WHILE AND DO IF IS INCORRECTLink copied to clipboard

Corrective Action: Correct the nesting of DO WHILE and DO IF.

IOAJVNE INVALID VALUE. MESSAGE MUST BEGIN WITH CTJLink copied to clipboard

Corrective Action: Correct the message ID to start with a CTJ prefix.

IOAJVOE INVALID VALUE. BLANKS ARE NOT ALLOWEDLink copied to clipboard

Corrective Action: Correct the message ID by removing blanks.

IOAJVPE FIELD SHOULD BE EMPTY WHEN 'SAVE REPORTS' IS SET TO 'D'Link copied to clipboard

Corrective Action: Delete the values in JREPPREF, JREPVOL and JREPUNIT.

IOAJVQE CANNOT FILL 'VOLUME' WHEN 'UNIT' IS EMPTYLink copied to clipboard

Corrective Action: Define a value for JREPUNIT, or delete the value of JREPVOL.

IOAJVRE JREPVOL MUST CONTAIN A VALID VOLSER NAMELink copied to clipboard

Corrective Action: Enter a valid VOLSER name in JREPVOL.

IOAJVSE MUST ENTER A PREFIX WHEN 'SAVE REPORTS' IS SET TO 'Y'Link copied to clipboard

Corrective Action: Enter a valid prefix for the saved report files in JREPPREF.

Messages IOAL00 through IOALxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAL00I IDL FACILITY RECEIVED REQUEST (request)Link copied to clipboard

Explanation: This information message indicates that IDL facility received the specified request either through a modify command or programmatically.

In this message, request is the name of the request. Valid values are:

  • SNAP

    When this message is issued for a SNAP request, the current date is additionally issued as DATE (dd/ mm/ yyyy).

  • HELP

  • SHOWMODULES

  • SHOWGROUP

  • SHOWLEVEL

  • WTOLEVEL

  • SHOWSNAP

  • DUP={HANDLE | IGNORE}

  • SHOWMODULE={ name | mask}

  • WTOMODULE={ name | mask}

  • SHOWCSECT={ name | mask}

  • WTOCSECT={ name | mask}

  • SHOWFULL

  • SHOWUNKNOWN

  • SHOWUNIDENT

  • SHOWFOREIGN

  • SHOWSHORT

  • SHOWMEMORY={ module | address | control_block}[,{ size| FULL}]

  • REFRSUMMARY

  • DEFGROUP[= group_ID]

  • DABAPI={ENABLE | DISABLE}

Corrective Action: No action is required.

IOAL01I module csect offset length date time release apar lng fromLink copied to clipboard

Explanation: This information message specifies a line of the level information for a separate CSECT. A group of IOAL01I messages are preceded by header message IOAL02I.

The variables in this message are:

  • module - name of a module

  • csect - name of a CSECT

  • offset - offset value for the indicated CSECT, relative to the beginning of the module

  • length - CSECT length

  • date - date of compilation

  • time - time of compilation

  • release - IOA release this CSECT belongs to

  • apar - last APAR ID applied to the indicated CSECT

  • lng - language in which this CSECT is written. Valid values are:

    • ASM (Assembler)

    • S/C (SAS/C)

  • from - where this module was taken from, to identify its level. Valid values are:

    • storage - from storage

    • library - from disk

Corrective Action: No action is required.

IOAL02I MODULE CSECT OFFSET LENGTH DATE TIME RELEASE APAR LNG FROMLink copied to clipboard

Explanation: This information message is a header for a group of subsequent IOAL01I messages.

Corrective Action: No action is required.

IOAL03I size kb OF IDL DATA SUCCESSFULLY SNAPPED AT (address-time-date) sss.tt sec CPU used; DUP=dup_valueLink copied to clipboard

Explanation: This information message indicates that IDL facility successfully performed a SNAP request.

The variables in this message are:

  • size - number of kilobytes the SNAP data occupies in storage

  • address - starting address of the SNAP data in storage

  • time - time the SNAP data was written

  • date - date the SNAP data was written

  • sss.tt - number of seconds the CPU takes to generate and write the SNAP data into memory

  • dup_value - value of the DUP parameter. Valid values are:

    • HANDLE - each instance of a duplicate module is handled

    • IGNORE - only the first instance from a group of duplicate modules is handled

The DUP value is set by the program and can be replaced at any time by the DUP={ HANDLE | IGNORE } modify command.

Corrective Action: No action is required.

IOAL04I FIRST IDL SNAP REQUEST RECEIVEDLink copied to clipboard

Explanation: This information message indicates that IDL facility received the first SNAP request since startup.

Corrective Action: No action is required.

IOAL05S INTERNAL ERROR OCCURRED (error) IN IDL FACILITY, UNABLE TO CONTINUELink copied to clipboard

Explanation: The IDL facility encountered an internal problem, which is specified by the error value.

The only valid value for error is:

error

Explanation

040

The IDL facility did not discover the SNAP data, even though at least one SNAP request was already performed

The IDL facility removes itself. Normal processing of the INCONTROL product continues.

Corrective Action: No action is required.

IOAL06I IDL ENVIRONMENT REMOVED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that IDL facility has removed itself. Normally this message is issued when the INCONTROL product goes down.

Corrective Action: No action is required.

IOAL07W IDL ROUTINE (routine) FAILED WITH RC (rsn) REQUEST (request)Link copied to clipboard

Explanation: The IDL facility encountered an error when performing a request.

The variables in this message are:

  • routine - name of a routine that discovered an error

  • rsn - reason code of an error

  • request - name of the request that is performed when the IDL facility encountered a specified error

The indicated request fails.

Corrective Action: Contact BMC Customer Support.

IOAL08S FAILURE (rc) TO CREATE SNAP TOKEN FOR IDLLink copied to clipboard

Explanation: A severe error was encountered when the IDL facility tried to create an MVS token.

The IDL facility removes itself. Normal processing of the INCONTROL product continues.

Corrective Action: Contact BMC Customer Support.

IOAL09W CALL (call) OF BINDER API FAILED WITH RC (rc) REASON (rsn), MODULE (mod)Link copied to clipboard

Explanation: The IDL facility encountered the specified error when performing a Binder API call. This message is followed by one of the messages from IOAL10W-IOAL1YW or IOAL31W-IOAL3HW, which describes the reason for the failure.

Corrective Action: If necessary, contact BMC Customer Support.

You should contact BMC Customer Support if the variables in this message differ from the following:

  • RC=08

  • REASON=83000514

MODULE= mod: This means that the specified module is changed (replaced or moved) in the load library during an INCONTROL product run. This may happen when a new PTF is applied or the LOAD library is compressed.

IOAL0AI mod tcb cbName owner epa length subpool use attribute resident amode aliasLink copied to clipboard

Explanation: This information message describes a separate load module. A group of IOAL0AI messages are preceded by header message IOAL0BI.

The variables in this message are:

  • mod - name of a module

  • tcb - TCB address

  • cbName - name of the control block that controls the indicated module.

    Valid values are:

    • RB

    • LLE

  • owner - TCB address of an owner subtask

  • epa - entry point address of a module

  • length - size of a module

  • subpool - subpool number in which a module resides

  • use - use counter of a module

  • attribute - attributes of a module.

    Valid values are:

    • Rent

    • Reus

    • AC1

  • resident - area in which this module resides.

    Valid values are:

    • FLPA

    • PLPA

    • MLPA

    • JPA

    • >16

  • amode - addressing mode of a module.

    Valid values are:

    • 24

    • 31

    • ANY

  • alias - name of a module of which the indicated module is an alias.

Corrective Action: No action is required.

IOAL0BI Module TCB CB Owner EPAddrss Length SP Use Attributes Resident AMODE AliasLink copied to clipboard

Explanation: This information message is a header for a group of subsequent IOAL0AI messages.

Corrective Action: No action is required.

IOAL0CI MODULE (mod) WAS RELOADED SINCE LAST IDL SNAP (timeStamp)Link copied to clipboard

Explanation: The IDL facility discovered the specified module has been reloaded since the previous SNAP request was performed.

The variables in this message are:

  • mod - name of a module that IDL facility discovered was reloaded

  • timeStamp - timestamp of the last SNAP request before the specified module was reloaded

Corrective Action: No action is required.

IOAL0DI MODULE (mod) WAS DELETED SINCE LAST IDL SNAP (timeStamp)Link copied to clipboard

Explanation: This information message indicates that the IDL facility discovered the specified module has been deleted since the previous SNAP request was performed.

The variables in this message are:

  • mod - name of a module that IDL facility discovered was deleted

  • timeStamp - timestamp of the last SNAP request before the specified module was deleted

Corrective Action: No action is required.

IOAL0EI NEW TASK (mod / tcbAddress) STARTED SINCE LAST IDL SNAP (timeStamp)Link copied to clipboard

Explanation: This information message indicates that the IDL facility discovered that a new subtask has been started since the previous SNAP request was performed.

The variables in this message are:

  • mod - name of a main module running under the control of a new subtask

  • tcbAddress - TCB address of a new subtask

  • timeStamp - timestamp of the last SNAP request before the specified subtask started

Corrective Action: No action is required.

IOAL0FW MODULE (mod / csect) CHANGED SINCE LAST IDL SNAP (oldTimeStamp / newTimeStamp)Link copied to clipboard

Explanation: The IDL facility discovered a change in the specified module/csect, which occurred between the instances specified by two subsequent timestamps.

The variables in this message are:

  • mod - name of a module which in the IDL facility discovered a change

  • csect - CSECT of a module which in IDL facility discovered a change

  • oldTimeStamp - timestamp of the previous SNAP request

  • newTimeStamp - timestamp of the last SNAP request

Corrective Action: No action is required.

IOAL0GI APAR (old_apar/ new_apar) CODE COMPILED (old_time/ new_timeold_date-new_date)Link copied to clipboard

Explanation: This information message follows message IOAL0FW and describes the change that the IDL facility discovered in the module specified in message IOAL0FW.

The variables in this message are:

  • old_apar - last APAR ID applied to the CSECT specified by IOAL0FW before the change

  • new_apar - last APAR ID applied to the CSECT specified by IOAL0FW after the change

  • old_time - compilation time of the CSECT specified by IOAL0FW before the change

  • new_time - compilation time of the CSECT specified by IOAL0FW after the change

  • old_date - compilation date of the CSECT specified by IOAL0FW before the change

  • new_date - compilation date of the CSECT specified by IOAL0FW after the change

Corrective Action: No action is required.

IOAL0HW CSVQUERY FAILED TO GET REQUESTED DATA, RC (004)Link copied to clipboard

Explanation: The IDL facility encountered an error when performing an internal CSVQUERY request.

The current IDL request fails. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL0IW CSVQUERY FAILED TO LOCATE MODULE(mod) EPA(address)Link copied to clipboard

Explanation: The IDL facility encountered an error when performing an internal CSVQUERY request to locate the specified module.

The current IDL request fails. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL0JW CSVQUERY FAILURE: RC (rc)Link copied to clipboard

Explanation: The IDL facility encountered a failure when performing an internal CSVQUERY request.

The current IDL request fails. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL0KI OLD TASK (mod/tcbAddress) COMPLETED SINCE LAST IDL SNAP (timeStamp)Link copied to clipboard

Explanation: This information message indicates that the IDL facility discovered that a specified subtask has been completed since the previous SNAP request was performed.

The variables in this message are:

  • mod - name of a main module that ran under the control of a completed subtask

  • tcbAddress - TCB address of an old subtask

  • timeStamp - timestamp of the last SNAP request before the specified subtask was completed

Corrective Action: No action is required.

IOAL0LI BINDER API OUTPUT (DABAPI) HAS BEEN {ENABLED | DISABLED}Link copied to clipboard

Explanation: This information message is sent in response to the DABAPI={ENABLE | DISABLE} modify command issued by an operator:

  • When DABAPI=ENABLE, the DABAPI output file is enabled, and the original IBM diagnostic messages of the Binder API are sent to this output.

  • When DABAPI=DISABLE, the DABAPI output file is disabled. (Default)

Corrective Action: No action is required.

IOAL0MW INVALID GROUP SPECIFIED (group_ID), DEFAULT GROUP ID (default_group_ID) WILL BE USEDLink copied to clipboard

Explanation: An invalid group ID was specified in an IDL=SHOWGROUP= group_ID modify command issued by an operator.

The "IOA" group ID is used instead of the requested group. Processing continues.

Corrective Action: Correct the group ID and reissue the modify command.

IOAL0OW IDL FACILITY RECEIVED INVALID REQUEST (request)Link copied to clipboard

Explanation: An unknown IDL= request modify command was issued by an operator.

The invalid request is ignored.

Corrective Action: Correct the request and reissue the modify command.

IOAL0PI IDL ENVIRONMENT CREATED SUCCESSFULLY; APAR (apar) RELEASE (release) IDL (address)Link copied to clipboard

Explanation: This information message indicates that the IDL facility has been successfully started and its environment has been created.

The variables in this message are:

  • apar - last APAR ID applied to the main IDL module

  • release - IOA release to which the main IDL module belongs

  • address - area address of IDL internals

Corrective Action: No action is required.

IOAL0QW NO IDL ENVIRONMENT CREATED, RC (rc)Link copied to clipboard

Explanation: The IDL facility has failed to create its environment.

Corrective Action: Contact BMC Customer Support, specifying the return code displayed.

IOAL0RI IDL REQUEST (request) PROCESSED SUCCESSFULLY, sss.tt sec CPU used; ITEMS: item1/item2Link copied to clipboard

Explanation: This information message indicates that the IDL facility has successfully processed the IDL request.

The variables in this message are:

  • request - name of the request the IDL facility processed

  • sss.tt - CPU time that was consumed by the IDL facility to process the request

  • item1 - first output parameter of the processed request. In most cases, this variable contains the number of elements the IDL facility processed when implementing the request.

  • item2 - second output parameter of the processed request. In most cases, this variable contains the number of elements the IDL facility did not process (skipped) when implementing the request.

Corrective Action: No action is required.

IOAL0SW IDL ENVIRONMENT ALREADY EXISTSLink copied to clipboard

Explanation: The IDL facility failed to create another IDL environment, because one already exists.

Corrective Action: Contact BMC Customer Support.

IOAL0TS IDL FACILITY FAILED (rc) TO ALLOCATE ddName OUTPUT DD STATEMENT, IOALLOC (rc)Link copied to clipboard

Explanation: A severe error was encountered when the IDL facility was trying to allocate the DAPRIDL output DD statement.

The IDL environment is not created. Normal processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL0UW CSVQUERY RETURNED ZERO ENTRY POINT TOKEN FOR EPA (address)Link copied to clipboard

Explanation: The IDL facility encountered a failure when performing an internal CSVQUERY request for the specified entry point address.

The module with the specified entry point address is not processed. Normal processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL0VI BINDER API OUTPUT (DABAPI) ALREADY {ENABLED | DISABLED}Link copied to clipboard

Explanation: This information message is sent in response to the DABAPI={ENABLE | DISABLE} modify command issued by an operator:

  • When DABAPI=ENABLED, the DABAPI output file is already enabled, and the original IBM diagnostic messages of the Binder API are sent to this output.

  • When DABAPI=DISABLED, the DABAPI output file is already disabled. (Default)

Corrective Action: No action is required.

IOAL0WW BINDER API FAILED TO PROCESS MODULE (mod), NO LEVEL DATA WRITTEN; RC (rc) REASON (rsn)Link copied to clipboard

Explanation: One of the Binder API functions failed (with the specified return code and reason code) when the IDL facility tried to process the specified module.

The specified module is not processed. Normal processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL0XI mod csect offset size timeStamp release apar entrypoint-token attributes sp apfLink copied to clipboard

Explanation: A set of IOAL0XI messages is issued in response to a SHOWSNAP request. Each IOAL0XI message specifies a line of the level information for a separate CSECT.

The variables in this message are:

  • mod - name of a module

  • csect - name of a CSECT

  • offset - offset value for the indicated CSECT relative to the beginning of the module

  • size - CSECT size

  • timeStamp - time and date of the CSECT compilation

  • release - IOA release to which this CSECT belongs

  • apar - last APAR ID applied to the indicated CSECT

  • entrypoint - entry point token of the module

  • attributes - attributes of the module

  • sp - subpool number in which the module resides

  • apf - APF authorization code of the module

Corrective Action: No action is required.

IOAL0YS FAILURE TO GET STORAGE size KB FOR IDL SNAP BUFFERLink copied to clipboard

Explanation: The IDL facility failed to allocate storage for the SNAP buffer.

The IDL environment removes itself. Normal processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL0ZS IDL FAILED TO LOAD MODULE (mod)Link copied to clipboard

Explanation: The IDL facility failed to load the specified module.

The IDL environment removes itself. Normal processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL10W EDITING REQUEST FAILED DURING INCLUSION OF THE MODULELink copied to clipboard

Explanation: One or more editing requests (delete, change, or replace operations) failed during inclusion of the module.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000502.

Corrective Action: Contact BMC Customer Support.

IOAL11W INCLUDED MODULE NOT EDITABLELink copied to clipboard

Explanation: The included module was marked NOT-EDITABLE.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000505.

Corrective Action: Contact BMC Customer Support.

IOAL12W FORMAT ERROR ENCOUNTEREDLink copied to clipboard

Explanation: A format error was encountered in a module being included.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000507.

Corrective Action: Contact BMC Customer Support.

IOAL13W ERRORS ENCOUNTERED IN THE INCLUDED MODULELink copied to clipboard

Explanation: Errors were encountered in the included module.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000510.

Corrective Action: Contact BMC Customer Support.

IOAL14W RECURSIVE STATEMENT ENCOUNTEREDLink copied to clipboard

Explanation: A control statement in an included file attempted to include the file containing the statement, or include another file that, in turn, included the original file.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000511.

Corrective Action: Contact BMC Customer Support.

IOAL15W EITHER VERSION OF REQUESTED MEMBER OR TTR ADDRESS IN LIBRARY WAS CHANGEDLink copied to clipboard

Explanation: The Binder API is unable to process the indicated module, either because of its version or because the TTR address in the library was changed since the module was first loaded.

You should contact BMC Customer Support if the variables in this message differ from the following:

  • RC=08

  • REASON=83000514

MODULE= mod: This means that the specified module is changed (replaced or moved) in the load library during an INCONTROL product run. This may happen when a new PTF is applied or the LOAD library is compressed.

Corrective Action: No action is required.

IOAL16W FORMAT ERROR ENCOUNTERED IN CONTROL STATEMENTLink copied to clipboard

Explanation: A format error has been encountered in one or more control statements.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000516.

Corrective Action: Contact BMC Customer Support.

IOAL17W NAME STATEMENT ENCOUNTERED, BUT NO TARGET LIBRARY SPECIFIEDLink copied to clipboard

Explanation: A NAME control statement was encountered, but no target library (MODLIB) was specified.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000517.

Corrective Action: Contact BMC Customer Support.

IOAL18W NAME STATEMENT ENCOUNTERED IN A SECONDARY INPUT FILELink copied to clipboard

Explanation: A NAME control statement was encountered in a secondary input file.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000518.

Corrective Action: Contact BMC Customer Support.

IOAL19W ERRORS (INVALID DATA) FOUND IN A MODULE BROUGHT BY INCLUDELink copied to clipboard

Explanation: Errors (invalid data) were found in a module being brought in by an INCLUDE control statement.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000519.

Corrective Action: Contact BMC Customer Support.

IOAL1AW DATA SET OR LIBRARY MEMBER SPECIFIED BY INCLUDE STATEMENT NOT FOUNDLink copied to clipboard

Explanation: The data set or library member specified by an INCLUDE control statement could not be found.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000520.

Corrective Action: Contact BMC Customer Support.

IOAL1BW I/O ERROR WHEN READING INPUT DATA SET OR DIRECTORY SPECIFIED IN INCLUDELink copied to clipboard

Explanation: An I/O error occurred while trying to read an input data set (or directory) specified on an INCLUDE control statement.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000521.

Corrective Action: Contact BMC Customer Support.

IOAL1CW DATA SET SPECIFIED IN INCLUDE STATEMENT COULD NOT BE OPENEDLink copied to clipboard

Explanation: The input data set specified on an INCLUDE control statement could not be opened.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000522.

Corrective Action: Contact BMC Customer Support.

IOAL1DW IDENTIFY DATA CANNOT BE PROCESSED DUE TO SECTION NOT INCLUDED PRIOR TO IDENTIFY STATEMENTLink copied to clipboard

Explanation: Identify data could not be processed because the section was not included prior to the identify statement.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000527.

Corrective Action: Contact BMC Customer Support.

IOAL1EW LACK OF REQUIRED PARAMETERS FOR INTYPELink copied to clipboard

Explanation: Not all the parameters required for the specified INTYPE were provided.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000101.

Corrective Action: Contact BMC Customer Support.

IOAL1FW INCLUDE ATTEMPTED TO INCLUDE A SECOND MODULE WHEN ACCESS USEDLink copied to clipboard

Explanation: The INCLUDE call attempted to include a second module when the processing intent is ACCESS.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000500.

Corrective Action: Contact BMC Customer Support.

IOAL1GW I/O ERROR OCCURRED WHILE READING INPUT DATA SET OR ITS DIRECTORYLink copied to clipboard

Explanation: An I/O error occurred while trying to read the input data set or its directory.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000503.

Corrective Action: Contact BMC Customer Support.

IOAL1HW MODULE SUCCESSFULLY INCLUDED, BUT ALIASES OR ATTRIB OPTION COULD NOT BE HONOREDLink copied to clipboard

Explanation: The module was successfully included, but the ALIASES or ATTRIB option could not be honored because the directory was not accessible.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000504.

Corrective Action: Contact BMC Customer Support.

IOAL1IW FILE COULD NOT BE OPENEDLink copied to clipboard

Explanation: The file could not be opened.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000513.

Corrective Action: Contact BMC Customer Support.

IOAL1JW FORMAT ERROR IN THE REQUESTED MODULELink copied to clipboard

Explanation: For INTENT=ACCESS, the requested module contained a format error and was not been placed in the workmod.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000523.

Corrective Action: Contact BMC Customer Support.

IOAL1KW OPTION VALUE MISSING OR INVALIDLink copied to clipboard

Explanation: The option value is invalid for the specified keyword.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000108.

Corrective Action: Contact BMC Customer Support.

IOAL1LW OPTIONS OPTION ENCOUNTERED IN THE OPTIONS FILELink copied to clipboard

Explanation: There was a syntax error or unrecognized option in the parameter list.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000111.

Corrective Action: Contact BMC Customer Support.

IOAL1MW FAILURE TO OPEN PRINT DATA SETLink copied to clipboard

Explanation: A print data set could not be opened during initialization.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000200.

Corrective Action: Contact BMC Customer Support.

IOAL1NW INVALID OPTIONS SPECIFIED IN STARTDLink copied to clipboard

Explanation: One or more invalid options, specified in STARTD, were ignored.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000201.

Corrective Action: Contact BMC Customer Support.

IOAL1OW FAILURE TO OPEN TERM DATA SETLink copied to clipboard

Explanation: The SYSTERM data set could not be opened during initialization.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000203.

Corrective Action: Contact BMC Customer Support.

IOAL1PW CURRENT TIME IS UNAVAILABLE FROM THE OPERATING SYSTEMLink copied to clipboard

Explanation: The date and time could not be obtained from the operating system.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000205.

Corrective Action: Contact BMC Customer Support.

IOAL1QW FAILURE TO OPEN SYSTERM DATA SETLink copied to clipboard

Explanation: The data set or file allocated to TERM could not be found.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000206.

Corrective Action: Contact BMC Customer Support.

IOAL1RW FAILURE TO OPEN SYSPRINT DATA SETLink copied to clipboard

Explanation: The data set or file allocated to PRINT could not be found.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000207.

Corrective Action: Contact BMC Customer Support.

IOAL1SW WORKMOD IA IN AN ALTERED STATE AND PROTECT=YES SPECIFIEDLink copied to clipboard

Explanation: The workmod was in an altered state, but PROTECT=YES was specified.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000707.

Corrective Action: Contact BMC Customer Support.

IOAL1TW BUFFER IS NOT LARGE ENOUGH FOR ONE RECORDLink copied to clipboard

Explanation: The buffer is too small for a single record.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000750.

Corrective Action: Contact BMC Customer Support.

IOAL1UW REQUESTED ITEM DID NOT EXIST OR EMPTYLink copied to clipboard

Explanation: The requested element was not found or was empty.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000801.

Corrective Action: Contact BMC Customer Support.

IOAL1VW BUFFER VERSION INCOMPATIBLE WITH THE MODULE CONTENTLink copied to clipboard

Explanation: The workmod data is incompatible with the specified buffer version.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000813.

Corrective Action: Contact BMC Customer Support.

IOAL1WW WORKMOD IS IN AN UNBOUND STATELink copied to clipboard

Explanation: The workmod was in an unbound state. GET calls are not allowed.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000102.

Corrective Action: Contact BMC Customer Support.

IOAL1XW UNEXPECTED CONDITION OCCURRED WHILE ENDING THE DIALOGLink copied to clipboard

Explanation: An unexpected condition occurred while ending the dialog.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000704.

Corrective Action: Contact BMC Customer Support.

IOAL1YW ONE OR MORE WORKMODS WERE IN AN ACTIVE STATE AND PROTECT=YESLink copied to clipboard

Explanation: One or more workmods were in an active state, and PROTECT=YES was specified or defaulted.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000708.

Corrective Action: Contact BMC Customer Support.

IOAL1ZW THERE IS NO IDL MESSAGE FOR THE INDICATED REASON AND RC COMBINATIONLink copied to clipboard

Explanation: The IDL facility does not recognize the RC and Reason combination returned by the Binder API.

Corrective Action: Contact BMC Customer Support.

IOAL21I SHOWMODULES - SHOW MAP OF THE ADDRESS SPACELink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWMODULES command: to display all modules and tasks running in an address space.

Corrective Action: No action is required.

IOAL22I SHOWGROUP[=...] - SHOW IDL INFO ABOUT GROUP OF MODULES PRE-DEFINED IN SUMMARY TABLELink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWGROUP[=...] modify command: to display IDL information about a group of modules predefined in the IOALSUM table.

Corrective Action: No action is required.

IOAL24I SHOWSNAP - SHOW CONTENTS OF THE LAST IDL SNAPLink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWSNAP modify command: to display the contents of the last IDL snapshot.

Corrective Action: No action is required.

IOAL27I HELP - SHOW LIST OF AVAILABLE MODIFY COMMANDSLink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the HELP modify command: to display a list of available IDL modify commands.

Corrective Action: No action is required.

IOAL2CI SNAP - WRITE DOWN IDL SNAP INTO MEMORYLink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SNAP modify command: to generate and write IDL snapshots into memory.

Corrective Action: No action is required.

IOAL2DI SHOWMODULE - SHOW IDL INFO ABOUT SPECIFIC MODULE OR MODULES[*]Link copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWMODULE modify command: to display IDL information about a specific module or modules.

Corrective Action: No action is required.

IOAL2EI WTOMODULE - WTO IDL INFO ABOUT SPECIFIC MODULE OR MODULES[*]Link copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the WTOMODULE modify command: to display IDL information on the console about a specific module or modules.

Corrective Action: No action is required.

IOAL2FI SHOWCSECT - SHOW IDL INFO ABOUT SPECIFIC CSECT OR CSECTS[*]Link copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWCSECT modify command: to display IDL information about a specific CSECT or CSECTs.

Corrective Action: No action is required.

IOAL2GI WTOCSECT - WTO IDL INFO ABOUT SPECIFIC CSECT OR CSECTS[*]Link copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the WTOCSECT modify command: to display IDL information on the console about a specific CSECT or CSECTs.

Corrective Action: No action is required.

IOAL2HI SHOWFULL - SHOW *FULL* IDL INFO ABOUT ENTIRE RUNNING CODELink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWFULL modify command: to display full IDL information about currently running code.

Corrective Action: No action is required.

IOAL2II SHOWLEVEL - SHOW MAIN IDL INFO ABOUT ENTIRE RUNNING CODELink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWLEVEL modify command: to display the main IDL information about the currently running code.

Corrective Action: No action is required.

IOAL2JI WTOLEVEL - WTO MAIN IDL INFO ABOUT ENTIRE RUNNING CODELink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the WTOLEVEL modify command: to display the main IDL information on the console about the currently running code.

Corrective Action: No action is required.

IOAL2KI SHOWUNKNOWN - SHOW LIST OF UNKNOWN ELEMENTsLink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWUNKNOWN modify command: to display a list of CSECTs unknown to the IDL facility.

Corrective Action: No action is required.

IOAL2LI SHOWUNIDENT - SHOW LIST OF KNOWN BUT UNIDENTIFIED ELEMENTsLink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWUNIDENT modify command: to display a list of the CSECTs that are known to the IDL facility but are unidentified.

Corrective Action: No action is required.

IOAL2MI SHOWFOREIGN - SHOW LIST OF FOREIGN (NON-BMC) ELEMENTsLink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWFOREIGN modify command: to display a list of foreign CSECTs, that is, CSECTs not proprietary to BMC.

Corrective Action: No action is required.

IOAL2NI SHOWSHORT - SHOW LIST OF ELEMENTs THAT ARE TOO SHORT TO BE IDENTIFIEDLink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWSHORT modify command: to display a list of CSECTs too short to be identified.

Corrective Action: No action is required.

IOAL2OI SHOWMEMORY - DISPLAY MEMORY, MODULE OR CONTROL BLOCK (DATRACE OUTPUT)Link copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the SHOWMEMORY modify command: to print memory, module, or control block into DATRACE output.

Corrective Action: No action is required.

IOAL2PI REFRSUMMARY - REFRESH SUMMARY TABLELink copied to clipboard

Explanation: This information message indicates that an operator issued the IDL=HELP modify command and the IDL facility displayed the usage of the REFRSUMMARY modify command: to dynamically refresh the IOALSUM summary table.

Corrective Action: No action is required.

IOAL2QI DUP={ handle | ignore } - ALTER TREATING OF DUPLICATE MODULEsLink copied to clipboard

Explanation: This information message is the response to the modify command IDL=HELP showing the DUP= IDL sub-command:

  • handle - duplicate modules are handled as they are the original module.

  • ignore - ignore duplicate modules. The first found module entry will contain the module description.

For more information about the Identity Level (IDL) facility, see the chapter about IOA administration in the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

IOAL2RI DEFGROUP= - SET or CHANGE DEFAULT ID OF A GROUP OF MODULEs PRE-DEFINED IN SUMMARY TABLELink copied to clipboard

Explanation: This information message is the response to the modify command IDL=HELP showing the DEFGROUP= IDL sub-command.

For more information about the Identity Level (IDL) facility, see the chapter about IOA administration in the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

IOAL2UI SNAPs CANNOT BE COMPARED: DUPLICATE MODULEs TREATING HAS CHANGEDLink copied to clipboard

Explanation: This information message indicates that the IDL facility cannot compare two snap tables because the duplicate mode was different when the two snap tables were made.

For more information about the Identity Level (IDL) facility, see the chapter about IOA administration in the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

IOAL2VI DUPLICATE MODULEs WILL BE ={handle | ignore}. ; DEFAULT GROUP ID (groupId)Link copied to clipboard

Explanation: This information message indicates how duplicate modules will be handled when found (duplicate mode):

  • handle - duplicate modules are handled as they are the original module.

  • ignore - ignore duplicate modules. The first found module entry will contain the module description.

For more information about the Identity Level (IDL) facility, see the chapter about IOA administration in the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

IOAL2WI HANDLING OF DUPLICATE MODULEs HAS BEEN ={ handle | ignore }Link copied to clipboard

Explanation: This information message is the response to the modify command IDL= DUP={ handle | ignore } and indicates how the IDL facility handles duplicates modules:

  • handle - duplicate modules are handled as they are the original module.

  • ignore - ignore duplicate modules. The first found module entry will contain the module description.

For more information about the Identity Level (IDL) facility, see the chapter about IOA administration in the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

IOAL2XW MEMORY {address | size} IS NOT ALLOCATEDLink copied to clipboard

Explanation: This message indicates that the IDL facility received the SHOWMEMORY request; however, it has become clear that the specified memory is unavailable.

The current request fails. Processing continues.

Corrective Action: Correct and re-issue the SHOWMEMORY request.

IOAL2YE FAILURE (code) TO {PROCESS | REFRESH} SUMMARY TABLE, SHOWGROUP SUPPORT DISABLEDLink copied to clipboard

Explanation: The IDL facility failed to process or refresh the IOALSUM summary table.

The SHOWGROUP request is disabled.

Corrective Action: Try to correct the IOALSUM table and recycle the product. If this does not resolve the problem, contact BMC Customer Support.

IOAL2ZI SUMMARY TABLE HAS BEEN {PROCESSED | REFRESHED} SUCCESSFULLY ADDRESS (add)Link copied to clipboard

Explanation: This information messages indicates that the IDL facility successfully processed or refreshed the IOALSUM summary table.

Corrective Action: No action is required.

IOAL30W ALL MODULES PROVIDED BY provider WILL NOT BE TRACKED BY IDLLink copied to clipboard

Explanation: The Binder API will not handle any module retrieved from the provider system area.

In this message, the only valid value for provider is LLA.

Corrective Action: No action is required.

IOAL31W DATA INCOMPATIBLE WITH BUFFER VERSIONLink copied to clipboard

Explanation: The workmod data is incompatible with the specified buffer version.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 08 and a reason code of 83000813.

No data is returned. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL32W INVALID WORKMOD TOKENLink copied to clipboard

Explanation: An invalid workmod token was received.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000001.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL33W INVALID DIALOG TOKENLink copied to clipboard

Explanation: An invalid dialog token was received.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000002.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL34W BINDER INVOKED FROM WITHIN USER EXITLink copied to clipboard

Explanation: A binder was invoked from within a user exit.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000003.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL35W INVALID FUNCTION CODE SPECIFIEDLink copied to clipboard

Explanation: An invalid function code was specified.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000004.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL36W INVALID PARAMETERLink copied to clipboard

Explanation: An invalid call parameter was specified.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000005.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL37W PASSED SYMBOL CONTAINS UNACCEPTABLE CHARACTERSLink copied to clipboard

Explanation: A symbol passed in the parameter list contains characters outside the range acceptable to the binder.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000007.

The current request to the IDL facility fails. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL38W WRONG NUMBER OF ARGUMENTS SPECIFIEDLink copied to clipboard

Explanation: The wrong number of arguments was specified.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000008.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL39W PARAMETER LIST CONTAINS INVALID ADDRESSLink copied to clipboard

Explanation: One or more parameters not accessible by the binder.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000009.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3AW PARAMETER LIST IS NOT ADDRESSABLE BY THE BINDERLink copied to clipboard

Explanation: The parameter list was not addressable by the binder.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000010.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3BW IMPROPER COMBINATION OF PARAMETERSLink copied to clipboard

Explanation: An invalid combination of parameters was specified.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 12 and a reason code of 83000101.

The request was rejected. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3CW STORAGE LIMIT ESTABLISHED BY WORKSPACE OPTION EXCEEDEDLink copied to clipboard

Explanation: The storage limit established by the workspace option was exceeded.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 16 and a reason code of 83000050.

The dialog was terminated. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3DW INSUFFICIENT STORAGE AVAILABLELink copied to clipboard

Explanation: Insufficient storage was available.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 16 and a reason code of 83000051.

The dialog was terminated. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3EW OPERATING SYSTEM NOT AT CORRECT DFSMS/MVS LEVELLink copied to clipboard

Explanation: The operating system was not at the correct DFSMS/MVS level. No dialog was established and the requested function was not processed.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 16 and a reason code of 83000060.

The current request to the IDL facility fails. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3FW IEWBIND MODULE COULD NOT BE LOADEDLink copied to clipboard

Explanation: The IEWBIND module could not be loaded.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 16 and a reason code of 83000FFF.

The current request to the IDL facility fails. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3GW BINDER LOGIC ERRORLink copied to clipboard

Explanation: A binder logic error occurred.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 16 and a reason code of 83EE2900.

The dialog was terminated. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3HW BINDER ABEND OCCURRED WITH AAA ABEND COMPLETION CODELink copied to clipboard

Explanation: A binder abend occurred with a system abend completion code of AAA.

This message is preceded by message IOAL09W, which contains a specific combination of return and reason codes returned by the IBM Binder API. For further explanation of the Binder API, see the IBM manual z/OS MVS Program Management: Advanced Facilities. In this case, message IOAL09W contains a return code of 16 and a reason code of 83FFAAA0.

The dialog was terminated. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAL3YW IDL RECOVERY EXIT INTERCEPTED ABEND(abCode); PROCESSING WILL BE RETRIEDLink copied to clipboard

Explanation: The Recovery exit of the IDL facility intercepted an abend (abCode) that took place in IDL code, and an attempt will be made to retry processing.

The following system actions occur:

  • A DUMP is issued.

  • The IDL facility is disabled.

  • The ABEND is contained and processing continues.

Corrective Action: Forward the DUMP to BMC Customer Support.

IOAL3ZW IDL RECOVERY EXIT INTERCEPTED ABEND(abCode); IMPOSSIBLE TO RETRYLink copied to clipboard

Explanation: The Recovery exit of the IDL facility intercepted an abend (abCode) that took place in IDL code, and an attempt to retry processing is not possible.

The following system actions occur:

  • A DUMP is issued.

  • The ABEND is percolated.

Corrective Action: Forward the DUMP to BMC Customer Support.

IOAL41I INITIALIZING IOAIDLLink copied to clipboard

Explanation: This information message indicates that the program is going to initialize the IDL facility.

Corrective Action: No action is required.

IOAL42W FAILED TO RELEASE DESB BLOCKLink copied to clipboard

Explanation: The program failed to release the memory allocated for the DESB block.

Corrective Action: No action is required.

IOAL43I TERMINATING IOAIDLLink copied to clipboard

Explanation: This information message indicates that the program is going to terminate the IDL facility.

Corrective Action: No action is required.

IOAL44W FAILED TO TERMINATE IDLLink copied to clipboard

Explanation: The program failed to terminate the IDL facility.

Corrective Action: No action is required.

IOAL45W FAILED TO CLOSE THE LOAD DATA SETLink copied to clipboard

Explanation: The program failed to close the load data set.

Corrective Action: No action is required.

IOAL46I CREATING THE SORT CONTROL STATEMENTLink copied to clipboard

Explanation: This information message indicates that the program is going to create the sort control statement.

Corrective Action: No action is required.

IOAL47E FAILED TO CLOSE THE DAPRMDF DATA SETLink copied to clipboard

Explanation: The program failed to close the data set containing the sort control statement

The program terminates with a return code of 8.

Corrective Action: No action is required.

IOAL48W FAILED TO RELEASE THE STORAGELink copied to clipboard

Explanation: The program failed to release the previously allocated storage.

Corrective Action: No action is required.

IOAL49E FAILED TO SETUP ESTAELink copied to clipboard

Explanation: The program failed to setup the recovery routine.

The program terminates with a return code of 8.

Corrective Action: No action is required.

IOAL4AE I/O ERROR OCCURED DURING PROCESSING DAPRIDLLink copied to clipboard

Explanation: The program failed while processing the data set allocated to DAPRIDL.

The program terminates with a return code of 12.

Corrective Action: Fix the data set’s allocation attributes in the job.

IOAL4BE BAD PARAMETER RECEIVEDLink copied to clipboard

Explanation: The program received an invalid parameter.

The program terminates with a return code of 8.

Corrective Action: Fix the program’s PARM string in the job.

IOAL4CE IOASTOR GETMAIN FAILEDLink copied to clipboard

Explanation: The program failed to allocate storage below the line.

The program terminates with a return code of 8.

Corrective Action: Increase the REGION and rerun the program.

IOAL4DE FAILED TO OPEN THE LOAD DATA SETLink copied to clipboard

Explanation: The program failed to open the load data set.

The program terminates with a return code of 8.

Corrective Action: Ensure that the load data set can be opened.

IOAL4EE FAILED TO OPEN THE DAPRMDF DATA SETLink copied to clipboard

Explanation: The program failed to open the sort control statement data set.

The program terminates with a return code of 8.

Corrective Action: Ensure that the DAPRMDF data set can be opened.

IOAL4FE FAILED TO PUT TO DAPRMDF DATA SETLink copied to clipboard

Explanation: The program failed to put the data into the sort control statement data set.

The program terminates with a return code of 12.

Corrective Action: Fix the allocation attributes of the data set in the job.

IOAL4GE DESERV FAILEDLink copied to clipboard

Explanation: The program failed during execution of the DESERV macro.

The program terminates with a return code of 12.

Corrective Action: Check the validity of the load data set definition.

IOAL4HE IOAIDL INITIALIZATION FAILEDLink copied to clipboard

Explanation: The program failed to initialize the IDL facility.

The program terminates with a return code of 8.

Corrective Action: Check the IDL facility trace messages in order to detect the source of the problem.

IOAL4IE BLDL FAILED FOR THE MODULE modNameLink copied to clipboard

Explanation: The BLDL macro failed for the modName module.

The program terminates with a return code of 12.

Corrective Action: Check the properties of the modName module.

IOAL4JE TERMINATING BECAUSE LOAD FAILURELink copied to clipboard

Explanation: The program failed to load a member from the load data set.

The program terminates with a return code of 12.

Corrective Action: No action is required.

IOAL4KE IOAIDL SHOWGROUP FAILEDLink copied to clipboard

Explanation: The IDL facility failed to execute the SHOWGROUP request.

The program terminates with a return code of 12.

Corrective Action: Check the IDL facility trace messages to detect the source of the problem.

IOAL4LI GROUPID: groupIdLink copied to clipboard

Explanation: This message is issued for a SHOWGROUP request. In this message, groupId is a predefined group of modules, as listed in the IOALSUM Summary Table.

Corrective Action: No action is required.

Messages IOAM00 through IOAMxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAM01I FUNCTIONAL MONITOR STARTEDLink copied to clipboard

Explanation: This information message indicates that the Functional monitor was started.

Corrective Action: No action is required.

IOAM02E FUNCTIONAL MONITOR NOT APF-AUTHORIZEDLink copied to clipboard

Explanation: The Functional monitor is not APF authorized. The IOAFMON module is not in an APF authorized library, and it does not have the AC=1 attribute.

The Functional monitor ends with a return code of 8.

Corrective Action: Add the name of the library in which IOAFMON resides to the IEAAPF00 member in the SYS1.PARMLIB library.

IOAM03E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:Link copied to clipboard

Explanation: An invalid parameter was passed to the Functional monitor by means of a modify command. Following this message, one or copies of message IOAM14I appear on the operator console, each containing a valid modify parameter.

The modify command is ignored.

Corrective Action: Specify the modify command with a valid parameter.

IOAM04E BLDL/ATTACH FAILED FOR SUBTASK taskNameLink copied to clipboard

Explanation: Initialization of one of the Functional monitor subtasks failed. Possible causes are:

  • The specified subtask is not found in the IOA LOAD library.

  • Insufficient storage is available for the Functional monitor.

The Functional monitor shuts down.

Corrective Action: Call your system programmer for assistance. If necessary, increase the region size of the Functional monitor.

IOAM05E UNRECOVERABLE ERROR ENCOUNTEREDLink copied to clipboard

Explanation: An unrecoverable error occurred in the IOA Functional Monitor.

The IOA Functional Monitor stops running.

Corrective Action: Check for any accompanying message that describe the nature of the problem, correct accordingly, and restart the monitor.

IOAM06E ONE OF THE FUNCTIONAL MONITOR SUBTASKS HAS ABENDEDLink copied to clipboard

Explanation: A subtask of the Functional monitor abended.

The Functional monitor shuts down with user abend 0006. A dump of the abending subtask is included in the SYSABEND output file.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

IOAM07I SHUT DOWN ON REQUEST FROM OPERATORLink copied to clipboard

Explanation: This information message indicates that an operator command requesting shutdown of the Functional monitor was issued.

The Functional monitor starts to shut down.

Corrective Action: No action is required.

IOAM10W FUNCTIONAL MONITOR IS ALREADY ACTIVE. QNAME "qName"Link copied to clipboard

Explanation: A Functional monitor was started with the same QNAME as an already active Functional monitor. It is impossible to run two Functional monitors with the same QNAME at the same time.

The newly started Functional monitor is shut down.

Corrective Action: No action is required.

IOAM11I FUNCTIONAL MONITOR SHUTTING DOWNLink copied to clipboard

Explanation: This information message indicates that the Functional monitor is shutting down. Messages describing the reason for the shutdown are in at least one of the following:

  • The IOA Log.

  • The Functional monitor JES messages file.

  • The Functional monitor SYSPRINT file.

Corrective Action: If the shutdown was not requested, check messages in the above mentioned locations for more information on the reasons for the shutdown.

IOAM12S FUNCTIONAL MONITOR ENDED WITH ERRORLink copied to clipboard

Explanation: The Functional monitor ended with an error. Messages describing the error may be in the following locations:

  • The IOA Log.

  • The Functional monitor JES messages file.

  • The Functional monitor SYSPRINT file.

The Functional monitor shuts down.

Corrective Action: Check the above mentioned locations for the reasons for the error. If necessary, ask your system programmer for assistance

IOAM13E INTERVAL MUST BE A TWO-DIGIT NUMBER BETWEEN 03 AND 99 SECONDSLink copied to clipboard

Explanation: An invalid Functional monitor Sleeping Interval was specified in a modify command. The Functional monitor Sleeping Interval is specified in seconds. It must be a 2-digit value from 03 through 99.

The modify command is ignored.

Corrective Action: Enter the following modify command with a valid sleeping interval: F monitorname,INTERVAL=xx

IOAM14I valid_parmLink copied to clipboard

Explanation: An invalid parameter was specified for a modify command. In this message, valid_parm is a valid modify parameter for the relevant command. This information message follows message IOAM03E. It may be issued more than once, with each occurrence specifying another valid parameter.

Corrective Action: No action is required.

IOAM15I FUNCTIONAL MONITOR INTERVAL IS SET TO "nn " SECONDSLink copied to clipboard

Explanation: This information message indicates that the specified Functional monitor sleeping interval (nn) has been set by means of a modify command.

Corrective Action: No action is required.

IOAM16S INSUFFICIENT MEMORY FOR IOA FUNCTIONAL MONITORLink copied to clipboard

Explanation: The available storage is insufficient for execution of the Functional monitor.

The Functional monitor shuts down.

Corrective Action: Increase the region size and restart the Functional monitor.

IOAM17S SEVERE INTERNAL ERROR WHILE PROCESSING AUTOEDIT INSTRUCTIONS, RC=rc SERVICE servLink copied to clipboard

Explanation: An internal error was detected during the AutoEdit initialization phase of the specified service. In this message, rc is the return code from the AutoEdit initialization phase.

The service is shut down, and as a result the Functional monitor shuts down.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

IOAM18I UNSERVICEABLE REQUEST FROM taskName. TYPE: taskType. REQUEST IGNOREDLink copied to clipboard

Explanation: When an input task attempted to place a request in queue for the Functional monitor no executor was found in the IOAFMON table for this request. This message indicates an internal error.

The variables in this message are:

  • taskName - the name of the input task.

  • taskType - the type of request.

The request is ignored.

Corrective Action: Contact BMC Customer Support.

IOAM19S SERVICE service CANNOT PROCESS REQUESTS FROM TYPE "type"Link copied to clipboard

Explanation: An internal error occurred during the validity checks phase of the specified service.

The service is shut down and as a result the Functional monitor shuts down.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

IOAM20S INTERNAL ERROR IN FUNCTIONAL MONITOR. RC=rcLink copied to clipboard

Explanation: The Functional monitor encountered a severe internal error.

The Functional monitor shuts down.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

IOAM21S SERVICE serv FAILED TO LOAD MODULE CTMJSPLink copied to clipboard

Explanation: The specified service failed to load the CTMJSP module. Possible causes are:

  • The IOA LOAD library is not in the load modules search list.

  • Insufficient memory is available to load the CTMJSP module.

  • The CTMJSP module does not exist in the IOA LOAD library.

The service shuts down and, as a result, the Functional monitor shuts down.

Corrective Action: Correct the problem and restart the Functional monitor.

IOAM22S INSUFFICIENT MEMORYLink copied to clipboard

Explanation: The IOAFCPL utility was unable to obtain the necessary main storage.

The IOAFCPL utility is ended.

Corrective Action: Increase the region size for the IOAFCPL utility.

IOAM23S CANNOT OPEN FMLOG FILELink copied to clipboard

Explanation: An attempt to open the Functional monitor Log failed. The FMLOG DD statement may be missing or in error in the JCL of the Functional monitor.

The Functional monitor is shut down.

Corrective Action: Check and correct the FMLOG DD statement. Restart the Functional monitor.

IOAM24S FMLOG FILE IS FULLLink copied to clipboard

Explanation: Either the Functional monitor or the IOAFCPL utility determined that writing the next record into the FMLOG file would destroy previously written information that is not yet obsolete. FMLOG is a cyclic file with periodic checkpoints. A checkpoint is a record of all information in the queue of the functional monitor at a given time. Possible causes are:

If the FMLOG file is too small, this message may result from an attempt to write a new checkpoint to the FMLOG file. If an FMLOG file bigger than 100 tracks is allocated, it will never become full, thereby preventing the problem indicated by this message.

The Functional monitor shuts down.

Corrective Action: Allocate a bigger FMLOG file, and copy the contents of the old file into the new one by means of the IOAFCPL utility.

IOAM25S LOGICAL ERROR IN FMLOG. RESTORE FMLOG FROM BACKUP OR ALLOCATE A NEW FILELink copied to clipboard

Explanation: The last checkpoint could not be found in the Functional monitor Log (FMLOG). The FMLOG file is unusable. This message indicates an internal error.

The program that issued this message is terminated.

Corrective Action: Suggested actions:

  • Allocate a new FMLOG file, or restore it from backup and restart the Functional monitor.

  • Report the problem to BMC Customer Support, and supply a copy of the FMLOG file, the IOA Log, and output from the last IOAFMON execution.

IOAM26W SHOUT DESTINATION TABLE dest_table WAS NOT LOADEDLink copied to clipboard

Explanation: Loading of the shout destination table (dest_table) failed. Possible causes are:

  • The IOA LOAD library is not in the load modules search list.

  • Insufficient memory is available to load the dest_table member.

  • The dest_table member does not exist in the LOAD library.

Corrective Action: Correct the problem and issue the modify command with the NEWDEST parameter.

IOAM27E NEWDEST PARAMETER MISSING OR INVALIDLink copied to clipboard

Explanation: Invalid NEWDEST command was given to Functional monitor. Valid format is NEWDEST or NEWDEST=dest_table.

The modify command is rejected.

Corrective Action: Enter a valid NEWDEST modify command.The format is: F monitorname,NEWDEST/NEWDEST=dest_table.

IOAM28I FORMATTING FMLOG FILELink copied to clipboard

Explanation: This information message indicates that the Functional monitor now starting, determined that the FMLOG is in an invalid format.

The Functional monitor reformats the FMLOG file.

Corrective Action: No action is required.

IOAM29S I/O ERROR: explanLink copied to clipboard

Explanation: I/O error occurred on FMLOG the file. In this message, explanation is the information provided about this error by MVS macro SYNADAF.

The program that issued this message is terminated.

Corrective Action: Allocate a new FMLOG file, or restore the old one from backup. If the text in this message indicates a software related problem, report it to BMC Customer Support and send a copy of the FMLOG file.

IOAM30I NEWDEST COMMAND ACCEPTED: NEWDEST=dest_tableLink copied to clipboard

Explanation: This information message indicates that a NEWDEST operator command was passed to Functional monitor and was accepted.

The Functional monitor directs shout messages according to the new destination table.

Corrective Action: No action is required.

IOAM33S FUNCTIONAL MONITOR INITIALIZATION PHASE FAILEDLink copied to clipboard

Explanation: The initialization phase of the Functional monitor failed. Messages describing the error can be found in the following locations:

  • the IOA Log

  • the Functional monitor JES messages file

  • the Functional monitor SYSPRINT file

The Functional monitor shuts down.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

IOAM34I USER EXIT IOAX038 WAS NOT LOADEDLink copied to clipboard

Explanation: This information message indicates that user exit IOAX038 is not active. The exit was probably deleted. Exit IOAX038 checks each request to be written to the request queue.

Processing proceeds without checking requests written to the request queue.

Corrective Action: Check if exit IOAX038 was deleted from the IOA Load library. Notify your INCONTROL administrator.

IOAM35I REQUEST FROM taskName TYPE taskType REJECTED BY exitNameLink copied to clipboard

Explanation: An exit called to validate a request produced a non-zero return code.

The variables in this message are:

  • taskName - The name of the input subtask that supplied the request.

  • taskType - The request type.

  • exitName - The exit that rejected the request. In this message, IOAX038 or IOASE38.

The request is not processed.

Corrective Action: No action is required.

IOAM36W DO-SET REQUEST FAILED. MEMBER=memName, DSN=dsn, LINE=linLink copied to clipboard

Explanation: Processing of a DO SET request failed. The Functional monitor failed to add the specified line to the specified member in the dsn data set.

The Functional monitor does not perform this DO SET command, and proceeds to handle subsequent requests.

Corrective Action: For more information, look for previous messages in the IOA Log and in the DASETPRT DD statement, which is allocated by the Functional monitor.

IOAM37I DO-SET REQUEST PERFORMED. MEMBER=memName, DSN=dsn, LINE=linLink copied to clipboard

Explanation: This information message indicates that a DO SET request was successfully performed. The Functional monitor inserted the lineNum line into the memName member in the dsn data set.

Corrective Action: No action is required.

IOAM38S CANNOT OPEN THE type FILELink copied to clipboard

Explanation: Open failed for input or output file. The DD statement specifying this file is either missing or in error.

In this message, type is the type of file that failed to open. Valid values are:

  • INPUT

  • OUTPUT.

The program that issued this message is terminated.

Corrective Action: Correct the JCL and restart the program.

IOAM39S INCORRECT FORMAT OF INPUT FILELink copied to clipboard

Explanation: The input file specified for the IOAFCPL utility is not in correct FMLOG format.

The IOAFCPL utility is terminated.

Corrective Action: Verify that the FMLOGI DD statement points to a valid FMLOG file.

Messages IOAP00 through IOAPxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAP01I - IOAP2AI Information messages issued by the IOADPT utility to display IOA Access Method file data component attributes as they are in the control record.Link copied to clipboard

Explanation: These messages are issued by the IOADPT utility when FUNC=DB0 is specified.

Corrective Action: No action is required.

IOAP2BI ESTIMATED FREE SPACE num%Link copied to clipboard

Explanation: This information message displays the estimated percentage of free space remaining in an IOA Access Method file.

Corrective Action: No action is required.

IOAP2EW SECONDARY SPACE IS NOT DEFINED FOR THE USER FILE dsnLink copied to clipboard

Explanation: This warning message indicates that the secondary space is not defined for the user file dsn. The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

The utility continues processing, however, when the utility finishes it ends with a return code of 4.

Corrective Action: Use the following procedure to resolve this issue:

  1. Check the User file definitions in the DEFxxx member

  2. Specify secondary space in the DEFxxx member

  3. Run the IOADBF utility with the FUNC parameter set to CHANGE

IOAP2FW AUTOMATIC ALLOCATION OF NEW EXTENTS IS NOT DEFINED FOR THE USER FILE dsnLink copied to clipboard

Explanation: This warning message indicates that the option to automatically extend the file is not specified for the user file dsn. The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

The utility continues processing, however, when the utility finishes it ends with a return code of 4.

Corrective Action: Use the following procedure to resolve this issue:

  1. Check the User file definitions in the DEFxxx member.

  2. Specify EXTEND=A in the DEFxxx member

  3. Run the IOADBF utility with the FUNC parameter set to CHANGE

IOAP2GW NUMBER OF EXTENTS FOR THE USER FILE dsn MORE THEN 50Link copied to clipboard

Explanation: This warning message indicates that the number of extents for the specified user file dsn is more then 50. This warning is issued because a large number of extents can adversely impact performance when accessing the user file. The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

The utility continues processing, however, when the utility finishes it ends with a return code of 4.

Corrective Action: Check the User file definitions in the DEFxxx member. If the reason of for the large number of extents is a small secondary space definition, increase the space values in the DEFxxx member. Then perform a reorganization of the User file reformatting the files with the new SPACE parameters.

IOAP2IW FREE SPACE IN THE USER FILE dsn REACHED THE THRESHOLD CAPACITYLink copied to clipboard

Explanation: This warning message indicates that the free space in the specified user file dsn has reached the threshold capacity and neither the secondary space or the automatically extend option were specified. This warning message is issued when one of the following conditions is true:

  • estimated free space in the Data component is less then 15 percent of the total space

  • free space in the Index component is less then 5 percent of the total space

The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

Corrective Action: Check the User file definitions in the DEFxxx member. If the reason of for the large number of extents is a small secondary space definition, increase the space values in the DEFxxx member. Then perform a reorganization of the User file reformatting the files with the new SPACE parameters.

IOAP30I IOAPFSTC UTILITY STARTED Link copied to clipboard

Explanation: This information message indicates that the IOAPFSTC utility, which prints IOA Application Server performance statistic reports, started.

Corrective Action: No action is required.

IOAP31E INVALID PARAMETER: parm Link copied to clipboard

Explanation: The parm input parameter specified for the IOAPFSTC utility is not valid.

The utility stops with return code 16.

Corrective Action: Correct the invalid input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP32E REDUNDANT PARAMETER: parm Link copied to clipboard

Explanation: The parm input parameter for IOAPFSTC utility is specified twice although it can only be specified once in this statement.

The utility stops with return code 16.

Corrective Action: Remove the redundant input parameter from the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP33E INVALID LENGTH OF PARAMETER parm Link copied to clipboard

Explanation: The length of the parm input parameter is not available for this parameter.

The utility stops with return code 16.

Corrective Action: Correct the invalid input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP34E REQUIRED PARAMETER parmIS NOT SPECIFIEDLink copied to clipboard

Explanation: The obligatory parm input parameter is not specified in the input stream for the IOAPFSTC utility.

The utility stops with return code 16.

Corrective Action: Correct the input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP35E INCORRECT COMBINATION OF DATEFROM AND DATETO VALUESLink copied to clipboard

Explanation: The end date specified in the parameter DATETO is less than the beginning date specified in the parameter DATEFROM.

The utility stops with return code 16.

Corrective Action: Correct the input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP36W PARAMETER parm IS IGNORED FOR FUNCTION=CLEANLink copied to clipboard

Explanation: This warning message is issued when the parm parameter is specified for FUNCTION=CLEAN in the IOAPFSTC utility input parameters. No additional parameters are processed for FUNCTION=CLEAN. The parm parameter is ignored.

Corrective Action: Check the input parameters specified for the utility. Correct the parameters and resubmit the job if it is necessary. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP3AW NO PERFORMANCE STATISTIC RECORDS IN PERMANENT USER FILELink copied to clipboard

Explanation: The IOAPFSTC utility has not found any IOA Application Server performance statistic records in the Permanent User File. This can occur if the statistic collecting is not activated at the site (optional wish WIN102 is set to APPLY=NO).

Corrective Action: If necessary, apply the optional wish WIN102.

IOAP3BI nnnnn PERFORMANCE STATISTIC RECORDS HAVE BEEN READLink copied to clipboard

Explanation: This information message indicates how many IOA Application Server performance statistic records were read from the Permanent User File during the IOAPFTSC utility run.

Corrective Action: No action is required.

IOAP3CI nnnnn PERFORMANCE STATISTIC RECORDS HAVE BEEN SELECTEDLink copied to clipboard

Explanation: This information message indicates how many IOA Application Server performance statistic records have been selected according to selection parameters specified for the utility IOAPFTSC.

Corrective Action: No action is required.

IOAP3DI nnnnn PERFORMANCE STATISTIC RECORDS HAVE BEEN DELETEDLink copied to clipboard

Explanation: This information message indicates how many old IOA Application Server performance statistic records have been have been deleted from the Permanent User File during the IOAPFTSC utility run with FUNCTION=CLEAN.

Corrective Action: No action is required.

IOAP3EI IOAPFSTC UTILITY ENDED SUCCESSFULLY Link copied to clipboard

Explanation: This information message indicates the utility IOAPFTSC ended successfully.

Corrective Action: No action is required.

Messages IOAQ00 through IOAQxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAQ01S APPLICATION SERVER VERSION srvr IS ACTIVELink copied to clipboard

Explanation: This information message indicates that the IOA Application server has been initiated and is ready to receive requests.

Corrective Action: No action is required.

IOAQ02S LOADING OF RECIPIENT TREE FAILEDLink copied to clipboard

Explanation: The Control-D Recipient Tree could not be loaded during initialization of the Application server.

The IOA Application server is terminated.

Corrective Action: Correct the problem with the Recipient Tree and restart the Application server.

IOAQ03S LOADING OF APPROVAL TREE FAILEDLink copied to clipboard

Explanation: The Control-D Approval Tree could not be loaded during initialization of the Application server.

The IOA Application server is terminated.

Corrective Action: Correct the problem with the Approval Tree and restart the Application server.

IOAQ04E MODIFY COMMAND INVALIDLink copied to clipboard

Explanation: The user sent an invalid MODIFY (F) command to the IOA Application server. The list of valid MODIFY commands is displayed on the operator console.

The invalid command is ignored.

Corrective Action: Reissue a valid MODIFY command.

IOAQ05W INVALID TIMEOUT VALUE PASSED. DEFAULT num SEC IS SETLink copied to clipboard

Explanation: This warning message indicates that an invalid timeout value was passed by IOAGATE when the IOA Application server was started.

The invalid value is ignored and default value will be used.

Corrective Action: No action is required.

IOAQ07E CONTROL MESSAGE OF UNKNOWN TYPE HAS BEEN RECEIVED FROM MANAGERLink copied to clipboard

Explanation: This message indicates that a control message of an invalid type was passed by IOAGATE.

The control message is ignored.

Corrective Action: Report the problem.

IOAQ08W INVALID MAXMSGSZ VALUE PASSED. DEFAULT XXXXX IS SET.Link copied to clipboard

Explanation: Since an invalid value was specified for the MAXMSGSZ parameter in the ECAAPPL member, MAXMSGSZ is set to its default value instead.

Corrective Action: Specify a correct value for the MAXMSGSZ parameter in the ECAAPPL member of the IOAENV library.

IOAQ10E MAILBOX opn ERROR. RC=rcLink copied to clipboard

Explanation: The specified Mailbox operation (READ or WRITE) failed. The IOA Gateway and the IOA Application server communicate through mailboxes.

The Application server subtask is terminated.

Corrective Action: Report the problem, the return code, and any additional relevant messages to BMC Customer Support.

IOAQ11E INVALID REQUEST TYPE reqTypeLink copied to clipboard

Explanation: The IOA Application server received a request of an unknown type. The request is probably not recognized by the Application server because the software on the mainframe and the PC are not the same release level.

The request is ignored and this error message is sent to the client.

Corrective Action: Do not use the feature that is discussed in this message until the appropriate software is upgraded.

IOAQ12E SESSION HANDLE NOT FOUNDLink copied to clipboard

Explanation: The IOA Application server received a request from a client, but a corresponding session did not exist. The session was probably terminated due to a timeout, a restart of the IOA Gateway, or a restart of the IOA Application server.

The request is ignored and this error message is sent to the client.

Corrective Action: Exit the problematic session and start a new session.

IOAQ13E USER userId NOT AUTHORIZEDLink copied to clipboard

Explanation: An unauthorized user attempted to log in to the IOA Application server. The user name or password is checked by Security Exit IOAX016 through the security subsystem, for example, RACF, ACF2SAF, or Top Secret.

The request is ignored and this error message is sent to the client.

Corrective Action: If the user is authorized to use the server, set the authorized user name and password in the client software.

IOAQ14I SESSION FOR USER userId TERMINATED DUE TO TIMEOUTLink copied to clipboard

Explanation: This information message indicates that the IOA Application server terminated a session that was dormant longer than the specified timeout interval. The timeout interval is specified in the TIMEOUT parameter in the Application server declaration. For details see the parameters for IOAGATE.

The session is terminated. All storage areas connected with the session in the Application Server are freed.

Corrective Action: Exit the problematic session and start a new session.

IOAQ15I USER userId LOGGED IN APPLICATION SERVERLink copied to clipboard

Explanation: This information message indicates that the Application server started a new session for the specified user.

Corrective Action: No action is required.

IOAQ16I USER userId LOGGED OUT. USED CPU TIME nnnnn.nn SECLink copied to clipboard

Explanation: This information message indicates that the Application server terminated a session for the specified user. This message reports the CPU time used.

Corrective Action: No action is required.

IOAQ17I USER STATUS LAST REQ CPU TIMELink copied to clipboard

Explanation: This information indicates that the IOA Application server processed the DISPLAY (D) command successfully. This message displays the column headings for information supplied by message IOAQ18I, which follows. The DISPLAY (D) command displays a list of active sessions.

Corrective Action: No action is required.

IOAQ18I userId stat last cpuTimeLink copied to clipboard

Explanation: This information message displays information about a currently open session for the IOA Application server. The first occurrence of this information message always follows the IOAQ17I message. Multiple occurrences of this information message display a table of currently open sessions. IOAQ18I is displayed in response to a DISPLAY (D) command. The IOAQ19I message follows immediately after the last occurrence of this message. The following information is included in each occurrence of this message:

  • userId - the user ID of the user currently logged on to the system

  • stat - the current status of the user, either W (WAITING) or A (ACTIVE)

  • last- time of the last request made by this user in hh:mm format

  • cpuTime - the amount of CPU time used by this user during the current session in the format sssss.th, where

    • sssss - seconds

    • t - tenths of seconds

    • h - hundredths of seconds

Corrective Action: No action is required.

IOAQ19I TOTAL NUMBER OF SESSIONS IS numLink copied to clipboard

Explanation: This information message indicates the total number of sessions open for the IOA Application server. This message marks the end of a table displayed by IOAQ18I and IOAQ17I messages. These messages are displayed in response to a DISPLAY command sent to the IOA Application server.

Corrective Action: No action is required.

IOAQ1AE INVALID PARAMETERS FOR PERFORMANCE STATISTICS ACCUMULATION PROGRAMLink copied to clipboard

Explanation: This message is issued because of an internal error.

Performance statistics cannot be accumulated.

Corrective Action: Report the problem.

IOAQ1BE PERFORMANCE STATISTICS CANNOT BE INITIATEDLink copied to clipboard

Explanation: This message can be issued if the IOAPFST module, which accumulates performance statistics, is absent from the STEPLIB library, or because of an internal error. This message might appear at the start of the application server.

Performance statistics collection is not initiated.

Corrective Action: If the module is present, report the problem to BMC Customer Support.

IOAQ1EE INVALID PARAMETERS FOR TRACE LIMITATION PROGRAMLink copied to clipboard

Explanation: This message is issued because of an internal error.Trace cannot be limited.

Corrective Action: Report the problem to BMC Customer Support.

IOAQ1FE TRACE LIMITATION CANNOT BE INITIATED/SHOWNLink copied to clipboard

Explanation: This message can be issued if the IOATRSRP module, which performs perfomance trace limitation commands, is absent from the STEPLIB library, or because of an internal error. This message can appear after MODIFY command TRCSHARP.

Performance statistics collection is not initiated.

The MODIFY command is ignored.

Corrective Action: If the module is present, report the problem to BMC Customer Support.

IOAQ20E ACCESS DENIED FOR USER userId: rsnLink copied to clipboard

Explanation: A user tried to log on to the IOA Application server. However, the IOASE16 security module or the IOAX016 user exit rejected the request. The message displays the reason provided by the security package for rejecting the user. Your security software documentation will have an explanation of the reason code.

  • userId - the name of the user

  • rsn - the reason for denying access

The login request is rejected.

Corrective Action: Check that the user name and password are spelled correctly and retry. If necessary, contact your security administrator.

IOAQ21E Output message of xxxxxxxx exceeds the allowed max valueLink copied to clipboard

Explanation: The OUTPUT message created by Application Server for Control-D/WebAccess server, is longer than the value defined by the MAXMSGSZ parameter in the ECAAPPL member of the IOAENV library. The request is not performed. Additional information is written to DATRACE.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem, DATRACE content, and any additional error messages to BMC Customer Support.

IOAQ22E Initialization of application U failedLink copied to clipboard

Explanation: Application U, specified in the IOA Application Server declaration (see IOAGATE parameters), could not be initiated. The message can be preceded with other messages, which provide further explanation.

The application is not initiated and is available for requests.

Corrective Action: If possible, correct the problem and restart the Application server. Otherwise, report the problem, supplying all appropriate messages.

IOAQ23E CPU limit has been exceeded for the requestLink copied to clipboard

Explanation: The amount of CPU required for processing the Control-D/WA request exceeds the value set in the optional wish WD3473. The request processing has terminated.

Corrective Action: Examine the selection parameters for the report list request to find the probable cause of the long processing time. Alternately, try increasing the value of the WD3473 optional wish.

IOAQ24E Application has not been found for user UUUUUUUULink copied to clipboard

Explanation: A user tried to log on to the IOA Application server. However, his request can be served. The user sent a request with the code of an application that has not been initiated in this Application server. The reasons can be as follows:

  • Software on the mainframe and the PC are not of the same release level.

  • The application is specified in the Application server declaration, but the Application server does not support this feature.

  • Initiation of the application failed when the Application server started. In this case this message is preceded with the message IOAQ22E.

The request is ignored and this error message is sent to the client.

Corrective Action: Do not use the feature that explains this message until the appropriate software is upgraded, or repeat the request after the Application server restart if the reason for the IOAQ22E message can be corrected.

IOAQ25W TOTAL NUMBER OF SESSIONS HAS BEEN EXCEEDED LIMIT OF 800 SESSIONSLink copied to clipboard

Explanation: This warning message indicates that the number of sessions opened in Application Server exceeded the limit of 800 sessions. This limit is designed to prevent insufficient memory problems in Application Server.

Corrective Action: Define an additional Control-D Application Server for the IOA Gateway.

IOAQ30S IOAREQ ERROR. RC=rcLink copied to clipboard

Explanation: The IOA Application server executor subtask failed to retrieve a request from the queue. The executor subtask processes requests such as OPEN/CLOSE operations from other subtasks inside the Application server address space.

The Application server abends with code U0005.

Corrective Action: Contact BMC Customer Support.

IOAQ31E ABEND DURING REQUEST EXECUTIONLink copied to clipboard

Explanation: The Application Server executor subtask detected an error while processing a request. The executor subtask processes requests such as OPEN/CLOSE operations from other subtasks inside the Application Server address space.

The current request abends. Processing continues with the next request.

Corrective Action: Report the problem to BMC Customer Support. Supply the abend sysout produced at the time of the problem.

Messages IOAS00 through IOASxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAS01I DATABASE REORGANIZATION STARTEDLink copied to clipboard

Explanation: This information message indicates that an IOA Access Method (IAM) file data component record reorganization started. While processing an IAM file data component, the I/O performance degradation threshold was reached. To maximize I/O performance, the IAM file data component records are dynamically sorted.

Corrective Action: No action is required.

IOAS02I DATABASE REORGANIZATION ENDED WITH RC=rcLink copied to clipboard

Explanation: This information message indicates that an IOA Access Method (IAM) file data component record reorganization process ended.

The IAM file data component dynamic record sorting process completed with the indicated return code.

Corrective Action: If IAM reorganization ended with a non-zero return code, check the IOA Log file and system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unsolved, contact BMC Customer Support.

IOAS03I DCBOUT OPEN ERRORLink copied to clipboard

Explanation: The file referenced by the SYSPRINT DD statement could not be opened by the sort program. This file is used to write message output during program execution.

The sort program terminates.

Corrective Action: Check the IOA Log file and system log for additional messages that describe the error, and correct the problem accordingly.

IOAS04I ERROR DURING OPENING OF PARAMETER FILELink copied to clipboard

Explanation: An attempt to open and read the file containing an IOA Access Method sorting parameters failed.

The sort program terminates.

Corrective Action: Check the IOA Log file and system log for additional messages that describe the error, and correct the problem accordingly.

IOAS05I INSUFFICIENT STORAGE TO RUN REORGANIZATIONLink copied to clipboard

Explanation: Not enough memory is available to sort IOA Access Method file records for a data component. An attempt to obtain storage for sorting records for a database file data component failed because not enough region storage was available.

The data is not sorted. Processing continues. I/O performance may degrade.

Corrective Action: Increase the REGION size.

IOAS06W DYNAMIC DATABASE SORTING STOPPED. PARAMETER STOP-WHEN-OVER CANNOT BE REACHEDLink copied to clipboard

Explanation: The level of reorganization specified by the STOP-WHEN-OVER parameter is not achievable. The STOP-WHEN-OVER parameter determines the maximum number of different data blocks that can be referenced by all the index records in any single index block after reorganizing the index block. Database sorting stopped, because more data blocks are referenced by the records for the last index block than the number specified in the STOP-WHEN-OVER parameter.

Database file data record sorting terminates. Processing continues. I/O performance may be degraded.

Corrective Action: Increase the value of the STOP-WHEN-OVER parameter or use the IOADBF utility to allocate an additional database extent. If the problem remains unresolved, contact BMC Customer Support.

IOAS07I DATABASE DOES NOT NEED SORTINGLink copied to clipboard

Explanation: This information message indicates that the level of sorting specified by the START-WHEN-OVER parameter was not reached. The START-WHEN-OVER parameter determines the number of different database file data blocks referred to by all the index records within any single index block that automatically triggers record reorganization. This trigger level was not reached. Therefore, database reorganization was not performed.

The database file data records are not sorted. Processing continues.

Corrective Action: No action is required.

IOAS08I INCORRECT INPUT PARAMETER parmLink copied to clipboard

Explanation: An invalid parameter was passed to the database sorting routine. Therefore, database reorganization is not performed.

In this message, parm is the identity of the invalid parameter.

Processing continues. I/O performance may degrade.

Corrective Action: Correct the problematic parameter.

IOAS09I DATABASE SORT TASK STARTEDLink copied to clipboard

Explanation: This information message indicates that the database sort routine subtask that will dynamically inspect a database file data component to determine whether the component records should be sorted to improve Database I/O performance was started and initialized.

Corrective Action: No action is required.

IOAS0AI SORTING DATA BASE IS NOT PERFORMED BECAUSE ALTERNATE INDEXES ARE IMPLEMENTEDLink copied to clipboard

Explanation: This information message indicates that the database internal sort is not performed. This internal sort improves IOA Access Method database performance. This sort process is not performed for a database with alternate indexes.

Corrective Action: No action is required.

IOAS10I DATABASE SORT TASK ENDEDLink copied to clipboard

Explanation: This information message indicates that the database sort routine that dynamically determines whether a database file data component records should be sorted ended.

Corrective Action: No action is required.

IOAS13E ERROR IN func FUNCTION. RC = rcLink copied to clipboard

Explanation: An internal error occurred while attempting to access a database file component. Processing of an IOA Database file component could not be completed because an internal error was encountered by an IOA Database utility.

The sort program terminates.

Corrective Action: Check the IOA Log file and system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.

Messages IOAT00 through IOATxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAT00S FAILURE TO LOCK WS TRACE WORK AREALink copied to clipboard

Explanation: The tracing facility failed to lock the internal (WS) trace work area.

The tracing request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT01S FAILURE TO LOCATE DDNAME(ddName) SUPPLIED TO IOATRCLink copied to clipboard

Explanation: The tracing facility failed to locate the ddName DD statement.

In this message, ddName is the name of the DD statement that was supplied to the trace facility as an internal parameter.

The tracing request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT02E APF-AUTHORIZATION REQUIRED TO INVOKE SVC DUMPLink copied to clipboard

Explanation: An SVCDUMP request was received by the tracing facility. Such a request requires APF authorization for STEPLIB load libraries.

The SVCDUMP tracing request is ignored. Processing continues.

Corrective Action: Ensure that STEPLIB load libraries have APF authorization, and restart the product monitor.

IOAT03E INVALID BUFID (bufid) HAS BEEN SUPPLIED IN INPUT PARAMETERSLink copied to clipboard

Explanation: The Buffer ID specified in one of the parameters contains invalid characters. Valid characters for the Buffer ID are A - Z, 0 - 9, @, #, $.

Processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT04E SYNTAX ERROR IN INPUT PARAMETERSLink copied to clipboard

Explanation: This error message indicates there is a syntax error in one of the input statements.

Processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT05W BUFFER (bufid) IS NOT DEFINED. FLUSH COMMAND IGNOREDLink copied to clipboard

Explanation: The buffer (bufid), which is required to flush in operator MODIFY command, is NOT allocated. The Flush command is ignored.

Corrective Action: In the Flush command, check the buffer ID.

IOAT06E UNKNOWN COMMAND/KEYWORD (keyword) IN INPUT PARAMETERSLink copied to clipboard

Explanation: An unknown command or keyword is specified in one of the input statements. The processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT07E INVALID ARGUMENT FOR KEYWORD (keyword)Link copied to clipboard

Explanation: An invalid value was specified for the keyword.

The processing of parameters is stopped.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT08S INTERNAL ERROR ENCOUNTERED. MODULE: module REASON: rsnLink copied to clipboard

Explanation: An internal error was encountered in the module module.

The variables in this message are:

  • module - the name of the module where an internal error was encountered

  • rsn - the exact reason for the error. Valid values are:

    • DESCRIPTOR LOST

    • NO DESCRIPTOR ADDR

The option to trace into a buffer is disabled. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT09E INVALID LEVEL PARAMETER SPECIFIED IN INPUT PARAMETERSLink copied to clipboard

Explanation: An invalid LEVEL parameter was detected in an input statement.

Corrective Action: Check the input parameters in the operator command or in the DATRCIN/DATRCBF input files and make appropriate adjustments as needed. Then rerun the command or product monitor.

IOAT0BW BUFFER x IS NOT DEFINED. DEFAULT BUFFER WILL BE USED INSTEADLink copied to clipboard

Explanation: This warning message indicates that redirection to the x buffer was required, but the buffer is NOT allocated. The messages are redirected to the default buffer.

Corrective Action: No action is required.

IOAT0CI THE FOLLOWING TRACE LEVELS IN THE BUFFERS: bufID[1, bufID2, . . . bufIDn]Link copied to clipboard

Explanation: This information message is issued after command TRACE= with keyword BUF= is performed. It is a header for subsequent IOAD02I messages. Normal processing continues.

bufID[1, bufID2, . . . bufIDn] are one or more buffer IDs.

Corrective Action: No action is required.

IOAT0DI FOR THE DESTINATIONS: dest[1, dest2, dest3, dest4]Link copied to clipboard

Explanation: This information message is issued after command TRACE= with keyword BUF= is performed. This message is a header for subsequent IOAD02I messages. Normal processing continues. dest[1, dest2, dest3, dest4] can be one or more of the following:

  • PRINT

  • CHAIN

  • WTO

  • GTF

Corrective Action: No action is required.

IOAT0FE TRACE trc_num CAN NOT BE TURNED ON AS EXTERNAL TRACE. WILL NOT BE ISSUED.Link copied to clipboard

Explanation:This message indicates that the tracing for trc_num trace number (where trc_num is the trace number requested in the TRACE MODIFY command) has not been turned on because of the environment limitation.

Corrective Action:Contact BMC Customer Support.

IOAT0HI TRACING INTO A BUFFER HAS BEEN DISABLEDLink copied to clipboard

Explanation: This information message indicates that the tracing into a buffer facility has been disabled.

Corrective Action: No action is required.

IOAT0IE DDNAME(ddName) NOT FOUND; FAILURE TO FLUSH THE TRACE BUFFERLink copied to clipboard

Explanation: The TRACE=FLUSH modify request was issued, but tracing into a buffer facility failed to perform the request, because the DD statement that was supplied to the trace facility as an internal parameter was not found.

In this message, ddName is the name of the DD statement that was supplied to the trace facility as an internal parameter.

The TRACE=FLUSH request is ignored. Normal processing continues.

Corrective Action: No action is required.

IOAT0JS FAILURE TO GETMAIN STORAGE FOR TRACE BUFFER bufIDLink copied to clipboard

Explanation: This message indicates an attempt to getmain trace buffer bufID failed.

The option to trace into a buffer is disabled.

The processing of parameters is stopped.

Corrective Action: Try specifying REGION=0 in the JOB JCL statement and run the product monitor again. Otherwise, contact BMC Customer Support.

IOAT0KI TRACING INTO BUFFERS IS ENABLEDLink copied to clipboard

Explanation: This information message indicates that the tracing into a buffer facility has been successfully initialized and enabled. Normal processing continues.

Corrective Action: No action is required.

IOAT0LI number1 LINES (number2 KB) ARE ALLOCATED FOR TRACE BUFFER xLink copied to clipboard

Explanation: This information message indicates that trace buffer x of the specified size is successfully allocated. Normal processing continues.

Corrective Action: No action is required.

IOAT0MW TRACING INTO A BUFFER IS NOT SUPPORTEDLink copied to clipboard

Explanation: This warning message indicates the TRACE= modify command with the BUF= parameter was issued, but the tracing into a buffer facility is not supported.

The TRACE= modify command is ignored. Normal processing continues.

Corrective Action: No action is required.

IOAT0OE FAILURE TO FLUSH THE TRACE BUFFER: UNABLE TO LOCKLink copied to clipboard

Explanation: The TRACE=FLUSH modify command was issued, but it could not be performed because of the failure to lock the trace buffer.

The TRACE= FLUSH modify command failed. Normal processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT0RS FAILURE TO LOAD module PROCESSOR OF TRACE=command MODIFY COMMANDLink copied to clipboard

Explanation: The specified load module failed to load, and therefore did not perform the command modify command.

The variables in this message are:

  • module - name of the load module that was attempted to be loaded

  • command - name of the modify command that initiated loading of the module.

The modify request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT0UI TRACE BUFFER (bufid) HAS BEEN WRAPPED AROUND nnnn TIMESLink copied to clipboard

Explanation: This information message indicates that the tracing buffer became full with tracing records, and it has been recycled nnnn times.

Corrective Action: No action is required.

IOAT0WE FAILURE TO OPEN DDNAME(ddName) TO FLUSH TRACE BUFFERLink copied to clipboard

Explanation: The specified DDNAME needed to perform the TRACE=FLUSH modify request could not be opened.

In this message, ddName is the name of the DD statement that was supplied to the trace facility as an internal parameter.

The TRACE= FLUSH modify request failed. Normal processing continues.

Corrective Action: Check the indicated DD statement, correct if necessary, and try running a product monitor again.

IOAT0XI number TRACE RECORDS HAVE BEEN FLUSHED INTO ddName FROM BUFFER xLink copied to clipboard

Explanation: This information message indicates that the TRACE=FLUSH modify request was issued and successfully processed. Normal processing continues.

The variables in this message are:

  • number--number of trace records flushed into the output

  • ddName--name of the DD statement supplied to the trace facility as an internal parameter

  • x--ID of the flushed buffer

Corrective Action: No action is required.

IOAT0YS IOATRC RECEIVED WS ADDRESS ABOVE THE LINE; CANNOT PROCEEDLink copied to clipboard

Explanation: The tracing facility received an invalid internal request.

The tracing request is ignored. Processing continues.

Corrective Action: Contact BMC Customer Support.

IOAT0ZS FAILURE TO GET MCT ADDRESSLink copied to clipboard

Explanation: An internal problem was encountered.

The system action is unpredictable. Action depends on the internal problem.

Corrective Action: Contact BMC Customer Support.

Messages IOAV00 through IOAVxxLink copied to clipboard

his group includes messages for the IOA (infrastructure) product.

IOAV02E INVALID VALUE FOR MODELink copied to clipboard

Explanation: In the IOA Variables Facility Entry screen (Screen IV), the MODE field contains an invalid value.

The only valid values for the MODE field are:

  • ADMIN

  • ' ' (Blank space)

Corrective Action: Type a valid value in the MODE field.

IOAV04E DATABASE/POOL NAME DOES NOT EXISTLink copied to clipboard

Explanation: In the IOA Variables Facility Entry screen (Screen IV), the DATABASE field contains a name, but no database nor pool with that name exists.

Corrective Action: Either correct the name in the DATABASE field, or select a database or pool from the list.

IOAV06E SPECIFIED DATABASE NAME ALREADY EXISTSLink copied to clipboard

Explanation: The user tried to insert a new variable database in the List of Databases - IOA Database Facility screen (Screen IV), and typed a name for the new database in the New Database window, but that database name already exists.

Corrective Action: Type a different new database name.

IOAV07E THE DATABASE/POOL IS IN USE. PLEASE TRY AGAIN LATERLink copied to clipboard

Explanation: An attempt was made to access a variable database, using the IOA Variables Facility Entry screen (Screen IV), but that database is already in use by another user.

Corrective Action: Try again later.

IOAV08E THE NUMBER OF ROWS MUST BE GREATER THAN 1Link copied to clipboard

Explanation: In the New Database Window of the List of Databases - IOA Database Facility screen (Screen IV), one of the following occurred:

  • No value was inserted in the NUMBER OF ROWS field.

  • The value "1" was inserted in the NUMBER OF ROWS field.

The NUMBER OF ROWS field is used to determine the amount of storage space allocated for the variable database. The number inserted in this field must be greater than 1.

Corrective Action: Correct the number in the NUMBER OF ROWS field.

IOAV09E COLUMN NAME HAS NOT BEEN FOUNDLink copied to clipboard

Explanation: An attempt was made to update a column in an existing variable database by typing U (Update) or D (Delete) in the OPT field beside a column name. However, the column name was not found in the database.

Corrective Action: Contact BMC Customer Support.

IOAV0AE A COLUMN WITH THIS NAME+NUMBER ALREADY EXISTSLink copied to clipboard

Explanation: An attempt was made to define a new column in an existing variable database. However, a column with the same values for COLUMN and NUMBER already exists.

Corrective Action: Specify new values for COLUMN and NUMBER.

IOAV10E NO ROOM AVAILABLE TO INSERT LINE HERELink copied to clipboard

Explanation: An attempt was made to insert a row into a variable database, but no row number is available at the location where the new row was to be inserted.

Rows in a variable database are originally numbered in thousands. Rows inserted later are assigned numbers in the gaps. For more information on how row numbers are assigned in a variable database, see the Control-O User Guide.

Corrective Action: Renumber the existing rows in the variable database, as follows:

  1. Use the IOAVARUL job to unload the variable database variables file. This job is in the IOA JCL library and invokes the IOADUL utility.

  2. Use the IOAVARLD job to reload the file, ensuring that the RENUM parameter is included. This job is in the IOA JCL library and invokes the IOADLD utility.

For more information about the IOADUL and IOADLD utilities, see the INCONTROL for z/OS Utilities Guide.

IOAV12E NO ROWS IN THE POOL. CAN'T BE VIEWED.Link copied to clipboard

Explanation: An attempt has been made to view the variables in a pool, but the pool does not contain any rows. Such a pool cannot be viewed.

Corrective Action: No action is required.

IOAV13E INVALID VARIABLE NAMELink copied to clipboard

Explanation: While trying to view the IOAVAR variable database or pool, an invalid variable name was specified.

Corrective Action: Specify a valid variable name.

IOAV14E NO AUTHORIZATION FOR PERFORMING THIS OPERATIONLink copied to clipboard

Explanation: The user is not authorized to perform the operation that was attempted.

Corrective Action: If you consider that you ought to have authority to perform an operation of this type, contact your INCONTROL administrator.

IOAV17E MAXIMUM NUMBER OF ROWS EXCEEDEDLink copied to clipboard

Explanation:An attempt was made to add a new variable into a Variable database by the I or R option in the Variable Database Display screen but the data base is full.

The action is aborted.

Corrective Action: Increase number of rows in the Variable database. It can be done by updating number of rows (For more information, see the INCONTROL for z/OS Administrator Guide, Chapter 2). Another option is to reformat the data base with bigger space parameters. (For more information, see the INCONTROL for z/OS Installation Guide: Installing, Step 7 - Set Global Variables database, and the INCONTROL for z/OS Upgrade Guide, Step 40)

IOAV18E THE NUMBER OF ROWS CANNOT BE GREATER THAN 65535Link copied to clipboard

Explanation: An attempt was done to specify value bigger than 65535 for the NUMBER OF ROWS parameter in the option U in the Database List screen.

The action is aborted.

Corrective Action: Specify a valid value and press ENTER to save the database parameters or specify N for the UPDATE field or press the RESET key (PF04) to close the window without saving the database parameters.

IOAV1AE CONTROL-O/CMEM MONITOR IS NOT ACTIVELink copied to clipboard

Explanation: An attempt was made to enter the Pools List or to view a pool, but the Control-O or CMEM monitor is not active.

To use this function, the Control-O or CMEM monitor must be active.

The request is rejected.

Corrective Action: Start the Control-O or CMEM monitor.

IOAV1BE THE COLUMN CONTAINS VARIABLES. CANNOT BE DELETED.Link copied to clipboard

Explanation: An attempt was made to delete a column from a variable database, but the column contains variables.

Corrective Action: Delete all variables from the column, then try again to delete the column.

IOAV1CE ERROR DURING DB/POOL ACCESS RC=rc, FUNCTION=funcLink copied to clipboard

Explanation: The user attempted to gain access to a variable database or pool, but failed.

Corrective Action: Note the values of rc and func and contact BMC Customer Support.

IOAV1DE NO COLUMNS IN THE DATABASE/POOLLink copied to clipboard

Explanation: An attempt was made to view the variables in a variable database or pool. However, the database or pool does not contain any columns. Such a database or pool cannot be viewed.

Corrective Action: No action is required.

IOAV20I IOAGLV UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOAGLV utility, which handles IOA global variables, started.

Corrective Action: No action is required.

IOAV21I nnnnn VARIABLES ARE READ FROM IOAVARLink copied to clipboard

Explanation: This information message indicates how many IOA Global Variables are read from the pool during the IOAGLV utility run.

Corrective Action: No action is required.

IOAV22E CONTROL-O/CMEM MONITOR IS NOT ACTIVELink copied to clipboard

Explanation: An attempt was made to submit the IOAGLV utility but the Control-O or CMEM monitor is not active. The Control-O or CMEM monitor must be active to use this utility.

Corrective Action: Start the Control-O or CMEM monitor, and then resubmit the utility.

IOAV23E ERROR DURING IOAVAR POOL ACCESS: RC=rc, REASON CODE =rsn.Link copied to clipboard

Explanation: The IOAGLV utility attempted to access IOA Global Variables from the IOAVAR pool but the access failed.

The utility stops with RC=8.

Corrective Action: Check the return code (rc) and the reason code (rsn). The return and reason codes are described in the tables attached to the API575E message description. Correct the problem and resubmit the utility.

IOAV24E INVALID FUNCTION: funcLink copied to clipboard

Explanation: The func function cannot be specified for the IOAGLV utility input parameters. The following functions can be specified:

  • LIST

  • VIEW

  • LOAD

  • DELETE

  • SETVAR

The utility stops with RC=16.

Corrective Action: Correct the input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV25E INVALID PARAMETER: parmLink copied to clipboard

Explanation: The parm input parameter specified for the IOAGLV utility is not valid.

The utility stops with RC=16.

Corrective Action: Correct the invalid input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV26E REQUIRED PARAMETER parm IS NOT SPECIFIEDLink copied to clipboard

Explanation: The mandatory parm input parameter is not specified in the input stream for the IOAGLV utility.

The utility stops with RC=16.

Corrective Action: Correct the input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV27W NO VARIABLES HAVE BEEN SELECTEDLink copied to clipboard

Explanation: No variables matching the specified path or path prefix were found in the IOA Global Variables pool.

The utility stops with RC=4.

Corrective Action: Check the input parameters in the JCL. Correct the input parameters in the JCL, if necessary, and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV28E PARAMETER parm LENGTH EXCEEDEDLink copied to clipboard

Explanation: The length of the parm input parameter exceeds the maximum allowable length for this parameter.

The utility stops with RC=16.

Corrective Action: Correct the invalid input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV29E REDUNDANT PARAMETER: parmLink copied to clipboard

Explanation: The parm input parameter for the IOAGLV utility is specified twice although it can be specified only once in this statement.

The utility stops with RC=16.

Corrective Action: Remove the redundant input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV2AW INCORRECT LINELink copied to clipboard

Explanation: An incorrect line was read from the input dataset, which was specified by the FROM parameter for the IOAGLV utility processing the LOAD function. This warning message is followed by the incorrect line itself.

The incorrect line is skipped and the utility continues processing other lines from the dataset. The utility ends with RC=4 if at least one incorrect line was detected in the dataset.

Corrective Action: Check the input dataset. Fix it and, if necessary, resubmit the utility. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV2BI VARIABLE IS ADDED TO IOAVARLink copied to clipboard

Explanation: This information message indicates that the IOAGLV utility added a variable to the IOA Global Variables pool. The variable itself is printed in the next line using the following format: varname=value.

Corrective Action: No action is required.

IOAV2CI VARIABLE IS UPDATED IN IOAVARLink copied to clipboard

Explanation: This information message indicates that the IOAGLV utility added a variable to the IOA Global Variables pool. The variable itself is printed in the next line using the following format: varname=value.

Corrective Action: No action is required.

IOAV2DI nnnnn VARIABLES ARE SELECTEDLink copied to clipboard

Explanation: This information message indicates how many IOA Global Variables, matching the specified path, are selected during the IOAGLV utility run.

Corrective Action: No action is required.

IOAV2EI nnnnn PATHS ARE SELECTEDLink copied to clipboard

Explanation: This information message indicates how many IOA Global Paths, matching the specified prefix, are selected during the IOAGLV utility run.

Corrective Action: No action is required.

IOAV2FI nnnnn VARIABLES ARE ADDEDLink copied to clipboard

Explanation: This information message indicates how many variables are added to the IOA Global Variables pool during the IOAGLV utility run.

Corrective Action: No action is required.

IOAV2GI nnnnn VARIABLES ARE DELETEDLink copied to clipboard

Explanation: This information message indicates how many variables are deleted from the IOA Global Variables pool during the IOAGLV utility run.

Corrective Action: No action is required.

IOAV2HI nnnnn VARIABLES ARE UPDATEDLink copied to clipboard

Explanation: This information message indicates how many variables are updated in the IOA Global Variables pool during the IOAGLV utility run.

Corrective Action: No action is required.

IOAV2II IOAGLV UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the IOAGLV utility completed successfully.

Corrective Action: No action is required.

IOAV2JE DYNAMIC ALLOCATION ERROR, RC=rc, REASON=rsn, DSN=dsnameLink copied to clipboard

Explanation: Dynamic Allocation of the input dataset (dsname), specified in the FROM parameter for the IOAGLV utility with function LOAD, failed.

The utility stops with RC=8.

For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, see the MVS Programming: Authorized Assembler Services Guide (IBM manual).

Corrective Action: Examine the return and reason codes, take the appropriate corrective actions, and resubmit the utility.

IOAV2KE MAXIMUM NUMBER OF ROWS nnnnn IN IOAVAR POOL EXCEEDEDLink copied to clipboard

Explanation: The IOAGLV utility, using either the LOAD or SETVAR functions, attempted to add a variable to the IOA Global Variables pool, exceeding the maximum number of variables in the IOAVAR database.

The utility writes from the pool to the database only the variables in the pool that were added or updated before exceeding the maximum limit, and then stops with RC=8.

Corrective Action: Do the following:

  1. Increase the maximum number of rows in the IOAVAR database from the online IV screen.

  2. Reload the IOAVAR pool from the database using the LOADGLOBAL=IOAVAR modify command issued for the Control-O or CMEM monitor.

  3. Resubmit the utility.

IOAV2LE ONLY ONE FUNCTION CAN BE SPECIFIEDLink copied to clipboard

Explanation: Multiple specifications of the following functions, or combinations of them are invalid in IOAGLV:

  • LIST

  • VIEW

  • LOAD

  • DELETE

(Only the SETVAR function can be specified multiple times, other functions must be specified singularly.)

Corrective Action: Correct the input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.

IOAV2ME REQUIRED FUNCTION IS MISSINGLink copied to clipboard

Explanation: No function was specified.

Corrective Action: Correct the input parameters in the JCL and resubmit the job.

Messages IOAZ00 through IOAZxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

IOAZ00I The performance trace limitations are as follows:Link copied to clipboard

Explanation: This is the first of a series of information messages that together display the current performance trace limitation settings.

This message is followed by the IOAZ01I message.

Corrective Action: No action is required.

IOAZ01I The following requests groups are to be traced:Link copied to clipboard

Explanation: This is the second of a series of information messages that together display the current performance trace limitation settings.

This message is preceded by the IOAZ00I message, and followed by the IOAZ02I message.

Corrective Action: No action is required.

IOAZ02I request group1request group2Link copied to clipboard

Explanation: This is the third of a series of information messages that together display the current performance trace limitation settings. The contents of this message lists the group(s) of requests to be traced. The request group can be one of the following: LIST, REPORT, ALL (where ALL means no limitation).

This message is preceded by the IOAZ01I message, and can be followed by the IOAZ03I message.

Corrective Action: No action is required.

IOAZ03I The following users are to be traced:Link copied to clipboard

Explanation: This is the fourth of a series of information messages that together display the current performance trace limitation settings.

The contents of this message form part of the headers of the columns of statistics.

This message is preceded by the IOAZ02I message, and followed by the IOAZ05I message.

Corrective Action: No action is required.

IOAZ05I user-idLink copied to clipboard

Explanation: This is the fifth of a series of information messages that together display the current performance trace limitation settings.

The content of this message is the user ID whose actions are to be traced. The first instance of this message is preceded by the IOAZ03I message. This message is repeated with new user-id values until all the user IDs to be traced have been displayed.

Corrective Action: No action is required.

IOAZ11E ZIIP ENCLAVE CREATION FAILED. RC=rc RSN=rsnLink copied to clipboard

Explanation: The Workload Management Service (IWM4ECRE macro) failed during enclave creating for ZIIP usage. For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, see the IBM manual MVS Programming: Workload Management Services. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ12W NO ZIIP CONFIGURED TO WHICH WORK COULD BE OFFLOADED TO. ZIIP WORK WILL BE REPORTED AS "SUP_ON_CP" WORK. RC=rc RSN=rsnLink copied to clipboard

Explanation: This warning message indicates that the Workload Management Service could not be configured for offloading work to the ZIIP. The address space continues to work and uses the ZIIP processor but ZIIP work will be reported as specific work.

Corrective Action: For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, contact BMC Customer Support.

IOAZ13E NO ZIIP CONFIGURED TO WHICH WORK COULD BE OFFLOADED TO. ZIIP PROCESSING DISABLED. RC=rc RSN=rsnLink copied to clipboard

Explanation: The Workload Management Service could not be configured for offloading work to the ZIIP. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ14E ZIIP OFFLOAD CPU PERCENTAGE FAILED. RC=rc RSN=rsnLink copied to clipboard

Explanation: The Workload Management Service failed during setting offload CPU percentage for ZIIP usage. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ15E ZIIP ENCLAVE DELETION FAILED. RC=rc RSN=rsnLink copied to clipboard

Explanation: The Workload Management Service (IWM4EDEL macro) failed during ZIIP enclave deleting. The address space continues to work, but does not use the ZIIP processor.

Corrective Action: Contact BMC Customer Support.

IOAZ16I INTERFACE TO XBM IS ACTIVELink copied to clipboard

Explanation: The message is issued when the interface to XBM is initialized successfully.

Corrective Action: No action is required.

IOAZ17I THE XBM MODIFY COMMAND IS IGNORED BECAUSE parameter_name PARAMETER IS SET TO NLink copied to clipboard

Explanation: The message is issued when the XBM modify command is ignored because the parameter_name parameter was set to N, where parameter_name is one of the following: ZIIPXBMO, ZIIPXBMP, or ZIIPXBMA.

Corrective Action: No action is required.

IOAZ18I CPU TIME OFFLOADED TO ZIIP: dddD hhH mmM ss.ccSLink copied to clipboard

Explanation: The message is issued upon a termination of the XBM-enabled address space. It contains the number of days (ddd), hours (hh), minutes (mm), seconds (ss) and hundredths of a second (cc) of CPU time offloaded to ZIIP.

Corrective Action: No action is required.

IOAZ19I INTERFACE TO XBM IS INACTIVELink copied to clipboard

Explanation: The message is issued when the interface to XBM is not initialized for the following possible reasons:

  • The ZIIPXBMx parameter (where ZIIPXBMx is one of the following: ZIIPXBMO, ZIIPXBMP or ZIIPXBMA) in the IOAPARM parameter member is set to N.

  • XBM address space is inactive, regardless the value of the ZIIP parameter.

Corrective Action: No action is required.

IOAZ1AI NO ONLINE ZIIP PROCESSORS FOUNDLink copied to clipboard

Explanation: The message is issued when no online ZIIP processors were found.

Corrective Action: No action is required.

JAR messagesLink copied to clipboard

This group includes messages for the Control-V product.

Messages JARG00 through JARGxxLink copied to clipboard

This group includes messages for the Control-V product.

JARGD0I CONTROL-V JCL ARCHIVING STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility started.

Corrective Action: No action is required.

JARGD1I CONTROL-V JOB ARCHIVING ENDED O.K.Link copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility ended successfully.

Corrective Action: No action is required.

JARGD2I CONTROL-V JOB ARCHIVING FAILEDLink copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility failed. Other messages generated in response to the failure describe the cause for the failure.

Job archiving ends.

Corrective Action: Examine all messages issued by the Job and correct the failure. If necessary, correct the input and rerun the CTVJAR Job Archiving utility.

JARGD3I *** PARM=TEST SPECIFIED - SIMULATION MODE ***Link copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility was run in TEST mode. CTVJAR was activated using the TEST parameter in the PARM field of the executive statement. When CTVJAR is active in TEST mode, no updates are performed to the Active User file. Only a report is created.

If the user sets the SYNC parameter to YES in CTVJAR, active generic decollation will close the recently created CDAM file. The active generic decollation will wait for new decollations until the CTVJAR Job Archiving utility is terminated.

No updates are performed to the Active User file. A report is created.

Corrective Action: Do the following:

  1. Check the results of the TEST mode run.

  2. If results are acceptable, rerun the CTVJAR utility with PARM set to PROD.

JARGD4E INVALID RETURN CODE FROM SORT, RC=rcLink copied to clipboard

Explanation: The CTVJAR Job Archiving utility received an invalid return code from the SORT utility. CTVJAR called the SORT utility to sort the entry being consolidated, and the sort failed.

In this message, rc is the invalid return code.

The system terminates CTVJAR.

Corrective Action: Examine the messages generated by the SORT utility for a description of the problem. Correct the problem and rerun CTVJAR.

JARGD5E OPEN OF SORT FILE FAILED. DDNAME "SORTIN"Link copied to clipboard

Explanation: The CTVJAR Job Archiving utility was unable to open the file referenced by the SORTIN DD statement. Either the SORTIN DD statement is missing in the JCL of CTVJAR, or the definition of the SORTIN DD statement is invalid.

CTVJAR terminates.

Corrective Action: Correct the DD statement and rerun the CTVJAR utility.

JARGD6I NUMBER OF CONSOLIDATED reptype RECORDS=numLink copied to clipboard

Explanation: This information message indicates that multiple records of type reptype were joined together into a single report. The CTVJAR Job Archiving utility consolidates multiple records, of type SYSDATA, USER or INDEX, into a single record according to type.

The variables in this message are:

  • reptype - the type of record consolidated

  • num - the number of consolidated records

Corrective Action: No action is required.

JARGD7I NUMBER OF NEWLY GENERATED REPORTS =numLink copied to clipboard

Explanation: This information message indicates how many new reports were created by a run of the CTVJAR Job Archiving utility. CTVJAR consolidates multiple SYSDATA, USER, or INDEX type records into a single record, according to type.

Corrective Action: No action is required.

JARGD8S INVALID INPUT PARAMETERLink copied to clipboard

Explanation: An invalid parameter was specified as input for the CTVJAR utility.

CTVJAR terminates.

Corrective Action: Correct the input parameters, and rerun the utility

JARGD9S INVALID PARAMETER, VALID PARAMETER: MODE=TEST OR MODE=PRODLink copied to clipboard

Explanation: An invalid value was specified for the MODE parameter of the CTVJAR Job Archiving utility. The only valid values for the MODE parameter are TEST and PROD.

CTVJAR terminates.

Corrective Action: Specify either TEST or PROD, and rerun the CTVJAR utility.

JARGDAW INDEX RECORD WITHOUT SYSDATA RECORD FOUND fileNameLink copied to clipboard

Explanation: Control-V attempted to match an index record with a corresponding SYSDATA record. However, a corresponding SYSDATA record could not be found for the index record. During Job archiving, selected index and user records are matched with their corresponding SYSDATA records.

In this message, fileName specifies the CDAM file name defined by the index. The index originally belonged to the SYSDATA record that satisfied the CTVJAR selection criteria.

The system ignores the index record. All other index and user records relating to this SYSDATA are also ignored.

Corrective Action: Determine the cause for the missing SYSDATA record. Correct if possible and rerun CTVJAR.

JARGDBW SYSDATA RECORD FOUND WITH NO USER RECORDS fileNameLink copied to clipboard

Explanation: Control-V attempted to match a SYSDATA record with a corresponding user record. However, a corresponding user record could not be found for the SYSDATA record. During Job archiving, Control-V matches selected index and user records with their corresponding SYSDATA records.

In this message, fileName is the CDAM file name of the SYSDATA record.

The system ignores the SYSDATA record.

Corrective Action: Determine why the user record is missing. Determine if the required user records were deleted using the online U screen.

JARGDCE CTDRPUF FAILED. RC: rcLink copied to clipboard

Explanation: Control-V called routine CTDRPUF to create a report entry in the Active User file of the newly archived report. However, CTDRPUF was unable to create the new report. In this message, rc is the CTVJAR return code.

CTVJAR processing continues with the next report.

Corrective Action: Check the IOA log for all messages generated for this failure. If the cause for the failure remains unclear, contact BMC Customer Support.

JARGDEE INVALID PARAMETERS RECEIVED FROM USER. RC =rcLink copied to clipboard

Explanation: There are invalid parameters in the SYSIN file. This is a summary message. Preceding messages clarify the error. CTVJAR issues the return code rc.

The system terminates job archiving.

Corrective Action: Check all messages generated for this error. Correct the input parameters, and rerun job archiving.

JARGDFE THE PARAMETER parm MUST BE SPECIFIED FOR JOBARC UTILITYLink copied to clipboard

Explanation: The user attempted to execute the CTVJAR Job Archiving utility without specifying the parm parameter. The parm parameter is mandatory for CTVJAR.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Add the parm parameter, and rerun CTVJAR.

JARGE0E INVALID PARAMETER: - parmLink copied to clipboard

Explanation: An invalid parameter was specified in the parameter statement for the CTVJAR Job Archiving utility. In this message, parm is the invalid parameter specified by the user.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Correct the values in the PARM statement, and rerun the CTVJAR Job Archiving utility.

JARGE1E REDUNDANT PARAMETER: - parmLink copied to clipboard

Explanation: A parameter was specified more than once in the input for the CTVJAR Job Archiving utility. That parameter can be specified only once in the input for this utility.

In this message, parm is the redundant parameter specified by the user.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Ensure that the parm parameter is specified only once, and rerun CTVJAR.

JARGE2E ERROR IN PARAMETERS: FODATE IS HIGHER THAN TODATELink copied to clipboard

Explanation: A later date value was specified in FODATE than in TODATE in the input for the CTVJAR Job Archiving utility. The FODATE and TODATE parameters indicate a date range for reports to be consolidated by CTVJAR. A date range is valid only if FODATE is earlier than, or the same as, TODATE.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Ensure that the date value specified for FODATE is not later than the date value for TODATE. Rerun CTVJAR.

JARGE3E INVALID DATE SPECIFIED:= ddNameLink copied to clipboard

Explanation: An invalid date value was specified in the ddName DD statement in the input for the CTVJAR Job Archiving utility.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Check and correct the date value and rerun CTVJAR.

JARGE4E NO USER RECORDS FOUND FOR -fileNameLink copied to clipboard

Explanation: Control-V found a SYSDATA record for CDAM file fileName. However, CDAM file fileName contained no user records that corresponded to the SYSDATA record. In the input for the CTVJAR utility, the user specified a CDAM file that contained no user records in the input for the CTVJAR utility.

In this message, fileName is the name of the CDAM file in error.

CTVJAR ignores the SYSDATA record, and continues processing normally.

Corrective Action: Check why the user records are missing. If the user records were deleted using the U screen, restore user records from a backup.

JARGE5I JOB ARCHIVING FOR FILE: cdamfil USER: userIdLink copied to clipboard

Explanation: This information message provides details about a consolidated report that is being produced by the CTVJAR utility.

The information about the report is provided in message CTDI0CI, which follows this message.

Corrective Action: No action is required.

JARGE6E CTVXVAL FAILED FOR - indexFile - SEE OTHER ERROR MESSAGESLink copied to clipboard

Explanation: The CTVXVAL internal routine was unable to process the indexFile index file.

The system skips the index file, and continues processing.

Corrective Action: To determine the cause, check the other messages generated by the failure of CTVXVAL.

JARGE7I REPORT ALREADY CONSOLIDATED FOR CDAM: cdamfilLink copied to clipboard

Explanation: This information message indicates that Control-V found a previously consolidated report in the ACTIVE user file. A CDAM file was specified to the CTVJAR utility. However, a consolidated report already exists for this CDAM file. It is unnecessary to consolidate a previously consolidated report.

In this message, cdamfil is the name of the CDAM file for which a consolidated report already exists.

The system skips the consolidation of this CDAM file and continues processing normally.

Corrective Action: No action is required.

JARGE8E CTDTRE FAILED RC: 08Link copied to clipboard

Explanation: An internal routine failed with a return code of 08. The CTVJAR Job Archiving utility uses the CTDTRE routine to determine the validity of each user name supplied by the user for the consolidated report.

CTVJAR terminates.

Corrective Action: Determine the cause by checking preceding error messages generated by the failure. Verify that the user tree is properly defined and rerun the CTVJAR utility.

JARGE9E USER NAME userId IS NOT FOUND IN TREE. JOB ARCHIVING WILL NOT BE PERFORMEDLink copied to clipboard

Explanation: The specified user name could not be found by the CDTRE utility. The CTVJAR Job Archiving utility uses the CTDTRE utility to determine the validity of the user name supplied by the user for the consolidated report. User name userId was specified by the USER parameter of the CTVJAR utility, but could not be found in the Control-D recipient tree.

CTVJAR terminates.

Corrective Action: Correct the user parameter and rerun CTVJAR.

JARGEAI USER PARAMETERS FOR CONSOLIDATION: parmLink copied to clipboard

Explanation: This information message indicates the parameters specified by the user as input for the CTVJAR Job Archiving utility. Multiple incidences of this message creates a list of all the user specified parameters.

Corrective Action: No action is required.

JARGEBE INDEX indexName IS NOT FOUND IN FILE fileNameLink copied to clipboard

Explanation: The CTVJAR utility did not find an expected index in the specified index file. The CTVJAR utility consolidates all small index files created by the decollation with the ALLOCOPT CDAM parameter and consolidates them into a single index file. For more information on ALLOCOPT, See the Control-D and Control-V User Guide.

The variables in this message are:

  • indexName - the name of the expected index

  • fileName - the name of the index file

The CTVJAR utility terminates.

Corrective Action: Check why the specified index was not found, correct the error, and if necessary, rerun the CTVJAR utility.

JARGECE SYNC= PARAMETER INVALID. ONLY SYNC=YES OR SYNC=NO ARE VALIDLink copied to clipboard

Explanation: An invalid value was specified for the SYNC parameter of the CTVJAR Job Archiving utility. Valid values for the SYNC parameter are YES and NO.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Correct the SYNC parameter and rerun CTVJAR.

JARGEEE THERE ARE TOO MANY MATCHING CDAM DATASETS KEPT OPEN BY CONTROL-D MONITORS. UTILITY TERMINATES.Link copied to clipboard

Explanation: The CTVJAR Job Archiving utility terminated execution without creating consolidated reports. This occurred under option SYNC=NO, because too many CDAM datasets matching selection criteria are opened by the Control-D decollation monitor.

Corrective Action: Execute the utility with parameter SYNC=YES.

JDL messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages JDLK00 through JDLKxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JDLK40I PRIORITY PROPAGATION PROCESS STARTEDLink copied to clipboard

Explanation: This information message indicates that the Priority Propagation process has been started by the Control-M monitor.

Corrective Action: No action is required.

JDLK41I PRIORITY PROPAGATION PROCESS ENDEDLink copied to clipboard

Explanation: This information message indicates that the Priority Propagation process has ended.

Corrective Action: No action is required.

JDLK42E INSUFFICIENT STORAGE FOR CALCULATIONLink copied to clipboard

Explanation: The Control-M monitor did not have enough storage for either the Deadline Scheduling Calculation process or for the Priority Propagation process.

The process is aborted.

Corrective Action: Increase the storage for the Control-M monitor.

JDLK43W WAITING FOR DEPENDENCIES FILE. DDNAME "ddName"Link copied to clipboard

Explanation: The Control-M monitor cannot access a file because it is being used by another component. The monitor requires exclusive access to the file.

The monitor waits for the file to be released.

Corrective Action: Check who is holding the file and have it released.

JDLK44S QNAME MISMATCH IN DEPENDENCIES FILELink copied to clipboard

Explanation: The Dependencies file allocated to the Control-M monitor does not belong to the current installation.

The process is aborted.

Corrective Action: Verify that the correct Dependencies file is allocated to the Control-M monitor through the DAGRAPH DD statement.

JDLK45I numRecd JOBS RECEIVED HIGHER PRIORITY. numHeld JOBS HELDLink copied to clipboard

Explanation: This information message is issued when the Priority Propagation process ends. The message indicates the number of jobs that received higher priority, and the number of jobs whose priority was not changed, that is, were held.

Corrective Action: No action is required.

JDLK46I DEADLINE SCHEDULING PROCESS STARTEDLink copied to clipboard

Explanation: This information message indicates that a request to resolve all deadline scheduling requests was received either from a modify command, or from a user entering command REFRESH in the Jobs Dependencies screen.

The Control-M monitor resolves all deadline scheduling definitions.

Corrective Action: Wait for message JDLK47I or CTMK47I, to signal the end of the process.

JDLK47I DEADLINE SCHEDULING PROCESS ENDEDLink copied to clipboard

Explanation: This information message indicates that the Control-M monitor successfully finished resolving all deadline scheduling definitions. This message is accompanied by message JDLK48I or CTMK48I which displays the number of updated jobs.

Corrective Action: No action is required.

JDLK48I num1 JOBS DUE OUT TIME UPDATED. num2 JOBS HELD/FINISHEDLink copied to clipboard

Explanation: This information message indicates that the Control-M monitor successfully finished resolving all deadline scheduling definitions.

The variables in the message are:

  • num1 - the number of jobs with DUE OUT times that were updated

  • num2 - the number of jobs that were not updated, because

    • the job was held

    • the job ended

    • the job record was not available for change

This message follows the JDLK47I message.

Corrective Action: No action is required.

JDLK49E DEADLINE SCHEDULING FACILITY IS DISABLED. PROCESSING STOPPEDLink copied to clipboard

Explanation: A request has been made to resolve deadline scheduling, but the Deadline Scheduling Facility has not been enabled in the Control-M defaults member.

Deadline scheduling is not performed.

Corrective Action: Ask your INCONTROL administrator to enable the Deadline Scheduling Facility in the Control-M default parameters member.

JDLK4AE CREATOR OF IN-CONDITION NOT FOUND. PROCESSING ABORTED.Link copied to clipboard

Explanation: A job or group entity that produces an out-condition that acts as an in-condition for the job being processed was not found in an internal table. This internal error was detected during the processing of the REFRESH DEADLINE (deadline scheduling) command while it was analyzing a group entity and its component jobs.

The REFRESH DEADLINE command is aborted.

Corrective Action: Contact your INCONTROL representative for assistance. Have the complete job log and the output of the Control-M monitor address space available.

JDLK4BE GROUP CROSS-REFERENCE LIST NOT FOUND. PROCESSING ABORTEDLink copied to clipboard

Explanation: An internally-created cross-reference table used for group processing was missing when the REFRESH DEADLINE (deadline scheduling) command was analyzing a group entity and its component jobs.

The REFRESH DEADLINE command is aborted.

Corrective Action: Contact your INCONTROL representative for assistance. Have the complete job log and the output of the Control-M monitor address space available.

JDLK50I INITIALIZATION OF DEPENDENCIES FILE COMPLETEDLink copied to clipboard

Explanation: This information message indicates that the Dependencies file was successfully formatted and is ready for use. The current dependencies between jobs can be viewed after entering the REFRESH command from the appropriate screen.

Corrective Action: No action is required.

JDLK51S BAD PARAMETER SUPPLIED TO REFRESH COMMANDLink copied to clipboard

Explanation: A REFRESH command was issued to the Control-M monitor with an unrecognizable parameter.

The REFRESH command is not executed.

Corrective Action: Check the command syntax and reissue the command.

JDLK52E DEADLINE COMMAND DOES NOT ACCEPT PARAMETERSLink copied to clipboard

Explanation: A REFRESH DEADLINE command was submitted with parameters. However, this command does not take any parameters.

The command is not executed.

Corrective Action: Delete the parameters and resubmit the command.

JDLK53E TOO MANY INTERJOB CONNECTIONSLink copied to clipboard

Explanation: The number of prerequisite conditions for dependency calculations exceeds the maximum number supported. The maximum number of conditions is ten times the maximum number of records in the Active Jobs file.

The dependency calculation process is aborted.

Corrective Action: Increase the size of the Active Jobs file.

JDLK54I DEPENDENCIES FILE REFRESH DONELink copied to clipboard

Explanation: This information message is issued to the IOA Log file after the Job Dependencies file is updated.

Corrective Action: No action is required.

JDLK55W DEADLINE SCHEDULING INTERNAL ERROR - DIAGNOSTIC DUMP PRODUCEDLink copied to clipboard

Explanation: The Control-M monitor encountered an internal error during REFRESH processing in the Control-M Active Environment screen.

The system produces a diagnostic dump, and continues processing.

Corrective Action: Ask your system programmer to record the error message, the diagnostic dump, and the Control-M monitor full output; and contact BMC Customer Support.

JDLK56S INVALID INPUT TO SHIFT. DATA SHOULD BE +NNN/-NNNLink copied to clipboard

Explanation: The user specified invalid parameters for operator command SDOUT.

The operator command is ignored.

Corrective Action: Specify valid parameters for operator command SDOUT. See the Control-M chapter of the INCONTROL for z/OS Administrator Guide for a details about this operator command.

JDLK57I shiftnum JOBS DUE-OUT TIME SHIFTED. heldnum JOBS HELDLink copied to clipboard

Explanation: This information message is issued after successful execution of operator command SDOUT.

The variables in this message are:

  • shiftnum - The number of jobs for which the DUE OUT time was shifted the requested number of minutes.

  • heldnum - The number of jobs that are currently in HELD status and were therefore not shifted.

Corrective Action: No action is required.

JDR messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages JDRK00 through JDRKxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JDRK15I REFRESH REQUESTED BY USER usrLink copied to clipboard

Explanation: This information message is issued to the IOA Log file after a user issues a refresh request.

Corrective Action: No action is required.

JDS messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages JDSN00 through JDSNxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JDSN06I NO MATCHING ENTRIES FOUNDLink copied to clipboard

Explanation: The Control-M CTMRJDS utility did not find any data set names in the Control-M statistics file that matched those specified in the DSN utility control statements.

Processing terminates.

Corrective Action: Change the DSN control statements and rerun the utility.

JDSN09I FUNCTION NOT SPECIFIED -- LIST ASSUMEDLink copied to clipboard

Explanation: The Control-M CTMRJDS utility detected a missing function statement.

The utility continues processing as if the LIST=DSN function had been specified.

Corrective Action: No action is required.

JES messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages JES200 through JES2xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JES260S OID=orderId OPEN OF DDNAME ddName FAILEDLink copied to clipboard

Explanation: Control-M monitor failed to open a work data set defined by the ddName DD statement.

This data set must be defined as a temporary or fixed work area for Control-M monitor. The ddName DD statement is probably missing.

Control-M monitor will shut down with errors.

Corrective Action: Correct the JCL for the Control-M monitor, and start again.

JES261S taskTypememNamejobName/ jobId OID=orderId ALLOCATION OF {SYSOUT FILE | ARCIVE FILE} dsn FAILED: R15=rc ERR=erc INFO=ircLink copied to clipboard

Explanation: Dynamic allocation to the specified dsn failed.

Control-M dynamically allocates the job sysout data sets, and/or the archive data set. The allocation failed for the specified reasons. For an explanation of the return codes displayed as part of this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

Return codes in this message:

  • rc - the contents of R15 in hexadecimal notation.

  • erc - error reason code in hexadecimal notation.

  • irc - information reason code in hexadecimal notation.

The requested function is stops. If analysis of job results was in process, the job terminates NOTOK with Reason Unknown (*UKNW).

Corrective Action: Check the relevant IBM publication for the reason.

  • For sysout data sets, check if the sysout was purged while the Control-M monitor was trying to read it.

  • For archive files, the Control-M monitor allocates archive files with DISP=(NEW,CATLG). Therefore, the same data set name should not be used in different sysout archive instructions, even for the same job.

If your system programmer is unable to resolve the problem, prepare the Control-M monitor full output and contact BMC Customer Support.

JES262W taskType memName jobName /jobId OID=orderId num UNSUCCESSFUL ATTEMPTS TO READ JOB DATA BY SUBSYSTEM REQUEST. RETRY CONTINUESLink copied to clipboard

Explanation: This message is issued every num unsuccessful attempts to read job data by subsystem request.

Whenever the Control-M monitor does not succeed in reading job sysout, this message appears on the operator console. For example, when a job is not run due to a JCL error, then the third sysout data set is missing and this message is issued.

Control-M continues to retry reading the job data for a predefined number of times. If the error persists, this job is not read and error message CTMD50S is issued.

Corrective Action: For the appropriate action, refer to the section on the Control-M Monitor and JES in the Control-M for z/OS Administrator Guide.

JES263S taskType memName jobName/jobId OID=orderId OPEN OF SMB FILE DSNAME dsn FAILED. RC=rcLink copied to clipboard

Explanation: Open of sysout data set of the job by Control-M monitor failed. Control-M cannot read the job sysout and analyze it. Possible causes are:

  • Someone purged the output of the job while Control-M monitor was trying to read it.

  • Internal Control-M monitor error.

  • General problems with JES that caused JES to terminate.

The job will finish with status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES264S taskType memName jobName/jobId OID=orderId POINT TO DSNAME dsn FILE FAILED. FDBK codeLink copied to clipboard

Explanation: Control-M reads the jobs output as a VSAM file. For some reason it failed in a VSAM operation. Control-M cannot read the jobs sysout and analyze it. Possible causes are:

  • Someone purged the output of the job while Control-M monitor was trying to read it.

  • Internal Control-M monitor error.

  • General problems with JES that caused JES to terminate.

The job will finish with status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES265S taskType memName jobName/jobId OID=orderId GET TO DSNAME dsn FILE FAILED. FDBK codeLink copied to clipboard

Explanation: Control-M reads the jobs output as a VSAM file. For some reason it failed in a VSAM operation. Control-M cannot read the jobs sysout and analyze it. Possible causes are:

  • The output of the job was purged while Control-M monitor was trying to read it.

  • Internal Control-M monitor error.

  • General problems with JES that caused JES to terminate.

The job will finish with status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES266S OID=orderId READING JOB DATA BY SUBSYSTEM REQUEST FAILEDLink copied to clipboard

Explanation: Control-M monitor could not read all the data sets of the job, and analyze the data.

Possible causes are:

  • Internal Control-M monitor error.

  • General problems with JES that caused JES to terminate.

  • Someone has purged the output of the job while the Control-M monitor was trying to read it.

The job finishes with status FAILED - REASON UNKNOWN.

Corrective Action: Look for prior messages in the IOA Log. If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES267S taskType memName jobName/jobId OID=orderId ARCHIVE FUNCTION ABENDED ON abCodeLink copied to clipboard

Explanation: An abend occurred during sysout archiving function. Common abend codes:

  • SB37, SE37 - No more space for the sysout in the file.

  • S913 - Security violation.

Archiving stops.

Corrective Action: For an Sx37 type of abend, consult your INCONTROL administrator for the possibility of changing the default Control-M archive file allocation size in the Control-M installation parameters (CTMPARM). For an S913 abend, check with your security administrator. For other abends, check IBM publications for the reason.

JES268S taskType memName jobName/jobId OID=orderId INVALID INSTALLATION PARAMETERS FOR SYSOUT ARCHIVINGLink copied to clipboard

Explanation:Highlighted, unrollable message.

Invalid values of the Control-M Installation Parameters (CTMPARM) which control the sysout archiving function.

The archiving function is terminated. Control-M will not perform any sysout archiving and valuable data may be lost.

Corrective Action: Consult your INCONTROL administrator immediately. See the section on Control-M operational parameters in the Control-M chapter of the INCONTROL for z/OS Installation Guide for the valid values of the sysout archiving parameters. To load new parameters, shut down the Control-M monitor and start it again.

JES269W OID=orderId INVALID RESPONSE FROM IEFSSREQ: SSOBFUNC=func R15=r15 SSOBRETN=ssobrc PHASE=xLink copied to clipboard

Explanation: A failure during sysout operation. The Control-M monitor is using subsystem request services to process the job sysout. A sysout function failed.

The Control-M monitor sometimes recovers from this kind of situation, and completes the function. If another error message indicating a sysout operation failure follows this one, then follow the User Response instructions.

Corrective Action: If the Control-M monitor does not recover from the failure, consult BMC Customer Support. To solve the problem, support personnel require the data of the message, a list of all the IOA Log messages concerning the problematic job, and the small SNAP (DUMP) of storage areas that the Control-M monitor produces in this event.

JES26AS OID=orderId ABEND code WHILE READING SYSOUTS. JOBORDER joborder HELDLink copied to clipboard

Explanation: Control-M could not read the output of a job from the spool. Control-M may be unable to read the output of a job because the OUT180 data set in which the data is placed overflows. The reason for this abend is either that the job output is unusually large, or that a spool corruption occurred that caused Control-M to read a very large amount of information, not related to the specific job, into its OUT180 data set.

The Control-M monitor changes the job status to HELD PROBLEMS READING SYSOUT.

Corrective Action: If the OUT180 data set is too small for the job output, increase the space value in the OUT180 DD, restart Control-M monitor, and free the job order in the Active Jobs file (AJF).

Messages JESD00 through JESDxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JESD50S READING JOB DATA BY IEFSSREQ FAILED num TIMES. LAST RC rc. fileNum_jobName/jobIdLink copied to clipboard

Explanation: This message is issued after the number of unsuccessful attempts to read job data by subsystem request reaches the defined maximum. After searching for the job data the maximum number of times, Control-M changes the job status to DISAPPEARED and stops searching.

The job status changes to DISAPPEARED.

Corrective Action: For the appropriate action, refer to the section on the Control-M monitor and JES in the INCONTROL for z/OS Administrator Guide.

JESD51S OID=orderId NO MORE SPACE FOR SYSOUT ARCHIVING (SB37)Link copied to clipboard

Explanation: No space is available on the designated volumes to archive SYSDATA sysouts.

Archiving of SYSDATA is not completed due to lack of the space on the volumes designated for allocation of the Archived Sysout Datasets.

Control-M issues additional messages describing the nature of the problem and terminates.

Corrective Action: Please do the following before attempting to restart the Control-M monitor:

  1. Make sure that there is sufficient free space on the volumes defined by the AMVOL parameter of the CTRPARM member.

  2. If it is not possible to provide enough space on the volumes defined by the AMVOL parameter of CTRPARM, please add another volume to the list of volumes designated for allocation of the Archived Sysout Data Sets.

  3. If it is not possible to add more volumes to the AMVOL parameter of the CTRPARM member, remove all of them. Then the Archived Sysout Data Sets will be allocated only according to the AMUNIT parameter of the CTRPARM member.

  4. Start the Control-M monitor.

  5. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

JESD52W OID=orderId PROBLEM PROBABLY CAUSED BY PREVIOUS MVS SYSTEM CRASH. END-OF-FILE ASSUMEDLink copied to clipboard

Explanation: A failure occurred during sysout processing.

Control-M received a bad return code from JES (feedback code of 0C0204) during sysout processing. This is a typical return code for a system crash event which prevented JES from closing the sysout in a standard manner.

The Control-M monitor ignores the return code, assumes that end-of-file has been encountered, and continues normally.

Corrective Action: No action is required.

JESD53S OID=orderId UNABLE TO ALLOCATE COMPRESSED DATASET FOR SYSDATA SYSOUT ARCHIVING. LAST RC=rcLink copied to clipboard

Explanation: Dynamic allocation of an Archived Sysout Dataset has failed.

This message will be preceded by other messages detailing the nature of the problem, the DD name, the return code, and the reason code.

The Archived Sysout Dataset is not allocated and Control-M terminates.

Corrective Action: Record all relevant messages, prepare the Control-M monitor full output, and contact BMC Customer Support.

JOB messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages JOB300 through JOB3xxLink copied to clipboard

This group includes messages for the Control-M for z/OS product, including: Control-M/Assist, Control-M/Links for z/OS and Control-M/Restart products.

JOB330E taskType memName OID=orderId ODATE odate INVALID RC FROM CTMMEM rc NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error. Non-zero return code from the CTMMEM internal program while reading a calendar.

The job order is not scheduled.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB331E taskType memName OID=orderId ODATE odate READING DATEMEM (CALENDAR) calName FAILEDLink copied to clipboard

Explanation: Reading of a calendar failed.

The job order or mission is not scheduled. Depending on whether or not optional wish WM0738 is applied, the program will terminate or continue with the next job.

Corrective Action: Look for prior messages in the IOA Log that explain why this error occurred and make any necessary corrections.

  • For a batch daily, correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement), to the values of date-2 (or date-4).

  • For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then run the Daily again.

If the previous abend happened after many jobs or missions had been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDREPRQ, CTDPRTRQ, CTDBKPRQ or CTDRSTRQ for missions).

JOB332E taskType memName OID=orderId ODATE odate CALENDAR calName - OPEN FAILEDLink copied to clipboard

Explanation: Reading of a calendar failed.

The calName calendar member does not exist in the library described by the DACAL DD statement.

The job order or mission is not scheduled.

Corrective Action: Correct the name of the calName member in the scheduling table, to a name of a valid calendar.

Check whether the DACAL DD statement describes one (and only one) valid Calendar library. Data set concatenation is not supported in this DD statement.

  • For a batch daily, correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement), to the values of date-2 (or date-4).

  • For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then run the Daily again.

If the previous abend happened after many jobs or missions had been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDREPRQ, CTDPRTRQ, CTDBKPRQ or CTDRSTRQ for missions).

JOB333E taskType memName OID=orderId ODATE odate MISSING DDNAME "DACAL"Link copied to clipboard

Explanation: Reading of a calendar failed.

The DACAL DD statement describes the calendar library.

The job order or mission is not scheduled.

Corrective Action: If this problem occurs during the New Day procedure, correct the JCL and rerun it. Correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement), to the values of date-2 (or date-4).

For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then rerun the Daily again.

If the previous abend happened after many jobs/missions had been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDREPRQ, CTDPRTRQ, CTDBKPRQ or CTDRSTRQ for missions).

JOB334E READING CALENDAR calName FAILEDLink copied to clipboard

Explanation: Reading of the specified calendar failed.

The job order or mission is not scheduled.

Corrective Action: Look for prior messages in the IOA Log that explain why the calendar could not be read.

If the error occurred during the New Day procedure or a User daily, correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (DD statement DACHK), to the values of date-2 (or date-4).

For a rerun of the same daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs or Active Missions file and then rerun the Daily again.

If the previous abend happened after many jobs or missions have been ordered, a manual request is recommended (the CLIST CTMJOBRQ for jobs; the CLIST CTDMISRQ for missions).

JOB335E taskType memName OID=orderId ODATE odate CALENDAR calName CONTAINS TOO MANY YEARSLink copied to clipboard

Explanation: A calendar contains too many years to be processed.

The job order or mission is not scheduled.

Corrective Action: Delete the oldest years in the calendar. Keeping a history of many years of calendars is unnecessary.

JOB336E taskType memName OID=orderId ODATE odate AN ABEND - abCode OCCURRED WHILE READING CALENDAR calNameLink copied to clipboard

Explanation: An abend occurred while reading a calendar.

The job order or mission is not scheduled. The New Day procedure terminates with a condition code of 08.

Corrective Action: Look for the abend code in the relevant IBM literature and respond accordingly.

JOB337E STATISTICAL CALENDAR statCal MUST BE PERIODICLink copied to clipboard

Explanation: During the job ordering process, the statCal statistical calendar specified in a group or job scheduling definition was found to be in a non-periodic format.

The job order is not scheduled.

Corrective Action: Replace the statCal calendar in the job scheduling definition with a periodic calendar, or modify the statCal calendar to make it periodic.

JOB338E ORDERING DATE odate (YYMMDD) NOT FOUND IN STATISTICAL CALENDAR calendarLink copied to clipboard

Explanation: The Statistical Calendar defined in a job definition does not include the date specified for the Ordering Date of the job. This error usually occurs when the Statistical Calendar does not include the year indicated in the Ordering Date. The ordering process fails.

Corrective Action: Add the definition for the year used in the Ordering Date to the Statistical Calendar.

JOB350S taskType memName OID=orderId ODATE odate INSUFFICIENT MEMORY TO PERFORM func FUNCTIONLink copied to clipboard

Explanation: There is insufficient memory to perform the internal New Day procedure function func.

The job order is not scheduled, but the New Day procedure continues to process other job orders.

Corrective Action: For batch, increase REGION size. For TSO, logon again using a larger SIZE parameter.

JOB351I warning_msgLink copied to clipboard

Explanation: This message is a user-defined warning message that is issued by the WRN task type.

Corrective Action: No action is required.

JOB354E taskType memName OID=orderId ODATE odate OPEN OF MEMBER FAILEDLink copied to clipboard

Explanation: Open of the warning messages member failed.

This could be due to one of the following:

  • The member does not exist in the specified library.

  • There is not enough memory to open the member.

The warning order is not activated.

Corrective Action: Do the following:

  • Check the validity of the member and library.

  • Increase the REGION size allocated for the New Day procedure.

JOB355E taskType memName OID=orderId ODATE odate DSN dsn IN USE (DISP=OLD)Link copied to clipboard

Explanation: The data set described in the MEMLIB parameter is in use.

Another user is holding the data set described by the MEMLIB parameter with DISP set to OLD.

The warning order is skipped.

Corrective Action: Try again later (or try to find the other user).

JOB356E taskType memName OID=orderId ODATE odate DSN dsn - NOT A LIBRARYLink copied to clipboard

Explanation: The data set described in the MEMLIB parameter is not a library (partitioned data set).

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB357E taskType memName OID=orderId ODATE odate DSN dsn - RECFM NOT FIXEDLink copied to clipboard

Explanation: The record format of the data set described by the MEMLIB parameter is not fixed.

The warning order is not issued.

Corrective Action: Correct the production parameters table and try again.

JOB358E taskType memName OID=orderId ODATE odate DSN dsn - LRECL NOT 80Link copied to clipboard

Explanation: The record length of the data set described by the MEMLIB parameter is not 80.

The warning order is not issued.

Corrective Action: Correct the production parameters table and try again.

JOB359E taskType memName OID=orderId ODATE odate DSN dsn NOT FOUNDLink copied to clipboard

Explanation: The data set described by the MEMLIB parameter is cataloged, but is not found on the disk.

The warning order is not issued.

Corrective Action: Correct the production parameters table or the catalog and try again.

JOB360E taskType memName ODATE odate DSN dsn - DYNAMIC ALLOCATION FAILEDLink copied to clipboard

Explanation: Dynamic allocation for the data set described by the MEMLIB parameter failed.

The warning order is not issued.

Corrective Action: Check the validity of the data set name or call BMC Customer Support for assistance.

JOB361E taskType memName OID=orderId ODATE odate INTERNAL ERROR ON func- MISSING PARAMETER. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warn task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB362E taskType memName OID=orderId ODATE odate INTERNAL ERROR ON func- ACT BEFORE INIT. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB363E taskType memName OID=orderId ODATE odate INTERNAL ERROR - INVALID REQUEST FROM CTMLIB. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB364W taskType memName OID=orderId ODATE odate TOO MANY DSNAMES FOR CTMLIBLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB365E taskType memName OID=orderId ODATE odate DSN dsn NOT CATALOGEDLink copied to clipboard

Explanation: The data set described by the MEMLIB parameter is not cataloged.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB366E taskType memName OID=orderId ODATE odate UNEXPECTED ERROR ON CTMLIB FUNCTION func. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB367S taskType memName OID=orderId ODATE odate INITIALIZATION OF MAIN LIB FAILED. DDNAME ddNameLink copied to clipboard

Explanation: Initialization of main library failed (the ddName DD statement).

Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB368S INSUFFICIENT MEMORY TO PERFORM func FUNCTIONLink copied to clipboard

Explanation: Insufficient memory to perform the internal New Day procedure function func.

The job order is not scheduled, but the New Day procedure continues to process other job orders.

Corrective Action: For batch, increase REGION size. For TSO, logon again using a larger SIZE parameter.

JOB369I warning_msgLink copied to clipboard

Explanation: This message is a user defined warning message that is issued by the WRN task type.

Corrective Action: No action is required.

JOB370E taskType memName ODATE odate OPEN OF MEMBER memName DSN dsn FAILEDLink copied to clipboard

Explanation: Open of the warning messages member failed.

Possible causes are:

  • The member does not exist in the specified library.

  • There is insufficient memory to open the member.

The warning order is not activated.

Corrective Action: Do one or both of the following:

  • Check the validity of the member and library.

  • Increase the New Day procedure REGION size.

JOB371E DSN dsn IN USE (DISP=OLD)Link copied to clipboard

Explanation: Data set described in the MEMLIB parameter is in use.

Another user is holding the data set described by the MEMLIB parameter with DISP set to OLD.

The warning order is skipped.

Corrective Action: Try again later, or find the other user.

JOB372E DSN dsn - NOT A LIBRARYLink copied to clipboard

Explanation: The data set described in the MEMLIB parameter is not a library (partitioned data set).

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB373E DSN dsn - RECFM NOT FIXEDLink copied to clipboard

Explanation: The record format of the data set described by the MEMBLIB parameter is not fixed.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB374E DSN dsn - LRECL NOT 80Link copied to clipboard

Explanation: The record length of the data set described by the MEMLIB parameter is not 80.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB375E DSN dsn NOT FOUNDLink copied to clipboard

Explanation: The data set described by the MEMLIB parameter is cataloged, but is not found on the disk.

The warning order will not be issued.

Corrective Action: Correct the production parameters table or the catalog and try again.

JOB376E DSN dsn - DYNAMIC ALLOCATION FAILEDLink copied to clipboard

Explanation: Dynamic allocation for the data set described by the MEMLIB parameter failed.

The warning order will not be issued.

Corrective Action: Check the validity of the data set name. If necessary, call BMC Customer Support for assistance.

JOB377E INTERNAL ERROR ON func - MISSING PARAMETER. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB378E INTERNAL ERROR ON func - ACT BEFORE INIT. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB379E INTERNAL ERROR - INVALID REQUEST FROM CTMLIB. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB380W TOO MANY DSNAMES FOR CTMLIBLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB381E DSN dsn NOT CATALOGEDLink copied to clipboard

Explanation: The data set described by the MEMLIB parameter is not cataloged.

The warning order will not be issued.

Corrective Action: Correct the production parameters table and try again.

JOB382E UNEXPECTED ERROR ON CTMLIB FUNCTION func. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

JOB383S INITIALIZATION OF MAIN LIB FAILED. DDNAME ddNameLink copied to clipboard

Explanation: Initialization of main library failed (the ddName DD statement).

Internal error in the New Day procedure while performing a warning task type.

The warning order will not be issued.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

Messages JOB500 through JOB5xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JOB501I CTMJOB STARTED JOB=username/jobID TYPE=jobTypeLink copied to clipboard

Explanation: This information message indicates that the CTMJOB program has started.

The CTMJOB program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

JOB502S OPEN OF SCHEDULE DATA FAILED. DDNAME "DAJOB"Link copied to clipboard

Explanation: Open of scheduling tables data set failed (the DAJOB DD statement).

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure, and could be due to one of the following:

  • The DAJOB DD statement is missing.

  • The data set described by the DAJOB DD statement cannot be opened for sequential read or record length is not 80.

The CTMJOB program will end with errors.

Corrective Action: Correct the JCL for the job or CLIST.

JOB503S OPEN OF USER DATE CONTROL RECORD FAILED - DDNAME "DACHK"Link copied to clipboard

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). Issued by the CTMJOB program which is usually activated by the New Day procedure.

Possible causes are:

  • The DACHK DD statement is missing.

  • The data set (member) described by the DACHK DD statement does not exist.

The CTMJOB program will end with errors.

Corrective Action: Correct the JCL for the job or CLIST.

JOB504S USER DATE CONTROL RECORD IS EMPTYLink copied to clipboard

Explanation: The data set described by the DACHK DD statement is empty.

The CTMJOB program will end with errors.

Corrective Action: Correct the JCL for the job or CLIST.

JOB505S PREVIOUS RUN OF CTMJOB DID NOT FINISH OKLink copied to clipboard

Explanation: A previous run of the CTMJOB program did not finish OK. This program is usually activated as part of the New Day procedure.

Date-2 and date-3 (or date-4 and date-5) of the Date Control Record are not equal. Possible causes are:

  • The previous run of the CTMJOB program did not finish OK.

  • Someone has modified the contents of the User Date Control Record (the DACHK DD statement).

For more information, see the Control-M chapter in the INCONTROL for z/OS Administrator Guide.

The CTMJOB program will end with errors.

Corrective Action: Change date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement) to the values of date-2 (or date-4).

To rerun the same daily, correct all the dates to the value of the day before. Be careful not to order the same job twice during a rerun on the same day. We recommend that you delete the ordered jobs from the Active Jobs file and then run the daily again.

If the previous abend happened after many jobs had been ordered, we recommend requesting the remaining jobs manually using CLIST CTMJOBRQ.

JOB506S SCHEDULING FAILED FOR MEMBER memNameLink copied to clipboard

Explanation: Scheduling failed for the memName member. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

The IOA Log or the job output should contain an additional message concerning the reason for failure.

The job order of the memName member is not placed in the Active Jobs file. Depending on the severity of the problem, the New Day procedure will continue to the next job order or terminate with the condition code 08.

Corrective Action: Check the IOA Log or the job output for the reason.

JOB507S LAST MONTHLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATELink copied to clipboard

Explanation: Invalid last monthly Scheduling Date.

The last monthly Scheduling Date (positions 18-23) in the User Date Control Record is greater than the current original Scheduling Date (positions 1-6). Possible causes are:

  • The previous run of the CTMJOB program did not finish OK.

  • Someone has modified the contents of the User Date Control Record (the DACHK DD statement).

For more details refer to the INCONTROL for z/OS Administrator Guide.

The CTMJOB program will end with errors.

Corrective Action: Correct the User Date Control Record (the DACHK DD statement).

JOB508S LAST MONTHLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK ITLink copied to clipboard

Explanation: The last monthly scheduling date is more than 28 days ago.

Possible causes are:

  • The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to “yesterday.”

  • Someone has modified the contents of the General Date Control Record incorrectly.

For more details refer to the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the User Date Control Record (the DACHK DD statement).

JOB50BS ERROR READING SCHEDULE DATA. DDNAME DAJOB. ERROR TYPE IS error_typeLink copied to clipboard

Explanation: You invoked a Daily job (either System or User) that has a concatenation of Control-M Definition Tables in DAJOB input DD statements. When accessing one of the DD statements in this concatenation, a problem occurred — either an ABEND (error type ABEND) or an Input/Output error (error type IO ERROR). This message is usually followed with z/OS system messages that contain additional information about the ABEND or Input/Output error.

The Daily job terminates with an error. Jobs from the tables in the DAJOB DD statements prior to the problematic one are processed. All remaining DAJOB DD statements are not processed.

Corrective Action: Analyze the ABEND or Input/Output error data, perform the required corrections, and try to rerun the Daily job to order the remaining jobs. If an Enhanced Checkpoint Date Record is used, the Daily job will automatically start from the point where it stopped in the previous run. If an Enhanced Checkpoint Date Record is not used, then before the Daily job rerun, the tables that have already been processed (that is, DD statements prior to the problematic one in the DAJOB concatenation) should be temporary commented or removed from the Daily job JCL.

JOB50CE Additional_Input/Output_error_dataLink copied to clipboard

Explanation: This message contains additional information about an Input/Output error, in SYNADAF data format. It follows the JOB50BS message when the error type is IO ERROR. See the description of message JOB50BS.

Corrective Action: See message JOB50BS.

JOB510S SEVERE ERROR IN THE SCHEDULING DATA - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Severe error in the scheduling data.

This message is produced when scheduling tables (described by the DAJOB DD statement) contain erroneous data. It can be due to the following:

  • The contents of a table were incorrectly modified using an editor or program, and the format of the table is invalid.

  • Internal error in Control-M.

'The program terminates with a condition code of 08.

Corrective Action: Try to restore the table to its original state. If you cannot, prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

If it is a batch Daily using a permanent Date Control Record, correct the contents of the record before running the Daily again. If issued during a User Daily or New Day procedure, see message JOB505S for further details.

JOB511I OID=orderId ODATE odate TASK=owner / systemId / jobName PLACED ON AJFLink copied to clipboard

Explanation: This information message indicates that the job order was placed successfully in the Active Jobs file (AJF).

The task is now in the Active Jobs file in Wait Schedule state.

The following variable TASK fields are displayed:

  • owner - the security user ID under which the ordering job that issued the JOB511I message was run

  • systemId - the system ID of the ordering job

  • jobName - the job name of the ordering job

Corrective Action: No action is required.

JOB512W LIBRARY lib SHOULD BE COMPRESSEDLink copied to clipboard

Explanation: The library specified in the PDS parameter contains fewer free tracks than the number specified in the MINIMUM parameter.

The PDS and MINIMUM parameters are used for automatically compressing a library. If the MINIMUM condition is satisfied, then the CTMJOB program will issue this message and the job order will be placed in the Active Jobs file.

For more details, refer to the Control-M chapter of the Control-M for z/OS User Guide.

The job order will be placed in the Active Jobs file.

Corrective Action: No action is required.

JOB513I SCHEDULE FAILED FOR number CONTROL-D CATEGORIESLink copied to clipboard

Explanation: This information message indicates that a number of Control-D decollating missions categories were not found in the library allocated to the DAREPMIS DD statement.

The Control-M New Day procedure continued processing.

Corrective Action: Look at the IOA Log for the failed categories and associated reasons for failure.

JOB514S INSUFFICIENT STORAGE FOR THE JOBLink copied to clipboard

Explanation: There is insufficient storage for processing the job order.

The program terminates with a condition code of 08.

Corrective Action: Increase the REGION size of the task which issued the request.

JOB515S ERROR IN SCHEDULING DATA - TOO MANY CARDS FOR ONE JOBLink copied to clipboard

Explanation: Too many statements for one job. Scheduling data used to describe the job order are too large to be processed by Control-M.

The job order will not be placed on the Active Jobs file. The New Day procedure will terminate with a condition code of 08.

Corrective Action: Check the contents of the job order, using the Online Scheduling Facility and remove unnecessary scheduling data. Prepare the Control-M monitor full output and contact BMC Customer Support.

JOB516S ERROR IN SCHEDULING DATA - FIRST CARD SHOULD START WITH "D"Link copied to clipboard

Explanation: There is invalid scheduling data in the first data set described by the DAJOB DD statement.

The first statement of a valid scheduling table should start with D. This could be due to one of the following:

  • The data set described by the DAJOB DD statement is not a scheduling table.

  • The scheduling data has been manually modified incorrectly.

The CTMJOB program ends with errors.

Corrective Action: Check contents of the data set described by the DAJOB DD statement and if the problem is not solved, check to find the person who may have manually changed the scheduling data.

JOB517S SCHEDULING DATA NOT AVAILABLELink copied to clipboard

Explanation: The DD statement pointing to the job scheduling tables is empty or missing.

The program ends with errors.

Corrective Action: Correct the JCL for the job or CLIST.

JOB518S INVALID YEAR IN USER DATE CONTROL RECORDLink copied to clipboard

Explanation: There is an invalid year in the User Date Control record used by the New Day procedure.

This year is not supported by the release of Control-M you are using.

The CTMJOB program ends with errors.

Corrective Action: Please correct the year field (the DACHK DD statement).

JOB519S INVALID PREVIOUS WEEKLY SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 43-48)Link copied to clipboard

Explanation: Invalid previous weekly Scheduling Date in the User Date Control record (positions 43-48). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

This date (date-4 of User Date Control record) might not be equal to date-5 (positions 50-55) or in invalid format.

Valid formats are:

  • ddmmyy

  • mmddyy

Possible causes are:

  • The previous run of the CTMJOB program did not finish OK.

  • Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

JOB520S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed (the DALOG DD statement).

This error message is issued by the CTMJOB program, which is activated as part of the New Day procedure, and is due to one of the following:

  • The DALOG DD statement is missing.

  • The data set described by the DALOG DD statement is not the IOA Log file.

  • The data set described by the DALOG DD statement is the IOA Log file, but of a different version of Control-M or of a different Control-M monitor.

The New Day procedure ends with errors.

Corrective Action: Do the following:

  1. Look for additional messages that will help identify the problem.

  2. Correct the JCL or the CLIST.

  3. Rerun the job.

JOB522S INVALID ORIGINAL SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 1-6)Link copied to clipboard

Explanation: Invalid original scheduling date in the User Date Control Record (positions 1-6). This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

Valid formats are:

  • ddmmyy

  • mmddyy

The message may be due to one of the following:

  • The previous run of the CTMJOB program did not finish OK.

  • Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

JOB523S INVALID PREVIOUS MONTHLY SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 18-23)Link copied to clipboard

Explanation: Invalid previous monthly scheduling date in the User Date Control Record (positions 18-23). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

This date (date-2 of User Date Control Record) should be equal to date-3 (positions 24-29) or in valid format.

Valid formats are:

  • ddmmyy

  • mmddyy

The message may be due to one of the following:

  • The previous run of the CTMJOB program did not finish OK.

  • Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The CTMJOB program will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

JOB524S CTMJOB ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTMJOB program ended with errors. It is activated as part of the New Day procedure.

The IOA Log should contain prior messages concerning the errors.

The New Day procedure will finish executing with a condition code of 08.

Corrective Action: Check the IOA Log for the errors. If necessary, correct the Date Control Record (date-3 and date-5) manually to allow the next run of the New Day procedure. If you cannot find any prior error messages in the IOA log or job log, ensure that the Control-M Job Scheduling library is not being compressed simultaneously with any job ordering.

For more details, see the INCONTROL for z/OS Administrator Guide.

JOB525I CTMJOB ENDED JOB=username/jobID TYPE=jobTypeLink copied to clipboard

Explanation: This information message is a normal message issued when the CTMJOB program terminates. CTMJOB is activated as part of the New Day procedure.

Corrective Action: No action is required.

JOB526S **** ERROR IN SCHEDULING DATA FORMAT ****Link copied to clipboard

Explanation: The scheduling table has been corrupted. Scheduling data do not conform to Control-M valid format.

This message is followed by a number of JOB527 messages which describe all the statements that belong to the damaged job order. The asterisk (*) appears in the line under the erroneous data.

The CTMJOB will terminate with a condition code of 08.

Corrective Action: If you cannot restore the table to its original state, have your system programmer call BMC Customer Support for assistance.

If it is a batch Daily using a permanent Date Control Record, correct the contents of the record before running the Daily again. For considerations, please see message JOB505S.

JOB527S CARD = stmtLink copied to clipboard

Explanation: The scheduling table has been corrupted.

This message follows message JOB526, and displays each statement in the damaged job order in the scheduling table. An asterisk (*) appears in the line under a damaged statement.

The CTMJOB program ends with errors.

Corrective Action: If you cannot restore the table to its original state, have your system programmer call BMC Customer Support.

If it is a batch Daily using a permanent Date Control Record, correct the contents of the record before running the Daily again. For considerations, please see message JOB505S.

JOB528I MEMBER memName ID=orderId ODATE odate PLACED ON ACTIVE JOBS FILE-descrLink copied to clipboard

Explanation: This information message is a standard message indicating that a job order has been placed on the Active Jobs file.

The task is now on the Active Jobs file in WAIT SCHEDULE state.

Corrective Action: No action is required.

JOB529S LAST WEEKLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATELink copied to clipboard

Explanation: The last weekly scheduling date in the Date Control Record is greater than the current original scheduling date.

This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure. Date-4 (positions 43-48) should not be greater than date-1 (positions 1-6) in the Date Control Record. The message may be due to one of the following:

  • The previous run of the CTMJOB program did not finish OK.

  • Someone modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the User Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

JOB530S LAST WEEKLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK ITLink copied to clipboard

Explanation: The last weekly scheduling date is more than 28 days ago.

Possible causes are:

  • The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to yesterday.

  • Someone has modified the contents of the General Date Control Record incorrectly.

For more details, refer to the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the Date Control Record (the DACHK DD statement) and rerun.

JOB531W MEMBER memName ODATE odate - SCHEDULING CANCELLED BY USER EXITLink copied to clipboard

Explanation: Scheduling cancelled by user exit CTMX001; the memName member did not pass user checking.

User exit CTMX001 is activated for each job order before it is placed on the Active Jobs file. The exit can specify to the New Day procedure not to place the job order on the Active Jobs file, in which case this message is issued.

The job order will not be placed on the Active Jobs file.

Corrective Action: Look for additional messages in the IOA Log clarifying the reason for the cancellation (usually security). If you cannot find a reason, consult your system programmer.

JOB532S OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED. DDNAME "DACKPT"Link copied to clipboard

Explanation: Open of Control-M Active Jobs file failed.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure, and is due to one of the following:

  • The DACKPT DD statement is missing.

  • The data set described by the DACKPT DD statement is not the Control-M Active Jobs file.

  • The data set described by the DACKPT DD statement is the Control-M Active Jobs file but of a different version of Control-M, or of a different Control-M monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job or CLIST and rerun it.

JOB534S SEVERE ERROR ON CONTROL-M ACTIVE JOBS FILELink copied to clipboard

Explanation: Severe error on Control-M Active Jobs file.

This could be due to one of the following:

  • An I/O error, or the file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.

  • The Active Jobs file has been corrupted.

The CTMJOB Control-M program which is activated as part of the New Day procedure will end with errors.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support. Check whether the file has been updated from two computers without global ENQ control, or maybe by an unauthorized program.

JOB535S CONTROL-M ACTIVE JOBS FILE IS BEING FORMATTED. TRY AGAIN LATERLink copied to clipboard

Explanation: Control-M Active Jobs file is currently being formatted. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

The General New Day procedure is currently running and is formatting the file.

Corrective Action: Try again later.

JOB536S SEVERE ERROR IN SCHEDULING DATA CARDSLink copied to clipboard

Explanation: Severe error was found in the scheduling data statements. This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Scheduling fails for the job order. The CTMJOB program terminates with a condition code of 08.

Corrective Action: Look for additional messages concerning the error, correct the error and rerun.

JOB537S NO MORE INTERNAL WORK AREA. SEE MESSAGES AND CODES FOR REQUIRED ACTIONLink copied to clipboard

Explanation: Internal work areas of the New Day procedure have been exhausted.

The job order contains more data than can be handled by the current release of Control-M.

The New Day procedure will terminate with a condition code of 08.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

JOB538E taskType memName OID=orderId ODATE odate SCHEDULING FAILEDLink copied to clipboard

Explanation: Scheduling failed. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

The IOA Log or the output of the job should contain prior message concerning the reason for failure.

The job order of member is not placed in the Active Jobs file.

Corrective Action: Check the IOA Log or the job output for the reason.

JOB539W taskType memName ODATE odate SCHEDULING CANCELLED BY USER EXIT userExitLink copied to clipboard

Explanation: An unauthorized user attempted to send a job to the AJF.

The job order will not be placed on the Active Jobs file.

Corrective Action: Do the following:

  1. Check your authorization.

  2. The next step depends on how the job is being ordered, as follows:

    • If the job is being ordered online, log off and log on again.

    • If the job is being ordered by the Control-M monitor, restart the monitor.

    • If the job is being ordered by the New Day procedure, rerun the New Day procedure.

  3. Look in the IOA Log for additional messages that clarify the reason for the job being cancelled. If there is no such message, check the userExit user exit.

JOB53AS AJF IS ALMOST FULL AND REACHED THE 'STOP ORDER' THRESHOLD. JOB IS NOT ORDEREDLink copied to clipboard

Explanation: When the amount of used space in the AJF increases and reaches the percentage threshold specified in the STOPORDR CTMPARM parameter, Control-M stops ordering jobs.

Control-M stops ordering jobs but all other functions (for example, job submission and post-processing) continue normally.

Corrective Action: The user must compress the AJF.

JOB53BE JOB CAN NOT BE ADDED BECAUSE THE MOST RECENT GROUP ON THE AJF IS DELETEDLink copied to clipboard

Explanation: An attempt was made to use the DYNAMIC INSERT JOB INTO GROUP option "R" (recent) to add a job to a deleted group.

Corrective Action: No action is required.

JOB540E ERROR IN CARDS. REASON=rsn, CODE=field Link copied to clipboard

Explanation: A severe error was found in the scheduling data statements. This message is issued by Control-M (the CTMINP program) when it discovers an invalid value in a data statement.

The variables in this message are:

  • rsn - a reason code that describes the probable cause of the error

  • field - the field in which the error was found

Possible values of rsn and field, with explanations, are shown in the following tables.

rsn

Explanation

01

Invalid option

02

Nonnumeric character

03

Out of bounds. Field exceeds its limits.

04

Invalid time format

05

Plus or minus sign expected

06

Invalid date format

07

Conflict with a previous field

08

Minus or blank expected

09

Invalid or missing parameter or scheduling data statement

10

Internal format error

field

Explanation

00

Internal Parameter

01

TASKTYPE

02

MAXWAIT

03

TIME FROM

04

TIME UNTIL

05

DUE OUT

06

MEMLIB

07

CTB STEP

08

IN Condition

09

CONTROL or RESOURCE

10

OUT

11

MAXDAYS

13

MAXRUNS

14

RETENTION, either # OF DAYS TO KEEP or # NUMBER OF GENERATIONS TO KEEP

15

MAXRERUN or INTERVAL

16

Invalid DO action

17

SYSOUT or DO SYSOUT

18

ON PGMST

19

SHOUT or DO SHOUT

20

DO COND or DO MAIL

21

PIPE

22

STATISTICS

Job order scheduling will fail. The User Daily will terminate with a condition code of 08.

Corrective Action: Use the values of rsn and field to locate the problem in the job definition. Correct the problem and run the User Daily again.

JOB541I JOB PLACED ON ACTIVE JOBS FILE AT RBA: rbaLink copied to clipboard

Explanation: This information message indicates that a job has been successfully placed in the Active Jobs file, and displays the job’s rba.

Corrective Action: No action is required.

JOB54AE RESOLVED CONDITION NAME '%%COND_VAR' IS TOO LONG,ORDER FAILED.Link copied to clipboard

Explanation: This error message indicates that the job order failed because the AutoEdit condition variable contains more than 40 characters.

Corrective Action: Ensure that the AutoEdit condition variable contains 40 characters or less.

JOB54BE RESOLVED CONDITION NAME '%%COND_VAR' CONTAINS BLANKS,ORDER FAILED.Link copied to clipboard

Explanation: This error message indicates that the job order failed because the AutoEdit condition variable contains spaces.

Corrective Action: Ensure that the AutoEdit condition variable does not contain any spaces.

JOB547W TABLE TblName IS NOT A SMART TABLE. RBC STATEMENT IGNOREDLink copied to clipboard

Explanation: The SELECT or IGNORE RBC statement refers to a job which is not part of a SMART Table.

SELECT and IGNORE RBCs always follow an ORDER statement for a SMART Table. They are meaningless for a job which is not part of a SMART Table.

The SELECT or IGNORE RBC statement is ignored. The job is ordered.

Corrective Action: No response needed.

JOB548E OID=orderId SEVERE ERROR IN CALENDAR calName OR YEAR NOT FOUND IN CALENDARLink copied to clipboard

Explanation: Severe error in the calName IOA calendar, or the year not found in the calendar.

Either the year is not defined in the calendar or the calendar has been incorrectly modified.

The job order is not issued. Processing of other job orders continues.

Corrective Action: Check the contents of the job order and the calendar.

JOB549W CONTROL-M/RESTART NOT AVAILABLE. IFRERUN ACTION IGNORED FOR MEMBER memNameLink copied to clipboard

Explanation: The scheduling table contains the IFRERUN definition, but Control-M was unable to act on this definition.

The probable cause is that CTR is set to N in IOAPARM, the IOA installation parameters member.

The scheduling table is ordered without the IFRERUN definition.

Corrective Action: Ensure that CTR is set to Y in IOAPARM.

JOB550W CONTROL-M/RESTART NOT AVAILABLE. SET ACTION IGNORED FOR MEMBER memNameLink copied to clipboard

Explanation: The scheduling table contains the SET definition, but Control-M was unable to act on this definition.

The probable cause is that CTR is set to N in IOAPARM, the IOA installation parameters member.

The scheduling table is ordered without the SET definition.

Corrective Action: Ensure that CTR is set to Y in IOAPARM.

JOB551S LOAD OF CTMPARM FAILED IN CTMRSG GROUP PROCESSINGLink copied to clipboard

Explanation: During group order processing the Control-M configuration parameters could not be accessed.

The program aborts the order processing.

Corrective Action: Contact your INCONTROL administrator who should verify that the CTMPARM member exists in the installation library.

JOB552S GETMAIN FAILED IN CTMRSG GROUP PROCESSINGLink copied to clipboard

Explanation: The CTMRSG program could not allocate storage.

Group processing is terminated.

Corrective Action: Increase the region size.

JOB553S AJF (CKP) FILE OPEN FAILED IN CTMRSG GROUP PROCESSINGLink copied to clipboard

Explanation: During Group Order processing, the CTMRSG program was unable to open the Active Jobs File (AJF).

Group Order processing terminates.

Corrective Action: Correct the AJF file problem, and order the group again.

JOB554I INPUT CONDITION REMOVED: CONDITION=cond, MEMBER=memName, GROUP=grpLink copied to clipboard

Explanation: This information message is issued during group order processing, when Control-M determined that in a certain group, an output condition of a member that was not scheduled, is an input condition for a member that was scheduled.

The input condition is removed as a prerequisite for job execution.

Corrective Action: No action is required.

JOB555I MEMBER memName SCHEDULING FORCED BY USER EXITLink copied to clipboard

Explanation: This information message indicates that the memName member was ordered due to a user exit decision.

This message is only issued when user exit CTMX001 is called before normal Control-M scheduling logic has been performed, or when CTMX001 overrides a Control-M scheduling decision not to order the job. This message can appear only after optional installation feature WM2603 has been enabled.

Corrective Action: No action is required.

JOB556W MEMBER memName- INVALID RETURN CODE FROM USER EXIT IGNORED. PRESUMED TO BE 0Link copied to clipboard

Explanation: User exit CTMX001 returned an invalid return code.

Control-M continues as if the user exit had not been called.

Corrective Action: Contact your INCONTROL administrator to correct user exit CTMX001.

JOB557W OID=orderId SCHEDULING FORCED BY USER EXITLink copied to clipboard

Explanation: A member was ordered as a result of a user exit decision. This message is issued when user exit CTMX001 is called before normal Control-M scheduling logic has been performed, or when CTMX001 overrides a Control-M scheduling decision not to order the job. This message can appear only after optional installation feature WM2603 has been enabled.

Corrective Action: No action is required.

JOB558W OID=orderId ILLEGAL RETURN CODE FROM USER EXIT IGNOREDLink copied to clipboard

Explanation: User exit CTMX001 returned an invalid return code.

Control-M continues as if the user exit had not been called.

Corrective Action: Contact your INCONTROL administrator to correct user exit CTMX001.

Messages JOBD00 through JOBDxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JOBD65E JOB jobName OID=orderId ODATE odate BYPASSED DUE TO MISSING PREV/NEXT DATES - descrLink copied to clipboard

Explanation: The job was not scheduled by Control-M because the requested previous or next original scheduling date (ODAT), could not be calculated.

The job to be scheduled contains IN and/or OUT conditions with ODAT PREV or ODAT NEXT. However these dates could not be calculated by Control-M, possibly because the calendar for the previous or next year is missing.

The job is not scheduled. Processing continues with the next job.

Corrective Action: Correct the situation and then reschedule the job manually.

JOBD66E MEMBER memName ODATE odate BYPASSED DUE TO MISSING PREV/NEXT DATES - descrLink copied to clipboard

Explanation: The member was not scheduled by Control-M because the requested previous or next original scheduling date (ODAT) could not be calculated.

The member to be scheduled contains IN and/or OUT conditions with ODAT PREV or ODAT NEXT. However, these dates could not be calculated by Control-M, possibly because the calendar for the previous or next year is missing.

The member is not scheduled. Processing continues with the next member.

Corrective Action: Correct the situation and then reschedule member manually.

JOBD67S ORDERING CHECKPOINT RECORD IS INVALID FOR THIS DAILYLink copied to clipboard

Explanation: The Ordering Checkpoint Record contains recovery information which is invalid for this Daily run.

The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains data specifying recovery for the CTMJOB program, but these data are incorrect for the jobs that were ordered in this run of CTMJOB.

The CTMJOB program ends with errors.

Corrective Action: Either run CTMJOB with the same data (ordered jobs) as were in the last (abending) run, or blank out the values of the keywords in the Ordering Checkpoint Record, and run CTMJOB without recovery.

JOBD68S STRUCTURE OF ORDERING CHECKPOINT RECORD IS INVALIDLink copied to clipboard

Explanation: The Ordering Checkpoint Record contains invalid keywords, or valid keywords in invalid offsets. The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains keywords in an unexpected structure.

The CTMJOB program ends with errors.

Corrective Action: Either correct the Ordering Checkpoint Record, or delete the Ordering Checkpoint Record, and run CTMJOB without recovery.

JOBD69I NO JOBS WERE SCHEDULED DURING SCHEDULING REQUESTLink copied to clipboard

Explanation: This information message indicates that no jobs matched the ordering criteria during a scheduling request. This message is issued after the scheduling request has been processed, and no jobs were ordered.

Corrective Action: If you think a job should have been ordered in this scheduling request, check and correct the scheduling parameters as required, and rerun the scheduling request.

JOBD6AI RETRO SCHEDULING BYPASSED FOR JOBS WITHIN GROUPLink copied to clipboard

Explanation: This information message indicates that Y was specified in the RETRO field in a group entity or in one of the group jobs. RETRO processing is not supported in GROUPS. Setting RETRO to Y in a group can cause jobs to be scheduled on inappropriate ODATES.

The RETRO field is ignored in group processing.

Corrective Action: Set the RETRO field to N and retry.

JOBD6BI NUMBER OF JOBS ORDERED - jobsnumLink copied to clipboard

Explanation: This information message indicates the number of jobs ordered by the present invocation of CTMJOB.

Corrective Action: No action is required.

JOBD90E RECOVERY RECORD INCOMPATIBLE WITH DATE RECORDLink copied to clipboard

Explanation: The Date Control Record indicates that recovery is not necessary, but the recovery record, that is, the second record of the Date Control Record member used for Enhanced Daily Checkpointing, indicates that recovery is needed.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. In the Date Control Record, date-2 (columns 18-23) is equal to date-3 (columns 25-30) and date-4 (columns 43-48) is equal to date-5 (columns 50-55). However, the recovery record contains non-blank values for the recovery parameters.

For more details, please refer to the description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.

The program terminates with a condition code of 08.

Corrective Action: If recovery is required, set date-3 to the day before date-2, and date-5 to the day before date-4. If recovery is not required, replace the values in the recovery record with blanks.

JOBD91E INVALID PREVIOUS MONTHLY SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 25-30)Link copied to clipboard

Explanation: Invalid previous monthly scheduling date in the User Daily Date Control Record date-3 (columns 25-30). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Valid formats for the date are:

  • ddmmyy

  • mmddyy

  • yymmdd

Possible causes are:

  • The previous run of the CTMJOB program did not complete successfully.

  • The contents of the User Daily Date Control Record (the DACHK DD statement) have been incorrectly modified manually.

For more details please refer to description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.

The program terminates with a condition code of 08.

Corrective Action: Correct the Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

Messages JOBL00 through JOBLxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JOBL34E INVALID ORDER REQUEST STARTING keyNameLink copied to clipboard

Explanation: A syntax error was found on the previously displayed line.

The CTMJOB program ends with errors.

Corrective Action: Correct the erroneous keyword or data in the order request.

JOBL35I ORDER REQUEST LINELink copied to clipboard

Explanation: This information message is a standard message when a request order is being processed.

Corrective Action: No action is required.

JOBL36E DUPLICATE KEYWORD keywd IN ORDER REQUESTLink copied to clipboard

Explanation: A keyword was given twice in the same order request. The order request which was listed prior to this message contains the same keyword twice, regardless of whether or not the values are identical.

The CTMJOB program ends with errors.

Corrective Action: Delete the duplicate keyword in the order request.

JOBL37S SIZE OF TABLE table_mem FROM DSN lib GREATER THAN MAXIMUMLink copied to clipboard

Explanation: The table member either exceeds the maximum allowed size, or contains invalid data.

The CTMJOB program ends with errors.

Corrective Action: Check that the table member contains less than 32,000 records of valid scheduling definitions.

JOBL38S ERROR READING MEMBER table_mem FROM DATASET lib. RC=rc.Link copied to clipboard

Explanation: Reading the specified table member failed.

The order request could not be done either because the library did not exist, or could not be allocated, or the table member was not found.

The CTMJOB program ends with errors.

Corrective Action: Check that the order request is given to an existing 80-bytes record length library, and the member can be accessed. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

JOBL39E INVALID DATE date IN ORDER REQUESTLink copied to clipboard

Explanation: The date specified in the order request is not a valid date.

The CTMJOB program ends with errors.

Corrective Action: Check that the specified date is specified correctly according to your installation standards.

JOBL40E JOB jobName GROUP groupName COMBINATION NOT FOUND IN TABLE table_memLink copied to clipboard

Explanation: None of the jobs in the table satisfy both selection criteria of “JOB” and “GROUP”, specified in the ORDER request.

Corrective Action: Specify other values to order the jobs.

JOBL41E MISSING OBLIGATORY PARAMETER parm IN ORDER REQUESTLink copied to clipboard

Explanation: The specified parameter was not given in the order request.

Some parameters are obligatory in each order request. Failing to specify one of them results in this message being issued.

The CTMJOB program ends with errors.

Corrective Action: Supply the missing parameter.

JOBL42E MUTUALLY EXCLUSIVE KEYWORDS SPECIFIED IN ORDER REQUESTLink copied to clipboard

Explanation: Two keywords which are mutually exclusive where given in the same order request.

Certain keywords, such as DSNAME and DDNAME, cannot appear together on the same order request.

The CTMJOB program ends with errors.

Corrective Action: Specify one of the keywords.

JOBL43W DASTAT DD CARD MISSINGLink copied to clipboard

Explanation: The DASTAT DD statement is missing from the file allocation of the job step.

This warning message is issued by the CTMJOB program.

The Automatic Tape Adjustment facility is skipped. Jobs are ordered, but required resource quantities are not computed for these jobs.

Corrective Action: Add a DASTAT DD statement for future runs.

JOBL44W AUTO TAPE DRIVE RESOURCE ADJUSTMENT IS BYPASSED DUE TO PREVIOUS MESSAGELink copied to clipboard

Explanation: This warning message indicates that the Automatic Tape facility cannot adjust resources for jobs currently being processed.

This is a summary message. It is preceded by a message that describes the reason for the error.

The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the quantity of required resources.

Corrective Action: View the error message that precedes this message and correct the problem described there.

JOBL45E ERROR ANALYZING PARM MEMBER "UNITDEF" AT LINE lineNumLink copied to clipboard

Explanation: An invalid definition was found in the UNITDEF parameter member.

The UNITDEF parameter member associates logical names to physical resources.

In this message, lineNum is the number of the line in the UNITDEF parameter member where the error occurred.

Resource definition example in the UNITDEF file:

CARTRIDGE=(0480-0483,0440-0445,0300-031F,0552-0553,0556-0557),DESC=3490 RANGE

The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the required amount of resources.

Corrective Action: Correct the error at the specified line. View the description in the UNITDEF file supplied during the installation.

JOBL46W DAUNITDF DD CARD MISSINGLink copied to clipboard

Explanation: The UNITDEF DD statement is missing.

This warning message is issued by the CTMJOB program.

The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the required amount of resources.

Corrective Action: Add a UNITDEF DD statement to the JCL stream.

JOBL47S GETMAIN FAILED IN CTMATD AUTO TAPE PROCESSINGLink copied to clipboard

Explanation: The Control-M Daily Subsystem stopped due to insufficient memory.

The Daily job stops execution.

Corrective Action: Increase the region size defined in the Daily job and rerun the job.

JOBL48W CONDITION IN JOB NOT ADJUSTEDLink copied to clipboard

Explanation: The requirement that a prerequisite condition exist (for a job which is part of a group) was not deleted.

The “adjust conditions in a group” feature failed to delete the requirement that a prerequisite condition exist for one of the jobs of a group.

The job is ordered with the prerequisite condition requirement intact.

Corrective Action: Determine if the condition prevents the job from running. If so, add the required condition manually in screen 4 or erase the requirement for the condition from the job in zoom screen 3.Z.

JOBL49W NOT ALL CONDITIONS IN JOB COULD BE ADJUSTEDLink copied to clipboard

Explanation: The requirement for prerequisite conditions for a job which is part of a group were not deleted.

This message accompanies message JOBL48W.

The job is ordered prerequisite condition requirement intact.

Corrective Action: Determine if the condition prevents the job from running. If so, add the required condition manually in screen 4 or erase the requirement for the condition from the job in zoom screen 3.Z.

JOBL4AE DSN data_set_nameLink copied to clipboard

Explanation: The scheduling library in which the table mentioned in JOBL40E resides.

This message accompanies message JOBL40E.

Corrective Action: Specify the correct values to order the jobs.

JOBL50E DYNAMIC ORDER FAILEDLink copied to clipboard

Explanation: A request to dynamically insert a job into a Group Entity that is already on the Active Jobs file has failed. The reason for the failure is detailed in an accompanying message.

Dynamic ordering of the job was not performed.

Corrective Action: Check the accompanying message to determine the cause of the failure, and respond accordingly.

JOBL51E RBA rba IS NOT POINTING TO A VALID GROUP IN THE AJFLink copied to clipboard

Explanation: A request to dynamically insert a job into a group failed because the rba, which points to the Group Entity in the Active Jobs file, was not pointing to a Group Entity.

Dynamic ordering of the job is not performed.

Corrective Action: Find the correct Group Entity rba, and change the order request accordingly.

JOBL52E JOB jobName NOT FOUND IN GROUP grpname RBA rbaLink copied to clipboard

Explanation: A request to dynamically insert a job as part of a group failed, because the job is not a member of the group. Users can dynamically insert jobs only if the jobs are members of the group definition.

The job is not ordered.

Corrective Action: Correct the order request appropriately.

JOBL53E GROUP grpname RBA rba IS FULL. NO MORE JOBS CAN BE DYNAMICALLY INSERTEDLink copied to clipboard

Explanation: A request to dynamically insert a job into a group in the AJF failed, because the group already contains the maximum number of jobs allowable in a group.

The job is not ordered.

Corrective Action: No action is required.

JOBL54E DUPLICATE JOB jobName FOUND IN GROUP grpname RBA rbaLink copied to clipboard

Explanation: A request to dynamically insert a job into a group in the Active Jobs file failed because a job with same name already exists in the group, and the order request did not specify the DUP (duplicate) parameter.

The job is not ordered.

Check if the job should still be inserted in the group. If so, dynamically insert a duplicate job into the group using the DUP parameter in the ORDER statement.

Corrective Action: No action is required.

JOBL55E TABLE table IS NOT A SMART TABLELink copied to clipboard

Explanation: The table specified is not a SMART table.

Corrective Action: No action is required.

JOBL56I NEWDAY OCCURRED DURING SMART TABLE PROCESSING. TABLE REORDEREDLink copied to clipboard

Explanation: NEWDAY processing occurred during the ordering of a Smart Table. Some of the jobs in the Smart Table were ordered before NEWDAY started, but after NEWDAY started the ordering process was suspended. The NEWDAY process then deleted the jobs that were already ordered, as indicated in the NEWDAY SYSOUT.

After NEWDAY has ended, CTMJOB/CTMAPI resumes the job ordering process for this Smart Table. It detects that the previously ordered jobs are no longer in the Active Jobs File (AJF). These jobs are now Held (as they are ‘orphans’ that are no longer attached to their Smart Table) and the JOBL56I message is issued. The complete Smart Table is now (correctly) ordered again.

Corrective Action: Delete the ‘orphan’ jobs from the Actives Jobs File.

JOBL57E SELECT/IGNORE RBC COMMAND IN ERRORLink copied to clipboard

Explanation: There is a syntax error in the SELECT or IGNORE RBC statement. The ORDER statement (to which this SELECT or IGNORE RBC command refers) is ignored. The daily job resumes processing with the next ORDER statement.

Corrective Action: Use one of the following syntaxes:

  • SELECT RBCrbcname

  • IGNORE RBCrbcname

JOBL58I JOB xxxxxxxx ORDERID=nnnnn ODATE YYYYYY ORDEREDLink copied to clipboard

Explanation: Job has been ordered successfully.

Corrective Action: No action is required.

JOBL59I JOB xxxxxxxx NOT ORDEREDLink copied to clipboard

Explanation: Job has not been ordered.

Corrective Action:Check for additional messages that explain why the job was not ordered successfully.

JOBL60I SMART ENTITY xxxxxxxx ORDERID=nnnnn ODATE YYYYYY ORDEREDLink copied to clipboard

Explanation: SMART Entity has been ordered successfully.

Corrective Action: No action is required.

JOBL61I SMART ENTITY xxxxxxxx NOT ORDEREDLink copied to clipboard

Explanation: SMART Entity has not been ordered.

Corrective Action:Check for additional messages that explain why the SMART Entity was not ordered successfully.

JOBL62I JOB xxxxxxxx ORDERING BYPASSEDLink copied to clipboard

Explanation: Ordering of job has been bypassed because the SMART Table has not been ordered.

Corrective Action: Refer to previous message(s) that describe why SMART Table has not been ordered.

JOBL63I NO JOBS WERE SCHEDULED. REQUEST IS IGNOREDLink copied to clipboard

Explanation: Performing ORDER request, but no JOB was eligible to be ordered because the scheduling criteria were not satisfied.

Corrective Action: No action is required.

JOBL64E ORDERING FAILED FOR SMART TABLE xxxxxxxxLink copied to clipboard

Explanation: Performing ORDER request of a SMART Table. The order request failed because of an error in the SMART Table.

Corrective Action: Refer to previous message(s) that describes the error.

JOBL65W ORDERING CANCELED BY USER EXITLink copied to clipboard

Explanation: Performing ORDER request of a SMART Table. The order request failed because of an error return code from either the Control-M user exit CTMX001 or the security module CTMSE01.

Corrective Action: Refer to previous message(s) that describes the error.

JOBL66I ORDERING UNIQUE FLOW PROCESS STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTMJOB program has started a UNIQUE FLOW (UFLOW) order request.

Corrective Action: No action is required.

JOBL67I ORDERING UNIQUE FLOW PROCESS ENDED - ID WAS SET TO uidLink copied to clipboard

Explanation: This information message indicates that the CTMJOB program has successfully ordered a UNIQUE FLOW (UFLOW) request.

The uid is the three characters that the CTMJOB adds to all IN and OUT conditions that are part of the UNIQUE FLOW.

Corrective Action: No action is required.

JOBL68W ORDERED UNIQUE FLOW ID. NO VALID CONDITION FOUND. UFLOW REQUEST IGNOREDLink copied to clipboard

Explanation: This warning message indicates that the CTMJOB program did not find any valid conditions that satisfy the UNIQUE FLOW (UFLOW) rule.

For a description of UNIQUE FLOW, refer to the Control-M for z/OS User Guide.

The CTMJOB program will perform the ORDER request as a regular order.

Corrective Action: No action is required.

JOBL69E ERROR IN UNIQUE FLOW ID PROCESSING --- - BACKED OUT order_number ORDER'S REQUESTLink copied to clipboard

Explanation: This error message indicates that the CTMJOB program succeeded in backing out jobs that were ordered as part of the UNIQUE FLOW (UFLOW).

Message JOB511I was issued for the JOBs that were ordered.

The jobs will not be placed in the AJF.

If order_number equals “000” it means that the error occurred before any jobs were ordered as part of the UNIQUE FLOW (UFLOW).

Corrective Action: Correct the error as described in the previous message and reorder the table.

JOBL6AE ERROR IN ORDER FOR UNIQUE FLOW ID --- - BACKED OUT order_number ORDER'S REQUESTLink copied to clipboard

Explanation: This error message indicates that the CTMJOB program succeeded in backing out jobs that were ordered as part of the UNIQUE FLOW (UFLOW).

Message JOB511I was issued for the JOBs that were ordered.

The jobs will not be placed in the AJF.

If order_number equals “000” it means that the error occurred before any jobs were ordered as part of the UNIQUE FLOW (UFLOW).

Corrective Action: Correct the error as described in the previous message and reorder the table.

JOBL6BE UNIQUE FLOW ID - CONDITION IS TOO LONG condition_name DATE dateLink copied to clipboard

Explanation: This error message indicates that the CTMJOB program found an IN or OUT condition name whose length is greater than 36 characters. When the UNIQUE FLOW process adds a prefix of three characters to the condition name, the name will become invalid.

The UNIQUE FLOW process will fail and all jobs will be backed out.

Corrective Action: Shorten the condition name and reorder the table.

JOBL6CE UNIQUE FLOW ID - NOT ENOUGH SPACE FOR CONDITION - condition_name DATE dateLink copied to clipboard

Explanation: This error message indicates that the CTMJOB program failed to add the JOB to the AJF because the UNIQUE FLOW process increased the size of the IN or OUT condition name.

The UNIQUE FLOW process will fail and all jobs will be backed out.

Corrective Action: Compress the AJF or increase the AJF file size. Refer to the INCONTROL for z/OS Administrator Guide.

JOBL6DE ORDER REQUEST REJECTED BECAUSE KEYWORDS "UFLOW" AND "JOB=" ARE MUTUAL EXCLUSIVELink copied to clipboard

Explanation: This error message indicates that the CTMJOB program identified that the UNIQUE FLOW is filtered by "JOB=". UNIQUE FLOW is only for jobs in the table whose scheduling criteria are satisfied.

The UNIQUE FLOW process will not continue.

Corrective Action: Remove the JOB or the UFLOW from the ORDER request and reorder the table.

JOBL6ES ORDER UFLOW SEVERE ERROR RC=return_codeLink copied to clipboard

Explanation: CTMJOB was performing an ORDER request with a Unique Flow ID (UFLOW), but the process failed with an internal error, indicated by RC=return_code.

Corrective Action: Perform the ORDER request again. If the problem persists, do the following:

  1. Add IOA TRACE LEVEL=128 to the JOB as follows:

    CopyCopied to clipboard 
    //DATRACE DD SYSOUT=* 
    //DATRCIN DD *        
    TRACE=128      

  2. Perform the ORDER request again.

  3. Collect the JOB's outputs.

  4. Contact BMC Customer support or open an ISSUE about the problem, attaching the JOB's outputs to the ISSUE.

JSA messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages JSA900 through JSA9xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JSA901S SORT FAILED RC=rcLink copied to clipboard

Explanation: A sort program activated by the CTMJSA utility failed.

In this message, rc is the SORT return code.

The utility stops executing with a condition code of 12.

Corrective Action: Check the SORT manual for the return code and correct.

JSA903S OPEN OF JOBS EXECUTION STATISTICS FILE FAILED. RC=rc ERROR=errCodeLink copied to clipboard

Explanation: The CTMJSA utility is unable to open Control-M Jobs Execution Statistics file.

Possible causes are:

  • The DASTAT DD statement is missing.

  • The DASTAT DD statement describes a file different from the Control-M job execution statistics file.

  • VSAM open error.

  • The statistics file was not properly initialized. (See the FORMSTT job in the Control-M installation library.)

  • The CTMJSA utility was invoked simultaneously from batch and from the online facility (Option S in the Status screen).

The utility stops executing with a condition code of 12.

Corrective Action: Look for VSAM messages or other system messages. Correct the JCL and rerun the job.

JSA904S INVALID RC WHILE READING JOBS EXECUTION STATISTICS FILE. RC=rc ERROR=errCodeLink copied to clipboard

Explanation: An unexpected return code from VSAM during read operation by the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Check the return codes in the related IBM VSAM manuals, and correct the problem accordingly.

JSA905S INVALID RC WHILE WRITING JOBS EXECUTION STATISTICS FILE. RC=rc ERROR=errLink copied to clipboard

Explanation: An unexpected return code from VSAM during write operation by utility CTMJSA.

The utility stops executing with a condition code of 12.

Corrective Action: Check the return codes in the related IBM VSAM manuals, and correct the problem accordingly. If the Job Execution Statistics file reaches its capacity, it is highly recommended to check whether the CTMJSA utility is also accumulating “ad hoc” jobs. Your system programmer should use Control-M exit CTMX005 to control the jobs accumulated to the statistics file.

JSA906S ACCUMULATION STOPPED BECAUSE OF A REQUEST FROM USER EXIT 005Link copied to clipboard

Explanation: The CTMX005 Control-M user exit returned a return code to stop the run of the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Check for messages from the user exit that will clarify the reason.

JSA907S INVALID CLEANUP DATE PARAMETERLink copied to clipboard

Explanation: An invalid value was specified in the CLEANUP parameter of the CTMJSA utility.

The CTMJSA utility is used to collect statistics about Control-M jobs.

The utility ends with errors.

Corrective Action: Specify a valid date (in the format in use at your site), and rerun the utility.

JSA908S {READ | WRITE} ERROR err_num REASON rsn WHILE PERFORMING "CLEANUP". OPERATION WILL BE SKIPPED.Link copied to clipboard

Explanation: An error was encountered while the CTMJSA utility processed the statistics file.

The err_num and rsn are IBM codes returned by IBM VSAM.

Old records are not removed from the statistics file. However, updates to this file are attempted.

Corrective Action: Check the IBM manual Macro Instruction for Data Sets for a list of reason codes and their meaning when processing VSAM files, such as the Control-M statistics file.

JSA909I STAT RECORD: MEMBER memName GROUP groupName WAS actionLink copied to clipboard

Explanation: This information message indicates the action taken against the indicated Statistics job record (with the memName member and groupName group in its key), based upon the CLEANUP criteria specified during a run of the CTMJSA utility.

When the action is DELETED, the entire job record is removed from the Statistics file. When the action is CLEANED, the individual job occurrences in the job record (but not the job record itself) are removed.

Corrective Action: No action is required.

JSA921I ACCUMULATION OF JOB EXECUTION STATISTICS STARTEDLink copied to clipboard

Explanation: This information message is a normal starting message of the CTMJSA utility.

Corrective Action: No action is required.

JSA922I ACCUMULATION OF JOB EXECUTION STATISTICS ENDED WELLLink copied to clipboard

Explanation: This information message is a normal ending message of the CTMJSA utility.

Corrective Action: No action is required.

JSA924S INVALID DATE FORMAT. "DDMMYY" OR "MMDDYY" EXPECTEDLink copied to clipboard

Explanation: Invalid date format specified in the parameters to the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter and rerun the utility. See the INCONTROL for z/OS Utilities Guide for a description of the parameters of the utility.

JSA925S MULTIPLE USE OF PARAMETER. ONLY ONE OCCURRENCE IS ALLOWEDLink copied to clipboard

Explanation: The same parameter has been specified more than once (the CTMJSA utility).

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter and rerun the utility. See the INCONTROL for z/OS Utilities Guide for a description of the parameters of the utility.

JSA926S INVALID ACCUMULATION PARAMETERLink copied to clipboard

Explanation: Invalid parameter specified to the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter and rerun the utility. See the INCONTROL for z/OS Utilities Guide for a description of the parameters of the utility.

JSA927S INVALID DATE FORMAT. "DDMMYY" OR "MMDDYY" OR -"NN" EXPECTEDLink copied to clipboard

Explanation: Invalid date format specified in the parameters to the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter and rerun the utility. See the INCONTROL for z/OS Utilities Guide for a description of the parameters of the utility.

JSA928S "ODATE" MUST BE SPECIFIED WHEN RELATIVE DATE IS USEDLink copied to clipboard

Explanation: The parameters of the CTMJSA utility contained a relative date reference. Therefore, an ODATE must be specified.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter and rerun the utility. See the INCONTROL for z/OS Utilities Guide for a description of this utility.

JSA929S MISSING OBLIGATORY PARAMETERSLink copied to clipboard

Explanation: Some obligatory parameters are missing for the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter and rerun the utility. See the INCONTROL for z/OS Utilities Guide for a description of the parameters of the utility.

JSA930S "FROMDATE" IS AFTER "TODATE"Link copied to clipboard

Explanation: Wrong date range to the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter and rerun the utility. See the INCONTROL for z/OS Utilities Guide for a description of the parameters of the utility.

JSA932W MEMBER=memName MAXIMUM NUMBER TAPE UNITS (number) EXCEEDED FOR JOBLink copied to clipboard

Explanation: During execution of the Control-M utility CTMJSA (Statistics Accumulation), message SPY28GI (Tape usage for the Automatic Tape Adjustment feature) was processed, which specified more than 15 tape units (number) for a tape device type allocated in a job ordered under the memName MEMNAME.

Future automatic allocations of Control-M tape resources may be under-allocated for jobs that exceed a maximum of 15 tape units of a given device type.

A maximum of 15 units for the tape device in question will be stored in the Control-M Statistics file and displayed in the Statistics screen (3.S) for the member.

Corrective Action: No action is required.

JSA933S ERROR MERGING STATISTICS FILE RECORDS. FUNCTION=function RC= rc ERROR=errCodeLink copied to clipboard

Explanation: An unexpected return code from an operation by the CTMJSA utility. If the function prefix is VSM, the attempted operation is indicated as 'oooo' in the FUNCTION=VSMoooo parameter. A function prefix of BSR indicates a non-VSAM internal routine error.

The utility stops executing with a condition code of 12.

Corrective Action: If the function prefix is VSM, check the return codes in the related IBM VSAM manuals and correct the problem accordingly. If the function prefix is BSR, contact BMC Customer Support.