Blueserver Operators Guide

THE BLUE SERVER V7
No. D10574-002
AFP/IPDS/SCS emulation
Mainframe & AS/400 to LAN printer
for Microsoft® Windows and
SUN Solaris AIX and LINUX
Operator‟s Guide
Reference : Blue Server V7

Date : September 9, 2009
Rev : D10574-002
About MPI Tech
The MPI Tech Group is a leading manufacturer of printing solutions for IBM systems.
All products are developed and produced by MPI Tech and sold through MPI Tech sales offices or authorized
dealers around the world.
MPI Tech partakes in various international committees to further spread its know-how and define the future of
digital printing (Members of the “AFP Color Consortium”).
Copyrights:
®
IBM, Microsoft , Hewlett Packard, products mentioned are trademarks of their respective owners.
All other products mentioned are trademarks of their respective owners.
 Copyright MPI Tech 1981 - 2009. All rights reserved.
http://www.mpitech.com
MPI TECH (France) MPI TECH (North America)

Corporate Headquarters  +1 714 840 8077 (west coast)
E-mail techsup@mpitech.com
40, rue du Général Malleret Joinville
94400 Vitry sur Seine – France
 +1 703 243 3322 (East coast)
 + 33 1 45 73 09 40
E-mail support.us@mpitech.com
Fax + 33 1 46 80 70 71
E-mail support.fr@mpitech.com
MPI TECH (Germany) MPI TECH (UK) MPI TECH (Denmark)

 49 (0) 89 35 4762 -30  + 44 (0) 1344 891 008  + 45 4436 6000
E-mail support.de@mpitech.com E-mail support.uk@mpitech.com E-mail support.dk@mpitech.com
2 The Blue Server V7

CONTENTS
1. MPI TECH. LOCATION & TECHNICAL SUPPORT .............................................................................................................. 11
2. HOW TO START BLUE SERVER INTERFACE .................................................................................................................... 13
®
2.1. MICROSOFT BLUE SERVER MAIN MENU ............................................................................................................................... 13
2.2. SUN SOLARIS, AIX AND LINUX BLUE SERVER MAIN MENU ....................................................................................................... 14
2.3. BLUE SERVER INTERFACE ORGANIZATION................................................................................................................................ 15
2.3.1. Main task bar ....................................................................................................................................................... 15
2.3.1.1. Icon list ................................................................................................................................................................................ 15
2.3.1.2. Tabs list ............................................................................................................................................................................... 17
3. IBM HOST CONFIGURATION FOR PARSER SESSION ...................................................................................................... 19
3.1. PSF/400 AFP PRINTING USING TCP/IP ............................................................................................................................... 19
3.1.1. TCP/IP With AS/400 V3R1..................................................................................................................................... 19
3.1.1.1. Creating The AS/400 Printer Device .................................................................................................................................... 19
3.1.1.2. Creating The WRKAFP2 Command On Your AS/400 (V3R1)................................................................................................ 19
3.1.1.3. Using The WRKAFP2 Command For The Blue Server .......................................................................................................... 20
3.1.2. TCP/IP With AS/400 V3R2..................................................................................................................................... 21
3.1.2.2. The CRTPSFCFG Command Parameters .............................................................................................................................. 21
3.1.3. TCP/IP With AS/400 V3R6..................................................................................................................................... 22
3.1.3.2. Creating the WRKAFP2 command on your AS/400 V3R6 .................................................................................................... 22
3.1.3.3. Using The WRKAFP2 Command For The Blue Server .......................................................................................................... 23
3.1.4. TCP/IP With AS/400 V3R7..................................................................................................................................... 24
3.1.4.1. Using the CRTPSFCFG command for with the Blue Server .................................................................................................. 24
3.1.4.2. Creating the AS/400 printer device ..................................................................................................................................... 25
3.1.5. TCP/IP With AS/400 V4R1 and V4R2 .................................................................................................................... 26
3.1.6. TCP/IP With AS/400 V4R3 , V4R4, V4R5, V5R1, V5R2, V5R3, V5R4 and V5R5 ..................................................... 28
3.2. PSF/MVS AFP PRINTING USING TCP/IP ............................................................................................................................. 30
3.2.1. PSF/VM Configuration .......................................................................................................................................... 30
3.2.1.1. Software Prerequisites ........................................................................................................................................................ 30
3.2.1.2. Defining the Printer to PSF .................................................................................................................................................. 30
4. IBM HOST CONFIGURATION FOR ROUTER SCS 5250 SESSION ....................................................................................... 33

4.1. AS/400 SCS-DCA PRINTING USING TCP/IP LPR/LPD........................................................................................................... 33
4.1.1. Create a remote output queue ............................................................................................................................. 33
4.1.2. AS/400 printing ..................................................................................................................................................... 34
5. IBM HOST CONFIGURATION FOR ROUTER SCS 3270 SESSION ....................................................................................... 35
5.1. SETUP MAINFRAME SNA ENVIRONMENT ............................................................................................................................... 35
5.1.1. How to Define Host VTAM PU and LUs ................................................................................................................. 35
5.1.1.1. EXAMPLE : Token ring VTAM/NCP File for a Node type 2.0 Connection ............................................................................. 36
5.1.1.2. NT Server - Network protocol configuration ....................................................................................................................... 37
6. IBM HOST CONFIGURATION FOR TN3270/TN5250 ....................................................................................................... 43

6.1. TN3270 SETUP ................................................................................................................................................................ 43
6.1.1. Description ............................................................................................................................................................ 43
6.1.2. Telnet 3270 connectivity ....................................................................................................................................... 44
6.1.3. VTAM Configuration ............................................................................................................................................. 45
6.1.3.1. Sample of major node definition (only printers) ................................................................................................................. 45
6.1.4. Configuration TCP/IP ............................................................................................................................................ 46
6.1.4.1. TCP-IP Telnet configuration ................................................................................................................................................ 46
6.1.4.2. Sample ................................................................................................................................................................................ 47
6.2. TN5250 SETUP ................................................................................................................................................................ 49
6.2.1. Autoconfiguration of Devices ............................................................................................................................... 49
7. HOW TO CONFIGURE PARSER SESSION - IPDS CONNECTION ........................................................................................ 51
The Blue Server V7 3

7.1. THE MPI PARSER MAIN MENU............................................................................................................................................ 51
7.2. CREATING A NEW PRINTER CONFIGURATION .......................................................................................................................... 52
7.2.1. Parser - Information window ................................................................................................................................ 53
7.2.1.1. Profile Name ....................................................................................................................................................................... 53
7.2.1.2. Printer Group ...................................................................................................................................................................... 53
7.2.1.3. Comments ........................................................................................................................................................................... 53
7.2.2. Parser - Host window............................................................................................................................................ 54
7.2.2.1. Input Data Stream ............................................................................................................................................................... 54
7.2.2.2. Connection .......................................................................................................................................................................... 55
7.2.2.3. IP Port ................................................................................................................................................................................. 55
7.2.2.4. Printer Emulation ................................................................................................................................................................ 55
7.2.2.5. IBM Resolution .................................................................................................................................................................... 55
7.2.2.6. License Group ..................................................................................................................................................................... 56
7.2.2.7. Color license ........................................................................................................................................................................ 56
7.2.2.8. Input Speed in ppm ............................................................................................................................................................. 56
7.2.2.9. Code Page Version .............................................................................................................................................................. 56
7.2.2.10. Default FGID ................................................................................................................................................................... 57
7.2.2.11. Default CPI ...................................................................................................................................................................... 57
7.2.2.12. Page Format ................................................................................................................................................................... 57
7.2.2.13. Early print complete ....................................................................................................................................................... 57
7.2.2.14. Block Char Error (or Null Suppress) ................................................................................................................................ 57
7.2.2.15. Code Page ....................................................................................................................................................................... 58
7.2.2.16. Report Position Error ...................................................................................................................................................... 59
7.2.2.17. Graphic Overlay .............................................................................................................................................................. 59
7.2.2.18. Free Type Rasterizer ....................................................................................................................................................... 59
7.2.2.19. Active String Indexer....................................................................................................................................................... 59
7.2.2.20. Share IPDS with other session ........................................................................................................................................ 59
7.2.3. Parser – Destination window ................................................................................................................................ 60
7.2.3.1. Output Language................................................................................................................................................................. 62
7.2.3.2. PPD file ................................................................................................................................................................................ 62
7.2.3.3. Using Virtual Child ............................................................................................................................................................... 62
7.2.3.4. Output Resolution ............................................................................................................................................................... 62
7.2.3.5. Destination Type ................................................................................................................................................................. 63
7.2.3.6. PJL Support ......................................................................................................................................................................... 63
7.2.3.7. SNMP Support ..................................................................................................................................................................... 63
7.2.3.8. Printer IP Address ............................................................................................................................................................... 64
7.2.3.9. Printer IP Port ..................................................................................................................................................................... 64
7.2.3.10. Windows Queue ............................................................................................................................................................. 64
7.2.3.11. Split Document ............................................................................................................................................................... 65
7.2.3.12. LPD Queue Name............................................................................................................................................................ 65
7.2.3.13. Print to file ...................................................................................................................................................................... 65
7.2.3.14. Page Configuration ......................................................................................................................................................... 65
7.2.3.15. Text as graphic ................................................................................................................................................................ 65
7.2.3.16. Data Extraction ............................................................................................................................................................... 65
7.2.3.17. Start string ...................................................................................................................................................................... 66
7.2.3.18. Stop String ...................................................................................................................................................................... 66
7.2.3.19. Embed fonts ................................................................................................................................................................... 66
7.2.4. Parser - Input trays window .................................................................................................................................. 66
7.2.4.1. AFP Tray .............................................................................................................................................................................. 66
7.2.4.2. Printer Tray ......................................................................................................................................................................... 67
7.2.4.3. Duplex Tray ......................................................................................................................................................................... 68
7.2.4.4. Rotation .............................................................................................................................................................................. 68
7.2.4.5. Edge to Edge Support .......................................................................................................................................................... 68
7.2.4.6. Suplex .................................................................................................................................................................................. 68
7.2.4.7. Paper Size ............................................................................................................................................................................ 68
7.2.4.8. Paper Length ....................................................................................................................................................................... 69
7.2.4.9. Page Width .......................................................................................................................................................................... 69
7.2.4.10. Physical Margin............................................................................................................................................................... 69
7.2.4.11. Escape Sequence ............................................................................................................................................................ 70
7.2.4.12. Tray Offset ...................................................................................................................................................................... 70
7.2.4.13. Front Left Offset ............................................................................................................................................................. 70
7.2.4.14. Front Top Offset ............................................................................................................................................................. 70
7.2.4.15. Back Left Offset .............................................................................................................................................................. 71
7.2.4.16. Back Top Offset............................................................................................................................................................... 71
7.2.4.17. Horizontal Compression ................................................................................................................................................. 71
7.2.4.18. Vertical Compression ...................................................................................................................................................... 71
7.2.4.19. Scale Ratio ...................................................................................................................................................................... 71
7.2.4.20. Duplex Support ............................................................................................................................................................... 71
7.2.4.21. Nup Support ................................................................................................................................................................... 71
7.2.5. Parser - Output trays window ............................................................................................................................... 72
7.2.5.1. AFP Tray .............................................................................................................................................................................. 72
7.2.5.2. Printer Tray ......................................................................................................................................................................... 72
7.2.5.3. Stapling Mode ..................................................................................................................................................................... 72
7.2.5.4. Punching Mode ................................................................................................................................................................... 72
7.2.5.5. Split on Stapling .................................................................................................................................................................. 72
7.2.5.6. Split on Punching ................................................................................................................................................................ 72
7.2.6. Parser - Utilities window ....................................................................................................................................... 73
7.2.6.1. Trace Option ....................................................................................................................................................................... 73
7.2.6.2. Job Header file .................................................................................................................................................................... 73
7.2.6.3. Job Trailer file ...................................................................................................................................................................... 73
7.2.6.4. Job Automate ...................................................................................................................................................................... 73
7.2.6.5. Job Name ............................................................................................................................................................................ 74
7.2.6.6. Windows Command ............................................................................................................................................................ 91
7.2.7. Parser - Color window........................................................................................................................................... 92
7.2.7.1. Color Palette ....................................................................................................................................................................... 92
7.2.8. Parser - Mail window ............................................................................................................................................ 93
7.2.8.1. Outgoing mail server (SMTP) .............................................................................................................................................. 93
7.2.8.2. Email Service ....................................................................................................................................................................... 93
7.2.8.3. Email Sender ....................................................................................................................................................................... 93
7.2.8.4. Email Destination ................................................................................................................................................................ 93
7.2.8.5. Bcc Mail Address ................................................................................................................................................................. 93
7.2.8.6. Subject ................................................................................................................................................................................ 93
7.2.8.7. Message .............................................................................................................................................................................. 93
7.2.9. Parser - PDF window ............................................................................................................................................. 94
7.2.9.1. Encryption Level .................................................................................................................................................................. 95
7.2.9.2. Permanent editing lock ....................................................................................................................................................... 95
7.2.9.3. Administrator Password...................................................................................................................................................... 95
7.2.9.4. User Password .................................................................................................................................................................... 95
7.2.9.5. Printing allowed .................................................................................................................................................................. 95
7.2.9.6. Changes allowed ................................................................................................................................................................. 95
7.2.9.7. Enable copying of content .................................................................................................................................................. 95
8. ROUTER AS/400 LPD-SCS .............................................................................................................................................. 97

8.1. MPI ROUTER FUNCTIONS.................................................................................................................................................... 97
8.2. CREATING A NEW PRINTER CONFIGURATION .......................................................................................................................... 98
8.2.1. Router LPD/SCS - information window ................................................................................................................. 99
8.2.1.1. Profile Name ..................................................................................................................................................................... 100
8.2.1.2. Printer Group .................................................................................................................................................................... 100
8.2.1.3. Comments ......................................................................................................................................................................... 100
8.2.2. Router LPD/SCS - connection window ................................................................................................................ 100
8.2.2.1. LPD Queue Name .............................................................................................................................................................. 100
8.2.2.2. Destination Type ............................................................................................................................................................... 100
8.2.2.3. Printer IP Address ............................................................................................................................................................. 101
8.2.2.4. IP Port ............................................................................................................................................................................... 101
8.2.3. Router LPD/SCS - control window ....................................................................................................................... 102
8.2.3.1. ASCII Printer (X2) ............................................................................................................................................................... 102
8.2.3.2. Printer character Set (X10) ................................................................................................................................................ 103
8.2.3.3. IBM Printer Emulation (X16) ............................................................................................................................................. 103
8.2.3.4. IBM System language (X19) .............................................................................................................................................. 103
8.2.3.5. Paper Orientation (X28) .................................................................................................................................................... 104
8.2.3.6. Flash Directory .................................................................................................................................................................. 104
8.2.3.7. Trace Option/Dump (X14) ................................................................................................................................................. 104
9. ROUTER MAINFRAME SCS/IPDS OVER SNA SERVER ................................................................................................... 105

9.1. MPI ROUTER FUNCTIONS.................................................................................................................................................. 105
9.2. THE MPI ROUTER MAIN MENU ......................................................................................................................................... 105
9.3. CREATING A NEW PRINTER CONFIGURATION ........................................................................................................................ 106
9.3.1. SNA Mainframe - Information window .............................................................................................................. 107
9.3.1.1. Profile Name ..................................................................................................................................................................... 108
9.3.1.2. Printer Group .................................................................................................................................................................... 108
9.3.1.3. Comments ......................................................................................................................................................................... 108
9.3.2. SNA Mainframe - connection window ................................................................................................................ 108
9.3.2.1. LU Name............................................................................................................................................................................ 108
9.3.2.2. Destination Type ............................................................................................................................................................... 108

9.3.2.3. Queue name ..................................................................................................................................................................... 109
9.3.2.4. IP Address ......................................................................................................................................................................... 109
9.3.2.5. IP Port ............................................................................................................................................................................... 110
9.3.3. SNA Mainframe - IPDS setting window .............................................................................................................. 111
9.3.3.1. Printer Emulation .............................................................................................................................................................. 111
9.3.3.2. Code Page ......................................................................................................................................................................... 112
9.3.3.3. Code Page Version ............................................................................................................................................................ 112
9.3.3.4. Dynamic Sharing ............................................................................................................................................................... 113
9.3.3.5. Standby Time .................................................................................................................................................................... 113
9.3.4. SNA Mainframe - Paper Controls window .......................................................................................................... 113
9.3.4.1. Paper Size .......................................................................................................................................................................... 113
9.3.4.2. Main Paper Tray ................................................................................................................................................................ 114
9.3.4.3. Out Paper Tray .................................................................................................................................................................. 114
9.3.4.4. Front Top........................................................................................................................................................................... 114
9.3.4.5. Front Left .......................................................................................................................................................................... 114
9.3.4.6. Back Top............................................................................................................................................................................ 114
9.3.4.7. Back Left............................................................................................................................................................................ 115
9.3.4.8. Duplex ............................................................................................................................................................................... 115
9.3.4.9. Suplex on Manuel Tray...................................................................................................................................................... 115
9.3.4.10. Suplex on Lower Tray ................................................................................................................................................... 115
9.3.4.11. Suplex on Upper Tray ................................................................................................................................................... 115
9.3.5. SNA Mainframe - SCS Settings window .............................................................................................................. 116
9.3.5.1. End of Line Option (X1) ..................................................................................................................................................... 116
9.3.5.2. End of Page Option (X2) .................................................................................................................................................... 116
9.3.5.3. IBM System Language (X3) ................................................................................................................................................ 117
9.3.5.4. Printer Form Length (X6) ................................................................................................................................................... 117
9.3.5.5. MPL Default Value (X14) ................................................................................................................................................... 117
9.3.5.6. Printing Format on First Paper Tray (X28) ......................................................................................................................... 118
9.3.5.7. Printer Character Set (X82) ............................................................................................................................................... 118
9.3.5.8. FSL Partial Mode ............................................................................................................................................................... 118
9.3.5.9. Evolution ........................................................................................................................................................................... 118
9.3.6. Traces Options window ...................................................................................................................................... 119
9.3.6.1. File Name .......................................................................................................................................................................... 119
9.3.6.2. Tracing Mode .................................................................................................................................................................... 119
9.3.6.3. Trace Flip Length ............................................................................................................................................................... 119
9.3.6.4. Dump Mode ...................................................................................................................................................................... 119
9.3.6.5. Reset Factory Default ........................................................................................................................................................ 119
10. ROUTER TELNET 5250 OR 3270 ............................................................................................................................... 121

10.1. MPI ROUTER TELNET FUNCTIONS ................................................................................................................................... 121
10.2. THE MPI ROUTER TELNET MAIN MENU .......................................................................................................................... 121
10.3. CREATING A NEW PRINTER CONFIGURATION .................................................................................................................... 122
10.3.1. Router Telnet - Information window .................................................................................................................. 123
10.3.1.1. Profile Name ................................................................................................................................................................. 124
10.3.1.2. Printer Group ................................................................................................................................................................ 124
10.3.1.3. Comments .................................................................................................................................................................... 124
10.3.2. Router Telnet 3270 – Telnet window .................................................................................................................. 124
10.3.2.1. Telnet Type ................................................................................................................................................................... 124
10.3.2.2. Server IP Address .......................................................................................................................................................... 124
10.3.2.3. Telnet IP Port ................................................................................................................................................................ 124
10.3.2.4. LU Name ....................................................................................................................................................................... 124
10.3.2.5. Telnet TimeOut ............................................................................................................................................................. 125
10.3.2.6. Trace Option ................................................................................................................................................................. 125
10.3.3. Router Telnet 3270 – Connection window .......................................................................................................... 125
10.3.3.1. Destination Type........................................................................................................................................................... 125
10.3.3.2. IP Port ........................................................................................................................................................................... 126
10.3.4. Router Telnet 3270 – Control window ................................................................................................................ 127
10.3.4.1. ASCII Printer (X2) .......................................................................................................................................................... 127
10.3.4.2. Printer character Set (X10) ........................................................................................................................................... 128
10.3.4.3. IBM Printer Emulation (X16) ......................................................................................................................................... 128
10.3.4.4. IBM System language (X19) .......................................................................................................................................... 128
10.3.4.5. Paper Orientation (X28) ................................................................................................................................................ 129
10.3.4.6. Flash Directory .............................................................................................................................................................. 129
10.3.4.7. Trace Option/Dump (X14) ............................................................................................................................................ 129
11. AFP/IPDS COMPATIBILITY ....................................................................................................................................... 131
11.1. COMPATIBLE RESIDENT FONTS ....................................................................................................................................... 131
11.1.1. Blue Server - Parser............................................................................................................................................. 131
11.2. LATIN 1 - EURO CODE PAGES......................................................................................................................................... 132
12. TROUBLE SHOOTING .............................................................................................................................................. 133
12.1. HOW TO GET THE BLUE SERVER “REGISTERING NUMBER” BEFORE INSTALLATION ..................................................................... 133
12.1.1. Description .......................................................................................................................................................... 133
12.1.2. Procedure ........................................................................................................................................................... 133
12.2. DURING THE INSTALLATION ........................................................................................................................................... 134
12.2.1. First installation .................................................................................................................................................. 134
12.2.2. During an Update ............................................................................................................................................... 134
12.2.2.1. MPI Services – Proccess not stopped ........................................................................................................................... 134
12.2.2.2. Error 1723 ..................................................................................................................................................................... 134
12.3. HOW TO ACTIVATE A CORRECT BLUE SERVER LICENSE.......................................................................................................... 135
12.3.1. Description .......................................................................................................................................................... 135
12.3.2. Explanation ......................................................................................................................................................... 136
12.4. HOW TO UPDATE BLUE SERVER ...................................................................................................................................... 140
12.4.1. From V5.xx to V5.80 or higher ............................................................................................................................ 140
12.4.1.1. Introduction .................................................................................................................................................................. 140
12.4.1.2. Getting started ............................................................................................................................................................. 140
12.4.2. From V6.xx to V7.xx ............................................................................................................................................ 144
12.4.2.1. Important information about the new Blue Server and update process ...................................................................... 144
12.4.2.2. Uninstall process .......................................................................................................................................................... 145
12.4.2.3. Install process ............................................................................................................................................................... 146
12.4.2.4. Configuration and Update ............................................................................................................................................ 146
12.4.2.5. Finalizing ....................................................................................................................................................................... 147
12.4.3. Since Blue Server BSV7.03.0001_20070327 ....................................................................................................... 147
12.5. HOW TO UPDATE CONFIGURATIONS ................................................................................................................................ 148
12.5.1. Blue Server printer configurations and profiles .................................................................................................. 148
12.5.2. MPI File Server service ........................................................................................................................................ 149
12.5.2.1. Updating configurations ............................................................................................................................................... 150
12.5.2.2. The printer configuration filter ..................................................................................................................................... 150
12.5.2.3. The Update Button ....................................................................................................................................................... 151
12.5.2.4. Update specific configurations ..................................................................................................................................... 151
12.5.3. Modify a parameter for all the printer configurations associated to a profile ................................................... 152
12.6. HOW TO CONFIGURE “DATA EXECUTION PREVENTION” ...................................................................................................... 153
12.6.1. Description .......................................................................................................................................................... 153
12.6.2. Opening Blue Server ........................................................................................................................................... 153
12.6.3. Action.................................................................................................................................................................. 154
12.7. HOW TO CONFIGURE REMOTE WINDOWS XP QUEUE USING BLUE SERVER .............................................................................. 155
12.7.1. From Windows NT4 ............................................................................................................................................ 155
12.8. HOW TO CONFIGURE CUSTOM PAPER SIZE FOR BLUE SERVER - PARSER ................................................................................. 158
12.9. HOW TO PRODUCE MULTIPLE OUTPUTS SIMULTANEOUSLY ................................................................................................... 161
12.9.1. Description .......................................................................................................................................................... 161
12.9.2. Blue Server master session configuration ........................................................................................................... 162
12.9.3. Blue Server child session configuration .............................................................................................................. 163
12.9.4. Blue Server interface sessions status .................................................................................................................. 163
12.10. HOW TO USE BLUE SERVER AND THE INDEXER FEATURE ....................................................................................................... 164
12.10.1. Description ...................................................................................................................................................... 164
12.10.2. IPDS indexing .................................................................................................................................................. 164
12.10.2.1. Step 1: Defining the rules ............................................................................................................................................. 164
12.10.2.2. Step 2: Running in production ...................................................................................................................................... 165
12.10.3. Prerequisite ..................................................................................................................................................... 165
12.10.4. Example used with this manual ...................................................................................................................... 166
12.10.5. Producing the tiff files ..................................................................................................................................... 168
12.10.5.1. Blue Server configuration ............................................................................................................................................. 168
12.10.6. Launching Index composer ............................................................................................................................. 170
12.10.7. Composer window .......................................................................................................................................... 172
12.10.8. Creating indexes ............................................................................................................................................. 173
12.10.8.1. Identifying a job and a page ......................................................................................................................................... 173
12.10.8.2. Defining the criteria to recognize this page .................................................................................................................. 174
12.10.8.3. Defining the indexes ..................................................................................................................................................... 175
12.11. HOW TO USE THE “ADD FORM” OPTION WITH BLUE SERVER................................................................................................ 177
12.11.1. Description ...................................................................................................................................................... 177

12.11.2. What objects can be included ......................................................................................................................... 178
12.11.3. How to specify when the images are added ................................................................................................... 178
12.11.4. Activating the “Add Form” option .................................................................................................................. 178
12.11.5. Location of the images used ........................................................................................................................... 179
12.11.6. XML utility ....................................................................................................................................................... 179
12.11.7. Syntax of the XML file ..................................................................................................................................... 179
12.11.7.1. Example of XML file ...................................................................................................................................................... 180
12.11.7.2. Example of XML file ...................................................................................................................................................... 180
12.11.8. Windows Pre-requisite – MSXML4.dll ............................................................................................................. 181
12.11.8.1. MSXML 4.0 Service Pack 2 (Microsoft XML Core Services) ........................................................................................... 182
12.11.9. AS/400 message CPA3394 : Load form type ................................................................................................... 183
12.12. HOW TO USE BLUE SERVER - GENERATING MAIL ............................................................................................................... 184
12.12.1. One Blue Server printer addresses one E-mail destination ............................................................................. 184
12.12.1.1. “Destination” Tab, “Output Language” must be set to “PDF”: ..................................................................................... 184
12.12.1.2. “Mail” tab configuration: .............................................................................................................................................. 185
12.12.1.3. Resulting E-mails in Lotus Notes and Microsoft Outlook.............................................................................................. 186
12.12.2. One Blue Server printer addresses any E-mail destination ............................................................................. 187
12.12.2.1. Modify the application: ................................................................................................................................................ 187
12.12.2.2. Blue Server configuration: ............................................................................................................................................ 188
12.13. HOW TO SPLIT ON TLE MO:DCA STRUCTURED FIELDS ....................................................................................................... 190
12.13.1. Introduction .................................................................................................................................................... 190
12.13.2. AFP Files with indexes ..................................................................................................................................... 190
12.13.3. Blue Server configuration ............................................................................................................................... 190
12.13.4. Example .......................................................................................................................................................... 191
12.14. HOW TO SET-UP AND USE BLUE SERVER BACK-UP ............................................................................................................ 192
12.14.1. Description ...................................................................................................................................................... 192
12.14.2. Installation & set up ....................................................................................................................................... 193
12.14.2.1. Installation .................................................................................................................................................................... 193
12.14.2.2. Set-up – Blue Server A .................................................................................................................................................. 194
12.14.2.3. Set-up – Blue Server B .................................................................................................................................................. 195
12.14.3. Starting Blue Server ........................................................................................................................................ 196
12.14.4. Problems ......................................................................................................................................................... 198
12.14.4.1. No more IP connection available with Blue Server ....................................................................................................... 198
12.15. HOW TO SET UP PDF ENCRYPTION .................................................................................................................................. 200
12.15.1. Description ...................................................................................................................................................... 200
12.15.2. Old interface – until V7.00.192 ....................................................................................................................... 200
12.15.3. New interface – Since V7.01.003 .................................................................................................................... 201
12.15.3.1. Encryption Level ........................................................................................................................................................... 202
12.15.3.2. Permanent editing lock................................................................................................................................................. 202
12.15.3.3. Administrator Password ............................................................................................................................................... 202
12.15.3.4. User Password .............................................................................................................................................................. 202
12.15.3.5. Printing allowed ............................................................................................................................................................ 202
12.15.3.6. Changes allowed ........................................................................................................................................................... 202
12.15.3.7. Enable copying of content ............................................................................................................................................ 203
12.16. HOW TO CHECK BLUE SERVER STATUS ............................................................................................................................. 203
12.16.1. Introduction .................................................................................................................................................... 203
12.16.2. Status problem ............................................................................................................................................... 203
12.17. HOW TO HANDLE “PRINTER RESTART” EXCEPTION ERROR .................................................................................................... 203
12.17.1. Parameter #54 AF ........................................................................................................................................... 203
12.18. HOW TO LOAD – UNLOAD BLUE SERVER PRINTERS WITH A FILE COMMAND ............................................................................. 205
12.18.1. Description ...................................................................................................................................................... 205
12.18.2. Creating “Order.Lst” file ................................................................................................................................. 205
12.18.2.1. Syntax of the file "Order.Lst" ........................................................................................................................................ 205
12.18.3. Example .......................................................................................................................................................... 205
12.19. HOW TO INSTALL BLUE SERVER ON WINDOWS 2003 CLUSTER ............................................................................................. 206
12.19.1. Requirement ................................................................................................................................................... 206
12.19.2. Cluster configuration ...................................................................................................................................... 206
12.19.3. Blue Server Installation ................................................................................................................................... 207
12.19.4. Cluster configuration for Blue Server .............................................................................................................. 209
12.19.4.1. MPI Parser .................................................................................................................................................................... 209
12.19.4.2. Shared Disk ................................................................................................................................................................... 211
12.20. HOW TO CONFIGURE BLUE SERVER ON CLUSTERED WINDOWS QUEUE ................................................................................... 214
12.20.1. Cluster configuration for windows queue ....................................................................................................... 214
12.20.2. Print Driver installation on the virtual server ................................................................................................. 214
12.20.3. Printer port installation on the virtual server ................................................................................................. 215
12.20.4. Print queue installation on the virtual server ................................................................................................. 215
12.20.5. Windows Queue sharing properties ............................................................................................................... 216
12.21. HOW TO RECORD A SPY TRACE USING BLUE SERVER – TELNET SESSION.................................................................................. 217
12.21.1. Description ...................................................................................................................................................... 217
12.21.2. Configuration on the Blue Server .................................................................................................................... 217
12.21.2.1. Telnet Session ............................................................................................................................................................... 217
12.21.3. Send the job .................................................................................................................................................... 218
12.22. HOW TO RECORD A INTERNAL SPY TRACE USING BLUE SERVER – PARSER SESSION.................................................................... 219
12.22.1. Description ...................................................................................................................................................... 219
12.22.2. Setup and Configuration ................................................................................................................................. 219
12.23. HOW TO RECORD AN EXTERNAL SPY TRACE WITH PPRSPY UTILITY – PARSER SESSION .............................................................. 220
12.23.1. Description ...................................................................................................................................................... 220
12.23.2. Setup and Configuration ................................................................................................................................. 221
12.24. HOW TO CONFIGURE A SNA/HIS LU USING BLUE SERVER - PARSER SESSION .......................................................................... 223
12.24.1. SNA Server configuration – Create a Printer LU ............................................................................................. 223
12.24.2. Blue Server - Router Mainframe configuration............................................................................................... 224
12.24.2.1. Connection tab ............................................................................................................................................................. 224
12.24.3. Blue Server – Parser configuraiton ................................................................................................................. 225
12.24.3.1. Host tab ........................................................................................................................................................................ 225
12.24.4. Loading the Router Maiframe and Parser ...................................................................................................... 226
12.24.4.1. SNA ............................................................................................................................................................................... 226
12.24.5. Blue Server side ............................................................................................................................................... 226
12.25. HOW TO ALLOCATE A SNA/HIS LU USING BLUE SERVER – TELNET SESSION............................................................................ 227
12.25.1. Description ...................................................................................................................................................... 227
12.25.2. Allocate a LUA to Telnet ................................................................................................................................. 227
12.25.2.1. PRTSNA02 properties : ................................................................................................................................................. 228
12.25.3. Blue Server configuration: .............................................................................................................................. 230
12.26. HOW TO INITIATE JOGGING IN BLUE SERVER – AOS – ALTERNATE OFFSET STAKER .................................................................. 231
12.26.1. Description ...................................................................................................................................................... 231
12.26.2. Procedure........................................................................................................................................................ 231
12.27. HOW TO SETUP BLUE SERVER FOR AFP ........................................................................................................................... 232
12.27.1. Input Configuration ........................................................................................................................................ 232
12.27.2. External AFP resources ................................................................................................................................... 233
12.27.3. AFPDS transform Log ...................................................................................................................................... 233
12.28. HOW TO CONFIGURE BLUE SERVER AFP FONT TABLES ........................................................................................................ 234
12.28.1. The AFP font resources ................................................................................................................................... 234
12.28.1.1. Font Character Set ........................................................................................................................................................ 234
12.28.1.2. Code Page ..................................................................................................................................................................... 234
12.28.1.3. Coded Font ................................................................................................................................................................... 234
12.28.2. The Blue Server IPDS font ressources .............................................................................................................. 234
12.28.3. The AFP – IPDS correlation ............................................................................................................................. 235
12.29. HOW TO VERIFY AN AS/400 FEATURE FOR TELNET5250 EMULATION WITH BLUE SERVER ......................................................... 236
12.30. HOW TO DISPLAY BLUE SERVER JOB NAMES ON THE FRONT PANEL OF YOUR PRINTER ................................................................ 237
12.30.1. Description ...................................................................................................................................................... 237
12.30.2. Procedure........................................................................................................................................................ 237
12.30.2.1. For Canon imageRUNNER ............................................................................................................................................. 237
12.30.2.2. For Hp or compatible PJL printers ................................................................................................................................ 237
12.31. HOW TO VERIFY AN IPDS PRINTER EMULATION FROM A MVS HOST USING IP PROTOCOL .......................................................... 238
12.32. HOW TO REMOTELY ACCESS USING MPI PARSER SERVICE .................................................................................................... 240
12.32.1. Description ...................................................................................................................................................... 240
12.32.2. Configuration .................................................................................................................................................. 240
12.32.2.1. MPI Parser Service Properties ...................................................................................................................................... 240
12.32.3. Problems ......................................................................................................................................................... 244
12.33. HOW TO UNDERSTAND BLUE SERVER V7.XX LICENSING ...................................................................................................... 245
12.33.1. Summary......................................................................................................................................................... 245
12.33.2. Access ............................................................................................................................................................. 245
12.33.2.1. You cannot get an access to GUI .................................................................................................................................. 245
12.33.3. Discovery ........................................................................................................................................................ 246
12.33.4. Definition ........................................................................................................................................................ 246
12.33.5. Detail .............................................................................................................................................................. 247
12.33.5.1. License Usage ............................................................................................................................................................... 247
12.33.5.2. Active Products ............................................................................................................................................................. 248

12.33.5.3. Registered Licenses ...................................................................................................................................................... 250
12.33.5.4. Alerts ............................................................................................................................................................................ 251
12.33.5.5. Migration ...................................................................................................................................................................... 253
13. BLUE SERVER RECOVERY......................................................................................................................................... 257
13.1. PRODUCT SUPPORT ..................................................................................................................................................... 257
14. TRADEMARKS ......................................................................................................................................................... 259
15. CUSTOMER SUPPORT AND WARRANTY INFORMATION ......................................................................................... 273
15.1. CUSTOMER SUPPORT ................................................................................................................................................... 273
15.2. AUTHORIZED DEALERS.................................................................................................................................................. 273
15.3. USER WARRANTY ........................................................................................................................................................ 273
15.4. MAINTENANCE ........................................................................................................................................................... 273
15.5. END USER LICENSE AGREEMENT FOR MPI TECH SOFTWARE ................................................................................................ 273

1. MPI Tech. location & technical support
Web site : www.mpitech.com
Europe North America

France US (East coast)
MPI TECH SA - Corporate Headquarters MPI TECH Inc.
40 rue du Général Malleret Joinville 901 North Stuart Street
BP 88 #Suite 1105
94402 Vitry sur Seine Arlington,
France VA 22203
Phone + 33 (0) 1 45 73 09 40 USA
Fax + 33 (0) 1 46 80 70 71 Phone + 1 (703) 243 3322
e-mail : support.fr@mpitech.com Fax + 1 (703) 243 3305
e-mail : support.us@mpitech.com
Denmark US (West coast)

MPI TECH A/S MPI TECH Inc.
Vadstrupvej 35 4952 Warner Avenue,
Dk – 2880 Bagsværd Suite 301
Denmark Huntington Beach
Phone + 45 4436 6000 CA 92649-5506
Fax + 45 4436 6111 USA
e-mail : support.dk@mpitech.com Phone + 1 (714) 840 80 77
Fax + 1 (714) 840 21 76
e-mail : techsup@mpitech.com
United Kingdom
MPI TECH United
Kingdom Gibbs House,
Kennel Ride,
Ascot
Berkshire
SL5 7NT
United Kingdom
Phone + 44 (0) 1344 891 008
Fax + 44 (0) 1344 890 908
e-mail : support.uk@mpitech.com
Germany
MPI TECH Gmbh
Bavariastr. 7a
D-80336 Munich
Germany
Phone + 49 (0) 89 35 4762 -30
Fax + 49 (0) 89 35 4762-11
e-mail : support.de@mpitech.com

<This page is intentionally left blank>

2. How to Start Blue Server interface
2.1. Microsoft® Blue Server Main Menu
The first time, to access the MPI Blue Server V7.xx main menu :
 Start Programs MPI Blue Server The Blue Server
 And you will get the following display :

2.2. SUN Solaris, AIX and Linux Blue Server Main Menu
The first time, to access the MPI Blue Server main menu :
 You can launch Blue Server in two different modes:
- With silent mode or
- With the process shell windows,
The command for launching Blue server is: <blueserver [-w | -stop]>.
Usage:
./blueserver : launches Blue Server in silent mode.
./blueserver -w : launches Blue Server with process whell windows and the
BlueServer interface.
./blueserver -stop : Stops all Blue Server processes.
LINUX-SUSE:/opt/MPI_Blue_Server/MPI_Parser # ./blueserver -w█

2.3. Blue Server Interface organization
2.3.1. Main task bar
2.3.1.1. Icon list
This icon allows to add a Domain name from our Blue Server GUI. (This
Add Domain domain name is not a Microsoft Windows domain). Useful, when you
want to manage different Blue Server installation. You must first create
a Domain, and then Server.
This icon allows adding a Server name from our Blue Server GUI..
Useful, when you want to manage different Blue Server installation. For
Add Server adding a Server, IP address or <Server_Name> can be used.
From this new entry, you can manage all other Blue Server installation
(create, delete, modify, load and unload access).
This icon allows adding a new profile. This profile can be used for new
Add Profile printer not listed in our standard installation.
This icon allows adding a new Printer.

Add Printer
This icon allows deleting a Domain previously created. You must first to
Delete Domain delete all Server, and then delete the Domain.
Delete Server This icon allows deleting a Server.
Delete Profile This icon allows deleting a Profile.
Delete Printer This icon allows deleting a Printer
Update Profile, printer
Channel Board configuration
Printer filter
Wizard
Help
Status: not connected

Backup Server
Status: connected

This display shows a typical organization mapped to different domains, servers.
 On each Domain, for example :
- TECH_FR
- TECH_UK
- TECH_US
 Some servers can be displayed, with their specific IP address or name .

 On each servers, you are able to display the available products (LPD EVOLUTION, LDS SCS,
PARSER…).
When the status is green, means the service is available,
When the status is red, means the service is stopped,
When the information “Locked by DHA”, , means the service is already started
by this user. You are not able to stop/start this service.
When the information “Used by EOLE”, , means the service is already started
by this user. You are able to stop/start this service.

2.3.1.2. Tabs list
2.3.1.2.1.Printer tab
 On the Blue Server main menu, select printers,
This function allows displaying all the printers available on the listed server.
2.3.1.2.2.Service tab
 On the Blue Server main menu, select Services,
This function allows to display all the services available on the listed server.
For more information refer to chapter xxxxx

2.3.1.2.3.Profiles tab
 On the Blue Server main menu, select Profiles,
This function allows displaying all the profiles available on the listed server.

3. IBM Host configuration for Parser session
3.1. PSF/400 AFP Printing Using TCP/IP
This chapter provides information to configure your OS/400 using TCP/IP.
The printer device configuration is different depending the OS/400 version.
Requirements
Please check the following points before the device creation.
– TCP/IP installed and enabled.
– PSF/400 license active on your AS/400 system.
Warning
Depending on your AS/400 version you must use WRKAPF2 command (V3R1 or V3R6) or
CRTPSFCFG command (V3R2, V3R7 or V3R1)
3.1.1. TCP/IP With AS/400 V3R1

 OS/400: V3R1M0 or later, TCP/IP configured
 PSF/400: must be installed.
(From OS/400 V3, PSF is an optional feature: product 5763SS1 feature 5102)
3.1.1.1. Creating The AS/400 Printer Device

In order to create an AS/400 printer device type the following command:
CRTDEVPRT
Press ENTER and the F11 command key to get the keyword displayed.
You must configure as follows:
Device Description Name DEVD <Printer Name>

Device Class DEVCLS *RMT
Type TYPE *IPDS
Model MODEL 0
AFP AFP *YES
AFP Attach AFPATTACH *APPC
Online ONLINE *YES
Font FONT 11
FORMFEED *AUTOCUT
Remote Location Name RMTLOCNAME <Printer Name>
Local Location Name LCLLOCNAME *NETATR
Remote Net Id RMTNETID *NETATR

Mode MODE QSPWTR
When the device is created use the WRKDEVD command to vary on the device.
3.1.1.2. Creating The WRKAFP2 Command On Your AS/400 (V3R1)

The WRKAFP2 command is provided by IBM. It offers an interface to a data area used by PSF/400 for
TCP/IP printing. There are two WRKAFP2 source codes, one is provided with the SF24144 PTF cover
letter and the latest with SF29961 PTF cover letter.
In order to know which WRKAFP2 version you must use, verify which PTF is applied on your AS/400:
If SF29961 PTF is already installed, use 29961.SRC file.
If SF24144 PTF is installed, use 24144.SRC file.
If neither of the above PTF are installed, order SF29961 PTF.

3.1.1.3. Using The WRKAFP2 Command For The Blue Server
The WRKAFP2 command parameters used for the Blue Server are:
DEVD : <Printer Name>

TCPIP : *YES (printer uses TCP/IP)
RMTSYS : printer IP address 193.157.60.20 for example
PORT : from 5001 to 9999 Parser number (one number per printer)
ACTTMR : *NOMAX The activation timer specifies the number of seconds PSF/400
will wait for a printer to respond to an activation request.
Setting this parameter to *NOMAX indicates it will wait for ever
INACTTMR : *SEC15 or *SEC30 The inactivity timer specifies the length of time PSF/400 will
maintain a session with the printer while there are no spooled
files with a status of RDY. If the time elapsed, PSF/400 closes
the connection with the printer which permits another LAN
application to print.

CRTDEVPRT
Type TYPE *IPDS
Model MODEL 0
AFP AFP *YES
Online ONLINE *YES
Font FONT 11
FORMFEED *AUTOCUT

Mode MODE QSPWTR
3.1.2.2. The CRTPSFCFG Command Parameters

The CRTPSFCFG command is provided by IBM. It offers an interface to a data area used by PSF/400 for
TCP/IP printing:
IPDSPASTHR : NO
RLSTMR : *SEC15 or *SEC30
RESTFONT : *YES
ACTTMR : *NOMAX The activation timer specifies the number of seconds
PSF/400 will wait for a printer to respond to an activation
request. Setting this parameter to *NOMAX indicates it
will wait for ever

CRTDEVPRT
Type TYPE *IPDS
Model MODEL 0
AFP AFP *YES
Online ONLINE *YES
Font FONT 11
FORMFEED *AUTOCUT

Mode MODE QSPWTR
3.1.3.2. Creating the WRKAFP2 command on your AS/400 V3R6

As version V3R1 the WRKAFP2 is provided by IBM. It offers an interface to a date area used by PSF/400
for TPC/IP printing.
The following PTF‟s must be applied on your system:
 SF 32499
 SF 32501
 SF 33878
 SF 33891
 SF 31461
 SF 32907
Some of these may superseded each other, and two of these contains the WRKAFP2 source on
descriptions:
# SF 32907
# SF 31461

3.1.3.3. Using The WRKAFP2 Command For The Blue Server
The WRKAFP2 command parameters used for the Blue Server are:
IPDSPASTHR : *NO
DEVD : <Printer Name>
TCPIP : *YES (printer uses TCP/IP)
ACTTMR : *NOMAX The activation timer specifies the number of seconds
PSF/400 will wait for a printer to respond to an activation
request. Setting this parameter to *NOMAX indicates it
will wait for ever
INACTTMR : *SEC15 or *SEC30 The inactivity timer specifies the length of time PSF/400
will maintain a session with the printer while there are no
spooled files with a status of RDY. If the time elapsed,
PSF/400 closes the connection with the printer which
permits another LAN application to print.

3.1.4.1. Using the CRTPSFCFG command for with the Blue Server
CRTPSFCFG
Press ENTER and the F11 command key to get the keyword display.
First Display
PSF Configuration PSFCFG PRTV3R7 <- PRINTER NAME

Library *CURLIB
User resource library list USRRSCLIBL *JOBLIBL
Device resource library list DEVRSCLIBL *DFT
+ for more values
IPDS pass through IPDSPASTHR *NO
Active release timer ACTRLSTMR *NORDYF
Release timer RLSTMR *SEC30 <-set to
Restart timer RESTRTMR *IMMED
SNA retry count RETRY 2
Delay between SNA retries RETRYDLY 0
Text description' TEXT
Second Display
Blank page BLANCKAPGE *YES

Page size control PAGSIZCTL *NO
Resident fonts RESFONT *YES
Resource retention RSCRET *NO
Edge orient EDGEORIENT *NO
Remote location RMTLOCNAME
Name or address *NONE
TCP/IP port PORT *NONE

TCP/IP activation timer ACTTMR 170
Use outline fonts USEOUTLFNT *NO

3.1.4.2. Creating the AS/400 printer device
CRTDEVPRT
First Display :
Device description DEVD PRTV3R7 <- PRINTER NAME

Device Class DEVCLS *LAN
Device Type TYPE *IPDS
Device model MODEL 0
LAN attachment LANATTACH *IP
Advanced function Printing AFP *YES
Port number PORT 5001 <- set to
Online at IPL ONLINE *YES
Font : FONT
Identifier 11
Pointsize *NONE
Form feed FORMFEED *AUTOCUT <- set to
Separator drawer SEPDRAWER *FILE
Separator program SEPPGM *NONE
Printer error message PRTERRMSG *INQ
Second Display :
Message queue MSGQ QSYSOPR

Library *LIBL
Activation timer ACTTMR *NOMAX <- set to
Maximum pending requests MAXPNDRQS 6
Print while converting PRTCVT *YES
Print request timer PRTRQSTMR *NOMAX
Form definition FORMDEF F1C10110
Library *LIBL
Remote location RMTLOCNAME 193.157.60.20 <- IP address
User-defined options USRDFNOPT *NONE

+ for more value
Third Display :
User defined object USRDFNOBJ

Object PRTV3R7 <- Printer name
Library *LIBL <- set to
Object type *PSFCFG <- set to
Data transform program USRDTATFM *NONE
Library
User defined driver program USRDRVPGM *NONE
Library
Text 'description' TEXT Device IPDS over TCP/IP

3.1.5. TCP/IP With AS/400 V4R1 and V4R2
CRTPSFCFG
First Display
PSF Configuration PSFCFG PRTV3R7 <- PRINTER NAME

Library *CURLIB
+ for more values
Release timer RLSTMR *SEC30 <- set to
SNA retry count RETRY 2
Delay between SNA retries RETRYDLY 0
Second Display

Remote location RMTLOCNAME
Name or address *NONE
TCP/IP port PORT *NONE

TCP/IP activation timer ACTTMR 170
Use outline fonts USEOUTLFNT *NO

CRTDEVPRT
First Display :
Device description DEVD PRTV3R7 <- PRINTER NAME
Font : FONT
Identifier 11
Pointsize *NONE
Second Display :

Library *LIBL
Library *LIBL

+ for more value
Third Display :

Object PRTV3R7 <- Printer name
Library *LIBL <- set to
Object type *PSFCFG <- set to
Library
Library

3.1.6. TCP/IP With AS/400 V4R3 , V4R4, V4R5, V5R1, V5R2, V5R3, V5R4 and V5R5
CRTPSFCFG
First Display:
PSF Configuration PSFCFG PRTV4RX <- PRINTER NAME

Library *CURLIB
+ for more values
Release timer RLSTMR *SEC30 <- set to
Retry APPC and TCP/IP RETRY 15
Delay between APPC retries RETRYDLY 90
AUTOSSNRCY *NO
ACKFRQ 100
Second Display:

USEOUTLFNT *NO
PSF defined options PSFDFNOPT *NONE
+ for more values
Font substitute message FNTSUBMSG *YES
Font capture FNTCAPTURE *NO
Font resolution FNTRSL *SEARCH
Third Display:
CSEMODE *NONE
Replace REPLACE *YES
AUT *LIBCRTAUT

CRTDEVPRT
Press ENTERS and the F11 command key to get the keyword displayed.
First Display:
Device description DEVD PRTV4RX <- PRINTER NAME

Font : FONT
Identifier 11
Pointsize *NONE
Second Display:

Library *LIBL
IMGCFG *NONE
Library *LIBL

+ for more value
Third Display:

Object PRTV4RX <- Printer name
Library *LIBL <-set to
Object type *PSFCFG <-set to
Library
Library

3.2. PSF/MVS AFP Printing Using TCP/IP
3.2.1. PSF/VM Configuration
3.2.1.1. Software Prerequisites
To print from PSF on TCP/IP attached IPDS printers, you need the following:
 PSF/MVS Version 2 Release 2.0 with APAR OW15599.
 MVS Scheduler APAR OW12236 to support two new PRINTDEV keywords:
 TCP/IP Version 3 Release 1, or higher, installed and configured on MVS.
Note: The TCP/IP address space name must be set to „TCPIP‟, which is the default at installation
3.2.1.2. Defining the Printer to PSF

In the PSF startup procedure two new keywords have been added to the Printer statement. To print to a
SNA attached printer, the destination is set using the keyword-LUNAME:
For TCP/IP printing the 2 new keywords are:
 IPADDR specifies the printer TCP/IP address
 PORTNO specifies the TCP/IP port number be used for PPD/PPR communication (IPDS
printing).For Blue Server, the Parser port number is starting from value 5001 to 9999
PSFMVS startup procedure sample:

//JOBHORT OUTPUT PAGE=V00643 /* JOB SEPARATOR PAGEDEF */
// FORMDEF=A10110, CHARS=GT15 /* JOB SEPARATOR FORMDEF */
//JOBTLR OUTPUT PAGEDEF=V00643, /* JOB SEPARATOR PAGEDEF */
// FORMDEF=A10110, CHARS=GT15 /* JOB SEPARATOR FORMDEF */
//DSHDR OUTPUT PAGEDEF=V00643, /* DS SEPARATOR PAGEDEF */
// FORMDEF=A10110, CHARS=GT15 /* DS SEPARATOR FORMDEF */
//MSGDS OUTPUT PAGEDEF=A06462, /* MESSAGE DATASET PAGEDEF */
// FORMDEF=A10110 /* MESSAGE DATASET FORMDEF */
//*FONT01 DD DSN=SYS1.FONTLIBB, /* SYSTEM FONT - 240 PEL */
//* DISP=SHR */
//FONT02 DD DSN=SYS1.FONT300, /* SYSTEM FONT - 300 PEL */
// DISP=SHR */
//PSEG01 DD DSN=SYS1..PSEGLIB, /* SYSTEM PAGE SEGMENTS */
// DISP=SHR */
//OLAY01 DD DSN=SYS1OVERLIB, /* SYSTEM MEDIUM OVERLAY */
// DISP=SHR */
//PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */
// DISP=SHR */
//FDEF01 DD DSN=SYS1.FDELIB, /* SYSTEM FORMDEFS */
// DISP=SHR */
//* */
//*********************************************************************************
/
//* PRINTDEV
*/
//*
*/
//*********************************************************************************
********/
//PRT1 CNTL */
//*PRT1 PRINTDEV FONTDD=*.FONT01, /* 240 PEL FONT LIBRARY DD */
//* /*  SEE REQUIRED ACTION ABOVE */
//PRT1 PRINTDEV FONTDD=*.FONT02 /* 300 PEL FONT LIBRARY DD */
//* /*  SEE REQUIRED ACTION ABOVE */
// OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */
// PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */
// PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */
// FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */
// JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR */
// JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR */
// DSHDR=*.DSHDR, /* DATA SET HEADER */
// MESSAGE=*. MSGDS, /* MESSAGE DATA SET OUTPUT */
// BUFNO=5, /* MESSAGE DATA SET OUTPUT */
// PAGEDEF=A06462, /* DEVICE PAGEDEF DEFAULT */
// FORMDEF=A10110, /* DEVICE FORMDEF DEFAULT */
// CHARS=(GF10, /* DEVICE */
// GS10,TU10,GU10), /* DEFAULT FONT SET */
// PIMSG=YES, /* ACCUMULATE DATA SET */
// DATACK=BLOCK, /* REPORT ALL DATA-CHECK */
// TRACE=NO, /* CREATE INTERNAL TRACE */
// FAILURE=WCONNECT, /* PSF ACTION ON PRINTER */
// TIMEOUT=REDRIVE, /* PSF ACTION ON TIMEOUT */
// MGMTMODE=IMMED, /* PRINTER MANAGEMENT MODE */
// DISCINTV=15, /* DISCONNECT INTERVAL IN SEC */
//* TCP/IP =Printer Definition */
// IPADDR=’192.187.60.20’, /* BLUE SERVER TCP/IP ADDRESS */
// PORT NO=’5001 /* IP Port Number for PARSER (value */
from 5001 to 9999 => one per
configuration)
//PRT1 ENDCNTL */
Sample JCL Startup Procedure for a TCP/IP-Attached printer


4. IBM Host configuration for Router SCS 5250 session
4.1. AS/400 SCS-DCA Printing Using TCP/IP LPR/LPD
Once these parameters have been configured, and the Blue Server session Router SCS has been
completed, printing from AS/400 will be possible.
Requirements:
AS/400 version 3.1 with TCP/IP installed.
4.1.1. Create a remote output queue

The CRTOUTQ command is used to create a Remote output queue. This will enable the AS/400 to
automatically output SCS/DCA data directly to the Blue Server.
Create Output Queue (CRTOUTQ)
Type choices, press Enter.
Output queue . . . . . . .
. . . OUTQ > BSOUTQ
Library . . . . . . . .
. . . > QGPL
Maximum spooled file size:
MAXPAGES
Number of pages . . . .
. . . *NONE
Starting time . . . . .
. . .
Ending time . . . . . .
. . .
+ for more values
Order of files on queue . . . . SEQ *FIFO
Remote system . . . . . . . . . RMTSYS > *INTNETADR
Remote printer queue . . . . . . RMTPRTQ > 'BSOUTQ'
More...

Writers to autostart . . . . . . AUTOSTRWTR > 1

Queue for writer messages . . . MSGQ QSYSOPR
Library . . . . . . . . . . . *LIBL
Connection type . . . . . . . . CNNTYPE > *IP
Destination type . . . . . . . . DESTTYPE *OS400
Host print transform . . . . . . TRANSFORM > *NO
User data transform . . . . . . USRDTATFM *NONE
Library . . . . . . . . . . .
Image configuration . . . . . . IMGCFG *NONE
Internet address . . . . . . . . INTNETADR > '192.168.30.200'
Destination options . . . . . . DESTOPT *NONE
Print separator page . . . . . . SEPPAGE *YES

User defined option . . . . . . USRDFNOPT *NONE
+ for more values
More...
User defined object: USRDFNOBJ

Object . . . . . . . . . . . . *NONE
Library . . . . . . . . . .
Object type . . . . . . . . .
User driver program . . . . . . USRDRVPGM *NONE
Library . . . . . . . . . . .
Spooled file ASP . . . . . . . . SPLFASP *SYSTEM
Text 'description' . . . . . . . TEXT 'Blue Server - Remote OUTQ'
Bottom
The value *INTNETADR must be used for RMTSYS.

The number “1” signifying “YES”, i.e. writer starts automatically when created,
The value *IP must be used for CNNTYPE,
The value *OS400 must be used for DESTTYPE,
The value *NO must be used for TRANSFORM,
The value used for INTNETADR must be the same as IP address of your local Blue Server.
4.1.2. AS/400 printing

The data to be printed must be associated with the defined OUTQ via the various PRTF commands.
This method of printing supports various printer emulations.
When printing from OFFICE/400 care must be taken when submitting data to be printed. The printer
defined in the Print Option menu panel of OFFICE/400 must have a similar emulation to the printed defined
in the OUTQ parameter.

5. IBM Host configuration for Router SCS 3270 session
5.1. Setup Mainframe SNA environment
Notes:
 This document is a help tutorial for configuring a Mainframe SNA connection.
 The following are configuration examples for establishing SNA Mainframe sessions.
 For more specific information on Mainframe SNA configuration, refer to the IBM documentation.
5.1.1. How to Define Host VTAM PU and LUs

For host connections, you can link IBM host systems through 317x cluster controllers, 37x5 front-end
processors, 3746 communications controllers, or integrated token-ring controllers on 9370
IBM host
SNA gateway

5.1.1.1. EXAMPLE : Token ring VTAM/NCP File for a Node type 2.0 Connection
5.1.1.2.
VTAM LIST
=========
*Line Definition
*---------------
NTRILN1 LINE ADDRESS=(1088, FULL), PORTADD=0,
RCVBUFC=4095,
MAXTSL=1033,
LOCADD=400031741601, <- LOCCADD = NT Server MAC Address
*PU LU Definitions
*-----------------
PS0105E PU ADDR=04,
IDBLK=05D, <- 3 first bytes of Local Node ID
IDNUM=00000, <- 5 last bytes of Local Node ID
CPNAME=PU,
DISCNT=N0,
MAXOUT=1,
MAXDATA=1456, <- Max BTU Length
MODETAB=LU1MODE,
MAXPATH=2,
VPACING=0,
PUTYPE=2
XID=NO, <- Set to N0 for node 2.0
DLOGMODE=XCOM4K,
USSTAB=USSTAB
PATH105E PATH DIALNO=0044020000000088, <- First 04=Source SAP

GRPNM=GRP0401,
CALL=INOUT
GID=1,
PID=2
PRTSNA201 LU LOCADDR=01 <- LUA address

USSTAB=USSADP
DLOGMODE=PDMGRP4R

NT Server - Network protocol configuration
5.1.1.2.1.Adding DLC 802.2 protocol to you NT Server/Workstation

In order to communicate via Token ring or Ethernet over SNA, you must add the DLC protocol to your NT
Server or Workstation running SNA Server.

5.1.1.2.2.SNA Server configuration – Create a link
You must define the Server LAN card to be used to communicate with the host.
- Folder Link Services, make a right click and select Link Service. Select DLC 802.2 Link Service from the
list.
- In the DLC 802.2 Link Service Properties window, select the LAN card you want to use.
5.1.1.2.3.SNA Server configuration – Create a connection

You must define a connection (PU Emulation) with attributes matching the VTAM PU Definitions
- Folder Connections, make a right click and select 802.2 from the list:

Connections : General
Connections : Address
Note : Remote Network Address must match the Host MAC Address (TIC)

Connections : System Identification
Note : local Node ID must match the ID_NUM and ID_BLOCK parameters of the VTAM PU Definition
Connections : System Identification
Note : MAX BTU Length must match the MAX_DATAD parameter of the VTAM PU Definition

5.1.1.2.4.SNA Server configuration – Create a Printer LU
Attached to the connection, you must create your printer LU. In order to run with MPI Router, you must
define a LUA LU.
- Make a right click on your connection and select Application LU (LUA).
This new window appears :
Note : The number specified for LU must match the LOCADDR parameter of the VTAM LU Definition


6. IBM Host configuration for TN3270/TN5250
6.1. TN3270 Setup
6.1.1. Description
WorkStation/Server where the

IBM Host MPI Blue Server – Router telnet Printers
module is installed
This document is a help tutorial for configuring a Telnet Server on the IBM host.
The following are configuration examples for establishing Telnet sessions.
For more specific information on TELNET 3270 configuration, refer to :
”IP Configuration Guide for z/os” SC31-8775-01

6.1.2. Telnet 3270 connectivity
The TN3270 Telnet Server acts as an interface between IP and SNA networks. End users in an IP network
connect to the server which is also a VTAM application. The Server activates one SNA application minor
node logical unit (LU) to represent each Telnet IP client.
These Telnet application LUs establish sessions with VTAM host applications (for example, CICS),
simulating terminals (LU0 or LU2) or printers (LU1 or LU3).
The TN3270 Telnet server runs in the TCP/IP address space as part of TCP/IP. The Telnet Server is
started as part of the TCP/IP startup procedure. To enable connections, the VTAM and TCP/IP
configuration data sets must be modified with Telnet statements. These statements describe the Telnet
LUs, a listening port, and the characteristics of that port.
After TCP/IP is started, VARY and DISPLAY commands specifically related to the Telnet server can be
used to alter the state of Telnet or display information about Telnet. For more information about these
command sets, refer to z/OS Communications Server: IP System Administrator’s Commands.

6.1.3. VTAM Configuration
6.1.3.1. Sample of major node definition (only printers)
Following is an example of an appropriate major node for six LU VTAM printers definition :
TELPRT01 to TELPRT05 and TELMYPRT
TELNET VBUILD TYPE=APPL

TELPRT01 APPL AUTH=NVPACE, X
EAS=1, X
PARSESS=NO, X
MODETAB=MPITAB, X
SESSLIM=YES
EAS=1, X
PARSESS=NO, X
MODETAB=MPITAB, X
SESSLIM=YES
EAS=1, X
PARSESS=NO, X
MODETAB=MPITAB, X
SESSLIM=YES
EAS=1, X
PARSESS=NO, X
MODETAB=MPITAB, X
SESSLIM=YES
EAS=1, X
PARSESS=NO, X
MODETAB=MPITAB, X
SESSLIM=YES
TELMYPRT APPL AUTH=NVPACE, X
EAS=1, X
PARSESS=NO, X
MODETAB=MPITAB, X
SESSLIM=YES

6.1.4. Configuration TCP/IP
In this document, we assume that TCP/IP is already active and Telnet server is already configured and
active. We will simply detail the elements relating to printers.
In a general way, a Telnet printer client must be associated to a specific VTAM LU.
To configure a Telnet printer client, it will be necessary to modify the TCP/IP profile. This configuration
intervenes in a group BEGINVTAM/ENDVTAM in which, one creates an association between Telnet clients
and VTAM LUs.
6.1.4.1. TCP-IP Telnet configuration

In the above TCP/IP profile, inside a BEGINVTAM / ENDVTAM group, we will define:
 An IPGROUP name – this is the most common method used to map Objects to the client. In a
static network, Objects can be mapped to clients based on the exact IP address, or Objects can be
mapped to IPGROUP names containing exact IP addresses and subnets.
 Then a PRTGROUP name - The Generic PRTMAP mapping statement maps a single LU or
PRTGROUP Object to a client. For single LU mappings, Telnet will assign the LU name to the
connection if the LU is available. For PRTGROUP mappings, Telnet will assign an available LU
from the group to the connection. An LU is required to represent the client when initiating a VTAM
session.
 At least a PRTMAP name - The PRTMAP statement assigns the LUs in PRTGROUP to any client
identified by IPGROUP
TCP/IP profile
; Define the VTAM parameters required for the Telnet server.
;
BEGINVTAM ;
<Parameters>....
IPGROUP <IPGroup Name> ;

<IP address list which are authorized to reach the mainframe>
ENDIPGROUP
;
PRTGROUP <ImpGroup Name> ;
<LU VTAM list which are authorized to reach the Telnet connection>
ENDPRTGROUP
;
PRTMAP <ImpGroup Name> <IPGroup Name>
ENDVTAM

6.1.4.2. Sample
Below is an extract from a TCP/IP profile corresponding to a VTAM definition listed previously.
Note : all the parameters are not indicated.
;
; TCPIP.PROFILE.TCPIP
; ===================
;
; COPYRIGHT = NONE.
;
; NOTES:
;
; The device configuration statements MUST be changed to match your
; hardware and software configuration.
;
; The BEGINVTAM section must be changed to match your VTAM
; configuration.
;
ARPAGE 20
; TELNETPARMS indicate the Port for Telnet communication
TELNETPARMS
PORT 23
INACTIVE 28800
TIMEMARK 28800
ENDTELNETPARMS
;;;;;;;;
;
;
;
PORT
7 UDP MISCSERV ; Miscellaneous Server
7 TCP MISCSERV
9 UDP MISCSERV
9 TCP MISCSERV
19 UDP MISCSERV
19 TCP MISCSERV
20 TCP OMVS NOAUTOLOG ; FTP Server
21 TCP OMVS ; FTP Server
23 TCP INTCLIEN ; Telnet Server
25 TCP SMTP ; SMTP Server
69 UDP OMVS ; OE TFTP SERVER
80 TCP OMVS ; OE WEB SERVER
111 TCP PORTMAP ; Portmap Server
111 UDP PORTMAP ; Portmap Server
135 UDP LLBD ; NCS Location Broker
161 UDP OSNMPD ; SNMP Agent
162 UDP SNMPQE ; SNMP Query Engine
433 TCP OMVS ; OE WEB Server
443 TCP OMVS ; Secure Server
512 TCP RXSERVE ; Remote Execution Server
513 UDP OMVS ; OE RLOGIN SERVER
514 UDP OMVS ; OE syslog server
514 TCP RXSERVE ; Remote Execution Server
515 TCP EPMLPD ; LPD Server

;
; Define the VTAM parameters required for the Telnet server.
;
BEGINVTAM
;
PORT 23
; Define logon mode tables to be the defaults shipped with the
; latest level of VTAM
TELNETDEVICE 3277 D4C32XX3
TELNETDEVICE 3278-2-E D4C32XX3,D4C32XX3
TELNETDEVICE 3278-2 D4C32XX3,D4C32XX3
TELNETDEVICE 3279-2-E D4C32XX3
TELNETDEVICE 3279-2 D4C32XX3
TELNETDEVICE DYNAMIC ,D4C32XX3
TELNETDEVICE 3287-1 ,D4C32XX3
;;;;;;;;;;;;
; Define the LUs to be used for general users.
DEFAULTLUS
SC0TCP01..SC0TCP30
ENDDEFAULTLUS
;;;;;;;;;;
;
; definition of an IP address group authorized for Telnet printer client
; In this case, IP address 192.16.31.5 and address ranging between
; 192.168.31.40 to 192.168.31.60 are authorized
IPGROUP IPPRT
192.168.31.5
192.168.31.40..192.168.31.60
ENDIPGROUP
;
; assign an available LU from the group to a Telnet connection
PRTGROUP PRTN32 ;
TELPRT01..TELPRT05 TELMYPRT
ENDPRTGROUP
;
; assigns the LUs in PRTGROUP to any client identified by IPGROUP
PRTMAP PRTN32 IPPRT
ENDVTAM

6.2. TN5250 Setup
To set up TN5250, configure your Telnet session using Blue Server.
Start Blue Server, select Config / Add printer. Select TELNET and enter the Device Name. When this
new device has been loaded, it will automatically set up a device on your AS/400.
Note :
Auto configuration of devices must be set up on your AS/400, telnet must be started and the correct PTFs
must be installed.
See APARII10918 on IBM‟s support page for a list of PTFs to be installed for the different versions of
AS/400 for TN5250e printing support.
http://www.as400.ibm.com/clientaccess/caiixd1.htm
6.2.1. Autoconfiguration of Devices

How to set up your AS/400 to autoconfigure devices :
 Issue the command :
WRKSYSVAL
And follow the screen dump below.
Work with System Values
System: S4449156
Position to . . . . . . Starting characters of system value
Subset by Type . . . . . *ALL F4 for list
Type options, press Enter.

2=Change 5=Display
System
Option Value Type Description
QABNORMSW *SYSCTL Previous end of system indicator
QACGLVL *MSG Accounting level
QACTJOB *ALC Initial number of active jobs
QADLACTJ *ALC Additional number of active jobs
QADLSPLA *ALC Spooling control block additional storage
QADLTOTJ *ALC Additional number of total jobs
QALWOBJRST *SEC Allow object restore option
QALWUSRDMN *SEC Allow user domain objects in libraries
More...
Command
===>
F3=Exit F4=Prompt F5=Refresh F9=Retrieve F11=Display names only
F12=Cancel

Work with System Values
System: S4449156
Position to . . . . . . Starting characters of system value
Subset by Type . . . . . *ALL F4 for list
Type options, press Enter.

2=Change 5=Display
System
Option Value Type Description
QASTLVL *SYSCTL User assistance level
QATNPGM *SYSCTL Attention program
QAUDCTL *SEC Auditing control
QAUDENDACN *SEC Auditing end action
QAUDFRCLVL *SEC Force auditing data
QAUDLVL *SEC Security auditing level
5 QAUTOCFG *SYSCTL Autoconfigure devices
QAUTORMT *SYSCTL Autoconfigure of remote controllers
More...
Command
===>
F3=Exit F4=Prompt F5=Refresh F9=Retrieve F11=Display names only
F12=Cancel
Display System Value
System value . . . . . : QAUTOCFG

Description . . . . . : Autoconfigure devices
Autoconfigure device . : 1 0=Off

1=On
Press Enter to continue.
F3=Exit F12=Cancel

7. How to configure Parser session - IPDS connection
7.1. The MPI Parser Main Menu
To access the MPI Blue Server V5 (or higher) main menu,
 S tart: Programs MPI Blue Server The Blue Server
From this Menu you can :

1. Create and/or modify the printer‟s configuration,
2. Load or unload the printer‟s configuration,
3. Display the status of the loaded printer‟s configuration,
4. Create a remote access to another MPI Blue Server.

7.2. Creating a New Printer Configuration
 From the previous display, select “Wizard Create Printers” to create a new printer configuration.
 Select “PARSER”.
 Double click or select “Apply”,
 Select the printer profile you want to use with this new configuration.
PCL5 Profile used for generic PCL5 printers
PDF Profile used for PDF files creation.
PS2 Profile used for PostScript level 2 and level 3 printers. Use this profile if you want
to print color data.
Sample Generic profile
XXXXXXXX All the other profiles are created for specific printer model.
This list can be updated every month.

 Enter the name of the new printer configuration. Then, select “OK”.
 And you will get directly the following display :
7.2.1. Parser - Information window
7.2.1.1. Profile Name

Sample is the default; this is the profile you select for the printer creation.
7.2.1.2. Printer Group

Used to select a specific printer group. Useful to manage different servers.
7.2.1.3. Comments
Used to write some notes.

7.2.2. Parser - Host window
The Blue Server Parser can accept IPDS data over Six different ways:
 TCP/IP Input
 Channel Input Working in conjunction with the PCI channel board.
For additional information, please contact your local MPI
Tech office.
 Directory Path Available for input AFP.
 Telnet
 BS Session (IPDS from Host) For additional information, please contact your local MPI
Tech office. A specific license is requested.
 BS Session (Preprocessed IPDS) For additional information, please contact your local MPI
Tech office. A specific license is requested.
7.2.2.1. Input Data Stream

Values allowed:
 IPDS: Select this option when your host sends IPDS over TCP/IP protocol (PPD/PPR).
Configure the IP PORT according to your host device description.
 AFPDS: Select this option when your host sends AFPDS files (from IBM Host, Press, Info Print
Manager…) to a specific input Blue Server “Directory Path”. A specific license is
requested.

7.2.2.2. Connection
Values allowed:
 TCP/IP: Select this option when your host sends IPDS over TCP/IP protocol (PPD/PPR).
 Channel: Select this option when your Blue Server station is attached to the host system
over Channel 370 connection. The MPI PCI Channel interface card is required.
Configure the channel address and speed according to the host definition.
 Directory Path Select this option when AFP/IPDS data will be sent to this directory.
 Telnet For additional information, please contact your local MPI Tech office.
 BS Session (IPDS from host) For additional information, please contact your local MPI office.
 BS Session (Preprocessed IPDS) For additional information, please contact your local MPI office.
Channel Address
Available for NT and Solaris
With the MPI PCI Channel interface card, you can manage up to eight devices (8 logical printers).
Values allowed:
 00* (default) to 07
7.2.2.3. IP Port
This number (ranging from 5001 to 65535) must match the Port Number set in the host printer definition.
When you define several printer configurations with the Blue Server Parser, each of them must be setup
with a different IP Port.
7.2.2.4. Printer Emulation

This parameter defines the IBM printer the Blue Server emulates.
Values allowed:
 IBM 4028
 IBM 3812
 IBM 3816
 IBM 3130
 IBM 3825
 IBM 3827
 IBM 3835
 IBM 4000
IBM4028 is the default emulation suggested when using 300 DPI resources at the host level.
IBM 3812 is the default emulation suggested when using 240 DPI resources.
IBM 3827 is a continuous form (fanfold) printer. The IPDS paper origin is different. Use this emulation when
you want to rotate the page 90 degrees clockwise compared to other IPDS emulation
7.2.2.5. IBM Resolution

Values allowed:
 240 dpi
 300 dpi
 600 dpi
 Auto
This parameter is only accessible with the following IBM printer emulations :
3130, 3825, 3827, 3835 and 4000.

7.2.2.6. License Group
Used to select the out put speed (ppm – Page Per Minute). Usually this parameter matches with the target
printer speed. A specific license is requested.
Values allowed:
 Group0 (reserved)
 Group1 (1-55)
 Group2 (56-85)
 Group3 (86-120)
 Group4 (121-200)
 Group (no limit)
7.2.2.7. Color license
Warning
To use this functionality, a specific license must be added.

Please contact MPI TECH or your local MPI TECH for further instructions.
 Checked: Allows the Blue Server to print IPDS color data stream. Check in the license server if
you have color license installed. If not, please contact your dealer.
 Unchecked: All color data are printed in black and white.
Values allowed:
 Group0 (reserved)
 Group1 (1-16)
 Group2 (17-30)
 Group3 (31-45)
 Group4 (46-60)
 Group5 (61-85)
 Group6 (86-120)
 Group7 (121-150)
 Group8 (151-200)
 Group (no limit)
7.2.2.8. Input Speed in ppm

This parameter is used in conjunction with License Group.
Used to select the out put speed (ppm – Page Per Minute). Usually this parameter matches with the target
printer speed.
Values allowed:
 from 1 to 9999
7.2.2.9. Code Page Version

This parameter indicates the version of the code page.
Some of the code pages supported by the printer are available in two versions. Certain characters differ
between versions of the same code page.
If you have problems printing characters like this , ÷, =, © , change the default code page.
Values allowed:
 0
 1

7.2.2.10.Default FGID
This parameter indicates the FGID used when the application request default.
For additional information, please refer to chapter “AFP/IPDS Compatibility”.
7.2.2.11.Default CPI
This parameter indicates the CPI used when the application request default.
7.2.2.12.Page Format
Determines how data is positioned on the page.
Values allowed:
 Whole: The printer does not move or compress the page. All page positioning and formatting is
done at the application level.
 Margin: Moves the page origin if this falls within the unprintable area.
7.2.2.13.Early print complete

Values allowed:
 Checked: The Blue server signals the host that the job is completed as soon as the IPDS data is
formatted.
 Unchecked: The Blue Server waits until the job is physically completed to signal the host that the job
is complete.
Note
Setting Early prints complete = Checked may improve print performance, but may also degrade recovery and
cause lost data from some printing problems, such as jams.
7.2.2.14.Block Char Error (or Null Suppress)

Defines the way The Blue Server reports the IPDS Invalid character exceptions to the host.
Values allowed:
 Checked: The Blue Server does not report the invalid character exception to the host. Invalid
characters such as Hex00 are replaced with a blank character and processing
continues.
 Unchecked: The Blue server reports the invalid characters as required by the host printer
configuration. Printout may stop depending your host configuration.

7.2.2.15.Code Page
This parameter selects the default Code Page for the country:
Country Code Page

USA/Canada 37
US ASCII-L 38
Canadian French 260
Austria/Germany 273
Belgium 274
Brazil 275
Denmark/Norway 277
Finland/Sweden 278
Italy 280
Japan-English 281
Portugal 282
Spanish-Speaking 284
United Kingdom 285
Austria/Germany (alternate) 286
Denmark/Norway (alternate) 287
Finland/Sweden (alternate) 288
Spain (alternate) 289
Japan-Katakana 290
France 297
English ASCII 367
Arabic 420
Greek 1 423
Hebrew 1 424
Personal Computer (PC) 437
International Set 5 500
Hebrew 2 803
Portugal (alternate) 831
Latin 2 870
Iceland 871
Greek 2 875
Cyrillic 880
Turkish 1 905
Turkish 2 1026
USA/Canada (€) 1140
Austria/Germany (€) 1141
Denmark/Norway (€) 1142
Finland/Sweden (€) 1143
Italy (€) 1145
Spanish speaking (€) 1145
United Kingdom (€) 1146
France (€) 1147
International Set 5 (€) 1148
Iceland (€) 1149

7.2.2.16.Report Position Error
Defines the way The Blue Server reports the IPDS Position Error exceptions to the host.
Values allowed:
 Checked: The Blue server reports the Position Error as required by the host printer configuration.
Printout may stop depending your host configuration.
 Unchecked: The Blue Server does not report the Position Error exception to the host.
7.2.2.17.Graphic Overlay
Values allowed:
 Checked: The Blue Server uses caching, which improves performance for jobs with repeated
overlays, but it consumes more memory at the server level.
 Unchecked: The Blue Server does not use caching. It requires less memory but provides less
performance for jobs with repeated overlays.
7.2.2.18.Free Type Rasterizer

This option defines which rasterizer is used by Blue Server – parser module
Values allowed:
 Checked: The Blue Server uses FreeType rasterizer
Note
- Mandatory for True Type fonts.
- Recommended for Double bytes fonts.
 Unchecked: The Blue Server uses Nimbus rasterizer.
7.2.2.19.Active String Indexer

A specific license is requested.
Values allowed:
 Checked: The Blue Server uses the “String Indexer” functionality.
 Unchecked: The Blue Server does not use the “String Indexer” functionality.
For additional information, please contact your local MPI Tech office.
7.2.2.20.Share IPDS with other session

Values allowed:
 Checked: The Blue Server uses the “Share IPDS with others session” functionality.
 Unchecked: The Blue Server does not use the “Share IPDS with others session” functionality.

7.2.3. Parser – Destination window
TCP/IP example
LPD Printer example

Windows Queue example
Only to File example

7.2.3.1. Output Language
Values allowed:
 BMP: Output format is compressed PCL bitmap (Approx. 75 Ko per page).
Use this format only when you want to use the vertical and horizontal
compression parameters to resize the logical page in the physical page.
 PCL5: Output format is PCL5. This format is adapted to the most popular printers
and keeps your network band switch available. Do not used for Color
output.
 PS2: Output format is PostScript Level 2. Use this format when your printer
supports the PostScript level 2 language or when you want to print color
IPDS jobs.
 PS3: Output format is PostScript Level 3. Use this format when your printer
supports the PostScript level 3 language or if you want to print color IPDS
jobs.
 PDF: Output format is PDF (Portable document format – Adobe ©). You can use
this option to print on PDF printers (Xerox Dp65 for example) or to
generate PDF files on your computer. (See „Print to file Option‟). A specific
license is requested.
 TIFF: TIFF format. Used for archive documentation. Only Back & White support.
The TIFF produced is a multi page document (contains the entire job
unless the split option is set). A specific license is requested.
 PPML: Personalized Print Markup Language.
For more details, please contact MPI Tech. A specific license is requested.
 IPDS: Not supported for the moment. For more details, please contact MPI Tech.
 PDF/A-1b:2005 PDF format for legal archiving. A specific license is requested.
 IMAGE Produces one (Black & White or Color) image per page, in various
compression format (bmp, jpg, tif, png…). For more details, please contact
MPI Tech. A specific license is requested.
7.2.3.2. PPD file

This parameter is only available when PS2 or PS3 are selected on Output Language parameter.
Only used when Output Language is set to PS2 or PS3. Specify the cfg file of the target PostScript printer
to handle the printer feature such as input and output paper trays, Duplex, stapling… properly.
Most current cfg files of printers manufacturers are created by MPI. If this cfg file does not exits for your
target printer, contact MPI.
The PPD files are located : <local_drive>:\MPI Blue Server\MPI Parser\ppd folder and select
it in the printer configuration.
7.2.3.3. Using Virtual Child

For additional information, please contact your local MPI office.
7.2.3.4. Output Resolution

This parameter is used to select the output resolution.
Values allowed:
 300
 600

7.2.3.5. Destination Type
Values allowed:
 TCP/IP: Used when the printer destination is an IP printer that supports TCP/IP socket
printing.
 LPD Printer: When you want to address the printer or a print server over TCP/IP LPR/LPD
protocol.
 Windows Queue: Used when you want to address Windows Shared printers. Windows printer
may be local or remote (even Novell print queue). Use the browse button to
discover the available printers over the network.
Use this functionality when you want to print to a printer connected through
parallel port.
 Only to File: Folder path where you want to store output spool files. The file name is
generated with the printer name, job id, job number, page range, date and time.
Leave this field blank if you don‟t want to store output files on your computer.
 NULL Transform: Just allows a host connection with No printout.
7.2.3.6. PJL Support

This parameter is only available when TCP/IP port is selected on Destination Type parameter.
Values allowed:
 Checked: Enables bi-directional communication between The Blue Server and the printer. Printer
errors such as Paper Jam, Paper Out, Toner out, Out bin Full, Cover Open are reported
to the host system.
Note
Make sure that your printer supports this protocol before using this parameter (please refer to your printer
documentation).
 Unchecked: (default) Disable bi-directional communication between The Blue Server and the printer.
7.2.3.7. SNMP Support

This parameter is only available when TCP/IP port is selected on Destination Type parameter.
Values allowed:
 Checked: Enables status between The Blue Server and the printer. Printer errors such as Paper
Jam, Paper Out, Toner out, Out bin Full, Cover Open are reported to the host system.
Note
Make sure that your printer supports this protocol before using this parameter (please refer to your printer
documentation).
 Unchecked: (default) Disable bi-directional communication between The Blue Server and the printer.

7.2.3.8. Printer IP Address
This parameter is only available when TCP/IP or LPD Printer is selected on Destination Type parameter.
Values allowed:
 Target printer IP Address or DNS name.
For internal print servers, this address can be found or changed through the front panel of the printer
and will also appear on the printer configuration (Self-Test) page. For external print servers this
address is set with specific printer/print server manufacturer and will also appear on the configuration
page (Self-Test) for the external print server.
7.2.3.9. Printer IP Port

This parameter is only available when TCP/IP is selected on Destination Type parameter.
Specify the IP socket (or Port Number or Raw Port) to be used to send data to the print server over TCP/IP.
The IP port varies depending on the print server manufacturer.
Note
This list is not exhaustive.
Manufacturer Model Socket / Port Number / Raw port

Axis box 9100
DEC Digital card 2501
IBM NP or Info Print 2501
Emulex box 2501 (parallel) and 2502 (serial)
HP Jet Direct MIO 9100 or 9099
HP Jet Direct EIO 9100
HP external print server EX Plus 3 9100 (LPT1)
9101 (LPT2)
9102 (LPT3)
Kyocera 9100
Lexmark Marknet N 9100
Lexmark MarkNet S 9100 or 9600
Lexmark external print server MarkNet Xle 9100 (LPT1) et 9102 (LPT2)
Lexmark external print server MarkNet Pro 3 9100 (LPT1),
9102 (LPT2),
9103 (Serial)
MPI Tech (I-Data) EIO/LinkCom 9100
QMS card 35
Ricoh Internal card 9100
Xerox Internal card for N32/40 2000, 2501, 9100
Xerox Internal card 9100
7.2.3.10.Windows Queue
This parameter is only available when Windows Queue is selected on Destination Type parameter.
Use “Browse” for searching your local or remote windows queue.
Example:
\\PRINT_SERVER\PRT_TEST

7.2.3.11.Split Document
Use this parameter to split a big document into several jobs.
With this option you can increase the printer speed on big documents because the printer can start printing
without having to wait for the end of a job.
Example:
Setting this value to 50 generates 4 printer spool files for a 200 sheets job and the printer starts printing
after receiving only 50 pages.
7.2.3.12.LPD Queue Name

Name of print queue to be addressed.
Example :
Lpdprt1
7.2.3.13.Print to file
File Path
Specify the folder you want the transformed IPDS documents to be stored.
7.2.3.14.Page Configuration
Values allowed:
 Checked: include PostScript configuration page (paper size, duplex and paper tray selection)
required when you want to send a PostScript document to the printer.
 Unchecked: Remove PostScript configuration page from output data file. This is needed when you
want to view PostScript documents with a PostScript viewer such as Ghostscript.
7.2.3.15.Text as graphic
Values allowed:
 Checked: Includes all fonts and objects as bitmap objects. This option increases file size and
decreases printer performance. This is needed when you want to use PostScript files
with a PS viewer like Ghostscript.
 Unchecked: Use standard fonts.
7.2.3.16.Data Extraction
This parameter is used for specific functionalities. A specific license is requested.
 Enables the Blue Server to send to a fax software (such as RightFax  software). Most fax software
use trigger and trailer strings to extract information such has phone number, receiver name, sender
name, subject… from the document.
 Checking Send to fax or String Extraction allows you to set Start String and Stop String
according to your fax software requirement. Within the IPDS document, any string found between
these two strings will be added in ASCII format at the top of the page.
Values allowed:
 None
 Send to Fax
 String Extraction

7.2.3.17.Start string
This parameter is only available when Send to Fax or String Extraction is selected on Data Extraction
parameter.
Indicates the trigger string detected by the fax software.
7.2.3.18.Stop String
This parameter is only available when Send to Fax or String Extraction is selected on Data Extraction
parameter.
Indicates the trigger string detected by the fax software.
7.2.3.19.Embed fonts
Values allowed:
 Checked: Substitutes standard Adobe Acrobat fonts with internal MPI scalable fonts. PDF
files are bigger but more realistic.
 Not checked: Adobe Acrobat reader fonts are used (Courier, Arial, Times New Roman). PDF files
are smaller but documents may not be exactly like the original one.
7.2.4. Parser - Input trays window
7.2.4.1. AFP Tray

Tray number selected from the host application.
Values allowed:
 Tray1 to Tray8, envelope and manual feed.

7.2.4.2. Printer Tray
Trays available on the printer (set according to the printer profile used such as PCL5, PS2, PS3,
DCxxxx…).
Any other input tray can be added by the user. You need to modify the specific profile (PCL5, PS2, PS3,
DCxxxx….) used.
 From the main Blue Server Menu, select “Profiles” Tab,
 Select the specific profile,
 Click right -> Setup
 Select “Tray Profile” tab,
 From this display, you can add, delete, and rename the input Tray. Do not forget to configure the
PCL command for your target input Tray modification.

7.2.4.3. Duplex Tray
This parameter is only available for printers with the duplex option installed.
This parameter allows users when printing a duplex job to select another input Tray, when “Preprinted or
“Letterhead” or what else is configured.
7.2.4.4. Rotation
This parameter allows users to change the standard rotation on a specific IBM tray.
Values allowed:
 0 degree*
 90 degrees
 180 degrees
 270 degrees
7.2.4.5. Edge to Edge Support

This parameter is only available for printer that support “Edge to Edge”.
If you are not sure about this, please refer to your Printer Reference User‟s Guide.
Values allowed:
 Checked: supported.
 Unchecked: Unsupported.
7.2.4.6. Suplex
This parameter selects Duplex printing on target tray whatever duplex is selected or not. It means all the
pages will be printed in duplex mode. This option may be useful if the input tray is fed with letterhead
paper.
7.2.4.7. Paper Size

Select paper size for each physical printer paper tray.
Available sizes:
 Custom
 Letter
 Legal
 A4
 Exec
 Com10
 Monarch
 C5
 DL
 A3
 A5
 Ledger
 B4JIS
 B5JIS
 B6JIS

Note : When custom paper size is selected, please read the hereafter table.
Unit : 300*Page Length or Page Width.
=> For example: Letter = P L = 11.00*300 = 3300
P W = 8.5*300 = 2550
Size Page Length Page Width Physical Margin Escape Sequence

A4 3507 2480 50 ^&l26A
LETTER 3300 2550 50 ^&l2A
LEGAL 4200 2550 50 ^&l3A
EXECUTIVE 3150 2175 50 ^&l1A
MONARCH 2250 1162 50 ^&l80A
COM-10 2850 1237 50 ^&l81A
DL 2598 1299 50 ^&l90A
C5 2704 1913 50 ^&l91A
A3 4960 3507 50 ^&l27A
A4_E2E 3507 2480 0 ^&l26A
A4_WIDE 3507 2480 40 ^&l26A
LETTER_E2E 3300 2550 0 ^&l2A
A5 2480 1748 50 ^&l13A
JISB4 4299 3035 50 ^&l46A
JISB5 3035 2150 50 ^&l12A
LEDGER 5100 3300 50 ^&l6A
INVOICE 2550 1650 50 ^&l15A
FOLIO 3900 2550 50 ^&l9A
QUARTO 3248 2550 50 ^&l2A
COM-9 2662 1162 50 ^&l89A
ISOB5 2952 2078 50 ^&l100A
A5 2480 1753 50 ^&l4A
A6 1753 1240 50 ^&l203A
7.2.4.8. Paper Length

This parameter is only available when Custom is selected on Page Size parameter.
Indicates the page length (refer to the above table).
7.2.4.9. Page Width

Indicates the page width (refer to the above table).
7.2.4.10.Physical Margin
Indicates the physical margin (refer to the above table).

7.2.4.11.Escape Sequence
Indicates the PCL Escape command for selecting the correct paper size (refer to the above table).
7.2.4.12.Tray Offset
Values allowed:
 For all Tray: Checked, all “Front Offsets”, “Back Offsets” and “Compression” will be apply to all
Printer Tray.
 Per Tray: Checked, when you want to apply special values to “Front Offsets”, “Back Offsets” and
“Compression” parameters for a specific Printer tray.
7.2.4.13.Front Left Offset

Are used to move the printed logical page within the physical page. Front offsets apply to the front page.
Back offsets apply to the back page when printing duplex. When setting these parameters, always consider
the page in the portrait orientation. The increment is 1/100 inch (a value of 10 = one character width at 10
CPI pith = 2.54 cm).
This parameter selects the horizontal offset of the logical page on the physical page.
Values allowed:
 -127 to + 127 (in 1/100 of an inch)
th
 0*
7.2.4.14.Front Top Offset

This parameter selects the vertical offset of the logical page on the physical page.
Values allowed:
 -127 to + 127 (in 1/100 of an inch)
th
 0*

7.2.4.15.Back Left Offset
This parameter selects the horizontal offset of the logical page on the physical page for the back page in
duplex mode.
Values allowed:
 -127 to + 127 (in 1/100 of an inch)
th
 0*
7.2.4.16.Back Top Offset

This parameter selects the vertical offset of the logical page on the physical page for the back page in
duplex mode.
Values allowed:
 -127 to + 127 (in 1/100 of an inch)
th
 0*
7.2.4.17.Horizontal Compression
Available only with printer language set to BMP
This parameter selects the horizontal reduction and allows you to compress the page. The increment is
1/300 of inch. Used to fit logical page in physical page by pixel suppression.
Values allowed:
 0 to 999
 0*
7.2.4.18.Vertical Compression
Available only with printer language set to BMP
This parameter selects the vertical reduction and allows you to compress the page. The increment is 1/300
of inch. Used to fit logical page in physical page by pixel suppression.
Values allowed:
 0 to 999
 0*
7.2.4.19.Scale Ratio
(Percentage) (available only with printer language set to PS or PDF)
Used to fit logical page in physical page. Default is 100 (no compression).
7.2.4.20.Duplex Support
Specify if the target printer has a duplex feature installed.
7.2.4.21.Nup Support
Specify if your application selects this functionality.

7.2.5. Parser - Output trays window
7.2.5.1. AFP Tray

Tray number selected from the host application
7.2.5.2. Printer Tray

Trays available on the printer (set according to the printer profile)
7.2.5.3. Stapling Mode

When selecting an output tray from the host application it is possible to address a printer specific tray and
force a stapling option even when stapling is not specified in the application. This feature is available
according to the printer profile.
7.2.5.4. Punching Mode

When selecting an output tray from the host application it is possible to address a printer specific tray and
force a punching option even when punching is not specified in the application. This feature is available
according to the printer profile.
7.2.5.5. Split on Stapling

Values allowed:
 Checked: In case of “Non stapling” job, activate this option.
 Not checked: default value
7.2.5.6. Split on Punching

Values allowed:
 Checked: In case of “Non punching” job, activate this option.
 Not checked: default value

7.2.6. Parser - Utilities window
7.2.6.1. Trace Option

Values allowed:
 Inactive (default) No action
 Record For technical support only.
This option is used to record the complete incoming IPDS data stream.
 Replay For technical support only.
This option is used to replay an IPDS recorded with The Blue Server.
7.2.6.2. Job Header file

A file (with extension TXT, PJL or what else) can be sent at the beginning of a printout. Useful for sending
specific Escape or PJL commands.
Default directory path: ..\MPI Blue Server\MPI Parser\nt
7.2.6.3. Job Trailer file

A file (with extension TXT, PJL or what else) can be sent at the end of a printout. Useful for sending
specific Escape or PJL commands.
Default directory path: ..\MPI Blue Server\MPI Parser\nt
7.2.6.4. Job Automate


7.2.6.5. Job Name
Job Name function is only available when the output used is PDF, PS2, PS3, PCL or BMP but stored in
a file.
When the Job Name functionality is not activated, test result in the target directory is:
7.2.6.5.1.Host Job Name - %JOBNAME%

OS400 : The ten-character EBCDIC spooled file name associated with the file being printed.
MVS : The eight-character EBCDIC job name parameter associated with the data set being printed.
Test result in the target directory :
Note :
If the same JOBNAME is used for all jobs, just the latest job will be saved.

7.2.6.5.2.Host Job Identifier - %JOBID%
OS400 : The four-character EBCDIC spooled file name associated with the file being printed.
MVS : The eight-character EBCDIC job identifier number parameter associated with the data set being
printed.
VM : The four-character EBCDIC spool identification number (spooled) of the print file.

7.2.6.5.3.Job Form Name - %FORM%
OS400 : The ten-character EBCDIC forms name parameter associated with the file being printed.
MVS : The eight-character EBCDIC job FORMS parameter associated with the data set being printed.
VM : The four-character EBCDIC spool identification number (spooled) of the print file.
Note :
If the same FORMS is used for all jobs, just the latest job will be saved.

7.2.6.5.4.Host User Name - %USERNAME%
OS400 : The ten-character EBCDIC user name associated with the file being printed.
VM : The eight-character EBCDIC user id of the print file originator.

7.2.6.5.5.Host Library Name - %LIBNAME%
OS400 : The ten-character EBCDIC library name associated with the specified output queue.
Note :
If the same LIBNAME is used for all jobs, just the latest job will be saved.

7.2.6.5.6.Host Device Name - %DEVNAME%
OS400 : The ten-character EBCDIC output queue name.
Note :
If the same DEVNAME is used for all jobs, just the latest job will be saved.

7.2.6.5.7.Host Session Identifier - %SESSID%
OS400 : The six-character EBCDIC job number associated with the file being printed.

7.2.6.5.8.Host Session Name - %SESSNAME%
OS400 : The ten-character EBCDIC job name associated with the file being printed.

7.2.6.5.9.AFP Name - %AFPNAME%
InfoPrint : The job name associated with the file being printed.
Test result in the target directory:

Blue Server specific functionalities
7.2.6.5.10.Blue Server Job Number - %INCREMENT%
Blue Server : Increment Job number associated with the host file being printed.
Note :
In our case, we have just printed 3 jobs from the host.

7.2.6.5.11.Blue Server Printer Name - %PRINTERNAME%
Blue Server : Blue Server printer name (without extension al4).
Note :
Just the latest job is saved.

7.2.6.5.12.Blue Server Date - %DATE%
Blue Server : The standard format used is YYYYMMDD
YYYY Year
MM Month
DD Day
Note :
Just the latest job is saved.

7.2.6.5.13.Blue Server Time - %TIME%
Blue Server : The standard format used is xxHyyMzzSuuuu
xxH Hour
yyM Minute
zzS Second

7.2.6.5.14.Blue Server Pagerange - %PAGERANGE%
Blue Server : Allows to display page range.

7.2.6.5.15.Blue Server Frompage to page - %FROMPAGE% %TOPAGE%
Blue Server : Allows to display option “from” -> “to”.

7.2.6.5.16.Blue Server Sheetrange - %SHEETRANGE%
Blue Server : Allows to display Sheet range.

7.2.6.5.17.Blue Server From sheet to sheet - %FROMSHEET% %TOSHEET%
Blue Server : Allows to display option “from” -> “to”.
Note: Additional information,

%FROMPAGE%_%TOPAGE% => this option will display the physical page in the queue
%FROMSHEET%_%TOSHEET% => this option will display the sheet in the queue

7.2.6.5.18.Mixed options
When some Job Name functions such as :
- JOBNAME,
- FORMS
- LIBNAME
- DEVNAME
- PRINTERNAME
- DATE
stored one job in a spool, two or three (or more) Job Name functions can be used together.
7.2.6.6. Windows Command

For technical support only. When this option is checked, a MSDos window is opened to display the MPI
Parser activity.
Do not close the MSDos window this would stop the Blue Server Parser Service.

7.2.7. Parser - Color window
Warning

This parameter is only available when PS2, PS3, PDF or PPML is selected on Output Language
parameter.
7.2.7.1. Color Palette

AFP Hi-lite/RGB Color correspondence table. Used to map AFP colors with printer colors.
This table is only used for some High-speed hi-lite color printers.

7.2.8. Parser - Mail window
Warning

This window is available when Output Language is set to PDF. The AFP/IPDS document is then
transformed to PDF and is sent as an attached file to an E-mail address.
7.2.8.1. Outgoing mail server (SMTP)

DNS name or IP address of the mail server providing the SMTP service.
7.2.8.2. Email Service
It is the name of the email sender. This name is located in the address book of your Lotus Notes, Outlook
Express…
7.2.8.3. Email Sender
Internet address of the email sender.
7.2.8.4. Email Destination
Internet address of the email destination.
7.2.8.5. Bcc Mail Address
Internet address of the bcc (blind carbon copy) email destination.
7.2.8.6. Subject
Enter the subject you want to be sent with the email.
7.2.8.7. Message
Enter the message you want to be sent with the email delimited by “ character. The message can contains
several lines and Blue Server variables.
Example :
Example of Message:
This,0x20,mail,0x20,has,0x20,been,0x20,generated,0x20,wiht,0x20,BlueServer.,0x0
d,0x0a,On,0x20,%DATE%,0x20,at,0x20,%TIME%

7.2.9. Parser - PDF window
Warning

This window is available when Output Language is set to PDF. The AFP/IPDS document is then
transformed to PDF and put to a local drive and patch directory.
1. From a Blue Server GUI,
2. Selecting “Destination” tab, and checking “PDF encryption”, you will get:
3. Selecting “Options” box, you will get :

7.2.9.1. Encryption Level
Values allowed:
 40 bits: (default) No action
 128 bits: strong encryption.
7.2.9.2. Permanent editing lock

 Checked: no more modification such as:
- Change the document,
- Document Assembly
- Filling of form Fields
- Signing
are available.
7.2.9.3. Administrator Password

Password length: 20 alphanumeric characters.
Entering an Administrator password, this password is necessary for opening the PDF file.
7.2.9.4. User Password

Entering a User password, this password is necessary for opening the PDF file.
7.2.9.5. Printing allowed

 Unchecked: this option is not available.
 Checked: this option is available.
7.2.9.6. Changes allowed

7.2.9.7. Enable copying of content

 Checked: this options is available.
Allows with Acrobat these options:

- Content Copying or Extraction and
- Content Extraction for Assembly.
Notes:
 For “Changes allowed” and “Enable copying of content” options, if a USER password active, an
ADMINISTRATOR password is mandatory for activating the options.
For opening the PDF file, the USER password is necessary, but for activating other options, the
ADMINISTRATOR password is necessary.


8. Router AS/400 LPD-SCS
8.1. MPI Router functions
The MPI Router converts the Host SCS data to PCL and forwards it the to the LAN printers.
From this Menu you can:


 And you will get the following display:
 Select “LPD SCS”.

Note
Usually, it must be the same name of the Remote OUTQ created on the AS/400 or Mainframe.

 And you will get directly the following display:
8.2.1. Router LPD/SCS - information window

You will get the following display:

Sample is the default.

Used to select a specific printer group. Useful for managing different server.
8.2.1.3. Comments
8.2.2. Router LPD/SCS - connection window

8.2.2.1. LPD Queue Name

Must match with the Remote OUTQ created on the AS/400.

Values allowed :
 Windows Queue when the printer destination is a Windows Queue.
 TCP/IP Port when the printer destination is an IP printer configuring on the LAN.
 File when you want to record an output specific trace.
 LPR Port when the printer destination is a LPR port.
Note
IP port parameter is automatically set to 515.

8.2.2.3. Printer IP Address
Is the IP address of the printer.
8.2.2.4. IP Port
Note

Axis box 9100
9101 (LPT2)
9102 (LPT3)
Kyocera 9100
9102 (LPT2),
9103 (Serial)
QMS card 35

8.2.3. Router LPD/SCS - control window
8.2.3.1. ASCII Printer (X2)

This option is used to define which type of printer is connected to the kit.
Values allowed :
 0 ASCII
 1* HP (PCL)
 2 Xerox (Iso mode)
 3 IBM-PPDS
 4 Canon LBP8 (Iso)
 5 Epson LQ2500 (PC set 2)
 6 Epson FX800 (PC set 2)
 8 IBM Proprinter XL24e
 9 Kyocera (PCL mode)
 10 XPPM (only for Xerox printer)
 11 ASCII GENERIC

8.2.3.2. Printer character Set (X10)
This option allows any printer to be used with any other printer character set.
Values allowed:
 0 ASCII 7 bits
 1 HP Roman-8
 2 ISO 6937 (Xerox)
 3 PC-850
 4 ISO (Canon)
 5 PC Set 2 (PC-8)
 6 Epson FX
 8 IBM Proprinter
8.2.3.3. IBM Printer Emulation (X16)

This option is used to define the type of IBM printer that is emulated.
Values allowed:
 0,6 3812 (5219 emulation) in non OS400 mode
 1,6* IBM 3812 (5219 mode) in OS400 mode
 0,7 IBM 4214 in non OS400 mode
 1,7 IBM 4214 in OS400 mode
 0,16 LU1-SCS (for mainframe connection with Interlink IP protocol)
 0,17 ASCII (for UNIX connection)
8.2.3.4. IBM System language (X19)

It defines the language used for the text translation. It must be selected according to the control unit
configured language.
Values allowed:
 0* Multinational
 1 US
 2 Germany
 3 Belgium
 4 Brazil
 5 Canadian
 6 Denmark/Norway
 7 Finland/Sweden
 8 France
 9 Italy
 10 Japan
 11 Portuguese
 12 Spain
 13 Spanish Speaking
 14 UK
 252 Hebrew Bulletin
 253 Old Hebrew
 254 Hebrew

8.2.3.5. Paper Orientation (X28)
Parameter X-28 defines the options used for the page rotation/reduction. It defines the format of the paper
used by the printer, the default orientation of printer tray 1 and tray 2, and whether these orientations are
immutable or are defaults, depending on the automatic orientation option.
Values allowed :
 0x008A Automatic, A4, COR, COR
 0x00EA Automatic, Letter, COR, COR
 0x100 No Automatic, A4, Portrait, Portrait
 0x160 No Automatic, Letter, Portrait, Portrait
 0x028A No Quality, Automatic, A4, COR, COR
 0x02EA No Quality, Automatic, Letter, COR, COR
 Value Specified in File (only accessible with an ASCII editor)
8.2.3.6. Flash Directory

Used only for specific functionality.
8.2.3.7. Trace Option/Dump (X14)

This option defines the type of dump mode helpful in finding out the origin of printout defects.
Values allowed:
 0x00* No dump
 0x01 EBCDIC dump with translation
 0x02 BINARY dump (only used for recording a trace file, in conjunction with parameter
“Destination Type” setting to “File”
 0x03 ASCII Dump with translation
 0x11 EBCDIC dump without translation
 0x13 ASCII dump without translation

9. Router Mainframe SCS/IPDS over SNA server
9.1. MPI Router functions
The MPI Router has two functions:
SCS printing
It converts the Host SCS data to PCL and forwards it the to the LAN printers.
Routing IPDS
The MPI Router routes the IPDS data stream either to the LAN printers equipped with the MPI IPDS
SIMM/DIMM or the MPI Parser.
9.2. The MPI Router Main Menu



 Select “SNA Mainframe”.

Note
Usually, it must be the same name of the LU Name of the SNA server.

 And you will get directly the following display:
9.3.1. SNA Mainframe - Information window



9.3.1.3. Comments
9.3.2. SNA Mainframe - connection window

9.3.2.1. LU Name
Name of the „LU Name‟ configuring on the SNA server.

Values allowed:
 Parser when using the MPI Parser to print IPDS.
Note

9.3.2.3. Queue name
Value : Empty
 For only SCS printer emulation :
Type "//Server_Name/NT_queue_name" when the printer destination is a NT Queue
Empty if you prefer to use an IP printer address.
 For only SCS and IPDS printer emulation :
Type "//Server_Name/NT_queue_name" when the printer destination is a NT Queue for only SCS
printout.
Empty if you prefer to use the Parser configuration.
Note
 For the IPDS printout, the Parser configuration is always used.
 With the Parser configuration, you can print SCS and IPDS through an NT queue or an IP Printer
Address.
9.3.2.4. IP Address
 For only SCS printer emulation :
Is the IP address of the printer.
 For only SCS and IPDS printer emulation :
Is the IP address of the NT server where is running the Parser.
It can be the same IP address of the NT machine or a remote NT server.
Note
IP protocol must be configured and started on both servers.

9.3.2.5. IP Port
Note

Axis box 9100
9101 (LPT2)
9102 (LPT3)
Kyocera 9100
9102 (LPT2),
9103 (Serial)
QMS card 35

9.3.3. SNA Mainframe - IPDS setting window
9.3.3.1. Printer Emulation

This parameter selects the IBM printer emulation.
Values allowed :
 3812 (240 dpi)
 4028 (300 dpi)

9.3.3.2. Code Page
This parameter selects the default Code Page for the country:
Code Page correspondance :
Country Code Page

USA/Canada 37
US ASCII-L 38
Canadian French 260
Austria/Germany 273
Belgium 274
Brazil 275
Denmark/Norway 277
Finland/Sweden 278
Italy 280
Japan-English 281
Portugal 282
Spanish-Speaking 284
United Kingdom 285
Austria/Germany (alternate) 286
Denmark/Norway (alternate) 287
Finland/Sweden (alternate) 288
Spain (alternate) 289
Japan-Katakana 290
France 297
English ASCII 367
Arabic 420
Greek 1 423
Hebrew 1 424
Personal Computer (PC) 437
International Set 5 500
Hebrew 2 803
Portugal (alternate) 831
Latin 2 870
Iceland 871
Greek 2 875
Cyrillic 880
Turkish 1 905
Turkish 2 1026
9.3.3.3. Code Page Version

This parameter indicates the version of the code page.
Some of the code pages supported by the printer are available in two versions. Certain characters differ
between versions of the same code page.
If the character , ÷, =, © are not printing correctly, change the default code page.
Values allowed :
 0
 1

9.3.3.4. Dynamic Sharing
This parameter allows to select the dynamic sharing option.
Values allowed :
 Yes*
 No
9.3.3.5. Standby Time

This parameter allows to set the timeout before switching from the SNA mode to the LAN mode.
The time is set in seconds
Values allowed:
 0 to 990
 50*
9.3.4. SNA Mainframe - Paper Controls window

9.3.4.1. Paper Size

This parameter selects the paper size.
Values allowed :
 Letter
 Legal
 A4
 Excec
 Cm10
 Monarch
 C5
 DL
 B5
 A3

9.3.4.2. Main Paper Tray
This parameter is used to select if the primary paper tray is the upper one or the lower one (choose lower
when the large capacity feeder is installed).
Values allowed :
 Upper* The upper paper tray is used as primary tray (default tray)
 Lower The Lower paper tray is used as primary tray.
9.3.4.3. Out Paper Tray

This parameter is used to select if the output paper bin is the upper one or the lower one (the lower one is
located at the back side of the printer)
Choose the lower one when the large capacity feeder is installed.
Values allowed :
 Upper* The upper paper bin is used to collect the printed pages.
 Lower The Lower paper bin is used to collect the printed pages.
9.3.4.4. Front Top

This parameter selects the vertical offset of the logical page on the physical page.
Values allowed :
 -127 to + 128 (in 1/100 of an inch)
th
 0*
9.3.4.5. Front Left

This parameter selects the horizontal offset of the logical page on the physical page.
Values allowed :
 -127 to + 128 (in 1/100 of an inch)
th
 0*
9.3.4.6. Back Top

This parameter selects the vertical offset of the logical page on the physical page for the back page in
duplex mode.
Values allowed :
 -127 to + 128 (in 1/100 of an inch)
th
 0*

9.3.4.7. Back Left
This parameter selects the horizontal offset of the logical page on the physical page for the back page in
duplex mode.
Values allowed :
 -127 to + 128 (in 1/100 of an inch)
th
 0*
9.3.4.8. Duplex
9.3.4.9. Suplex on Manuel Tray

This parameter selects “duplex” printing on the printer tray whatever duplex is selected or not. It means
that all pages will be printed in duplex mode.
9.3.4.10.Suplex on Lower Tray

9.3.4.11.Suplex on Upper Tray

Note
These options may be useful if a printer tray is fed with letter head paper.

9.3.5. SNA Mainframe - SCS Settings window
9.3.5.1. End of Line Option (X1)

This option defines the action at the end of a line.
Values allowed :
 0 No action at the end of the line.
 1 Automatic sending of NL (New Line) at MPP position (Maximum Print
Position).
 2* NL sent at MPP position, if neither CR nor LF.
9.3.5.2. End of Page Option (X2)

This option defines the action at the end of a page.
Values allowed :
 0 No Form Feed (FF) added at MPL.
 1* Form Feed at MPL, if not already at 1st of physical page.

9.3.5.3. IBM System Language (X3)
This option defines the language.
Values allowed :
 0* English (US)
 1 International
 2 English (UK)
 3 Canadian bilingual
 4 German/Austrian
 5 German/Austrian alternate
 6 Danish/Norwegian
 7 Danish/Norwegian alternate
 8 Finnish/Swedish
 9 Finnish/Swedish alternate
 10 French
 11 French AZERTY 105
 12 Swiss French/Swiss German
 13 Belgian
 14 Italian
 15 Portuguese
 16 Brazilian
 17 Spanish
 18 Spanish alternate
 19 Spanish speaking
 20 Japanese (English)
 21 Multinational (P500)
 22 Portuguese alternate
 23 Canadian French
 24 Old Hebrew
 25 New Hebrew
 26 Bulletin Hebrew
9.3.5.4. Printer Form Length (X6)

This option defines the maximum number of vertical lines which can be printed on each physical form
Values allowed :
 0 to 255 Printer form length.
64*
9.3.5.5. MPL Default Value (X14)

This option is a page-formatting parameter that can be sent by the host in SCS mode. X-14 is taken into
account only if the host has not sent any MPL. It defines the maximum number of lines, which can be
printed on each form.
Values allowed :
 0 to 255 Maximum Print Line
66*

9.3.5.6. Printing Format on First Paper Tray (X28)
This option specifies the text printing format on tray one.
Values allowed :
Column Line
X-28 Orient. Format number number Value
Portrait P - MPP MPL 0*
Landscape L - MPP MPL 1
Normal C.O.R L - MPP MPL 2
User C.O.R - S94 - - 3
Spec C.O.R P A4 80 66 4
Spec C.O.R P LETTER 80 66 5
Spec C.O.R P A4 80 88 6
Spec C.O.R P A4 132 66 8
Spec C.O.R P A4 132 88 10
Spec C.O.R L A4 80 66 12
Spec C.O.R L LETTER 80 66 13
Spec C.O.R L A4 80 88 14
Spec C.O.R L A4 132 66 16
Spec C.O.R L A4 132 88 18
Spec C.O.R L A4 198 66 20
Spec C.O.R L A4 198 88 22
Spec C.O.R P A4 80 72 24
Spec C.O.R P A4 132 72 26
Spec C.O.R L A4 132 72 28
Spec C.O.R L A4 198 72 30
9.3.5.7. Printer Character Set (X82)

This option allows any characters to be used with the printer.
Values allowed :
 0* Roman 8
 1 PC set 2 (PC8)
 2 PC 850
 3 ISO character set (Xerox)
 4 ASCII Hebrew 7 bits
 5 ASCII Hebrew PC set
 6 ASCII Hebrew HP Roman
9.3.5.8. FSL Partial Mode

This option is only used for specific functions (FSL commands).
9.3.5.9. Evolution
This option is only used with the module Evolution.

9.3.6. Traces Options window
9.3.6.1. File Name

Enter a name (8 characters maximum)
9.3.6.2. Tracing Mode

This option is used to activate a trace.
Values allowed:
 0* Disable
 1 Enable
 2 Replay
9.3.6.3. Trace Flip Length

This option is used to create a file with a maximum length.
Values allowed:
 100000 to 1000000
9.3.6.4. Dump Mode

Values allowed:
 0* Disable
 1 Input
 2 Output
9.3.6.5. Reset Factory Default

This option is only used to reset all parameters to the default value.


10. Router Telnet 5250 or 3270
10.1. MPI Router Telnet functions
The MPI Router converts the Host SCS data to PCL and forwards it the to the LAN printers.
10.2. The MPI Router Telnet Main Menu


 Select “TELNET 3287”.

Note
Usually, it must be the same name of the Device created on the AS/400 or Mainframe.

And you will get directly the following display:
10.3.1.Router Telnet - Information window

10.3.1.1.Profile Name
10.3.1.2.Printer Group
10.3.1.3.Comments
10.3.2.Router Telnet 3270 – Telnet window

10.3.2.1.Telnet Type
Select Telnet 3270 for mainframe connection
Select Telnet 5250 for AS/400 connection
10.3.2.2.Server IP Address
Enter the mainframe IP address.
10.3.2.3.Telnet IP Port
Leave this value to 23, this is the default value for Telnet communication.
10.3.2.4.LU Name
Must match with the LU used on the mainframe side.

10.3.2.5.Telnet TimeOut
Default value in 120 seconds.
Specifies the amount of time to wait, after the last page of the last ready spooled file has printed, before
releasing the printer.
10.3.2.6.Trace Option
Values allowed:
 Inactive (default)
 Record: Allow you to record a trace file for technical support
 Replay: Used to replay a trace file recorded with the record trace option.
10.3.3.Router Telnet 3270 – Connection window

10.3.3.1.Destination Type
Values allowed:
 Parser when using the MPI Parser to print IPDS.
Note

10.3.3.2.IP Port
Note

Axis box 9100
9101 (LPT2)
9102 (LPT3)
Kyocera 9100
9102 (LPT2),
9103 (Serial)
QMS card 35

10.3.4.Router Telnet 3270 – Control window
10.3.4.1.ASCII Printer (X2)

This option is used to define which type of printer is connected to the kit.
Values allowed:
 0* ASCII
 1 HP (PCL)
 2 Xerox (Iso mode)
 3 IBM-PPDS
 4 Canon LBP8 (Iso)
 5 Epson LQ2500 (PC set 2)
 6 Epson FX800 (PC set 2)
 8 IBM Proprinter XL24e
 9 Kyocera (PCL mode)
 10 XPPM (only for Xerox printer)
 11 ASCII GENERIC

10.3.4.2.Printer character Set (X10)
This option allows any printer to be used with any other printer character set.
Values allowed:
 0 ASCII 7 bits
 1 HP Roman-8
 2 ISO 6937 (Xerox)
 3 PC-850
 4 ISO (Canon)
 5 PC Set 2 (PC-8)
 6 Epson FX
 8 IBM Proprinter
10.3.4.3.IBM Printer Emulation (X16)

This option is used to define the type of IBM printer that is emulated.
Values allowed:
 0,6 3812 (5219 emulation) in non OS400 mode
 1,6* IBM 3812 (5219 mode) in OS400 mode
 0,7 IBM 4214 in non OS400 mode
 1,7 IBM 4214 in OS400 mode
 0,16 LU1-SCS (for mainframe connection with Interlink IP protocol)
 0,17 ASCII (for UNIX connection)
10.3.4.4.IBM System language (X19)

It defines the language used for the text translation. It must be selected according to the control unit
configured language.
Values allowed:
 0* Multinational
 1 US
 2 Germany
 3 Belgium
 4 Brazil
 5 Canadian
 6 Denmark/Norway
 7 Finland/Sweden
 8 France
 9 Italy
 10 Japan
 11 Portuguese
 12 Spain
 13 Spanish Speaking
 14 UK
 252 Hebrew Bulletin
 253 Old Hebrew
 254 Hebrew

10.3.4.5.Paper Orientation (X28)
Parameter X-28 defines the options used for the page rotation/reduction. It defines the format of the paper
used by the printer, the default orientation of printer tray 1 and tray 2, and whether these orientations are
immutable or are defaults, depending on the automatic orientation option.
Values allowed:
 0x008A Automatic, A4, COR, COR
 0x00EA Automatic, Letter, COR, COR
 0x100 No Automatic, A4, Portrait, Portrait
 0x160 No Automatic, Letter, Portrait, Portrait
 0x028A No Quality, Automatic, A4, COR, COR
 0x02EA No Quality, Automatic, Letter, COR, COR
 Value Specified in File (only accessible with an ASCII editor)
10.3.4.6.Flash Directory
Used only for specific functionality.
10.3.4.7.Trace Option/Dump (X14)

Values allowed:
 0x00* No dump
 0x01 EBCDIC dump with translation
 0x02 BINARY dump (only used for recording a trace file, in conjunction with parameter
“Destination Type” setting to “File”
 0x03 ASCII Dump with translation
 0x11 EBCDIC dump without translation
 0x13 ASCII dump without translation


11. AFP/IPDS Compatibility
11.1. Compatible Resident Fonts
11.1.1.Blue Server - Parser
The Blue Server contains the IPDS scalable internal fonts, compatible with the new resident fonts of the
IBM printers.
They are listed in the tables below. If the resident font is selected by the application, the FGID and the point
size are the font identifiers.
IPDS – Resident scalable font set
FGID Font Name

304 Gothic
305 OCR A
306 OCR B
307 APL
318 Prestige Bold
319 Prestige Italic
322 APL Bold
400 Letter Gothic
404 Letter Gothic Bold
416 Courier Roman Medium
420 Courier Roman Bold
424 Courier Roman Bold
428 Courier italic old
432 Prestige
2304 Helvetica Roman Medium
2305 Helvetica Roman Bold
2306 Helvetica Italic Medium
2307 Helvetica Italic Bold
2308 Times New Roman Medium
2309 Times New Roman Bold
2310 Times New Roman Italic Medium
2311 Times New Roman Italic Bold
20224 Boldface
Parser : Internal fonts

11.2. Latin 1 - Euro Code Pages
This table displays, for each country, the code pages with and without the € currency.
Supported Languages Regular Code Page Euro Code Page
USA, Canada 37 1140

Austria, Germany 273 1141
Denmark, Norway 277 1142
Finland, Sweden 278 1143
Italy 280 1144
Spain, Latin America 284 1145
UK 285 1146
France 297 1147
International 500 1148
Iceland 871 1149
With AS/400 when you want to select a Euro code page (with Printer file, Office/400, Device definition..) set
the CHRID parameter to 0695 - 114X :
Where:
- 695 is the Graphic Character Set
- 114X is the Euro code page (1140 for USA, 1141 Germany…)

12. Trouble shooting
12.1. How to get the Blue Server “Registering Number” before installation
12.1.1.Description
1. When you plan to install Blue Server on a production server, despite Blue Server is not installed
yet, it is possible to get the “Registering Number” of this server. Forwarding the registering number
to MPI will allow you to get the license keys before you install Blue Server. When the installation is
performed, you just have to copy the License keys file “keys.cfg” to the directory
“..\MPI Blue Server\MPI License”.
2. If you have planned to install Blue Server on another WorkStation / Server, you must run again the
MLRegister.exe
 For creating a permanent or temporary license, these information must be provided:
- Products (Parser, Router LPD, Router Telnet 3270/5250, Router SNA Mainframe…)
- Numbers of printers,
Only for Parser:
- Printer speed group,
- Functionalities such as : Full Color, PDF, Job Automat, Mail, Tiff, Fax
Upon reception of these information, a permanent or temporary license is created.
 When a temporary / permanent license is activated, do not load more printers than the quantity
asked. Otherwise, all the products will stop after 15 days.
 Always ask a new temporary license before the end of the test period, even if you haven‟t finish to
test it completely.
12.1.2.Procedure
 Copy the MLRegister.exe file to the WorkStation / Server where the Blue Server is planned to be
installed,
 Execute the MLRegister.exe utility. You get this display. The Registering Number is a unique
number.
 Make a copy / paste of this Registering Number and forward to MPI TECH sales or supports or your
local MPI TECH vendor.

12.2. During the installation
12.2.1.First installation
Action:
 Before installing the Blue Server, check the user access on the target station or server.
This user must be able to create services, and share directory.
12.2.2.During an Update
12.2.2.1.MPI Services – Proccess not stopped
Action:
Before installing the newest Blue Server version, check on the station or server:
 All MPI Services must be stopped,
 All the printers must unloaded,
 The Blue Server interface must be closed,
 MPIMigrate.EXE must be stopped (Check on Process folder of the Task Manager).
12.2.2.2.Error 1723
Action:
OS : Windows 2000 or Windows 2003
Solution : this problem is a MSI installer 3.1 not updated.

12.3. How to activate a correct Blue Server license
12.3.1.Description
Parser job format

PDF
PDF/A-1b:2005
PCL
PostScript
BMP printing
TIFF
E-mail/FAX PostScript (B&W) printing
Image
PCL5 printing
Blue Server
Host
PostScript (Color) printing PDF printing
For each configuration a specific license should be available.

12.3.2.Explanation
1. For each Output Language, a specific license should be available:
 Standard license : BMP, PCL5, PS2 – black & white and PS3 – black & white.
 Specific license : PDF, TIFF, PPML, IPDS, PDF/A-1 b:2005, IMAGE
2. For each License Group, a specific license should be available:

 Printer Group:
- Group 1 [1 – 55]
- Group 2 [55 – 85]
- Group 3 [86 – 120]
- Group 4 [121 – 200]
- Group [no limit]
 Printer Speed (ppm)

3. For each functionality, a specific license should be available:
 When on of this output is selected: PostScript (PS2 or PS3), PDF, PPML and PDF/A-1 b:2005,
a “Colors” tab is added.
Checking Color License => a license is requested.
 When PDF language is selected => a license is requested, a “Mail” tab is added.
Configuring this section => a license is requested.

 From “Destination” tab, a new functionality is displayed, Data Extraction.
Selecting String to Fax or Data Extraction => a license is requested.
Note: Using Data Extraction -> Send to Fax or String Extraction use the same license
information (Fax license is used).
 From “Host” tab, a new functionality is displayed, Activate String Indexer.
Checking Activate string Indexer => a license is requested.

 From “Host” tab, a new functionality is displayed, Share IPDS with others Sessions.
Checking Share IPDS with other Sessions => a license is requested.
 From “Utilities” tab, a new functionality is displayed, Backup Server Sertup.

Configuring Backup Server Setup => a license is requested.
 From “Tools” bar, a new functionality is displayed, Job Automate.

Configuring Job Automate => a license is requested.

12.4. How to update Blue Server
12.4.1.From V5.xx to V5.80 or higher
For all Blue Server version, please contact MPI TECH or your local MPI TECH vendor for this
update.
WARNING
After this update and starting your MPI License service, a new registering number is displayed.
All your previous agreement number(s) are no longer valid.
Therefore, please call MPI Tech to obtain your new agreement number(s).
12.4.1.1.Introduction
Downloading from the www.mpitech.com or installing from a new CD-Rom, please execute the following
steps:
12.4.1.2.Getting started
 On the main display of Blue Server, check the Blue Server version (top line – left side)

 Unload all printers
 Stop all MPI services:
- MPI Licenses Service
- MPI Parser Service
- MPI Router AS400 IPDS
- MPI Router AS400 LPD
- MPI Router AS400 SCS
- MPI Router LPD Evolution
- MPI Router Mainframe
- MPI Router TELNET 3287
 Open your explorer, select this directory:
<Local drive>:\MPI Blue Server,
and copy to another drive or directory location for a back-up.
 Run a Blue Server installation from the zip file downloaded from the web site or from the CD-Rom.
“Blue_Server_NT\disk1\setup” .
This new installation will erase all old version(s).
 This new version will create automatically a new service: MPI File Server
 After this installation, it would be recommended to reboot your computer.
 After the reboot, your can check the new MPI Files Server. This MPI File Server Service must be
always started before starting the Blue Server V5.80.

 If this MPI Files Server is not operating, you will get this windows:
 Just start the MPI Files Server, then on Blue Server interface, press F5 to refresh and you will get this
new window:
 Before loading the printers, you need first to update the printers configuration.

 Select all the printers,
 use this specific icon for running the update,
 Then you get this dialog box:

 Select Yes
 Automatically all your old printers configuration will be saved to this specific directory:
For Parser configuration:
- <Local drive>:\MPI Blue Server\MPI Parser\pfn\backup
For the other printers configuration (LPD; Router SCS or IPDS, TELNET):
- <Local drive>:\MPI Blue Server\MPI Router\pfn\backup
 You can check on one or more printers configuration, that the configuration is still available.
 If everything looks correct, you can close the Blue Server interface, and restart again.
 Now you can load the printers configuration.
 Do not forget to call MPI Tech to obtain your new agreement number(s) at:
- By phone : +33 1 45 73 60 80 (technical department) or
- By mail : support.fr@mpitech.com
12.4.2.From V6.xx to V7.xx

For all Blue Server version, please contact MPI TECH or your local MPI TECH vendor for this
update.
WARNING
After this update and starting your MPI License service, a new registering number is displayed.
All your previous agreement number(s) are no longer valid.
Therefore, please call MPI Tech to obtain your new agreement number(s).
12.4.2.1.Important information about the new Blue Server and update process
Downloading from the www.mpitech.com or installing from a new CD-Rom, please execute the following
steps :
The Blue Server release includes fixes for the Router engine, Parser engine, license module and
Blue Server interface.
- You no longer can edit the licenses.cfg file (except for viewing). This file contains control
codes that are not visible through most text editors and may be corrupted if modified.
- The Main License Server (MLS) has been renamed to the Main License Daemon (MLD) and the
client (Secondary License Server - SLS) is now called a Main License Client (MLC).
- When upgrading the servers you should start with the local „administrator‟ server and then the
MLD. The remaining server can be upgraded in any order.
- The Blue Server version number has been changed to the following format 7.00.00xx

12.4.2.2.Uninstall process
This action must be done on the local workstation or server where the Blue Server is installed.
Execute the following steps :
 Open your Blue Server interface,
 Unload all the printers configuration,
 Stop all the MPI services :
- MPI Files Server
- MPI License Service
- MPI Parser Service
- MPI Router AS400 IPDS
- MPI Router AS400 SCS
- MPI Router LPD Evolution
- MPI Router Mainframe
- MPI Router TELNET3287
 Check for this process. If it is running, stop it.
From this point the server will be offline, meaning output is not possible.
Error messages may occur in licensing and on the host.
 Back all of the Parser configurations and Router Configurations and profiles to a directory outside of
the Blue Server structure :
- Parser configurations ..\MPI Blue Server\MPI Parser\pfn\*.pf4
- Router configurations ..\MPI Blue Server\MPI Router\pfn\*.pf2, pf6, pf7,
pf8
- Profile configurations ..\MPI Blue Server\MPI Parser\nt\*.*
..\MPI Blue Server\MPI Router\nt\*.*
 Run the Blue Server uninstall from the servers control panel „Add/Remove Programs‟ feature,
 Open your Windows Registry using regedit and delete the following keys :
HKEY_LOCAL_MACHINE → Software → MPI Blue Server
HKEY_LOCAL_MACHINE → Software → MPITech
 Delete the following file(s) from Windows Explorer (if the file exists) :
..\WINNT\Downloaded Installations\
any directory that contains a „The Blue Server V6.0.msi‟ file

 Delete the entire Blue Server directory structure from Windows Explorer. If a file or folder will not
delete because of a sharing violation please try the delete after reboot.
A server reboot is now required to insure all Blue Server mechanisms are stopped.
The steps above will insure that the new version is installed without existing files
from a previous installation.
 Please reboot now. Upon boot the Blue Server will be completely removed from your server.
12.4.2.3.Install process
After the server is back online install the new version of Blue Server. The InstallShield consists of the
following screens :
 Welcome Screen – click next
 License Agreement – accept and click next
 Customer Information – complete and click next
 Setup Type – choose custom and click next
 Custom Setup – choose the modules you want to install (note: MPI License and The Blue Server
must be installed on every server). Next choose the „Install To‟ directory at the bottom of this screen.
Click next.
 Ready to Install Program – click install
The file copy process will now run.
 Completed Screen – click finish
The Blue Server is now installed. If you are logged in remotely do not open the
local Blue Server interface. All changes and updates will be done from the
„administrator‟ PC(s).
 Copy back in the Parser configurations, Router configurations and profiles.

 Start the MPI License Service and set to automatic
 Start the MPI Parser or SNA Mainframe service and set to automatic.
Installation is complete for this server. You must do the preceding steps on all
servers.
12.4.2.4.Configuration and Update
 Open your local „administrator‟ Blue Server interface. This will be the PC from which you will monitor
all of the Blue Server servers.
 If the remote servers are not visible then you must install each by selecting „Add Server‟ from the
Config Menu.
 Select the first remote server, this should be the MLD. All of your printers should appear in the right
pane.
Select all of the printers and click the green and red recycle symbol in the top center to update the
configurations to the current release.

Do not load any printer yet.
 Right click on the MPI License Server in the upper left corner and select Licensing System.
 The Licensing System module will now open. From here you can view all of the licensing statistics,
enable the error log, set email alerts and migrate servers. Our first step is to migrate each server to
the main license server.
Migration simply means we will be pointing each remote server to the MLD server for license
validation.
 Select the migration tab. In the bottom left corner (To use the licensing server) enter the MLD‟s IP
address or DNS name.
 On the right side (Add MLC to list) enter the first servers IP address or DNS name to migrate and
click Add MLC. You will now see the server in the „Configure the following servers‟ field.
 Highlight this server and click Migrate in the bottom right corner.
 It is highly recommended that you verify the remote server properly accepted the migration request.
To do this you can edit the licenses.cfg file which resides in the
..\MPI Blue Server\MPI License\ directory on the remote server. The line that reads
MLDaemonIPAddress = should point to the MLD‟s IP address. When you are finished close the file
but do not save if prompted.
 Continue to do this until all of your remote servers are migrated. It is recommended that you also
migrate the MLD sever to point to its own IP address or DNS name.
 On each remote server restart the MPI License Service for the changes to take effect.
12.4.2.5.Finalizing
All servers are now updated, migrated and configured.
You now will need to begin loading printers.
Start with the Parsers and wait for host status in Blue Server to become available.
Next load the Routers. After about an hour of operation you should look at the licensing to verify servers
are reporting to the licensing module correctly.
12.4.3.Since Blue Server BSV7.03.0001_20070327

If your previous Blue Server V7 installation is lower than V7.03.001, we recommend :
to save your configuration files from ..\MPI Blue Server\MPI Router\pfn or ..\MPI Blue
Server\MPI Parser\pfn directory,
 uninstall this version,
 reboot your server/workstation, and
 re-install from our latest link (please contact MPI tech).

12.5. How to update configurations
12.5.1.Blue Server printer configurations and profiles
Each Blue Server printer configuration is stored in a file. The file name = the Blue Server Printer name and
the extension is pfx. X varies depending on the MPI product.
Pf1 = Router SNA AS/400 IPDS
Pf2 = Router Mainframe
Pf4 = Parser
Pf5 = Router SNA AS/400 SCS
Pf6 = Router LPD
Pf7 = Router LPD Evolution
Pf8 = Router Telnet
The printer configurations are stored in the directories:
<Local_Drive>:\MPI Blue Server\MPI Parser\pfn
<Local_Drive>:\MPI Blue Server\MPI Router\pfn
The Blue Server printer configurations are created from profiles. They are stored in the directory
C:\MPI Blue Server\MPI Router\nt
The default profile is sample.pfx. It is a text file which contains all the parameters with their default values. If
the sample.pfx defaults are not suitable for the customer printer creation (the default parameters do not
match the customer‟s requirements), it is possible to create new profiles.

While creating a new printer configuration from the GUI, you must give a new name and select the profile
you want to create the new printer from.
The new printer creation consists then in copying the selected profile from the \nt directory to the \pfn
directory and renames it with the name chosen.
12.5.2.MPI File Server service

MPI File Server service handles the configurations for the interface (no matter if it is local or remote)
The sample.pfx files are located in the directory C:\MPI Blue Server\The Blue Server. When the service
MPI File Server starts, it copies the Sample.pfx in the directories :
<Local_drive>:\MPI Blue Server\MPI Parser\nt
<Local_drive>:\MPI Blue Server\MPI Router\nt

12.5.2.1.Updating configurations
12.5.2.2.The printer configuration filter

The filter allows you to work with a subset of printer configurations. In order to activate the filter, use the
icon:
When you click on this icon, you get the filter window where you select the attributes of the filter:
In the above example, you will work with the printer configurations of the product “SNA Mainframe” and
with a name starting with PRT.
When the filter mode is activated, the filter icon turns green:

12.5.2.3.The Update Button
When a new Blue Server version is installed, it may be necessary to update the profiles and the printer
configurations when new parameters have been added.
From the GUI, you can access this button:
The update button allows to update all the profiles and the printer configurations from the profiles
sample.pfx.
Caution: When the filter mode is activated, only the printer configurations selected with the filter will be
affected.
12.5.2.4.Update specific configurations

When you want to update only certain printer configurations, you can use the update function : Select the
printer(s) you want to update, make a right click and select update.
This will update only the printer selected.

12.5.3.Modify a parameter for all the printer configurations associated to a profile
With the GUI, you can modify the parameters for one printer configuration at a time. In some cases, it may
be necessary to add/modify parameters of the printer configurations for all the printers associated to a
profile. This can be performed by modifying the profile.
With the Blue Server interface, once you have modified a profile (with setup or edit), and click on “Apply”,
the GUI asks if you want to apply these modifications to all the associated printers (printer configurations
which have been created from this profile)
If you click Yes, the modifications brought to the profile will be copied to the printer configurations.
Caution: if the filter is active, the modifications will be done only for the printers selected with the filter.

12.6. How to configure “Data Execution Prevention”
12.6.1.Description
Blue Server V6 or V7 on Windows 2003
12.6.2.Opening Blue Server

 Opening Blue Server GUI, and nothing is dipslayed.
 Or something you can get this message :
 Selecting Close Message, you will get this new message:

12.6.3.Action
On Windows Server 2003 or 2008, you must allow this Blue Server executable list.
 My Computer / Properties / Advanced / Performance - Settings / Data
Execution prevention
 Then allows this Software list from the MPI Blue Server directory:
MPI License\MLClient.exe MPI Router\ipfnt370.exe
MPI License\MLCsrv.exe MPI Router\svcmainf.exe
MPI License\MLD.exe MPI Router\ipfntlpd.exe
MPI License\MLDsrv.exe MPI Router\svcaslpd.exe
MPI License\MLDitf.exe MPI Router\tel3270.exe
MPI License\MLProduct.exe MPI Router\svctelnet.exe
MPI Parser\ipdsbsvc.exe The Blue Server\blueserv.exe

MPI Parser\ipfntpcl.exe The Blue Server\newblue.exe
The Blue Server\svcmpisrv.exe

12.7. How to configure remote Windows XP queue using Blue Server
Using MPI Blue Server installed on Windows NT, 2000 or Xp, you may have some problem for printing on
remote queue configured on Xp machine.
In this case, verify this points:
12.7.1.From Windows NT4

Please execute the following steps:
 Start -> setting -> Printers,
 Select your target printer,
 Printer -> Properties, you will have this new display:
 Security, you will have this new display:
 Select Auditing, you will have this new display:

This is the default setting.
 Select Add, you will have this new display:

 Select NETWORK -> Add, you will have this new display:
 Select OK -> Print Success, you will have this new display:
For the other parameters, please contact your local LAN administrator.
 Select OK to confirm and valid this new configuration.
 Select OK, to close the printer properties,
This modification will be taken immediately.

12.8. How to Configure Custom Paper Size for Blue Server - Parser
Using Blue Server – Parser session, you can configure standard (letter, legal, A4…) and custom (edge to
edge letter & A4 or other size).
Note: To determine the Blue Server paper size setting you must multiply the paper length and width by
300.
 From “Input Trays”, change Paper Size (from A4, letter, legal or ..) to custom:
 this figure shows how to modify the custom paper size:

 When you set to Custom, you must define all the other parameters according to this table.
These parameters are available for BMP, PCL5, PS2 and PS3 driver:
Unit : 300*Page Length or Page Width
=> For example: Letter = P L = 11.00*300 = 3300
P W = 8.5*300 = 2550
Size Page Length Page Width Physical Margin Escape Sequence

A4 3507 2480 50 ^&l26A
LETTER 3300 2550 50 ^&l2A
LEGAL 4200 2550 50 ^&l3A
EXECUTIVE 3150 2175 50 ^&l1A
MONARCH 2250 1162 50 ^&l80A
COM-10 2850 1237 50 ^&l81A
DL 2598 1299 50 ^&l90A
C5 2704 1913 50 ^&l91A
A3 4960 3507 50 ^&l27A
A4_E2E 3507 2480 0 ^&l26A
A4_WIDE 3507 2480 40 ^&l26A
LETTER_E2E 3300 2550 0 ^&l2A
A5 2480 1748 50 ^&l13A
JISB4 4299 3035 50 ^&l46A
JISB5 3035 2150 50 ^&l12A
LEDGER 5100 3300 50 ^&l6A
INVOICE 2550 1650 50 ^&l15A
FOLIO 3900 2550 50 ^&l9A
QUARTO 3248 2550 50 ^&l2A
COM-9 2662 1162 50 ^&l89A
ISOB5 2952 2078 50 ^&l100A

 This figure shows how a complete setup (for PCL5 or BMP) must be configured for:
- A4_E2E (edge to edge) configuration
- LETTER_E2E (edge to edge) configuration
- LEGAL (standard size) configuration
 This figure shows how a complete setup (for PS2, PS3, PDF, TIFF, PDF/A-1 b:2005 or IMAGE) must
be configured for:
- A4_E2E (edge to edge) configuration
- LETTER_E2E (edge to edge) configuration
- LEGAL (standard size) configuration
Note: if one of these sections is empty, the custom paper size is not used, and returns to the previous
paper size configured.

12.9. How to produce multiple outputs simultaneously
Warning
12.9.1.Description
Parser job format

PDF
PCL BMP printing
PostScript
TIFF
PostScript (B&W) printing
E-mail/FAX
PCL5 printing
PostScript (Color) printing PDF printing
4. Since version V7.01.004, Blue server is able to produce simultaneously different outputs.
5. For example, you can print PCL on a printer and archive the job in PDF on a remote server.
6. Blue Server is able to manage unlimited number of outputs at the same time.
7. Each session can print, generate output file, send email ……

12.9.2.Blue Server master session configuration
To configure this new option, you must define a “master” session that sends its IPDS buffers to additional
sessions.
You must configure the Blue Server printer configuration as follow:
- “Share IPDS with other sessions”: to activate the input buffer sharing option.
- Configure the number of sub-session you want to manage from the main session.
- The printer emulation parameters must match on all printer definitions.
- The slower printer defines the printing speed for all printer definitions.

12.9.3.Blue Server child session configuration
You must configure the child sessions according to the number of sub-sessions you define,
 Connection: BS Session (IPDS from Host)

Allow this session to connect to the main printer and receive IPDS buffers
 Connection: BS Session (Preprocessed IPDS)
Allow this session to connect to the main printer and receive IPDS buffers modified to generate
indexed output. (see How to configure IPDS indexer)
Printer emulation must be the same as the main session.
12.9.4.Blue Server interface sessions status
Available
The printer session is available to the system and is awaiting IPDS data from the Host for a sub-session.
Wait Children
The parent session waits for all sub-sessions to be loaded.
Wait Parent
The sub-session printer waits for the child session to be loaded
Session Error
This status appears when you unload one session. The others session loose communication and must be
Unloaded/Loaded again

12.10.How to use Blue Server and the indexer feature
Warning
12.10.1.Description
Since version V7.01.07, Blue server is able to locate and extract information from the IPDS data stream.
This means that thanks to information found in the IPDS pages, the Blue Server is able to split the job,
extract data that may be used to rename the output document produced and generate an XML file which
can be used with Archiving systems.
12.10.2.IPDS indexing
With AFP printing, it is possible to take advantage of the TLE command embedded in the AFPDS files to
split and name the output files generated. With IPDS such a structure does not exist.
With Blue Server, you can now split IPDS documents and name the files according to information extracted
from the IPDS data. You can even extract any information present in the IPDS data stream to create
indexing files for archiving.
Typical application: an AS/400 customer produces invoices in IPDS. All invoices are in a single spool file.
He wants to produce a PDF of each invoice with the invoice number and the company name part of the
PDF file name.
In order to achieve this goal, it is necessary to perform the following two steps.
12.10.2.1.Step 1: Defining the rules

It is first necessary to analyse the document, define the rules and create a configuration file which will be
used in production. This step is performed only once per host application.
First “print” an application job (an invoice for instance) and produce with Blue Server a Tiff output. Blue
Server produces a single tiff file for each page. Thanks to the MPI Tiff viewer, you can locate and specify
the information to be used to identify the pages and the data to be extracted and used as indexes. This
configuration information is stored in a configuration file (.IDX file).

12.10.2.2.Step 2: Running in production
Two Blue Server configurations are required.
The first configuration receives the IPDS data from the system and analyses it. Thanks to the index
configuration file, it is able to recognize the pages and extract the relevant data. This information is then
injected to the IPDS data as NOP commands. This configuration can produce an output (PCL,
PostScript…)
The second Blue Server configuration receives the “enhanced IPDS” from the first configuration and
produces the output data stream (PCL, PS, PDF…). It takes advantage of the NOP commands to split the
document, name the files generated.
12.10.3.Prerequisite
Blue Server version V7.01.008 (since)
Index Composer: It is the Tiff viewer which allow you to create the .Idx files. It is a java application
MPI Tiff viewer: IndexComposer.jar
Java Installed: JRE V4 or later
File charsets.jar: this file contains the java code Pages. It must be in the java installation library in the
\Lib sub-directory (example : C:\Program Files\Java\jre1.5.0_04\lib\charsets.jar)

12.10.4.Example used with this manual
With this manual we will use the AS/400 INVNEW3 job provided with the QSAMPLER AFP/IPDS
demonstration library provided by IBM.
This job produces 4 invoices:
First invoice = 3 pages
Second invoice = 6 pages
Third invoice = 3 pages
Forth invoice = 3 pages
The purpose of this example is to convert the job to PDF, create a independent PDF for each invoice and
name each PDF file generated with the “customer number” and the “Invoice number” which will be
extracted from the document.
When looking at the entire document one can see that each first page of an invoice contains fix information
that may be used to identify that it is the first page of an invoice. In the above image, it is the information
surrounded with a red ellipse (“Customer copy” and “Page 1”).
When this information will be found at this specific location on a page, Blue Server will assume that it is the
first page of an invoice. Data must then be extract and the job must be splitted.
The customer number and the invoice number are found on the same page. They are surrounded with a
Blue ellipse (“100” and ”31300”). They will be extracted and used to rename the PDF file.

12.10.5.Producing the tiff files
The first step consists in producing the tiff files of the application.
12.10.5.1.Blue Server configuration
12.10.5.1.1.Host tab
In order for Blue Server to extract the information from the data, you must configure in the Blue Server
printer configuration as follow:
- “Overlay caching” must be unchecked.

12.10.5.1.2.Destination tab
- “Output language” = Tiff

- “Split document” =1
- “Print path” = directory to store the pages transformed in tiff format
Load the tiff printer and print the job of the application you want the indexes for
The tiff files will be stored in the directory

12.10.6.Launching Index composer
- Run IndexComposer.jar,
- And you will have this new display
- Select “load page” at the top right corner to open a tiff file produced with Blue Server,
- Select the tiff image you want to open,
- Once the tiff page has opened a new window with all the data extracted from the page appears,
- Big5 may be the default character set.

- Select the appropriate code page (the one selected in the application)

Example: IBM01140 (International with euro)  the text becomes readable.
Note:
If the code pages do not appear in the list, check the charsets.jar in the java install library

12.10.7.Composer window
Once the Tiff page has been displayed, you get this window.
When you move the cursor to the right side of the window, you can see that the text is highlighted. These
are the text strings recognized with the Index Composer. The strings will be used to identify the pages and
select the index fields
On the right side of the window there are 4 windows:
Page type: Represents the type of document you are working with. It helps you knowing which
kind of document you are working with. Enter a friendly name to recognize the job, like
INVOICES
Page sub type: Represents the name of a specific page of the job you want to work with. Example
“Firstpage”
Criteria: This is the information picked on the page to identify a specific page.
Indexes: These are the information picked on the page you want to extract and use as indexes.

12.10.8.Creating indexes
12.10.8.1.Identifying a job and a page
As an IDX file can contain different job descriptions and indexes, it is necessary to identify the jobs and the
pages you are working with. This is text is informational
First window = “Page Types” : make a “add” and enter a name which qualifies the job you are working
with. example : INVOICES
Second window = “Page Sub-Types” : make a “add” and enter a name which qualifies the page of the job
you are working with. Example : First Page

12.10.8.2.Defining the criteria to recognize this page
On the right side of the window, locate the strings you to use to identify the page. Once this information is
highlighted, make “Add” In the criteria window. The selected text appears in the criteria window.
You can do the same with “Page” and “1”

12.10.8.3.Defining the indexes
As for the Criteria, highlight in the right window the information you want to use as indexes.
- In the “Indexes” window, make “Add”. A new window with the title “Entrée” appears.
- The string selected by the index composer appears above the text “Enter index name for” (100 in the
above example). Make sure that this is the right information you want to use as index.
- Enter a name for this index (Cust_num)
- You can do the same for the invoice number.

- The final result is:
- You now just have to save your configuration.

- Click on save and specify the name of your indexing file (file extension = .idx)
- Example: invoices.idx

12.11.How to use the “Add Form” option with Blue Server
Warning

12.11.1.Description
1. Since Blue Server V7.01.00x, a new interface has been designed for this “Add Form” functionality.
2. Without any application modification, it is possible with Blue Server to add images to the document in
order to enhance the printout generated by Blue Server.
Examples of typical applications:
- Add the company logo to the documents,
- Produce PDF documents from applications, which have been designed to be printed on preprinted
paper,
- Add a watermark to the documents…
Without the add form option:
With the add Form Option :

12.11.2.What objects can be included
The elements, which can be included to enhance the printout, are black and white, grayscale or color
images.
The image formats which can be used are:
- Jpeg (file extension .jpg or .jpeg)
- Tiff (file extension .tiff or .tif)
- Gif (file extension .gif)
12.11.3.How to specify when the images are added

A XML file gives the flexibility to add images to specific pages of desired documents.
Each Blue Server printer configuration can use different rules.
The conditions which can be used to differentiate the documents are:
 Form : This information comes from the application and is part of the IPDS data Stream
received at the beginning of each IPDS job. It is one of the AS/400 printer File attribute
or it is a JCL statement added to the job used to submit the print
 Input This is the IPDS printer input paper tray selected by the application.
 Ouput This is IPDS printer output paper tray selected by the application
The conditions that can be used to differentiate the pages within a specific document are:
 frompage the image will be added from this page
 topage this option goes with the « frompage » option.
 Modulo this option allows to indicate every how many pages (modulo 4 means that the image
will be added every 4 pages)
 Front When it is set to 1, the image will be added on the front sides of a duplex document
 Back When it is set to 1, the image will be added on the back sides of a duplex document
 Suplex This option is used to force the image to be placed on the back side of a page when the
document is simplex
If several conditions are configured, the image is added only when all the conditions are satisfied
12.11.4.Activating the “Add Form” option

The Add Form Option is activated by setting the parameter #162 with the XML file name
@0 --- Section 0 ---
#162 Pre-Printed File : c:\My_BS_Images\MyXML_AddForm.xml
If you specify the XML filename without the path, the XML file must be located in the directory:
..\MPI Blue Server\MPI Parser\.
Important Note : The XML file goes together with the file “preprinted.xsd”. These two files must be in
the same directory.

12.11.5.Location of the images used
Compared to the location of the XML file, the images used to enhance to print must be in the same
directory or in a sub-directory.
Example:
If the XML file (and the preprinted.xsd file) is located in the:
<local_drive>\MPI Blue Server\MPI Parser\ directory
and the images are in the
<local_drive>\MPI Blue Server\MPI Parser\Images directory
the file name specified in the XML configuration will be:
<filename>\Images\my_company_logo.jpg</filename>
12.11.6.XML utility
The utility “Blue Server Form Overlay” is provided in order to help building XML file.
12.11.7.Syntax of the XML file

The XML file must follow the standard XML conventions. Only some tags are allowed.
It is possible to check the validity of the XML you configure. The file “preprinted.xsd” located in the same
directory is be used to control the validity of the XML file when you open it (with MS Internet Explorer for
instance).

12.11.7.1.Example of XML file
<?xml version="1.0" encoding="UTF-8" ?>
- <preprinted xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="preprinted.xsd">
- <image>
- <reference>
<filename>my_company_logo.jpg</filename>
</reference>
- <placement>
<x>10</x>
<y>600</y>
<o>0</o>
</placement>
- <condition>
<form>STD</form>
<frompage>1</frompage>
<topage>1</topage>
</condition>
</image>
</preprinted>
In this example, the image my_company_logo.jpg will be added only on the first page of the all the
document having the form = STD.
12.11.7.2.Example of XML file

The two first lines (in Blue) are mandatory
</preprinted> is the beginning of the XML configuration
<image> defines a new rule
<reference> defines the image to be used
<placement> defines the position and the rotation of the image in the page.
<x> and <y> are the absolute positions of the image on the page in 1/300 of inch
<o> defines the rotation of the image on the page. Allowed values are 0, 1 (=90°), 2
(=180°), 3 (=270°).
<condition> defines the conditions to insert the image on the page.
The tags allowed for the <condition> tag are:

<form>, <input>, <output> <frompage>, <topage>, <modulo>, <front>, <back>

12.11.8.Windows Pre-requisite – MSXML4.dll
In order to use the add Form option, the msxml4.dll Service Pack 2 must be installed on the PC.
Please check that this dll is installed in the C:\WINDOWS\system32.
If it is not installed on the PC, please download it from the Microsoft web site:

12.11.8.1.MSXML 4.0 Service Pack 2 (Microsoft XML Core Services)
Run msxml.msi in order to update MSXML 4.0 Service Pack 2

12.11.9.AS/400 message CPA3394 : Load form type
An inquiry message is sent to the message queue when a spooled file has a form type that is different than
the form type in the printer. The spool file status changes to “MSGW” and it is necessary to answer the
message with the option ”G” to process the spool file.
Additional Message Information
Message ID . . . . . . : CPA3394 Severity . . . . . . . : 99

Message type . . . . . : Inquiry
Date sent . . . . . . : 11/21/05 Time sent . . . . . . : 13:51:21
Message . . . . : Load form type 'CONFIDENT' device IPPHD writer IPPHD. (G

B I H R C)
Cause . . . . . : The file on output queue IPPHD in library QUSRSYS requires
form type 'CONFIDENT' to be loaded on device IPPHD. The form type for the
file was all blanks when '' appears as the form type.
Possible choices for replying to message . . . . . . . . . . . . . . . :
G -- Begin processing the current file after loading the form type.
B -- Begin processing the current file after loading and aligning the form
type (no alignment message is sent - same as option 1 on System/36).
I -- Ignore the request to load the form type. Print the file on the
current formtype (same as option 0 on System/36).
More...
Reply . . . : G
In order not to have to answer the message each time the writer processes a spool file with a new form
type, modify the parameter FORMTYPE to (*ALL *NOMSG) when you start the printer writer. The
CPA3394 message will not be issued and the writer will then process the spool files automatically.
Start Printer Writer (STRPRTWTR)
Printer . . . . . . . . . . . . MY PRT Name, *ALL, *SYSVAL

Output queue . . . . . . . . . . *DEV Name, *DEV
Library . . . . . . . . . . . Name, *LIBL, *CURLIB
Queue for writer messages . . . *DEVD Name, *DEVD, *REQUESTER
Library . . . . . . . . . . . Name, *LIBL, *CURLIB
Form type options:
Form type . . . . . . . . . . *ALL Form type, *ALL, *STD, *FORMS
Message option . . . . . . . . *NOMSG *INQMSG, *MSG, *NOMSG...
File separators . . . . . . . . *FILE 0-9, *FILE
Drawer for separators . . . . . *DEVD 1-255, *DEVD, *FILE
Bottom
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

12.12.How to Use Blue Server - generating Mail
Warning

Blue Server can transform the IPDS data to PDF. Each host spool file generates a PDF file that can be
sent as an attachment to an E-mail destination. Depending on the IPDS data and Blue Server configuration
it may be possible from one Blue Server printer configuration to address either one or any E-mail
destination.
12.12.1.One Blue Server printer addresses one E-mail destination

Instead of printing to a physical printer if you want Blue Server to send each document to one E-mail
destination, you just have to configure the Blue Server printer as follow:
12.12.1.1.“Destination” Tab, “Output Language” must be set to “PDF”:

12.12.1.2.“Mail” tab configuration:
 Outgoing Mail Server This is the IP address or the DNS Name of the server providing the SMTP
Service.
 Email Service This name will appear in the “From” Filed of the E-mail.
 Email sender This is the mail address that generates the mail. It will be used if somebody
makes a reply to the E-mail sent from Blue Sever.
 Email Destination This is the mail address the PDF file generated will be sent to.
 Bcc Mail Address Internet address of the bcc (blind carbon copy) email destination.
 Subject This text will appear in the subject field of the E-mail.
 Message Open text filed. As for the other fields of this window, it can contain
variables generated by Blue Server.
In this example, the date and time are specified. For a complete list of
variables that may be used, please refer to the document “How to use
variables with Blue Server” section.
Note : For Space (0x20), Carriage Return (0x0d) and Line Feed (0x0a)
characters, it must be entered in Hexadecimal format.
Example :
This,0x20,mail,0x20,has,0x20,been,0x20,generated,0x20,w
ith,0x20,BlueServer.,0x0d,0x0a,On,0x20,%DATE%,0x20,at,0
x20,%TIME%

12.12.1.3.Resulting E-mails in Lotus Notes and Microsoft Outlook
The PDF file produced by Blue Server is attached to the mail. In the following example, the file name of
the PDF file is the default name produced by Blue Server. It can be configured with variables to match the
customer‟s requests (please refer to the document “How to use variables with Blue Server” for more
information).

12.12.2.One Blue Server printer addresses any E-mail destination
It may be possible to address any E-mail if the application specifies the necessary information such as the
mail destination.
12.12.2.1.Modify the application:

In order to specify the E-mail destination to be used by Blue Server to address the Mail destination, you
must add this information in the application data. You must first define 2 character strings that will be used
by Blue Server to extract the E-mail information from the data. The first string activates the Start extraction
mode and the second string defines the End extraction mode.
Caution:
- These strings must be special strings that cannot be found in normal application data.
Example the start data extraction string may be $** and the end data extraction may be
**$.
- The text found between these strings will be removed from the “printed” data.
Example: In your application you want to specify
- the mail destination
- the subject
- the mail sender
The start data extraction string you chose is $** and the end data extraction string is **$.
You must add in the application:
$**MAILTO=mail001@mycompany.com**$
$**MAILFROM=master@mycompany.com**$
$**SUBJECT= This will be the subject of the mail**$
MAILTO, SUBJECT and MAILFROM become variables you can use in the Blue Server printer configuration

12.12.2.2.Blue Server configuration:
In order For Blue Server to extract the mail information from the data, you must configure in the Blue
Server printer configuration as follow:
“Destination” tab:
- “Data Extraction” = “String Extraction”
- “Start String” = $**
- “End String” = **$

“Mail” tab:
You must inform Blue Server about how you use the variables set in the application. With Blue Server
configuration, you must specify the variable between % (example: %MAILTO%):
The variables %MAILFROM%, %MAILTO% and %SUBJECT% will be replaced with their values extracted
from the application data.
%MAILFROM%  master@mycompany.com
%MAILTO%  mail001@mpitech.com
%SUBJECT%  This will be the subject of the mail

12.13.How to split on TLE MO:DCA structured fields
Warning

12.13.1.Introduction
This document gives basic information about AFPDS indexes and describes how you can take advantage
of this information with Blue Server.
One of the main usage is to produce multiple named pdf files out of a single AFP document. A separate
XML file containing the PDF file names and the indexes is produced. The PDF files and the XML file can be
used to fill a document database.
12.13.2.AFP Files with indexes

An AFPDS file may be indexed.
When indexed, the AFPDS document contains page groups.
A page group is used in the data stream to define a named, logical grouping of sequential pages.
Page groups are defined so that the pages that comprise the group can be referenced or processed as a
single entity. The page group may contain index information carried by TLE structured fields.
The AFPDS file structure is then:
Resource Group
Resource Object data
Resource object Data
…….
Document
Page group
TLE
TLE
...
Page
Page
. . .
Page group
TLE
TLE
...
Page
Page
. . .
The TLE structured fields mainly contain a pair of information:
- A fully qualified Name (example “NAME”)
- An attribute value (example “James Cameron”)
In addition, the MO:DCA architecture defines Document Index. The Document index is a structure which
contains the indexing information for the entire document. It may be located within the document or
external to the AFPDS File. MO:DCA elements that may be indexed are pages and page groups. Blue
Server does not use this structure.
12.13.3.Blue Server configuration

The parameter “#70 Split On TLE :” has been added. When this parameter is set with a “Fully
qualified Name”, Blue Server splits the job when a TLE field with this “fully qualified name” is encountered.
All the TLE “fully qualified name” become Blue Server variables and may be invoked to rename the job
produced. To invoke this variable, use the %#<Fully_Qualified_Name>% syntax (starting with %# and
ending with %).
The file “Tle_afp.xml” is automatically created.

12.13.4.Example
- An AFPDS file contains 3 page groups.
- Each page group contains a variable number of pages.
- Each page group starts with two TLE structured fields.
Nb of
Page Group TLE (Fully Qualified Name = Attribute value)
pages
NAME = Cameron
Page Group 0001 3 COUNTRY = United Sates
NAME = Durant
Page Group 0002 1 COUNTRY = France
NAME = Wolf
Page Group 0003 2 COUNTRY = Germany
Blue Server Configuration:

- Transform = PDF
- Output Directory = C:\AFP_Output
- #70 Split On TLE : NAME
- Job Name = %#NAME%_%#COUNTRY%_%TOPAGE%_pages.pdf
when processed by Blue Server, the “C:\AFP_Output” directory will contain 3 PDF files:
- Cameron_United Sates_00003_pages.pdf
- Durant_ France_00001_pages.pdf
- Wolf_Germany_00002_pages.pdf
In the “C:\AFP_Output” directory, the “Tle_afp.xml” file contains:
<TLE>
<INDEX><NAME>Cameron</NAME>
<COUNTRY>United States</COUNTRY>
<DOCUMENT>Cameron_United Sates_00003_pages.pdf </DOCUMENT>
</INDEX>
<INDEX><NAME>Durant</NAME>
<COUNTRY>France</COUNTRY>
<DOCUMENT>Durant_France_00001_pages.pdf</DOCUMENT>
</INDEX>
<INDEX><NAME>Wolf</NAME>
<COUNTRY>Germany</COUNTRY>
<DOCUMENT>Wolf_Germany_00002_pages.pdf</DOCUMENT>
</INDEX>
</TLE>

12.14.How to Set-Up and Use Blue Server Back-Up
Warning

12.14.1.Description
A B
Station/Server where Blue Server is Station/Server where Blue Server
installed Back-Up is installed
(For example (For example
IP address = 192.168.31.66) IP address = 192.168.31.19)
1. This function is available since Blue Server V7.00.0153 (Parser session for the moment).
2. This Back-Up functionality is useful when a problem occurs on Blue Serve A (maintenance, IP
problem, MPI File Server Service stopped…) automatically the printers loaded from this Blue Server
A are loaded to Blue Server B and are ready to print.
3. While they are connected, the Blue Server A will replicate all new setup modification to the Back-Up.
4. When you have loaded printers on Blue Server A, the printers Back-Up are just awaiting. They are
not loaded at the same time.
5. A mail notification is send to the administrator when a problem occurs.
Notes:
 The only action/modification that the administrator must do is on the Host printer definition. All these
A and now must match with the Blue Server B.
printers definition match with Blue Server
 For each Blue Server installation A and B it must be done on the same C:\ or D:\ target drive to
avoid directory access for PDF files, traces…
 Since version Blue Server V7.04.04, you must also modify the registry (BS installation A and B)

12.14.2.Installation & set up
12.14.2.1.Installation
 If you pay for an annual Blue Server maintenance, please contact MPI Tech or your local MPI Tech
for further instructions. You will get from us a link for downloading our latest version.
 After the installation, starting the Blue Server :
 Change from :
View -> Refresh Time
value from 1sec to 2sec
 and new functionally is available from the “Tools” tabs:

Tools → Backup Server Setup
Unload All Printer Backup
Synchronize Backup Server

12.14.2.2.Set-up – Blue Server A
To perform this setup, the MPI File Server Service, must be stopped before.
 After starting your Blue Server A GUI,

 Select, “Tools → Backup Server Setup”,
and you will have this new display :*

* Information displayed in the above picture are the default values.
Use Backup Server Option Uncheck this box if you don‟t want to active this function.
Backup Server Address This is IP address of the Blue Server B (backup).
Backup Server Port This number (ranging from 0 to 65 535) must be equivalent on both
sides.
Backup Polling Tempo This number (ranging from 3 to 10 000), specified the amount of time
between each problem.
Retry Number to Disconnect This number (ranging from 1 to 1 000), is the number of Backup
Polling Tempo before starting the Back-Up procedure.
Outgoing Mail Server (SMTP) This is the IP address or the DNS Name of the server providing the
SMTP Service.
Email Account This name will appears in the “From” Filed of the E-mail.
Email Sender This is the mail address that generates the mail. Is will be used if
somebody makes a reply to the E-mail sent from Blue Server.
Email Destination This is the mail address the notification file generated will be sent to.
 Then select Apply for saving the information.

12.14.2.3.Set-up – Blue Server B
To perform this setup, the MPI File Server Service, must be stopped before.
 After starting your Blue Server B GUI,

 Select “Tools → Backup Server Setup”,
*
and you will have this new display :
* Information displayed in the above picture are the default values.
Use Backup Server Option Uncheck this box if you don‟t want to active this function.
Backup Server Address In this case, it must be set to 127.0.0.1 for the Blue Server B
Backup Server Port This number (ranging from 0 to 65 535) must be equivalent on both
sides.
Backup Polling Tempo This number (ranging from 3 to 10 000), specified the amount of time
between each problem.
Retry Number to Disconnect This number (ranging from 1 to 1 000), is the number of Backup
Polling Tempo before starting the Back-Up procedure.
Outgoing Mail Server (SMTP) This is the IP address or the DNS Name of the server providing the
SMTP Service.
Email Account This name will appears in the “From” Filed of the E-mail.
Email Sender This is the mail address that generates the mail. Is will be used if
somebody makes a reply to the E-mail sent from Blue Server.
Email Destination This is the mail address the notification file generated will be sent to.
 Then select Apply for saving the information.

12.14.3.Starting Blue Server
 After configuring yours Blue Server A and B, you can load the printers, and you will have this
display on Blue Server A:
 From the interface, you can check if the Backup server is active or not.
 In our case, there is no connection with the Backup server,
Action:
You must check:
- From Blue Server A : Tools → Backup Server Setup”, the correct IP address of the Backup server
- From Blue Server B : Tools → Backup Server Setup”, the correct IP address “127.0.0.1”
- That MPI File server Service is started,
 Then you will have:

Notes :
1. When you start the first time, the Backup Server, we recommend to use Synchronize Backup
Server option, to be sure that on both side; all printers use the same configuration.
2. On Backup server B side, files located in the

<Local_Drive>:\MPI Blue Server\MPI Parser\pfn directory, are the printers loaded on
Blue Server A are awaiting to be load, if a problem occurs.
- Blue Server A:
PRT6000.PF4 → Configuration file
PRT6000.AL4 → Configuration loaded
And you will have:
- Blue Server B:
PRT6000.TP4 → Temporary configuration
And you will have:
3.

12.14.4.Problems
12.14.4.1.No more IP connection available with Blue Server
In this case of problem, what should be the different steps:
 On the Blue Server A, you will have:
 On the Backup server B, you will have:

 On your E-mail account, you will receive a mail for this problem
 Inside the MpiBackup.log file, you will read :

Load config PRT6000.PF4 on Server(EOLE)
 Now the Backup server is ready to operate, but do not forget to change the Host IP address.
The Host IP destination must match with the new Blue Server address.
Notes:
When the primary server A comes back online again, and you want to load the printers, must be manually
perform this action on server B:
1. Tools -> Unload All Printer Backup
2. If your backup was running for a couple of hours/days/month, if should be advise to Synchronize
backup server B
3. This action is done, to make sure that all printers are up to date on both sides.
4. Then "Load" on the server A the printers,

5. On the Server A side, in the ..\MPI Parser\pfn directory, AL4 files will appear again.
6. On the Backup B side, in the ..\MPI Parser\pfn directory, TP4 files will appear again.
The server A and backup B are ready again.

12.15.How to set up PDF encryption
Warning

12.15.1.Description
PDF output
IBM Host Blue Server

 Since Blue Server V7.01.004, a new interface has been designed for this “encryption” functionality.
12.15.2.Old interface – until V7.00.192

 From a Blue Server GUI,
 Selecting “Destination” tab, you will get :

 Checking PDF encryption, you will get :
 This interface is no longer supported, and has been replaced by a new one.
12.15.3.New interface – Since V7.01.003

 From a Blue Server GUI,
 Selecting “Destination” tab, and checking “PDF encryption”, you will get :

 Selecting “Options” box, you will get :
12.15.3.1.Encryption Level
Values allowed:
 40 bits: (default) No action
 128 bits: strong encryption.
12.15.3.2.Permanent editing lock

 Checked: no more modification such as:
- Change the document,
- Document Assembly
- Filling of form Fields
- Signing
are available.
12.15.3.3.Administrator Password
Entering an Administrator password, this password is necessary for opening the PDF file.
12.15.3.4.User Password
Entering a User password, this password is necessary for opening the PDF file.
12.15.3.5.Printing allowed
12.15.3.6.Changes allowed

12.15.3.7.Enable copying of content
Allows with Acrobat these options:

- Content Copying or Extraction and
- Content Extraction for Assembly.
Notes:
 For “Changes allowed” and “Enable copying of content” options, if a USER password active, an
ADMINISTRATOR password is mandatory for activating the options.
For opening the PDF file, the USER password is necessary, but for activating other options, the
ADMINISTRATOR password is necessary.
12.16.How to check Blue Server status

12.16.1.Introduction
On the Blue Server GUI, Host and Printer status can be displayed.
These status, such as :
- Pending, Connected, Not Connected, Printing, Sharing, Available, Inactive, Active, Session Error….
are useful to help you when a problem occurs.
12.16.2.Status problem
In case of problem, status are not displayed or disappeared, you can activate from the Blue Server GUI :
 Tools / Report Trace Option
(default value is unchecked).

 By activating this option can help you to understand or find the problem.
 Then open : Tools / Blue Server Report.
 This action will open the “LogBS.txt” file located on
<local_drive>:\MPI Blue Server\The Blue Server directory
 Inside this file, you will display all the actions for opening or displaying status used. If you cannot
understand this log file, sent it directly to MPI by mail.
12.17.How to handle “Printer Restart” exception error

12.17.1.Parameter #54 AF
@2 --- Section 2 ---

This parameter was used with old Blue Server versions (Router + DIMM) 20020703 : the parameter
becomes
#54 Block exception Printer restart.
This new implementation has been performed for few customers who generates IPDS with an CICS
application.
When the exception 0100..00 Normal Printer Restart is sent to CICS it locks the session.
#54 Block exception Printer restart : 0 (This is the default value).
#54 Block exception Printer restart : 1
The exception 0100..00 is not reported to the host .

12.18.How to load – unload Blue Server printers with a file command
12.18.1.Description
“Order.Lst” is a file used by the Blue Server Interface for unloading or loading printers.
12.18.2.Creating “Order.Lst” file

When a specific action need to be completed for unloading or loading Blue Server printers, you must create
a file named "Order.Lst".
This file must be copy to “..\MPI Blue Server\The BlueServer" directory
And automatically this “Order.Lst” file is executed by Blue Server.
The Blue Server Interface polls periodically if this file exists, if it exits it treats it and deletes it.
12.18.2.1.Syntax of the file "Order.Lst"

The complete syntax is :
<FILE> = <Line of Order><Line of Order><Line of Order>...<Line of Order><EOF>
<Line of Order> = <ORDER><SP><server><SP><printer><SP><product>;
<server><SP><printer><SP><product>;.....;<CR><LF>
<ORDER> = L | U (L for LOAD, U for UNLOAD)

<SP> = space character
<server> = serverName concerned (in Your case the Local Server normally)
<printer> = printerName concerned by order
<product> = Mpi Product Number in Text
Notes :
1. case sensitive for the Server and printer name.
2. Router SCS Mainframe it is 2, that corresponding to extension PF2
Parser it is 4, that corresponding to extension PF4
LPD it is 6, that corresponding to extension PF6
Telnet it is 8, that corresponding to extension PF8
12.18.3.Example
L EOLE lpd5 6;EOLE lpd6 6;EOLE lpd7 6;
U SRV_PRT lpd3 6; SRV_PRT lpd8 6;
L WRKTEST AF1075 4;
U WRKTEST IPJMD2 4;
L BSTST xdf 4;

12.19.How to install Blue Server on Windows 2003 cluster
12.19.1.Requirement
 Windows 2003 installed on each cluster server (Node)
 Shared disk drive between each node
12.19.2.Cluster configuration
First, you must define on one server, using the cluster administration tools:
 The cluster name
 The cluster IP address
 The nodes used by the cluster
By default after the cluster configuration, you must have something configure as follow:
For this example, we define R:\ as the shared disk and nodes name is EOLE and Bigbrother

12.19.3.Blue Server Installation
 From the cluster administrator, switch to the first node.
 Launch setup.exe from the Blue Server installation cdrom.
 Choose Custom install and change the installation path from c:\MPI Blue Server to
R:\MPI Blue Server.
 After the installation complete, stop the MPI License File server service and the MPI License client
service.
 Copy the folder R:\MPI Blue Server\MPI License to
C:\MPI Blue Server\MPI License.
 Delete the folder R:\MPI Blue Server\MPI License,
 Open regedit,
 Go on HKEY_LOCAL_MACHINE\Software\MPI Blue Server\MPI License\CurrentVersion\Setup
and change the Rootdir key by the new license path (c:\MPI Blue Server\MPI License)
 Go on HKEY_LOCAL_MACHINE\Software\MPITech\MPI License\CurrentVersion\Setup and

change the Rootdir key by the new license path (c:\MPI Blue Server\MPI License)

 Go on HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MPI License Client
Service and change the ImagePath key by the new license path
(c:\MPI Blue Server\MPI License\MLCsrv.exe)
 Go on HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MPI License Service and

change the ImagePath key by the new license path
(c:\MPI Blue Server\MPI License\MLCsrv.exe)
 Then Start the MPI File Server service, MPI License Client service, MPI License Service (Set these
services to Automatic startup)
 Generate a license key for this node
 Switch to the second node and then do the same procedure to install the Blue Server and modify the
registry.

12.19.4.Cluster configuration for Blue Server
 You must now add the resources managed by the cluster.
 We need to add the MPI Parser service and the Shared disk as cluster resources
12.19.4.1.MPI Parser
 From the cluster administrator , select New, New resources
 Configure this new resource like bellow
 Select the servers used to create the MPI Blue Server Cluster

 Create a MPI Parser Service dependency to the Shared disk. This is needed to be sure the
shared disk was online before the MPI Parser service start.

12.19.4.2.Shared Disk

 Select the servers who use the shared disk ressource
 No dependency are needed for the shared disk

 Select the physical disk volume used by the Cluster
 Select Bring Online
The cluster became online and ready to use. You can use after the move group command to change the
active server on the cluster group.
On host side, you must use the CLUSTER IP ADDRESS and not the SERVERS IP ADDRESS

12.20.How to configure Blue Server on clustered Windows queue
12.20.1.Cluster configuration for windows queue
To create a cluster-managed printer:
1. Open Cluster Administrator,
2. Create a virtual server, that is, a resource group containing a Network Name resource (where the
Network Name resource is the name of a virtual server), an IP address resource, and a Physical
Disk resource, if these do not already exist, creates.
For more information on creating a new resource group and resources, see "To create a new group"
and "To create a new resource" in Related Topics.
For more information, see "Virtual servers" in Related Topics.
3. Create a Print Spooler resource in that virtual server and make it dependent on the Network Name
and Physical Disk resources.
Important:
These two resources are required dependencies for the Print Spooler resource.
4. Bring the virtual server containing the Print Spooler resource online.
For more information, see "To bring a group online" in Related Topics.
5. Install printer drivers for your printer on the virtual server.
12.20.2.Print Driver installation on the virtual server

 Click Start and then click Run.
 In the Run dialog box, type \\MyVirtualServer where MyVirtualServer is the name of the virtual server
that the print spooler resource depends on.
The virtual server opens.
 Open Printers and Faxes, right click and select Server Properties, then click the Drivers tab.
 Install the printer drivers.
Important
o The port monitor must be installed on all nodes in the cluster before installing printer drivers on the
virtual server. For the Windows Server 2003 family, the port monitor for the Standard TCP/IP Port is
installed by default with the operating system. For two other types of ports, you must first install the
appropriate port monitor on each node before installing the printer drivers, printer port, and printer
queue on the virtual server.
LPR Ports: The LPR port monitor files are shipped on the Windows Server 2003 family media. For
more information on installing the LPR port monitor and adding it to the list of Available port types
for a node, see "To add a port" in Related Topics.
Custom IHV Ports: Printer drivers from Independent Hardware Vendors (IHVs) may include a custom
IHV port monitor that must first be installed on each node. To install the IHV port monitor on each
node, install the driver package on each virtual server in the cluster. Contact your IHV to verify that
the third party port monitor is compatible with the Cluster service before installing on the cluster
nodes.

12.20.3.Printer port installation on the virtual server
 Click Start and then click Run.
 In the Run dialog box, type \\MyVirtualServer where MyVirtualServer is the name of the virtual server
that the print spooler resource depends on.
 The virtual server opens.
 Open Printers and Faxes, right click and select Server Properties, then click the Ports tab.
 Add a port.
12.20.4.Print queue installation on the virtual server

 Open the remote printers folder of the virtual server.
 Use the Add Printer Wizard to add a new print queue.
Notes:
o To perform this procedure, you must be a member of the Administrators group on the local
computer, or you must have been delegated the appropriate authority. If the computer is joined to a
domain, members of the Domain Admins group might be able to perform this procedure. As a
security best practice, consider using Run as to perform this procedure.
o To open Cluster Administrator, click Start, click Control Panel, double-click Administrative Tools,
and then double-click Cluster Administrator.
o Not all printer ports may be used in a server cluster. LPR and Standard TCP/IP Port, both provided
with the Windows Server 2003 family, may be used in a server cluster. Check your printer
documentation to verify that your printer can use one of these two ports.
o To share out the printer, you must share out the print queue from the virtual server itself and not from
the individual nodes.

12.20.5.Windows Queue sharing properties
In order to use the windows queue from the Blue Server, you must add some security user rights on the
windows Queue.
 Open the windows queue properties windows
 Open the Security Tab

 Add the Network and Network Service user.
 Give all right to these users.

12.21.How to record a SPY trace using Blue Server – Telnet session
12.21.1.Description
With Blue Server you can record a Telnet trace with the internal utility.
AS/400 or Mainframe WorkStation where the Blue Server is installed

(e g : IP address = 192.168.31.3) (e g : IP address = 192.168.31.64)
12.21.2.Configuration on the Blue Server

12.21.2.1.Telnet Session
 On Blue Server side, unload the printer session,
 Double click to activate the set up mode,
 Set the Trace Option parameter to “Record”

 Select Apply,
 Load the printer,
 The communication is established with the AS/400 or Mainframe.
12.21.3.Send the job

 Wait for the entire job to print on the printer.
Note :If you are running AS400 you will now need to end the writer.
 To Stop the trace, unload the printer. The trace file will be created.

12.22.How to record a internal SPY trace using Blue Server – Parser session
12.22.1.Description
Blue Server internal trace is a internal TCPIP utility used for capturing IPDS traces in a Mainframe and
AS400 environment.
Use this trace mode, only in case of “simple” printing problem (fonts, overlay, page presentation..).
If a Dr Watson, or application problem is generated from the ipfntpcl.exe file, do not use this trace
mode, but the external trace utility.
AS/400 or Mainframe WorkStation where the Blue Server is installed

The IBM Host will send data over TCP/IP to the PC/Workstation running Blue Server Spy utility. The Blue
Server Spy utility will forward the data to the printer without alteration.
The Blue Server Spy utility will record the data to a file.
At the end of the job, Spy utility needs to be stopped to close the recording.
12.22.2.Setup and Configuration

 Unload your target printer configuration from the Blue Server GUI,
 Click right, select setup mode,
 Select the “Utilities” tab,
 Change the Trace Option parameter to “Record”,

 A new parameter is displayed,
 Fill this new option with a <file_name.spy>,

The default directory used for recording the spy trace is :
..\MPI Blue Server\MPI Parser\trace
 Apply the modification, and load the printer
 Print the job.

12.23.How to record an external SPY trace with PPRSPY utility – Parser
session
12.23.1.Description
PPRSPY is a TCPIP utility used for capturing IPDS traces in a Mainframe and AS400 environment
AS/400 or Mainframe WorkStation where PPRPSY is installed WorkStation where the Parser is installed
The IBM Host will send data over TCP/IP to the PC/Workstation running PPR Spy. The PPR Spy tool will
forward the data to the Parser without alteration.
The PPR Spy tool will record the data to a file.
At the end of the job, PPR Spy needs to be stopped to close the recording.
Note: For PPR Spy to record the job, verify that the Host sends the data to the TCP/IP address of
the PC/Workstation. PPR Spy will not record a job sent directly to the Parser.

12.23.2.Setup and Configuration
 Copy PPRSPY2.EXE to a new directory of your local C or D hard drive (for example C:\PPRSPY)
 On your IBM host (Mainframe or AS/400) printer definition change the TCP/IP address to the one of
the PC running the PPR Spy tool (PC IP Address). Be sure to note the port number you are using,
you will need to specify this in the PPR Spy utility (5001)
 Open the utility by double clicking on the application: The Following GUI will appear
 One to one : checked ”1”

 IP Address : Setup the TCP/IP address of the target LinkCom or Host2Net product ”2”
 IP Port : Setup the Port Number of the target LinkCom or Host2Net product ”3”
 PC IP Address : Match this to the IP address of the workstation where the utility is running,
instead of the IP address of the LinkCom or Host2Net.
 Accepting IP Port : Match this to the IP port you have specified your IBM host printer definition
”4”
 File Name : Browse to any location and specify a file name ”5”

 Click on Record ”6”
This will also open a Dos window and the message "waiting for accepting” will display
You can now send the job to the new printer definition setup on you IBM Host pointing to the PPR Spy tool. (On the
PPR Spy DOS window you will see data being received.).
Closing the Trace
When the Job is printed please click the Stop button, this will close the MPI PPR Spy GUI and the MPI
PPR Spy Dos window.
**Please email the file to you MPI technical support representative.**

12.24.How to configure a SNA/HIS LU using Blue Server - Parser session
12.24.1.SNA Server configuration – Create a Printer LU
Attached to the connection, you must create your printer LU. In order to run with MPI Router, you must
define a LUA LU.
- Make a right click on your connection and select Application LU (LUA).
- This new window appears:
Note : The number specified for LU must match the LOCADDR parameter of the VTAM LU Definition

12.24.2.Blue Server - Router Mainframe configuration
12.24.2.1.Connection tab
Notes:
- The other tabs “IPDS Settings”, “Paper Controls”, are not used in this case.
- The SCS Settings tab is only used only for SCS printout.

12.24.3.Blue Server – Parser configuraiton
12.24.3.1.Host tab

12.24.4.Loading the Router Maiframe and Parser
12.24.4.1.SNA
The PSNA201 is SSCP
12.24.5.Blue Server side
With this configuration, you are now able to print SCS or IPDS jobs from your Mainframe IBM host.

12.25.How to allocate a SNA/HIS LU using Blue Server – Telnet session
12.25.1.Description
When you have a LUA printer attached to a SNA Connection, you can assign it to the with the TN3270
service which will transform the SNA data stream to TN 3270 data stream.
AS/400 or Mainframe WorkStation/Server where SNA / HIS is WorkStation/Server where the Blue
installed Server is installed
12.25.2.Allocate a LUA to Telnet

MATRIX is the HIS server : IP address = 192.168.31.15
In the above example, MPI3 Is the SNA connection
PRTSNA02 is the LUA LU defined with MPI3 and assigned to the TN3270 service.

12.25.2.1.PRTSNA02 properties :
12.25.2.1.1.TN3270
Set Type = Generic Printer

12.25.2.1.2.IP Address List
192.168.31.61 is the PC running Blue Server. You must allow this IP Address to access the PRTSNA02
printer

12.25.3.Blue Server configuration:
Telnet Type = Telnet 3270 SCS (Mainframe)

You must specify the HIS Server as “Server IP Address” : in this case Matrix is 192.168.31.15

12.26.How to Initiate Jogging in Blue Server – AOS – Alternate Offset Staker
12.26.1.Description
This article describes the steps needed to initiate jogging in Blue Server.
12.26.2.Procedure
Below are the steps needed to turn the jogging function “on” in Blue Server.
 Open the Blue Server interface and unload your printer. This process will need to be done on all
printers needing the ability to job.
 Right click on the printer and select edit. This will open a window which will allow you to edit
additional printer parameters.
 Scroll down to Section 2, Parameter 21 Alternate Offset Stacker: 1
1 – Enables jogging
0 – Disables jogging
@2 --- Section 2 ---

#1 Defaults switches: 0
#2 Paper size (Upper bin): 0
#3 Paper size (Lower bin): 0
#4 Automatic / manual: 0
#5 Paper sizer (manual bin): 2
#6 Print orientation (Upper bin): 0
#7 Print orientation (Lower bin): 0
#8 Print orientation (Manual bin): 0
#9 Automatic print orientation: 0
#10 Primary tray: 0
#11 Lines Per Inch: 0
#12 Line spacing: 0
#13 Characters Per Inch: 0
#14 Send to Fax: 0
#15 Page Configuration: 1
#16 Text as Graphics: 0
#17 Maximum Page Length: 64
#18 Maximum Print Position: 132
#19 Top binding margin: 2
#20 Left binding margin: 2
#21 Alternate Offset Stacker: 1
#22 Default code page: 0
#23 Code page version: 1
 After parameter 21 has been set click the disk icon in the upper right corner to save and then click
apply.
 Next reload the printer, vary the device off and on again and retest.
 If the job does not jog we will need to capture a trace to verify that the XOA AOS (jog command) is
present in the data.

12.27.How to setup Blue Server for AFP
Warning
In addition to IPDS, The Blue Server (Parser) supports AFPDS input data.
The AFPDS data used in Blue Server may be created with embedded or external resources. The resources
can be fonts, overlays, Page Segments or Formdefs (PageDefs support is not implemented yet).
The Blue Server accepts the AFPDS file from a “Hot Directory”. It transforms the AFPDS to IPDS in order
to take advantage of all the transforms already available (PCL, PostScript …..)
12.27.1.Input Configuration
In this example, “C:\Input_AFP” is the active directory. As soon as a file with the extension .afp arrives in
this directory, Blue Server automatically detects it and processes it.
The software which analyses and transforms the AFPDS to IPDS is the DLL “AfpAnalyzer.dll” located
in the “..\MPI Blue Server\MPI Parser\” directory.
From this point, all the standard Blue Server features are available (transforms, splitting, job naming,….)
In order to rename the output produced, the parameter %FILENAME% has been added to the naming
convention. It represents the name of the input AFPDS file without the extension .afp

12.27.2.External AFP resources
There are specific directories to store the external AFP resources. If a required resource is not embedded in
the AFPDS file, Blue Server searches it first in the corresponding configured directory. If it is not present, it
looks in the “UserLib” configured directory.
I case of a font resources, if it is not found in the AFPDS file nor in the configured directories, The Blue
Server looks at external files for font substitution:
- FGIDLIST.TXT : substitution file for Character Sets
- IbmMpiPages.TXT : substitution file for Code Pages
These font substitution files are located in the “..\MPI Blue Server\MPI Parser\pfont” directory.
12.27.3.AFPDS transform Log

In addition to the standard Blue Server Parser log, “afpsyn.log” located in
“..\MPI Blue Server\MPI Parser\log” is an additional Log file which gives indications about the
AFP transform process.

12.28.How to configure Blue Server AFP font tables
12.28.1.The AFP font resources
There are three kinds of AFP font resources:
12.28.1.1.Font Character Set

Contains the descriptive information, font metrics, and the digital representation of character shapes for a
specified graphic character set. It is a finite set of different graphic or control characters that is complete for
a given purpose. For example, the character set in ISO Standard 646,
The character set may contain a raster or an outline font. In IPDS, the raster font is identified with a FGID
and a Font Width. The outline font is identified with a FGID and a Pointsize (corresponding to a Font Width)
The IBM raster fonts use the prefix C0 (example C0420000 = raster Character set courier latin 1
The IBM outline fonts use the prefix CZ (example CZH200 = Character set Helvetica Latin 1
12.28.1.2.Code Page
Contains A set of assignments, each of which assigns a code point to a character. In IPDS the code page
is „identified with both a GCSGID and a CPGID.
The IBM code pages use the prefix T1 (example T100500= international)
12.28.1.3.Coded Font
Contains elements of a code page and a font character set
The IBM coded fonts use the prefix X0 (example X04140 = char set C0420000 + code page T1000361)
12.28.2.The Blue Server IPDS font ressources

The directory \MPI Parser\Pfont contains the Blue Server font resources:
- A collection of Adobe type one fonts corresponding to the IBM resident fonts (example: mpicou.pfb)
- The file 3812.cpg contains all the code pages known by Blue server.
- The file T1IPDS.fon contains the association adobe type 1 font to a FGID and a list of code page
supported
Example:
#mpicou.pfb,416 ,37,38,256,259,260,273,274,275,276,277,….
- The file Subst4028.xml contains the font correlation between a raster IPDS font (FGID + Font Width)
with the corresponding outline font
Example:
<Substitution>
<RasterCodedFont>
<RegisteredFontID>11</RegisteredFontID>
<FontWidth>144</FontWidth>
</RasterCodedFont>
<OutlineCodedFont>
<RegisteredFontID>416</RegisteredFontID>
<FontWidth>144</FontWidth>
<FontHeight>144</FontHeight>
<Report>1</Report>
</OutlineCodedFont>
</Substitution>

12.28.3.The AFP – IPDS correlation
The default is all the AFP resources are downloaded in IPDS and then incorporated to the transformed
data stream (PCL PS…)
The customers who want to produce PDF from the AFP often have concerns about the PDF file size and
PDF quality.
Example:
from raster fonts they want the fonts to be substituted with outline PDF fonts and only have a subset of the
outline font embedded to the PDF or just want to have the reference of the font in the PDF (It is then
Acrobat reader from its internal font list which makes the substation for the display).
In order to address the right IPDS font, two tables have been produced:
AFPCPSubst.xml this table makes the correspondence between the AFP code page name to the
IPDS code page number (CPGID)
Example:
<CPSUBSTITUTION>
<CODEPAGE>
<NAME>T1V10037</NAME>
<CPGID>37</CPGID>
<DESCRIPTION>USA/CANADA - CECP</DESCRIPTION>
</CODEPAGE>
<CPPRINTER>
<CPGID>37</CPGID>
<DOWNLOAD>false</DOWNLOAD>
</CPPRINTER>
</CPSUBSTITUTION>
AFPFontSubst.xml this table makes the correspondence between the AFP Character set and the
IPDS font selected (FGID + Font Width):
Example:
<CSSUBSTITUTION>
<CHARACTERSET>
<NAMENBR>1</NAMENBR>
<NAMELIST>C0G00001</NAMELIST>
<FGID>2304</FGID>
<DESCRIPTION>Helvetica</DESCRIPTION>
</CHARACTERSET>
<IPDSFONT>
<FGID>2304</FGID>
<FONTWIDTH>67</FONTWIDTH>
<FONTHEIGHT>0</FONTHEIGHT>
<DOWNLOAD>false</DOWNLOAD>
</IPDSFONT>

12.29.How to verify an AS/400 feature for Telnet5250 emulation with Blue
Server
Before loading and SCS Telnet 5250 emulation with MPI Blue Server, check these points on the AS/400.
 Minimum OS/400 V3R1M3 or higher, and the appropriate PTFs or Service Packs,
 The QAUTOVRT system value also applies to printer emulation sessions, so be sure to set it large
enough to allow for necessary printer session as well as display sessions. The default value
QAUTOVRT is set to zero to prevent automatic virtual device creation. You need to change this value.
To allow for up to 50 virtual devices (for example), you have to issue the following command :
CHGSYSVAL SYSVAL(QAUTOVRT) VALUE(50)
 The OS/400 Telnet server needs to be started before the printer emulation can be used. This can be
done by issuing the command :
STRTCPSVR SERVER(*TELNET)
 Alternatively the Operations Navigator interface can be used as well. At the Operation Navigator
screen; select Network → Servers → TCP/IP. If you want the Telnet server to start automatically,
right-click Telnet, selects Properties, click the General tab, and check the box next to "Start this
server automatically when TCP/IP starts."
 You also have to make sure that an interactive subsystem is active to run interactive jobs for Telnet
sessions. The QSPL subsystem needs to be started to run printer passthrough sessions.

12.30.How to Display Blue Server job names on the front panel of your
printer
12.30.1.Description
This article describes the steps needed to display job names from Blue Server on the front panel of your
printer.
12.30.2.Procedure
You must create a Job Header file that will be specified in the Blue Server printer setup. This file will insert
PJL commands and these commands will allow the job name to be displayed on the front panel of your
printer. Note that each printer manufacture may use different PJL commands to produce the job name. We
recommend contacting them for a PJL manual.
12.30.2.1.For Canon imageRUNNER

You can use a basic text editor to produce the file. Below are sample header files.
<ESC>%-12345X@PJL JOB NAME="AFP"
@PJL COMMENT CANPJL SET DOCNAME="%JOBNAME%"
<ESC>%-12345X
12.30.2.2.For Hp or compatible PJL printers

You can use a basic text editor to produce the file. Below are sample header files.
<ESC>%-12345X@PJL JOB NAME="AFP"
@PJL RDYMSG DISPLAY="%JOBNAME%"
<ESC>%-12345X
The above header will produce the job name on an HP printer. Note on HP‟s there is a priority to the
messages that are displayed on the front panel. When the printer is idle and displaying the “Ready”
message this is a priority of 0 (zero). When a job is processing and the printer displays “Processing Job” this
is a higher priority and therefore will over ride the “Ready” message. When using the PJL command
“RDYMSG”, if a front panel message is produced with a higher priority your job name will disappear. Also be
aware that HP‟s require a RDYMSG reset. You can accomplish this by creating a second file or trailer file.
Below is an example.
<ESC>%-12345X@PJL
@PJL COMMENT Restore READY message
@PJL RDYMSG DISPLAY=""
<ESC>%-12345X
Once this file(s) is created save it to the following directory ..\MPI Blue Server\MPI Parser\NT\.
Then in your Blue Server specify the file on the Utilities tab under Job Header File. You can then apply the
printer and test.
If you would like, you can use a number of other parameters in place of the job name. They include the
following :
%JOBNAME% %SESSNAME%
%JOBID% %INCREMENT%
%FORMS% %PRINTERNAME%
%USERNAME% %DATE%
%LIBNAME% %TIME%
%DEVNAME%
%SESSID%

12.31.How to verify an IPDS printer emulation from a MVS host using IP
protocol
 Used your LOGON access for the MVS session,
 From the main menu :
Menu Utilities Compilers Options Status Help

------------------------------------------------------------------------------
ISPF Primary Option Menu
Option ===>
0 Settings Terminal and user parameters User ID . : PHD

1 View Display source data or listings Time. . . : 15:31
2 Edit Create or change source data Terminal. : 3278
3 Utilities Perform utility functions Screen. . : 1
4 Foreground Interactive language processing Language. : ENGLISH
5 Batch Submit job for language processing Appl ID . : ISR
6 Command Enter TSO or Workstation commands TSO logon : ISPFPROC
7 Dialog Test Perform dialog testing TSO prefix: PHD
8 LM Facility Library administrator functions System ID : S390
9 IBM Products IBM program development products MVS acct. : ACCT#
.----------------------------------------------. r Release . : ISPF 4.8
| Licensed Materials - Property of IBM |
| 5647-A01 (C) Copyright IBM Corp. 1980, 1999. |
| All rights reserved. |
| US Government Users Restricted Rights - | s
| Use, duplication or disclosure restricted |
| by GSA ADP Schedule Contract with IBM Corp. |
'----------------------------------------------' ard F8=Forward F9=Swap
F10=Actions F12=Cancel
 Select option 6
 From this menu, enter this command :
TELNET <printer_IP_Address> <Port_Number>
For example:
Menu List Mode Functions Utilities Help
------------------------------------------------------------------------------
ISPF Command Shell
Enter TSO or Workstation commands below:
===> TELNET 192.168.31.201 5001
Place cursor on choice and press enter to Retrieve command
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap

F10=Actions F12=Cancel

 Press enter,
If the connection is possible :

------------------------------------------------------------------------------
ISPF Command Shell
===> TELNET 192.168.31.201 5001
=>
=>
=>
=>
=>
=>
=>
=>
=>
EZA8200I MVS TCP/IP TELNET CS V2R8
EZA8256I Connecting to 192.168.31.201, port 5001
***
If the connection is NOT possible :

------------------------------------------------------------------------------
ISPF Command Shell
===> TELNET 192.168.31.201 5001
=>
=>
=>
=>
=>
=>
=>
=>
=>
EZA8200I MVS TCP/IP TELNET CS V2R8
EZA8256I Connecting to 192.168.31.201, port 5001
EZA8262I Foreign host did not respond within OPEN timeout (8560)
***

12.32.How to remotely access using MPI Parser Service
12.32.1.Description
AS/400 or Mainframe WorkStation where Blue Server is WorkStation where the Parser wants to
installed remotely access
The IBM Host will send data over TCP/IP to the PC/Workstation running Blue Server – Parser session.
The Parser files (PDF, PS2, PCL) can be forwarded to a remote workstation.
12.32.2.Configuration
12.32.2.1.MPI Parser Service Properties
In the Column "Log On As" the default value is LocalSystem

To allow the remotely access, the MPI Parser Service must be configured as follows:
 Select MPI Parser Service,
 Click right, select properties
 Select the Log On Tab,

 Select This account:
 The default value is "LocalSystem"
 Click on Browse box
 And you will get the default name of the workstation / server.

 Change this value to your Domain Name,
 When the Domain Name is displayed, select the Administrator account.
 Select OK, and you will get this new display :

 Enter the Password, and Confirm.
 Select Apply, and you will get this message :
Now your MPI Parser Service is ready for remotely access to other workstation or server
12.32.3.Problems
 If you get the other message => Problem.
 Check the previous steps.

12.33.How to understand Blue Server V7.xx Licensing
12.33.1.Summary
 The Main License Server (MLS) has been renamed to the Main License Daemon (MLD) and the
client (Secondary License Server - SLS) is now called a Main License Client (MLC).
 The Blue Server license module is designed to be run on one central server.
 To configure the Blue Server License system, Java (version 1.3 or higher) must be installed on the
MLD server.
 All remote Blue Servers will poll this server for the required licenses.
 The main license server can report any errors via an email broadcast, a log file or an interface which
can be viewed from any remote PC running the proper software.
12.33.2.Access
Once the Blue Server is installed you can access the license module from the main interface by :
 Double left clicking on the “ “ icon in the upper left corner.

 Or open a MSDos window and run these commands (on the local drive, where Blue Server is
installed) :
CD MPI Blue Server\MPI License
javaw –jar mlditf.jar (enter)
 Your first step is to connect to the main license server.
 You can do this by entering either the IP address or DNS name in the field labeled „Server‟ in the
upper left corner.
 Then click connect.
12.33.2.1.You cannot get an access to GUI

Unfortunately you cannot get an access to the MPI License GUI, and you have checked:
- IP Connection,
- Java version,
- Blue Server V7 version,
Special utilities has been created for identifying problems:
1. MLDiag tools
- Open the MLDiag.exe file from <Local_Drive>:\MPI Blue Server\MPI License
- Double click on it,
- A “licenses.diagnostic.log” file is created,
- Read this file, or send it by mail to you local MPI Tech area.

2. MLRegister tools
- Open the MLRegister.exe file from <Local_Drive>:\MPI Blue Server\MPI License
- Double click on it,
- And you will get the following display
12.33.3.Discovery
There are a couple points to know before moving on.
Any product in red is considered to be in an overflow status. This simply means that the number of active
(loaded) printers for that product exceeds the number of licenses installed. This can be remedied by
unloaded the number of printers in overflow or purchasing an upgraded license.
The second point to know is that the license screen is updated automatically every 15 minutes. You may
not see updated information during an automatic update because remote servers will poll licenses at
different times. To see any updates immediately you must click refresh at the bottom of the interface. Keep
in mind that a server may reside a great distance from the main license server so it could take a minute or
two before the updated information displays.
12.33.4.Definition
The license module contains 5 tabs as well as a registering number field, a server field and a refresh and
exit button.
The registering number is unique to each Blue Server. This number along with some additional information
allows MPI to generate a proper license. The server field along with the refresh button we have already
outlined and the exit button will close the license interface.
Each tab contains information important to managing your license server and Blue Server environment.
1. The first tab, called License Usage, shows over all data for your entire Blue Server environment. It
will display such information as the connected product, platform, version, and so forth.
2. The second tab, Active Products breaks your licenses up by server and product. You will see DNS
and IP addresses for each server as well as last communication between servers. You will also see
the types of products installed and the options being used for each product.
3. The next tab is Registered Licenses. This is where you will install and manage your agreement
numbers. The agreement numbers are generated by MPI and are what define how many active
printers you can safely run.
4. Following the Registered Licenses tab is the Alerts tab. Here you can setup alerts to be sent to you
in the case of a product overflow. You can also enable or disable the license logging and reset
licenses in the case of an extended trial period or license error.
5. The last tab is called Migration. On this tab you will configure all of your remote servers to connect
to the mail license server.

12.33.5.Detail
12.33.5.1.License Usage
Product : This will always say “The Blue Server”. For now this is the only product we have
developed to connect to this license module.
Platform : Our Blue Server versions are being developed to connect to one universal license
platform. This includes our Sun Solaris, Linux and Windows versions.
Ver. : Displays version of remote license module.
Type : There are many different products within Blue Server that can be configured such as
SNA Mainframe, Parser and Telnet. This column displays these products.
Option of : Along with the above mentioned products there are many options under each product
that can be installed such as AFP input, faxing and emailing. They are displayed in this
column.
Speed : This displays the speed in which the printers are configured to rip.
Nb Lic : This column shows the number of licenses installed for the named product.
Lic Used : The total amount of licenses used for a given product are displayed in the column.
Usage : Some products have a limit of pages that can be processed each month such as PDF or
Tiff. This column will show how many pages are defined by the license for a monthly rip.
Used : Here you will see how many total pages have been ripped for each product. If you are
using a product that has a monthly rip limitation the product will show in overflow if the
Used column exceeds the Usage column.

12.33.5.2.Active Products
All columns on this tab have the same definition as the Licenses Usage tab except for the following :
Server : Displays the DNS name of the connected server.
Ip : Displays the IP address of the connected server.
Last Comm : Here you will see the time of the last communication between the remote server and
the main license server.

Button :
Remove Server : You have the option of removing servers from the list by selecting them and clicking
the Remove Server button. If the server is still active it will reappear in the list when
you click refresh.
Check Presence : By selecting a server and clicking this button you can verify that a remote server is
responding to requests from the main license server. If the server does not respond
you need to verify that it is online.
Get Counters : During a Blue Server trial this button will tell you how many days remain on the
installed products. In the below image you can see that “IPDS”, no limit” has a
permanent license of usage.

12.33.5.3.Registered Licenses
All columns on this tab have the same definition as the Licenses Usage tab except for the following.
S/N : This is the internal serial number of the product installed.
Gen Date : Displays the date the licenses were generated by MPI.
Validity : This column displays the date the licenses expire. If the licenses are permanent then
a “No Limit” is displayed.
Button :
Add Agreement : This button allows you to add a new agreement number generated by MPI.
File keys.cfg can be generated, and sent to the customer.
To perform this Agreement update, execute the following steps :
- Stop the MPI License service,
- Copy this file to ”<Local_Drive>:\MPI Blue Server\MPI License”
directory,
- Re Start the MPI License Service.
Delete Agreement : Clicking this button will delete the selected agreement number.

12.33.5.4.Alerts
All columns on this tab have the same definition as the Licenses Usage tab except for the following :
Outgoing SMTP : This is the internal DNS name or IP address of the mail server providing the
SMTP service.
Email address : It is the name of the email sender.
Log to File :.Used to create all “Licenses Services Events” (for tech supports, in case of
problem).
Error log : Display current license server status.
Button :
Save New Setting : Used for saving the new parameters
Load Current Setting : Used for retrieving parameters from the configuration file.
Refresh : Used for displaying the updated modification (Error log for example)
Exit : Used for exit.

Reset License Errors : Used with the agreement of MPI.

12.33.5.5.Migration
 The migration tab will allow you to define your main license server and all of the remote servers you
want to connect.
 To configure the Blue Server License system, Java (version 1.3 or higher) must be installed on the
server/workstation.
 Make sure the “MPI License Service “ is started.
 This action can be done on the MPI License server or on other workstation.
Just copy these files:
- MLDitf.jar
- MLDitf.exe
- Configuration.txt
- Launcher.ini
to the server/workstation, and double click on MLDitf.jar file.
And you will get the following display:
Notes:
If the message: “Communication problem or Licensing Service Stopped” is displayed, check:
- MPI License Service started on the MLD
- Firewall configuration, and
- Server field name.
Make sure in the Server field, the local host (default value) may be replace with the MLD
server name, if the GUI is not running on the MLD server.

1. In the “Add a new MLC” field specify the DNS or IP address of all the Main License Client installed.
2. Then click on the field “>>”
3. In the MLCs to migrate column, the new server should be displayed.
4. Repeat this action as many once as necessary.
5. Then in the field “migrate MLCs to use the following license server (aka MLD)” enter the DNS or
IP address of the remote server you would like to connect.
Note:
In the above display, (i.e: idafr2) only manage the licenses. No Parser and/or Router are installed.

6. Then in the field “migrate MLCs to use the following license server (aka MLD)” enter the DNS or
IP address of the remote server you would like to connect.
Note:
In the above display, (i.e: idafr2) manage the licenses and Parser and/or Router.
7. Next click the “Do Migration” button, and you will get the following display:
8. The migration has been finished.


13. Blue Server Recovery
13.1. Product Support
To aid fast and efficient recovery from a server or system failure it is necessary to have the following items
available from the original installation:
The original Blue Server installation files.
A backup copy of the configuration files.
When the product is being used as a “business critical” application requiring availability 24 hours a day 7
days a week, MPI recommends using one of the following options as a means of backup:
 Use of the MPI Backup system (optional component):
A second copy of Blue Server can be installed on a separate machine in a backup capacity to mirror
the primary server. The backup server will monitor the operation of the primary server and if it
detects a failure will automatically load its copy of the printer configurations ready for operation. The
only manual intervention required is the re-direction of the host data to the backup server.
 Use a Windows active/passive cluster environment. When the active node fails, the passive node
automatically starts the application.
 Use the VMware environment and a backup image of the server.


14. Trademarks
- Adobe® is a trademark of Adobe Systems Incorporated.
- Microsoft® is U.S. registered trademark of the Microsoft Corporation.
- PostScript® is a trademark of adobe Systems.
- PANTONE® Colors generated may not match PANTONE-identified standards. Consult current
PANTONE Publications for the accurate color. PANTONE® and other Pantone, Inc. trademarks are the
property of Pantone, Inc. © Pantone, Inc., 2000.
- True Type™ is U.S. trademark of Apple Computers, Inc.
- Netscape Navigator is a U.S. trademark of Netscape Communications.
- Unix® is a registered trademark of the Open Group.
- Windows®, MS Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
- Portions of this software are copyright © 2006 The FreeType Project (www.freetype.org). All rights
reserved.
==========================================================
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by

the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity

exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical

transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or

Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object

form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications

represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including

the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity

on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of

this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of

this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the

Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or

Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,

any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or

agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,

whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing

the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following

boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");

you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software

distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
==========================================================
*************************************************************
*** ***
*** GIF Image Class Loader and Writer copyright(s) notice ***
*** ***
*************************************************************
---- CxImageICO (c) 07/Aug/2001 <ing.davide.pizzolato@libero.it> ----
CxImage version 5.71 25/Apr/2003
original CImageGIF and CImageIterator implementation are:

Copyright: (c) 1995, Alejandro Aguilar Sierra <asierra@servidor.unam.mx>
6/15/97 Randy Spann: Added GIF87a writing support

R.Spann@ConnRiver.net
DECODE.C - An LZW decoder for GIF

Copyright (C) 1987, by Steven A. Bennett
Copyright (C) 1994, C++ version by Alejandro Aguilar Sierra
GIF and 'Graphics Interchange Format' are trademarks (tm) of Compuserve, Incorporated, an H&R
Block Company.
---- CxImageTIF (c) 07/Aug/2001 <ing.davide.pizzolato@libero.it> ----
CxImage version 5.71 25/Apr/2003

See the file history.htm for the complete bugfix and news report.
Parts of the code come from FreeImage 2

Design and implementation by
- Floris van den Berg (flvdberg@wxs.nl)
- Herve Drolon (drolon@iut.univ-lehavre.fr)
- Markus Loibl (markus.loibl@epost.de)
- Luca Piergentili (l.pierge@terra.es)
LibTIFF is:
Copyright (c) 1988-1997 Sam Leffler
Copyright (c) 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software and its documentation for any
purpose is hereby granted without fee, provided that (i) the above copyright notices and this
permission notice appear in all copies of the software and related documentation, and (ii) the
names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating
to the software without the specific, prior written permission of Sam Leffler and Silicon
Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE,
INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT
OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
---- miGIF Compression - mouse and ivo's GIF-compatible compression ----
Copyright (C) 1998 Hutchison Avenue Software Corporation

http://www.hasc.com
info@hasc.com
Permission to use, copy, modify, and distribute this software and its documentation for any
purpose and without fee is hereby granted, provided that the above copyright notice appear in all
copies and that both that copyright notice and this permission notice appear in supporting
documentation. This software is provided "AS IS." The Hutchison Avenue Software Corporation
disclaims all warranties, either express or implied, including but not limited to implied
warranties of merchantability and
fitness for a particular purpose, with respect to this code and accompanying documentation.
The miGIF compression routines do not, strictly speaking, generate files conforming to the GIF
spec, since the image data is not LZW-compressed (this is the point: in order to avoid
transgression of the Unisys patent on the LZW algorithm.) However, miGIF generates data streams
that any reasonably sane LZW decompresser will decompress to what we want.
miGIF compression uses run length encoding. It compresses horizontal runs of pixels of the same
color. This type of compression gives good results on images with many runs, for example images
with lines, text and solid shapes on a solid-colored background. It gives little or no compression
on images with few runs, for example digital or scanned photos.
der Mouse
mouse@rodents.montreal.qc.ca
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ivo@hasc.com
The Graphics Interchange Format(c) is the Copyright property of

CompuServe Incorporated. GIF(sm) is a Service Mark property of
CompuServe Incorporated.
---- $Id: FilterRotate.cpp,v 1.10 2000/12/18 22:42:53 uzadow Exp $ ----
Copyright (c) 1996-1998 Ulrich von Zadow

********************************
*** ***
*** JPEG copyright(s) notice ***
*** ***
********************************
This software (The Blue Server) is based in part on the work of the Independent JPEG Group.
***********************************
*** ***
*** NETSNMP copyright(s) notice ***
*** ***
***********************************
---- Part 1: CMU/UCD copyright notice: (BSD like) -----
Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000

Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose
and without fee is hereby granted, provided that the above copyright notice appears in all copies
and that both that copyright notice and this permission notice appear in supporting documentation,
and that the name of CMU and The Regents of the University of California not be used in
advertising or publicity pertaining to distribution of the software without specific written
permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU
OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----
Copyright (c) 2001-2003, Networks Associates Technology, Inc

All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials provided with
the distribution.
* Neither the name of the Networks Associates Technology, Inc nor the names of its contributors
may be used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----
Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd. All rights reserved.
the distribution.
* The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER `ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----
Copyright © 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
California 95054, U.S.A. All rights reserved.
Use is subject to license terms below.
This distribution may include materials developed by third parties.
Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
the distribution.
* Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written permission.
---- Part 5: Sparta, Inc copyright notice (BSD) -----
Copyright (c) 2003-2004, Sparta, Inc

* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
the distribution.
* Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
********************************
*** ***
*** TIFF copyright(s) notice ***
*** ***
********************************
Copyright (c) 1988-1997 Sam Leffler

Copyright (c) 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software and its documentation for any
purpose is hereby granted without fee, provided that (i) the above copyright notices and this
permission notice appear in all copies of the software and related documentation, and (ii) the
names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating
to the software without the specific, prior written permission of Sam Leffler and Silicon
Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE,
INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT
OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
**********************************
*** ***
*** JASPER copyright(s) notice ***
*** ***
**********************************
Copyright (c) 1999-2000 Image Power, Inc. and the University of

British Columbia.
Copyright (c) 2001-2002 Michael David Adams.
JasPer Software License
IMAGE POWER JPEG-2000 PUBLIC LICENSE

************************************
GRANT:

Permission is hereby granted, free of charge, to any person (the "User") obtaining a copy of this
software and associated documentation, to deal in the JasPer Software without restriction,
including without limitation the right to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the JasPer Software (in source and binary forms), and to permit
persons to whom the JasPer Software is furnished to do so, provided further that the License
Conditions below are met.
License Conditions
******************
A. Redistributions of source code must retain the above copyright notice, and this list of
conditions, and the following disclaimer.
B. Redistributions in binary form must reproduce the above copyright notice, and this list of
conditions, and the following disclaimer in the documentation and/or other materials provided with
the distribution.
C. Neither the name of Image Power, Inc. nor any other contributor (including, but not limited
to, the University of British Columbia and Michael David Adams) may be used to endorse or promote
products derived from this software without specific prior written permission.
D. User agrees that it shall not commence any action against Image Power, Inc., the University of
British Columbia, Michael David Adams, or any other contributors (collectively "Licensors") for
infringement of any intellectual property rights ("IPR") held by the User in respect of any
technology that User owns or has a right to license or sublicense and which is an element required
in order to claim compliance with ISO/IEC 15444-1 (i.e., JPEG-2000 Part 1). "IPR" means all
intellectual property rights worldwide arising under statutory or common law, and whether or not
perfected, including, without limitation, all (i) patents and patent applications owned or
licensable by User; (ii) rights associated with works of authorship including copyrights,
copyright applications, copyright registrations, mask work rights, mask work applications, mask
work registrations; (iii) rights relating to the protection of trade secrets and confidential
information; (iv) any right analogous to those set forth in subsections (i), (ii), or (iii) and
any other proprietary rights relating to intangible property (other than trademark, trade dress,
or service mark rights); and (v) divisions, continuations, renewals, reissues and extensions of
the foregoing (as and to the extent applicable) now existing, hereafter filed, issued or acquired.
E. If User commences an infringement action against any Licensor(s) then such Licensor(s) shall
have the right to terminate User's license and all sublicenses that have been granted hereunder by
User to other parties.
F. This software is for use only in hardware or software products that are compliant with ISO/IEC
15444-1 (i.e., JPEG-2000 Part 1). No license or right to this Software is granted for products
that do not comply with ISO/IEC 15444-1. The JPEG-2000 Part 1 standard can be purchased from the
ISO.
THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.

NO USE OF THE JASPER SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. THE JASPER
SOFTWARE IS PROVIDED BY THE LICENSORS AND CONTRIBUTORS UNDER THIS LICENSE ON AN `ÀS-IS'' BASIS,
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
WARRANTIES THAT THE JASPER SOFTWARE IS FREE OF DEFECTS, IS MERCHANTABLE, IS FIT FOR A PARTICULAR
PURPOSE OR IS NON-INFRINGING. THOSE INTENDING TO USE THE JASPER SOFTWARE OR MODIFICATIONS THEREOF
FOR USE IN HARDWARE OR SOFTWARE PRODUCTS ARE ADVISED THAT THEIR USE MAY INFRINGE EXISTING PATENTS,
COPYRIGHTS, TRADEMARKS, OR OTHER INTELLECTUAL PROPERTY RIGHTS.
THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE JASPER SOFTWARE IS WITH THE USER. SHOULD
ANY PART OF THE JASPER SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, THE USER (AND NOT THE INITIAL
DEVELOPERS, THE UNIVERSITY OF BRITISH COLUMBIA, IMAGE POWER, INC., MICHAEL DAVID ADAMS, OR ANY
OTHER CONTRIBUTOR) SHALL ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. UNDER
NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR
OTHERWISE, SHALL THE INITIAL DEVELOPER, THE UNIVERSITY OF BRITISH COLUMBIA, IMAGE POWER, INC.,
MICHAEL DAVID ADAMS, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE JASPER SOFTWARE, OR ANY
SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO THE USER OR ANY OTHER PERSON FOR ANY INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION,
DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY HAD BEEN INFORMED, OR OUGHT TO HAVE KNOWN, OF THE
POSSIBILITY OF SUCH DAMAGES. THE JASPER SOFTWARE AND UNDERLYING TECHNOLOGY ARE NOT FAULT-TOLERANT
AND ARE NOT DESIGNED, MANUFACTURED OR INTENDED FOR USE OR RESALE AS ON-LINE CONTROL EQUIPMENT IN
HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR
FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, DIRECT LIFE SUPPORT
MACHINES, OR WEAPONS SYSTEMS, IN WHICH THE FAILURE OF THE JASPER SOFTWARE OR UNDERLYING TECHNOLOGY
OR PRODUCT COULD LEAD DIRECTLY TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL
DAMAGE ("HIGH RISK ACTIVITIES"). LICENSOR SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY
OF FITNESS FOR HIGH RISK ACTIVITIES. USER WILL NOT KNOWINGLY USE, DISTRIBUTE OR RESELL THE JASPER
SOFTWARE OR UNDERLYING TECHNOLOGY OR PRODUCTS FOR HIGH RISK ACTIVITIES AND WILL ENSURE THAT ITS
CUSTOMERS AND END-USERS OF ITS PRODUCTS ARE PROVIDED WITH A COPY OF THE NOTICE SPECIFIED IN THIS
SECTION.
***********************************
*** ***
*** zlib copyright(s) notice ***
*** ***
***********************************
zlib.h -- interface of the 'zlib' general purpose compression library. version 1.2.3, July 18th,
2005
Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the
authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial
applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the
original software. If you use this software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as
being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly jloup@gzip.org

Mark Adler madler@alumni.caltech.edu
zlib software copyright © 1995-2004 Jean-loup Gailly and Mark Adler.
***********************************
*** ***
*** libpng copyright(s) notice ***
*** ***
***********************************
This copy of the libpng notices is provided for your convenience. In case of any discrepancy
between this copy and the notices in the file png.h that is included in the libpng distribution,
the latter shall prevail.
COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
If you modify libpng you may insert additional notices immediately following this sentence.
libpng versions 1.0.7, July 1, 2000, through 1.2.5, October 3, 2002, are Copyright (c) 2000-2002
Glenn Randers-Pehrson and are distributed according to the same disclaimer and license as libpng-
1.0.6 with the following individuals added to the list of Contributing Authors
Simon-Pierre Cadieux
Eric S. Raymond
Gilles Vollant
and with the following additions to the disclaimer:
There is no warranty against interference with your enjoyment of the library or against
infringement. There is no warranty that our efforts or the library will fulfill any of your
particular purposes or needs. This library is provided with all faults, and the entire risk of
satisfactory quality, performance, accuracy, and effort is with the user.
libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are Copyright (c) 1998, 1999
Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-
0.96,with the following individuals added to the list of Contributing Authors:
Tom Lane
Glenn Randers-Pehrson
Willem van Schaik
libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright (c) 1996, 1997 Andreas
Dilger Distributed according to the same disclaimer and license as libpng-0.88, with the following
individuals added to the list of Contributing Authors:
John Bowler
Kevin Bracey
Sam Bushell
Magnus Holmgren
Greg Roelofs
Tom Tanner
libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright (c) 1995, 1996 Guy Eric
Schalnat, Group 42, Inc.
For the purposes of this copyright and license, "Contributing Authors" is defined as the following
set of individuals:
Andreas Dilger
Dave Martindale
Guy Eric Schalnat
Paul Schmidt
Tim Wegner
The PNG Reference Library is supplied "AS IS". The Contributing Authors and Group 42, Inc.
disclaim all warranties, expressed or implied, including, without limitation, the warranties of
merchantability and of fitness for any purpose. The Contributing Authors and Group 42, Inc.
assume no liability for direct, indirect, incidental, special, exemplary, or consequential

damages, which may result from the use of the PNG Reference Library, even if advised of the
possibility of such damage.
Permission is hereby granted to use, copy, modify, and distribute this source code, or portions
hereof, for any purpose, without fee, subject to the following restrictions:
1. The origin of this source code must not be misrepresented.
2. Altered versions must be plainly marked as such and must not be misrepresented as being the
original source.
3. This Copyright notice may not be removed or altered from any source or altered source
distribution.
The Contributing Authors and Group 42, Inc. specifically permit, without fee, and encourage the
use of this source code as a component to supporting the PNG file format in commercial products.
If you use this source code in a product, acknowledgment is not required but would be appreciated.
A "png_get_copyright" function is available, for convenient use in "about" boxes and the like:
printf("%s",png_get_copyright(NULL));
Also, the PNG logo (in PNG format, of course) is supplied in the files "pngbar.png" and
"pngbar.jpg (88x31) and "pngnow.png" (98x31).

Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a certification mark
of the Open Source Initiative.
Glenn Randers-Pehrson
randeg@alum.rpi.edu
October 3, 2002
***********************************
*** ***
*** lua.org copyright(s) notice ***
*** ***
***********************************
Copyright © 1994-2008 Lua.org, PUC-Rio.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
URL : http://www.lua.org
***********************************
*** ***
*** cip4 copyright(s) notice ***
*** ***
***********************************
This package includes software developed by the The International Cooperation for the Integration
of Processes in Prepress, Press and Postpress (www.cip4.org), specifically, the CIP4 JDFWrapper
C++ Library.
Copyright © 2001-2005 The International Cooperation for the Integration of Processes in Prepress,
Press and Postpress (CIP4). All rights reserved. The CIP4 Software License, Version 1.0 may be
found at http://www.cip4.org/open_source/cip4_software_license.html.
Redistribution and use of this library in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
The end-user documentation included with the redistribution, if any, must include the following
acknowledgment:
This product includes software developed by the The International Cooperation for the Integration
of Processes in Prepress, Press and Postpress (www.cip4.org).
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-
party acknowledgments normally appear.

The names CIP4 and The International Cooperation for the Integration of Processes in Prepress,
Press and Postpress must not be used to endorse or promote products derived from this software
without prior written permission. For written permission, please contact info@cip4.org.
Products derived from this software may not be called CIP4, nor may CIP4 appear in their name,
without prior written permission of the CIP4 organization.
Usage of this software in commercial products is subject to restrictions. For details please
consult info@cip4.org.
THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE INTERNATIONAL COOPERATION FOR THE INTEGRATION OF PROCESSES IN
PREPRESS, PRESS AND POSTPRESS OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.


15. CUSTOMER SUPPORT AND WARRANTY INFORMATION
15.1. Customer Support
MPI has support services available from France, Denmark, United Kingdom, Germany, and USA (California
and Virginia) to help you in case of difficulties with this product.
15.2. Authorized Dealers

If you determine that the Blue Server requires support, call your local authorized MPI dealer or call MPI:
 + 33 (0) 1 45 73 09 40 in France,
 + 45 4436 6000 in Denmark,
 + 44 (0) 1344 891 008 in UK,
 + 49 (0) 89 35 4762 30 in Germany,
 + 1 (714) 840 80 77 in California (West coast – USA),
 + 1 (703) 243 3322 in Virginia (East coast – USA).
during normal business hours.
15.3. User Warranty

This product is warranted against malfunction for a period of 3 months from the date of installation by the
End User. During this warranty period, MPI will provide bug fixes at no charge provided the host and the
network environment have not been modified.
This warranty does not apply if this product has been damaged by accident or misuse, or as the result of
service and modification by other than an authorized dealer or MPI Support Service Facility. No other
express warranty is given by MPI. In particular MPI shall not be liable for consequential damages or indirect
losses.
15.4. Maintenance
In order to guaranty a proper operation of your Blue Server Software over the years, and specifically in case
of Host and Network environment evolutions or modifications, please subscribe the MPI maintenance
agreement through your local authorized MPI dealer or directly with MPI
15.5. End User License Agreement for MPI Tech Software

Important: Please read this License carefully before using this Software.
This End User License Agreement ("EULA") is a legal and binding agreement between The End User (either an
individual or a single entity) and MPI Tech Group, its subsidiaries, affiliates, agents and OEM licensees (
collectively, "MPI Tech") for the Software The End User are about to download (or otherwise install, access or use)
and the associated proprietary media, printed materials, any associated documentation (including any electronic
documentation) provided to The End User by MPI Tech (collectively "Software"), however said Software is named
or branded. Any software updates, add-on components, web services, enhancements or supplements that MPI
Tech, its licensees or agents may provide to The End User or make available to The End User, by key permission
access or otherwise, after the date The End User obtain The End User initial copy of the Software, shall be
deemed to be "Software" within the scope of this EULA, from and after the date permission is granted to The End
User, to the extent that such items are not accompanied by a separate license agreement or terms of use. By
installing, copying, downloading, accessing or otherwise using the Software, The End User manifest The End User
consent to and agreement to be bound by the terms of this EULA. If The End User do not agree to the terms of this
EULA, do not install, access or use the Software, but immediately cease the download / return the unused
Software to the place of the original purchase.

SOFTWARE LICENSE
The Software is protected by intellectual property laws and treaties. Any references hereunder to "sales" or
"acquisition" or like terms notwithstanding, the Software is licensed, not sold, and rights granted hereunder are
limited to the Software in object code only. No source code rights are granted hereby. The End User may not
assign or otherwise transfer this EULA to any other party, without specific written permission from MPI Tech.
1 GRANT OF LICENSE. Under copyright law the End User are not permitted to install or run the Software
product ('the Software') or use the electronic material ('the Documentation') supplied to the End User without the
permission of the Owner. In consideration of the End User accepting the terms of this agreement the Owner grants
the End User a non-exclusive right ('the License') to install and run the Software and use the Documentation as
permitted by this Agreement. All references to the Software mean the object code only of the program(s)
comprising the Software. The End User has no rights to distribute, copy, reverse-engineer, modify or adapt the
Software unless such rights are clearly and specifically granted herein.
1.1 General License to Install and Use Software Product.
1.1.1 The End User may use the Software and the Documentation in connection with a single computer or such
other number of computers as may be specifically licensed and for which license fees have been paid, as reflected
on license records generated in connection with the acquisition of the Software ("License Record");
1.1.2 The End User may load the Software and use it only on a single computer which is under the control or
such other number of computers as may be specifically licensed and also under the End User control.
1.1.3 The End User may use the Software for its personal use or in its business or profession. The license
granted hereunder may not be shared and permitting unauthorised access to, copying or use of the Software and
the Documentation is beyond the scope of the license and is therefore a breach of this Agreement.
1.2 Additional License Permitting Use of Software under a Subscription or Service Agreement. If The End
User licensed the Software under a subscription ("Subscription Product"), the following additional licensing terms
apply and supersede any inconsistent provision under section 1.1: During the term of The End User subscription
only, The End User may install the Software on a single computer which is under its control or such other number
of computers as may be specifically licensed and also under its control. The initial subscription period begins on
the date The End User first activate its copy of the Subscription Product and ends at the end of the subscription
period, as set forth under the License Record. The End User cannot use the Subscription Product on any
computer after its subscription expires unless The End User renew or extend its subscription. By renewing or
extending its subscription, The End User will be entitled to continue using the Subscription Product for a specified
period of time beyond the date when its previous subscription would have otherwise ended. All the terms and
conditions of this EULA will continue to apply to its use of the Subscription Product during any subsequent renewal
periods unless otherwise specified. Separation of Component Parts: The Software Product is licensed as a single
product and its component parts may not be separated, except as may be provided in the Documentation, unless
expressly authorized by MPI Tech in writing.
1.3 Updates, Enhancements and Supplemental Software. No Software maintenance or support is included in
the calculation of license fees paid in consideration for this EULA. Any rights The End User may be granted for
Software maintenance or support, including updates, patches, enhancements, modifications or other support
services related to the Software ("Support Services") are beyond the scope of this EULA and will be the subject of
and governed by a separate maintenance or support agreement (if any) between The End User and MPI Tech or
licensed MPI Tech 'resellers, distributors or OEM providers' (Resellers), and may be subject to the payment of
additional fees. Support Services provided by MPI Tech or its Resellers are governed by the policies and programs
adopted from time to time by MPI Tech or by those Resellers offering such services, as described in the
Documentation, or in other materials furnished by MPI Tech or its Resellers.
1.4 Reservation of Rights. All rights not expressly granted are retained by MPI Tech.
2. ADDITIONAL RIGHTS, TERMS AND LIMITATIONS
2.1 License Fees. All license fees (and, if applicable, subscription or service fees) The End User have paid are
non-refundable, except in connection with a return of the Software as provided in the initial paragraph of this EULA
or under section 6.1.
2.2 Intellectual Property Rights. All title and intellectual property rights in and to the Software and all elements
and components, the accompanying printed materials, and any copies of the Software are owned by MPI Tech or
its suppliers/licensors. If this Software contains documentation that is provided only in electronic form, the End
User may print ten copies of such electronic documentation. The End User may not copy the printed materials
accompanying the Software. MPI Tech retains all rights in and to any copy, translation, modification, enhancement,
improvement, development, adaptation or derivative works of the Software, including all unauthorised work.

2.3 Copy Protection. The Software may incorporate copy protection technology to prevent the unauthorised
copying of the Software or may require original media for use of the Software on the Device. It is unlawful and
prohibited to make unauthorised copies of the Software or to circumvent any copy protection technology included in
the Software.
2.4 Rental, leasing or commercial hosting. The End User may not rent, lease, lend or provide commercial
hosting services to third parties with the Software, without MPI Tech's express written authorization.
2.5 Compliance. The End User agree to supervise and control use of the Software to ensure compliance with
all terms and limitations under this EULA (including but not limited to compliance with the laws and regulations of
all applicable jurisdictions in which The End User use the Software) and to maintain accurate records of the
number and location of all users and copies of the Software and the number of storage devices used in connection
with the Software (Compliance Data"). In this connection, The End User also agrees to the following:
2.5.1 The End User agree to provide to MPI Tech with summaries of updated Compliance Data, in a form
reasonably required by MPI Tech, within thirty (30) days of any written request, and to furnish therewith written
certification that its use of the Software at the time of the request complies with this EULA. As an alternative to
such written reports or certification, and at MPI Tech's sole option, The End User agree to enable and to allow MPI
Tech to collect, via a Web interface, ONLY the record of the number of installed clients; and
2.5.2 The End User agree to allow MPI Tech or its agents full access, on 14 days' notice and during normal
business hours, to all of the devices on which the Software is loaded or from which it may be accessed "Devices"),
and to the site or sites on which Devices are located, to monitor its compliance with this section 2.5 and the other
terms of this EULA.; and
2.5.3 The End User agree to make all relevant employees, agents, advisers, consultants, group-companies,
affiliates, sub-contractors and other parties who have use of or access to the Software aware of the provisions of
this Agreement prior to such use or access, and shall ensure compliance by such users with this EULA.
2.6 The End User acknowledge that in the event that the End User have been granted a licence pursuant to
this agreement for a Subscription Product we may without notice enable the Subscription Product so that it shall
cease to operate at the end of the licence term in any event.
3. TERM AND TERMINATION
3.1 This EULA shall terminate automatically on the date (if any) specified on the License Record, unless
extended by the prior mutual consent of the parties in writing. If no date is specified on the License Record, this
EULA shall be perpetual subject to termination in accordance with subsections 3.2 below. The End User may
terminate this EULA at any time by destroying the Software and the Documentation together with all copies in any
form. However, no license fee paid or owing for the Software shall be refunded or abated by virtue of such
unilateral termination.
3.2 Furthermore, the License to use the Software will terminate automatically if The End User fails to comply
with any term of this EULA. Unless applicable license fees are paid in full, this EULA and all licenses granted
hereunder will also terminate without further action and may also terminate on notice by MPI Tech if The End User
become unable to pay its debts or are otherwise insolvent, bankrupt, appoint an Administrator, cease trading,
become the subject of any liquidation or winding up action in any jurisdiction, enter into any arrangement with its
creditors other than for the purpose of a solvent reorganisation or become the subject of any action under which a
receiver or administrator is appointed by a court, regulatory agency or other authority or in the event that any local
equivalent of the aforesaid arise in any jurisdiction. Upon expiration or termination of the EULA for any reason The
End User will immediately destroy the Software together with all copies in any form, including copies on its hard
and back-up disks. Any use of any copies of the Software after expiration or termination of the License is unlawful.
3.3 Termination of this EULA shall be without prejudice to the accrued rights and liabilities of either party.
4. INDEMNITY. The End User agree to defend, indemnify and hold harmless MPI Tech, its subsidiaries,
affiliates, distributors, licensors, suppliers, officers, directors, employees and agents from any third party claims,
damages, liabilities, costs and fees (including reasonable attorney fees) arising from its use of the Software as well
as from its failure to comply with any term of this EULA. The End User agrees that MPI Tech shall have no liability
whatsoever for any use The End User make of the Software.

5. US GOVERNMENT RESTRICTED RIGHTS. This Software is commercial computer software and the
related documentation is commercial computer software documentation. Thus, if The End User are an agency,
department, or other entity of the United States Government ("Government"), the use, duplication, reproduction,
release, modification, disclosure or transfer of the Software, or any related documentation of any kind, including
technical data or related manuals, is restricted in accordance with Federal Acquisition Regulation 12.212 for civilian
agencies and Defence Federal Acquisition Regulation Supplement 227.7202 for military agencies to the extent said
regulations apply to solicitations within the scope of said regulations. The use of the Software and related
documentation is further restricted in accordance with the terms of this Agreement, or any modification hereto.
MPI Technologies Inc., a US subsidiary of MPI Tech Group, is located at
MPI Tech, 4952 Warner Avenue, Suite 301, Huntington Beach, CA 92649-5506, USA.
6. LIMITED WARRANTY
6.1 LIMITED WARRANTY FOR SOFTWARE ACQUIRED IN THE US, EU AND CANADA: MPI Tech warrants
that the Software, when used properly, will perform substantially as described in the accompanying materials and
documentation for a period of thirty (30) days from the date of receipt and that the media on which the Software is
recorded will be free from defects in material and workmanship under normal use for the same period.
If an implied warranty or condition is created by the End User state/jurisdiction and federal/national or
state/provincial law prohibits disclaimers of it, the End User may also have an implied warranty or condition, BUT
ONLY AS TO DEFECTS DISCOVERED DURING THE PERIOD OF THIS LIMITED WARRANTY (THIRTY DAYS).
AS TO ANY DEFECTS DISCOVERED AFTER THE THIRTY (30) DAY PERIOD, THERE IS NO WARRANTY OR
CONDITION OF ANY KIND. Some states/jurisdictions do not allow limitations on how long an implied warranty or
condition lasts, so the above limitation may not apply to The End User.
Any supplements or updates to the SOFTWARE PRODUCT, including without limitation, any (if any) service packs
or hot fixes provided to the End User after the expiration of the initial thirty (30) days Limited Warranty period are
not covered by any warranty or condition, express, implied or statutory.
6.1.1 LIMITATION ON REMEDIES; NO CONSEQUENTIAL OR OTHER DAMAGES. The End User exclusive
remedy for any breach of this Limited Warranty is as set forth below. Except for any refund elected by MPI Tech,
THE END USER ARE NOT ENTITLED TO ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
CONSEQUENTIAL DAMAGES. The terms of Section 8 below ("Exclusion of Incidental, Consequential and Certain
Other Damages") are also incorporated into this Limited Warranty. Some states/jurisdictions do not allow the
exclusion or limitation of incidental or consequential damages, so the above limitation or exclusion may not apply to
the End User. This Limited Warranty gives the End User specific legal rights. The End User may have others
which vary from state/jurisdiction to state/jurisdiction.
6.1.2 THE END USER EXCLUSIVE REMEDY. The entire liability of MPI Tech and its suppliers and the End
User exclusive remedy relative to any Software, that does not meet this Limited Warranty and that is returned to the
original place of purchase with a copy of the End User proof of purchase, shall be, at MPI Tech's sole option
exercised subject to applicable law, either (a) return of the price paid (if any) for the Software, or (b) repair or
replacement of the Software. The End User will receive the remedy elected by MPI Tech without charge, except
that the End User are responsible for any expenses the End User may incur (e.g. cost of returning the Software to
MPI Tech). This Limited Warranty is void if failure of the Software has resulted from accident, abuse,
misapplication, abnormal use or a virus. Any replacement Software will be warranted for the remainder of the
original warranty period or twenty (20) days, whichever is longer. To exercise the End User remedy, contact MPI
Tech in writing at one of the following addresses:
MPI Tech A/S, Vadstrupvej 35, 2880, Bagsvaerd, Denmark.
MPI Tech SAS, 40, Rue du Général Malleret-Joinville, BP 88, 94402 Vitry Sur Seine Cedex, France
6.2 LIMITED WARRANTY FOR SOFTWARE PRODUCTS ACQUIRED OUTSIDE THE EU, US AND
CANADA. FOR THE LIMITED WARRANTIES AND SPECIAL PROVISIONS PERTAINING TO THE END USER
PARTICULAR JURISDICTION, PLEASE REFER TO THE WARRANTY PROVIDED TO THE END USER WITH
THE SOFTWARE DOCUMENTATION. IF NO SPECIAL AND SEPARATE WARRANTY IS APPLICABLE, THE
WARRANTIES OF MPI Tech AND ITS SUPPLIERS SHALL BE LIMITED AS PROVIDED HEREIN TO THE
FULLEST EXTENT ALLOWED UNDER THE LAWS OF THE APPLICABLE JURISDICTION. MPI TECH HEREBY
EXCLUDES ALL IMPLIED WARRANTIES TO THE FULLEST EXTENT ALLOWED BY LAW IN EACH
JURISDICTION IN WHICH THE SOFTWARE IS USED UNDER THIS EULA.

7. GENERAL DISCLAIMER OF WARRANTIES. THE LIMITED WARRANTY THAT APPEARS IN SECTION
6 ABOVE IS THE ONLY EXPRESS WARRANTY MADE TO THE END USER AND IS PROVIDED IN LIEU OF
ANY OTHER EXPRESS WARRANTIES (IF ANY) CREATED BY ANY DOCUMENTATION OR PACKAGING.
EXCEPT FOR THE LIMITED WARRANTY AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE
LAW, MPI Tech AND ITS SUPPLIERS PROVIDE THE SOFTWARE AND SUPPORT SERVICES (IF ANY) AS IS
AND WITH ALL FAULTS, AND HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, EITHER
EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY (IF ANY) IMPLIED
WARRANTIES, DUTIES OR CONDITIONS OF MERCHANTABILITY, OF FITNESS FOR A PARTICULAR
PURPOSE, OF ACCURACY OR COMPLETENESS OR RESPONSES, OF RESULTS, OF WORKMANLIKE
EFFORT, OF LACK OF VIRUSES AND OF LACK OF NEGLIGENCE, ALL WITH REGARD TO THE SOFTWARE,
AND THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES. ALSO, THERE IS NO
WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO
DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SOFTWARE.
8. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES. TO THE
MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MPI Tech OR ITS SUPPLIERS
BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER.
MPI Tech SHALL NOT BE LIABLE FOR THE FOLLOWING TYPES OF LOSS IN ANY EVENT, BE THEY DIRECT
OR CONSEQUENTIAL DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION,
FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO
MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR
ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER AND ANY OTHER LOSS ARISING OUT OF OR IN
ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE PRODUCT, THE PROVISION
OF OR FAILURE TO PROVIDE SUPPORT SERVICES, OR OTHERWISE UNDER OR IN CONNECTION WITH
ANY PROVISION OF THIS EULA, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE),
STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF MPI Tech OR ANY SUPPLIER,
AND EVEN IF MPI Tech OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
9. LIMITATION OF LIABILITY AND REMEDIES. NOTWITHSTANDING ANY DAMAGES THAT THE END
USER MIGHT INCUR FOR ANY REASON WHATSOEVER (INCLUDING, WITHOUT LIMITATION, ALL
DAMAGES REFERENCED ABOVE AND ALL DIRECT OR GENERAL DAMAGES), THE ENTIRE LIABILITY OF
MPI TECH AND ANY OF ITS SUPPLIERS UNDER ANY PROVISION OF THIS EULA AND THE END USER
EXCLUSIVE REMEDY FOR ALL OF THE FOREGOING (EXCEPT FOR ANY REMEDY OF REPAIR OR
REPLACEMENT ELECTED BY MPI TECH WITH RESPECT TO ANY BREACH OF THE LIMITED WARRANTY)
SHALL BE LIMITED TO THE GREATER OF 110% OF THE AMOUNT ACTUALLY PAID BY THE END USER FOR
THE SOFTWARE OR U.S. $250.00. THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS
(INCLUDING SECTIONS 6, 7, AND 8, ABOVE) SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY
APPLICABLE LAW, EVEN IF ANY REMEDY FAILS ITS ESSENTIAL PURPOSE.
10. APPLICABLE LAW. If the End User acquired this Software in the United States, Canada, or any country of
South America, and unless expressly prohibited by local law, this EULA shall be governed and construed under
California (USA) law (without regard to its conflicts of laws provisions) as such law applies to agreements between
Californian residents entered into and to be performed within California. The sole and exclusive jurisdiction and
venue for actions arising under this Agreement shall be the State and Federal courts in California.
If the End User acquired this Software in any other country, and unless expressly prohibited by local law, this EULA
shall be governed by the laws of Switzerland (Code Suisse des Obligations) by the Court in Geneva.
The End User consent and submit to the jurisdiction of the applicable courts, as provided above, and agree to
service of process in accordance with the applicable court rules. The party prevailing in any dispute under this
Agreement shall be entitled to its costs and legal fees.
11. GENERAL PROVISIONS. This Agreement and the terms of any License Record provided to the End User
(if any) combine to represent the complete agreement concerning this license between the parties and supersedes
all prior agreements and representations between them. This EULA may be amended only in writing executed by
both parties. If any provision of this EULA is held to be illegal or unenforceable, that provision shall be limited or
eliminated to the minimum extent necessary to make it legal and enforceable and this Agreement shall otherwise
remain in full force and effect and enforceable. The failure of MPI Tech to act with respect to a breach of this EULA
by The End User or others does not constitute a waiver and shall not limit MPI Tech's rights with respect to such
breach or any subsequent breaches. This EULA is personal to the End User and may not be assigned or
transferred for any reason whatsoever without MPI Tech's prior written consent and any action or conduct in
violation of the foregoing shall be void and without effect. MPI Tech expressly reserves the right to assign this
Agreement and to delegate any of its obligations hereunder.
EACH PARTY RECOGNIZES AND AGREES THAT THE WARRANTY DISCLAIMERS AND LIABILITY AND
REMEDY LIMITATIONS IN THIS AGREEMENT ARE MATERIAL BARGAINED FOR BASES OF THIS
AGREEMENT AND THAT THEY HAVE BEEN TAKEN INTO ACCOUNT AND REFLECTED IN DETERMINING
THE CONSIDERATION TO BE GIVEN BY EACH PARTY UNDER THIS AGREEMENT AND IN THE DECISION
BY EACH PARTY TO ENTER INTO THIS AGREEMENT.
Questions concerning this Agreement should be sent to the either of the addresses set forth below. Any notices or
correspondences will only be effective if sent to such address:
MPI Tech A/S, Vadstrupvej 35, 2880, Bagsvaerd, Denmark.
MPI Tech SAS, 40, Rue du Général Malleret-Joinville, BP 88, 94402 Vitry Sur Seine Cedex, France

Blueserver Operators Guide

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Blueserver Operators Guide

Enviado por

Direitos autorais:

Formatos disponíveis

THE BLUE SERVER V7

Reference : Blue Server V7

MPI TECH (France) MPI TECH (North America)

MPI TECH (Germany) MPI TECH (UK) MPI TECH (Denmark)

2 The Blue Server V7

4. IBM HOST CONFIGURATION FOR ROUTER SCS 5250 SESSION ....................................................................................... 33

6. IBM HOST CONFIGURATION FOR TN3270/TN5250 ....................................................................................................... 43

The Blue Server V7 3

8. ROUTER AS/400 LPD-SCS .............................................................................................................................................. 97

9. ROUTER MAINFRAME SCS/IPDS OVER SNA SERVER ................................................................................................... 105

The Blue Server V7 5

10. ROUTER TELNET 5250 OR 3270 ............................................................................................................................... 121

The Blue Server V7 7

The Blue Server V7 9

10 The Blue Server V7

Europe North America

Denmark US (West coast)

The Blue Server V7 11

12 The Blue Server V7

 And you will get the following display :

The Blue Server V7 13

LINUX-SUSE:/opt/MPI_Blue_Server/MPI_Parser # ./blueserver -w█

14 The Blue Server V7

This icon allows adding a new Printer.

Delete Server This icon allows deleting a Server.

Delete Profile This icon allows deleting a Profile.

Delete Printer This icon allows deleting a Printer

Update Profile, printer

Channel Board configuration

Status: not connected

The Blue Server V7 15

 Some servers can be displayed, with their specific IP address or name .

When the status is green, means the service is available,

When the status is red, means the service is stopped,

16 The Blue Server V7

The Blue Server V7 17

18 The Blue Server V7

3.1.1. TCP/IP With AS/400 V3R1

3.1.1.1. Creating The AS/400 Printer Device

Device Description Name DEVD <Printer Name>

Remote Net Id RMTNETID *NETATR

3.1.1.2. Creating The WRKAFP2 Command On Your AS/400 (V3R1)

The Blue Server V7 19

DEVD : <Printer Name>

20 The Blue Server V7

Remote Net Id RMTNETID *NETATR

3.1.2.2. The CRTPSFCFG Command Parameters

The Blue Server V7 21

Remote Net Id RMTNETID *NETATR

3.1.3.2. Creating the WRKAFP2 command on your AS/400 V3R6

22 The Blue Server V7

The Blue Server V7 23

PSF Configuration PSFCFG PRTV3R7 <- PRINTER NAME

Blank page BLANCKAPGE *YES

TCP/IP port PORT *NONE

24 The Blue Server V7

Device description DEVD PRTV3R7 <- PRINTER NAME

Message queue MSGQ QSYSOPR

User-defined options USRDFNOPT *NONE

User defined object USRDFNOBJ

The Blue Server V7 25

PSF Configuration PSFCFG PRTV3R7 <- PRINTER NAME