Barr software supports two types of Advanced Function Printing (AFP) printers: IPDS Group 3 printers (for example, the IBM 3825 and 3827) and VTAM-attached IPDS printers (for example, the IBM 3820). You can request either type of AFP support at no additional charge.
This chapter describes AFP requirements, explains how AFP works, and lists the required mainframe parameters. It also tells you how to monitor the printer status from the Barr software and how to use the Barr AFP Resource Saving feature.
AFP printing is controlled by the mainframe, and thus requires a mainframe connection. To attach AFP printers to the PC, you must have BARR/RJE, RJE+3270, BARR/3270, or BARR/AFP software. Because you can control AFP printers with a 3270 terminal session, you should use BARR/3270 or RJE+3270.
You also should use a printer control application such as the SPOOL Display and Search Facility (SDSF) from IBM or the Interactive Output Facility (IOF) from Fisher International. IOF software allows you to change the form or class and start or drain the printer. To obtain SDSF, contact your nearest IBM representative. To obtain IOF, contact Fisher International Systems, Naples, Florida, at 941-643-1500.
Because AFP printers communicate directly with the mainframe, they can only print data received directly from the IBM Print Services Facility (PSF). You cannot send RJE system files or PC-generated files to AFP printers and you cannot direct AFP files to the print spool or the PC disk. (Thus, AFP printers do not display on the Barr Assign Devices screen.) The only software options for AFP printers are those you can reach from the S/390 Channel Attached Printers screen.
PSF at the mainframe controls the printer via an LU Type 6.2 session. The LU Type defines session characteristics such as the type of data stream the session uses and type of communication the session supports. LU Type 6.2 uses the Intelligent Printer Data Stream (IPDS) and supports full-duplex communication.
The mainframe writes AFP jobs to the JES spool and then JES sends the jobs to PSF, which formats the jobs and sends them to the remote printer. PSF converts AFP data or line data to IPDS. As the jobs arrive at the PC, the Barr software directs the data to the AFP printer. PRINT370 does not modify the data stream except to request job header information for jobs going to IPDS Group 3 printers.
Because IPDS Group 3 printers work differently than VTAM-attached IPDS printers, the Barr software treats them differently.
The VTAM-attached IPDS printers process the IPDS data stream and implement SNA communications, so the Barr software simply passes the data and communications protocol between PSF and the printer. Data transfer from the mainframe LU to the Barr software is similar to the data pass-through in a gateway. Because VTAM-attached IPDS printers communicate directly with the mainframe, the Barr software does not know the nature of the data it sends and receives. The Barr software provides a 3270 session for viewing the status of VTAM-attached IPDS printers.
IPDS Group 3 printers only process the IPDS data. They do not implement SNA communications. The Barr software passes the data to the printer and performs the SNA communications. The Barr software also sends printer responses to PSF, which remains in full control of the printer. The printer status displays on the Barr Status Line.
For more information about the status for AFP printers, see section 7.4.
Unlike RJE, PSF does not support data compression. Thus, AFP requires faster communication speeds to obtain the same printer output rate as an RJE application. To generate the same number of pages per minute as RJE, AFP requires about twice the line speed.
When you use Barr software with AFP printers, host systems programmers must enter specific mainframe definition parameters in VTAM, PSF, and JES2. The definition consists of five parts. The sample definition in this section shows the statements you need for one AFP printer. Figure 7-1 at the end of this section shows portions of the mainframe definitions that must match.
In VTAM, the host programmer must define a logical unit (LU), physical unit (PU) and LU macros, and a logmode table.
PSF uses an LU to communicate with the remote AFP printer. More specifically, it uses an application LU. The host programmer enters the LU definition in the SYS1.VTAMLST(APPL) library. The LU definition that the Barr software requires is shown below.
The macro name (in this case, psflu) must match the APPLID value in the PSF definition.
The PU and LU macros are part of the VTAM NCP definition. The host programmer enters these macros in the SYS1.VTAMLST(NCP) library. The PU and LU macros display in the Barr software after you enter the Communication Link parameters. See your BARR/RJE manual or your 3270 manual for more information about any parameters not discussed in this section.
The following example shows PU and LU macros for the AFP printer.
The DLOGMOD parameter must have the same value in the NCP LU macro, VTAM Logmode Table definition, and the PSF printer definition.
DLOGMOD=bbbbbbbb
Specify the name of the logon mode table entry, or logmode, for the PSF printer. See AFP Logmode Table later in this section for the logon mode table definition Barr Systems recommends.
Mainframe LUs must be defined in a certain sequence, depending on the type of applications the LUs are used for. If LU1 is available, the host programmer usually begins defining AFP printers with LU1.
If you are using both VTAM-attached IPDS and IPDS Group 3 printers, or if the mainframe connection is through the BARR GATEWAY product, the host programmer must use LU1 for the VTAM-attached IPDS printer. Additionally, in the Barr software, you must set the option Allow IPDS Group3 printers to use LU1 to No from the Tuning and Global Options, Modem and Line Control screen. This ensures that PSF uses LU1 for the first VTAM-attached IPDS printer instead of the IPDS Group 3 type printer.
In the mainframe definition, the host programmer should assign the LUs in this order:
First, the host programmer assigns LUs to all VTAM-attached IPDS printers, beginning with LU1.
If you are not using VTAM-attached IPDS printers or the BARR GATEWAY, the host programmer can assign LU1 to the first IPDS Group 3 printer. Alternatively, if you are not using any VTAM-attached IPDS printers and you set Allow IPDS Group3 printers to use LU1 to No, the host programmer can assign LU1 to the first RJE session.
After LUs are assigned to all the VTAM-attached IPDS printers, the host programmer can assign the remaining LUs first to any 3270 sessions, next to any IPDS Group 3 printers, and finally to RJE sessions.
The list below shows how the host programmer would assign LUs for two 3820 (VTAM-attached IPDS) printer sessions, one 3825 (IPDS Group 3) printer session, four 3270 sessions, and five RJE sessions.
|
Session Type |
LU Number |
|
3820 |
LUs 1 - 2 |
|
3270 |
LUs 3 - 6 |
|
3825 |
LU 7 |
|
RJE |
LUs 8 - 12 |
This is an example of a typical AFP Logmode Table definition. The logmode is defined in the SYS1.VTAMLIB library.
PSF procedures describe the type of printer attachment (in this case, remote) and set up the different resource libraries needed for AFP printing. The host programmer must define a separate procedure in the SYS1.PROCLIB for each AFP printer. A sample definition follows.
The PSF procedure name (psfproc) and printer names (PRTxx) must match the values in the JES2 definition. The APPLID (psflu), LUNAME (luname01), and LOGMODE (BARRPSF) must match the values in the VTAM definitions.
The example below shows the Printer Definition portion of the JES2 Remote Definition. Define AFP printers according to the example.
It is helpful to understand how the five parts of the mainframe definition are related. Each part of the definition contains parameters that are common to another part. Make sure these values match, as illustrated in Figure 7-1.
Figure 7-1. The PSF definition shares some parameter values with the JES2 and VTAM definitions.
Barr software provides status information for the AFP printers. The status displays differently for the two types of AFP printers.
When you start the Barr software, the software requests the printer type and model of each AFP printer, and then displays this information on the Operation screen. Information for IPDS Group 3 printers displays on the Status Line. Information for VTAM-attached IPDS printers displays on the console portion of the screen.
If the printer status information does not display, confirm that the printer is powered on and online.
The IPDS Group 3 printers appear on the Barr Status Line as AFPxx, where xx is the printer address. Status information includes a block count of data printed and the printer status.
In this example, the status shows that zero blocks of data were sent to the printer AFP0E and that the printer is idle. The printer name is color-coded to indicate the connection status with the mainframe. If the printer has not bound to PSF, the status information is red. If the printer has bound to PSF, the status information is yellow.
For more information about the Status Line messages for AFP printers, see section 8.1.
You can view two types of status information for VTAM-attached IPDS printers. The console message displays the printer address and printer model and a separate Link Status screen displays more detailed information.
In this example, the software found a 3827 Model 01 printer at address 1E.
To view the status of the VTAM-attached IPDS printer, switch to the Barr 3820 session. For more information about switching between sessions, see the BARR/RJE Operation, Advanced section in your BARR/RJE manual or your BARR/SPOOL manual.
The Link Status screen displays the real-time status of the mainframe connection, local sessions, and the AFP printer LUs. When the state of the SNA links change, the software updates the status screen. Check this screen if a problem arises with 3820 printing.
In this example, S/370 CHANNEL LU is an AFP printer awaiting activation and S/370 1E is an active AFP printer.
Link Information A link is a communication channel that connects the Barr PC with the mainframe.
All communication with the mainframe goes through the HOST link, the first link on the screen. The LOCAL link represents all the RJE, 3270, and non-3820 AFP sessions. The remaining links are for the 3820 AFP printers. Each link is either disconnected from or connected to the mainframe.
The following information displays for each link.
Link
The link name.
Receive
The number of SNA frames received from the mainframe on this link since the link connection was made. For HOST, this is the sum of the frames received from the mainframe for all the links since you started the Barr software.
Send
The number of SNA frames sent to the mainframe from the link since the link connection was made. For HOST, this is the sum of the frames sent to the mainframe by all the links since the Barr software started.
Start
The time of day when the link connection was made.
Last
The time of day when data was last sent or received on this link.
Sessions
The first value is the total number of LUs requested by the Barr software. The second value is the number of LUs in use. If the first number does not equal the second number, the mainframe did not grant the total number of LUs you requested.
Status
The link status has four possible values.
Active The link is ready to exchange data.
Inactive The link is shut down and will not accept connection requests. Check the Operation screen for error messages that might indicate a problem.
Opening For the HOST link, the Barr software is trying to connect to the mainframe. For a 3820 link, the Barr software is trying to establish a session with the printer.
Closing The link connection was broken. This can happen at the end of user signoff, if the mainframe breaks the connection, or if you issue a Close command.
Additional Link Information The following fields display at the bottom of the Link Status screen. They give more information about the current link, the link which is highlighted on the screen. You can change the current link selection with the cursor movement keys.
Link
Each link has a unique number which helps you keep track of your place in the menu when many links appear in the list.
Protocol
The communication protocol for this link, usually SDLC, LOCAL, TOKEN RING LLC, or S/370 CHANNEL.
PU state
For the HOST link, this is the SNA state of the PU maintained between the mainframe and the Barr software. No SNA communications can take place until the PU is active. The following values can display in this field.
Active Normal state. SNA communications can take place.
Inactive The Barr software is waiting for ACTPU (Activate Physical Unit) from the mainframe.
PendAct Pending Active. The Barr software sent ACTPU but has received no reply.
PendInact Pending Inactive. Barr software sent DACTPU (for logoff or Deactivate Physical Unit) but has received no reply.
Buffers
The number of SNA frames waiting to be transmitted on this link, either to the mainframe or destination LU (local or 3820). This measures traffic on the link.
Link Commands From the Link Status screen, you can issue commands to control the current link (highlighted link).
Close
Press C (for Close) to disconnect the current link. Close is an abrupt disconnect. All communications on that link will be interrupted and data could be lost. For the HOST link, Close results in all other links being closed as well.
Open
Press O (for Open) to make the current link available for connection. Usually you only need to open links that were closed with the Close command or closed by an error condition.
Link LUs You can get additional information about the HOST and session LUs by selecting a link and pressing ENTER. You can view two screens of information (not shown in this text). To reach the second screen, press the RIGHT ARROW key.
For the HOST and LOCAL links, you might see multiple LUs listed. For a 3820 link, only one LU will be listed.
These two screens list information for Barr Technical Support. If you call for support, you might be asked to provide some of the information on these screens.
If you use AFP with an IPDS Group 3 printer, you can use the resource saving feature. The only resource Barr software supports is fonts. Font resource saving stores frequently used fonts on the local PC hard drive. As a result, fonts need to be sent over the communications line only once instead of every time the printer uses the font.
To use font resource saving, follow these basic steps.
Mark frequently used fonts public in PSF.
Enable the BARR/RJE software to use resource saving.
Maintain your stored fonts.
To enable font resource saving, you must mark each font public in PSF. This allows the font to be stored remotely. For the entire font to be marked public, you must mark each component of the font. Consult your host systems programmer to determine how to accomplish this step.
After you mark a font public, the mainframe computer checks for the font on the PC before it sends the font over the communication line. Your next step is to set up the Barr software so it can respond to the mainframes inquiry.
You need to enter settings on the PRINT370 AFP Description screen.
Select S/390 Channel Attached Printers.
Select AFP Options.
You must fill in the two fields of the PRINT370 AFP Description screen. The third field is optional.
Enable Local Resources?
Choose whether or not to enable AFP font resource saving.
No Default. Do not use AFP font resource saving.
Yes Use AFP font resource saving.
AFP Resource Directory:
Specify the directory where font resource files will be stored. The Barr software searches this directory when it needs to load a font. Include the drive and the full directory path. The default directory name is C:\BARR\AFP, the name of the directory where the RESOURCE.EXE file resides. If you specify a different directory name, remember to create the actual directory.
Log Job Start/End to Console?
Choose whether or not to display a console message at the start and end of jobs printed on the AFP printer.
No Default. Do not display a console message at the beginning and end of each job.
Yes Display a console message at the beginning and end of each job.
After you set up the Barr software to use AFP resource saving, the software begins to store fonts on the PC. Each time the mainframe sends a print job that uses a public font to the PC, the mainframe checks for the font on the PC. Barr software checks if the font is stored. If the Barr software finds the font on the PC, it tells the mainframe not to send the font again. If the Barr software does not find the font, the mainframe sends a copy of the font to the PC. The Barr software stores the font on the PC disk for future use and loads the font into the printer for the current job.
Now you must manage the font files on your PC. Consider which fonts you use frequently enough to store on your PC. Do you want to store a font you only used once and will never use again? Is it worth your PC space to store a font for a twice-a-year print job? The Resource utility included on the Barr software disk helps you manage the AFP resource files stored on your PC.
You use two files, RESOURCE.EXE and RESOURCE.DAT, to run the Resource utility.
The RESOURCE.EXE file comes on the Barr software disk. When you install the software files on your PC, the installation program puts RESOURCE.EXE in the C:\BARR\AFP directory. If you create a different directory for your AFP files, copy the RESOURCE.EXE file from the C:\BARR\AFP directory into your AFP directory. Remember, the name of the directory you create must match the directory name you specify on the PRINT370 AFP Description screen.
The Barr software creates the file RESOURCE.DAT the first time you run the software and store a font. RESOURCE.DAT contains information about your stored fonts. The Barr software uses this file to locate fonts and the Resource utility uses this file to manage font files.
Store your fonts in a separate subdirectory in the AFP directory. For example, store all fonts in a subdirectory named FONT. If you named your font directory C:\BARR\AFP, your directory listing might look like the following.
You can divide the FONT directory into separate subdirectories for each font type stored on the PC.
To maintain your font files, use the Resource utility. This utility lists stored fonts, shows how often those fonts were used, and allows you to delete the fonts that you rarely use. You must unload the BARR/RJE software before you run the Resource utility. To run the Resource utility, type resource at your DOS prompt.
Resource Utility Keys While in the Resource utility, you can use the following keys:
|
Key |
Description |
|
SPACEBAR |
List the valid options for a field. |
|
ENTER |
Select a value from an option list when an option list displays. Otherwise, move to the next screen. |
|
ARROW UP |
Move between the screen fields. |
|
ESC |
Exit the utility. |
|
PAGE UP |
Navigate through the list of fonts. |
AFP Resource Facility Screen The initial Resource utility screen contains two options.
Resource Types
Barr software supports only FONT resources.
Sort Order
Choose the order in which to list fonts.
Usage Sort by total number of times the resource has been used.
Last Used Sort by last date the resource was used.
Date Copied Sort by date the resource was originally copied to the resource directory.
Resource ID Sort numerically by resource ID.
AFP Resource List Screen From the first screen of the Resource utility, press PAGE UP or PAGE DOWN to reach this screen, which lists information about each font you stored.
ID
Identification number assigned to the font by Barr software.
Type
Type of resource. Barr software supports only FONT fonts.
Member
Name of the mainframe member from which the font originated.
Font Type
Type of font. This column is subdivided into five columns (OOOOO). Marks in the columns indicate the font type.
Indicates a base font.
Font index for a 0-degree rotated font.
Font index for a 90-degree rotated font.
Font index for a 180-degree rotated font.
Font index for a 270-degree rotated font.
Use
Total times the resource was used.
Last Used
Last date the font was used.
Copied
Date resource was originally copied to the resource directory.
Member/Data Set Name
Mainframe library or partitioned data set (PDS) from which the font originated.
Volser
Mainframe volume serial number from which the font originated.
Date
Last date the mainframe font was modified.
Time
Time at which the mainframe font was last modified.
Delete Stored Resources To delete fonts on the AFP Resource List screen, use the keys described below.
|
Key |
Description |
|
DEL |
Delete the highlighted or tagged fonts. The cursor rests on the highlighted font. Tagged fonts have a checkmark. |
|
SPACEBAR |
Tag or mark fonts to delete. |
A sample screen follows.
In this example, assume you tagged FONT 0009, FONT 0011, and FONT 0012. When you press DELETE, the prompt Tagged or Highlighted (T/H) displays. Choose whether to delete the tagged or highlighted fonts. Use the keys listed below.
|
Key |
Description |
|
T |
Delete all tagged (checked) fonts. |
|
H |
Delete only the font where the cursor rests. |
|
ESC |
Close the delete box without deleting any fonts. |