ADDRESS AOF commands produce the following return codes:
The host command environment abended while processing the AOF command.
The command executed successfully.
The host command issuing the AOF command contained errors.
A warning message was issued.
AOF is inactive (The AOFACTIVE parameter is set to OFF)
The command timed out because it took too much time to complete. Not all responses were received.
Rule set OPEN error
An error occurred in one of the I/O service routines. Check related messages in the external data queue and/or the OPSLOG to determine the cause
The AOF command contained a syntax error.
Rule set CLOSE error
The subsystem is not active, and CA OPS/MVS is not running.
Parameter list error (this is an internal error)
The subsystem version is incompatible with this command.
GETMAIN/FREEMAIN storage error. Insufficient storage in the main product address space.
SENDMG failed.
Catalog error detected when attempting to find the rule data sets that match the ruleset prefix and suffix.
The authorization exit rejected the AOF command.
Rule not found.
The user exit abended.
Rule has no ISPF statistics
Required output was not produced.
There is an AOF compile syntax error.
The SYSWAIT time expired before all output was retrieved from the remote system.
Ruleset prefix error.
Ruleset suffix error.
Receive message error from cross-system operation.
Either of the following:
The specified system ID is not defined to the MSF.
Ruleset alternate prefix error.
The specified system is not active.
There is a mismatch between MSF versions.
An action command was ignored, because the remote system that sent the command is not secure.
An internal service failed. An informative message is issued that further documents the failure.
The maximum dynamic rule size of one megabyte has been exceeded.
The maximum dynamic rule line length of 255 bytes has been exceeded.
The command failed because it was not issued from the SECURITYRULESET.
An ADDRESS AOF list type command (LIST, LISTSRC, LISTCOMP, LISTINST) was issued but the NOOUTPUT flag was either explicitly set or implied. Since no output can be returned, this operation is considered to be an error. Specifying multiple systems or using either EXT or ALL in the SYSTEM keyword on one of the list commands above most likely causes this error.
The rule has no PROC or TERM section and has been automatically disabled. This does not necessarily indicate an error.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |