GDDM services on VM

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 ADMDEFS PROFILE file or the GDDM defaults module, ADMADFV with the specifications of your nickname.
3. Update the PRINTER field of the user's row in the Q.PROFILES table.

Choosing a GDDM nickname for your printer

In CMS, GDDM searches the ADMDEFS PROFILE file and then the defaults module, ADMADFV, for a matching nickname that defines how and where to direct the output.

Choosing the right type of GDDM device

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

• Family 1 devices specify auxiliary devices attached to a workstation using GDDM-PCLK. A Family 1 device can also include display devices, such as 3270 data-stream terminals.
• Family 2 devices include devices such as IBM 3270 terminals and queued printers.
• Family 3 devices are system printers that support the ANSI code of carriage control characters.
• Family 4 devices are advanced function printers for which you need to use the ADMOPUT and ADMOPUJ utilities (in TSO, and native OS/390 batch only) to print output. These utilities are provided by GDDM.

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.

Creating a nickname specification

To create a nickname in CMS, you can add the nickname to your PROFILE ADMDEFS file. GDDM looks at this file first. If the nickname is not found, GDDM looks in the external default module, ADMADFV, in which you define a GDDM ADMMNICK specification.

Example nickname for a family 2 GDDM printer

To define the nickname GRAPHIC for a Family 2 GDDM printer, you might use an ADMMNICK specification similar to the one below. It uses the device token R87S, an example of a token for a remotely attached 3287 printer.

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

After you create your nickname in CMS, a file with type ADMPRINT is created on your A-disk. This file has a file name of the printer that was supplied on input to the DSOPEN call. You can then print the ADMPRINT file using the ADMOPUV utility.

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.

ADMMNICK NAME=370PRINT,TOFAM=3,DEVTOK=R87S (CMS)

In CMS, a file with type ADMLIST is created. You can then send the formatted file to the printer you have chosen.

Example nickname for a family 4 GDDM printer

To define the nickname 3900PRNT for a Family 4 GDDM printer, you might use an ADMMNICK specification similar to the one below.

ADMMNICK NAME=3900PRNT,TOFAM=4,DEVTOK=R87S

After you create your nickname, the ddname ADMIMAGE is created. You can spool the file to PSF/VM if you have the CSPOOL processing option set. For more information about Family 4 printing, see theGDDM System Customization and Administration manual.

Defining multiple nicknames with one definition

You can use a single nickname to define multiple printer addresses by including the wildcard ? in your nickname definition, like this:

ADMMNICK TOFAM=3,NAME=MYPRINT?,PROCOPT=((PRINTCTL,0))

The nickname MYPRINT? allows you to route print output to printers named MYPRINT1, MYPRINT2, MYPRINTA, and so on. For example, when you enter:

PRINT REPORT (PRINTER=MYPRINT2

GDDM uses the nickname definition for the MYPRINT? nickname to create a data set and direct the output from the PRINT command to the data set with ddname MYPRINT2.

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 appropriate GDDM Installation and System Management manual for GDDM.

• 3800, 3812, or 3820 printer, 6 lines per inch: Use the following definition to define the nickname GDDMPRT1 for a Family 3 printer:

  GDDMPRT1 ADMMNICK TOFAM=3,DEVTOK=S3800N6,NAME=MYPRINT1

• 3800, 3812, or 3820 printer, 8 lines per inch: Use the following definition to define the nickname GDDMPRT2 for a Family 3 printer:

  GDDMPRT2 ADMMNICK TOFAM=3,DEVTOK=S3800N8,NAME=MYPRINT2

• Non-3800 system printer, 132 columns, 8 lines per inch: Use the following definition to define the nickname GDDMPRT3 for a Family 3 printer:

  GDDMPRT3 ADMMNICK TOFAM=3,DEVTOK=S1403W8,NAME=MYPRINT3

• A remotely attached 3287 (suitable for printing charts): Use the following definition to define the nickname GDDMPRT4 for a Family 2 printer:

  GDDMPRT4 ADMMNICK TOFAM=2,DEVTOK=R87,NAME=MYPRINT4

• Any destination without print control options: Use the following definition to define the nickname GDDMPRT5 for a Family 3 printer:

  GDDMPRT5 ADMMNICK TOFAM=3,PROCOPT=((PRINTCLTL,)),NAME=MYPRINT5

  The PROCOPT parameter specifies processing options using a print control (PRINTCTL) keyword, which allows you to specify a number of print control options. For example, you can use PRINTCTL to specify a page heading to be printed, the number of copies to print, and the width of margins. The zero in this example suppresses page headings.
  Attention: If the print data set has RECFM=F, GDDM printing changes the DCB of the data set from RECFM=F to RECFM=V.

  For a list of print control options and how to use them, see the GDDM System Customization and Administration manual.

• A PC printer using GDDM-PCLK (for DOS users): Use the following definition to define the nickname PCPRINT for a Family 1 printer:

  GDDMPRT6 ADMMNICK TOFAM=1,FAM=0,NAME=PCPRINT,TONAME=*,ADMPCPRT

  where * indicates the user's current device or the default value.

  To print to a workstation printer connected to DOS, GDDM-PCLK must be installed on your workstation.

Updating the GDDM defaults module with the nickname

In CMS, the ADMMNICK nickname specifications reside in the GDDM external defaults module ADMADFV, which is supplied with the GDDM product. The default module also contains default values for the GDDM product. The module is stored as a file with a type ASSEMBLE.

To update the modules with your nickname specification:

1. Copy the GDDM source file to your own storage.
2. Edit the source file to add the nickname.
3. Enter your ADMMNICK specification after the ADMMDFT statements in the module.
4. Reassemble and replace the changed default module. For more information on the default modules, see the GDDM System Customization and Administration for GDDM manual or the GDDM Installation and System Management for VM for GDDM manual.

Testing the nickname definitions in external default files

Test your nickname definitions by placing them in an external default file and printing with them until you are satisfied they are working correctly. Then you can assemble them into external default modules.

Name the external default file ADMDEFS PROFILE and name the external default module ADMADFV. Testing the nickname definitions requires access to the minidisks containing these files. The external default file can be placed on any minidisk normally accessed when using QMF (for example the GDDM minidisks, which are accessed when using QMF).

GDDM uses external default modules more efficiently than a data set to find a given nickname.