Conversion Installation

#### Search Results

Search

# Conversion Installation

The following outlines the conversion installation from a previously installed PAC installation. When converting from a previous version of PAC to version 2.7.1, perform the following steps after copying the tape contents to disk.

- Upgrading PAC

- Converting the ACF and the PCF Data

- Upgrading PAA

- Converting the FPAA Data

## Upgrading PAC

#### Step 1: Deleting old PAC/PAA System Programs

Job I051, Steps 1700, 1701, 1702, 1703, 1704 and 1705

- Backup all of the following system libraries and modules mentioned then perform the following tasks:

  - Copy the modules PQPNPUR and PRDPACVW from library SYSPAC into a different library.

  - Delete the system libraries SYSPAC, SYSPACA, SYSPACUS, SYSPAA, SYSPAAA, and SYSPAAUS on the FNAT.

  - Delete the modules SYSPAC, SYSPACA, SYSPAA, SYSPAAA from library SYSTEM on the FNAT and FUSER.

  - Delete the module COMPARE and all modules where the name starts with either MIG, MG, PAC or PAA from library SYSTEM on the FNAT and FUSER.

  - Restore the modules PQPNPUR and PRDPACVW into library SYSPAC.

  This step is required because numerous PAC/PAA modules from previous versions have been discontinued.

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

Batch Job I060, Steps 0010, 0015 and 0020

Com-plete Job I080, Steps 2300, 2310 and 2320

CICS Job I080, Steps 2210, 2220 and 2230

TSO Job I080, Steps 0010, 0015 and 0020

IMS DC Job I080, Steps 2500 and 2510

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

1. 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.

   Note
   If you want to transfer objects from status External, the following settings must be specified when starting Natural: `XML=(ON,RDOC=ON),CFICU=ON,CP='xxxxxx'`.

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 n with the appropriate file number.

   NTFILE ID=210,DBID=m, FNR=n (ACF)
   NTFILE ID=211,DBID=m, FNR=n (PCF)
   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 Natural Nucleus

Job I060, Step 0020

1. Find the JCL used to link your current batch 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 1: 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

1. Before loading the INPL dataset, make a note of the PAC administrator user ID of the existing PAC system, or ask the PAC administrator to define a temporary administrator user for installation purposes. You will need this user-ID later.

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

#### Step 5: Copy LOGON000 and PACSTEP - Non Natural Security

Job I082, Step 1710

Note
LOGON000 is delivered in source format. The contents of this module shows as an example of how the various PAC required settings are to be used. It is recommended that you make the correct adaptations to fit into your own environment.

- Copy modules LOGON000 and PACSTEP from SYSPACUS to SYSTEM on FNAT using the SYSMAIN Utility.

#### Step 6: Load the PAC Jobs

Job I200, Step 1707

To load the relevant JCL texts from data set PAC27n.DATA to the ACF do the following:

1. Assign data set PAC27n.DATA to file CMWKF01

2. Execute module PACJOBLO from library SYSPAC; specify the value of its one parameter: a range of JCL text names indicating which of the texts in PAC27n.DATA should be loaded to the ACF.

   #### Example:

       PACJOBLO OS*

   This will load all jobs for operating system z/OS.

## Converting the ACF and the PCF Data

#### Step 1: Converting the ACF Data

Job I200, Step 1720

This step converts your PAC ACF data from version 2.6.n format.

1. Make sure that the logical file 210 points at your ACF and logical file 211 to your PCF. If not, restart Natural, specifying 'LFILE=(210,DBID,FNR)', 'LFILE=(211,DBID,FNR)'.

2. Execute module CONVERT from library SYSPACA, ensure that MENU is not defined as startup transaction for library SYSPACA.

   Please now continue with Customizing PAC and PAA.

#### Step 2: Converting the PCF Data

Job I200, Step 1720

The conversion of PCF data is always required when the Predict version is upgraded.

When upgrading from a previous Predict version to the current Predict version, the PAC PCF system file must conform to the current Predict version.

In order to do this:

1. Start a Natural session with your FDIC parameter pointing to your current PCF value.

2. Log on to library SYSDICCO and execute the CONVERT routine.

   A batch example is shown below.

   #### Batch Example:

       //CMSYNIN       DD      *
       SYSDICCO,DBA,DBA1
       MENU
       CONVERT VERSIONxx
       FIN

   where xx is the current Predict version (two digits, without the dot).

## Upgrading PAA

### Prerequisites

The two steps described in this section need be taken only if the PAA being upgraded is to run in an environment without an already upgraded PAC.

#### Step 1: Load PAA System Programs

Job I061, Step 1700

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

## Converting the FPAA Data

#### Step 1: Execute the CONVERT module

Job I200, Step 1715

This step converts your PAA data from version 2.6.n to 2.7.1 format.

1. Make sure that logical file 178 points at your FPAA. If not, restart Natural, specifying 'LFILE=(178,DBID,FNR)'.

2. Execute module CONVERT from library SYSPAAA, specifying no parameters.

   This module does access your production FUSER / FUSERS in order to verify and or update PAA control records.

   Please now continue with Customizing PAC and PAA.

### On this page

- Upgrading PAC
- Converting the ACF and the PCF Data
- Upgrading PAA
- Converting the FPAA Data