|
|
|
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:
The SYSLOGD pipe receiver has completed initialization successfully and is now waiting to read messages from the pipe.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to start the SYSLOGD pipe receiver without specifying the P1 parameter.
System Action:
The SYSLOGD pipe receiver does not start.
User Action:
The most likely cause for this message is starting the SYSLOGD pipe receiver manually with incorrect parameters on the command. Re-action the SYSLOGD parameter group instead to restart the SYSLOGD pipe receiver.
Reason:
The SYSLOGD pipe receiver tried to open the named pipe, but the operation failed.
P1 identifies the named pipe.
P2 is the return code.
System Action:
The SYSLOGD pipe receiver terminates.
User Action:
Verify that the named pipe exists. If not, create the pipe, and then restart the SYSLOGD pipe receiver by re-actioning the SYSLOGD parameter group.
Reason:
The SYSLOGD pipe receiver encountered return code P1 while trying to read from the named pipe.
System Action:
The SYSLOGD pipe receiver terminates.
User Action:
Verify that your UNIX file system has no problems, then restart the SYSLOGD pipe receiver by re-actioning the SYSLOGD parameter group.
Reason:
The SYSLOGD pipe receiver uses this diagnostic message to log the messages read. This message has the following format:
seq.pos mon day time system source[pid]: msgtext
seq is the message sequence number (as received by the pipe receiver).
pos is the message position within the sequence number. Some messages contain multiple messages separated by the carriage return character. The pipe receiver disassembles these multiline messages into separate messages, allocating a position number to each message.
mon is the month (for example, Sep).
day is the day in the month.
time is the time-of-day in hh:mm:ss format.
system identifies the system from which the message originated. This value can be a name or an IP address.
source[pid]: identifies the source of the message, ending with a colon. This value can be a process or job name, with a process ID in square brackets (for example, telnetd[659]:), or this value can be simply a name (for example, syslogd:).
msgtext is the actual free-format message text.
System Action:
The SYSLOGD pipe receiver continues processing.
User Action:
These messages are a useful aid when setting up your SYSLOGD event detector rules.
If the activity log has too many of these messages, you can disable the logging of these messages. Update the SYSLOGD parameter group to set Log Messages? to NO. Then, action the parameter group.
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 © 2012 CA. All rights reserved. |
|