Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP 9000 Networking: HP-UX SNAplus2 Administration Command Reference > Chapter 4 Commands (remove_dlc_trace to term_node)

set_bck_cs_trace

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The set_bck_cs_trace command specifies options for back-level client-server tracing—the tracing of data sent between a current-level SNAplus2 server and a back-level server or client. This command is used only when you are in the process 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, refer to the HP-UX SNAplus2 Upgrade Guide.

This command must be issued to a node on a computer where the back-level support software is running.

Supplied Parameters

Parameter name           Type         Length       Default
[set_bck_cs_trace]
trace_flags constant ALL
init_flags constant YES
set_flags constant YES

Supplied parameters are:

trace_flags

The types of tracing required. To set tracing for all types of messages, specify one of the following values:

NONE

Do not activate tracing for any type of message.

ALL

Activate tracing for all types of messages.

To activate tracing on specific message types, select one or more of the following values (combined using a + character):

UDP

Trace UDP messages

TCP

Trace TCP messages

UDP_TEXT

Trace text strings describing UDP events

TCP_TEXT

Trace text strings describing TCP events

TEXT

Trace text strings describing other events

MS

Trace 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:

YES

Initialize tracing. The trace_flags parameter defines the required state of tracing at all interfaces.

NO

Change the state of tracing. The trace_flags parameter defines the interfaces where tracing is to be activated or deactivated; other interfaces will not be affected.

set_flags

If init_flags is set to NO, this parameter specifies whether tracing is to be activated or deactivated at the requested interfaces. Possible values are:

YES

Activate tracing at the interfaces specified by the trace_flags parameter.

NO

Deactivate tracing at the interfaces specified by the trace_flags parameter.

If init_flags is set to YES, this parameter is ignored.

Returned Parameters

No parameters are returned by SNAplus2 when this command executes successfully.

Error Return Codes

If the command cannot be executed, SNAplus2 returns a primary return code to indicate the type of error and a secondary return code to provide specific details about the reason for unsuccessful execution.

Parameter Check

No parameter errors occur for this command.

State Check

If the command does not execute because of a state error, SNAplus2 returns the following parameters:

primary_rc

STATE_CHECK

secondary_rc
INVALID_TARGET

The back-level support software is not running on the target server.

Other Conditions

Appendix A “Common Return Codes from snapadmin Commands” lists combinations of primary and secondary return codes that are common to all commands.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2001 Hewlett-Packard Development Company, L.P.