Configuring Output Manager to allow access from multiple LPARs

Prerequisites:
  • These configurations assume that each LPAR is in the same SYSPLEX, is using shared DASD, and is able to share the same security definitions.
  • Output Manager load modules must be APF authorized. For more information on how to accomplish this, refer to APF-authorize the load library and LPA library and Make Output Manager modules available.
  • The BJTISMF Output Manager program must be added to IKJTSOxx AUTHCMD, AUTHPGM, and AUTHTSF sections. For more information on how to accomplish this, refer to Update your TSO configuration
  • The ARA_HOST Output Manager configuration parameter must be set to the name of the system on which the Output Manager started task is running.

Security requirements

In order to access Output Manager, the remote LPAR/Db2® subsystem requires the same security privileges that it requires to access the collector environment. Any time you add, delete, or change the security definitions related to Output Manager, you must refresh the RACF® class on both LPARs. To do so, issue the following command on each LPAR that Output Manager viewing (of reports and archive) and administration occurs: 
SETROPTS RACLIST(XFACILIT|FACILITY) REFRESH
Provide Output Manager with READ access to the EZBDOMAIN resource:
  1. In the SERVAUTH class, locate the EZBDOMAIN resource profile. If the EZBDOMAIN resource profile does not exist, create it. The following is an example of defining the EZBDOMAIN resource in RACF:
    SETROPTS CLASSACT(SERVAUTH)
SETROPTS RACLIST (SERVAUTH)
    Note: The SERVAUTH class must be active and RACLISTed.
  2. Define the EZBDOMAIN profile and customize the APPLDATA field to contain the security domain name for the SYSPlex: 
    RDEFINE SERVAUTH EZBDOMAIN APPLDATA('security_domain_name')
  3. Provide the user ID or Group of the Output Manager started task READ access to the EZBDOMAIN profile: 
    	PERMIT  EZBDOMAIN CLASS(SERVAUTH) ID(BJTSTCU) ACCESS(READ)
  4. Refresh the SERVAUTH class to activate the changes: 
    SETROPTS RACLIST(SERVAUTH) REFRESH

Option 1: Configuring Output Manager to allow viewing archives and reports from a remote Db2 using Db2 data sharing:

  1. Set up the Output Manager Collector environment. It is recommended to follow the instructions found in Customizing Output Manager.
    Note: Specify the Db2 data sharing Group Attachment Name as the Db2 subsystem ID during the setup.
  2. Copy the customized SBJTEXEC member BJTUI used for the Output Manager Collector environment and make it available for TSO users on the LPAR running a Db2 Subsystem that is part of the same data sharing group.

Option 2: Configuring Output Manager to allow viewing archives and reports from a remote Db2 using DRDA

With DRDA, Output Manager connects to a server at another location and executes packages that have been previously bound at that server. Output Manager uses a CONNECT statement and an alias defined to substitute the three-part name used to access Db2 tables and views at a remote location.

  1. Set up the Output Manager Collector environment using the instructions found in Customizing Output Manager. This configuration will use the Db2 running on the same LPAR (through the local Db2 connection).
  2. Create a new SBJTSAMP library for remote Db2 access on each LPAR that will be used to run TSO viewers.
    Overview: BJT@CPYA is used to copy specific members from the SBJTSAMP and SBJTEXEC that was provided with the installation into a new HLQ used for customization. You then modify members BJT@PREA and BJT@JCEA to specify configuration values that will aid in creating aliases, and then submit member BJT@JCEA.
    1. Copy BJT@CPYA from your SMP/E install library to a separate JCL library.
    2. Modify the copy of BJT@CPYA to specify a new location for a copy of the specific members of the SBJTSAMP library:
      • ?BJTHLQ?: Specify the high-level qualifier for the Output Manager product libraries. This high-level qualifier was specified during the installation process, as documented in the Program Directory for Tivoli® Output Manager for z/OS®.
      • ?SAMPHLQ?: Specify a high-level qualifier for the SBJTSAMP containing the members used to set up the view-only configuration. In the following examples, the value HLQ.CPYA is used.
    3. Submit the modified version of BJT@CPYA. BJT@CPYA creates a copy of the members of SBJTSAMP required to configure the viewer sessions.
    4. Modify HLQ.CPYA.SBJTSAMP(BJT@JCEA) to replace the ?SAMPHLQ? variable with the high level qualifier for this newly copied SBJTSAMP library, and replace the ?BJTHLQ? variable with the high level qualifier for your Output Manager V3R1 product libraries.
      Important: Never run BJT@JCEA against your SMPE applied library.
    5. Modify <JOB PARAMETERS> on the job card.
    6. Modify HLQ.CPYA.SBJTSAMP(BJT@PREA). Follow instructions within the member and specify the following configuration parameters:
      • ?SAMPHLQ?: Specify the high-level-qualifier of this newly copied version of SBJTSAMP (the DSNAME of the library for this member). For example, HLQ.CPYA.
      • ?BJTHLQ?: The high-level qualifier of the new Output Manager V3R1 product libraries.
      • The following variables are optional for setting up JOB cards: ?ACCT? , ?PROGRAMMER NAME?, ?JOBCLASS?, ?MSGCLASS?.
      • ?SDSNEXIT?, ?SDSNLOAD?, ?RUNLIB?, and ?TEPPLAN?: Specify values for the Db2 subsystem where you are creating the aliases. ?SDSNEXIT? is the EXIT library for your Db2 subsystem. ?SDSNLOAD? is the Db2 LOAD library for your Db2 subsystem. ?RUNLIB? is the Db2 RUN library. ?TEPPLAN? is the plan name for the DSNTEP2 program.
      • ?DB2SSID?, ?BJTBASE?, and ?BJTQUAL?: Specify values used to create the aliases. ?DB2SSID? is the subsystem ID of the viewer. ?BJTQUAL? must be the same qualifier used on the collector system. ?DB2LOCTN? is the location name of the collector system. This is used to construct the aliases.
      • ?OWNER?: The authorization ID of the owner of the new Output Manager database. If your site has no specific security requirements for the database, set this to the user ID that submits the job to create the database.
      • ?PLANOWNER?: The authorization ID of the owner for the plans and packages. If your site has no specific security requirements for the Output Manager database, set this to the user ID that submits the jobs to BIND the packages and plans.
      • ?BJTPLAN?: The ?BJTPLAN? value in HLQ.CPYA must be the same value used on the collector system for the plan name prefix.
      • ?BJTCOL?: The ?BJTCOL? value in HLQ.CPYA must be the same value used on the collector system for the collection name.
      • ?BJTHLQ?: (This variable must be specified in two locations in BJT@PREA.) Specify the high-level qualifier of the new Output Manager V3R1 product libraries.
    7. Submit HLQ.CPYA.SBJTSAMP(BJT@JCEA). BJT@JCEA automatically modifies all of the members of the specified SBJTSAMP library according to the values specified in BJT@PREA.
  3. Create Db2 ALIAS definitions. In the new SBJTSAMP library, run the SQL statements in BJT@ALCR using SPUFI or BJT@JCUT.
  4. DROP ALIAS definitions. In the new SBJTSAMP library, run the SQL statements in BJT@ALDR using SPUFI or BJT@JCUT if you wish to remove the remote access capabilities.
  5. Bind Db2 plans and packages: from the new SBJTSAMP library, submit BJT@JCBX. Expected completion code of this job is 0000.
  6. ?BJTPLAN?: The ?BJTPLAN? value in HLQ.CPYA must be the same value that is used on the collector system for the plan name prefix.

    The package(s) must be bound on the collector system (Db2 subsystem that contains the tables.). If the collection name on the viewer system is different than the one on the collector system, the packages defined in BJT@PRBX need to be bound on both systems.

    Note: Do not use the same name for collections and plans to refer to the different database objects.
  7. Customize the Output Manager user interface to use the Db2 subsystem definitions allowing remote access:
    1. BJT@CPYA copies the SBJTEXEC BJTUI member into a library that can be accessed on the LPAR where the Output Manager ISPF interface will use remote Db2 access.
    2. When you run BJT@JCEA the following changes are made to BJTUI:
      • sdsnexit = Modified to contain the Db2 exit library for the Remote Db2 subsystem used for Output Manager viewing
      • sdsnload = Modified to contain the Db2 load library for the Remote Db2 subsystem used for Output Manager viewing
      • db2ssid = Modified the SSID to the remote Db2 subsystem id where the Db2 ALIAS definitions are stored.

Considerations for applying Output Manager PTFs when Output Manager is sharing Db2 objects (database, plans, or packages) or using Db2 Views in a multi-LPAR environment

When Output Manager is sharing the same database, plans, or packages in a multi-LPAR environment (with Db2 data sharing, with a distributed connection using DRDA protocol and ALIASes pointing to a remote Db2, or using Db2 Views), the following considerations must be made when applying Output Manager PTFs:
  • If an Output Manager PTF includes additions, deletions, or updates to SBJTSAMP BIND statements found in BJT@PRBI, BJT@PRBU, or BJT@PRBX, you must update your customized version of the SBJTSAMP BIND members on the Collector Db2 subsystem where Output Manager definitions are stored. Then, run the updates using bind JCL (BJT@JCBI, BJT@JCBU, or BJT@JCBX). On each Db2 Subsystem/LPAR for viewing, update BJT@PRBX and run BJT@JCBX to bind the plan used by the TSO session.
  • If an Output Manager PTF creates a new table (denoted by a new SBJTSAMP member BJTALTxx containing a CREATE TABLE definition along with an update to SBJTSAMP member BJT@TBCR with the same CREATE TABLE definition added), and you use DRDA to connect to the Output Manager collector started task, you must create a new alias definition (CREATE ALIAS) for the Output Manager viewer started task. If your environment uses Db2 views, you must also add a new Db2 VIEW for the new table, unless otherwise specified.
  • If an Output Manager PTF requires an existing table or tablespace to be dropped and rebuilt (denoted by a new SBJTSAMP BJTALTxx member containing a drop table or tablespace followed by a CREATE of this same table or tablespace) and your Output Manager environment uses Db2 views, those views will be dropped as a result of the table or tablespace being dropped, so the views must be rebuilt.