The printcommand parameter specifies
how the operating system, that CICS® Transaction Gateway is running
on, must process requests to print from CICS.
printcommand=<string>- Description
- Enter a string containing the instruction to the operating system
on how to process print files. The string can be 1 - 256 characters
in length. When a request to print is received, the Client daemon
generates a temporary print file with a unique name. The temporary
file name is appended to the parameter string, and the print command
is run. This means that print requests to be copied to a file, directed
to a local printer, formatted for inclusion into documentation, and
other similar actions. It is the responsibility of the print command
to delete the temporary print file after it processed it. This parameter
overrides the value defined in the printfile parameter.
For Windows, a command file might
be necessary to act as an interface between the syntax of the command
and more general operating system syntax. For example, if the command
string is COPY printfile LPT2, a simple command file would be required
to reorder the parameters. Also, you can specify only a local program
in the printcommand parameter and UNC paths of
the type \\User1\Share\Notepad.exe are not supported.
For UNIX, you can use a shell script
with the Print command,
for example, lpr or rm.
This parameter is in the CLIENT section of the configuration file.
- Default value
- On Windows, if the printcommand parameter
and the printfile parameter are omitted, the
default action is to direct the print data to LPT1.
- Configuration Tool
- In the Configuration Tool, you can set the value of printcommand in
the Print command field on the Resourses tab
in the Client daemon configuration page.