Messages IOAL00 through IOALxx

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

IOAL00I IDL FACILITY RECEIVED REQUEST (request)

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

Note:

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 from

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 FROM

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_value

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 RECEIVED

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 CONTINUE

Explanation: The IDL facility encountered an internal problem, which is specified by the error value.

The only valid value for error is:

The IDL facility removes itself. Normal processing of the INCONTROL product continues.

Corrective Action: No action is required.

IOAL06I IDL ENVIRONMENT REMOVED SUCCESSFULLY

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)

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 IDL

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)

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.

Note:

You should contact BMC Customer Support if the variables in this message differ from the following:

• RC=08
• REASON=83000514

MODULE= modThis 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 alias

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 Alias

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)

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)

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)

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)

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)

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)

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)

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)

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)

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}

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 USED

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)

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)

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)

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/item2

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 EXISTS

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)

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)

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}

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)

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 apf

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 BUFFER

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)

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 MODULE

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 EDITABLE

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 ENCOUNTERED

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 MODULE

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 ENCOUNTERED

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 CHANGED

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.

Note:

You should contact BMC Customer Support if the variables in this message differ from the following:

• RC=08
• REASON=83000514

MODULE= modThis 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 STATEMENT

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 SPECIFIED

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 FILE

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 INCLUDE

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 FOUND

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 INCLUDE

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 OPENED

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 STATEMENT

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 INTYPE

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 USED

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 DIRECTORY

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 HONORED

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 OPENED

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 MODULE

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 INVALID

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 FILE

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 SET

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 STARTD

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 SET

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 SYSTEM

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 SET

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 SET

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 SPECIFIED

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 RECORD

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 EMPTY

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 CONTENT

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 STATE

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 DIALOG

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=YES

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 COMBINATION

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 SPACE

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 TABLE

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 SNAP

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 COMMANDS

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 MEMORY

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[*]

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[*]

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[*]

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[*]

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 CODE

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 CODE

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 CODE

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 ELEMENTs

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 ELEMENTs

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) ELEMENTs

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 IDENTIFIED

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)

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 TABLE

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 MODULEs

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 TABLE

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 CHANGED

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)

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 }

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 ALLOCATED

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 DISABLED

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)

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 IDL

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 VERSION

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 TOKEN

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 TOKEN

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 EXIT

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 SPECIFIED

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 PARAMETER

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 CHARACTERS

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 SPECIFIED

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 ADDRESS

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 BINDER

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 PARAMETERS

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 EXCEEDED

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 AVAILABLE

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 LEVEL

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 LOADED

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 ERROR

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 CODE

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 RETRIED

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 RETRY

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 IOAIDL

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 BLOCK

Explanation: The program failed to release the memory allocated for the DESB block.

Corrective Action: No action is required.

IOAL43I TERMINATING IOAIDL

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 IDL

Explanation: The program failed to terminate the IDL facility.

Corrective Action: No action is required.

IOAL45W FAILED TO CLOSE THE LOAD DATA SET

Explanation: The program failed to close the load data set.

Corrective Action: No action is required.

IOAL46I CREATING THE SORT CONTROL STATEMENT

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 SET

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 STORAGE

Explanation: The program failed to release the previously allocated storage.

Corrective Action: No action is required.

IOAL49E FAILED TO SETUP ESTAE

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 DAPRIDL

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 RECEIVED

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 FAILED

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 SET

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 SET

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 SET

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 FAILED

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 FAILED

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 modName

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 FAILURE

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 FAILED

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: groupId

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.