Previous Topic: Distribution LibrariesNext Topic: CA Datacom/AD Database

Preparing for Installation › Storage Requirements › Permanent Data Sets

Permanent Data Sets

The default sizes are shown in the Stage 1 SYSGEN macro U7SPACE and amount to approximately 2000 tracks of 3390 space. These defaults are typically sufficient to define and control from 200 through 400 jobs depending on the average number of steps and DD statements per job. Obviously, the default sizes can be inadequate for sites running large workloads.

If you do not have enough information to estimate your space requirements, use the defaults and increase your allocations as needed using backup and reload procedures.

If you plan to use the CA WA System Agent interface, CA Integrated Agent Services (CA IAS), see the CA Integrated Agent Services Implementation Guide for information about its permanent files. The SYSGEN generated JCL for CA7ONL allocates these files. If you are using your existing CA7ONL JCL, be sure to include these files.

The following table summarizes the data set requirements.

Data Set

Organization

Online

Est. Space on 3390

DASD Restrictions

CA Datacom/AD database

DB

yes

variable (note 1)

none

JCL or PARM data sets

PO/LIB/PAN

yes

variable (note 1)

none

Checkpoint data set

PSU

yes

1 cyl

none

Communications data set (note 2)

PS

yes

minimum 50 tracks

(note 1)

Submit data sets

PS

yes

1 cyl

none

Log data sets

PS

yes

At least 10 cyls

Both primary and secondary files must reside on the same volume

Log history/archives

PS

no

variable (note 1)

none

Batch terminal data sets

PS

yes

input: 5 tracks
output: 10 cyls

none

Statistics data set

PS

yes

750 records of 1024 bytes each

none

Workload planning data sets

PS

yes

variable (note 1)

none

Browse data set

PS

yes

variable (note 1)

none

Override library

PO/LIB/PAN

yes

variable (note 1)

none

JCLLIB

PO

yes

1 cyl

none

CA JCLCheck options data set

PS/PO

yes

variable (note 3)

none

CA Driver procedure library

PO

yes

variable (note 4)

none

Model Problem Management interface transaction file

PS

yes

1 track (note 5)

none

Problem Management API deferred request

PS

yes

variable (note 5)

none

Calendar PDS

PO

yes

variable (note 1)

none

Perpetual Calendar PDS

PO

yes

variable (note 1)

none

Cross-Platform Scheduling Profile

PO

no

variable (note 1)

none

Cross-Platform Checkpoint file

PS

no

1 track (note 1)

none

MSMR control file

PS

yes

variable (note 6)

none

Email address library

PO

yes

variable (note 1)

none

Sample email templates

PO

yes

variable (note 1)

none

Sample templates for CA Service Desk

PO

yes

(note 7)

none

Agent Information

VSAM

yes

Variable (note 8)

none

Agent Definition

PS

yes

(note 8)

none

Encryption Keys

PS

yes

(note 8)

none

IAS checkpoint

VSAM

yes

(note 8)

none

XCF data set

PS

yes

At least 3 cyls (note 1)

none

XCF checkpoint data set

PS

yes

1 track (note 1)

none

All data sets MUST be CONTIG except for the JCL, override, and CA WA CA 7 Edition JCLLIB libraries.

Note 1:

See the individual topics later in this chapter.

Note 2:

Shared DASD if multi-CPU.

Note 3:

Used only if you want the CA WA CA 7 Edition CA JCLCheck interface.

Note 4:

Used only if you want the CA Driver component.

Note 5:

Required with the Problem Management interface.

Note 6:

Required for CA WA CA 7 Edition Master Station Message Routing.

Note 7:

Used when installing the interface to CA Service Desk.

Note: For more information, see the Interface Reference Guide.

Note 8:

These files are only required if CA WA CA 7 Edition is to interface with CA WA System Agent r11.3 and above.

Note: For more information about each file, see the CA Integrated Agent Services Implementation Guide.