Installation Prerequisites

#### Search Results

Search

# Installation Prerequisites

This document describes step-by-step how to install Predict under the z/OS operating system.

Note
Starting with Natural for Mainframe version 9.2, BS2000 and VSE platforms are no longer supported. Instead, Software AG promotes applications for z/OS or re-hosting to Linux and Cloud. However, some Add-On products still run with older versions of Natural and therefore will still be able to support BS2000 or VSE platforms.

The steps to be taken depend on which installation method you choose: first-time installation or inplace conversion.

This document covers the following topics:

- Product Requirements

- Using Predict in Heterogeneous Environments

- Installation Jobs/Procedures

- Using System Maintenance Aid

- Installation Medium

- Copying the Installation Medium Contents to Disk

- Which Installation Method?

#### Notation vrs or vr:

When used in this document, the notation `vrs` or `vr` represents the relevant product version (see also Version in the Glossary).

## Product Requirements

The following prerequisites must be met when using Predict on mainframe platforms.

- Product Requirements

- Other Related Software GmbH products

- Other Related Products

- Entire Net-Work

- Special Considerations For Predict Application Control

- Accessing the Dictionary Server with Natural for Windows

### Product Requirements

The products listed below must be installed in order to use Predict.

Product Name (Product ID) | Minimum Requirements
--- | ---
Natural (NAT) | Natural for Mainframes Version 9.2 SP2 or above. We recommend to apply the current zaps. For further information, please refer to the Natural documentation. The following parameter settings are recommended during the installation of Predict: MADIO=0 MAXCL=0 MT=0 RI=OFF. The Natural editor must be installed. The Software AG Editor is required for this version of Predict. You are recommended to set the size of the editor buffer pool to 1024k. If you are using System Maintenance Aid (SMA), the necessary modules are linked when the SMA parameter `SAG-EDITOR` is set. If you are installing without SMA, see the Natural Installation for Mainframes documentation.
Adabas (ADA) | Adabas Version 8.5 or above. The following Adabas parameter should be set during the installation of Predict: NISNHQ = 700 or greater AOSASM must be linked to the Batch Natural nucleus if AOS is installed. You are recommended to load the Predict system file and the Coordinator FDIC file with index compression.

### Other Related Software GmbH products

These products are not necessary in order to use Predict, but if they are installed, the following prerequisites must be met.

Product Name (Product ID) | Minimum Requirements
--- | ---
Adabas Online Services (AOS) | Adabas Online Services Version 8.5 or above.
Adabas Native SQL (SQL) | Adabas Native SQL Version 2.4 or above.
Entire System Server (NPR) | Entire System Server Version 3.6 SP2 or above.
Natural Security (NSC) | The Natural Security version that corresponds to your Natural version.
Natural ISPF (ISP) | Natural ISPF Version 9.2 SP1 or above.
Natural for Windows (NAT) | Natural for Windows Version 9.1 SP2 or above.
Predict Application Control (PAC) | Predict Application Control Version 2.6 SP1 with Cumulative Fix 18 or above.
Con-form (CMF) | Con-form Version 3.4 SP3 or above.
Con-nect (CNT) | Con-nect Version 3.4 SP3 or above. If Con-nect is installed at your site, copy the following modules from SYSCNT2 to SYSDIC to enable the transfer of texts to and from Con-nect: Z-ADD11A, Z-DIS11, Z-ERA11, Z-GET11B, Z-GET11C. See Application Programming Interface in the Con-nect Administration documentation for additional modules that must be copied.
Predict SYSHELP | If SYSHELP is used, you must copy the SYSH* routines from library SYSDICH to a steplib of your application because some routines have changed.
Super Natural (NSN) | Super Natural Version 9.2 SP1 or above.
Natural Business Services (NBS) | Natural Business Services Version 8.2 SP2 or above.
Natural Development Server (NDV) | Natural Development Server Version 9.2 SP1 or above.
webMethods EntireX | 10.1 for z/OS or above

Although it may be technically possible to run versions of other Software GmbH products which are older than the ones listed above with a new version of Predict, this is not recommended because, for legal reasons, Software GmbH cannot continue to support such combinations and cannot make any statements about whether it is technically possible to run a new version of Predict with versions of other Software GmbH products which are older than the ones listed above.

### Other Related Products

Product Name | Minimum Requirements
--- | ---
Natural DB2 Interface | If DB2 is installed, Version 10, Release 1 or above must be installed.
Natural SQL/DS Interface | If SQL/DS is installed, Version 2, Release 2 or above must be installed.
MS Word | Microsoft Word.

### Entire Net-Work

- Entire Net-Work for Mainframes Version 6.3 or above

- Entire Net-Work for Open Systems 7.7 or above

These products are required if you are using Predict in a heterogeneous environment.

When the Predict FDIC file is shared between Natural on a mainframe and Natural on a Windows or Linux platform, Entire Net-Work must be used. For details concerning each platform, see the corresponding Natural Installation documentation.

### Special Considerations For Predict Application Control

Note
Predict Application Control 2.6 SP1 with Cumulative Fix 15 or above is required when using Predict.

#### Prerequisites

- The PCF (Predict Control File) must be converted to Predict Version 8.6 format. See the section Conversion in the Predict Administration documentation.

- A Coordinator FDIC file must be allocated to the PCF. The Coordinator FDIC of the PCF can be the same as the Coordinator FDIC of the Predict file, but does not have to be.

  #### If the Coordinator FDIC files are identical

  If the Coordinator FDIC of the PCF is the same as the Coordinator FDIC of the Predict file, perform the following steps:

  1. Start a Natural session with FDIC=(DBnr,Fnr) of PCF.

  2. Call the function Defaults > Coordinator Defaults to specify a Coordinator FDIC for the PCF. See the section Defaults in the Predict Administration Documentation.

  See also the section Define Coordinator file for PCF in the PAC/PAA Release Notes

  #### If the Coordinator FDIC files are different

  If the Coordinator FDIC of the PCF is not the same as the Coordinator FDIC of the Predict file, perform the following steps:

  1. Load the Coordinator FDIC contained in data set/file PRDvrs.SYSF using the ADALOD utility (Job I050, Step 0601).

  2. Start a Natural session with FDIC=(DBnr,Fnr) of PCF.

  3. Call the function Defaults > Coordinator Defaults to specify a Coordinator FDIC for the PCF. See the section Defaults in the Predict Administration Documentation.

- The following parameter values must be set when migrating Predict objects from the Development FDIC into PAC (job <opsys>_PREDICT-MIGRATE_IN). This is applicable to Predict migrations only.

  Step 2: Unload PRD from Development

  SSIZE=100

  Step 3: Load to Control File

  DATSIZE=85

#### Functional Scope

You can migrate data from Predict 8.6 to PAC 2.6 or above.

### Accessing the Dictionary Server with Natural for Windows

With dictionary servers, you can access remote free rules and automatic rules maintained in Predict once you have access to Predict on a mainframe or Linux host. Predict rules can only be used by accessing Predict on a Linux or mainframe server.

Note
A dictionary server (also referred to as Predict server) can be any Natural RPC server running in the same environment that Predict is installed in.

#### Starting the Server

Please read the Natural Remote Procedure Call (RPC) documentation before starting the RPC server. The dictionary server name must be known in order to set up the remote dictionary access on the client side.

#### Accessing the Server

To access the server, you need a Net-Work connection to the server's Net-Work. Please ask your data center for the appropriate settings.

Before starting Natural, define the dictionary server using the Natural for Windows Configuration Utility with the following two steps:

1. Define a logical dictionary server. For this you need to know

   - the server name of the dictionary server (DDM server) that has been defined to the EntireX Broker on the server system.

   - the node name on which this server is running. This is the name of the broker.

   Ask your data center for these names. The logical dictionary server is defined in the menu Global CONFIG File > Dictionary Server Assignments.

2. Set the parameter USEDIC (remote dictionary access) to a logical dictionary server name that has been defined in the global CONFIG file.

When running Natural using this parameter module, you must have access to the server. To check whether you are connected to the server, use the command MENU from SYSRPC to ping the server. You therefore need to define the server using the SERVER MAINTENANCE option.

Please ensure that the Server Node Classification has been set to the appropriate values. You can then use the SERVER COMMAND EXECUTION option to ping the server. The server should reply:

    I'm still up!

## Using Predict in Heterogeneous Environments

The following applies:

- If you are using Natural on the mainframe, the Predict system file FDIC must be located in the mainframe database.

- If you want to access FDIC only under Natural for Windows or Linux platforms, FDIC can be located in an Adabas database on any of these platforms.

- If you share the FDIC file between Natural on the mainframe and a Natural for Windows or Linux installation, your FDIC file must be located on the mainframe and you need to configure the translation definitions in Entire Net-Work. Add the following translation definitions to your Entire Net-Work on the mainframe:

      Translate Define ADD ID=(<FDIC-DBnr>,<FDIC-Fnr>) Field=LO, FORMAT=(A,33,X,2)
      Translate Define ADD ID=(<FDIC-DBnr>,<FDIC-Fnr>) Field=LK, FORMAT=(X,2,A,88)
      Translate Define ADD ID=(<FDIC-DBnr>,<FDIC-Fnr>) Field=LJ, FORMAT=(A,16,X,2)
      Translate Define ADD ID=(<FDIC-DBnr>,<FDIC-Fnr>) Field=L2, FORMAT=(X,2,A,32)

- For the Predict Coordinator FDIC file, the same translation definition as described above must be configured, but using the following syntax. Replace the ID parameter in the four above definitions with:

      ID=(<Coordinator-DBnr>,<Coordinator-Fnr>)

- If you are using the Predict Coordinator, it must be installed on the same platform as the main FDIC.

- Set the Coordinator defaults parameter Clear with System Utility to N.

## Installation Jobs/Procedures

For z/OS, the installation of Software GmbH products is performed by installation jobs. These jobs are either adapted manually or generated by System Maintenance Aid (SMA), see Using System Maintenance Aid.

For each step of the installation procedure described below, the job number of a job performing the respective task is indicated. This job number refers to an installation job generated by SMA. If you are not using SMA, a sample installation job of the same number is provided in the job library on the Predict installation medium; you must adapt this example job to your requirements.

## Using System Maintenance Aid

If you are using Software GmbH's System Maintenance Aid (SMA) for the installation process, perform the following before generating jobs:

1. Load the SMA table data as described in the SYSTEM MAINTENANCE AID documentation (if you have not already done so).

2. Set PRDvrs in the list of available products for your environment to 'TO BE INSTALLED'.

Then perform one of the following steps depending on the installation method you choose:

- If you are performing a First-Time Installation, adapt parameters FDIC Fnr and FDIC-DBID in the parameter group FILNUM to the required values. Then make the appropriate settings in parameter group OPTION as shown in table below.

- If you are performing an Inplace Conversion (Predict Version 4.6 is marked as 'INSTALLED' in your SMA environment), you can convert the installed version to Version 8.6 with the following settings in parameter group OPTION:

  SMA Switch | For First-Time Installation | For Migrate from Version 4.6
  --- | --- | ---
  PRD-FIRST-INSTALL | Y | N
  PRD-CONVERSION | N | Y

  Note
  Leaving a field blank is the equivalent of entering N.

See the System Maintenance Aid documentation for more information.

## Installation Medium

The installation medium contains the data sets or files for z/OS listed in the table below. The sequence of the data sets/files is shown in the Software GmbH product Delivery Report which accompanies the installation medium.

- Datasets Required for Predict

### Datasets Required for Predict

The following data sets/files are required to install Predict. The data sets/files delivered (X) depend on the z/OS operating system on which you are installing.

Data Set/File Name | z/OS | Contents
--- | --- | ---
PRDvrs .JOBS | X | Sample installation jobs.
PRDvrs .Tape |  | Sample installation jobs.
PRDvrs .INPL | X | Natural modules of Predict in INPL format. This data set/file also contains Predict error messages.
PRDvrs .SYSF | X | Predict system file in Adabas ADAULD format without database description.
PRDvrs .DATA | X | Predict description of Predict 8.6 in Migrate 8.6 format.
PRDvrs .DEMO | X | Predict Demo DB in Migrate 8.6 format. This includes sample files such as EMPLOYEES and VEHICLES and other sample data.
PRDvrs .LIBJ |  | Sample installation jobs.
PRDvrs .DE44 | X | List of modules no longer used by Predict since version 4.4.
PRDvrs .DE45 | X | List of modules no longer used by Predict since version 4.5.
PRDvrs .DE46 | X | List of modules no longer used by Predict since version 4.6.
PRDvrs .DE82 | X | List of modules no longer used by Predict since version 8.2.
PRDvrs .DE83 | X | List of modules no longer used by Predict since version 8.3.
PRDvrs .DE84 | X | List of modules no longer used by Predict since version 8.4.
PRDvrs .DE85 | X | List of modules no longer used by Predict since version 8.5.
PRDvrs .DE86 | X | List of modules no longer used by Predict since version 8.6.

## Copying the Installation Medium Contents to Disk

The steps required to copy the contents of the installation medium to disk depend on your operating system environment.

- Copying the Installation Medium Contents to a z/OS Disk

#### Notation vrs or vr:

When used in this document, the notation `vrs` or `vr` represents the relevant product version (see also Version in the Glossary).

### Copying the Installation Medium Contents to a z/OS Disk

Copy the data sets from the supplied installation medium to your disk before you perform the individual installation procedure for each component to be installed.

The way you copy the data sets depends on the installation method and the medium used:

- If you use System Maintenance Aid (SMA), refer to the copy job instructions provided in the System Maintenance Aid documentation.

- If you are not using SMA and want to copy the data sets from CD-ROM, refer to the README.TXT file on the CD-ROM.

- If you are not using SMA and want to copy the data sets from tape, follow the instructions in this section.

This section explains how to copy all data sets from tape to disk.

- Step 1: Copy Data Set COPY.JOB from Tape to Disk
- Step 2: Modify hilev.COPY.JOB on Your Disk
- Step 3: Submit COPY.JOB

#### Step 1: Copy Data Set COPY.JOB from Tape to Disk

- Modify the following sample job according to your requirements:

      //SAGTAPE JOB SAG,CLASS=1,MSGCLASS=X
      //* ---------------------------------
      //COPY EXEC PGM=IEBGENER
      //SYSUT1 DD DSN=COPY.JOB,
      // DISP=(OLD,PASS),
      // UNIT=(CASS,,DEFER),
      // VOL=(,RETAIN,SER=tape-volser),
      // LABEL=(2,SL)
      //SYSUT2 DD DSN=hilev.COPY.JOB,
      // DISP=(NEW,CATLG,DELETE),
      // UNIT=3390,VOL=SER=disk-volser,
      // SPACE=(TRK,(1,1),RLSE),
      // DCB=*.SYSUT1
      //SYSPRINT DD SYSOUT=*
      //SYSIN DD DUMMY
      //

  where:

  `tape-volser` is the VOLSER of the tape, for example: `T12345`,
  `hilev` is a valid high-level qualifier, and
  `disk-volser` is the VOLSER of the disk.

- Execute the job to copy the data set `COPY.JOB` to your disk.

#### Step 2: Modify hilev.COPY.JOB on Your Disk

- Modify `hilev.COPY.JOB` according to your requirements:

  Set `EXPDT` to a valid expiration date, for example, `99365`.

  Set `HILEV` to a valid high-level qualifier, for example, `USERLIB`.

  Set `LOCATION` to a storage location, for example, `STORCLAS=ABC` or `UNIT=3390,VOL=SER=USR123`.

#### Step 3: Submit COPY.JOB

- Execute `hilev.COPY.JOB` to copy single, multiple, or all data sets to your disk.

## Which Installation Method?

The installation method you choose depends on whether Predict is already installed at your site. There are two methods available: First-Time Installation and Inplace Conversion.

### On this page

- Product Requirements
- Using Predict in Heterogeneous Environments
- Installation Jobs/Procedures
- Using System Maintenance Aid
- Installation Medium
- Copying the Installation Medium Contents to Disk
- Which Installation Method?