VTAM Printer Support
Sterling Connect:Direct® for z/OS® uses VTAM Printer Support (VPS) to retrieve JES spool files for processing. Expansion of the VPS application includes Sterling Connect:Direct support for moving print files from the JES spool to any Sterling Connect:Direct node. The VPS module (VPSSCDI) directs spooled output from JES to the Sterling Connect:Direct API for file transfer.
The following diagram illustrates the flow of the print file through this process.
VPS passes control to the Sterling Connect:Direct API at the following times:
| Phase | Description |
|---|---|
| System Initialization | When a JES spool file is sent through Sterling Connect:Direct, VPS first transfers control to the Sterling Connect:Direct API for printer initialization and the API issues a SIGNON to the local DTF. |
| Printer Initialization | After signon, VPS copies the print files to a disk file and sends it to the Sterling Connect:Direct API. |
| SYSOUT Data Set Ready | The Sterling Connect:Direct API
constructs a SUBMIT PROCESS command to send printer attributes, data
set name, and the submitter's user ID to the local DTF. If the SUBMIT fails because the Process can not be found or the SNODE is unavailable, the print file is returned to the JES print queue according to the values specified in the requeue parameters. If the SUBMIT fails for another reason, VPS deletes the staged data set, drains its DTF WRITER, and leaves the JES spool file in the JES queue for restart. If the SUBMIT is successful, VPS releases ownership of the staged data set to Sterling Connect:Direct, and the JES spool file is PURGED from JES. |
| Printer Termination | When no more JES files are printing to Sterling Connect:Direct, a printer termination request is sent to Sterling Connect:Direct API. |
| System Termination | The Sterling Connect:Direct API then sends a SIGNOFF command to the local DTF. |
You can change VPSSCDI to modify Sterling Connect:Direct control blocks prior to calling DGASVPSA.