FAQ

In EPM you can map raster fonts to outline fonts, either by font family (byte 3-6 of the font name) or by the entire font name (byte 3-8).

The mapping by family name does not fit in if the last 2 bytes don't meet the compatibility font naming standard, where the point size is calculated on basis of byte 7 and 8 (byte 8*36 + byte 7) Please note that byte 7 '0' means 10 and 'A' means 11, 'B' means 12 and so on.

As a result, C0S0CR12 equals point size 83 (11 + 2*36) though you would probably want a 10 point 12 pitch outline.

Use the 'mapping by font name' table:

*
* TABLE THAT MAPS SINGLE OUTLINES <> RASTER
*
SCALEMAP DC AL4(0)
DC CL6'S0CR12',CL6'4200',AL2(10) MAP C0S0CR12 TO COURIER 10 POINT
DC CL6'S0CR10',CL6'4200',AL2(12) MAP C0S0CR10 TO COURIER 12 POINT
DC AL4(0) END OF TABLE

Yes - EPM can create PDF documents, just select "TYPE=PDF" in the printer profile.

There is a number of facilities along with the creation of PDF documents, like:

• Use of Acrobat Reader built-in fonts to minimize file size.
• Use of AFP outline fonts to create nicer looking text in the PDF documents.
• Full color support on graphics, text and rulers.
• Support of graphic objects like TIFF or JFIF (JPG) with user defined compression.

You can use the EPM facility "SUBMIT" that automatically submits a JOB after successful creation of the data set. Use the parameter "SUBMIT=<jobname>" on the printer definition. (Submit JCL...;in Panel EPM1210C)

Sample JCL:

//FTPJOB JOB (ACCT#),'IDA1',CLASS=A,MSGCLASS=L,MSGLEVEL=(1,1),
// TIME=1440
//FTP EXEC PGM=FTP,REGION=4096K
//INPUT DD *
172.16.11.112
ida1
<password>
binary
put '%DSN' /PDFPRINT/%DSN..PDF
quit
/*
//OUTPUT DD SYSOUT=L
//SYSPRINT DD SYSOUT=*

Yes - record format in pagedef / formdef is supported by EPM version 1.04.00 and up. 

Yes - Enhanced N-up is supported by EPM version 1.04.00 and up.

This problem can be solved by un-clicking Use Greek Text Below 6 Pixels in the Acrobat reader. You find the setting in Acrobat Reader under File Preferences and General Parameters. The changed setting in Acrobat Reader does not influence any other PDF files.

Yes - EPM supports MO:DCA Objects TYPE 'OTHER' TIFF and JFIF.

Just upload your pictures to MVS, and define your object as object type 'OTHER' and as a TIFF or JFIF component.

You could also place it in a PageSegment as an object container, with the EPM Utility 'PUTOBJ', and use it directly in your LineData with an IOB (include object) structured field.

If you are certain that the printer has a duplexer installed, then the problem might be that the printer definition in EPM must reflect that the printer supports duplex:

Profile sample:

Enterprise Print Manager
PRINTER PRTID=MYPRT,DUPLEX=YES,<other parameters>

EPM Menu (panel EPM1210K 'MODIFY CONFIGURATION'):

Printer capability

Duplex . . . . . . YES

If you are certain that the printer has a duplexer installed, then the problem might be that the printer definition in PSS must reflect that the printer supports duplex:

Profile sample:

Print SubSystem
PRINTER PRTID=MYPRT,DUPLEX=YES,<other parameters>

Printer capability

Duplex . . . . . . YES

This document tells you how to create a PDF file and at the same time have the job printed on the printer.

Many users easily find out how to create a PDF file from an AS/400 or Mainframe print job and store it in the directory specified via PrintGuide. This, however, will only create the PDF file and will not print the job.

The reason for this is that DocOut, by default, is not authorised as a user of the network. This means it cannot start Adobe Acrobat Reader for printing the PDF document. To be able to create and print PDF documents simultaneously, you must allow DocOut to logon as a user who is already defined and authorised on the Windows server.

Special Requirements

The printer to be used in connection with PDF printing from DocOut must be setup with a printer driver for this printer. The printer must be able to receive and print from normal Windows applications, including Adobe Acrobat Reader.

Note: Adobe Abrobat Reader must be installed and initialised on the system.

Do the following:

1. Set up DocOut to generate PDF files.
2. Click the Start menu, point to Settings, and then click Control Panel.
3. Double-click the Services icon in the Control Panel.
4. Select the DocOut service, click the Stop button and wait for the Service to stop.
5. Select the DocOut service and click the Start button.
6. Check 'This Account' and enter user name* and password (twice).
7. Click OK twice.
8. Start the service for DocOut and watch to ensure that the Service starts.
9. Click Close.

*) It is important that this user has logged on to the Windows Server system at least once in order to initialise this user for the applications currently running. This user must have Administrator rights.
DocOut is now configured for printing the job at the same time as a PDF file is generated on the disk.

If the output printer language is PCL:

1. Start PrintGuide™.
2. In Monitor View, locate the PrintServer in the list of Detected Devices and double-click it.
3. In Configuration View, locate a Logical Printer that matches your requirements and double-click it.
4. Select the Printer tab to show the Printer Settings. The Tray Definitions shown represent a physical description of the connected printer's input and output (if applicable) trays.If Auto Configure Settings is checked, the PrintServer gets the description from the physical printer when it is started up. If unchecked, you can change the definitions manually. The PCL values used are specific to the printer model and determine the tray used.
5. If you want to change which physical tray is used for a particular definition, you must refer to the printer's manual and change the PCL value in the table to reflect the PCL Media Source you want to use. Note: The PCL values are the same as the PAPERSOURCE values in the printer description (*.itc) file.
6. If you want to install/ uninstall a particular tray, click on the Installed value in the table to toggle Yes/ No.
7. Select the PSS/ IPDS/ DCA/ SCS tab. The installed trays are mapped from the host to the printer as shown in the Tray Mapping table. If Auto Configure Settings is checked, the PrintServer automatically maps the trays based on the Tray Definitions table when it is started up. If unchecked, you can change the mappings manually.
8. When you have finished editing the settings, select PrintServer, Save Configuration.
9. Click OK to confirm, remembering to check Restart PrintServer after download.

If the output printer language is Postscript:

If you want to change the physical tray used for a particular Tray definition, use this procedure. This is the only Tray Definition parameter that cannot be changed from PrintGuide™ for printers using PostScript. Please refer to the procedure above for change of other Tray Definition parameters (for example; whether a tray is Installed), or to change Tray Mapping.

1. Follow steps 1 to 3 of the PCL language procedure, above.
2. In General Settings, change the Description to make it unique. Write it down. You need to be able to identify this logical printer later in this procedure.
3. Click OK.
4. Select File, Save As to save the configuration to file (*.cf2).
5. Open the configuration file in a plain text editor (for example; Notepad).
6. Search for the logical printer Description you wrote down earlier. Write down the printer incarnation id.

Example:

BEGIN_CONFIGURATION PRINTER 1

The incarnation id here is 1.

1. Locate the printer description file (*.itc) that most closely matches your printer model.
2. Open the *.itc file in a plain text editor (for example; Notepad). A collection of these files are installed together with PrintGuide™ in a subdirectory named Printer Descriptions.
3. Edit the file to match the printer incarnation id you wrote down earlier in step 6 and save the file under a new name.
4. Locate the PostScript language specific information part of the file.
5. Refer to the PostScript language section of the printer's manual to find its Media Position value (HP printers & PostScript Level 3) or Priority value (all other printers). Change the INPUTPRIO value in the table to match.
6. Save the *.itc file.
7. In PrintGuide™, Monitor View, highlight the PrintServer in the list of Detected Devices.
8. Select PrintServer, Update Configuration.
9. Change Files of Type to All files *.*, locate the edited *.itc file.
10. Click Open.
11. Click OK to confirm and ensure to check Restart PrintServer after download. The PrintServer merges the edited *.itc file with its current configuration.

Check/change the QAUTOVRT setting

1. Issue the WRKCTLD*.VWS command.
   This will determine the number of auto-configured virtual controllers on the system.
2. Issue the DSPSYSVAL QAUTOVRT command.
   If the system value of QAUTOVRT is zero, devices must be configured manually. See Installation & Operator's guide for further details.
   If the system value of QAUTOVRT is equal to the number of auto-configured virtual controllers, the QAUTOVRT value must be increased by the number of devices you want to configure.

Configure the PrintServer using PrintGuide™

1. Start PrintGuide™.
2. In Configuration View for the selected DocOut™ PrintServer, locate the DCA using TN5250e logical printer.
3. Right-click on it in the list and select Edit Logical Printer.
4. Select the Telnet Print tab.
5. Enter the Device Name.
   This will be the printer's name on the AS/400. It must unique and must have 10 characters or less.
6. Enter the AS/400's IP address in Host IP Address.
   Note: The Host Port is default set to 23. This is the standard, pre-defined Telnet port and it is most unlikely that you will need to change it.
7. Click OK.
8. Select Save Configuration, remembering to check Restart PrintServer after download in the Confirm dialog.

From a licensed DocOut™

Use PrintGuide™ to backup your DocOut™ configuration.

1. Start PrintGuide™.
2. In Monitor View, locate the DocOut PrintServer in the list of Detected Devices and click it.
3. On the PrintServer menu, click Backup Configuration.

From an expired DocOut™

Follow the steps below to port the configuration from an expired trial version of DocOut™.

1. You must manually backup the file factory.cf2 in the DocOut installation directory and the cfg subdirectory. The typical DocOut installation directory is: c:\Program Files\MPI Tech\DocOut.
2. Uninstall DocOut.
3. Install the latest DocOut™ version without starting the DocOut service.
4. Restore the files you saved in step 1 into the installation directory of the newly installed DocOut™.
5. Start the DocOut service.

The DocOut™ service starts automatically after a reboot, but it can also be started and stopped manually.

1. Click the Start menu, point to Settings, and then click Control Panel.
2. Double-click the Services icon in the Control Panel.
3. Select the DocOut™ service and click the Stop button.
4. Select the DocOut™ service and click the Start button.

A trace may be requested by MPI Tech to recreate and solve a specific customer problem. Many trace options are available on the market to capture various data streams. However, to get the necessary information we ask that you use the built-in trace option from DocOut™.

The data is captured in a special format, readable by using special tools from MPI Tech. This ensures the fastest response from MPI Tech.

Do the following:

1. Stop the service for DocOut™.
2. Enable the trace on the Windows Server as follows (using a DOS Prompt):
   Enter the library (default library): C:\Program Files\MPI Tech\DocOut
   Type: ‘Pcontrol -logtrc on’ <ENTER>
3. Start the service for DocOut™.
4. Start the Writer for the specific printer on the system.
5. Send the job and leave sufficient time for the system to finish the job (The job will be printed during the trace).
6. Disable the trace on the Windows Server as follows: (using a DOS Prompt):
   Enter the library: C:\Program Files\MPI Tech\DocOut
7. Type: ‘Pcontrol -logtrc off’ <ENTER>

The traces are placed in: (default location) '[Drive]:\Program Files\MPI Tech\DocOut\traces\log.trc'

If more than one trace is made, please rename the trace file in ...\traces\log.trc, as the trace will always use the name 'log.trc' overwriting any existing trace with the same name.

This reflects to DocOut version 4 and higher

Do the following:

1. Start PrintGuide™.
2. Locate and highlight the DocOut™ PrintServer in the list.
3. Select ‘PrintServer’ – ‘License Manager’ – Change –‘OK’.
4. Select ‘Send License Key to Selected Product’ and hit ‘Next >’.
5. Select ‘Read from file’ and hit ‘Next >’.
6. Locate the supplied license key file and select ‘Open’
7. Hit ‘Next >’ and follow the instructions 
   Leave the ‘Golden Key’ option unchecked unless otherwise instructed.
8. ‘Restart PrintServer after download’ must be enabled.
9. Wait for download confirmation and click OK
10. Monitor the DocOut™ restart.
11. Verify correct download of the license key
    Successful installation of the license can be verified using the ‘License Manager’

Notes:

• The evaluation key is assigned by MPI Tech along with an expiration date, typically via e-mail. We recommend to detach and use the attached .lic file or to copy and paste the key from the e-mail.

An evaluation extension key can be inserted in DocOut™ regardless of whether the previous evaluation period has expired. The expiry date can be verified in the PrintGuide's License Manager Window.

DocOut™ is capable of creating PDF files that can be stored on the hard disk of a Windows PC and used for archiving, viewing and reprinting purposes.

PDF is a format which is readable by Adobe Acrobat Reader. Printing from Adobe Acrobat Reader is done using the normal Windows Server functions and formatted using the currently installed printer driver for the printer in question. This will enable AFP jobs to be printed not only to PCL and Postscript printers but also on other graphics-capable printers, including matrix and inkjet printers.

Acrobat Reader is included on, and can be installed from, the DocOut™ installation CD.

Do the following:

This procedure requires the logical printer to be created and stored in DocOut™.

1. Start PrintGuide™.
2. Highlight the DocOut™ in question and double-click to view the logical printers.
3. Highlight the Logical printer that must be changed to create PDF files.
4. Double-click on the selected printer or click Edit.
5. Enter the IPDS folder.
6. In IPDS Settings select Language: PDF.
7. Enter the Port Driver (or Spool) folder and select: Print with Acrobat Reader
8. In File Path, enter the preferred disk and directory for the generated PDF files.
   If this is left blank, the PDF file is stored in the same directory as the one in which DocOut™ is installed.
9. Click OK to return to the logical printer view.
10. Right-click the logical printer in the list and select Save Configuration.
11. Check Restart PrintServer after Download and click OK.
12. Click OK after successful download to confirm the new settings information.
13. Monitor the restarting of DocOut™.

DocOut™ is now configured for creating a PDF file from the IBM host print job. The PDF file will be stored in the directory specified in the procedure above.

DocOut™ supports printers directly via TCP/IP and printers with a local spool queue attached. Printers that are configured to direct print or LAN manager printers are not shown in the selection list for a logical printer spool in the Logical Printer Wizard and PrintGuide™.

1. Click the Start menu, point to Programs, and then click Command Prompt.
2. Type 'net use' in the Command Prompt window to see information about your computer connections. Refer to Microsoft Windows Help for information on the net use command. For example to assign the lpt2: port to the LAN manager printer \\ida00483a\p1_printer_1 you should type:
   net use lpt2: \\ida00483a\p1_printer_1
3. Click the Start menu, Point to Settings, and click Printers.
4. Right-click a printer, and click Properties. Click the Ports tab, and check the Port (lpt2:)

This document describes how you configure the Windows environment so that DocOut™ can use a printer that doesn't have a local spool queue.

DocOut™ is not able to print to printers which do not have a local spool queue. For example, DocOut™ is installed on a separate NT Server or NT Workstation, but the printers in the network are defined on another NT Server.

Since DocOut™ can only use printers which have a queue present on the same PC on which DocOut is installed, we cannot use Share Names. The reason for this is that if we define a Network Printer instead of a Local Printer, it only appears like a queue; in fact no queue is created locally.

This gives not only a problem for DocOut™, but also for NT-Workstations. If, for example, a user wants to change the Printer Settings, he is, depending on the PrintServer's Authorisation, not able to - or if he is allowed to do that, the Settings are changed on the PrintServer. This would affect all users!

The only way around this problem is to use LPR printing to the Printserver. This means, that we have to create a Local Printer using LPR on the Workstation or Server where DocOut™ is located and to allow LPR printing on the Server where the printers are defined.

On the Windows NT PrintServer, do the following:

1. Install the Microsoft TCP/IP Printing Services if not already installed.
2. In the System Settings select Services and look for TCP/IP Print Server.
3. Click on Starttype and Select Automatic. Then click on OK.
4. Now click on Start and verify that the Service shows Started.

Now the PrintServer is ready to accept Jobs via the TCP/IP LPR Protocol on all Printers defined as Shared. The Share Name is used as LPR Queue Name.

Perform the following on the DocOut™ Workstation or Server:

1. Install the Microsoft TCP/IP Printing Services.
2. Add all printers using the Add Printer Wizard and select Local Printer.
3. Click on Add Port.
4. Select LPR Port and then New Port.
5. In the first field, enter the IP address or IP Hostname of the Server, where the printers are defined and in the second field enter the Share Name.
6. Click on OK.
7. Click on Next.
8. Select the printer manufacturer and model. Note: If a model is requested for the first time, Windows NT asks you to insert the Installation CD.
9. Specify a name for the printer. We recommend you use the same name as it is defined already in the Printserver.
10. Choose Not Shared.
11. Select Print Test Page and verify afterwards that the test page has been printed.

You are now able to use the defined Print Queue in DocOut™.

The IBM OS/390 version 2.8 is capable of supporting TN3270E sessions communicating directly. The following describes the required mainframe definitions for a PrintServer. It is assumed that the TN3270E service is already active on the mainframe.

1. Mainframe TCPIP profile definitions:

PRTGROUP PRTGRP1

LU08

TCPPRT01 TCPPRT02 TCPPRT03 TCPPRT04 TCPPRT05

TCPPRT06 TCPPRT07 TCPPRT08 TCPPRT09 TCPPRT10

TCPPRT11 TCPPRT12 TCPPRT13 TCPPRT14 TCPPRT15

ENDPRTGROUP

IPGROUP IPGRP1 255.255.0.0:128.0.0.0 ENDIPGROUP

LUMAP LUGRP1 IPGRP1 SPECIFIC PRTGRP1

PRTMAP PRTGRP1 IPGRP1

************

2. SNA definitions:

TCP VBUILD TYPE=APPL

LU08 APPL EAS=1, ESTIMATED CONCURRENT SESSIONS *

AUTH=ACQ, *

VPACING=3, *

MODETAB=RSCSTAB, *

SESSLIM=YES

TCPPRT* APPL EAS=1, ESTIMATED CONCURRENT SESSIONS *

AUTH=ACQ, *

VPACING=3, *

MODETAB=RSCSTAB, *

SESSLIM=YES

The link service allows the SNA server to communicate with host, peer, or downstream computers over Token Ring and Ethernet LANs.

1. Start the Microsoft SNA Server Manager.
2. In the left pane click the server on which the link service will be installed. On the Insert menu, click Link Service.
3. In the Insert Link Service dialog select Link Service i.e. DLC 802.2 Link Service and click Add.
4. In the Title box you can use the default title or type your own.
5. In the Adapter box, select the adapter card you are using.
6. Leave the remaining properties at their defaults or click Help for additional information.
7. Click OK and then click Finish in the Insert Link Service dialog.

1. Click the Start menu, point to Settings, and then click Control Panel.
2. Double-click the Add/Remove Programs icon in the Control Panel.
3. Click the Install/Uninstall tab.
4. Select the program from the list and click Add/Remove.

Installation of trial license key

This is for trial versions only:

1. A temporary license is included with the first installation of DocOut
2. Start DocOut
3. Click 'License Manager'
4. Verify temporary license

Installation of purchased license key

This is for purchased license registration only:

1. Obtain the license from your dealer or local MPI Tech office
2. Start the PrintGuide program
3. Click 'PrintServer', then click 'License Manager'
4. Follow the instructions installing the license

Since the Microsoft SNA Server does not include the QSPWTR mode needed for LU 6.2 - IPDS printing, we will describe how to create it:

Insert APPC Mode Definition

1. Start the Microsoft SNA Server Manager.
2. On the Insert menu, point to APPC and click Mode Definition.
3. Type QSPWTR as Mode Name. Comment is optional, but we recommend you write Mode for LU 6.2 Printers.
4. Click the Limits tab. Enter the values below:
   1. Parallel Session Limit: 8
   2. Minimum Contention Winner Limit: 0
   3. Partner Min. Contention Winner Limit: 0
   4. Automatic Activation Limit: 0
5. Click the Characteristics tab. Enter the values below:
   1. Pacing Send Count: 63
   2. Pacing Receive Count: 63
   3. Max Send RU Size: 1024
   4. Max Receive RU Size: 1024
   5. Check High Priority Mode
6. Click OK to complete the insertion of the new mode.

Note: You need to configure a local LU for each printer you intend to use with DocOut™.

• In the left pane of the Microsoft SNA Server Manager click SNA Service. On the Insert menu, point to APPC, and click Local LU.
• Enter LU Alias (used in DocOut™) and LU Name (used on host). We recommend that you use identical names. Network Name of SNA Server machine is filled automatically (default is APPN). Comment is optional.
• Click the Advanced tab. Implicit Incoming Remote LU should be changed from <None> to the Remote APPC LU. Set LU 6.2 Type to Independent.
• Click OK.

Note: This How to document is based on Microsoft SNA server version 4.0. You may find the document useful, even if you have other versions of the SNA server. Refer to the Microsoft SNA server online help for additional information.

Mainframe APPC/LU6.2 wizard

The wizard consists of two parts. In part 1, the wizard will help you collect preliminary information about your host environment. In part 2 it will create an Application Program to Program Communication (APPC) mainframe connection if necessary. It will also create a Remote LU Name, Local LU Name, and Mode.

A link service must be installed on the SNA server service before you can use the Wizard. Refer to Insert Link Service.

Part 1

1. Start the Microsoft SNA Server Manager.
2. On the Tools menu, click Mainframe APPC/LU6.2 Wizard.
3. Click Next, and select Third-party or custom APPC application as the APPC application. Click Next.
4. Select Other or unknown as host environment. Click Next.
5. Select the SNA server service you want to configure. Click Next.
6. Enter new connection name (or select existing). Click Next.
7. Answer Yes or No to if you are connecting through an IBM 3174/3172 controller. Click Next.
8. Select Independent LU6.2 Connection. Click Next.
9. Click Work sheets and print the resulting worksheets in landscape and distribute them to mainframe personnel if necessary. Click Next to continue with part 2 if you have the information ready.

Part 2

1. Enter Network Address. Click Next.
2. Enter Network Name and Local Control Point Name. If you are not connecting through an IBM 3174/3172 controller, then you must also enter Local Node ID (XID or Exchange ID). Click Next.
3. Select Local LU Name or enter a unique name to create a new one. Click Next.
4. Select Remote LU Name or enter a unique name to create a new one. Click Next.
5. Create a new MODE62 mode with 128 as Parallel Session Limit. Click Next.
6. Read the summary and click Finish to complete the configuration.

Additional printers

If you wish to add more printers than the one created by the Mainframe APPC/LU6.2 Wizard, then you must:

1. Insert Local LUs for each additional printer.
2. The mainframe's PSS Printer Profile must contain corresponding printer definitions that include the LUNAME.
3. Add the corresponding Logical Printers in DocOut™ (using the Logical Printer Wizard).
4. DocOut™ settings
5. The Mainframe APPC/LU6.2 Wizard takes the value of the Local LU Name (Part 2, step 3) and reuses it for the LU Alias, thus making them identical. The LU Alias must match the LU 6.2 Alias used in the Logical Printer Wizard and the PrintGuide™ LU 6.2 (APPC) configuration tab.
6. Use IDAPSS as the Transaction Program Name in the Logical Printer Wizard and the PrintGuide™ LU 6.2 (APPC) configuration tab.

Note: This How to document is based on Microsoft SNA Server version 4.0. You may find the document useful, even if you have other versions of the SNA Server. Refer to the Microsoft SNA server online help for additional information.

Mainframe APPC/LU6.2 wizard

The wizard consists of two parts. In part 1, the wizard will help you collect preliminary information about your host environment. In part 2 it will create an Application Program to Program Communication (APPC) mainframe connection if necessary. It will also create a Remote LU Name, Local LU Name, and Mode.

A Link Service must be installed on the SNA Server Service before you can use the Wizard. Refer to Insert Link Service.

Part 1

1. Start the Microsoft SNA Server Manager.
2. On the Tools menu, click Mainframe APPC/LU6.2 Wizard.
3. Click Next, and select Third-party or custom APPC application as the APPC application. Click Next.
4. Select Other or unknown as host environment. Click Next.
5. Select the SNA Server Service you want to configure. Click Next.
6. Enter new connection name (or select existing). Click Next.
7. Answer Yes or No to if you are connecting through an IBM 3174/3172 controller. Click Next.
8. Select Independent LU6.2 Connection. Click Next.
9. Click Work sheets and print the resulting worksheets in landscape and distribute them to mainframe personnel if necessary. Click Next to continue with part 2 if you have the information ready.

Part 2

1. Enter Network Address. Click Next.
2. Enter Network Name and Local Control Point Name. If you are not connecting through an IBM 3174/3172 controller, then you must also enter Local Node ID (XID or Exchange ID). Click Next.
3. Select Local LU Name or enter a unique name to create a new one. Click Next.
4. Select Remote LU Name or enter a unique name to create a new one. Click Next.
5. Create a new MODE62 mode with 128 as Parallel Session Limit. Click Next.
6. Read the summary and click Finish to complete the configuration.

Additional printers

If you wish to add more printers than the one created by the Mainframe APPC/LU6.2 Wizard, then you must:

1. Insert Local LUs for each additional printer.
2. The mainframe's PSF Startup Procedure must contain corresponding printer definitions that include LUNAME.
3. Add the corresponding Logical Printers in DocOut™ (using the Logical Printer Wizard).

DocOut™ settings

1. The Mainframe APPC/LU6.2 Wizard takes the value of the Local LU Name (Part 2, step 3) and reuses it for the LU Alias, thus making them identical. The LU Alias must match the LU 6.2 Alias used in the Logical Printer Wizard and the PrintGuide™ LU 6.2 (APPC) configuration tab.
2. Use $DPF as the Transaction Program Name in the Logical Printer Wizard and the PrintGuide™ LU 6.2 (APPC) configuration tab.

To start the Microsoft SNA server manager

1. Click the Start menu, point to Microsoft SNA Server and click Manager.

The AS/400 parameter names are written in italics and the Microsoft SNA server manager parameter names are written in bold:

Use the Display Network Attributes (DSPNETA) command on the AS/400 to find the correct values for:

• Local Network ID = Network Name
• Local Control Point = Control Point Name and Remote APPC LU

Use the Display Line Description (DSPLIND) command on the AS/400 to find the correct parameter for:

• Local Adapter Address = Network Address (MAC address, e.g. 020000000000)
• XID or Exchange ID = Remote Node ID (e.g. 056 DD973)

AS/400 wizard

The wizard will help you create an AS/400 connection, a Remote APPC LU for the connection, and a Local APPC LU if necessary.

A link service must be installed on the SNA server service before you can use the wizard. Refer to Insert Link Service.

1. Start the Microsoft SNA Server Manager.
2. On the Tools menu, click AS/400 Wizard. Click Next
3. Select the SNA Server machine for which you want to configure the connection to your AS/400. Click Next.
4. Type a Connection Name for your AS/400 connection. The connection is identified by this name in the Connections folder. Click Next.
5. Select an SNA Server Link Service on which to configure the connection to your AS/400. Click Next.
6. Enter Network Name (Local Network ID) and Control Point Name (Local Control Point). The Control Point Name is also used as the name for the Remote APPC LU. Click Next.
7. Enter the Network Address (Local Adapter Address on AS/400). Leave Remote SAP Address and Local SAP Address at their default (04). Click Next.
8. Click Finish to complete the configuration.

Adjust connection properties

1. In the Microsoft SNA Server Manager right-click the connection and click Properties.
2. In the General tab, ensure that Allowed Directions is set to Both Directions.
3. Click System Identification tab. In the Remote Node Name group you must fill in:
   - Network Name (Local Network ID)
   - Control Point Name (Local Control Point)
   - Remote Node ID (XID or Exchange ID)
4. Click OK

Insert APPC mode definition

Since the Microsoft SNA server does not include the QSPWTR mode needed for LU 6.2 - IPDS printing, you must create it. See Insert APPC Mode Definition.

Add printer

• Insert Local LU for the printer.
• Add Printer on AS/400.
• Add the corresponding logical printer in DocOut (using the Logical Printer Wizard).

DocOut settings

• The AS/400 wizard takes the value of the Local LU Name and reuses it for the LU Alias, thus making them identical. The LU Alias must match the LU 6.2 Alias used in the Logical Printer Wizard and the PrintGuide™ LU 6.2

(APPC) configuration tab.

• Use $DPF as the Transaction Program Name in the Logical Printer Wizard and in the PrintGuide™ LU 6.2 (APPC) configuration tab.

Note: This How to document is based on Microsoft SNA Server version 4.0. However, you may find the document useful, even if you have other versions of the SNA server. Refer to the Microsoft SNA server online help for additional information.

3270 wizard

The 3270 wizard will help you collect preliminary information about your host environment and it will create a 3270 mainframe connection if necessary.

A link service must be installed on the SNA server service before you can use the Wizard. Refer to Insert Link Service.

Adding a 3270 connection

1. Start the Microsoft SNA Server Manager.
2. On the Tools menu, click 3270 Wizard.
3. Click Next, and select a SNA Server machine for the connection. Click Next.
4. Enter the name of your connection. Click Next.
5. Select the SNA Server Link Service you want to use. Click Next.
6. Enter the Local Node ID of the SNA Server. Click Next.
7. Enter the Network Address, Remote SAP and Local SAP Address. Click Next.
8. Enter the LU Information and click Next.
9. Select the Access Rights for your mainframe. Click Next and click Finish.

Adding application LU

1. Right click the appropriate 3270 connection in the left pane of the Microsoft SNA Server Manager and select Insert, 3270 and Application LU (LUA).
2. Enter the general properties of the application LU and click OK.

DocOut™ comes with five IBM font sets: 3812, 3816, 4028, IP40 and 4247(matrix). In PrintGuide™ there is a one to one correspondence between the emulation selection and the font set.

However, it is possible to override the binding between emulation (3812, 3816, 4028, IP40 and 4247) by changing the contents of the DocOut™ font directories (RES3812, RES3816, RES4028, RESIP40 and RES4247) or by going through the following steps:In PrintGuide™; Upload the configuration from the DocOut™ PrintServer.

1. In PrintGuide™; Upload the configuration from the DocOut™ PrintServer.
2. Record the name of the logical printer. You will need the name or description when you edit the configuration file. If the name is not already unique, you should double-click the logical printer and edit its description to make it unique.
3. On the File menu, click Save As to save the configuration to a file (*.cf2).
4. Open the file (*.cf2) in Notepad or another editor.
5. In Notepad; Search for the name of the logical printer you recorded earlier. Scroll down to the first occurrence of "TRANSFORM_SEL IPDS". Record the ID (12).
6. Search for the text "IPDS 12" where 12 is the ID you recorded before.
7. Scroll down to the first occurrence of "RESOURCEPATH". Change the value to the directory you want to use. The values include; "RES3812", "RES3816", and "RES4028".
8. On the File menu, click Save to save the configuration to a file (*.cf2).
9. In PrintGuide; On the PrintServer menu, click Update Configuration to download the modified configuration file (*.cf2).

Use PrintGuide™ to backup your DocOut™ configuration

1. Start PrintGuide™
2. In Monitor View, locate the DocOut™ PrintServer in the list of Detected Devices and click it.
3. On the PrintServer menu, click Backup Configuration.
4. Then open the DocOut.upd with an editor e.g. Notepad. Default the DocOut.upd file is saved in
   C:\Program Files\MPI Tech\PrintGuide.
5. Then find the session number used to print "AFP/IPDS (PSF) using TCP/IP in this example PPD 5001 as input using SESSION 2 and change the "SESS_MEMORY" from 2048 to 16000 or more.
   
   SESSION 2
   
   DESCRIPTION "AFP/IPDS (PSF) using TCP/IP"
   
   SESS_MEMORY 16000
   
   PRESENT YES
   
   TPG_DISP YES
   
   INPUT_DEF
   
   INPUT_SEL PPD
   
   ID 1
   
   END_SET
   
   TRANSFORM_DEF 1
   
   TRANSFORM_SEL IPDS
   
   ID 1
   
   END_SET
   
   TRANSFORM_DEF 2
   
   TRANSFORM_SEL ICDS
   
   ID 1
   
   END_SET
   
   OUTPUT_DEF
   
   OUTPUT_SEL PRINTER
   
   ID 1
   
   END_SET
   
   END_SET
6. Then save the DocOut.upd file.
7. In Monitor View, locate the DocOut™ PrintServer in the list of Detected Devices and click it.
8. On the PrintServer menu, click Update Configuration and open the DocOut.upd file just changed.
9. Click OK to confirm, remembering to check Restart PrintServer after download. The PrintServer merges the edited *.upd file with its current configuration.

Use PrintGuide™ to backup your DocOut™ configuration.

1. Start PringGuide™
2. In Monitor View, locate the DocOut™ PrintServer in the list of Detected Devices and click it.
3. On the PrintServer menu, click Backup Configuration.
4. Then open the DocOut.upd with an editor e.g. Notepad. Default the DocOut.upd file is saved in
   C:\Program Files\MPI Tech\PrintGuide™.
5. If PCL: Then find the session number used to print "AFP/IPDS (PSF) using TCP/IP in this example PPD 5001 as input using PRINTER 1 and change under LANGUAGE_DEF PCL5e the "AVALIMEMORY" from 1024 to 4096 or more.
   
   LANGUAGE_DEF PCL5
   
   PRESENT YES
   
   AVAILMEMORY 4096
   
   OFFSETREG YES
   
   HPGL YES
   
   GMACROS YES
   
   RASTEROP YES
   
   PATTERNS YES
   
   CTABLES NO
   
   If PostScript: Then find the session number used to print "AFP/IPDS (PSF) using TCP/IP in this example PPD 5001 as input using PRINTER 1 and change under LANGUAGE_DEF PostScript the "AVAILMEMORY" from 1500 to 4096 or more.
   
   LANGUAGE_DEF POSTSCRIPT
   
   PRESENT YES
   
   AVAILMEMORY 4096
6. Then save the DocOut.upd file.
7. In Monitor View, locate the DocOut™ PrintServer in the list of Detected Devices and click it.
8. On the PrintServer menu, click Update Configuration and open the DocOut.upd file just changed.
9. Click OK to confirm, remembering to check Restart PrintServer after download. The PrintServer merges the edited *.upd file with its current configuration.

Adding a 3270 connection

Note: You can ignore this part of the procedure if you have a 3270 mainframe connection already.

1. Start the Microsoft SNA Server Manager.
2. On the Tools menu, click 3270 Wizard. The 3270 wizard will help you collect preliminary information about your host environment and it will create a 3270 mainframe connection, if necessary. A Link Service must be installed on the SNA Server Service before you can use the Wizard. Refer to Insert Link Service.
3. Click Next, and select a SNA Server machine for the connection. Click Next.
4. Enter the name of your connection. Click Next.
5. Select the SNA Server Link Service you want to use. Click Next.
6. Enter the Local Node ID of the SNA Server. Click Next.
7. Enter the Network Address, Remote SAP and Local SAP Address. Click Next.
8. Enter the LU Information and click Next.
9. Select the Access Rights for your mainframe. Click Next and click Finish.

Adding and assigning an application LU

1. Start the Microsoft SNA Server Manager.
2. Right-click the mainframe connection you intend to use and select Insert, 3270, Application LU (LUA). The 3270 LU Properties dialog is displayed.
3. Enter the LU Number and LU Name. Click OK
4. In the LU Name list (on the right-hand side), right-click the LU Name you just created, select Assign To, TN3270 Service On, <Name of the computer you want to use>.
5. Highlight the TN3270 Service in the list on the left-hand side. The LU you created is shown in the list of LUs assigned to TN3270 Server.
6. Right-click the new LU Name in the list (right hand-side), select Properties, TN3270 tab.
7. Select the Type as Specific Printer.
8. Under Terminal Names, check IBM-3287-1.
9. Click OK.

Configuring the PrintServer using PrintGuide™

1. Start PrintGuide™.
2. In Configuration View for the selected DocOut PrintServer, locate the SCS using TN3270e logical printer.
3. Right-click on it in the list and select Edit Logical Printer.
4. Select the Telnet Print tab.
5. Enter the LUName. This will be the printer's name on the mainframe. It must unique and must have 10 characters or less.
6. Enter the mainframe's IP address in Host IP Address. Note: The Host Port is default set to 23. This is the standard, pre-defined Telnet port and it is most unlikely that you will need to change it.
7. Click OK.
8. Select Save Configuration, remembering to check Restart PrintServer after download in the Confirm dialog.

CRTDEVAPPC - Create an APPC device description

CRTDEVPRT - Create a printer description

CHGCFGL - Change configuration list

It is recommended to add an entry for each printer in the APPN Remote Configuration List. Type:

CHGCFGL TYPE (*APPNRMT) CFGL(QAPPNRMT)

If you do not have a Remote Configuration List, you can use the CRTCFGL command to create one.

The DocOut™ product has support for Euro Currency from S82 061.050.

This problem can be solved by un-clicking Use Greek Text Below 6 Pixels in the Acrobat reader. You find the setting in Acrobat Reader under File Preferences and General Parameters. The changed setting in Acrobat Reader does not influence any other PDF files.

On AS/400 V4R4 or higher, a new parameter has been implemented in the PSFCFG called Automatic Session Recovery. Change Automatic Session Recovery to *YES to solve the problem with the writer ending.

The Release Timer in the PSF configuration (Inactivity timer in ver 3.1 WRKAFP2 configuration) must be set to a value other than *NOMAX (*SEC15 or *SEC30 recommended). The default is *NOMAX. This will ensure that the system releases its session with the interface when printing has been completed.

When installing DocOut™ on a Windows server I get the error:

Application error

Exception EAccessViolation in module sesswiz.exe at 0007AD9. Access violation at address 00407AD9 in module 'sesswiz.exe'. Read of address 73736553.
There is not defined any printer on the Windows server.

To install a printer:

1. Click Start, Settings, Printers and Add printer and follow the instructions.
2. Install DocOut™ again

Probably there is either a syntax error in the list of Spool Options or the total length of spool options with expanded spool option parameters exceeds 255 characters.

Option 1:

Starting DocOut results in an error code 1069 and DocOut remains stopped. When operating Windows XP, Server 2003 and Server 2008 requires that the Windows Firewall Service / Internet Connection Sharing (ICS) is running. The Firewall may be set to ‘Off’ or ‘On’. If set to ‘On’ both DocOut and PrintGuide must be listed and enabled in the list of Exceptions

Option 2:

If you assign a logon account to the DocOut™ service and the DocOut™ service will not start (you will see an error code 1069), it might be the selected logon account that has no rights to log on as a service. To fix this you have to change your user rights policy.
Note: Please consult your IT Administrator to obtain the required authorisation for the logon account (user) selected.

Follow these steps to restore the DocOut™ configuration:

Step 1: Back-up the configuration

• Start the PrintGuide™ program.
• Locate the DocOut™ on the list of Detected Devices and select this.
• On the Actions menu, locate: PrintServer - Backup Configuration.
• Save the .upd to file.

The configuration is now backed up.

Step 2: Restore the configuration using the back-up

• Stop DocOut™.
• Delete 'CFG' directory and 'Factory.cf2' file from the DocOut Installation directory. In a typical English installation, You will find DocOut™ in 'C:\Program Files\MPI Tech\DocOut'.
• Start DocOut™.
• In PrintGuide™; Locate the DocOut™ on the list of Detected Devices and select this.
• On the Actions menu, locate: PrintServer - Update Configuration.
• Click Files of type, and select PrintServer Configuration File (*.cf2;*.upd). Double-click the backup file (*.upd). A confirmation dialog is displayed.
• Click OK to download the configuration to the DocOut™.

The configuration is now restored.

The mainframe's PSS Printer Profile must contain a printer definition that includes IP, PORT, and PRTID.

1. IP should be set to the IP address of the Server system where DocOut™ is installed.
2. PORT holds the value of the TCP/IP port number, and should match the one specified in the Logical Printer Wizard and the PrintGuide™ PPD configuration tab. The range of PORT is 5005 - 5009.
3. PRTID should match Printer ID in the Logical Printer Wizard and the PrintGuide™ PPD configuration tab.

Products Involved

• MPI Tech BlueServer
• MPI Tech DocOut
• MPI Tech PrintGuide all versions
• Microsoft Windows XP with Service Pack 2
• Microsoft Windows Server 2003 with Service Pack 1

Introduction

This document describes how to be prevent the built in Firewall in Windows XP SP2 and Windows 2003 Server SP1 from blocking MPI Tech BlueServer, DocOut and PrintGuide. By default the Firewall is enabled when installing SP2 to Windows XP but disabled when installing SP1 on Windows 2003 server. On both Windows XP and 2003 the firewall should be configured no matter if it’s enabled or not. This is to ensure that the MPI Tech related software is working correctly.

How to setup the firewall

1. The firewall is located in the Control Panel and is named Windows Firewall.
2. Opening Windows Firewall displays if the firewall is turned on or not, MPI Tech advices to add the MPI Tech related software, even if the firewall is turned OFF.
3. Open the exceptions menu. In this menu you will probably see several exceptions added.
4. You can add both port numbers and software to the exceptions, MPI Tech advises to add the *.exe file of the software, then all used ports by the software is added to the exceptions. This is done using the Add Program wizard. The files to add are: BlueServer = Blueserv.exe DocOut = Pserver.exe PrintGuide = PGuide.exe. The exe files are located in the folder where the application is installed.

The IPDS DIMM may have reported an error while receiving data. Check for messages relating to the printer in the host error log.

One possible error might be that the memory capacity of the printer is not sufficient. (Especially when it comes to duplex printing).

Another possibility is that the IPDS EMULATION is not set correctly.

There are two different font sets depending on the IBM IPDS printer emulated. In order to change the IPDS printer emulation, click Printer Configuration, “IPDS MENU”, “IPDS EMULATION” Parameter.

Allowed values are:

• 3812 (240 DPI host resources)
• 4028 (300 DPI host resources)

The IBM emulation is incorrect. If 4028 is selected, it must be changed to 3812/3816. If 3812/3816 is selected, it must be changed to 4028.

Make sure that the host configuration printer IP address is correct and that the IP Port is set to 9100.

(Mainframe PSF configuration “IPPORT”=9100, AS/400 configuration “PORT Number”=9100).

Make sure that you can ping the printer from the IBM host.

You haven't drained the printer (Mainframe) or varied the device (AS/400) off and on. Also, power the device off and on again.

This problem may occur when communication with the host takes place over TCP/IP.

• The host must release the TCP/IP communication after each job (to allow printing from other systems):
• Mainframe environment: Check the DISCINTV parameter in the PSF configuration. Set it to 15
• AS/400 environment: Configuration varies depending on the AS/400 release. Refer to your “DIMM Installation and User’s Guide” manual. Generally in PSF configuration, set the “RLSTMR” = *SEC15
• The printer must not release the TCP/IP communication before the last page has been printed.
• From the printer front panel, set the JetDirect TCP/IP “IDLE TIMEOUT” parameter to 3600 or 0

This situation might occur when communication with the host is over TCP/IP with HP JetDirect print servers. You must configure the JetDirect card according to its model and the firmware release.
With HP LaserJet HP4000/4050/8000/8100/8150:

1. Open a Telnet communication with the JetDirect print server.
2. Type “buffer-packing: off” + (enter) With HP4100 (J4169A Version L.21.11)
3. Open a Telnet communication with the JetDirect print server.
4. Type: menu (enter)
5. Select option: 2 (TCP/IP Menu) + (enter)
6. Select option: 2 (TCP/IP - Print Options)
7. Set buffer Packing: Enabled
8. Save the settings.

When re-mapping the input paper sources via the tray definitions on IPDS interfaces, it is often necessary to disable the Auto-Configure function. This will prevent the interface from changing the user settings when re-booted.

If you are certain that the printer has a duplexer installed, then the problem might be:

The interface IPDS configuration does not have duplex enabled
Or, in the case of a Twinax attached device,

The Advanced Function Printing parameter in the device description is set to *NO and the interface is not set up to emulate a 3816. With the AFP parameter set to *NO, duplex printing is only possible in 3816 emulation. If set to *YES, duplex can be obtained in all of the IPDS emulations.
 

The Release Timer in the PSF configuration (Inactivity timer in ver 3.1 WRKAFP2 configuration) must be set to a value other than *NOMAX (*SEC15 or *SEC30 recommended). The default is *NOMAX. This will ensure that the system releases its session with the interface when printing has been completed.

Use Telnet or check the settings printout from the LinkCom™.

It is the MAC address of the nearest upstream controller.

This may be because you have not assigned a unique Local Address for each of the Logical Printers/ports. Follow the steps below to specify the Local Address.

Start PrintGuide™.

1. Locate the PrintServer on the list of Detected Devices and double-click it.
2. Locate and double-click the Logical Printer that match your requirements in terms of both SNA print and printer (output).
3. In the SNA Print panel specify a Local Address that match the address used on the host. Click OK.
4. Repeat step 3. and 4. for each of the Logical Printers you wish to use.
5. On the PrintServer menu, click Save Configuration.

Move the PrintServer to EIO Slot 2 and then it is working.

LinkCom III:

Ensure that the setting of the LinkCom III output language match the target printer.

If the target printer is configured to Epson LQ emulation, this must be reflected by a setting in the output language of Epson LQ from LinkCom III.

LinkCom Xpress:

Ensure the correct printer driver is loaded on the LinkCom™. Four drivers are provided on the CD with the product or available on the web site. These are:

• Mainframe Host => PCL output
• Mainframe Host => EPSON/PRO-PRINTER output
• AS/400 Host => PCL output
• AS/400 Host => EPSON/PRO-PRINTER output.

You have to restart the LinkCom after downloading a new version of the Firmware.

The valid range for Local MAC adresses in Host2Net Ethernet, LinkCom 10/100 and LinkCom Xpress 10/100 products.

Factory default for Local MAC is:
0200 0000 0000

Valid range for Local MAC:
x2xx xxxx xxxx

x6xx xxxx xxxx

xAxx xxxx xxxx

xExx xxxx xxxx

Where x can be defined from 0 to F.

This can have one of two reasons:

1. You are probably not taking the canonical MAC address into account. Make sure that the remote MAC address is set up with the reverse MAC address.
2. Your routers are set up with a MAC address filter and the universal MAC address on the LinkCom™ (00036exxxx) is not within those limits. Change via Telnet, PrintGuide™, or web browser, from using the universal MAC address to the local MAC address 400012345678.

Yes, it is possible to have different IPDS configurations for two ( up to three ) printers attached to a LinkCom™, but only one IPDS font set can be loaded which the two definitions will share. Note, the active IPDS printer sessions will equally share the available memory of the LinkCom product.

The DocOut™ product has support for Euro Currency from S82 061.050.

The error is reported for any one of the following reasons:

• It is the first time ever you are trying to change the password. You must leave the Old Password blank (empty).
• The Old Password does not match. Try with adm or a blank (empty).
• You failed to type exactly the same in New Password and Verify Password. Please retype.

The Telnet configuration method in the EasyCom™ and LinkCom™ is for MPI Tech internal use only. Use web browser or PrintGuide™ to change the configuration.

You probably did not allow enough time for the PrintServer to auto-configure with the printer and the PrintServer is choking (Sometimes, this could even result in an "Awaiting microcode download" printout).

Wait for 30-60 seconds, then press the test button. Also, make sure that the printer is on-line and ready before powering on the PrintServer.

Initial discovery
PrintServers without a previously configured IP address can be discovered in Web JetAdmin via IPX and subsequently configured with an IP address, subnet mask, and gateway.

Web JetAdmin requires that the Novell NetWare protocol be installed on the server, in order for this feature to function.

Configuration via Web JetAdmin

The Web JetAdmin support includes:

• Configuration of TCP/IP.
• Configuration of IPX/SPX (NetWare).
• Enable protocols.
• Print path creation.
• You can set/change the PrintServer's password via Web JetAdmin's Device Password. The maximum length of the password is 9 characters.
• Diagnostics.
• Access to the PrintServer's web pages via Web JetAdmin's Device Server button.

Compatibility

Since Web JetAdmin was developed by HP for HP JetDirect PrintServers, there are some parameters that are named differently in the PrintServer, or are not supported by the PrintServer. This is described below:

• The PrintServer does not support the Upgrade Firmware button in Web JetAdmin.
• The Serial Number of printer appears in Web JetAdmin, but it is blank.
• Error Behaviour is presented as unknown.
• No support for DLC/LLC printing.
• The PrintServer's IPX/SPX Frame Type option Auto is mapped to Web JetAdmin's Frame Type option All.
• The PrintServer's Share Timer is mapped to Web JetAdmin's TCP/IP Idle Timeout.

Note: Since the Xpress PrintServers do not support JetSend, no JetSend parameters will appear in Web JetAdmin.

Yes, you need to execute the following command to do so:

route -p add xxx.xxx.xxx.xxx mask 255.255.yyy.yyy zzz.zzz.zzz.zzz metric 1

Where xxx.xxx.xxx.xxx = the IP-address of the router you are trying to access and zzz.zzz.zzz.zzz = the IP-address of the router you are on. Furthermore, if you need to make this a permanent solution, you can add /p at the end of the command line.

You probably used this IP address on another device, and your arp table has not been refreshed to reflect the new MAC address that the IP address is matched to. (This may happen if you are replacing a Jet Direct type device with a LinkCom™ or other LAN type devices).

Either

Press and hold the test button down for approx. 8 seconds while the print server is on. When all LEDs are blinking, release the Test botton and allow time for restart of the print server.

Or

Use PrintGuide as follows:

• Locate and select the actual print server.

• In the actions menu locate: PrintServer - Restore Factory Defaults ...

Or

Use the web browser to enter the 'Advanced Configuration' pages and choose 'Restore Factory Default Configuration'.

NOTE:

Any user defined password will remain unchanged after a restoring of factory settings.

The following Control Units are supported:

• IBM /34
• IBM /36, all models
• IBM /38, all models
• IBM AS/400
• IBM 5294 and 5394 remote controllers

You must set Function 10 to 1 (Landscape) using the following command:

• %Y10,1%

In LU1 mode the CPI & the LPI can be sent from the host. Take an on-line hex dump to see if 2B commands are being issued. If they are, you must have the programmer turn them off or have the person responsible for VTAM set the printer to LU3 mode.

HostCom™ Cx

You must set Function 10 to 2 (COR - Computer Output Reduction) using the following command:

• %Y10,2%

HostCom™ Tx

Make sure that Function 98 is set to 0 (Enable APO, Automatic Page Orientation):

• %Y10,2%

If this does not activate COR printing you must set function 10 to 82.

• %Y10,82%

Which will enable COR as on IBM 3812, but independent of the PPM print quality parameter.

This is usually a wiring problem. If you are using twisted pair cables, there is a possibility that the polarity is reversed. Or the balons may have to much resistance. If you are using a pure Twinax cable, the connectors may be loose.

In order to print 15 CPI the printer needs to know the "ESC g" command (not the "ESC G" command).

Most of the matrix printers with Epson FX emulation know this command
( IBM 6400 and OKI 590 know the "ESC g" command ).

The 15 CPI is created using 'Variable Character Spacing'.

If you do not know if the matrix printer you are using supports the "ESC g" command you have to make a test or look in the printer manual to see if "ESC g" is supported in the Epson FX emulation on your printer.

You must do the following:

• Stop VPS-PCL on the printer
• Send this command to the converter: &&??%%Y37,4%%X1
• Turn VPS-PCL back on.

One reason could be that auto configure was used by the AS/400 and the device was configured as a 5219 instead of a 3812 Model 1. 

You should print the LaserJet self test : “INFORMATION MENU” , “PRINT CONFIGURATION”. The configuration page is then printed.

Check in the “Installed personalities and options” paragraph that the “MPIPDS” personality is installed.

PrintGuide™ supports the following PrintServers:

• DocOut™
• EasyCom™ III
• LinkCom™ IV
• LinkCom III S
• LinkCom III S EIO
• HostCom IV Coax / Twinax
• LanBrick IV Coax / Twinax

and the following old print servers:

• EasyCom™ Xpress series
• LinkCom™ Xpress/III series
• Host2Net™
• PlusCom™ series