Installation - syncsort_cobol_migration_manager - syncsort_clone_center - syncsort_space_recovery_system - syncsort_scc_monitor - syncsort_simulate_2000 - syncsort_allocation_control_center - Latest

Installation checklist

The following checklist summarizes the steps required to install SCC products.

1. Create the distribution libraries on your host machine. The product distribution libraries can be delivered in various formats, but the end result is a set of software distribution libraries on your host system. For more information, Software delivery
2. Create the production data sets:
   • DTS.R71.LOADLIB
   • DTS.R71.PARMLIB
   • DTS.R71.RULECKPT
   • DTS.R71.ISPFLIB
   • DTS.R71.DIFVAR
   • DTS.R71.RULELIB
   • DTS.R71.RPTLIB
3. Authorize the load library.
4. Copy the JCL for the DIF started task to a system procedure library.
5. Copy members to the DIF parameter library: DTS.R71.PARMLIB.
6. Copy load modules to the DIF authorized load library.
7. Run the Installation Verification Procedure (IVP) jobs. For more information, see Step 10 - Perform the Product IVPs.

Service level and product release information

When the packages a new set of distribution libraries, the current Julian date is assigned as the Service Level of the software. The service level can be identified from the file name.

Product licensing

All product and customer information is encrypted into a single self-signed license key. Whenever license changes are needed, you must obtain a new key file from your distributor. Save the new key in the LICENSE member in the parameter library:

DTS.R71.PARMLIB(LICENSE)

After updating the license member, you may want to validate the new key. The DIF CHECK LICENSE command can be used to validate the new license information without restarting the product. For more information, see “CHECK” on page 5-13.

Maintenance releases

If you are currently running the products and have obtained the latest release for maintenance, always install the most current version of the Dynamic Install Facility (DIF) along with the products you are updating. Many new features and fixes require corresponding updates to DIF.

You can obtain the DIF release information from your current DIF started task by issuing the DIF status command: F DIF,STATUS. To determine whether DIF should be updated, check the product release information in the installation distribution library:

DTS.R71.SLyyddd.LOADLIB(DTSRELI)

If the distribution libraries contain a new version of DIF, install the new version by running install step 5.

Step 1 - create the production libraries

• DTS.R71.LOADLIB

  This authorized library will contain DIF and product load modules. The Dynamic Install Facility (DIF) is a started task primarily responsible for installing the products, and DIF must be executed from an authorized load library. The next install step explains how to authorize the DIF load library.

• DTS.R71.PARMLIB

  The parameter library contains members that automatically start SCC products and validate product license keys. It also contains the rule definitions that control the products. Since this file may contain rules for several products, allocate enough space to allow for frequent updates.

• DTS.R71.RULECKPT

  The checkpoint data set stores successful rule conversions in a compiled format. During product initialization after an IPL, any errors introduced to the rule definitions can be recovered by using the last successful rule conversion.

• DTS.R71.DIFVAR

  The DIF variable data set stores the DEFVAR SYSTEM variables used by the products. This file is mainly used by Monitor to store variable names and their values.

• DTS.R71.ISPFLIB

  This library contains the DIF and SCC ISPF interface panels, Clists, and tables.

• DTS.R71.RULELIB
  The SCC rule library contains your installation-developed rules for SCC products. This step creates the library.

  Note: During the customization process for Monitor, sample rules can be found in DTS.R71.SLyyddd.SAMPLIB.
• DTS.R71.RPTLIB

  The SCC report library contains JCL, PROCs, and copybook members used to create data for report generation in the products. It also contains members used for the web requests to format report data for browser output.

        //INSTEP01 JOB ... (RC=0 EXPECTED)
        //*
        //* CREATE THE DIF PRODUCTION DATA SETS
        //*
        //* REQUIRED CHANGES:
        //*
        //* STEP01 - SELECT A VOLSER FOR THE LIBRARIES
        //* STEP02 - SELECT A VOLSER FOR THE DIFVAR VSAM FILE
        //*
        //STEP01 EXEC PGM=IEFBR14
        //DD1 DD DSN=DTS.R71.LOADLIB,
        // DISP=(NEW,CATLG,DELETE),UNIT=SYSALLDA,
        // SPACE=(CYL,(5,2,80)),VOL=SER=??????,
        // DCB=(RECFM=U,BLKSIZE=6144,DSORG=PO)
        //DD2 DD DSN=DTS.R71.PARMLIB,
        // DISP=(NEW,CATLG,DELETE),UNIT=SYSALLDA,
        // SPACE=(CYL,(5,2,80)),VOL=REF=*.DD1,
        // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120,DSORG=PO)
        //DD3 DD DSN=DTS.R71.RULECKPT,
        // DISP=(NEW,CATLG,DELETE),UNIT=SYSALLDA,
        // SPACE=(CYL,(5,2,80)),VOL=REF=*.DD1,
        // DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096,DSORG=PO)
        //DD4 DD DSN=DTS.R71.ISPFLIB,
        // DISP=(NEW,CATLG,DELETE),UNIT=SYSALLDA,
        // SPACE=(CYL,(5,2,80)),VOL=REF=*.DD1,
        // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120,DSORG=PO)
        //DD5 DD DSN=DTS.R71.RULELIB,
        // DISP=(NEW,CATLG,DELETE),UNIT=SYSALLDA,
        // SPACE=(CYL,(5,2,80)),VOL=REF=*.STEP01.DD1,
        // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120,DSORG=PO)
        //DD6 DD DSN=DTS.R71.RPTLIB,
        // DISP=(NEW,CATLG,DELETE),UNIT=SYSALLDA,
        // SPACE=(CYL,(5,2,80)),VOL=REF=*.DD1,
        // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120,DSORG=PO)
        //STEP02 EXEC PGM=IDCAMS
        //SYSPRINT DD SYSOUT=*
        //IN DD *
        //$DUMMY
        //SYSIN DD *
        DEFINE CLUSTER(NAME(DTS.R71.DIFVAR) VOLUME(??????) +
        SHAREOPTIONS(2) +
        RECORDSIZE(56 254) CYL(2 2) INDEXED KEYS(52 0) )
        REPRO INFILE(IN) OUTDATASET(DTS.R71.DIFVAR)
        LISTCAT ENTRY(DTS.R71.DIFVAR) ALL
        //

Step 2 - Authorize the Load Library

The Dynamic Install Facility (DIF) must be executed from an authorized load library. The manual assumes the load library will be created in the first installation step, and subsequent steps will link DIF and product load modules into an authorized library. This section explains how to authorize the load library.

On z/OS systems, the APF authorized data sets can be listed by an operator command, and modified without an IPL. The following console command can be used to list the current APF authorized libraries found on your system:

D PROG,APF,ALL
      

To add the load library to the list of APF libraries, add an APF statement to your existing APF list in member SYS1.PARMLIB(PROGnn). For example, the last line in the following PROGnn entry establishes an authorized load library on the DTS001 volume. You can add a similar statement to your PROGnn member, using the data set and volume names matching the ones in the first install step.

APF FORMAT(DYNAMIC)
APF ADD DSNAME(SYS1.CMDLIB) VOLUME(******)
APF ADD DSNAME(SYS1.CSSLIB) VOLUME(******)
APF ADD DSNAME(SYS1.ISAMLPA) VOLUME(******)
.
.
.
APF ADD DSNAME(DTS.R71.LOADLIB) VOLUME(DTS001)
      

If FORMAT(DYNAMIC) has been specified in the PROGnn member, the following command can be issued from the console to authorize the load library that resides on volume DTS001:

SETPROG APF,ADD,DSNAME=DTS.R71.LOADLIB,VOLUME=DTS001
      

SETPROG APF,ADD,DSNAME=DTS.R71.LOADLIB,SMS
      

For more information about authorizing libraries, examine z/OS MVS Initialization and Tuning Reference Document Number SA22-7592-nn.

Step 3 - Copy the JCL for DIF to a system procedure library

Copy the DIF member from the SCC installation library to a system procedure library: SYS1.PROCLIB or an equivalent library.

Once SCC is in a production environment, a START DIF command should be added to SYS1.PARMLIB(COMMNDnn) to automatically start DIF during system initialization.

The PARMLIB DD statement can be used to automatically start the products during DIF initialization.

The following JCL can be found in the DIF member of the Storage Control Center installation library: DTS.R71.SLyyddd.INSTLIB. Fields represented with bold type should be modified to match installation standards before the DIF member is placed in a system procedure library.

//*********************************************************************
//*                                                                   *
//* DTS SOFTWARE DYNAMIC INSTALL FACILITY (DIF)                       *
//*                                                                   *
//*********************************************************************
//DIF PROC P=
//DIF EXEC PGM=DIF,DYNAMNBR=20,TIME=1440,REGION=4M,
// PARM=’CMDCHAR=#,TSO=NO,&P'
//STEPLIB DD DISP=SHR,DSN=DTS.R71.LOADLIB
//PARMLIB DD DISP=SHR,DSN=DTS.R71.PARMLIB
// DD DISP=SHR,DSN=DTS.R71.RULELIB
// DD DISP=SHR,DSN=DTS.R71.RPTLIB
//RULECKPT DD DISP=SHR,DSN=DTS.R71.RULECKPT
//HTML DD DISP=SHR,DSN=DTS.R71.RPTLIB
//RTMDB DD DUMMY
//LPALIB DD DISP=SHR,DSN=SYS1.LPALIB
//*MLPALIB DD DISP=SHR,DSN=mlpa.library
//SYSPRINT DD SYSOUT=A
//SYSABEND DD SYSOUT=A
//SYSEXEC DD DISP=SHR,DSN=DTS.R71.RPTLIB
//*SYSPROC DD DISP=SHR,DSN=clist.library
//*SYSTSPRT DD UNIT=VIO,SPACE=(CYL,1)
//*SYSTSIN DD DUMMY
      

Step 4 - Copy members from distribution to production libraries

This step copies members from the distribution libraries to the parameter, ISPF, and rule libraries. This process synchronizes the IVP rules and controlled members in the distribution libraries, with the verification procedures and the programs delivered with this release.

This installation step will replace any existing members with two exceptions:

• LICENSE: This member contains sample License Keys. Your installation materials include the license keys to activate the products. After running this installation step, replace the sample license keys in the parameter library with the ones provided with your installation materials.
• START00: The START00 member in the parameter library is read by the DIF started task during DIF initialization. By default, the distribution copy of START00 does not start any SCC products. After performing product verification and customization, you can modify the START00 member in the parameter library to automatically activate products during DIF initialization. The START00 member delivered in the distribution library contains sample commands to activate each SCC product.

• IVP members: The IVP members in the SCC rule library contain the rules statements used for the installation verification procedures in the next chapter.
• ISPF members: The ISPF members in the ISPF library contain the Clist, panel, and message members used for the DIF and SCC ISPF interface.
• @members: Monitor contains members that should not be changed by your installation and should always be refreshed during any maintenance releases. These members all have an “@” prefixed to the member name. This installation step will refresh the “@” members found in your SCC rule library: DTS.R71.RULELIB.
  The following JCL can be found in the INSTEP04 member of the Storage Control Center installation library (DTS.R71.SLyyddd.INSTLIB). Fields represented with bold type should be modified to match installation standards before submission.

  JCL to Copy members from the distribution to the production libraries

  //INSTEP04 JOB ...
  //*
  //* THIS STEP WILL COPY MEMBERS INTO THE DTS PARAMETER, ISPF, AND
  //* RULE LIBRARIES
  //*
  //* HLQ=DTS HLQ FOR DISTRIBUTION DATA SETS
  //* SL=SLYYDDD SERVICE LEVEL FOR THE INSTALLATION TAPE
  //*
  //COPYPRM PROC HLQ=DTS,SL=SLYYDDD
  //STEP01 EXEC PGM=IEBCOPY
  //INSTLIB DD DISP=SHR,DSN=&HLQ..R71.&SL..INSTLIB
  //ISPFLIB DD DISP=SHR,DSN=&HLQ..R71.&SL..ISPFLIB
  //SAMPLIB DD DISP=SHR,DSN=&HLQ..R71.&SL..SAMPLIB
  //RPTLIB DD DISP=SHR,DSN=&HLQ..R71.&SL..RPTLIB
  //DIFPARM DD DISP=SHR,DSN=&HLQ..R71.PARMLIB
  //DIFISPF DD DISP=SHR,DSN=&HLQ..R71.ISPFLIB
  //RULELIB DD DISP=SHR,DSN=&HLQ..R71.RULELIB
  //DIFRPT DD DISP=SHR,DSN=&HLQ..R71.RPTLIB
  //SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,1)
  //SYSUT4 DD UNIT=SYSALLDA,SPACE=(CYL,1)
  //SYSIN DD DISP=SHR,DSN=&HLQ..R71.&SL..INSTLIB(COPYPRM)
  //SYSPRINT DD SYSOUT=*
  // PEND
  //S01 EXEC COPYPRM
  //

Step 5 - IEBCOPY Load Modules to an Authorized Library

This installation step assumes that the load library has been created and authorized by install steps 1 and 2.

The following JCL uses IEBCOPY to copy the load modules from the distribution library to the load library:

DTS.R71.LOADLIB

The following JCL can be found in the INSTEP05 member of the Storage Control Center installation library (DTS.R71.SLyyddd.INSTLIB). Fields represented with bold type should be modified to match installation standards before submission.

//INSTEP05 JOB ... (RC=0 EXPECTED)
//*
//* THIS JOB WILL IEBCOPY DTS MODULES FROM THE DISTRIBUTION LOAD
//* LIBRARY INTO AN APF AUTHORIZED LIBRARY.
//*
//* NOTE 1: FOR z/OS INSTALLS ONLY! HITACHI VOS3 AND FUJITSU MSP
//* MUST USE THE LINKAGE-EDITOR TO MOVE MODULES INTO AN
//* AUTHORIZED LOAD LIBRARY.
//*
//* NOTE 2: DO NOT USE ISPF 3.3 TO MOVE THE MEMBERS. THE MODULE ALIAS
//* INFORMATION WILL BE LOST!
//*
//COPYAUTH EXEC PGM=IEBCOPY
//LOADLIB DD DISP=SHR,DSN=DTS.R71.SLYYDDD.LOADLIB
//AUTHLIB DD DISP=SHR,DSN=DTS.R71.LOADLIB
//SYSIN DD *
COPYMOD INDD=((LOADLIB,R)),OUTDD=AUTHLIB
//

Figure - JCL to IEBCOPY Modules to an APF Authorized Library

Step 6 - LINK Load Modules to an Authorized Library

This installation step assumes that the load library has been created and authorized by install steps 1 and 2.

The following JCL uses the linkage-editor to copy the load modules from the distribution library to the load library:

DTS.R71.LOADLIB

The following JCL can be found in the INSTEP06 member of the Storage Control Center installation library (DTS.R71.SLyyddd.INSTLIB). Fields represented with bold type should be modified to match installation standards before submission.

//INSTEP06 JOB ... (RC=0 EXPECTED)
//*
//* THIS PROCEDURE WILL LINK MODULES INTO AN APF
//* AUTHORIZED LIBRARY.
//*
//* HLQ=DTS HLQ FOR DISTRIBUTION DATA SETS
//* SL=SLYYDDD SERVICE LEVEL FOR THE INSTALLATION TAPE
//* AUTH= NAME OF AUTHORIZED LIBRARY
//* LINKER=IEWL LINKAGE-EDITOR (LNKEDT FOR HITACHI VOS3)
//* MEM=
//*
//LINKDTS PROC HLQ=DTS,SL=SLYYDDD,LINKER=IEWL,MEM=,
// AUTH=DTS.R71.LOADLIB
//*
//* LINK REENTRANT MODULES
//*
//LINK1 EXEC PGM=&LINKER,PARM='LIST,RENT,NCAL'
//SYSLMOD DD DISP=SHR,DSN=&AUTH
//PRODLIB DD DISP=SHR,DSN=&HLQ..R71.&SL..LOADLIB
//SYSLIN DD DISP=SHR,DSN=&HLQ..R71.&SL..INSTLIB(&MEM.R)
//SYSUT1 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSPRINT DD SYSOUT=*
//*
//* LINK NON-REENTRANT MODULES
//*
//LINK2 EXEC PGM=&LINKER,PARM='LIST,NORENT,NCAL'
//SYSLMOD DD DISP=SHR,DSN=*.LINK1.SYSLMOD
//PRODLIB DD DISP=SHR,DSN=*.LINK1.PRODLIB
//SYSLIN DD DISP=SHR,DSN=&HLQ..R71.&SL..INSTLIB(&MEM)
//SYSUT1 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSPRINT DD SYSOUT=*
// PEND
//S01 EXEC LINKDTS,MEM=LINKDIF LINK DYNAMIC INSTALL FACILITY
//S02 EXEC LINKDTS,MEM=LINKACC LINK ACC/SRS/SMSDEBUG
//S03 EXEC LINKDTS,MEM=LINKMON LINK MONITOR/ABC
//S04 EXEC LINKDTS,MEM=LINKDSL LINK DLIMIT
//S05 EXEC LINKDTS,MEM=LINKEXT LINK EASY/EXIT
//

Step 7 - Install the ISPF Interface

The products have an ISPF interface. The main panel (DTS@PRIM) contains options for the DIF, MON, DLimit, DCC, ABC, SMSDEBUG, and MON-TS7700 products.

The following steps can be used to install and use the ISPF interface. Install step 4 created the members referenced in the following instructions. The members can be found in the ISPF library: DTS.R71.ISPFLIB.

Step 7.1

Modify the REXX member CDIFINIT in the ISPF data set to specify the appropriate data set names created during the install process. This REXX routine will allocate and concatenate the required data set names used by the ISPF interface and then display the main panel. The updates should be limited to the HLQISPF and HLQLOAD variables shown below.

/* REXX *****************************************************/
/* DIF MAIN ISPF START APPLICATION */
/************************************************************/
/* ALLOCATE PROPER LIBRARIES AND START THE DIF APPLICATION: */
/* */
/* ISPF - WHERE THE PANELS, MESSAGE, AND SKELETON LIBRARIES */
/* LOAD - WHERE THE LOAD LIBRARY IS LOCATED */
/* */
/************************************************************/
ARG NXTPANEL
HLQISPF = 'DTS.R71'
HLQLOAD = 'DTS.R71'
DTSPLIB = HLQISPF||'.ISPFLIB'
ADDRESS ISPEXEC 'VPUT (DTSPLIB) PROFILE'
/************************************************************/
/* SET THE DIF CLISTS AND LIBRARIES TO BE FIRST IN CONCAT */
/************************************************************/
ADDRESS ISPEXEC
"LIBDEF ISPLLIB DATASET ID('"HLQLOAD".LOADLIB') "
IF RC <> 0 THEN SIGNAL ERROR_DIF1
"LIBDEF ISPPLIB DATASET ID('"HLQISPF".ISPFLIB') "
IF RC <> 0 THEN SIGNAL ERROR_DIF2
"LIBDEF ISPMLIB DATASET ID('"HLQISPF".ISPFLIB') "
IF RC <> 0 THEN SIGNAL ERROR_DIF3
"LIBDEF ISPSLIB DATASET ID('"HLQISPF".ISPFLIB') "
IF RC <> 0 THEN SIGNAL ERROR_DIF4
ADDRESS TSO
"ALTLIB ACTIVATE DATASET('"HLQISPF".ISPFLIB') APPLICATION(CLIST) "
IF RC <> 0 THEN SIGNAL ERROR_DIF5
/************************************************************/
/* DISPLAY AND PROCESS THE MAIN SELECTION MENU */
/************************************************************/
IF NXTPANEL \= '' THEN
ADDRESS ISPEXEC 'SELECT '||NXTPANEL
ELSE
ADDRESS ISPEXEC 'SELECT PANEL(DTS@PRIM)'
IF RC > 8 THEN SIGNAL ERROR_DIF6
ADDRESS ISPEXEC
"LIBDEF ISPLLIB" /* RETURN LIB TO DEFAULT */
"LIBDEF ISPPLIB" /* RETURN LIB TO DEFAULT */
"LIBDEF ISPMLIB" /* RETURN LIB TO DEFAULT */
"LIBDEF ISPSLIB" /* RETURN LIB TO DEFAULT */
ADDRESS TSO
"ALTLIB DEACTIVATE APPLICATION(CLIST)"
EXIT RC
/************************************************************/
/* ERROR ROUTINES */
/************************************************************/
ERROR_DIF1:
SAY 'UNABLE ALLOCATE LOADLIB, RC='RC
EXIT 8
ERROR_DIF2:
SAY 'UNABLE ALLOCATE ISPPLIB, RC='RC
EXIT 8
ERROR_DIF3:
SAY 'UNABLE ALLOCATE ISPMLIB, RC='RC
EXIT 8
ERROR_DIF4:
SAY 'UNABLE ALLOCATE ISPSLIB, RC='RC
EXIT 8
ERROR_DIF5:
SAY 'ERROR DURING ALTLIB ACTIVATE, RC='RC
EXIT 8
ERROR_DIF6:
SAY 'ERROR DURING PANEL DISPLAY, RC='RC
EXIT 8

Step 7.2

%D +DTS - DTS Software Products
.
.
.
&ZSEL = TRANS ( TRUNC (&ZCMD,'.')
.
.
.
D,'CMD(CDIFINIT)'

Step 7.3

Update the TSO LOGON proc or LOGON clist to include the ISPF data set (DTS.R71.ISPFLIB) on the SYSPROC DD concatenation.

Step 8 - OS Selection for Fujitsu MSP or Hitachi VOS3 Only

For Fujitsu MSP or Hitachi VOS3 systems, the OPSYS= parameter must be specified in the DIF PARM field to select the OS type and level. For more information, examine “DIF - PARM Information” on page 6-7. The following example shows the use of the OPSYS parameter on an MSPEX system:

PARM='CMDCHAR=%,TSO=NO,DIFTSO=DIFTSO,OPSYS=MSPEX'

DIF also provides a batch interface that is used by SCC report programs. For example, the SRSSMF program used to extract and print SRS recovery information uses the DIFBATCH interface. Since no parameter field is available to set the OS type and level, the following zap must be applied to select the appropriate operating system.

The following JCL can be found in the INSTEP08 member of the Storage Control Center installation library (DTS.R71.SLyyddd.INSTLIB). Fields represented with bold type should be modified to match installation standards before submission.

//INSTEP08 JOB ... (RC=0 EXPECTED)
//*
//* FUJITSU MSP AND HITACHI VOS3 ONLY!!!
//*
//* TO SPECIFY THE OPSYS PARAMETER FOR DIFBATCH JOBS,
//* SELECT THE APPROPRIATE OS AND REMOVE THE ASTERISK
//* FROM THE REP CARD.
//*
//STEP1 EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DISP=SHR,DSN=DTS.R71.LOADLIB
//SYSIN DD *
NAME DIF0010 DIF0013
IDRDATA DTS22521
VER 0002 E7C4C37E,D5D64040,40404040
*REP 0002 D6D7E2E8,E27ED4E2,D6C5E740 OPSYS=MSPEX
*REP 0002 D6D7E2E8,E27ED4E2,D6C5F2F0 OPSYS=MSPE20
*REP 0002 D6D7E2E8,E27ED4E2,D6C5F2F0,C1C5 OPSYS=MSPE20AE
*REP 0002 D6D7E2E8,E27EE5D6,E2F34040 OPSYS=VOS3
*REP 0002 D6D7E2E8,E27EE5D6,E2F3C5E2 OPSYS=VOS3ES
*REP 0002 D6D7E2E8,E27EE5D6,E2F3C5E2,F1 OPSYS=VOS3ES1
*REP 0002 D6D7E2E8,E27EE5D6,E2F3C1E2 OPSYS=VOS3AS
*REP 0002 D6D7E2E8,E27EE5D6,E2F3C1E2,F3F1 OPSYS=VOS3AS31
*REP 0002 D6D7E2E8,E27EE5D6,E2F3C6E2 OPSYS=VOS3FS
*REP 0002 D6D7E2E8,E27EE5D6,E2F3C6E2,F1 OPSYS=VOS3FS1
      

Figure. Set OPSYS Parameter for DIFBATCH

Step 9 - Update the LICENSE and STARTnn Members

During the product evaluation period, the keys provided with the trial will activate the products for the trial period. No CPU validation will occur during the trial period. After the trial period, only purchased products and options will run on licensed CPU(s). If installed on another CPU, the products will not function.

New Installation - One or more license keys are required for each purchased product. The sample keys delivered with the installation library are not valid. The license keys provided by your sales representative should be added to the parameter library:

DTS.R71.PARMLIB(LICENSE)

Version Upgrade - For customers performing a version upgrade, license keys produced for SCC release 5.1 products will work with release 7.1, and can be copied to the LICENSE member in the new parameter library. For companies upgrading from a pre-5.1 environment, please contact your sales representative for a new license.

The sample START00 member delivered in the installation library will not automatically start any of the SCC products during DIF initialization. To automatically start products, edit the following member in the parameter library and uncomment the appropriate START commands.

DTS.R71.PARMLIB(START00)

Step 10 - Perform the Product IVPs

The SCC Product Installation Guide, the manual you are currently reading, explains how to install the distribution libraries on your system, and how to use the distribution libraries to build the production libraries. After the production libraries have been built, the installer should proceed to the appropriate product manuals to perform product verification and customization.

Installation step 4 copied the rule members used for installation verification (IVRAS, IVRMON, IVRRTM, IVRDSR, IVRDSL, IVRABC, IVREXT, IVRJCL) to the SCC rule library: DTS.R71.RULELIB. After you perform minor customization, these IVP rule members will be used by the product’s verification jobs to verify that the product is installed and functioning correctly.

Each product manual contains a chapter that documents the product verification process. Use the following list to continue the product installation and verification procedures:

• ABC: Continue with the chapter “PRODUCT VERIFICATION” on page 3-1 in the ABC User’s Guide
• ACC/SRS: Continue with the chapter “PRODUCT VERIFICATION” on page 2-1 in the ACC/SRS User’s Guide
• DLimit: Continue with the chapter “PRODUCT VERIFICATION” on page 3-1 in the SCC DLimit User’s Guide
• EXT: Continue with the chapter “PRODUCT VERIFICATION” on page 3-1 in the EASY/Exit User’s Guide
• JCLQA: Continue with the chapter “PRODUCT VERIFICATION” on page 3-1 in the JCLQA User’s Guide
• Monitor: Continue with the chapter “PRODUCT VERIFICATION” on page 3-1 in the MON-Snapshot User’s Guide
• RTM: Continue with the chapter “PRODUCT VERIFICATION” on page 3-1 in the MON-RTM User’s Guide

About the Product Rules Language

The individual product manuals provide a limited view of the rules language. For a detailed overview and tutorial of the rules language used by the products, examine “RULES CUSTOMIZATION” of the Rules Language Programming Guide. For a comprehensive explanation of the statement parameters, examine “RULES LANGUAGE REFERENCE” in the same manual.

Manuals on the Website

All SCC product manuals are regularly updated and available on the Precisely Help Center. Customers and companies evaluating Storage Control Center products can download PDF versions of the manuals from the website.

Updates to Manuals

We welcome any comments or suggestions about the manuals. Visit https://support.precisely.com.