Messages BMCIPA1000 through BMCIPA1999

This group includes messages for the BMC system administration family of products for IMS.
NumberDescription
BMCIPA1000E

Message Generator initialization failure


Explanation: The Message Generator function failed to initialize.

User response: Contact BMC Customer Support.

BMCIPA1010I

Output from origin system systemOutput


Explanation: This message precedes any command output displayed in the job log of the eLink task. The message indicates from which system the output was generated.

User response: No action is required.

BMCIPA1011I

text


Explanation: This message displays command output in the job log of the eLink or IMS Connect task.

User response: No action is required.

BMCIPA1031I

Energizer for IMS Connect Product Level:productLevel Date:maintenanceDate


Explanation: This message indicates the product's currently active release and maintenance level.

User response: No action is required.

BMCIPA1033E

Recovery not established, RC=returnCode


Explanation: An attempt to establish an ESTAE within the eLink address space failed with the specified return code. The eLink task abends.

User response: Contact BMC Customer Support.

BMCIPA1037E

productTask Task ABEND abendCode


Explanation: The specified product task abended with the indicated abend code.

User response: Contact BMC Customer Support.

BMCIPA1039I

Shutdown Complete


Explanation: The eLink task terminated.

User response: No action is required.

BMCIPA1041E

CIB not freed, RC=returnCode


Explanation: An attempt to free a command input buffer (CIB) failed with the specified return code.

User response: Contact BMC Customer Support.

BMCIPA1043I

productTask TCB Initialization Complete


Explanation: The indicated product task completed the initialization process.

User response: No action is required.

BMCIPA1045I

product TCB Termination Complete


Explanation: The indicated product task completed the termination process.

User response: No action is required.

BMCIPA1052E

Load failed for SERVER options member member, RC=returnCode


Explanation: An attempt to load the indicated UIM server address space options member failed with the specified return code. The UIM server task abends.

User response: Ensure that the indicated options member is located in the load library allocated to the IPROPTS DD statement.

BMCIPA1053E

SERVER options member member is invalid


Explanation: The indicated UIM server address space options member is invalid. The UIM server task abends.

User response: Ensure that the indicated options member was created using the console. Edit the options using the console and ensure that the values are valid.

BMCIPA1054E

Load failed for Global options member member, RC=returnCode


Explanation: An attempt to load the indicated Global options member failed with the specified return code. The UIM server task abends.

User response: Ensure that the indicated options member is located in the load library allocated to the IPROPTS DD statement.

BMCIPA1055E

Global options member member is invalid


Explanation: The indicated Global options member is invalid. The UIM server task abends.

User response: Ensure that the specified options member was created using the console. Edit the options using the console and ensure that the values are valid.

BMCIPA1060E

OPEN failed for DDname ddname


Explanation: An attempt to open the data set allocated to the indicated ddname failed. The UIM server task abends.

User response: Ensure that the data set is available.

BMCIPA1061E

BLDL failed for member member, from DDname ddname, RC=returnCode


Explanation: A BLDL for the indicated member against the data set allocated to the indicated ddname failed. The action being performed fails.

User response: Ensure that the indicated member is located in data set that is allocated to the specified ddname.

BMCIPA1062E

LOAD failed for member member, from DDname ddname, RC=reasonCode


Explanation: A LOAD for the indicated member against the data set allocated to the indicated ddname failed. The action being performed fails.

User response: Ensure that the indicated member is located in data set allocated to the indicated ddname.

BMCIPA1063E

Processing Options member member is invalid, SSI verification failed


Explanation: Verification for the named processing options member failed. The System Status Index (SSI) that is associated with the member is invalid. The options member is invalid and unusable. If the address space is initializing it will abend.

User response: Ensure that the indicated options member was created using the console.

BMCIPA1064E

Processing Options member member is invalid, validation error


Explanation: Verification for the indicated processing options member failed. Validation of internal fields has failed. The options member might be at the wrong level. The options member is invalid and unusable. If the address space is initializing it will abend.

User response: Ensure that the indicated options member was created using the console for the correct level of the product.

BMCIPA1065E

Error reading member member from DDname ddname, error


Explanation: An error occurred while reading the indicated member. The message might list one of the following errors:

  • DATA SET NOT PARTITIONED

  • RECORD LENGTH NOT FIXED

  • RECORD LENGTH TOO SHORT

  • MEMBER NOT FOUND

  • NO BUFFER AVAILABLE

  • ABEND DURING READ

The data set cannot be processed.

User response: Ensure that the indicated DD statement is allocated to a data set of the correct type.

BMCIPA1066E

I/O ERROR, SYNAD DATA: errorData


Explanation: An I/O error occurred. The data set cannot be processed.

User response: Ensure that the DD statement is allocated to a data set of the correct type.

BMCIPA1071E

Journal DDname ddname device allocation error


Explanation: An attempt to allocate the journal data set that is associated with the indicated ddname failed. The specified journal data set is unusable. If no usable journal data sets are found, the journal will not be activated.

User response: Ensure that the indicated journal data set is allocated with the appropriate DCB attributes and is located on DASD.

BMCIPA1073E

Open failed for all Journal Datasets


Explanation: Attempts to open all allocated journal data sets failed. The journal is not active.

User response: Ensure that the journal data sets are allocated with the appropriate DCB attributes and are located on DASD.

BMCIPA1074W

Journal processing terminated - some journal entries discarded


Explanation: Some journal entries might have been discarded because of an I/O error or because a task ended without completing a journal entry. The journal is closed without writing the incomplete buffers.

User response: Contact BMC Customer Support.

BMCIPA1075E

Journal DDname ddname discarded - inconsistent DCB attributes, errorDescription


Explanation: The DCB attributes associated with the journal data set associated with the indicated ddname are invalid or inconsistent with previously allocated journal data sets. The journal data sets must be variable-blocked DASD data sets with identical record lengths and block sizes greater than 1000. The following specific errors might be listed in the message:

  • DSORG=PS required

  • RECFM=VB required

  • record lengths different

  • record length too small

  • blocksizes different

  • blocksize too small

  • blocks/track unavailable

The specified journal data set is unusable.

User response: Ensure that all journal data sets are allocated with the same DCB attributes and are located on DASD. BMC recommends that the logical record length and block size be as large as possible (a logical record length less than 1000 is not allowed). You may specify BLKSIZE=0 to request a system-determined block size.

BMCIPA1076E

Journal processing could not be restarted due to previous errors


Explanation: A restart is required to restart journal processing. Review previous error messages to determine the cause of the journal failure. The journal remains closed.

User response: Contact BMC Customer Support.

BMCIPA1077I

Journal DDname ddname now {OPEN | CLOSED} DSN=dataSetName


Explanation: The journal data set allocated to the indicated ddname is now OPEN or has been CLOSED.

User response: No action is required.

BMCIPA1080E

Open failed for DDname ddname


Explanation: An OPEN request for the indicated ddname failed. The system issues error messages and abends.

User response: Attempt to resolve the situation and restart the task.

BMCIPA1081E

Find failed for member member


Explanation: The indicated member was not found in the job STEPLIB concatenation. The system issues error messages and abends.

User response: Attempt to resolve the situation and restart the task. Contact BMC Customer Support if necessary.

BMCIPA1082E

Module moduleName not loaded


Explanation: The indicated load module was not loaded in the address space. This error is probably an internal logic error. The system issues error messages and abends.

User response: Contact BMC Customer Support.

BMCIPA1083E

CSECT csect not found in load module loadModule


Explanation: The named CSECT not found in the named load module. This error is probably an internal logic error. The system issues error messages and abends.

User response: Contact BMC Customer Support.

BMCIPA1084E

Address verify failed for CSECT csect in load module loadModule


Explanation: The indicated load module read from STEPLIB indicates a reference to the indicated CSECT. Inspection of the load module’s reference to the named CSECT disagreed with the expected value. This error is probably an internal logic error. The system issues error messages and abends.

User response: Contact BMC Customer Support.

BMCIPA1085E

FIND failed for member memberName, from ddname ddname,RC=returnCode,RSN=reasonCode


Explanation: A FIND operation on the indicated member failed. The archival action that is in progress fails.

User response: Ensure that the data set allocated to the indicated ddname contains the indicated member. If you are unable to determine the problem, contact BMC Customer Support.

BMCIPA1086I

Archive JCL member ARCHIPR was not found and journal archiving is disabled


Explanation: The product could not find the indicated archive skeleton JCL member. The archival job cannot be created and journal archiving is disabled. The product bypasses the archival action.

User response: To enable journal archiving, add an ARCHIPR skeleton JCL member to one of the data sets that are allocated to the PROCLIB.

BMCIPA1087E

Open failed for ddname ddname


Explanation: An attempt to open the indicated ddname failed. The open was being performed to obtain the skeleton JCL for the archiving of a journal data set. The archival action that is in progress fails.

User response: Ensure that the PROCLIB data sets are allocated with the appropriate DCB attributes and are located on DASD.

BMCIPA1088E

Journal archival failed due to I/O error while reading ddname ddname


Explanation: An I/O error occurred while reading the skeleton JCL data set for the journal archive job. The archival action that is in progress fails.

User response: Ensure that the indicated DD statement is allocated to a data set of the correct type.

BMCIPA1089E

Open failed for an internal reader


Explanation: An attempt to open an internal reader for journal data set archiving failed. The archival process does not initialize.

User response: Contact BMC Customer Support.

BMCIPA1090I

JOURNAL ARCHIVAL JOB jobName SUBMITTED


Explanation: The indicated job was submitted to archive the closed journal data set. The journal archival process continues.

User response: No action is required.

BMCIPA1091E

Command length error


Explanation: The length of the input command has exceeded the length of the allocated command buffer. The command is rejected.

User response: Input commands are limited to 256 characters. If the command was input from the console, contact BMC Customer Support.

BMCIPA1093E

Command type error


Explanation: The command received and being processed by the OS command processor is invalid. The command is rejected.

User response: Re-input the command.

BMCIPA1095E

Signon error, RC=returnCode


Explanation: An attempt to signon a user has failed with the specified return code. This error is probably an internal logic error. The command being entered is rejected.

User response: Re-input the command. Contact BMC Customer Support, if necessary.

BMCIPA1096E

Signon required


Explanation: An attempt to issue a command has failed because a prior signon was not performed. This error is probably an internal logic error. The command being entered is rejected.

User response: Re-input the command. Contact BMC Customer Support, if necessary.

BMCIPA1097E

Signoff error


Explanation: An attempt to sign a user off after successful command completion has failed. This error is probably an internal logic error.

User response: Contact BMC Customer Support if the problem persists.

BMCIPA1098E

Console communications quiesced for shutdown - command rejected


Explanation: An attempt was made to issue a command after the UIM server started shutdown processing. The command is rejected.

User response: No action is required.

BMCIPA1099I

Command processing complete


Explanation: The command entered has completed processing.

User response: No action is required.

BMCIPA1100I

Command processing complete with errors


Explanation: The command entered has completed processing but errors were encountered.

User response: Review the messages issued to determine the error.

BMCIPA1101I

Stop command acknowledged


Explanation: A request to terminate the eLink task has been received. The eLink task begins termination.

User response: No action is required.

BMCIPA1103I

command


Explanation: This message echoes the command that was entered and is being processed to the eLink job log or IMS Connect task.

User response: No action is required.

BMCIPA1104I

Command issued - no output available


Explanation: The IMS Connect command was issued. Either no wait was requested or no messages were issued within the wait time requested.

User response: No action is required.

BMCIPA1111E

Invalid command input


Explanation: The command being processed is invalid. The command is rejected.

User response: Re-input the command correctly.

BMCIPA1113E

Missing required command keyword


Explanation: One or more required command keywords are missing from the command being processed. The command is rejected.

User response: Correct the command.

BMCIPA1115E

Invalid command keyword encountered


Explanation: The command being processed contains an invalid keyword. The command is rejected.

User response: Correct the command.

BMCIPA1117E

Invalid destination keyword/value


Explanation: The command destination was specified incorrectly, or the target member is not active. The command is rejected.

User response: Correct the command.

BMCIPA1118E

No matching identifier found


Explanation: The specified identifier could not be located.

User response: Ensure that the identifier is valid and reissue the command.

BMCIPA1119E

No valid command destinations found


Explanation: No valid destinations were found that are associated with the target specified on the command.

User response: Specify a valid command destination and reissue the command.

BMCIPA1121E

Command rejected - no journal files are open


Explanation: A command was entered to take action against the journal but no journal files are currently open. The command is rejected.

User response: Ensure that the journal has been properly installed and initialized.

BMCIPA1122E

No trace filters are currently defined


Explanation: A command to display trace filters was received but there are currently no filters defined. The command is rejected.

User response: Use the SET FILTER command to define filters.

BMCIPA1123E

Duplicate identifier


Explanation: A command specified an identifier which already exists. The command is rejected.

User response: Use an identifier that is not already defined.

BMCIPA1125E

Invalid command keyword value encountered


Explanation: The command being processed contains an invalid keyword value. The command is rejected.

User response: Correct the command.

BMCIPA1127E

Command processing failure


Explanation: The command being processed encountered errors and failed.

User response: Review the messages issued to determine the reason for the failure.

BMCIPA1128I

No Router type are currently defined


Explanation: A command to display router definitions was received but there are currently no values defined for the indicated type of definition.

User response: No action is required.

BMCIPA1129I

No ODBM supportType are currently defined


Explanation: Energizer for IMS Connect received a command to display Open Database Manager (ODBM)definitions, but no values are defined for the indicated type of support. Processing continues.

User response: No action is required.

BMCIPA1130I

{INITIALIZATION | SHUTDOWN} in progress - command rejected


Explanation: A command was entered and the eLink is either performing INITIALIZATION or SHUTDOWN processing and cannot process the command. The command is rejected.

User response: If the eLink is in INITIALIZATION, wait until restart completes and reissue the command.

BMCIPA1131I

type options reload processing complete


Explanation: Reload processing completed for the specified options type. Changes specified in the new options were activated.

User response: No action is required.

BMCIPA1132E

type options reload processing failed


Explanation: Reload processing failed for the specified options type. No changes to the specified options were made.

User response: Review any additional messages in the address space job log to determine what errors have occurred.

BMCIPA1133W

type options reload processing complete, some parameters were not updated


Explanation: Reload processing completed successfully for the indicated options type, but some fields that require a restart to change were not updated. Only those parameters which can be changed dynamically were updated. Other fields require that the address space to be recycled.

User response: Review the documentation relating to the options to see which options cannot be changed by RELOAD.

BMCIPA1134W

Filter ID=filterID matches everything, so all filters are ignored


Explanation: An active filter that matches everything will cause all transactions and events to be traced, negating the effect of any other active filters. All other filters are ignored.

User response: Change the state of the identified filter to inactive or delete it to allow other filters to be used.

BMCIPA1140E

User Output Manager error failed, RC=returnCode


Explanation: The User Output Manager has encountered an error. The variable error will be INIT, XFER, or FLUSH. The output cannot be returned to the user.

User response: Contact BMC Customer Support.

BMCIPA1150I

Member memberSystem has {JOINED | LEFT} the XCF group groupName


Explanation: The indicated member system either JOINED or LEFT the indicated XCF group.

User response: No action is required.

BMCIPA1151I

Join for XCF group groupName successful, member name is member


Explanation: The address space successfully joined the indicated XCF group as the indicated member.

User response: No action is required.

BMCIPA1152E

XCF member with token XCFToken not found, message discarded


Explanation: An XCF message was received by this address space but a member with the specified XCF token could not be found in the list of XCF members. The following reasons for obtaining this message are the most common reasons:

  • The partner system terminated after the message was sent.

  • The XCF group being used by the product is not unique and is being used by other address spaces for other purposes.

The message is discarded.

User response: Ensure that the XCF group name specified for the product is unique. To display all of the members joined to the XCF group, issue the following command to the MVS console: /D XCF,GROUP,groupName,ALL where groupName is the XCF group name specified in the options. Ensure that all of the members joined to the group are associated with the product.

BMCIPA1160E

XCF FRR ENTERED FOR RECOVERY


Explanation: An XCF exit routine experienced an error that led to the FRR recovery routine being invoked. A dump will be taken.

User response: Contact BMC Customer Support.

BMCIPA1161E

Energizer for IMS Connect XCFexitRoutineError


Explanation: An XCF exit routine experienced an error for which an SDUMP was attempted. The message indicates the status of the dump, which will be one of the following:

  • SDUMP SUCCESSFUL

  • PARTIAL SDUMP TAKEN

  • SDUMP FAILED

The abend will percolate.

User response: Contact BMC Customer Support.

BMCIPA1250E

XCF message received is too large and is discarded.


Explanation: The eLink has received an XCF message which is too large to handle. The most common cause for this error is that the XCF group specified for the product is not unique and is being used for other processing. The output cannot be returned to the user.

User response: Ensure that the XCF group name specified for the product is unique. To display all of the members joined to the XCF group, issue the following command to the MVS console: /D XCF,GROUP,groupName,ALL where groupName is the XCF group name specified in the message. Ensure that all of the members joined to the group are associated with the product.

BMCIPA1251E

Invalid message received, segmentType segment not found


Explanation: The eLink received an XCF message which is not correctly formatted. The segment type will be PERSISTENT or RESPONSE. The most common cause for this error is that the XCF group name specified for the product is not unique and is being used for other processing. The output cannot be returned to the user.

User response: Ensure that the XCF group name specified for the product is unique. To display all of the members joined to the XCF group, issue the following command to the MVS console: /D XCF,GROUP,groupName,ALL where groupName is the XCF group name specified in the message. Ensure that all of the members joined to the group are associated with the product.

BMCIPA1252E

Cleanup processing in progress for user user


Explanation: During the execution of a user request, the partner system terminated. Cleanup processing is being performed for the indicated user which had a request in process waiting on the terminated system. The process is terminated.

User response: Determine the reason for the partner system failure.

BMCIPA1253E

User blocks not found for userid userID


Explanation: A response message was received by the eLink but the user blocks that are associated with the message could not be found. The output cannot be returned to the user.

User response: If the problem persists, contact BMC Customer Support.

BMCIPA1255E

XCF member not found - response truncated


Explanation: The eLink attempted to send a response back to a partner address space but was unable to locate the member in the XCF group. This problem can occur if the partner system terminates during message processing. The output cannot be returned to the user.

User response: If the problem persists, contact BMC Customer Support.

BMCIPA1257E

Response acknowledgment failed - response truncated


Explanation: The eLink attempted to send a response back to a partner address space but the send process failed. The output cannot be returned to the user.

User response: Review any additional information messages in the eLink joblog.

BMCIPA1258E

Negative acknowledgment received, NAK code=NAKcode


Explanation: The eLink received a negative acknowledgment from the partner system. The NAK code is returned. The process is terminated.

User response: Review any additional information messages in the eLink joblog. Contact BMC Customer Support, if necessary.

BMCIPA1260E

Requested target member is no longer active Job=jobName, System=system, Group=groupName


Explanation: The eLink attempted to send a message to the partner indicated in the message but the partner is no longer active. The process terminates.

User response: Review the eLink job log for any additional information messages. Contact BMC Customer Support, if necessary.

BMCIPA1261E

Send to requested target member failed Job=#jobName, System=system, Group=groupName


Explanation: The eLink attempted to send a message to the partner indicated in the message but the operation failed. The process is terminated.

User response: Review the eLink job log for any additional information messages. Contact BMC Customer Support, if necessary.

BMCIPA1263E

Target XCF member failure detected


Explanation: During command processing, a target member failed, preventing the process from continuing.

User response: Review the eLink job log for any additional information messages. Contact BMC Customer Support, if necessary.

BMCIPA1270I

Maximum user threshold reached


Explanation: The maximum number of users has been reached. No new processes can be initiated until some of the active users are terminated. The process is rejected.

User response: Wait for some of the work that is in progress to complete and retry the operation. Contact BMC Customer Support if the problem persists.

BMCIPA1271W

IMS Connect has not joined an IMSPLEX - default routing is not available


Explanation: The current IMS Connect address space has not joined any IMSPLEX; this address space cannot respond to commands from the BMC application programming interface (API) to the Operations Manager (OM) on the IMSPLEX. Therefore, commands cannot be routed to the current IMS Connect, as is normally the default. If no IMSPLEX is specified, the command is rejected with a syntax error. If IMSPLEX is specified, but no ROUTE list is specified, the command is routed to all members of the specified IMSPLEX.

User response: Ensure that the IMS Connect is set up to join an IMSPLEX in order to route commands to the IMS Connect. Ensure that the IMSPLEX and ROUTE keywords are used to route commands to the desired IMSPLEX members.

BMCIPA1280E

XCF process failed, RC=returnCode, RSN=reasonCode, Group=groupName, Member=member


Explanation: A failure occurred during execution of the specified XCF process. The return and reason codes are returned as well as the XCF group and member name. Valid processes are: IXCJOIN, IXCQUERY, IXCLEAVE, and IXCMSGO. The process is rejected.

User response: For information about the return and reason code for the function being performed, see the appropriate IBM manual. Correct the problem. Contact BMC Customer Support, if necessary.

BMCIPA1281E

Unknown member connected to XCF group groupName, member ignored


Explanation: During product initialization, it was detected that an unknown member is connected to the XCF group used by the product to communicate between the various address spaces. The most common cause for this error is that the XCF group name specified for the product is not unique and is being used for other processing. The member is ignored.

User response: Ensure that the XCF group name specified for the product is unique. To display all of the members joined to the XCF group, issue the /D XCF,GROUP,groupName,ALL command where groupName is the XCF group name specified in the message.

BMCIPA1600I

VTAM console interface is active


Explanation: This message is issued by the eLink to indicate that the VTAM communications interface has become active.

User response: No action is required.

BMCIPA1601E

VTAM vtam RC=returnCode, FDBK2=feedbackCode, description


Explanation: The function specified received the indicated return code and feedback code. Also returned is a brief description of the error. The requested function fails.

User response: Verify that the VTAM interface for the eLink has been properly installed and is active.

BMCIPA1602E

VTAM Console Interface still active - Use STOP CONSOLE to quiesce


Explanation: The START CONSOLE command cannot be issued when the VTAM console interface applid is active. The interface will not terminate until all active sessions are quiesced. The requested function is not performed.

User response: The VTAM applid may be recycled by using the STOP CONSOLE command, waiting for the termination message, and then issuing the START CONSOLE command.

BMCIPA1603E

Energizer for IMS Connect Global Options mismatch in ISPF environment


Explanation: The global options in use by the eLink and those used by the console are not at the same level. The requested function fails.

User response: Ensure that all environments are utilizing the same global options.

BMCIPA1604I

VTAM Console interface is inactive


Explanation: This message is issued by the eLink to indicate that the VTAM communications interface has become inactive. This may be due to an error described by previous messages or due to the STOP CONSOLE command.

User response: The VTAM interface may be restarted by using the START CONSOLE command.

Was this page helpful? Yes No Submitting... Thank you

Comments