Con-nect Installation Medium

This Dokument contains the following topics:

z/OS Installation Medium

The following topics are covered below:

Data Sets

The z/OS installation medium contains the data sets listed below. The sequence of the data sets is shown in the Software AG Product Delivery Report which accompanies the installation medium.

Data Set Name Contents
CNTnnn.JOBS Example installation jobs.
CNTnnn.INPL INPL data set containing language-independent components of the Con-nect processor and transport service.
CNTnnn.LOAD Contains the CTMOD module which must be linked to the Natural nucleus. This data set is specifically for the transport service.
CNTnnn.SRCE Source library for the transport service. This data set is specifically for the transport service.
CNTnnn.SYS2 An unloaded copy of an empty Con-nect help system file. This file has the internal identification LFILE number 222.
CNTnnn.SYS3 An unloaded copy of an empty Con-nect spool file. This file is used for the external mailing facility, e.g., Con-nect multi-node. It has the internal identification LFILE number 223.
CNTnnn.SYS4 An unloaded copy of an empty central directory file for the directory synchronization. It has the internal identification LFILE number 160.
CNTnnn.SYS5 An unloaded copy of an empty Con-nect system file in the format used by the Cabinet Transfer utilities. The internal identification LFILE number for this data set is 224.
CNTnnn.SYS6 An unloaded copy of an empty Con-nect Text Retrieval document file. The internal identification LFILE number for this data set is 233.
CNTnnn.SYS7 An unloaded copy of an empty Con-nect Text Retrieval vocabulary file. The internal identification LFILE number for this data set is 231.
CSxnnn.INPL INPL data set containing components for the language-dependent parts of Con-nect and internal error text (language-dependent).
CSxnnn.HLPS Con-nect help screens (language-dependent).

Copying Data Sets to a z/OS 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 all data sets from tape to disk.

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

  • Modify the following sample job according to your requirements:

    //SAGTAPE JOB SAG,CLASS=1,MSGCLASS=X
//* ---------------------------------
//COPY EXEC PGM=IEBGENER
//SYSUT1 DD DSN=COPY.JOB,
// DISP=(OLD,PASS),
// UNIT=(CASS,,DEFER),
// VOL=(,RETAIN,SER=tape-volser),
// LABEL=(2,SL)
//SYSUT2 DD DSN=hilev.COPY.JOB,
// DISP=(NEW,CATLG,DELETE),
// UNIT=3390,VOL=SER=disk-volser,
// SPACE=(TRK,(1,1),RLSE),
// DCB=*.SYSUT1
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//

    where:

    tape-volser is the VOLSER of the tape, for example: T12345,
    hilev is a valid high-level qualifier, and
    disk-volser is the VOLSER of the disk.

  • Execute the job to copy the data set COPY.JOB to your disk.

Step 2: Modify hilev.COPY.JOB on Your Disk

  • Modify hilev.COPY.JOB according to your requirements:

    Set EXPDT to a valid expiration date, for example, 99365.

    Set HILEV to a valid high-level qualifier, for example, USERLIB.

    Set LOCATION to a storage location, for example, STORCLAS=ABC or UNIT=3390,VOL=SER=USR123.

Step 3: Submit COPY.JOB

  • Execute hilev.COPY.JOB to copy single, multiple, or all data sets to your disk.

z/VSE Installation Medium

The following topics are covered below:

Data Sets

The installation medium contains the data sets listed below. The sequence of the data sets is shown in the Software AG Product Delivery Report which accompanies the installation medium.

Data Set Name Contents
CNTnnn.INPL INPL data set containing language-independent components of the Con-nect processor and transport service.
CNTnnn.LIBR Contains the CTMOD module which must be linked to the Natural nucleus and the source library for the transport service. This data set is specifically for the transport service.
CNTnnn.LIBJ Example installation jobs.
CNTnnn.SYS2 An unloaded copy of an empty Con-nect help system file. This file has the internal identification LFILE number 222.
CNTnnn.SYS3 An unloaded copy of an empty Con-nect spool file. This file is used for the external mailing facility, e.g., Con-nect multi-node. It has the internal identification LFILE number 223.
CNTnnn.SYS4 An unloaded copy of an empty central directory file for the directory synchronization. It has the internal identification LFILE number 160.
CNTnnn.SYS5 An unloaded copy of an empty Con-nect system file in the format used by the Cabinet Transfer utilities. The internal identification LFILE number for this data set is 224.
CNTnnn.SYS6 An unloaded copy of an empty Con-nect Text Retrieval document file. The internal identification LFILE number for this data set is 233.
CNTnnn.SYS7 An unloaded copy of an empty Con-nect Text Retrieval vocabulary file. The internal identification LFILE number for this data set is 231.
CSxnnn.INPL INPL data set containing components for the language-dependent parts of Con-nect and internal error text (language-dependent).
CSxnnn.HLPS Con-nect help screens (language-dependent).

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 from tape to disk. All other data sets can be installed directly from the tape.

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.

BS2000 Installation Medium

The following topics are covered below:

Data Sets

The installation medium contains the files listed below. The sequence of the files is shown in the Software AG Product Delivery Report which accompanies the installation medium.

Data Set Name Content
CNTnnn.JOBS Example installation jobs.
CNTnnn.INPL INPL data set containing language-independent components of the Con-nect processor and transport service.
CNTnnn.MOD Contains the CTMOD module which must be linked to the Natural nucleus. This data set is specifically for the transport service.
CNTnnn.SYS2 An unloaded copy of an empty Con-nect help system file. This file has the internal identification LFILE number 222.
CNTnnn.SYS3 An unloaded copy of an empty Con-nect spool file. This file is used for the external mailing facility, e.g., Con-nect multi-node. It has the internal identification LFILE number 223.
CNTnnn.SYS4 An unloaded copy of an empty central directory file for the directory synchronization. It has the internal identification LFILE number 160.
CNTnnn.SYS5 An unloaded copy of an empty Con-nect system file in the format used by the Cabinet Transfer utilities. The internal identification LFILE number for this data set is 224.
CNTnnn.SYS6 An unloaded copy of an empty Con-nect Text Retrieval document file. The internal identification LFILE number for this data set is 233.
CNTnnn.SYS7 An unloaded copy of an empty Con-nect Text Retrieval vocabulary file. The internal identification LFILE number for this data set is 231.
CSxnnn.INPL INPL data set containing components for the language-dependent parts of Con-nect and internal error text (language-dependent).
CSxnnn.HLPS Con-nect help screens (language-dependent).

Copying Files to a BS2000 Disk

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

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

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

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

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

This section explains how to copy all files from tape to disk.

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

This step is not necessary if you have already copied the library SRVvrs.LIB from another Software AG installation tape. For further information, refer to the element #READ-ME in this library. The library SRVvrs.LIB is stored on the tape as a sequential file named SRVvrs.LIBS containing LMS commands. The current version vrs can be obtained from the Software AG Product Delivery Report.

  • Execute the following commands to convert SRVvrs.LIBS into an LMS library: 

    /IMPORT-FILE  SUPPORT=*TAPE(FILE-NAME=SRVvrs.LIBS,-
/   VOLUME=volser, DEV-TYPE=tape-device)
/ADD-FILE-LINK  LINK-NAME=EDTSAM, FILE-NAME=SRVvrs.LIBS,-
/   SUPPORT=*TAPE(FILE-SEQ=3), ACC-METH=*BY-CAT,-
/   BUF-LEN=*BY-CAT, REC-FORM=*BY-CAT, REC-SIZE=*BY-CAT
/START-EDT 
@READ  '/'
@SYSTEM 'REMOVE-FILE-LINK  EDTSAM'
@SYSTEM 'EXPORT-FILE  FILE-NAME=SRVvrs.LIBS'
@WRITE  'SRVvrs.LIBS'
@HALT
/ASS-SYSDTA  SRVvrs.LIBS
/MOD-JOB-SW  ON=1
/START-PROG  $LMS
/MOD-JOB-SW  OFF=1
/ASS-SYSDTA  *PRIMARY

    where:

    tape-device is the device type of the tape, for example, TAPE-C4, and
    volser is the VOLSER of the tape (see the Software AG Product Delivery Report).

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

  • Call the procedure P.COPYTAPE in the library SRVvrs.LIB to copy the procedure COPY.PROC to disk: 

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

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

Step 3: Copy all Product Files from Tape to Disk

  • Enter the procedure COPY.PROC to copy all product files to disk: 

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

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

    The result of this procedure is written to the file L.REPORT.SRV.