This verb specifies options for back-level client-server tracing
(tracing of data sent between a current-level SNAplus2 server and
a back-level server or client). It is used only when you are in
the processs of migrating a client-server SNAplus2 system to a new
release of the software, so that one or more servers are running
the current-level software and providing support for computers running
the back-level software. For more information about the migration
process and on support for back-level computers, see the HP-UX
SNAplus2 Upgrade Guide.
This verb must be issued to a running node on a computer where
the back-level support software is running (for more information,
see the HP-UX SNAplus2 Upgrade Guide).
VCB
Structure |
 |
typedef struct set_bck_cs_trace
{
AP_UINT16 opcode; /* verb operation code */
unsigned char reserv2; /* reserved */
unsigned char format; /* reserved */
AP_UINT16 primary_rc; /* primary return code */
AP_UINT32 secondary_rc; /* secondary return code */
AP_UINT32 trace_flags; /* trace flags */
unsigned char init_flags; /* YES if initializing flags */
unsigned char set_flags; /* YES if setting flags */
/* NO if unsetting flags */
} SET_BCK_CS_TRACE;
|
Supplied
Parameters |
|
The application supplies the following parameters:
- opcode
AP_SET_BCK_CS_TRACE
- trace_flags
The types of tracing required. To turn off all tracing,
or to turn on tracing of all types, specify one of the following
values:
- AP_BCK_NO_TRACE
No tracing.
- AP_BCK_ALL_TRACE
Tracing of all types.
To activate tracing on specific message types, select one or
more values from the list below, combined using a logical OR operation.
- AP_BCK_UDP_TRACE
UDP messages
- AP_BCK_TCP_TRACE
TCP messages
- AP_BCK_UDP_TEXT
Text strings describing UDP events
- AP_BCK_TCP_TEXT
Text strings describing TCP events
- AP_BCK_TEXT
Text strings describing other events
- AP_BCK_MS_TRACE
Tracing on TRANSFER_MS_DATA verbs (passed to the
MS library on the server)
- init_flags
Specifies whether to initialize tracing (define
the tracing state at all interfaces), or to change the state of tracing
at one or more interfaces (leaving the others unchanged). Possible
values are:
- AP_YES
Tracing is being initialized. The trace_flags parameter defines the required state of tracing at
all interfaces.
- AP_NO
Tracing is being changed. The trace_flags parameter defines the interfaces where tracing is being activated
or deactivated; other interfaces will not be affected.
- set_flags
If init_flags is set to AP_NO, this parameter
specifies whether tracing is to be activated or deactivated at the requested
interfaces. Possible values are:
- AP_YES
Tracing is to be activated at the interfaces specified
by the trace_flags parameter.
- AP_NO
Tracing is to be deactivated at the interfaces specified
by the trace_flags parameter.
If init_flags is set to AP_YES, this parameter
is ignored.
Returned
Parameters: Successful Execution |
|
If the verb executes successfully, SNAplus2 returns the following parameters:
- primary_rc
AP_OK
- secondary_rc
Not used.
Returned
Parameters: State Check |
|
If the verb does not execute because of a state error, SNAplus2
returns the following parameters:
- primary_rc
AP_STATE_CHECK
- secondary_rc
- AP_INVALID_TARGET
The back-level support software is not running on
the target server.
Appendix A “Common
Return Codes” lists further
secondary return codes associated with AP_STATE_CHECK,
which are common to all NOF verbs.
Returned
Parameters: Other Conditions |
|
Appendix A “Common
Return Codes” lists further
combinations of primary and secondary return codes that are common
to all NOF verbs.
Printable version
