Messages IOAJ00 through IOAJxx

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)

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

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 ADMINISTRATOR

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_shrqnam

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

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

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_num

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 rba

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_cndrec

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

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

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

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

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

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

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

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.

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_dest

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 INACTIVE

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

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

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

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 SUPPRESSED

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 ACTIVE

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

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

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

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

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

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

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

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

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

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 SUPPRESSED

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 TERMINATED

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

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.

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.

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.

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.

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.

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@=addr

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.