Manually configuring RTCS
If you do not use OZI Customization to configure RTCS, complete the steps in the following table to manually configure a target z/OS image to run RTCS.
Table 1. Tasks to manually configure RTCS
Task | Description | See |
|---|---|---|
1 | (optional, but recommended) Create the production RTCS subsystem program library (POSZRTCS). | |
2 | (optional, but recommended) Create the production RTCS product program library (POSZLINK). | |
3 | (optional, but recommended) Create the production RTCS hypertext document library (POSZHTML). | |
4 | APF-authorize the RTCS subsystem program library and the RTCS product program library. | |
5 | Allocate a VSAM LDS cluster for the RTCS system registry. | |
6 | Ensure the availability of sufficient common area data spaces. | |
7 | Ensure the availability of sufficient system linkage indexes (LXs). | |
8 | Add RTCS programs to the z/OS PPT. | |
9 | Select an SSID for the RTCS subsystem control address space. | |
10 | Guarantee the availability of an SSID for exclusive use by the RTCS subsystem. | |
11 | Create and customize the RTCS Initiator started task PROC. | |
12 | Create the RTCS subsystem started task PROC. | |
13 | Create the RTCS Generalized Server started task PROCs. | |
14 | Establish ESM user IDs for RTCS address spaces. | |
15 | Start RTCS. | |
16 | Add the RTCS start command to SYS1.PARMLIB or the logical PARMLIB data set for the z/OS image. |