HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
QUERY_ACTIVE_TRANSACTION
active_transaction_data.dest_ms_appl_name
Application name of the destination application for the transaction. This name is normally an 8-character
EBCDIC string, using type-1134 characters (uppercase A–Z and numerals
0–9); alternatively, it can be one
of the MS Discipline-Specific Application Programs specified in Systems Network Architecture: Management
Services Reference (see Related Publications).
active_transaction_data.fq_req_loc_cp_name
Fully qualified control point name of the transaction requestor. The name is a 17-byte EBCDIC string, right-
padded with EBCDIC spaces. It consists of a network ID of up to 8 A-string characters, an EBCDIC dot
(period) character, and a network name of up to 8 A-string characters.
active_transaction_data.req_agent_appl_name
Application name of the transaction requestor. This name is normally an 8-character EBCDIC string, using
type-1134 characters (uppercase A–Z and numerals 0–9); alternatively, it can be one of the MS Discipline-
Specific Application Programs specified in Systems Network Architecture: Management Services Reference
(see Related Publications).
active_transaction_data.seq_num_dt
Sequence number date/time correlator (17 bytes long) of the original transaction, as defined in the IBM SNA
Formats manual.
3.90.4 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_ACTIVE_TRANSACTION
The control point name, application name, or sequence number correlator did not match that of an
active transaction.
AP_INVALID_LIST_OPTION
The list_options parameter was not set to a valid value.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK
,
which are common to all NOF verbs.
3.90.5 Returned Parameters: Function Not Supported
If the verb does not execute successfully because the local node configuration does not support it, SNAplus2 returns
the following parameters:
primary_rc
AP_FUNCTION_NOT_SUPPORTED
The local node does not support MS network management functions; this is defined by the
mds_supported parameter on the DEFINE_NODE verb.
3.90.6 Returned Parameters: Other Conditions
Appendix B, Common Return Codes lists further combinations of primary and secondary return codes that are
common to all NOF verbs.
345