Previous Topic

Next Topic

Book Contents

Book Index

Allocation Options Comparison

A comparison between some of the allocation options is shown below. We are comparing the normal way in which Control-D handles report output, the ALLOCOPT=ONEDSN option that groups output at job level, and the ALLOCOPT=JOBSDSN1 option that groups output in a "super" CDAM. Assume that one thousand batch jobs are running each night. The table below shows the resources used for each option:

Table 38 Comparison of Allocation Options (Based On 1,000 Jobs Per Night)

 

NORMAL

ONEDSN

JOBSDSN1

JES DATASET

3000+

3000+

3000+

CDAM FILE

3000+

1000

1

$SYSDATA ENT

3000+

1000

1000

USER ENT

1000+

1000+

1000+

VTOC ENT

3000+

1000

1

TRKS RQD

3000+

1000

180

BMC strongly recommends that generic decollating missions handling MSGCLASS output uses the JOBSDSN1 allocation parameter. This will prevent and save on resources used. It cuts down on the number of VTOC entries, prevents fragmentation problems, cuts down on the number of records stored in the Control-D user files and reduces the amount of space required to hold the MSGCLASS output.

For further information on the allocation options, see the CDAM chapter in the Control-D and Control-V User Guide.

Parent Topic

Write Output to a Collective CDAM File