This document describes step-by-step how to install Predict under the following operating systems:
BS2000
z/OS
z/VSE
The steps to be taken depend on which installation method you choose: first-time installation or inplace conversion.
This document covers the following topics:
When used in this document, the notation
vrs or
vr represents the relevant product
version (see also Version in the
Glossary).
The following prerequisites must be met when using Predict on mainframe platforms.
The products listed below must be installed in order to use Predict.
| Product Name (Product ID) | Minimum Requirements |
|---|---|
| Natural (NAT) |
Natural for Mainframes Version 8.2 SP7 or above. The following parameter settings are recommended during the installation of Predict:
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
|
| Adabas (ADA) |
Adabas Version 8.3 or above. The following Adabas parameter should be set during the installation of Predict:
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. |
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.3 or above. |
| Adabas Native SQL (SQL) |
Adabas Native SQL Version 2.4 or above. |
| Adabas SQL Server (ESQ) |
Adabas SQL Server Version 1.4 SP2 or above On mainframes, Interactive Facilities of Adabas SQL Server must be installed within Natural. |
| 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 8.2 SP7 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 10 and hotfix PA26127, 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 8.2 SP7 or above. |
| Natural Business Services (NBS) |
Natural Business Services Version 8.2 SP2 or above. |
| Natural Development Server (NDV) |
Natural Development Server Version 8.3 SP4 or above. |
| Natural SQL Gateway (NSB) |
The Natural SQL Gateway version that corresponds to your Natural version on the client. CONNX Version 13 or above on the server. |
| webMethods EntireX |
10.1 for z/OS or above |
Although it may be technically possible to run versions of other Software AG products which are older than the ones listed above with a new version of Predict, this is not recommended because, for legal reasons, Software AG 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 AG products which are older than the ones listed above.
| 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 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 UNIX platform, Entire Net-Work must be used. For details concerning each platform, see the corresponding Natural Installation documentation.
Note:
Predict Application Control 2.6 SP1 with Cumulative Fix 6 or
above is required when using Predict.
The PCF (Predict Control File) must be converted to Predict Version 8.3 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 of the PCF is the same as the Coordinator FDIC of the Predict file, perform the following steps:
Start a Natural session with FDIC=(DBnr,Fnr) of PCF.
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 of the PCF is not the same as the Coordinator FDIC of the Predict file, perform the following steps:
Load the Coordinator FDIC contained in data set/file PRDvrs.SYSF using the ADALOD utility (Job I050, Step 0601).
Start a Natural session with FDIC=(DBnr,Fnr) of PCF.
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
You can migrate data from Predict 8.4 to PAC 2.6 or above.
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 UNIX host. Predict rules can only be used by accessing Predict on a UNIX 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.
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.
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:
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.
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!
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 UNIX 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 UNIX 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.
The method used for installing Predict depends on your operating system environment.
For these operating systems, the installation of Software AG 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.
If you are using Software AG's System Maintenance Aid (SMA) for the installation process, perform the following before generating jobs:
Load the SMA table data as described in the SYSTEM MAINTENANCE AID documentation (if you have not already done so).
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.4 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.
The installation medium contains the data sets (or files for BS2000, z/OS and z/VSE) listed in the table below. The sequence of the data sets/files is shown in the Software AG Product Delivery Report which accompanies the installation medium.
The following data sets/files are required to install Predict. The data sets/files delivered (X) depend on the operating system on which you are installing.
| Data Set/File Name | BS2000 | z/OS | z/VSE | Contents |
|---|---|---|---|---|
| PRDvrs .JOBS | X | X | Sample installation jobs. | |
| PRDvrs .Tape | Sample installation jobs. | |||
| PRDvrs .INPL | X | X | X | Natural modules of Predict in INPL format. This data set/file also contains Predict error messages. |
| PRDvrs .SYSF | X | X | X | Predict system file in Adabas ADAULD format without database description. |
| PRDvrs .DATA | X | X | X | Predict description of Predict 8.4 in Migrate 8.4 format. |
| PRDvrs .DEMO | X | X | X | Predict Demo DB in Migrate 8.4 format. This includes sample files such as EMPLOYEES and VEHICLES and other sample data. |
| PRDvrs .LIBJ | X | Sample installation jobs. | ||
| PRDvrs .DE44 | X | X | X | List of modules no longer used by Predict since version 4.4. |
| PRDvrs .DE45 | X | X | X | List of modules no longer used by Predict since version 4.5. |
| PRDvrs .DE46 | X | X | X | List of modules no longer used by Predict since version 4.6. |
| PRDvrs .DE82 | X | X | X | List of modules no longer used by Predict since version 8.2. |
| PRDvrs .DE83 | X | X | X | List of modules no longer used by Predict since version 8.3. |
| PRDvrs .DE84 | X | X | X | List of modules no longer used by Predict since version 8.4. |
The steps required to copy the contents of the installation medium to disk depend on your operating system environment.
When used in this document, the notation
vrs or
vr represents the relevant product
version (see also Version in the
Glossary).
Copy the files (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 files 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 files from CD-ROM, refer to the README.TXT file on the CD-ROM.
If you are not using SMA and want to copy the files from tape, follow the instructions in this section.
This section explains how to copy all files from tape to disk.
This step is not necessary if you have already copied the library
SRVvrs.LIB from another Software AG
installation tape. For further information, refer to the element
#READ-ME in this library. The library
SRVvrs.LIB is stored on the tape as a
sequential file named SRVvrs.LIBS
containing LMS commands. The current version
vrs can be obtained from the
Software AG Product Delivery Report.
Execute the following commands to convert
SRVvrs.LIBS into an LMS library:
/IMPORT-FILE SUPPORT=*TAPE(FILE-NAME=SRVvrs.LIBS,- / VOLUME=volser, DEV-TYPE=tape-device) /ADD-FILE-LINK LINK-NAME=EDTSAM, FILE-NAME=SRVvrs.LIBS,- / SUPPORT=*TAPE(FILE-SEQ=3), ACC-METH=*BY-CAT,- / BUF-LEN=*BY-CAT, REC-FORM=*BY-CAT, REC-SIZE=*BY-CAT /START-EDT @READ '/' @SYSTEM 'REMOVE-FILE-LINK EDTSAM' @SYSTEM 'EXPORT-FILE FILE-NAME=SRVvrs.LIBS' @WRITE 'SRVvrs.LIBS' @HALT /ASS-SYSDTA SRVvrs.LIBS /MOD-JOB-SW ON=1 /START-PROG $LMS /MOD-JOB-SW OFF=1 /ASS-SYSDTA *PRIMARY
where:
tape-device is the device
type of the tape, for example, TAPE-C4, and
volser is the VOLSER of the
tape (see the Software AG Product Delivery
Report).
Call the procedure P.COPYTAPE in the library
SRVvrs.LIB to copy the procedure
COPY.PROC to disk:
/CALL-PROCEDURE (SRVvrs.LIB,P.COPYTAPE), - / (VSNT=volser, DEVT=tape-device)
If you use a TAPE-C4 device, you can omit the parameter
DEVT.
Enter the procedure COPY.PROC to copy all product files to
disk:
/ENTER-PROCEDURE COPY.PROC, DEVT=tape-device
If you use a TAPE-C4 device, you can omit the parameter
DEVT.
The result of this procedure is written to the file
L.REPORT.SRV.
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.
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.
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.
Execute hilev.COPY.JOB to copy
single, multiple, or all data sets to your disk.
Entire Net-Work requires some Adabas modules. For systems where Adabas is not installed, these modules are supplied on the installation tape in the Adabas limited libraries (WALvrs). See the Software AG Product Delivery Report for specific information regarding these limited libraries.
Software AG recommends that you concatenate the Adabas limited (WAL) libraries with the Entire Net-Work (WDX) load library first in the sequence.
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 the data sets .LIBJ,
.LIBR and .LICS (if supplied) from tape to disk. All
other data sets can be installed directly from the tape.
Modify the following sample job according to your requirements:
* $$ JOB JNM=LIBRCAT,CLASS=0, + * $$ DISP=D,LDEST=(*,UID),SYSID=1 * $$ LST CLASS=A,DISP=D // JOB LIBRCAT * ***************************************** * STORE COPYTAPE.JOB IN LIBRARY * ***************************************** // ASSGN SYS004,nnn // MTC REW,SYS004 // MTC FSF,SYS004,4 ASSGN SYSIPT,SYS004 // TLBL IJSYSIN,'COPYTAPE.JOB' // EXEC LIBR,PARM='MSHP; ACC S=lib.sublib' /* // MTC REW,SYS004 ASSGN SYSIPT,FEC /* /& * $$ EOJ
where:
nnn is the tape address,
and
lib.sublib is the library
and sublibrary in which the data set COPYTAPE.JOB is to be
stored.
Execute the job to copy the data set COPYTAPE.JOB to
disk.
COPYTAPE.JOB contains the JCL required to copy the data
sets .LIBJ, .LIBR and .LICS from tape to
disk.
Modify COPYTAPE.JOB according to your requirements and set
the disk space parameters as appropriate.
Execute COPYTAPE.JOB to copy the data sets
.LIBJ, .LIBR and .LICS to your disk.
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.