Verifying Initial Installation

Products

• Allocate DASD Space and Placement

Issue/Introduction

What do I need to do to verify CA-Allocate is functioning properly after the initial installation?

 

Environment

Release:
Component: ALLOC

Resolution

These basic items will verify both functionality and provide some familiarity with the CA-Allocate product:

*Test STC commands:
Install, Remove, Parmref, Refresh, Stop, Qrebuild, Qsync, Cleanup
(Can be done via oper cmd or in the STC JCL)

Via syslog: /F STCname, CLEANUP

OR

file://* EXAMPLE : STC JCL FOR  CA-Allocate
file://*******************************************************
file://ALLOC EXEC PGM=VDSST451,TIME=1440,REGION=0M,
// PARM=('INSTALL')
file://* PARM=('CLEANUP')
file://* PARM=('PARMREF')
file://* PARM=('QREBUILD')
file://* PARM=('QSYNC')
file://* PARM=('REFRESH')
file://* PARM=('REMOVE')
file://* PARM=('STOP')
file://STEPLIB DD DISP=SHR,DSN=YOUR.ALLOCATE.LOADLIB
file://PARMS DD DISP=SHR,DSN=YOUR.ALLOCATE.PARMLIB
ETC ETC

*Test functionality of all  CA-Allocate environments:
ACS
ALLOC
DEFINE
EXTEND
EOV
EOV_VSAM
OLD
PREALLOC
QUOTA
RENAME
RELEASE
SCRATCH
SPACE

It is suggested to use as many different dataset types & dataset organizations as possible, especially the ones commonly used at your site.
SMS / non-SMS / VSAM / nonVSAM / Single & multi-vol data sets / etc.

TESTING TIPS:
When setting up such testing, it can be easier to de-bug ASRs / JCL when they are kept small, for example, having one ASR & JCL to TEST the EOV environment and having another set for each environment until you are sure the basic functionality is correct before combining them into one larger ASR / test JCL. Setup the ASRs with the variables you believe will be most useful and commonly used at your site. This also provides validation of the variables you specify.

EXAMPLE:
IF &JOB NE jobnam* THEN EXIT CODE(0)
IF &USER NE 'userid' THEN EXIT CODE(0)

IF &VAMENVIR EQ 'ALLOC'

THEN

DO

WRITE 'DATASET NAME = &DSN'

IF &SMS NE 'N' THEN SET &SG = 'PRODPOOL''

WRITE 'STORAGE GROUP = &SG'

END

IF &VAMENVIR EQ 'SPACE'

THEN

DO

IF &DSN(3) = 'TESTSNC2'

THEN

DO

IF &IFCAT = 'Y'
THEN

DO

SET &SNC2 = 'D'

IF &SNC2RC = 0 THEN EXIT CODE(0)

WRITE 'DENYING ALLOCATION TO PREVENT NOT CATLG 2 CONDITION'

EXIT CODE(8)

END

END

END

NOTE: in this example the use of the &JOB & &USER variables to limit
the effect of the test ASR on other users of the system where the Allocate STC is currently 'active'. Bringing up the STC in 'dormant' mode is another option. Using the WRITE statement can also be helpful.

*Test functionality of 'major' CA-Allocate variables:
It is probably not feasible to test every single variable as there are hundreds of them. However, setting up a few tests to verify the functionality of the major ones your site expects to be using is highly recommended. Add these to the test ASRs to be used for testing the various environments.

*Test functionality of 'major'  CA-Allocate sysparms:
It is probably not feasible to test every single sysparm as your site may not need to use all of them. However, setting up a few tests to verify the functionality of the major ones your site expects to be using is highly recommended.