OSI/AS Configuration and Management Manual

OSI/AS Subsystem Description

OSI/AS Configuration and Management Manual—424119-001

7-6

Upward Information Flow

There are two types of completions that the TAPS process returns to the user: indication

or confirm primitives, and I/O completions. Incoming SPDUs are received by the TAPS

process and returned to the API as indication or confirm primitives.

The following PTrace example shows an incoming CN-SPDU (connect session protocol

data unit):

Indication and confirm primitives are passed by the TAPS process to the application as

completions to APS_EVENT_RECEIVE_ calls.

15:45:52:580 >000.010 #83 TAPS L5 PROV

L5 I/O Completion Su Name #Z000002 Session ID 2

File ID %H000119C0 Tag %H00000005 DCB Addr %H001AD942

Count Transferred 00200 FS Error 00000 MCW %H0001

CN(Connect) SPDU

Protocol Options: %H00 unable to rcv extended concatenated SPDUs

Version Number: %H01 Vsn 1

Token Setting Item: %H01

Release MajorSync MinorSync Data

initiator initiator initiator responder

Session User Rqmnts: %H0001

HalfDuplex

Calling S-Sel: (3) 5555 02

Called S-Sel: (3) 5555 01

User Data: (512+) 2222222222222222