6. DATA SOURCES › 6.10 APPC/MVS Overview › 6.10.3 APPC/MVS Accounting

6.10.3 APPC/MVS Accounting

ALL MVS ADDRESS SPACES CAN USE APPC SERVICES

 When APPC/MVS is active, all local address spaces can use
 APPC services to execute cooperative programming
 applications with partner TPs.  The BATPGM, BAT_TS, BAT_ST,
 BAT_TP, and BATJOB files all have data elements that
 quantify APPC activity.  In these batch program, TSO
 session, started task, ASCH-scheduled TP, and job-level
 files, the APPC-related measurements are derived from the
 APPC Resource section of the SMF type 30 Common
 Address Space records.

 The APPC Resource Section includes such measurements as the
 total number of APPC conversations allocated (PGMCOALC and
 JOBCOALC) and the amount of data sent and received during
 the conversations (PGMDATAS, JOBDATAS, PGMDATAR, and
 JOBDATAR).  Duplicate accounting issues exist for the data
 sent and received data elements, and care should be
 exercised when using them for data traffic analysis and
 chargeback purposes.  These issues are thoroughly discussed
 in the Data Dictionary entries for the elements.

APPC/MVS ASCH-SCHEDULED TRANSACTION PROGRAMS

 Two Batch Information Area files provide information about
 the Transaction Programs (TPs) executed in the APPC/MVS
 ASCH-managed address spaces.

 THE BAT_TP FILE

 Like the BAT_ST and BAT_TS files, the APPC/MVS TP Activity
 file (BAT_TP) is a parallel file to the Batch User Program
 Activity file (BATPGM).  It is created from the SMF type 30
 Common Address Space Work records and provides an address
 space perspective of ASCH-scheduled TPs running in the APPC
 subordinate address spaces.  The BAT_TP file contains all
 of the paging, memory utilization, CPU times, and other
 address-space-related measurements, but does not provide
 good accountability back to the partner TP that requested
 the ASCH-scheduled TP represented by the record.  In fact,
 the BAT_TP observation does not provide such important
 information as the scheduling type (standard or multi-
 trans), TP name, profile, or class.  And, when the TP is a
 multi-trans scheduled TP, the resource utilization data
 involving many individual transactions or conversations
 with partner TPs is summarized together in the type 30
 record, and thus the BAT_TP observation.

 For these reasons, the BAT_TP file is not a good candidate
 for APPC/MVS transaction accounting, but, if required,
 step-level chargeback is supported by CA MICS Accounting
 and Chargeback Option.

 THE BATATP FILE

 The APPC/MVS Transaction file (BATATP), on the other hand,
 satisfies all of the requirements for accounting.  It is
 created from the SMF type 33 APPC/MVS TP Accounting record
 and has the following characteristics:

 o A single DETAIL timespan observation is created for each
   transaction (conversation).

 o The partner TP that requested the execution is identified
   by RACF user ID (RACFUSID) and group ID (RACFGRID).

 o The accounting information of the requesting partner TP
   is present (ACTFLD1 - ACTFLDn).

 o The requesting partner's Network Identifier (ATPNETID)
   and LU name (ATPPLU) are provided.

 o The TP type (ATPTYPE), class (ATPCLASS), profile
   (ATPPROF), and name (ATPNAME) are provided.

 o Resource utilization measurements are provided.

     ATPTCBTM - TP TCB CPU Time
     ATPSRBTM - TP SRB CPU Time
     ATPCPUTM - TP TCB+SRB CPU Time
     ATPTCNT  - Total Device Connect Time
     ATPBLKTR - Blocks Transferred
     ATPDATAR - Data Received (Bytes)*
     ATPDATAS - Data Sent (Bytes)*

     * Carefully read the Data Dictionary entries for Data
       Received and Data Sent.  Duplicate accounting
       possibilities exist with these elements.

 APPC/MVS can be implemented with a variety of security
 requirements.  In order to guarantee accountability back to
 the requesting TP, it is important that your APPC/MVS
 administrator fully understand the implications of the
 various security options.  We recommend that the APPC/MVS
 environment be implemented so that user IDs and passwords
 are required from TPs requesting APPC services.

 The BATATP file is the best choice for APPC/MVS
 ASCH-scheduled TP accounting and chargeback purposes
 because it provides transaction level granularity and
 accountability back to the requesting partner.

 The Batch and Operations Analyzer provides an account code
 derivation exit routine (APPCRTE), discussed in Section
 7.2.3, that is used to set the ACCTNOx variables.  CA MICS
 Accounting and Chargeback Option provides complete
 accounting support for the BATATP file.