OSI/FTAM Programming Reference Manual

NonStop FTAM Initiator Diagnostic Messages
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
D-3
1007
Cause. The initiator has detected a protocol error.
Effect. The initiator aborts the association.
Recovery. This message might indicate an interoperability problem. Verify that the
responder is making a valid response to the initiator. This can be done by tracing the
initiator and verifying the protocol. For help in tracing the initiator process and
troubleshooting the problem, refer to the OSI/FTAM and OSI/APLMGR SCF Reference
Manual and OSI/FTAM Configuration and Management Manual.
For protocol details, refer to Section 4, FTM Procedures.
1011
Cause. The initiator has detected an error communicating with a TAPS process.
Effect. The initiator aborts the association.
Recovery. Retry the operation. If the problem persists, verify that the TAPS process is
configured properly and trace the initiator process using the PROV option. Examine the
status, error-code, error-subcode, and original-error-info information
displayed in the trace record. This information should help identify the cause of the
problem communicating with the TAPS process. For more information about tracing the
FTAM initiator/provider interface activity, refer to the OSI/FTAM and OSI/APLMGR SCF
Reference Manual.
1015
Cause. The initiator has received a group that is invalid for the service class
negotiated for the association, or the group of procedure calls is out of sequence.
Effect. The grouped service is not performed, and the initiator aborts the association.
Recovery. This message could indicate an interoperability problem. Use the SCF
TRACE command and PTRACE to trace the initiator process and verify the group
sequence. For information about tracing the initiator process, refer to the OSI/FTAM
and OSI/APLMGR SCF Reference Manual. To verify the sequence of procedure calls,
refer to the OSI/FTAM Programming Guide.
ZFTM-DIAG-PROTOCOL-ERROR
ZFTM-DIAG-LOWER-LAYER-FAILURE
ZFTM-DIAG-ILLEGAL-GROUPING