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-UX SNAplus2 API NOF Programmer's Guide: HP-UX 11.0, 11i v1, and 11i v2 > Chapter 3 NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)

ADD_DLC_TRACE

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

This verb specifies tracing on SNA messages sent on a DLC. It can be used to activate tracing on a particular DLC, port, or LS, or on a particular session on a specified LS, and to specify which types of messages are to be traced. It can also be used to activate tracing on all DLCs, ports, and LSs. For more information about how to use SNAplus2 tracing, see the HP-UX SNAplus2 Administration Guide.

If multiple ADD_DLC_TRACE verbs relating to the same resource are issued, a message will be traced if it matches any of the verbs currently active. For example:

  • If you issue a verb to trace all messages for a port and its LSs, and then issue a second verb to trace only messages with a specified LFSID for one of the LSs owned by the port, all messages for the LS will continue to be traced (because they match the first verb). If you then use REMOVE_DLC_TRACE to remove tracing for the port, messages on the LS with the specified LFSID will continue to be traced (because they match the second verb which is still active), but other messages on this LS will not be traced.

  • If you issue a verb to trace XID messages on all resources, and then issue a second verb to trace SC and DFC messages on a particular LS, all three message types will be traced for this LS.

VCB Structure

typedef struct add_dlc_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 */
DLC_TRACE_FILTER filter; /* resource to be traced */
} ADD_DLC_TRACE;

typedef struct dlc_trace_filter
{
unsigned char resource_type; /* type of resource */
unsigned char resource_name[8]; /* name of resource */
SNA_LFSID lfsid; /* session identifier */
unsigned char message_type /* type of messages */
} DLC_TRACE_FILTER;

typedef struct sna_lfsid
{
union
{
AP_UINT16 session_id;
struct
{
unsigned char sidh;
unsigned char sidl;
} s;
} uu;
AP_UINT16 odai;
} SNA_LFSID;

Supplied Parameters

The application supplies the following parameters:

opcode

AP_ADD_DLC_TRACE

filter.resource_type

Specifies the resource to be traced, and optionally the specific message types to be traced for this resource. Possible values are:

AP_ALL_RESOURCES

Set up tracing options for all DLCs, ports, and LSs.

AP_DLC

Set up tracing options for the DLC named in resource_name, and for all ports and LSs that use this DLC.

AP_PORT

Set up tracing options for the port named in resource_name, and for all LSs that use this port.

AP_LS

Set up tracing options for the LS named in resource_name.

AP_PORT_DEFINED_LS

Set up tracing options for the port named in resource_name, and for all defined LSs (but not implicit LSs) that use this port.

AP_PORT_IMPLICIT_LS

Set up tracing options for the port named in resource_name, and for all implicit LSs (but not defined LSs) that use this port.

filter.resource_name

The name of the DLC, port, or LS for which tracing is being activated. This parameter is reserved if resource_type is set to AP_ALL_RESOURCES.

filter.lfsid

The Local Form Session Identifier for a session on the specified LS. This is only valid for resource_type AP_LS, and indicates that only messages on this session are to be traced. The structure contains the following three values, which are returned in the SESSION_STATS section of a QUERY_SESSION verb:

filter.lfsid.uu.s.sidh

Session ID high byte.

filter.lfsid.uu.s.sidl

Session ID low byte.

filter.lfsid.odai

Origin Destination Assignor Indicator.

filter.message_type

The type of messages to trace for the specified resource or session. Set this parameter to AP_TRACE_ALL to trace all messages, or specify one or more of the following values (combined using a logical OR):

AP_TRACE_XID

XID messages

AP_TRACE_SC

Session Control RUs

AP_TRACE_DFC

Data Flow Control RUs

AP_TRACE_FMD

FMD messages

AP_TRACE_SEGS

Non-BBIU segments that do not contain an RH

AP_TRACE_CTL

Messages other then MUs and XIDs

AP_TRACE_NLP

Trace Network-Layer Protocol messages

AP_TRACE_NC

Trace Network Control messages

Returned Parameters: Successful Execution

If the verb executes successfully, SNAplus2 returns the following parameters:

primary_rc

AP_OK

secondary_rc

Not used.

Returned Parameters: Parameter Check

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

primary_rc

AP_PARAMETER_CHECK

secondary_rc

Possible values are:

AP_INVALID_RESOURCE_TYPE

The resource_type parameter specified a value that was not valid.

AP_INVALID_MESSAGE_TYPE

The message_type parameter specified a value that was not valid.

Appendix A “Common Return Codes” lists further secondary return codes associated with AP_PARAMETER_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
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2003 Hewlett-Packard Development Company, L.P.