Messages BMCETA258500 through BMCETA258599

CPUID Security module refreshed for imsID

Explanation: The request to refresh the CPU password security in the named IMS control region completed successfully. The password security is updated in the specified IMS control region.

User response: No action is required.

CPUID Security module not refreshed for imsID - RC=returnCode

Explanation: The request to refresh the CPU password security in the named IMS control region encountered an error with the indicated return code. The CPU password security is not refreshed.

User response: Verify that module ETATBL3T, ETATBL3P, or both reside in the IMS STEPLIB concatenation. If not, copy the required modules into a library in the IMS STEPLIB concatenation and try the refresh function again.

User messages successfully refreshed

Explanation: A request to refresh the user messages module used by the specified IMS control region completed successfully. The user message table is updated in the specified IMS control region.

User response: No action is required.

Signon messages successfully refreshed

Explanation: A request to refresh the signon return code module used by the specified IMS control region completed successfully. The signon return code table is updated in the specified IMS control region.

User response: No action is required.

Error encountered refreshing User messages

Explanation: An attempt was made to update the module in the IMS control region that stores the ETA user messages (ETAUMSG0), but the required module was not found in the IMS control region STEPLIB OBLIB concatenation. The user message module is not changed in the specified IMS control region.

User response: Determine why the requested message module was not found in the IMS Control region STEPLIB OBLIB concatenation, correct the problem, and retry the operation.

Error encountered refreshing Signon messages

Explanation: An attempt was made to update the module in the IMS control region that stores the ETA signon messages (ETASMSG0), but the required module was not found in the IMS control region STEPLIB OBLIB concatenation. The signon message module is not changed in the specified IMS control region.

User response: Determine why the requested message module was not found in the IMS Control region STEPLIB OBLIB concatenation, correct the problem, and retry the operation.

value successfully refreshed

Explanation: A request to refresh the parameter named in value was completed in the specified IMS control region.

User response: No action is required.

Error encountered refreshing value, invalid value specified

Explanation: A request to refresh the parameter named in value was not completed because an invalid value was specified.

User response: Correct the chosen value, and retry the refresh function.

Command Security Profiles successfully refreshed

Explanation: In response to a request to refresh the Command Security profiles, the profiles have been refreshed in the IMS control region. Any changes made to the profiles will now take effect.

User response: No action is required.

Command Security ACEE deleted for userID

Explanation: In response to a request to delete the Accessor Environment Element (ACEE) for command security user ID userID, the ACEE has been deleted in the IMS control region. A reference to the user ID will cause the ACEE to be reloaded.

User response: No action is required.

Command Security CSS Userid refreshed for userID

Explanation: In response to a request to refresh the CSS Userid for ID userID, the CSS Userid has been refreshed in the IMS control region.

User response: No action is required.

Exit action performed successfully

Explanation: In response to a request to Deactivate/Reactivate/ Load/Reload an ETA or IMS exit, the chosen exit action has completed successfully in the IMS control region.

User response: No action is required.

New options module, module date/time mismatch

Explanation: An attempt was made to refresh the IMSID or Group options. The link edit date/time stamp of the options in the control region, however, did not match the date/time stamp passed from ISPF. The request is rejected. ETA requires that the date/time stamps match in an attempt to ensure the options are not corrupted and the control region uses the correct options.

User response: Make sure your control region STEPLIB contains the correct options module.

Extended Terminal Assist module module at incorrect product level

Explanation: An ETA module was found to be at an incorrect level. Further processing is not possible. Probable cause is an ETA maintenance mismatch between the named module and the rest of the product load modules. Processing ends.

User response: Determine why the named module is at the incorrect product level. The named module must be at the same version level.

Extended Terminal Assist module module at incorrect IMS level

Explanation: The indicated module is not at the correct IMS level. The IMS control region issues error messages and abends.

User response: Ensure the module listed is correct for this level of IMS.

IMSid options refreshed for imsID

Explanation: A request to refresh the IMSID options in the named control region completed successfully.

User response: No action is required.

Invalid control block requested

Explanation: The control block requested from the DUMP/ZAP screen is not a valid. The request is rejected.

User response: Specify a valid control block.

Descriptor action successfully processed

Explanation: The chosen action for descriptor processing completed successfully.

User response: No action is required.

Descriptor action failed

Explanation: The chosen action for descriptor processing did not complete successfully. The request is terminated.

User response: Check the IMS control region job log for other messages. Contact BMC Customer Support if further assistance is required.

RCNT name, name, duplicates an IMS resource name

Explanation: During descriptor add processing, it was determined that the name of the requested RCNT descriptor duplicated the name of an existing LTERM, RCNT, transaction, LU 6.2 descriptor, or an IMS reserved word. The descriptor request in progress ends without adding the descriptor.

User response: Choose another name for the descriptor. IMS will not allow an RCNT descriptor name to duplicate the name of an existing IMS resource name.

LTERM name, name, duplicates an IMS resource name

Explanation: During descriptor add processing, it was determined that the name of the requested LTERM descriptor duplicated the name of an existing LTERM, RCNT, transaction, LU 6.2 descriptor, or an IMS reserved word. The descriptor request in progress ends without adding the descriptor.

User response: Choose another name for the descriptor. IMS will not allow an LTERM descriptor name to duplicate the name of an existing IMS resource name.

Storage display function not allowed

Explanation: The storage display function is not enabled in the IMSID options. The request is rejected.

User response: This function must be enabled in the IMSID options before it can be used.

Storage alter function not allowed

Explanation: The storage alter function is not enabled in the IMSID options. The request is rejected.

User response: This function must be enabled in the IMSID options before it can be used.

Verify failed for storage to be zapped

Explanation: An attempt was made to alter storage but the data has changed since it was last displayed. This caused the verification process to fail. The request is rejected.

User response: Use the storage display function to display the storage again and attempt the alter function again. If the storage you are trying to alter is volatile, it can be difficult to alter.

Memory access violation

Explanation: An attempt to display storage has resulted in a memory access violation because the control region does not have access to this storage. This message might also be issued if you are attempting to zap a module that resides in key 0 storage. The request is rejected.

User response: Ensure you entered the address of the storage correctly and try again.

Invalid command

Explanation: The command entered is not a valid command for this release of IMS. The command is rejected.

User response: Ensure that the command is typed correctly.

Command not supported

Explanation: The command entered using the IMS Command interface is not supported by ETA. The command is rejected and not processed.

User response: No action is required.

Insufficient WKAP storage to issue command

Explanation: There was insufficient storage in the WKAP pool to execute this command. The command is rejected.

User response: Try the command again later.

Unknown error attempting to issue command

Explanation: An unknown error condition was encountered while executing this command. The command is not processed.

User response: Contact BMC Customer Support.

Storage alteration successful

Explanation: The storage alter function completed successfully. The requested storage was altered.

User response: No action is required.

Dump complete

Explanation: You have displayed IMS control region storage from the IMS Storage Dump/Zap panel. ETA displays the requested storage.

User response: Review or modify the storage.

Invalid request code received

Explanation: A request was made to the IMS control region but the request code was invalid. The request is rejected.

User response: Contact BMC Customer Support immediately with the text from this message and the type of request that was being attempted.

Control block not found

Explanation: A request was made to return an IMS control block, but an IMS control block with the specified name could not be located.

User response: Specify a valid control block name.

Syntax error found within command stream

Explanation: The command stream specified from the DUMP/ZAP screen contains invalid characters. The request is rejected.

User response: Edit the command stream and remove invalid characters.

IMODULE {GETSTOR | LOAD | LOCATE} failed for target, RC=returnCode

Explanation: An internal error occurred during the indicated IMODULE macro call. The variable target specifies the target of the IMODULE call, returnCode is the return code from the IMODULE call. The system action depends on the processing that was taking place at the time of the error.

User response: Review additional error messages to determine what occurred at the time of the error. If this failure is the result of a GETMAIN or GETSTOR call, you might need to increase the region size for your control region. If you are unable to determine the error, contact BMC Customer Support.

IMS service service, function function failed with RC=returnCode

Explanation: An internal error was encountered while processing the indicated IMS service and function. returnCode is the return code from the service. The system action depends on the processing that was taking place at the time of the error.

User response: Review additional error messages to determine what occurred at the time of the error, and contact BMC Customer Support.

RCVY value invalid for SRMDEF setting for {RCVYCONV | RCVYFP}

Explanation: When adding a user descriptor to IMS, the named RCVY value was inconsistent with the specified SRMDEF value. The user descriptor is not added to IMS.

User response: Specify consistent RCVY and SRMDEF settings for the user descriptor and execute the descriptor list again.

SRMDEF invalid for IMS SRMDEF setting

Explanation: When adding a user descriptor to IMS, the SRMDEF value was inconsistent with the IMS SRMDEF value. The user descriptor is not added to IMS.

User response: Specify an SRMDEF value that is consistent with the IMS SRMDEF setting and execute the descriptor list again.

Command not executed, IMS not registered with Operations_Manager (OM)

Explanation: ETA has determined that the target IMS was not registered with any Operations Manager (OM). The type 2 is command not processed.

User response: Restart IMS and point to an IMSPLEX that contains SCI and OM address spaces.

Error returned from OM when executing TYPE 2 command; RC=returnCode, REA=reasonCode

Explanation: OM or IMS failed to process the type 2 command. The return code and reason code are provided.

Some common combinations for return code 08 and various associated reason codes with their main cause are described below.

• Reason=0400004C—Error in loading the module IEANTRT. Detected in module DCEXMEM0.
• Reason=04000050—MVS NAME or TOKEN services error (Module IEANTRT was called to retrieve the TOKEN but a non-zero return code was received from the module). Detected in module DCEXMEM0.
• Reason=0400000C—IMS SCI Information : IMSplex global block (AOPSCISG) was not found in the NAME or TOKEN services. Detected in module DCEXMEM0.
  
• Reason=04000010—IMS SCI Information : IMSplex global block (AOPSCISG) did not have the right eye-catcher 'CSLSPGBL'. Detected in module DCEXMEM0.
• Reason=04000014—IMS SCI Information : the SCI global block was not found in the NAME or TOKEN services. Detected in module DCEXMEM0.
• Reason=04000018—IMS SCI Information : the SCI global block did not have the right eye-catcher 'CSLSSGBL'. Detected in module DCEXMEM0.
• Reason=0400001C—IMS SCI Information : ASCB Address for the IMS SCI was not found. Detected in module DCEXMEM0.
• Reason=0400001D—IMS SCI Information : After getting the ASCB Address, the AXEXT program is called to get the current addressing mode , if the return code is non-zero then it indicates an error. Detected in module DCEXMEM0.
• Reason=0400001E—IMS SCI Information : There was an error while switching to the addressing mode 1. Detected in module DCEXMEM0.
• Reason=04000028—There was an error in opening a TASKLIB DCB. Detected in module DCEXMEM0.
• Reason=04000048—There was an error in obtaining the CSA extension storage (subpool 231). Detected in module DCEXMEM0.
• Reason=04000020—Dynamic Allocation (DYNALLOC macro call) of IMS SCI STEPLIB data set failed. Detected in module DCEXMEM0.
• Reason=04000024—Concatenation of all IMS SCI STEPLIB data sets failed. Concatenation was done using DYNALLOC macro call. Detected in module DCEXMEM0.
• Reason=00000004—The error occurred because version of the caller was not =X'00000115'. Detected in module DCEUAOP0.
• Reason=04000058—AOP_Token address was not valid (address=zero). Detected in module DCEUAOP0.
• Reason=04000054—IMS release dependent module address was not valid (address=zero), Check when passing the control to the release-dependent module. Detected in module DCEUAOP0.
• Reason=04000004—There was an error while loading the DFSVC000 module. Detected in module DCEUAOP0.
• Reason=04000008—The correct release-dependent module was not found in the IMSTAB table. Detected in module DCEUAOP0.
• Reason=24000004—The necessary APF authorization was missing. Detected in module DCEUAOP0.
• Reason=24000008—The XCF Group was not found when the XCF query (IXCQUERY Macro) was called. Detected in module DCEUAOP0.
• Reason=2400000C—The returned XCF SIZE was too small when the XCF query (IXCQUERY Macro) was called. Detected in module DCEUAOP0.
• Reason=24000010—The returned XCF SIZE was too small when the XCF query (IXCQUERY Macro) was called. Detected in module DCEUAOP0.
  
  

System Action: The type 2 command is not processed.

User response: Review the return code and reason code passed from OM. For more information about the return code and reason code, see IBM’s manual for IMS messages and codes.

Extended Terminal Assist chainer function for chain_name failed, RC= return_code

Explanation: An internal error was encountered within the storage chainer for the function and chain indicated. return_code is the return code from the chainer.

System Action: The system action is dependent on the processing that was taking place at the time of the error.

User response: Look for other error messages to determine what happened at the time of the error and contact BMC Software Product Support for assistance.

Command will not be executed, the IMS Common Service Layer (SCI,OM,RM) must be initialized first

Explanation: An attempt was made to execute a type-2 command from the ISPF interface, however a CSL address space (SCI, OM, or RM) has not been initialized.

System Action: The type-2 command is rejected. 

User response: Start the address spaces associated with Common Service Layer.