Objectif Lune PlanetPress Suite - 6.0 Instruction Manual
Trigger and Data Capture Guide
Copyright Information
Copyright © 1994-2007 Objectif Lune Inc. All Rights Reser ved.
No part of this pub lication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any other language or computer language in
whole or in par t, in any form or by any means, wh ether it be electronic, mechanical, magnetic, optical, manual or otherwise, without prior written consent of Objectif Lune Inc.
Objectif Lune Inc. disclaims all warranties as to this software, whether expressed or implied, including without limitation any implied warranties of merchantability,
fitness for a particular purpose, functionality, data integrity or protection.
PlanetPress is a registered trademark of Objectif Lune Inc.
PostScript and Acrobat are registered trademarks of Adobe Systems Inc.
Pentium is a registered trademark of Intel Corporation.
Windows is a registered trademark of Microsoft Corporation.
Adobe, Adobe PD F Library, Adobe Acrobat, Adobe Distiller, Adobe R eader, Adobe Illustrator, Adobe Pho toshop, Optimized Postcri pt Stream, the Adobe logo, the
Adobe PDF logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Trademarks of other companies mentioned in this documentation appear for identification purposes only and are the property of their respective companies.
Title Trigger and Data Capture Guide
Revision 6.1 8/17/07
OBJECTIF LUNE PLANETPRESS SUITE
END USER LICENSE AGREEMENT
AND LIMITED WARRANTY
IMPORTANT - READ CAREFULLY
1. LICENSE AGREEMENT AND LIMITED WARRANTY AGREEMENT. - This End User License Agreement (“EULA”) and Limited Warranty (hereinafter collectively the
“License Agreement”) constitute a legal agreement between you (either as a physical, legal person (e.g. corporation) or a partnership) and Objectif Lune Inc.
(“Objectif Lune”) for the software product identified as PlanetPress® Suite, including all companion products, components, patches, updates and upgrades, and also
including any computer software, PostScript® programs, media and all accompanying on-line or printed documentation (collectively the “Software”). The Software
also includes Adobe® Technology and related documentation, and any upgrades, modified versions, additions and copies thereof.
2. BINDING EFFECT. - BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE, YOU, AS NON-EXCLUSIVE SUB LICENSEE, ACCEPT TO BE AND YOU ARE BOUND BY
ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. IF YOU ARE THE ORIGINAL PURCHASER OF THE SOFTWARE AND DO NOT AGREE WITH THE TERMS
AND CONDITIONS OF THE LICENSE AGREEMENT, PROMPTLY RETURN THE UNUSED SOFTWARE TO THE PLACE FROM WHICH YOU OBTAINED IT FOR A FULL REFUND. BY
YOUR ACCEPTANCE OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT AS MENTIONED ABOVE, OBJECTIF LUNE GRANTS YOU THE RIGHT TO USE THE SOFTWARE IN THE MANNER HEREIN PROVIDED.
3. COPYRIGHTS. - This Software is owned by Objectif Lune or its suppliers and is protected by the Copyright Act (Canada), any copyright law and international copyright treaties. Therefore, you must treat this Software like any other copyrighted material (e. g., a book), except that you may, for example, make one copy of the
Software solely a) for backup or archival purposes or b) if it is essential for the compatibility of the computer program, or transfer the Software to a single hard disk,
provided you keep the original solely for backup or archival purposes and that such copy is not installed or used on any other computer.
4. PROPERTY AND INTELLECTUAL PROPERTY RIGHTS. - All Objectif Lune’s libraries, source code, byte code executables and any other files (collectively the “files”)
remain Objectif Lune’s exclusive property. Regardless of any modifications that you make, you may not distribute any files (particularly but not limited to Objectif
Lune source code and other non-executable files) except those that Objectif Lune has expressly designated. Nothing in this License Agreement permits you to derive
the source code of files provided to you in executable form only, or to reproduce, modify, use or distribute the source code of such files. This L icense Agreement does
not grant you any intellectual property rights in the Software.
5. TRANSFER. - You may transfer the Software only on a permanent basis, provided you retain no copies except as provided in Section 3 and the recipient or transferee shall be bound by the terms of this License Agreement. Except as provided in this License Agreement, you may not transfer, rent, lease, lend, copy, modify,
adapt, translate, sublicense or time-share in any manner the Software or any part hereof.
6. TRADE SECRET. - You acknowledge that the Software in source code, its structure and organization form remains a confidential valuable trade secret of Objectif
Lune or its suppliers and therefore you agree not to modify the Software or attempt to reverse engineer, decompile or disassemble or other wise attempt to discover
the source code of the Software.
7. UPGRADED VERSION. - If you have purchased an upgrade version of the Software, this version constitutes a single product with and forms part of the Software.
Any transfer of an upgrade version of the Software can be made only in accordance with this License Agreement.
8. SCOPE OF USE. - You agree to use the Software for your own customary business or personal purposes on only one device (physical or virtual computer system). If
you need to use the Software on more than one device, you must purchase additional licenses. Contact Objectif Lune for applicable royalties payable and licensing
terms. Please refer to th e appropriate following sections 9 o r 10 “ADDI TIONAL LICENSE TERMS” for “Variable Content D ocuments” or - for “Optimized PostScript and
Windows Printing outputs”.
9. ADDITIONAL LICENSE TERMS FOR VARIABLE CONTENT DOCUMENTS. - If the Software can or will generate or create or modify Postscript programs called “Variable
Content Documents” (VCD), any VCD generated by the Software is licensed on a per “licensed output device” basis (including, without limitation, printers, Adobe
Acrobat Distiller, Aladdin Ghostscript, etc.). This means that any VCD generated by the Software can be used by any number of users as long as they use the VCD on
only that single licensed output device. If you need to use the VCD on more than one output device, you must purchase additional licenses. In case of cluster printing
systems (multiple print engines attached to a single Raster Image Processor (RIP), each print engine needs to be licensed individually. Contact Objectif Lune for the
applicable royalties payable and licensing terms for distribution of any VCD.
10. ADDITIONAL LICENSE TE RMS FOR OPTIMIZED POSTSCRIPT AND WINDOWS PRI NTING OUTPUTS.- Section 9 does not apply for PlanetPress Server’s “Optimized Postscript” or “Windows Printing”.
11. TERM. - This license is effective until terminated. Objectif Lune has the right to terminate your license immediately if yo
of this Agreement. Upon ter mination, you must destroy the original and any copy of the Software and cease all use of all the trademarks mentioned herein.
12. LIMITED WARRANTY. - Objectif Lune warrants that the Software media will be free from defects in materials and workmanship, for a period of ninet y (90) days
from the date of its purchase.
You must repor t all errors and return the Software to the location where you bought it with a copy of your receipt within such period to be eligible for warranty service.
u fail to comply with any one of the terms
Objectif Lune’s and its suppliers’ liability and the exclusive remedy shall be, at Objectif Lune’s sole option, either (a) return of the price paid, or (b) repair or replacement of the Software if it does not meet Objectif Lune’s Limited Warranty and if returned to Objectif Lune with a copy of your receipt. No warranty is given by Objectif Lune for and in the name of any of its suppliers.
DO NOT RETURN ANY PRODUCT UNTIL YOU HAVE CALLED THE OBJECTIF LUNE CUSTOMER CARE DEPARTMENT AND PREVIOUSLY OBTAINED A RETURN AUTHORIZATION
NUMBER.
This Limited Warranty is void if failure of the Software results from accident, abuse or misapplication. Any replacement of the Software media will be warranted for
the remainder of the original warranty period or thirty (30) days, whichever is longer. Outside Canada, neither these remedies nor any product support services
offered by Objectif Lune are available without proof of purchase from a duly authorized non-Canadian source.
OBJECTIF LUNE DOES NOT AND CANNOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THE SOFTWARE. THIS LICENSE AGREEMENT STATES THE
SOLE AND EXCLUSIVE REMEDIES FOR OBJECTIF LUNE’S BREACH OF WARRANTY, EXPRESS OR IMPLIED, AS TO MERCHANTABILITY, NON-INFRINGEMENT OF THIRD PARTY
RIGHTS, OR FITNESS FOR A PARTICULAR PURPOSE.
For further warranty information, you may contact your nearest Objectif Lune representative. Contact information can be found at www.objectiflune.com.
13. LIMITATION OF LIABILIT Y. - IN NO EVENT SHALL OBJECTIF LUNE OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS OR SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE OR THE PROVISION OF OR THE FAILURE TO
PROVIDE SUPPORT SERVICES, EVEN IF OBJECTIF LUNE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN ANY CASE, OBJECTIF LUNE’S ENTIR E LIABILITY
UNDER ANY PROVISION OF THIS LICENSE AGREEMENT SHALL BE LIMITED TO THE GREATER OF: A) THE AMOUNT PAID FOR THE PURCHASE OF THE SOFT WARE OR B)
CAD $25.
14. WARNING ? HIGH RISK ACTIVITIES. - THE SOFTWARE IS NOT FAULT-TOLERANT AND IS NOT DESIGNED, MANUFACTURED OR INTENDED FOR USE OR RESALE AS ONLINE CONTROL EQUIPMENT IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS, WITHOUT LIMITATION, 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 SOFTWARE COULD LEAD DIRECTLY TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE (“HIGH RISK ACTIVITIES”).
OBJECTIF LUNE AND ITS SUPPLIERS SPECIFICALLY DISCLAIM ANY EXPRESS OR IM PLIED WARRANT Y OF FITNESS FOR HIGH RISK ACTIVITIES.
15. GENERAL PROVISIONS. - This License Agreement may only be modified in writing by a duly authorized officer of Objectif Lune. If any or part of any provision of
this License Agreement is, by final judgment, found void or unenforceable, the remainder shall remain valid and enforceable according to its terms. Even if any remedy provided is determined to have failed for its essential purpose, all limitations of liability and exclusions of damages herein set forth shall remain in full force and
effect.
16. GOVERNING LAW. This License Agreement is governed by the laws in force in the Province of Québec (Canada) and parties hereby elect domicile in judicial district
of Montréal, Québec, Canada. This Agreement is not governed by the United Nations Convention on Contracts for the International Sale of Goods (CISG), the application of which being expressly exclud ed.
17. U.S. GOVERNMENT RESTRICTED RIGHTS. - If a Licensed Application i s acquired under the terms of a proposal or agreement with the United States Government or
any contractor therefor, the Licensed Application is subject to the following restricted rights notice: “This Software is commercial computer software provided with
RESTRICTED RIGHTS. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical
Data and Computer Software clause at DFARS 252.227-7013 , FAR 52.227-17 Alternate III (g)(3), or subparagraphs (c)(1) and (2) of the Commercial Computer Software -- Restricted Rights at 48 CFR 52.227-19, as applicable, and their successor provisions. Contractor/Manufacturer is Objectif Lune Inc., Montréal, Québec, Canada, H1V 2C8.
18. U.S. EXPORT RULES. - You agree that the Software will not be shipped, transferred or exported into any country or used in any manner prohibited by the United
States Export Administration Act or any other export laws, restrictions or regulations (collectively the “Export Laws”). In add
export controlled items under the Export Laws, you represent and warrant that you are not a citizen of or otherwise located within an embargoed nation (including,
without limitation, Iran, Iraq, Syria, Sudan, Libya, Cuba, North Korea and Serbia) and that you are not otherwise prohibited under the Export Laws from receiving the
Software. All rights to use the Software are granted on condition that such rights are forfeited if you fail to comply with the terms of this paragra ph.
ition, if the Software is identified as
Table of Contents
1 Capturing Data 1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Key Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Detailed Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Capture Sample Data for a Document You Install on a Printer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Capture Sample Data for a Document You Install in PlanetPress Watch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Capture Sample Data in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Capture Sample Data in Windows 2000/Server 2003/XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Capture Sample Data in Windows Host Using a Novell Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Capture Sample Data in UNIX (Solaris) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Capture Sample Data using an AS/400 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Capture Sample Data From a Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 Creating Triggers 17
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Key Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Detailed Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Implement a Trigger under Novell 3.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Implement a Trigger under Novell 4.x and 5.x with NDS or Bindery Printers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Implement a Trigger under Windows NT 4.0 with TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Implement a Trigger under BSD Printing Systems (BSDi, FreeBSD, Linux). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Implement a Trigger under UNIX System V (Solaris). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Implement a Trigger and Configure an AIX 4.3 Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Implement a Trigger under VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Implement a Trigger with AS/400 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Prepare SAP Device Type for PlanetPress Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Implement a Trigger under HP 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
i
toc
Appendix A: Special Printer Requirements 93
HP Printers with Flash Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Lexmark Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Printers with Automatic Emulation Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Appendix B: ASCII Conversion Table 95
ASCII Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Appendix C: CL Program for AS/400 Systems 101
CL Program for AS/400 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
ii
This chapter provides procedures for capturing data on different platforms.
Overview
In this section, you learn to:
• “Capture Sample Data for a Document You Install on a Printer” on page 3
• “Capture Sample Data for a Document You Install in PlanetPress Watch” on page 4
Capturing Data
• “Capture Sample Data in Windows NT” on page 5
• “Capture Sample Data in Windows 2000/Server 2003/XP” on page 6
• “Capture Sample Data in Windows Host Using a Novell Print Server” on page 7
• “Capture Sample Data in UNIX (Solaris)” on page 8
• “Capture Sample Data using an AS/400 Systems” on page 10
• “Capture Sample Data From a Serial Port” on page 14
In addition, you will be able to answer the following questions:
• “What is a sample data file?” (p. 2)
1
1
Capturing Data
• “What is a spool file?” (p. 2)
Key Concepts
Sample Data File
What is a sample data file?
The sample data file is a text file that contains a representative sample of the input data destined for the
document, as that input data arrives at a printer or a PlanetPress Watch process. You use a data capture
process to create a sample data file.
You create your document based on the contents of this sample data file. Whether the document you
create executes properly, and under all circumstances, with the input data it receives when it executes
depends on how accurately the sample data file represents that input data. The two criteria for a reliable
sample data file are:
1. It includes all possible variations on the data that the document may encounter when it executes.
A sample data file that does not take into account all possible variations on the data can have serious
consequences. For example, if you design a cheque based on an amount field of a certain length, and
one of the records in the input data exceeds that length, the result is a cheque with an incorrect
amount.
Things to check for variation include field lengths, the location of decimal points in numeric data, and
whether or not a field always contains data.
2. It exactly represents the input data at the moment that data arrives at the printer or PlanetPress Watch
process. A difference of a single character can result in a document that does not produce accurate
results.
If your sampl e data file d oes no t meet this c riteria, you end up creat ing a d ocume nt that exe cutes with
a different input data structure than the one for which you designed it.
Spool File
What is a spool file?
A spool file is a file containing a job destined for a specific printer. When you print a file, the application you
use to print writes a file to the spool folder for that printer. The system monitors this folder. When a file
appears in the folder, it sends that file to the printer, and deletes it from the spool folder.
It is common to use a spool file as the sample data file for a document you intend to install on a printer.
2
Detailed Directions
Capture Sample Data for a Document You Install on a Printer
This procedure describes the general steps involved in capturing sample data for a document you intend
to install on a printer. If you are using database emulation, you capture sample input data at the time you
set up the emulation.
An understanding of the general procedure for capturing a reliable sample data file can help you
understand and navigate the platform-specific instructions.
To capture data for a document you install on a printer:
1. Determine the input data you need.
Determine all the variations of input data you need to include in the sample data file, and the query
that retrieves that input data. This is specific to your database and computing environment.
2. Determine the type of connection that exists between the host on which the input data resides and
the printer on which the document will execute.
In general there are three types of connections:
Detailed Directions
• Direct connection. The printer is either directly connected to the host on which the input data resides,
or the host can directly address it on a network.
• Serial connection. The printer and the host are connected by a serial cable.
• Print server. The printer is connected to a print server. The host sends print jobs to the print server.
3. Capture the representative sample of input data.
In general you set up a process to intercept a print job on its way to the printer. You then send the
representative sample of data to the printer. The process you set up intercepts the job and saves the
spool file as the sample data file. For example, if your host can address the printer directly, you could
use the following method:
• Pause printing on the printer on which you intend to install the document. This tells the printer driver
not to send any files that it finds in the spool folder for this printer, to the printer. If you print to a
printer after you pause it, a spool file appears in that printer’s spool folder and remains there until you
re-enable printing on that printer.
• Send the representative sample of input data to the printer on which you intend the document to
execute. This creates a spool file.
3
1
Capturing Data
• Retrieve the spool file.
• Restart printing on the printer you paused.
Things to Remember
• As a rule you want to capture the data as close to the printer as possible since the data file may undergo
several transformations as it makes its way through drivers, spoolers, or physical devices. If your printer
is not yet connected, you will need to anticipate how it will fit into your network configuration. For
example, will it be connected to a print ser ver or addressed directly by the host? What protocol will it use?
Capture Sample Data for a Document You Install in PlanetPress Watch
This procedure describes the general steps involved in capturing sample data for a document you intend
to install in PlanetPress Watch. An understanding of the general procedure for capturing a reliable sample
data file helps you understand and navigate the platform-specific instructions.
It assumes you have a general understanding of what a PlanetPress Watch process is, and how it works.
See the PlanetPress Watch User’s Guide for further information.
Note that if you are using database emulation, you capture sample input data at the time you set up the
emulation.
To capture data for a document you install in PlanetPress Watch:
1. Determine the input data you need.
Determine all of the variations of input data you need to include in the sample data file, and the query
that retrieves that input data. This is specific to your database and computing environment.
2. Determine the input mode you intend to use when you execute your document in PlanetPress Watch.
The input modes you can use for data capture include Windows printer driver, lpd queue, directory,
email, and serial capture. The input modes available depend on your platform and the type of
connection that exists between the host on which the input data resides and the host on which
PlanetPress resides. For example, to use a Windows queue, your input data must reside on the same
host on which you are running PlanetPress Watch. Consult the PlanetPress Watch User’s Guide for
complete descriptions of all input modes.
3. Map exactly how your input data will travel from source to destination when you execute the
completed document.
You must replicate this path exactly when you capture data, or define how you intend to compensate
for any deviations from it during document design.
4
Detailed Directions
4. Capture the sample of input data.
What follows is a general outline of the procedure. Consult the specific data capture procedure for your
platform, and the PlanetPress Watch User’s Guide for help setting up PlanetPress Watch processes.
• Create a PlanetPress Watch process to accept the data through the input mode you specify and save
the result as a file in a folder.
• Send the representative sample of input data to PlanetPress Watch using the input mode you
specified in the PlanetPress Watch process you set up for the data capture.
• Retrieve the file from the output folder.
Capture Sample Data in Windows NT
You perform this procedure on the machine that controls the printer, not on the workstation.
To perform data capture under Windows NT:
1. In the Windows Start menu, choose Settings, then choose Printer.
The Printers window appears.
2. Right-click on the printer on which you intend to execute your document and choose Pause printing.
3. In the application you use to manipulate the input data, send the data you want to capture to the
printer you selected in step 2.
The printer driver creates a printer spool file containing the representative data sample.
4. In the Windows Start menu, choose Run.
The Run dialog box appears.
5. In the Run dialog box, in the Open box, enter CMD.
A DOS Command Prompt window appears.
6. In the DOS Command Prompt window, change directory to the spool folder:
cd C: \winnt\system32\spool\printer
7. Copy the spool file (.spl) you just created to a floppy or to another folder.
The *.spl file contains your data.
8. Close the DOS session.
5
1
Capturing Data
9. In the Windows Start menu, choose Settings, then choose Printer.
The Printers window appears.
10. Right-click on the printer you paused and choose Pause printing.
The spooler sends the job to the printer.
Capture Sample Data in Windows 2000/Server 2003/XP
You perform this procedure on the machine that controls the printer, not on the workstation.
1. In the Windows Start menu, choose Settings, then choose Printer.
The Printers window appears.
2. Right-click on the printer on which you intend to execute your document and choose Pause printing.
3. In the application you use to manipulate the input data, send the data you want to capture to the
printer you selected in step 2.
The printer driver creates a printer spool file containing the representative data sample.
4. In the Windows Start menu, choose Run.
The Run dialog box appears.
5. In the Run dialog box, in the Open box, enter COMMAND.(
A DOS Command Prompt window appears.
6. In the DOS Command Prompt window, change directory to the spool folder:
cd C: \windows\spool\printer
7. Copy the spool file (.spl) you just created to a floppy or to another folder.
The *.spl file contains your data.
8. Close the DOS session.
9. In the Windows Start menu, choose Settings, then choose Printer.
The Printers window appears.
10. Right-click on the printer you paused and choose Pause printing.
The spooler sends the job to the printer.
6
Detailed Directions
Capture Sample Data in Windows Host Using a Novell Print Server
This procedure describes how to capture data for a document you intend to execute using a Novell print
server.
To capture data on a Windows host that uses a Novell print server:
1. Start the NetWare Administrator.
2. In the NetWare Administrator window, double-click the print server in the list of printers. For the
purposes of this procedure, the print server is the optra1650s-nds.
The Print Server dialog box for that print server appears.
3. Click Status.
The Status dialog box appears.
4. Note the values of the Volume and ID fields and then click Close.You use these values later to navigate
to the print queue.
5. In the Print Server dialog box double-click the print queue for the print server. The print queue is the
file whose file name ends in the letters pq. For example, the print queue for the optra1650s-nds print
server is optra1650s-nds-pq.
The Print Queue dialog box for that print server appears.
6. Disable Allow service by current print server and click OK.
7. To verify the print server is paused, print a test page and verify the spool file remains in the print queue.
You can print a test page by clicking Print Test Page in the General tab of the print queue properties
dialog box for this print queue. You can then verify the file remains in the print queue by navigating to
the print queue in Windows Explorer and verifying there is a spool file for the test page. The spool file
has a .Q extension. You use the Volume and ID information you noted in step 4. to determine the path
of the print queue.
8. Send your input data to the print server.
9. Retrieve the spool file for the input data from the print queue.
In Windows Explorer, navigate to the print queue for the print server. Use the Volume and ID
information you noted in step 4. to determine the path of the print queue. The spool file has a .Q
extension.
10. Double-click the spool file to open it and verify the contents are what you expect.
7
1
Capturing Data
Capture Sample Data in UNIX (Solaris)
Create a Virtual Printer
To create a virtual printer:
1. In the File Manager, choose File and then Open Ter mi na l.
2. Use the following commands to open the Hosts file:
cd /etc
vi ./hosts
3. In the Hosts file, add the IP address of the printer, or the IP address of the workstation on which
PlanetPress Watch is installed, and assign a name to that IP address. For example:
192.xxx.yyy.zzz printdestination
4. Save the Hosts file as follows:
Press ESCAPE.
Enter :wq
Assign a Print Queue to a Virtual Printer
To assign a print queue to a virtual printer:
1. Use the command:
lpadmin -p queuename -I any -s printdestination
Where:
-p queuename specifies the name of this queue
-I any specifies no data formatting (i.e.: Text Only)
-s printdestination specifies the name of the virtual printer
8
Detailed Directions
Send Data to the Print Queue
To send data to the print queue:
•Use the command:
lp -d queuename data_filename
Note that you must create a PlanetPress Watch process before you send data from UNIX to the
workstation running PlanetPress Watch.
PlanetPress Watch Configuration
To set up PlanetPress Watch to capture data sent using LPR:
1. In PlanetPress Watch Configuration, create a new PlanetPress Watch process by choosing Insert | New
Process.
2. In the PlanetPress Watch Process area, click the unknown task in the upper-left corner at the beginning
of the data stream.
3. Choose Insert | Input | LPD Input.
The LPD Input’s Properties dialog appears.
4. In the LPD Queue name text box, enter the name of the print queue you defined (see “Assign a Print
Queue to a Virtual Printer” on page 8).
5. Click OK.
An LPD input replaces the unknown task at the beginning of the PlanetPress Watch process, which
captures the data sent from the UNIX computer. In PlanetPress Watch Configuration, you then
configure the rest of the tasks that process this incoming data, including where and how it is output.
You then send the configuration to PlanetPress Watch to run. Refer to the PlanetPress Watch User’s
Guide for more information about its LPR client and LPD ser ver ser vices, and for setting up PlanetPress
Watch processes.
9
1
Capturing Data
Capture Sample Data using an AS/400 Systems
Generic Output
To create a generic output queue on an AS/400:
1. In the AS/400 main menu, enter the create output queue command CRTOUTQ and press F4.
10
Detailed Directions
2. In the Change Output screen, in the Output queue field, enter an output queue name. In this example,
the name entered is OUTQ1.
3. Press F10 followed by F9 to display the Remote Printer Queue parameter.
4. Enter the following information:
• In the Remote system field, enter the string *INTNETADR.
• In the Remote printer queue field, enter the name of the remote printer queue, enclosed in single
quotes. The remote printer queue is the one located on the machine that will receive the input data.
In this example, ‘PRINTER1’ is the remote printer queue name.
11
1
Capturing Data
5. Press PAGE DOWN to display the Create Output Queue screen.
6. Complete the fields with the following values. Unless otherwise specified, you must enter these values
exactly as they appear here.
Writers to autostart: 1
12
Connection type: *IP
Destination type: *OTHER
Host print transform: *YES
Manufacturer type and model: *WSCST
WS customizing object: QWPDEFAULT
Library: QSYS
Internet address: The IP address of the workstation to which you will send the data. In this example,
the address is 192.168.100.109.
7. Press PAGE DOWN.
Detailed Directions
The next page of the Create Output Queue screen appears.
8. If you want to prevent a separator page from printing, enter *NO in the Print separator page field.
Leave all other fields untouched.
9. Press ENTER to create the new generic output queue.
A confirmation message appears at the bottom of the main menu.
13
1
Capturing Data
Capture Sample Data From a Serial Port
This procedure describes how to use Microsoft’s Hyperterminal to capture serial data. Refer to the
PlanetPress Watch User’s Guide for information on capturing serial data using PlanetPress Watch’s Serial
input.
To set the serial data capture parameters:
1. In the Windows Start menu, choose Programs | Accessories | HyperTerminal.
If necessary, install Windows HyperTerminal.
The Connection Description dialog box appears.
14
2. In the Name box, enter a name for the connection and click OK.
The Connect To dialog box appears.
3. Select COM 1 or COM 2 and click OK. If you need to determine which COM port the printer uses, open
the Control Panel, then open Modems and click Diagnostics. In most cases you select COM2. The
remaining steps of this procedure assume you selected COM2.
The COM2 Properties dialog box appears.
4. Adjust the COM2 Properties and click OK.
A HyperTerminal window for this connection appears.
5. In the menu for the HyperTerminal window, choose Tra nsf er | Capture Te xt .
The Capture Text dialog box appears.
Detailed Directions
6. The file name that appears in this dialog box is Ca pture.tx t. If this file does not exist, you will need to
create it (this is the text file that will be used as the capture file).
7. Click Start.
8. Send the input data to the printerusing the procedure you would usually use to print the data.
9. When the print command completes, return to the HyperTerminal window for this connection and
choose Tra ns fer | Capture Tex t | Stop.
The input data you sent to the printer appears in the HyperTerminal window and is saved in the
Captu re.txt file.
10. The Capt ure.txt file is the sample data file you use to create your document.
15
1
Capturing Data
16
Creating Triggers
This chapter describes platform-specific procedures for creating a trigger and inserting it
at the head of a data stream.
Overview
A job consists of a document, a trigger, and data. If you are not using PlanetPress Watch, you must
manually create the appropriate trigger, add it to the head of the data stream, and send the result to the
printer on which the document resides. The procedure for creating the trigger and adding it to the head of
the data stream is platform-dependent.
In this section, you learn to:
• “Implement a Trigger under Novell 3.x” on page 21
• “Implement a Trigger under Novell 4.x and 5.x with NDS or Bindery Printers” on page 31
• “Implement a Trigger under Windows NT 4.0 with TCP/IP” on page 39
• “Implement a Trigger under BSD Printing Systems (BSDi, FreeBSD, Linux)” on page 47
• “Implement a Trigger under UNIX System V (Solaris)” on page 49
• “Implement a Trigger and Configure an AIX 4.3 Printer” on page 51
• “Implement a Trigger under VMS” on page 66
• “Implement a Trigger with AS/400 Systems” on page 69
17
2
Creating Triggers
• “Prepare SAP Device Type for PlanetPress Design” on page 85
• “Implement a Trigger under HP 3000” on page 91
In addition, you will be able to answer the following questions:
• “What is a trigger?” (p. 18)
• “What is the syntax of a trigger?” (p. 19)
• “What are the common techniques for inserting a trigger?” (p. 20)
Key Concepts
Trigger
What is a trigger?
A trigger is two lines of PostScript that immediately precedes the input data and performs two functions:
it puts the printer in PostScript mode, and tells the printer which document to launch. A trigger “triggers”
the execution of a document.
You execute a document installed on a printer by sending a trigger to the printer, followed by the input
data. If you execute your document in PlanetPress Watch, PlanetPress Watch inserts the trigger. If you
execute your document directly on a printer, you must manually insert the trigger at the head of the data
stream.
18
Printer-Specific Control Characters
You can precede a trigger with printer-specific control characters. The most common reason to do so is to
ensure the printer receives the job you send it as a new job.
A printer expects each job that it handles to end with a special character that tells the printer it has reached
the end of the input data. Until the printer receives this special character, it continues to process all input
it receives as part of that job. If there is no input, the printer waits for a defined period of time, then times
out and proceeds to the next job. If a new job arrives during the period of time the printer is waiting for
input, the printer does not recognize it as a new job; rather it processes it as input for the current job.
It is thu s common practi ce to include an end of job character at the beginning of the trigger to ensu re that
the printer recognizes your job as a new print job. For certain printers <CTRL D> or ASCII 04 is a valid end
of job character, while more recent printers require a Printer Job Language (PJL) sequence such as
<ESC>%-12345X<CR><LF>.
Key Concepts
As an example, the following trigger includes <CTRL D> as an end of job character:
<CRTL-D>%!PS-Adobe <CR>
run INVOICE <CR><LF>
Trigger Syntax
What is the syntax of a trigger?
In all syntax descriptions in this section, italics denote a variable, square brackets indicate the element is
optional, <CR> denotes a carriage return and <LF> denotes a line feed.
The general syntax for the first line of the trigger is the same for all triggers:
[ printer-specific_commands ] %!PS-Adobe <CR>
The first line of the trigger uses the string “%!PS-Adobe” to put the printer in PostScript mode. It may also
include printer-specific commands.
The syntax of the second line of the trigger depends on where the document is installed in the printer: on
the hard drive, in RAM, or in flash memor y. The second line, written in PostScript, tells the printer the name
and location of the document, and launches the document. If you are using version numbers in your
documents, this line also contains the version number.
Trigger Syntax for Documents Installed on a Hard Disk
The general syntax of a trigger for a document that resides on the printer’s hard drive is:
[ printer-specific_commands ] %!PS-Adobe <CR>
[[ (location_of_document) ] run ] name_of_document <CR><LF>
The simplest example of a trigger for a document named INVOICE that resides on the printer’s hard drive
excludes the location of the document. If a trigger does not specify the location of the document, the
printer assumes it is on the hard disk.
%!PS-Adobe <CR>
run INVOICE <CR><LF>
An equivalent trigger that makes the location of the INVOICE document explicit:
%!PS-Adobe <CR>
(INVOICE) run INVOICE <CR><LF>
If t he printe r has more t han on e hard dis k you must inclu de the name o f the h ard dis k. In t his examp le, the
name of the hard disk is “presswork” and the name of the document is INVOICE.
%!PS-Adobe <CR>
(%presswork%INVOICE) run INVOICE <CR><LF>
19
2
Creating Triggers
Trigger Syntax for Documents Installed in RAM
The general syntax of a trigger for a document that resides in the printer’s RAM is:
[ printer-specific_commands ] %!PS-Adobe <CR>
name_of_document <CR><LF>
An example of the trigger for a document named FORMLETTER that resides in the printer’s RAM:
%!PS-Adobe <CR>
FORMLETTER <CR><LF>
Trigger Syntax for Documents Installed in Flash Memory
The general syntax of a trigger for a document that resides in the printer’s flash memory is:
[ printer-specific_commands ] %!PS-Adobe <CR>
(%flash%name_of_document) run name_of_document <CR><LF>
An example of the trigger for a document named PAYROLL that resides in the printer’s flash memory:
%!PS-Adobe <CR>
(%flash%PAYROLL) run PAYROLL <CR><LF>
20
Techniques for Inserting Triggers
What are the common techniques for inserting a trigger?
How you create and insert a trigger is operating system dependent. There are many ways to inser t a trigger
manually. Four common techniques are:
1. Manually concatenating two files
In this technique you add a trigger by concatenating two files where the first contains the trigger and
the second contains the input data. You send the concatenated file to the printer using the DOS Copy
command or the file transfer protocol (FTP).
2. Setting up the print server to automatically insert triggers
This technique works with a print server running either Novell or Windows NT. You create a print queue
or print device for each document installed in the printer, and associate the appropriate trigger for the
document with the queue you set up for it. All queues point to the same physical printer. When you
send a job to that queue, the server automatically inserts the trigger associated with that queue before
it forwards the printer job to the printer.
3. Setting up the host to automatically insert triggers
This is the same technique as setting up the print server to automatically insert triggers. The only
difference here is that you set up the queues on the host on which the input data resides. The host
inserts the trigger ahead of the spool file when it sends the print job to the printer. This technique does
not work with all hosts.
4. Including the trigger in application output
In this technique you modify the output of the application that generates the print file so that it adds
a trigger for the appropriate document. It is important to understand that this hampers your ability to
print these jobs using other printers since two additional lines are added to the print file.
Detailed Directions
Implement a Trigger under Novell 3.x
Unless otherwise indicated, always press ENTER at the end of a command. Note that you can exit any
window or command area at any time by pressing ESCAPE.
Detailed Directions
To install a trigger:
1. Log on to the server, and enter Supervisor and printdef.
2. In the PrintDef Options dialog box, select Print Devices.
3. In the Print Device Options dialog box, select Edit Print Devices.
4. Press INSERT.
21
2
Creating Triggers
5. In the New Device Name dialog box, enter the name of the document you want to execute. For this
example, enter Mailing.
6. In the Defined Print Devices dialog box, select Mailing and press ENTER.
7. In the Edit Device Options dialog box, select Device Functions.
22
8. Press INSERT.
9. In the Function Definition dialog box, enter the following information:
• In the Name field, enter Reset
• In the Escape Sequence field, enter the following sequence: <ESC>%-12345X<CR><LF>
Loading...