z/VSE Installation

#### Search Results

Search

# z/VSE Installation

The installation steps described in this section must be followed in sequence in order to install Com-plete successfully. You are recommended to use the provided examples up to successful initialization in order to ensure that the installation was successful. Once a functional system is available, you can start customizing the product as required.

All sample JCL referred to in the installation steps is illustrated in z/VSE Sample JCL.

This document covers the following topics:

- The Installation Medium

- Installation Steps

- Startup Procedure

- What Next?

## The Installation Medium

### Contents of the Installation Medium

The installation medium is created using IBM standard labels.

Important
Please see the Software AG Product Delivery Report for the correct Volser.

File Name | Description / Remarks
--- | ---
SMT111.TABS | SMA tables
COMvrs.USER | User ID file
COMvrs.CTLG | Catalog file

Notes:

1. The files may not be on the installation medium in the order shown above: please consult the Software AG Product Delivery Report.
2. The notation vrs stands for current version, release and maintenance level.
3. There may be no cumulative fix pack libraries for a component if this is a new release of the respective component.

### Copying Data Sets to a z/VSE Disk

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

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

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

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

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

This section explains how to copy the data sets `.LIBJ`, `.LIBR` and `.LICS` (if supplied) from tape to disk. All other data sets can be installed directly from the tape.

- Step 1: Copy Data Set COPYTAPE.JOB to Disk
- Step 2: Modify COPYTAPE.JOB on Your Disk
- Step 3: Submit COPYTAPE.JOB

#### Step 1: Copy Data Set COPYTAPE.JOB to Disk

- Modify the following sample job according to your requirements:

      * $$ JOB JNM=LIBRCAT,CLASS=0,                                          +
      * $$ DISP=D,LDEST=(*,UID),SYSID=1
      * $$ LST CLASS=A,DISP=D
      // JOB LIBRCAT
      * *****************************************
      *     STORE COPYTAPE.JOB IN LIBRARY
      * *****************************************
      // ASSGN SYS004,nnn
      // MTC REW,SYS004
      // MTC FSF,SYS004,4
      ASSGN SYSIPT,SYS004
      // TLBL IJSYSIN,'COPYTAPE.JOB'
      // EXEC LIBR,PARM='MSHP; ACC S=lib.sublib'
      /*
      // MTC REW,SYS004
      ASSGN SYSIPT,FEC
      /*
      /&
      * $$ EOJ

  where:

  `nnn` is the tape address, and
  `lib.sublib` is the library and sublibrary in which the data set `COPYTAPE.JOB` is to be stored.

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

  `COPYTAPE.JOB` contains the JCL required to copy the data sets `.LIBJ`, `.LIBR` and `.LICS` from tape to disk.

#### Step 2: Modify COPYTAPE.JOB on Your Disk

- Modify `COPYTAPE.JOB` according to your requirements and set the disk space parameters as appropriate.

#### Step 3: Submit COPYTAPE.JOB

- Execute `COPYTAPE.JOB` to copy the data sets `.LIBJ`, `.LIBR` and `.LICS` to your disk.

## Installation Steps

#### Step 1: Create the Com-plete User Data library

- The SAGLIB.COMUSER library contains installation-dependent modules and user programs. This sublibrary is recommended, since future maintenance to the system may replace the private distribution libraries completely, thereby destroying any user modules in that library.

  Create the library using the sample job JCLINST2 (Sublib=SAGLIB.COMUSER).

#### Step 2: Allocate and Initialize the Com-plete VSAM System Data Containers

- Only for a new installation:

  Allocate, initialize and load the Com-plete system information data sets by modifying sample job JCLINST4 to reflect appropriate size and placement of the files. Please refer to the Com-plete Files and Associated User Files in the Com-plete System Programming documentation for more information on this VSAM file.

#### Step 3: Allocate and Initialize the Capture Data Set(s)

- Required only if capture is used at your installation.

  Com-plete capture data sets are defined as VSAM data sets in the current version. Sample job JCLINST5 provides JCL to allocate and initialize two capture data sets. You must modify the job to reflect appropriate size and placement of the capture data sets.

  Note
  In z/VSE, the Com-plete account records (SMF-records) are written to the capture data set.

#### Step 4: Allocate and Initialize the Com-plete SD Dataset

- The Com-plete SD dataset must be defined as a VSAM dataset in the current version. For detailed information on this file, please refer to the Com-plete Files and Associated User Files in the Com-plete System Programming documentation. To allocate and initialize the SD dataset, modify sample job JCLINST6 to reflect your requirements and run this job.

#### Step 5: Allocate and Initialize the Com-plete VSAM Spool Data Set

- Required.

  The Com-plete spool data set reside on a VSAM file. To allocate and initialize this file, modify sample job JCLINST7 to reflect appropriate size and placement of the data set. Then run the job.

#### Step 6: Install the Com-plete License File

- Required (see section Software AG Mainframe Product Licensing)).

  Store the license file in ASCII or EBCDIC encoding to sublib member of your choice. Make the location of the license file known to Com-plete by means of either a DLBL statement with the DLBL name LICENSE, or sysparm LICENSE.

#### Step 7: Update VTAM Definitions

- Required only if the Com-plete interface with VTAM is to be used.

  To enable the Com-plete VTAM interface, you must define an ACB to VTAM in the PRD2.CONFIG data set (MEMBER=VTMAPPL.B). The following sample definition generates an ACB called "COMPLETE" with the necessary privileges for Com-plete:

      VBUILD TYPE=APPL
      COMPLETE   APPL     AUTH=(ACQ,PASS)

  To use this feature, you must specify the Com-plete system parameter VTAMAPPL=COMPLETE.

  Please refer to VTAM documentation for more information.

#### Step 8: Install the Com-plete Batch Online Interface

Required.

The Com-plete BATCH utilities and migration jobs require ACCESS when performing some or all of their functions.

Batch applications that use Com-plete services communicate with the target Com-plete via ACCESS. This communication is based on an Adabas SVC (ACCESS-SVC) and a DBID (ACCESS-ID).

For ADABAS 8 and higher make sure that the Link Global Table used by ADALNK or ADALNKR points to the same SVC as defined in the ACCESS-SVC sysparm.

The Com-plete BATCH interface module loads a module with name ACSTAB and search this module for an entry name BATCH.

1. Modify the sample ACSTAB module on the source data set to reflect the system requirements for SVC and NODE ID.

2. Assemble and linkedit the module into the SUB=SAGLIB.COMUSER library. Modify sample job JCLINSTF to do this.

   Note that the DBID chosen may be greater than 255 and that the value of both DBID and SVC must correspond to the values of ACCESS-ID and ACCESS-SVC specified in the SYSPARM member.

#### Step 9: Set the Com-plete System Parameters (SYSPARM)

- Sample job COMJCVSE refers to a set of Com-plete parameters in COMPARM.COMTEST3. Copy them to the library SAGLIB.COMUSER and ensure that the following parameters reflect your installation requirements:

  PATCHAR | Choose a unique single character value for your installation.
  VTAMAPPL | Must be changed to the ACB name you have set up in installation step Update VTAM Definitions.
  ACCESS-SVC | Must be set to the Adabas SVC number (see Install the Com-plete Batch Online Interface).
  ACCESS-ID | Must be set to the database ID (see Install the Com-plete Batch Online Interface).

  The following two statements are mandatory in Com-plete 6.5 and above:

      SERVER=(OPERATOR,TLINOPER)
      SERVER=(POSIX,PAENKERN)
      SERVER=(COMPLETE,TLINCOMP)

  The SERVER statements for Console, Natural and Power must be put after the Com-plete server.

#### Step 10: Add z/VSE/POWER Interface

- Add the following statement after the SERVER statement for COMPLETE:

      SERVER=(POWER,TLINPOW0)

#### Step 11: Install the Com-plete High Level Language Interface

- Optional.

  Applications that use Com-plete functions must be linked with the Com-plete high level language interface modules. These modules provide a standard interface between the application and Com-plete.

  These modules are provided on the supplied load data set. If you are migrating from a previous version of Com-plete, some applications may need to be relinked with the new version of the HLLI modules. For details, see Migration.

#### Step 12: Install the UDEBUG Environment

Optional.

Com-plete provides an online debugging utility (UDEBUG). In order to establish the working environment, proceed as follows:

1. Include the list of required UDEBUG residentpage modules in your SYSPARM member. A list of these modules is given in member DBUGSAMP in the supplied source datasets.

   The UDEBUG facility is described in detail in the Com-plete Utilities documentation.

#### Step 13: Install NSPOOL

Optional.

The printout spooling facility NSPOOL is described in the Com-plete Application Programming documentation. The required dataset for running NSPOOL is on the Com-plete installation medium and is loaded as part of the Com-plete installation. The dataset name is COMvrs.NS22.

1. Run an INPL of NSPOOL.

2. If NSPOOL is to be used in a Natural environment running under Natural Security, you must stow the following modules in the Natural Security system library; otherwise, proceed to the next point.

       SPSE01-N,
       SPSE02-S,
       SPSE01-&,
       SPSE02-&,
       SPSE03-&
       SPAPPL-N *
       SPUSER-N *

   See also the section Default Authorization below.

3. You must place the following module in the Natural system library and delete them from the NSPOOL library:

       SPSEC01N

4. The Natural startup application (for example, NAT31) must be cataloged with ULIB as PV (privileged).

5. If you are using Natural Security, you must copy the latest versions of NSCUS and NSCXR to the NSPOOL library.

#### Step 14: Install the POSIX Server

The license checker of Com-plete 6.5 and higher (z/VSE 4.1 and higher) requires the POSIX runtime to be active.

All load modules used by the POSIX runtime are contained in APSvrs.LDnn which is mandatory for Com-plete 6.5 and higher, even if you do not plan to use any other POSIX-based components (e.g., Telnet tn3270 support, HTTP server, LPD print server support).

1. To activate the POSIX runtime, add the following SERVER statement to your SYSPARMs:

       SERVER=(POSIX,PAENKERN)

2. POSIX runtime parameters can be specified directly in the Com-plete SYSPARM member, or in a separate member concatenated to the Com-plete SYSPARMs in the startup JCL procedure. The POSIX runtime may require additional parameters to be set, please refer to the Configuration of the SMARTS Environment for a detailed description of those parameters.

   Note
   Servers are started in the order in which their SERVER= statements are found in the SYPARMs. The servers OPERATOR, POSIX, COMPLETE must be defined in this order.

   If your TCP/IP connection uses an ID other than 00, insert the line

       //OPTION SYSPARM='nn'

   Note
   z/VSE 4.1 or higher: if you do not add the server statement(s) to your sysparms, the server will be started internally.

#### Step 15: Activate the tn3270 Server

Add the Loadlibrary of your TCPIP stack to the Com-plete LIBDEF chain.

The tn3270 server must be defined using a SERVER SYSPARM statement. See section The tn3270 Server in Software Interfaces in the System Programming documentation for a detailed description.

- The SERVER statement for the tn3270 server must be located after the SERVER statement for the COMPLETE server.

#### Step 16: Install the HTTP Server

Install the HTTP server as described in the Com-plete HTTP Server documentation.

In general, the following steps are necessary:

1. Add the Loadlibrary of your TCPIP stack to the Com-plete LIBDEF chain.

2. Make sure the POSIX runtime is setup properly, including the CDI drivers (see above).

3. Add a SERVER statement to your SYPARMs:

       SERVER=(HTTP,HAENSERV,CONF=/lib/sublib/haanconf.j).

   Note that this server definition must be placed behind the definitions of the servers OPERATOR, POSIX, and COMPLETE in the SYSPARMs.

4. Use the sample module HAANCONF from the HTTP server source library as a pattern to setup your own configuration. This is the place where you specify, for example, the port number your HTTP server will be using.

## Startup Procedure

Com-plete can run in any partition. If it’s started in a dynamic partition you need Adabas with ESA features for ACCESS support.

#### Step 1: Modify Procedure COMJCVSE

- Review sample job COMJCVSE in the source library for correct data set names.

  Note
  For more information on the data sets and their purpose, see the Com-plete System Programming documentation.

#### Step 2: Initialize Com-plete System Intercept

- In z/VSE environments, communication between the Com-plete nucleus and the user program is established using SVC 200.

  The program COMSIP is used to load the intercept module into the SVA and to put it into the chain of z/VSE’s First Level Interrupt Handlers anchored in lowcore. Additional information about the intercept module is stored into CRSVATBL, a module which must have been loaded into the SVA using SET SDL prior to running COMSIP.

  #### Executing the COMSIP Program

      * $$ JOB   JNM=COMSIP,DISP=D,CLASS=?
      * $$ LST   DISP=D,CLASS=A
      // JOB     COMSIP   initialize Com-plete system adapter
      // ASSGN   SYSLST,IGN
      // DLBL    SAGLIB,'.....LIBRARY'
      // EXTENT  ,vvvvvv
      // LIBDEF  PHASE,SEARCH=SAGLIB.APSvrs,TEMP
      // UPSI    00000000  make sure it is not set
      // EXEC    COMSIP,SIZE=AUTO
      // ASSGN   SYSLST,UA
      /*
      /&
      * $$ EOJ

  Important
  This step should never run while another SAG product running on SMARTS (APS) is up.
  CRSVATBL and COMSIP must be loaded from the same library. The modules are downward compatible and can be used by every currently supported version of Com-plete.
  If you have software from CA and/or Macro 4 installed, this step must run AFTER the initialization of the CA system and BEFORE the initialization of Macro 4.
  In a multi-processor environment, this step can only run before the second CPU is started.

  Insert the following into the ASI BG JCL procedure according to the above mentioned requirements before the START of the POWER partition so that the Com-plete SVC intercept will be installed automatically during each IPL.

      // DLBL    SAGLIB,'.....LIBRARY'
      // EXTENT  SYS010,vvvvvv
      // ASSGN   SYS010,DISK,VOL=vvvvvv,SHR
      // LIBDEF  PHASE,SEARCH=SAGLIB.APSvrs,TEMP
      SET SDL
      CRSVATBL,SVA
      /*
      // UPSI    00000000
      // EXEC    COMSIP,SIZE=AUTO

#### Step 3: Initialize Com-plete for the First Time

- Start Com-plete by submitting the created job. Monitor the startup messages carefully for any signs of problems. When the initialization is complete, a message to that effect is written to the operator console.

  A message is also sent to the console to notify you that the VTAM interface has initialized.

#### Step 4: Log On

- Log on through VTAM to the specified VTAM application name. The Com-plete ULOG menu is displayed, prompting you for user ID and password. Log on to Com-plete using user ID SAGADMIN and password ADMIN.

  This user ID has a definition on the Com-plete system data container with the required authorization to define more user IDs to the system, using the user ID maintenance facility described in the Com-plete Utilities documentation.

  After defining other user IDs, you are recommended to change the password for user SAGADMIN and use this user ID in emergency cases only.

## What Next?

Com-plete is now up and ready for work. How you continue depends on whether you have installed Com-plete for the first time or whether you are migrating from a previous version.

- If you have installed Com-plete for the first time, no further migration is necessary. You can continue with customization steps described in the Com-plete System Programming documentation and the Com-plete Utilities documentation.

- If you are migrating from a previous version of Com-plete, see Migration.

### On this page

- The Installation Medium
- Installation Steps
- Startup Procedure
- What Next?