Transaction program profiles

If you write a transaction program in REXX and you plan to run the program as an inbound TP, you have to create a transaction program (TP) profile for the exec. The profile is required for inbound or attached TPs. The transaction program (TP) profile consists of a set of JCL statements that you store in a TP profile data set on MVS™. The following figures provide example JCL for transaction program (TP) profiles. For more information about TP profiles, see z/OS MVS Planning: APPC/MVS Management.

Figure 1 shows example JCL for an exec that you write for non-TSO/E address spaces.

Figure 1. Example JCL for TP profile for a Non-TSO/E REXX exec

//JOBNAME  JOB  parameters
//STEPNAME EXEC PGM=IRXJCL,PARM='exec_member_name argument'
//SYSPRINT DD   SYSOUT=A
//SYSEXEC  DD   DSN=exec_data_set_name,DISP=SHR
//SYSTSIN  DD   DSN=input_data_set_name,DISP=SHR
//SYSTSPRT DD   DSN=output_data_set_name,DISP=SHR

Figure 2 shows example JCL for an exec that you write for a TSO/E address space.

Figure 2. Example JCL for TP profile for a TSO/E REXX exec

//JOBNAME  JOB  parameters
//STEPNAME EXEC PGM=IKJEFT01,PARM='exec_member_name argument'
//SYSPRINT DD   SYSOUT=A
//SYSEXEC  DD   DSN=exec_data_set_name,DISP=SHR
//SYSTSPRT DD   DSN=output_data_set_name,DISP=SHR
//SYSTSIN  DD   DUMMY