Reason:
A SUBCONFIG command was issued from an IDENTITY entry, but no SUBCONFIG entries were defined.
Action:
The SUBCONFIG command ends.
Reason:
A feature keyword that is found in the VMXRPI CONFIG file is no longer supported. The specification to include the feature is now specified on an ENABLE statement in the SECURITY CONFIG file.
Action:
The VMXCFG processing completes normally. To request support for the desired security feature, add an ENABLE statement to the SECURITY CONFIG file.
Reason:
A directory file lock was found during initialization of an Agent product server in a single System Image complex. The Agent server cannot process the directory files while they are being changed, so the server waits for the lock to be released. The most probable cause of a lock is that the specified user ID has issued an EDIT command.
Action:
To release the lock, contact the specified user ID and request them to complete the EDIT command. The Agent product server then completes its initialization.
Reason:
The current request to delete an IDENTITY directory entry cannot be completed because the entry contains BUILD statements for associated SUBCONFIG directory entries.
Action:
Delete the associated SUBCONFIG entries. Then delete the IDENTITY entry.
Alternatively, issue the DELENTRY command, which automatically deletes any associated SUBCONFIG entries.
Reason:
An internal utility is generating trace information on communications between member systems in a Single System Image complex. A request from Technical Support may activate this utility.
Action:
Provide the console log containing the tracing information to Technical Support for problem determination analysis.
Reason:
You are attempting to remove a Directory Manager from the MANAGERS definition file, but the Directory Manager has defined directory entries under its control. Only Directory Managers with no remaining assigned directory entries can be removed.
Action:
To transfer the directory entries controlled by the Directory Manager to another Directory Manager, issue the ASSIGN command. Then remove the specified Manager from the MANAGERS definition file.
Reason:
A REXX program is calling a product command and supplying the name of a REXX stemmed variable which supplies additional input to the command. The product server was unable to retrieve a value for the specified stemmed variable name.
Action:
Correct the program to assign the stemmed variable before using the name of the stem with the STEM option keyword.
Reason:
An ENTRY command specified that a statement be displayed or deleted, but no statement of the specified type or with the specified operands was found. The command ends with an error return code.
Action:
None.
Reason:
A command is modifying or adding operands to a directory statement of the specified type, but the maximum number of operand values was exceeded.
Action:
Processing is ended and the additions or changes are not executed. Correct the number of operand values so it does not exceed the defined limits for the type of statement being added or updated.
Reason:
An ENTRY command requested that a new value be removed from a directory entry statement, but the value was not present. The deletion attempt was ignored because the value was not present. Any other values being deleted on the same request, which are not already present, are added.
The command ends with a warning return code.
Action:
None.
Reason:
An ENTRY command requested that a new value be added on a directory entry statement, but the value was already present. The addition attempt was ignored because the value was already present. Any other values being added on the same request, which are not already present, are added.
The command ends with a warning return code.
Action:
None.
Reason:
The same node name was specified on more than one SSINODE statement in the PRODUCT CONFIG file. If present at startup, system initialization fails. If present during an update of the PRODUCT CONFIG file, the reconfiguration attempt will fail.
Action:
Remove the duplicate SSINODE name specification. Each SSINODE name must be unique.
|
Copyright © 2014 CA.
All rights reserved.
|
|