Step 13: Configure the z/OS Persistent Datastore

Enter 7 on the Configure prodname RTE screen (Figure 2) to configure the ITCAM for WebSphere® Tivoli® Enterprise Monitoring Agent's storage of historical data within the z/OS® Persistent Datastore (PDS).

Note: The acronym PDS for the z/OS Persistent Datastore is distinct from, and should not be confused with, the z/OS Partitioned Dataset (dataset library) commonly known as PDS.

The Specify Persistent Datastore Values screen is displayed:

Figure 1. Specify Persistent Datastore Values menu

This figure shows the Specify Persistent Datastore Values screen, where you specify allocation parameters for the PDS datasets.

If the monitoring server was configured locally, the values initially displayed are those defined for the PDS when you built the monitoring server. You can change them now, for those files that will be allocated for the ITCAM for WebSphere Tivoli Enterprise Monitoring Agent. (You might especially want to specify a new prefix—one specific to the ITCAM for WebSphere Tivoli Enterprise Monitoring Agent—for the started tasks that will be submitted to maintain the PDS files.) When finished, press Enter; the Allocate Persistent Datastore Menu screen is displayed:

Figure 2. Allocate Persistent Datastore Menu

This figure shows the Allocate Persistent Datastore Menu, where you perform steps that allocate and configure the PDS datasets.

Enter 1 to define the allocation of PDS files. The Persistent Datastore Specifications screen is displayed:

Figure 3. Persistent Datastore Specifications screen

This figure shows the Persistent Datastore Specifications screen, where you specify allocation parameters for the PDS datasets.

Specify the allocation and maintenance parameters for these datasets.

Note the two subheadings, Lowlev and Count, under the heading Datasets in Group. The Lowlev value is the suffix for the PDS dataset. The Count value is the number of PDS datasets for this group. The PDS rotates the use of these datasets; when one fills up, data recording begins on the next dataset, and a PDS maintenance job is started to clear the filled dataset.

When you have finished, press Enter and then F3; you return to the Allocate Persistent Datastore Menu screen (Figure 2).

Enter 2 to update the PDS maintenance job's JOB information. You enter the ISPF editor on the JCL shown in figure 69:

Figure 4. Create or Edit PDS Maintenance Jobcard screen

This figure shows the Create or Edit PDS Maintenance Jobcard screen, where you create the job statement used for PDS maintenance jobs.

This job information is saved in the RKANSAM library, member KPDJOBC and used to run the PDS maintenance jobs. Update the statements as necessary, and press Enter to return to the Allocate Persistent Datastore Menu (Figure 2). Alternatively, you may press F3 to return to the Allocate Persistent Datastore Menu without updating the JCL.

Enter 3 to create the PDS maintenance JCL members. A PDS information panel is displayed.

Figure 5. PDS information panel

Press Enter. You enter the ISPF editor on the JCL shown in Figure 6.

Figure 6. JCL for creating PDS maintenance members

This figure shows the JCL that creates the PDS maintenance members.

Customize the JCL as necessary, and enter SUBMIT. Then press F3 to return to the Allocate Persistent Datastore Menu (Figure 2).

Enter 4 to submit the job that allocates the PDS files. You enter the ISPF editor on the JCL shown in Figure 7

Figure 7. JCL for allocating Persistent Datastore files

This figure shows the JCL that allocates the PDS datasets.

Customize the JCL as necessary, and enter SUBMIT. Then press F3 to return to the Allocate Persistent Datastore Menu (Figure 2).

Note: This action will normally take some time to complete while it formats the datasets for persistent storage. It may instead complete quickly because the PDS datasets already exist from a prior configuration. In this case, you need to delete these datasets, so that the job can reformat or reallocate them, and then submit the job again. The datasets to delete are named itmhlq.rtename.RKYNPDSx and itmhlq.rtename.RYNSGRPx, where itmhlq is the high-level qualifier you defined for your site's Tivoli Monitoring environment, rtename is the name you gave this runtime environment, and x is a digit, usually 1 to 3.

Enter 5 to complete PDS allocation. The first screen of the Complete Persistent Datastore Configuration process is displayed. Press DOWN (F8) to scroll through the screens:

Figure 8. Complete Persistent Datastore Configuration screen (1 of 2)

This figure shows the first screen of the PDS configuration instructions.

Figure 9. Complete Persistent Datastore Configuration screen (2 of 2)

This figure shows the second screen of the PDS configuration instructions.

While these screens are displayed, perform the following steps outside ICAT (for example, using an ISPF split):

Copy JCL members xxxxPDS1 and xxxxPDS2 (where xxxx is the STC prefix, see Figure 1) from the RKANSAM dataset listed to your system proclib (for example, SYS1.PROCLIB) so they can be submitted as started tasks.
Using your site's security system (such as RACF®), authorize the user ID under which these started tasks will run to be able to delete, allocate, and update all PDS datasets for this RTE. These datasets are named itmhlq.rtename.RKYNPDSx and itmhlq.rtename.RYNSGRPx, where itmhlq is the high-level qualifier you defined for your site's Tivoli Monitoring environment, rtename is the name you gave this runtime environment, and x is a digit, usually 1 to 3.
Verify persistent datastore configuration.

Refer to the text on the screens for details of these steps.

When you have finished these steps, press F3 to return to the Allocate Persistent Datastore Menu (Figure 2). You have completed the allocation and initialization of the Persistent Datastore for this agent; press F3 again to return to the Configure prodname RTE screen (Figure 2).