SNAX/APC Configuration and Management Manual

SCF Error Messages for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
C-12
Error 00033
Error 00033
Probable Cause. The TRACE, STOP command was rejected because the trace was
already in the INACTIVE state.
Recommended Action. None.
Error 00034
Probable Cause. The TRACE, STOP command was rejected due to a deallocate-
segment error.
Recommended Action. You need to seek additional help. Follow the procedures
described at the beginning of this appendix for collecting relevant information and
contacting the appropriate support personnel.
Error 00035
Probable Cause. An ADD command was rejected because of an unknown target object.
For example, an ADD PTNR-LU command specified an unknown target LU, or an ADD
PTNR-MODE command specified an unknown remote partner LU.
Recommended Action. Verify the existence of the parent object, and add the parent
object, if necessary, before attempting to add its subordinates.
Error 00036
Probable Cause. Either an ADD SESSION command was rejected because its parent
PTNR-MODE object was not in the STARTED state, or a START command was
rejected because the target object’s parent was not in the STARTED state.
Recommended Action. Start the parent object before attempting to add a session or start
a subordinate object.
Error 00037
Probable Cause. An attribute specified with the ALTER PTNR-MODE command could
not be changed because the PTNR-MODE object was not in a valid summary state.
SNAXAPC 00033 Tracing has not been started.
SNAXAPC 00034 Tracing shutdown error.
SNAXAPC 00035 Parent object not found.
SNAXAPC 00036 Parent object not started.
SNAXAPC 00037 The token token-name is invalid in the current
keyword summary state.