Space banner This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Task 7 Deploying Session Monitor

This topic contains considerations to be aware of and tasks to perform when you deploy Session Monitor.

Depending on your environment, review Task 3 Configure Session Monitor — New installation if you are deploying a new install or Upgrading if you are deploying an upgrade.

As an alternative to completing an entire Session Monitor installation on each LPAR on which you plan to use Session Monitor, the product contains the following sample batch jobs to assist in copying the Session Monitor installation from the current LPAR location to another LPAR:

  • QQFCOPY1—dynamically built and uses the high-level qualifier specified for the SMP/E Target libraries
  • QQFCOPY2—static sample that requires editing of the data sets before submission.

These batch jobs utilize the Batch TSO Transmit function to send the identified data sets to the specified LPAR or UserID. These batch jobs are stored in the .INSTALL library used. You can use them after the original installation has been completed.

Both samples require editing of the Batch TSO Transmit command (XMIT) to identify the destination LPAR and TSO UserID that will receive the identified data sets. For more information, see IBM documentation TSO/E Primer.

Important

Roles involved:

  • z/OS Security Administrator
  • Session Monitor Installer
  • z/OS System Programmer.

Complete the following task to deploy Session Monitor.

Task 7.1 Target library deployment

After the product installation is complete, edit the sample jobs according to their Usage Notes. When submitted for execution, the jobs package the specified data sets and transmit them to the specified LPAR and TSO userID. The specified userID must log on to the specified LPAR and use the TSO RECEIVE command to receive the data sets into their new location. If desired, the TSO RECEIVE command allows to rename the data sets.

The customizations needed to use the newly transmitted libraries include, but are not limited to, those in the following tasks.

Task 7.1.1 Create Global Recording request file

Use .INSTALL library member GRDBDEF to create and initialize a unique Global Recording request file for the new LPAR.

Important

Do not be share this file across multiple LPARs.

Task 7.1.2 Install HSCM PARMLIB member

  1. Copy the PARMLIB member to the new LPAR.
  2. Update the following specifications:
    • The product file specifications if they were renamed
    • The specifications needed for web-based reporting and Reporting
    • The product default jobcard
    • The Global Recording Request File specification
  3. Install the HSCM member into the CMSC on the new LPAR.

Task 7.1.3 Create web-based reporting elements

Copy all elements installed on USS HFS/ZFS paths, but only if Web-Based Reporting and Archiving were installed. If either function is used, you must verify the required elements on the new location.

Task 7.1.4 Review manual tasks

Validate all tasks detailed in the Manual Tasks list for the new LPAR location.

Task 7.1.5 Install PROCLIB members

You might need to update, validate, and install all elements installed into the original LPAR’s PROCLIB data set into the PROCLIB on the new LPAR.

Task 7.1.6 Create Security Rules

Re-create and validate all Security Rules on the new LPAR if the Security Package database (RACF/ACF2/Top Secret) is not shared across LPARs.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*