OPSCTL OPSLOG commands produce these return codes:
The ADDRESS OPSCTL OPSLOG command string is too short. No command verb was supplied.
Examples of valid command verbs are: DEFINE, ACTIVATE and SETLIVE.
A syntax error was detected while parsing the OPSCTL OPSLOG command.
A syntax error was detected while scanning the OPSCTL OPSLOG command.
The log name specified is invalid. Log names must be from 1 to 16 characters in length and may contain any characters that are valid in OPS/REXX variable names. They cannot be all numeric and cannot start with a numeric character.
Either MSF is not active or the SYSTEM keyword was specified with an MSF SYSID that is invalid or inactive.
The OPSCTL OPSLOG LIST command cannot be used with the SYSTEM keyword in a NOWAIT environment.
A cross-system OPSCTL OPSLOG command was rejected because the target system is at a release below 11.06.00 and does not support this command.
A DEFINE command failed because the log name specified is already defined. Log names must be unique.
A DEFINE command failed because the data set name or pseudo-data set name specified is already defined. Data set names must be unique.
A DEFINE command failed because the maximum number of OPSLOGs are already defined.
A DEFINE command failed because of an internal 'lock' failure.
An ACTIVATE command failed because the maximum number of OPSLOGs are already activated. The maximum number of active OPSLOGs is controlled by the BROWSEACTIVEMAX product parameter.
An ACTIVATE command failed because the requested log name is already the live OPSLOG.
An ACTIVATE command failed because the requested log name is either already active or is in transition.
A SETLIVE command failed because the requested log name is already the live OPSLOG.
A SETLIVE or RESET command failed because the named OPSLOG is read-only.
A SETLIVE or RESET command failed because the named OPSLOG is not currently active and is therefore ineligible for this command.
A SETLIVE command failed because of an internal lock failure.
A SETLIVE command failed because of an internal failure. OPS_DSP address is zero.
A SETLIVE command failed because a non-normal UCBLEVEL value has been set for the device on which the OPSLOG data set resides. This is typically a short-lived condition and may be caused by EMC AutoSwap processing. Wait for a short time before retrying the command.
A RESET command failed because the named OPSLOG is currently the live OPSLOG.
A RESET command failed because of an internal lock failure.
A RESET command failed because of an internal unlock failure.
A DEACTIVATE command failed because the named OPSLOG is currently the live OPSLOG.
A DEACTIVATE command failed because the named OPSLOG is not currently active and is therefore ineligible for this command.
A DEACTIVATE command failed because there is a checkpoint pending for the named OPSLOG. A checkpoint writes the data in the OPSLOG data space to a DIV data set. Wait for the checkpoint to complete before retrying this command.
A DEACTIVATE command failed because there is a reset pending for the named OPSLOG. Wait for the reset to complete before retrying this command.
A DEACTIVATE command failed because there is a high checkpoint pending for the named OPSLOG. A high-checkpoint only occurs when a new DIV-backed OPSLOG is first used and may take some time to complete. Wait for the high checkpoint to complete before retrying this command.
A DELETE command failed because the named OPSLOG is currently the live OPSLOG.
A DELETE command failed because the named OPSLOG was not defined using an OPSCTL OPSLOG DEFINE command.
A DELETE command failed because the named OPSLOG is not currently inactive and is therefore ineligible for this command.
The current command failed due to a failure in unlocking the internal OPSLOG control block.
A LIST command failed because there are no OPSLOG entries to list.
A LIST command failed because of a missing buffer address. This internal error can only occur if there is an error in OPSLOG WebView.
A LIST command failed because of an internal buffer error (zero entries). This internal error can only occur if there is an error in OPSLOG WebView.
A LIST command failed because of an internal buffer overflow. This internal error can only occur if there is an error in OPSLOG WebView.
The log name specified on the current command does not exist on this OPS/MVS subsystem.
An attempt to send to message to a message queue failed. Check the external data queue and the OPSLOG for messages relating to a “send failure”.
An attempt to obtain storage failed. Check the external data queue and the OPSLOG for messages relating to storage failures.
No output was received as the result of a cross-system command.
Message queue allocation failed.
Message queue deletion failed.
Error in command output processing.
An error occurred attempting to send a message to an MSF queue.
The control blocks required for OPSCTL OPSLOG processing have not been created yet.
An ABEND occurred during OPSCTL OPSLOG processing.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|