OBJECTIF LUNE PlanetPress Suite 6.0 User guide

Type
User guide
Trigger and Data Capture Guide
Copyright Information
Copyright © 1994-2007 Objectif Lune Inc. All Rights Reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any other language or computer language in
whole or in part, in any form or by any means, whether it be electronic, mechanical, magnetic, optical, manual or otherwise, without prior written consent of Objec-
tif 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 PDF Library, Adobe Acrobat, Adobe Distiller, Adobe Reader, Adobe Illustrator, Adobe Photoshop, Optimized Postcript 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 SOFT-
WARE 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 copy-
right 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 Lunes libraries, source code, byte code executables and any other files (collectively the “files”)
remain Objectif Lunes 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 License 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 trans-
feree 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 otherwise 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 the appropriate following sections 9 or 10 “ADDITIONAL LICENSE TERMS” for “Variable Content Documents” 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 TERMS FOR OPTIMIZED POSTSCRIPT AND WINDOWS PRINTING OUTPUTS.- Section 9 does not apply for PlanetPress Server’s “Optimized Post-
script” or “Windows Printing”.
11. TERM. - This license is effective until terminated. Objectif Lune has the right to terminate your license immediately if yo
u fail to comply with any one of the terms
of this Agreement. Upon termination, 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 ninety (90) days
from the date of its purchase.
You must report 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 ser-
vice.
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 replace-
ment of the Software if it does not meet Objectif Lunes Limited Warranty and if returned to Objectif Lune with a copy of your receipt. No warranty is given by Objec-
tif 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 LIABILITY. - IN NO EVENT SHALL OBJECTIF LUNE OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAM-
AGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS OR SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSI-
NESS 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 ENTIRE LIABILITY
UNDER ANY PROVISION OF THIS LICENSE AGREEMENT SHALL BE LIMITED TO THE GREATER OF: A) THE AMOUNT PAID FOR THE PURCHASE OF THE SOFTWARE 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 ON-
LINE 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 IMPLIED WARRANTY 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 rem-
edy 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 applica-
tion of which being expressly excluded.
17. U.S. GOVERNMENT RESTRICTED RIGHTS. - If a Licensed Application is 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 Soft-
ware -- Restricted Rights at 48 CFR 52.227-19, as applicable, and their successor provisions. Contractor/Manufacturer is Objectif Lune Inc., Montréal, Québec, Can-
ada, 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
ition, if the Software is identified as
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 paragraph.
i
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
ii
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
1
Capturing Data
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
• “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)
2
Capturing Data
1
• “What is a spool file?” (p. 2)
Key Concepts
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 sample data file does not meet this criteria, you end up creating a document that executes with
a different input data structure than the one for which you designed it.
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.
What is a sample data file?
What is a spool file?
Detailed Directions
3
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:
• 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 printers 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.
4
Capturing Data
1
• 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 server 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.
Detailed Directions
5
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.
6
Capturing Data
1
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.
Detailed Directions
7
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.
8
Capturing Data
1
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 Terminal.
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
Detailed Directions
9
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 Users
Guide for more information about its LPR client and LPD server services, and for setting up PlanetPress
Watch processes.
10
Capturing Data
1
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.
Detailed Directions
11
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.
12
Capturing Data
1
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
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.
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118

OBJECTIF LUNE PlanetPress Suite 6.0 User guide

Type
User guide

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI