GDDM services on VSE

To use GDDM services for printing QMF objects, you must:

  1. Choose a GDDM nickname for the print device.

    Nicknames enable you to predefine complex print or display devices to simplify the work of your end users. Nicknames define device characteristics that indicate to GDDM how to format and distribute the report, and they can define both local and remote devices.

  2. Update the GDDM defaults module, ADMADFC, with the specifications of your nickname.
  3. Update CICS resource definitions with the values in the nickname specification, so that CICS can link the nickname with the physical device it manages.
  4. Update the PRINTER field of the user's row in the Q.PROFILES table.

Choosing a GDDM nickname for your printer

In CICS, GDDM searches only the defaults module, ADMADFC. GDDM uses nicknames to recognize all the devices with which it can communicate (including terminals).

Choosing the right type of GDDM device

The printer nickname you use depends on the type of device:

This chapter explains how to define nicknames for Family 1, 2, and 3 devices. For more information on how to set up a nickname for a Family 4 printer and use the ADMOPUT and ADMOPUJ utilities, see the GDDM System Customization and Administration manual for GDDM or the appropriate GDDM Installation and System Management manual. These publications also provide more information on each type of GDDM device.

To create a nickname in CICS, first define a GDDM ADMMNICK specification in the GDDM external default module ADMADFC. This specification indicates the device characteristics to GDDM, such as the number of lines per page the printer can handle, and how the printer is managed by CICS.

Use the format shown below for your ADMMNICK specification.

Figure 122. Using the ADMMNICK specification to define a nickname
ADMMNICK NAME=nickname,TOFAM=family_type,
DEVTOK=device_token(,TONAME=name)

TONAME is used only in CICS.

Example nickname for a family 3 GDDM printer

To define the nickname 370PRINT for a Family 3 GDDM printer, you might use an ADMMNICK specification similar to the one below.

Figure 123. Using the ADMMNICK specification to define a nickname for a Family 3 printer
ADMMNICK NAME=370PRINT,TOFAM=3,DEVTOK=R87S,TONAME=370P 

After you create the ADMMNICK specification in CICS, link the name with a physical device by updating the DCT. Make sure TONAME in the ADMMNICK specification and DESTID in the DCT have matching values.

Examples of nickname definitions

This section shows examples of nicknames you might use for Family 1, 2, or 3 devices. For examples on defining nicknames for Family 4 devices, see the GDDM System Customization and Administration manual for GDDM or the appropriateGDDM Installation and System Management manual for GDDM.

Updating the GDDM defaults module with the nickname

In CICS, the ADMMNICK nickname specifications reside in the GDDM external defaults module ADMADFC, which is supplied with the GDDM product.

To update the modules with your nickname specification:

  1. Punch ADMADFC to ICCF or another editor, and edit the member to update it with the nickname specification.
  2. Enter your ADMMNICK specification after the ADMMDFT statements in the module.
  3. Reassemble and link-edit the changed default module.

For more information on the defaults modules, see the GDDM System Customization and Administration manual for GDDM or the GDDM Installation and System Management for VSE for GDDM manual.

In VSE, use the CEMT transaction to load a new copy of the ADMADFC phase into CICS storage. Use a statement similar to the following example:

CEMTS PROG(ADMADFC)NEW

Linking the nickname with a physical device

After you update the ADMADFC module, you need to update the CICS resource definitions so that CICS can link the nickname with a physical device it manages.

Linking a family 1 or 2 nickname with a physical device

For a family 1 or 2 printer, you can use macros to update CICS resource definitions in the TCT, or use CICS resource definition online (RDO) to update the CICS system definition (CSD) file.

For example, for this nickname specification:

ADMMNICK NAME=GRAPHIC,TOFAM=2,DEVTOK=R87S,TONAME=GRAP

you can update the CICS TCT using a macro similar to the example shown in below.

Figure 124. Defining to CICS a nickname for a Family 2 GDDM printer
GRAP     DFHTCT TYPE=TERMINAL,
               ACCMETH=VTAM,
               TRMIDNT=GRAP,
               TRMTYPE=SCSPRT,
                   . . .
                   . . .
                   . . .

In VSE, all Family 1 and 2 devices must be described to CICS as queued.

Linking a family 3 nickname with a physical device

For a Family 3 printer in CICS/VSE, you need to update the DCT using macros. For example, for this nickname specification:

ADMMNICK NAME=370PRINT,TOFAM=3,DEVTOK=S3800N6,TONAME=S04E

you can update the CICS DCT.

Add the TYPE=SDSCI entry shown in Figure 125 after all other TYPE=SDSCI entries in the DCT. The device address (SYS097) corresponds to the printer, 04E, according to the assign statement in the startup JCL. If you use SYSLST, CICS STATS is part of your QMF report. Instead, use an alternate printer.

Figure 125. TYPE=SDSCI entry for the DCT
************************************************************************                                                                    *                                                                       *
*           SYSTEM PRINTER FOR QMF OUTPUT.                              *
*           BLKSIZE:  132 + 1 FOR CTLCHR=ASA + 4 FOR RECFORM=VARUNB     *
*************************************************************************                                                                 *
            DFHDCT TYPE=SDSCI,                                          +
                   BLKSIZE=137,                                         +
                   DSCNAME=UTMS04E,                                     +
                   RECFORM=VARUNB,                                      +
                   DEVADDR=SYS097,                                      +
                   DEVICE=1403,                                         +
                   TYPEFILE=OUTPUT,                                     +
                   CTLCHR=ASA

Add the TYPE=EXTRA entry shown in Figure 126 after all other TYPE=EXTRA and TYPE=INDIRECT DCT entries. The TYPE=EXTRA entry corresponds to the preceding TYPE=SDSCI entry by the matching value for DSCNAME.

Figure 126. TYPE=EXTRA entry for the DCT
************************************************************************                                                                    *                                                                       *
*           SYSTEM PRINTER FOR QMF OUTPUT.                              *
*************************************************************************                                                                      *
            DFHDCT TYPE=EXTRA,                                          +
                   DESTID=S04E,                                         +
                   DSCNAME=UTMS04E,RSL=1                                   
[ Previous Page | Next Page | Contents | Index ]