GDDM V3R2 System Customization and Administration
|
Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF |
BOOK
Coding UDSs for an external defaults file GDDM V3R2 System Customization and Administration SC33-0871-02 |
|
An external defaults file contains one or more source-format, user-default specifications. It can be used without restriction under VM/CMS and TSO. However, it cannot be used under IMS, and is intended to be used only for testing or diagnosis purposes under CICS. (9) Under MVS, you allocate the DD name ADMDEFS to the sequential data set that is to contain the external defaults data. Under VM, the external defaults file is called PROFILE ADMDEFS. These names can be altered using the TSODFTS and CMSDFTS external defaults respectively. (TSODFTS and CMSDFTS can be specified in encoded UDSs only.) The external defaults file is usually held in storage local to the user for whom it has been provided. The external defaults file can be in fixed or variable record format and must have a record length no greater than 255 bytes. On TSO, it can be either a sequential data set or a member of a partitioned data set. Also, on TSO, the external defaults file must not be a null data set: it must contain at least one record. The format of an external defaults file is the same as that of an external defaults module, but with some relaxations of the syntax rules. See "Coding UDSs for an external defaults module" in topic 3.8.2 for the rules that apply to the external defaults module. The external defaults file differs from an external defaults module in the following ways:
(9) The role of the external defaults file in the diagnosis task is described in the GDDM Diagnosis book.
Subtopics: |
Copyright IBM Corporation 1990, 2012 |