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_trace_file

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The set_trace_file command specifies the name of the file that SNAplus2 uses to record trace data.

If you issue a second set_trace_file command specifying a new file name for the same file type, all subsequent trace data will be written to the new file; the existing file is not removed, but further information will not be written to it.

To reset the current trace file or files while tracing is active (the existing contents of the file are discarded, but any subsequent tracing is written to the same file), issue a set_trace_file command specifying the same trace file name and backup file name as the files that are currently being used.

This command can be issued to a running node, or for client-server trace files only, to a HP-UX client computer on which the SNAplus2 software is running. To issue the command to a client computer, use the snapadmin program on the client computer without specifying a node name.

On Windows clients, client-server tracing is controlled by options in the sna.ini file. For more information, refer to the HP-UX SNAplus2 Diagnostics Guide.

Supplied Parameters

Parameter name      Type           Length     Default
[set_trace_file]
trace_file_type constant IPS
dual_files constant LEAVE_UNCHANGED
trace_file_size decimal 1000000
file_name character 80 (none specified)
file_name_2 character 80 (none specified)

Supplied parameters are:

trace_file_type

The type of trace file. Possible values are:

CS

File contains tracing on data transferred across the SNAplus2 LAN between the specified computer and other nodes. This type of tracing is activated by the set_cs_trace command.

BCK_CS

File contains tracing on data transferred across the SNAplus2 LAN between a current-level server and back-level computers. This type of tracing is activated by the set_bck_cs_trace command.

TN_SERVER

File contains tracing on the SNAplus2 TN server component.

IPS

File contains tracing on kernel components for the specified node. This type of tracing is activated by the set_trace_type or add_dlc_trace command.

dual_files

Specifies whether tracing uses one file or to two files. Possible values are:

YES

Tracing uses two files. When the first file reaches the size specified by trace_file_size, the second file is cleared, and tracing continues to the second file. When this second file reaches the size specified by trace_file_size, the first file is cleared, and tracing continues to the first file. This ensures that tracing can continue for long periods without using excessive disk space; the maximum space required is approximately twice the value of trace_file_size.

NO

Tracing uses one file.

LEAVE_UNCHANGED

Leave the dual_files setting unchanged from the existing definition. (When the SNAplus2 software is started, the initial default is to use two files.)

trace_file_size

The maximum size of the trace file, in bytes. To continue using the existing trace file size definition, specify 0.

If dual_files is set to YES, tracing switches between the two files when the current file reaches this size. If dual_files is set to NO, this parameter is ignored; the file size is not limited.

You may need to increase the size of the trace files according to the size of the SNAplus2 client-server network to allow for the volume of trace information generated in larger systems. Consider increasing the trace file size on a server to allow for large numbers of clients or users accessing the server.

file_name

Name of the trace file, or the name of the first trace file if dual_files is set to YES. To continue using the file name specified on a previous set_trace_file command, do not specify this parameter.

To create the file in the default directory for diagnostics files, /var/opt/sna, specify the file name with no path. To create the file in a different directory, specify either a full path or the path relative to the default directory. If you include the path, ensure that it is a valid path (either a path relative to the application's working directory or a full path) on any computer to which this command is issued.

file_name_2

Name of the second trace file; this parameter is used only if dual_files is set to YES. To continue using the file name specified on a previous set_trace_file command, do not specify this parameter.

To create the file in the default directory for diagnostics files, /var/opt/sna, specify the file name with no path. To create the file in a different directory, specify either a full path or the path relative to the default directory. If you include the path, ensure that it is a valid path (either a path relative to the application's working directory or a full path) on any computer to which this command is issued.

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

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

primary_rc

PARAMETER_CHECK

secondary_rc

Possible values are:

INVALID_FILE_NAME

The file_name or file_name_2 parameter was not set to a valid HP-UX file name, or file_name_2 was not specified when changing from a single trace file to dual trace files.

INVALID_FILE_TYPE

The trace_file_type parameter was not set to a valid value.

State Check

No specific state errors, other than those listed in Appendix A “Common Return Codes from snapadmin Commands” occur for this command.

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.