Product verification - syncsort_scc_monitor - Latest

IVP step 1 - Allocate and format the DLimit database

A BDAM file must be allocated for DLimit to use as its default database. DLimit keeps information about each disk space account (account name, current space utilization, high-water mark, and budgeted space limit) in the database.

The following JCL allocates the DLimit database and executes program DLMAINT located in DTS.R71.LOADLIB to format the file and create database accounts. Fields represented with bold type in the original may need modification before submission.

//JOBNAME JOB .... (RC=0 expected)
//*
//* THIS IS THE SCC DLIMIT DATABASE FORMAT JOB
//* MESSAGE IEC030I B37-04 IS NORMAL
//* JOB SHOULD TERMINATE WITH RC = 0
//*
//FORMAT  EXEC PGM=DLMAINT
//STEPLIB DD DISP=SHR,DSN=DTS.R71.LOADLIB
//RRDS    DD DSN=DTS.R71.DSLDB,DISP=(NEW,CATLG,DELETE),
//        SPACE=(CYL,(5,2)),UNIT=SYSALLDA
//SYSPRINT DD SYSOUT=*
//SYSIN   DD *
SET DATABASE(BDAM(RRDS FORMAT)) DLSYS
DLADD MODEL MODE(WARN) WARN(80) MAX(100M)
DLADD TEST1 MODEL(MODEL)
DLLIST MODEL
DLLIST TEST1
/*

Figure 3-1. JCL to allocate and format the DLimit database

IVP step 2 - Activate the DLimit database

After defining the DLimit database, add a DD statement for the file in the DIF started task. The following DD statement should be added to the DIF started task for the file created in the previous step:

//RRDS DD DISP=SHR,DSN=DTS.R71.DSLDB

If you were not involved in the initial installation of DLimit or do not have authority to modify a system procedure library, contact the storage administrator or system programmer with access to the DIF started task. For details, see "Step 3 - Copy the JCL for DIF to a system procedure library" in the SCC Product Installation Guide.

If the DIF started task is already active, DIF must be stopped and restarted to complete activation of the database. This can be accomplished with the following console commands. Note: this process will not stop products previously started by DIF.

F DIF,Z S DIF

IVP step 3 - Customize the DLimit verification rules

For DLimit verification testing, customize the IVRDSL member

This member is located in a data set allocated to the PARMLIB DD statement in the DIF started task (usually DTS.SCCR71.RULELIB).

When developing a rule, it is often useful to examine the information used during the decision process. The tracing facility can be enabled with the DSLTRACE DD statement. This facility allows viewing all compare operations that occur during rule processing. For example, allocate the following DD statement to jobs to activate rule tracing:

//DSLTRACE DD DUMMY

Edit the IVRDSL member in the SCC rule library (DTS.SCCR71.RULELIB) and customize rules to your installation requirements.

Sample IVRDSL member

* 
INSTALLATION VERIFICATION RULES FOR DLIMIT
*
CHANGE ??????? TO VALID HLQS
IF THE HLQS MATCH, THE DATASET WILL BE
ASSIGNED TO THE SPECIFIED ACCOUNT.
DEFPROD MESSAGE(LEVEL(I))
DEFRULE IVPRULE
IF &HLQ EQ (??????,??????)
THEN SET &DACCT= &HLQ WRITEMSG(IVPMSG) SET &MODEL = MODEL
DO
IF &DSORG = 'VS'
THEN SET &DACCT{2} = '&DACCT{1}:VSAM'
ISSUE WRITEMSG(IVPMSG)
END
DEFMSG IVPMSG
"DSLIVP: ACCOUNT(S) (&DACCT{1} &DACCT{2}) ASSIGNED TO DATASET &DSNAME"

Figure 3-2. Sample IVRDSL member

IVP step 4 - Start the DLimit product using the verification rules

If the Dynamic Install Facility (DIF) is not active on your system, issue the console command S DIF.

For first-time installs, the installation facility activates and waits for command input. Use the following console command to activate the DLimit product using the IVRDSL rules for verification testing:

F DIF,START DSL IVRDSL

IVP step 5 - Run the DLimit installation verification job

The installation verification job allocates several datasets. The space required for each dataset is added to the current balance in the account assigned by the rule member IVRDSL, and messages are issued. STEP3 of the job creates a large dataset which causes the account balance to be exceeded.

The following JCL can be found in the IVPDSL02 member of the Storage Control Center installation library (DTS.R71.SLyyddd.INSTLIB). Fields that may need modification before submission are indicated in the comments in the original members.

//JOBNAME JOB (RC=0 EXPECTED)
//*
//* THIS IS THE SCC-DLIMIT INSTALLATION VERIFICATION JOB.
//*
//* JCL CHANGES REQUIRED:
//*
//* 1) CHANGE JOBCARD TO MEET INSTALLATION REQUIREMENTS
//* 2) CHANGE JOBLIB DD TO DIF/DLIMIT LOAD LIBRARY
//*
//* 3) HLQ - ANY VALID DATASET NAME MAY BE USED. REPLACE
//* ???? WITH THE SAME HIGH LEVEL QUALIFIERS SPECIFIED
//* IN THE IVRDSL RULE MEMBER.
//*
//* STEP0 DELETES ANY EXISTING DATASETS FROM PRIOR EXECUTIONS
//* STEP1 ALLOCATES A SEQUENTIAL DATASET
//* STEP2 ALLOCATES A VSAM CLUSTER
//* STEP3 ALLOCATES A LARGE SEQUENTIAL DATASET WHICH
//* WILL EXCEED THE SPACE LIMIT FOR THE ACCOUNT.
//* SINCE THE ACCOUNT IS IN 'WARN' MODE, WARNING MESSAGES
//* WILL BE ISSUED, BUT THE ALLOCATION WILL NOT FAIL.
//* MESSAGE DSLIVP WILL BE ISSUED FOR EACH STEP INDICATING
//* THAT SPACE HAS BEEN ASSIGNED TO THE ACCOUNT NAMES.
//* STEP4 DISPLAYS THE CONTENT OF THE ASSIGNED ACCOUNTS.
//*
//JOBLIB  DD DISP=SHR,DSN=DTS.R71.LOADLIB
//STEP0   EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN   DD *
DELETE ???? .DSLIVP.FILE
DELETE ???? .DSLIVP.LARGE
DELETE ???? .DSLIVP.CLUS
SET MAXCC = 0
/*
//* ALLOCATE VSAM CLUSTER
//STEP1   EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN   DD *
DEF CL(NAME(???? .DSLIVP.CLUS) VOL(??????) KILOBYTES(1000) NIXD)
/*
//* ALLOCATE NONVSAM DATASET
//STEP2   EXEC PGM=IEFBR14
//DSLTEST DD DSN=???? .DSLIVP.FILE,DISP=(,CATLG),UNIT=SYSDA,
//         SPACE=(2,(1,1)),AVGREC=M
//*
//* ALLOCATE NONVSAM DATASET TO TRIGGER WARNING
//STEP3   EXEC PGM=IEFBR14
//DSLTEST DD DSN=???? .DSLIVP.LARGE,DISP=(,CATLG),UNIT=SYSDA,
//         SPACE=(100,(1,1)),AVGREC=M
//*
//* DISPLAY ACCOUNT BALANCE
//STEP4   EXEC PGM=DLMAINT
//SYSPRINT DD SYSOUT=*
//SYSIN   DD *
DLLIST ????
DLLIST ???? :VSAM
/*

Figure 3-3. JCL for the DLimit installation verification procedure

IVP step 6 - Run the DLimit report job

The DLimit report job lists account names and datasets assigned to the accounts.

The following JCL can be found in the IVPDSL03 member of the Storage Control Center installation library (DTS.R71.SLyyddd.INSTLIB). Fields represented with bold type in the original may need modification before submission.

//JOBNAME JOB (RC=0 EXPECTED)
//*
//* THE DLIMIT REPORT JOB IS USED TO LIST THE
//* ACCOUNT NAMES AND THE DATASETS ASSIGNED TO THE ACCOUNTS.
//*
// EXEC PGM=DLMAINT
//STEPLIB   DD DSN=DTS.R71.LOADLIB,DISP=SHR
//SYSPRINT  DD SYSOUT=*
//RRDS      DD DSN=DTS.R71.DSLDB,DISP=SHR
//PARMLIB   DD DSN=DTS.R71.PARMLIB,DISP=SHR
//          DD DSN=DTS.R71.RULELIB,DISP=SHR
//SYSUT1    DD SPACE=(CYL,(1,1)),UNIT=SYSDA
//SYSUT2    DD SPACE=(CYL,(1,1)),UNIT=SYSDA
//SYSUT3    DD SPACE=(CYL,(1,1)),UNIT=SYSDA
//SYSOUT    DD SYSOUT=*
//SYSIN     DD *
SET DATABASE(BDAM(RRDS))
SET RULES(NAME(IVRDSL) DDNAME(PARMLIB)) SHOW LIST
REPORT ACCOUNT(DETAIL)
//

Figure 3-4. JCL for the DLimit report job