6.0
Table Of Contents
- Capturing Data
- Overview
- Key Concepts
- Detailed Directions
- Capture Sample Data for a Document You Install on a Printer
- Capture Sample Data for a Document You Install in PlanetPress Watch
- Capture Sample Data in Windows NT
- Capture Sample Data in Windows 2000/Server 2003/XP
- Capture Sample Data in Windows Host Using a Novell Print Server
- Capture Sample Data in UNIX (Solaris)
- Capture Sample Data using an AS/400 Systems
- Capture Sample Data From a Serial Port
- Creating Triggers
- Overview
- Key Concepts
- Detailed Directions
- Implement a Trigger under Novell 3.x
- Implement a Trigger under Novell 4.x and 5.x with NDS or Bindery Printers
- Implement a Trigger under Windows NT 4.0 with TCP/IP
- Implement a Trigger under BSD Printing Systems (BSDi, FreeBSD, Linux)
- Implement a Trigger under UNIX System V (Solaris)
- Implement a Trigger and Configure an AIX 4.3 Printer
- Implement a Trigger under VMS
- Implement a Trigger with AS/400 Systems
- Prepare SAP Device Type for PlanetPress Design
- Implement a Trigger under HP 3000
- Special Printer Requirements
- ASCII Conversion Table
- CL Program for AS/400 Systems
- Index
18
Creating Triggers
2
• “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
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.
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 thus common practice to include an end of job character at the beginning of the trigger to ensure 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>.
What is a trigger?