Using GDDM under TSO batch

GDDM V3R2 Base Application Programming Guide

Using GDDM under TSO batch

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

TSO Extensions (TSO/E) is a licensed program (program number 5665-285) that provides a TSO Batch environment in which TSO commands and command procedures can be run in the background. GDDM can be used in this environment, in normal MVS Batch, subject to the following considerations.

TSO Batch applications must be link-edited using the information under "Link-editing a GDDM application program" in topic C.1.
GDDM processes any External Defaults File allocated by means of a DD statement; the default ddname is ADMDEFS.
The GDDM default error exit reports errors. These messages usually appear on the JOB LOG output.
GDDM dynamically allocates queued printer files or high-resolution image files for family-4 devices using a unit specification that is defined in the TSOS99U option in the current GDDM external defaults. The default unit specification is SYSDA. If required, this can be changed, as described in the GDDM Base Application Programming Reference book.
The GDDM-supplied interactive utilities necessarily use the default primary device (the "TSO terminal"), unless called for noninteractive processing. Therefore, these utilities cannot be run interactively in TSO batch.
The default primary device (the simulated TSO terminal) is not suitable for GDDM full-screen operations. GDDM diagnoses any attempt to use this device.
Therefore, an application must include an explicit DSOPEN to identify a nondefault primary device (for example, a dummy device or non-family-1 device).
The GDDM default error exit reports errors. User PROFILE options can be used to cause the messages to appear as part of the session output file (SYSTSPRT). The TSO command to request that messages appear on the session output file is:
```
         PROFILE WTPMSG
```
and this should be included in the session input file (SYSTSIN) before GDDM is used.
Unless the application is running as part of a RACF job with USERID, no default data-set-name prefix or user ID is defined. A default data-set-name prefix may be required by GDDM for dynamic allocation of queued printer files or high-resolution image files (for family-4 devices). The TSO command to establish a default data-set-name prefix is:
```
         PROFILE PREFIX(dsname-prefix)
```
and this should be included in the session input file (SYSTSIN) before GDDM is used.
GDDM uses the user ID only for annotation purposes (in print files and trace files). In the absence of a user ID, GDDM uses the JOB name.

Notices | Terms of use | Support | Contact z/OS