|
|
|
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:
When adding a SHARED System Image it is required that the System Affinity is specified by using the F10=Affinity key.
System Action:
The request is rejected.
User Action:
Use F10 to specify the system affinity for the Shared System Image.
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:
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:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
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:
You have specified a value in the version field that is the same as the version you are copying.
System Action:
The request is rejected.
User Action:
Change the value in the version field so that it is different to the version you are copying.
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:
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:
You are changing the home system of a local system image and if you proceed with it, relationships with resources in shared system images will be deleted. Only resources with the same home system can form relationships.
System Action:
None.
User Action:
Either cancel the change, or save it and unlink all related shared resources.
Reason:
You cannot exclude the home system of a resource. The home system is displayed in white .
System Action:
The request is rejected.
User Action:
To exclude a system that is currently the home system, you must make another system the home system first. Proceed as follows:
Step 1. Enter H beside another system to make it the new home system.
Step 2. Enter E beside the original home system to exclude it.
Reason:
The region is unable to contact the selected system, P1 .
System Action:
The request is rejected.
User Action:
Select a system that is displayed in green, indicating that the system is available.
Reason:
A command was issued against a shared resource but communication could not be established with any of the systems contained in the resource's system affinity list.
System Action:
The request is rejected.
User Action:
Ascertain why none of the systems in the affinity list are contactable. It may be that the region(s) on the system(s) are inactive or are not linked to the local region.
Reason:
You issued the AFFINITY command against a resource that is not part of a shared system image. This is not valid because only resources in shared images have system affintiy lists.
System Action:
The request is rejected.
User Action:
None.
Reason:
The P1 system was either added to or removed from the system affinity list of the P3 resource.
System Action:
None.
User Action:
None.
Reason:
The message indicates whether the P3 system is already included in or excluded from the affinity list of the P1 resource.
System Action:
None.
User Action:
None.
Reason:
The P1 resource has the P2 system as its home. The system was excluded from the affinity list of the owning shared system image, and you must specify another home system for the resource.
System Action:
The resources whose home systems need to be updated are listed.
User Action:
Update the home system of each affected resource.
Reason:
You must update the listed resource definitions before exiting the panel. For example, a system was excluded from the affinity list of the owning shared system image. However, the excluded system was the home system for a defined resource and you must update the definition to use a different home system.
System Action:
Exit from the list is prevented.
User Action:
Update each resource definition.
Reason:
A sysplex resource that begins with the supplied value P1 was not found.
System Action:
None.
User Action:
Specify ? to display a selectable list of sysplex resources.
Reason:
A resource class that begins with the supplied value P1 was not found.
System Action:
None.
User Action:
Specify ? to display a selectable list of resource classes.
Reason:
No selection was made from the Sysplex Resource selection list.
System Action:
None.
User Action:
None.
Reason:
No selection was made from the Resource Class selection list.
System Action:
None.
User Action:
None.
Reason:
User P1 is updating this system image.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The wildcard character, *, is required at the end of a generic name.
System Action:
The field in error is highlighted.
User Action:
Correct the value, and retry.
Reason:
This message displays the number of records for which the transient log size will be updated. You are prompted to confirm the updates.
System Action:
None.
User Action:
If the number of records found is excessively high, review the appropriateness of the specified transient log size as this can affect the overall performance of the region.
If you want to proceed with the updates, press F6 (Action) to confirm.
If you do not want to proceed with the updates, press Enter. You can then change the criteria to make it more restrictive.
Reason:
An error occurred when accessing a vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
Command Processor has returned the above error when attempting to issue a system command.
System Action:
Processing terminates in error.
User Action:
Determine the cause of the error from the returned message. Refer to the activity log for additional information.
Reason:
The containment resource object ID was not passed to exit process $RM02CRP.
System Action:
The process fails.
User Action:
Contact your system administrator.
Reason:
An invalid parameter was passed to process $RM02CRP. P1 is the parameter name, P2 is the parameter value, P3 is the Containment Resource that contains the process call and P4 is the call option.
System Action:
The process fails.
User Action:
Correct the process call parameter in the resource definition.
Reason:
The containment resource process ($RM02CRP) was called to process an action for a resource that did not have a resource type of CONTAINMENT.
System Action:
The process fails.
User Action:
Update the resource definition and either set the resource type to CONTAINMENT or remove the call to process $RM02CRP.
Reason:
An error was encountered by the Containment Resource Process.
System Action:
The containment process fails.
User Action:
Determine the cause of the error from the message content.
Reason:
A system command was issued by the Containment Resource process for an actual resource belonging to the containment resource.
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The status of a resource belonging to the containment resource was set because the indicated message was received.
System Action:
None.
User Action:
None. This message is informational only.
Reason:
An invalid parameter was passed to process $RM02CRP.
P1 is the parameter value.
System Action:
The process fails.
User Action:
Correct the process call parameter in the resource definition.
Reason:
An invalid keyword was passed to process $RM02CRP.
System Action:
The process fails.
User Action:
Correct the process call parameter in the resource definition.
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:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
Process name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
None.
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
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:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
Process name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
None.
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
A scantext line specified in the relationship expression has a blank scantext value.
System Action:
Field in error is highlighted.
User Action:
Correct.
Reason:
Invalid token value specified.
System Action:
Field in error highlighted.
User Action:
Correct.
Reason:
Parentheses are not matched.
System Action:
Field in error is highlighted.
User Action:
Correct.
Reason:
A defined Extended filter line is not specified in the current relationship expression.
System Action:
Field in error is highlighted.
User Action:
Correct.
Reason:
The length of this variable is restricted to P1 characters.
System Action:
Field in error is highlighted.
User Action:
Correct field value.
Reason:
The scan text is a required field if any of the above fields are specified.
System Action:
Scan text is highlighted in error.
User Action:
Specify a scan text or clear the other specified fields for this line.
Reason:
There is a conflict between the extended filter and the message text.
System Action:
The scan text is highlighted in error.
User Action:
Correct message text or extended filter.
Reason:
Syntax error.
System Action:
Field in error is highlighted.
User Action:
Correct.
Reason:
If a word number is specified then the scan text should not contain any blanks.
System Action:
Field in error is highlighted.
User Action:
Correct.
Reason:
A required field has been omitted.
System Action:
Field in error is highlighted.
User Action:
Enter value.
Reason:
Invalid P1 value encountered during validation.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Invalid character value specified.
System Action:
Field in error highlighted.
User Action:
Correct and try again.
Reason:
A field value contains an invalid character.
System Action:
The field is highlighted.
User Action:
Correct the value in the field.
Reason:
The command entered on the command line was not recognized.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
No value was supplied for a mandatory field.
System Action:
The field is highlighted.
User Action:
Enter a value in the field.
Reason:
The value entered in the Name field is invalid because it is too long for the selected class.
System Action:
The field is highlighted.
User Action:
Correct the resource name.
Reason:
A value was entered in the Name field, but resources in the nominated class are not named.
System Action:
The field is highlighted.
User Action:
Erase the name or correct the resource class.
Reason:
An message was not selected from the list for inclusion in the resource definition. P1 is the type of message that was being processed.
System Action:
Resource Learning continues.
User Action:
None.
Reason:
Resource Learning could not obtain a lock for the resource being created because another user was creating or updating the resource.
System Action:
The current panel is redisplayed and Resource Learning cannot continue until the lock becomes available.
User Action:
This error indicates that another user is attempting to create or update the same resource. Coordinate resource maintenance with the other user.
Reason:
An unexpected feedback code was returned from an NCL vartable verb.
System Action:
Resource Learning does not continue.
User Action:
Contact your support representative.
Reason:
A question mark (?) was entered in the Resource Name field but there is no prompt support for resource names in this class.
System Action:
The Resource Name field is highlighted as in error.
User Action:
Correct the resource name.
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:
An invalid character was included in the field value.
System Action:
The field is highlighted as in error.
User Action:
Change the field value so it does not include the disallowed character.
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:
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:
This command requires the number of pages to be specified.
System Action:
The request is rejected.
User Action:
Enter number of pages and retry.
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:
Invalid option specified on the panel selection.
System Action:
The request is rejected.
User Action:
Specify valid option of the display.
Reason:
The JES SET command has been issued to alter the Printer setup as requested.
System Action:
None.
User Action:
None.
Reason:
The display to solicit the Printer details has timed out without having retrieved all necessary information.
System Action:
Procedure terminates in error.
User Action:
Retry.
Reason:
The resource the display was requested for is not an active system image and therefore is not a valid request.
System Action:
Procedure terminates in error.
User Action:
None.
Reason:
The resource selected is controlled by a remote region and therefore requires the display to be send to the remote region by ROF. A remote SIGNON was issued, but it timed out before success notification.
System Action:
No further processing is done.
User Action:
Ensure the INMC link to this region is available, 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:
The 'Mount' command requires the volser to be specified.
System Action:
The request is rejected.
User Action:
Enter the volser and retry.
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:
Invalid option specified on the panel selection.
System Action:
The request is rejected.
User Action:
Specify valid option of the display.
Reason:
An invalid character was included in the field value.
System Action:
The field is highlighted.
User Action:
Change the field value so it does not include the disallowed character.
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:
Parameter field line 2 was specified but line 1 was not.
System Action:
The missing parameter field line is highlighted.
User Action:
If line 2 is the only parameter field required, then move it to line 1. Otherwise, enter the missing parameter filed(s) on line 1.
Reason:
The User Profile identified by P1 has been deleted. P2 may contain additional information from the call to the security system
System Action:
None
User Action:
None
Reason:
The User Profile specified does not exist.
System Action:
The request is rejected.
User Action:
Check User Profile specified, rerun procedure.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
An attempt to maintain a user's UAMS record in a linked region failed because the updating procedure terminated abnormally. More information about the error was written to the activity log in the linked region.
System Action:
Processing continues. The UAMS record for the user was not updated in the linked region and is therefore not synchronized with the user's UAMS record in the current region.
User Action:
View the activity log in the region where the update failed to determine the cause of the error. After the problem has been rectified, retry to syncronize UAMS records with the linked regions.
Reason:
An attempt to maintain a user's UAMS record in a linked region failed because either the region is not active or the link to the region is not active.
System Action:
Processing continues. The UAMS record for the user was not updated in the linked region and is therefore not synchronized with the user's UAMS record in the current region.
User Action:
When communication with the remote region is established, retry.
Reason:
An attempt to update a user's UAMS record on a linked region failed because there was no UAMS record for the user on that region. The record cannot be added because an initial password is required.
System Action:
Processing continues. The UAMS record for the user was not created on the linked region.
User Action:
If the remote system is configured using a (full or partial) security exit, simply update the user record via UAMS or the Automation Services User Profile. This will cause the record to be added to the remote region. You can then force an initial password.
If the remote system is not configured with a security exit, then you need to be able to add the user record specifying an initial password. You can do this using either of the following methods: * delete and redefine the user record on this system. The user's initial password is specified when you add the record. * log on to the remote region and add the user record there, specifying the initial password.
Reason:
The UAMS record was successfully added, updated, deleted, or the password was forced on the current region.
P1 identifies the action performed. A value of "Focal Point Propagation" indicates an action has been performed by a focal point region on behalf of a subordinate region.
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:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
Type specified for processing unknown to the procedure.
System Action:
The request is rejected.
User Action:
Contact 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:
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:
Operand value specified for the OCS profile is rejected because user does not have enough authorization in its UAMS definition.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Userid specified has not been defined in UAMS.
System Action:
The request is rejected.
User Action:
Define userid in UAMS and try again.
Reason:
Values entered in the 'New Password' and 'Confirm New Password' fields were not exactly the same.
System Action:
The password change request is rejected.
User Action:
Reenter your new password in both the 'New Password' and 'Confirm New Password' fields.
Reason:
Your user password has expired and an new password must be entered before continuing.
System Action:
None.
User Action:
Enter a new password.
Reason:
A userid is being used for the first time. The password must be changed before continuing.
System Action:
None.
User Action:
Enter a new password.
Reason:
The value entered in the Current Password field does not match your existing user password for this region.
System Action:
The password change request is not processed.
User Action:
Correct the value in the Current Password field and retry.
Reason:
The value entered P1 is not valid for parameter P2 .
System Action:
The value is rejected.
User Action:
Correct the value for the parameter and retry.
Reason:
The prompt support character (=) was entered in a field on the User Description panel, which indicates that the field value should be sourced from the UAMS record for the nominated user ID. However, there was no UAMS record for the user.
System Action:
The value is rejected.
User Action:
Enter a value other than '=' in the field and retry.
Reason:
The userid specified in a copy request is already present in the database.
System Action:
The request is rejected and the User ID field is highlighted in error.
User Action:
Change the user ID to create a new user profile record or use the update function to update an existing user profile record.
Reason:
If the IP Summary Display field is set to ON , you must select at least one component to display from the list presented below this field; otherwise, you must set the IP Summary Display to OFF .
System Action:
Field set in error.
User Action:
Select a component to display in the IP Summary or set the IP Summary Display to OFF.
Reason:
An attempt to update a user's UAMS record on a linked region failed because there was no UAMS record for the user on that region. The record cannot be added because an initial password is required.
System Action:
Processing continues. The UAMS record for the user was not created on the linked region.
User Action:
If the remote system is configured using a (full or partial) security exit, simply update the user record via UAMS or the Automation Services User Profile. This will cause the record to be added to the remote region. You can then force an initial password.
If the remote system is not configured with a security exit, then you need to be able to add the user record specifying an initial password. You can do this using either of the following methods: * delete and redefine the user record on this system. The user's initial password is specified when you add the record. * log on to the remote region and add the user record there, specifying the initial password.
Reason:
An update of a user's UAMS record in a linked region was propagated to the current region and was processed successfully.
P1 is the operation that was performed (Add, Update, Password_Force, or Delete).
P2 is the ID of the user.
P3 is the name of the ACB from where the request originated.
System Action:
None.
User Action:
None.
Reason:
The UAMS record was successfully added, updated, deleted, or the password was forced on a linked region.
System Action:
None.
User Action:
None.
Reason:
The UAMS record could not be added, updated, deleted, or the password forced because the requesting user does not have authority to update the record in the region.
System Action:
None.
User Action:
None.
Reason:
A request to maintain a user's UAMS record on a linked region was rejected because the linked region is not configured to allow UAMS updates from other regions.
System Action:
The request is rejected.
User Action:
To configure a region to allow UAMS updates from other regions, go to /PARMS and update the SECSHIPPING parameter group.
Set "Ship to Linked Systems?" to YES to allow updates to be propagated. Set "Including Password Changes?" to YES to allow password changes to be propageted.
This process should be repeated on each region that will be involved in UAMS update propagation.
Reason:
Your password change request was passed to a linked region but could not be processed because the old value was not the same as on the current region.
System Action:
Processing continues. Your password is not updated on the linked region.
User Action:
Log on directly to the linked region and update your password so that it is the same as on the current region. Future password changes can then be propogated to the linked systems automatically.
Reason:
The UAMS record details were successfully added, updated, or deleted in a linked region. However, the request included a new password but the region was not configured for remote password change. As a result, the password was not changed in the remote region.
System Action:
The UAMS details were changed but the password was not changed.
User Action:
See the SECSHIPPING paramater group for specifications of remote UAMS update parameters.
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 filter identified by P1 has been successfully saved to disk.
System Action:
None
User Action:
None
Reason:
The function P1 being performed on filter P2 was cancelled at the user's request.
System Action:
None
User Action:
None
Reason:
An attempt was made to Insert or Repeat a condition line which would cause the filter to exceed the maximum number of conditions allowed.
System Action:
Request rejected.
User Action:
None
Reason:
An error has occurred which prevents another condition line from being inserted. Use the REFRESH command in an attempt to re-sequence the existing conditions and allow inserts to be performed.
System Action:
Request rejected.
User Action:
Use REFRESH command
Reason:
The filter identified by P1 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:
A vartable error occurred while performing function(P1) on vartable(P2). The FDBK was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact systems programmer
Reason:
While defining a filter 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 filter the field highlighted as being in error will only accept 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:
The VALUE field of a filter condition line must be a quoted value. The data will automatically be quoted unless it is too long to fit into the field after being quoted, in which case this message will issue.
System Action:
Field highlighted in error.
User Action:
Quote the data in the field.
Reason:
Right and left parentheses were entered without any filter information between them. This is an invalid situation.
System Action:
Field highlighted in error.
User Action:
Enter some filter information between the parentheses.
Reason:
While defining a filter the field highlighted as being in error will not accept the value identified by P1 as being valid.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field
Reason:
An information only message. If ? is entered in the VALUE field for a FIELD which does not require a discrete set of values, this message will display, indicating the TYPE of data required.
System Action:
None
User Action:
Enter a valid value for the specified field
Reason:
The user has specified a Filter name on an Add or Copy which corresponds to an existing Filter.
System Action:
Request is rejected.
User Action:
Change the name of this Filter and continue.
Reason:
The Filter definition identified by P1 has benn successfully deleted.
System Action:
None
User Action:
None
Reason:
The Filter definition identified by P1 is currently being used by the user identified by P2
System Action:
Request is rejected
User Action:
Wait until the other user has finished with the filter
Reason:
The system name specified in the filter boolean expression does not exist in the system.
System Action:
None.
User Action:
None.
Reason:
The pattern matching characters _ and % are only valid when the LIKE operator is specified.
System Action:
Field highlighted in error.
User Action:
Remove the pattern matching characters or use the LIKE operator.
Reason:
The use of the Field Prompt ? is not supported when any of the Pattern Matching Characters, % or _ are present.
System Action:
Field highlighted in error.
User Action:
Remove either the Field Prompt or the Pattern Matching Characters.
Reason:
Command specified is not recognized by the system.
System Action:
The request is rejected.
User Action:
Specify a valid command.
Reason:
The value for the STAMP field must be numeric, unless the operator is LIKE, in which case the wildcard characters % and _ are supported. The format of the STAMP field is YYYYMMDDHHMMSS.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field.
Reason:
Valid values for transmission state are start, end and failure.
System Action:
Field highlighted in error.
User Action:
Enter a valid value in field specified.
Reason:
Must be a valid Dataset.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field.
Reason:
Valid values for the Rule Status field are ACTIVE and INACTIVE.
System Action:
The field in error, Rule Status, is highlighted.
User Action:
Correct the value in the Rule Status field.
Reason:
File name can either be the 'source' filename or the 'target' filename.
System Action:
Field highlighted in error.
User Action:
Enter a valid value in the field specified.
Reason:
The value for the TIME field must be numeric in the format HHMMSS.
System Action:
Field highlighted in error.
User Action:
Enter a valid time value for the specified field.
Reason:
Within the time format HHMMSS, the HH (hours) value cannot exceed 24.
System Action:
Field highlighted in error.
User Action:
Enter a valid 'hours' value for the specified field.
Reason:
Within the time format HHMMSS the MM (minute) value and the SS (second) values cannot exceed 59.
System Action:
Field highlighted in error.
User Action:
Enter a valid 'minutes' and/or 'seconds' value for the specified field.
Reason:
The rule, P1 , is saved.
System Action:
None
User Action:
None
Reason:
You cancelled the function, P1 , which you were performing on rule P2 .
System Action:
None
User Action:
None
Reason:
You used the I or R action code to add a criteria line, but the rule filter already contains the maximum allowable number of lines, P1 .
System Action:
Request is rejected.
User Action:
Redesign your filter expression so that the number of criteria lines is less than the displayed maximum.
Reason:
The rule, P1 , was not found.
System Action:
Request is rejected.
User Action:
Determine the correct name or the reason for the object's absence. Correct the error, and retry.
Reason:
You specified a criteria line that contains only a left and a right parenthesis. A pair of parentheses must enclose a criterion.
System Action:
The fields in error are highlighted.
User Action:
Enter a criterion expression between the parentheses.
Reason:
While adding or copying a rule, you specified a name that is the same as the name of an existing rule.
System Action:
Request is rejected.
User Action:
Change the name of this rule, then continue.
Reason:
The rule definition identified by P1 has been successfully deleted.
System Action:
None
User Action:
None
Reason:
The rule definition identified by P1 is currently being updated by the user identified by P2 .
System Action:
Request is rejected.
User Action:
Wait until the other user has finished with the rule.
Reason:
The number of bytes transferred and the transfer rate are valid filtering values only if the transfer status is END.
System Action:
The field in error is highlighted.
User Action:
Remove the value from the field in error, or change the transfer status criterion to END.
Reason:
The character may not be used within the VALUE Field.
System Action:
Field highlighted in error.
User Action:
Remove the ~ character from the VALUE value.
Reason:
The filter requires at least one line of criteria entry.
System Action:
The fields in error are highlighted.
User Action:
Enter values for the fields in error.
Reason:
You used the I or R action code to add a criteria line, but the maximum allowable number of lines, P1 , has already been reached.
System Action:
The request is rejected.
User Action:
Review your filter so that the number of entries is not more than the displayed maximum.
Reason:
The value for the ELAPSED TIME field is an amount of time, not the time of day. The amount of time is specified in hours and minutes, in the format HHH:MM. Hours must be in the range 0 to 999 (inclusive). Minutes must be in the range 0 to 59 (inclusive). A colon separates the hours and minutes.
System Action:
Field in error highlighted.
User Action:
Enter a valid elapsed time value for the specified field.
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:
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:
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:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
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:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
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:
You tried to include a class that was already included in another P1 command with the INC class scope.
System Action:
The class is not selected for inclusion.
User Action:
If you want to include this class in the command, you can create a copy of the command specifically for this class.
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:
You tried to save a command that includes classes already included in another P1 command with the INC class scope.
System Action:
The command definition is not saved.
User Action:
Review the P1 command definitions with the INC class scope, and remove the duplicate classes.
Reason:
When specifying a command's scope, it is not necessary to include an * in the Type or Name fields because they are automatically treated as generic entries.
System Action:
The field in error is highlighted.
User Action:
Remove the * .
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:
If you specified a confirmation exit, the value of the Does This Command Require Confirmation? field must be YES.
System Action:
The field in error is highlighted.
User Action:
Either change the value of the Does This Command Require Confirmation? field to YES or remove the confirmation exit.
Reason:
In the Command Scope window, you cannot specify the P1 field if the value of the CLASS field is P2 .
System Action:
The field in error is highlighted.
User Action:
If you want to use the P1 field, specify a specific class in the CLASS field.
Reason:
In the Command Scope window, you must specify a type in order to specify a name.
System Action:
The field in error is highlighted.
User Action:
Either specify a type or remove the name.
Reason:
The P1 type of prompting is not valid for this command because the class scope is P2 . If present, P3 provides further detail as to the nature of the error.
If the class scope of the command is ALL, INC, or a specific resource
class , the type of prompting must be RESOURCE. These class scopes indicate that the command must be issued against a resource and as such should support prompting for the resource name.
If the class scope of the command is SNA , you may use any type of prompting. However, if the type scope of the command is also specified, the type of prompting must be RESOURCE.
If the class scope of the command is NONE , the type of prompting may be either SYSTEM or NONE.
Commands with SYSTEM or NONE prompting may only be issued as primary commands rather than being issued against resources.
System Action:
The field in error is highlighted.
User Action:
If P2 is ... Then in the Type of Prompting Required field, enter ... ALL, INC, or a specific resource class RESOURCE SNA with a Type command scope RESOURCE SNA without a Type command scope NONE, SYSTEM, or RESOURCE NONE NONE or SYSTEM
Reason:
You can use the F5 (Classes) function key only if the value in the CLASS field is INC or ALL. When the CLASS field contains one of these two values, preessing F5 will list the resource classes that you can include (INC) or exclude (ALL).
System Action:
The command is rejected.
User Action:
If you want to be able to include or exclude classes, specify INC or
ALL in the CLASS field.
Reason:
The command definition you tried to save has a class scope of INC, but you have not included any classes.
System Action:
The command definition is not saved.
User Action:
Press F5 (Classes), and select the classes for inclusion.
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:
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:
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:
Invalid parameters being passed to the procedure. Function must be specified.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the procedure and rerun exec.
Reason:
There is no availability map or monitoring map specified on this resource; therefore, a request to display it is ignored.
System Action:
The request is rejected.
User Action:
None.
Reason:
Delete process cancelled.
System Action:
None.
User Action:
None.
Reason:
A successful request to free table.
System Action:
None.
User Action:
None.
Reason:
The record identified by P1 does not exist.
System Action:
The request is rejected.
User Action:
Refresh the list of records...as the selected record may have been deleted, previously or by another user.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The record identified by P1 has been successfully saved to the database.
System Action:
None
User Action:
None
Reason:
The function P1 being performed on resource P2 was canceled at the user's request.
System Action:
None
User Action:
None
Reason:
An attempt was made to insert or repeat a timer which would cause the maximum number of timers (P1) to be exceeded.
System Action:
Request rejected.
User Action:
None
Reason:
An error has occurred which prevents anothers timer from being inserted. Use the REFRESH command in an attempt to re-sequence the existing timers and allow inserts to be performed.
System Action:
Request rejected.
User Action:
Use REFRESH command
Reason:
A vartable error occurred while performing function(P1) on vartable(P2). The FDBK was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact systems programmer
Reason:
While defining a resource availability map or monitoring map, the field identified by P1 was not entered. It is a required field.
System Action:
Field in error highlighted.
User Action:
Enter a value for the specified field.
Reason:
The value identified by P1 is not valid for the field identified by P2
This message may also have a list of valid values for the field appended to the end of it.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field
Reason:
One of the fields identified by P1 and P2, must be specified on this screen
System Action:
Field(s) highlighted in error.
User Action:
Enter a valid value for one of the specified fields
Reason:
When defining timers in an availabilty map or monitoring map, each combination of DAY, DATE, TIME, and RESOURCE must be unique. This message is issued if two or more timers have been defined with the same DAY, DATE, TIME, and RESOURCE name.
System Action:
Fields in error highlighted.
User Action:
Change details to make timers unique.
Reason:
The DAY portion of a date must be a value between 1 and P1
System Action:
Field(s) highlighted in error.
User Action:
Change day to conform with message
Reason:
It is an invalid situation to specify a generic date AND a day on the one timer.
System Action:
Field(s) highlighted in error.
User Action:
Specify either a generic date or a DAY.
Reason:
The resource identified by P2 may be affected by a change to the availability map or monitoring map identified by P1 .
System Action:
None.
User Action:
Check the resource to ensure its desired state and mode or monitoring activity status are as required.
Reason:
A generic value of '*', 'W/D' or 'W/E' was specified, which would cause the maximum number of timers (P1) to be exceeded, if it were expanded out to one timer entry for each day covered.
System Action:
Field(s) highlighted in error.
User Action:
Correct the number of timer entries to remain below the limit.
Reason:
It is an invalid situation to specify a date AND a generic day on the one timer. A generic day is either * for every day, W/E for Weekends and W/D for Weekdays.
System Action:
Field(s) highlighted in error.
User Action:
Specify either a date or a generic DAY.
Reason:
The availability map or monitoring map identified by P1 has been deleted, causing the resource identified by P2 to have its status reset.
System Action:
None.
User Action:
None.
Reason:
The Availability Map or Monitoring Map identifed by P1 was not saved or copied, because it already exists in the target system image.
System Action:
Request rejected.
User Action:
Specify a name that does not already exist in the target system image.
Reason:
The availability map or monitoring map identified by P1 has been deleted.
System Action:
None.
User Action:
None.
Reason:
The resource status has been reset because no availability map or monitoring map is attached.
System Action:
None.
User Action:
None.
Reason:
There is no use of specifying a timer without specifying any of P1 or
P2 or P3 .
System Action:
Validation failed.
User Action:
Specify desired state, mode or a process.
Reason:
When a process parameter specified, the process name must be specified.
System Action:
Validation failed.
User Action:
CLear process parameter or specify a process name in the process name field.
Reason:
Validation found an expired date and time specified.
System Action:
Validation failed.
User Action:
Specify future date and time.
Reason:
A date entered in a timer detail line cannot be greater than the specified expiry date.
System Action:
Field highlighted in error.
User Action:
Specify a date less than the expiry date or specify later expiry date.
Reason:
You have attempted to do a map reset (MPR) action against a resource that does not have a map override (MPO).
System Action:
Request rejected.
User Action:
None.
Reason:
The availability map or monitoring map P1 was copied successfully from one system image to another system image. Either a copy was created or an existing map was replaced, as indicated by P2 .
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
Update is in progress on this definition by another user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact the 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:
Update is in progress on this definition by another user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
Validation found an invalid value has been specified for P1 .
System Action:
The value is rejected.
User Action:
Specify a value with no blanks.
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:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
Filter name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
Specify filter name or use '?' to select filter 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:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
Filter name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
Specify filter name or use '?' to select filter 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:
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:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
Filter name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
Specify filter name or use '?' to select filter name.
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:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
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:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
Filter name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
Specify filter name or use '?' to select filter name.
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 complex icon filter, should use option 3 because option 2 is reserved for a simple icon filter
System Action:
The request is rejected.
User Action:
Use option 3 instead.
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:
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:
Invalid option specified.
System Action:
The request is rejected.
User Action:
Use '?' to display valid options, or check comment for valid options.
Reason:
Filter name to be processed with the option specified not found.
System Action:
The request is rejected.
User Action:
Specify filter name or use '?' to select filter name.
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 complex icon filter, should use option C because option B is reserved for a simple icon filter.
System Action:
The request is rejected.
User Action:
Use option C instead.
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:
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:
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:
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:
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:
This message is displayed on exit from an interactive session, if any changes have been made to a process using interactive edit.
System Action:
Re-enter interactive edit mode and allow user to select FILE or CANCEL
User Action:
Select FILE or CANCEL as appropriate
Reason:
In interactive mode, the STEP command was issued but no steps have been defined in the process.
System Action:
Reject the request.
User Action:
Define steps and continue
Reason:
The current process has been 'STEPPED' to the point where execution would normally terminate. To use the STEP command again the interactive environment will need to be reset by using the REFRESH command
System Action:
Request is rejected.
User Action:
Use the REFRESH key to reset the environment.
Reason:
The process log for this interactive session has been cleared.
System Action:
None
User Action:
None
Reason:
The process log for this interactive session has been cleared, and the processing environment has been refreshed so that execution will re-commence from the first step if the STEP command is used.
System Action:
None
User Action:
None
Reason:
The user has been in interactive edit mode and has returned to RUN mode. The processing environment has been refreshed so that execution will re-commence from the first step if the STEP command is used.
System Action:
None
User Action:
None
Reason:
The process identified by P1 has been successfully saved.
System Action:
None.
User Action:
None.
Reason:
The function P1 being performed on process P2 was cancelled at the user's request.
System Action:
None
User Action:
None
Reason:
A request was made to view the process log for an interactive session but there were no log records found
System Action:
Request rejected
User Action:
None
Reason:
An attempt was made to Insert or Repeat a step which would cause the process to exceed the maximum number of steps allowed.
System Action:
Request rejected.
User Action:
None
Reason:
An error has occurred which prevents anothers step from being inserted. Use the REFRESH command in an attempt to re-sequence the existing steps and allow inserts to be performed.
System Action:
Request rejected.
User Action:
Use REFRESH command
Reason:
A request for parameter definition was made against a line which did not contain a macro name
System Action:
Request rejected
User Action:
Enter details before trying to define parameters
Reason:
The object type identified by P1, with a name of P2, system name of P3 and system version of P4 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:
A request to browse/update parameters for the macro identified by P1 has ended with return code P2.
System Action:
None
User Action:
Contact systems programmer
Reason:
A request to define parameters for the step identified by P1, which invokes the macro identified by P2, has ended without a change being made to the parameters.
System Action:
None
User Action:
None
Reason:
A request to define parameters for the step identified by P1, which invokes the macro identified by P2, has ended successfully. The new parameter settings will be retained in memory and written to disk if/when the FILE or SAVE command is issued.
System Action:
None
User Action:
None
Reason:
A vartable error occurred while performing function(P1) on vartable(P2). The FDBK was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact systems programmer
Reason:
While defining a process 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 process identified by P1 has not been saved to disk as no changes had been made.
System Action:
None
User Action:
None
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 value identified by P1 is not a valid value where it appears because it is reserved for internal use.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field
Reason:
All steps which make up a process must have a unique name. This step is invalid because a step with the same name appears prior to it in the process.
System Action:
Field highlighted in error.
User Action:
Enter a unique step name
Reason:
If one part of a condition is entered then all three portions must be entered.
System Action:
Field(s) highlighted in error.
User Action:
Enter missing portions of condition expression
Reason:
No condition may be specified for the first step of a process
System Action:
Field(s) highlighted in error.
User Action:
Clear the condition in error.
Reason:
A condition expression is referencing a step name which does not appear prior to this step in the process
System Action:
Field highlighted in error.
User Action:
Enter another step name or define a step with the required name prior to the current step.
Reason:
A '?' was placed in the macro field and no macros were found to list.
System Action:
Field highlighted in error.
User Action:
Define some macros
Reason:
No macros were found which match the generic portion entered in the macro field.
System Action:
Field highlighted in error.
User Action:
Change the generic portion and try again, or use '?' to list all macros
Reason:
The process identified by P1 has been successfully deleted.
System Action:
None
User Action:
None
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
The user has been in interactive edit mode and has returned to RUN mode. The processing environment has not been refreshed as no changes were made during the interactive edit session.
System Action:
None
User Action:
None
Reason:
The user has specified a Process name on an Add or Copy which corresponds to an existing Process.
System Action:
Request is rejected.
User Action:
Change the name of this Process and continue.
Reason:
This is a warning message only. It indicates that P1 steps have been included in the process without having parameters defined for their macros. Issuing FILE or SAVE immediately will cause the process to be saved.
System Action:
None
User Action:
Either issue FILE or SAVE immediately to ignore the warning, or define parameters for the specified macros.
Reason:
A function such as Browse or Update was attempted with the special internal process $NCL as the target. This is invalid as $NCL is not a real process definition.
System Action:
Request is rejected.
User Action:
None.
Reason:
The P1 process definition was not copied because of P2 .
If the definition is for a global process, the operation is inappropriate because a global process is available to all system images already.
If a definition of the same name already exists in the target image, the operation cannot be performed.
System Action:
The process definition is not copied.
User Action:
If the process definition already exists in the target system image, review the definition to determine whether you want to replace it.
Reason:
The submit action for the process P1 was cancelled as requested.
System Action:
None.
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:
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 cannot 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.
Reason:
The process selected cannot be submitted to the scheduler because it is not in the currently loaded system image or the process is a special reserved process that cannot be submitted.
System Action:
The request is rejected.
User Action:
None.
Reason:
The P1 process definition was copied successfully from one system image to another system image. Either a copy was created or an existing definition was replaced as indicated by P2 .
System Action:
The process definition is copied.
User Action:
None.
Reason:
A record defining the action to be taken when an alert is raised is missing.
System Action:
The process is not saved.
User Action:
To recreate the action, enter P beside the entry for the GENALERT macro and press F10 (Actions).
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 copied without the action record.
User Action:
Note the process, and update it to recreate the missing action.
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 icon identified by P1 was not found on the database
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 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:
While defining an icon 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 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 field identified by P1 cannot contain a value greater than P2. Issued in relation to the HEIGHT and WIDTH fields. When issued in relation to HEIGHT the value of P2 will be dependent on the current value of WIDTH (P4) and vice versa.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field
Reason:
Only one input (CMD) field may be specified in an icon.
System Action:
Request rejected
User Action:
Only specify one CMD field
Reason:
The TXT command was issued against a line which already had a field assigned to it. This means that the text will be interpreted as a LABEL. However, LABELS need an icon to be at least 16 characters wide to be able to be inserted.
System Action:
Request rejected
User Action:
Make icon wider.
Reason:
Function P1, which was being performed on an icon was cancelled by the user.
System Action:
None
User Action:
None
Reason:
The icon P1 has had action P2 successfully performed upon it.
System Action:
None
User Action:
None
Reason:
This message issues if a value is specified for HEIGHT or WIDTH which is below the permissible minimum.
System Action:
Request rejected
User Action:
Select a value equal to or greater than the minimum (P2)
Reason:
The required ICON is currently being updated by the user P1.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The user has specified an Icon name on an Add or Copy which corresponds to an existing Icon.
System Action:
Request is rejected.
User Action:
Change the name of this Icon and continue.
Reason:
An icon panel which requires P2 rows is attempting to be displayed on a terminal which only has a capacity of P3 rows. This situation has most probably arisen by the icon being created on a terminal which supports a larger screen size.
System Action:
Request rejected.
User Action:
Display the panel definition on a terminal large enough to hold it.
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 icon panel definition identified by P1 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 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:
While defining an icon panel definition 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 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:
Function P1, which was being performed on an icon panel definition was cancelled by the user.
System Action:
None
User Action:
None
Reason:
The icon panel P1 has had action P2 successfully performed upon it.
System Action:
None
User Action:
None
Reason:
The icon attempting to be placed on the screen will not fit at the row,col combination identified by P1. This may be beacause it will overlay an existing icon or it will go over the edges of the screen. The reason is contained in P2.
System Action:
Reject request
User Action:
Make the icon smaller or move it to a different position.
Reason:
An attempt was made to use the PUTICON command to place an icon on the screen, however, there was no "current icon". An icon can be selected as the "current icon" by using the PICKICON command.
System Action:
Reject request
User Action:
Select an icon for placement using the PICKICON command.
Reason:
An attempt was made to use a command which requires an icon to identified. To identify an icon the cursor must be placed within the body of the icon. The cursor was detected as having not been within the body of an icon.
System Action:
Reject request
User Action:
Place the cursor over the icon to be actioned.
Reason:
Either a PICKICON or PICKGRP command was issued, to display a list of available ICONS or RESOURCE GROUPS but one was not chosen from the list.
System Action:
None
User Action:
None
Reason:
This is a warning message only. It indicates that P1 icons have been included on the panel without having resource groups attached. Issuing FILE or SAVE immediately will cause the definition to be saved, but no Icon Panel will be generated until all icons have resource groups attached. Resource Groups are attached to icons using the PICKGRP command .
System Action:
None
User Action:
Either issue FILE or SAVE immediately to ignore the warning, or attach icons to the specified boxes and try to SAVE/FILE again.
Reason:
An icon panel which requires P2 lines/columns is attempting to be displayed on a terminal which only has a capacity of P3 lines/columns.
System Action:
Request rejected.
User Action:
Display the panel definition on a terminal large enough to hold it.
Reason:
This message is issued in response to a QUERY command against an icon on the panel. P1 is the name of the ICON used and P2 is the name of the RESOURCE GROUP attached to it.
System Action:
None.
User Action:
None.
Reason:
The user has specified an Icon Panel name on an Add or Copy which corresponds to an existing Icon Panel.
System Action:
Request is rejected.
User Action:
Change the name of this Icon Panel and continue.
Reason:
As a result of a PICKGRP command a Resource Group was selected to be attached to an Icon. However, the selected Resource Group was previously attached to another Icon. Each Resource Group to be monitored may only be attached to ONE Icon per Icon Panel.
System Action:
Request rejected.
User Action:
Select a different Resource Group or delete the Icon to which this Resource Group was previously attached, or attach another Resource Group to it.
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 specified record was not found.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
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:
Not allowed to have the same full value.
System Action:
The request is rejected.
User Action:
Specify a unique full value.
Reason:
The specified record was not found.
System Action:
None.
User Action:
None.
Reason:
A Field Prompt Definition with the abbreviation entered already exists.
System Action:
The request to file or save the record is rejected.
User Action:
Change the abbreviation of the Field Prompt Definition and attempt to save it again.
Reason:
A Field Prompt Definition with the P1 entered already exists.
System Action:
The value is rejected.
User Action:
Change the P1 of the Field Prompt Definition and try again.
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 auto population facility has created the above resource.
System Action:
Informational only.
User Action:
None.
Reason:
The auto population facility has attempted to create a resource definition, but failed.
System Action:
Processing continues.
User Action:
None.
Reason:
The command processor encountered an error while processing a system command. P1 indicates the cause of the error.
System Action:
Processing terminates in error.
User Action:
Use P1 to determine the cause of the error, and rectify the problem.
Reason:
No resources were selected from the Auto Populate resource selection list previously presented.
System Action:
None.
User Action:
None.
Reason:
The auto population facility has created the above definition.
System Action:
Informational only.
User Action:
None.
Reason:
The Auto population request has completed.
System Action:
Informational only.
User Action:
None.
Reason:
You were auto-populating the P2 system image and entered SU beside the
P1 resource. The region cannot find the resource definition after population.
System Action:
The SU action terminates with the error message.
User Action:
Contact uour local technical support representative.
Reason:
The Auto Populate Facility tried but failed to create a sysplex resource definition.
System Action:
Processing continues.
User Action:
Contact Technical Support.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
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 Unselect command (U) was entered against a resource in the Auto Populate selection list, but it had not previously been selected and therefore could not be 'unselected'.
System Action:
None.
User Action:
None.
Reason:
The command processor encountered an error while processing a system command. P1 indicates the cause of the error.
System Action:
Processing terminates in error.
User Action:
Use P1 to determine the cause of the error, and rectify the problem.
Reason:
A request to select a resource for Auto Population was rejected because the resource is already defined in the selected System Image.
System Action:
None.
User Action:
None.
Reason:
When using the ALL command, S or U must be used to indicate whether all entries are to be selected or unselected (for example, ALL S).
System Action:
Command is rejected.
User Action:
Re-issue the command by specifying either ALL S or ALL U as required.
Reason:
The Auto Populate Facility is available to CONNECT:Direct for MVS CDMGR resources only (CDMGR type of JOB or STC).
System Action:
The request is rejected.
User Action:
Specify a CONNECT:Direct file transfer manager of type JOB or STC.
Reason:
You were auto-populating a local system image and entered S beside the
P1 resource on the Auto Populate Selection List panel. However, the P1 resource is already part of an active shared system image, and you cannot add it to the local system image.
System Action:
The region does not select the P1 resource for auto-population.
User Action:
Determine whether the P1 resource should be shared and, if required, update the affected system images.
Reason:
You entered the ALL command with an invalid operand. The valid commands are as follows: ALL U, ALL S, and ALL SU.
System Action:
The command is rejected.
User Action:
Reissue the command with the correct operand.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
You entered the ALL command with an invalid operand. The valid commands are as follows: ALL U, ALL S, and ALL SU.
System Action:
The command is rejected.
User Action:
Reissue the command with the correct operand.
Reason:
You entered U beside a resource that has not been selected. You cannot deselect that resource.
System Action:
None.
User Action:
None.
Reason:
You must select at least one resource before you press F6 (Action).
System Action:
None.
User Action:
Enter S beside the resources you want to define, then press F6 (Action).
Reason:
The command processor encountered an error while processing a system command. P1 indicates the cause of the error.
System Action:
Processing terminates in error.
User Action:
Use P1 to determine the cause of the error, and rectify the problem.
Reason:
The function specified in P1 is not operative; therefore, your system is not running in a Sysplex environment.
System Action:
The process terminates.
User Action:
This function is not relevant in a non-sysplex environment.
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:
Request action on the database failed with non zero return code.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The active System Image Definition cannot be deleted.
System Action:
The request is rejected.
User Action:
Delete the System Image Definition when it is inactive.
Reason:
No records of System Definition found in the database.
System Action:
None.
User Action:
None.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
The System image selected for deleting is the last System Image that points (via APPC LU value) to a ServiceView system and therefore cannot be deleted.
System Action:
The request is rejected.
User Action:
This system image can only be delete if another system image points to this LU. If appropriate create another definition and retry.
Reason:
The System Image Definition is the template definition base which should not be deleted.
System Action:
The request is rejected.
User Action:
None.
Reason:
No system images with names or versions that start with P2 were found.
P1 is either SYSNAME or VERSION.
System Action:
None.
User Action:
If required, create the system image. You can use any of the following methods to create a system image:
- Use the AutoAssist Express Setup Facility (/RADMIN.AD.E).
- Use the System Images option on the Resource Administration menu (/RADMIN).
- Use the AutoAssist Auto Populate Facility (/RADMIN).
Reason:
The global process image definition you have attempted to delete is a required component of Automation Services. You are not able to delete this global process image definition. However, you are able to delete other versions of the $PROCESS global process image definition if you wish.
System Action:
The request is rejected.
User Action:
None.
Reason:
The service image definition you have attempted to delete is a required component of Automation Services. You are not able to delete this service image definition. However, you are able to delete other versions of the $SERVICE image definition if you wish.
System Action:
The request is rejected.
User Action:
None.
Reason:
No system images of the type P1 were found.
System Action:
None.
User Action:
If required, create the system image. You can use any of the following methods to create a system image:
- Use the AutoAssist Express Setup Facility (/RADMIN.AD.E).
- Use the System Images option on the Resource Administration menu (/RADMIN).
- Use the AutoAssist Auto Populate Facility (/RADMIN).
Reason:
A request to load a new system image was rejected because there is already a system load in progress. The current load was started at P1.
System Action:
Request rejected.
User Action:
None.
Reason:
A request to load a system image was rejected because the home system was not supported by a linked region.
This may be because this is a system image from a region that has subsequently been unlinked.
System Action:
Request is rejected.
User Action:
Where the remote region is no longer linked, log on to that region and load the system image locally.
Reason:
From a subordinate region, you cannot delete a system image whose home system is not your own. P1 is the home system.
System Action:
The request is rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
Action P1 was issued against the base resource, that is, the resource whose relationships are being displayed or defined. This is not a valid action for this resource.
System Action:
The error is highlighted, and the request is rejected.
User Action:
Use a valid action.
Reason:
You tried to create a P1 relationship with the base resource. However, the P2 resource already has the maximum number of P1 relationships. A resource can have a maximum of 25 relationships of each type.
System Action:
The request is rejected.
User Action:
Review the existing P1 relationships for the P2 resource.
Reason:
You entered an action that makes no sense for the selected resource (for example, a PP action against a reesource which is already a primary parent).
System Action:
The request is rejected.
User Action:
Use an action which is applicable to the selected resource.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No records exist.
System Action:
None
User Action:
None
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The 'Unlink' line command is only valid for a currently linked Parent or Child.
System Action:
The request is rejected.
User Action:
None
Reason:
The 'Connect' Line command is not valid for a currently connected resource. 'Connect' is only valid for Eligible resources.
System Action:
The request is rejected.
User Action:
None
Reason:
The 'Connect' Line command is not valid for a currently connected resource. 'Connect' is only valid for Eligible resources.
System Action:
The request is rejected.
User Action:
None
Reason:
The user has cancelled the update of the relationships.
System Action:
Relationships are not updated.
User Action:
None
Reason:
The 'Existing Related' line command cannot be performed against the resource the Relationship List is currently presented for.
System Action:
None
User Action:
None
Reason:
A resource may have a maximum of P1 parents connected to it. This message indicates that an attempt has been made to connect a parent to a resource which would cause the maximum to be exceeded.
System Action:
Request to connect is rejected.
User Action:
Restructure the hierarchy, possibly by inserting a LOGICAL resource, so that not all the parents are connected directly to the resource in question.
Reason:
You tried to specify a relationship between resources in a local system image and a shared system image, but the local image does not have a home system. To specify such a relationship, both resources must have the same home system.
From Version 4.0 onward, a local image must have a home system. The home system nominates the system on which the image can be loaded.
System Action:
The system image definition is displayed for update.
User Action:
Specify a home system for the image, then press F3 (File) to save the updated definition.
Reason:
You tried to relate two resources that have different home systems. Only resources with the same home system can form a relationship.
System Action:
The request is rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No records exist.
System Action:
None
User Action:
None
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The 'Existing Related' line command cannot be performed against the resource the Relationship List is currently presented for.
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 User Profile found in the system.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to view the User Profile List was rejected because the user did not have UAMS access authority.
System Action:
The request is rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
Request action on the database failed with non zero return code.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
No records of Filter Definition found in the database.
System Action:
None.
User Action:
None.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
The Group Filter identified by P1 is currently included as a secondary filter in P2 SNA Groups and may not be deleted as this may affect the Group(s) integrity. The LG option may be used to list the Groups in which a filter is included.
System Action:
Request is disallowed.
User Action:
Use LG to list the affected groups and update them to remove the filter.
Reason:
The selected ruleset is currently active. You cannot delete it.
System Action:
The request is disallowed.
User Action:
To enable the ruleset to be deleted, proceed as follows:
1. At a ===> prompt, enter /PARMS to list the customizer parameter groups.
2. Enter F AUTOIDS to find the AUTOIDS parameter group.
3. Enter U beside the group to display its parameters panel.
4. In the Active Ruleset for File Transfer field, either fill it with blanks or replace the ruleset you want to delete by another ruleset.
5. Press F6 (Action) to unload the active ruleset and possibly load a new ruleset.
The ruleset you want to delete is now unloaded, and you can proceed to delete it.
Reason:
The Ruleset Load request was not actioned because there is no active file transfer monitoring.
System Action:
The request is ignored.
User Action:
Use Customization Parameters to set up File Transfer Monitoring.
2. Enter F AUTOIDS to find the AUTOIDS parameter group.
3. Enter U beside the group to display its parameters panel.
4. In the Active Ruleset for File Transfer field, either fill it with blanks or replace the ruleset you want to delete by another ruleset.
5. Press F6 (Action) to unload the active ruleset and possibly load a new ruleset.
The ruleset you want to delete is now unloaded, and you can proceed to delete it.
Reason:
You canceled your request.
System Action:
None.
User Action:
None.
Reason:
Your request to load the P1 file transfer ruleset was accepted.
System Action:
The request will be processed.
User Action:
None.
Reason:
You cannot delete a filter that is associated with a monitor. For example, you cannot delete the RESOURCEVIEW filter because it is associated with the general resource monitor.
System Action:
The request is denied.
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:
Request action on the database failed with non zero return code.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
No records of Command Definition found in the database.
System Action:
None.
User Action:
None.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No records found to be displayed in the selection list.
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 Monitoring/Availability Maps found for sysname and version specified.
System Action:
The request is rejected.
User Action:
None. If you want to set up a monitoring or availability map for this resource, go to the resource administration functions (shortcut /radmin).
Reason:
No Availability Map added or found for the sysname and version specified
System Action:
The request is rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No Availability Map found for sysname and version specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
List of resources attach to availability map P1 .
System Action:
None.
User Action:
None.
Reason:
This resource already detached by previous action.
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 records of Icon Definition found in the database.
System Action:
None.
User Action:
None.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No records found to be displayed in the selection list.
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 records of Macro Definition found in the database.
System Action:
None.
User Action:
None.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
The process identified by P1 was executed and there were no log records generated.
System Action:
None
User Action:
None
Reason:
The process selected cannot be submitted to the scheduler because it is not in the currently loaded system image or the process is a special reserved process that cannot be submitted.
System Action:
The request is rejected.
User Action:
None.
Reason:
None.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to select the global process described by P1 which had previously been selected.
System Action:
Request rejected.
User Action:
None.
Reason:
An attempt was made to unselect the global process described by P1 which had not previously been selected.
System Action:
Request rejected.
User Action:
None.
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. To access that menu, enter the /RADMIN.T path at the ===> prompt.
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 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:
$RMDYNAMIC is the definition used to generate the default Graphical Monitor screen when multiple products are present in the same region. It displays one icon per product. This definition cannot be updated.
System Action:
Request rejected.
User Action:
None.
Reason:
An invalid keyword was passed to the procedure $RMADAPI.
System Action:
The request is rejected.
User Action:
Correct the procedure call to $RMADAPI.
Reason:
The action P1 is not available for class P2 - P3.
System Action:
The request is rejected.
User Action:
None.
Reason:
Resource P2 of type P1 on system image P3 has changed to an ATTENTION state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for an ATTENTION state.
User Action:
For more information about the cause of the ATTENTION state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
Resource P2 of type P1 on system image P3 has changed to a DEGRADED state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for a DEGRADED state.
User Action:
For more information about the cause of the DEGRADED state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
Resource P2 of type P1 on system image P3 has changed to a FAILED state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for a FAILED state.
User Action:
For more information about the cause of the FAILED state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
Resource P2 of type P1 on system image P3 has changed to an INERROR state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for an INERROR state.
User Action:
For more information about the cause of the INERROR state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
Resource P2 of type P1 on system image P3 has changed to a MONERROR state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for a MONERROR state.
User Action:
For more information about the cause of the MONERROR state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
Resource P2 of type P1 on system image P3 has changed to a MONFAILED state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for a MONFAILED state.
User Action:
For more information about the cause of the MONFAILED state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
Resource P2 of type P1 on system image P3 has changed to a PENDING state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for a PENDING state.
User Action:
For more information about the cause of the PENDING state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
Resource P2 of type P1 on system image P3 has changed to an UNKNOWN state.
System Action:
An alert is issued with the severity defined in the $RM STATECHANGE parameter group for an UNKNOWN state.
User Action:
For more information about the cause of the UNKNOWN state, use the TL (Transient Log) action to view the Transient Log for the resource.
You can also use the A (Analyze) action to access the resource monitor for the resource. From here you can perform various actions against the resource.
Reason:
An error occurred generating a State Change Alert for resource P2.
P1 has one of the following values:
P3 contains an error explanation.
System Action:
The action on the alert fails.
User Action:
Investigate the cause of the error. If an alert exit procedure $RMAM00X is in use, the error message may be from the procedure. If the error is N48C01, a problem occurred with an APPC START of the Alert Monitor API, for example, a disconnected domain.
Reason:
The CALLTYPE keyword has the unsupported value, P1 .
System Action:
The return code is set, and no processing is performed.
User Action:
Contact Technical Support.
Reason:
The alert serial number could not be located using the alert identifiers provided.
System Action:
The return code is set to 8, and the requested processing is not performed.
User Action:
Ensure the alert keyword parameters uniquely identify an open alert.
Reason:
The argument, P1 , has the value, P2 , which is not supported by this Call-Back package.
System Action:
The return code is set, and processing terminates.
User Action:
Contact Technical Support.
Reason:
You have selected the P1 action for an alert, but the resource associated with the alert is not part of an active system image, so the P1 action is not available.
System Action:
The action terminates.
User Action:
Select another action.
Reason:
The AOMPROC is the receiver of messages from the primary message filter. This message indicates that the AOMPROC has been started and is ready to process message traffic.
System Action:
None - message is informational only.
User Action:
None.
Reason:
This message is part of the Unmatched Message Alerting (UMA) facility. It is issued when a message matches the Unmatched Message Alerting filter defined in the MSGAWARENESS parameter group.
An unmatched message is a message that does not match any EventView or ResourceView rules.
The message text comprises the message ID followed by ++UMA++, followed by the message ID and message text of the unmatched message. You can customize the text to the right of ++UMA++ through the MSGAWARENESS parameter group (/PARMS).
System Action:
The system writes this message to the Activity Log, raises an alert with this message as the alert description, or issues an EDS event with this message as its text. The option used is specified through the MSGAWARENESS parameter group.
User Action:
Review the captured message. If it is not important, define an EventView rule to suppress it. Conversely, the message may identify a resource under Automation Services control, in which case you may want to define it in the Status Monitor messages for that resource.
Reason:
The Unmatched Message Alerting server procedure, P1, failed to start. P2 is the error message returned from the APPC START command. The message that caused the alert is written after this message.
System Action:
Message processing continues without alerting for this message.
User Action:
Correct the problem highlighted by the error message in P2.
Reason:
The message burst protection facility has detected a flood of duplicated unsolicited P1 messages. To avoid damaging automation and the flooding of system consoles, the message burst facility will suppress all further duplicate messages until the rate of arrival drops below the parameters set during region initialization.
A message burst typically indicates a runaway task. The message burst facility suppresses the symptoms of this problem.
System Action:
Duplicates of the P1 message are suppressed.
User Action:
Investigate why the suppression occurred.
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:
An error was encountered while attempting to access the RAM database.
System Action:
Procedure is terminated without successfully establishing APPC requirements.
User Action:
Correct the database error and issue restart.
Reason:
The APPC function was not successfully completed. SYSMSG contains the unexpected message that resulted.
System Action:
Processing is continued.
User Action:
Contact your System Administrator.
Reason:
A region was unlinked and therefore the Traffic Managers are no longer required and are being shut down.
System Action:
The event, data and traffic manager procedures are flushed. Some APPC errors may be displayed on the activity log as the procedures are forcefully terminated.
User Action:
None.
Reason:
An attempt to start a link to a remote region failed. The remote region is P1 and the error message is P2 .
System Action:
The link activation will continue to be attempted as a background task.
User Action:
The most likely cause of the problem is that the remote region is not available. Check its status. If the link still fails after the remote region becomes available, contact your system administrator.
Reason:
You specified P1 as a column name on the SORT command; however, the column name is not recognized.
The following are valid sort columns:
System Action:
The sort command is rejected.
User Action:
Specify a valid column name.
Reason:
You specified P1 as a sort order on the SORT command; however, the sort order is invalid.
System Action:
The sort command is rejected.
User Action:
Specify a valid sort order. Valid values are A, ASCENDING, D, and DESCENDING. For example, to sort on the JOBNAME column in descending order, then issue the command SORT JOBNAME D.
Reason:
The Statistics Handler has attempted to allocate a Table, but the allocation has failed.
System Action:
Processing terminated in error.
User Action:
Contact your System Administrator.
Reason:
The Statistics Handler has attempted the specified action, but the attempt has failed.
System Action:
Processing terminated in error.
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:
As this resource exists on a remote region, an APPC conversation is required to process this statistics 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:
The command entered on the command line was not recognised 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:
There are currently no statistics available for this resource.
System Action:
The request is rejected.
User Action:
None.
Reason:
The Statistics table is not available.
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
As this resource exists on a remote region, an APPC conversation is required to process this statistics request. 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:
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:
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:
A temporary table is required to load current statistics table into. The allocation of this table has failed.
System Action:
Processing terminated in error.
User Action:
Contact your System Administrator.
Reason:
Vartable error.
System Action:
No further processing.
User Action:
None.
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
You elected not to print statistics.
System Action:
Processing continues.
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:
ServiceView and ResourceView SMF records will not be written because SMF has not been enabled due to one or both of the following:
- To write SMF records, the SMF Record Identification must have a non-zero value. This value is specified in the Customizer SMF parameter group.
- To collect ServiceView and ResourceView SMF records, specify YES in the Customizer SMFDATA parameter group.
System Action:
The procedure terminates and writes an error message to the system log.
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.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |