System Automation Tools - Software AG Product Documentation

System Automation Tools

Version 3.3.1

April 2010

This document applies to System Automation Tools Version 3.3.1.

Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions.

Copyright © 1991-2010 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America,and/or their licensors.

The name SoftwareAG,webMethods and all SoftwareAGproduct names are either trademarks or registered trademarks of SoftwareAGand/or Software AG USA, Inc. and/or their licensors. Other company and product names mentioned herein may be trademarks oftheir respective owners.

Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the product doc-umentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).

This softwaremay include portions of third-party products. For third-party copyright notices and license terms, please refer to "LicenseTexts, Copyright Notices and Disclaimers of Third-Party Products". This document is part of the product documentation, located athttp://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).

Table of Contents

1 System Automation Tools ............................................................................................... 12 Release Notes for Version 3.3.1 ....................................................................................... 3

Migrating from Previous Versions ............................................................................. 4Prerequisites ............................................................................................................... 4Compatibility and Migration ..................................................................................... 5SAGSIS Problems ....................................................................................................... 5Enhancements and New Features .............................................................................. 5

3 Introduction ..................................................................................................................... 7Concepts ..................................................................................................................... 8Operating System Names .......................................................................................... 8

4 Installation on Mainframe Platforms ............................................................................ 115 Installing System Automation Tools ............................................................................. 13

Installation Jobs ........................................................................................................ 14Using System Maintenance Aid ............................................................................... 14

6 Installation Tape ............................................................................................................ 15Contents of the Installation Tape ............................................................................. 16z/OS .......................................................................................................................... 21BS2000/OSD .............................................................................................................. 16z/VSE ........................................................................................................................ 22

7 Copying the Tape Contents to Disk ............................................................................... 19z/OS .......................................................................................................................... 20BS2000/OSD .............................................................................................................. 21z/VSE ........................................................................................................................ 22

8 Installation Procedure ................................................................................................... 25Step 1: Load SAT System File ................................................................................... 26Step 2: Scratch SAT Library ...................................................................................... 26Step 3: Migrating from Previous Version ................................................................. 26Step 4: Create NATPARMModule ........................................................................... 27Step 5: Link Natural Subtask/Batch ......................................................................... 29Step 6: Load the INPL and ERRN Files .................................................................... 31Step 7: Create NATPARMModule ........................................................................... 32Step 8: Relink all Online Natural Nuclei .................................................................. 34

9 Natural Security Definitions ......................................................................................... 35Applications ............................................................................................................. 36User .......................................................................................................................... 36

10 External Security Definitions ....................................................................................... 3711 Define SAT, Natural and Product Parameters ............................................................. 39

General ..................................................................................................................... 40General Layout of a Parameter Block ....................................................................... 40Long Database IDs and File Numbers ..................................................................... 41Parameter Blocks and Parameters ............................................................................ 41SATDIR Text Object .................................................................................................. 46

12 SATBKR: SAT Definitions for EntireX Broker Access ................................................. 49

iii

After NOP or NOM Installation ............................................................................... 50Customizing the SATBKR Text Object ..................................................................... 50Using EntireX Brokers .............................................................................................. 55

13 SATSRV: SAT Definitions for NPR Nodes on UNIX and Windows ............................ 53After NOP or NOM Installation ............................................................................... 54Customizing the SATSRV Text Object ...................................................................... 54Accessing Services via EntireX Broker ..................................................................... 55Accessing Local Service ............................................................................................ 55

14 Starting a Server ........................................................................................................... 57ONLINE-Start ........................................................................................................... 58AUTO-START .......................................................................................................... 58RPC Servers .............................................................................................................. 62

15 Installation on UNIX Platforms ................................................................................... 63Overview .................................................................................................................. 64Customizing the Application SYSSAT ..................................................................... 64

16 Messages and Codes in English .................................................................................. 6517 System Automation Tools Messages and Codes 0001-0050 ........................................ 6718 System Automation Tools Messages and Codes 0051-0100 ........................................ 6919 System Automation Tools Messages and Codes 0101-0150 ........................................ 7120 System Automation Tools Messages and Codes 0151-0200 ........................................ 7321 System Automation Tools Messages and Codes 0201-0250 ........................................ 7522 System Automation Tools Messages and Codes 0251-0300 ........................................ 7723 System Automation Tools Messages and Codes 0301-0350 ........................................ 7924 System Automation Tools Messages and Codes 0351-0400 ........................................ 8125 System Automation Tools Messages and Codes 0401-0450 ........................................ 8326 System Automation Tools Messages and Codes 0451-0500 ........................................ 8527 System Automation Tools Messages and Codes 0501-0550 ........................................ 8728 System Automation Tools Messages and Codes 0551-0600 ........................................ 8929 System Automation Tools Messages and Codes 0601-0650 ........................................ 9130 System Automation Tools Messages and Codes 0651-0700 ........................................ 9331 System Automation Tools Messages and Codes 0701-0750 ........................................ 9532 System Automation Tools Messages and Codes 0751-0800 ........................................ 9733 System Automation Tools Messages and Codes 0801-0850 ........................................ 9934 System Automation Tools Messages and Codes 0851-0900 ...................................... 10135 System Automation Tools Messages and Codes 0901-0950 ...................................... 10336 System Automation Tools Messages and Codes 1001-1050 ...................................... 10537 System Automation Tools Messages and Codes 1051-1100 ...................................... 10738 System Automation Tools Messages and Codes 1101-1150 ...................................... 10939 System Automation Tools Messages and Codes 1301-1350 ...................................... 11140 System Automation Tools Messages and Codes 1351-1400 ...................................... 11341 System Automation Tools Messages and Codes 1401-1450 ...................................... 11542 System Automation Tools Messages and Codes 1451-1500 ...................................... 11743 System Automation Tools Messages and Codes 1501-1550 ...................................... 11944 System Automation Tools Messages and Codes 1551-1600 ...................................... 12145 System Automation Tools Messages and Codes 1601-1650 ...................................... 123

System Automation Toolsiv


46 System Automation Tools Messages and Codes 1651-1700 ...................................... 12547 System Automation Tools Messages and Codes 1701-1750 ...................................... 12748 System Automation Tools Messages and Codes 1751-1800 ...................................... 12949 System Automation Tools Messages and Codes 1801-1850 ...................................... 13150 System Automation Tools Messages and Codes 1851-1900 ...................................... 13351 System Automation Tools Messages and Codes 1901-1950 ...................................... 13552 System Automation Tools Messages and Codes 2001-2050 ...................................... 13753 System Automation Tools Messages and Codes 2201-2250 ...................................... 13954 System Automation Tools Messages and Codes 3000-3001 ...................................... 14155 Messages and Codes in German ................................................................................ 14356 System Automation Tools Messages and Codes 0001-0050 ...................................... 14557 System Automation Tools Messages and Codes 0051-0100 ...................................... 14758 System Automation Tools Messages and Codes 0101-0150 ...................................... 14959 System Automation Tools Messages and Codes 0151-0200 ...................................... 15160 System Automation Tools Messages and Codes 0201-0250 ...................................... 15361 System Automation Tools Messages and Codes 0251-0300 ...................................... 15562 System Automation Tools Messages and Codes 0301-0350 ...................................... 15763 System Automation Tools Messages and Codes 0351-0400 ...................................... 15964 System Automation Tools Messages and Codes 0401-0450 ...................................... 16165 System Automation Tools Messages and Codes 0451-0500 ...................................... 16366 System Automation Tools Messages and Codes 0501-0550 ...................................... 16567 System Automation Tools Messages and Codes 0551-0600 ...................................... 16768 System Automation Tools Messages and Codes 0601-0650 ...................................... 16969 System Automation Tools Messages and Codes 0651-0700 ...................................... 17170 System Automation Tools Messages and Codes 0701-0750 ...................................... 17371 System Automation Tools Messages and Codes 0751-0800 ...................................... 17572 System Automation Tools Messages and Codes 0801-0850 ...................................... 17773 System Automation Tools Messages and Codes 0851-0900 ...................................... 17974 System Automation Tools Messages and Codes 0901-0950 ...................................... 18175 System Automation Tools Messages and Codes 1001-1050 ...................................... 18376 System Automation Tools Messages and Codes 1051-1100 ...................................... 18577 System Automation Tools Messages and Codes 1101-1150 ...................................... 18778 System Automation Tools Messages and Codes 1301-1350 ...................................... 18979 System Automation Tools Messages and Codes 1351-1400 ...................................... 19180 System Automation Tools Messages and Codes 1401-1450 ...................................... 19381 System Automation Tools Messages and Codes 1451-1500 ...................................... 19582 System Automation Tools Messages and Codes 1501-1550 ...................................... 19783 System Automation Tools Messages and Codes 1551-1600 ...................................... 19984 System Automation Tools Messages and Codes 1601-1650 ...................................... 20185 System Automation Tools Messages and Codes 1651-1700 ...................................... 20386 System Automation Tools Messages and Codes 1701-1750 ...................................... 20587 System Automation Tools Messages and Codes 1751-1800 ...................................... 20788 System Automation Tools Messages and Codes 1801-1850 ...................................... 20989 System Automation Tools Messages and Codes 1851-1900 ...................................... 21190 System Automation Tools Messages and Codes 1901-1950 ...................................... 213

vSystem Automation Tools


91 System Automation Tools Messages and Codes 2001-2050 ...................................... 21592 System Automation Tools Messages and Codes 2201-2250 ...................................... 21793 System Automation Tools Messages and Codes 3000-3001 ...................................... 219

System Automation Toolsvi


1 System Automation Tools

This documentation is organized under the following headings:

What is new in this version of System Automation Tools?Release Notes

What can be done with System Automation Tools?Introduction

How to install System Automation Tools under z/OS, z/VSEand BS2000/OSD.

Installation on Mainframe Platforms

How to install System Automation Tools on UNIX platforms.Installation on UNIX Platforms

English messages in numerical order by their numbers.Messages and Codes in English

German messages in numerical order by their numbers.Messages and Codes in German

1

2

2 Release Notes for Version 3.3.1

■ Migrating from Previous Versions ......................................................................................................... 4■ Prerequisites .................................................................................................................................... 4■ Compatibility and Migration ................................................................................................................. 5■ SAGSIS Problems ............................................................................................................................. 5■ Enhancements and New Features ........................................................................................................ 5

3

These Release Notes inform you of the enhancements and new features that are provided withSystemAutomationToolsVersion 3.3.1. TheReleaseNotes apply to all supported operating systems:z/OS, z/VSE, BS2000/OSD, UNIX (HP-UX, AIX, Sun Solaris, Linux).

Migrating from Previous Versions

Migration of Data

Migration from SAT 321 to SAT 331:

The SAT Log File was extended.

New FDT Fields

CommentAdabasShort NameLevel

LOG-NOP-OBJECT-VERSION10 A NUAV1

Existing SAT log files can be adapted by using Adabas Online Services or another Adabas utility.

Prerequisites

System Automation Tools Version 3.3.1 requires:

■ Adabas Version 8.x or above (mainframe), Adabas Version 6.x or above (UNIX);■ Natural Version 4.2 or above, including the Software AG Editor component (on UNIX Version6.3.8 or above);

■ Entire System Server (Mainframe) Version 3.4.x or above;■ Entire System Server (UNIX and Windows) Version 2.1.4 or above.■ Natural Security (same as NAT) (optional); for openUTM users under BS2000/OSD Natural Se-curity is required;

■ Entire Net-Work (optional, for multi-CPU support).

System Automation Tools4

Release Notes for Version 3.3.1

Compatibility and Migration

With the release of System Automation Tools Version 3.3.1, versions below 3.2.1 are no longersupported. Therefore, we strongly advise you to switch to the current version at your earliestconvenience.

If youwant to use SystemAutomationToolsVersion 3.3.1 togetherwith EntireOutputManagement,Entire Output Management 3.2.1 with Cumulative Fix (Service Pack) 3 is required.

SAGSIS Problems

All solved problems of System Automation Tools Version 3.2.1 and below are included in this re-lease.

Enhancements and New Features

EntireX Broker Security and SSL Support

With this SAT Version, EntireX Broker Security and / or SSL Support can be used for the commu-nication with NPR / UNIX and Windows nodes.

Please refer to the section SATBKR: SAT Definitions for EntireX Broker Access.

5System Automation Tools

Release Notes for Version 3.3.1

6

3 Introduction

■ Concepts ......................................................................................................................................... 8■ Operating System Names ................................................................................................................... 8

7

This documentation describes System Automation Tools (SAT) used in combination with EntireOutput Management (NOM), Entire Operations, (NOP) and Entire Event Management, (NCL)and its installation under z/OS, z/VSE andBS2000/OSD aswell as underUNIX. SystemAutomationTools (SAT) is only offered together with NOP, NOM or NCL.

Concepts

System Automation Tools allows you to start the products of the ESM family whenever EntireSystem Server is started (AUTO-Start) or on request, using the product's start monitor function.Parameters can be specified for:

■ the SAT environment itself;■ the Natural environment used;■ each product of the SAT family, i.e.:

■ Entire Operations (NOP);■ Entire Output Management (NOM);■ Entire Event Management (NCL);

System Automation Tools can start servers for the above products:

■ Independently of the underlying operating system. This means the same parameters are validin all environments.

■ Independently of the product version, even with different product versions in parallel.■ Independently of the version of SystemAutomation Tools. Thismeans compatibilitywith futureversions of System Automation Tools and the products under its control.

■ Independently of the mode of operation in which these servers run. This means they can runas subtasks in z/OS and z/VSE or as separate batch jobs under z/OS, z/VSE and BS2000/OSD.

■ Even in multi-node-environments consisting of any number of nodes. Of course, they must beinterlinked with Software AG's Entire Net-work products.

Operating System Names

BS2000, MVS and VSE are short names for the corresponding operating systems, which can befound on the individual screens in this documentation and in the online help. But throughout theremaining text, their long names are consistently used, i.e., BS2000/OSD, z/OS and z/VSE.


Introduction

Operating SystemsLong NamesShort Names

BS2000/OSDBS2000

z/OSMVS

z/VSEVSE


Introduction

10

4 Installation on Mainframe Platforms

This section describes System Automation Tools (SAT) and its installation under z/OS, z/VSE andBS2000/OSD:

Installing System Automation Tools

Installation Tape

Copying the Tape Contents to Disk

Installation Procedure

Natural Security Definitions

External Security Definitions

Notation vrs or vr:

If used in this section, the notation vrs or vr stands for the relevant version, release and systemmaintenance level number of a product. For further information on product versions, see Versionin the Glossary of the Natural documentation.

11

12

5 Installing System Automation Tools

■ Installation Jobs .............................................................................................................................. 14■ Using System Maintenance Aid .......................................................................................................... 14

13

Installation Jobs

The installation of Software AG products is performed by installation jobs. These jobs are eithercreated manually or generated by System Maintenance Aid (SMA).

For each step of the installation procedure described below, the job number of a job performingthe 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 libraryon the SystemAutomation Tools installation tape; youmust adapt this sample job to your require-ments.

Using System Maintenance Aid

For information onusing SoftwareAG's SystemMaintenanceAid (SMA) for the installation process,refer to the System Maintenance Aid documentation.


Installing System Automation Tools

6 Installation Tape

■ Contents of the Installation Tape ......................................................................................................... 16■ z/OS ............................................................................................................................................. 21■ BS2000/OSD .................................................................................................................................. 16■ z/VSE ........................................................................................................................................... 22

15

Contents of the Installation Tape

The installation tape contains the data sets listed in the table below. The sequence of the data setsis shown in the Report of Tape Creation which accompanies the installation tape.

The SAT (System Automation Tools) load/module and source libraries contain modules sharedby the SAT product family.

z/OS

ContentsData Set Name

System Automation Tools Installation JobsSATvrs.JOBS

System Automation Tools System Libraries (Natural)SATvrs.INPL

System Automation Tools Error MessagesSATvrs.ERRN

System Automation Tools System FileSATvrs.SYSF

* Some data sets for the solution of certain SAGSIS problems may be included on theinstallation tape. Please refer to the problem descriptions before applying them.

....*

BS2000/OSD

ContentsFile Name

System Automation Tools Installation JobsSATvrs.JOBS





....*


Installation Tape

z/VSE

ContentsData Set Name

System Automation Tools Installation JobsSATvrs.LIBJ





....*


Installation Tape

18

7 Copying the Tape Contents to Disk

■ z/OS ............................................................................................................................................. 20■ BS2000/OSD .................................................................................................................................. 21■ z/VSE ........................................................................................................................................... 22

19

z/OS

Copying the Tape Contents to a z/OS Disk

Note: If you are using SMA, refer to the System Maintenance Aid documentation. If you arenot using SMA, follow the instructions below.

This section explains how to copy all data sets from tape to disk. You will then need to performthe individual installation procedure for each component to be installed.

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

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

The data set COPY.JOB contains the JCL required to copy all data sets from tape to disk. If the datasets for more than one product are delivered on the tape, the data set COPY.JOB contains the JCLto unload the data sets for all delivered products from the tape to your disk.

Copy COPY.JOB to your disk using the following sample JCL:

//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-volume),// LABEL=(2,SL)//SYSUT2 DD DSN=hilev.COPY.JOB,// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=volume,// SPACE=(TRK,(1,1),RLSE),// DCB=*.SYSUT1//SYSPRINT DD SYSOUT=*//SYSIN DD DUMMY//

where:

hilev is a valid high-level qualifiertape-volume is the tape volume name, for example: T12345volume is the disk volume name



Step 2: Modify COPY.JOB on Your Disk

Modify COPY.JOB according to your local naming conventions and set the following disk spaceparameters:

■ Set HILEV to a valid high-level qualifier.■ Set LOCATION to a storage location.■ Set EXPDT to a valid expiration date.

Step 3: Submit COPY.JOB

Submit COPY.JOB to copy all data sets from tape to your disk.

BS2000/OSD

Copying the Tape Contents to a BS2000/OSD Disk


This section explains how to copy all files from tape to disk. You will then need to perform theindividual installation procedure for each component to be installed.

■ Step 1: Copy the Library SRVvrs.LIB from Tape to Disk■ Step 2: Copy the Procedure COPY.PROC from Tape to Disk■ Step 3: Copy all Product Files from Tape to Disk

Step 1: Copy the Library SRVvrs.LIB from Tape to Disk

This step is not necessary if you have already copied the library SRVvrs.LIB from another SoftwareAG installation tape. For further information, refer to the element #READ-ME in this library. Thelibrary SRVvrs.LIB is stored on the tape as a sequential file named SRVvrs.LIBS containing LMScommands. The current version vrs can be obtained from the Report of Tape Creation. To convertthis sequential file into an LMS library, execute the following commands:

/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-C4volser is the VOLSER of the tape (see Report of Tape Creation)

Step 2: Copy the Procedure COPY.PROC from Tape to Disk

To copy the procedure COPY.PROC to disk, call the procedure P.COPYTAPE in the library SRVvrs.LIB:

/CALL-PROCEDURE (SRVvrs.LIB,P.COPYTAPE), -/ (VSNT=volser, DEVT=tape-device)

If you use a TAPE-C4 device, you may omit the parameter DEVT.

Step 3: Copy all Product Files from Tape to Disk

To copy all Software AG product files from tape to disk, enter the procedure COPY.PROC:

/ENTER-PROCEDURE COPY.PROC, DEVT=tape-device

If you use a TAPE-C4 device, you may omit the parameter DEVT. The result of this procedure iswritten to the file L.REPORT.SRV.

z/VSE

Copying the Tape Contents to a z/VSE Disk


This section explains how to copy the data sets .LIBJ, .LIBR and .LICS from tape to disk. Allother data sets can be installed directly from the tape.

You will then need to perform the individual installation procedure for each component to be in-stalled.

■ Step 1: Copy Data Set COPYTAPE.JOB from Tape to Disk



■ Step 2: Modify COPYTAPE.JOB■ Step 3: Submit COPYTAPE.JOB

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

The data set COPYTAPE.JOB contains the JCL required to copy the data sets .LIBJ, .LIBR and .LICSfrom tape to disk. Copy COPYTAPE.JOB to your disk by using the following sample JCL:

* $$ 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 addresslib.sublib is the library and sublibrary in which COPYTAPE.JOB is to be stored

Step 2: Modify COPYTAPE.JOB

Modify COPYTAPE.JOB according to your local naming conventions and set the disk space paramet-ers.



Step 3: Submit COPYTAPE.JOB

Submit COPYTAPE.JOB to copy the data sets .LIBJ, .LIBR and .LICS from tape to your disk.



8 Installation Procedure

■ Step 1: Load SAT System File ............................................................................................................ 26■ Step 2: Scratch SAT Library ............................................................................................................... 26■ Step 3: Migrating from Previous Version ............................................................................................... 26■ Step 4: Create NATPARM Module ...................................................................................................... 27■ Step 5: Link Natural Subtask/Batch ..................................................................................................... 29■ Step 6: Load the INPL and ERRN Files ................................................................................................ 31■ Step 7: Create NATPARM Module ...................................................................................................... 32■ Step 8: Relink all Online Natural Nuclei ................................................................................................ 34

25

Step 1: Load SAT System File

(Job I050, Step 3700)

System Automation Tools (SAT) Version 3.3.1 uses a SAT system file with LFILE 131. Please usethe Adabas load utility (Job I050, Step 3700) to load the SATvrs.SYSF file. The system file is inVersion 7 format. For SAT Version 3.3.1, this step can be omitted if SAT is not being installed forthe first time.

Migration to Version 3.3.1 is possible from Version 3.2.1, but not from earlier versions.

For the ADALOD utility use the following parameters:

ValueParameter

100000MAXISN

10DSSIZE

100BUISIZE

1000BNISIZE

YESISNREUSE

YESDSRU

Step 2: Scratch SAT Library

(Job I051, Step 3700)

If the System Automation Tools sub-component has been installed before, scratch the SYSSATlibrary using theNatural SYSMAINutility and scratch the errormessageswith the SYSERRutility.

Step 3: Migrating from Previous Version

Migration from SAT 321 to SAT 331:

(Job I051, Step 3705)

New FDT Fields



CommentAdabasShort NameLevel

LOG-NOP-OBJECT-VERSION10 A NUAV1

Existing SAT log files can be adapted by using Adabas Online Services or another Adabas utility.

Step 4: Create NATPARM Module

Modify, assemble and link the parameter module for the Natural subtask. To do this, adapt JobI060: Steps 3700-3710 (subtask) / Steps 0010-0015 (batch).

Themodulemust contain at least the following parameterswith the documentedminimumvalues.Entries for other products are possible, but not documented here. Refer to the Natural ParameterReference documentation for further information.

Note: To complete these settings additional parametersmay be required for other product(s).See product-specific installation procedure.

Size of user-buffer extension area.ESIZE=96NTPRM

Entire SystemServerwork area size. Choose a value between48 and 64 1.

ASIZE=64

Number of dynamic loaded modules.CDYNAM=10

Max. program calls (no limit)MAXCL=0

Maximum DBMS calls (no limit)MADIO=0

No ET at end of program.

OFF is the default setting.

ETEOP=OFF

WAIT on HOLD, NAT.

This is an obligatory setting.

WH=ON

Set input modeIM=D

Max. CPU time: no limitMT=0

Physical line size.

The default setting is 0.

LS=250

Page size for Natural reports.


PS=66

Response Code 113 will be ignored, and processing of theFIND loop will continue by reading the next record.

This parameter ismandatory for the accurate execution ofEntire Operations. It can be set dynamically too.

RCFIND=OFF



ResponseCode 113will be ignored, the systemvariable *ISNwill be set to 0, and processing will continue.


RCGET=OFF

Natural compares the physical (store clock) and logical(system environment)machine times and uses the difference

TD=AUTO

between the two as the setting for the TD parameter. For atime change to take effect forNatural (for example, to changetime to summer time or back to winter time), it is thereforesufficient to reset the logical machine time.

Note: Please refer to the Natural parameter documentationfor other possibilities to set the TD parameter. In centralEurope, TD=EURO-CET is recommended.

LFILE (logical system file) definition:

use the ID of a physical database (dbid) and the number ofa system file (fnr).

204,dbid,fnrNTLFILE

SAT System File access; use a physical database ID (dbid)and file number (fnr).

131,dbid,fnrNTLFILE

Entire System Server Views cataloged to this DBIDPROCESS,148NTDB

Global buffer pool definition.

n is the sequence number of the buffer pool and bpname thename of the buffer pool.

TYPE=NAT,SEQ=n,NAME=bpnameNTBPI

Local buffer pool definition.

n is the sequence number of the buffer pool and nnn the sizeof the buffer pool.

TYPE=NAT,SEQ=n,SIZE=nnn

If you use a local buffer pool (for NOM/ NCL only), theparameter SIZE must be 512 or higher. The default settingis 256.

Printer definition.(1-4),AM=STD, OPEN=ACCNTPRINT

Work file definition.(1-4),AM=STDNTWORK

1 See the minimum values for Entire System Server.



Step 5: Link Natural Subtask/Batch

(Job I060: Step 3720 - Subtask / Step 0020 - Batch)

■ z/OS■ BS2000/OSD■ z/VSE

z/OS

Servers for SAT 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:

DescriptionLibrary

Natural Load Library.//NATLIB DD DISP=SHR,DSN=SAGLIB.NATvrs.LOAD

Supplied Entire System Server Load Library.//NPRLIB DD DISP=SHR,DSN=SAGLIB.NPRvrs.LOAD

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

■ Take the link job of an existing batch Natural, link the Entire System Server interface to Naturalas 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 SystemServer load library.

■ TomakeCon-nect features available, ensure that the appropriate CNT/TRSmodules are included.

For NPR and Natural

The following example applies to Entire System Server (NPR) Version 3.3.2 and above togetherwith Natural Version 4.2 and above. It demonstrates how to link the Natural subtask front-end.

INCLUDE ...

ESY node tableINCLUDE SMALIB(ESYNODTB)

INCLUDE ...



For NOM

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

Natural subtask / batch interface.INCLUDE SMALIB (NATOS)

NATPARM parameter module.INCLUDE natparm

Adabas / Entire System Server interface.INCLUDE NPRLIB (ADANPR)

SAT Calendar (required for NOP, NOM,NCL), if Natural Version 4.2 andabove are used.

INCLUDE NATLIB(SATDTA)

Software AG Editor.INCLUDE NATEDT

Program editor and map editor.INCLUDE NATEDIT

External entry.ENTRY CMSTART

Name of Natural subtask for SAT, for example, SAT321ST.NAME SATvrsST (R)

BS2000/OSD

■ Take the link job of an existing batch Natural, link the Entire System Server interface to Naturalas described in the currentNatural Installation documentation and include the statements listedbelow.


The following libraries must be used for the linkage:

DescriptionLibrary

Supplied Natural Load Library.

natural-library-namedenotes the name of theNatural loadlibrary.

natural-library-name =NATvrs.MOD

For NPR and Natural

The following example applies to NPR Version 3.3.2 and above together with Natural Version 4.2and above. It demonstrates how to relink Natural, including the following modules:

SAT Calendar (required for NOP, NOM, NCL).

natural-library-namedenotes the name of theNatural loadlibrary.

INCLUDESATDTA,natural-library-name

Product-specific modules.

product-library-name denotes the name of the productlibrary.

INCLUDExxxxxxxx,product-library-name



z/VSE

■ Take the link job of an existing batch Natural, link the Entire System Server interface to Naturalas described in the currentNatural Installation documentation and include the statements listedbelow.


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

For NPR and Natural

The following example applies to NPR Version 3.3.2 and above together with Natural Version 4.2and above.

Change as required.PHASE SATvrsST

Natural Batch DriverINCLUDE NATVSE

SATCalendar (required forNOP,NOM,NCL), youwill find SATDTA in theNaturallibrary.

INCLUDE SATDTA

Software AG Editor.INCLUDE NATEDT

Program editor and map editor.INCLUDE NATEDIT

Adabas interface.INCLUDE LNKVSER

Product-specific INCLUDEs.INCLUDE ...

Step 6: Load the INPL and ERRN Files

(Job I061, Steps 3700 and 3702)

Load the programs and error messages for System Automation Tools.

ContentsFileLibrary

System Automation Tools programs and error messages.FNATSYSSAT

Note: If there are any data sets for the solution of certain SAGSIS problems on the installationtape, refer to the problem descriptions before loading them, now.



Natural Security Environment

Define SYSSAT as STEPLIB for all products of the SAT product family.

Non-Natural Security Environment

The SYSSAT library is automatically defined as STEPLIB for all products of the SAT productfamily.

Step 7: Create NATPARM Module

(for Online Natural)

Modify, assemble and link the parameter module for the online Natural. To do this, adapt Job I080(see the jobs NATvrs.JOBS in your Natural environment). The module must contain at least thefollowing parameters (entries for other products are possible, but not documented here):

Size of user-buffer extension area.ESIZE=96NTPRM

Software AG Editor work area sizeSSIZE=60

Entire System Serverwork area size. Choose a value between48 and 64.1

ASIZE=64

Number of dynamic loaded modules.CDYNAM=10

Entries for SAT products 2. Max. program calls (no limit)MAXCL=0

Maximum DBMS calls (no limit)MADIO=0

No ET at end of program.

OFF is the default setting.

ETEOP=OFF

WAIT on HOLD, NAT.

This is an obligatory setting.

WH=ON

Set input modeIM=D

Max. CPU time: no limitMT=0

Physical line size.


LS=250

Page size for Natural reports.


PS=66

Response Code 113 will be ignored, and processing of theFIND loop will continue by reading the next record.


RCFIND=OFF



ResponseCode 113will be ignored, the systemvariable *ISNwill be set to 0, and processing will continue.


RCGET=OFF

Natural compares the physical (store clock) and logical(system environment)machine times and uses the difference

TD=AUTO

between the two as the setting for the TD parameter. For atime change to take effect forNatural (for example, to changetime to summer time or back to winter time), it is thereforesufficient to reset the logical machine time.

Note: Please refer to the Natural parameter documentationfor other possibilities to set the TD parameter. In centralEurope, TD=EURO-CET is recommended.

LFILE (logical system file) definition:

use the ID of a physical database (dbid) and the number ofa system file (fnr).

204,dbid,fnrNTLFILE

SAT System File access; use a physical database ID (dbid)and file number (fnr).

131,dbid,fnrNTLFILE

Entire System Server Views cataloged to this DBID.PROCESS,148NTDB

Global buffer pool definition.

n is the sequence number of the buffer pool and bpname thename of the buffer pool.

TYPE=NAT,SEQ=n,NAME=bpnameNTBPI

Local buffer pool definition.

n is the sequence number of the buffer pool and nnn the sizeof the buffer pool.

TYPE=NAT,SEQ=n,SIZE=nnn

If you use a local buffer pool (for NOM/ NCL only), theparameter SIZE must be 512 or higher. The default setting is256.

1 See the minimum values for Entire System Server.

2 See installation section in documentation for desired product.



Step 8: Relink all Online Natural Nuclei

AllNaturalmodules, online and batch,whichwill be used to execute ESM functionality (for exampleonline usage of SYSEOR, SYSNOM, SYSNCL and batch jobs used for NOM printing, archiving,etc.) must be relinked:

■ Link the Entire System Server interface toNatural as described in the currentNatural Installationdocumentation.

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




9 Natural Security Definitions

■ Applications ................................................................................................................................... 36■ User ............................................................................................................................................. 36

35

If Natural Security is installed at your site, youmust create the definitions described in this section.

Applications

DescriptionApplications

System Automation Tools application.SYSSAT

System Automation Tools user library.SYSSATU

User

Define the Natural Security User representing the various servers of the SAT product family as“person”withUser ID andpassword identical toNSCUSERandNSCPSWDparameters describedin the subsection Parameter Blocks and Parameters.

Specify PRIVATE LIBRARY=YES.

If you define the above applications “people-protected”, you must link this User to them.


Natural Security Definitions

10 External Security Definitions

z/OS only

If Entire System Server is installed with an external security system (RACF, ACF2, TOP SECRET),a User ID identical to the ESYUSER parameter (described in the subsection Parameter Blocks andParameters) must be defined in the security system. The user must have sufficient authorizationto access the spooling system, the console and all data sets used in the online system.

37

38

11 Define SAT, Natural and Product Parameters

■ General ......................................................................................................................................... 40■ General Layout of a Parameter Block .................................................................................................. 40■ Long Database IDs and File Numbers ................................................................................................. 41■ Parameter Blocks and Parameters ...................................................................................................... 41■ SATDIR Text Object ......................................................................................................................... 46

39

General

You can define the run-time environment of your products in one or more Natural text objects inthe SYSSATU user library for SAT. You can specify any object name except the main object name,whichmust conform to the following naming convention: SPnnnnn, where nnnn denotes the EntireSystem Server node (with leading zeros) under which the SAT products are AUTO-Started. Fora 3-digit ESY node, the SAT text object can still be named SATPnnn, where nnn denotes the EntireSystem Server node. We recommend that you migrate to the SPnnnnn names.

In the main text object, you must specify all parameter values needed to start the products. Anasterisk * in the first columndenotes a comment line. Lines prefixedwith SAT are treated as defaultvalues for SAT or Natural. They can be overwritten by product-specific values. This means thatall occurrences of a parameter are merged when the product is started.

For each occurrence of a SATSTART entry a product server is started.

Note: If Software AG's integrated application development tool Natural ISPF is installed atyour site, you can use the SAT menu to perform this maintenance work and for logging onto any of Software AG's solutions in the Entire SystemsManagement product line. The SATmenu is provided in the SATvrs.INPL data set. Tomake thismenu availablewithinNaturalISPF'smenu system, simply activate the SAT subsystem ofNatural ISPF. If you need furtherinformation, see the section System Configuration in the Natural ISPF Administration Guide.

General Layout of a Parameter Block

prefix block-identifier [keyword=value,...]

where:

DescriptionParameter

SAT or compressed product code + prefix as specified in the SATSTART instruction.prefix

SATENV/NATENV/SATSTART or product block identifier.block-identifier

Block-specific parameter.[keyword=value,...]


Define SAT, Natural and Product Parameters

Examples

SAT SATENV NATTASK=NOPSUBT, NSC=NONOP521 NATENV DU=OFF, FUSER= (9,81)

Long Database IDs and File Numbers

Database IDs (DBID) and file numbers (FNR) may be specified with up to 5 digits, that is from 1to 65,535, as specified in the Natural documentation.

Parameter Blocks and Parameters

This subsection covers the following topics:

■ Table of Parameter Blocks and Parameters■ Example■ SAT Environment Settings■ Natural Environment Settings■ Product Environment Settings■ Product Automatic Start■ Example Contents of SP00148 in SYSSATU

Table of Parameter Blocks and Parameters

DescriptionParameterParameterBlock

All profile parameters supported by Natural are possible.-NATENV

See product.-ProductBlock

Indicates whether Natural Security is installed or not.NSC=YES/NOSATENV

If Natural Security is installed, this is the user ID for logging onto it.

NSCUSER=

Password for logging on to Natural Security.NSCPSWD=

User ID for logging on to Entire System Server, if it is installed,and an interface to an external security system is activated.

In BS2000/OSD: Use the user ID under which the Entire SystemServer is running.

ESYUSER=




Name of the Natural subtask module for starting a server as asubtask.

In BS2000/OSD: *DUMMY has to be used if the Natural subtaskmodule is specified in the JCL, to avoid ESY5660 errors.

NATTASK

Name of the Natural batchmodule for starting a server as a batchjob.

NATBATCH=

Job skeleton for starting a server as a batch job.NATSKEL=

Job name prefix xxx to be used for building job names whenstarting servers as a batch job. For example: EOR in the monitorjob name EORMON.

JOBPREF=xxx

SATENVparametersfor RPCservers

Number of RPC server replications to be started.NUMTASK=

Name of an RPC server which will connect to a broker.SRVNAME=

Name of the broker service an RPC server will connect to.SRVNODE=

Natural parameter profile which is used to start one watchdogtask per RPC server.

PROFILE=

This keyword causes the ping function to RPC servers and thecheck of NPR eventing (shutdown request) interval to be set to

CHECK-INTERVAL=

nnnnn seconds. To utilize this parameter the SATENV parameter"SATVERS" has to be set to "32" (or above).

SAT version (for example, SATVERS=32), which is supported bythe product startup program. This does not necessarily reflect the

SATVERS=vrSATSTART

currently installed SAT version - it means , the SAT interfaceversion, i.e. the suffix of programs

RPCSAT

nn in library SYSSAT.

Note: This parameter is relevant only for SAT versions beforeversion 331.

3-byte code, eg.: NOP, NOM, NCL.PRODUCT=

PRODUCT and PREFIX are compressed into a prefix whichidentifies the server-specific parameters.

PREFIX=

Start server as a batch job or subtask.TYPE=BATCH/SUBTASK

Name of the Natural library where the product is installed.APPLLIB=

Product-specific data file. For each SATSTART instruction of oneSPnnnnn text object, a different data file must be referred to.

SERVSYSF=




You can specify amemberwhere product-specific parameters arelocated.

MEMBER=

Example

The text object SP00148 in SYSSAT provides an example of a main text object. To use this as thebasis for your own object: just copy it to SYSSATU and adapt it.

In the example below, it is assumed that you are running three products of the SAT product family(NCL, NOM and NOP) as subtasks on Node 148. The parameters of NOP are located in a secondtext object NOPPARMS.

SAT Environment Settings

1NATTASK=SATvrsSTSATENVSAT * *

NATBATCH=NATvrsBA

NATSKEL=JSKELVSE

ESYUSER=NOMMON

NSC=YES

NSCUSER=NOMMON

NSCPSWD=NOMMON

STEPLIB1=(SYSLIBS,dbid,fnr)

STEPLIB2=(SYSEXT,dbid,fnr)

STEPLIB3=(SYSTEM,dbid,fnr)

2NATTASK=NSATT08SATENVNCL221 *

NSC=NO

ESYUSER=NCLMON

2NATTASK=NSATT08SATENVNOM321 *

NSC=NO

ESYUSER=NOMMON

2NSC=NOSATENVNOP521 *

ESYUSER=NOPMON



JOBPREF=xxx

Natural Environment Settings

If the following parameters are passed to Natural as dynamic parameters, the maximum stringlength of all parameters may not exceed 250 bytes.

3DU=OFFNATENVSAT *

9MAXCL=0

MADIO=0

MT=0

ID=' '

DC='.'

ETID='' (for NOM only)

4FNAT=(1,5)NATENVNCL221 *

4FNAT=(9,45)NATENVNOM311

4FNAT=(9,45)NATENVNOP521 *

Product Environment Settings

8BS2USER=PROD01NOMENVNOM311

Product Automatic Start

5PRODUCT=NCLSATSTARTSAT *

PREFIX=221

TYPE=SUBTASK

APPLLIB=SYSNCLSV

SERVSYSF=(1,7)

5PRODUCT=NOMSATSTARTSAT *

PREFIX=311

TYPE=SUBTASK

APPLLIB=SYSNOM

SERVSYSF=(9,46)



5PRODUCT=NOPSATSTARTSAT *

APPLID=SYSEOR

PREFIX=521 /* EOR 521 SUBTASK

TYPE=SUBTASK

APPLLIB=SYSEOR SERVSYSF=(9,65)

Example Contents of SP00148 in SYSSATU

6NSC=YES,SATENVNOP521 *

NSCUSER=NOPMON,

NSCPSWD=HUGO

7DU=ONNATENVNOP521 *

Explanations:

1 Sets the SAT defaults for all SAT products, here: NOP and NOM.

2 Overwrites some SAT values for NCL221, NOM311 and NOP521 respectively.

3 Sets the NAT defaults for all SAT products.

4 Overwrites some NAT values for NCL221, NOM311 and NOP521 respectively.

5 Specifies that the servers for NCL221, NOM311 and NOP521 respectively should be started assubtasks.

6 Overwrites some SAT defaults for NOP521 only.

7 Overwrites some NAT defaults for NOP521 only.

8 Product environment settings are documented in the corresponding product installation docu-mentation.

9 It is recommended to use ETID=''. CheckNatural documentation for the valid ETID syntax (appliesonly to NOM).



SATDIR Text Object

The following topics are covered below:

■ General■ SAT in Distributed Computing Environments■ Explanation■ General Description of SATDIR

General

You must define your SAT environment(s) in the text object SATDIR in the library SYSSATU. Theentries in this object are used to distribute your definitions into your SAT environments (with theSATNET program) and to determine the local SAT environment for a specific node when startingservers from online.



SAT in Distributed Computing Environments



Explanation

A user has logged onto Natural, whose LFILE entry for ID=204 is pointing to FNAT=(9,80). Theuser's main text object SP00148 and the text object SATDIR reside in the SYSSATU library of thatFNAT. With this connection he can start SAT product servers online.

General Description of SATDIR

Database IDs (DBID) and file numbers (FNR) may be specified with up to 5 digits.

Syntax

SATnnnnn SATDIR SATSYSF=(sat-dbid,sat-fnr)

where:

SATnnnnn is the Entire System Server node number

sat-dbid is the DBID of the local FNAT

sat-fnr is the FNR of the local FNAT

Example

SAT00148 SATDIR SATSYSF=(9,80) /* Default settings for node 148.

This line reflects the scenario above.



12 SATBKR: SAT Definitions for EntireX Broker Access

■ After NOP or NOM Installation ........................................................................................................... 50■ Customizing the SATBKR Text Object .................................................................................................. 50■ Using EntireX Brokers ...................................................................................................................... 55

49

After NOP or NOM Installation

■ Create aNatural text object SATBKR in the library SYSSATUas described in the following section.

Customizing the SATBKR Text Object

Youmust customize the text object SATBKR in theNatural library SYSSATU to contain the requiredparameter definitions for SystemAutomation Tools. For example definitions, see the <SATBKREX>text object in the SYSSATU library.

If you are installing System Automation Tools for the first time, proceed as follows:

1. Invoke Natural.

2. Log on to the SYSSATU library.

3. Issue the direct command: E <SATBKREX>.

4. Enter the command: SAVE SATBKR.

5. Press ENTER.

The parameters and appropriate parameter values (if required) contained in SATBKR and<SATBKREX> are described in the following section:

BROKER-ATTRIBUTES BROKER-ID=broker-id USERID=user-id CPW=ciphered-password SSL-TRUST-STORE=SSL-trust-store

MeaningParameter

Corresponds to the parameter BROKER-ID specified in the EntireX Broker attributefile.

broker-id is the name of the EntireX Broker under which the service is started, forexample, BRKnnn. If NOP orNOM is executed in aUNIX or aWindows environment,

BROKER-ID

for broker-id the following syntax can be used: host:port:TCP. Example:BROKER-ID=ibm1:29000:TCP

Corresponds to the parameter USER-ID specified in the EntireX Broker attribute file.

user-id is the user ID for the mainframe or the UNIX server.

USER-ID

For Broker Security:

The password for the user-id, in ciphered format.

CPW


SATBKR: SAT Definitions for EntireX Broker Access

MeaningParameter

To cipher a password, please use the utility nprpwc (UNIX) or nprpwc.exe (Windows).It is delivered with NPR / Unix and NPR / Windows.How to use:

UNIX:

Open a console (shell) window cd $NPRDIR/$NPRVERS/bin nprpwc

Windows:

Open a DOS (command prompt) window cd %nprdir%\%nprvers%\binnprpwc.exe

Note: After any password change, the ciphering must be repeated.

Optional, for SSL communication:

The SSL Trust Store, as described in the EntireX Broker documentation.

SSL-TRUST-STORE

SSL communication will be used only if this parameter is present.

Note for invoking ESM Products:

There are no additional definitions required in the invoking ESM products (e.g. NOP or NOM).Broker Security and SSL support is fully transparent for their node definitions.

Using EntireX Brokers

For each EntireX Broker that is to be accessed with Broker Security and / or SSL, you need onesection of parameter definitions in SATBKR. The text object SATBKREX can be used as a templatefor this purpose.

For Brokers without Broker Security and without SSL, you do not need an entry in SATBKR.


SATBKR: SAT Definitions for EntireX Broker Access

52

13 SATSRV: SAT Definitions for NPR Nodes on UNIX and

Windows■ After NOP or NOM Installation ........................................................................................................... 54■ Customizing the SATSRV Text Object .................................................................................................. 54■ Accessing Services via EntireX Broker ................................................................................................ 55■ Accessing Local Service ................................................................................................................... 55

53

After NOP or NOM Installation

■ Create aNatural text object SATSRV in the library SYSSATUas described in the following section.

Customizing the SATSRV Text Object

Youmust customize the text object SATSRV in theNatural library SYSSATU to contain the requiredparameter definitions for System Automation Tools. For example definitions, see the SATSRVEXtext object in the SYSSATU library.

If you are installing System Automation Tools for the first time, proceed as follows:

1. Invoke Natural.

2. Log on to the SYSSATU library.

3. Issue the direct command: E SATSRVEX.

4. Enter the command: SAVE SATSRV.

5. Press ENTER.

The parameters and appropriate parameter values (if required) contained in SATSRV and SATS-RVEX are described in the following section:

The entries in SATSRV have the format:

node-name SATSRV TYPE=ACI BROKER-ID=broker-id SERVER-CLASS=NPR SERVER-NAME=server-name SERVICE=service-name USER-ID=user-id WAIT-TIME=seconds LOCALE-STRING=locale_string

MeaningParameter

Usually the same name as server-name.node-name

Type of communication. Must always be ACI.TYPE

Corresponds to the parameter BROKER-ID specified in the EntireX Broker attributefile.

broker-id is the name of the EntireX Broker under which the service is started, forexample, BRK034. If NOP or NOM is executed in a UNIX or a Windows environment,

BROKER-ID


SATSRV: SAT Definitions for NPR Nodes on UNIX and Windows

MeaningParameter

for broker-id the following syntax can be used: host:port:TCP. Example:BROKER-ID=ibm1:3800:TCP

Corresponds to the parameter CLASS specified in the EntireX Broker attribute file.SERVER-CLASS

Corresponds to the parameter SERVER in the SDPA structure.

server-name is the name of a mainframe or a UNIX server.

SERVER-NAME

Corresponds to the parameter SERVICE specified in the EntireX Broker attribute file.

service-name is the name of the EntireX Broker Service.

SERVICE

Corresponds to the parameter USER-ID specified in the EntireX Broker attribute file.

user-id is the user ID for the mainframe or the UNIX server.

USER-ID

Corresponds to the parameter WAIT specified in the EntireX Broker attribute file.

seconds is the 3-character wait time in seconds, for example, 60S.

WAIT-TIME

Corresponds to the parameter LOCALE_STRING in the SDPA structure.

The field is important for character set translation and conversion.

LOCALE-STRING

Note for Entire Operations:

node-name and server-namemust correspond to the node names specified in the EntireOperationsnode table (see the sectionDefinition of Nodes in SystemAdministrator Services in the Entire OperationsAdministration documentation), and node-name and service-namemust correspond to a sectionname within the npr.ini file on the target system. We recommended that you choose the sameidentifiers for node names and service names.

Accessing Services via EntireX Broker

For each service that is to be accessed, you need one section of parameter definitions. The textobject SATSRVEX can be used as a template for this purpose.

Accessing Local Service

To access a service in local mode (without using EntireX Broker), certain parameter definitionsare required. Copy the second section of the example in the text object SATSRVEX into the textobject SATSRV and replace service-namewith a name of your choice.


SATSRV: SAT Definitions for NPR Nodes on UNIX and Windows

56

14 Starting a Server

■ ONLINE-Start ................................................................................................................................. 58■ AUTO-START ................................................................................................................................. 58■ RPC Servers .................................................................................................................................. 62

57

Different methods are supported for starting a server of the SAT product family.

ONLINE-Start

The start of a server of any SAT product

■ Entire Operations■ Entire Output Management■ Entire Event Management

in any environment supported (z/OS, z/VSE, BS2000/OSD) can be performed online. Proceed asfollows:

1. Use an online Natural with the following specifications:■ FNAT must contain SYSSAT library (as installed in Step 2).■ LFILE 204 must point to your local SYSSAT environment in order to find main text objectSP00148 in SYSSATU (see Step 6 and Step 7 of the Installation Procedure).

2. LOGON to the appropriate product library, for which you want to start the server(s).

3. Invoke the product-specific start command (see documentation for the product itself).

4. This start command reads the SATSTARTparameter block of the appropriate product in SP00148and invokes the server initialization program.

5. You will be informed online about the success of the operation.

AUTO-START

With AUTO-START you can automatically start one or more servers at Entire System Serverstartup time. Proceed as follows:

1. Link a suitable Natural for this purpose (as described in Step 4 and Step 5):

For z/OS and z/VSE

This must be a subtask-Natural, because it runs in the address space of the Entire SystemServer.

For BS2000/OSD

This must be a multi-user Natural.


Starting a Server

2. To activate this process, adapt the startup parameters of Entire System Server. This consists ofthe following actions:■ Specify the name of the Natural module which should be given control.■ Specify the LOGON commands to invoke program SATSTART in library SYSSAT.

For z/OS and z/VSE

If Natural Security is installed, specify the following parameters and supply the appropriateparameter values if required:

NATSHARE=nucleus-nameNATNUMSUB=subtask-maximumNATMOD=subtask-moduleSTRTNTP1=STACK=(LOGON SYSSAT,nsc-user,nsc-pswd;STRTNTP2=SATSTART;FIN),AUTO=OFF

where:

nucleus-name is the name of Natural shared nucleus if used.subtask-maximum is the maximum number of subtasks (recommended: 20).subtask-module is the name of Natural subtask module as linked in Step 4.nsc-user is the user ID required to log on to Natural Security.nsc-pswd is the password required for logging on to Natural Security.

If Natural Security is not installed, specify the following parameters:

STRTNTP1=STACK=(LOGON SYSSAT;SATSTART;FIN),AUTO=OFF

For BS2000/OSD

Specify the following parameters and supply the appropriate parameter values:

JOBNATSUB=subtask-locationPRMNATSUB=startup-parmsNATNUMSUB=subtask-maximum

where:

subtask-location is the JCL location for Natural subtask AUTO-Start.startup-parms are the parameters for ENTER/START-JOB.subtask-maximum is the maximum number of subtasks (recommended: 20).

Note: You can find an example of JCL for Natural subtask AUTO-STARTs in the memberE.STARTSAT in the LIB.SATvrs library.

3. During startup, the program SATSTART now gets control. As in the case of an online start,SATSTART uses the LFILE setting for File 204 to find its main text object.


Starting a Server

4. For each SATSTART instruction defined in the SP00148 text object, SATSTART starts a server.The type of the server (batch or subtask) is determined by the parameter TYPE.■ For TYPE=SUBTASK:The Natural subtask module specified with the NATTASK parameter is given control.

■ For TYPE=BATCH:The Natural batch module specified with the NATBATCH parameter is given control. Thenecessary JCL for this batch job is expected in theNatural object specifiedwith theNATSKELparameter (library is SYSSATU). The jobname of the server task is created automatically.

For more information on the above, see the subsections Starting Servers with Type=Subtaskand Starting Servers with Type=Batch.

5. These server sessions can be adapted with the SATENV parameter block: Default settings aremarkedwith the prefix SAT. They can be overridden by product-specific parameter blocks. Thesame holds true for Natural-specific parameter settings (NATENV block).

6. During each server startup, a product-specific initialization module gets control. Its name isautomatically derived from parameters given in the SATSTART block in the following way:

productSATsat-vr

where product denotes the 3-letter code of the respective product and sat-vr denotes the SATversion, for example, NOPSAT32.

7. This server initialization module can itself start other servers.

8. You can check the success of this processing either by examining the Entire System Serverprotocol or by logging on to the online application and testing the server status online.

The following topics are covered below:

■ Starting Servers with TYPE=SUBTASK■ Starting Servers with TYPE=BATCH

Starting Servers with TYPE=SUBTASK

For each SATSTART instruction, in the address space of Entire System Server (z/OS, z/VSE), asubtask is started which initiates the server start. The subtask name is built as follows:

pppSTAdddddfffff

where:

ppp = product code

ddddd = DBID as specified in the SERVSYSF parameter

fffff = FNR


Starting a Server

Note: If you want to start servers as subtasks in a BS2000/OSD environment, proceed asfollows:

1. Adapt either the NSBTSKIS text object (for ISP format) or the NSBTSKSD text object (for SDFformat) in the SATvrs source library.

Note: The ADALNK parameter file is optionally supported. To use this function, youmust change the text object NSBTSKIS or NSBTSKSD correspondingly. Further informa-tion is available in the current Adabas Release Notes.

2. Assemble it into the Entire System Server load library.

Subtasks are simulated by Entire System Server: batch jobs are submitted under the BS2000/OSDuser ID as specified in the ESYUSER parameter. The job names of these batch jobs are built asfollows:

pppSTnnn

where:

ppp = product code

nnn = node number

Starting Servers with TYPE=BATCH

For each SATSTART instruction, a batch job is submitted. For this submit, the user ID specifiedin the ESYUSER parameter is in effect. The job name is built as follows:

pppnnnrr

where:

ppp = prefix as specified in the JOBPREF parameter or product code

nnn = node number

rr = run number

You must prepare a job skeleton which reflects your system environment and which is used bythe SATSTART program. Examples are delivered in the SYSSAT library which you can use as abasis for your skeletons. Skeletons must reside in the SYSSATU library. You can specify theirnames with the NATSKEL parameter, for example:


Starting a Server

NATSKEL=JSKELMVS /* z/OS environmentNATSKEL=JSKELVSE /* z/VSE environmentNATSKEL=JSKELBS2 /* BS2000/OSD environment

RPC Servers

If an ESM PC product is installed, which is connected to a mainframe monitor (like NOM GUIClient) it may be useful to start several RPC servers in parallel to balance data traffic. This couldbe done by starting several Natural RPC servers as batch jobs, but administration is easier, if startand stop is controlled by SAT.

For this purpose, there is the following:

■ A new product code "RPC" for SAT to start and stop Natural RPC servers like monitors startedfor NOM or NOP. This means that RPC servers will come up when NPR is started and be readyfor use until NPR stops.

■ AnewNPR console command "SHUTDOWNRPC" to end all RPC servers started by SATSTART.■ An extra task "WATCHDOG": since no Natural program is executed in a Natural RPC server,we need an extra task that controls start and stop procedures. This task issues the control com-mands to shutdown RPC servers, triggered by NPR (at shutdown time of NPR or if a "SHUT-DOWN RPC" command occurs).


Starting a Server

15 Installation on UNIX Platforms

■ Overview ....................................................................................................................................... 64■ Customizing the Application SYSSAT .................................................................................................. 64

63

This section describes System Automation Tools (SAT) and its installation on UNIX platforms.

Overview

SYSSAT is a common base-library for the Entire SystemsManagement Products Entire Operations(NOP) und Entire Output Management (NOM). It is included within the installation process ofNOM and NOP.

The installation procedures ofNOP andNOMautomatically ensure that an existing SAT installationis replaced by a current SAT version only.

Customizing the Application SYSSAT

This menu item contains the creation of the application SYSSAT in your Natural FNAT directory.In addition, the shared library will be copied automatically to NATEXTLIB.

Before you perform this step:

■ Make sure that enough disk space is available in the target environment.■ Make sure that you have write access rights to the Natural FNAT directory, as well as to thedirectory specified by the NATEXTLIB parameter in the local configuration file as described inthe Natural Configuration Utility documentation.

Continuewith the instructions in SATSRV: SATDefinitions forNPRNodes onUNIXandWindows.


Installation on UNIX Platforms

16 Messages and Codes in English

The System Automation Tools messages are organized under the following headings:

System Automation Tools Messages and Codes 0001-0050
















65























Messages and Codes in English

17 SystemAutomationToolsMessages andCodes 0001-0050

SAT0002: SAT0002 Node not specified

SAT0003: SAT0003 Invalid System Type

SAT0004: SAT0004 Invalid Server Type

SAT0006: SAT0006 NATURAL Library not specified

SAT0007: SAT0007 NATURAL Program not specified

SAT0008: SAT0008 NATURAL SECURITY user ID not specified

SAT0009: SAT0009 NATURAL SECURITY password not specified

SAT0010: SAT0010 Skeleton Library not specified

SAT0011: SAT0011 Skeleton Member not specified

SAT0012: SAT0012 Subtask Name not specified

SAT0013: SAT0013 NATPARMS Line exceeded

SAT0014: SAT0014 NATENV parameter does not fit into one line

SAT0015: SAT0015 NATENV Number of Lines exceeded

SAT0016: SAT0016 Skeleton DBID not specified

SAT0017: SAT0017 Skeleton FNR not specified

SAT0018: SAT0018 NATURAL Batch Module not specified

SAT0019: SAT0019 Invalid SAT Version

67

68


SAT0051: SAT0051 Invalid function specified

SAT0052: SAT0052 No logical files currently available

SAT0053: SAT0053 Bad response from CMMPP call

69

70


SAT0101: SAT0101 Unknown status


SAT0103: SAT0103 Invalid Server Type

SAT0104: SAT0104 Subtask Name not specified

SAT0105: SAT0105 Jobname not specified

SAT0106: SAT0106 Job Number not specified

71

72


SAT0151: SAT0151 Please specify SAT node

73

74


SAT0201: SAT0201 Node not specified

SAT0202: SAT0202 Subtask name not specified

SAT0203: SAT0203 NATURAL Parameter not specified

SAT0204: SAT0204 NATURAL Parameters longer than 250 bytes

SATNT0204 NATURAL Parameters longer than 250 bytes.Text

The accumulated length of the dynamic Natural parameters mustnot exceed 250 bytes.

Expl.

SAT0210: SAT0210 NATURAL Parameter Syntax Error

75

76


SAT0251: SAT0251 Invalid SYSF value specified

77

78


SAT0305: SAT0305 Invalid Skeleton

SAT0307: SAT0307 NATURAL Logon line not specified

SAT0308: SAT0308 NATURAL Program Line not specified


79

80


SAT0352: SAT0352 Library not specified

SAT0353: SAT0353 Member not specified

SAT0354: SAT0354 DBID not specified

SAT0355: SAT0355 FNR not specified

SAT0356: SAT0356 Name not specified

SAT0357: SAT0357 Type not specified

SAT0358: SAT0358 Parameter member not found

81

82


SAT0401: SAT0401 Line contains no key assignment

83

84


SAT0451: SAT0451 Resulting parm block is too long

85

86


SAT0501: SAT0501 Invalid System type

87

88


SAT0551: SAT0551 DBID not specified

SAT0552: SAT0552 FNR not specified

SAT0555: SAT0555 Name not specified


SAT0557: SAT0557 At least one block must be specified

89

90


SAT0601: SAT0601 SATLIB not specified

SAT0602: SAT0602 SATMEM not specified

SAT0603: SAT0603 ApplFnr specified but no ApplDbid

SAT0604: SAT0604 ApplDbid specified but no ApplFnr

SAT0605: SAT0605 No SATSTART entries found

SAT0606: SAT0606 Caller"s system file :1: not matching any SERVSYSF

SATSP0606 Caller"s system file :1: not matching any SERVSYSF.Text

No SATENV block was found, which has a system file (SERVSYSF)equal to the caller"s system file.

Expl.

SAT0607: SAT0607 Parameter "AUTO" must be "ON" or "OFF"

SAT0608: SAT0608 SRVNODE not specified

SAT0609: SAT0609 SRVNAME not specified

91

92


SAT0652: SAT0652 Product System File (DBID) not specified

SAT0653: SAT0653 Product System File (FNR) not specified

93

94


SAT0701: SAT0701 SatDbid not specified

SAT0702: SAT0702 SatFnr not specified


SAT0704: SAT0704 No keywords specified

SAT0707: SAT0707 Prefix name missing

SAT0708: SAT0708 At least one block must be specified

95

96


SAT0752: SAT0752 SATDIR Member not found or no entry for this node

SAT0753: SAT0753 Invalid SATSYSF parameter

97

98


SAT0801: SAT0801 Invalid Message Type - "N" or "U" are valid

SAT0802: SAT0802 No error code specified

SAT0803: SAT0803 Bad response from call to "USR0120N"

SAT0804: SAT0804 SAT LFILE is not set

99

100


SAT0851: SAT0851 From-member not specified

SAT0852: SAT0852 From-library not specified

SAT0853: SAT0853 From-DBID not specified

SAT0854: SAT0854 From-FNR not specified

SAT0855: SAT0855 To-library not specified

SAT0856: SAT0856 To-DBID not specified

SAT0857: SAT0857 To-FNR not specified

101

102


SAT0901: SAT0901 SATNET Parameter Distribution Protocol

SAT0902: SAT0902 Please press <ENTER> to start distribution

SAT0903: SAT0903 Distribution in progress - please wait

SAT0904: SAT0904 Distribution complete - no errors detected

SAT0905: SAT0905 Distribution with errors - press enter for protocol

SAT0906: SAT0906 No members for distribution found

SAT0907: SAT0907 Duplicate entries in SATDIR found - terminating

103

104


SAT1001: SAT1001 NATURAL Library not specified

SAT1002: SAT1002 Invalid DBID

SAT1003: SAT1003 Invalid FNR

SAT1004: SAT1004 Invalid Cipher Code

105

106


SAT1052: SAT1052 Product System File (DBID) not specified

SAT1053: SAT1053 Product System File (FNR) not specified

107

108


SAT1101: SAT1101 Error during REGISTER :1:

SAT1102: SAT1102 Abnormal termination during REGISTER :1:

SAT1103: SAT1103 Invalid conversation handle in function RECEIVE

SAT1104: SAT1104 Neither a handle nor ANY,OLD,NEW specified

SAT1105: SAT1105 Maximum number of conversations exceeded

SAT1106: SAT1106 Error during RECEIVE - :1:

SAT1107: SAT1107 Abnormal termination during RECEIVE - :1:

SAT1108: SAT1108 Error during DEREGISTER - :1:

SAT1109: SAT1109 Abnormal termination during DEREGISTER - :1:

SAT1110: SAT1110 Error during END CONVERSATION - :1:

SAT1111: SAT1111 Abnormal termination during END CONVERSATION :1:

SAT1112: SAT1112 SendMessage - ACI invalid conv handle specified

SAT1113: SAT1113 SendMessage - ACI Neither conv handle nor NEW specified

SAT1114: SAT1114 SendMessage error - ACI :1:

SAT1115: SAT1115 SendMessage abend - ACI :1:

SAT1116: SAT1116 DeleteMessage abend - ACI :1:

109

110


SAT1301: SAT1301 Abnormal termination - WaitForAnyMessage (ACI) :1:

SAT1302: SAT1302 Abnormal termination - WaitForAnyMessage (ESY) :1:

111

112


SAT1351: SAT1351 Abnormal termination - WaitForNewMessage (ACI) :1:

SAT1352: SAT1352 Abnormal termination - WaitForNewMessage (ESY) :1:

113

114


SAT1401: SAT1401 Abnormal termination - WaitForOldMessage (ACI) :1:

SAT1402: SAT1402 Abnormal termination - WaitForOldMessage (ESY) :1:

115

116


SAT1451: SAT1451 Abnormal termination - WaitForSpeMessage (ACI) :1:

SAT1452: SAT1452 Abnormal termination - WaitForSpeMessage (ESY) :1:

117

118


SAT1501: SAT1501 Abnormal termination - PollForAnyMessage (ACI) :1:

SAT1502: SAT1502 Abnormal termination - PollForAnyMessage (ESY) :1:

119

120


SAT1551: SAT1551 Abnormal termination - PollForNewMessage (ACI) :1:

SAT1552: SAT1552 Abnormal termination - PollForNewMessage (ESY) :1:

121

122


SAT1601: SAT1601 Abnormal termination - PollForOldMessage (ACI) :1:

SAT1602: SAT1602 Abnormal termination - PollForOldMessage (ESY) :1:

123

124


SAT1651: SAT1651 Abnormal termination - PollForSpeMessage (ACI) :1:

SAT1652: SAT1652 Abnormal termination - PollForSpeMessage (ESY) :1:

125

126


SAT1701: SAT1701 Invalid conversation handle specified

SAT1702: SAT1702 Conversation handle missing

SAT1703: SAT1703 Abnormal termination - EndConversation - ACI :1:

127

128


SAT1751: SAT1751 SendReply not possible

SAT1752: SAT1752 Conversation handle missing

SAT1753: SAT1753 Abnormal termination - SendReply (ACI) :1:

SAT1754: SAT1754 Abnormal termination - SendReply (ESY) :1:

129

130


SAT1801: SAT1801 Abnormal termination - ForwardMessage (ACI) :1:

SAT1802: SAT1802 Abnormal termination - ForwardMessage (ESY) :1:

131

132


SAT1851: SAT1851 Abnormal termination - SendRequest (ACI) :1:

SAT1852: SAT1852 Abnormal termination - SendRequest (ESY) :1:

133

134


SAT1901: SAT1901 Service name missing

SAT1902: SAT1902 Partner type missing

SAT1910: SAT1910 Parameter block not found: :1:

SAT1911: SAT1911 Parameter block read error :1:

135

136


SAT2001: SAT2001 Invalid ISN Lower Limit value specified

SAT2002: SAT2002 Invalid ISN Quantity value specified

SAT2003: SAT2003 Invalid number of ISNs specified

SAT2004: SAT2004 Invalid number of records in hold specified

SAT2005: SAT2005 Invalid CID value specified

SAT2006: SAT2006 Invalid time for execution of Sx specified

137

138


SAT2211: SAT2211 - Broker Session Logoff - :1: Session(s)

139

140


SAT3001: SAT3001 - This message is used for various runtime errors :1:

141

142

55 Messages and Codes in German

The messages are sorted in numerical order by their numbers.

















143























Messages and Codes in German


SAT0002: SAT0002 Knoten nicht angegeben

SAT0003: SAT0003 Ungueltiger Systemtyp

SAT0004: SAT0004 Ungueltiger Servertyp

SAT0006: SAT0006 NATURAL Bibliothek nicht angegeben

SAT0007: SAT0007 NATURAL Programm nicht angegeben

SAT0008: SAT0008 NATURAL SECURITY Benutzer-ID nicht angegeben

SAT0009: SAT0009 NATURAL SECURITY Passwort nicht angegeben

SAT0010: SAT0010 Skeleton-Bibliothek nicht angegeben

SAT0011: SAT0011 Skeleton-Member nicht angegeben

SAT0012: SAT0012 Subtask-Name nicht angegeben

SAT0013: SAT0013 NATPARMS Zeile zu gross

SAT0014: SAT0014 NATENV Parameter passt nicht in eine Zeile

SAT0015: SAT0015 NATENV zu viele Zeilen

SAT0016: SAT0016 Skeleton DBID nicht angegeben

SAT0017: SAT0017 Skeleton FNR nicht angegeben

SAT0018: SAT0018 NATURAL Batch-Modul nicht angegeben

SAT0019: SAT0019 Ungueltige SAT-Version

145

146


SAT0051: SAT0051 Ungueltige Funktion angegeben

SAT0052: SAT0052 Zur Zeit keine logischen Files frei

SAT0053: SAT0053 CMMPP Aufruf war fehlerhaft

147

148


SAT0101: SAT0101 Status unbekannt


SAT0103: SAT0103 Ungueltiger Servertyp

SAT0104: SAT0104 Subtask Name nicht angegeben

SAT0105: SAT0105 Jobname nicht angegeben

SAT0106: SAT0106 Jobnummer nicht angegeben

149

150


SAT0151: SAT0151 Bitte SAT Knoten angeben

151

152


SAT0201: SAT0201 Knoten nicht angegeben

SAT0202: SAT0202 Subtask-Name nicht angegeben

SAT0203: SAT0203 NATURAL Parameter nicht angegeben

SAT0204: SAT0204 NATURAL Parameter laenger als 250 Bytes

SATNT0204 NATURAL Parameter laenger als 250 Bytes.Text

Die Gesamtlaenge der dynamischen Natural-Parameter darf nichtgroesser als 250 sein.

Expl.

SAT0210: SAT0210 NATURAL Parameter Syntax-Fehler

153

154


SAT0251: SAT0251 Ungueltiger SYSF Wert angegeben

155

156


SAT0305: SAT0305 Ungueltiges Skeleton

SAT0307: SAT0307 NATURAL Logon-Zeile nicht angegeben

SAT0308: SAT0308 NATURAL Programm-Zeile nicht angegeben


157

158


SAT0352: SAT0352 Bibliothek nicht angegeben

SAT0353: SAT0353 Member nicht angegeben

SAT0354: SAT0354 DBID nicht angegeben

SAT0355: SAT0355 FNR nicht angegeben

SAT0356: SAT0356 Name nicht angegeben

SAT0357: SAT0357 Typ nicht angegeben

SAT0358: SAT0358 Parameter-Member nicht gefunden

159

160


SAT0401: SAT0401 Zeile enthaelt keine Keyword-Zuweisung

161

162


SAT0451: SAT0451 Resultierender parm block ist zu lang

163

164


SAT0501: SAT0501 Falscher Systemtyp

165

166


SAT0551: SAT0551 DBID nicht angegeben

SAT0552: SAT0552 FNR nicht angegeben

SAT0555: SAT0555 Name nicht angegeben


SAT0557: SAT0557 Mindestens ein Block muss angegeben sein

167

168


SAT0601: SAT0601 SATLIB nicht angegeben

SAT0602: SAT0602 SATMEM nicht angegeben

SAT0603: SAT0603 ApplFnr angegeben jedoch ohne ApplDbid

SAT0604: SAT0604 ApplDbid angegeben, jedoch keine ApplFnr

SAT0605: SAT0605 Keine SATSTART Anweisungen gefunden

SAT0606: SAT0606 Aufrufer-System-File :1: entspricht keiner SERVSYSF

SATSP0606 Aufrufer-System-File :1: entspricht keiner SERVSYSF.Text

Es wurde kein SATENV-Block gefunden, dessen System-File (SERVSYSF)gleich der des Aufrufenden ist.

Expl.

SAT0607: SAT0607 Parameter "AUTO" muss "ON" oder "OFF" sein

SAT0608: SAT0608 SRVNODE nicht angegeben

SAT0609: SAT0609 SRVNAME nicht angegeben

169

170


SAT0652: SAT0652 Produktdatei (DBID) nicht angegeben

SAT0653: SAT0653 Produktdatei (FNR) nicht angegeben

171

172


SAT0701: SAT0701 SatDbid nicht angegeben

SAT0702: SAT0702 SatFnr nicht angegeben


SAT0704: SAT0704 Keine Schluesselworte angegeben

SAT0707: SAT0707 Prefix fehlt

SAT0708: SAT0708 Mindestens ein Block muss angegeben sein

173

174


SAT0752: SAT0752 SATDIR nicht gefunden oder kein Eintrag fuer den Knoten

SAT0753: SAT0753 Falsche Angabe im SATSYSF Parameter

175

176


SAT0801: SAT0801 Ungueltige Meldungstyp - "N" oder "U" sind gueltig

SAT0802: SAT0802 Fehlercode nicht angegeben

SAT0803: SAT0803 Fehler beim Aufruf von "USR0120N"

SAT0804: SAT0804 SAT LFILE ist nicht gesetzt

177

178


SAT0851: SAT0851 From-member nicht angegeben

SAT0852: SAT0852 From-library nicht angegeben

SAT0853: SAT0853 From-DBID nicht angegeben

SAT0854: SAT0854 From-FNR nicht angegeben

SAT0855: SAT0855 To-library nicht angegeben

SAT0856: SAT0856 To-DBID nicht angegeben

SAT0857: SAT0857 To-FNR nicht angegeben

179

180


SAT0901: SAT0901 Protokoll SATNET Parameter Verteilung

SAT0902: SAT0902 Bitte <FREIGABE> druecken um Verteilung zu starten

SAT0903: SAT0903 Verteilung laeuft - bitte warten

SAT0904: SAT0904 Verteilung beendet - keine Fehler aufgetreten

SAT0905: SAT0905 Verteilung fehlerhaft - <FREIGABE> fuer Protokoll

SAT0906: SAT0906 Keine Member zur Verteilung gefunden

SAT0907: SAT0907 Doppelte Eintraege in SATDIR - keine Verteilung

181

182


SAT1001: SAT1001 NATURAL-Bibliothek nicht angegeben

SAT1002: SAT1002 Falsche DBID

SAT1003: SAT1003 Falsche FNR

SAT1004: SAT1004 Angabe im Chiffrierschluessel nicht numerisch

183

184


SAT1052: SAT1052 Produktdatei (DBID) nicht angegeben

SAT1053: SAT1053 Produktdatei (FNR) nicht angegeben

185

186


SAT1101: SAT1101 Fehler waehrend der Funktion REGISTER :1:

SAT1102: SAT1102 Programmabbruch waehrend der Funktion REGISTER :1:

SAT1103: SAT1103 Unbekannte Konversation in der Funktion RECEIVE

SAT1104: SAT1104 Keine gueltige Konversation noch ANY,OLD, NEW angegeben

SAT1105: SAT1105 Maximale Anzahl von Verbindungen ueberschritten

SAT1106: SAT1106 Fehler waehrend der Funktion RECEIVE - :1:

SAT1107: SAT1107 Programmabbruch bei der Funktion RECEIVE - :1:

SAT1108: SAT1108 Fehler waehrend der Funktion DEREGISTER - :1:

SAT1109: SAT1109 Abbruch bei der Funktion DEREGISTER - :1:

SAT1110: SAT1110 Fehler bei END CONVERSATION - :1:

SAT1111: SAT1111 Abbruch bei der Funktion END CONVERSATION :1:

SAT1112: SAT1112 SendMessage - ACI unbekannte Konversation angegeben

SAT1113: SAT1113 SendMessage - ACI weder guelt. Konv. noch NEW angegeben

SAT1114: SAT1114 SendMessage Fehler - ACI :1:

SAT1115: SAT1115 SendMessage Abbruch - ACI :1:

SAT1116: SAT1116 DeleteMessage Abbruch - ACI :1:

187

188


SAT1301: SAT1301 Abbruch bei WaitForAnyMessage (ACI) :1:

SAT1302: SAT1302 Abbruch bei WaitForAnyMessage (ESY) :1:

189

190


SAT1351: SAT1351 Abbruch bei WaitForNewMessage (ACI) :1:

SAT1352: SAT1352 Abbruch bei WaitForNewMessage (ESY) :1:

191

192


SAT1401: SAT1401 Abbruch bei WaitForOldMessage (ACT) :1:

SAT1402: SAT1402 Abbruch bei WaitForOldMessage (ESY) :1:

193

194


SAT1451: SAT1451 Abbruch bei WaitForSpeMessage (ACI) :1:

SAT1452: SAT1452 Abbruch bei WaitForSpeMessage (ESY) :1:

195

196


SAT1501: SAT1501 Abbruch bei PollForAnyMessage (ACI) :1:

SAT1502: SAT1502 Abbruch bei PollForAnyMessage (ESY) :1:

197

198


SAT1551: SAT1551 Abbruch bei PollForNewMessage (ACI) :1:

SAT1552: SAT1552 Abbruch bei PollForNewMessage (ESY) :1:

199

200


SAT1601: SAT1601 Abbruch bei PollForOldMessage (ACI) :1:

SAT1602: SAT1602 Abbruch bei PollForOldMessage (ESY) :1:

201

202


SAT1651: SAT1651 Abbruch bei PollForSpeMessage (ACI) :1:

SAT1652: SAT1652 Abbruch bei PollForSpeMessage (ESY) :1:

203

204


SAT1701: SAT1701 Unbekannte Konversation angegeben

SAT1702: SAT1702 Fehlende Konversation

SAT1703: SAT1703 Abbruch bei EndConversation - ACI :1:

205

206


SAT1751: SAT1751 SendReply nicht moeglich

SAT1752: SAT1752 Fehlende Konversation

SAT1753: SAT1753 Abbruch bei SendReply (ACI) :1:

SAT1754: SAT1754 Abbruch bei SendReply (ESY) :1:

207

208


SAT1801: SAT1801 Abbruch bei ForwardMessage (ACI) :1:

SAT1802: SAT1802 Abbruch bei ForwardMessage (ESY) :1:

209

210


SAT1851: SAT1851 Abbruch bei SendRequest (ACI) :1:

SAT1852: SAT1852 Abbruch bei SendRequest (ESY) :1:

211

212


SAT1901: SAT1901 Service-Name fehlt

SAT1902: SAT1902 Partner-Typ fehlt

SAT1910: SAT1910 Parameter-Block nicht gefunden: :1:

SAT1911: SAT1911 Parameter-Block Lesefehler :1:

213

214


SAT2001: SAT2001 Falsches "ISN Lower Limit" angegeben

SAT2002: SAT2002 Falsche "ISN Quantity"-Angabe

SAT2003: SAT2003 Falsche "Number of ISNs"-Angabe

SAT2004: SAT2004 Falsche "Number of Records in hold"-Angabe

SAT2005: SAT2005 Falscher CID-Wert angegeben

SAT2006: SAT2006 Falsche Ausfuehrungszeit fuer Sx angegeben

215

216


SAT2211: SAT2211 - Broker Session Logoff - :1: Session(s)

217

218


SAT3001: SAT3001 - Diese Meldung wird für verschiedene Laufzeitfehler verwendet :1:

219

220

Documents

System Automation Tools - Software AG Product Documentation