|
|
|
Reason:
An invalid request was received. The details are in P1.
System Action:
Request rejected.
User Action:
Specify a valid request.
Reason:
The request is denied because the system is currently in status P1.
System Action:
Request is rejected.
User Action:
Try again later.
Reason:
The system is currently unavailable and cannot perform the request.
System Action:
Request is rejected.
User Action:
Try again later.
Reason:
Tracing for various system functions has been started.
System Action:
None.
User Action:
None.
Reason:
Tracing of various system functions has been disabled.
System Action:
None.
User Action:
None.
Reason:
The requested function was completed.
System Action:
None.
User Action:
None.
Reason:
The system has been successfully started.
System Action:
None.
User Action:
None.
Reason:
The system has successfully started but is in a suspended status so that no requests will be serviced.
System Action:
None.
User Action:
None.
Reason:
The system has been released from the suspended status and is now servicing requests.
System Action:
None.
User Action:
None.
Reason:
The system has been suspended. No requests will be serviced until the system is released.
System Action:
None.
User Action:
None.
Reason:
The system is shutting down.
System Action:
None.
User Action:
None.
Reason:
The system was shutting down but all outstanding processes did not complete within the timeout period. The system will now be forced to terminate.
System Action:
System is forced to terminate.
User Action:
None.
Reason:
The system has terminated successfully.
System Action:
None.
User Action:
None.
Reason:
The current system status is P1.
System Action:
None.
User Action:
None.
Reason:
The current process statistics are P1.
System Action:
None.
User Action:
None.
Reason:
The scheduler processor status is P1 and the NCL ID is P2.
System Action:
None.
User Action:
None.
Reason:
The process logger status is P1 and the NCL ID is P2.
System Action:
None.
User Action:
None.
Reason:
End of display messages.
System Action:
None.
User Action:
None.
Reason:
The process with name P1, with unique process identifier is P2 and step P3 does not exist.
System Action:
Request rejected.
User Action:
None.
Reason:
The process with name P1 and with unique process identifier P2 has been successfully copied with a new process identifier of P3.
System Action:
None.
User Action:
None.
Reason:
The request was denied because the process identified was not in the correct status for the request. P1 is the process name, P2 is its unique identifier, P3 is the current step and P4 is the current status.
System Action:
Request rejected.
User Action:
None.
Reason:
The process P1 with unique identifier P2 has been put into the processable state.
System Action:
None.
User Action:
None.
Reason:
The process P1 with unique identifier P2 has been put into the executable status.
System Action:
None.
User Action:
None.
Reason:
The process P1 with unique identifier P2 has been suspended.
System Action:
None.
User Action:
None.
Reason:
The process P1 with unique identifier P2 and step P3 has been suspended.
System Action:
None.
User Action:
None.
Reason:
The process P1 with unique identifier P2 has been cancelled.
System Action:
None.
User Action:
None.
Reason:
The process P1 with unique identifier P2 and step P3 has been cancelled.
System Action:
None.
User Action:
None.
Reason:
The process P1 with unique identifier P2 has been purged from the work database and log files.
System Action:
None.
User Action:
None.
Reason:
Header message for a display of processes.
System Action:
None.
User Action:
None.
Reason:
Detail line for a display of processes.
System Action:
None.
User Action:
None.
Reason:
Header line for display of steps of a process.
System Action:
None.
User Action:
None.
Reason:
Detail line for the display of process steps.
System Action:
None.
User Action:
None.
Reason:
End of display marker.
System Action:
None.
User Action:
None.
Reason:
An attempt to change the status of the Activity Scheduler failed because another user or process was already changing the status. P1 specifies the user ID, Nclid, and time the current status change was initiated.
System Action:
The request is rejected.
User Action:
Wait until the current action has completed and try again.
Reason:
The status of the Activity Scheduler has changed and the scheduler system is now P1. P1 can be ACTIVE, INACTIVE, or PAUSED.
System Action:
None.
User Action:
None.
Reason:
The feature or features P1 are either excluded or not licensed for this CPU.
System Action:
Function is terminated.
User Action:
Contact your Systems Administrator.
Reason:
The field P1 is required and must not be null.
System Action:
Field is set in error.
User Action:
Specify a value for P1.
Reason:
The value P1 has already been specified in this Parameter Group.
System Action:
Field is set in error.
User Action:
Specify a unique value.
Reason:
The field contains an invalid value. The only valid values are ACTIVE or INACTIVE.
System Action:
Field is set in error.
User Action:
Specify either ACTIVE or INACTIVE.
Reason:
The internal process P1 which is used by the Activity Scheduler was successfully updated or created.
System Action:
None.
User Action:
None.
Reason:
The internal process P1 which is used by the Activity Scheduler could not be created or updated. The action failed with return code P2 and the error message returned was P3.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
An invalid keyword value was passed. The keyword is P1 the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
There is no log information available for the process P1.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword is P1 the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
There are no process logs available.
System Action:
None.
User Action:
None.
Reason:
An attempt to start the Activity Scheduler Log processor was rejected because the logger is already running.
System Action:
Processing terminates.
User Action:
None.
Reason:
This is an information message indicating the action that the Activity Scheduler Log processor is about to take.
System Action:
The indicated action is performed.
User Action:
None.
Reason:
An error occurred in the work file manager. The error message returned is P1.
System Action:
Processing continues with the next log event.
User Action:
Check the P1 error message.
Reason:
The message P1 has been logged to the Activity Scheduler Logger.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact your local support representative.
Reason:
Template definitions cannot be accessed from this menu.
System Action:
The request is rejected.
User Action:
Access template definitions from the appropriate menu.
Reason:
Template definitions cannot be accessed from this menu.
System Action:
The request is rejected.
User Action:
Access template definitions from the appropriate menu.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The start date specified must be a date and time in the future.
System Action:
Fields set in error.
User Action:
Specify a future date and time.
Reason:
The field P1 is required if a value is specified for the field P2.
System Action:
Field P1 is set in error.
User Action:
Specify a value for P1 or blank out field P2.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The Activity Schedule P1 already exists.
System Action:
Field set in error.
User Action:
Specify a unique Activity Schedule.
Reason:
The Activity Schedule P1 was saved.
System Action:
None.
User Action:
None.
Reason:
A request to forecast an Activity Schedule failed because the Calendar Criteria and/or the Activity Schedule name was not specified.
System Action:
Request rejected.
User Action:
Specify the missing data.
Reason:
The function P1 for Activity Schedule P2 was cancelled.
System Action:
None.
User Action:
None.
Reason:
The maximum number of Activity Schedule items allowed is P1. This number has already been reached and no more items can be added.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to browse or update the parameters for a process was rejected because a process name was not specified.
System Action:
The request is rejected.
User Action:
Specify a process name.
Reason:
An error occurred trying to perform action P1 with table P2 resulting in a feedback code of P3. The key used was P4.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
At least one Activity Schedule item must be specified.
System Action:
Fields set in error.
User Action:
Specify at least one item.
Reason:
No Activity Schedule item was specified.
System Action:
Fields set in error.
User Action:
Specify at least one item.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The Activity Schedule P1 was deleted.
System Action:
None.
User Action:
None.
Reason:
The Activity Schedule P1 is being updated by user P2.
System Action:
Request is rejected.
User Action:
Try later.
Reason:
The selected action is not valid for system images other than the currently loaded system image and the associated schedule image.
System Action:
Request is rejected.
User Action:
None.
Reason:
No process name is defined.
System Action:
None.
User Action:
Correct your input.
Reason:
The submit function was cancelled as requested.
System Action:
None.
User Action:
None.
Reason:
The activity schedule P1 was submitted for processing to start at time P2 on date P3.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The specified action cannot be applied to activity schedules.
System Action:
None.
User Action:
None.
Reason:
The specified action cannot be applied to the activity schedule or process because it is in status P1. The object cannot be in this status to perform the selected action.
System Action:
None.
User Action:
None.
Reason:
Access to the Activity Scheduler monitor is denied because it is currently inactive.
System Action:
The request is rejected.
User Action:
Activate the Activity Scheduler and then retry the request.
Reason:
An invalid request was received. P1 is request.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The function P1 failed. P2 is additional information about the error.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
An invalid request was received. P1 is the request details.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The function P1 failed. P2 is additional information about the error.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
An invalid request received by scheduler processor. P1 is the request.
System Action:
Processing continues.
User Action:
Contact your local support representative.
Reason:
The processor is already active and only one can be active at a time.
System Action:
Request rejected.
User Action:
None.
Reason:
The processor has been STARTED or STOPPED. P1 indicates whether it was started or stopped.
System Action:
None.
User Action:
None.
Reason:
The processor has failed. P1 is more information about the error.
System Action:
Processing terminates.
User Action:
Contact your local support representative. Restart the processor by actioning the SCHEDOPTS parameter group.
Reason:
The processor has ended. P1 is more information.
System Action:
None.
User Action:
None.
Reason:
The service request P1 was put into HOLD status. P2 provides more information.
System Action:
None.
User Action:
None.
Reason:
The system has stopped processing after completing normal shutdown processing.
System Action:
None.
User Action:
None.
Reason:
A process has been started as requested.
System Action:
None.
User Action:
None.
Reason:
A process has completed processing.
System Action:
None.
User Action:
None.
Reason:
Execution for a process failed. P1 is a message describing the error.
System Action:
None.
User Action:
See the message in P1.
Reason:
A process definition has been successfully deleted.
System Action:
None.
User Action:
None.
Reason:
The log entries for a process have been deleted.
System Action:
None.
User Action:
None.
Reason:
A process has actioned. The action performed for the process is P1.
System Action:
None.
User Action:
None.
Reason:
A process step has been started.
System Action:
None.
User Action:
None.
Reason:
A process step has completed processing.
System Action:
None.
User Action:
None.
Reason:
A process step execution failed. P1 is a message describing the error.
System Action:
None.
User Action:
See the message in P1.
Reason:
The process step P1 was skipped.
System Action:
None.
User Action:
None.
Reason:
A process step macro definition was not found.
System Action:
None.
User Action:
None.
Reason:
A process step has been actioned. P1 is the action performed.
System Action:
None.
User Action:
None.
Reason:
A request to the service request interface was invalid.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The function/action P2 has been performed for service request P1. P3 is additional information about the service request.
System Action:
None.
User Action:
None.
Reason:
An attempt to queue a request to the service execution processor failed because it was not active.
System Action:
The request is not queued.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The record is already being updated by user P1.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The field P1 is required if a value is specified for the field P2.
System Action:
Field P1 is set in error.
User Action:
Specify a value for P1 or blank out field P2.
Reason:
The start date specified must be a date and time in the future.
System Action:
Fields set in error.
User Action:
Specify a future date and time.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The requested service P1 completed successfully.
System Action:
None.
User Action:
None.
Reason:
The service P1 failed for file P2 and the return code was P4. The action performed was P3 and the VSAM feedback code was P5.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The requested service P1 failed with a vartable access error for table P2 performing action P3 and receiving feedback code P4.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The function P3 has completed successfully for process P1 with process identifier P2.
System Action:
None.
User Action:
None.
Reason:
The specified record was not found.
System Action:
None.
User Action:
None.
Reason:
An invalid request was received. P1 is the request details.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The service P1 was successfully completed for activity schedule P2.
System Action:
None.
User Action:
None.
Reason:
Service P1 for activity schedule P2 failed. P3 is additional information for the error.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The scheduler status is invalid for the request. P1 is the current system status.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The necessary control information has been added to the scheduler work file and a process ID allocated for process P1. The process ID is P2.
System Action:
None.
User Action:
None.
Reason:
The process P1 was not found on the database.
System Action:
Processing terminates.
User Action:
Specify a process that already exists.
Reason:
An invalid keyword value was passed. The keyword is P1 the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |