|
|
|
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. 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:
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.
Reason:
This message displays a trace record of the Hardware Interface Service events handler procedure.
p1 is the trace ID, and p2 is the trace text.
System Action:
None.
User Action:
For assistance, contact CA Support.
Reason:
The Hardware Interface Service event handler procedure is connected to the Hardware Interface Service and is listening for events.
p1 is the version of the service.
p2 is the Hardware Interface Service instance ID.
System Action:
Hardware Interface Service events are processed.
User Action:
None.
Reason:
The Hardware Interface Service event handler procedure $RMHIMSG failed. A backup copy has been restarted; its NCL ID is p1. Some Hardware Interface Service events may have been lost.
System Action:
Processing continues; however, some Hardware Interface Service events may have been lost.
User Action:
Check the activity log to determine the reason for the initial $RMHIMSG procedure failure.
Contact CA Support with the diagnostic data obtained from the activity log.
Reason:
The Hardware Interface Service is not available or is not accepting API connections.
System Action:
Wait for Hardware Interface Service to become available.
User Action:
If the service is not active, start Hardware Interface Service.
If Hardware Interface Service is active, take the following steps:
Reason:
Hardware Interface Service shutdown is in process. The API connection is terminated.
System Action:
Wait for Hardware Interface Service to restart.
User Action:
Start Hardware Interface Service.
Reason:
Connection to Hardware Interface Service has been lost.
System Action:
Wait for Hardware Interface Service to become available.
User Action:
If the service is not active, start Hardware Interface Service.
If Hardware Interface Service is active, take the following steps:
Reason:
Unknown event received from Hardware Interface Service.
p1 gives some details about the received event.
System Action:
The event is ignored.
User Action:
Contact CA Support with the diagnostic data obtained from the activity log.
Reason:
Unknown event name received from Hardware Interface Service.
p1 is the event name.
System Action:
The event is ignored.
User Action:
Contact CA Support with the diagnostic data obtained from the activity log.
Reason:
An error occurred while decoding an entity attribute.
p1 is the attribute flag name.
p2 is the event name.
p3 is the entity name.
p4 is the entity type name.
System Action:
The attribute is ignored.
User Action:
Contact CA Support with the diagnostic data obtained from the activity log.
Reason:
The Hardware Interface Service Event Message Handler procedure $RMHIMSG failed because of an internal system error.
P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
A Hardware Interface Service ENTITY STATUS CHANGE event is received.
p1 (optional) is the event message number (#n to #nn). The number is used only when the event Attributes Data is too large to fit on a single message.
p2 is the entity name.
p3 is the entity type.
p4 is the entity hierarchy level.
p5 is an attribute list relevant to this entity (some entities have no attributes). Each attribute is prefixed by one of the tags in the following table:
|
Tag |
Attribute description |
|---|---|
|
CAC= |
Capacity Change |
|
CAR= |
Capacity Record |
|
CML= |
Command Last |
|
CMR= |
Command RC |
|
CMT= |
Command Type |
|
DW#= |
Disabled Wait Serial # |
|
DWI= |
Disabled Wait Part Id |
|
DWP= |
Disabled Wait Proc # |
|
DWS= |
Disabled Wait PSW |
|
HIF= |
Hardware Interface Name |
|
HWP= |
Permanent Hardware Error |
|
ILn= |
Image List -- (IL1 to IL9 - see note) |
|
MSA= |
Alarm Message |
|
MSD= |
Message Date |
|
MSH= |
Held Message |
|
MSI= |
Message Id |
|
MSN= |
New Message |
|
MSP= |
Priority Message |
|
MSn= |
Message Time Stamp -- (MS1 to MS9 - see note) |
|
MST= |
Message Time |
|
NM1= |
Number 1 for some events |
|
NM2= |
Number 2 for some events |
|
NMN= |
New Name |
|
NMO= |
Old Name |
|
OSN= |
Operating System Name |
|
PMN= |
New Power Mode Value |
|
PMO= |
Old Power Mode Value |
|
PSN= |
New Power Save Mode Allowed |
|
PSO= |
Old Power Save Mode Allowed |
|
STN= |
New Status |
|
STO= |
Old Status |
|
TN#= |
New E Type |
|
TNN= |
New E Type Name |
|
TO#= |
Old E Type |
|
TON= |
Old E Type Name |
|
TOI= |
Initial Topology |
|
TPn= |
Prompt Text -- (TP1 to TP9 - see note) |
|
TXn= |
messagetext -- (TX1 to TX9 - see note) |
Note: Some attributes can be a long character string that does not fit on the current message. In this case, the string is segmented, each segment is prefixed by a numbered tag, for example:
TX1="Start of string ....... .. .. ....." + TX2="end of string ......."
A + indicates continuation.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service ENTITY NAME CHANGEG event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service ENTITY COMMAND RESPONSE event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service NEW CHILD UNDER ENTITY event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service DELETED CHILD OF ENTITY event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service NEW ENTITY CREATED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service ENTITY DELETED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service HARDWARE MESSAGE ISSUED BY ENTITY event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service HARDWARE MESSAGE DELETED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service OPERATING SYSTEM MESSAGE event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service ACTIVE PROFILE CHANGED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service ENTITY EXCEPTION event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service APPLICATION STARTED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service APPLICATION ENDED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service CAPACITY CHANGED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service CAPACITY RECORD CHANGE event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service SECURITY EVENT event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service DISABLED WAIT event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service POWER CHANGE event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service HARDWARE COMMUNICATIONS ERROR event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service ATTRIBUTES ADDED OR UPDATED event is received.
For details, see message RMHIS101.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service system SERVER DOWN event is received.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service system SERVER UP event is received.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service system SERVER HARDWARE INTERFACE UP event is received.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service system SERVER HARDWARE INTERFACE DOWN event is received.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service system INITIAL H/W TOPOLOGY COLLECTION COMPLETE event is received.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service system INITIAL H/W TOPOLOGY COLLECTION HAD ERRORS event is received.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
A Hardware Interface Service system TEST EVENT event is received.
p1 is test event text string.
System Action:
AOMALERT is generated.
User Action:
Process as required.
Reason:
Invalid parameters were passed to Procedure $RMIC01D.
System Action:
The Procedure terminates.
User Action:
Contact your support representative.
Reason:
The panel, P1, you have chosen to be displayed as a graphical monitor is currently being updated by the user identified by P2.
System Action:
Request rejected.
User Action:
Use another panel or wait until the user currently updating the panel is finished with it.
Reason:
The Resource Group you have elected to Zoom to does not contain any resources.
System Action:
The Zoom request is rejected.
User Action:
Check that the Resource Group definition is correct, and that all links between Service/View Regions are up.
Reason:
The panel name P1 is not a valid panel name.
System Action:
Request rejected.
User Action:
Specify a valid panel name.
Reason:
The command identified by P1, issued against the Icon identified by P2 was not a valid Icon command.
System Action:
Request rejected.
User Action:
Enter a valid Icon command
Reason:
The command P1 is not allowed to be issued against resource group P2 because it appears in the list of restricted commands contained in GLOBAL variable $RM$GCBL.
System Action:
Command is rejected.
User Action:
If it is required to be able to issue this command then remove it from the GLOBAL variable $RM$GCBL in the system startup parameters.
Reason:
The requested command(s) were successfully submitted.
System Action:
None.
User Action:
None.
Reason:
There was en error encountered Zooming to a Resource Group panel.
P1 is the resource group being ZOOMed to and P2 is the error message returned.
System Action:
The Zoom is terminated.
User Action:
Check to see if the Zoomed Panel or Resource Group are invalid.
Reason:
The specified Command is Invalid.
System Action:
None.
User Action:
Enter a "?" in the field to get a list of Valid Commands.
Reason:
Resource commands cannot be issued against an icon which contains a resource group which points to another icon panel. You must first Zoom the lower level panel and issue resoure commands at that level, if possible.
System Action:
Command is rejected.
User Action:
Zoom on the icon to reveal the panel below. If the icons on this subsequent panel point directly to resources then commands may be issued against them.
Reason:
An error occurred while displaying the indicated panel. The panel may have changed since it was last displayed. The activity log contains more information about the panel error.
System Action:
The displaying operation is terminated.
User Action:
See the activity log for more information about the panel error.
Reason:
The specified command has been issued.
System Action:
The command will be processed.
User Action:
None
Reason:
An invalid keyword value was passed to the Graphical Resource Monitor service procedure. 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 command specified was invalid.
System Action:
Command field is set in error.
User Action:
Enter a valid command.
Reason:
A request to execute a command against all the resources represented by an Icon was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
Allocation for the vartable named P3 with scope P4 of type P2 was unsuccessful. FDBK P1 was returned.
System Action:
The Icon Manager terminates.
User Action:
Resolve the reason for the vartable allocation failure. This may be that the region is short of storage and it may be necessary to restart the region with more storage.
Reason:
A panel path has been invoked in which the ICON (Resource Group) known as P1 points to the PANEL P2 which has either been referenced earlier in the path or which contains the ICON (Resource Group) identified by P1
System Action:
Entry to the Graphical Monitor is denied as this sort of recursive path leads to excessive CPU usage and degradation of performance.
User Action:
Locate where the recursion occurs in the path and correct the situation and retry.
Reason:
You invoked the Icon Manager Service procedure with invalid parameters identified by P1.
System Action:
The Icon Manager Service procedure terminates.
User Action:
These are internal calls and should not provide invalid parameters. Contact Technical Support.
Reason:
You invoked the Icon Manager Service procedure to resolve the icons in an icon panel, but the name of the panel, identified by P1, is not a valid panel name.
System Action:
The Icon Manager Service procedure terminates.
User Action:
Correct the source of the invalid panel name. It may be stored in a user's profile.
Reason:
You invoked the Icon Manager Service procedure to resolve the icons in the icon panel identified by P1 but the panel cannot be read from the panel library identified by P2.
System Action:
The Icon Manager Service procedure terminates.
User Action:
Ensure that the region has initialized without errors. The most likely cause of this error is that the ICOPANL data set is not allocated.
Reason:
The System Image P1 of version P2 is being loaded as the current system.
System Action:
None.
User Action:
None.
Reason:
The registration table used to support multiple systems was successfully allocated.
System Action:
None.
User Action:
None.
Reason:
The status table was successfully loaded.
System Action:
None.
User Action:
None.
Reason:
The loading of the status table failed. See associated message(s) for the reason.
System Action:
System load terminates.
User Action:
See the associated messages and correct the error indicated by these messages.
Reason:
The processes that manage APPC communication sessions with this system are being started and initialized.
System Action:
None.
User Action:
None.
Reason:
The various SSO long running processes which manage message traffic and event flows are being started and initialized.
System Action:
None.
User Action:
None.
Reason:
The long running background process P1 failed to initialize.
System Action:
Load of the system fails.
User Action:
See the associated messages for the reason that the process failed.
Reason:
The long running background process P1 successfully initialized.
System Action:
None.
User Action:
None.
Reason:
The action of starting and initializing all the required long running background process failed.
System Action:
System load fails.
User Action:
See the associated messages.
Reason:
The Availibility Statistics Monitor is being started in the background.
System Action:
None.
User Action:
None.
Reason:
The process responsible for Starting all the resources of the current System Image is being started.
System Action:
None.
User Action:
None.
Reason:
Initialization of Console Consolidation processing failed.
System Action:
System load fails.
User Action:
See the associated messages for the reason.
Reason:
The Console Consolidation ISR link manager process is being started.
System Action:
None.
User Action:
None.
Reason:
An invalid command was entered.
System Action:
The command is rejected.
User Action:
Specify a valid command.
Reason:
The system image load has completed.
System Action:
None.
User Action:
None.
Reason:
An request to load a new system image was rejected because there is already a system load in progress. The currently running load was started at P1.
System Action:
Request rejected.
User Action:
None.
Reason:
The system load process detected that the monitor process was already running. This is normal, the process will not be restarted.
System Action:
None.
User Action:
None.
Reason:
The system load process had previously been unsuccessful with the initialization of some components which are not critical but which resulted in a load status of WARNING. This message indicates that a user has initiated a Retry request in order to initialize these components.
System Action:
None.
User Action:
None.
Reason:
A request to retry the initialization of non-critical components was issued.
System Action:
None.
User Action:
Wait for subsequent messages, which indicate the results of the request.
Reason:
An attempt to initialize non-critical components failed.
System Action:
Initialization remains in the warning state.
User Action:
Determine the reason for the errors and retry the request.
Reason:
An attempt to initialize non-critical components completed successfully and the components are now initialized.
System Action:
None.
User Action:
None.
Reason:
The load of System Image P1 with Version P2 has completed.
System Action:
None.
User Action:
None.
Reason:
The long running background process P1 failed to initialize. The reason is P2. If the reason is ended then the process prematurally ended before notifying the loader.
System Action:
Load of the system fails.
User Action:
See the associated messages (also in the activity log) for the reason that the process failed.
Reason:
A system image load was requested but the supplied system image name was not found in the database.
System Action:
A dummy system image is loaded.
User Action:
Load a valid system image.
Reason:
A system image load was requested but the supplied system image name is the active system image on a linked region.
System Action:
A dummy system image is loaded.
User Action:
Load a different system image on this region or the linked region, or unlink the regions and retry.
Reason:
The indicated Template System Image Version does not exist in the RAMDB. System load cannot proceed without a valid Template System Image Version.
System Action:
System load fails.
User Action:
Update ICS parameter member OPSYSIDS with a valid Template System Image Version.
Reason:
The monitors defined to the Data Sampling Framework are being started in the background.
System Action:
None.
User Action:
None.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
There were no records in the log.
System Action:
None
User Action:
None
Reason:
There were more tha 9999 log records.
System Action:
The first 9999 log records will be displayed.
User Action:
None
Reason:
The feature or features P1 are either excluded or not licensed for this CPU.
System Action:
Function is terminated.
User Action:
Contact your Systems Administrator.
Reason:
The field P1 is required and must not be null.
System Action:
Field is set in error.
User Action:
Specify a value for P1.
Reason:
The field P1 is required when the value of field P2 is P3 .
System Action:
Field is set in error.
User Action:
Specify a value for P1 .
Reason:
The field P1 is required if the field P2 is specified.
System Action:
Field is set in error.
User Action:
Specify a value for P1 or blank out the value for P2 .
Reason:
An invalid job entry subsystem was specified. The only valid job entry subsystems are:
- For MVS: JES2 or JES3 - For MSP: JES - For VOS3: JSS3 or JSS4
System Action:
Field is set in error.
User Action:
Specify a valid value.
Reason:
The specified character, P1 , is invalid. Specify one of the characters in P2 .
System Action:
The field in error is highlighted.
User Action:
Specify a valid character.
Reason:
The field P1 must have a different value to the field P2 .
System Action:
Field is set in error.
User Action:
Specify different values for P1 and P2 .
Reason:
The P1 type specified was invalid. The only valid values are GLOBAL or LOCAL. P1 will be either JES3 or JSS4.
System Action:
Field is set in error.
User Action:
Specify either GLOBAL or LOCAL.
Reason:
The field must have the value NO if the field P1 is NO.
System Action:
Field is set in error.
User Action:
Specify NO for the field or specify YES for P1 .
Reason:
This region is configured with the NetMaster Automation product that requires the $RSPPOPR PPO procedure.
System Action:
The parameter group fails.
User Action:
Either specify the correct PPO procedure name, or clear the field for it to default to the required value.
Reason:
The field contains an invalid value. The only valid values are ACTIVE or INACTIVE.
System Action:
Field is set in error.
User Action:
Specify either ACTIVE or INACTIVE.
Reason:
The field contains an invalid value. The field must be in the format n-m, where n and m are both numeric and in the range 1 to 128. Also n must be less than or equal to m. For example 17-128.
System Action:
Field is set in error.
User Action:
Specify a valid range.
Reason:
The field contains an invalid value. The field must be in the format n,n,n:m where n and m are numeric and in the range 1 to 128. For example 1,2,8:12,29,36:123
System Action:
Field is set in error.
User Action:
Specify a valid series of route codes.
Reason:
The field contains an invalid value. The only valid values are SMFID or NMDID.
System Action:
Field is set in error.
User Action:
Specify either SMFID or NMDID.
Reason:
The AOMPROC was started and did not return an indication that it had successfully initialized within the time allowed.
System Action:
The parameter group fails.
User Action:
Determine the reason the AOMPROC failed or did not issue a notification.
Reason:
The parameter P1 could not be changed because AOM is currently in a status which does not allow the altering of this parameter. The current status of AOM is P2 . AOM must be inactive to action this parameter. P1 gives the name of the parameter and in parentheses the current value.
System Action:
Parameter is not set.
User Action:
Save the parameters value and it will become effective at next startup or stop AOM, set the parameter and then restart AOM.
Warning: Stopping AOM will affect the functioning of the system. No messages will be received, no automation will be taken and the resource status changes will be lost. You will need to reload the system image.
Reason:
The field contains an invalid value. The only valid values are AUTOMATED or MANUAL.
System Action:
Field is set in error.
User Action:
Specify either AUTOMATED or MANUAL.
Reason:
The field contains an invalid value. The only valid values are 0 or a number between 128 and 255.
System Action:
Field is set in error.
User Action:
Specify either 0 or a number between 128 and 255.
Reason:
The field contains an invalid value. The field must be greater than or equal to 10 minutes (00.10) and less than 24 hours (ie less than or equal to 23.59).
System Action:
Field is set in error.
User Action:
Specify a time interval between 00.10 and 23.59.
Reason:
The AOM global number variable P1 was set to the value P2.
System Action:
None.
User Action:
None.
Reason:
This is an informational message which describes an NDB error code.
System Action:
None.
User Action:
See related messages.
Reason:
The NDB specified was invalid because the NDB was not defined for the current version.
System Action:
The RAMDB is not allocated.
User Action:
Specify a valid RAMDB.
Reason:
The value for field P1 must be greater than the value specified for field P2.
System Action:
Field is set in error.
User Action:
Specify a higher value for P1 or a lower value for P2.
Reason:
The value for field P1 must be a valid IP address in numeric form. AAA.BBB.CCC.DDD where AAA,BBB,CCC,DDD are numbers less than 256.
System Action:
Field is set in error.
User Action:
Specify a proper numeric format IP address for P1.
Reason:
The value for field P1 was specified as NO, and thus no further WSPEER parameters were processed.
System Action:
None.
User Action:
If you wish to use a Workstation peer system, then change the setting of the field to YES, and specify all of the other parameters correctly. Otherwise this message can be ignored.
Reason:
The selected System Image cannot be loaded on this region because it is active on a linked region.
System Action:
Field is set in error.
User Action:
Select another System Image.
Reason:
The value for the IP address in the WSPEER customization parms was found to be null.
System Action:
WSPEER parameter processing is terminated.
User Action:
Specify a proper numeric format IP address in the WSPEER customization parameters. If WSPEER processing is not required, set the 'Workstation peer in use' field to NO.
Reason:
The Template System Image Version specified is not valid for the JES identified by P2.
System Action:
The field is highlighted and a message is displayed to the user.
User Action:
Correct the Template System Image Version entered in the field.
Reason:
The field contains an invalid value. The only valid values are YES or NO.
System Action:
Field is set in error.
User Action:
Specify either YES or NO.
Reason:
The PPOPROC was started and did not return an indication that it had successfully initialized within the time allowed.
System Action:
The parameter group fails.
User Action:
Determine the reason the PPOPROC failed. Use the $LOG command to access the activity log. Look for any messages that indicate that the procedure has ended, either normally or as a result of an abend.
Reason:
There is insufficient storage to load all the console consolidation message profiles.
System Action:
Console consolidation profiles are unloaded and the screening table activation is reattempted.
User Action:
Reduce the amount of storage needed by the console consolidation profiles by: - inactivating unused profiles
- reducing the size (complexity) of the profiles Reactivate the profiles from the customization parameter for console consolidation (CCONSOLIDATN).
Reason:
Background user IDs must be defined to execute the procedure that operates the product. If they are not defined, the product may not operate correctly.
System Action:
Processing continues.
User Action:
From a session with UAMS authority, run procedure $NMUAINI with no arguments to generate the background user IDs. Then go to /BCAST.L and delete this broadcast message or it will be retained until the region is stopped.
Reason:
See message RMINWI37.
System Action:
See message RMINWI37.
User Action:
See message RMINWI37.
Reason:
See message RMINWI37.
System Action:
See message RMINWI37.
User Action:
See message RMINWI37.
Reason:
See message RMINWI37.
System Action:
See message RMINWI37.
User Action:
See message RMINWI37.
Reason:
To activate the use of the Workstation Peer, the Workstation Peer User ID must be defined in this system. P1 is the Workstation Peer User ID and it does not exist. The system wanted to create it automatically for you but you are not authorized for UAMS maintenance access and hence the request was not attempted.
System Action:
Validation for this parameter group fails.
User Action:
Either obtain the required authority to perform user maintenance or ask a suitably authorized user to update this parameter group. You can also ask a suitably authorized user to run the following procedure to automatically define the required user ID. Run this procedure from OCS:
$RMUAINI ACTION=DEFINE NAME=WSPU
Reason:
There is insufficient storage to load all the event simulation code.
System Action:
Event simulation is disabled, and the screening table activation is retried.
User Action:
If event simulation is not required, disable it permanently through the MSGAWARENESS parameter group. In future, no attempt to enable its code will be made. This improves the performance of system initialization.
If event simulation is required, reduce the amount of storage used by console consolidation and/or NetMaster Automation. This can be done in the following ways:
Note: If console consolidation profiles are modified, reactivate the profiles by selecting option A - Activate Message Profiles from the System Console Consolidation menu. Then action the MSGAWARENESS parameter group to enable event simulation.
Reason:
The P1 component of Message Awareness was set to P2.
Message Awareness consists of the following components:
This facility lets you simulate message traffic through your environment and report any EventView rules or ResourceView definitions affected.
This facility notifies you about possible critical system messages that your EventView and ResourceView environment is not set up to deal with. The messages and the alerting method are controlled through the MSGAWARENESS parameter group.
System Action:
None.
User Action:
None.
Reason:
The global variable P1 was set to the value P2 .
System Action:
None.
User Action:
None.
Reason:
The screening table has exceeded its storage limit while loading code dynamically generated by the Unmatched Message Alerting facility, and that facility has been disabled.
System Action:
Unmatched Message Alerting is disabled, and the screening table activation is retried.
User Action:
If Unmatched Message Alerting is not required, disable it permanently through the MSGAWARENESS parameter group. In future, no attempt to enable its code will be made. This improves the performance of system initialization.
Reason:
The AOM global flag variable P1 was set to the value P2.
System Action:
None.
User Action:
None.
Reason:
The AOM SSI Command String Prefix contains an invalid character. The supported characters are:
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 @ $ # ' , . / ( ) * & + - › < | ! ; % _ > ? : "
System Action:
Field is set in error.
User Action:
Correct the AOM SSI Command String Prefix or leave the input field blank if no Command String Prefix is required.
Reason:
The dataset specified does not have the correct dataset organization.
P1 is dataset organization of the dataset. Valid values are PO or PS.
System Action:
Field is set in error.
User Action:
Specify a partitioned (PO) dataset with a member name or a physical sequential (PS) dataset.
Reason:
The dataset specified was a partitioned dataset however a member name was not specified. A member name must be specified if the dataset is partitioned.
System Action:
Field is set in error.
User Action:
Specify a partitioned (PO) dataset with a member name or a physical sequential (PS) dataset.
Reason:
An error was encountered when attempting to access a 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:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The link record indicated by P1 has been successfully processed. P2 indicates if the record was CREATED, REPLACED or SKIPPED. The record is SKIPPED if there is an existing multisystem link record with the key P1 that has been customized.
System Action:
None.
User Action:
None.
Reason:
Ruleset name given must be a valid defined rulest under File Transfer Ruleset definition.
System Action:
Validation for this parameter fails.
User Action:
Enter a valid defined Ruleset name.
Reason:
The set of communication access methods you have selected is not valid at this time. The set has no access method in common with linked region P1 and would render P1 uncontactable.
System Action:
Fields required to access P1 are highlighted.
User Action:
Set one of the highlighted fields to YES. Alternatively, unlink region P1.
Reason:
You must enable at least one of the communication access methods.
System Action:
The fields that cause the error are highlighted.
User Action:
Specify YES to at least one access method.
Reason:
The TCP/IP? field cannot be set to YES because the interface to TCP/IP has not been enabled on this system.
System Action:
The TCP/IP? field is highlighted.
User Action:
If you want to use TCP/IP, update the SOCKETS parameter group and set the TCP/IP Software Type field to a value other than NONE.
Reason:
You cannot specify YES in the EPS? field because the interface to the SSI has not been defined.
System Action:
The field in error, EPS?, is highlighted.
User Action:
If you want to use EPS, specify an SSI in the SSI parameter group to provide the EPS service.
Reason:
You cannot specify YES in the EPS? field because this is not an MVS system. EPS is available on MVS only.
System Action:
The field in error, EPS?, is highlighted.
User Action:
Specify NO in the EPS? field.
Reason:
The value in the P1 field cannot be greater than the value in the P2 field.
System Action:
The field in error is highlighted.
User Action:
Specify a lower value in the P1 field or a higher value in the P2 field.
Reason:
This region requires the console support level of Management Services 3.7 (plus APARs).
System Action:
Initialization cannot complete.
User Action:
Contact Technical Support.
Reason:
The highlighted field contains an invalid value. The only valid value is PRIMARY or ALTERNATE, indicating which set of resource relationships will be used when the SHUTSYS or SHUTFORCE command is used to shut down a system image.
System Action:
The field in error is highlighted.
User Action:
Specify either PRIMARY or ALTERNATE.
Reason:
During region startup, no records were found in the knowledge base (RAMDB) that match the primary (ACB) name of this region. However, other records exist matching other primary names. This is an abnormal situation, usually indicating that the PRI JCL parameter of the region has changed. The change means that remote regions become inaccessible. As a consequence, the region is unlinked automatically from other regions.
System Action:
The region is unlinked, and the message is broadcasted to all users.
User Action:
If new multisystem links are required, the administrator will need to relink the region by using the Link Region and Synchronize Database option on the Multi-System Support Menu (=/MADMIN.SD).
Reason:
The value specified for the NSM Agent Instance name contains special characters such as '@#$-'. Only alphabetic or numeric characters are valid in the instance name and should start with an alphabetic character.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
The P1 system image was not loaded because of reason P2 .
System Action:
The P1 image is not loaded. A default image, $&ZNMDID Version NONE, is loaded instead. &ZNMDID contains the domain identifier of the region.
User Action:
Enter the /PARMS shortcut to display the list of parameter groups, and enter U beside the AUTOIDS group. Specify a system image that is appropriate for the region. If no appropriate images exist, define one and specify it in the AUTOIDS group.
Reason:
The VTAM Application ID specified in the Terminal Prefix field does not exist.
System Action:
Field is set in error.
User Action:
Specify a valid VTAM Application ID that is currently defined to VTAM. The ID can be for a pool of Application IDs with the same prefix and numeric suffixes starting from 001 and up to 999. Alternatively the Application ID can be a generic prefix.
Reason:
The NetMaster for TCP/IP agent does not support filtering.
System Action:
Field is set in error.
User Action:
Specify NONE as the filter value.
Reason:
An absolute directory path is required.
System Action:
Field in error is highlighted.
User Action:
Provide an absolute path directory.
Reason:
The P1 file is empty.
System Action:
Field is set in error and the agent is not started.
User Action:
Specify a valid P1 dataset.
Reason:
The contents of P2 is displayed after this message.
System Action:
None.
User Action:
None.
Reason:
An attempt to OPEN the P1 file failed and the system could not read its contents.
System Action:
Initialization continues.
User Action:
None.
Reason:
The value provided is not in the valid range of 5-60.
System Action:
Field is set in error.
User Action:
Specify a number within the valid range.
Reason:
The CA-7 User ID field contains an invalid value.
System Action:
Field is set in error.
User Action:
Specify other values.
Reason:
The CA-7 User Password field contains an invalid value.
System Action:
Field is set in error.
User Action:
Specify other values.
Reason:
The CA-7 SSID field contains an invalid value.
System Action:
Field is set in error.
User Action:
Specify other values.
Reason:
The option is set to NO because the security exit is not installed.
System Action:
Message displayed. Processing continues.
User Action:
Install the security exit, if required.
Reason:
The automatic password option of the SCHEDAPI parameter group requires the CA-7 user to be defined to UAMS. If the option is set to YES, the system attempts to automatically add the user to the UAMS file. If the attempt is unsuccessful, this message is displayed. P1 is the message returned by the SECCALL ADD function.
System Action:
Message displayed. Processing continues.
User Action:
Determine why the ADD failed. The user may already be defined. Correct the problem and add the user manually.
Reason:
The value provided is not a valid host with port specification. A valid IP address or host name, optionally followed by a port number (:nnnnn), is required.
If a host name is specified, special characters, including @ and #, are not permitted.
If an IPv6 address is specified with a port number, the address must be enclosed in square brackets.
Examples:
192.10.23.24
my.host.com
los-angeles.ARN24
192.10.23.128:1080
[fd00:7a06:a20:100::1]:1080
my.host.com:31076
System Action:
The field is highlighted in error.
User Action:
Specify an alphanumeric IP host name or address.
Reason:
The specified AOM Message Suppression Character is invalid. The supported characters are:
@ # , . / & + - › < | ! ; % _ > ? : ^
System Action:
Field is set in error.
User Action:
Specify a valid character.
Reason:
The system parameter (SYSPARM) with name P1 is already set to the value P2.
System Action:
None.
User Action:
None.
Reason:
The default size must have a value less than or equal to the value specified for the maximum size.
System Action:
None.
User Action:
Correct the field value, and retry.
Reason:
An Alert Severity field must contain 1, 2, 3, 4, or be blank.
System Action:
None.
User Action:
Correct the value, and retry.
Reason:
An IPv6 address has been entered in the Web Address Override field, but the sockets API supports IPv4 addresses only.
System Action:
The field is highlighted in error.
User Action:
Specify a host name or IPv4 address in the Web Address Override field. Alternatively, check the SOCKETS parameter group (/PARMS). For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
The valid Hardware Interface Service API security environments are REGION, SERVER, or USER.
System Action:
The field is set in error.
User Action:
Specify a correct value.
Reason:
CA NetMaster NM for TCP/IP r11.6 SP1 deprecated some monitoring attributes and replaced them with new ones. When the region starts, the RAMDB is scanned and if the deprecated attributes are found, defined EE resources are checked and if they are using the deprecated attributes, they are replaced with the new attributes. When all defined EE resources are updated, the deprecated attributes are deleted.
The deprecated attributes are:
LowPriorityData
HighPriorityData
MediumPriorityData
NetworkPriorityDat
SignalTraffic
The replacement attributes are:
EEBytesPriLow
EEBytesPriHigh
EEBytesPriMedium
EEBytesPriNetwork
EEBytesPriSignal
This message is issued at the start and end of this processing, as identified by P1 . Messages issued in between detail any action taken.
System Action:
Deprecated attributes in resource monitoring defintions are replaced and the deprecated attributes deleted.
User Action:
None.
Reason:
The Telnet, FTP or Connection 'Workload' option was selected but no host samples exist for this option.
System Action:
None.
User Action:
None.
Reason:
The selected STACK resource is not registered internally.
System Action:
The command is rejected.
User Action:
This message may occur transiently following a system image load or when remote stack resources are accessed. Try the command again later.
If the situation persists, there may be a mismatch in the information provided about the stack. Check the stack name, type and SSID (if applicable) are correct in the following places:
- The stack resource definition (A.R.R)
- SOCKETS parameter group (/PARMS)
Reason:
A display query for P1 has no matching data in Workload Manager (WLM).
System Action:
None.
User Action:
None.
Reason:
The definition of the selected resource does not include the associated TCP/IP stack job name.
System Action:
The request is rejected.
User Action:
Update the resource definition to include the associated stack job name.
Reason:
The Telnet option was selected but no samples exist for this option.
System Action:
None.
User Action:
None.
Reason:
The command P1 is not valid against the selected resource. The command requires P2 (OSA/SF or SNMP) and the OSA resource definition specifies that P2 is not used.
System Action:
The command is rejected.
User Action:
None.
Reason:
The command request identified by P1 has been canceled.
System Action:
None
User Action:
None
Reason:
The command request identified by P1 has been canceled because CA NetSpy is not configured.
System Action:
None.
User Action:
None.
Reason:
You tried to file or save a definition that has not been changed. The requested action is not performed.
System Action:
The definition is not saved again.
User Action:
None.
Reason:
The associated STACK jobname P1 for the selected resource is not registered internally.
System Action:
The command is rejected.
User Action:
This message may occur transiently following a system image load or when remote stack resources are accessed. Try the command again later.
If the situation persists, there may be a mismatch in the information provided about the associated stack jobname. Check the stack jobname, type and SSID (if applicable) are correct in the following places:
- The Associated STACK Jobname field definition for the selected resource (A.R.R)
- The stack's own resource definition (A.R.R)
- SOCKETS parameter group (/PARMS)
Reason:
Another user is updating this definition.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The IP Resource Monitor IU command (List IP UDP Connections) is no longer supported. You can list UDP end points using the Connection List function.
System Action:
None.
User Action:
To display current UDP end points and their total traffic counts, use a Connection List /CONNC (not /CONNCF) with the criteria Connection Status EQ UDP.
Reason:
The entered command is not valid against the selected resource. The stack associated with this resource is type TCPaccess. The command is not supported for TCPaccess stacks.
System Action:
The command is rejected.
User Action:
None.
Reason:
The link name identified by p1 is not currently active.
System Action:
The request is rejected.
User Action:
Investigate the cause of the link failure, and retry the operation.
Reason:
The requested command is not supported by the remote region, p1. The link is in Migration Mode. This type of linkage is used during the migration of the remote region to a new release level.
System Action:
Processing of the command terminates.
User Action:
This command will be available in the remote region when you have upgraded the remote region to the same release level as this region.
Reason:
Initialization has successfully completed. The process will now attempt to connect to the remote host. P1 is the protocol used in the connection.
System Action:
None.
User Action:
None.
Reason:
The connection manager has terminated for protocol P1.
System Action:
None.
User Action:
See previous messages.
Reason:
A keyword parameter was either not specified or was specified with an invalid value. The keyword parameter was P1 and the value was P2.
System Action:
The request is rejected and processing terminates.
User Action:
Specify the keyword parameter with a valid value.
Reason:
A request to act as the P1 process for P2 failed because another process was already performing the function. If KILLPREV=YES was specified then this process could not be flushed.
System Action:
The request is rejected and processing terminates.
User Action:
Try the action later or specify KILLPREV=YES to terminate the current process acting as the P1 for P2.
Reason:
The link manager could not continue processing because the service package P1 did not exist or the necessary procedure P2 did not exist in the package.
System Action:
Processing terminates.
User Action:
Ensure all required procedures are supported by the package or that the package name is correct.
Reason:
An error occurred executing a TCP/IP socket function. P1 is the function being performed, P2 is socket ID, P3 is the return code from the function, P4 is the feedback code from the function, P5 is the protocol being used, P6 is the port number at the remote host and P7 is the remote host name or address (if applicable).
System Action:
The request fails and the connection will be retried.
User Action:
Ensure that the Host Name/Address and Port Number are correct. Check the error codes to determine the exact nature of the error. More information may follow in subsequent messages.
Reason:
This message described additional information associated with a previous error. P1 is the vendor software specific error code and P2 is a description of the socket error number received. The vendor specific code may not be present.
System Action:
None.
User Action:
See related messages. Check the error codes and description to determine the exact nature of the error.
Reason:
A request to terminate the P1 protocol client/server process P2 was accepted. The process will terminate.
System Action:
Processing terminates as requested.
User Action:
None.
Reason:
A connection was successfully established with a remote system. The protocol being used is P1, the socket identifier is P2 and the port is
P3. The remote system is on address P4 with port P5.
System Action:
None.
User Action:
None.
Reason:
A connection failed and has been automatically scheduled to be retried in P2 minutes. The connection is for protocol P1.
System Action:
None.
User Action:
None.
Reason:
A request to act as the Client process failed because the remote host name/address P1 did not respond.
System Action:
Processing terminates.
User Action:
Ensure that the correct host name/address is specified and retry the request again.
Reason:
Initialization has completed successfully. The process is now attempting to register on a port. P1 is the protocol used in the connection, and P2 is the port number being registered for.
System Action:
None.
User Action:
None.
Reason:
Registration was successful for protocol P1 . The port that was registered is P2, and the socket identifier is P3 .
System Action:
None.
User Action:
None.
Reason:
The remote client for a specific connection has terminated the connection to P1.
System Action:
Processing terminates as requested.
User Action:
None.
Reason:
Initialization has completed successfully for a specific server. The protocol is P1 and the port which the client connected to is P2 . The socket being transferred is P3 .
System Action:
None.
User Action:
None.
Reason:
System image load processing has started and will be requesting confirmation of the system image name and version, the automation mode, and whether a cold or a warm load is to be performed. The system ID is
P1 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue the load process.
Reason:
The region is initializing and will be requesting confirmation of the system image and version to use. The system ID is P1 , and the currently nominated system image name is P2 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is initializing, and will be requesting confirmation of the system image and version to use. The system ID is P1 , and the currently nominated system image version is P2 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is initializing, and will be requesting confirmation of the system image and version to use. The system ID is P1 , and the currently nominated automation mode is P2 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is initializing, and is requesting confirmation of the system image name and version, automation mode, and cold load setting to use for the region. The system ID is P1 , and the currently nominated system image name is P2 , the version is P3 , the automation mode is
P4 , and cold load is P5 .
System Action:
The system waits for a reply.
User Action:
Reply to the message, or allow it to time out to continue initialization.
Reason:
The region is starting system image load or network discovery, and is requesting override or confirmation of the parameters listed in the previous messages (RMIWTOnn). The messages display the current setting of parameter values. See AUTOIDS or AUTOSNACNTL for further details of the parameters in the group. P1 is the system ID of the region.
System Action:
The system will wait for a reply, or will use the values shown when the timeout value expires. The timeout value is determined by the Confirm via WTOR at Startup? field in the parameter group. The default is 120 seconds.
User Action:
Check that the parameter values are correct.
If they are correct, reply as follows: R n,U
If a value is not correct, reply with the parameter name and its correct value in the format, PARM=VALUE. The following example changes the system image to be loaded:
R n,SYSTEM=SOLVPROD,VERSION=0002,MODE=AUTOMATED
Reason:
The region is initializing, and will be requesting confirmation of the system image and version to use. The system ID is P1 , and P2 indicates if there will be a cold start of checkpointing.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is starting its network discovery processing, and will be requesting confirmation of the discovery rate (number of commands per time frame) and whether a cold start is required. The system ID is P1 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and will be prompting for confirmation of the discovery parameters. P1 is the system ID, and P2 indicates whether a cold start will be done. P2 can be changed in response to a subsequent WTOR message by replying COLD=YES or COLD=NO.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and will be prompting for confirmation of the discovery parameters. P1 is the system ID, and P2 indicates the maximum number of commands that can be issued within the time frame displayed in a subsequent message. P2 can be changed in response to a subsequent WTOR message by replying CMDS=n, where n is the new number of commands per time frame.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and will be prompting for confirmation of the discovery parameters. P1 is the system ID, and P2 indicates the time frame within which the specified maximum number of commands can be issued (see previous message). P2 can be changed in response to a subsequent WTOR message by replying TIME=n, where n is the new value for the time frame in seconds.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and is requesting confirmation of the Cold Start, Commands per Time Frame, and Time Frame in Seconds discovery control parameters. The system ID is P1 and the current value for Cold Start is P2 , Commands per Time Frame is P3 , and Time Frame in Seconds is P4 .
System Action:
None.
User Action:
Check that the Cold Start, Commands per Time Frame, and Time Frame in Seconds are correct, and if so, reply "U".
Reason:
A reply received to confirm System Image Load or Network Discovery specified an invalid value for the keyword parameter P2. This parameter must be P3. The system's ID is P1.
System Action:
None.
User Action:
Reply to the subsequent WTOR the correct value for the keyword P1.
Reason:
A reply to change the System Image name and/or Version was rejected because the specified system and version combination could not be found in the database. P1 is the system's ID, P2 is the system image name and version, P3 is the database return code and P4 is the message returned from the database manager.
System Action:
None.
User Action:
Reply to the subsequent WTOR with a valid system name and version that exist.
Reason:
No reply to change the parameter for the P2 process was received within 2 minutes. The current values will be accepted as confirmed. The system's ID is P1.
System Action:
None.
User Action:
None.
Reason:
Confirmation of the parameter for the P2 process was acknowledged. The system's ID is P1.
System Action:
None.
User Action:
None.
Reason:
Indicates the reply that was received to the last request for parameter confirmation. P1 is the system's ID and P2 is the reply received.
System Action:
None.
User Action:
None.
Reason:
The reply received for confirmation of parameters was invalid. It was not in valid keyword format. P1 is the system's ID and P2 is the error message received.
System Action:
None.
User Action:
None.
Reason:
The parameters for the P2 process were reset to their initial values. The system's ID is P1.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
An non-numeric value was entered into the field identified by P1 .
System Action:
The field is highlighted and an error message is displayed to the user.
User Action:
Correct the value entered and retry.
Reason:
The command P1 is invalid.
System Action:
Command field is set in error.
User Action:
Enter a valid command.
Reason:
The number of Defined Initiators has been changed to P1 .
System Action:
None
User Action:
The message is informational only.
Reason:
The Group identified by P1 is does not exist on the system specified.
System Action:
The modify command fails.
User Action:
Check the Group is named correctly and that it is defined to JES3.
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 scheduler jobs found.
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:
The dataset which contains the required JCL member could not be allocated. P1 contains the error message received.
System Action:
The procedure terminates in error.
User Action:
Contact your system administrator.
Reason:
The JCL for this job has been successfully submitted to JES.
System Action:
None.
User Action:
None.
Reason:
The JCL for this job has not be submitted successfully to JES.
System Action:
Job is placed in automation failed state.
User Action:
Investigate.
Reason:
The List of the JCL member has failed.
System Action:
Procedure terminates in error.
User Action:
Contact your system administrator.
Reason:
JES2 termination has been requested however the resource P2 of type
P1 is still active.
System Action:
The system waits for a reply to the WTOR.
User Action:
Reply P if the active resource is to be terminated with a JES2 PURGE command. Replay C if the active resource is to be terminated with a CANCEL or N for IGNORE if the resource has been terminated already using operator intervention.
Reason:
The JES type has been determined.
System Action:
None
User Action:
None
Reason:
The JES type has not been determined. JES Default assumed.
System Action:
None
User Action:
None
Reason:
The JES type has not been determined. JES Default assumed.
System Action:
None
User Action:
None
Reason:
The JES3 type has been determined.
System Action:
None
User Action:
None
Reason:
Default of JES3 LOCAL assumed.
System Action:
None
User Action:
None
Reason:
Default of JES3 LOCAL assumed.
System Action:
None
User Action:
None
Reason:
Unexpected response received.
System Action:
None
User Action:
Contact your System Administrator.
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:
The keyword P1 was deleted.
System Action:
None.
User Action:
None.
Reason:
The keyword P1 cannot be updated because it is already being updated by user P2.
System Action:
Request is 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:
The selected record is already being updated by user P1.
System Action:
Request rejected.
User Action:
Try later.
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:
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:
All system keywords are reserved and cannot have actions applied against them.
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:
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 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 activity log will be swapped.
System Action:
The next available activity log will be emptied and will then become the active log.
User Action:
None.
Reason:
A log browse request has been received, but no log can be found for the requested starting date and time.
System Action:
Request is rejected.
User Action:
None.
Reason:
The user cancelled the log swap request.
System Action:
The log is not swapped.
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:
No log file are available.
System Action:
Logproc will terminate.
User Action:
Contact your system administrator.
Reason:
No log file are available.
System Action:
Logproc will terminate.
User Action:
Contact your system administrator.
Reason:
The executing NCL process with the specified NCLID has been flushed to enable a Log Swap to take place.
System Action:
None.
User Action:
None.
Reason:
The specified User was has been cancelled to enable a Log Swap to take place.
System Action:
None.
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 a full license is required, contact Technical Support.
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:
$RMLINK 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:
$RMLINK has not be supplied with all required details. The list provides the keywords that are needed.
System Action:
Request is rejected.
User Action:
Correct command and retry.
Reason:
The link request made is not valid.
System Action:
Request is rejected.
User Action:
None.
Reason:
The link request has completed successfully.
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:
The link manager is attempting to start the component specified in P1 for connected region P2 .
System Action:
None.
User Action:
None.
Reason:
An attempt was made to dynamically define a component, but it has failed. P1 contains the name of the failed component, while P2 and P3 contain the return code and failure message respectively.
System Action:
Processing continues.
User Action:
None.
Reason:
The region specified in P1 has been unlinked.
System Action:
None.
User Action:
None.
Reason:
The local or remote database is blocked against link access.
System Action:
The traffic manager terminates.
User Action:
Synchronize the databases if you require contact between the regions.
Reason:
The Database does not have a Database Information Record defined. Therefore no correlator ID checking can be performed.
System Action:
The traffic manager terminates.
User Action:
The database has not been initialized correctly. Contact your Systems Administrator.
Reason:
An error was encountered when trying to retrieve a record from the database.
System Action:
Traffic is not received from the linked system until the Link Manager is restarted.
User Action:
Contact your System Administrator.
Reason:
A Traffic Manager attempted the APPC verb P1 which resulted in the error.
System Action:
The conversation is terminated and will be retried later.
User Action:
Determine whether the remote system is still available. Contact your System Administrator.
Reason:
The database correlator does not match the database correlator on the connected region. This indicates that the connected region has been unlinked.
System Action:
The traffic manager will terminate.
User Action:
None.
Reason:
The database at the remote end of the link could not be accessed.
System Action:
The traffic manager will terminate.
User Action:
See the remote log for the cause of the error.
Reason:
An Unlink request has been received from the indicated region.
System Action:
The traffic manager will terminate and the indicated region will be unlinked.
User Action:
None.
Reason:
An Unlink was performed on the local region, P1. This resulted in P2 connected regions being unlinked from this region.
System Action:
All connected regions where unlinked from the local region.
User Action:
None.
Reason:
Either the current region or the linked region was Unlinked and therefore the Traffic Manager is no longer required and has been shut down.
System Action:
None.
User Action:
None.
Reason:
The link manager is stopping the traffic manager specified in P1 for the connected region P2 because the connected region does not have the required license.
System Action:
The traffic manager stops and the internal resource that represents it is deleted.
User Action:
If the remote region should be licensed for the specified type of traffic, stop the region, update it to include the licence, and then restart it.
Reason:
The Linked Regions list service procedure was called with keyword P2 set to a value ( P1 ) which the procedure does not support.
System Action:
The request is rejected.
User Action:
Check the defined allowed values for the keyword P2 and retry.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
The P1 region has been unlinked.
System Action:
None.
User Action:
None.
Reason:
An Unlink was performed on the home region, P1. This resulted in P2 remote region(s) being unlinked from this region.
System Action:
None.
User Action:
None.
Reason:
An error occurred while performing function P1 on vartable P2. The FDBK code returned was P3 and P4 the key of the record being processed.
System Action:
Request rejected.
User Action:
Contact your Systems Administrator.
Reason:
The Unlink option was selected for an ACB other than the current ACB. This option is only supported for the current region.
System Action:
The request is rejected.
User Action:
Log on to the region that you wish to Unlink and select the Unlink (D) option from the Linked Regions list on that region.
Reason:
A vartable error occurred while performing function(P1) on vartable(P2). The FDBK was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact your Systems Administrator.
Reason:
The database correlator does not match with the database correlator on a connected region. This indicates that the connected region has been unlinked.
System Action:
The traffic manager will terminate.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
The local database is blocked against link access.
System Action:
The traffic manager terminates.
User Action:
Synchronize the databases if you require contact between the regions.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
The Database does not have a Database Information Record defined. Therefore no correlator ID checking can be performed.
System Action:
The traffic manager terminates.
User Action:
The database has not been initialized correctly. Contact your Systems Administrator.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
An error was encountered when trying to retrieve a record from the database.
System Action:
Traffic is not sent to the linked system until the Link Manager is restarted.
User Action:
Contact your Systems Administrator.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A Traffic Manager attempted the APPC verb P1 which resulted in the error.
System Action:
The conversation is terminated and will be retried later.
User Action:
Determine whether the remote system is still available. Contact your Systems Administrator.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A region attempted to commence communications with another region, but the former region had been Unlinked while it was not active. A signal will be returned to that region to permanently terminate the connection.
System Action:
None.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A region attempted to commence communications with another region, but the two regions had the same active System Image and could not be connected. P3 identifies the type of connection being attempted.
System Action:
The regions are not connected. Events and database updates are not transmitted between the regions but are held in staging files until the regions are connected.
User Action:
Two connected regions should not have the same active System Image. Load a different System Image in one of the regions, and the regions will be connected automatically.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A link manager from a connected region attempted to start communication with the current region but could not because database synchronization was in progress on the current region.
System Action:
The request is rejected and will be re-attempted when database synchronization has completed.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A link manager from a connected region attempted to start communication with the current region but the connecting region has been Unlinked by user request at some earlier time.
System Action:
The link manager is terminated and the connected region will be permanently disconnected.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A region attempted to commence communications with another region, but the two regions had the same Domain ID and could not be connected. P3 identifies the type of connection being attempted, and P4 is the region to which the connection was being attempted.
System Action:
The regions are not connected. Resource status events are not transmitted between the regions. Database updates are held in staging files until the regions are connected.
User Action:
Two connected regions must not have the same domain ID. Restart one of the regions with a different Domain ID, and the regions will be connected automatically.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
The Link Record definition panel display service procedure was called with keyword P2 set to a value ( P1 ) which the procedure does not support.
System Action:
The request is rejected.
User Action:
Check the defined allowed values for the keyword P2 and retry.
Reason:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The Object ID was 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:
An Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
An error occurred while performing function P1 on vartable P2. The FDBK code returned was P3 and P4 the key of the record being processed.
System Action:
Request rejected.
User Action:
Contact your Systems Administrator.
Reason:
The Link Name assigned to a link definition is already assigned to another link definition.
System Action:
The Link Name field is highlighted as in error.
User Action:
Change the value in the Link Name field.
Reason:
An invalid parameter value was passed to the Link Resource activation/inactivation process ($RMLK05P).
System Action:
The link resource process terminates.
User Action:
Contact Technical Support.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed but the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Contact System Administrator.
Reason:
An invalid class specified.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Both System name and Version are mandatory field.
System Action:
The request is rejected.
User Action:
Specify System name and Version or use '?' to display available System name and Version to the system.
Reason:
Sysname and Version specified is unknown to the system.
System Action:
The request is rejected.
User Action:
Use '?' to list a selection list of Sysname and Version known to system.
Reason:
Template definition is a special definition which must be access only from Customisation Menu option "T".
System Action:
The request is rejected.
User Action:
Access Template definition from Customisation menu option "T".
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 format was received for an unsolicited event data.
System Action:
The event data is not processd; however, the text of the event message is written to the activity log.
User Action:
Contact your local support representative and provide the details of the event message.
Reason:
The profile was requested to be reset, but no profile was in effect.
System Action:
The request is rejected.
User Action:
None.
Reason:
A restart of the transient log handler completed without errors.
System Action:
None.
User Action:
None.
Reason:
The transient log handler terminated because a restart of the handler was requested.
System Action:
None.
User Action:
None.
Reason:
You attempted to start the transient log handler; however, it is already running.
The transient log handler is always restarted during a system image load and should never be stopped while the region is active.
System Action:
None.
User Action:
None.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
The command which was entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
Function key P1 was pressed and the command assigned to it was invalid
System Action:
Command is rejected.
User Action:
Contact System Administrator.
Reason:
You attempted to view transient log records; however, logging is disabled for this resource.
Logging is disabled by one of the following methods:
System Action:
None.
User Action:
None.
Reason:
A PROFILE EDS command, issued internally by Resource Learning, failed with message P1.
System Action:
Resource Learning fails.
User Action:
Contact your local support representative.
Reason:
Resource Learning is listening for any messages concerned with the resource that is being created. These will be displayed on the list automatically as soon as they are detected.
System Action:
None.
User Action:
None.
Reason:
The profile command entered is invalid.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun the executable.
Reason:
The profile is reset.
System Action:
None.
User Action:
None.
Reason:
The profile was modified successfully.
System Action:
None.
User Action:
None.
Reason:
The profile command was not successful.
System Action:
None.
User Action:
Correct and retry.
Reason:
The transient log size for the current resource is P1 (increased or decreased) from P2 to P3 for one of the following reasons, P4:
Indicates that the transient log size for this resource has been updated.
Indicates that the default value specified in the AUTOTABLES parameter group has been updated.
Indicates that the maximum value specified in the AUTOTABLES parameter group has been updated.
Indicates that the maximum value specified in the AUTOTABLES parameter group has been updated and the current value specified for this resource exceeds this maximum.
System Action:
None.
User Action:
None.
Reason:
The current view of the transient log browser ended because the log is being resized.
System Action:
None.
User Action:
Retry the L command to restart the transient log browser.
Reason:
The indicated number, P1, of messages in the transient log are deleted according to the retention period specified in the AUTOTABLES parameter group.
System Action:
None.
User Action:
None.
Reason:
A message was received by the logger procedure for a resource that has the 'Log to Activity Log' flag set to YES.
P1 is the class of the resource.
P2 is the resource name.
P3 is the severity level of the message.
P4 is the ID of the NCL process that raised the message.
P5 is the name of the NCL procedure that raised the message.
P6 is the actual message received by the logger procedure.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
As this resource exists in a remote region, an APPC conversation is required to process this log request. APPC function P1 has ended in error. P2 contains the return code, P3 the feedback code, and P4 the message describing the failure.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your systems administrator.
Reason:
The profile command entered was invalid.
System Action:
The request is rejected.
User Action:
Respecify the profile with the correct keywords.
Reason:
The profile was requested to be reset, but no profile was in effect.
System Action:
The request is rejected.
User Action:
None.
Reason:
The profile has been reset.
System Action:
None.
User Action:
None.
Reason:
The profile has been modified successfully.
System Action:
None.
User Action:
None.
Reason:
The profile command was not successful.
System Action:
None.
User Action:
Correct and retry.
Reason:
The command which was entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
Function key P1 was pressed and the command assigned to it was invalid
System Action:
Command is rejected.
User Action:
Contact System Administrator.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
As this resource exists in a remote region, an APPC conversation is required to process this log request. APPC function P1 has ended in error. P2 contains the return code, P3 the feedback code, and P4 the message describing the failure.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your systems administrator.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
Procedure in unexpected APPC "What Received" State.
System Action:
None.
User Action:
Contact System Administrator.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
The PROFILE command entered was invalid.
System Action:
The request is rejected.
User Action:
Respecify the PROFILE command with the correct keywords.
Reason:
The profile was requested to be reset, but no profile was in effect.
System Action:
The request is rejected.
User Action:
None.
Reason:
The profile has been reset.
System Action:
None.
User Action:
None.
Reason:
The profile has been modified successfully.
System Action:
None.
User Action:
None.
Reason:
The user cancelled the profile command.
System Action:
None.
User Action:
None.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
The command which was entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
Function key P1 was pressed and the command assigned to it was invalid
System Action:
Command is rejected.
User Action:
Contact System Administrator.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
You have selected a service or an owner resource. No resource records were found to match the service or ownership criteria for the resource. The type is identified by P1, and the name of the service or owner is identified by P2.
System Action:
None.
User Action:
The message is informational only.
Reason:
An error occurred while attempting to build a resource list for the entity identified by P1 .
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while getting the first record in the vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while adding a record to the vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while getting a record from the vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while getting a record from the $RM$$LOGOBJ vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
Procedure $RMLOAD was invoked with an invlaid value of P2 for keyword P1.
System Action:
Request rejected.
User Action:
Correct call and retry.
Reason:
Self Explanatory
System Action:
Request rejected.
User Action:
Specify one of the correct values
Reason:
The entity identified by P1 has been shut down due to a request for a system image load made by the user identified by P2.
System Action:
Informational only.
User Action:
None.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This message indicates an action being performed by the system image load procedure.
System Action:
None.
User Action:
None.
Reason:
A System Image load request was rejected because the System Image is loaded on a linked region.
System Action:
None.
User Action:
None.
Reason:
A System Image load request was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The System Image name supplied in a load command is not the name of an active System Image.
System Action:
The load request is rejected.
User Action:
Correct the System Image name and retry.
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 a full license is required, contact Technical Support.
Reason:
The valid values for P1 are 'YES' or 'NO'.
System Action:
Request rejected.
User Action:
Specify one of the correct values either 'YES' or 'NO'.
Reason:
Cannot Warm Start as Checkpoint Restart is not active.
System Action:
Value changed to 'YES', error message displayed to user.
User Action:
None.
Reason:
A request to load a new system image was rejected because there is already a system load in progress. The current load was started at P1.
System Action:
Request rejected.
User Action:
None.
Reason:
The LXCMD/VMCMD handler is attempting to connect to the Linux Connector Command Server, but the token containing the port number is not yet available.
P1 identifies the token being queried.
System Action:
The unsolicited message receiver will continue to retry querying the token every 30 seconds.
User Action:
Ensure that Linux Connector is available.
Reason:
The LXCMD/VMCMD handler is attempting to connect to the Linux Connector's Command Server, but found that the value of "Connect to Linux Connector" was set to NO.
System Action:
The LXCMD/VMCMD handler terminates.
User Action:
If connection to Linux Connector is desired change the value of the "Connect to Linux Connector?" parameter in the LINUXCONNECT parameter group to YES.
Reason:
The LXCMD/VMCMD handler is attempting to connect to the Linux Connector Command Server but has not been able to connect on port P1.
System Action:
The LXCMD/VMCMD handler ends.
User Action:
Ensure that Linux Connector is available.
If Linux Connector is available, ensure that the value specified in the Command Server Token/Port field of the LINUXCONNECT parameter group matches the value specified for the CMDTOKEN or CMDPORT parameter in the Linux Connector LNXPARMS member.
Reason:
The LXCMD/VMCMD handler has successfully connected to the Linux Connector COMMANDS server; however, the server has terminated the connection.
System Action:
The LXCMD/VMCMD handler terminates.
User Action:
For assistance, contact CA Support.
Reason:
The unsolicited message traffic receiver is attempting to connect to the Linux Connector Unsolicited Message Server, but the token containing the port number is not yet available.
P1 identifies the token being queried.
System Action:
The command handler ends.
User Action:
Ensure that Linux Connector is available.
Reason:
The unsolicited message traffic receiver has successfully connected to the Linux Connector's Unsolicited Message Server. P1 is the job name of the Linux Connector Main Task and P2 is its IP address.
System Action:
None
User Action:
None
Reason:
The unsolicited message traffic receiver has successfully connected to the Linux Connector Unsolicited Message Server; however, the server did not follow the correct connection protocol.
System Action:
The unsolicited message receiver terminates.
User Action:
Check that the unsolicited message receiver is pointing to the correct port/token. A common problem is that the unsolicited message receiver is configured to point to the Commands Server instead of the Unsolicited Message Server. For further assistance, contact CA Support.
Reason:
The unsolicited message traffic receiver has successfully connected to the Linux Connector Unsolicited Message Server; however, the server has terminated the connection.
P1 contains the reason if available.
System Action:
The unsolicited message receiver terminates.
User Action:
For assistance, contact CA Support.
Reason:
The unsolicited message traffic receiver was started, but found that the value of "Connect to Linux Connector" was set to NO.
System Action:
The unsolicited message receiver terminates.
User Action:
If connection to Linux Connector is desired change the value of the "Connect to Linux Connector?" parameter in the LINUXCONNECT parameter group to YES.
Reason:
The unsolicited message traffic receiver is attempting to connect to the Linux Connector Unsolicited Message Server but has not been able to connect on port P1.
System Action:
The unsolicited message traffic receiver retries connecting every 30 seconds.
User Action:
Ensure that Linux Connector is available.
If Linux Connector is available, ensure that the value specified in the Unsolicited Message Server Token/Port field of the LINUXCONNECT parameter group matches the value specified for the MSGTOKEN or MSGPORT parameter in the Linux Connector LNXPARMS member.
If Linux Connector uses a different TCP/IP stack, update the Alternate IP Address field in the LINUXCONNECT parameter group to specify the corresponding IP address.
Reason:
The unsolicited message traffic receiver is trying to verify that the TCP/IP interface is active before establishing a connection. This message indicates that no such interface is active.
System Action:
The unsolicited message traffic receiver retries TCP/IP verification every 30 seconds.
User Action:
Make sure that the TCP/IP interface has started successfully.
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 ruleset name specified is not defined.
System Action:
The request is rejected.
User Action:
Correct and retry. Enter ? in the Ruleset Name field to view a list of rulesets.
Reason:
A prompt list was presented, but you did not choose an item.
System Action:
No value is entered.
User Action:
None.
Reason:
The specified system name and version combination does not exist.
System Action:
The request is rejected.
User Action:
Correct and retry. Use ? to display a list of valid system image names.
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:
Check that the file is not allocated to another application.
Reason:
You have selected an incorrect mode when adding records to your Automation Services database.
MERGE adds the imported records that are new but does not affect any existing records. OVERLAY adds the imported records that are new and updates existing records. REPLACE deletes any existing target records before importing records to the RAMDB.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The specified dataset is not valid. Either it does not exist, or it is not sequential with a record length of at least 80 characters (LRECL=80).
System Action:
The request is rejected.
User Action:
Specify a valid dataset and retry.
Reason:
The request, P1 , has been rejected because there is a multisystem task already in progress. The request cannot be performed while another task is in progress.
System Action:
The request is rejected.
User Action:
Wait for the current task to complete.
Reason:
You have attempted to link this region into a multi-system network. However, this region is already part of a multi-system network.
System Action:
The request is rejected.
User Action:
If you want to proceed with this request, you must first disconnect this region from the existing multi-system network using the UNLINK option (U).
Reason:
You have selected the U option to unlink this region from a multi-system network. However, this region is not currently part of a multi-system network.
System Action:
The request is rejected.
User Action:
None.
Reason:
The specified system image already exists in the knowledge base. You cannot autopopulate an existing sysplex system image.
System Action:
The field in error is highlighted.
User Action:
Change the value in the Version field to specify a sysplex system image that is not already in the knowledge base and retry.
Reason:
The P1 system image is not an image that is defined in the knowledge base and cannot have resources defined to it.
System Action:
Access to the resource learning feature is prevented.
User Action:
Define a system image in the knowledge base, and load it in the region.
Reason:
The TCP/IP sockets interface is not active. The express setup of IP resources cannot continue unless this interface is active.
System Action:
Request rejected.
User Action:
The TCP/IP sockets interface is started by the $NM SOCKETS parameter group in Customizer. Enter /PARMS to access the Customizer parameter groups and check that the $NM SOCKETS parameter group specifies the correct values. Check the parameter group log for any errors. Ensure that this parameter group has been actioned.
Reason:
The NETSTAT interface is not available. The express setup of IP resources cannot continue unless this interface is active.
System Action:
Request rejected.
User Action:
The NETSTAT interface is activated by the Sub-System Interface (SSI) hat is connected to this region. Ensure that the SSI that this region is connected to is active.
Enter /PARMS to access the Customizer parameter groups and check that the $NM SSI parameter group specifies the correct SSI ID. Check the parameter group log for any errors.
Ensure that the parameters of the SSI task specify UNIX=YES (this enables the NETSTAT interface).
If your region is running CA NetMaster File Transfer Management, you must specify UNIX=YES in a separate SSI to the one this region is connected to. Both SSI tasks must be active. Ensure that both SSIs have the same XCFGROUP= value specified.
Reason:
A macro was invoked with the SERVICE keyword set to value P1 which is not supported.
System Action:
Request is rejected.
User Action:
Correct the SERVICE keyword and re-try.
Reason:
A macro was invoked with the OPTION keyword set to value P1 which is not supported.
System Action:
Request is rejected.
User Action:
Correct the SERVICE keyword and re-try.
Reason:
A macro was invoked with an invalid SERVICE and OPTION combination.
System Action:
Request is rejected.
User Action:
Correct either the SERVICE or OPTION keyword and re-try.
Reason:
The macro identified by P1 was invoked without the required parameter identified by P2
System Action:
Request is rejected
User Action:
Correct call and re-try.
Reason:
The macro identified by P1 was invoked without one of the two parameters identified by P2 and P3. One of these must be specified for successful execution.
System Action:
Request is rejected.
User Action:
Correct call and re-try.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
While defining macro parameters the field identified by P1 was not entered and is a required field.
System Action:
Field highlighted in error.
User Action:
Enter a value for the specified field
Reason:
The value, P1 , is not valid for the field, P2 .
System Action:
The field in error is highlighted.
User Action:
Enter a valid value for the field, P2 .
Reason:
The data entered in the field identified by P1 contains imbedded blanks. Blanks are not allowed anywhere in this field except at the end.
System Action:
Field highlighted in error.
User Action:
Remove the imbedded blanks
Reason:
The field identified by P1 is required if a value has been entered into the field identified by P2.
System Action:
Field highlighted in error.
User Action:
Enter a value for the specified field
Reason:
The field identified by P1 cannot contain any data if none was entered into the field identified by P2.
System Action:
Field highlighted in error.
User Action:
Enter a value in the field identified by P2 or clear the field identified by P1
Reason:
The value/values identified by P1 are the only acceptable values for this selection field.
System Action:
Field highlighted in error.
User Action:
Enter one of the valid values in the specified field
Reason:
One of the two paramaters identified by P1 and P2 must be specified for successful execution of this macro.
System Action:
Fields highlighted in error.
User Action:
Specify one of the required fields.
Reason:
The two paramaters identified by P2 and P3 cannot both be specified for successful execution of this macro.
System Action:
Fields highlighted in error
User Action:
Blank out one of the fields.
Reason:
When specifying delimiters for a PARSE macro, single and double quotes cannot both be specified in the one delimter string.
System Action:
Fields highlighted in error
User Action:
Use only a single or double quote in the delimiter string.
Reason:
It is invalid, when specifying message text to begin the message text with a wildcard character (in this case identified by P1).
System Action:
Field(s) highlighted in error.
User Action:
Do not specify a wildcard character as the first character of message text.
Reason:
Invalid character value specified.
System Action:
Field in error highlighted.
User Action:
Correct and try again.
Reason:
There is a choice of fields to be entered. Although none is mandatory in itself, at least one of the fields must be entered.
System Action:
Field in error is highlighted
User Action:
Please enter data in one of the fields indicated or cancel
Reason:
A numeric field must be entered and it must be in the indicated range.
System Action:
Field in error is highlighted.
User Action:
Please enter data in the range indicated.
Reason:
Field P1 must be of type P2.
System Action:
Field in error is highlighted.
User Action:
Enter the correct type of data.
Reason:
The field P1 must be null if the field P2 has the value P3.
System Action:
Field in error is highlighted.
User Action:
Please enter data in the range indicated.
Reason:
The field P1 cannot have the value P2 when field P3 has been specified.
System Action:
Field in error is highlighted.
User Action:
Change the value of P1 or blank out the value for P3.
Reason:
The field P1 cannot have a value that specifies a date or time from the past, it must always be in the future.
System Action:
Field in error is highlighted.
User Action:
Change the value of P1 to specify a future moment.
Reason:
DBCS data was encountered during validation. DBCS data is not valid in this field.
System Action:
The value is rejected.
User Action:
Enter a non-DBCS value.
Reason:
The data in field P1 contains an invalid variable name. A variable must start with an & followed by a name that:
- Consists of national and alphanumeric characters
- Does not start with a numberic character
- Contains no embeded blanks
System Action:
The field in error is highlighted.
User Action:
Correct the variable name.
Reason:
You cannot change the actual state of a SYSPLX class resource.
System Action:
If the error occurs on the SETSTATE Macro Parameter Definition panel, the field in error is highlighted. If the error occurs during the execution of the macro, the state change is not honored while the other settings are honored.
User Action:
Review the process definition to ensure that the process is not defined to change the actual state of a sysplex resource.
Reason:
The EVVARSET or EVVARGET macro failed because the name of the EventView variable is invalid. P1 is the invalid name.
System Action:
The process step fails.
User Action:
Correct the process or if a variable is used to specify the Eventview variable name at execution time, ensure that the variable resolves to a valid name.
Reason:
The EVVARSET or EVVARGET macro failed because the name of the EventView variable is not provided. P1 is the variable used to set the EventView variable name.
System Action:
The process step fails.
User Action:
Ensure that variable P1 resolves to a valid name at execution time.
Reason:
The macro to reply to an outstanding WTOR was invoked, and the parameter "LAST WTOR?" was set to "YES". However, there was no record of an outstanding WTOR message.
System Action:
The request is rejected.
User Action:
Determine the reason for the absence of the expected WTOR. Make any necessary corrections and re-try.
Reason:
The macro to reply to an outstanding WTOR was invoked, and the parameter "WTORTEXT" was specified. However, no outstanding WTOR was found which matched the supplied text (P1).
System Action:
The request is rejected.
User Action:
Determine the reason for the absence of the expected WTOR. Make any necessary corrections and re-try.
Reason:
This message will issue when defining parameters to reply to a WTOR, but none of the three methods of identifying the WTOR has been indicated. The WTOR to be replied to may be identified by entering, YES in the LASTWTOR field, the name of the job which issued the WTOR or by entering text to match an outstanding WTOR against.
System Action:
All WTOR Identification fields are highlighted in error.
User Action:
Specify at least one of the identification methods.
Reason:
When specifying WTOR Identification the 'JOBNAME' and 'TEXT' fields cannot be entered if the 'LASTWTOR' field has been set to 'YES'. Specifying 'YES' in this field indicates that the last recorded WTOR is to be replied to and so no further forms of identification are required.
System Action:
Field(s) in error are highlighted.
User Action:
Clear either the 'LASTWTOR' field or the highlighted field(s)
Reason:
The macro to reply to an outstanding WTOR was invoked, and the parameter "JOBNAME" was specified. However, no outstanding WTOR was found for this job.
System Action:
The request is rejected.
User Action:
Determine the reason for the absence of the expected WTOR. Make any necessary corrections and re-try.
Reason:
A request was made to answer an outstanding WTOR for a job, identified by P1. However, it was determined during processing that the required job is not active.
System Action:
Request is rejected.
User Action:
Determine why the required job was not active.
Reason:
While trying to identify the required outstanding WTOR the macro has timed out.
System Action:
None
User Action:
None
Reason:
During execution of a REPLY macro, the parameters of the macro were found to include a JOBNAME in the WTOR Identification field. JOBNAME selection is only supported if the process is executed on an MVS or MSP system. On VOS3, it it not possible to identify WTORs by their issuing Jobname.
System Action:
Process continues. Jobname is ignored.
User Action:
Ensure LAST WTOR or WTOR MESSAGE TEXT is included in the REPLY macro parameters to identify the WTOR to be replied to.
Reason:
Parameters for a process must be in the KEYWORD format acceptable as input to a SETVARS NCL statement.
System Action:
Highlight the field in error.
User Action:
Enter the parameters in a valid KEYWORD format. i.e. KEYWORD=value
Reason:
Parameters for a process must be in the KEYWORD format acceptable as input to a SETVARS NCL statement.
System Action:
Highlight the field in error.
User Action:
Enter the parameters in a valid KEYWORD format. i.e. KEYWORD=value
Reason:
The RUNPRCSS Macro has detected that if it allowed processing to continue the NCL nesting limit will be exceeded.
System Action:
Process is terminated.
User Action:
Check for unintentional recurssion.
Reason:
When specifying the dataset name where the JCL to be submitted resides no member name was specified. The member which contains the JCL must be specified in dataset name.
System Action:
Field highlighted in error.
User Action:
Specify the member name which contains the required JCL
Reason:
In the SVAPI macro, you specified a value in the Class field that does not match the class associated with the command to be issued. P1 identifies the command.
System Action:
Field in error is highlighted.
User Action:
To correct the problem, do one of the following:
- Change the value of the Class field to match the selected command.
- Enter ? in the Command field, and select a suitable command for the specified class.
Reason:
The compare defined within the parentheses was processed successfully.
P1 contains the value being tested, P2 contains the compare operator and P3 contains the constant or variable value to which P1 was compared.
P4 contains the return code from the compare - '0' is returned when the compare result is true and '4' when it is false.
System Action:
None.
User Action:
None.
Reason:
No EVENT for specified Event profile arrived within defined timeframe.
System Action:
Macro Execution terminates with user defined return code.
User Action:
Adjust Event profile or time window.
Reason:
The defined From Status does not match with the actual Resource Value.
System Action:
Macro Execution terminates with return code 4.
User Action:
Adjust Event profile.
Reason:
The data entered in the field identified by P1 contains a variable name which has imbedded blanks. Blanks are not allowed within a variable name except at the end.
System Action:
Field highlighted in error.
User Action:
Remove the imbedded blanks
Reason:
A record defining the action to be taken when an alert is raised is missing.
System Action:
None.
User Action:
To recreate the action, ensure that Function=UPDATE and press F10 (Actions).
Reason:
An attempt has been made to include more than 2 resources in the resource field for this macro.
System Action:
The field in error is highlighted.
User Action:
Re-enter the resource field data so that it conforms to the rules for an event.
Reason:
Field P1 does not conform to the rules specified for EVENT names.
System Action:
The field in error is highlighted.
User Action:
Correct the data entered according to the rules for event names as specified for the &EVENT verb in the NCL Reference.
Reason:
Resource P1 does not conform to the rules specified for resource names. Resource names are allowed to contain alphnumeric characters and the special characters '@#$.-:' and can be a maximum of 64 bytes long.
System Action:
The field in error is highlighted.
User Action:
Correct the data entered according to the rules for resource names.
Reason:
An attempt has been made to include more than 2 resources in the resource field for this macro.
System Action:
The field in error is highlighted.
User Action:
Re-enter the resource field data so that it conforms to the rules for an event.
Reason:
Field P1 does not conform to the rules specified for EVENT names.
System Action:
The field in error is highlighted.
User Action:
Correct the data entered according to the rules for event names as specified for the &EVENT verb in the NCL Reference.
Reason:
Resource P1 does not conform to the rules specified for resource names. Resource names are allowed to contain alphnumeric characters and the special characters '@#$.-:' and can be a maximum of 64 bytes long.
System Action:
The field in error is highlighted.
User Action:
Correct the data entered according to the rules for resource names.
Reason:
This message is logged during process execution of a WAITEVNT macro. It records the event on which the process is waiting. Message RMMC2904 is followed by one or more messages RMMC2904A with details of the event profile.
System Action:
The process waits for the event to occur.
User Action:
None.
Reason:
This message is logged during process execution of a WAITEVNT macro. The event on which the process is waiting has occurred. Message RMMC2905 is followed by one or more messages RMMC2905A with details of the received event.
System Action:
The process continues.
User Action:
None.
Reason:
This message is logged during process execution of a WAITEVNT macro. The event on which the process is waiting has not occurred during the nominated timeout period of P1 seconds.
System Action:
The WAITEVNT macro completes with a return code of 4. Any subsequent steps in the process are executed.
User Action:
None.
Reason:
Procedure, P1, was invoked without the required parameter, P2.
System Action:
Request is rejected.
User Action:
Contact your local support representative.
Reason:
Procedure $RMMC31S timed out on an &INTREAD statement waiting for a response from the service procedure.
System Action:
Processsing continues.
User Action:
Contact your local support representative.
Reason:
The value, P1, is not valid for the field, P2. Valid values are identified by P3.
System Action:
Field in error is highlighted.
User Action:
Enter a valid value for the specified field.
Reason:
The user has entered static data together with one or more variables in the same field. Static data and variables cannot be mixed in the same field.
System Action:
Field in error is highlighted.
User Action:
Re-enter the data into seperate fields.
Reason:
An illegal variable name has been entered into the field highlighted.
System Action:
Field in error is highlighted.
User Action:
Correct the variable name and re-enter.
Reason:
The value P1 is not a valid Job Identifier.
System Action:
Field is set in error.
User Action:
Specify a valid Job Identifier. There are two valid formats allowed:
xxxnnnnn - where xxx is either JOB, STC, or TSU and nnnnn is a numeric value from 1 to 5 digits.
xnnnnnnn - where x is either J, S, or T and nnnnnnn is a numeric value from 1 to 7 digits.
Reason:
The process with name P1 and with process identifier P2 is in status P3 which is the required status.
System Action:
Macro processing completed.
User Action:
None.
Reason:
A process with the name P1 and identifier P2 was not found.
System Action:
Macro processing completes.
User Action:
None.
Reason:
The timeout period expired before process with name P1 entered the status P2.
System Action:
Macro processing terminates with requested return code.
User Action:
None.
Reason:
The timeout after period has expired for macro P1.
System Action:
Macro processing completes.
User Action:
None.
Reason:
The response message queue for macro P1 has overflowed.
System Action:
Macro processing terminates.
User Action:
None.
Reason:
An error occurred while performing function P1 against the SNMP trap destination dataset P2 . RETCODE P3 was returned with error message P4 .
System Action:
Process terminates.
User Action:
Ascertain the cause of the error, correct and retry,
Reason:
An error occurred while encoding the MDO to be used to write the SNMP trap. RETCODE is P1 with FEEDBACK P2
System Action:
Process terminates.
User Action:
Ascertain the cause of the error, correct and retry,
Reason:
An error occurred while performing SOCKET function P1 . The return code is P2 ,with feedback P3 and ZSOCERRN P4 .
System Action:
Process terminates.
User Action:
Ascertain the cause of the error, correct and retry,
Reason:
The system variable ZTCP that contains the state of NetMaster for TCP/IP is not currently set to ACTIVE.
P1 identifies the current value of ZTCP.
System Action:
Process terminates.
User Action:
Ascertain the cause of the error, correct and retry.
Reason:
The PINGCD macro needs to know which dataset contains the supplied CONNECT:Direct process, $RFPNGCD. It uses the process to check the availability of remote nodes. This information is currently unavailable to it. It will issue the command, $RFCALL ACTION=SETPING, to try to find the dataset.
System Action:
$RFCALL OPT=SETPING is issued to try to ascertain the dataset name. If unsuccessful, an error message will be logged and the macro ended.
User Action:
If unsuccessful, try re-issuing either the PINGCD macro or $RFCALL ACTION=SETPING.
Reason:
The result of the concatenation exceeds 256 characters and was truncated when stored in the P1 variable.
System Action:
Processing continues.
User Action:
If you do not want the result to be truncated, reduce the length of the input data.
Reason:
The data to be concatenated contains text and variable without an intervening blank (for example, A&B). The data must contain only pure text and pure variables separated by blanks.
System Action:
Field in error is highlighted.
User Action:
Correct the input data.
Reason:
The P1 variable has an invalid name.
System Action:
Field in error is highlighted.
User Action:
Specify the correct variable.
Reason:
The "Exception Report Filter" field and the "FTSCHD" field details are mutually exclusive.
System Action:
The validation fails.
User Action:
Specify value for either the "Exception Report Filter" field or the "FTSCHD" fields but not both.
Reason:
The date and time fields are mutually exclusive with the "Within the last" field.
System Action:
The validation fails.
User Action:
Specify value for either the date and time fields or the "Within the last" field but not both.
Reason:
You specified mutually exclusive values in both the Report Definition Details and the Period to Check boxes.
System Action:
The validation fails.
User Action:
Refer to the RMMC4101 and RMMC4102 message Help for user actions.
Reason:
You have specified invalid dates.
System Action:
The validation fails.
User Action:
Correct the dates in the highlighted fields.
Reason:
You have specified an invalid date-time combination.
System Action:
The validation fails.
User Action:
Correct the date and time in the highlighted fields.
Reason:
The FTCHECK macro requires input for both the "Report Definition Details" and the "Period to Check" boxes.
System Action:
The validation fails.
User Action:
Specify the required values.
Reason:
No P1 class resource definitions were found.
System Action:
The list of resource definitions is not displayed.
User Action:
None.
Reason:
You did not select a value for the highlighted field.
System Action:
None
User Action:
None
Reason:
The FTCHECK macro requires input for the "Report Definition Details"box.
System Action:
The validation fails.
User Action:
Specify required value.
Reason:
The FTCHECK macro requires input for the "Period to Check" box.
System Action:
The validation fails.
User Action:
Specify required value.
Reason:
The name of the FTSCHD class resource definition that contains the filter is required.
System Action:
The validation fails.
User Action:
Specify a valid FTSCHD name, or enter ? to select from a list of file transfer schedule monitor definitions.
Reason:
A socket connection was successfully established to the IP Address/Host Name identified by P1.
System Action:
None
User Action:
None
Reason:
A socket connection to the IP Address/Host Name identified by P1 failed to be established.
System Action:
Socket connection is not made. Macro ends with RC=8.
User Action:
None
Reason:
A request to establish a socket connection has failed because an open connection already exists. The ID is P1. Only one open connection at a time is supported in a process.
System Action:
Socket connection is not made. Macro ends with RC=8.
User Action:
None
Reason:
A socket connection cannot proceed. The target address is IPv6, but the sockets API on region P1 supports IPv4 addresses only.
System Action:
Socket connection is not made. Macro ends with RC=8.
User Action:
Check the SOCKETS parameter group (/PARMS) in the P1 region. For IPv6 support, TCP/IP Software Type must specify IBMV6.
Reason:
A socket connection with ID P1 was successfully closed.
System Action:
None
User Action:
None
Reason:
A socket connection with ID P1 was not successfully closed.
System Action:
Macro ends with a return code of 8.
User Action:
None
Reason:
Data was successfully sent to a connection with socket ID P1.
System Action:
None
User Action:
None
Reason:
A send to a socket connection with ID P1 was not successful.
System Action:
Macro ends with a return code of 8.
User Action:
None
Reason:
The hex string&P1&was found to contain invalid hex characters.
System Action:
The value is rejected.
User Action:
Enter only valid hex characters.
Reason:
Data was received from a connection with socket ID P1 which caused the macro to end with Return Code P2 .
System Action:
None
User Action:
None
Reason:
A receive from a socket connection with ID P1 was not successful.
System Action:
Macro ends with a return code of 8.
User Action:
None
Reason:
The macro request has successfully completed.
System Action:
The request is completed.
User Action:
No action is required.
Reason:
This message logs the macro command to the activity log.
System Action:
None.
User Action:
Check the activity log for details. Contact your System Administrator.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected.
User Action:
Correct the keyword value and retry.
Reason:
A numeric field of the indicated range must be entered.
System Action:
Field in error is highlighted.
User Action:
Please enter data in the range indicated.
Reason:
A mandatory field must be entered.
System Action:
Field in error is highlighted.
User Action:
Please enter data in the range indicated.
Reason:
A mandatory field must be entered with a valid value.
System Action:
Field in error is highlighted.
User Action:
Please enter data in the range indicated.
Reason:
When defining macro parameters the field identified by P1 was incorrect. This is a required field.
System Action:
Field highlighted in error.
User Action:
Enter a value for the specified field.
Reason:
The value specified for this field is not valid. Use ? to display a selection list of valid values.
System Action:
The request is rejected.
User Action:
Use ? to specify a valid value.
Reason:
No value selected from the selection list displayed.
System Action:
None
User Action:
None
Reason:
There is either a subsystem error or the scheduler is inactive.
System Action:
The macro interface has a problem.
User Action:
Check if the scheduler is active. Contact your System Administrator.
Reason:
This message provides information about Retcode and Sysmsg for command execution.
System Action:
The request is completed.
User Action:
Check the value of Retcode and Sysmsg.
Reason:
The command issued by the macro failed.
System Action:
The macro has encountered a problem issuing the command.
User Action:
Check the Retcode and Sysmsg.
Reason:
Invalid value specified in either PRODUCT, SSID, or COMMAND.
System Action:
Macro command parameter has an error.
User Action:
Check the value entered in Product, SSID, or Command.
Reason:
This message provides details of the macro command.
System Action:
No action is required.
User Action:
No action is required.
Reason:
Invalid product type specified in PRODUCT.
System Action:
Macro command parameter has an error.
User Action:
Check the value entered in PRODUCT.
Reason:
The subsystem is not available.
System Action:
Macro command execution has an error.
User Action:
Contact your System Administrator.
Reason:
The reply from the Schedule system has timed out.
System Action:
The macro has encountered a problem retrieving from the Scheduling System.
User Action:
Check the Retcode and Sysmsg.
Reason:
The P1 Subsystem cannot be started.
System Action:
Macro command processing has an error.
User Action:
Contact your System Administrator.
Reason:
There is a subsystem error.
System Action:
The macro interface has a problem. The request is rejected.
User Action:
Contact your System Administrator. Check the activity log for details.
Reason:
There is an error in the CA-7 subsystem.
System Action:
The macro interface has a severe problem. The request is rejected.
User Action:
Contact your System Administrator.
Reason:
There is a subsystem error.
System Action:
The macro interface has a severe problem. The request is rejected.
User Action:
Contact your System Administrator.
Reason:
There is a subsystem error.
System Action:
The macro interface has a severe problem. The request is rejected.
User Action:
Contact your System Administrator.
Reason:
There is an unknown command passed to P1 subsystem.
System Action:
The macro interface has a severe problem. The request is rejected.
User Action:
Check the command used and retry.
Reason:
Invalid parameter count passed to P1 subsystem.
System Action:
The request is rejected.
User Action:
Check the parameter count and retry.
Reason:
Invalid parameter name passed to P1 subsystem.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
Invalid path name passed to P1 subsystem.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
Duplicated path name passed to P1 subsystem.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
Unknown path name passed to P1 subsystem.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
Storage shortage in P1 subsystem.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
Function not valid in this state.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
P1 is not running as a subsystem.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
An unknown command count has been passed to P1 subsystem.
System Action:
The request is rejected.
User Action:
Check the command text used and retry.
Reason:
There is no command reply passed from P1 subsystem.
System Action:
The request is rejected.
User Action:
Check the command text and scheduling system and then retry.
Reason:
Invalid instance specified in product subsystem name.
System Action:
The macro command parameter has an error.
User Action:
Check the value entered in SSID.
Reason:
The subsystem for CA-7 is not running due to an open path failure.
System Action:
The macro command execution has an error.
User Action:
Contact your System Administrator.
Reason:
The background user cannot log on to CA-7 because of a password problem.
System Action:
Macro command execution has an error.
User Action:
Contact your System Administrator.
Reason:
The CA-7 API procedure was invoked with an invalid value, identified by
P1 for the keyword parameter identified by P2.
System Action:
The request is rejected. The interface procedure ends with return code 16.
User Action:
Correct the invalid keyword parameter.
Reason:
The background user cannot log on to CA-7 because their password has expired.
System Action:
Macro command execution has an error.
User Action:
Contact your System Administrator.
Reason:
The background user cannot log on to CA-7 because their password has expired.
System Action:
Macro command execution has an error.
User Action:
Contact your System Administrator.
Reason:
Unsupported Operating System. The macro can only be run on MVS ESA or higher.
System Action:
No action is required.
User Action:
Stop execution of the macro.
Reason:
The ResourceView message filter occasionally issues a FORCE status change for a particular resource because the filter has seen a state change message that is serious but was not acted on by any message definition in the Knowledge base (for example, JCL errors in a started task procedure). In this case, however, the state change was obsolete.
If this message appears in the activity log, a resource identifier is appended to the end of the message (for example, - STC(MYTASK)).
System Action:
The FORCE state change is rejected.
User Action:
Ignore the message.
Reason:
The ResourceView message filter occasionally issues a FORCE status change for a particular resource because the filter has seen a state change message that is serious but was not acted on by any message definition in the Knowledge base (for example, JCL errors in a started task procedure). The status being forced is indicated by P1.
If the message appears in the activity log, a resource identifier is appended to the end of the message (for example, - STC(MYTASK)).
System Action:
The state of the resource is changed to P1.
User Action:
Review the resource definition to see whether the event can be catered for by explicit message definitions. If not, there is no harm in leaving ResourceView to continue raising FORCE status events.
Reason:
This message indicates that the ResourceView filter has seen a message
P1 that it does not know how to handle. It is unable to determine what resource this message should apply to in order to continue to process the rest of the filter.
System Action:
The message is skipped after raising this warning. No action is taken.
User Action:
The message P1 would normally be a message that is issued by the operating system on behalf of a resource but is not otherwise related to the resource. Messages with JOBNAMES such as *MASTER* or CONSOLE fall into this category. Report the message to your technical support representative.
Reason:
Internal error in the ResourceView message filter.
System Action:
Recovery is attempted but may not be successful.
User Action:
Report the message to your technical support representative.
Reason:
The message indicates that the ResourceView secondary filter is now ready to process events from the ResourceView Primary filter.
System Action:
None.
User Action:
None.
Reason:
The ResourceView Secondary Message filter has terminated. All message event processing will cease.
System Action:
The monitor will be restarted when required.
User Action:
None.
Reason:
The ResourceView message filter is split into two parts, the Primary filter and the Secondary filter. The primary filter tests only the first 12 characters of a message while the secondary filter tests the entire message text. This message indicates that a message passed the primary filter but failed to pass the secondary filter.
System Action:
No action is taken by the system other than to issue this warning message.
User Action:
This warning message indicates a close miss for one or more messages defined in the Knowledge base. This may be because of a typing error or a system error caused by the inclusion of a variable string in the message definition such as a time stamp. Review the matching defined message(s).
Reason:
The ResourceView Message Filter has attempted to update the status of a resource but the update failed.
System Action:
The status change for the resource listed in P1 will not be recorded.
User Action:
Report the message to your technical support representative.
Reason:
The message filter failed to obtain exclusive control of the lock with primary name P1 and minor name P2. This indicates that another process is already running and failed to end.
System Action:
Message filter terminates.
User Action:
None.
Reason:
A WTOR message issued by this resource was detected but not defined in the resource definition. An alert to this effect was raised by the message filter task.
If the message appears in the activity log, a resource identifier is appended to the end of the message (for example, - STC(MYTASK)).
System Action:
An extended display message was forced on the resource display.
User Action:
Use the W command to view and respond to the WTOR messages.
Reason:
The ResourceView Message filter Loader received a non-zero return code when attempting to retrieve a message rule from the Knowledge base.
System Action:
The message listed in P1 is not loaded into the filter and its associated state change and actions will not be executed.
User Action:
Report the message to your technical support representative.
Reason:
The ResourceView message loader encountered a serious error P1 while attempting to load all resource message rules into the filter P2.
System Action:
LOAD processing is stopped.
User Action:
Report the message to your technical support representative.
Reason:
Internal diagnostic message.
System Action:
None.
User Action:
Ignore.
Reason:
Internal diagnostic message.
System Action:
Updates to the knowledge base will no longer be reflected in the message filter.
User Action:
If this message occured after a SHUTDOWN was issued then it can be ignored. Otherwise report it to your technical support representative.
Reason:
The maximum number of resources supported by ResourceView has been exceeded. Remaining resources will be ignored. The maximum number of resources that are currently supported in one ResourceView region is 9999.
System Action:
Remaining resources defined will be ignored.
User Action:
Use Containment Resource definitions to group numerous, like resources such as JES LINES or DASD devices instead of defining individual resource instances. Contact your technical support representative if further assistance is required.
Reason:
During the load of a system image, all the required message filters could not be loaded because the 'AOM Filter Table Size' parameter was too small. During automatic recovery for this failure after extending the table size, it again encountered this error.
System Action:
The system image is not loaded.
User Action:
Report the problem to your technical support representative.
Reason:
During the load of a system image, it was found that the AOM Filter Table Size initialization parameter is too small. The system has loaded successfully after automatically increasing the table limit but the default limit should be increased to at least P1 for better performance of the system load process.
System Action:
The limit has been dynamically expanded, and the message filter table has been loaded successfully; however, the load has been attempted twice.
User Action:
Update the initialization parameter AOM Filter Table Size in the parameter group $RM AUTOTABLES, to at least the value specified. This avoids the overhead of loading the filter table again after automatically adjusting the table size.
Reason:
This message is issued when the user has defined log text to be written.
P1 contains the message text defined by the user.
System Action:
None.
User Action:
None.
Reason:
The region issued the operating system command P1 .
System Action:
None.
User Action:
None.
Reason:
The region issued the reply P1 to the outstanding WTOR message P2 .
System Action:
None.
User Action:
None.
Reason:
None.
System Action:
None.
User Action:
None.
Reason:
None
System Action:
None
User Action:
None
Reason:
None
System Action:
None
User Action:
None
Reason:
None
System Action:
None
User Action:
None
Reason:
None
System Action:
None
User Action:
None
Reason:
None
System Action:
None
User Action:
None
Reason:
None
System Action:
None
User Action:
None
Reason:
The procedure identified by P1 was invoked with an invalid value, identified by P3 for the keyword identified by P2.
System Action:
Request is rejected, procedure terminates.
User Action:
Correct keyword in error and retry.
Reason:
A request to reply to a WTOR was made without supplying the information necessary to identify the WTOR. Either the WTOR Reply Id or the Message Text should be supplied to allow the message to be identified.
System Action:
Request is rejected, procedure ends.
User Action:
Supply either the WTOR Reply Id or the Message Text.
Reason:
The system command P1 was successfully issued.
System Action:
None
User Action:
None
Reason:
Reply P1 has been issued in response to outstanding WTOR message P2.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact your local support representative.
Reason:
This message is an audit message to provide a record that a state change exit has been run on behalf of the resource identified by P1.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is an audit message to provide a record that a state change exit run on behalf of the resource identified by P1 has ended. The return code is identified by P2 and the sysmsg by P3.
System Action:
Processing continues.
User Action:
None.
Reason:
The NCL procedure identified by P2 is being run on behalf of resource
P1.
System Action:
Processing continues.
User Action:
None.
Reason:
A change of state to P1 has tried to execute NCL procedure P2 which does not exist.
System Action:
The NCL procedure is not run.
User Action:
Check that the NCL procedure name is correct and that it exists.
Reason:
The NCL procedure identified by P2 run on behalf of resource P1 has completed with return code P3 and the sysmsg P4.
System Action:
Processing continues.
User Action:
None.
Reason:
The NCL procedure identified by P2 run on behalf of resource P1 has completed with an error, the return code is P3 and the sysmsg P4.
System Action:
Processing continues.
User Action:
Determine the cause of the error from the RC and SYSMSG and correct the problem.
Reason:
The State Change Exit Handler was not passed the parameters required for it to identify the object identifier of a resource.
System Action:
Processing continues.
User Action:
Contact your local support representative.
Reason:
The process identified by P2 is being run on behalf of resource P1.
System Action:
Processing continues.
User Action:
None.
Reason:
An error has occurred running a process. P1 contains the error message.
System Action:
Processing continues.
User Action:
Determine the cause of the error and correct the problem.
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 vartable error has occurred while processing this request.
System Action:
Allocation error - no further processing. Otherwise, processing continues.
User Action:
Contact your system administrator.
Reason:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
The database is only capable of holding upto 97 monitor messages for a resource. Your request will cause this limit to be exceeded.
System Action:
The request is rejected.
User Action:
None.
Reason:
The request is invalid if the message text is blank.
System Action:
The request is rejected.
User Action:
Enter message text and retry.
Reason:
Requested process has been cancelled.
System Action:
None.
User Action:
None.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The values 'AUTOMATED' and 'MANUAL' are the only values recognized for the Automation Mode field.
System Action:
Request rejected.
User Action:
Specify one of the correct values.
Reason:
The Global Mode is already set to the requested mode.
System Action:
The request is 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 a full license is required, contact Technical Support.
Reason:
The MTO command is not supported for this resource. The MTO command is supported only for:
- Started tasks of type CICS, IMS, or SOLVE
- Other started tasks that specify an ACB name
- Jobs that specify an ACB name - CICS resources
System Action:
The command is rejected.
User Action:
If appropriate, select another command.
Reason:
You specified an invalid value in the P1 field.
System Action:
The field value was not updated.
User Action:
Specify a valid value in the field.
Reason:
An unexpected result was encountered for a command that needed to use the old RAMDB. The command was UDBCTL OPEN or CLOSE, or NDB START or STOP. If the message in the activity log is N28503 or N15613 and the VSAM ACB reason code is X'A8', the old RAMDB was probably in use elsewhere.
System Action:
The migration utility waits for further input.
User Action:
Examine the activity log for messages. You can access information about the codes from the System Support : Messages and Codes Menu (/Codes).
Reason:
User P1 is currently using the migration utility, and you are not able to use it.
System Action:
None.
User Action:
Confer with the other user about the use of the utility.
Reason:
This function cannot be performed on the VM operating system
System Action:
None.
User Action:
If this region is connected to a region on another operating system it may be possible to perform the function on the other region
Reason:
You have exitted from the RAMDB Migration Utility.
System Action:
None.
User Action:
If you wish to perform further RAMDB migration select option M from the RAMDB Utilities Menu.
Reason:
An invalid keyword value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact your local Support Center.
Reason:
The P1 operation on the P2 vartable failed. P3 is the scope of the table. P4 is the returned code.
System Action:
The migration utility terminates.
User Action:
If the region is short of storage, restart the region with more storage; otherwise, contact your local Support Center.
Reason:
You did not select any knowledge base component to migrate.
System Action:
The sction terminates.
User Action:
Select at least one component from the list, and do the action again.
Reason:
An invalid keyword value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact your local Support Center.
Reason:
The P1 operation on the P2 vartable failed. P3 is the scope of the table. P4 is the returned code.
System Action:
The migration utility terminates.
User Action:
If the region is short of storage, restart the region with more storage; otherwise, contact your local Support Center.
Reason:
You did not select a knowledge base component to migrate.
System Action:
The action terminates.
User Action:
Select at least one component from the list, and do the action again.
Reason:
There were no components of the selected class to migrate. Either the components have not changed or the components do not exist in the old knowledge base.
System Action:
None.
User Action:
Press F3 to exit from the empty list.
Reason:
An invalid keyword value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
The P1 operation on the P2 vartable failed. P3 is the scope of the table. P4 is the returned code.
System Action:
The migration utility terminates.
User Action:
If the region is short of storage, restart the region with more storage; otherwise, contact Technical Support.
Reason:
The migration utility does not support the Review action for components which are (or are reserved for) distributed data. These are the templates ($TEMPLAT) Versions 1 through 9 and the global processes ($PROCESS) Version 1. Only modified records in these components can be migrated.
System Action:
The action is ignored.
User Action:
Review the RMMUAD05 messages in the activity log to identify the records that have not been migrated. If you want to migrate those records, make a copy of the affected component in the old knowledge base and then migrate the copy.
Reason:
The migration utility has completed copying all or selected components. You can find details of the copied records in the activity log through RMDBMS00 messages. If any records were not copied, the details of those records are in RMMUAD05 messages. You can use the TEXT log command to isolate particular messages.
System Action:
None.
User Action:
Enter /LOG to display activity log. In the log, enter TEXT RMMUAD05 at the Command prompt to display only RMMUAD05 messages. Review the messages to identify the records that have not been migrated. If you want to migrate those records, use the R (Review) action or make a copy of the affected component in the old knowledge base and then migrate the copy.
Reason:
An invalid keyword value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact your local Support Center.
Reason:
During knowledge base migration, you tried to rename a component without providing the new name.
System Action:
None.
User Action:
Specify the new name for the component you want to rename before applying the R (Rename) action.
Reason:
The P1 operation on the P2 vartable failed. P3 is the scope of the table. P4 is the returned code.
System Action:
The migration utility terminates.
User Action:
If the region is short of storage, restart the region with more storage; otherwise, contact your local Support Center.
Reason:
You entered R (Review) beside a component that was fully migrated. There are no outstanding items for further action.
System Action:
None.
User Action:
None.
Reason:
An error was encountered while attempting to access the RAMDB database.
P1 is the DD name of the database.
P2 is an NDB response code.
P3 is a message.
System Action:
The procedure terminates without successfully migrating the objects.
User Action:
Contact your local Support Center.
Reason:
The P1 operation on the P2 vartable failed. P3 is the scope of the table. P4 is the returned code.
System Action:
The migration utility terminates.
User Action:
If the region is short of storage, restart the region with more storage; otherwise, contact your local Support Center.
Reason:
The P1 operation for the current component was successful.
System Action:
None.
User Action:
None.
Reason:
The knowledge base migration procedure is terminating in error. P1 is the error condition.
System Action:
The procedure terminates without successfully migrating all of the definitions.
User Action:
Contact Technical Support.
Reason:
The knowledge base migration procedure has found a duplicate item.
P1 is the name of the system image.
P2 is the version of the image.
P3 is the class of the item.
P4 is the name of the item. This will be blank for System Image and Template Image definitions. (Class 01).
System Action:
The duplicate item is not copied.
User Action:
If you want to migrate the item, use the R (Review) action or make a copy of the affected component in the old knowledge base and then migrate the copy.
Reason:
An action for a GENALERT macro is not in the old knowledge base. The macro is in a process with the object ID P2 that is a concatenation of the following:
- Image name
- Image version
- 71 (class number for process definitions)
- Process name
System Action:
The process is copied without the action record.
User Action:
Note the process, and update it to recreate the missing action.
Reason:
A process contains a GENALERT macro with an action. However, the action record is in another system image in the old knowledge base. Another copy of the action record is created in the system image in which the process is defined.
System Action:
The process is copied with the action record created in the same image.
User Action:
None.
Reason:
The P1 operation on the P2 vartable failed. P3 is the scope of the table. P4 is the returned code.
System Action:
The migration utility terminates.
User Action:
If the region is short of storage, restart the region with more storage; otherwise, contact your local Support Center.
Reason:
The migration utility encountered an error while trying to access the
P1 database.
System Action:
The procedure is terminated without migrating any objects.
User Action:
Use the P2 NDB response code and the P3 message to determine the cause of the error. To get Help about NDB codes, enter /NDBERR to display the Browse NDB Error Codes panel.
Correct the database error, then retry the operation.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected.
User Action:
Correct the keyword value and retry.
Reason:
You have issued an action other than RESET for a resource that failed validation. The only valid action for these resources is RESET (RS), which revalidates the resource.
System Action:
Request rejected.
User Action:
If the error condition for this resource has been rectified, issue RS against the resource to revalidate it.
Reason:
You can issue action P1 against resources of type or status P2 only.
System Action:
Request rejected.
User Action:
None.
Reason:
The resource P1 does not exist in the target system image. The move request is rejected. P2 is the target system image name and P3 is the version. When you move a local resource to another system, the resource must be defined in the system image on the remote system.
System Action:
The command is rejected.
User Action:
Ensure that the correct system image was selected and that the resource to be moved is defined in the selected image.
Reason:
You tried to move a resource's control from one system to another but did not select a target system.
System Action:
The request is rejected.
User Action:
Select a target system when you move a resource.
Reason:
A fatal error occured involving the internal table used to control the execution of the move command. The name of the table should be passed to procedure $RMMVCMD in variable &ZRMMOVETABLE. P1 contains a description of the error.
System Action:
The command is rejected.
User Action:
Retry the move command. If problems persist, contact Technical Support.
Reason:
The move command successfully moved resource P1 to system P2. The resource is in system image P3-P4 (for local resources the system image will be different as a result of the move).
System Action:
None.
User Action:
None.
Reason:
Resource P1 is in mode P2 on the target system P3 with version P4. You cannot move the resource if the target system contains the resource in a mode other than OFF.
System Action:
The move is rejected.
User Action:
None.
Reason:
A MANUAL override is placed on resource P1 so that it can be terminated before it is moved.
System Action:
The MANUAL override is issued against the resource.
User Action:
None.
Reason:
The move command is not valid for the type of resource indicated by P1.
System Action:
The command is rejected.
User Action:
None.
Reason:
The move command is processing for resource P1. P2 gives information about the current situation.
System Action:
The move is processing in background mode and continues when resource events occur.
User Action:
None.
Reason:
The resource P1 is not in a state that permits the move to P2 to progress. P3 provides the reason.
System Action:
Processing terminates.
User Action:
None.
Reason:
You issued the move command in a subordinate region. This is not valid because only a focal region has the visibility to remote regions to complete the command successfully.
System Action:
The command is rejected.
User Action:
Log on to a focal region, and issue the command from there.
Reason:
The move command is not valid for resources that are in the status indicated by P1.
System Action:
The command is rejected.
User Action:
None.
Reason:
The move command is not valid for shared resources that are active on more than one system.
System Action:
The command is rejected.
User Action:
None.
Reason:
The move command is not valid for shared resources that do not have the target system, identified by P1, in their system affinity list.
System Action:
The command is rejected.
User Action:
None.
Reason:
Action P2 will be performed on resource P1. P2 is TERMINATED or ACTIVATED.
System Action:
Processing continues.
User Action:
None.
Reason:
Resource P1 is in status P2. The MANUAL mode override placed on P1 as part of the move is removed.
System Action:
The mode override is removed.
User Action:
None.
Reason:
Resource P1 is part of a Shared System Image; therefore, its Home System is changed from P2 to P3.
System Action:
None.
User Action:
None.
Reason:
An invalid value was entered in the 'Local or Remote?' field.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The user identified by P1 is being prevented from accessing the function selected due to insufficient access authority. A user requires AOM message receipt, All routcodes and console authority equal to or greater than 'C'.
System Action:
A message is displayed to the user.
User Action:
Contact your system administrator.
Reason:
The resource name mask contains DBCS characters. DBCS values are not valid in this field.
System Action:
The request is rejected.
User Action:
Correct the mask, and retry the operation.
Reason:
The system image name P1 is special and cannot be accessed from this menu option.
System Action:
The request is rejected.
User Action:
Access to the system image P1 may be possible through other menu options or menus. Refer to the manual for more information.
Reason:
Template definitions are special and cannot be accessed from this panel.
System Action:
The request is rejected.
User Action:
Access template definitions from the Template Definition Menu.
Reason:
The system image name P1 is special and cannot be accessed from this menu option.
System Action:
The request is rejected.
User Action:
Access to the system image P1 may be possible through other menu options or menus. Refer to the manual for more information.
Reason:
The NDB parameter member P1 was not found. This member contains the necessary parameters required to define all the fields in the SSO NDB.
System Action:
NDB definitions not added to the SSO NDB.
User Action:
Check the COMMANDS concatenation, ensuring that the SSO distributed libraries are available.
Reason:
The NDB parameter member P1 was processed and there were P2 field definitions and P3 duplicate field definitions.
System Action:
Processing continues with the definition of the fields into the NDB.
User Action:
None.
Reason:
A duplicate field definition for field P1 was encountered in the NDB parameter member. The duplicate field definition was ignored.
System Action:
None.
User Action:
Ensure that the field name is correctly spelt.
Reason:
The NDB parameter member P1 is to be used in defining the necessary NDB fields.
System Action:
None.
User Action:
None.
Reason:
The NDB parameter member P1 is to be used in defining the necessary NDB fields.
System Action:
Processing terminates.
User Action:
Check the reason for the error and retry the request.
Reason:
The field P2 could not be defined in the NDB P1. The action being done was P3 and the NDB return code was P4.
System Action:
Processing terminates.
User Action:
Check the reason for the error and retry the request.
Reason:
The NDB definitions for P1 were processed and there were P2 field definitions, P3 errors and P4 duplicate field definitions.
System Action:
Processing continues.
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 Criteria P1 was deleted.
System Action:
None.
User Action:
None.
Reason:
The Calendar Criteria P1 is being updated by user P2.
System Action:
Request is rejected.
User Action:
Try later.
Reason:
The Calendar Criteria select list was presented but a calendar criteria was not selected.
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:
There were no Activity Schedules found for the specified System Image.
System Action:
Request is rejected.
User Action:
Specify another System and/or Version.
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:
There were no records found which reference the Calendar Criteria P1 in the specified System Image.
System Action:
Request is rejected.
User Action:
Specify another System Image.
Reason:
The object of type P1 with name P2 does not exist in the database.
System Action:
Request is rejected.
User Action:
Specify an existing object.
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:
The Calendar Criteria definition P1 was saved in the database.
System Action:
None.
User Action:
None.
Reason:
The maintenance function P1 for the calendar criteria definition P2 was cancelled.
System Action:
All changes to the Calendar Criteria since the last SAVE command are discarded.
User Action:
None.
Reason:
The maximum number of Calendar Criteria expression lines allowed is P1. This number has already been reached and no more lines can be added.
System Action:
The request is rejected.
User Action:
None.
Reason:
An error occurred trying to perform action P1 with table P2 resulting in a feedback code of P3. The key used was P4.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The parentheses specification for P1 parenthesis is invalid.
System Action:
Field is set in error.
User Action:
Specify valid parentheses of type P1.
Reason:
An expression line was entered with parentheses but no other details.
System Action:
Fields set in error.
User Action:
Specify other fields or blank out the parentheses.
Reason:
A boolean value is required when multiple lines of expression are specified. The line P1 is the line in error.
System Action:
Field set in error.
User Action:
Specify a boolean value.
Reason:
The parentheses specified for the criteria expression are unbalanced. There are P1 left parentheses and P2 right parentheses.
System Action:
Fields set in error.
User Action:
Specify an equal number of left and right parentheses.
Reason:
No Calendar Criteria expression was specified.
System Action:
Fields set in error.
User Action:
Specify at least one line of expression.
Reason:
At least one Calendar Criteria expression must be specified.
System Action:
Fields set in error.
User Action:
Specify at least one line of expression.
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:
Infoman function unsuccessful.
System Action:
None.
User Action:
None.
Reason:
The OIM application is running on a Remote system and therefore requires the problem details to be ROF'ed to this remote system. A remote SIGNON has been issued, but has timeout before success notification.
System Action:
Processing terminates in error.
User Action:
Ensure the INMC link to this system is available and retry.
Reason:
The region will wait 60 seconds for a response from the OIM application when raising a problem ticket. The time period has expired without any response.
System Action:
Processing terminates in error.
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:
Infoman function successful. Record number as mentioned.
System Action:
None.
User Action:
None.
Reason:
Infoman function unsuccessful.
System Action:
None.
User Action:
None.
Reason:
Vartable error on nsuccessful.
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:
One or more INFOMAN required field null.
System Action:
No further processing.
User Action:
Contact your system administrator.
Reason:
The INFOMAN problem ticket wasn't supplied.
System Action:
None.
User Action:
None.
Reason:
Infoman call complete.
System Action:
None.
User Action:
None.
Reason:
INFOMAN API initialization has failed.
System Action:
No further processing.
User Action:
Contact your 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:
INFOMAN API command failed.
System Action:
No further processing.
User Action:
Contact your 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 SOLVE:Problem application is running on a remote system and therefore requires the problem details to be sent by ROF to this remote system. A remote SIGNON has been issued, but has timeout before success notification.
System Action:
Processing terminates in error.
User Action:
Ensure that the INMC link to this region is available, and retry.
Reason:
The region will wait 60 seconds for a response from the SOLVE:Problem application when raising a problem ticket. The time period has expired without any response.
System Action:
Processing terminates in error.
User Action:
None.
Reason:
No service procedure specified in the parameter for the panel driver.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Panel to display does not exist in the library path.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Requested process has been completed successfully.
System Action:
None.
User Action:
None.
Reason:
You tried to file or save a definition that has not been changed. The requested action is not performed.
System Action:
The definition is not saved again.
User Action:
None.
Reason:
Requested process has been canceled.
System Action:
None.
User Action:
None.
Reason:
Validation found no entry specified on mandatory field.
System Action:
The request is rejected.
User Action:
Specify entry on field in error.
Reason:
Invalid option specified on the panel driver menu selection.
System Action:
The request is rejected.
User Action:
Specify valid option of the menu display.
Reason:
There is no help found for the panel being displayed.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Request to save the record definition to the database has been successfully completed.
System Action:
None.
User Action:
None.
Reason:
The command which was entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
Request to create a new record definition to the database has been successfully completed.
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:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
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:
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 entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
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:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
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:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
Profile definition to be created already exists in the database.
System Action:
The request is rejected.
User Action:
Specify a different profile name and ID.
Reason:
There is no use saving this profile definition because nothing has been specified for the message flow criteria (from 3rd to the last panel).
System Action:
The request is rejected.
User Action:
Specify message selection criteria.
Reason:
The cursor was not placed over the include or exclude area before pressing the Scrllist function key.
System Action:
None.
User Action:
Place the cursor in the include or exclude fields on the panel and press the Scrllist function key to get a scrollable list of include or exclude values.
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:
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:
The cursor was not placed over the include or exclude area before pressing the Scrllist function key.
System Action:
None.
User Action:
Place the cursor in the include or exclude fields on the panel and press the Scrllist function key to get a scrollable list of include or exclude values.
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:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
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:
There is no use saving this profile definition because nothing has been specified for the message flow criteria (from 3rd to the last panel).
System Action:
The request is rejected.
User Action:
Specify message selection criteria.
Reason:
The cursor was not placed over the include or exclude area before pressing the Scrllist function key.
System Action:
None.
User Action:
Place the cursor in the include or exclude fields on the panel and press the Scrllist function key to get a scrollable list of include or exclude values.
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:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
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:
There is no use saving this profile definition because nothing has been specified for the message flow criteria (from 3rd to the last panel).
System Action:
The request is rejected.
User Action:
Specify message selection criteria.
Reason:
The cursor was not placed over the include or exclude area before pressing the Scrllist function key.
System Action:
None.
User Action:
Place the cursor in the include or exclude fields on the panel and press the Scrllist function key to get a scrollable list of include or exclude values.
Reason:
An invalid keyword was passed to the service procedure $RMPD34L.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
Requested process has been cancelled.
System Action:
None.
User Action:
None.
Reason:
The database is only capable of holding up to 97 entries to be included or excluded. Your request exceeds this amount.
System Action:
The request is rejected.
User Action:
None.
Reason:
A vartable error has occurred while processing this request.
System Action:
Request rejected..
User Action:
Contact your systems administrator.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
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:
There were more tha 9999 log records.
System Action:
The first 9999 log records will be displayed.
User Action:
None
Reason:
The process identified by P1 has been selected for update or interactive mode but another user identified by P2 is already using it.
System Action:
Reject request
User Action:
None
Reason:
The PDF process execution procedure was invoked without the required parameter identified by P1
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The PDF process execution procedure was invoked with an invalid value of P2 for the parameter identified by P1
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The PDF process identified by P1 has begin execution and its NCLID is identified by P2.
System Action:
None
User Action:
None
Reason:
The object type identified by P1, with a name of P2, was not found
System Action:
Request rejected
User Action:
Determine the correct name or the reason for the object's absence. Correct the error, and retry.
Reason:
The process P1 ended with a bad return code of P3 from step P2
System Action:
None
User Action:
None
Reason:
The PDF process identified by P1 has ended execution and its return code is P2.
System Action:
None
User Action:
None
Reason:
The NCL procedure identified by P1 was executed as a result of specifying process $NCL.
System Action:
None
User Action:
None
Reason:
The user cancelled execution of the process identified by P1
System Action:
None
User Action:
None
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A process was invoked and the parameters passed did not conform to the keyword=value format (keyword format). P1 is set to either ALLPARMS or SHRVARS to indicate the source of the parameters. Message RMPDFE18 is written to the Activity Log and lists the parameter string in error.
System Action:
Execution of the process is terminated.
User Action:
Correct the definition for the process invocation to specify all parameters in the keyword format.
Reason:
The process identified by P1 was not run due to the associated resource definition not being found in the database/status table.
System Action:
The process is not executed.
User Action:
Contact your system administrator.
Reason:
The NCL procedure identified by P1 was not run due to the associated resource definition not being found in the database/status table.
System Action:
The NCL procedure is not executed.
User Action:
Contact your system administrator.
Reason:
A request to interactively execute the $NCL process cannot be actioned because these processes are not supported in interactive mode.
System Action:
The request is rejected.
User Action:
None.
Reason:
Step P2 which executed macro P3 returned an undefined step name as the next step to execute. The undefined step name is P1.
System Action:
The process is terminated in error.
User Action:
Correct the target step name returned from step P2 by macro P3.
Reason:
The step P1 returned another step name that is to be the next step to execute, however, this step has already altered the flow of control in the process by the allowed limit of P2 as specified in the macro or as defaulted. This limit can not be exceeded and is used to prevent the process from looping continuously.
System Action:
The process is terminated in error.
User Action:
Correct the specifications in the process to prevent step P1 from being executed more than the specified limit, or increase the limit.
Reason:
The process identified by P1 has been selected for update or interactive mode but another user identified by P2 is already using it.
System Action:
The request is rejected.
User Action:
Try later.
Reason:
The step to be restarted was not found in the process. P1 is the relative number of the step to be restarted. This occurs if the process on the database has been modified since it was last executing.
System Action:
The process is terminated in error.
User Action:
None.
Reason:
This message is written to the log in conjunction with message RMPDFE10. It lists the parameters in error referred to in message RMPDFE10.
System Action:
None
User Action:
None
Reason:
The process logger received an event which indicated that the process driver procedure ended abnormally. The logger will then dump the process logs to the activity log, clear them, and then end.
System Action:
None
User Action:
None
Reason:
The process identified by P1 has begun execution
System Action:
None
User Action:
None
Reason:
The process identified by P1 has chained to the process identified by P2. The P2 process will then execute. Processing will not return to the P1 process.
System Action:
None
User Action:
None
Reason:
The process identified by P1 has ended execution with a return code of P2.
System Action:
None
User Action:
None
Reason:
The process identified by P1 has begun execution on behalf of resource
P2.
System Action:
None.
User Action:
None.
Reason:
THe macro identified by P1 was not found
System Action:
Request rejected
User Action:
Determine the reason for the macro's absence. Correct the error, and retry.
Reason:
The step, P2, of process, P1, was not run because it failed to pass the pre-requisite condition for its execution
System Action:
Attempt to execute the next step in the process
User Action:
None
Reason:
This message issues after RMPDFS02 and outlines the condition which the step failed to satisfy (P1) and the return code of the step (P2)
System Action:
Attempt to execute the next step in the process
User Action:
None
Reason:
The step, P2, of process, P1, has begun execution
System Action:
None
User Action:
None
Reason:
Step, P2, of process P1 has ended either successfully or unsuccessfully as denoted by P3. If successfully completed the STEPRC, the value used in evaluating conditions on subsequent steps, will be displayed at the end of the message text.
System Action:
None.
User Action:
None.
Reason:
This message issues after RMPDFS04 if the step ended and returned a value in SYSMSG. P1 is the value os SYSMSG.
System Action:
None
User Action:
None
Reason:
The PDF process utility procedure was invoked without the required parameter identified by P1
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The PDF process utility procedure was invoked with an invalid value of P2 for the parameter identified by P1
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
The panel identified by P1 has been selected for update or interactive mode but another user identified by P2 is already using it.
System Action:
Reject request
User Action:
None
Reason:
A command has been issued with invalid syntax
System Action:
Reject request
User Action:
Correct wrong syntax and re-try
Reason:
A command has been issued which requires a panel name to be specified, but the panel name has been omitted.
System Action:
Reject request
User Action:
Specifiy a panel name and re-try
Reason:
A command has been issued which requires a panel name to be specified, but the panel name is invalid.
System Action:
Reject request
User Action:
Specifiy a valid panel name and re-try
Reason:
An attempt was made to CREATE a new panel, using the name of a panel which already exists in that library.
System Action:
Reject request
User Action:
Specifiy a panel name which does not already exist and re-try
Reason:
The panel identified by P1 has had the action identified by P2 performed against it successfully.
System Action:
None
User Action:
None
Reason:
The library identified by P1 has not been defined
System Action:
Request rejected
User Action:
None
Reason:
The panel identified by P1 was not saved because the were no changes detected.
System Action:
None
User Action:
None
Reason:
The selected option was unavailable because the region has not yet completed its initialization process.
System Action:
None.
User Action:
Wait until the region has finished initializing, and retry.
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:
No Field Prompt Entry found for the field.
System Action:
The request is rejected.
User Action:
To create an entry, use option P from Customisation menu.
Reason:
User has placed a ? in a field which supports field prompting, however a Field Prompt List corresponding to this particular field has not been defined. Some prompt lists are delivered with the product, but not in this case. The name of the required prompt list is P1.
System Action:
No prompt list is displayed and the field is highlighted in error.
User Action:
Use the Field Prompt Lists option of the Automation Services Administration Menu to define the required prompt list.
Reason:
Entries defined already reached 97.
System Action:
The request is rejected.
User Action:
None.
Reason:
This is a diagnostic message.
System Action:
None.
User Action:
Collect all the details related to the message and any associated messages, and forward them on to your local support representative.
Reason:
An invalid value was specified for the keyword P1. The value was P2.
System Action:
Processing terminates.
User Action:
Contact your support representative.
Reason:
The function P1 could not obtain exclusive control for the required resource. The resource was the PPI receiver ID P2. P3 was the return code from the lock, and P4 was the feedback code.
System Action:
The request to activate the function is rejected.
User Action:
No actions are required. There is already a process performing the desired functions.
Reason:
An error occurred while processing a PPI queue. The PPI receiver ID for the queue was P1, and the verb issued was P2. The return code from the PPI was P3, and the feedback code was P4.
System Action:
Processing is retried or suspended.
User Action:
Determine the reason the PPI action failed, and correct the situation. The receiver process will resume processing if PPI is still active or when the PPI becomes active. The PPI return codes and feedback codes are documented in the Network Control Language Reference.
Reason:
The function P1 was terminated as requested. The PPI receiver ID being used for the function was P2.
System Action:
None.
User Action:
None.
Reason:
The notification from a PPI receive request was P1.
System Action:
Processing for the queue continues (if possible).
User Action:
No actions are required. If processing cannot continue, another message is issued to give further details of the problem.
Reason:
The resource P1 performing the function P2 with PPI receiver ID P3 has status P4 for reason P5.
System Action:
None.
User Action:
None.
Reason:
A client process requested that its response queue for P1 be cleared and the request was successfully completed.
System Action:
All responses received for past requests will be discarded.
User Action:
None.
Reason:
A client process sent an invalid request to P2. The invalid request was
P1.
System Action:
None.
User Action:
Contact your support representative.
Reason:
A client process sent a request to server P1 but the server was unable to process the registration table. The feedback code was P2 and the key was P3.
System Action:
The request is rejected.
User Action:
Contact your support representative.
Reason:
A client process sent a request to P1 and it was accepted.
System Action:
The request is processed by the server, and responses are queued to the client process as they become available.
User Action:
None.
Reason:
A client process sent a request to server P1 and a communications error occurred.
System Action:
The request is rejected, and the server is set as INACTIVE.
User Action:
Check the status of the PPI link P1 and check the transient log for related error messages.
Reason:
A request to the P1 PPI agent for job name P2 failed because its status is not active. Its current status is P3.
System Action:
The request is rejected.
User Action:
Determine the reason why the P1 PPI agent is not active by checking the messages in the transient log of the internal resource for the PPI agent.
Reason:
This is a general response message for a client from the server P1. P2 is the message from the server.
System Action:
None.
User Action:
None.
Reason:
A command was sent to the P1 system with jobname P2 . However, not all responses arrived within the time out interval (30 seconds).
System Action:
No more responses will be delivered for the command entered.
User Action:
Ensure that the agent system P1 is responding, and check the internal resource managing the connection to the system. This may occur if the system response time is slow or the agent system is overloaded.
Reason:
This is a general response message indicating that no more responses will be received from P1 for the previously entered command.
System Action:
None.
User Action:
None.
Reason:
An error occurred while trying to retrieve the message filter for the command server for job name P1 . The table accessed was P2 , the feedback code received was P3 , and the key used was P4 .
System Action:
No message filtering is done for unsolicited messages received from the linked region. That is, all messages are delivered to this region and processed.
User Action:
Contact Technical Support.
Reason:
A request to system type P1 was invalid because the specified job name was either invalid or is not linked. P2 is the jobname that was specified.
System Action:
The requset is rejected.
User Action:
Specify the name of an active and linked P1 job.
Reason:
A request to system type P1 was invalid. The job name specified was P2 and the invalid command was P3.
System Action:
The requset is rejected.
User Action:
Specify a valid command for the system type P1.
Reason:
A request to a send a command to the P1 job P2 failed either because the P1 region is not active or because no connection has been established.
System Action:
The request is rejected.
User Action:
Determine the status of P1 P2 and its connection to this region. The agent must be installed in the P1 region, and either this region must have an explicit CICS connection definition in ICS or this region must have Dynamic Registration in ICS set to YES.
Reason:
Invalid data was received on the PPI queue. The PPI ID for the queue was P1, P2 was the MDO return code, P3 was the MDO feedback code and P4 was the MDO component which was invalid.
System Action:
The data is logged to the log and discarded.
User Action:
Contact your software support representative.
Reason:
This is an informational message showing the data received on the PPI queue. It is associated with message RMPP0020.
System Action:
None.
User Action:
None.
Reason:
The data received on the PPI queue P1 was invalid. The data received was P2 but the expected data is P3.
System Action:
The data is discarded.
User Action:
Contact your support representative.
Reason:
Internal message only.
System Action:
None.
User Action:
None.
Reason:
The PPI processing function identified by P1 could not create the internal resource P1. This resource is needed to provide control of the function. The error returned from the create was P2.
System Action:
Another attempt to create the resource will be made in 5 minutes.
User Action:
Check the log for additional messages that may indicate the reason for not being able to create an internal resource.
Reason:
The unsolicited message delivery facility from system P2 of type P1 is inactive because another PPI receiver has control of the interface currently. The PPI receiver ID of the other region is P3 .
System Action:
No unsolicited messages are delivered to this region from the identified system.
User Action:
No actions are required. However, if you require this region to have control of the interface, deactivate the interface of the other region.
Reason:
While validating and/or compiling free form statements, an invalid statement type was encountered. The statement type was P2 and P1 is the line number on which the statement started.
System Action:
The free form statements are rejected.
User Action:
Correct the statement type on line P1.
Reason:
While validating and/or compiling free form statements, invalid keyword syntax was encountered. The statement which caused the error starts on line number P1 and the error message is P2.
System Action:
The free form statements are rejected.
User Action:
Change the syntax to use only keyword format parameters for the desired statement type. If a statement does not fit on a single line, use the plus (+) continuation character to continue the statement on the next line. If a keyword value contains blanks or special characters, enclose the value with single or double quotes. Comments can be included at the end of a line by specifying the comment characters "-*". All text after the comment characters and up to the end of the line is ignored.
Reason:
While validating and/or compiling free form statements, an invalid value was encountered for the keyword P2. The value was P3 which is invalid. The statement started on line number P1.
System Action:
The free form statements are rejected.
User Action:
Enter a valid value for the keyword P2.
Reason:
The filter with name P2 has already been specified. This is a duplicate specification and is not allowed. The duplicate filter statement starts on line P1.
System Action:
The free form statements are rejected.
User Action:
Delete one of the filter specifications with the name P2.
Reason:
The CICS connection with P2 set to P3 has already been specified. This is a duplicate specification and is not allowed. Each CICS specification must have a unique JOBNAME and SYSID. The duplicate specification starts on line P1.
System Action:
The free form statements are rejected.
User Action:
Delete one of the CICS specifications that have the P2 keyword set to
P3.
Reason:
A CICS statement was specified with queue prefix and suffix combinations that conflict with another CICS definition or with the other queue for the current CICS definition. The duplicate specification starts on line P1. The duplicate queue was a P2 type queue with name P3 and the previously identified queue was a P4 type queue.
System Action:
The free form statements are rejected.
User Action:
Delete one of the CICS specifications, or alter the prefix and suffix combination to form a unique queue name.
Reason:
A CICS statement specified a filter that does not exist. The statement in error starts on line P1.
System Action:
The free form statements are rejected.
User Action:
Correct the FILTER= specification for the CICS definition in error or define the missing filter.
Reason:
An unexpected vartable access error occurred. The vartable name was P1, the verb was P2, the feedback code was P3 and the key was P4.
System Action:
Procedure terminates in error.
User Action:
Contact your system support representative.
Reason:
The specified CICS filter and definition statements were compiled, and P3 command servers were started. There were P1 filters and P2 CICS definitions.
System Action:
None.
User Action:
None.
Reason:
A PPI manager process was started and no notification was received of it status. The type of manager was P1 and the PPI queue it was to manage was P2.
System Action:
Action fails.
User Action:
Contact your support representative.
Reason:
The filter with name DEFAULT has not been specified. The filter statements must always define a default filter.
System Action:
The free form statements are rejected.
User Action:
Define a filter with the name DEFAULT.
Reason:
The PPI server of type P1 has successfully started and initialized. The NCL ID of the process is P2 and the PPI queue being managed is P3.
System Action:
None.
User Action:
None.
Reason:
The PPI manager process P1 for P2 has encountered an unrecoverable error condition. The process will terminate and a new manager will be started. The associated error message is P3 and a full list of diagnostic details will be written to the log.
System Action:
The process is terminated and a new copy will be started.
User Action:
Contact your support representative.
Reason:
An unexpected file access error occurred. The file ID was P1, the file action was P2, the return code was P3, the error code was P4, and the key was P5.
System Action:
Processing continues, but the function being performed is aborted.
User Action:
Contact your system support representative.
Reason:
The dynamic registration manager for P2 type agents processed P1 records from the VFS.
System Action:
None.
User Action:
None.
Reason:
The internal control request P1 is invalid.
System Action:
The request is rejected.
User Action:
Enter a valid internal request.
Reason:
The filter, P2, has already specified a JOBNAME and SYSID combination that is the same as was encountered on line P1. The JOBNAME and SYSID combination must be unique for each filter. The incorrect filter specification starts on line P1.
System Action:
The free form statements are rejected.
User Action:
Change the JOBNAME and/or the SYSID on line P1, or change them for the filter P2.
Reason:
A PPI manager was unable to manage the PPI queue, P1 , because another program already had control of the queue. Only one receiver may control a given queue under PPI.
System Action:
The manager terminates in a FAILED state.
User Action:
Determine which program has control of the queue. If the PPI started task is the SSI, then use the SHOW PPIUSERS command to determine which task has control of the queue (note that the command must be issued from the region that is connected to the SSI). Either terminate that program or disable the function. If the queue is the SOLVxxxx queue, it indicates that more than one dynamic registration servers have been started on the same system. Disable one of them.
Reason:
A PPI manager was unable to manage the PPI queue P1 because it could not define itself as the PPI receiver for the queue. A previous message indicates the error codes received.
System Action:
The manager terminates in a failed state.
User Action:
Determine the reason the queue could not be defined and then restart the manager.
Reason:
This is a header message for a display of a PPIPROC processor for the PPI queue P1. Statistics for message processing will follow.
System Action:
None.
User Action:
None.
Reason:
This is a header message for a display of a PPIPROC processor. The JOBNAME column gives the name of the job which sent messages and the TOTAL MESSAGES RECEIVED column is the total number of messages received from that job.
System Action:
None.
User Action:
None.
Reason:
This is a detail message for a display of a PPIPROC processor. P1 is the JOBNAME of a job which sent messages to the PPIPROC and P2 is the total number of messages received from that job.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPIPROC processor. P1 is the total number of messages processed by the PPIPROC.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI manager process. P1 is the total number of messages received that were error messages from a PPI agent. These error messages include those sent by the agent via the PPI queue being managed and those sent by the agent via WTO. The errors are logged to the transient log for the PPI Manager Resource.
System Action:
None.
User Action:
Check the messages in the transient log.
Reason:
This is a summary message for a display of a PPI manager process. P1 is the total number of messages received that could not be mapped to the $RMXPPI map by Mapping Services and the total number of messages received that were not expected by the manager. For each invalid data buffer, a message is logged to the transient log of the PPI Manager Resource.
System Action:
None.
User Action:
Check the messages in the transient log.
Reason:
This is a summary message for a display of a PPI manager process. P1 is the total number of messages received that were discarded. Messages that are found on the managed queue at the time when the manager was initializing are discarded as well as messages remaining on the managed queue during deactivation (except for SOLVxxxx queue managers). Messages that are responses for solicited commands to an agent are discarded if the command issuer is no longer active (they are however still delivered to the unsolicited message filter for automation purposes).
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI manager process. P1 is the total number of records received off the PPI queue being managed.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI manager process. P1 is the total number of records queued to PPI receivers by the manager.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI Manager Process. P1 is the total number error return codes returned by PPI in response to various requests from the manager. Messages describing the errors are logged to the transient log of the PPI Manager Resource.
System Action:
None.
User Action:
Check the messages logged to the transient log.
Reason:
This is a summary message for a display of a PPI Manager Process. This message indicates the end of the display and no more messages will be written.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI Dynamic Registration processor. P1 is the total number of PPI manager processes started by this manager to manage other PPI queues.
System Action:
None.
User Action:
None.
Reason:
This is a header message for a display of a PPICMDSVR processor for the PPI queue P1. Statistics for commands and messages processed follow.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI Command Server processor. P1 is the total number of command requests received by the manager.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI Command Server processor. P1 is the total number of messages received that were responses from previously requested commands.
System Action:
None.
User Action:
None.
Reason:
This is a summary message for a display of a PPI Command Server processor. P1 is the total number of messages received that were responses from previously requested commands and that were successfully delivered to the command issuer.
System Action:
None.
User Action:
None.
Reason:
The internal control request to start the unsolicited message flow to PPI receiver ID P1 was rejected because the receiver ID specified was an invalid name.
System Action:
The request is rejected.
User Action:
Specify a valid PPI receiver ID or leave blank to use the default.
Reason:
The attempt to send a message to the screening table failed with feedback code P2 . The request was P1 , and P3 to P6 identify the job name, job ID, time, and text of the message being sent.
System Action:
Processing continues.
User Action:
Contact your local support representative.
Reason:
The PPO procedure encountered an error when trying to route a VTAM WTO message from the PPO interface to AOM.
System Action:
The message is not passed to AOM. The PPO procedure continues processing.
User Action:
The following table describes the feedback code and the corresponding action.
Code Description Action 32 Storage shortage Increase the region size for the task, or try later.
44 The AOM SSI does not exist Ensure that the AOM Sub-system Interface Identifier is defined and correctly specified in the OPSYSIDS parameter group of ICS.
56 No screening table loaded Ensure that initialization has completed successfully and that the OPSYSIDS parameter group has not had errors.
60 Screening table not active as above.
other Internal error Contact Technical Support.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
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 procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
The maximum length for a panel record is P3, and while attempting to save panel P1 it was calculated that its length exceeded this maximum.
System Action:
Request rejected
User Action:
Reduce the size of the panel and try to save again
Reason:
An error occurred while trying to save panel P1. The error return code is contained in P2 and the VSAM feedback is in P3.
System Action:
Request rejected
User Action:
Contact systems administrator
Reason:
The Resource Relationship service procedure was passed an invalid call type. The call type is P1 .
System Action:
Processing terminates.
User Action:
Contact the System Administrator.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact your local support representative.
Reason:
System image setting change.
System Action:
None.
User Action:
None.
Reason:
The LOCK value for this request was invalid.
System Action:
Process terminates in error.
User Action:
Contact your system administrator.
Reason:
The registration table function has ended in error.
System Action:
Process terminates in error.
User Action:
Contact your system administrator.
Reason:
The requested lock has been unsuccessful.
System Action:
Process terminates in error.
User Action:
Contact your system administrator.
Reason:
The Vartable name has changes for this SYSTEM/VERSION/CLASS.
System Action:
None.
User Action:
None.
Reason:
The value of P1 was changed from P2 to P3 for the P4 system image.
System Action:
None.
User Action:
None.
Reason:
The Domain ID for this remote system has changed.
System Action:
None.
User Action:
None.
Reason:
The image description for this remote system has changed.
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:
If multiple options specified in the selection list then the second option will be processed with the same panel sequence as the first.
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:
No resources of the indicated type were found.
P1 identifies the resource type.
P2 (optional) is a mask used to match against existing resources of the indicated type. The message indicates that no resources matched the supplied mask.
The message can indicate that a manager resource is required for this resource class or the templates might have been set up incorrectly.
Note: Monitor class resources must be owned by a manager resource. If you are trying to define a monitor class resource, it must be associated with a manager resource of the same product type.
System Action:
The selection list is not displayed.
User Action:
If P1 indicates that managers were not found, define a manager of the relevant class before redefining this resource.
To define the manager
If P1 indicates that templates were not found, it might indicate that the active template image needs to be changed.
To change the active template image
Reason:
No resource of the type identified by P1 added or found for the sysname and version specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
Process cancelled because resource class is not selected/specified.
System Action:
The request is rejected.
User Action:
Class must be selected to add resource definition.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
Requested process has been completed successfully.
System Action:
None.
User Action:
None.
Reason:
The record was not saved because no changes were made to the definition.
System Action:
None.
User Action:
None.
Reason:
Only one definition allowed to be defined to the system for class SPOOL, JES, EE and CSM.
System Action:
None.
User Action:
None.
Reason:
Resource P2 has been successfully added to Class P1 by a Cross Class Copy function.
System Action:
None.
User Action:
None.
Reason:
Resource P2 wasn't successfully added to Class P1 by a Cross Class Copy because a resource of that name already exists within the class.
System Action:
Request rejected.
User Action:
Use a different name.
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 requested Cross Class Copy Function was cancelled at the user's request.
System Action:
None
User Action:
None
Reason:
A scan has revealed that no resources in the system image identified by P1 were modelled using the template identified by P2.
System Action:
None.
User Action:
None.
Reason:
The template identified by P1 was applied to P2 resources in the system image identified by P3.
System Action:
None.
User Action:
None.
Reason:
Deletion of a resource which has owned resources was canceled by the user.
System Action:
None.
User Action:
None.
Reason:
A user canceled the request.
System Action:
None.
User Action:
None.
Reason:
You tried to move the P1 resource to the P3 local system image. However, the resource and the image do not have the same home system. You can move a resource from a shared image to a local image only if the resource and the local image have the same home system.
System Action:
The request is rejected.
User Action:
Do one of the following:
- If you want to move the resource to the P3 image, change the home system of the resource to match that of the image first.
- Move the resource to an image that has the same home system as the resource.
Reason:
You tried to move the P1 resource to the P3 shared system image. However, the resource's home system does not appear in the shared image's system affinity list. You can move a resource from a local image to a shared image only if the resource's home system appears in the shared image's affinity list.
System Action:
The request is rejected.
User Action:
Do one of the following:
- If you want to move the resource to the P3 image, change the home system of the resource to one in the image's system affinity list or include the resource's home system in the shared image's system affinity list.
- Move the resource to a different image, which has the home system of the resource in its system affinity list.
Reason:
You applied the P1 action to a class of resource for which the action is not valid.
System Action:
The request is rejected.
User Action:
None.
Reason:
The File Transfer Schedule P1 cannot be updated whilst ACTIVE.
System Action:
The request is rejected.
User Action:
You have the following options:
1) Wait for File Transfer Schedule termination and then update it.
or
2) Issue an "OFF" command against the File Transfer Schedule to terminate the schedule and then update it.
or (if applicable)
3) Use the "EAS" command against the File Transfer Schedule to temporarily extend the monitoring period.
Reason:
The default destination monitor group has been successfully set. All subsequent CG actions will use this monitor group as the default destination.
System Action:
None.
User Action:
None.
Reason:
The specified IP Node Monitor group does not exist in the database.
System Action:
None.
User Action:
Issue the primary command SETGRP ? to display a list of monitor groups.
Reason:
No selection was made from the IP Node Monitor Group selection list.
System Action:
None.
User Action:
None.
Reason:
The SETGRP command has been issued and the default destination monitor group has been successfully cleared.
System Action:
None.
User Action:
None.
Reason:
The SETGRP command has been issued to clear the default destination monitor group but no destination monitor group was set.
System Action:
None.
User Action:
Issue the command SETGRP groupname or alternatively, SETGRP ? , to display a selection list of monitor groups.
Reason:
The selected IP Node resource definition has been updated or moved to monitor group P1 .
System Action:
None.
User Action:
None.
Reason:
You try to save a newly defined resource with no template applied. The following options are available:
System Action:
None.
User Action:
When a resource is defined with no template applied, it is likely that the resource will not be monitored correctly. Either manually specify all relevant values in the succeeding definition panels or use a template to predefine values for selected fields.
To apply a template
The first panel appears.
A selectable list of templates appears.
The definition acquires the template values.
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:
You tried to access a class that does not exist in the knowledge base.
System Action:
The request is rejected.
User Action:
Use a valid class name.
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:
Resource definition to be created already exists in the database.
System Action:
The request is rejected.
User Action:
None.
Reason:
Sysname and Version specified is unknown to the system.
System Action:
The request is rejected.
User Action:
Use '?' to list a selection list of Sysname and Version known to system.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
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:
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:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The specified record was not found.
System Action:
The request is rejected.
User Action:
Check that the owner CDMGR has not been deleted. Review the values in the System Name, Version, and CDMGR Name fields. Correct any values in error.
Reason:
The name of the remote node being monitored by this CDMON resource cannot be the same name as this monitor's owning CDMGR.
System Action:
The request is rejected.
User Action:
Input a different remote node name, or change the owner name.
Reason:
You are changing the home system of a resource in a shared system image and if you proceed with it, relationships with other resources in local system images will be deleted. Only resources with the same home system can form relationships between local and shared system images.
System Action:
None.
User Action:
Either cancel the change, or save it and unlink all related local image resources.
Reason:
The File Transfer Schedule P1 cannot be updated whilst ACTIVE.
System Action:
The request is rejected.
User Action:
You have the following options:
1) Wait File Transfer Schedule termination and then update it.
or
2) Issue an "OFF" command against the File Transfer Schedule to terminate the schedule and then update it.
or (if applicable)
3) Use the "EAS" command against the File Transfer Schedule to temporarily extend the monitoring period.
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:
No resources were found in class P1 which began with supplied prefix P2 which could be displayed in a list for selection.
System Action:
None.
User Action:
None.
Reason:
No resources were found in class P1 whose name matches the supplied name, identified by P2.
System Action:
None.
User Action:
None.
Reason:
No availability map name has been specified and therefore no timer details can be displayed.
System Action:
The request is rejected.
User Action:
Timer list can only be actioned if resource has an availability map name specified.
Reason:
Request to display attached resources rejected because there is no attached resources to display.
System Action:
The request is rejected.
User Action:
None.
Reason:
Invalid character specified to display attached resources list.
System Action:
The request is rejected.
User Action:
Use '?' to display attached resources list.
Reason:
An invalid option specified
System Action:
The request is rejected.
User Action:
Specify Availability Map name or use '?' to select Availability Map which has already been defined to the system.
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:
There is no template found to be processed with the option specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
Template processing require resource name to replace resource name in the template, therefore resource name should exists before using template.
System Action:
The request is rejected.
User Action:
Specify resource name, retry process.
Reason:
Process name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
None.
Reason:
Message text to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
None.
Reason:
Field selected is unknown to the system, this is an error of the internal processing.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
A required field has been omitted.
System Action:
Field in error is highlighted.
User Action:
Enter value.
Reason:
Template specified has not been processed.
System Action:
The request is rejected.
User Action:
Specify M to merge, O to override, or R to reset, the resource definition with the template definition.
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 Containment Filter name was added to a resource definition but the resource is not a containment resource.
System Action:
The field is highlighted as in error.
User Action:
Either change the resource type to CONTAINMENT or erase the value in the Containment Filter field.
Reason:
The 'F' option was specified without a valid SNA Resource Group Filter name being present. 'F' is only valid if a valid Filter name has been entered.
System Action:
The field in error is highlighted.
User Action:
Specifiy a valid SNA Resource Group Filter name.
Reason:
An attempt was made to View the resources which passed a particular filter criterion but none were selected.
System Action:
None
User Action:
If this is not a desired result check the filter and modify it so that resources will be selected. View the filter again to check if the desired result is achieved.
Reason:
Operation mode of MANUAL is the only valid option for a remote FTSMGR
System Action:
Field in error is highlighted.
User Action:
Enter MANUAL as the Operation Mode
Reason:
The field, P1 , is not applicable when the type is P2 .
System Action:
The field in error is highlighted.
User Action:
Remove the value from field P1 .
Reason:
The field identified by P1 is a required field which has been omitted.
System Action:
Field in error is highlighted.
User Action:
Enter a valid value.
Reason:
The 'V' option was specified for a file filter type 'TGT','SRC','ID', or the 'E' option was specified for a file filter type 'CTL' .
System Action:
The request is rejected.
User Action:
Check the file filter type and select the appropriate action.
Reason:
You are deleting one or more status monitor messages and are asked to confirm the operation.
System Action:
None.
User Action:
To delete all the selected messages, press ENTER.
If you change your mind about deleting a message, clear the D beside it before you press ENTER. When you press ENTER, only those message with a D beside them are deleted.
Reason:
You cannot define a resource of the P1 type in a shared system image.
System Action:
The field in error is highlighted.
User Action:
Change the type to a valid value. If you have applied a template, delete the values in the Type and TemplateName fields, and then apply a template of the valid type by using the Reset action.
Reason:
You have successfully updated the SNMP host details record corresponding to this resource definition.
System Action:
None
User Action:
None
Reason:
You have canceled the update of the SNMP host details record corresponding to this resource definition. The SNMP host details record remains unchanged.
System Action:
None
User Action:
None
Reason:
A value of YES has been specified for Use SNMP?. YES is invalid for this resource type. SNMP support was introduced for DIRECTEXPRESS in z/OS 1.4 and EXPRESS in z/OS 1.6.
System Action:
The Use SNMP? field is highlighted.
User Action:
Change the Use SNMP? value to NO, or change the OSA type.
Reason:
When the Is Name Generic? field is set to YES, the Address Space Monitor Name must be no more than 7 characters long. The name is used as a mask, with a trailing '*' assumed.
System Action:
Address Space Monitor Name field is highlighted.
User Action:
Shorten the length of the name, or change Is Name Generic? to NO.
Reason:
The resource definition has Monitoring Status set to ACTIVE on panel 1; however, no monitoring attributes are selected.
System Action:
None.
User Action:
Press F10 (EditLst), then F4 (Add), and select attributes for this resource.
Reason:
The resource definition has Monitoring Status set to ACTIVE on panel 1, but no type of monitoring has yet been specified.
System Action:
None.
User Action:
Select the monitoring you want to perform using an 'A' or 'S' against one or more types on this panel.
Reason:
Another user is updating this definition.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
You did not specify the interface name. This field is required when the VIPA address is IPv6.
System Action:
The field is highlighted in error.
User Action:
Supply a value for interface name.
Reason:
When the Is Name Generic? field is set to YES, the Address Space Monitor Type must be NONE. Generic monitoring is not supported for the indicated type of address space resource.
System Action:
Is Name Generic? field is highlighted.
User Action:
Change the value to NO, or set Address Space Monitor Type to NONE.
Reason:
You did not specify fields required for address space port monitoring. Address space port monitoring attributes contain the suffix ByPort in its attribute name. When these attributes are selected, a port number and/or an associated stack name is required.
System Action:
The required fields are highlighted.
User Action:
Update the resource definition, adding port numbers and stack details, or remove all address space port monitoring attributes if they are not needed.
Reason:
As a result of your change to the TCP/IP Stack Type field, some previously active monitoring attributes are no longer applicable. P1 attributes have been removed.
System Action:
None.
User Action:
Press F8, and review the attributes.
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 Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
Vartable error.
System Action:
No further processing.
User Action:
None.
Reason:
As this resource exists in a remote region, an APPC conversation is required to process this log request. APPC function P1 has ended in error. P2 contains the return code, P3 the feedback code, and P4 the message describing the failure.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your 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:
As this resource exists in a remote region, an APPC conversation is required to process this log request. APPC function P1 has ended in error. P2 contains the return code, P3 the feedback code, and P4 the message describing the failure.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your system administrator.
Reason:
Vartable error.
System Action:
No further processing.
User Action:
None.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
Procedure in unexpected APPC "What Received" State.
System Action:
None.
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 $RMAVTEMP table is not available.
System Action:
No further processing.
User Action:
None.
Reason:
Vartable error.
System Action:
No further processing.
User Action:
None.
Reason:
The region cannot recognize the transaction request from a remote conversation partner.
System Action:
This transaction is not processed any further.
User Action:
Contact technical support.
Reason:
The status table function has ended in error.
System Action:
Processing continues.
User Action:
Contact technical support.
Reason:
An error has occurred in the APPC conversation used by the Shared Event Traffic Manager. This will cause loss of status table updates for remote resources in a shared system image.
System Action:
The region will retry the conversation.
User Action:
If the remote region is inactive, restart the remote region; otherwise, contact technical support.
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.
Reason:
Procedure $RMSEACX failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
Right and left parentheses were entered without any search information between them. This is an invalid situation.
System Action:
Field highlighted in error.
User Action:
Enter some search information between the parentheses.
Reason:
While specifying a search the field identified by P1 was not entered and is a required field.
System Action:
Field highlighted in error.
User Action:
Enter a value for the specified field.
Reason:
While defining a search the field highlighted as being in error only accepts the value identified by P1 as being valid.
System Action:
Field highlighted in error.
User Action:
Enter the valid value for the specified field.
Reason:
An unbalanced number of parentheses have been specified in the search expression. P1 parentheses were specified on the left and P2 parentheses were specified on the right. There must be an equal number of parentheses on the left and right.
System Action:
Field highlighted in error.
User Action:
Add or remove parentheses to balance them.
Reason:
There was an NDB error on the database P1 . The &NDBRC return code is P2 and the &NDBERRI error information is P3 .
System Action:
None.
User Action:
Refer to the NCL Guides for information on the return code.
Reason:
The field name P1 that you specified is not a valid field name.
System Action:
Field highlighted in error.
User Action:
Enter a valid field name or place a '?' in the field to get a list of valid field names.
Reason:
The line command P1 is an invalid line command. Valid line commands are: I - Insert a line D - Delete a line R - Repeat a line
System Action:
Field highlighted in error.
User Action:
Enter a valid line command.
Reason:
Procedure $RFSF00S has been invoked with an invalid value of P2 for keyword P1.
System Action:
Procedure is cancelled.
User Action:
As this procedure is only called interally, this message represents a serious error. Contact Technical Support immediately.
Reason:
An error occurred while performing a VSAM function, P1 , on the RAMSTAGE file. The value of &FILERC is returned in P2 and any error message is returned in P3 . If the error is an OPEN error and the file was being opened to write records to it, the region will be unlinked. This is done to maintain data integrity, as updates to the RAMDB cannot be propagated to linked regions.
System Action:
Procedure ends in error. Region may be unlinked.
User Action:
Try to determine the cause of the error and take any necessary steps to rectify it. Relink the region if required.
Reason:
A GET request has found no records for the specified ACBNAME.
System Action:
Procedure ends with Retcode 4.
User Action:
None.
Reason:
A write or delete request has failed due to the user's lack of authority. If the file was being opened to write records to it, the region will be unlinked. This is done to maintain data integrity, as updates to the RAMDB cannot be propagated to linked regions.
System Action:
Procedure ends with retcode 8. Region may be unlinked.
User Action:
As this procedure usually runs in background check the authority of the BSYS user, and update it if necessary. It may also be necessary to relink the region.
Reason:
A GET request did not find the record whose key is returned in P1.
System Action:
Procedure ends with Retcode 4.
User Action:
None.
Reason:
The request identified by P1 on the RAMSTAGE file failed with FILERC P2 FeedBack P3 and, optionally Message P4. If the request was a PUT, the region will be unlinked. This is done to maintain data integrity, as updates cannot be propagated to linked systems.
System Action:
Procedure ends. Region may be unlinked.
User Action:
Rectify problems causing RAMSTAGE errors and relink the system.
Reason:
An internal LOCK request of type P1 has failed with a P2 return code, and P3 feedback code. P4 is the lock text from the held lock and P5 is the name of the lock in the form Primary Name.Minor Name.
System Action:
The lock request is retried every 30 seconds, until successful.
User Action:
If this message logs repeatedly for an extended period of time, it may indicate that a procedure has locked the record and is now hung and is not releasing the record, thereby preventing other procedures from accessing the record. If this happens, contact CA Technical Support.
Reason:
A LOCK request was made with the invalid P1 type.
System Action:
Processing terminates.
User Action:
Contact your support representative.
Reason:
One or more records have been deleted from the RAMSTAGE file for the key identified by P1.
System Action:
None
User Action:
None
Reason:
This is the first of a series of three messages issued in a broadcast to indicate that there has been an error on the staging file which will cause the system to be unlinked. The region will be unlinked to maintain data integrity, as updates to the RAMDB cannot be propagated to linked regions.
P1 is the NMID of the Region.
P2 is the Date.
P3 is the Time.
System Action:
The region is unlinked.
User Action:
Determine and correct any problems and relink the region.
Reason:
The request identified by P1 for file key P2 on the RAMSTAGE file failed with FILERC P3 FeedBack P4 . The request is retried five times before a LOCK is taken to prevent multiple procedures retrying simultaneously. The first procedure to get the lock continues to retry while others wait. P5 identifies current retry count.
System Action:
The first procedure continues to retry while subsequent procedures wait on a LOCK request.
User Action:
None.
Reason:
This is the third of a series of three messages issued in a broadcast to indicate that there has been an error on the staging file which will cause the system to be unlinked. The region will be unlinked to maintain data integrity, as updates to the RAMDB cannot be propagated to linked regions.
P1 is the NMID of the Region.
System Action:
The region is unlinked.
User Action:
Determine and correct any problems and relink the region.
Reason:
An event was simulated as specified but no results were generated. This is because the event has no hits/misses as per the event controls.
System Action:
None.
User Action:
None.
Reason:
An event was simulated as specified and P1 result lines generated.
System Action:
None.
User Action:
None.
Reason:
An attempt to simulate an event failed because the AOMALERT failed. The feedback code returned from the AOMALERT was P1.
System Action:
Event is not simulated. Processing terminates in error.
User Action:
The following table describes the feedback code and the corresponding action:
|
Code |
Description |
Action |
|---|---|---|
|
32 |
Storage shortage |
Increase the region size for the task or try later. |
|
44 |
The AOM SSI does not exist |
Ensure that the AOM Sub-system Interface Identifier is defined and correctly specified in the OPSYSIDS parameter group. |
|
56 |
No screening table loaded |
Ensure that initialization completed successfully and that the OPSYSIDS parameter group has not had errors. |
|
60 |
Screening table not active |
As above. |
|
other |
Internal error |
Contact Technical Support. |
Reason:
An invalid value for the keyword parameter P1 was passed. The invalid value was P2.
System Action:
Processing is terminated.
User Action:
Contact your systems administrator or Technical Support.
Reason:
The selected result line was not generated as part of a hit of a database entity that can be displayed. Essentially there is nothing to display.
System Action:
Request is rejected.
User Action:
None.
Reason:
The specified action P1 is not valid for the ALL command.
System Action:
Request is rejected.
User Action:
Specify an action that is valid for the ALL command.
Reason:
An invalid value for the keyword parameter P1 was passed. The invalid value was P2.
System Action:
Processing is terminated.
User Action:
Contact your systems administrator or Technical Support.
Reason:
An invalid command was entered. The invalid command was P1.
System Action:
The command is rejected.
User Action:
Specify a valid command.
Reason:
An invalid value was entered for the field P1. This field must contain P2.
System Action:
The field is set in error.
User Action:
Specify a valid value for P1.
Reason:
One or more required fields were not specified.
System Action:
The field(s) are set in error.
User Action:
Specify valid values for the fields set in error.
Reason:
The selected simulation event was not found in the simulation table. This occurs if another user deletes the event after you displayed your list, and you then select the deleted event.
System Action:
Request is rejected.
User Action:
Create a new simulation event.
Reason:
The selected simulation event is already being updated by user P1.
System Action:
Request is rejected.
User Action:
Try later.
Reason:
An invalid value for the keyword parameter P1 was passed. The invalid value was P2.
System Action:
Processing is terminated.
User Action:
Contact your systems administrator or Technical Support.
Reason:
The selected simulation event was not found in the simulation table. This occurs if another user deletes the event after you displayed your list, and you then select the deleted event.
System Action:
Request is rejected.
User Action:
Create a new simulation event.
Reason:
The selected simulation event is already being updated by user P1.
System Action:
Request is rejected.
User Action:
Try later.
Reason:
The specified action P1 is not valid for the ALL command.
System Action:
Request is rejected.
User Action:
Specify an action that is valid for the ALL command.
Reason:
Event simulation is not active.
System Action:
Request is rejected.
User Action:
If you require event simulation, activate it as follows:
If the event simulation is still not available, a possible cause is a memory problem. Such a problem is indicated by a message, RMINWI42, in the initialization log. Read the message help for corrective actions.
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:
A vartable error occurred while performing function P1 on vartable with name P2. The feedback code was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact your local support representative.
Reason:
The calendar matrix for year P1 was not defined.
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:
There were P1 dates that were satisified by the Calendar Criteria P2.
System Action:
None.
User Action:
None.
Reason:
The P1 command for the P2 resource was rejected because of the reason,
P3 .
System Action:
The command was rejected.
User Action:
Use P3 to determine your next action.
Reason:
You did not make a selection in the previously displayed list.
System Action:
None.
User Action:
None.
Reason:
An alert was generated for the <MSGID> message.
System Action:
None.
User Action:
None.
Reason:
A command was entered for a SYSPLX class resource, and control has been passed to the LPAR Display Facility (LDF) for further processing.
System Action:
None.
User Action:
Enter the indicated line command beside the desired LPAR to continue your processing.
Reason:
The selected resource does not authorize the CDC command.
System Action:
The command is not processed.
User Action:
If you are authorized to update resource definitions, proceed as follows:
Step 1. Enter DB beside the resource.
Step 2. Select the Couple Dataset Automation panel.
Step 3. Specify YES in the "Allow Operator to Reset to Defined Primary and Alternate Couple Datasets?" field.
Step 4. Press F3 (File) to save the change.
Step 5. Enter CDC beside the updated resource definition.
Reason:
The cross-system extended services (XES) resource has no associated display command.
System Action:
None.
User Action:
None.
Reason:
This message asks you to confirm the request to reset the usage of the couple datasets for the selected sysplex resource. The reset operation starts when you press F6 (Action).
System Action:
None.
User Action:
Press F6 (Action) to confirm the request to reset the couple dataset usage, or press F12 (Cancel) to cancel the request.
Reason:
You canceled the request to reset the couple data set usage for the indicated sysplex resource.
System Action:
None.
User Action:
None.
Reason:
The couple data sets were reset to the ones specified in the sysplex resource definition successfully.
System Action:
None.
User Action:
None.
Reason:
Your request to reset the couple data set usage for the indicated sysplex resource failed.
System Action:
The reset failed.
User Action:
See the logs to determine why the reset did not proceed. Retry the operation, or try to reset the couple data set usage by issuing SETXCF commands.
Reason:
This message shows the progress of resetting the usage of couple data sets. P1 is the text of the message.
System Action:
None.
User Action:
None.
Reason:
The P1 command is not valid for sysplex resources of the P2 type.
System Action:
None.
User Action:
None.
Reason:
The currently allocated couple data sets for the indicated sysplex resource match the data sets assigned in the resource definition. No reset is required.
System Action:
None.
User Action:
None.
Reason:
This message shows the command issued as part of the operation to reset couple data set usage.
P1 is the command.
P2 is the region in which the command was issued.
System Action:
The command is passed to the system for processing.
User Action:
None.
Reason:
You issued a CDC command against a sysplex resource and confirmed the request. The requested operation timed out and stopped because a response was not received within 90 seconds.
System Action:
Couple data set usage is not reset. The displayed panel shows the current allocation.
User Action:
See the logs to determine why the reset did not proceed. Retry the operation or try to reset the couple data set usage by issuing SETXCF commands.
Reason:
You issued a CDC command against a sysplex resource and confirmed the request. However, another user, P1 , is already resetting the couple data set usage for that resource.
System Action:
Your request to reset the couple data set usage for the resource is not processed.
User Action:
None.
Reason:
A WTOR has been auto-replied as part of sysplex couple data set reset. This message is issued as part of the CDC command used to reset sysplex couple data sets to their resource definition default settings. P1 is the WTOR text.
System Action:
None.
Note: Auto-replies to sysplex WTORs has been enabled through setting the "Allow Operator to Reset to Defined Primary and Alternate Couple Datasets?" to "YES".
User Action:
None.
Reason:
You cannot enter commands on panels processing the CDC command. Sysplex couple data set control is deemed too critical to allow command entry.
System Action:
Your command is not processed.
User Action:
Use another window to issue your command.
Reason:
The operation to reset the usage of the P1 couple data sets is in progress.
System Action:
The usage of the data sets is being reset to the settings in the resource definition.
User Action:
None.
Reason:
No log records have been recorded yet.
System Action:
None.
User Action:
None.
Reason:
The definition for the selected resource does not contain full couple data set information to support the CDC command.
System Action:
The command is not processed.
User Action:
If you wish to use the CDC command, ensure that couple data set information is specified in the sysplex resource definition.
Reason:
You can issue the P1 command from focal point regions only because subordinate regions have limited cross-system visibility.
System Action:
None.
User Action:
Retry the command from a focal point region.
Reason:
The P1 function key is not supported on this panel.
System Action:
None.
User Action:
None.
Reason:
The P1 command is not valid for a SYSPLX-class resource.
System Action:
The command is rejected.
User Action:
None.
Reason:
You tried to add a sysplex resource definition that already exists in the sysplex system image. You can add one definition only for each type of sysplex resource. For an ETR or GRS resource, you can add a definition for one of the variant types only.
System Action:
The request is rejected.
User Action:
None.
Reason:
You entered the LDF command in a region that does not include the S:SYSPLEX feature.
System Action:
The command is not processed.
User Action:
Enter the command in a region that includes the S:SYSPLEX feature. To check whether a region includes the feature, enter CMD STATUS and then press Enter twice. The included features are returned in the N11414 messages.
Reason:
You have entered a command for a SYSPLX class resource; however, the command must be issued using the LDF display facility.
System Action:
None.
User Action:
Enter the indicated line command from the Call LPAR Display Facility for your processing.
Reason:
Invalid parameters were passed to procedure $RMST00L.
System Action:
The procedure terminates.
User Action:
Contact your local support representative.
Reason:
An attempt by the Status Monitor to allocate its internal tables has failed, probably due to insufficient storage.
System Action:
The Monitor terminates.
User Action:
Contact your local support representative.
Reason:
This is an informational message issued by the Status Monitor indicating that some change has occurred to the resource identified by P2, which is not in the current window. P1 is either ABOVE or BELOW and indicates the direction in which the change is to be found.
System Action:
None.
User Action:
If it is desired to see the change which has occurred, scroll the list in the indicated direction.
Reason:
An invalid parameter with value P2 was supplied for the command P1.
P3 may optionally contain information about the correct values.
System Action:
None.
User Action:
Reenter the command with the correct parameter.
Reason:
The requested Filter was not found, so the Status Monitor Filter has been reset.
System Action:
None.
User Action:
Define a new Status Monitor Filter if you so desire.
Reason:
The requested View was not found, so the Status Monitor View has been reset.
System Action:
None.
User Action:
Define a new Status Monitor View if you so desire.
Reason:
The Specified Profile element P1 has been set to the displayed value P2.
System Action:
None.
User Action:
The Status Monitor will use the new value for its displays.
Reason:
The Specified Profile Element P1 was not changed from its previous value P2 and a redisplay was not done.
System Action:
None
User Action:
None
Reason:
The status monitor is building the list of resources to be monitored and sorting them into the order indicated in your user profile.
System Action:
None.
User Action:
None.
Reason:
The heartbeat value in the resource definition was less than the minimum global value. The heartbeat value is increased automatically to P1.
System Action:
The heartbeat value is increased automatically to the minimum value.
User Action:
None.
Reason:
The Status Monitor cannot support the LOCATE command due to the complex nature of its key structures and the ability to SORT the list on up to three of eleven possible fields. Hence the FIND command should be used to position the cursor on the required resource, state etc.
System Action:
Request is rejected.
User Action:
Use the FIND command as an alternative.
Reason:
The command identified by P1 was issued for execution.
System Action:
None.
User Action:
None.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
FORMAT list definition not defined or the information in the list cache was incorrect. The information in the list cache can become incorrect due to list definitions being added to the MODS file by using the Definition Utility move or copy functions. The Definition Utility does not update the list cache when moving or copying list definitions. FILTER requested was not found, so the Resource Monitor filter has been reset.
System Action:
The request is rejected.
User Action:
If the list is defined on the MODS file reset the list cache (option R on the CAS : List Definition Menu) and retry the request. Otherwise specify a list previously defined and retry. FILTER - Define a new Resource Monitor Filter if you so desire.
Reason:
The Status Monitor was in the P2 View, which does not support the P1 command.
System Action:
None.
User Action:
None.
Reason:
This is an informational message indicating that a system load for the System Image identified by P1 and P2 has begun.
System Action:
The Status Table for the nominated system image will be allocated and the resources for that system image will be loaded into it.
User Action:
None.
Reason:
The system load of the System/Version identifed by P1 and P2 has been completed successfully, resulting in P3 resources being loaded into a Status Table.
System Action:
None.
User Action:
None.
Reason:
This is a warning message issued during a system load if an error occurs trying to retrieve the list of resources for a particular class. The system image identified by P1 and P2 failed to load, returning a return code from the database scan of P3 while any error message returned will be contained in P4.
System Action:
None.
User Action:
None.
Reason:
This is an informational message issued during system load which indicates that a heartbeat timer with timer id P1 has been set for the resource identified by P2 with an interval of P3.
System Action:
None.
User Action:
None.
Reason:
During system load an attempt was made to gain exclusive control of the Status Table for the class identified by P1 which resulted in a return code of P2.
System Action:
System load is abandoned.
User Action:
Check if another process has an exclusive lock on the required Status Table. If so, either wait until it has completed or flush it, and then retry the system load.
Reason:
This is an informational message indicating that a system load for the System/Version identified by P1 and P2 has begun.
System Action:
The system load will proceed.
User Action:
None.
Reason:
The system load has completed successfully, resulting in P1 resources being loaded from P2 system images.
System Action:
None.
User Action:
None.
Reason:
This is an informational message issued during system startup, indicating that any dynamic resources defined in the system image being loaded will be deleted.
System Action:
Dynamic resources will be deleted.
User Action:
None.
Reason:
The dynamic resource identified by P1 was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
An error occurred attempting to delete the dynamic resource identified by P1. The return code and error message received are contained in P2 and P3 respectively.
System Action:
None.
User Action:
None.
Reason:
Informational message indicating the deletion of P1 dynamic resources.
System Action:
None.
User Action:
None.
Reason:
While loading the Status Tables during system startup a relationship was found in which the resource identifed by P1 appears more than once in a conflicting parent-child scenario. 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:
System load is abandoned.
User Action:
Find the relationship which caused the error and correct it, then re-load the system image.
Reason:
The P1(P2) resource in the P3 P4 system image was already loaded from another system image, identified in a following message, RMST0064.
System Action:
The resource is not loaded again.
User Action:
Review the system images and, if appropriate, remove the duplication.
Reason:
The P1(P2) resource was loaded from the P3 P4 system image. This message follows the RMST0063 message.
System Action:
None.
User Action:
None.
Reason:
The P1(P2) resource was unloaded from the local system image and reloaded in the P3 P4 shared system image.
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:
Based on the information supplied we are unable to determine the logical status.
System Action:
Procedure terminates in error.
User Action:
Contact your system administrator.
Reason:
We have been unable to obtain the requested lock.
System Action:
Procedure terminates in error.
User Action:
Contact your system administrator.
Reason:
An invalid call was made to procedure $RMSTMS.
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
Procedure $RMSTMS received an unexpected return code from a lock request.
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
Procedure $RMSTMS encountered an invalid lock request.
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
Procedure $RMSTMS encountered an unexpected feedback code when attempting to access the status table.
System Action:
The request fails.
User Action:
If the error occurred on the web interface from a bookmarked URL it most likely means that the resource in the URL is no longer defined. If this is NOT the case then contact Technical Support.
Reason:
Procedure $RMSTMS encountered an unexpected feedback code when evaluating the normalized state of a resource.
System Action:
The request fails.
User Action:
If the error occurred on the web interface from a bookmarked URL it most likely means that the resource in the URL is no longer defined. If this is NOT the case then contact Technical Support.
Reason:
The actual state of a resource was not changed because the transition from status P1 to status P2 is not permitted.
System Action:
The resource's actual status is not changed.
User Action:
None.
Reason:
Procedure $RMSTMS encountered an error when retrieving a record from the status table.
System Action:
The request fails.
User Action:
If the error occurred on the web interface from a bookmarked URL it most likely means that the resource in the URL is no longer defined. If this is NOT the case then contact Technical Support.
Reason:
A change to the ASID field value in a resource definition was noted in the status table.
System Action:
None.
User Action:
None.
Reason:
A change to the automation mode setting in a resource definition was noted in the status table.
System Action:
None.
User Action:
None.
Reason:
The Mode Override Flag for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Desired State for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Desired State Override Flag for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Automation State for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Degradation State for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Failure Flag for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Extended Display for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Extended Display Attribute for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Filter Keyword Field for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
A Transferable Keyword Field for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Actual State for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Availability Map Mode for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
Procedure $RMSTMS could not determine the name of the internal status table.
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
The 'Tree Inactivate' Flag for a resource was changed.
System Action:
None.
User Action:
None.
Reason:
The Current Mode setting for the resource is P1.
System Action:
None.
User Action:
None.
Reason:
The current Desired State setting for the resource is P1.
System Action:
None.
User Action:
None.
Reason:
The status table field identified by P1 has been reset by the receipt of a request to set the Actual State of the resource to the value identified by P2.
System Action:
None.
User Action:
None.
Reason:
The Service Override setting for the resource was changed.
System Action:
None.
User Action:
None.
Reason:
This message indicates that an attempt to set a resource's Extended Display, identified by P1, with a severity of P2, was unsuccessful because an extended display, identified by P3, was already set and had a higher severity of P4.
System Action:
None.
User Action:
None.
Reason:
The Monitor Status for a resource was changed from P1 to P2 .
System Action:
None.
User Action:
None.
Reason:
This message follows RMSTMS53 and describes the reason for the change in Monitor Status.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword was P1 and the invalid value was P2.
System Action:
The request is rejected.
User Action:
Correct the parameters and retry the request.
Reason:
Invalid keyword parameters were specified. The parameters must be in Keyword format (ie. keyword=value ... ). P1 is the specified parameters.
System Action:
Request is rejected.
User Action:
Correct the parameters ensuring that they are in keyword format. Use quotes (either/both double and single) if values contain blanks or quotes.
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:
The transaction request from remote conversation partner is not recognized.
System Action:
This transaction is not processed any further.
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:
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:
The database function identified by P1 on the database identified by P2 for the object identified by P3 failed with a return code of P4 and a SYSMSG of P5.
System Action:
APPC conversation ends.
User Action:
Contact System Administrator.
Reason:
Linking a region into a multi-system network requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminated in error. The regions are not linked. The RAMDB on the receiving system is in an indeterminate state.
User Action:
Determine whether the remote system is still available. If the system is available, retry the Synchronize function.
Reason:
The procedure received an unexpected response from APPC.
System Action:
None.
User Action:
Contact your Systems Administrator.
Reason:
The database function has ended in error.
System Action:
If the return code is 0 or 4, processing continues. If the return code is greater than 4, the database function terminates in error.
User Action:
Contact your Systems Administrator.
Reason:
All the data from system P1, for the databases listed in P2, will be transmitted to the local region and replace any existing data, thereby synchronizing the databases on the two systems.
If the selected database is RAMDBVO , then only the link records from the remote system are synchronized.
System Action:
None.
User Action:
None.
Reason:
The multi-system link from the remote P1 region has ended.
P2 contains the return code, and P3 the message describing its success or failure.
System Action:
None.
User Action:
None.
Reason:
Database Sync summary lines.
System Action:
None.
User Action:
None.
Reason:
The remote process of the transmission facility terminated abnormally and processing could not continue.
System Action:
Database synchronization terminates.
User Action:
Review the messages on the activity log in the system from which the database was being synchronized to determine the cause of the error. When the problem has been corrected, rerun the database synchronization utility.
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 your Systems Administrator.
Reason:
An error has been encountered by the remote APPC conversation partner.
System Action:
Processing continues.
User Action:
Contact your Systems Administrator.
Reason:
An invalid sequence of chained record segments has been received.
System Action:
This synchronize fails.
User Action:
Contact your Systems Administrator.
Reason:
Attempt has been made to clear the Staging File for this system.
System Action:
Informational only.
User Action:
None.
Reason:
Multi-system link encountered an unexpected return or feedback code from an &LOCK verb.
System Action:
The multi-system link request fails.
User Action:
Contact your Systems Administrator.
Reason:
An error was encountered when attempting to access a 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:
Multi-system link terminates.
User Action:
Contact your Systems Administrator.
Reason:
A multi-system link request was rejected because another database administration task was already in progress. P1 is the task number and P2 is the ACB from which the task was initiated.
System Action:
The request is rejected.
User Action:
View the administration task log for the progress of any other tasks and wait until they are completed before retrying.
Reason:
Multi-system link completed but one or more records were not processed successfully. The database has not been completely replicated.
System Action:
None.
User Action:
The database is treated as complete and is available for use but the errors must be rectified. Contact Technical Support.
Reason:
The ACB name selected for a multi-system link operation was not valid or was not allowed. P2 is the reason. Possible values are:
SAME NAME the selected ACB name is the same as this region's ACB name.
INCOMPATIBLE VERSION the version of procedure $RMSY02S on the remote region appears to be incompatible with the version of $RMSY01S on this region. This may be due to required maintenance not being applied.
System Action:
The multi-system link request is rejected.
User Action:
Select a valid ACB name and retry, or ensure that the version of code on the remote region is correct, and any maintenance required, has been applied.
Reason:
An attempt to perform a multi-system link with the specified ACB was rejected because the region associated with the ACB is not running an Automation Services product.
System Action:
The multi-system link request is rejected.
User Action:
None.
Reason:
The multi-system link procedure is in progress and requires exclusive access to the database. The indicated NCL procedure was accessing the database and therefore will be terminated to allow the multi-system link procedure to continue.
System Action:
The indicated NCL procedures is terminated.
User Action:
None.
Reason:
A request was made to link the region with another automation region but the two regions are already linked.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to link two automation regions was rejected because the BSYS user ID of one or more of the regions that the target region is being connected to is not defined in the source region and the requesting user does not have UAMS Maintenance authority.
System Action:
The synchronization request is rejected.
User Action:
If the user requesting the multi-system link is authorized to perform UAMS maintenance functions on all the regions that will be connected, the required user IDs will be created automatically. Otherwise, you must define the BSYS user of the target region manually in each region that it will be connected to and define the BSYS user IDs of all regions that will be connected on the target region before linking the regions.
Reason:
The APPC conversation with a remote system timed out while waiting to receive data.
System Action:
The multi-system link request is rejected.
User Action:
If the reason for the timeout is not apparent, refer to the activity log on the remote region for more information.
Reason:
A request was made to perform a multi-system link with another system but a required link record was not found in the RAMDB. The record is for ACBNAME P1. The NDB return code was P3 and the error indicator was P4. The RID for the record expected was P2.
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
A multi-system link request requires the establishment of an APPC conversation. An APPC function has ended in error.
System Action:
Processing terminates in error.
User Action:
Determine whether the remote system is still available. Contact your Systems Administrator.
Reason:
Attempt has been made to clear the Staging File for this system.
System Action:
Informational only.
User Action:
None.
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 your Systems Administrator.
Reason:
The remote process of the transmission facility terminated abnormally and processing could not continue.
System Action:
Multi-system link request terminates.
User Action:
Review the messages on the activity log in the system to which this region was being linked to determine the cause of the error. When the problem has been corrected, rerun the multi-system link utility.
Reason:
This is an informational message about the status of a multi-system link request from a remote region. P1 is the ACB name of the region and P2 is either STARTED or ENDED.
System Action:
None.
User Action:
None.
Reason:
A multi-system link request was rejected because another database administration task was already in progress. P1 is the task number and P2 is ACB from which the task was initiated.
System Action:
The request is rejected.
User Action:
View the administration task log for the progress of any other tasks and wait until they are completed before retrying.
Reason:
A request to link two automation regions was rejected because the BSYS user ID of the target region was not registered in the UAMS file of the source region and the requesting user does not have UAMS Maintenance authority.
System Action:
The multi-system link request is rejected.
User Action:
If the user requesting the multi-system link is authorized to perform UAMS maintenance functions on all the regions that will be connected, the required user IDs will be created automatically. Otherwise, you must define the BSYS user of the target region manually in each region that it will be connected to and define the BSYS user IDs of all the regions that will be connected on the target region before performing the multi-system link.
Reason:
A new region is being linked by the multi-system link process and its BSYS user ID must be added to the UAMS file in each linked region. A request to add the user ID to a linked region failed because the linked region was not running or because the link to this region was not active.
System Action:
Multi-system link continues.
User Action:
If the BSYS user for the newly linked region is not present on any of the existing linked regions, it must be added manually before the regions can communicate.
Reason:
A new region is being linked using the multi-system link process. The attempt has been rejected for the reason given in P1 . Possible values of P1 are:
PRODUCT SET MISMATCH When you are performing a linking operation, the remote region must be configured with an appropriate product set. If you are linking a region as a subordinate, the product set in the subordinate region must be a subset of the remote region's product set. If you are linking a region as a focal point, or in Migration Mode, then the product sets in the regions being linked must match exactly.
xxxxxxx IS A SUBORDINATE SYSTEM When you are performing a linking operation, the remote region must be a focal point.
SYSPLEX REGION ALREADY ON xxxxxxxx You cannot link OPSOS licensed regions on the same system. The OPSOS product name key is specified in the RUNSYSIN member for the region.
ALREADY LINKED IN MIGRATION MODE You cannot link a region in Migration Mode if it is already linked in Migration Mode to another region.
SAME SYSTEM IMAGE LOADED ON xxxxxxxx You cannot link in Migration Mode if the system image name currently loaded on this region is the same as the the system image name loaded on a region in the multi-system network you are linking to.
SYSTEM IMAGE NAME ALREADY IN USE The name chosen as the system image name for the subordinate region has already been chosen by another subordinate region, or it matches an image currently loaded on a linked focal point region.
DUPLICATE DOMAIN ID ON xxxxxxxx The domain ID of the region being linked is the same as that of the region (xxxxxxxx) which is already linked into the multi-system network.
P2 REGION P3 IS UNREACHABLE The network you were linking to has a region that cannot be communicated with using the specified connection medium. P2 is the role of the remote region, and P3 is its primary name or ACB name. In a multi-system environment, a region must be able to communicate with all focal point regions.
System Action:
The multi-system link operation is rejected.
User Action:
If appropriate, identify the regions preventing the multi-system link and unlink the regions.
For P2 REGION P3 IS UNREACHABLE, specify a communication access method that is used by all the linked focal point regions.
Reason:
A request was made to perform a multi-system link with another system but a required link record was not found in the RAMDB. The record is for ACBNAME P1.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
The P1 region tried to perform a multi-system link, but it uses an earlier version of the product that has an incompatible database format.
System Action:
The multi-system link request is rejected.
User Action:
None.
Reason:
The P1 object could not be transmitted. The most likely cause is if a definition exceeds the maximum allowable size of 32 KB, as indicated by ZMDORC(8) and ZMDOFDBK(2).
System Action:
The multi-system link request fails.
User Action:
Update the P1 definition on the remote system to reduce its size, then retry the multi- system link.
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 Image Sync command 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 Systems Administrator.
Reason:
The procedure received an unexpected response from APPC.
System Action:
None.
User Action:
Contact your Systems 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 your Systems 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 your Systems Administrator.
Reason:
The Image Transmit for this system/version/class has commenced.
System Action:
None.
User Action:
None.
Reason:
Transmission of the indicated system image has completed. If the RC value is non-zero, the transmission completed unsuccessfully and SYSMSG contains the reason.
System Action:
None.
User Action:
If the transmission completed unsuccessfully, see the Help for the message in SYSMSG. When the problem has been corrected, retransmit the image.
Reason:
Image Sync summary lines.
System Action:
None.
User Action:
None.
Reason:
Tranmit informational message.
System Action:
None.
User Action:
None.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A transmit image or component command cannot be performed between regions that are linked and have their knowledge bases synchronized.
System Action:
The command is rejected.
User Action:
None.
Reason:
You cannot transmit a system image to a remote region in which that image is active.
System Action:
The request is rejected.
User Action:
If you wish to transmit this image to the remote region, you must first load a different image in that remote region.
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 database synchonisation request fails.
User Action:
Contact your Systems Administrator.
Reason:
The remote process of the transmission facility terminated abnormally and processing could not continue.
System Action:
Database synchronization terminates.
User Action:
Review the messages on the activity log in the system from which the database was being synchronized to determine the cause of the error. When the problem has been corrected, rerun the database synchronization utility.
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 your Systems Administrator.
Reason:
An image transmission request was rejected because another database administration task was already in progress. P1 is the task number and P2 is ACB from which the task was initiated.
System Action:
The request is rejected.
User Action:
View the administration task log for the progress of any other tasks and wait until they are completed before retrying.
Reason:
A system image was transmitted to a remote region but one or more records were not transmitted successfully.
System Action:
None.
User Action:
View the activity log to determine the cause of the errors, correct, and then re-transmit the system image.
Reason:
The File Transfer Ruleset you have selected has the same name as the active File Transfer Ruleset on the remote system. You cannot replace the active ruleset.
System Action:
The command is rejected.
User Action:
None.
Reason:
An action for a GENALERT macro is not in the knowledge base. The macro is in a process with the object ID P2 that is a concatenation of the following:
- Image name
- Image version
- 71 (class number for process definitions)
- Process name
System Action:
The process is transmitted without the action record.
User Action:
Note the process, and update it to recreate the missing action.
Reason:
The P1 object could not be transmitted. The most likely cause is if a definition exceeds the maximum allowable size of 32 KB, as indicated by ZMDORC(8) and ZMDOFDBK(2).
System Action:
The object is not transmitted.
User Action:
Update the P1 defintion to reduce its size.
Reason:
An attempt was made (due to a tranmission mode of REPLACE) to RESET the ICOPANL dataset by deleting all the records within it. This failed with the FILERC identified by P1 and the VSAMFDBK identified by P2.
System Action:
Processing terminated in error.
User Action:
Attempt to determine why the RESET of the ICOPANL dataset failed. Contact your Systems Administrator.
Reason:
A Image Sync command 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 Systems Administrator.
Reason:
Procedure in unexpected APPC "What Received" State.
System Action:
None.
User Action:
Contact your Systems Administrator.
Reason:
A database error has occurred attempting to perform function P1. The database is P2 , the record identifier is P3 , and the return code received was P4.
P5 is the error message, if one was returned.
System Action:
Processing continues. The record(s) in error are not written to the database.
User Action:
Attempt to ascertain why the record(s) were not written. Correct the problem and retry.
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 your Systems Administrator.
Reason:
An error has been encountered by the remote APPC conversation partner.
System Action:
Processing continues.
User Action:
Contact your Systems Administrator.
Reason:
A transmit image or component command cannot be performed between regions that are linked and have their knowledge bases synchronized.
System Action:
The command is rejected.
User Action:
None.
Reason:
The active system image cannot be overridden by a Transmit Image command. The system image you have selected is the active system image on system P1.
System Action:
The command is rejected.
User Action:
None.
Reason:
A database synchronisation request was rejected because another database administration task was already in progress. P1 is the task number and P2 is ACB from which the task was initiated.
System Action:
The request is rejected.
User Action:
View the administration task log for the progress of any other tasks and wait until they are completed before retrying.
Reason:
The ACB name selected for transmitting a system image was not valid or was not allowed.
System Action:
The database synchronisation request is rejected.
User Action:
Select a valid ACB name and retry.
Reason:
The Transmit Image option has been issued to transmit an image to system P1. The request has been rejected because P1 is a subordinate system, and is restricted to system name P2.
System Action:
The request is rejected.
User Action:
None.
Reason:
The Transmit Image option has been issued to transmit a service image. The request has been rejected because the selected destination is a subordinate region, and does not support services.
System Action:
The request is rejected.
User Action:
None.
Reason:
A Transmit File Transfer Ruleset from system P1 has been rejected. The File Transfer Ruleset being tranmitted has the same name as the active File Transfer Ruleset on the target region.
System Action:
The command is rejected.
User Action:
None.
Reason:
A Transmit Ruleset from system P1 has been rejected. The Ruleset being tranmitted has the same name as an active/loaded Ruleset on the target region.
System Action:
The command is rejected.
User Action:
None.
Reason:
An invalid sequence of chained record segments has been received.
System Action:
This record is not transmitted.
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 elements of the type described by P1 were found in the database.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to unselect the component described by P1 which had not previously been selected.
System Action:
Request rejected.
User Action:
None.
Reason:
You have not selected any elements from the list presented.
System Action:
None.
User Action:
Select elements from the list and try again.
Reason:
An attempt was made to select the element described by P1 which had previously been selected.
System Action:
Request rejected.
User Action:
None.
Reason:
You try to display a list with more than 9999 entries, which is the limit of the selection list display process.
System Action:
The list displays 9999 entries.
User Action:
None.
Reason:
The command entered on the command line was not known.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
No task definition was found that matched the specified task number. The task definition may have been deleted by another user.
System Action:
None.
User Action:
None.
Reason:
The task ended abnormally, but no reason for the failure was recorded.
System Action:
None.
User Action:
Review the system log around the time at which the task should have ended. This message is displayed if the background task was manually canceled or the region was shut down while the task was executing.
Reason:
The task identified by P1 has completed processing.
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:
The record variables prefixed with P2 from objid P1 could not be encoded. The most likely cause is that the total length of these variables is longer than 32K.
System Action:
The record is not transmitted.
User Action:
Contact your Systems Administrator.
Reason:
The field identified by P1 was not entered and is a required field.
System Action:
Field set in error.
User Action:
Enter a value for the specified field.
Reason:
The value identified by P1 is not valid for the field identified by P2.
System Action:
Field set in error.
User Action:
Enter a valid value for the specified field.
Reason:
The field P1 must be specified when the value for field P2 is P3.
System Action:
Field set in error.
User Action:
Enter a valid value for the specified field.
Reason:
The field identified by P1 is either not numeric or within the range specified by P2 and P3.
System Action:
Field set in error.
User Action:
Correct the identified field and retry the operation.
Reason:
A value for field P1 must be specified if a value for P2 is specified.
System Action:
Field set in error.
User Action:
Enter a valid value for the specified field.
Reason:
A Communication Access Method must be specified. Enter either YES to Use VTAM? or enter a valid TCP/IP Host Name/Addr and TCP/IP Port Number to use the TCPIP Access Method.
System Action:
Field highlighted in error.
User Action:
Enter a value for the specified field.
Reason:
This system has not been set up to permit the access method identified by P1. Refer to the Customizer parameter group MULTISYS under the TUNING category to check the current system configuration for access methods. To list the parameter groups, enter the /PARMS shortcut.
System Action:
Field highlighted in error.
User Action:
Enter a valid value consistent with the supported access methods in this system.
Reason:
The specified system name and version combination does not exist.
System Action:
The request is rejected.
User Action:
Correct and retry. Use '?' to display a list of valid system images names.
Reason:
The specified transmission mode is not valid.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
A prompt list was presented, but you did not choose an item.
System Action:
No value is entered.
User Action:
None.
Reason:
The Ruleset name specified is not defined.
System Action:
The request is rejected.
User Action:
Correct and retry. Enter a '?' in the Ruleset Name field to see a list of rulesets.
Reason:
You must specify the primary name of a remote region. Instead, you have specified the primary name of this region.
System Action:
The field that causes the error is highlighted.
User Action:
Enter a value that is the primary name of a remote region.
Reason:
The field P1 must be blank when the value for field P2 is P3.
System Action:
Field set in error.
User Action:
Blank out field P1 or change the value for P2.
Reason:
An attempt to establish communication with the remote region failed because TCP/IP is not active and access method VTAM has not been specified.
System Action:
Communication to the remote region is not established.
User Action:
1. Check the status of the TCP/IP interface by using the SH TCPIP command.
2. Attempt the operation specifying VTAM as the access method.
3. Ensure that the Management Services used by the remote region is at Version 3.4 or later.
4. Check the MULTISYS parameter group in this region to ensure that VTAM is allowed as an access method for communication. To list the parameter groups, enter the /PARMS shortcut.
Reason:
The TCP/IP Host Name/Addr is an IPv6 address; however, the region's SOCKETS API is not enabled for IPv6.
System Action:
The command is rejected.
User Action:
Correct the TCP/IP Host Name/Addr value and retry, or change the SOCKETS parameter group to use type IBMV6.
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 request to perform a database maintenance option was refused because the requesting user did not have sufficient authority level in his/her UAMS profile.
System Action:
The request is rejected.
User Action:
Ask your Systems Administrator to increase the Authority level in the UAMS definition for your userid if this capability is required.
Reason:
A database administration request was rejected because the request was for transmitting data to or from an ACB which is currently involved in another database administration task.
System Action:
The request is rejected.
User Action:
Wait until the previous database administration task has completed and retry.
Reason:
You have canceled a database synchronization, image transmission, express set up request, or database export request.
System Action:
None.
User Action:
None.
Reason:
The user has elected to transmit common components to another system but has not selected any components from the list(s) presented.
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:
The database synchronisation or express set up procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
A request to start the Express Set Up facility was rejected because Express Set Up is already in progress.
System Action:
The request is rejected.
User Action:
None.
Reason:
The user identified by P1 is being prevented from accessing the function selected due to insufficient access authority. A user requires AOM message receipt, All routcodes and console authority equal to or greater than 'C'.
System Action:
A message is displayed to the user.
User Action:
Contact your Systems Administrator.
Reason:
The requested multisystem function is not available because the default APPC link used by the region not being defined. This is defined during region initialization.
System Action:
The requested multisystem option is not performed.
User Action:
Verify that region initialization has completed successfully by viewing the initialization and customization logs from the Customization menu. If there are failed parameters, examine the failed parameter groups and correct or ignore the error. If the problem persists, contact your Systems Administrator.
Reason:
The P1 region has been unlinked.
System Action:
None.
User Action:
None.
Reason:
The home region, P1, was unlinked from the multisystem environment. This resulted in P2 remote regions being unlinked from this region.
System Action:
None.
User Action:
None.
Reason:
The requested operation failed because no response was received for the LINK START command in the timeout period.
System Action:
None.
User Action:
1. Check that the remote region is available. 2. Ensure that the Primary Name specified for the remote region is correct.
Reason:
The requested operation failed as the user specified an ACB Name that is the same as the local ACB Name. The ACB Name must not be the local ACB Name.
System Action:
None.
User Action:
Correct the Source ACB Name field and retry the operation.
Reason:
You specified the 'TS' Transmit Services option on the menu to transmit a service image, but you specified a system name which is not $SERVICE. You must have a system name of $SERVICE to transmit a service image. If you leave the 'System Name' and 'Version' fields blank, the 'TS' option processing will default to using a system name of $SERVICE and a version of 0001.
System Action:
Request rejected.
User Action:
Specify the value '$SERVICE' in the 'System Name' field and also check that the value in the Version field is correct.
Reason:
An attempt to establish communication with the remote region failed. Possible causes are as follows:
- The remote region is uncontactable. - The remote region does not support APPC over INMC. - The option to use APPC over VTAM may have been explicitly disallowed, and hence no communication could be established.
System Action:
Communication to the remote region is not established.
User Action:
1. Check that the remote region is available.
2. Ensure that the primary name specified for the remote region is correct.
3. Ensure that the Management Services used by the remote region is at Version 3.4 or later.
4. Check the MULTISYS parameter group in this region to ensure that VTAM is allowed as an access method for communication. To list the parameter groups, enter /PARMS from any panel.
Reason:
An attempt to check the release level of the remote region failed.
System Action:
The request is rejected.
User Action:
If the reason for the failure is not apparent, see the local and remote activity logs for more information.
Reason:
The P1 remote region is not licensed for the P2 product. To synchronize this region with or transmit knowledge base definitions from this region to a remote region, the remote region must be running at least version P3 of the P2 product.
System Action:
The request is rejected.
User Action:
Upgrade the remote region, then retry.
Reason:
The remote region is being unlinked from this region by an earlier request, and the background tasks associated with the operation are still in progress. Your request to link and synchronize this region to a remote region cannot be processed.
System Action:
The request to link and synchronize this region to a remote region is rejected.
User Action:
Wait for a few seconds, then retry.
Reason:
An error was encountered when attempting to find the name of the dataset allocated to the DD P1. The error message is contained in P2.
System Action:
The database synchronisation or express set up procedure terminates.
User Action:
The most likely scenario is that the required file is not allocated. Allocate the file and retry the function.
Reason:
The transmit request has been disallowed because the remote region is running an earlier version of the product. A transmit is only allowed with a remote region that has the same or a higher version than the region from where the request was initiated.
System Action:
The request is rejected.
User Action:
None.
Reason:
The DB synchronization request has been disallowed because the remote region is running an earlier version of the product. Synchronization is allowed only when the remote region has the same or a higher version than the region from where the request was initiated.
System Action:
The request is rejected.
User Action:
None.
Reason:
A Migration Mode synchronization request has been disallowed because the remote region is running an equal or later version of the product. Migration Mode is only allowed when the remote region has a lower version than the region where the request was initiated.
System Action:
The request is rejected.
User Action:
None.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |