Information that SMF Records for APPC/MVS Work

The following table briefly summarizes the information that SMF provides for APPC/MVS.

Table 1. SMF Records for APPC/MVS
SMF Record	When Written	Contents of Record
Type 30 (address space/time based)	For every job that uses APPC/MVS callable services	Routine type 30 information plus conversation information such as: # of conversations # of send and receive calls Amount of data sent and received
Type 33, Subtype 1 (inbound transaction based)	For an inbound conversation scheduled by the APPC/MVS transaction scheduler and for each multi-trans Get_Transaction and Return_Transaction call	Conversation information similar to that written by the type 30 record, but specific to the transaction. TP information such as: TP name Local and partner LU names User and account numbers I/O statistics Scheduling information such as: Schedule class Schedule type Specific dates and times work was received, queued, started, and ended.
Type 33, Subtype 2 (conversation based)	For all conversations on the system (inbound and outbound), including inbound conversations scheduled by the APPC/MVS transaction scheduler or processed by an APPC/MVS server, as well as all outbound conversations.	Detailed information about each conversation on the system, such as: Conversation ID Name of the TP that issued the conversation request Local and partner LU name Number of sends and receives Amount of data sent and received. When inbound conversations are processed by APPC/MVS servers, subtype 2 records also contain information about server processing, such as the specific dates and times that the conversation was: Received by APPC/MVS Added to the server's allocate queue Received by the server for subsequent processing Deallocated.

A single APPC/MVS outbound or inbound transaction program generates at least one set of SMF type 30 records for job accounting. If the transaction program is inbound and is scheduled as standard, it generates the set of SMF type 30 records and a type 33 record (subtypes 1 and 2). If the transaction program is inbound and scheduled as multi-trans, it generates the set of SMF type 30 records for the TP as a whole, an SMF 33, subtype 1 record for shell initiation and another SMF type 33, subtype 1 record for shell termination, an SMF type 33 subtype 1 record for each Get_Transaction and Return_Transaction call, and an SMF type 33, subtype 2 record at the end of each conversation (when either partner program deallocates the conversation).

For more information about SMF records for APPC/MVS, see z/OS MVS System Management Facilities (SMF).