Establishing a Separate PAA Environment

#### Search Results

Search

# Establishing a Separate PAA Environment

This section describes the actions necessary for the first time installation of Predict Application Audit (PAA) and the steps required to establish a separate or additional PAA production environment to be served by a single PAC 2.7.1 system.

- Installation Procedure

## Installation Procedure

#### Step 1: Load PAA System File

Job I050, Step 1710

- Load the Predict Application Audit (PAA) file contained in dataset PAC27n.SYSF.

  Note
  If you install PAA in more than one environment, load the PAA into the additional environments directly from the installation tape. DO NOT use Adabas utilities to install the files from an existing system.

#### Step 2: Modify, Reassemble, and Link the Natural Parameter Module/s

Batch Job I060, Steps 0010 and 0015

Com-plete Job I080, Steps 2300 and 2310

CICS Job I080, Steps 2210 and 2220

TSO Job I080, Steps 0010 and 0015

IMS DC Job I080, Steps 2500 and 2510

1. Modify all Natural parameter modules used for batch and online processing with PAC. Follow the procedure below for each module:

   Note
   The size parameters are recommendations only. You may have to adapt these values to your particular environment.

   The following Natural parameter settings are recommended during the installation of PAC/PAA 2.7.1:

   CDYNAM=8 (or higher)
   ESIZE=128
   LC=ON (for use with the new COMPARE utility)
   MADIO=0
   MAXCL=0
   MT=0
   RJESIZE=8

   Note
   The ESIZE required by PAC depends on the characteristics of your migration. It is used to store individual entries in the object list when you process PAC migration events or use the Expand function. The actual size needed may be larger or smaller than 128K. If error message NAT0886 occurs, the ESIZE has been set too low and has to be set higher.

2. For online and batch processing, set: PRINTER 1 in either the NTPRINT macro or dynamically using the printer parameter.

3. Set: WORK 1,2,3 in either the NTWORK macro or dynamically using the work parameter.

   OPEN=OBJ in the NTWORK macro.

4. Specify the following NTFILE parameters for the PAC ACF and PCF files and PAA file. For each file replace m with the appropriate database number and nwith the appropriate file number.

   NTFILE ID=178,DBID=m, FNR=n (PAA)

5. Setting up NATRJE for the various TP-Monitors:

   For information about setting up and installing this functionality of Natural, please refer to the Natural Installation and Operations documentation. (Natural under CICS and Natural under IMS TM).

6. Assemble and link the Natural parameter modules.

#### Step 3: Link the Batch / Online Natural Nucleus

Job I060, Step 0020 - batch and online

1. Find the JCL used to link your current batch / online Natural nucleus. This will ensure that all INCLUDE statements specified when you built your current batch Natural nucleus are included in this step.

2. In the INCLUDE statement for the Natural parameter module, specify the name of the batch Natural parameter module that you reassembled in Step 2: Modify, Reassemble and Link the Natural Parameter Module(s)

3. Link the Natural nucleus.

#### Step 4: Load PAC/PAA System Programs

Job I061, Step 1700

- The PAC/PAA system programs are contained in the dataset PAC27n.INPL and are loaded to your Natural FNAT and FUSER system files using the Natural utility INPL.

#### Step 5: Initialize PAA

Predict Application Audit (PAA) can be initialized only after ALL installation steps have been completed successfully. Perform the following sequence of activities.

1. #### Define the PAA Libraries (With Natural Security)

   Define the libraries SYSPAAUS, SYSPAA (make SYSPAC, SYSPAAUS and SYSPACUS a steplib; SYSTEM must be specified last in the list) and SYSPAAA (people-protected=yes, make SYSPAA and SYSPAC a steplib; SYSTEM must be specified last in the list) to Natural Security.

2. #### Define the PAA-AUTH group (With Natural Security)

   PAA-AUTH is a special group of PAA users who are authorized to add, modify, and delete applications, statuses, application status links, and migration paths.

   1. Define the group PAA-AUTH to Natural Security.

   2. Add to this group all users requiring the ability to run migration events (PAA jobs) that migrate objects into production statuses.

   3. Link all users or groups requiring access to PAA Administrator Functions to the library SYSPAAA.

3. #### Customize Logon Exit (Without Natural Security)

   Job I082, Step 1710

   1. If you have not already done so for PAC, customize the user exit LOGON000 in library SYSPACUS as required. Then catalog and copy it to library SYSTEM on the FNAT using the SYSMAIN utility.

   2. Copy module PACSTEP from library SYSPACUS to library SYSTEM on the FNAT using the SYSMAIN utility.

4. #### Initialization

   Job I200, Step 1710

   Ensure that the NSC start-up transaction 'MENU' is not defined.

   1. Execute module PAAPIBEG from the library SYSPAA.

   2. With Natural Security, define online start-up transaction MENU for libraries SYSPAA and SYSPAAA.

#### Step 6: Starting PAA

1. Log on to Natural

2. Ensure that the Natural NTFILE definitions for the PAA system file is correct. If the NTFILE definitions are incorrect, you will receive a PAA initialization error and will be unable to enter the PAA system.

   Note
   The LFILE parameter may be used temporarily as a dynamic override until the Natural parameter modules are updated.

3. Invoke the PAA administration system by entering ADMIN at the NEXT prompt from library SYSPAA.