|
|
|
|
Position |
Field Length |
Field Name |
Notes |
|---|---|---|---|
|
1 |
1 |
Statement Type |
Must be blank |
|
2 |
1 |
Action Code |
Must be blank |
|
3-10 |
8 |
Run Date |
mm/dd/yy or dd/mm/yy; defaults to current |
|
11 |
1 |
Reserved |
Not used |
|
12-16 |
5 |
Run Type |
UPDAT for update function |
|
17-80 |
64 |
Reserved |
Not used |
The UPDAT mode indicates that an input Data Management Utility Job Accounting data set to be modified as defined by the input control statements. This mode implies the following processes:
The control statements are assumed to be a mixture of ADD, CHANGE and DELETE statements, discussed later in this chapter.
The BUILD mode indicates that the DMU Job Accounting data set is created solely by input control statements. This mode necessarily implies the following processes:
All control statements are assumed to be ADD statements. No input data set is required, nor is it requested.
The MERGE mode indicates that multiple input DMU job accounting data sets will be merged into one file. This mode implies the following processes:
No input control statements (except SETUP statement) are required for this mode. The control report displays the first and last record read from each DMU job accounting data set. A record count for all records read and written is also displayed.
The control statements are used to ADD, CHANGE, or DELETE specific records on the DMU job accounting data sets. These statements are required for the UPDAT and BUILD modes and are not used for the MERGE mode as defined by the run type on the SETUP statement. If present, the control statements can appear in any order since they are automatically sorted to interact with the input files.
The Statement Type is a one-character code defining the functions performed by the control statement.
The Action Code is a one-character code defining the type of record(s) involved in the function.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |