Allocating the VSAM data sets

Perform this task if you are installing a controller.

HCL Workload Automation for Z VSAM data sets shows the VSAM data sets and their characteristics. The JCL procedure for the controller uses all of these data sets except for EQQLDDS and EQQLTBKP, which are used only in the planning batch jobs. Allocate all these VSAM data sets for a controller.

Table 1. HCL Workload Automation for Z VSAM data sets
Sample DD name Record type Attributes Share option Keys Record size Data set
EQQPCS09 N/A KSDS REUSE NSPND 3 19 0 200 32000 Archive of current plan
EQQPCS01 EQQADDS KSDS UNIQUE SPANNED 3 25 0 1000 131072* Application description
EQQPCS01 EQQCP1DS KSDS REUSE NSPND 3 19 0 200 32000 Current plan 1
EQQPCS01 EQQCP2DS KSDS REUSE NSPND 3 19 0 200 32000 Current plan 2
EQQPCS01 EQQCXDS KSDS REUSE NSPND 3 64 0 500 32000 Current plan extension
EQQPCS01 EQQXD1DS KSDS REUSE NSPND 3 68 0 500 32000 Extended data 1
EQQPCS01 EQQXD2DS KSDS REUSE NSPND 3 68 0 500 32000 Extended data 2
EQQPCS01 EQQNXDDS KSDS REUSE NSPND 3 68 0 500 32000 New extended data
EQQPCS01 EQQJS1DS KSDS REUSE SPANNED 3 28 0 804 180004 JCL repository 1
EQQPCS01 EQQJS2DS KSDS REUSE SPANNED 3 28 0 804 180004 JCL repository 2
EQQPCS01 EQQLDDS KSDS REUSE SPANNED 2 28 0 440 131072 Long-term-plan work
EQQPCS01 EQQLTBKP KSDS REUSE SPANNED 3 28 0 200 131072 Long-term-plan backup
EQQPCS01 EQQLTDS KSDS REUSE SPANNED 3 28 0 200 131072 Long-term plan
EQQPCS01 EQQNCPDS KSDS REUSE NSPND 3 19 0 200 32000 New current plan
EQQPCS01 EQQNCXDS KSDS REUSE NSPND 3 64 0 500 32000 New current plan extension
EQQPCS01 EQQNSTDS KSDS UNIQUE SPANNED 3 68 0 500 32000 New step awareness
EQQPCS01 EQQOIDS KSDS UNIQUE NSPND 3 28 0 800 32000 Operator instruction
EQQPCS07 EQQPKIxx KSDS UNIQUE INDEXED 1,3 34 0 77 77 Primary Index
EQQPCS01 EQQRDDS KSDS UNIQUE NSPND 3 64 0 400 32000 Special resource descriptions
EQQPCS01 EQQSCPDS KSDS REUSE NSPND 3 19 0 200 32000 Current plan backup copy for for IBM® Tivoli® Monitoring integration
EQQPCS07 EQQSDFxx LINEAR N/A 2,3 N/A N/A Data files
EQQPCS01 EQQSIDS KSDS UNIQUE NSPND 3 64 0 110 220 Side information file: ETT and configuration information
EQQPCS07 EQQSKIxx KSDS UNIQUE INDEXED 1,3 38 0 76 32000 Secondary Index
EQQPCS01 EQQSTDS KSDS UNIQUE SPANNED 3 68 0 500 32000 Step awareness
EQQPCS01 EQQWSDS KSDS UNIQUE NSPND 3 10 0 100 32000 Workstation, calendar, and period descriptions.
EQQPCS01 EQQSCPDS KSDS REUSE NSPND 3 19 0 200 32000 Current plan backup copy for IBM® Tivoli® Monitoring integration
Note:
  1. * The maximum record size for EQQPCS01 is the default maximum value. This can be increased as in the example that follows.
  2. In specific situations where the size of the CP files (CP1, CP2, NCP, SCP) are large and the batch daily planning jobs cause a considerable number of updates to the NCP, it is possible for the NCP to become very large. This might require the allocation of additional extents (not additional volumes, since ADDVOL support is not available for the NCP file). Consider freespace allocation for the current plan, including NCP (EQQCP1DS, EQQCP2DS, EQQCXDS, EQQNCPDS and EQQSCPDS), application descriptions (EQQADDS), resource descriptions (EQQRDDS), and operator instructions (EQQOIDS) data sets.
  3. The extended data sets XD1DS, XD2DS, NXDDS, OXDDS have a logical correspondence and use like the current plan data sets CP1DS. CP2DS, NCPDS, ONCPDS. As the old CP (OCP) can be either the CP1 or the CP2 according to which one is inactive and not current, with the same logic OXD can be either XD1 or XD2 according to which one is not currently active.
  4. If you are upgrading from a previous HCL Workload Automation for Z release, it is recommended to use the new samples shipped and set with EQQJOBS. The allocation samples like EQQPCS01 use variables. If you are customizing previous allocation JCLs, make sure you correctly position the changes and use the correct set of defined variables.
  5. The IDCAMS ALTER ADDVOLUMES command is not supported for HCL Workload Automation for Z data sets because it requires that the data set be closed and reopened before the VSAM is updated with the new volumes added.
You can allocate the VSAM data sets by submitting the sample listed in HCL Workload Automation for Z VSAM data sets. Alternatively, you can allocate one or more of the VSAM data sets by running a job like this: 
Allocating a VSAM data set
//ALOCVSAM JOB STATEMENT PARAMETERS
//*----------------------------------*
//* ALLOCATE AN OPC VSAM DATA SET *
//*----------------------------------*
//ALLOC   EXEC PGM=IDCAMS,REGION=512K
//SYSPRINT DD  SYSOUT=Q
//EQQVOL1  DD  DISP=OLD,VOL=SER=volser,UNIT=3390
//SYSIN    DD  *
  DEFINE +
    CLUSTER ( +
      NAME('OPC.INST.AD') UNIQUE +
      SPANNED +
      SHR(3) VOL(volser) CYLINDERS(2 2) +
            ) +
    DATA    ( +
      NAME('OPC.INST.ADDATA') +
      KEYS(25 0) RECORDSIZE(1000 132072) +
            ) +
    INDEX   ( +
      NAME('OPC.INST.ADINDEX') +
            )
/*

This example allocates the application description database.

You can allocate VSAM data sets on different device types.

Allocate enough space for your data sets, depending upon the amount of work HCL Workload Automation for Z processes at your installation. For details about allocating space for VSAM data sets Calculations of VSAM data set size.

Table 2. Calculations of VSAM data set size
Data set Size in bytes is total of:
Number of Multiplied by
Application description (EQQADDS)

Application and group definitions
Run cycles
Positive run days
Negative run days
Operations
Internal dependencies
External dependencies
Special resources
Operation Extended Information
Variable tables
Variables
Variable dependencies
Extended Name

208
120
3
3
110
16
84
64
200
98
476
88
Current plan (EQQCPnDS)

Header record (one only)
Workstations
Workstation open intervals
Workstation access method data
Occurrences
Operations
Dependencies
Special resource references
Operation Extended Information
Jobs
Executed steps
Print operations
Unique application names
Operations currently in error
Reruns of an operation
Potential predecessor occurrences
Potential successor occurrences
Operations for which job log information has been collected
Stand-alone clean up
Restart and clean up operinfo retrieved
Number of occurrences

188
212
48
72
302
356
14
64
200
116
20
20
64
264
264
32
24
111
70
44
43
Extended data (EQQXDnDS and EQQNXDDS)

Header record (one only)
Bind requests

244
565
JCL repository (EQQJSnDS)

Number of jobs and started tasks
Total lines of JCL
Operations for which job log information has been collected
Total lines of job log information

80
80
107
143
Note: As a base, calculate a figure for all your jobs and started tasks controlled by HCL Workload Automation for Z. Add to this figure the expected space required for jobs and started tasks in the current plan.
Long-term plan (EQQLTDS)

Header record (one only)
Occurrences
External dependencies
Operations changed in the LTP dialog

92
160
35
58
Operator instruction (EQQOIDS)

Instructions
Instruction lines

78
72
Special resource database (EQQRDDS)

Resource definitions
Defined intervals
Entries in the WS connect table

216
48
8
Side information file (EQQSIDS) ETT requests

128
Workstation/calendar (EQQWSDS)

Calendars
Calendar dates
Periods
Period origin dates
Workstation closed dates
Workstations
Workstation access method data
Interval dates
Intervals

96
52
94
6
80
124
72
52
32
Note:
  1. Use the current plan data set calculation (EQQCPnDS) for the new current plan data sets (EQQNCPDS and EQQSCPDS).
  2. Use the long-term-plan data set calculation (EQQLTDS) for the long-term-plan work data set (EQQLDDS) and the long-term-plan backup (EQQLTBKP).
  3. Use the special resource database calculation (EQQRDDS) for the current plan extension data set (EQQCXDS) and the new current plan extension (EQQNCXDS).

Consider the following information when allocating VSAM data sets.