Quest Central for DB2 - Systems Programmer Installation Steps

This document contains details about the remaining steps that need to
be performed to complete the mainframe installation of Quest Central 
for DB2.

The mainframe installation wizard has already been executed, so 
six Quest Central files now reside on the mainframe and have the 
temporary high-level qualifier that was specified by the user that
executed the wizard; for documentation purposes, these files are 
referred to by the placeholder temphlq. The actual value entered for
this high-level qualifier can be located at the top of this document.  

FILE             DESCRIPTION
---------------  -----------

temphlq.SAMPXMI  The SAMPLIB partitioned dataset, converted by the TSO
                 TRANSMIT command to flat-file format for transfer to 
                 the mainframe

temphlq.JCLLIB   A customized partitioned dataset containing members 
                 required by the systems programmer to complete the 
                 mainframe component installation

temphlq.LOADXMI  The LOADLIB partitioned dataset, converted by the TSO
                 TRANSMIT command to a flat-file format that can be 
                 transferred to the mainframe

temphlq.PARMLIB  A customized partitioned dataset containing the 
                 QPAGENT parameter member, QPAGTPRM

temphlq.QCINST   A customized JCL stream that can run TSO in batch 
                 mode to copy temphlq.QSMSG, temphlq.PARMLIB, and 
                 temphlq.JCLLIB to their permanent location and to 
                 convert the SAMPLIB to PDS or PDSE format and the 
                 LOADLIB to PDSE format

temphlq.QSMSG    The text file that contains the informational and 
                 error messages for Quest Central for DB2


Note:  After you submit temphlq.QCINST for execution in step 1 under 
       "TO COMPLETE THE INSTALLATION", the temporary high-level 
       qualifier is replaced by the permanent qualifier specified 
       through the wizard. You can find the value of the permhlq at 
       the top of this document or the DB2 administrator who ran the 
       wizard can tell you what the permanent qualifier actually is; 
       for documentation purposes, these files are referred to by the 
       placeholder permhlq.



TO COMPLETE THE INSTALLATION
----------------------------

1  Submit temphlq.QCINST for execution. 

   When execution completes successfully, the permhlq.SAMPLIB and 
   permhlq.LOADLIB partitioned datasets have been created.

2  If the WLM application environments specified through the wizard 
   have not yet been defined, you must do so now. Make sure these 
   environments have been defined using ISPF Application IWMARIN0. 
   z/OS V1R4.0 MVS Planning: Workload Management (SA22-7602-06)
   provides instructions for using the WLM ISPF panels.

3  Quest Central's z/OS component issues privileged operating system
   instructions and macros. To ensure that these programs function 
   properly, permhlq.LOADLIB must be APF-authorized. To dynamically 
   authorize the library for immediate use, please see the SETPROG 
   command in z/OS V1R4.0 MVS System Commands (SA22-7627-07).

   Note:  Be sure to add the permhlq.LOADLIB to your system’s PROGxx 
          member so that the library remains authorized after your 
          z/OS system is IPLd.

4  Copy both Workload Manager application environment members in 
   permhlq.JCLLIB to a system PROCLIB that is available when starting
   tasks. 

   Note:  These members were assigned names through the wizard. The
          values entered are specified at the top of this document.

5  Copy the Performance Monitoring agent JCL member, 
   permhlq.JCLLIB(QPAGENT), to a system PROCLIB.


6  (Optional) By default, the started task used to run DSN commands is
   called QPDSNAT. This same task can be used for multiple DB2 
   subsystems. If you do not need to change the name of this started 
   task, go on to step 7.

   Otherwise, if you do need to change the name of this started task,
   do the following:

   a  Copy permhlq.JCLLIB(QPDSNAT) into a system PROCLIB, using the 
      new name.

   b  Click to open SQL Editor.

   c  On SQL Editor’s SQL tab, enter the following DDL in the 
      upper pane:

      ALTER SPECIFIC FUNCTION QUEST.QP200DSNCOMMAND 
        RUNOPTS ‘ENVAR(“STCNAME=newname”)’

      where newname is the new name of the QPDSNAT member.

   d  Click  to execute the script.

   e  Go directly to step 8.

7  Copy the DSN command processor task member, 
   permhlq.JCLLIB(QPDSNAT), to a system PROCLIB.

8  Use TSO/ISPF option 3.4 to delete the following files:

   - temphlq.SAMPXMI    - temphlq.LOADXMI

   - temphlq.JCLLIB     - temphlq.QCINST

   - temphlq.PARMLIB    - temphlq.QSMSG

9  Confirm that the Quest Central mainframe components are completely
   installed:

   a  Run permhlq.JCLLIB(QCIVP). 

      This job verifies that the DB2 CLI has been installed and 
      bound, and tests a sample of the Quest procedures and 
      functions.

   b  Check the return code and QSPRINT message file:

      Return Code    Message                 Meaning
      -----------    -------                 -------

      0              Execution SUCCESSFUL    Success

      >4             Execution FAILED        Problems exist. Save the 
                     maxrc=xx	             job output and contact 
                                             Quest Technical Support



WHERE DO I GO FROM HERE?
------------------------

If you want to install Quest Central on another mainframe subsystem or
configure the Performance Monitoring Agent for additional subsystems, 
refer to the Install the Mainframe Components section of the Quest 
Central for DB2 Getting Started Guide.

Otherwise, installation of the Quest Central mainframe components is 
complete.



CONTACTING QUEST TECHNICAL SUPPORT
----------------------------------

If you have questions about any of this information, please contact 
Quest technical support:

Phone    949.754.8000 (between 5 am and 5 pm, Pacific Standard
         Time)
Fax      949.754.8999
E-mail   support@quest.com
Web      http://www.quest.com/support/
Mail     Quest Software
         8001 Irvine Center Drive
         Irvine, CA  92618
         USA