NetBatch-Plus Reference Manual

Setting Up the Processing Environment
NetBatch-Plus Reference Manual—522461-002
4-12
6. Plan Catalog Attachments
a single catalog attachment. You can then use that attachment for as many jobs as you
want, overriding its attributes at the job level when necessary.
Planning Considerations and Recommendations
You derive information about the catalog attachments for your system from the
attachments you planned for your jobs. By sorting through those attachments, you can
identify attachments shared by a number of jobs. These shared attachments form the
basis of your attachments catalog.
To make identifying common attachments easier, create a table similar to Figure 4-6 on
page 4-13. By using such a table to indicate which attachments belong to which jobs,
you can identify attachments that are common to many jobs.
In some cases, you can have a number of job attachments that differ from one another
in a minor way only. For example, three ASSIGNs might be the same except for the
physical file they reference. In these circumstances, combine the attachments into one
catalog attachment. Users can then use a single catalog attachment as the basis of
their job attachments, specifying their own physical file where necessary.
You must associate each catalog attachment with a defaults set. You can select the
most appropriate set for this purpose by using the information in your table. For
example, where jobs sharing an attachment have the same defaults set, choose that
set. Another example is where the attachment is an ASSIGN or map DEFINE. In this
case, you can choose the defaults set belonging to the owner of the file referenced by
the ASSIGN or DEFINE.
Example
Figure 4-6 on page 4-13 is an example of a catalog attachments table. The table lists a
number of jobs and identifies their defaults sets and attachments.
The table contains enough information to allow identification of catalog attachments.
For example, all jobs in the table use PARAM P4 with the most common defaults set
among those jobs being Set1. The table therefore highlights an obvious catalog
PARAM (CP3) for Set1.
The table also shows where catalog attachments are unnecessary. For example, there
is no benefit in creating catalog records for ASSIGN A4, PARAMs P2 and P5, and
DEFINEs D2 and D5 because there are few occurrences of these attachments.