- 100% Command Level Coding to support CICS 3.2 and later.
- “Virtual Key” support, which lets DynaPrint share a PA or PF key with existing applications. Even if all of your PF or PA keys are being used by other applications, you can still run DynaPrint.
- Users are given a list of available printers when re-routing output. The list can be changed dynamically if a printer is added or placed out of service.
- User exits that allow CICS screens to be printed on system printers or routed with VPS or other report distribution systems.
DynaPrint delivers simple controls for printing CICS screens. Users can print the exact contents of their 3270 screens on any CICS printer or high-speed system printer, and can customize page headers, banner pages, form feeds, scales, and blank-line suppression. Just press the print key to get an exact copy of the image on your screen at the printer of your choice.
- VSE/SP, VSE/ESA, OS/VS1, MVS/370, MVS/XA, MVS/ESA, OS/390, or z/OS.
- IBM 3270-type terminals or emulators.
- CICS 1.7 or greater.
- INQUIRE/SET support in your PPT.
- VSAM access for the definition file.
- VTAM or BTAM access for printers and video terminals.
- VSAM or BDAM access for the control file.
- If the control file works with BDAM, any IBM CKD-type disk device.
If the control file works with VSAM, any VSAM-compatible disk drive.
- DynaPrint functions properly in an MRO environment. Install it in each of your terminal-owning MRO regions.
- IBM terminals operating in model 1, 2, 3, 4, or 5 mode can be used in any combination.
- Load the libraries from tape.
- Define files, programs, and transactions.
- Set CICS parameters and add to the startup JCL.
- Refresh CICS.
- Set the initial parameters for DynaPrint.
- Verify the installation.
- Customize the installation.
- CICS Assembler programs to define your environment and process your print requests.
- CICS transactions for users’ preference-setting and print requests.
- An Assembler program that can route screen images to the JES or POWER queue.
- A definition file, which stores system configuration and users’ print-formatting preferences.
- A control file, which stores users’ printer selections.
- An Assembler program to format and load the control file.
- An Assembler program that gives CICS applications access to the control file.
- A sample Assembler program that can be used to modify page headers.
- A sample Assembler program to provide a default printer selection and override users’ selections.
- Node Error Program (NEP) code for receiving screen prints while a VTAM terminal is engaged in a conversational transaction.
- Terminal Error Program (TEP) code for receiving screen prints from a BTAM terminal.