Previous Topic

Next Topic

Book Contents

Book Index

Write Output to a Collective CDAM File

The default working practice of Control-D is to store every JES dataset created on the spool as a CDAM file. This is acceptable for standard reports, but for small reports like MSGCLASS output, this becomes a resource overhead.

Each MSGCLASS output created consists of at least three small separate JES datasets. Using the default workings of Control-D, three CDAM datasets would be created (one for each JES dataset), three $SYSDATA entries would be created (one describing each CDAM dataset), and a variable number of user entries would be created (depending on how many recipients are allocated the report). For example:

Parent Topic

Generic Processing Workflow