Typically, you create one printer definition for each printer and one for each email destination. In the printer definition, you specify the printer's address or the recipients' email addresses. However, depending on the job submission method that is used and the type of printer, job submitters can sometimes specify a printer's address or email addresses during job submission in job attributes and JCL parameters. If so, you might be able to create one printer definition for a group of printers that share attributes, and another printer definition for all email destinations.
|Published (Last):||3 October 2017|
|PDF File Size:||11.24 Mb|
|ePub File Size:||18.89 Mb|
|Price:||Free* [*Free Regsitration Required]|
Typically, you create one printer definition for each printer and one for each email destination. In the printer definition, you specify the printer's address or the recipients' email addresses. However, depending on the job submission method that is used and the type of printer, job submitters can sometimes specify a printer's address or email addresses during job submission in job attributes and JCL parameters.
If so, you might be able to create one printer definition for a group of printers that share attributes, and another printer definition for all email destinations.
After you create printer definitions and specify attributes that are used by IP PrintWay, job submitters can print from batch applications by using JCL. For information about these attributes, see Planning printer and printer pool definitions for NetSpool and Planning printer definitions for Print Interface. IP PrintWay extended mode also uses the new attributes the next time it tries printing a data set that failed to print.
Guideline: Create at least one printer definition for each printer for these reasons: Some job submission methods for example, the LPR command do not support specification of job attributes or JCL parameters.
Job submitters cannot specify the printer's address if the printer uses the IPP protocol. Infoprint Central cannot display information about idle IP PrintWay printers when a printer definition does not exist for that printer.
In the printer definition, you also can specify attributes that IP PrintWay uses to format data in the output data set and transmit data sets to the printer. Table 4 summarizes the printer attributes that IP PrintWay uses and indicates whether the attributes are required or optional. Table 1 lists the information that describes how to do IP PrintWay tasks. Some of the tasks apply only to the indicated IP PrintWay transmission protocol.
If no mode is indicated in parentheses in the title, the task applies to both modes. Table 1. Note: For detailed information about each field such as values you can specify, restrictions, and examples , use the online help for each field on the Infoprint Server ISPF panels. Comparing printer definitions for IP PrintWay basic mode and extended mode. Selecting the LPR protocol. Selecting the direct sockets protocol. Selecting the IPP protocol. Selecting the email protocol. Specifying a printer definition name, description, and location.
Setting up operator security for the printer extended mode. Specifying allocation parameters for IP PrintWay. Handling unsuccessful data transmissions.
Retaining data sets on the JES spool. Tracking the number of printed pages extended mode. Converting line data to a text data stream. Using an FCB to format data. Transmitting multiple data sets in a JES output group. Sending commands to the printer. Validating that data sets can print as requested. Creating an IP PrintWay default printer definition. Using an installation-provided filter. Resubmitting documents to Print Interface for filtering basic mode.
Printing data without formatting basic mode. Formatting for PostScript landscape orientation basic mode.
Table 1 summarizes the tasks to customize IP PrintWay extended mode. Required tasks are necessary for all installations. Optional tasks are required only if the listed condition applies. Tip: Run IP PrintWay extended mode to obtain better performance, improved usability, and more functions.
Migrate from IP PrintWay basic mode to extended mode
Figure 1 shows the steps that occur from the time IP PrintWay selects output data sets from the JES spool until it transmits them to the printer or email destination and then deletes them from the JES spool. An explanation of each step follows. IP PrintWay can retransmit an unsuccessful transmission for a specified number of times at a specified interval. In addition to the requested retransmissions, IP PrintWay tries an unsuccessful transmission automatically for a short time after transmission. The administrator can use IP PrintWay extended mode to define a backup printer in case the retransmissions fail because the IP PrintWay printer is broken or offline. The operator can then select the backup printer for IP PrintWay to use when the primary printer is not functioning.