Adding the TP Profile to the VSAM KSDS

This discussion assumes that a VSAM KSDS already exists for TP profile information.

The APPC/MVS administration utility (ATBSDFMU) has commands for creating and modifying APPC/MVS TP profiles in the VSAM KSDS. You can use the TPADD command to add a TP profile. For a sample of using TPADD to add a variety of TP profiles, see system SAMPLIB member ATBUTIL (for example, SYS1.SAMPLIB(ATBUTIL)).

Figure 1 shows a job step that adds a DFM TP profile to SYS1.APPCTP using the TPADD command. This example can be found in system SAMPLIB member GDETPDEF (for example, SYS1.SAMPLIB(GDETPDEF) and in GDETPDEF.

Figure 1. TPADD Command Example

   //STEP     EXEC PGM=ATBSDFMU
   //SYSPRINT DD   SYSOUT=*
   //SYSSDOUT DD   SYSOUT=*
   //SYSSDLIB DD   DSN=SYS1.APPCTP,DISP=SHR
   //SYSIN    DD   DATA,DLM=XX
       TPDELETE
         TPNAME(^X'07'001)
       TPADD
         TPNAME(^X'07'001)                   <- TP key section
         ACTIVE(YES)                         <- TP attribute section
         TPSCHED_DELIMITER(##)               <------. TP scheduler section
           CLASS(A)                                 |
           JCL_DELIMITER(ENDJCL)                    |
   //GDEDFM JOB MSGCLASS=H,MSGLEVEL=(1,1),CLASS=A   |
   //GDEDFM    EXEC PGM=GDEISASB                    |
   //* CHANGE THE STEPLIB STATEMENT AS REQUIRED IF YOUR INSTALLATION
   //* DOESN'T HAVE THE LE RUNTIME DATA SET IN ITS LINK LIST.
   //*STEPLIB  DD  DSN=SYS1.SCEERUN,DISP=SHR
   //*CDRATRC DD DSN=SYS1.CDRATRC2,DISP=SHR  <- CDRA API TRACE OUTPUT
   //*SYSOUT  DD DSN=SYS1.CDRAOUT2,DISP=SHR  <- C RUNTIME MESSAGES
   //SYSOUT   DD DUMMY                       <- C RUNTIME MESSAGES (NO-OP)
   ENDJCL                                           |
   ##                                        <------'
   XX

As Figure 1 shows, each TP profile contains three sections.

TP profile key section

Consists of a TP name and a TP level (because TP level is not included in this example, TP Level defaults to SYSTEM).

The TP name for DFM must be ^X'07'001
TP level identifies which entities RACF® authorizes to access the DFM TP. It can be one of the following:
Level

Access

SYSTEM

Any user can attach the TP. This is the default if no TP level is used.

GROUP

Any member of a predefined group of users can attach the TP.

USER

A single user can attach the TP.

TP attributes section

Consists of ACTIVE(YES), which indicates that the TP status is active. If the status is set to ACTIVE(NO), the TP cannot be scheduled.

TP scheduler section

Has the following information:

Provides the JCL used to run the DFM TP. This example shows sample JOB and EXEC statements.
SCHED(A) indicates the APPC/MVS transaction scheduler for the DFM TP.
GDEDFM should have either no region size or a region size of 0K to contain cached stream files.
GDEISASB must be specified as the program to be executed on the EXEC statement.
Note: The language environment (LE) is required to use CDRA. If LE is installed and is not in the link list, SYS1.PROCLIB(DFM) and SYS1.SAMPLIB(GDETPDEF) should be modified so their STEPLIB DD statements refer to the proper LE run time library. Refer to DFMREADM in SYS1.SAMPLIB for details. SYSOUT and CDRATRC files can be allocated as RECFM=FBA, LRECL=133, and DSORG=PS for use in diagnosing CDRA problems.

TP profile definition parameters not included in this example are set to default values. For more details about adding and modifying TP profile information, see z/OS MVS Planning: APPC/MVS Management.