This document covers the following topics:
The installation of Software AG products is performed by installation jobs. These jobs are either created "manually" or generated by System Maintenance Aid (SMA).
For each step of the installation procedure described in this documentation, the job number of a job performing the corresponding task is indicated. This job number refers to an installation job generated by SMA. If you are not using SMA, an example installation job of the same number is provided in the installation job library on the Natural ISPF installation medium; you must adapt this example job to your requirements. Note that the installation job numbers on the medium are preceded by a product code (for example, ISPI061).
Information on using Software AG's System Maintenance Aid (SMA) for the installation process is provided by the System Maintenance Aid documentation.
Before you can install Natural ISPF, the following Software AG products must already be installed at your site:
Natural for Mainframes, including the Software AG Editor.
The currently supported Entire System Server releases to access operating system data (optional).
The currently supported System Automation Tools releases if Mainframe Navigation is used.
If VSAM files are used: Natural for VSAM (NVS) (optional).
For an initial installation using Adabas system files, a currently supported Adabas version is required.
If Predict is installed, a currently supported Predict version is required.
If Mainframe Navigation is used, Natural Development Server (NDV) or a Natural Remote Procedure Call (RPC) environment using EntireX is required.
The installation medium contains the following files:
| Medium file name | Description |
|---|---|
ISPvrs.JOBS |
Natural ISPF installation jobs. |
ISPvrs.INPL |
Natural ISPF programs. |
ISPvrs.ERRN |
Natural ISPF error messages. |
ISPvrs.SYS1 |
Natural ISPF empty versioning file. |
ISPvrs.SYS2 |
Natural ISPF empty container file. |
ISPvrs.DATA |
Natural ISPF Predict file descriptions. |
ISPvrs.VINI |
Natural ISPF VSAM init file. |
| Medium file name | Description |
|---|---|
ISPvrs.INPL |
Natural ISPF programs. |
ISPvrs.ERRN |
Natural ISPF error messages. |
ISPvrs.LIBJ |
Natural ISPF jobs. |
ISPvrs.SYS1 |
Natural ISPF empty versioning file. |
ISPvrs.SYS2 |
Natural ISPF empty container file. |
ISPvrs.DATA |
Natural ISPF Predict file descriptions. |
ISPvrs.VINI |
Natural ISPF VSAM init file. |
| Medium file name | Description |
|---|---|
ISPvrs.ERRN |
Natural ISPF error messages. |
ISPvrs.JOBS |
Natural ISPF installation jobs. |
ISPvrs.INPL |
Natural ISPF programs. |
ISPvrs.SYS1 |
Natural ISPF empty versioning file. |
ISPvrs.SYS2 |
Natural ISPF empty container file. |
ISPvrs.DATA |
Natural ISPF Predict file descriptions. |
As of Natural ISPF Version 2.5 a new logical format of the versions file is used. No Adabas FDT or VSAM structure must be changed. Migration must be performed within the file. Any upgrade from a version lower than 2.5.1 requires migration. Migration of version data below Natural ISPF version 2.3.1 is not supported.
Migration can be done with SMA Job I200 Step 2005. At startup time, Natural ISPF checks for old version records. If migration has not executed or only in part, versioning is disabled.
See Loading / Migrating the Natural ISPF Versions File for details.
Check whether you have used any Natural ISPF exits which were loaded
into library SYSISPX. If this is the case, you must make sure that
your modified source is copied to another library. If you have not already done
so, do it before installing the new version, since an INPL of
Natural ISPF overwrites all programs in SYSISPX.
Before installing the new version, you must delete some existing programs and data. Delete the following:
| Library Name | Programs |
|---|---|
SYSLIB |
All objects with prefix IS (IS*).
Job I051, Step 2002 can be used to delete these objects in batch mode
|
SYSISPS1 |
All members (*). Job I051, Step 2000 can be used to delete this library in batch mode (or Step 2001 for VSAM system files). |
Some internal data structures have been changed in Version 2,
compared with earlier versions. In particular, the field
SESSION-DATA has been extended from 128 to 200 bytes. This field
is used in some of the user exits as well as in Open NSPF subprograms which
implement new objects. Here the field is called OPERATION-DATA.
After deleting all members in SYSISPS1 you will have to
rerun INPL of product SAT to show all menu items of the products
NOM and NOP.