|
|
|
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
$RMCALL has been called with parameters which are not consistent with Keyword format (ie. KEYWORD=<value>).
System Action:
Procedure completed in error.
User Action:
Correct the calling procedure and rerun exec.
Reason:
You issued a command against a resource in the P1 P2 system image. However, the ACB name of the region where the command was to be executed could not be resolved. The most likely cause for this is that the selected image is not loaded in any of the linked regions currently.
System Action:
The command is not executed.
User Action:
Ascertain why the remote region's ACB name is not available. Correct the problem, and retry.
Reason:
A command issued from a monitor display cannot be processed due to one of the following reasons:
System Action:
The command is rejected.
User Action:
Check, correct, and retry the command.
Monitor commands can be entered as follows:
Some monitor commands are common to all resources, others apply only to resources of certain classes or types. Some resource classes support more commands than others.
To see a list of valid commands, enter ? at the Command prompt, or on the line next to the selected resource. From this list, you can also select the required command.
If you were attempting to navigate to another part of the product you can use one of the following methods (examples are in parentheses):
Note: Some shortcuts and options might be displayed but their operation suppressed for the following reasons:
To see a list of all shortcuts and their associated functions, enter a single slash (/) at the Command prompt. Select the desired shortcut from the list by entering S beside it.
Reason:
The command has been submitted successfully.
System Action:
Command is processed.
User Action:
None.
Reason:
System Action:
User Action:
Reason:
A request by an external application to issue an alert for a resource completed. P1 is the resource class, P2 is the resource name and P3 is the message.
System Action:
None.
User Action:
None.
Reason:
The specification for the PARMS keyword was invalid. The parameter P1 was passed with a value P2, however the value is invalid.
System Action:
The request is rejected.
User Action:
Check that the parameter being passed is valid for the service and/or action being requested. Retry the request.
Reason:
A request by an external application to issue an alert for a resource completed, however the message was filtered out because it was not relevant for the resource specified. P1 is the resource class, P2 is the resource name and P3 is the message.
System Action:
None.
User Action:
None.
Reason:
A list of possible commands was displayed but you exited from the list without selecting one.
System Action:
None
User Action:
None
Reason:
System Image Prompting was requested for a command but the command processor was running in an environment which does not permit panels to be displayed.
System Action:
Command is rejected.
User Action:
Re-invoke the command in an environment which supports panel displays, or provide SYSNAME= and VERSION= keywords when invoking the command processor.
Reason:
The value identified by P1 is not valid for the field identified by P2.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field.
Reason:
The command request identified by P1 has been cancelled.
System Action:
None.
User Action:
None.
Reason:
Only P1 or P2 are accepted values.
System Action:
The value is rejected.
User Action:
Enter P1 or P2.
Reason:
The command processor has prompted the user to identify the resource to be actioned by the command identified by P1 but the nominated resource does not match the command's TYPE and/or NAME scope values.
System Action:
The resource name is highlighted in error.
User Action:
Nominate a resource which does match the command's scope.
Reason:
A P1 command was submitted but no response was received within a P2 second timeout period.
System Action:
Control is returned to the calling procedure to decide on further processing.
User Action:
Contact your system administrator.
Reason:
The requested action, P1 is rejected because it is already in progress elsewhere. The action was successfully requested at P2 by user P3.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
P1 identified one or more keyword parameters, which are required for
P2 processing, that were not passed by the calling process.
System Action:
The procedure sets a return code of '8' and returns processing to the caller.
User Action:
Set a valid value for the defined keywords and retry.
Reason:
You entered a command beside a resource that belongs to a shared system image. The system affinity list was displayed to enable to you to select the system on which you want to execute the command, but you exited the list without making a selection.
System Action:
The command is not executed.
User Action:
If you want to execute the command, select the target system.
Reason:
The requested action P1 was cancelled at the user's request.
System Action:
None.
User Action:
None.
Reason:
The command processor that was executing the P1 command against the indicated resource has terminated unexpectedly. This may indicate that the command has abended.
System Action:
None.
User Action:
Check the activity log for possible error messages.
Reason:
The command identified by P1 is not a valid command to be issued against a system image loaded on the local system—it may only be issued against a remote system.
System Action:
The command is rejected.
User Action:
Re-issue the command against a connected remote system, or do not issue it at all.
Reason:
A list of System Images, SNA Domains or SNA Resources (as identified by
P1 ) against which a command may be actioned was presented but the user exited without selecting one.
System Action:
Command cancelled.
User Action:
Select a System Image against which to action the command.
Reason:
The command processor, which is executing the command identified by P1 , has not received any response from the command within 20 seconds and has issued this message and unlocked the keyboard so that subsequent commands may be issued. This may indicate that the command is still in progress or may have ended unsuccessfully. Check the log for any errors.
System Action:
Keyboard is unlocked.
User Action:
Check activity log for possible error messages.
Reason:
The command returns this message when the command procedure has terminated without returning any message. This is the default message to indicate that the command has ended.
System Action:
None.
User Action:
None.
Reason:
The combination of NETID and DOMAIN which was specified does not relate to a linked SNA Domain.
System Action:
Fields highlighted in error.
User Action:
Enter a valid NETID and DOMAIN combination.
Reason:
The SNA domain indicated by the NETID and DOMAIN is not currently Active/Available.
System Action:
Procedure completed in error.
User Action:
If the reason is because a remote NetMaster Automation region not being available, rectify and retry the command.
Reason:
The resource identified by P1 is of the type identified by P2 not the required type as specified by P3.
System Action:
Field highlighted in error.
User Action:
Correct and retry.
Reason:
The region specified in P1 has been purged from the list of linked regions.
System Action:
None.
User Action:
None.
Reason:
This message is in response to a LOAD command. The system image selected for loading is associated with subordinate region P1 , but the subordinate region is not currently accessible.
System Action:
The LOAD command is rejected.
User Action:
Determine why the subordinate region is not accessible. It may be inactive, or may be still initializing. You can check the Linked Regions panel for more information on the status of the subordinate region. Enter /LISTREG to display the panel.
Reason:
You are in a subordinate region, and you entered a command beside a resource that is active on a system managed by another subordinate region. From a subordinate region, you cannot access another subordinate region. The resource is in a shared system image and is currently managed by the P1 subordinate region.
System Action:
The command is rejected.
User Action:
Where possible, you should use focal point regions to manage the defined resources.
Reason:
A list of possible resources was displayed, but the user exited the list without selecting a resource.
System Action:
None.
User Action:
None.
Reason:
The command identified by P1 (either ALF or ACKLNKFAIL ) can be issued only against a remote system with which communication has been lost.
System Action:
The command is rejected.
User Action:
None.
Reason:
The command identified by P1 is not valid when issued against a resource that is currently running on a region linked in MIGRATION mode.
System Action:
The command is rejected.
User Action:
Issue the required command from a region which is linked as a FOCAL point or from the resource's home region.
Reason:
This message is in response to a command issued against a remote resource. The region, P1, that owns the resource is not currently accessible.
System Action:
The command is rejected.
User Action:
Determine why the region is not accessible. Enter /LISTREG to display the Linked Regions panel for more information about the link to the region.
Reason:
This message is in response to a command issued against a remote resource. The region, P2, that owns the resource is not currently accessible using APPC function P1. The APPC request sets return code P3 with feedback code P4.
System Action:
The command is rejected. The APPC error message is written to the activity log.
User Action:
Determine why the region is not accessible. Enter /LISTREG to display the Linked Regions panel for more information about the link to the region. Review the activity log message for details of the APPC failure.
Reason:
THIS IS A LONG RUNNING PROCEDURE THAT CA NONLY HAVE ONE COPY RUNNING AT ANY TIME IN EACH SYSTEM. THIS MESSAGE IS PRODUCED IF AN ATTEMPT IS MADE TO START A SECOND OR SUBSEQUENT COPY OF THE PROC.
System Action:
xx
User Action:
cc
Reason:
THIS IS A LONG RUNNING PROCEDURE THAT MAINTAINS ISR STATUS FOR CONSOLIDATED CONSOLES. THIS MESSAGE IS PRODUCED IF AN ATTEMPT TO ISSUE AN ISR ALTER COMMAND RECEIVED AN UNEXPECTED RESPONSE
System Action:
THE SYSTEM HAS NOT CHANGED THE ISR DEFINITION AS DESIRED , BUT WILL LEAVE THE OLD VALUE(S) IN PLACE
User Action:
CONTACT YOUR SYSTEMS ADMINISTRATOR
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No Record added or found for the sysname and version specified
System Action:
The request is rejected.
User Action:
None.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No message profile found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
Profile status already as requested.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to activate the message profiles for console consolidation was rejected because console consolidation is inactive.
System Action:
The request is rejected.
User Action:
If console consolidation is required to be active, then activate it by actioning the CCONSOLIDATN parameter group of Initialization and Customization Services on the Customization Menu. You must set Console Consolidation to ACTIVE and then action the parameter group.
Reason:
An invalid keyword or value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid value specification format was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
This message profile record is already being edited by the user named in the message.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid request was made to the menu handler service procedure. This is a system error.
System Action:
Request was rejected.
User Action:
Call Technical Support.
Reason:
The console consolidation subsystem interface (AOM) is not active and cannot accept the compiled message profiles.
System Action:
Message profile activation has failed.
User Action:
AOM has either not been started in the region initialization deck, or has been paused/stopped by an authorized person. Determine why AOM is not active, correct the situation, then retry the profile activation.
Reason:
The user is not authorized to use AOM facilities. The UAMS security profile did not contain authorisation for P1 to use AOM services. AOM is the Automation Services subsystem interface.
System Action:
Access denied.
User Action:
Contact the appropriate person to grant access (in UAMS) to AOM services.
Reason:
The procedure named in the above message cannot be executed in-line. It must be executed as an asynchronous process. This is a system error.
System Action:
Action rejected.
User Action:
Call Technical Support.
Reason:
Consolidate message delivery is already active for this console.
System Action:
Duplicate activation request is ignored.
User Action:
If you are not receiving messages use the PROFILE command to check that UNSOL=YES AOMMSG=YES MSG=YES and MONMSG=YES. If any of these are not set as described, issue the below command with the console window. PR AOMMSG=Y UNSOL=Y MONMSG=Y MSG=Y
Reason:
The users UAMS profile prevents activation of Consolidated Message Services. 1. The user does not have access to AOM 2. The field AOMMSG is set to NO - should be set to YES 3. The ROUTCDE field set to NONE or is restricted - should be set to ALL
System Action:
Consolidated Message Services is not initialized for this user environment.
User Action:
Correct the users UAMS definition and try again.
Reason:
The Consolidate Message Delivery Service could not be initialized because the desired console environmental profile could not be set.
System Action:
Message delivery not activated.
User Action:
Check the users automation profile and UAMS profile.
Reason:
The Initial OCS environment PROFILE attributes not available.
System Action:
Message delivery not initialized.
User Action:
Check the users automation and UAMS profiles.
Reason:
Consolidate message delivery is pending because the profile setting P1 must be set to YES.
System Action:
None. Messages will be received when UNSOL=YES and AOMMSG=YES and one or more Message Profiles have been enabled (ie ROUTCDE= is set to one or more route code values that match defined and activated message profiles).
User Action:
Use the PROFILE command to set the parameter identified by P1 to YES or use the PROFILE CC command to enable message flow from a full screen panel.
Reason:
Consolidate message delivery cannot deliver any messages until you have enabled one or more Message Profiles.
System Action:
None. Messages will not be delivered until one or more message profiles have been enabled.
User Action:
Use the PROFILE CC command to enable the profiles via full screen panels. You can change your User Profile record to default the enabled message profiles.
You can also use the PROFILE command to set the ROUTCDE parameter to include all the route codes associated with all the message profiles you wish enabled.
Reason:
Message delivery has been activated.
System Action:
Message delivery activated.
User Action:
None.
Reason:
Message flow has be enabled or disabled as requested.
System Action:
As indicated.
User Action:
None.
Reason:
The Consolidated Message delivery manager is not active in this system.
System Action:
The CCON command is not effective.
User Action:
Check the CCONSOLIDATN parameter group to ensure that the value of the Console Consolidation field is ACTIVE. Update the field if required.
If console consolidation is active, check the log for messages that indicate why console consolidation has failed. Review those messages to determine the cause.
Reason:
This message gives the status of both the ability of this console to receive consolidated messages and of the message Inter System Routing (ISR) manager. If ISR is disabled then you will receive messages from the local MVS region only.
System Action:
None.
User Action:
None.
Reason:
This console is profiled to receive messages delivered by the indicated Message Classification profile id numbers. Refer to the EventView Message Classification Profile menu for more detail on the profiles.
System Action:
None.
User Action:
None.
Reason:
Consolidated Message delivery to this console has been switched off.
System Action:
None.
User Action:
None.
Reason:
Consolidated Message delivery to this console was never switched on.
System Action:
None.
User Action:
None.
Reason:
Console consolidation is not active. This is a global setting, and no message profiles are effective.
System Action:
The CCON command is not effective.
User Action:
Enter the /PARMS panel shortcut, and update the CCONSOLIDATN parameter group to set the Console Consolidation field to ACTIVE.
Reason:
An invalid keyword or value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
User access rejected by security procedure.
System Action:
None.
User Action:
None.
Reason:
User change its profile to receive or not to receive aom message.
System Action:
None.
User Action:
None.
Reason:
UAMS prevent user of receiving messages from rout code P1 .
System Action:
None.
User Action:
None.
Reason:
A PROFILE command has been issued to change the consolidated message flow attributes of the OCS environment.
System Action:
None.
User Action:
None.
Reason:
The process requested is not going to change anything.
System Action:
The request is rejected.
User Action:
None.
Reason:
The route code string you have specified contains unsupported routing codes.
System Action:
The request is rejected.
User Action:
None.
Reason:
The program was not able to locate a $RMCCOCS Ncl procedure in this environment to be able to pick up the current msg flow control parameters.
System Action:
The request is rejected.
User Action:
None.
Reason:
The list has been sorted according to the value in P1. This can be either Identification Number or Profile Name. The LstSort command will toggle between the two.
System Action:
None.
User Action:
None.
Reason:
All console message consolidation profiles with STATUS=ACTIVE have now been loaded in all linked regions and are actively filtering messages on all systems.
System Action:
Profile activation functions are complete.
User Action:
None.
Reason:
An invalid keyword or value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The console consolidation subsystem interface (AOM) is not active and cannot accept the compiled message profiles.
System Action:
Message profile activation has failed.
User Action:
AOM has either not been started in the region initialization deck, or has been paused/stopped by an authorized person. Determine why AOM is not active, correct the situation, then retry the profile activation.
Reason:
The user is not authorized to use AOM facilities. The UAMS security profile did not contain autorization for P1 to use AOM services. AOM is the Automation Services subsystem interface.
System Action:
Access is denied.
User Action:
Contact the appropriate person to grant access (in UAMS) to AOM services.
Reason:
The request to obtain exclusive control for the resource P1 was denied. The return code from the lock was P2 and the feed back code was P3. This error indicates that another process or user is accessing the resource.
System Action:
Processing terminates.
User Action:
Retry the action later.
Reason:
Console consolidation message profiles have used the maximum number (P1) of global variables that the profiles can use.
System Action:
Processing terminates.
User Action:
Reduce the number and/or complexity of the message profiles, and retry the request.
Reason:
No STATUS=ACTIVE message consolidation profiles were found.
System Action:
Message consolidation profile activation abandoned
User Action:
Set the desired message profiles to STATUS=ACTIVE and then retry the profile compile
Reason:
The Console Consolidation Subsystem Interface (AOM) has not responded to the profile activation request in the alloted time. This is possibly due to slow response times.
System Action:
Activation in progress
User Action:
Determine the state of AOM. If active and functioning normally then the profile activation will eventually complete. If AOM is not OK then correct the problem and retry the profile activation.
Reason:
Failure accessing RAM initialization parameters.
System Action:
Activation in progress
User Action:
Determine the state of AOM. If active and functioning normally, the profile activation will eventually complete. If AOM is not OK, correct the problem and retry the profile activation.
Reason:
All console consolidation message profiles with STATUS=ACTIVE have now been loaded into global variables and will be active when the screening table is next compiled.
System Action:
None.
User Action:
None.
Reason:
There is insufficient storage to load all the active console consolidation profiles.
System Action:
The profiles are not loaded.
User Action:
Reduce the amount of storage required by the profiles by: * inactivating unused profiles or * reducing the size (complexity) of the active profiles. Retry the activate operation.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The keyword P1 is already referenced by the displayed date.
System Action:
The request is rejected.
User Action:
None.
Reason:
The keyword P1 is not referenced by the date displayed.
System Action:
The request is rejected.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The calendar P1 was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
One or more required fields were not entered.
System Action:
Field(s) set in error.
User Action:
Enter values for the omitted field(s).
Reason:
The selected record is already being updated by user P1.
System Action:
Request rejected.
User Action:
Try later.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
This message forms part of the returned messages on usage of the $RMCLOG procedure.
System Action:
None.
User Action:
The message is informational.
Reason:
A Resource has not been specified. Specify the name of a resource using the keyword NAME and
System Action:
None.
User Action:
Retry the command with the requested parameter.
Reason:
The Global Log Vartable which contains the names of all the resource vartables could not be located.
System Action:
None.
User Action:
Please contact your local support representative
Reason:
No Log vartable could be found for the resource identified by P1 . The procedure issuing the message is identified by P2 .
System Action:
None.
User Action:
Ensure the resource definition has a log table size greater than 0 specified. If this is the case, please contact your local support representative.
Reason:
The resource log for the resource identified by P1 is empty.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the returned messages extracted from the resources log. The timestamp of the record is identified by P1 and the text is identified by P2 .
System Action:
None.
User Action:
The message is informational.
Reason:
This message forms part of the returned messages extracted from the resources log. The NCLID of the procedure writing the message is identified by P1 . The name of the procedure writing the message is identified by P2 and the assigned attribute for the message is identified by P3 .
System Action:
None.
User Action:
The message is informational.
Reason:
A display of outstanding WTORs has been requested for resource P1. However, there are no outstanding WTORs for this resource.
System Action:
None.
User Action:
None.
Reason:
A request was made to display outstanding WTORs for resource P1, but resource P1 is not active.
System Action:
Request is rejected.
User Action:
None.
Reason:
While trying to identify outstanding WTORs for a resource, the command has timed out.
System Action:
None
User Action:
None
Reason:
The command P1 is not available on the current operating system ( P2 ).
System Action:
No command was issued, no response will be returned.
User Action:
None.
Reason:
While trying to issue the requested command for a resource, the command has timed out.
System Action:
None
User Action:
None
Reason:
An attempt to acquire a system console to issue a system command failed because there were no free consoles.
System Action:
The command processor will attempt to acquire a system console again in a short period of time. If successful, the requested command will be issued.
User Action:
None.
Reason:
The requested command was submitted to a system console a number of times but was rejected each time because a required resource is unavailable. The maximum number of retries (as defined in the System Initialization Parameters) was exceeded and so the command failed.
System Action:
The command is not processed.
User Action:
Possible reasons for command rejection are:
Wait a while for the resource to become available and retry.
Reason:
The requested system command was submitted but a required resource was not available. The command processor will wait the specified number of seconds (as defined in the System Initalisation Parameters) before retrying.
System Action:
The command will be re-submitted after the specified number of seconds.
User Action:
None.
Reason:
The requested command failed because the syntax of the request passed to the command processor was invalid.
System Action:
The command is rejected.
User Action:
Correct the command syntax and retry.
Reason:
All response messages for an issued system command have been processed by the command processor.
System Action:
None.
User Action:
None.
Reason:
The command cannot be issued against a resource that is in a Failed or Inactive state. The resource being actioned was P1 and its state at the time of the request was P2.
System Action:
Request is rejected.
User Action:
Activate the resource and then try again.
Reason:
The command cannot be issued because the current operating system version is P1 and the command first became available at version P2.
System Action:
The command is not issued.
User Action:
None.
Reason:
An invalid call was made to the named module.
System Action:
The call is rejected.
User Action:
Report problem to product support.
Reason:
An invalid call was made to the named module.
System Action:
The call is rejected.
User Action:
Report problem to product support.
Reason:
Command cache build was attempted for the command type listed. However, it failed to complete successfully.
System Action:
Command caching for command type shown will be bypassed. This may cause some performance and throughput degradation, but will not affect automation or monitoring.
User Action:
Report problem to product support.
Reason:
The command processor has registered to receive unsolicited messages with a message id of P1 emanating from the job P2.
System Action:
None.
User Action:
None.
Reason:
The command processor has registered to receive unsolicited messages with a message id of P1 irrespective of which job generates them.
System Action:
None.
User Action:
None.
Reason:
The command processor has acquired a system console and issued the command P1.
System Action:
None.
User Action:
None.
Reason:
The command processor has matched the message preceding this one on message id.
System Action:
None.
User Action:
None.
Reason:
The command processor has matched the message preceding this one on elements of its text identified by P1.
System Action:
None.
User Action:
None.
Reason:
The command processor has matched the message preceding this one on the basis of the extended filtering parameters passed on entry.
System Action:
None.
User Action:
None.
Reason:
The command processor has been unable to match any of the passed message criteria and has not received any further messages before the wait period, P1, expired.
System Action:
None.
User Action:
None.
Reason:
Expected command response was not received within the allotted time. This may be due to slow response times. Another cause is that the program to which a command was issued has not responded with a solicited message.
System Action:
The wait for command responses is terminated.
User Action:
Reason:
Expected command responses not received because the response queue was congested with unprocessed messages. The number of unprocessed messages exceeded the limit set by the NMIQLIM parameter.
System Action:
Command response process terminates with relevant return code.
User Action:
Investigate why so many messages are queued.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
A command was issued, but there were no ACTIVE/LINKED system images found against which the command could be actioned.
System Action:
The command is rejected.
User Action:
If this message is issued in response to an 'ADD' command entered on the resource monitor, it means that no system images are currently loaded on this system or any active linked system. Do one of the following:
- If system images exist, load one by entering LOAD at the ===> prompt.
- If no system images have been defined, you can define one by entering /RADMIN at the ===> prompt and selecting option I. Once you have defined a system image, load it as described above.
Reason:
The selected region cannot be contacted. P1 displays the ACB name of the region.
System Action:
The request is rejected.
User Action:
Select a region that is available.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
A display command was requested for resource P1 but the resource definition does not define a display command nor a display process. The resource cannot be displayed.
System Action:
The request is rejected.
User Action:
Define a display command or display process for the resource.
Reason:
An invalid keyword was passed to the user confirmation procedure.
System Action:
The user confirmation procedure terminates with RC=8.
User Action:
Contact your local support representative.
Reason:
The command that was specified on the command line was invalid.
System Action:
The command is rejected.
User Action:
Enter a valid command and retry.
Reason:
Function key P1 was pressed and it has no action assigned to it.
System Action:
None.
User Action:
None.
Reason:
No value was supplied for a mandatory field on the confirmation panel.
System Action:
The field is highlighted in error and the confirmation panel is redisplayed.
User Action:
Enter a valid value in the field or press the Exit key to cancel the request.
Reason:
The nominated system image has already been defined or is the 'active' system image. A new system image must be used for the Express Set Up facility.
System Action:
The System Name and Version fields are highlighted in error and the confirmation panel is redisplayed.
User Action:
Choose another system name/version combination and retry or press the Exit key to cancel the request.
Reason:
An invalid value was supplied for the nominated field.
System Action:
The field is highlighted in error and the confirmation panel is redisplayed.
User Action:
Enter a valid value in the field or press the Exit key to cancel the request.
Reason:
The system image name that you supplied is a reserved system image name and cannot be specified.
System Action:
The field is highlighted in error and the confirmation panel is redisplayed.
User Action:
Enter a valid value in the field or press the Exit key to cancel the request.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The requested resource is not present in the Status Table.
System Action:
Processing terminates in error.
User Action:
Correct and retry.
Reason:
The command issued against this resource is invalid given the physical status of the resource.
System Action:
No further processing.
User Action:
None.
Reason:
The command issued against this resource is invalid unless the resource is in MANUAL or UNATTENDED mode.
System Action:
No further processing.
User Action:
Place resource in MANUAL or UNATTENDED mode and retry.
Reason:
The Log has been successfully reset.
System Action:
None.
User Action:
None.
Reason:
The issued command has been accepted.
System Action:
None.
User Action:
None.
Reason:
The user (P4) has successfully set the field P2, for Resource P1, to the value P3.
System Action:
None.
User Action:
None.
Reason:
A status request has been issued.
System Action:
None.
User Action:
None.
Reason:
The request has been accepted.
System Action:
Processing continues.
User Action:
None.
Reason:
This request is only valid for dynamically defined resources.
System Action:
Request rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The Global Mode is already set to the request mode.
System Action:
The request is rejected.
User Action:
None.
Reason:
The mention request has been cancelled.
System Action:
None.
User Action:
None.
Reason:
Only CONFIRM or CANCEL accepted.
System Action:
The value is rejected.
User Action:
Enter CONFIRM or CANCEL.
Reason:
The value identified by P1 is not valid for the field identified by P2
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field
Reason:
The command request identified by P1 has been cancelled.
System Action:
None.
User Action:
None.
Reason:
The command identified by P1 requested against the resource identified by P2 was rejected for the reason identified by P3.
System Action:
Command rejected.
User Action:
None.
Reason:
This region is licensed as a SOLVE:Operations for IT/Operations or OpenView agent only and cannot be run in automated mode.
System Action:
The request is rejected.
User Action:
If you require a full license, contact Technical Support.
Reason:
The QLOAD command is not supported in full-screen mode. The command is designed for use from a system console or remotely-attached workstation. It returns a line-by-line summary of the active local system image and automation statuses. The information returned is similar to that provided on the confirmation panel when you issue a LOAD command interactively.
System Action:
The command is rejected.
User Action:
None.
Reason:
You issued an ACKLNKFAIL command for the P1 region while the link to that region is still active.
System Action:
The command is rejected.
User Action:
None.
Reason:
The message indicates that the P1 command was issued for the P2 resource. P3 is as follows:
If the number of systems on which the command was issued is one then the value of P3 is the name of the region on that system.
If the number of systems on which the command was issued is more than
one then the value of P3 is the number of systems.
For a resource in a shared system image (if supported), P3 can be greater than 1, which means that the command was issued on all the systems with which the resource has affinity.
System Action:
None.
User Action:
None.
Reason:
A command has been issued against resource P3 ; however, the attribute
P1 which the command is attempting to set is already in the state described by P2.
System Action:
The command is rejected.
User Action:
None
Reason:
A command to perform the action described by P1 has been entered for resource P2 . The command has been accepted and is being actioned.
System Action:
None
User Action:
None
Reason:
You issued an ACKLNKFAIL (ALF) command against a resource in a SHARED system image. This is not allowed because SHARED images receive information from multiple regions.
System Action:
The command is rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The Command Process has been started for the mentioned resource.
System Action:
Audit Message only.
User Action:
None.
Reason:
The Command Processor has ended for the mentioned resource.
System Action:
Audit Message only.
User Action:
None.
Reason:
The Command Processor initiated force inactivation processing.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor is processing a START/STOP/FORCE request for the mentioned resource.
Informational only.
System Action:
Processing continues.
User Action:
None.
Reason:
The Command Processor has issued a System Command for the mentioned resource.
System Action:
Audit message only.
User Action:
None.
Reason:
The Command Processor has been unsuccessful in processing the request.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor has been successful in processing the request.
System Action:
Audit message only.
User Action:
None.
Reason:
The Command Processor has been notified of a resource status change.
System Action:
Audit message only.
User Action:
None.
Reason:
The call to the Status Table API failed.
System Action:
Audit Message only.
User Action:
None.
Reason:
The Command Processor has set the Actual state.
System Action:
None.
User Action:
None.
Reason:
The Command Processor executed the defined process for this resource.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor has set the Mode Override.
System Action:
None.
User Action:
None.
Reason:
The executed process has completed with the following retcode and sysmsg.
System Action:
Informational only.
User Action:
None.
Reason:
Object ID not found and cannot be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact system administrator.
Reason:
The Command Processor has requested the Display Processor to determine the status of the resource.
System Action:
Display processor is inititated for this resource.
User Action:
None.
Reason:
The Display Processor has completed.
Informational only
System Action:
None.
User Action:
None.
Reason:
The monitor message status has been accepted by the Command Processor.
System Action:
No further processing.
User Action:
None.
Reason:
The Command Processor has determined that the resource is in a status that is contradictory to the command issued. eg. The resource was STARTED and the STATUS changed to INACTIVE.
System Action:
No further processing, Automation failed.
User Action:
Verify message definitions are corrected for this resource. Check Log details.
Reason:
If a resource is defined as type LOGICAL the Command Processor will issue START/STOP/FORCE commands, but will then assumed that they have worked.
System Action:
Audit message only.
User Action:
None.
Reason:
The Desired State Engine has changed the resource's operation mode to Manual because the resource was in Automated mode but the required automation command had not been defined in the resource definition.
System Action:
The resource operational mode was changed from Automated to Manual as no further automation was possible because of the missing command.
User Action:
The operator must manually issue the required command. Notify the sites Operations Analyst to define the required command or permanently place the resource in Manual mode.
Reason:
Solicited Message received by the Command Processor.
System Action:
Informational only.
User Action:
None.
Reason:
Unexpected Response received when attempting to issue command.
System Action:
No further processing.
User Action:
Contact System Administrator.
Reason:
The request has timeout, the Command Processor has therefore set the status to the Timeout Status indicated on the Resource definition
System Action:
Informational only.
User Action:
None.
Reason:
A return code of 99 was received from a process. A return code of 99 indicates that the process timed out.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor executed the defined process for this resource.
System Action:
Informational only.
User Action:
None.
Reason:
An error occurred executing a process. Error message is returned in P1.
System Action:
Informational only.
User Action:
None.
Reason:
The processing for command type P1 has been abandoned because it was detected that processing for command type P2 was already in progress. Use of the RES command will flush any current command processing.
System Action:
Command processing terminated.
User Action:
Wait until current command completes before re-submitting the failed command or use the RES command to flush any currently executing commands.
Reason:
Activation processing for a resource has been attempted more than P1 times within the period defined by P2.
System Action:
The resource is placed in a FAILED state, and any system command or process specified in the resource definition is executed.
User Action:
None.
Reason:
The Command Processor will issue the command identified by P1 for the resource identified by P2.
System Action:
Informational only.
User Action:
None.
Reason:
The activation or inactivation process P1 returned a code indicating that the process was unsuccessful. However, while the process was running, the resource has reached its required state P2 (possibly due to events outside the control of the process).
System Action:
The process return code is ignored.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
A Command Traffic Manager requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your System Administrator.
Reason:
Procedure in unexpected APPC "What Received" State.
System Action:
None.
User Action:
Contact System Administrator.
Reason:
A Command Traffic Manager requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your System Administrator.
Reason:
The remote conversation partner has indicated that the last transaction was processed in error.
System Action:
The transaction record is left on the staging file.
User Action:
Contact System Administrator.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The Database still has active users.
System Action:
The request is rejected.
User Action:
Display active users via: SH NDBUSER SH UDBUSERS Clear active users.
Reason:
The listed databases have been successfully cleared.
System Action:
None.
User Action:
None.
Reason:
A database error has occurred.
System Action:
Procedure terminates in error.
User Action:
Contact your system administrator.
Reason:
No databases were selected from the list.
System Action:
None.
User Action:
None.
Reason:
The user has cancelled when asked to confirm the reset of this database.
System Action:
None.
User Action:
None.
Reason:
The call to the RAMDB Utilities procedure $RMDB01M failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $RMDB01M terminates. Control is returned to the procedure that called $RMDB01M.
User Action:
Contact your System Administrator.
Reason:
You have elected to perform export processing but have not selected any components from the list presented.
System Action:
None.
User Action:
None.
Reason:
The data set from which you are importing data is not in the correct format. The data must be in the format OBJECT=objid, or Database Field Name = Value.
System Action:
The request is rejected.
User Action:
Ensure that the correct data set is specified for the import operation. The data must be created from an export using the RAMDB Utilities menu option.
Reason:
You cannot import records to the active system image.
System Action:
The request is rejected.
User Action:
Ensure that the records you are trying to import do not belong to the currently active system image.
Reason:
An import of a file transfer ruleset has been rejected. The file transfer ruleset being imported has the same name as the active file transfer ruleset.
System Action:
The request is rejected.
User Action:
Ensure that the file transfer ruleset being imported is not the active file transfer ruleset.
Reason:
Services cannot be imported to a subordinate region because this region does not support services.
System Action:
The request is rejected.
User Action:
None.
Reason:
The RAMDB import attempted to import a system image that is not supported. This system is a subordinate region and is restricted to system name P1.
System Action:
The request is rejected.
User Action:
Perform the import on a focal region.
Reason:
This is the summary report for the RAMDB Import Utility.
System Action:
None.
User Action:
None.
Reason:
The file operation specified by P1 failed on file P2 and the error is contained in P3.
System Action:
The file operation failed.
User Action:
Refer to the error message found in P3 for more information about the cause of the error.
Reason:
An import of an EventView ruleset has been rejected. The EventView ruleset being imported has the same name as the active EventView ruleset.
System Action:
The request is rejected.
User Action:
Ensure that the EventView ruleset being imported is not the active EventView ruleset.
Reason:
You have canceled a database import request.
System Action:
The request is canceled.
User Action:
None.
Reason:
The database function has ended in error. P1 is the function being performed, P2 is the name of the database, P3 is the system return code, and P4 is the system error message.
System Action:
The current processing terminates in error.
User Action:
Check the status of the NDB database using the SH ALLOC command.
Reason:
The data you are attempting to import was exported from a NetMaster system on a different release level. This is not allowed as RAMDB formats can change between releases.
System Action:
The request is rejected.
User Action:
You can only import the data to a system that has the same base level of software as the system that performed the export. If you browse the data set, the first record will show you the level of the NetMaster base where the export was performed. This must match the base level of the NetMaster system where you are attempting to perform the import. Use the CMD command at the ===> prompt at the top of your screen and the STATUS command to determine the level of your NetMaster system.
Reason:
You chose to perform export processing but no records were found in the database that match the component selected, identified by P1.
System Action:
None.
User Action:
None.
Reason:
The RAMDB Export Utility has started to write the selected records to the data set specified by P1. The records being written belong to the component identified by P2.
System Action:
None.
User Action:
None.
Reason:
The database function has ended in error. P1 is the function being performed, P2 is the name of the database, P3 is the system return code, and P4 is the system error message.
System Action:
The current processing terminates in error.
User Action:
Check the status of the NDB database using the SH ALLOC command.
Reason:
This is the summary report for the RAMDB Export Utility.
System Action:
None.
User Action:
None.
Reason:
The file operation specified by P1 failed on file P2 and the error is contained in P3.
System Action:
The file operation failed.
User Action:
The abend code indicates a system level error, correct the cause of the error and retry the request.
Reason:
An EXPORTRM command has been issued with DISP=MOD for the export data set. The command has failed because the existing data in the export data set is not in the correct format. The first record in the data set must contain LEVEL=nnnnnn.
System Action:
The request is rejected.
User Action:
Remove the DISP=MOD operand, or specify a valid export data set name.
Reason:
An EXPORTRM command has been issued with DISP=MOD for the export data set. The command has failed because the existing data in the export data set was exported from a different release level of the product.
System Action:
The request is rejected.
User Action:
Remove the DISP=MOD operand, or specify the name of an export data set created on the current release level.
Reason:
An invalid keyword value was passed to the Database Maintenance routine. The keyword was P1 and the invalid value was P2 .
System Action:
Request is rejected.
User Action:
Correct the keywords value and retry the request.
Reason:
The keyword P1 must also be specified if keyword P2 is specified.
System Action:
Request is rejected.
User Action:
Correct the parameters and retry the request.
Reason:
The fix application process could not allocate the specified data set because the specified DDname was already allocated to another data set. The specified DDname was P1 and the already allocated data set name is
P2 .
System Action:
Allocation of the data set terminates.
User Action:
Specify another DDname or the already allocated data set name.
Reason:
The fix application process could not open the specified data set because the specified name was already opened with another File ID. The specified name was P1 and the already in use file ID is P2 .
System Action:
Request is rejected.
User Action:
Specify another name.
Reason:
The fix application process could not continue as the specified database was in an invalid NDB state. The NDB file ID is P1 and the DDname specified was P2 and the current status of the NDB is P3 .
System Action:
Request is rejected.
User Action:
Retry the request when the database's current status is ACTIVE.
Reason:
The DDNAME= and the DATASET= keyword are mutually exclusive parameters.
System Action:
Request is rejected.
User Action:
Correct the parameters and retry the request.
Reason:
The Database application utility encountered a syntax error with the fix that was being applied. The expected data was P2 however P3 was found. The line on which the error was detected is P1 .
System Action:
Fix is rejected.
User Action:
Correct the fix and reapply.
Reason:
The database application utility encountered a queue problem. The size of the fix exceeds the total number of messages allowed for the internal dependent command environment queue.
System Action:
The fix is rejected.
User Action:
Contact Technical Support.
Reason:
The Database application utility could not continue because the fix file is empty.
System Action:
Fix is rejected.
User Action:
Specify a fix file that contains a real database fix.
Reason:
The Database application utility could not continue because the fix file was incomplete.
System Action:
Fix is rejected.
User Action:
Correct the fix file, ensuring the fix is complete.
Reason:
The Database application utility could not continue because the fix contained an attribute value assertion that exceeded the maximum of 256.
System Action:
Fix is rejected.
User Action:
Correct the fix file, ensuring all attribute values are not greater than 256 bytes.
Reason:
The command P1 is invalid.
System Action:
Command field is set in error.
User Action:
Enter a valid command.
Reason:
A request to apply a database fix was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
A request to apply a database fix encountered an error. The fix specified an action of P1 , which requires the object being on the target database, however the object was not found.
System Action:
Fix will be rejected, unless FORCE=YES is specified.
User Action:
Determine why the object was not on the target database.
Reason:
A request to apply a database fix encountered an error. The fix specified an action of P1 , which requires the object not being on the target database, however the object was on the database.
System Action:
Fix will be rejected, unless FORCE=YES is specified.
User Action:
Determine why the object was on the target database.
Reason:
A request to apply a database fix encountered an error. The fix was performing the action P1 against the object P2 . Comparisson of the target objects status indicates that the object was modified and is not equal to the distributed object. Applying the fix will regress any of the changes made to the target object.
System Action:
Fix will be rejected, unless FORCE=YES is specified.
User Action:
Determine why the object was modified.
Reason:
A request to apply a database fix encountered an error. The fix specified the action P1 be applied to the object P2 , however due to previous errors the action would not be performed. This is an apply check error. P3 is the created user ID for the object and would normally contain the version or last fix number for the object.
System Action:
Fix will be rejected, unless FORCE=YES is specified.
User Action:
Refer to previous errors for this object.
Reason:
A request to apply a database fix has successfully completed the CHECK phase for the action P1 against the object P2 . The previous level for the object is P3 .
System Action:
None.
User Action:
None.
Reason:
A request to apply a database fix failed.
System Action:
Apply terminates.
User Action:
Check the associated error messages.
Reason:
A request to apply a database fix failed. A previous message indicates the error. The action being performed was P1 , the database return code received was P2 and the object being actioned was P4 .
System Action:
None.
User Action:
Check the associated error messages.
Reason:
A request to apply a database fix has successfully completed the action P1 for the object P2 .
System Action:
None.
User Action:
None.
Reason:
A request to apply a database fix has completed. The check phase had P1 (Either ERRORS or NO ERRORS if all was successfully completed). The apply phase either HAD ERRORS, was NOT PERFORMED or WAS SUCCESSFUL as indicated by P2 .
System Action:
None.
User Action:
None.
Reason:
A request for an Apply Check of a database fix has completed.
System Action:
None.
User Action:
See previous messages.
Reason:
A request for an apply of a database fix has encountered errors however because the FORCE option was specified the apply process will continue with the next object and action.
System Action:
None.
User Action:
See previous messages.
Reason:
A request for an apply of a database fix specified the database file ID P1 .
System Action:
None.
User Action:
None.
Reason:
The Database application utility encountered a syntax error with the fix that was being applied. The expected data was a hex string with an even number of characters, however an invalid hex string was found.
System Action:
Fix is rejected.
User Action:
Correct the fix and reapply.
Reason:
When the fix is applied to the target database then the attribute P1 will be deleted. The current value of the attribute is P2 . A previous message identifies the object.
System Action:
None.
User Action:
None.
Reason:
When the fix is applied to the target database then the attribute P1 will be created. The value of the attribute will be P2 . A previous message identifies the object.
System Action:
None.
User Action:
None.
Reason:
When the fix is applied to the target database then the attribute P1 will be updated. The previious and new values for the attribute will be described in the following RMDB0431 messages.
System Action:
None.
User Action:
None.
Reason:
This is a continuation message for displaying the value of an attribute. See the previous message for more information.
System Action:
None.
User Action:
None.
Reason:
This message displays the OLD or NEW value of an attribute being updated as specified in the previous message. P1 is either "OLD" to indicate the display of an attributes previous value, or "NEW" to indicate its new value. P2 is the actual value.
System Action:
None.
User Action:
None.
Reason:
When the fix is applied to the target database then the object P1 will be modified as described by subsequent messages. P2 is the number of attributes that will be altered. This is a heading message for a difference display for an object that will be updated.
System Action:
None.
User Action:
None.
Reason:
A request to perform the action P1 for object P2 will be ignored because the object does not exist in the target database.
System Action:
None.
User Action:
None.
Reason:
A request to perform the action P1 for object P2 will be changed to action SET because the object already exists in the target database.
System Action:
None.
User Action:
None.
Reason:
A request to perform the action P1 for object P2 will be changed to action CREATE because the object does not exist in the target database.
System Action:
None.
User Action:
None.
Reason:
A request to perform the action P1 for object P2 will not result in any attributes being changed in the target database, because the target database's object is identical to that specified in the fix.
System Action:
None.
User Action:
None.
Reason:
A request to apply or restore the fix P2 failed because the DDNAME P2 did not contain the member name P1 , which should contain the fix source.
System Action:
The request is rejected.
User Action:
Ensure the dataset allocated to DDNAME P2 contains the member P1 and retry the request.
Reason:
A request to restore the delete action for object P1 was ignored because the object does not exist in the distribution database.
System Action:
None.
User Action:
None.
Reason:
A request to restore from action P1 was attempted by invoking action P2 . However the action received an error from the database manager. The return code was P3 and the object of the action was P4 .
System Action:
Restore for the object fails. Processing continues for the next object in the fix.
User Action:
Determine the reason for the database error and retry the restore.
Reason:
A request to restore object P1 failed because the object get from the distribution database failed. The return code was P2 .
System Action:
Restore for the object fails. Processing continues for the next object in the fix.
User Action:
Determine the reason for the database error and retry the restore.
Reason:
A request to restore object P3 from action P1 was perfromed by invoking action P2 against the target database. The action was successful and the object was successfully restored.
System Action:
None.
User Action:
None.
Reason:
A request to restore the create action for object P1 was set instead of delete because the object existed in the distribution database.
System Action:
None.
User Action:
None.
Reason:
The fix was attempting to modify object P1 however the object's stats indicate that it had been modified since distribution or the last fix applied. This is an apply CHECK error. The stats P2, P3, P4 and P5 are last updating User ID, the Date, Time and Domain ID of the update respectively.
System Action:
The fix fails the apply CHECK phase.
User Action:
Determine the reason the object was modified and use the FORCE=YES keyword to force the apply the fix. Then redo the customisations if necessary.
Reason:
The fix was successfully restored. See previous messages for further details.
System Action:
None.
User Action:
None.
Reason:
The restore processing has completed, however errors has occurred. See previous messages for details of the errors.
System Action:
None.
User Action:
None.
Reason:
When the fix is applied to the target database and the DIFF=YES keyword is specified then this message is displayed as the title for the difference display.
System Action:
None.
User Action:
None.
Reason:
A request to restore the set action for object P1 was delete instead of set because the object did not exist in the distribution database.
System Action:
None.
User Action:
None.
Reason:
An error was encountered when attempting to access file. P1 is the operation being performed, P2 is the ID of the file, P3 is the return code and P4 is the message set by the file verb.
System Action:
Database synchronisation terminates.
User Action:
Contact the system administrator.
Reason:
A request to delete a task record was rejected because the task is still in progress. P1 is the task number and P2 is the current status of the task.
System Action:
None.
User Action:
Task records can only be deleted after the task has completed. Wait until the task has a status of ENDED or FAILED before attempting to delete the record.
Reason:
A request to delete a task record was successfully processed.
System Action:
None.
User Action:
None.
Reason:
The task identified by P1 has not generated any log records.
System Action:
None.
User Action:
None.
Reason:
The log for the task identified by P1 no longer exists because the log is not preserved across system restarts and the system has been restarted after the task was started.
System Action:
None.
User Action:
Check the messages in the activity log for the time when the task was running.
Reason:
A call Syntax Error has been detected while processing a RAMDB Maintenance request. P1 contains the details of the error.
System Action:
The request is rejected.
User Action:
Correct the API Call request and re-submit.
Reason:
The value given by the field P1 exceeds the maximum length allowable,
P2, for that variable. P3 names the Field.
System Action:
The request is rejected.
User Action:
Reduce the length of the value to less than or equal to the value indicated by P2.
Reason:
The parameter(s) indicated by P2 are invalid when class is P1.
System Action:
The request is rejected.
User Action:
Remove the P1 parameter or change the class. Then retry.
Reason:
The ACBNAME parameter is invalid for all classes except 02 (STC), 09 (CDMON) and 22 (FTSMGR).
System Action:
The request is rejected.
User Action:
Remove the ACBNAME parameter or change the class. Then retry.
Reason:
The parameter indicated by P1 is invalid unless class is 09, which is CDMON class, or class is 26, which is the FTPMON class.
System Action:
The request is rejected.
User Action:
Remove the P1 parameter or change the class. Then retry.
Reason:
The VOLUME parameter is invalid for all classes except 06 (DASD).
System Action:
The request is rejected.
User Action:
Remove the VOLUME parameter or change the class. Then retry.
Reason:
The SCHEDULE parameter is invalid for classes 09(CDMON), 23(FTSMON), 24(FTSCHED) AND 26(FTPMON).
System Action:
The request is rejected.
User Action:
Remove the SCHEDULE parameter or change the class. Then retry.
Reason:
The SCHEDULE must contain at least one entry consisting of a schedule criteria, start time, pre-processing period, processing period, and post-processing period. Other criteria fields are optional.
System Action:
The request is rejected.
User Action:
Correct the SCHEDULE request by adding a schedule entry which contains at least the required parameters and retry.
Reason:
The maximum file size (in bytes) is less than the minimum file size (in bytes).
System Action:
The request is rejected.
User Action:
Correct the SCHEDULE request making the maximum file size greater than the minimum or the minimum less than the maximum.
Reason:
Schedule entries have been supplied in a request that is not class 24.
System Action:
The request is rejected.
User Action:
Either remove the schedule entries or change the class to 24 for a schedule request and retry.
Reason:
The value presented in P1 exceeds the maximum value allowable, P2, for that variable.
System Action:
The request is rejected.
User Action:
Reduce the value to less than or equal to the value indicated by P2.
Reason:
The parameter value P2 for Field P1 is invalid for the class P3 specified.
System Action:
The request is rejected.
User Action:
Specify a valid value in field P1 and retry.
Reason:
An invalid class has been specified in the request. If this is a System Image Create then Class is not a valid field. If it is a Resource Create request then the Class value specified is not a valid resource class.
System Action:
The request is rejected.
User Action:
Specify a valid class value or remove and retry.
Reason:
The parameter P1 is required for this request.
System Action:
The request is rejected.
User Action:
Add the required field P1 to the request and retry.
Reason:
The value P1 is an invalid value for the field P2.
System Action:
The request is rejected.
User Action:
Correct the value for the field and retry.
Reason:
The parameter indicated by P1 is invalid when type is P2.
System Action:
The request is rejected.
User Action:
Remove the P1 parameter or change the type P2 and retry.
Reason:
An invalid value was specified for QTYPE. Valid values are 'EXIT', 'HOLD', 'TIMER' or 'WAIT'.
System Action:
The request is rejected.
User Action:
Correct the value and retry.
Reason:
An invalid value was specified for the Queue Status. Valid values are 'H', 'HC', 'HE', 'HI','HO', 'HP', 'HR', 'HS', 'R', 'RA', 'RETRY', 'RH', or 'WS'.
System Action:
The request is rejected.
User Action:
Correct the value and retry.
Reason:
Time must be in HH.MM.SS format.
System Action:
Request is rejected.
User Action:
Respecify value and retry.
Reason:
The field indicated by P1 must contain a number in the range specified.
System Action:
Request is rejected.
User Action:
Respecify value and retry.
Reason:
When the parameter Force Termination is 'YES' then either a Force Inactivation Command or Process must be specified.
System Action:
The request is rejected.
User Action:
Add the required field to the request and retry.
Reason:
No records were found to match a List P1 request.
System Action:
None.
User Action:
Information only.
Reason:
An update request was made, using the 'SET' option, for other than a System Image record. Only System Image records may be updated using 'SET'.
System Action:
The request is rejected.
User Action:
Information only.
Reason:
The Parameter indicated by P1 is in error. The reason for the error is indicated by P2.
System Action:
The request is rejected.
User Action:
Correct the parameter and retry.
Reason:
Required fields to create a file transfer schedule have been omitted. The syntax for a Create Schedule request is:
$RMDBAPI SERVICE=CREATE (required)
SYSTEM=xxxxxxxx (required)
VERSION=llll (required)
CLASS=24 (required)
NAME=xxxxxxxxxxxxxxxxxx (required)
SDESC=xxxxxxxxxxxxxxxxxxxxx (required)
CRITn=xxxxxxxxxxxx (required, where n=1-97)
TIMEn=hh.mm (required, where n=1-97)
PREPn=hh.mm (required, where n=1-97)
PROCn=hh.mm (required, where n=1-97)
POSTn=hh.mm (required, where n=1-97)
LONGn=hh.mm (optional, where n=1-97)
FILEn=xxxxxxxxxxxxxxxxxxxxx (required, where n=1-97)
TYPEn=SRC/TGT/ID (required, where n=1-97)
FNUMn=lll (required, where n=1- 97) SRCn=xxxxxxxxxxxxxxxx (optional, where n=1-97)
TGTn=xxxxxxxxxxxxxxxx (optional, where n=1-97)
MINn=llllllllll (optional, where n=1-97)
MAXn=llllllllll (optional, where n=1-97)
System Action:
The request is rejected.
User Action:
Correct the request providing all required parameters, and retry.
Reason:
The service P1 was performed successfully.
System Action:
None.
User Action:
None.
Reason:
The System Image described by P1 (Image name) P2 (Version) does not currently exist.
System Action:
The Resource Create request is not performed.
User Action:
Either specify a different System Image or Create the given image proir to the Resource Create request.
Reason:
The VOLUME parameter is invalid for all classes except 14 (JES LINE).
System Action:
The request is rejected.
User Action:
Remove the LUNAME parameter or change the class. Then retry.
Reason:
You attempted to create a file transfer rule with alert automated actions, but the total storage size required to store the actions has exceeded that which is available for them.
System Action:
The request is rejected.
User Action:
Reduce the number of actions in the request.
Reason:
You have attempted to delete the resource manager, P1 , that currently is the owner of P2 resources. Because the deletion of a manager without prior removal of the dependent resources may lead to unexpected behavior by those owned resources, the request is rejected.
System Action:
The request is rejected.
User Action:
Delete the dependent resources before you delete the manager.
Reason:
The class of resource for which the request is made, P1 , is not licensed for the region in which the request was made.
System Action:
The request is rejected.
User Action:
To create a resource of the P1 class, do one of the following:
- Use a region that is licensed for the class.
- Set up the region again with the correct license.
Reason:
An attempt to create a new File Transfer Ruleset has failed because the Ruleset ( P1 ) already exists.
System Action:
The request is rejected.
User Action:
Check the RSNAME.
Reason:
The parameter field indicated by P1 is invalid for this request. The field name may be incorrect or the field is not relevant to the request being made.
System Action:
The request is rejected.
User Action:
Correct the request, providing only relevant parameters, and retry.
Reason:
The parameter list provided is not in Keyword format. That is parameters that are being passed in the request are not listed in the format 'Keyword'='Value'.
System Action:
The request is rejected.
User Action:
Check the parameter list. Blank spaces within Values may be interpreted as Keywords when 'EXEC' is used to initiate the request or when the value is incorrectly quoted. Beware the following when using &CALL or EXEC:
1)Field values should NOT be enclosed in quotes
2)If using EXEC, then if any field value contains embedded blanks, your calling NCL procedure must use &CONTROL NOVARSEG and the value must be coded as a variable. For instance - &CONTROL NOVARSEG &DCMD = &STR D J,STC1 EXEC $RMDBAPI SERVICE=CREATE.....DISPCMD=&DCMD ... If you are invoking $RMDBAPI to run as a separate process you must pass the field values via keyword parameters on the command and any value containing embedded blanks should be enclosed in quotes.
Reason:
Only one definition can be defined to the system for each of the following classes: SPOOL, JES, EE, and CSM.
System Action:
None.
User Action:
None.
Reason:
The definition you tried to delete was being updated by another user,
P1 .
System Action:
The request is rejected.
User Action:
Retry later.
Reason:
Deletion of a resource, that has owned resources, was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
You exited a list without making a selection.
System Action:
None.
User Action:
None.
Reason:
Only one definition can be defined to the system for each of the following classes: SPOOL, JES, EE, and CSM. A definition for the class indicated ( P1 ) already exists.
System Action:
None.
User Action:
The resource many be suppresed from the Status Monitor display if the monitoring status for the resource is OFF.
Do the following to confirm that a resource in the class indicated exists:
1. Use the /RADMIN.R shortcut to display the ResourceView : Resource Definition panel.
2. Select the appropriate class. The resource list for the class is displayed.
3. To change the monitoring status, update (U) the resource. The list of panels is displayed
4. Select the first panel in the list, (resource type) General Description.
5. Update the Monitoring Activity field to the desired value.
6. Press F3 (File) to file the change.
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
The database record identified by object ID P1 had the action P2 issued against it on date P3 at time P4 by user P5. If the update was originally done on a remote system, then P6 is additional information about when the update was done on the remote system in remote system time.
System Action:
None.
User Action:
None.
Reason:
An internal RAMDB call has failed due to an invalid call syntax or a non-existent function request.
System Action:
Processing is terminated.
User Action:
Contact Technical Support.
Reason:
There was an NDB error on the specified database.
System Action:
None.
User Action:
For information about the DBRC and ERROR fields, enter $INFO on the command line and select NDB Error Codes.
Reason:
There was an NDB warning on the specified database.
System Action:
None.
User Action:
For information about the DBRC and ERROR fields, enter $INFO on the command line and select NDB Error Codes.
Reason:
An object with the specified name was not found in the currently active system image, and is therefore unknown to monitoring on this region.
A system image is a collection of the definitions of all objects required for a NetMaster or SOLVE region to perform monitoring.
Most objects are resources (for example, names of your devices, tasks, and nodes) but objects can also include commands, profiles, filters, and icons.
Multiple system images, identified by different system image names, can be defined for different purposes; however, only one is loaded/active at any time.
System images are stored in the RAMDB VSAM file (referred to in some documentation as the knowledge base).
The system image that is currently active on this region does not contain a definition for this resource name.
System Action:
None. The requested action cannot be performed.
User Action:
A common cause of this message is requesting a diagnostic function on a resource that isn't known. Check for the correct resource name.
If you are typing the name of this resource into a name input field (for example, the Stack Name, Address Space Name, or network device name) check that you have not mistyped the name.
With most name input fields, you can enter ? to display a selection list of names known by the active system image, for example: Stack Name ...+ ?
If you are sure that this is the correct resource name, then check for the correct system image.
Look at this region's monitors to see the active system image and its resources. Use options /RMON, or if using NetMaster for TCP/IP, /IPMON or /IPNODE.
The system image name is at the top right, and consists of a system name and version number, for example, SYS1-0001 or PROD-0004.
Check with whoever set up this region that this is the right system image name. Some possible problems might be:
If this currently active system image is the correct one, then this resource name needs to be added to this system image.
Reason:
An Invalid Field name has been defined.
System Action:
None.
User Action:
Refer to SERVICE/VIEW Technical Support.
Reason:
No Records were found for the specified Search Criteria.
System Action:
None.
User Action:
Verify that you have specified the correct criteria - eg - a valid SYSNAME and VERSION Combination.
Reason:
The limits for an NDB scan were reached or exceeded.
System Action:
The request ends with an error, and no records are returned.
User Action:
You can raise the NDB scan limits by modifying the NDBLIMITS region initialization parameters group.
Reason:
You cannot copy the source onto itself.
System Action:
The request fails.
User Action:
Change the copy target.
Reason:
The option to merge two system images was cancelled at the user's request.
System Action:
Merge does not proceed.
User Action:
None.
Reason:
The record you are trying to add already exists.
System Action:
The request fails.
User Action:
Delete the existing record, or change the name of the one you are trying to add.
Note: If the region supports local, shared, and sysplex system images, the name must be unique across all image types.
Reason:
The class identified by P1 is not supported by the version installed on this system. The most likely scenario is that this region is linked to a region that is at a later version and contains resource classes not known by this region.
System Action:
The request is rejected.
User Action:
Perform the desired request in a region that recognizes this resource class. It is recommended that all monitoring be performed from the latest version of the product as it will be aware of all resource classes.
Reason:
An error was encountered when attempting to write to the staging file.
P1 is the ID of the object that was being processed and P2 is the message set by the staging file maintenance procedure.
System Action:
The database record will not be updated on any linked systems. Processing continues.
User Action:
Determine the cause of the error from the staging file maintenance procedure message and re-update the record in error in order to cause the changes to be transmitted to any linked regions.
Reason:
There was an NDB error on the specified database.
System Action:
The request fails.
User Action:
For information about the DBRC and ERROR fields, enter $INFO on the command line and select NDB Error Codes.
Reason:
A System Image Copy/Delete is underway.
System Action:
None.
User Action:
None.
Reason:
A request to the Database manager has been rejected due to the database being locked.
System Action:
Call is rejected.
User Action:
Contact your Systems Administrator.
Reason:
A serious error has ocurred on the RAMDB. P1 is the NCLID, P2 is the name of the procedure, P3 is the time and P4 is the date.
System Action:
None.
User Action:
None.
Reason:
This message is part of a block of messages detailing a severe database error. These messages show the values of various system and local variables for debugging purposes. P1 is the description of the NDBRC and NDBERRI values.
System Action:
Processing terminates.
User Action:
Save the information, and contact Technical Support.
Reason:
This message is part of a block of messages detailing a severe database error. These messages show the values of various system and local variables for debugging purposes. P1 is number of records processed before the error occurred.
System Action:
Processing terminates.
User Action:
Save the information, and contact Technical Support.
Reason:
This message is part of a block of messages detailing a severe database error. These messages show the values of various system and local variables for debugging purposes. P1 is name of the database access module, and the next message shows the parameters with which the module was invoked.
System Action:
Processing terminates.
User Action:
Save the information, and contact Technical Support.
Reason:
This message is part of a block of messages detailing a severe database error. These messages show the values of various system and local variables for debugging purposes. P1 displays the parameters with which the database access module was invoked.
System Action:
Processing terminates.
User Action:
Save the information, and contact Technical Support.
Reason:
The Database Manager was called with a request to build a sequence which requires the use of a vartable and no vartable name was supplied via the LISTVTAB keyword. Use the LISTVTSC keyword to identify the SCOPE of the VARTABLE.
System Action:
Call is rejected.
User Action:
Use the LISTVTAB and LISTVTSC keywords to identify the NAME and SCOPE of the VARTABLE to be used.
Reason:
The Database Manager was called with action P1 and system image P2 , however the action is not allowed for system images of linked regions.
System Action:
Call is rejected.
User Action:
You can perform this action only on the locally loaded system image or a system image that is NOT loaded on any other system.
Reason:
The resource P1 cannot be added since the same name exists in class P2.
System Action:
Call is rejected.
User Action:
Provide a different resource name, if possible.
If one of the resources is class ASMON then, if possible, delete it and add it again with the Is Name Generic? field set to YES. You should then be able to add the other resource with the same name.
Reason:
A request to the Database manager has been rejected because required information was not supplied with the request.
System Action:
Call is rejected.
User Action:
Contact your Systems Administrator.
Reason:
A request to delete the Link Definition record for the local region from the database was ignored. This record should never be deleted.
System Action:
None.
User Action:
None.
Reason:
You have attempted to delete a data sampling attribute, but it is currently in use in P1 resources.
Subsequent RMDBMS27 messages follow, listing the object ids of the affected resources.
System Action:
The data sampling attribute is not deleted.
User Action:
Update each of the affected resources to remove the attribute and then retry deleting the attribute.
Reason:
A mass update of resources and services (P1) is in progress.
System Action:
None.
User Action:
None.
Reason:
The mass update of resources and services (P1) has ended. The number of records (P2) of the total (P3) is indicated.
System Action:
None.
User Action:
If the number of updated records is less than the total, review the activity log to identify the records that were not updated and the error reason.
Reason:
You attempted to update multiple records with a new value; however, no records qualify for one of the following reasons:
System Action:
None.
User Action:
Check the validity of the selection criteria and retry.
Reason:
You attempted to copy a system image of type p1 into an existing system image of type p2.
You can copy a shared system image to a local system image only; otherwise, the types copied must be the same.
System Action:
None.
User Action:
Specify a different name for your system image to copy to.
Reason:
An attempt was made to perform the action P1 against a protected and distributed attribute. The Copy, Update, and Delete actions only apply to user-defined attributes.
System Action:
The action is not performed.
User Action:
Try another action or select a user-defined attribute for this action. User-defined attributes are displayed in turquoise at the top of the selection list.
Reason:
A delete request was specified for attribute P1 which is selected for monitoring in P2 resources. The count includes resources found in all system images.
System Action:
The delete request is rejected.
User Action:
Ensure that no resource uses these attribute for monitoring.
Reason:
A request was made to list attributes which pass a particular filter criterion but none were found.
System Action:
None.
User Action:
If this is not the desired result, then check the filter.
Reason:
The monitor attribute list display has been refreshed with no filters applied.
System Action:
None.
User Action:
None.
Reason:
A request was made to list the FILTER command options. The command has the following options:
1. FILTER ? - shows the list of FILTER command options.
2. FILTER class - view all attributes associated with a resource class (e.g., FILTER CIP).
3. FILTER attrname*Ù - view all attributes according to a particular name. Optionally, the wildcard '*' lists all attributes beginning with attrname. (e.g., FILTER ifInBytes displays an attribute whose name equals ifInBytes. FILTER Channel* lists all attributes whose name begins with Channel. )
4. FILTER **MULT** - view all attributes associated with multiple resource classes.
5. FILTER - disables filtering FILTER NONE FILTER *
System Action:
None.
User Action:
None.
Reason:
The selected attribute has been deleted successfully.
System Action:
The list is refreshed.
User Action:
None.
Reason:
An exclude class request was specified for attribute P1 which is selected for monitoring in P2 resources. The count includes resources found in all system images.
System Action:
The exclude class request is rejected.
User Action:
Ensure that no resource uses these attribute for monitoring.
Reason:
A request was made to list the resource classes associated with the selected monitoring attribute but none were found.
System Action:
None.
User Action:
None.
Reason:
An invalid value has been entered in field P1 . Correct values for this field are described in P2 .
System Action:
The value is rejected.
User Action:
Correct the value.
Reason:
An attempt was made to add either a new attribute with the same name, or an attribute that has the same first 18 characters of a pre-existing user attribute.
System Action:
The attribute is not added.
User Action:
Change the attribute name and try again.
Reason:
An attribute was successfully stored in the RAMDB
System Action:
The attribute is added to the RAMDB.
User Action:
None.
Reason:
An attempt was made to define an attribute with an attribute type other than ENUMERATED from a MIB object that happens to be enumerated.
System Action:
The attribute type is rejected.
User Action:
Change the attribute type to ENUMERATED.
Reason:
An attempt was made to add a new attribute that has the same name or the same first 18 characters of a reserved system attribute.
System Action:
The attribute is not added.
User Action:
Change the attribute name and try again.
Reason:
An attempt to access RAMDB failed with a return code P1 .
System Action:
The attribute is not added.
User Action:
Contact the system administrator.
Reason:
A request to save a monitoring attribute definition has failed because the MIBinsight details for MIB P1 was not provided.
System Action:
The request is rejected.
User Action:
Press PF10(MibAttr) to complete the MIBinsight details for the selected MIB or erase the MIB Name field before saving the definition.
Reason:
A qualifier filter value has been incorrectly specified. This occurred because of one of the following reasons:
* No MIB object was selected * No MIB qualifier object was selected * The selected MIB object is not part of a MIB table definition and cannot be qualified.
System Action:
The invalid field is highlighted.
User Action:
To select a MIB object, either provide a MIB Name , or press PF10(MibAttr) to select a MIB from the MIBinsight list of loaded MIBs, and scroll through the MIB definition to select the object you want to sample. For you to be able to specify a qualifier object, the the object must be part of a MIB table.
To nominate a MIB object qualifier, press PF11(MibQual) and select the MIB object whose values you want to use to qualify this attribute.
NOTE: The PF11(MibQual) is only available for MIB objects that are part of a MIB table definition.
Reason:
The Attribute Name can consist only of non-blank alphanumeric characters and the following characters:
( ) - parenthesis - - hyphen / - forward slash % - percent sign
System Action:
The field in error is highlighted.
User Action:
Correct the name.
Reason:
An attempt was made to define an attribute with an attribute type which is not inline with the MIB object syntax. When the MIB object syntax is 'Gauge' or 'Gauge32' you can only define a GAUGE attribute, and when the MIB syntax is 'Counter' or 'Counter64' you can only define a COUNTER attribute.
System Action:
The attribute type is rejected.
User Action:
Change the attribute type to a value of GAUGE or COUNTER.
Reason:
No selection was made from the MIBinsight Structure Viewer.
System Action:
None.
User Action:
None.
Reason:
Data sampling initialization is in progress for this resource.
System Action:
No further processing.
User Action:
Retry later.
Reason:
During the initialization of the P1 monitor, the request to start monitoring has failed.
System Action:
None.
User Action:
The message preceding this message indicates the cause of the failure.
Reason:
The change to monitoring attribute P1 will take effect on the next sampling interval for P2 resources.
System Action:
None.
User Action:
None.
Reason:
System initialization has been stalled at the PRE-INIT phase which has resulted in EE monitoring failure.
System Action:
Monitoring will be attempted for the EE resource with a degraded status.
User Action:
Review the activity log to determine the reason why initialization is being stalled in the PRE-INIT phase. In this phase, all VTAM commands are rejected.
Reason:
The keyword parameter P1 was either not specified or an invalid value was specified. P2 is the invalid value.
System Action:
Request is rejected.
User Action:
Correct the call parameters and retry.
Reason:
No data was found for display in the diagram.
System Action:
The Diagram Display call is terminated.
User Action:
None.
Reason:
The command entered on the command line was not recognized by the Diagram Handler.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The select option specified was invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the selection option and retry. Valid may be displayed on the fourth line of the window, otherwise use help to display the valid options.
Reason:
The service procedure P1 passed an invalid value for a variable required for generating a diagram. The service procedure's name is P1 and the varaible incorrectly set is P2 . P3 is the invalid value that was set.
System Action:
Processing is terminated.
User Action:
Correct the variable assignments in the service procedure P1 and retry the request.
Reason:
This is a prompt message which is displayed to allow the user to verify that the selected actions are correct before they are carried out.
System Action:
None.
User Action:
Press the ENTER key to execute the highlighted selections, or press the CANCEL function key to cancel the requested actions.
Reason:
This is an informational message indicating that a print request has successfully been sent to the requested printer. The print request number is P1 and the printer is P2 .
System Action:
None.
User Action:
None.
Reason:
The search string P1 was not found.
System Action:
None.
User Action:
None.
Reason:
A find command was issued and no character string was specified as the find argument and no previous find has been issued. The find command can be specified without a character string, but only if a previous find has been specified with a character string.
System Action:
The command is rejected.
User Action:
Re-enter the command specifying a valid character string.
Reason:
The hierarchical depth of the diagram to be constructed exceeds the maximum allowed. The maximum is 245.
System Action:
Processing terminates.
User Action:
None.
Reason:
The hierarchical structure being diagramatically represented is invalid. It contains at least one set of circular relationships. The child entity P1 is the parent of P2 and P2 is either the parent of P1 or is a grand parent, great grand parent, great great grand parent ... of P1.
For example, A is a parent of B, B is a parent of C, C is a parent of D and D is a parent of A.
System Action:
Processing terminates.
User Action:
Correct the entity relationships so that there are no circular relationships.
Reason:
Procedure $RMDM00S was invoked with invalid parameters.
P1 identifies the invalid parameters.
System Action:
Processing is terminated.
User Action:
Correct the parameters in the calling procedure and rerun the exec.
Reason:
The Desired State Manager for the resource P1 has been started by the initiating process P2.
System Action:
None
User Action:
None
Reason:
The Desired State Manager for resource identifed by P1 has ended.
System Action:
None.
User Action:
None.
Reason:
A database read for the record identified by P1, which is a relative of P2 has failed.
System Action:
Processing is terminated.
User Action:
Ensure the correct database record is entered.
Reason:
The Desired State Manager attempted to start a process for P1 but there was already a request in progress. This request will be terminated.
System Action:
The request is rejected.
User Action:
Wait for the current process to complete before entering request.
Reason:
The resource P1 is in the automation mode identified by P2. No automation action will be taken because of the automation mode.
System Action:
The request will be rejected.
User Action:
Review the automation mode.
Reason:
P1 is the resource, its desired state is P2, its actual state is P3, its automation mode is P4 and its automation status is P5.
System Action:
None.
User Action:
None.
Reason:
The action specified by P1 has been requested of resource P2.
System Action:
None.
User Action:
None.
Reason:
The resource display processor has been started for resource P1 and the actual state of the resource will be determined.
System Action:
None.
User Action:
None.
Reason:
The Desired State Manager has been started for resource P1. P2 identifies the nature of the relationship to P3.
System Action:
None.
User Action:
None.
Reason:
The resource P1 is not found in the status table as the mode may be specified as off.
System Action:
None.
User Action:
None.
Reason:
The status inquiry completed with return code P1 and has an actual status of P2.
System Action:
None.
User Action:
None.
Reason:
The resource P1 has no P2 relationship.
System Action:
None.
User Action:
None.
Reason:
Resource P1 is in the desired state of P2. The Desired State Manager will now check its P3.
System Action:
None.
User Action:
None.
Reason:
Command of P1 has been completed with return code P2 and system message P3.
System Action:
None.
User Action:
None.
Reason:
Automation has failed for resource P1 and automation has been bypassed.
System Action:
Resource automation state is flagged as failed.
User Action:
Review resource to determine reason for failure.
Reason:
The resource P1 has a relationship of P2 to P3 in state P4.
System Action:
None.
User Action:
None.
Reason:
Resource P1 has changed to desired state P2 and physical state P3.
System Action:
None.
User Action:
None.
Reason:
Resource P1 has had its automation state set to failed.
System Action:
The automation status is flagged as failed.
User Action:
Review resource to determine cause of failure.
Reason:
Resource P1 has not been set to P2 which is either active or inactive.
P3 identifies the number of resources, P4 identifies the nature of the resources relationship with P1 and P5 identifies the state of the resources which is either active or inactive.
System Action:
Processing is terminated.
User Action:
Ensure resources specified are either activated or inactived as required.
Reason:
P1 for resource P2 is in progress. The desire state lock text is
P3.
System Action:
None.
User Action:
None.
Reason:
The Desired State Manager is starting for resource P1.
System Action:
None.
User Action:
None.
Reason:
The schedule of resource P1 has set resource P2 to the desired state of inactive.
System Action:
None.
User Action:
None.
Reason:
The schedule state override flag has been set by P1. A check will be made to ensure that P1 still requires the resource to be overridden.
System Action:
None.
User Action:
None.
Reason:
The schedule state override flag has been reset as resource P1 is already in a desired state of active.
System Action:
None.
User Action:
None.
Reason:
The desired state override flag set by resource P1 is still in place and does not require to be reset.
System Action:
None.
User Action:
None.
Reason:
A desired state manager has started P1 desired state managers for related resources and will now enter a latency period of no longer than
P2 seconds. The latency period will end before P2 seconds if a state change event occurs for the resource or if all the started desired state managers complete processing.
System Action:
None.
User Action:
None.
Reason:
The latency period ended because of one of the following:
- All the started desired state managers ended.
- The latency period expired.
System Action:
None.
User Action:
None.
Reason:
A state change was received for resource P1 during the latency period while waiting for an event.
System Action:
None.
User Action:
None.
Reason:
A tree-inact of resource P1 has set resource P2 to a desired state of inactive.
System Action:
None.
User Action:
None.
Reason:
Entering wait period for resource P1 to either become active or inactive.
System Action:
None.
User Action:
None.
Reason:
The desired state manager detected that ARM recovery for a resource has failed. p1 is the failure reason.
The region will try to restart the resource.
System Action:
The region tries to restart the resource.
User Action:
None.
Reason:
The home system of the P1 resource is not P2 . During automation, the Desired State Manager can start a resource only on the home system of the resource.
System Action:
Processing is canceled.
User Action:
If you want the P1 resource to be able to start on the P2 system during automation, specify P2 as the home system of the resource.
Reason:
The Desired State Manager tried to shut down the P1 resource, but the resource is currently running on another system, P2 .
System Action:
Processing is canceled.
User Action:
None.
Reason:
The desired state manager detected that ARM recovery for a resource has denied a restart. p1 is the failure reason.
The region does not restart the resource.
System Action:
None.
User Action:
Review the related ARM policy specifications.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The Resource mention doesn't have either a Display Command or Display Process defined for it in it's RAM Database definition.
System Action:
Audit message only.
User Action:
None.
Reason:
The Display Process has been started for the mentioned resource.
System Action:
Audit Message only.
User Action:
None.
Reason:
The Display Processor has ended for the mentioned resource.
System Action:
Audit Message only.
User Action:
None.
Reason:
The Display Processor has been called to GET/SET the Actual state.
System Action:
Audit message only.
User Action:
None.
Reason:
The Display Processor has determined the Actual State to be as mentioned.
System Action:
Informational only.
User Action:
None.
Reason:
The Display Processor has issued a command identified by P1 for the resource. This is an audit message.
System Action:
Processing continues.
User Action:
None.
Reason:
The Display Processor has been called to determined the JOBID or ASID for a resource.
System Action:
Informational only.
User Action:
None.
Reason:
Results of ASID or JOBID request.
System Action:
Informational only.
User Action:
None.
Reason:
The Display Processor has set the Actual State to that mentioned.
System Action:
None.
User Action:
None.
Reason:
The Display Processor executed the defined process for this resource.
System Action:
Informational only.
User Action:
None.
Reason:
The executed process has completed with the following retcode and sysmsg.
System Action:
Informational only.
User Action:
None.
Reason:
A Display Processor is already in progress for this resource.
System Action:
No further processing.
User Action:
None.
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
A Display Table vartable error has occurred.
System Action:
Procedure terminates in error.
User Action:
Contact System Administrator.
Reason:
Solicited Message received by the Display Processor.
System Action:
Informational only.
User Action:
None.
Reason:
The region tries to start the display processor for the P1 resource, but the resource is defined as not eligible to run on this system. The eligibility of a resource to run on a system is determined by the system affinity specified in the resource definition.
System Action:
Processing is canceled.
User Action:
If you want to indicate that the P1 resource can run on the P2 system, update the system affinity in the resource definition.
Reason:
The region tries to start the display processor for the P1 resource, but the resource is currently running on another system, P2 .
System Action:
Processing is canceled.
User Action:
None.
Reason:
This message is issued by the display process for Link Resources.
P1 is the name of the link.
P2 is the type of link (DATA, EVENT,and so on).
P3 is the link status.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The message indicates that the action indicated by P1 has been taken for the system and version identified by P2 and P3 .
System Action:
The message is written to the log.
User Action:
None; the message is informational only.
Reason:
The resource identified by class name P1 and name P2 has no parents. A desired state manager has been started for this resource.
System Action:
A desired state manager is started for the resource.
User Action:
The message is informational only.
Reason:
The resource identified by class name P1 and name P2 has no children. A desired state manager has been started for this resource.
System Action:
A desired state manager is started for the resource.
User Action:
The message is informational only.
Reason:
The exit identified by P2 for action identified by P1 has been initiated.
System Action:
Control is passed to the exit identified.
User Action:
The message is informational only.
Reason:
The action identified by P1 completed with return code P2 and returned message P3 .
System Action:
Control is returned to desired state processor.
User Action:
The message is informational only.
Reason:
A Global Mode value was not passed to the procedure.
System Action:
Processing is terminated.
User Action:
Ensure the procedure is being called with the correct parameters.
Reason:
The actual state of the resource identified by P1 is unknown.
System Action:
A desired state manager is started for the resource.
User Action:
The message is informational only.
Reason:
The action identified by P1 was not performed due to a non-zero return code from the exit P2 .
System Action:
Processing for the action identified is discontinued.
User Action:
Check the reasons for the non-zero return code and retry the action.
Reason:
The desired state for resource P1 has been set to inactive in response to a shutdown request.
System Action:
Processing continues.
User Action:
The message is informational only.
Reason:
This region is licensed as a SOLVE:Operations for IT/Operations or OpenView agent only and cannot be run in automated mode.
System Action:
The request is rejected.
User Action:
If you require a full license, contact Technical Support.
Reason:
A Database Event Manager requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your System Administrator.
Reason:
The database function has ended in error.
System Action:
Return code 0,4 processing continues. Return code greater than 4 processing terminates in error.
User Action:
Contact System Administrator.
Reason:
An invalid sequence of chained records has been received in a transaction.
System Action:
This transaction is not processed any further.
User Action:
Contact System Administrator.
Reason:
A staging file record has been read which has an invalid transaction type specified.
System Action:
This transaction is not processed any further.
User Action:
Contact System Administrator.
Reason:
A staging file record has been read which has an invalid access method specified.
System Action:
This transaction is not processed any further.
User Action:
Contact System Administrator.
Reason:
An error has been encountered by the remote APPC conversation partner.
System Action:
Processing continues.
User Action:
Contact System Administrator.
Reason:
Registration Table error encountered.
System Action:
Procedure terminates in error.
User Action:
Contact System Administrator.
Reason:
A link manager received data from its remote partner.
System Action:
None.
User Action:
This message is written to a link manager's transient log when 'Log Internal Audit Trail' is set to YES in the resource definition and can be used to aid in link problem diagnosis.
Reason:
The database is blocked. This database is isolated from all remote regions.
System Action:
The database event manager will terminate.
User Action:
None.
Reason:
A Database Event Manager requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminated in error.
User Action:
Determine whether the link to the remote system has failed. If the link has failed, the region will try to recover the link. Otherwise, contact Technical Support.
Reason:
The database function has ended in error.
System Action:
Return code 0,4 processing continues. Return code greater than 4 processing terminates in error.
User Action:
Contact System Administrator.
Reason:
A staging file function has terminated in error.
System Action:
Processing terminates in error.
User Action:
Contact System Administrator.
Reason:
A staging file record has been read which is invalid.
System Action:
This transaction is not processed any further.
User Action:
Contact System Administrator.
Reason:
The remote conversation partner has indicated that the last transaction was processed in error.
System Action:
The transaction record is left on the staging file.
User Action:
Contact System Administrator.
Reason:
A staging file function has terminated in error.
System Action:
Processing terminates in error.
User Action:
Contact System Administrator.
Reason:
The P1 object could not be formatted for transmission. The most likely cause is if a definition exceeds the maximum transmittable size of 32 KB, as indicated by ZMDORC(8) and ZMDOFDBK(2).
System Action:
The transaction fails. The object is not updated on the remote region's database.
User Action:
For ZMDORC=8 and ZMDOFDBK=8, update the P1 defintion to reduce its size. Once the record is small enough, the remote database's copy will be updated automatically. For any other return code/feedback, contact your systems administrator.
Reason:
A failure occured processing a transaction for transmission to a linked region. The failure reason is described in the sysmsg P2 .
System Action:
The transaction fails. The object is not updated on the remote region's database.
User Action:
Contact your systems administrator.
Reason:
The 'HEX ATTR' option has been selected with the cursor positioned on a special character such as a DBCS shift character. This character is not eligible for display/alter.
System Action:
None.
User Action:
Position the cursor elsewhere and retry.
Reason:
The 'HEX ATTR' edit option has been selected, but the cursor is not positioned within the body of the text.
System Action:
None.
User Action:
Position the cursor within the body of the text and retry.
Reason:
The automatic restart manager (ARM) policy has become inactive, and the region takes control of the monitored resources that are registered to ARM.
The region relinguishes control back to ARM when the ARM policy becomes active again.
System Action:
The region takes control of the monitored resources that are registered to ARM.
User Action:
None.
Reason:
The ENF events receiver procedure was invoked without the required keyword, P1 .
System Action:
The request is rejected. The procedure ends with return code 8.
User Action:
Contact your local support representative.
Reason:
The events receiver failed when issuing an EPS request. The failure is identified by the following:
- Type of EPS request, P1
- Return code, P2 (&RETCODE)
- Error number, P3 (&ERRNO)
- Reason, P4 (for example, EPS UNAVAILABLE)
A possible cause is data corruption.
System Action:
The event is discarded, and processing continues. The ENF events receiver will attempt recovery.
User Action:
Contact your local support representative.
Reason:
The P1 resource was registered to or deregistered from the automatic restart manager, as indicated by P2 .
System Action:
None.
User Action:
None.
Reason:
The ENF events receiver failed due to an MDO error. The failure is identified by the following:
- The statement type, ASSIGN - The MDO return code, P1 (&ZMDORC)
- The MDO feedback code, P2 (&ZDMOFDBK)
- The map name, P3 (&ZMDOMAP)
- The full map component name, P4 (&ZMDONAME)
- The map component tag value, P5 (&ZMDOTAG)
- The ASN.1 type of the component, P6 (&ZMDOTYPE)
This failure indicates one of the following causes:
- An invalid record has been received.
- There is a mismatch between the ASN.1 map and the record.
System Action:
The procedure terminates.
User Action:
Contact your local support representative.
Reason:
The ENF events receiver procedure is ready to receive ENF events by using EPS services. The associated EPS receiver ID is P1 .
System Action:
The region is ready for ENF events processing. If required, the product specific events handler will be started when the first event is received.
User Action:
None.
Reason:
Recovery is attempted after an EPS request failure (see RMENFRC01).
System Action:
Reconnection to EPS is attempted.
User Action:
None.
Reason:
The required EPS services are currently unavailable. Events monitoring will resume as soon as EPS services are restored.
This message follows the RMENFRC01 message.
System Action:
The region waits for EPS to become available.
User Action:
Ensure that an SSI region is currently active with its event processor enabled.
From any panel, enter /PARMS and check the SSI parameter group. Ensure that the Sub- System Interface ID field contains the correct ID.
Reason:
An unrecoverable error occurred during an EPS request (see message RMENFRC01). Monitoring of ENF events has stopped.
System Action:
The ENF events receiver is terminated.
User Action:
Contact your local support representative.
Reason:
The database is blocked. This database is isolated from all remote regions.
System Action:
The database event manager will terminate.
User Action:
None.
Reason:
A Unsolicited Event Manager requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your System Administrator.
Reason:
Procedure in unexpected APPC "What Received" State.
System Action:
None.
User Action:
Contact System Administrator.
Reason:
The transaction request from remote conversation partner is not recognized.
System Action:
This transaction is not processed any further.
User Action:
Contact your system administrator.
Reason:
The status table function has ended in error.
System Action:
Processing continues.
User Action:
Contact Technical Support.
Reason:
The status table function has ended in error.
System Action:
Processing continues.
User Action:
Contact System Administrator.
Reason:
Registration Table error encountered.
System Action:
Procedure terminates in error.
User Action:
Contact System Administrator.
Reason:
Duplicate active images in remote regions.
System Action:
Processing terminates in error.
User Action:
Contact your system administrator.
Reason:
The RAM Database correlator id doesn't match with the remote RAM Database correlator id. This is a requirement for two systems to transfer database traffic.
System Action:
The Database Event Manager will terminate.
User Action:
None.
Reason:
The RAM Database doesn't have a Database Information Record defined. Therefore no correlator id checking can be performed.
System Action:
The Database Event Manager will terminate.
User Action:
The database has not been initialized correctly. Contact your System Administrator.
Reason:
A link manager received data from its remote partner.
System Action:
None.
User Action:
This message is written to a link manager's transient log when 'Log Internal Audit Trail' is set to YES in the resource definition and can be used to aid in link problem diagnosis.
Reason:
A Unsolicited Event Manager requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminated in error.
User Action:
Determine whether the link to the remote system has failed. If the link has failed, the region will try to recover the link. Otherwise, contact Technical Support.
Reason:
The Event Handler task was successfully started.
System Action:
None.
User Action:
None.
Reason:
The Event Handler task was successfully ended.
System Action:
None.
User Action:
None.
Reason:
The Event Handler received and processed the indicated event.
System Action:
None.
User Action:
None.
Reason:
The Event Handler received an event which indicated that a Desired State Manager should be invoked for the indicated resource. However, a Desired State Manager was already in progress for the indicated resource, so it was not re-invoked.
System Action:
None.
User Action:
None.
Reason:
A resource was not in AUTOMATED mode, so a desired state change was not actioned.
System Action:
None.
User Action:
None.
Reason:
Resource P1 has desired status of P2, actual status of P3, and automation mode of P4.
System Action:
None.
User Action:
This message is informational only.
Reason:
Resource P1 has is not in its desired state. A Desired State Manager process will be started to attempt to place it in its desired state.
System Action:
None.
User Action:
This message is informational only.
Reason:
The display processor is being invoked to determine the current status of a resource.
System Action:
None.
User Action:
This message is informational only.
Reason:
An event was received for a resource but the resource definition was not present in the status table.
System Action:
The event is not processed.
User Action:
Contact Technical Support.
Reason:
The Event Handler procedure was started, but another copy of the procedure was already running.
System Action:
The new copy of the procedure terminates.
User Action:
None.
Reason:
An event was received by the Event Handler that will prevent further monitoring of resources.
System Action:
Monitoring of resources will cease until the problem has been rectified.
User Action:
Determine the cause of the error from the messages following this one in the activity log.
Reason:
The Event Handler is temporarily not monitoring the status of resources. This mode is entered when a large number of resources are changing status simultaneously such as during a System Image load. P1 indicates the reason that the Event Handler entered 'idle' mode.
System Action:
Monitoring of resource status ceases until the condition causing the monitor to go into 'idle' mode has completed.
User Action:
Most conditions which cause the Event Handler to be placed in idle mode will resolve themselves without user intervention, however some do require user action. If P1 is:
RAMDB SHORT OF STORAGE issue the STARTSYS command once sufficient storage is available. If this is not possible the region will need to be restarted.
AOM MESSAGE QUEUE OVERFLOW issue the AOMRECOVER command once message traffic has subsided.
Reason:
This message follows message EV0015 and indicates the nature of the problem.
System Action:
None.
User Action:
None.
Reason:
The Event Handler has detected an AOM Message Queue Overflow condition and has gone into idle mode, to prevent unnecessary processing of events. This message will be followed by others outlinig the action taken to attempt to rectify this situation.
System Action:
Event Handler placed in idle mode.
User Action:
None.
Reason:
This message follows RMEV0021 and indicates that resource states may not be accurately represented because messages have been lost which may have indicated a change in a resource's state.
System Action:
None.
User Action:
None.
Reason:
This message follows RMEV0022 and indicates that no corrective action could be taken to alleviate an AOM message overflow situation because the queue size limits were already set to their respective maximums.
P1, P2 and P3 show the values of, respectively, the Global Queue Size, the Private Queue Size and the Private Queue Limit.
System Action:
None.
User Action:
None.
Reason:
This message follows message RMEV0023. Due to an AOM message overflow, all resources have been set to an UNKNOWN state. The second part of the message suggests you use the AOMRECOVER command when the message traffic that caused the overflow has abated.
System Action:
Set all resources to UNKNOWN.
User Action:
Wait for message traffic to subside and then issue an AOMRECOVER command.
Reason:
This message follows RMEV0021 and indicates the steps taken to try to alleviate an AOM message overflow situation. This message informs the user that AOM has been stopped and the queue limits set to their respective maximums.
System Action:
Stop AOM and set queue limits to maximum levels.
User Action:
Review queue limits in preparation for the next start of the Automation region.
Reason:
This message follows RMEV0025 and shows which queue values were set. Only those queue limits which were changed are displayed and the display shows what the value was and what it was changed to. These values are contained in P1 and P2 , P3 and P4 , P5 and P6 respectively.
System Action:
None.
User Action:
None.
Reason:
This message follows RMEV0026 and informs the user that when AOM re-starts, after having been stopped to adjust queue limits, a STARTSYS will be issued against the active system image, identified by P1 which should result in a resumption of normal processing.
System Action:
None.
User Action:
None.
Reason:
The Event Handler has detected a Short of Storage condition for the RAMDB on the region identified by P1 . Event Handler has gone into idle mode, to prevent unnecessary processing of events.
System Action:
Event Handler placed into IDLE mode.
User Action:
Attempt to determine if the problem is a short-term or long-term one, as this will help to decide if the region needs to be re-started or not. If the problem is short-term, issuing a STARTSYS command should allow processing to continue.
Reason:
This message outlines the action taken by the region upon detection of a Short of Storage condition. The Event Handler is placed into IDLE mode, and all resource states are set to UNKNOWN.
System Action:
None.
User Action:
Attempt to determine if the problem is a short-term or long-term one, because this will help to decide if the region needs to be restarted or not. If the problem is short-term, issuing a STARTSYS command should allow processing to continue.
Reason:
This message indicates the suggested course of action if the storage problem detected previously is deemed to be of a short-term nature.
System Action:
Informational Only.
User Action:
Issue STARTSYS when more storage is available.
Reason:
If the storage problem is deemed to be a long-term one then the region identified by P1 should be re-started with a larger allocation of storage.
System Action:
Informational Only.
User Action:
Re-start the nominated region with more storage.
Reason:
This message appears along with RMEV0021 indicating an AOM Message Queue Overflow has occurred. The RMEV0032 message is issued if the $RM AOMQUEUES parameter group is not using the default. The default offers the best chance of avoiding these overflow problems by having queues sizes set to maximum and using AOM Cross Memory Services.
System Action:
None.
User Action:
To best avoid the AOM Message Queue overflow problem in future use the default for the $RM AOMQUEUS parameter group. The SD command can be used against the parameter group to set default. Default uses the max queue sizes and AOM Cross Memory Services. It comes into effect at startup.
Reason:
A request to stop an event receiver for the receiver ID identified by P1 has failed because there is no active Event Receiver process for the same receiver ID on this system.
System Action:
The request is ignored.
User Action:
None.
Reason:
An event receiver for the receiver ID identified by P1 has stopped.
System Action:
The event receiver is inactive.
User Action:
None.
Reason:
Shows the status ( P3 ) of the event receiver ID ( P1 ) for event type ( P2 ). The status is one of the following:
ACTIVE - The receiver is active.
INACTIVE - The receiver is inactive.
RETRYING - The define for the receiver failed but is being retried. Messages RMEV2509 and RMEV2510 were written to the activity log when the define was last tried and failed. These messages give the reason for the failure.
INITIALIZING - The receiver is being defined.
System Action:
None.
User Action:
None.
Reason:
The define process for the event receiver whose receiver ID is P1 failed to start and the system entered a retry process. A request to stop the event receiver, and so cancel the retry process, has completed successfully.
System Action:
The event receiver is not defined and events will not be received.
User Action:
If you want to receive events, you must restart the event receiver.
Reason:
The event receiver for the receiver ID ( P1 ) and event type ( P2 ) has started, using NCL process ID P3 .
System Action:
The event receiver processes events of the specified type.
User Action:
None.
Reason:
The event receiver for the EPS receiver ID P1 did not connect to the SOLVE SubSystem Interface (SSI). The reason that the connection was refused follows in message RMEV2508.
System Action:
The event receiver cannot receive events.
User Action:
See the refusal reason in message RMEV2508, which accompanies this message on the log. The most likely causes are:
XMEM=YES
XAPI=YES
XEVNT=YES
For information about how to set up the SOLVE SSI, see the Installation Guide.
Reason:
This message accompanies message RMEV2507 when an EPS connection is refused. The refusal reason ( P1 ) is shown and will be either:
- Another message number - REFUSAL REASON UNAVAILABLE
System Action:
The event receiver will not receive events.
User Action:
Check the refusal reason:
- Refer to the description of the message in the reason. Also refer to the user actions described for message RMEV2507.
- REFUSAL REASON UNAVAILABLE indicates an internal error. (1) Check SupportConnect to ensure that any APARs that relate to EPS are installed. (2) Perform the user actions described for message RMEV2507. (3) If the problem is not resolved, contact Technical Support.
Reason:
An event receiver for the P1 receiver ID has failed. The failure reason is detailed in message RMEV2510, which is written to the activity log with this message.
System Action:
Message RMEV2510 includes the type of EPS operation that failed, which can be one of the following:
Indicates that the event receiver is not defined and events are not received. The system is suspended for a time and then try to define the receiver again.
Indicates that the EPS connection is closed and the process is suspended for 15 seconds during which time events are not received. After this interval, the event receiver tries to connect to the SSI and any further errors are shown as per CONNECT.
Indicates that the event receiver is terminated.
User Action:
Review the messages on the activity log. Message RMEV2510 includes the failure reason and the type of EPS operation that failed.
List this region's configuration details (/IPTEST), and investigate any errors.
Use the feedback reason to determine why the event receiver failed:
Indicate that the SSI (to which this region is connected), does not provide EPS event support. Either:
This usually indicates that you have not connected this region to a correct SSI.
EPS event support is provided by the XEVNT=YES (SSI) parameter.
Indicates that the connection to the SSI has been lost. This may occur if the SSI started task is terminated, or the region is disconnected from the SSI because the SSID parameter has been reset.
Use the SHOW SYSPARM=SSID command to determine the SSID value. Ensure that the correct SSID is specified and that the SSI started task is active. Use the SSI STATUS command to verify the status of the SSI started task.
Use the EPS operation type to determine the options available:
The event receiver, suspended in retry mode, may be canceled by stopping the receiver.
The event receiver may be restarted.
Important! Stopping or restarting the receiver should only be done under guidance from your system administrator or Technical Support.
Reason:
This message follows message RMEV2509 and provides the EPS operation type ( P1 ), failure code ( P2 ) and reason ( P3 ).
System Action:
Refer to message RMEV2509.
User Action:
Refer to message RMEV2509.
Reason:
Procedure ( P1 ), used to process EPS events, has abended.
This message is followed by additional messages that provide:
* error diagnostic information * a dump of the event received
System Action:
The event is ignored. Processing continues with the next event.
User Action:
Contact Technical Support. Provide the complete set of REMV25* messages from the activity log.
Reason:
This message is part of a group of messages which start with RMEV2511. This specific message provides the error description.
System Action:
Refer to message RMEV2511.
User Action:
Refer to message RMEV2511.
Reason:
This message is part of a group of messages which start with RMEV2511. This specific message provides the following error details:
LINE= P1 - the line number in the source code
COND= P2 - the error condition
STMT= P3 - the statement name (verb name)
KEYWORD= P4 - the keyword name (operand name)
NAME= P5 - the name specification
VAR= P6 - the variable name causing the error
System Action:
Refer to message RMEV2511.
User Action:
Refer to message RMEV2511.
Reason:
An End Point Services (EPS) event receiver has received an event that contains invalid data. A description of the field and invalid data is provided
(P1).
System Action:
The system writes this message to the Activity Log, then dumps the invalid event. The system assumes a default value depending on the field that is in error. For example, the current date is assumed when a date field is invalid.
Note: Successive events that have the same error reason ( P1 ) are not logged but do have a default value assumed.
User Action:
This message is provided for diagnostic purposes only. Use the event dump to identify the specific external event data, such as an SMF record.
Note: The event data is prefixed by EPS data - the external event data is the last part of the dump.
The invalid field and data ( P1 ) should be used to identify the specific field that has an error. Use this information, together with the entire external event data, to identify the source of the data and correct the data at the source.
Reason:
This message appears before a dump of received event data starts.
Normally, it follows message RMEV2514 and is followed by the hexadecimal aand character dump of the data.
P1 is the class of the event.
P2 is the receiver name of the event.
System Action:
None.
User Action:
See message RMEV2514.
Reason:
This message follows message RMEV2591 and accompanies each line of the data dump. Each line contains up to 16 bytes of data:
- offset is the hexadecimal data line offset from the start of the data.
- characters is the printable representation of the data line.
- hexadecimal is the hexadecimal representation of the data line.
System Action:
None.
User Action:
None.
Reason:
This message is the last message and follows the dump of received event data.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed to the the Express Setup facility procedure.
System Action:
The request is rejected.
User Action:
Correct the call parameters and retry.
Reason:
An input record in the Control Member for the Express Setup facility was not valid.
System Action:
The record is rejected and processing continues.
User Action:
Either correct the input record and rerun the Express Setup facility or define the resource or resources manually.
Reason:
The Express Setup facility encountered an error when attempting to create a resource definition.
System Action:
Processing continues.
User Action:
Determine the cause of the error from the return code and MSG and take appropriate action. Create the resource manually using the Resource Definition maintenance facility if required.
Reason:
The command processor encountered an error when attempting to issue a system command. The second word in the message is the ID of the message set by the command processor.
System Action:
No resource definitions are generated from the results of the command. Processing continues.
User Action:
Correct the command in the Express Setup input file and rerun Express Setup if necessary. Refer to the message definition for the message set by the command processor for more information.
Reason:
This message indicates that the IP node discovery phase of express setup has reached the maximum number of nodes as set in the control member. The maximum number used was P1.
System Action:
IP node discovery stops and express setup continues.
User Action:
If you would like to increase the maximum number of IP nodes discovered, then update the control member used, specifying a larger value for the argument MAXNODES and rerun the express setup.
Reason:
A database record was created by the Express Setup facility. P1 is the record type and P2 is the name of the record.
System Action:
None.
User Action:
None.
Reason:
The Express Setup facility has completed setting up resource definitions. P1 is one of the following:
COMPLETED SUCCESSFULLY - all control records processed successfully
COMPLETED WITH WARNINGS - all records processed but some warnings were issued. See the Express Setup log.
COMPLETED WITH ERRORS - all records processed but some errors were encountered. See the Express Setup log. FAILED - because of a fatal error, not all records processed. See the Express Setup log.
System Action:
None.
User Action:
If the message indicates that Express Setup has failed or errors occurred, review messages in the Express Setup Task Log, in the log for the specific express setup task, and in the activity log to determine the cause of failure.
Reason:
The IP node discovery phase of Express Setup has reached the maximum duration set in the control member. The duration used was p1 minutes.
System Action:
IP node discovery stops, and Express Setup continues.
User Action:
To extend the duration of the discovery, update the control member used.
Specify a larger value for the MAXDUR argument, and rerun the Express Setup.
Reason:
The Express Setup facility encountered an error when attempting to access the work file. The type of access attempted was P1, the file return code was P3 and the VSAM feedback code was P4 .
System Action:
The Express Setup facililty terminates.
User Action:
Determine the cause of the error from the return and feedback codes, correct and rerun the Express Setup procedure.
Reason:
The Express Setup procedure terminated because no records were found in the control file. P1 is the command library member which was nominated as the control file.
System Action:
The Exress Setup procedure terminates.
User Action:
Specify a valid control information member name and make sure the member is in a PDS which is in the command library of the invoking user, then rerun the Express Setup procedure.
Reason:
A 'C' (command) type control record was encountered in the control file for the Express Setup facility, but the class attribute ($RM00CLASS) was not set before the command record.
System Action:
The control record is rejected and processing continues.
User Action:
Correct the control file so that the $RM00CLASS field is set before each command record and rerun the Express Setup facility.
Reason:
The Express Setup facility rejected a request to add a resource definition to the database because either the class or type field was not assigned a value.
System Action:
The add request is rejected and processing continues.
User Action:
Correct the control records which are used to generate the resource and rerun the Express Setup facility or add the resource definition manually.
Reason:
An internal lock failed. P1 is the lock action that was attempted, P2 is the return code and P3 feedback code.
System Action:
The express set up request fails.
User Action:
Contact your Systems Administrator.
Reason:
An error was encountered when attempting to access file. P1 is the operation being performed, P2 is the ID of the file, P3 is the return code and P4 is the message set by the file verb.
System Action:
Express Setup terminates.
User Action:
Determine the cause of the error from the return code and message, correct the problem and rerun the Express Setup facility.
Reason:
The Express Setup Facility is currently finding all active P1 class resources on the system and creating resource definitions for them in the knowledge base.
System Action:
None.
User Action:
None.
Reason:
The Express Setup Facility is currently creating a resource definition in the knowledge base for a P1 class resource named P2 .
System Action:
None.
User Action:
None.
Reason:
A request to invoke the Express Setup Facility was rejected because the region is not licensed for any of the resource types that express setup creates.
System Action:
The Express Setup request is rejected.
User Action:
None.
Reason:
A request to invoke the Express Setup facility was rejected because the system image to be created has already been defined.
System Action:
The Express Setup request is rejected.
User Action:
Resubmit the request specifying a system name and/or version which does not already exist.
Reason:
Express Setup has completed and is now loading the newly created system image as the active image.
System Action:
None.
User Action:
None.
Reason:
The indicated procedure library was either specified in the Express Setup control file or defaulted as a procedure library to be searched in order to identify started task types.
System Action:
None.
User Action:
None.
Reason:
The indicated Template System image version does not exist in the RAMDB. Express Setup is not able to create resources without a valid Template System Image version.
System Action:
Express setup fails.
User Action:
Update the Customizer parameter member OPSYSIDS with a valid Template System Image version.
Reason:
This message contains an error message returned by a procedure that Express Setup has invoked to perform a service needed for setup.
System Action:
The message is written to the log and processing continues.
User Action:
Check the message P1 and any related messages in the log to determine if any action is required.
Reason:
This informational message shows the duration of node discovery by Express Setup. The duration can be affected by the HOPS and SNMPWAIT arguments in the Express Setup control member.
P1 nodes were discovered during the node discovery. In the next phase, the discovered nodes are compared to the NODETYPES or CIPTYPES filter criteria in the control member. Nodes matching the criteria are added as resources of class IPNODE or CIP.
System Action:
The message is written to the log, and processing continues.
User Action:
None.
Reason:
During Express Setup processing, the TCP/IP sockets interface terminated or never started.
System Action:
Processing is ignored for the current resource and continues to the next available resource. This results in a system image that may not contain all of the resources that are currently in the network.
User Action:
Ensure that the TCP/IP sockets interface is active. Perform the following steps:
1. Review the SOCKETS Parameter group (/PARMS). Verify that all of the details are correct and then press F6 (Action).
2. If actioning the group fails, verify that the associated stack address space is available and is completely initialized. Retry actioning the parameter group.
3. Rerun Express Setup if needed.
Reason:
Express Setup did not get a response from the IP stack P1 for the P2 command. The information contained in the response is needed to create the resource definition.
System Action:
Processing is ignored for this resource and continues to the next available resource. This results in a system image that may not contain all the resources currently in the network.
User Action:
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
The IP discovery is now searching for nodes starting from the interface address P1.
System Action:
None.
User Action:
This is an informational message indicating what IP node discovery is currently doing.
Reason:
The IP discovery process is now starting.
System Action:
None.
User Action:
This is an informational message indicating what IP node discovery is currently doing.
Reason:
IP discovery is now retrieving the routing table for address P1. This table is used to determine the adjacent networks and hosts. P2 is the current hop count represented by this level of discovery and P3 is the hop limit set for this Express Setup discovery.
System Action:
None.
User Action:
This is an informational message indicating what IP node discovery is currently doing.
Reason:
TCP/IP discovery is processing the routing table entry with first hop P1 and address P2 with subnet mask P3.
System Action:
None.
User Action:
This is an informational message indicating what TCP/IP node discovery is currently doing.
Reason:
IP discovery is now searching for the local interfaces for the TCP/IP stack of type P1 called P2.
System Action:
None.
User Action:
This is an informational message indicating what IP node discovery is currently doing.
Reason:
IP discovery is validating a potential P1 type TCP/IP stack called P2.
System Action:
None.
User Action:
This is an informational message indicating what IP node discovery is currently doing.
Reason:
The resource class P1 is not available for use by this region.
System Action:
The resource class is ignored and processing continues to the next entry in the control file.
User Action:
To avoid generating this warning message, remove resource class entries in the control file that are not licensed for this region.
Reason:
A request to load the newly created system image has been bypassed due to failures during Express Setup.
System Action:
Processing continues.
User Action:
Review messages in the Express Setup Task Log, in the log for the specific express setup task, and in the activity log to determine the cause of failure.
Reason:
During Express Setup processing, the TCP/IP sockets interface became available.
System Action:
Processing continues.
User Action:
It may be necessary to rerun Express Setup to ensure that all resources in the network are defined correctly.
Reason:
During Express Setup processing, the NETSTAT interface became available.
System Action:
Processing continues.
User Action:
It may be necessary to rerun Express Setup to ensure that all resources in the network are correctly defined.
Reason:
Express Setup did not receive a response from the NETSTAT interface. The information contained in the response is needed for P1 discovery processing.
System Action:
Processing is ignored for the current resource and continues to the next available resource. This results in a system image that may not contain all the resources that are currently in the network.
User Action:
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
During Express Setup IPNODE discovery, IPv6 subnet P1 was found in a routing table. Express Setup does not process IPv6 subnets because IPv6 subnets can be very large and the amount of time required to check each address would be excessive.
System Action:
Processing continues, skipping subnet P1.
User Action:
If there are addresses in this subnet that you want to monitor, you can add an IPNODE definition manually after Express Setup completes.
Reason:
Address P1 was found during Express Setup IPNODE discovery. Its node type is P2. No resource was build for this address because the node type does not match the list of types specified in the NODETYPES statement in the Express Setup control member.
System Action:
Processing continues.
User Action:
To monitor this address, add an IPNODE definition manually after Express Setup completes, or change the control member and rerun Express Setup.
Reason:
As part of the Express Setup process, some values are added to the list of TCP Port to Protocol Associations in the SmartTrace parameter group. Values were added based on listener ports discovered for known applications.
System Action:
None.
User Action:
None.
Reason:
This is an IP node discovery trace message issued during Express Setup. The message text is variable and indicates the actions that IP node discovery is performing.
System Action:
None.
User Action:
If the trace messages are requested by Technical Support, then ensure that a copy of all the messages are sent to them, including other messages whose message ID begins with RMEXPR.
Reason:
The parameters passed to the procedure to build filter boolean expressions are invalid.
System Action:
Processing is terminated.
User Action:
Correct the parameters in the calling procedure and rerun the exec call.
Reason:
The procedure to build filter boolean expressions found an invalid boolean expression. P1 is the sysmsg returned.
System Action:
Processing is terminated.
User Action:
Correct the incorrect boolean expression in the filter.
Reason:
The parentheses in the filter are unbalanced. P1 identifies the number of left parentheses and P2 identifies the number of right parentheses.
System Action:
Processing is terminated.
User Action:
Correct the unbalanced parentheses in the filter.
Reason:
No boolean value was found on the line P1.
System Action:
Processing is terminated.
User Action:
Correct the boolean value on the line identified.
Reason:
The transaction request from remote conversation partner is not recognized.
System Action:
This transaction is not processed any further.
User Action:
Contact Technical Support.
Reason:
An APPC error was detected attempting APPC verb P1 . The return code is
P2 , the feedback code is P3 , and the associated error message is P4 .
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your system administrator.
Reason:
Processing of the P1 APPC verb failed. The return code is P2 , the feedback code is P3 , and the associated error message is P4 .
System Action:
Processing terminated in error.
User Action:
Determine whether the link to the remote system has failed. If the link has failed, the region will try to recover the link. Otherwise, contact Technical Support.
| Copyright © 2012 CA. All rights reserved. |
|