 |
- Family-1 - IBM 3270 terminals
- The name-count value must be 0, 1, or 2:
- 0
- The device is the CMS console from which the application is being run.
- 1
- Name-list(1) must contain one of these:
- "*"
- Blanks
- "PUNCH"
- A character form of device address (for example "061").
If name-list(1) contains "*", the terminal is used as described for a
name-count of 0.
If name-list(1) = "PUNCH", GDDM writes the 3270 device output to the
CMS virtual punch, in the form described in GDDM Base Application
Programming Guide. In this case, the application must provide a
device token parameter to supply the device characteristics that are
to be used by GDDM.
- 2
- Name-list(1) must contain one of these:
- "*"
- Blanks
- A character form of device address (for example "061").
If name-list(2) contains "*", the terminal is used as described for a
name-count of 1. Otherwise, the name-list(2) value is the name of an
auxiliary device (a plotter or printer).
Note: For detail of the name-list value required when plotter output is
to be saved in IBM-GL format, see the description of the TOFILE processing
option in Appendix B, "Processing options" in topic B.0.
- Family-2 - queued printers
- The name-count value must be in the range 1 through 3.
Unless processing option group 1004 (INVKOPUV) is specified, the
name-list(1), name-list(2), and name-list(3) values define the file name,
file type, and file mode (respectively) of the print file that is to be
generated. The supplied default for filetype is ADMPRINT. Filemode
defaults to A1.
If automatic invocation of the VM Print Utility is requested (as specified
by INVKOPUV), name-count and name-list identify a family-1 device, and
must therefore be as defined for family-1 (above).
- Family-3 - system printers
- The name-count value must be 0, 1, 2, or 3:
- 0
- The device is the currently defined printer; that is, device
00E.
- 1 through 3
- Name-list(1), name-list(2), and name-list(3) define the file
name, file type, and file mode (respectively) of the print
file that is to be generated. The supplied default for
filetype is ADMLIST. Filemode defaults to A1.
When name-list(1) contains "*", the printer is used as described for a
name-count of 0.
- Family-4 - page-printer files
- The name-count value must be in the range 1 through 3.
The name-list(1), name-list(2), name-list(3) values define the file name,
file type, and file mode, respectively, of the CMS file(s) that is
generated. More than one file is generated if a color master table is
being used (as specified by processing option group 3000).
For both monochrome and multicolor masters, "A1" is assumed if the
filemode is omitted.
A family-4 namelist value of "PRINTER" causes subsequent output to be
directed to the virtual printer, instead of to a file. It is intended for
use only with AFPDS files, and takes effect only if the name-count value
is "1." If a namelist value of "PRINTER" is used with non AFPDS family-4
files, errors are likely to occur.
- Monochrome master
- When the filetype is omitted or is specified as "*", the filetype is taken
from the GDDM external default CMSMONO. The supplied default is ADMIMAGE.
- Color masters
- If only one color master is specified in the MASTERS option of the
ADMMCOLT macro, the filetype can be explicitly given. Otherwise, when the
filetype is specified, it must be "*". The filetype is taken from the
GDDM defaults. The supplied default is ADMCOL+. The "+" is replaced by
1, 2, 3, and so on (up to a maximum of 9) for each color master file.
For example, if:
___ ___ ___ ___ ___ ___ ___ ___
namelist(1) = | a | a | a | a | | | | |
|___|___|___|___|___|___|___|___|
___ ___ ___ ___ ___ ___ ___ ___
namelist(2) = | * | | | | | | | |
|___|___|___|___|___|___|___|___|
the derived file identifiers when using a color table specifying
four-color masters would be:
aaaa ADMCOL1 A1
aaaa ADMCOL2 A1
aaaa ADMCOL3 A1
aaaa ADMCOL4 A1
|--------------- End of General-use programming interface ---------------|
|
GDDM V3R2 System Customization and Administration
Copyright IBM Corporation 1990, 2012