Starting To Use CA Allocate
The following will be a new chapter added to the CA Allocate Installation Guide that will detail the steps to perform after the installation of the base product.
------
Chapter 6: Beginning to Use CA Allocate
This section describes what you need to know and do before you start using CA Allocate. These topics will help you to quickly setup a running configuration.
This section contains the following topics:
What Current Users Should Do
What New Users Should Do
Copy (or create) members from the CCTVJCL lib into the Parmlib:
Security, APF and LINK Requirements
Start and Stop the VAM Task
Deploy Your Product
Syntax Check ASRs
ASR Compile Failure
Correct Failed Install or Remove
Refresh Active Members
Limit VAM To Your Testing
1. What Current Users Should Do
No changes to your ASRs or Vkgparms are needed for CA Allocate to function as it has been.
Review the Product Information Packet (PIP) and review the recent changes in CA Allocate. Make any needed changes to take advantage of new features.
Review the VAM proc in the CCTVJCL lib to see if you need to make any changes to your VAM proc.
This is all that current users need to do after installing a new release. However, reviewing the remaining topics could be informative.
2. What New Users Should Do
To get some understanding of what CA Allocate does and how to control it, please review these chapters in the User Guide:
1. Introduction
2. Concepts and Facilities
3. Implementation
4. Operation
This paper developed by:
Donald Bell
Principal Support Engineer
CA Technologies, Inc.
3a. Copy (or create) members from the CCTVJCL lib into the Parmlib:
VAM Modify the sample VAM proc with your DSNs for the
STEPLIB and PARMS (Parmlib) DD's.
Copy the VAM proc into a system proclib.
(This member is not needed in the Parmlib.)
SAMPCONF Create member CONFIG. Customization is discussed later.
TESTASRS This is a simple batch job to syntax check your ASRs.
Specify your DSNs. When executed, the Cond Codes are:
CC=0 - The compile was successful
CC=1 - Syntax error, the compile was not successful.
Messages will indicate the problem. This will be described later.
VDSPROG The "EXIT CODE(0)" statement allows you to start VAM and
insure that no allocations are altered until you are ready.
See User Guide, Chapter 3, Implementation,
“Creating an Allocation Selection Routine”.
VDSTORGP Specify the volsers/patterns for your storage groups that VAM will redirect allocations to. See details for this member in the User Guide, Chapter 3, Implementation, "Creating a Storage Group Definition". You will customize this later. (A 'blank' in CC1 indicates a comment.)
If using the QUOTA optional feature, copy these additional members:
QCONFIG This member contains the Quota Configuration
QREBUILD This member contains the QREBUILD ASR
QSCAN This member contains the QSCAN ASR
3b. Create a member in the Parmlib called VKGPARMS and copy the following into it.
*------*
* VKGPARMS FOR CA ALLOCATE *
*------*
SUPLSNV (Y) * Y - ACTIVATE ALLOCATION MANAGER
SUPLSQ (N) * Y - ACTIVATE QUOTA OPTIONAL FEATURE
*
* SPECIFY N FOR ANY ENVIRONMENTS NOT USED - TO IMPROVE PERFORMANCE *
PLSLALLO (Y) * LAUNCH ALLOC ENVIRONMENT
PLSLDEF (Y) * LAUNCH DEFINE ENVIRONMENT
PLSLEOV (Y) * LAUNCH EOV ENVIRONMENT
PLSLEOVV (Y) * LAUNCH EOVVSAM ENVIRONMENT
PLSLEXT (Y) * LAUNCH EXTEND ENVIRONMENT
PLSLOLD (Y) * LAUNCH OLD ENVIRONMENT
PLSLPREA (Y) * LAUNCH PREALLOC ENVIRONMENT
PLSLREL (N) * LAUNCH RELEASE ENVIRONMENT
PLSLRENM (N) * LAUNCH RENAME ENVIRONMENT
PLSLSCR (N) * LAUNCH SCRATCH ENVIRONMENT
PLSLSPA (Y) * LAUNCH SPACE ENVIRONMENT
*
PLSALLNT (Y) * EXCLUDE TAPE FROM ALLOC ENV
PLSALLVL (1) * SPECIFY NUMBER OF ALIAS LEVELS
PLSBYPAS (VDSBYPAS) * THE DD NAME USED TO BYPASS VAM
PLSDDEVT (3390) * DEVICE TYPE FOR SIZEXX VARIABLES
PLSOPT6 (N) * Y - ACTIVE IAM EOV SUPPORT
PLSOPT10 (Y) * SMS ALLOCS GO INTO ALLOC & DEFINE ENV
PLSOPT11 (N) * Y - ALLOW VSAM SUPPORT IN EXTEND
PLSOPT15 (N) * Y - ACTIVATE DFSMSHSM RECALL/RECOVER SUPPORT
PLSOPT16 (N) * Y - ACTIVATE CA DISK NONVSAM EOV SUPPORT
PLSOPT20 (Y) * RANDOMIZE VOLUME SELECTION
PLSOPT23 (Y) * ENABLE EOV EVEN WHEN THE TCBTCT FIELD IS ZERO
PLSOPT27 (Y) * SNC2 EVEN IF NOT REDIRECT
PLSOPT31 (Y) * REDRIVE NEW NONVSAM SMS W/PLOPT10(Y)
PLSOPT37 (N) * Y - EOV MSGS ONLY WHEN DIAGS REQUESTED
PLSOPT38 (N) * Y - DIF MSGS ONLY WHEN DIAGS REQUESTED
PLSOPT39 (N) * Y - DIF MSGS ONLY WHEN DIAGS REQUESTED
PLSOPT41 (Y) * REDRIVE VOL SELECTION IF SNA NEW NONSMS VSAM
PLSEOV69 (Y) * ALLOW EOV EVEN IF DCB EXIT
PLSOPT79 (Y) * PERF - SKIP THE CVAF CALLS
PLSOPT80 (Y) * PERF - SKIP EDT CALL - (Y) ONLY IF ALL 3390
PLSOPT81 (Y) * PERF - ASR RELEASED AFTER 30-SEC. WAIT
PLSOPT82 (Y) * PERF - ACCESS TO CVAF INFO NOT SERIALIZED
PLSOPT94 (Y) * REMOVE PRE & POST HOOKS AT SHUTDOWN
PLSOPT98 (Y) * DIAGS ONLY TO JESYSMSG
PLSOPT99 (N) * Y - EXTENDED DIAGNOSTICS WILL BE CREATED
PLSSABDS (SYSOUT=*) * SYSABEND O/P DEST
PLSSPRDS (SYSOUT=*) * SYSPRINT OUTPUT DEST
PLSXRFDS (SYSOUT=*) * XRF OF COPYBOOKS
*
PLSPRGDS (BELDO05.ALLOC.PARMLIB) * THE DSN OF ALLOC PARMLIB
PLSVDSMB (VDSPROG) * ASR MEMBER NAME, DEFAULT VDSPROG
PLSSTRMB (VDSTORGP) * STORAGE GROUP MEMBER, DEFAULT VDSTORGP
*------*
* THESE VKGPARMS ARE NEEDED IF THE QUOTA OPTIONAL FEATURE IS USED *
*------*
PLSDQTDS (BELDO05.VAM.DISKQTBL) * SPECIFY THE DSN OF THE QUOTA TABLE
PLSQCFMB (QCONFIG) * QUOTA CONFIGURATION MEMBER
PLSQFACT (B) * QUOTA AMOUNTS KEPT IN: B-BYTES; KB-KBYTE
PLSQRBMB (QREBUILD) * QREBUILD ASR MEMBER
PLSQSCMB (QSCAN) * QSCAN ASR MEMBER
PLSQUOF8 (N) * SPECIFY Y TO CANCEL ALLOC FROM QUOTA
PLSQUOGM (N) * STATS TRACKING TIME: N - LOCAL; Y - GMT
*------*
4. Security, APF and LINK Requirements
To install CA Allocate, you need CREATE or UPDATE authority for all of the libraries in the SMP/E zone.
To customize CA Allocate, the user's TSO ID needs update authority to the Parmlib.
To run CA Allocate, the started task (VAM) needs READ authority for the CCTVLOAD and Parmlib libraries.
The CCTVLOAD must be APF authorized. Optionally, it can be added to Linklist.
The CCTVLINK would be added to Linklist only if the site is running CA AUDITOR.
5. Start and Stop the VAM Task
Enter the console command: S VAM
VAM will startup, compile the ASRs (just the one line for now) then it will idle.
To stop the task, enter this command: F VAM,REMOVE
It will take 2 or 3 minutes for VAM to shut down.
See “Operator Command Parameters”, in User Guide Chapter 4, Operation.
6. Deploy Your Product
For simple implementation on a single system, you will have a unique Parmlib specified on the PARMS DD in each VAM proc on each system.
A more complex implementation would utilize a single Parmlib with several VKGPARMx members, one for each of the multiple VAM procs. These definitions are made in the CONFIG member and specified on the EXEC in each VAM proc.
See details for the CONFIG member in the User Guide, Chapter 3, Implementation, "Multiple Systems – Parmlib Considerations”.
7. Syntax Check ASRs
During your testing, the ASRs will be modified frequently. To avoid the possibility of an ASR compile failure during your testing, be sure to syntax-check your ASR member with the TESTASRS job that you copied from CCTVJCL into the Parmlib.
8. ASR Compile Failure
After VAM was successfully installed, but a subsequent ASR compile should fail, VAM will continue to run with the ASRs that it had previously compiled. This is okay.
Compile messages at the end of the VAM task will indicate where and what the problem is. Correct the ASRs and then issue the refresh command again.
9. Correct Failed Install or Remove
If the ASRs do not compile at startup, review the SYSPRT DD output. Messages near the bottom will indicate the error. Correct the error in the ASRs and issue the REFRESH command (see below).
If VAM should abend, or error messages are displayed at startup indicating that VAM or some of its hooks are already installed, or there is an abend at REMOVE, VAM can be stuck partially installed and non-functional. This can be easily corrected with this command:
(if VAM still running) F VAM,CLEANUP
(if VAM not running) S VAM,CLEANUP
The VAM task will start, remaining hooks will be removed, then it will shut down. You can then do a normal Start of the VAM task.
Please review the CLEANUP command described in the User Guide, Chapter 4: Operation.
10. Refresh Active Members
To refresh all active VAM (and QUOTA) members including VKGPARMS, issue this command:
F VAM,PARMREF
To refresh all active VAM (and QUOTA) members, except VKGPARMS, issue this command:
F VAM,REFRESH
To change the active member for either the ASRs or the Storage Groups, you can issue the respective command specifying the new member:
F VAM,REFRESH,PROG=
F VAM,REFRESH,STORGP=
11. Limit VAM To Your Testing
Method 1 – DORMANT Mode
CA Allocate can operate in a dormant mode affecting only job-steps that have a specific DD statement included.
Specify Vkgparm: PLSMODE (DORMANT)
Start VAM.
Place this special DD statement in the job-step that you want VAM to control:
//#VAMTST# DD DUMMY
All other steps and jobs will be ignored.
This DDname can be changed with Vkgparm: PLSDRMNT
Method 2 – ACTIVE Mode
CA Allocate can run in ACTIVE mode with ASR statements to exclude all but the specific jobs you want to test.
Specify Vkgparm (or let default): PLSMODE (ACTIVE)
Add the following to your ASRs, after your FILTLIST statements, but before the first “VAMENVIR” statement...
IF &USER NE 'user' THEN EXIT
IF &JOB NE 'jobname' THEN EXIT
IF &DSN NE hlq.** THEN EXIT
This will cause CA Allocate to control only the JOB and USER and DSN allocations that you specify in these statements.
To determine if a job failure is caused by CA Allocate or not, place this special DD statement in the job so VAM will take no action, then rerun:
//VDSBYPAS DD DUMMY
If the job still abends, then CA Allocate is not the cause. If you can’t determine the cause of the failure, contact Technical Support.
This DDname can be changed with Vkgparm: PLSBYPAS
Starting To Use CA Allocate Page 1 of 5