Installation Procedure

This section covers the following topics:

Step 1: Load SAT System Files

(Job I050, Step 3700)

This step can be omitted if System Automation Tools is not being installed for the first time.

System Automation Tools (SAT) uses a SAT system file with LFILE 131. Use the Adabas load utility to load the file SATvrs.SYSF. The system file is in Version 7 format.

A migration to Version 3.4.3 is possible from Version 3.3.1, but not from earlier versions.

For the ADALOD utility use the following parameters:

Parameter Value
MAXISN 100000
DSSIZE 10
UISIZE 100B
NISIZE 1000B
ISNREUSE YES
DSRU YES

(Job I050, Step 3702)

This step can be omitted if you do not intend to use the event store.

The event store uses a SAT system file with LFILE 84. Use the Adabas load utility to load the file SATvrs.SYSE. The system file is in Version 7 format.

A migration from a previous version is not applicable as this system file was introduced with the current version.

For the ADALOD utility use the same parameters as listed above.

Step 2: Scratch SAT Library

(Job I051, Step 3700)

If System Automation Tools has been installed before, scratch the SYSSAT library using the Natural SYSMAIN utility, and scratch the error messages with the SYSERR utility.

Step 3: Migrating from Previous Version

Migration from Version 3.3.1 to Version 3.4.3 on Mainframes

Job Steps Action
I051 3711, 3713, 3715, 3717 Migration of system-file structure from Version 3.3.1 to Version 3.4.3.

Step 4: Create Natural Parameter Module

(Job I060: Steps 3700-3710 (Subtask) / Steps 0010-0015 (Batch)

Modify, assemble and link the parameter module for the Natural subtask.

The module must contain at least the following parameters with the documented minimum values. Entries for other products are possible, but not documented here. See the Natural Parameter Reference documentation for further information.

Note:
To complete these settings, additional parameters may be required for other products. See the product-specific installation procedure.

Macro Parameter Explanation
NTPRM ESIZE=96 Size of user-buffer extension area.
ASIZE=64 Entire System Server work area size. Choose a value between 48 and 64. See the minimum values for Entire System Server.
CDYNAM=10 Number of dynamically loaded modules.
MAXCL=0 Maximum number of program calls (no limit).
MADIO=0 Maximum number of DBMS calls (no limit).
ETEOP=OFF No end-of-transaction at end of program. OFF is the default setting.
WH=ON Wait on Hold, NAT. This is an obligatory setting.
IM=D Set input mode.
MT=0 Maximum CPU time: no limit.
LS=250 Physical line size. The default setting is 0.
PS=66 Page size for Natural reports. The default setting is 0.
RCFIND=OFF Response Code 113 will be ignored, and processing of the FIND loop will continue by reading the next record.

This parameter is mandatory for Entire Operations. It can also be set dynamically.

RCGET=OFF Response Code 113 will be ignored, the system variable *ISN will be set to 0, and processing will continue.

This parameter is mandatory for Entire Operations. It can also be set dynamically.

TD=AUTO Time Differential: Natural compares the physical (store clock) and logical (system environment) machine times and uses the difference between the two as the setting for the TD parameter. For a time change to take effect for Natural (for example, to change time to summer time or back to winter time), it is therefore sufficient to reset the logical machine time.

In central Europe, TD=EURO-CET is recommended. See the Natural Parameter Reference documentation for other possible TD parameter settings.

NTLFILE 204,dbid,fnr LFILE (logical system file) definition: Use the ID of a physical database (dbid) and the number of a system file (fnr).
NTLFILE 131,dbid,fnr System Automation Tools system file access: Use the ID of a physical database (dbid) and the number of a system file (fnr).
NTLFILE 84,dbid,fnr Optional, only required if the event store is to be used. Use the ID of a physical database (dbid) and the number of a system file (fnr).
NTDB PROCESS,148 Entire System Server views cataloged to this database ID.
NTBPI TYPE=NAT,SEQ=n,NAME=bpname Global buffer pool definition: n is the sequence number of the buffer pool and bpname the name of the buffer pool.
TYPE=NAT,SEQ=n,SIZE=nnn Local buffer pool definition: n is the sequence number of the buffer pool and nnn the size of the buffer pool.

If you use a local buffer pool (for Entire Output Management and Entire Event Management only), SIZE must be 512 or higher. The default setting is 256.

NTPRINT (1-4),AM=STD, OPEN=ACC Printer definition.
NTWORK (1-4),AM=STD Work-file definition.

Step 5: Link Natural Subtask/Batch

(Job I060: Step 3720 - subtask / Step 0020 - batch)

z/OS

Servers for Entire Systems Management products can be started either as subtasks or as separate batch jobs. Therefore, you need either a subtask Natural or a batch Natural.

The following libraries must be used for the linkage:

Library Description
//NATLIB DD DISP=SHR,DSN=SAGLIB.NATvrs.LOAD Natural load library.
//NPRLIB DD DISP=SHR,DSN=SAGLIB.NPRvrs.LOAD Supplied Entire System Server load library.

The result of the subtask linkage must be stored in any steplib of the Entire System Server node used and it must be reentrant. This library, like any steplib of the Entire System Server Started Task, must be APF-authorized.

  • Take the link job of an existing batch Natural, link the Entire System Server interface to Natural as described in the current Natural Release Notes and include the statements listed below.

  • Adjust NATLIB to your Natural load library, and NPRLIB and SMALIB to your Entire System Server load library.

  • To make Con-nect features available, ensure that the appropriate CNT/TRS modules are included.

For Entire System Server and Natural

The following example applies to Entire System Server together with Natural. It demonstrates how to link the Natural subtask front-end.

INCLUDE SMALIB(ESYNODTB) Entire System Server node table

For Entire Output Management, Entire Operations and Entire Event Management

The following is an example of how to link the Natural subtask front-end:

INCLUDE SMALIB (NATOS) Natural subtask / batch interface.
INCLUDE natparm Natural parameter module.
INCLUDE SMALIB (ADALNKR) Adabas reentrant link routine.
INCLUDE NATLIB (SATDTA) SAT Calendar (required for all Entire Systems Management products).
INCLUDE NATEDT Software AG Editor.
INCLUDE NATEDIT Program editor and map editor.
ENTRY CMSTART External entry.
NAME SATvrsST (R) Name of Natural subtask for System Automation Tools.

BS2000

  • Take the link job of an existing batch Natural, link the Entire System Server interface to Natural as described in the current Natural Installation documentation and include the statements listed below.

  • To make Con-nect features available, ensure that the appropriate CNT/TRS modules are included.

The following libraries must be used for the linkage:

Library Description
natural-library-name = NATvrs.MOD Supplied Natural load library.

natural-library-name is the name of the Natural load library.

For Entire System Server and Natural

The following example applies to Entire System Server together with Natural. It demonstrates how to link the Natural subtask front-end.

INCLUDE SATDTA,natural-library-name SAT Calendar (required for all Entire Systems Management products).

natural-library-name is the name of the Natural load library.

INCLUDE xxxxxxxx,product-library-name Product-specific modules.

product-library-name is the name of the product library.

z/VSE

  • Take the link job of an existing batch Natural, link the Entire System Server interface to Natural as described in the current Natural Installation documentation and include the statements listed below.

  • To make Con-nect features available, ensure that the appropriate CNT/TRS modules are included.

Include the library definitions for USRLIB, NATLIB, and NPRLIB in your LNKEDT procedure: (LIBDEF chain).

For Entire System Server and Natural

The following example applies to Entire System Server together with Natural. It demonstrates how to link the Natural subtask front-end.

PHASE SATvrsST Change as required.
INCLUDE NATVSE Natural batch driver.
INCLUDE SATDTA SAT Calendar (required for all Entire Systems Management products), you will find SATDTA in the Natural library.
INCLUDE NATEDT Software AG Editor.
INCLUDE NATEDIT Program editor and map editor.
INCLUDE LNKVSER Adabas interface.
INCLUDE ... Product-specific INCLUDE instructions.

Step 6: Load the INPL

(Job I061, Steps 3700)

Load the programs and error messages for System Automation Tools.

Library File Contents
SYSSAT FNAT System Automation Tools programs and error messages.

Natural Security Environment

Define SYSSAT as steplib for all Entire Systems Management products.

Non-Natural Security Environment

The SYSSAT library is automatically defined as steplib for all Entire Systems Management products.

Step 7: Create Online Natural Parameter Module

( Job I080)

Modify, assemble and link the parameter module for the online Natural (see the jobs NATvrs.JOBS in your Natural environment).

The relevant parameters are listed under Step 4 above.

In addition, the parameter SSIZE=60 (work area size of Software AG Editor) has to be specified in the NTPRM macro.

The macros NTPRINT and NTWORK can be omitted from the online Natural parameter module.

Step 8: Relink All Online Natural Nuclei

All Natural modules, online and batch, which will be used to execute Entire Systems Management functionality (for example, online usage of SYSEOR, SYSNOM, SYSNCL and batch jobs used for Entire Output Management printing, archiving, etc.) must be relinked:

  • Link the Entire System Server interface to Natural, as described in the Natural Installation documentation.

  • Include SATDTA (SAT Calendar function) from the Natural library and product-specific load modules as described in the documentation of the relevant products.

  • To make Con-nect features available, ensure that the appropriate CNT/TRS modules are included.