GDDM V3R2 System Customization and Administration
GDDM V3R2 System Customization and Administration
Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF |
BOOK
Nickname user-default specifications GDDM V3R2 System Customization and Administration SC33-0871-02 |
|
The GDDM Base API call DSOPEN defines to GDDM the device for which the issuing application is creating its output. The device definition supplied on DSOPEN can be complete, in which case the application is device dependent: if anything about the device changes, the application itself has to be altered. Alternatively, a partial device definition can be supplied on input to DSOPEN. A partial definition would include a device identifier, a family identifier, and a device name. A nickname, which is defined in a user-default specification (usually in the external defaults module or in an external defaults file, as described in "GDDM user-default specifications" in topic 3.8) supplies all the other information about the device. In particular, the nickname can provide a device token and some processing options. It can also redirect the application's output to a different family and device from those specified on DSOPEN, thereby extending the range of devices supported by the application. This mechanism allows you to alter the definition and usage of any device, without requiring updates to be made to applications that use it. You are recommended to add a set of nickname UDSs to the external defaults module that describes all printers and plotters in your enterprise, for use by all GDDM users. This simplifies the tasks of the application programmer and end user, without depriving them of the ability to override such definitions. Subtopics: |
 Copyright IBM Corporation 1990, 2012 |
