The user-defined segments can be an orderly method of documentation. By establishing standards that are related to segment names, a powerful tool results. To define a segment name, select an eight-character name meaningful to your environment; precede the name with a # sign. Enter the definition starting in column 1. For example:
#segment-name
The following list contains potential segment names that could fit into the naming conventions for segments:
Defines the format of the date cards that are used in this job.
Provides a description of programs that are used in the job.
Provides a description of job steps in the job.
Defines the instructions for disaster recovery procedures.
Defines the recovery specifications for I/O errors, abends, and so forth.
Provides the instructions for filing input or output.
Defines I/O media requirements of the job.
Defines names and numbers of personnel who support the job.
Defines I/O device requirements of the job.
Defines possible processing conflicts with other jobs.
Defines special manual verification requirements of the job.
Defines special procedures occurring after the close of the business day.
Other segment names can be helpful or more meaningful and easy to use in any particular data center. Within the constraints of the few reserved segment names, users have total flexibility in naming documentation segments.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|