Requesting a User-Level or Group-Level TP Profile
When setting up the APPC/MVS network, your APPC administrator creates a TP profile to contain scheduling and security information that might be necessary to run your TP in MVS. The APPC administrator can submit batch jobs to update entries in the TP profile.
A user-level TP profile is a TP profile that specifies that only a single user can execute a TP or access the TP's profile. A user-level TP profile prevents other system users from accessing the TP while it is still under test. A group-level TP profile is a TP profile that specifies that a specific group of users can run a TP or access the TP's profile.
- Your user ID, as it is known to your security system (if you are using RACF, this might be your TSO/E user ID).
- The 1- through 64-character TP name that the calling partner passes on its Allocate request to the TP under test.
- An "active status" of YES (to activate the TP).
- The name of a transaction scheduler exit, if your TP is not scheduled
by the APPC/MVS transaction scheduler, ASCH.
If your TP uses another scheduler, the rest of the profile contents will vary. If your TP uses the APPC/MVS transaction scheduler, provide the following additional information:
- SYSOUT and account tailoring (whether you want the TP's SYSOUT and account information to be tailored with information from your RACF profile).
- Scheduler class (defined by a system programmer).
- TP schedule type (standard or multi_trans).
- JCL, including a job statement, to schedule and attach the program. Use a unique jobname to help track and debug the TP.
- The name of a data set for the TP message log to record transaction program events. The default name of the TP message log is ‘&SYSUID.&SYSWUID.&TPDATE.&TPTIME.JOBLOG’.
- The KEEP_MESSAGE_LOG parameter value: ALWAYS or ERROR. For testing, use
ALWAYS.
Note: The JCL can include conditional statements to print the TP message log on selected error conditions.
- The status of the TP message log (new, old, or mod).
- Any SMS storage, management, or data classes for the TP message log.
When creating a group-level TP profile, the APPC administrator can replace the user ID defined in the user-level profile with a RACF group-id, which identifies a group of user IDs. The APPC administrator can enter RACF commands to define the group-id and connect user IDs to the group-id.
To request a group-level TP profile, provide the APPC administrator with the user IDs of all users to be assigned to the group (in addition to the above information). The APPC administrator can then replace the user ID in the TP profile with a RACF group-id.
For more information about the TP profile contents, including examples and JCL restrictions, see z/OS MVS Planning: APPC/MVS Management.