|
|
|
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid parameter was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The values in the template are assigned to the resource variables with the resource name substituted.
System Action:
None.
User Action:
None.
Reason:
This process does not generate any variables.
System Action:
None.
User Action:
None.
Reason:
No more monitor messages can be added.
System Action:
The remaining monitor messages from the template are not added to the resource.
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:
Missing template class for processing.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
No template known to the system with prefix specified.
System Action:
The request is rejected.
User Action:
Try again with shorter prefix or specify with no prefix.
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 more records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
Process failed to open file for processing.
System Action:
Process stop.
User Action:
Check filerc code in the NCL Reference under &FILE OPEN.
Reason:
Process failed to close file.
System Action:
Process stop.
User Action:
Check filerc code in the NCL Reference under &FILE CLOSE.
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 required service proc not found.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
No active timer table found in the system.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Timer table required not found.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
P2 processing for Availability Map P1 has started.
System Action:
None.
User Action:
None.
Reason:
P2 processing for Availability Map P1 has completed.
System Action:
None.
User Action:
None.
Reason:
Resource desired state is determined by availability map.
System Action:
None.
User Action:
None.
Reason:
Error processing timer table.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Availability Map desired state is set to change resource state but if override active, this desired state will not change resource desired state.
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 P2 availability map timer table was loaded successfully at the time,
P1 .
System Action:
None.
User Action:
None.
Reason:
An availability map timer table was swapped at the time, P2 . The name of the new timer table is P1 .
System Action:
None.
User Action:
None.
Reason:
An invalid parameter was passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Parameter value required for the table was not specified.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
A valid table type: "TODAY" and "NEXTDAY".
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The procedure can not find object ID to be loaded to the timer table.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The timer table loaded successfully.
System Action:
None.
User Action:
None.
Reason:
The timer table unloaded successfully.
System Action:
None.
User Action:
None.
Reason:
Object ID specified unknown to the system, load failed.
System Action:
The request is failed.
User Action:
Check object ID through availability map menu option.
Reason:
Object ID specified loaded to the timer table.
System Action:
None.
User Action:
None.
Reason:
Timer table to process not found in the system.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Object ID specified unloaded from the timer table.
System Action:
None.
User Action:
None.
Reason:
Failed to save availability map definition to the database.
System Action:
Processing continue, the message written to logfile for further checking
User Action:
Check Availability Map definition through option menu.
Reason:
Action on timer table failed.
System Action:
The request is failed.
User Action:
Contact System Administrator.
Reason:
An invalid keyword was passed to the procedure.
System Action:
The procedure terminates.
User Action:
If the cause of this error is not apparent, contact your support representative.
Reason:
The NSM agent event handler failed to initialize because the agent instance for which the event handler was started was not active.
System Action:
The NSM agent event handler terminates.
User Action:
Check the activity log for other error messages that may explain why the NSM agent was not active. If the problem persists, contact Technical Support.
Reason:
An update to the vartable used by the NSM agent has failed. P1 is the FDBK code received for the operation.
System Action:
The NSM agent event handler terminates.
User Action:
Lookup the FDBK code P1 for the VARTABLE PUT verb in the NCL Reference. If necessary refer the error to Technical Support.
Reason:
The NSM agent event handler has started successfully.
System Action:
None
User Action:
None
Reason:
An invalid keyword was passed to the procedure.
System Action:
The procedure terminates.
User Action:
If the cause of this error is not apparent, contact your support representative.
Reason:
An attempt to activate the P1 NSM agent has been rejected because the agent is already active.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to terminate the P1 NSM agent, but the agent is not active.
System Action:
None.
User Action:
None.
Reason:
During activation of the NSM Agent, the build of the internal resource (NMASAGT) has failed.
System Action:
The activation of the NSM Agent also fails
User Action:
P1 is the error message returned from the dynamic build. Refer to the message help for this message for more information. If the way to correct the problem is not apparent, contact Technical Support.
Reason:
This message shows the current state of the P1 NSM agent.
System Action:
None.
User Action:
None.
Reason:
An NSM agent is being started for the system image P1.
System Action:
None.
User Action:
Use the $RM UNICENTER customizer group to control agent activation.
Reason:
The P1 NSM agent is being stopped.
System Action:
None.
User Action:
Use the $RM UNICENTER customizer group to control agent activation.
Reason:
The Agent Technolgoy process ( P1 ) is in P2 status.
System Action:
The agent fails to start.
User Action:
Check the startup logs located in $AGENTWORKS_DIR/services/var/log to determine the cause of failure.
Reason:
awservices is not active or has failed.
System Action:
The agent fails to start.
User Action:
Start awservices using your installations startup procedure. In the case of a failure check the startup logs located in $AGENTWORKS_DIR/services/var/log to determine the cause.
Reason:
An unexpected response was received for an awservices status command. P1 shows the first 50 bytes of the last response line.
System Action:
The agent fails to start.
User Action:
Perform the following actions to check installation items and, if necessary, report the error to Technical Support.
. /$pathname/agentworks.profile awservices status
awftest tcpip
USS . /$pathname/agentworks.profile;;awservices status USS . /$pathname/agentworks.profile;;awftest tcpip
$pathname is the HFS path to Agent Technology.
Reason:
A servicectrl command returned a non-zero return code for the definition of nmAgent to Agent Technologies.
System Action:
The agent fails to start.
User Action:
Use the reason to determine why the agent could not be defined.
If necessary, see the product documentation for details on how to update $AGENTWORKS_DIR/services/config/awservices/awservices.cfg to include the nmAgent class.
Reason:
Agent Technologies installation is not complete. The 'awsAdmin' MIB has not been loaded to the aws_sadmin store.
System Action:
The agent fails to start.
User Action:
Check the Agent Technologies installation process. If necessary use the 'ldmib' command to load the appropriate MIB.
Reason:
The 'nmAgent' MIB has not been loaded.
System Action:
The agent fails to start.
User Action:
Use the ldmib command to load the NMAGENT MIB.
For more information, see your product documentation.
Reason:
The Agent Technology program library was not available during startup because it was not included in the STEPLIB or in the system LNKLST.
System Action:
The agent fails to start.
User Action:
Check that the program library is accessible via the STEPLIB or the system LNKLST.
Reason:
During activation of the NSM agent, the build of the internal resource has failed.
System Action:
The activation of the NSM Agent also fails.
User Action:
None.
Reason:
awservices is not active and the $RM UNICENTER parameter group is set to start the agent.
System Action:
The agent retries every 2 minutes to start.
User Action:
Start awservices using your installations startup procedure. In the case of a failure check the startup logs located in $AGENTWORKS_DIR/services/var/log to determine the cause. Use the $RM UNICENTER parameter group to disable the agent if the agent is not required.
Reason:
Agent Technology is now active.
System Action:
The NSM agent start is retried.
User Action:
None.
Reason:
The P1 NSM agent is being stopped because of a system condition. P2 is the cause and may have the following values: SYSTEM IMAGE RELOAD - A system image.
System Action:
The agent is stopped.
User Action:
Dependent on the system condition.
SYSTEM IMAGE RELOAD - No action required. Agents are restarted by the system image load processing.
Reason:
The NSM agent uses a filter to determine which resources are to be visible to CA NSM. No such filter was defined at the time of the agent startup.
System Action:
The agent terminates.
User Action:
Ensure that a filter is specified in the UNICENTER parameter group.
Reason:
The NSM agent uses a filter to determine which resources are to be visible to CA NSM. The filter P1 nominated for the agent could not be found.
System Action:
The agent terminates.
User Action:
The filter is specified in the UNICENTER parameter group. Check that the filter name is correct.
Reason:
The instance name specified for the NSM Agent is invalid. The instance name must not contain any '@' characters.
System Action:
The agent terminates.
User Action:
By default the NSM Agent uses the region's NMID for the instance name. This value may be overridden in the UNICENTER parameter group. Update the instance name field in the UNICENTER group with a valid name.
Reason:
A vartable used by the NSM Agent has failed allocation.
System Action:
The agent terminates.
User Action:
The meaning of the FDBK code P1 can be found in the explanation of the VARTABLE ALLOC verb in the NCL Reference. If the reason for this error is not apparent, contact Technical Support.
Reason:
The message indicates that an NSM agent has been activated successfully. P1 identifies the agent instance in the format 'sysid(sysimg)'. Where sysid is the local system identifier as specified in the $RM Unicenter parameter group and sysimg is the system image name that this agent instance is representing.
System Action:
A cold start trap is issued indicating a new agent is active.
User Action:
None.
Reason:
The message indicates that the P1 NSM agent has failed.
System Action:
The agent terminates.
User Action:
Review accompanying error messages to see why the agent failed.
If the reason for the failure is not apparent, contact Technical Support.
Reason:
During initialization of the NSM agent, the event handler thread failed to start.
System Action:
The agent terminates.
User Action:
Check the log for any error messages related to the NSM agent event handler (message prefix RMTN00). If the cause of the failure is not apparent, contact Technical Support.
Reason:
The message indicates that the P1 NSM agent has terminated.
System Action:
None.
User Action:
None.
Reason:
Agent Works Factory interface returned an error for the named NSM agent.
System Action:
The agent terminates.
User Action:
Activate AWF tracing by setting the global $RMAWTRC to YES (for example, GLBL $RMAWTRC YES). Use the CHK line command on the resource status monitor to reactivate the agent. Supply the activity log containing the trace of the agent activity to Technical Support for problem determination.
Reason:
NSM agent, P1, has been terminated by Agent Technologies. Either awservices has terminated or the AGENTCTRL command has been used to terminate the agent.
System Action:
None.
User Action:
Check that Agent Technologies (awservices) is active. If necessary restart awservices and issue a CHK command against the INTNL resource for the agent.
Reason:
The NSM agent has detected an internal logic error. The logical state P1 is unknown.
System Action:
The NSM resource severity is set to the value defined for UNKNOWN.
User Action:
Report the error to your product support representative.
Reason:
The NSM agent call back interval has changed from the default of 30 seconds because the global variable $RMTNIVL has been set to an interval of P1 .
System Action:
CA NSM checks the agent for events every P1 seconds.
User Action:
None.
You can change the call back interval by setting the global variable $RMTNIVL to a value between 5 and 30 seconds. To set the global variable, issue the following command:
$GLBL $RMTNIVL n
where n is the interval, for example, $GLBL $RMTNIVL 5.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No records found to be displayed in the selection list. This caused by user has not enough authority to issue syscmd.
System Action:
The request is rejected.
User Action:
Check userid authority level.
Reason:
The FILEID P1 is not available for processing. An attempt to open the file failed with return code P2.
System Action:
The log viewing procedure, $LOGVIEW, terminates.
User Action:
Determine why the file is unavailable (by using SH ALLOC and SH UDB commands). Correct the problem, and retry the operation.
Reason:
The time must be specified as an operand of the time command.
System Action:
Command field placed in error.
User Action:
Specify a time as an operand of the time command. For example, TIME 13.12.10
Reason:
The time that was specified was invalid.
System Action:
Command field placed in error.
User Action:
The time should be in the format HH.MM.SS.HS. For example 10.30.25.05
Only the first two digits (that represent the hours) are mandatory.
Reason:
No log data was found for the date that you specified on the DATE command.
System Action:
None.
User Action:
Specify a date that has log data for it. For a list of dates that contain log data, enter the DATE command without specifying a date.
Reason:
The '/' command was specified which indicates that any text following the '/' shall be issued as a command, but no text was specified after the '/'.
System Action:
None.
User Action:
Specify an ASM command after the '/'.
Reason:
The '/' command was specified which indicates that any text following the '/' shall be issued as a command, but you are not authorized to issue commands.
System Action:
None.
User Action:
Contact your system administrator to raise your privileges.
Reason:
A command was issued by the use of the '/' command.
System Action:
None.
User Action:
None.
Reason:
You have specified the USERID command without specifying a userid, therefore $LOGVIEW assumes that you do not want any log records for a particular userid to be highlighted.
System Action:
None.
User Action:
None.
Reason:
You have entered the REGION or HLREGION command specifying a userid that is to long.
System Action:
None.
User Action:
Specify a userid that is less than or equal to 8 characters in length.
Reason:
Log records that are associated with the userid P1 (user name P2 ) will be highlighted on the $LOGVIEW panel.
System Action:
None.
User Action:
None.
Reason:
Log records that are associated with the userid P1 will be highlighted on the $LOGVIEW panel.
System Action:
None.
User Action:
None.
Reason:
You have specified the ORIGIN command without specifying an ORIGIN, therefore $LOGVIEW assumes that you do not want any log records for a particular origin to be highlighted.
System Action:
None.
User Action:
None.
Reason:
You have specified the ORIGIN or HLORIGIN command specifying an origin that is greater than 8 characters long.
System Action:
None.
User Action:
Specify an ORIGIN that is less than or equal to 8 characters in length.
Reason:
Log records that have an origin of P1 will be highlighted on the $LOGVIEW panel.
System Action:
None.
User Action:
None.
Reason:
You have specified the TEXT command without specifying any text, therefore $LOGVIEW assumes that you do not want any log records containing a particular text string to be highlighted,
System Action:
None.
User Action:
None.
Reason:
Log records that are contain the text string P1 will be highlighted on the $LOGVIEW panel.
System Action:
None.
User Action:
None.
Reason:
The display of log data will now only show the time and the log data.
System Action:
None.
User Action:
None.
Reason:
The display of log data will now only show the log data.
System Action:
None.
User Action:
None.
Reason:
The display of log data will now show the time (in long format), the origin, the region and the log data.
System Action:
None.
User Action:
None.
Reason:
You have specified the REGION command without specifying a region, therefore $LOGVIEW assumes that you do not want to only display log records for a particular region.
System Action:
None.
User Action:
None.
Reason:
You have specified the REGION command specifying a region that you wish to restrict the display to, therefore only log records with the region that you have specified will be displayed.
System Action:
None.
User Action:
None.
Reason:
You have specified the ORIGIN command without specifying an origin, therefore $LOGVIEW assumes that you do not want to only display log from a particular origin.
System Action:
None.
User Action:
None.
Reason:
You have specified the ORIGIN command specifying an origin that you wish to restrict the display to, therefore only log records with the origin that you have specified will be displayed.
System Action:
None.
User Action:
None.
Reason:
The TEXT command was entered without a text parameter indicating that no filtering of log records will be performed.
System Action:
None.
User Action:
None.
Reason:
Only log records containing the text string that you have specified in the TEXT command will be displayed.
System Action:
None.
User Action:
None.
Reason:
The LOCATE command on this panel will only allow you to locate any labels that you have previously defined.
System Action:
None.
User Action:
The following is an example of how to define a label:
Command===> .TOP
The following is an example of how to locate a label:
Command===> LOCATE .TOP
The following is an example of how to get a pick list of defined labels:
Command===> LOCATE .?
If you wish to locate a time or date or the TIME or DATE commands.
Reason:
The ASM log proc is currently not running. This is just a warning message.
System Action:
None.
User Action:
To start the logproc use the SYSPARMS LOGPROC= command. Also check the size of the log file.
Reason:
The number of records to be searched must be entered as an operand of the FINDMAX command.
System Action:
Command field placed in error.
User Action:
Specify the number of records to be searched as an operand of the FINDMAX command.
Reason:
The number of lines specified to search was invalid.
System Action:
Command field placed in error.
User Action:
The number of lines to search should be specified and must be in the range 500 to 10000.
Reason:
A print range that has been previously defined has been cancelled.
System Action:
None.
User Action:
None.
Reason:
You have attempted to mark the start of a print range without indicating which log record you wish the print range to start from.
System Action:
None
User Action:
Mark the start of the range by using one of the following methods:
- To mark by cursor:
- Type PRINT START at the Command ===> prompt. - Place your cursor on a log record within the scrollable window. - Press ENTER.
- To mark by time, use the DATE and TIME operands.
Reason:
The start of the print range was successfully set.
System Action:
None.
User Action:
None.
Reason:
You have attempted to mark the start of the print range after the end of print range marker that you have previously set.
System Action:
None.
User Action:
Mark the start range before the end range, or move the end range and remark the start of the print range.
Reason:
The start of the print range was successfully modified.
System Action:
None.
User Action:
None.
Reason:
You have attempted to mark the end of a print range without indicating which log record you wish the print range to end at.
System Action:
None
User Action:
Mark the end of the range by using one of the following methods:
- To mark by cursor:
- Type PRINT END at the Command ===> prompt. - Place your cursor on a log record within the scrollable window. - Press ENTER.
- To mark by time, use the DATE and TIME operands.
Reason:
The end of the print range was successfully set.
System Action:
None.
User Action:
None.
Reason:
You have attempted to mark the end of the print range before the start of print range marker that you have previously set.
System Action:
None.
User Action:
Mark the end range after the start range, or move the start range and remark the end of the print range.
Reason:
The end of the print range was successfully modified.
System Action:
None.
User Action:
None.
Reason:
An invalid operand was specified on the print command.
System Action:
None.
User Action:
Valid operands are START, END and CANCEL. See help for further information on operands for the PRINT command.
Reason:
One of the operands that you have specified on the PRINT START or PRINT END commands is invalid.
System Action:
None.
User Action:
Specify a valid print operand. Valid operands are DATE and TIME. The following are examples of valid PRINT commands:
PRINT START DATE=-1 TIME=13.30
PRINT END DATE=15/07/92 TIME=23.30.28
Reason:
The date that was specified was invalid.
System Action:
Command field placed in error.
User Action:
The date should be in the format DD/MM/YY. For example 21/12/92
Refer to help for further information on date formats.
Reason:
The log you have selected is being swapped by LOGPROC.
System Action:
The request is rejected.
User Action:
Wait a minute, before retrying.
Reason:
The Log View procedure has been invoked without a specific FILEID. The default of the currently active automation log cannot be used as there is no current active automation log.
System Action:
Request rejected.
User Action:
Contact your System Administrator.
Reason:
Processing stopped because error encountered during fileget.
System Action:
$RMVIEW terminates.
User Action:
Determine why the fileget is in error, check return code and vsamfdbk, correct and retry.
Reason:
When issuing a date command for a remote log, the starting date must be specified.
System Action:
The command is rejected.
User Action:
The starting date must be specified with a date command. The date should be in the format DD/MM/YY, for example 21/12/92. Refer to help for further information on date formats.
Reason:
Currently, there is no support available for printing the remote activity log records.
System Action:
The command is rejected.
User Action:
Log on to the remote system and print the activity log records.
Reason:
Currently, there is no support available on cursor sensitive help for the remote activity log.
System Action:
The command is rejected.
User Action:
Log onto the remote system and view the help definition.
Reason:
An unexpected return code was received from an APPC verb.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
Procedure in unexpected APPC "What Received" State.
System Action:
None.
User Action:
Contact system administrator.
Reason:
An invalid keyword was passed to the procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the procedure and rerun exec.
Reason:
The PRINT command was entered but a section of the activity log was not selected for printing.
System Action:
The print request is rejected.
User Action:
Use the PRINT START and PRINT END commands to mark the section of the activity log that you wish to print and then re-issue the PRINT command.
Reason:
The User has scrolled past either the begining or end of a logfile resulting in the logfile being swapped for the next logfile in sequence.
System Action:
None.
User Action:
The message is informational only.
Reason:
The User has scrolled past either the begining or end of a day's log, resulting in records for the next or previous day being displayed.
System Action:
None.
User Action:
The message is informational only.
Reason:
A search for records satisfying a TEXT, REGION or ORIGIN command has been cancelled by the operator from the confirm search panel.
System Action:
The search is terminated.
User Action:
None.
Reason:
You entered $LOG in a processing environment that does not have an associated real terminal window (for example, the system background environment, LU 1 Telnet, or ROF session).
System Action:
The command cannot be serviced.
User Action:
Issue the $LOG command in an environment with a terminal window.
Reason:
An invalid keyword was passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
If type specified is local printer then the printer name must be 3 chars hex.
System Action:
The request is rejected.
User Action:
Specify 3 char hex for printer name.
Reason:
Definition to be created already exists in the database.
System Action:
The request is rejected.
User Action:
Specify a different definition name.
Reason:
The name change has been propagated through the resource definition. You are advised to check all panels in the resource definition to make sure that the changes are correct and no other changes are required.
System Action:
None.
User Action:
Check the resource definition to ensure that it has been updated correctly.
Reason:
The procedure can not find the system name and version being processed.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The required field P1 used for processing omitted.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
No template definition selected.
System Action:
None.
User Action:
None.
Reason:
Template specified does not exist in the database.
System Action:
The request is rejected.
User Action:
Use ? to display template definition known to the system.
Reason:
000 priority is only used for activation, inactivation and force termination.
System Action:
The request is rejected.
User Action:
Specify priority between 001 to 999.
Reason:
Only command or process may be specified, not both.
System Action:
The request is rejected.
User Action:
Specify only command or process.
Reason:
Only timeout assume status or try force inactivation specified not both.
System Action:
The request is rejected.
User Action:
Specify only timeout assume status or try force inactivation.
Reason:
Invalid time specified.
System Action:
The request is rejected.
User Action:
Specify time between 00.00.00 to 24.00.00
Reason:
None
System Action:
The request is rejected.
User Action:
None.
Reason:
Color, highlight, and intensity are used for the event description. The description must be specified if one of these attributes is specified.
System Action:
The request is rejected.
User Action:
Specify event description.
Reason:
A filter of the type identified by P1 with name identified by P2 is not a valid selection. This may be because the filter does not exist on the database or it exists but does not support the current view. If the latter is the case then P3 optionally identifies the VIEW for which the filter is required.
System Action:
The request is rejected.
User Action:
None.
Reason:
Only P1 or P2 accepted to be specified in the field.
System Action:
The request is rejected.
User Action:
Specify a valid value.
Reason:
The specified value must be greater than P1 .
System Action:
None.
User Action:
Correct the value to meet or exceed the minimum value.
Reason:
The P1 must be a hex value.
System Action:
Error highlighted.
User Action:
Specify a valid value.
Reason:
An invalid initiator name has been specified.
System Action:
Error highlighted.
User Action:
Specify a valid value.
Reason:
Only value values for this field are 'ON' or 'OFF'.
System Action:
Error highlighted.
User Action:
Specify a valid value.
Reason:
Only value values for this field are 'AUTOMATED' or 'MANUAL'.
System Action:
Error highlighted.
User Action:
Specify a valid value.
Reason:
A required field has been omitted.
System Action:
Field in error is highlighted.
User Action:
Enter value.
Reason:
Time must be in HH.MM.SS format.
System Action:
Field in error is highlighted.
User Action:
Respecify value.
Reason:
The field value must begin with START or EXEC.
System Action:
Field in error is highlighted.
User Action:
Respecify value.
Reason:
The field value must be a VTAM resource name. It may be either a Local or Remote VTAM resource. This is only a warning message as it may be a Remote resource which is not currently active.
System Action:
Warning message.
User Action:
Verify value.
Reason:
An attempt has been made to retrieve existing definitions, but none exist.
System Action:
Field in error is highlighted.
User Action:
Correct value.
Reason:
Enter only the first 3 char of day.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Enter only ACTIVE or INACTIVE or A for ACTIVE and I for INACTIVE.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Invalid character encountered during validation.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Valid formats are A:B, A*:B, A:B* and A*:B* where A and B are the message prefix.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Wild char '*' must be specified at the end of the word.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Because ':' is a range character, it must be used in between characters.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Only P1 characters maximum for a P2 .
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Only value values for this field are 'Y' or 'N' or ' '.
System Action:
Error highlighted.
User Action:
Specify a valid value.
Reason:
Can not mix values to include or exclude messages.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Maximum value for second: 60, minute: 60 and hour: 24.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Panel required does not exist in library ICOPANL.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Specified class name/number unknown to system.
System Action:
The value is rejected.
User Action:
Use '?' to select class name.
Reason:
No class name defined to the system with prefix specified.
System Action:
The value is rejected.
User Action:
Use '?' to select class name.
Reason:
Not allowed to use character P1 .
System Action:
The value is rejected.
User Action:
Try again.
Reason:
Keyword must be specified if specifying a value.
System Action:
The value is rejected.
User Action:
Specify keyword for the value.
Reason:
Class must be specified if specifying a resource.
System Action:
The value is rejected.
User Action:
Specify class for the resource.
Reason:
No value selected from the selection list displayed.
System Action:
None
User Action:
None
Reason:
The value specified must numeric and fall in the range specified.
System Action:
The value is rejected.
User Action:
Specify value within the range.
Reason:
The value specified must be numeric and fall in the range specified.
System Action:
The value is rejected.
User Action:
Specify a value within the range.
Reason:
Process specified does not exist.
System Action:
The value is rejected.
User Action:
Try again.
Reason:
The MACRO identified by P1 did not return a description when invoked for this purpose. This would indicate that the NCL procedure associated with this MACRO has been written incorrectly.
System Action:
The request is rejected.
User Action:
Correct the macro NCL procedure and re-try.
Reason:
The value specified for this field is not valid. Use "?" to display selection list of valid values.
System Action:
The request is rejected.
User Action:
Try use "?" to specify a valid value.
Reason:
No panels were found in the panels dataset which matched the generic value specified by P1
System Action:
The request is rejected.
User Action:
Try specifying a different value.
Reason:
The specified system image is not valid because of one of the following:
- The image is not known to the region.
- The image does not support the selected option.
System Action:
The request is rejected.
User Action:
Enter ? in the System Name field to list the system images known to the region, and select the one you want. If the System Name field is not modifiable, you may be able to enter ? in the Version field. This message can also be issued where both the System Name and Version fields are not modifiable. In this case, determine the status of the system image through the ResourceView : System Image Definition Menu (/RADMIN.I).
If the image is in the knowledge base but is shared, this message indicates that you selected a resource class that is not supported by shared images. Nominate a local image for the selected resource class.
Reason:
Menu definition specified unknown to the system.
System Action:
The value is rejected.
User Action:
Use '?' to select menu definition.
Reason:
No menu/s were found in the CAS database which matched the generic value specified by P1
System Action:
The request is rejected.
User Action:
Try specifying a different value.
Reason:
Invalid P1 value encountered during validation.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Illegal use of wildcard character in the text.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
The specified UAMS User Group definition does not exist.
System Action:
The field in error is highlighted.
User Action:
Use ? to display a list of valid UAMS Group IDs.
Reason:
The 'From' and 'To' values specified for a State Change Exit procedure were the same.
System Action:
The field in error is highlighted.
User Action:
Change one of the values.
Reason:
No message/s were found to be displayed.
System Action:
The request is rejected.
User Action:
Try '??' or '???' to select a message.
Reason:
No template/s were found in the template system image with the resource class and the value specified by P1.
System Action:
The request is rejected.
User Action:
Try using 'L' option.
Reason:
The resource name entered was too long for a resource of type P1 and the resource type was neither a LOGICAL resource or a containment resource.
System Action:
The resource name is highlighted as in error.
User Action:
Change the resource name so that it is valid for the resource type or change the resource type to LOGICAL or make the resource a containment resource by entering a value in the Containment Resource Filter Name field.
Reason:
A resource filter was selected as a containment filter for a resource definition but was not a valid containment filter.
System Action:
The Containment Filter field is highlighted as in error.
User Action:
Select a resource filter that only uses the NAME keyword.
Reason:
The use of the wildcard character '*' is invalid when: 1. It is used by itself (eg. *) or, 2. A range is specified and * is not the last character (eg. aaa*:bbb* is allowed, but a*a:bbb is not).
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
A question mark (?) was placed in the unit address field of a DASD or TAPE resource definition indicating that a list of known resources was to be displayed, but one of the following conditions apply: * the resource is a logical resource (resource type is LOGICAL) * the resource is a containment resource (resource type is CONTAINMENT) * the resource is a template (system name is $TEMPLAT) Prompting is not supported for these kinds of resource definition.
System Action:
The unit address field is highlighted as in error.
User Action:
Enter a valid resource name in the field.
Reason:
The value in the ACB name field was more than 8 characters in length and was not a variable name (did not contain an ampersand).
System Action:
The ACB name is highlighted as in error.
User Action:
Correct the ACB name.
Reason:
An invalid name was entered for a resource that is one the following:
- in a user-defined subclass
- a logical resource (resource type is set to LOGICAL)
- a template resource (system name is $TEMPLAT)
- a containment resource (a value is present in the Containment Filter field) The name for this type of resource can only contain:
- alphabetic characters (A to Z) * numeric characters (0 to 9)
- the special characers: @ # $ . - : ( ) Additionally, the name cannot be wholly numeric (a number) and cannot contain embedded blanks.
System Action:
The resource name is highlighted as in error.
User Action:
Enter a valid resource name in the field.
Reason:
The value in the indicated field contains characters that are not permitted. The value may only contain the following characters: - Alphanumeric (A to Z and 0 to 9) - National (@, # and $) - Characters in the set: . - : ( )
System Action:
The field is highlighted as in error.
User Action:
Correct the value or enter a question mark (?) in the field to display a list of valid values.
Reason:
The valid values for this field are AUTOMATED, STARTAUTO, MANUAL, IGNORED, and OFF.
System Action:
The field in error is highlighted.
User Action:
Correct the value, or enter a question mark (?) in the field to display a list of valid values.
Reason:
A Containment Filter name was added to a resource definition but the resource is not a containment resource.
System Action:
The field is highlighted as in error.
User Action:
Either change the resource type to CONTAINMENT or erase the value in the Containment Filter field.
Reason:
P1 already exists in the database.
System Action:
The request is rejected.
User Action:
Specify a different P1.
Reason:
Under a JES3 system, there are no STCs. All started tasks have a jobtype of JOB.
System Action:
The request is rejected.
User Action:
Do not specify a 'Y' for STC.
Reason:
The ICON FLAG field may only contain a value when one of the other extended display attribute fields contains a value.
System Action:
Field highlighted in error.
User Action:
Either specify one of INTENSITY, COLOUR or HIGHLIGHT, or clear the ICON FLAG field.
Reason:
Both strings must have the same length for a text range match. This includes leading and/or trailing wildcard *'s.
System Action:
The value is rejected.
User Action:
Specify the same length of strings.
Reason:
Range char(:) must be used to specify range of values. Only one range char(:) must be specified in the string.
System Action:
The value is rejected.
User Action:
Specify range char(:) in between two strings with the same lengths.
Reason:
An invalid name was entered for the JES2 spool. Only one spool device is permitted and it must be named SPOOL.
System Action:
None.
User Action:
Change the resource name to SPOOL.
Reason:
AOM uses ROUTCDE=2 for all messages which do not have a ROUTCDE.
System Action:
Field is highlighted in error.
User Action:
Use another profile id.
Reason:
The field 'On Timeout Assume Status Of ...' may only contain a value if a valid time value has been entered in the 'Timeout After ...' field.
System Action:
The field in error is highlighted and the panel re-displayed.
User Action:
Either specify a valid value in the 'Timeout After ...' field or clear the value in the 'On Timeout Assume Status Of ...' field.
Reason:
The 'Retry Time Limit' and 'Retry Attempt Limit' fields are mutually inclusive. If one is specified then the other is mandatory.
System Action:
The field in error is highlighted and the panel re-displayed.
User Action:
Either specify both fields or clear both fields.
Reason:
Only timeout assume status or perform recovery may be specified, not both.
System Action:
The request is rejected.
User Action:
Specify only timeout assume status or perform recovery.
Reason:
The field 'Perform Recovery' may only contain a value if a valid time value has been entered in the 'Timeout After' field.
System Action:
The field in error is highlighted and the panel re-displayed.
User Action:
Either specify a valid value in the 'Timeout After' field or clear the value in the 'Perform Recovery' field.
Reason:
The action field identified by &P1&may only be specified if valid retry limits have been specified.
System Action:
The field in error is highlighted and the panel re-displayed.
User Action:
Either specify valid values in the 'Retry Time Limit' and 'Retry Attempt Limit' fields or clear the invalid action field.
Reason:
The keyword name specified was invalid because it is a reserved system keyword.
System Action:
The field in error is highlighted and the panel re-displayed.
User Action:
Specify a unique and non-system keyword name.
Reason:
The field identified by P1 may only contain a value when Extended Display Text has been entered.
System Action:
Field highlighted in error.
User Action:
Either specify Extended Display Text or clear the f`ield
Reason:
The value, P1 , must be either greater than or less than the value, P3 .
P2 indicates if the value must be greater or less.
System Action:
Field in error is highlighted.
User Action:
Change the field values to satisfy the requirement stated in the message.
Reason:
You have entered a value that is not in the list of valid values.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Valid values for the Transfer Status field are START, END, and FAILURE.
System Action:
The field in error, Transfer Status, is highlighted.
User Action:
Correct the value in the Transfer Status field.
Reason:
The value highlighted is not a valid value for the field identified by
P1 . Perform the corrective action indicated by P2 .
System Action:
The field in error is highlighted.
User Action:
Perform the corrective action indicated by P2 .
Reason:
The field identified by P1 is either not numeric or not between the range identified by P2 and P3 .
System Action:
Field set in error.
User Action:
Specify a number in the range identified.
Reason:
The field identified by P1 does not contain a valid value.
System Action:
Field highlighted in error.
User Action:
Enter a valid value for the specified field.
Reason:
Date must be in the format dd-mmm-yyyy , or part thereof, where dd ,
mmm , and yyyy must provide a valid date combination.
System Action:
The field in error is highlighted.
User Action:
Specify a valid date combination in the format of dd , dd-mmm , mmm , or
dd-mmm-yyyy (for example, 31-JAN-1998).
Reason:
Date must be a valid date in the format dd-mmm-yyyy , or part thereof, where dd , mmm , and yyyy must provide a valid date combination.
System Action:
The field in error is highlighted.
User Action:
Specify a valid date combination in the format of dd , dd-mmm , mmm , or
dd-mmm-yyyy (for example, 31-JAN-1998).
Reason:
Valid values for the Alert Autoclear field are YES , NO , or a time period in the format hh.mm .
YES , the default, specifies that, for a single file transfer instance, START and FAILURE file transfer alerts are closed automatically by subsequent END or FAILURE status events. END alerts cannot be closed in this manner.
NO specifies that no alerts are closed automatically.
hh.mm specifies that alerts are closed automatically only at the end of the specified period of time. hh is hours and can have values up to 99, and mm is minutes and can have values up to 59.
System Action:
The field in error is highlighted.
User Action:
Use the default, YES , or specify NO or a time period in the format hh.mm in the error field.
Reason:
The day value for the DATE criterion must be in the range 1 through 31.
System Action:
The field in error is highlighted.
User Action:
Correct the specified day value.
Reason:
For the month specified, P1 , the valid range of days is 1 through 31.
System Action:
The field in error is highlighted.
User Action:
Correct the specified DATE value.
Reason:
For the month specified, P1 , the valid range of days is 1 through 30.
System Action:
The field in error is highlighted.
User Action:
Correct the specified DATE value.
Reason:
For the month specified, P1 , the valid range of days is 1 through 29.
System Action:
The field in error is highlighted.
User Action:
Correct the specified DATE value.
Reason:
The Sysname and Version specified identify an isolated system image. You cannot specify an isolated system image for remote systems. To use this system image you must issue from the target system.
System Action:
The request is rejected.
User Action:
Use '?' get a selection list of valid system images.
Reason:
You tried to load the indicated subordinate system image in a focal point region. You cannot load a subordinate system image in a focal point region.
System Action:
The request is rejected.
User Action:
Specify a system image that is not associated with a subordinate region. To display a list of valid images, enter!?`in the Sysname to be Loaded field.
Reason:
The names of the primary, alternate, and spare couple data sets must be different.
System Action:
The request is rejected.
User Action:
Specify unique names for the couple data sets.
Reason:
You must complete the Couple Datasets fields in sequence. For example, you cannot enter a value in the Spare Couple Dataset (1) field without completing the Alternate Couple Dataset field.
System Action:
The request is rejected.
User Action:
Specify values in the Couple Datasets fields in sequence, starting with the Primary Couple Dataset field.
Reason:
You specified an invalid P1 value. P2 is either GREATER THAN OR EQUAL or LESS THAN OR EQUAL. P3 is the field being compared.
System Action:
The field in error is highlighted.
User Action:
Correct the value to satisfy the requirement stated in the message.
Reason:
You specified an invalid LU name in the Remote Node LU Name field.
System Action:
The field in error is highlighted.
User Action:
Correct the LU name.
Reason:
You have entered a value that is not in the list of valid values.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
You have entered a value that is not in the list of valid values.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
Enter only ACTIVE or INACTIVE or OFF.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
The name specified contained invalid characters (blank,*,comma,?,quotes and non- displayable characters).
System Action:
The field in error is highlighted.
User Action:
Correct the name.
Reason:
The name must be different to the local domain IDname as identified by: - the primary domain name (specified by the PRI= JCL parameter) - the system identifier (specified by the SYSPARM ID= command)
System Action:
Processing will not continue until a valid name is specified.
User Action:
Choose a different name and retry.
Reason:
The field must contain either zero or a positive integer or the string 'ANY'.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The name specified contains one or more of the following invalid characters: a space ( ) - parenthesis * - asterisk ; - semi-colon , - comma _ - underscore ? - question mark ' - single quote " - double quote
System Action:
The field in error is highlighted.
User Action:
Correct the name.
Reason:
The specified time exceeded the 24-hour range.
System Action:
The field in error is highlighted.
User Action:
Specify a time in the range from 00.01.00 through 24.00.00.
Reason:
The specified value must be between 00.01.00 and 24.00.00.
System Action:
None.
User Action:
Correct the value.
Reason:
The specified link name contains invalid characters. A link name can be up to 12 characters long, must start with an alphanumeric or national character, and may contain any graphic characters except for the asterisk (*).
System Action:
None.
User Action:
Correct the name, and retry.
Reason:
The highlighted value must be in the range 1 through 9.
System Action:
The field in error is highlighted.
User Action:
Correct the value.
Reason:
You entered an invalid TCP/IP address or host name. The value must be one of the following:
- A valid TCP/IP address such as 10.255.255.255
- A valid host name such as TCPACC1 (maximum of 35 characters)
Note: If you specify a host name, ensure the name resolution is enabled at your site.
System Action:
The field in error is highlighted.
User Action:
Correct the TCP/IP address or host name.
Reason:
A invalid range of numbers has been specified. The low limit of the range should always be less than or equal to the high limit OR the range specified has more than 5 ports.
System Action:
The value is rejected.
User Action:
Specify the correct range.
Reason:
The partitioned dataset P1 was specified with a member name.
System Action:
The field containing the dataset name is highlighted as an error.
User Action:
Remove the member name.
Reason:
For a Web Action to be valid, it must be prefixed with one of the values shown in P1 .
System Action:
The field containing the Web Action is highlighted as an error.
User Action:
Insert a valid Web Action prefix.
Reason:
This region includes the capability to send data to ReportCenter, but this function is not yet activated.
This message occurs if the REPORTDATA or REPORTCENTER parameter group is present In this region but has never been updated.
The ReportCenter data feed will remain dormant until either of these groups is updated and actioned.
System Action:
Definition cannot be saved.
User Action:
If you want to enable this region to send data to ReportCenter, you must update and action the REPORTDATA or the REPORTCENTER parameter group, whichever is present In this region.
Implement the ReportCenter control region and the ReportCenter Java Task first to ensure that there is an application to receive the data feed.
Note: For more information about ReportCenter implementation, see the ReportCenter Guide.
If you have not or do not want to implement the ReportCenter feature, leave this field set to NO.
If you do not implement ReportCenter, you can see examples of reports at the following URL:
http://?your-host-and-port/public/reports/reportexpo.esp
?your-host-and-port is the IP address of this system and the port number of your WebCenter web interface port.
Example: http://141.202.66.44:8744/public/reports/reportexpo.esp
Reason:
A value of YES has been specified for Use SNMP?. YES is invalid for this Open System Adaptor type. SNMP support was introduced for DIRECTEXPRESS in z/OS 1.4 and EXPRESS in z/OS 1.6.
System Action:
The Use SNMP? field is highlighted.
User Action:
Change the Use SNMP? value to NO, or change the OSA type.
Reason:
You entered an IPv6 address or a host name, which resolved to an IPv6 address. IPv6 addresses are not supported by this resource class.
System Action:
The field in error is highlighted.
User Action:
Correct the IP address or host name.
Reason:
You specified an invalid value. This message displays the valid values.
System Action:
The value is rejected.
User Action:
Specify a valid value.
Reason:
The field P1 contains a valid IPv6 address; however, an IPv6 address is not acceptable here. Either the hostname is IPv4 or the sockets API does not support IPv6.
System Action:
The field is highlighted in error.
User Action:
Correct the value and retry.
Reason:
You set the Source Address field to ? to display a list of valid source addresses; however, a list cannot be displayed because of one of the following reasons:
System Action:
The field is highlighted in error.
User Action:
Supply a source address or clear the field.
Reason:
The type of command identified by P1 must start with one of the values in P2. The values for P2 are LXCMD, VMCMD, or both.
When used in the context of a resource definition, the NODE=, NAME=, or CMD= keywords are not required. These values are automatically filled in at the time the commands are used. The commands in this context have the following format:
LXCMD linux_command VMCMD vm_command
If you issue SYSCMD LXCMD and SYSCMD VMCMD from a Command Entry panel, those keywords are required, for example:
SYSCMD LXCMD NAME=linux_name NODE=vm_host_node CMD='linux_command'
SYSCMD VMCMD NODE=vm_node CMD='vm_command'
System Action:
The field is highlighted in error.
User Action:
Correct the syntax of the command.
Reason:
Connection P1 is rejected because an attempt to get the IP address for host name P2 failed or timed out.
System Action:
The connection is rejected, and processing terminates.
User Action:
See related messages to determine the reason for the error, or specify the IP address instead of the host name.
Reason:
Connection P1 could not determine the host name for address P2 .
System Action:
Processing continues.
User Action:
Processing continues, and you do not need to take any action. However, if you want to determine why this problem occurred, see related messages.
Reason:
Connection P1 failed because the remote host, whose name or address is P3 , was already connected to this region as connection P2 . A region can connect only once to the same remote host.
System Action:
Connection P1 cannot be processed.
User Action:
If you want to connect to another host, specify its name or address, and retry.
Reason:
An invalid keyword parameter was passed to procedure $RMVSDSP.
System Action:
The request is rejected.
User Action:
Specify a correct value for the keyword, then retry the execution of $RMVSDSP.
Reason:
An attempt to retrieve a list of resources has failed because no active system image could be identified.
System Action:
None.
User Action:
This is generally a transient condition, which may occur during system image load. Retry later. If the error persists, contact your local support representative.
Reason:
This is a trace message that is generated by the Status Monitor Web Agent procedure when the keyword parameter TRACE is set to YES.
System Action:
None
User Action:
None
Reason:
This is a message that is generated by the Status Monitor Web Agent procedure when it receives a message that it was not expecting.
System Action:
None
User Action:
None
Reason:
This is a message that is generated by the Status Monitor Web Agent procedure when it receives a request from the Web client that it does not support.
System Action:
None
User Action:
None
Reason:
An MDO assignment failed with ZMDORC 16 and ZMDOFDBK 0. This indicates that the map P1 does not exist in this system.
System Action:
The action terminates.
User Action:
Ensure that the OSCNTL file has been correctly updated for the installation of this product.
Reason:
An MDO assignment failed. The MAP was P1 , the MDORC was P3 , the MDOFDBK value was P4 , and the MDO component involved in the last operation was P2.
System Action:
The action terminates.
User Action:
Refer to the NCL Reference for details of the codes.
Reason:
A request passed to the Status Monitor Web Agent procedure contained invalid data. P1 contains the name of the element that was in error. P2 contains an explanation of the problem.
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
An indeterminate error occurred in the Status Monitor Web Agent. P1 contains an explanation of the error.
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
An MVS system command to the workload manager failed. P1 is VARY or MODIFY.
System Action:
The associated selection list line command is not effective.
User Action:
For more information, see the log.
Messages prefixed with RMWM0002 contain the error responses and the first contains the command that failed. Determine the cause of the command failure and correct it.
Reason:
An MVS system command to the workload manager failed. P1 is a response to the command or the command itself.
System Action:
The associated line command is not effective.
User Action:
Determine the cause of the command failure and correct it.
Reason:
A system command P1 has been issued by user P2.
System Action:
None.
User Action:
None.
Reason:
A D WLM,SYSTEMS command found no systems running with an active workload manager policy.
System Action:
None.
User Action:
If scheduling environments should exist, check the WLM configuration.
Reason:
An MVS system command, routed to the P1 region, has not responded within the allowed time.
System Action:
The associated selection line command is not effective.
User Action:
Check connectivity to the nominated region and retry the command.
Reason:
An invalid value was specified for the keyword P1 . The value specified was P2.
System Action:
The request is rejected and processing terminates.
User Action:
Specify a valid value for the keyword.
Reason:
The external application interface requires the services of the named feature.
System Action:
The request is rejected and processing terminates.
User Action:
Ensure that the requesting system has not excluded the named feature.
Reason:
An NCLCHECK command failed to validate the named script procedure.
System Action:
The request is rejected and processing terminates. An RSAPPL04 message is written to the log indicating the procedure error.
User Action:
Validate that the script name is correct and that the script is syntactically correct using the NCLCHECK command.
Reason:
This message is written to the log after an RMXCALL03 message indicating a script procedure is in error. The message text indicates the nature of the error in the first line of output from an NCLCHECK command.
System Action:
None.
User Action:
Use the message text to determine the reason for the script procedure being in error.
Reason:
An attempt to build the MAI session definition for an external application has failed.
System Action:
The request is rejected.
User Action:
Use the reason indicated to determine the cause of the error.
Reason:
An attempt to start the MAI session definition for an external application has failed.
System Action:
The request is rejected. The RMXCALL07 message containing the specific error details is written to the log.
User Action:
Review the RMXCALL07 message in the log to determine the cause of the error. Check that P1 is active, and that the corresponding application ID is defined and active on this system.
Reason:
This message is written to the log after an RMXCALL06 message indicating that a session could not be started. The message text indicates the nature of the error in the first line of output from an MAISESS START command. The possible causes include the following:
INACT indicates that the application ID is known to VTAM but inactive.
VTAM UNKNOWN indicates that the spplication ID is not known to VTAM.
System Action:
None.
User Action:
Use the message text to determine the reason for the error.
Reason:
An attempt to access an external application has ended.
System Action:
None.
User Action:
None.
Reason:
An attempt to access an external application has ended abnormally.
System Action:
None.
User Action:
Refer to the messages on the session end panel for problem determination
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 selected resource doesn't have Extended Functions defined.
System Action:
No further processing.
User Action:
None.
Reason:
The NCL Procedure specified as the Exit to be executed does not exist in the Commands Library concatenation.
System Action:
Procedure terminates in error.
User Action:
Correct exit in resource definition.
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The script generation process does not support the specified mode.
System Action:
The script terminates.
User Action:
Use the recording script for session start only. SKIP and END processing are not supported.
Reason:
The END function was entered from a Logon Recording panel.
System Action:
The Logon Recording script terminates.
User Action:
None.
Reason:
Logon Recording has started for the named application.
System Action:
The Logon Recording script proceeds.
User Action:
None.
Reason:
A VARTABLE ADD failed during Logon Recording.
System Action:
Logon Recording terminates.
User Action:
Determine the reason for the VARTABLE error.
Reason:
P1 should be specified as a function key number.
System Action:
Field is set in error.
User Action:
Specify a valid function key number for P1 .
Reason:
The field P1 is a required field.
System Action:
Field is set in error.
User Action:
Specify a value for P1 .
Reason:
The Logon Recording script has detected the entry of the Stop Recording function key.
System Action:
The Save Logon Recording prompt is displayed.
User Action:
Verify the details and press the Action key to confirm. Press the Cancel key to terminate Logon Recording.
Reason:
The Logon Recording script is building the script.
System Action:
The Confirm Generated Procedure panel is displayed when the script has been built.
User Action:
Wait for the Confirm Generated Procedure panel to view the script.
Reason:
There is a script generation process already running.
System Action:
Request rejected.
User Action:
Wait until the other user completes their script generation.
Reason:
The script procedure was successfully generated and saved as requested.
System Action:
None.
User Action:
None.
Reason:
The file request P1 failed for the file allocated with DDNAME P2 . The file return code was P3 and the VSAM feedback code was P4 .
System Action:
The requested is terminated.
User Action:
Determine the reason for the error and retry the request.
Reason:
The IDCAMS service P1 failed and the return code received was P2 .
System Action:
The request terminates.
User Action:
View the activity log for RMXGENSC13 messages which show the responses from IDCAMS.
Reason:
This is a bracketing message for the IDCAMS messages returned from a previous call.
System Action:
None.
User Action:
Determine the error as indicated in the IDCAMS message and retry your request.
Reason:
The entered command is not supported by Logon Recording.
System Action:
The request is rejected.
User Action:
Correct the command entered and retry.
Reason:
The Logon Recording script has detected the entry of the Stop Recording function key. The specified resource name was not used during the dialog. The generated script will therefore not be able to process for specific resources and may be incomplete.
System Action:
The Save Logon Recording prompt is displayed.
User Action:
Verify the details and press the Action key to confirm. Press the Cancel key to terminate Logon Recording. If necessary re-record the sequence making sure that the resource name is used in the dialog.
Reason:
An invalid value was specified for the keyword P1 . The value specified was P2 .
System Action:
The request is rejected and processing terminates.
User Action:
Specify a valid value for the keyword.
Reason:
A scripting function of keyword P1 has completed. P2 was the return code.
System Action:
None.
User Action:
None.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |