Use the Virtual Printer interface to collect data sent by a TP-monitor (like CICS or IMS) to a VTAM-attached printer and store the collected data as a CA Spool file. This file can then be printed on any printer regardless of how it is attached (TCP/IP, PSF, or VTAM).
Business Value:
Virtual printer definitions save time and are less error prone than the process of manually changing application programs or modifying TP-monitor definitions. It is a best practice to let CA Spool take over the responsibility for the physical printing.
Additional Considerations:
Use the following samples as a starting point in your definitions for CICS, IMS, and IDMS virtual printer interfaces.
DEFNODE TCPVCIC,TCPIP,GROUP=1,SEP=0,ACQUIRE=WORK, RELEASE=NOWORK,CLASS=A,TCPDRIV=LPRET, VPSFILE=BRACKET,VPSERROR=PASS,VPSOPT=6 NODE PRTV1,TCPVCIC,TCPHOST=111.22.333.4,VPS=PRTV1
Be aware of the following:
Note that this format can also be used for an IDMS virtual printer definition.
For an IMS virtual printer definition, simply change the VPSFILE parameter from BRACKET to CHAIN.
DEFNODE TCPVIMS,TCPIP,GROUP=1,SEP=0,ACQUIRE=WORK, RELEASE=NOWORK,CLASS=A,TCPDRIV=LPRET, VPSFILE=CHAIN,VPSERROR=PASS,VPSOPT=6 NODE PRTV2,TCPVIMS,TCPHOST=111.22.333.4,VPS=PRTV2
Be aware of the following:
|
Copyright © 2011 CA.
All rights reserved.
|
|