IBM Infoprint QuickFacts covering Infoprint printers, Infoprint Manager software (not including Xerox Transform) plus allied topics such as AFP, created from the standpoint of experience with AFP and various page printers in the AIX environment. as compiled by Richard Sims (r b s @ b u . e d u), On the web at http://people.bu.edu/rbs/Infoprint.QuickFacts Last update: 2015/03/10 This reference was originally created for my own use as a systems programmer's "survival tool", to accumulate essential information and references that I knew I would have to refer to again, and quickly re-find it. In participating mailing lists, it became apparent that others had a similar need for quick information references, and so it made sense to share the information. The information herein derives from many sources, but largely reflects my own experience with the involved products. This informal, non-authoritative "real-world" reference is intended to augment the formal, authoritative documentation provided by IBM and allied vendors, as frequently referenced herein. See the REFERENCES area at the bottom of this document for pointers to salient publications. Command syntax is included for the convenience of a roaming techie carrying a printed copy of this document, and thus is not to be considered definitive or inclusive of all levels for all platforms: refer to manuals for the syntax specific to your environment. Upper case characters shown in command syntax indicates that at least those characters are required, not that they have to be entered in upper case. I realize that I need to better "webify" this reference, and intend to do so in the future. (TSM administration is just a tiny portion of my work, and many other things demand my time.) Overall advisory: A perpetual complexity in dealing with Infoprint and AFP on AIX is that AFP is still primarily a mainframe facility, and as such largely uses EBCDIC, which engenders a lot of confusion when operating on ASCII data. Note on IBM printers: These days, IBM does not manufacture printers. IBM selects the best printer manufacturers and re-brands their offerings. For example, IBM's workgroup printer offerings, as of 2003,4, are Lexmark printers. In at least their larger printers, IBM may substitute its own custom microcode to optimize operation to their standards (AFP handling, job progress info for server user exit processing, etc.). == The "reset to default" operator, as in the pdmod and pdset commands. (Not for use in attribute definition files.) == pdls filter to exactly match the given value - all of it. Example: job-priority==* =* pdls filter to match the first part (head) of a value. The value should not be a token, but not a substring. *= pdls filter to match the last part (tail) of a value. *=* pdls filter to match any part of a value, such as a sub-string. If the value to be matched is a string containing blanks, put it in double quotes. Note that the pdls command will not work with -f specifying results-profile via '~=' or '*=*', apparently because of the colonized construction of results-profile. ==* pdls filter to match if the attribute is simply present, regardless of whatever value it may have. 1403 Circa 1971 IBM line printer model, printing 120 characters per line on continuous, Z-fold forms which were typically green & white and 14" wide and 11" high. 120 small hammers sat in the middle of a "racetrack" into which a "train" of print slugs could be loaded as a drop-in assembly. This horizontally mounted slug train would be propelled around at high speed and the hammers would fire to smack the type slug against a wide belt ink ribbon running vertically across the face of the train to make a character impression on the paper. All very noisy and very messy. Those nearby were thankful when the printer's motorized cover was closed. The 1403 used a loop of paper tape with holes punched in it to control carriage skipping. The tape ran on a set of sprockets that were synchronized with the motion of the paper in the carriage. The tape had 12 "channels" on it. When the printer received the command to skip to a particular channel, it would skip the carriage until it found a hole punched in the paper tape in the designated channel. This mechanism provided a method to skip the carriage precisely to a specific, downward vertical position on the page with a single command. Carriage control could also be exercised in software, in the first character of each line sent to the printer (controller), thus making the logical line 121 characters long. Print jobs utilizing this concept included a Carriage Control Character in the first position of each line - a convention which long endured, and was the basis of AFP architecture. 1585 See: Infoprint 1585 2085 See: Infoprint 2085 2105 See: Infoprint 2105 2705 IBM-specified "Machine Type" that the Infoprint 2105 is. 2706 IBM-specified "Machine Type" that the Infoprint 2105ES is. 2707-001 IBM-specified "Machine Type" that the InfoPrint 2190 is. 2707-002 IBM-specified "Machine Type" that the InfoPrint 2210 is. 2707-003 IBM-specified "Machine Type" that the InfoPrint 2235 is. 2770 IBM machine type for the Infoprint 70 printer. 2785 IBM-specified "Machine Type" that the Infoprint 2085 is. 3000 Large IBM continuous forms printer, withdrawn from marketing in 2006. Speed: Up to 344 ipm (two-up letter size in duplex mode) or 324 ipm? (two-up A4 in duplex mode) in simplex, duplex or dual simplex modes. Paper type: fan-fold or roll feed Paper width: Up to 18". Form length: 7" to 14" Resolution: 480, 600 or 480/600 dpi, operator-switchable 3160 IBM machine type for the Infoprint 60 printer. The startsrv script starts a PostScript transform daemon, using the /usr/lpp/psf/ps2afp/3160d.cfg config file, which its comments say is for the 3160. 3170 Although 3170 physical printers do not support auxiliary-sheet objects, they do print start sheets when the value of the printer-start-sheet actual destination attribute is full. The shell script that generates these start sheets is called /usr/lpp/pd/bin/ic70hdr.ksh. It reads from the /usr/lpp/pd/bin/ic70hdr.ps file. You can modify either of these programs to produce a customized start sheet. The output must be a valid PostScript file. Ref: Procedures manual, "Modifying start sheets for 3170 physical printers" 3203 Predecessor to the 3211, employing the same FCB concept. 3211 Circa 1976 IBM line printer model, utilizing wide (14" x 11") continuous forms paper. Dispensed with the 1403 style paper tape control method for an electronic Forms Control Buffer (FCB) to control carriage movement in feeding paper. It really amounted to an electronic version of the old paper tape. 3800 IBM continuous forms printer series, of the 1980s, employing lasergraphic reproduction, typically on letter-sized fan-fold paper. It employed "write black" technology, with the laser "writing" on the photoconductive surface of a rotating drum, which was then coated with a toner, like powdered ink, at the developer station. At the transfer station, the image was transferred electrostatically from the photoconductor to the paper. The paper then passed over the preheat platen and through the fuser station, where the image was bonded (fused) to the paper by the action of heat and pressure. Image resolution was typically 240 x 240 pels. The 3800 employed Z-fold paper which was a sort of shrunk-down version of the old 14" wide forms used in the 1403 and 3211: the 3800 forms were 11" wide. Job control consisted of the usual carriage control character in the first position of each print line, plus an optional second, following position for a Table Reference Character (TRC), which contained a code which referenced the Character Arrangement Table for selecting the character set to be used in printing the line. (JCL: OPTCD=J) 3800 Model 3 IBM continuous forms printer, circa 1984. Resolution: 240 x 240 pels. 3820 Early IBM cut-sheet page printer. Same 240 x 240 resolution as preceding 3800 printers. 3900 IBM continuous forms printer, circa 1996 - 2002. It was a large, multi-station, production printer. Resolution: 240/300 dpi The 3900 was part of a family which consisted of it and the 4000. The startsrv script starts a PostScript transform daemon, using the /usr/lpp/psf/ps2afp/ps2afpd.cfg config file, which its comments say is for the 3900. 4028 IBM tabletop laser printer, circa 1990. A high-performance printer with excellent graphics capability. - Print quality enhancement technology (PQET) - User-friendly 16-character LCD operator panel. - Small operating footprint Speed: 10 ppm simplex cut sheet. AMPV : 20.000 pages. Technique: Laser electrophotographic. Resolution: 300 x 300 dpi. Fonts: 32 internal fonts. IPDS emulation cards for IBM workgroup printers, such as the 1372 and 1145, default to this emulated model, as well as emulating 3812/6. 4224 IBM matrix printer. 4230 IBM matrix printer. 4250 IBM's mid-1980s electro-fusion, all points addressable printer (type-setter, for producing camera-ready master pages). Resolution: 600 x 600 pels per square inch. Software driver: Composed Document Printing Facility (CDPF). 4312 IBM 12 ppm, 600 dpi, tabletop laser printer. PDLs: PCL5e and, optionally, PostScript Level 2, and IBM's traditional AFPTM/IPDS. 4317 IBM 17 ppm, 600 dpi, tabletop laser printer. PDLs: PCL5e and, optionally, PostScript Level 2, and IBM's traditional AFPTM/IPDS. 4324 IBM 24 ppm, 600 dpi, tabletop laser printer. PDLs: PCL5e and, optionally, PostScript Level 2, and IBM's traditional AFPTM/IPDS. 4332 IBM model number for the workgroup printer family consisting of: 4332-001 InfoPrint 32 4332-004 InfoPrint 40 4370 IBM machine type for the Infoprint 62 printer. 5001 Port number on larger Infoprint printers for IPDS printing. Newer InfoPrint workgroup printers may required use of this port, no longer accepting IPDS on port 9100. See also: 9100 5157 See: Infoprint Select ports (TCP/IP) 5A AFP control record (q.v.). 600 dpi printing Increased resolution elevates the size of bitmap files sent to the printer. See also: print-qualities-supported 64xx Auxiliary page selection, referring to the dot-matrix line impact printers in the IBM model line (old stuff). 6795 See: NPM server port 6874 IPM server TCP port number for generally receiving client communications: - GUI communication - Infoprint Select jobs from a Windows client: it is the TCP port number through which the Infoprint Select client submits jobs to the Infoprint Manager server. (But this is not the pathway for subsequent notifications to the client.) The instances of these job submissions seem to be logged on the server in its error.log as 0423-481 entries. seems /etc/services name: psmd The server 6874 port communicates with an arbitrary port on the Windows client, such as 1440 or 1439. 6875 Server TCP port number for communicating status changes to client systems running some flavor of Infoprint Manager GUI, such as the Adminstration GUI or the Operator GUI. /etc/services name: pdeventd 8251 See: PostScript server port 9100 Commonly found printer port number. On HP and other PostScript printers, this is typically the "Raw printing port". On smaller Infoprint printers, with an optional IPDS card (e.g. Infoprint 1585), this port number would accept IPDS streams; but no longer, as of the InfoPrint 1985, which insists upon port 5001 for IPDS. This a "real time" port, which a driving host dwells on to feed the print job's data as the printer prints it. See also: 5001 A4 ISO paper size (210 mm x 297 mm; 8.27" x 11.7"). In all countries except the United States and Canada, A4 is the standard size for "letter" paper. In the U.S. and Canada, "letter" size is 8.5" x 11" (a size whose origin is lost in history). In an attempt to eliminate confusion, the size 8.5 x 11" is termed na-letter rather than letter in IPM. See also: na-letter "aborted by system" Status in GUI for a failed job, where it is red-iconed. (Job state reason.) This is what results when using a Transform Sequence, when the job has a PostScript error and the transform returns a non-zero status. (Without a Transform Sequence would result in "rip failed".) Such a job has key attributes job-hold = true current-job-state = held previous-job-state = processing job-state-reasons = aborted-by-system job-hold-set where job state reason "aborted-by-system" seems to be the key distinguisher for the red icon. The red icon cannot be undone via any known pdmod attribute change: the job seems to have to be subjected to further processing, such as pdresubmit. See also: PostScript error Accept jobs GUI: AD properties, Load Balancing tab Attribute: accept-jobs Indicates whether IPM can assign newly submitted or resubmitted jobs to this AD. If False, jobs are rejected. Overridable by accept-unsupported-jobs server attribute. Accept unsupported jobs Indicates whether the server accepts jobs even when no actual destination supports the required attribute values. If true, the job will be accepted but will be queued in Hold state, because of currently unavailable resources. If false, the job will be rejected. Watch out for /var/spool/lpd/pdlpd_gateway.error_log logging rejections. GUI: Server -> Properties, General Attr: accept-unsupported-jobs (true/false yes/no) Accounting data, log AD: log-accounting-data Server attribute: log-accounting-data Logging occurs in: /var/pd//accounting.logs/ .accounting.log.v1 Server attribute: log-accounting-data Admin GUI: Server -> Properties, General tab, "Log accounting data" Admin GUI: AD -> Properties, Job tab, "Log accounting data" (Usually conforms to server setting.) Note that additional logging can occur in /var/psf/jobcompletion.log, per Attr: accounting-exit, Value: accounting-log See also: Accounting log; pdaccount Access control See: Security Accounting exit AD property for PSF type printers: The GUI Customize tab has an "Accounting exit" selector. Values: "accounting log": invokes the ainuxjobcompletion post-print accounting exit, typically used for print quota (pquota) charging. See: accounting-exit Accounting log /var/pd//accounting.logs/ .accounting.log.v1 file as per AD "Log accounting data" setting (log-accounting-data attribute; "Log accounting data" GUI). Consists of a header followed by the records, one for each print job instance. The header and data records consist comma-separated fields (do not depend upon fixed lengths). Here are the header-named line elements: 1. "Destination" The name of the actual destination (the printer). Length: 1 - 255 chars 2. "Owner": for whom job will print. Of form Username@Hostname for a network submission; just Username if from within the IPM server system. Like: joeuser@PCnumber1 Note that the hostname may merely be the closest relaying LPD host - not necessarily the originating hostname. 3. "ID" (Global ID: the unique job number). Like: 4705600042 4. "Submission Time", GMT basis (Zulu), form YYYYMMDDhhmmssZ. Like: 20020705145602Z for 2002/07/05 14:56:02 (GMT). 5. "Submission Time" (date: MM/DD/YY) Like: 07/05/02 6. "Submission Time" (time of day) Like: 10:56:02 Submission time reflects when the job was sent to transform. Is same as submission-time attribute. Creation and submission times are usually the same, as a job is eligible for transform as soon as it arrives, but submission time *can* be slightly later. Note that this is *not* the time the job started printing. 7. "Completion Time", GMT basis (Zulu), form YYYYMMDDhhmmss. Like: 20020705145609Z for 2002/07/05 14:56:09 (GMT). Is same as completion-time attribute. May be 1 second later than the completion time recorded in the jobcompletion record. 8. "Completion Time" (date: MM/DD/YY) Like: 07/05/02 9. "Completion Time" (time of day) In IPM 4.2 is like: 10:56:09 In IPM 4.4 is like: 07:42:58 AM 03:54:53 PM 10. "Pages Completed" Is 0 for BSD DSS printing, because the print job is blindly sent to the printer, with no further communication with the printer for it to return a count of pages printed. Like: 2 11. "Octets Completed" The size of the source file, being equal to its natural size as the file sits in its originating file system. (Though the job may print via IPDS, the octet size of the AFP/IPDS stream is *not* reflected here.) If the user had printed multiple files with one print command, the value here is the combined size of all the files. Like: 593 A value of 0 is seen where the job partially printed, as when the job was paused by the operator or the printer was stuck and a Shutdown was performed on it. 12. "Format" The page description language of the job as it went to the Actual Destination. (This would typically be "modca-p" as output from a Transform Sequence.) In that this field does not necessarily reflect the actual incoming job type, it should not be considered definitive. Sample formats: ascii modca-p pcl postscript Note: This info is not available in the Jobcompletion record. If this field is empty, it can be due to the job having partially printed, as when the job was paused by the operator or the printer was stuck and a Shutdown was performed on it. 13. "Name" File name. Up to 63 chars, longer names truncated, shorter names as-is (no blank padding on right end). Note that this is longer than the jobname which can be obtained from the Jobcompletion record. If the user had printed multiple files with one print command, the name here is that of the first file. (The GUI will also have shown the multiple jobs under the first file name.) Notes: - In that the accounting record line content is rather free-form, there will not be descriptors for it in /usr/lpp/psf/exits/ainuexit.h (which is for other, fixed-length logs). The accounting record reports only pages printed, with no information explicit or implicit about number of sheets or simplex vs. duplex. - Time resolution is to a second granularity, which is not fine-grained, meaning that you can easily have multiple records with the same timestamp (so consider that in any programming). - The "Zulu" time field format is useful for sorting. - You can substitute a FIFO (named pipe) for this file, as when you want to efficiently capture data, real-time. The fifo reader must keep up with the reopening and reading of the fifo, else output to the AD will hang. - Experience is that the accounting log is susceptible to Daylight Savings Time discrepancies, in contrast to the Jobcompletion log. - If the Pages Completed and Octets Completed values are both 0 when implementing a new printer, that can be due to the new printer requiring the use of a different TCP port number than before, as for example the InfoPrint 1985 requiring the use of its port 5001 for IPDS printing rather than the 9100 of the InfoPrint 1585. - If the Pages Completed value is not 0 but the Octets Completed values is 0, it usually means that the printer printed some pages but did not receive the whole job, and the job was stopped before completion by the host, as for example putting a Hold on a processing job on a PostScript printer. There may be multiple Accounting records for a single job number. These reflect reattempts after a job has started going to a printer but could not complete on the attempt. In such cases, the Pages Completed and/or Octets Completed values will be zero on the failed attempts. The approach should be to take the last instance of an accounting record for a given job number, where the values are both non-zero. Updating characteristic: The IPM pdserver process closes this file after writing each new entry. Cut-off: The file grows indefinitely. You would naturally want to perform periodic cut-offs, monthly perhaps, to secure such a blob for historic reporting. You can do so while IPM is running by simply renaming the file: IPM will start a new one. See also: processing-time; /var/psf/jobcompletion.log; Transforms Accounting log, get netnames from Sometimes you want to extract the network names of submitting systems from the accounting records. Here is the command which can get the unique instances of the netnames: awk -F ',' '{print $2}' | sed -e 's/^[^@]*@//p' | sort | uniq Accounting log, manage Ref: Procedures: "How do you manage the contents of the Infoprint AIX server accounting logs?" Accounting log, printer Under printer Properties, the Customize tab has an "Accounting exit" selector, one value of which is "accounting log". Accounting logs directory /var/pd//accounting.logs/ and have filenames of the form: .accounting.log.v1 Attr: log-accounting-data accounting.logs See: Accounting logs directory; log-accounting-data accounting-exit AD attribute specifying the name of an auxiliary-sheet object that sets accounting exit parameters. GUI: Customize tab, "Accounting exit" field. DSS: PSF, Infoprint 2000 (not AIX) Not available for AIX DSS Possible values: 64xx accounting-log Invokes the ainuxjobcompletion post-print accounting exit, typically used for print quota (pquota) charging. It writes to log file /var/psf/jobcompletion.log. blank Technically valid, but should not be used. brief A sheet with brief accounting info is printed after the job. full A sheet with full accounting info is printed after the job. job-ticket Accounting info is written to /var/psf/podaccounting.log file for AIX. none No accounting info is produced. See also: auxiliary-sheets*; log-accounting-data; printer-end-sheet; printer-separator-sheet; printer-start-sheet ACIF AFP Conversion and Indexing Facility. /usr/lpp/psf/bin/acif An IBM AFP program included with IPM and PSF to convert, index and imbed resources for a MO:DCA archive document. It may be considered a superset of the 'line2afp' command - which is a symbolic link to 'acif'. Whereas 'line2afp' generates only an AFP document file, with references to external resources, ACIF can generate: - An AFP resource file, containing all referenced Overlays, Page Segments, Formdefs, Pagedefs and Fonts (resobjdd=___ restype=all) - An AFP document file (outputdd=) - An index object file (indexdd=) and those may subsequently be physically concatentated, in the above order, to create a complete, self-contained file with inline resources, suitable for archiving or viewing (as with the AFP Viewer Plug-in). With ACIF you can: - Convert line data, XML data, or mixed data into MO:DCA-P. - Index a document to enhance your ability to view, archive, or retrieve individual pages or groups of pages from large documents; create a separate index object file from the indexing tags. - Retrieve and package AFP resources needed for printing or viewing a document and place them in a separate file, so that you can print and view the exact document, possibly years after its creation, when all the original, external resources are long gone. ACIF accepts data from your application in these formats: - AFP data - MO:DCA-P data - Record format or traditional line data - Mixed-mode data - XML data - Unformatted ASCII data (AIX and Windows NT/2000 only) Syntax: 'acif [cc=value] [cctype=value] [chars=fontname(s)] [comsetup=name] [cpgid=value] [dcfpagenames=value] [fdeflib=pathlist] [fieldn={record,column,length} | {literal value | X'literal value'}] [fileformat=value] [fontlib=pathlist] formdef=fdefname [groupname=value] [imageout=value] [indexn={'attribute name' | X'attribute name'},field definition] [indexdd=filename] [indexobj=value] [indexstartby=value] [indxexit=programname] [inpexit=programname] [inputdd=filename] [msgdd=filename] [objconlib=pathlist] [outexit=PgmName] [outputdd=filename] [ovlylib=pathlist] pagedef=pdefname [parmdd=filename] [pdeflib=pathlist] [prmode=value] [pseglib=pathlist] [resexit=programname] [reslib=pathlist] [resobjdd=filename] [restype=value] [trc=value] [triggern={record | *},{column | *}, {'trigger value' | X'trigger value'}] [uniquebngs=value] [userlib=pathlist]' The 'acif' command is not documented in the IPM Reference manual, with other transforms; but you can do 'man acif'. Ref: AFP Conversion and Indexing Facility: User's Guide See also: line2afp ack-interval AD attribute for IPDS printers: Determines how often IPM sends acknowledgement requests to the destination...how often IPM requests updated station counters from the printer while processing a particular job, so as to update the pages-completed value. GUI label: Acknowledgement interval (pages) A smaller ack-interval give you a better view of printing progress, but you pay for this as more frequent taps on the printer's shoulder can reduce throughput as the printer has to interrupt its print processing to gather data and converse with the IPM server. A larger ack-interval lets the printer work with fewer interruptions, which enhances throughput; but the pages-completed number will be of less value to you, and printer status info will be less timely. (But note that printer status is also obtained via SNMP.) Possible values: 1 - 9999 (pages) Default: 100 (pages) The value should probably best be scaled such that the interval computes to a time of about once per minute (its ppm value), which will provide a good view of the printer's status. For a 360 page job, an ack-interval setting of 100 pages means that IPM will send an acknowledgement request to the printer after sending pages 100, 200, 300, and 360. Ref: Procedures manual, Appendix on IPDS Error Recovery See also: current-page-printing; pages-completed Acknowledgement interval (pages) GUI field for the ack-interval attribute (q.v.). ACL An Access Control List, available for security purposes, to restrict access to objects and/or commands. It is very important to remember that ACLs are case-sensitive - which can be a real hassle in the workstation name which the IPM server gets from DNS as a user connects, as the network name of the workstation may end up containing any combination of upper and lower case name components. ACL updating shows up in the server error.log like: D 09/22/06 12:15:48 [5378 joseph->oursrvr] server-operation: aacl/groups/salesgroup See also: fstsecutil; Security ACS for servers Leave empty. Do not add groups to it. (Tried this: resulted in inability to access.) acl_admin See: Security Group Acrobat Reader files Well, there's really no such thing as "Acrobat Reader files". See: PDF files Acrobat Reader fonts Acrobat Reader comes with a small number of fonts, which it utilizes in printing those PDFs which reference those fonts but do not embed them. (This is why the direct printing of a PDF may result in unsatisfactory substitution of Courier, whereas the results of printing of the PDF through Acrobat Reader, as PostScript, look great.) The fonts usually supplied: AdobeSans AdobeSerif Arial... Courier... Symbol TimesNewRoman... ZapfDingbats and are found in the install directory Resource/Font/ subdirectory. Note that PDF documents may customarily utilize the above-named fonts; but PostScript printer font sets don't usually have all of them so the direct printing of a PDF is problematic. This will often be the case for Arial fonts. Action Codes Associated with IPDS exceptions from the AD. As appears on printed error page, in message number 0420-249. HEX DESCRIPTION 01 Data-Stream exception. A syntax error has been found. 02 Operator intervention with OBR record. (Parallel or ESCON Channel attached only) 03 Operator intervention without OBR record. (Parallel or ESCON Channel attached only) 04 Channel Error (Parallel or ESCON Channel attached only) 05 End IPDS Dialog (all printers >V8.0) 06 Function no longer achievable. 08 Paper jam. The printer has detected a jam. 09 Data-related print exception. 0A Postprocessor exception. 0C Resource storage exception. 0D Printer restart. 15 Cancel. 16 Hardware-related print error. 17 Printer mechanism unusable. 18 Log only condition. (Parallel or ESCON Channel attached only) 1A Re-drive buffered pages. 1C Invalid Channel Command Sequence (Parallel or ESCON Channel attached only) 1D Printer characteristics changed. 1F Data stream exception in secure overlay. 22 Printer inoperative (See Note) 24 Printer not assigned. (ESCON Channel attached only) 25 The printer is assigned to another host. (ESCON Channel attached only) 4D Resetting Event. (ESCON Channel attached only) Ref: Manual: IPDS Handbook, Chapter 2 "Exception Reporting and Sense Data", "IPDS Exceptions Reported". See also: IPDS Exceptions Actual Destination In Infoprint, an object that represents the output device that performs the printing or transmission function. The actual destination is the software representation of an output device. An actual destination can be a physical printer (representing a printer device), a fax destination (representing a fax machine), or an email destination (representing an electronic mailing address). Create with Infoprint VSM administrator's GUI, the Infoprint Manager Administration GUI, or the command line. The programs that the actual destination uses to send jobs to the output device are called the destination support system (DSS; q.v.). Advice: One approach to naming an AD is to use upper case letters in it, as for example "EmailPDF" for an Email DSS, and use lower case (easy for users to type) for the corresponding LD ("emailpdf"). This essentially gives you the same name for both the AD and LD, but allows IPM to create both without conflict. See: email destination; fax destination See also: physical printer; printer device. Contrast with Logical destination. Actual Destination, create 'pdcreate -c destination :' Actual Destination, delete 'pddelete -c destination :' IPM prompts for confirmation in deleting the object, unless the environment variable PD_CONFIRM_DELETE is set "no". Actual Destination, shut down 'pdshutdown -c destination ' Inverse: pdenable Actual Destination, start 'pdenable ' Inverse: pddisable; pdshutdown Actual destination Attributes, change 'pdset -c destination -x "Attribute=Value" [:]' Use attribute+=value to add a value to a multi-value attribute. Use attribute-=value to remove a value from a multi-value attribute set, or render a single-value attribute null (reset to default). Use simply "attribute==" to remove all values from the attribute so as to have it lapse to a default value. Actual destination Attributes, list 'pdls -c destination -rall :' Actual destination files In /var/pddir/default_cell/printers/ Note that these files are rewritten in a server restart. See also: Physical destination files Actual destination name Is attr: destination-name Actual destinations in a queue See: Queue, actual destinations, list Actual destinations mix A given logical destination may be served by multiple actual destinations (printers). It is best that the ADs be in the same family, to avoid problems. For example, a good mix of ADs is Infoprint 1585 and 1145 and 2190, for example. A bad mix would be an Infoprint 1585 and HP 9000, where the former is printing in AFP and the latter PostScript or PCL, in that the former requires a wholly different configuration, with Formdef, whereas a Formdef specification is incompatible with PostScript printers. actual-destinations-requested Job/Default job attribute: Identifies a list of actual destinations, any one of which Infoprint may use to process the job. GUI label: Actual destinations requested If you request more than one actual destination, the job will process on the first one that becomes available that can support the job. A job submitted to an LD which has a single associated AD will have that AD assigned to this attribute. If there are multiple ADs associated with the LD, this attribute will be undefined. The order in which the names are coded has no effect. For example, in an environment of two 2105 printers you might want to prefer stapling to one and non-stapling to another (in that mixing is problematic for offset-stacking); but there is no way to achieve this. Moving a job from one queue to another may leave this attribute with the AD appropriate to the other queue, and so the job will red-flag with required-resources-not-supported = actual-destinations-requested. See also: destination-name-requested AD Actual Destination AD Attributes, list 'pdls -c destination -rall :' AD error logs For PSF printers: /var/psf/ For non-PSF printers: none Administration GUI See: Infoprint Manager Administration GUI Administrator, add Oddly, there is no way to do this from the IPM GUI: you have to do it outside of IPM, via SMIT: smit->Infoprint Printing System-> Security->Groups->Add Users To a Group See: fstsecutil; Infoprint Manager Security ADF Automatic Document Feeder, as found on a scanner or digital sender. In a larger context, ADF may mean Automated Document Factory, which is beyond the scope of simple printing. Adobe Distiller Used to convert PostScript files into PDF files. Is included with the server software (hence the elevated price). Adobe PostScript Extreme Adobe's Portable Document Format-based Architecture for High-Volume, High-Speed (commercial) Printing Systems, optionally available for InfoPrint Manager. Extreme for High Volume Printing, a simpler implementation, facilitates full run capacity by employing multiple RIPs to keep up with the output engines. Jobs will be split into individual pages that are then distributed to the RIPs on a "next bus out" basis, that is, whichever device is ready will get the next portion of the job. Much like the read/write heads of a RAID storage device, there will be a minimum of "inactive" time. See also: Digital Master AFCCU Advanced Function Common Control Unit Ref: IPDS Handbook manual AFP Advanced Function Presentation. (Formerly, Advanced Function Printing, in the days when it did only that, introduced in 1984 to support the IBM 3800 Model 3 high speed printer.) (1) A set of licensed programs, together with user applications, that use the all-points-addressable concept to print data on a wide variety of printers or to display data on a variety of display devices. AFP includes creating, formatting, archiving, retrieving, viewing, distributing, and printing information. (2) In architecture, the IBM strategic environment for presentation. AFP is an EBCDIC-based architecture developed by IBM for storing and printing graphical-intensive documents. Around 1990, AFP was deemed an open architecture, published and offered for adoption, hoping to become a de facto standard for electronic printing; but it never went far beyond IBM's own uses. Like its ASCII-based compatriots - Hewlett-Packard's PCL and Adobe's PostScript and PDF - AFP handles the management and routing of text, fonts, graphics, and overlays from the computer to the printer. AFP is primarily a page composition facility, allowing you to place elements on a page. AFP data is device independent, like Adobe PDF. Each AFP page is self-contained. AFP is found in files only, not in device data straeams. In IPM processing, AFP is converted to IPDS, which is device dependent. (Specifically, IPM creates AFP, then its embedded PSF creates IPDS.) That transformation is slight: most of the data stream needs no transformation. PSF tailors the stream to the printer. AFP originated in the IBM mainframe world, and its conventions still adhere to that environment's regimens. In particular, Formdefs, Pagedefs, and related resources are all in EBCDIC, even in an ASCII operating enviroment such as Unix. AFP is a registered trademark of IBM. See also: AFP vs. PostScript; Enhanced AFP AFP Analyzer See: AFP Datastream Analyzer AFP Consortium In October 2004 IBM initiated the formation of the AFP Color Consortium (AFPCC). The purpose was to collaboratively develop color management support in the AFP architecture. This resulted in the creation of the new AFP CMOCA (Color Management Object Content Architecture) specification, which was first published in 2006. In May 2006 IBM announced plans to open up the complete scope of the AFP architecture to the consortium. This new initiative was finalized in September 2006 and is now called simply the AFP Consortium (AFPC). In June 2007, IBM's role as founding member of the AFPC was transferred to the InfoPrint Solutions Company, the new IBM - Ricoh joint venture. Total membership has grown to over 30 companies and includes members from all parts of the document-processing industry. On February 26, 2009 it was announced that the Advanced Function Presentation Consortium (AFPC) had become an incorporated nonprofit organization standards body. Website: http://www.afpcolor.org AFP control record See: AFP file structure AFP Datastream Analyzer A downloadable utility from IBM which interprets the content of AFP files, providing more detail than the afpdmp command. Is more awkward to invoke than afpdmp, in that the invoker has to set LIBPATH to access its private libs. IBM site document number: P4000197 AFP Datastream Dump (afpdmp) The AFP Datastream Dump Utility dumps the contents of your AFPDS document or resource to display the AFPDS structured fields and values. The utility is provided with IPM in: /usr/lpp/psf/bin/afpdm Usage: afpdmp FileName 'afpdmp [-dOx] [-R#[-#]] [-Ssfi] [-Xsfi] filename [filename ...]' (The command also accepts redirected or -d Describe record in detail. -O Give record offset instead of record number. -x Dump record in hex format (raw data) instead of interpreting. -R Select a specific record or range of records. -S Select an SFI to work with. -X Exclude an SFI from being worked with. Values produced by -d execution: PGD: Page Size x The page horizontal size, in terms of the dpi of the transform. 5100 = 8.5" @ 600 dpi PGD: Page Size y The page vertical size, in terms of the dpi of the transform. 6600 = 11" @ 600 dpi Use '-dx' for the fullest output. Tips: You can do 'afpdmp ... | grep PAG' on most AFP files and inspect the BPG PAG00001 and subsequent PAG* page numbers, to quickly determine how many pages are in it. This is particularly useful when performed on the output of a transform which is in progress, to see how far it has gotten. But: line2afp BPG lines have "NAME ........" rather than like "NAME PAG00008": you have to resort to counting the BPG occurrences. Note also that an AFP file may be a composite of multiple AFP outputs, perhaps combined via afpconcat, where there can be multiple PAGs with the same page number. See also: AFP Datastream Analyzer AFP file, identify as being one Irony of ironies: The AIX 'file' command fails to recognize an AFP as AFP; instead, it says the file is: data or International Language text AFP file size vs. PostScript One may wonder about the relative file size of the AFP file generated from a transform of a PostScript file, particularly as the AFP/IPDS file is what is transmitted to the IPDS printer over an ethernet. Observation shows that the size difference can vary quite a bit: sometimes the PostScript is considerably smaller than the AFP, sometimes the AFP is much smaller than the PostScript. One dramatic example: A PostScript job to print 30 pages of text arrived as a file of 251,873,816 bytes and was transformed into an AFP file of only 5,060,198 bytes. That much smaller AFP file can be due to the images in the PostScipt file being inefficiently designed, as where a background image is meticulously rendered and then largely overlaid with foreground elements: IPM can simply send the final image, which is much reduced in data content. This goes to show that "it all depends". AFP file structure An AFP file (aka AFPDS data set) always has X'5A' (EBCDIC '!'; ASCII 'Z') as a carriage control character in the beginning of each record (AFP control record). It serves as a command to AFP. Note that an AFP file has no header: it contains just a sequence of control records, to be processed in isolation, with no context. This is because AFPDS is a stream format, for an output device to handle a sequence of instructions encoded in structured fields. The head of the record looks like: Byte 0 1 2 3 4 5 5A LL LL TT TT TT where: 0x5A is the "carriage control" position designator identifying an AFP control record. The 2-byte LLLL is the length of the record, including this length field (but not the carriage control position). Adding this length to the buffer position of this length gets you to the position of the next 0x5A. The 3-byte TTTTTT is the type, which always begins D3. Example: X'D3A8A8', a hex identifier for the BDT (Begin Document) record. The first record in an AFP file is seen to be BRG (Begin Resource Group), like: 5A 0010 D3A8C6 Note that printing ASCII text results in it being converted to EBCDIC in the PTX records in the body of the AFP. Ref: AFP Programming Guide and Line Data Reference (S544-3884); Mixed Object Document Content Architecture Reference (SC31-6802) AFP fonts Available in product: IBM AFP Font Collection: Fonts for AIX and Windows, Program Number 5648-B33. http://www.printers.ibm.com/R5PSC.NSF/ Web/afpfonthome Provides fonts for printing at 240 or 300 dpi, or higher resolutions using outlines. Also provides the AFP Type Transformer and FontLab, a utility that helps design custom fonts using Type 1 or TrueType outlines. Filename prefixes: CZ XZ The IBM Expanded Core Fonts in the Font Collection are all derived from Adobe (TM) Type 1 or CID scalable font architectures, and are provided in the following formats: - 240 dpi AFP raster format - 300 dpi AFP raster format (SBCS fonts only) - AFP outline format - Type 1 outline format - CID keyed outline format (double-byte font character sets) The AFP outline fonts are created with the Type Transformer program by adding the IBM AFP Font Object Content Architecture (FOCA) structured fields to the Type 1 or CID outlines. The Type 1 and CID outlines are the scalable font formats commonly used for screen formatting with the Adobe Type Manager (ATM) PC software product, and for printing on Postscript printers. Using this architecture as the basis for the Font Collection allows AFP documents to be printed on AFP printers, on Postscript printers or viewed using ATM screen fonts with complete WYSIWYG fidelity. The fonts in the group called "Compatibility" fonts are not available in outline font format, as they pre-dated scalable font technology. They are available only as raster fonts in 240 and 300 dpi AFP format. Ref: See PPFA User's Guide, Bibliography, "Fonts" for list of manuals. AFP job submissions from PC They arrive with a job name consisting of the driver name plus a relative job number, like: IBM AFP 600, Job 7 See also: Infoprint Select; MO:DCA-P AFP Print Driver A driver provided in the Common Clients bundle for installation on a Windows PC for converting print data to AFP on the Windows PC, for submission to Infoprint Manager or directly to an AFP printer. This interface allows the submitter to formulate all characteristics of the job within the PC environment prior to submitting it. IBM document: P4000187; P4000384 Installs into C:\AFP Driver\. See the Readme file in that directory for information. AFP Printer Driver Alternate name for AFP Print Driver AFP printing See: IPDS printing AFP resolution AFP conventionally employs the unusual image resolution of 1440 dots per inch or centimeter. It refers to this as "Page units per unit base" (as in value 14400) with a "Page unit base" of 10 inches, where division of the former by the latter yields the dot resolution. AFP transforms They create MO:DCA-P (MODCA-P). AFP Type Transformer and FontLab A utility that comes with the IBM AFP Font Collection. Helps design custom fonts using Type 1 or TrueType outlines. AFP viewer Generally speaking, this is a software program which generates page images from AFP data files, such that you can evaluate what the AFP will actually generate. This is useful in development cycles, to eliminate the time and waste that would result if proofs were produced through printing. There are two free AFP viewers from IBM, one a straight Windows application (AFP Workbench) and the other a Web browser add-on (AFP Viewer plug-in). An alternative to such a viewer is to use the afp2pdf transform to generate a PDF to a disk file, or use the Email DSS to create a PDF and mail it. AFP viewer for Macintosh? Alas, no known offering. AFP Viewer plug-in IBM-provided Windows AFP Viewer Plug-in. Lets you view AFP documents from a Web browser, allowing you to do things like download AFP files from your host system and view them. You can also print AFP files to both non-AFP printers and AFP printers. IBM document: P4000233 Downloads as gnsp32dm.exe . Environment: Windows 95/98, Windows NT, and Windows 2000 and requires Netscape Navigator (Version 3.01 or later) or Microsoft Internet Explorer (Version 3.01, Level 4.70.1215 or later). AFP textual files to be viewed should be produced with the 'acif' command, not the lesser 'line2afp' variant thereof. Technical reference: http://www.printers.ibm.com/pbin-afp/ go?/pdocs/fldu3mst.html reached from the Printing Systems Software Support Information web page, "AFP Viewer Plugin" link. Comments: Text is displayed with good resolution, but images are crude. See also: AFP Workbench For Windows AFP Viewer plug-in, installing Obtain from IBM web site: http://www.printers.ibm.com/R5PSC.NSF/ Web/afp_viewer_plug-in which downloads installer gnsp32dm.exe . Creates dir: C:\AFPPLGIN and installs plug-in NPOAFP32.DLL into browser PLUGINS directories that it can find - which may not be all of them: you may have to compensate by manually copying it to, for example, Netscape's C:\Program Files\ Netscape\Netscape\plugins directory. AFP Viewer plug-in, configuration Its file FTDPORT2.INI, conventionally in its directory C:\AFPPLGIN, allows you to tailor execution for finding resources such as page segments, overlays, and form definitions, which you might make available to a Windows workstation via a Samba share from the AIX system where IPM transforms are creating AFP files. The FTDPORT2.INI file will show up in a Windows directory listing as type Configuration Settings. The file comes with entry ResourceDataPath=C:\AFPPLGIN\RES but you need to either modify that entry or create the RES directory. AFP Viewer plug-in, using IBM fails to tell you how to use the viewer. It goes like this: - Double-click, or otherwise open the file of interest, which may be locally resident on your PC, or accessed from a Share. In Samba file access, at least: In the Windows directory listing, the Type column should show "AFP File" for the file, which reflects the filename extension being ".afp" (case independent): if it doesn't, then even if the file is actually AFP, the AFP viewer will not get invoked by the browser. (Sorting by the Type column will make things easier.) - Click "Select the program from a list"; click "OK". - In the Open With window, you should see your browser listed under "Recommended Programs". (If not, then the file is likely not AFP: see comments above.) Double-click the line containing your browser - into which the plug-in was installed. The AFP Viewer window should appear. In the image view, red lines mark the borders of the logical "sheet of paper". You can pull at the edges of the window to make the contents larger, which can shift the red lines, such that the page borders are then outside the boundaries of the window. (But note: there will be a vertical scroll bar, but no horizontal scroll bar - you have to resize the window to see the right edge of the "sheet".) Click the "?" icon for usage info. Benefits: - Printing of the viewed AFP document can be done on a PostScript printer. This allows you to very conveniently pursue development and capture hardcopy snapshots on a mundane, non-AFP departmental printer located nearby. Drawbacks: - What is portrayed is a bitmapped image: text cannot be copied because it is not being displayed as such. - No rulers as part of the window, to be able to gauge dimensions. - Fails to account for the Formdef: what it displays is the Logical Page...that which is contained within the Pagedef; thus, you lose sense of where the output will actually appear on the physical page, which is governed by the Formdef. - Error handling is nearly non-existent: a page segment positioning error will result in no error (just absence of the segment) whereas real printing will result in an error page with messages. Defects: - Gray-shading can show up as black, obscuring what is in the shaded area, as when you have a gray box with black type in it. - Use of a simplex Formdef does not result in a simplex display: it shows up as duplex. - Internet Explorer, at least as used with Samba, exhibit a defect, saying: "Cannot find 'file://" where the message accurately lists the full path name of the file, when the file is in a subdirectory below the "mount point" of the Share. IE can't find its way to the file - and inconsistently reflects slashes rather than backslashes in the path name. Circumvention: Use Netscape instead, which has no problem getting to "deep path" files. AFP viewer program "AFP Workbench" (q.v.). AFPviewer www.compulsivecode.com/projects.html Freeware: BARR/AFP Viewer http://www.barrsys.com/product/ afpviewer/default.asp AFP vs. PostScript How does AFP compare with the ubiquitous PostScript? AFP's lineage is mainframe printing, where data lines would contain the data to be printed, along with one or two lead control characters (carriage controk, TRC lookup) governing line spacing, page ejection, and fonts. AFP largely performs page composition functions, allowing you to place data lines and line subsets, and externally prepared objects, anywhere on the page. (More recently, some graphics drawing capabilities have been added.) AFP involves selection and placement decisions rather than programming. PostScript is a full-blown programming language, providing comprehensive facilities for the real-time creation of shapes, as well as the placement of externally authored elements. (PDFs afford no programming constructs, but do allow comprehensive shape generation, as in PostScript.) AFP Workbench For Windows An AFP viewer which acompanies Infoprint Submit, installable from its win/workbench directory. Installs into: C:\Program Files\IBM\AFP Workbench or C:\Program Files\AFP Workbench 32 In the AFP Workbench folder is a data folder containing AFP samples. The IBM Web page for it, as of 2005/08, says: "The AFP Workbench product is no longer supported. A complimentary version of the product is available as an unsupported download." It went out of support 2003/01/31. Latest version: 2.04.01.07 Model/Type Number: 5639-F14 IBM download document ID: P4000360 The download file is: ipsafpwb.exe To use, double-click on a file having a .afp extension, and then Viewer will launch and open and present it. Change the size of the window to govern the magnification of the image. Nuances: It removes inline objects before making use of offset info, such that indexing is accurate. This allows good viewing of AFP files that were created by concatenating AFP resource and document files. Shortcomings: No support for showing images in their natural color - all is monochrome. Don't expect text to be usable as such: Find and Copy should not be expected to work. Stability: Well, it's a Windows app, and like Windows, it may need to restart. I was looking at two simple files in two windows and, after moving the windows around the screen and then closing one, up poppe a dialog box saying: "AFP Workbench Viewer has encountered a problem and needs to close. We are sorry for the inconvenience." Evaluation: This viewer is much more straightforward than AFP Viewer, with no browser complexity, and produces much better imagery. See also: AFP Viewer AFP Workbench Viewer Installs into C:\Program Files\AFP Workbench afp2pdf IPM 4.2, 4.3 transform to convert Mixed Object: Document Content Architecture (MO:DCA-P) documents, also called AFP documents, into Adobe Portable Document Format (PDF) documents to be viewed, archived, e-mailed, or printed. Most typically used to generate a disk file. Transform ID: 8040 In Infoprint Manager, this transform operates through the Transform Manager; but expect to need to install the (extra-cost) IPM AFP2PDF PRPQ, 5799-TWL. There is a manual for it: G550-0538. Basic invocation: afp2pdf -o [-v] An alternative is to employ the Email DSS to generate a PDF (sent via email). This transform can be handy in development and debugging, to see what ps2afp and similar AFP-producing transforms have generated, where you do not have an AFP viewer. afpconcat Utility to concatenate AFP files, apparently intended to operate on multi-dataset files received from z/OS Download. Where: /usr/lpp/psf/bin/ There is no documentation. Basic usage info is revealed by invoking the command with no operands: Usage: afpconcat [-p] control-file-name [additional-acif-options] -p: Indicates page count should be returned Control file format: afp-filename1\n formdef-name1\n afp-filename2\n formdef-name2\n ... additional-acif-options: additional options being used with acif. afpconcat will use the reslib and userlib parameters. The output file name is the first file name in the input file with the extension changed to .AFP. Some info found in Web searches: The comprehensive inline form definition contains medium maps (copy groups) from all of the form definitions associated with the individual data sets. The formdefs requested for each input file are merged into a single combined formdef that is placed inline in the output MO:DCA-P document. If medium map names collide, the afpconcat program assigns unique names and updates references in the MO:DCA-P documents. The afpconcat program merges the inline resource group, discarding page definitions and the original form definitions. Resources with matching resource names and types are compared to verify that they are identical. The process reportedly invokes ACIF for each file and catenates the (modified) ACIF output. Usage example from mvsprsmd.sh: afpconcat $jobfile >>$logfile 2>&1 In operation, afpconcat combines the specified files into a new, composite AFP file whose name is derived from the first line of the control file, removing the last dot-qualified portion of the file name, then appending ".AFP". And it deletes the input files! What it does is really concatenation: if you do 'afpdmp ... | grep PAG' on the resulting file, you will see BPG PAG00001 more than once in the report. The command does work on empty files, as when you sometimes want to produce a separator page ahead of a PostScript output, but sometimes not, such that the same first filename may be used for both, where it is null (as for example copied from /dev/null) when no preceding page is to appear. (In this case, the output file is not the same size as the second input file, as you might expect: the output is somewhat larger. Defects: The -p option results in a "Segmentation fault". afpdmp See: AFP Datastream Dump AFPDS Advanced Function Presentation data stream (AFP data stream). The device-independent, application level form of data, which is in a neutral form, ready for specific transformation (by PSF) for display or printing on a given device. This is in contrast with output device-specific data streams, such as the printer data stream, IPDS. The AFP data stream includes composed text, page segments, and electronic overlays created by authoring applications, form definitions, and fonts downloaded from the operating system to the printer. AFPDS consists of structured field records which describe the content, placement, and characteristics of text, image, and graphics objects on a page. Pages created in this data stream are sometimes called "composed pages", or "composite documents". The AFP data stream includes MO:DCA-P-based data streams. Specifically, the AFPDS consists of structured fields which describe the content, placement, and characteristics of text, image, and graphics objects on a page. Pages created in this data stream are sometimes called "composed pages" or "composite documents". Pages are composed individually, and are thus independent of each other. (In this way, AFP is akin to PostScript, where pages are largely self-contains, as opposed to PDF, which is document oriented.) AFPDS provides all-points addressability in support of page printers. Pages are composed individually, and can stand alone. Resources in effect for each page are identified on a page-by-page basis, which provides accurate, automated error recovery and operator-directed restart at any page boundary. AFPDS is a raster format wherein the image is comprised of a matrix of zeroes and ones (white and black). This is to say that AFPDS is a bitmap format. The volume of bits can be reduced through tesselation: subdividing the image area into tiny squares, or tiles, where tiles with no image data can effectively be eliminated, and repetition of image patterns can utilize one tile more than once. AFPDS was originally called the Composed Page Data Stream (CPDS). Contrast with: IPDS See also: PSF afpdump You mean "afpdmp". See: AFP Datastream Dump ain* Prefix for various PSF modules such as ainbe ainhyper ain3* Prefix for various PSF modules such as ain3dccu ain3dpds PSF Command, Other ain3dtcp PSF TCP/IP, apparently Dir: /usr/lpp/psf/bin/ ain3dccu Channel Attached Printer Secondary process. Handles IPDS data, handed to it by ainmain, which has converted the data from AFPDS to IPDS. ain3dpds The Infoprint Manager PCL Secondary Print Process, used by the "PSF other-driver printer" DSS and the "PSF Command printer" DSS. (The PCL Data Stream process.) Handles IPDS data, handed to it by ainmain, which has converted the data from AFPDS to IPDS. ain3dpds then transforms the IPDS to PCL, for output to an AD program/process handling communication with a PSF Command or PSF Other printer. A ps2afpi process first transforms the incoming PostScript to APF, then ain3dpds transforms that to PCL, which it pipes through the specified command to put the file into the AIX print queue. (lsof shows this as a FIFO file descriptor.) The ain3dpds process is created when the AD is Enabled, and goes away when the AD is Shutdown. The AIX process looks like: ain3dpds 000 pubpd1 which is a child of: ainmain pubpd1 which in turn is a child of: /usr/lpp/psf/bin/./ainhyper pubpd1 The PCL Secondary performs the following processing: 1. Mimics an IPDS printer so that IPM can capture the IPDS data stream (a process that the other 2 PSF secondary print processes do not perform). 2. Converts the IPDS data stream into PCL with the appropriate fonts, formatting, image and text data commands. 3. Executes a print command that sends the job to a printer. For a PSF Command printer, you can resolve problems printing with the PCL Secondary by shutting down the queue that is identified in the print command used to send the job to the printer. For example, if using the AIX qprt command as your print command, you might specify: qprt -P pcl -dp -Z! -o -fv There are specific requirements that must be observed when sending jobs through the PCL Secondary: - IPM only supports printing the following data streams as output of the PCL Secondary: PPDS, PCL4, PCL5 & PCL5c. - The printer must be defined to IPM as either a PSF Command or a PSF Other-driver DSS. - The PCL Secondary cannot use either printer-resident fonts or outline fonts. - The PCL Secondary supports duplex printing for standard PCL media sizes such as letter & A4, not for custom media sizes. - The PCL Secondary only produces PCL image data when there is image in the data sent to it. The PCL Secondary converts on a job basis only and does not save AFP resources (whether fonts, overlays or page segments) from previous jobs received from the PCL printer. Because the resulting jobs are printed in a random order, often on different printers, none of these printer resources (including fonts) can be reused in subsequent jobs. The module is a CPU eater, which easily drives a CPU to 100% busy. As it's doing so, observing the contents of /var/spool/qdaemon (the AIX spool data directory) shows the output PCL file growing. Sadly, though the IPM concurrency value may be more than 1, this module will one Dir: /usr/lpp/psf/bin/ Accesses files: /var/psf//statfile.log (Infoprint Statistics File) /var/psf//error.log (Infoprint Error Log) Ref: APAR IY38680 See also: ainmain; pdserver ain3dtcp TCP/IP Attached Printer Secondary Print Process, handling communication with a PSF TCP/IP (IPDS) printer. Runs under ainmain, which runs under ainhyper. Handles IPDS data, handed to it by ainmain, which has converted the data from general AFPDS to printer-specific IPDS. This process stays in contact with the printer for the duration of the IPDS conveyance, and thereafter for the duration of the destination-release-timer value, whereupon it exits such that it and ainmain and ainhyper only then go away. By definition, there should never be more than one ain3dtcp process in existence for a given printer. In IPM 4.2 on AIX 5.2, the ain3dtcp process has been observed to consume an absurd amount of CPU time when printing AFP/IPDS which originated as page-oriented PostScript or PCL. It is especially persistent with a printer problem state, as on an Infoprint 2105ES having "Error 200 (30) Paper Jam". IBM found this to be caused by an AIX TCP defect. See also: ainmain; ainhyper; pdserver; SNMP and IPM 4.2 ainbe The printer input/output backend program used by the PSF DSS to send jobs to printer devices. Aka "PSF backend". /usr/lpp/psf/bin/ainbe This is obviously the AFP->IPDS translator and resource compiler: it has to translate generic AFP to the IPDS specific to the destination printer, and pull together the possible Formdef and font resources that the job may have called for at submit time. One ainbe process is started for each object sent to a PSF AD. Depending on the incoming data stream of the job, the PSF DSS may have transformed the data stream of the job prior to the backend program sending it to the printer device. From observation: ainbe runs ainhyper, which runs ainmain, which runs ain3dtcp. (There is no IBM-provided documentation of ainbe, except as a glossary definition.) The ainbe process takes a variety of parameters... Its first parameter is the AD name. Thereafter follow Keyword=Value sets, as for example: JOBNAME=Microsoft Word My Great.DOC spoolid=4895601796 FORMDEF=F1______ DUPLEX=YES PASSTHRU=class=N DATATYPE=AFPDS SEGMENT=YES DISTRIBUTION=someuser@some.IP.addr COPIES=1 SIDEBYSIDE=1 PROOF=YES /var/psf/seglist/4895601796.0.hostname .pdpr7p7jLM_xfm1.0039 In particular, the FORMDEF=________ parameter is the formdef which the IPDS processing should use. (See topic "Form Definition used".) Is seen to create small files like /var/pd//ainbeT94uM6 which contain processing parameters like: PIO_IPCWRITEFD=5 QUEUE_BACKEND=/usr/lpp/psf/bin/ainbe echo $$ >/var/psm/.acstmp/24.20468 exec /usr/lpp/psf/bin/ainbe tsthspr3 SEPARATOR=no TRAILER=no JOBNAME=____ FORMDEF=F1______ DUPLEX=YES PASSTHRU=class=S DATATYPE=AFPDS SEGMENT=YES DISTRIBUTION=Who@Host COPIES=1 SIDEBYSIDE=1 PROOF=YES /var/psf/seglist/ 2224900231.0.Host.pdprJNt-u9_xfm1.0110 3<>/var/pd/Host/stat1tt--n 5>/var/psm/.Host/11.20468 The maximum-concurrent-jobs attribute apparently limits the number of ainbe's. Problem handling: On rare occasions, an ainbe process may be found looping. (Such a looper *may* not interfere with printing, but then again you might encounter odd hangs in sending current jobs to the printer which the looper was originally sending to, and this may be the cause of such mystery hangs.) Such a process may be gotten rid of by doing 'kill -9' on it ('kill' alone won't cause it to go away). ainhyper PSF "shepherd" process, as in outputting a print job to an AD. It will show up in the AIX Process Table like: /usr/lpp/psf/bin/./ainhyper The oldest ainhyper for a given AD will serve as a manager for the one or more ainhyper processes destined for that AD, up to the maximum-concurrent-jobs limit. Under the worker ainhyper there will be an ainmain process for feeding the AD, with a feeder process like ain3dtcp under it. The manifestation of the ainhyper process depends upon the AD Release Time value (destination-release-timer attribute): - With a short value, where the AD is released and reacquired, ainhyper will first appear as a child of pdserver, as the jobs is in "processing" state and then, when the job is ready for output the ainhyper process becomes disowned and falls under the init (#1) process (status: printing), where is endures until it completes the output processing of the job, whereafter the ainhyper process evaporates. In that in this case ainhyper processes exist only for the duration of job shepherding, there should be no old ainhyper processes: see IPM SERVER PROBLEM SITUATIONS near the bottom of this file for problem handling. - With an "infinite" 9999 value, the ainhyper process is persistent as a separate process (no parent; shows up under init). In either case, there will be only one ainhyper process per AD, whether the job is in "processing" or "printing" state (the AD is serially used). If the AD is shut down, its ainhyper process goes away. If the AD is enabled after being shut down, and the ainhyper process stays lingering under pdserver indefinitely rather than going to run under init, it indicates a problem with the AD, which is not accepting data from IPM. Indications: If the ainhyper process lingers as a child of ainbe (non-infinite Release time), it indicates, from my experience, that it is waiting for the designated AD, but has not made sufficient communication with the AD to commit to output. If the ainhyper process leaves ainbe and becomes a process on its own, but then lingers with a job in-flight, it often means that there is a problem in continuing to communicate with the AD, as when a 2085/2105 printer web page says "061 Tray 1 not properly set. Reset tray 1.". ainmain The IPM Primary Print Process. Handles data which has been transformed to AFPDS, which is to go on to an AD as IPDS. The only exception to this pattern is ASCII data that goes through the ASCII converter in the Primary Print Process. The Primary Print Process' primary task is converting the AFPDS data into IPDS format, so it can be passed onto one of the 3 secondary print processes, all of which are based upon the type of printer attachment: - TCPIP attached printer secondary (ain3dtcp) - Channel attached Printer secondary (ain3dccu) - PCL secondary (ain3dpds) Where: /usr/lpp/psf/bin/ainmain Seems to be responsible for the contents of /var/psf//. Runs ain3dtcp as a child process. See also: ain3dpds ainurpt7 Reports /var/psf/jobcompletion.log data sorted by actual destination, resulting in a short summary report. Syntax: ainurpt7 ainurpt8 Reports /var/psf/jobcompletion.log data sorted by job submittor. Note: Handles a disappointingly limited number of usernames, and will fail in most real-world shops - which is to say that the command is generally useless. Syntax: ainurpt8 ainurpt9 Reports /var/psf/jobcompletion.log data sorted by jobs. Syntax: ainurpt9 (The manual erroneously specified that the command had no operands, and would report all users.) ainux* User exit modules. See: User exits ainuxjobcompletion.c Post-print accounting exit source file. Accounting log: /var/psf/jobcompletion.log (q.v.) See: User exits See also: accounting-exit AIX client Is installed with the AIX server. The Infoprint AIX client allows you to enter Infoprint commands on the AIX command line. It also allows you to enter lp, lpr, and qprt commands. It has no graphical user interface. AIX destination support system In this arrangement, IPM does (AIX DSS) essentially the same as what AIX printing does: receive, queue, and send jobs as-is to the actual destination, using a back-end program (pioibmnpm?), with some additional info being provided by that program. Another way of saying this is that this DSS can drive any printer which an AIX queue can. In standard AIX printing, users submit jobs to an AIX print queue: the AIX print-spooling subsystem schedules the jobs and passes them to a printer device by means of a backend program, usually piobe, pioinfo, or pioibmnpm for directly feeding a printer (synchronous handling); or if the destination is a remote queue, rembak (asynchronous handling). The pio* back ends tend to work the same, differing in the default port number accessed on the printer. In the AIX DSS, users submit jobs to an IPM destination from which an IPM queue receives them. The IPM AD submits jobs to the printer device using an AIX backend program. The IPM queue thus does what the AIX queue does in AIX printing. No AIX queueing is involved: the AIX DSS feeds the jobs directly to the printer device - its engine - not a frontal queue in the printer, as for example when a printer provides built-in LPD support. This is synchronous printing: the back end program stays in session with the printer until the job finishes, whereby page-done and job-done messages can be received from the printer (if it supports PJL). Contrast this with BSD DSS, where the job is asynchronously sent. Fields to be filled in: Name Server Model SNMP TCP/IP address Device (leave blank) Printer command [backend] For 2085/2105, use /usr/lib/lpd/pio/etc/pioibmdpm IPaddr For other, general printers, use: /usr/lib/lpd/pio/etc/pioibmnpm IPaddr [Port] Accounting data: This kind of DSS does not have an accounting-exit. Important characteristics of this arrangement: - AIX DSS can drive any printer an AIX queue can drive. - Model: The printer you intend to drive must appear in the server's "AIX printer models" (snmp-aix-printer-models attr), or must match the file prefix of a file in the AIX /usr/lib/lpd/pio/predef directory, unless the destination-model is an Infoprint model such that the external name (for example, an Infoprint 20) is mapped to the predefined name for you. Example: When defining the printer in the GUI, in the Model field you enter "generic", which utilizes the "generic.*" files in the predef directory. Note that a given printer engine feature package will typically not augment the list of model choices. - IPM serves only as a queue and load balancing agent. - The data is *not* transformed: the PCL or PostScript data will simply be passed through, and the printer will handle it as given. - Accurate page count and like info may be obtained, under some conditions. You should attach this type of printer device as specified by its documentation before creating its associated Infoprint actual destination. In addition, all necessary driver files for the printer device you are creating must be installed before creating the associated Infoprint actual destination. How duplex is effected: The job gets its duplex settings either at the submission point or, more commonly, from the Job/Document Defaults. Such settings become job attributes "sides" and "plex". When the IPM server gets to the point of conveying the PostScript job to the printer, it invokes pioibmnpm with a -Y option for that conveyor to know what plex setting to use, being one of: -Y 0 Simplex -Y 1 Duplex, long edge binding (the most common, for portrait) -Y 2 Duplex, short edge binding which will cause pioibmnpm to set PJL duplex value, as described in topic "Duplex printing via PJL". But note that if the PostScript contains a conflicting specification of plex, what is in the job's PostScript will prevail. For example, if the job emanates from a Windows PC and its printer instance is set up as '"Print on Both Sides" = None' then the PostScript will be generated to contain "<< /Duplex false /Tumble false >> setpagedevice", and simplex will result, regardless of anything to the contrary. The Linux version of IPM has a CUPS DSS parallel to the AIX DSS for AIX systems. See also: destination-model; pioibmdpm AIX print commands enq [-P DestinationName] [-okeyword=value ...] FileName ... (enq invokes pdenq, as of AIXv4) The enq command is AIX's fundamental print queue insertion tool: other printing commands invoke enq under the covers. lp [-d DestinationName] [-okeyword=value ...] FileName ... (lp invokes enq, which invokes pdenq, as of AIXv4) lpr [-P DestinationName] FileName ... (lpr invokes enq, which invokes pdenq, as of AIXv4) qprt [-P DestinationName] [-okeyword=value ...] FileName ... (qprt invokes enq, which invokes pdenq, as of AIXv4) See also: AIX printing commands accommodate IPM; pdenq AIX printing commands accommodate IPM If you do 'enq -A' or use an AIX command (or its LPD) to print to an IPM logical destination, the request somehow gets there. But how? Database item RTA000166101 explains: "Many AIX versions ago, the AIX enq command was changed to first check the AIX queues (queues defined in /etc/qconfig) for the existence of the requested queue. If it isn't found it checks for the existence of the pdenq command (pdenq is Infoprint Managers (first was PSM's) version of the aix enq command). If it finds pdenq, it hands the request off to it which then checks for the requested Logical Destination." If you invoke the AIX 'strings' command and/or otherwise examine the AIX commands 'enq', 'lpq', and 'lpr' binaries, you will find the string "/usr/lpp/pd/bin/pdenq". (It's not in the 'qprt' command; but that command issues the 'enq' command, which gets back to the same thing, as borne out by AIX accounting records.) See also: AIX print command AIX requirements Infoprint Manager for AIX requires the AIX operating system to be installed at Version 4.3.3 or later. It also expects the Common Desktop Environment (CDE) to be installed on the system. AIX server install Also installs the AIX client. aix_base.ecf The AIX product base Enrollment Certificate (license) file. See also: .ecf aixpdnls Name of the AIX Infoprint client software to format and print PostScript and PCL files. Formal driver name: "PS, PCL5e and PCL6 for AIX" Ref: IBM Infoprint 2085/2105 Ethernet and Token Ring Configuration Guide Alignment test pages /usr/lpp/psf/ps/align8.5x11.ps APA All Points Addressable: A fundamental attribute of AFP/IPDS processing where specification of a position on the page is down to the point level (more exacting than character position), thus allowing intermixing of graphics and text on the page, with exacting placement. See also: MO:DCA APAR installation command See: ip_update API There is no published API for Infoprint Manager, which a customer might use to do some custom programming. The operator and administrator GUIs pass information and alter values by means of OIDs and values, passed in TCP packets (not SNMP packets). apka2e An input exit program to convert ASCII file data to EBCDIC, for use with EBCDIC fonts. It is /usr/lpp/psf/bin/apka2e. It is is appropriate for ASCII files which contain only linefeed controls, not carriage returns and form feeds, and thus is suitable for Unix text files, where each line is marked by a final newline character, which is actually a line feed. Is used with the line2afp command, via inpexit=/usr/lpp/psf/bin/apka2e. Alternative: Use provided AFP ASCII fonts, which will work directly with ASCII text to generate proper output. See also: asciinpe apmctrc.log In /usr/lpp/pd/bin/. ASCII American Standard Code for Information Interchange: a 7-bit character code which is predominantly used in the industry - despite only allowing 128 combinations of characters. ascii See as the document-format of some jobs. Users may manage to submit jobs containing all binary zeroes, which the IPM server deems to be ASCII. This can happen where the users transfer (e.g., FTP) job files to their timesharing system accounts where they have exhausted their disk quota allotment, resulting in files devoid of content. ASCII, convert to EBCDIC AFP is primarily an EBCDIC facility, and mixing ASCII into it can cause headaches. IPM provides means for converting ASCII to EBCDIC: 1. The uconv command: uconv -f 850 -t 500 > 2. Commands 'acif' and 'line2afp' have an "inpexit" parameter. ASCII fonts These are fonts which can be used to directly print ASCII, without having to translate the ASCII to EBCDIC in using other fonts. Referenced via files in /usr/lpp/psf/reslib/, with names like "H262" (which refers to file X0H262, which is a symlink to X0H23062). These files are not the fonts themselves, but are Coded Font files containing the EBCDIC names of the actual font files in /usr/lpp/psf/fontlib/. (Do 'afpdmp' on them to inspect.) For example, X0H23062 contains the EBCDIC name C0H20060. The PPFA FONT command likes font names in their natural 8-char length (using just the 1-6 chars following the conventional "X0" prefix). The 'line2afp' command wants 4-char font names; hence that shortening. Point sizes below reflect height, not width, from the baseline of one line to the baseline of the next, allowing for asenders, descenders, and the minimum white space between lines. X04 Courier family (fixed width): X042 Roman medium X0423 Latin1 country extended X04202 -> X0423002 10 pts, 12 cpi X04272 -> X0423072 7 pts X04282 -> X0423082 8 pts X042B2 -> X04230B2 12 pts, 10 cpi X042D2 -> X04230D2 14 pts X042J2 -> X04230J2 20 pts X0H Helvetica family: X0H202 -> X0H23002 10 pts, 12 cpi X0H262 -> X0H23062 6 pts X0H272 -> X0H23072 7 pts X0H282 -> X0H23082 8 pts X0H292 -> X0H23092 9 pts X0H2A2 -> X0H230A2 11 pts X0H2B2 -> X0H230B2 12 pts, 10 cpi X0H2D2 -> X0H230D2 14 pts X0H2F2 -> X0H230F2 15 pts X0H2H2 -> X0H230H2 18 pts X0H2J2 -> X0H230J2 20 pts X0H2N2 -> X0H230N2 24 pts X0H2T2 -> X0H230T2 30 pts X0H2Z2 -> X0H230Z2 36 pts X0N Times New Roman family: X0N202 -> X0N23002 10 pts, 12 cpi X0N262 -> X0N23062 6 pts X0N272 -> X0N23072 7 pts X0N282 -> X0N23082 8 pts X0N292 -> X0N23092 9 pts X0N2A2 -> X0N230A2 11 pts X0N2B2 -> X0N230B2 12 pts, 10 cpi X0N2D2 -> X0N230D2 14 pts X0N2F2 -> X0N230F2 16 pts X0N2H2 -> X0N230H2 18 pts X0N2J2 -> X0N230J2 20 pts X0N2N2 -> X0N230N2 24 pts X0N2T2 -> X0N230T2 30 pts X0N2Z2 -> X0N230Z2 36 pts In /usr/lpp/psf/fontlib: X0EW72 Seemingly an EBCDIC font. X0EW96 Seemingly an EBCDIC font. X0EY72 Seemingly an EBCDIC font. X0EY96 Seemingly an EBCDIC font. X0KW72 Seemingly an EBCDIC font. X0KW96 Seemingly an EBCDIC font. X0KY72 Seemingly an EBCDIC font. X0KY96 Seemingly an EBCDIC font. Ref: Manual "Font Summary for AFP Font Collection" (S544-5633). Ref: IPM Procedures manual, chapter "Working with fonts", "Fonts for printing line data". Note that the TSM GUI's printer properties "ASCII/EBCDIC" tab lists ASCII font mappings. See also: Font size; GT10; line2afp ASCII printing Ordinary ASCII data files do not employ either carriage control (Traditional processing) nor Record IDs (Record Format processing). Only Traditional processing can not require triggering areas within the data; and Traditional and Record processing commands cannot be mixed in a Pagedef; and so only Traditional processing can be employed to print ASCII data. ASCII printing margins Being unformatted data, margins need to be supplied external to the job data. That could be done via PPFA in either FORMDEF OFFSET, or PRINTLINE POSITION values. ASCII transform line2afp ascii-font-map AD attribute in PSF printing, to define how the destination maps the ASCII font escape sequences to AFP character sets that IPM uses for ASCII fonts, to map each font-change escape to an AFP font character set. GUI label: ASCII fonts mappings See also: C0* asciinpe An input exit program to convert ASCII file data to EBCDIC, for use with EBCDIC fonts. It is /usr/lpp/psf/bin/asciinpe. It is is appropriate for ASCII files which contain linefeed, carriage returns, and form feeds. As such, it is more suitable for text files created under Microsoft operating systems, where the end of each line is marked by a CR LF pair. Is used with the line2afp command, via inpexit=/usr/lpp/psf/bin/asciinpe. Alternative: Use provided AFP ASCII fonts, which will work directly with ASCII text to generate proper output. See also: apka2e assign-to-destination Queue attribute for controlling Early Binding vs. Late Binding...which is to say jobs may be assigned to available destinations as soon at they arrive ("true" = early binding), or only when a destination is free to process the next job ("false"). It is common to have a value of "false" so that the queue waits until a job is next to be scheduled to print, then assigns it to the first suitable actual destination to become available (late binding). GUI label: Preassign jobs to actual destination Early Binding facilitates multiprocessing, which is important in doing RIPing well ahead of printing so that the printer does not sit idle as the next job initiates RIPing. It is common to not bind early, to let the next available AD processs a job as it approaches processing time. That is, late binding is common. Attempt to register with server Element of Printer Properties, Tuning tab: Specifies the amount of time that this actual destination will wait between attempts to communicate (register) with the server. This applies when the actual destination and the queue are in separate IPM servers. If the IPM server containing the queue is not running, the printer in the running server keeps trying to establish contact with the server that contains the queue. This attempt is made every n minutes with the following effect: - If you lower the value, network traffic increases when the server is down, but the actual destination registers more quickly when you bring up the server. - If you raise the value, network traffic decreases when the server is down, but the actual destination registers more slowly when you bring up the server. Attrib: destination-register-threshold Default: 10 (minutes) Attribute, change 'pdset -c -x :' For example, to change the maximum number of copies: 'pddisable :' 'pdset -c destination -x 'maximum-copies-supported=2' myserver:mydest' 'pdenable :' Note that some attributes can only be definied initially, and not changed thereafter, such as destination-data-stream. Attribute, job, delete 'pdmod -x '==' :' Attribute, job, modify See: pdmod Attribute values, multiple To specify multiple values for an (multiple attributes) attribute, simply code them with spaces in between, like: -x 'attrx=first second' which will result in pdls showing: attrx = first|second In an attributes file, it is common to have each value on its own line, like: attrx = first second attribute-map Actual Destination attribute for BSD destinations. Provides a list of Infoprint attributes and their associated generated command flags. GUI Label: Map attributes to flags Separate each pair of values with a colon, for example: destination-pass-through:-o See also: BSD destination support system Attributes, destination, list all 'pdls -c destination -rall :' Attributes, extend See: job-attributes-supported Attributes, job, list 'pdls -c job -rall -U :' Attributes, Job and Document As used on pdpr command via option -x "attribute=value ..." where you can specify multiple attributes within one -x spec, or you can have multiple -x specs on the command line, with one or more attribute equates in each. Ref: Chapter 7 of the Infoprint Manager: Reference Attributes, modify Via the Admin GUI, or the 'pdset' command. Attributes, set (define) Via the Admin GUI, the 'pdcreate' command, or the 'pdset' command. Attributes = A "command attribute" which names an attributes file, which contains some number of object attributes. Usage: - On a command line, like: -x "attributes = AFPprinterAttrsFile" - In an attributes file (to have one attributes file insert another at that point): attributes = AFPprinterAttrsFile Attributes File A file containing a collection of "keyword = value" attributes, one per line, as fed into various IPM commands via "-X AttributesFilename" or "-x 'attributes=AttributesFilename'". The 'pdls' command allows you to generate an attributes file from prevailing settings via the '-r archive' invocation option. Important: IPM regards an attributes file as a kind of "batch" file, and as such its contents are treated somewhat differently than via the -x command line option. In particular, IPM recognizes the '#' character as beginning a comment within the batch file, EVEN IF THAT '#' IS WITHIN THE ATTRIBUTE VALUE. Thus, if the file contains job-name='My job #1' what will happen is that the '#' and everything after it on the line will be treated as being a comment, meaning that IPM will attempt to process the line as job-name='My job which will fail, in that there is no quote on the right end! (IPM's programming fails to account for values being in quotes, to leave anything in quotes alone, as an integral unit.) To be able to have the '#' in an attributes file value, you need to precede the '#' by a backslash, so needs to be: job-name='My job \#1' Described near the beginning of the Reference manual. Attributes supported, add to See: job-attributes-supported Audit exit Under printer Properties, the Customize tab has an "Audit exit" selector, possible values: 64xx accounting log blank brief full job ticket none Authorization See: Security automatic-postscript-mode-switch AD attribute: Indicates whether the AD supports switching into PostScript mode using controls placed in the data stream. This allows printing PostScript documents among non-PostScript documents. GUI label: Switch to PostScript automatically Auxiliary Sheet An Infoprint term for a sheet of paper which is external to a job, added to the job output per Infoprint specs. The most common and familiar Auxiliary Sheet is the job separator page ("Start sheet"). An auxiliary sheet is a sheet of paper that prints at the beginning, prints at the end of a job, or separates different parts of a job. The auxiliary sheet may have information printed on it or it may be blank. Infoprint provides five default types of auxiliary sheets; you can create more as required. Auxiliary sheets allowed GUI: Element of Printer Properties, Auxiliary/Separator Sheets tab. Possible values: end none sep sep,end (sep-end) start start,end (start-end) start,sep (start-sep) start,sep,end (start-sep-end) See also: Auxiliary sheets allowed; End sheet; Slip/Separator sheet; Start sheet Auxiliary sheet object, list attrs 'pdls -caux -rall :' Auxiliary sheet objects, list attrs 'pdls -caux -rall :' Auxiliary/Separator Sheets GUI tab Attr: auxiliary-sheet-selection (q.v.) auxiliary-sheet-selection Initial value job attribute: Identifies the combination of start, separator, and end sheets requested for the job. Possible values: none, start, sep, end (where "none" is actually a value word for the attribute, not the absence of a value, or attribute absence). Jobs often arrive with a value of "start", per their generating application. Whether Infoprint prints the requested sheets depends on the actual destination. For a BSD DSS, the value whould be null (no value, not even "none"). GUI Label: Auxiliary/Separator Sheets In the Procedures manual, see topic "Allowing the auxiliary-sheet-selection job attribute with the BSD DSS". See also: printer-start-sheet; printer-separator-sheet; printer-end-sheet auxiliary-sheet-selections-supported Actual Destination attribute: Identifies the combination of start, separator, and end sheets that this destination supports for jobs. GUI: Auxiliary sheets allowed DSS: AIX, PSF, Infoprint 2000, IPP, Passthrough, Print Optimizer (not BSD) Allowed Values: end none sep sep-end start start-end start-sep start-sep-end - If you remove all values that specify a particular auxiliary sheet (such as "start"), the job submitter cannot "turn off" the corresponding actual destination attribute (such as printer-start-sheet). auxiliary-sheet-selections-supported Logical Destination attribute: Identifies the combination of start, separator, and end sheets that this destination supports for jobs. GUI: No GUI access DSS: AIX, PSF, Infoprint 2000, IPP, Passthrough, Print Optimizer Allowed Values: end none sep sep-end start start-end start-sep start-sep-end Default: No default values (all valid values supported). - If you do not specify a value, the corresponding actual destination attribute controls which auxiliary sheets a user can request. The default values for the actual destination attribute are all of the supported values. Bar codes (barcodes) A set of parallel bars and spaced of varying widths which together make a unique, scanner-readable patter, used to represent alphanumeric characters, special characters, and punctuation. The bars are a solid (usually dark) color, interleaved with the spaces, the background (usually light) color. The mix of bars and spaces much conform to a set of encoding laws which, together, are called a symbology. One can code bar codes one's self, in that they are a lot simpler than human-readable characters: - Each character is a sequence of bars and spaces of defined widths. - The ratio of bar and space widths is important. - Height is usually unimportant. All bar codes require stop/start characters so the bar code reader can recognize a coded string as being a specific type of bar code. Most also require one or more check digits for error verification. For many bar codes there exists no direct correspondence between the bar code symbols and the characters they represent. For example, some codes use identical groups of bars and spaces to represent entirely different things depending on where certain characters appear in the code or what characters precede others. For one type of bar code, bars convey one type of data, while intervening spaces convey completely different information. The calculations required to compute and assemble a readable bar code under these circumstances are quite complex. The IBM AFP Toolbox can generate bar code objects. Bar code samples: http://www.lifesuccess.org/bcodet.html See also: BCOCA; HRI base-printer Attribute: Indicates the printer model you want to RIP the document for. GUI: Job and DOcument Defaults, Document Print Quality tab, "RIP for" Really needs to be specified only if you want to RIP for a printer other than the one that the AD is defined for. Basic server When you install the Print-on-Demand Feature, the standard server environment is replaced by or extended with the basic printing environment. The basic printing environment is generally appropriate for commercial print shops printing large runs of image data (usually in PostScript or TIFF format). These large jobs often include variable data for direct mail programs. Users submit these jobs from a client (Windows or Macintosh) personal computer using Infoprint Submit or a scanning tool and related software. In a basic printing environment, Infoprint Manager assigns jobs to printers through early binding: the job is committed to a destination when it arrives. Contrast with: Standard server See also: Print-on-Demand Feature BCOCA Bar Code Object Content Architecture. Manual: Bar Code Object Content Architecture Reference, available at: http://www.printers.ibm.com/R5PSC.NSF/ web/archm See also: Bar codes Berkeley See: BSD destination support system Billing counter See: Clicks "Binary characters" Characters outside the ASCII displayable realm are displayed in the GUI as square boxes, as most often seen in foreign student jobnames. BMM Begin Medium Map: an AFP Record identifier, as seen in 'afpdmp -d' output. Refers to a sub-definition within a Formdef...a COPYGROUP. See: COPYGROUP; Medium Map BorderFree See: Edge-to-edge BR Begin Resource: an AFP Record identifier, as seen in 'afpdmp -d' output. See: Resource Group Breakaway Communications The full-service technology public relations and marketing communications firm which Infoprint Solutions Company has hired to write its announcements material. http://breakawaycom.com BRG Begin Resource Group: an AFP Record identifier, as seen in 'afpdmp -d' output. The set of definitions is delimited by a trailing ERG record. See: Resource Group BSD destination support system In this DSS, IPM acts as little more (BSD DSS) than a queue manager, dispatching jobs to some LPD protocol printer via an AIX command (rembak) which causes the job to be sent to the destination, either directly via a backend program, or through an existing AIX queue (double queuing). No RIPping occurs. The AIX command operands for specs which vary by job are specified via the attribute-map attribute, wherein IPM attributes are specified to be generated on command options via attr:opt pairs, as for example "job-name:-J" for the lpr command, which will generate "-J TheJobName", to be added to the end of the destination-command, to effect operations specified in an IPM manner. The BSD DSS gives you less control of the printer and reports less accurate job status than the other DSSs. In creating a BSD DSS, the actual destination definition elements are: Name (the name to give the printer) Server (the IPM server) SNMP TCP/IP address (the network address of the printer, for monitoring. Omit if not an SNMP printer.) Printer command (which in some way gets the jobstream to the LPD printer). Attr: destination-command Choices, by printer command: rembak ............................... Directly sends the job, to a remote printer: no secondary AIX queueing. Typical static command spec: /usr/lib/lpd/rembak -S -P -N Filter Filter should be /usr/lib/lpd/bsdshort for a non-AIX (e.g., LPRng) system, /usr/lib/lpd/aixshort if the server is another AIX machine. (Using bsdshort allows the job name to appear via the RFC1179 'J' control file line.) Job descriptor values have to be passed via the rembak -o option, which causes LPD control file entries to be generated exactly as they appear after "-o". For feeding an LPRng destination: attribute-map= dest-pass-through:o job-name:-oJ job-owner:-oP (The number of copies is automatic via multiple occurrences of f and N records generated into the resultant control file, by IPM; so no need to play with copy-count. Do not map the owner attribute: IPM automatically creates a P record in the control file.) enq ............................... Sends the job through the local AIX print queue. Typical static command spec: /usr/bin/enq -P Job-specific command options: attribute-map= job-name:-T job-owner:-t copy-count:-N Note that -T fails to result in a J record containing the job name: just get an N record. qprt ............................... Sends the job through the local AIX print queue. Typical static command spec: /usr/bin/qprt -P Job-specific command options: attribute-map= job-name:-T job-owner:-D copy-count:-N lpr ............................... Sends the job through the local AIX print queue. This command is not recommended in that it provides no option for specifying the name of the user for whom the job is to be printed. But its -T *does* result in a proper J record, which other commands don't. Usually, IPM should not produce a header sheet for the job, as the remote printing facility will typically be set up to do that itself. Note that if you don't specify attribute-map values, printing defaults to the IPM server values, as for example username "root" and jobname like "/var/pd/aixsys1/pdprel4p". Whereas rembak stays in communication with the remote system during the job processing, a pages count can be had. Ref: Getting Started manual, Chapter 7, Understanding Destination Support Systems (DSS) See also: attribute-map; rembak; remote-queue; AIX Usage QuickFacts BSD DSS and attributes particulars Job attribute auxiliary-sheet-selection must be null (not "none" or anything else). BSD DSS and MVS printing Files sent from an MVS system to an IPM BSD printer typically fail, because many attributes passed with the data are invalid with BSD DSS. One compensatory way to deal with this is to allow such incompatible jobs to queue in the IPM server, and then have a daemon fix problem jobs that it finds. See my description of the 5010-092 error for details. BSD physical printer In Infoprint, the object representing a printer device that uses the BSD destination support system. C:\Program Files\IBM Windows directory for Infoprint Select \Infoprint Select\Spool\ spooling. Be sure that the permissions on this directory allow writing for all users of the PC whom you want to print via IPS. C:\Program Files\IBM Windows directory containing Infoprint \Infoprint Select\att\ Select attribute (.att) files, where the attributes are Job Attributes as listed in the IPM Reference manual, which is to say that they are attributes for the job as it then exists in the server space. combo A combination of attributes to specify how and when jobs print. location To specify that jobs print at a certain location. piobe Requests that an AIX printer be used, and provides options for such printing. printer To specify that a certain printer model be used. priority To assign jobs a priority. retain How long to retain jobs after they print. Sample files are provided in that directory. Save a revised copy with a .att extention to have such attributes in effect. C0* Character set. In Unix, stored in: /usr/lpp/psf/fontlib /usr/lpp/psf/reslib See ascii-font-map attribute. C02055D0 10cpi C02075D0 10cpi-emphasized C02055P0 10cpi-subscript C02075P0 10cpi-subscript-emphasized C02059A0 10cpi-2wide C02079A0 10cpi-2wide-emphasized C02059L0 10cpi-2wide-2high C02079L0 10cpi-2wide-2high-emphasized C02055J0 10cpi-2wide-subscript C02075J0 10cpi-2wide-subscript-emphasized C02051K0 10cpi-2high C02071K0 10cpi-2high-emphasized C02055F0 10cpi-condensed C02051R0 10cpi-condensed-subscript C02059C0 10cpi-condensed-2wide C02056N0 10cpi-condensed-2wide-subscript C02055E0 12cpi C02075E0 12cpi-emphasized C02054Q0 12cpi-subscript C02074Q0 12cpi-subscript-emphasized C02059B0 12cpi-2wide C02079B0 12cpi-2wide-emphasized C02058M0 12cpi-2wide-subscript C02078M0 12cpi-2wide-subscript-emphasized C02055G0 proportional C02075G0 proportional-emphasized C02055S0 proportional-subscript C02075S0 proportional-subscript-emphasized C02059G0 proportional-2wide C02079G0 proportional-2wide-emphasized C02057S0 proportional-2wide-2high C02077S0 proportional-2wide-2high-emphasized C02051H0 proportional-2wide-subscript C02071H0 proportional-2wide-subscript-emphasized C02055H0 proportional-2high C02075H0 proportional-2high-emphasized Cancel a job, from IPM To "cancel" a job means, from the IPM server, to remove it from the queue, possibly interrupting the job if it was being processed. Removal is via the GUI Delete or Delete & Retain function, or via the 'pdrm' command. If the job was active on an output device, the Cancel will be logged in the /var/psf/ADname/error.log with messages 0424-136 and 0424-138. Observations show that such a cancelled job, on an IPDS printer, results in a 0,0 pages,bytes value in the printer accounting log, but an actual count of pages and sheets thus far in the jobcompletion log. Note: The Reference manual says: "Because of the way that Infoprint Manager pauses and cancels jobs, the totals for the pages completed could be inaccurate." Cancel a job, from printer A job can also be cancelled at the printer, from the printer control panel. For example, on an Infoprint 1145, press Menu to open the Job Menu, which causes Cancel Job to appear on the second line of the display, whereupon you can press the Select button to cause the cancellation. This usually results in a log entry in /var/psf/ADname/error.log, message 0420-257. See also: Cancelled job records Cancelled job records When cancelled via IPM command, will show up in the /var/psf//error.log with two records which look like: 0424-136: Infoprint is processing a cancel job request for jobid 2785710206. 0424-138: Infoprint has cancelled jobid 2785710206 at document page 22 of copy 1. Job Name=Microsoft Word - Satire.doc Job ID=2785710206 Node ID=PUB-SOU0 User ID=someuser When cancelled by pressing the Cancel button on the printer, will show up in the printer log like: 0420-257: The actual destination Cancel key was pressed. Job Name=MyPrintJob Job ID=3797159737 Node ID=_____ User ID=_____ Canon imageRUNNER, driving from IPM This printer lacks PJL capability, so cannot be driven via the pioibmnpm or pioinfo backends for session-oriented job following. The less certain BSD DSS can be used to feed this printer, with destination-command = "/usr/lib/lpd/rembak ...". But: with the BSD DSS, I find it is impossible to employ job attributes plex or sides (get 5010-092 errors) despite the AD having plexes-supported and sides-supported to supposedly allow, such that it's up to the job language (e.g., PostScript) to effect that. Canon imageRUNNER port numbers For model C5870U/C6870U, at least, the known port numbers are: 9100 (raw) Canon imageRUNNER queue names An imageRUNNER with an attached Fiery print manager may accept jobs with queue name "print" or "PRINT". .cdf Filename extension for a Coded Font. .cdp Filename extension for a Code Page. CDPF Composed Document Printing Facility, an IBM mainframe software product to produce the data stream for the IBM 4250 (q.v.) from the raster data generated by host programs such as DCF or GDDM. CE See: Customer Engineer CF Continuous forms printing, as in tractor feed paper. Contrast with cut-sheet printing. Change Requested Destination GUI icon operation to change the Actual Destination for a job. Note that the pop-up windowette allows you to choose an AD - but you can also type in the box... which allows an operator to get into trouble by entering an LD instead of an AD, as the operator confuses this function with Move Job (between LDs); and this causes red icon for the job, for reason required-resources-not-supported. Tip: The job may be destined for one of two printers, e.g., Printer1,Printer2. If you are trying to change that to be just Printer1, you will find that the change operation does not work, as the software falsely tests just the frontage of the to and from values. (A change to Printer2 will work.) This defect is exceedingly inconvenient when you are attempting to perform a mass change. A way around it is to perform the mass change to include a job which is destined for only one of those printers (which you can cause yourself): the GUI will see that the mix is non-uniform and will start with no presumptions about the destinations for the job, so any change you make will work. See also: Move Job CHANNEL PPFA: PRINTLINE subcommand; has the same function as the channel 1 control character in the FCB, causing a page eject if carriage control characters are being used and a channel 1 control character appears in the data. See: PRINTLINE Check Status Element of pop-up menu from a right-click on an Actual Destination, allowing the operator to check the status of the AD (printer, etc.). A windowette will appear, named "Destination Status " showing the State and Enabled values for the AD. Action buttons in the windowette are Close and Help. A More Information button may also appear which, when clicked, will bring up another windowette called the Console Graphic, which on its left will portray the printer with a graphical image, and on the right will present what text is actually on the printer's control panel at the moment. Unlike the basic Check Status info, this info from the printer control panel is real time data, and is implemented with a Java applet on the IPM server, through the server process called "java", configured on the IPM server via properties npm-server-ip-address and npm-server-port-number. Conventionally, the Check Status, More Information function communicates with port 6795 on the IPM server. If that port does not answer, the More Information button is not presented in the Check Status windowette. (Sometimes the process is wedged and needs to be restarted - see pdnpmsrv.) .chs Filename extension for a Character Set. class Initial-value Document attribute for the job class letter. The AD can be set to process one class. CLC Command line client. Clicks (printer billing counter) Vendors have historically charged lessees according to the usage reflected in what used to be a counting, tally meter built into the side of the printer (but values accessible these days via display panels or printer Web page). Each increment of the meter was called a "click", owing to the mechanical noise the early meters made. On the IBM Infoprint 2085/2105 printers the tally is visible from its Web page: Printer Settings: Usage Information reports: Printer uptime Total sheets printed Billing counter The Infoprint 1145 Web page provides a Page Count value. You will probably never find a vendor definition of what constitutes a click. My observations indicate that it reflects every sheet side which passes through the printer's imager, regardless... When printing simplex, the clicks value equals the number of pages in the document. When printing duplex, the clicks value equals the number of sheets times 2 - even if the number of pages in the document is odd, such that the backside of the last sheet is empty. Thus, from the IPM server you can compute a number which approximates the clicks value, by adding the number of simplex pages + (duplex sheets * 2). Your computed number will likely be somewhat less than the printer clicks number. Why? Most likely, paper jams. A jam may well occur somewhere after the imager station, and the destroyed sheet(s) will have to be re-done. This is extra work for the printer, and contributes to its wear, as reflected in the clicks count; but the printer will report to the server only successfully completed pages and sheets, a value which does not reflect the paper lost in the jam. This begs the question as to exactly when a click occurs in the printing path. My empirical evidence thus far suggests imager. Note that all IBM printers ship with their counters set to a high number (typically, 0 - 1000), which allows 1000 clicks for an introductory period in which testing and debugging can occur without charging the customer. The counter then wraps to 0 and "real" counting begins. See also: Infoprint 2105 Billing Pages count client-driver-names Names the 32-bit Windows client print drivers that can submit a data stream to the logical destination. Possible names are found via the Windows Add Printer icon: the values listed in the "Printer: list" box are the names of the Windows destination drivers that you can install on the workstation; for example, IBM 4039 LaserPrinter PS. Begin and end the string with single quotation marks. For submitting jobs from the Windows client to a PSF actual destination, select a generic destination driver, such as a PostScript driver, instead of one for a specific type of destination. Otherwise, the driver may generate device-specific data streams that IPM cannot transform correctly. The specified names effectively restrict the use of this logical destination. Ref: Getting Started manual, "Creating Infoprint Select printers" See also: Infoprint Select Clock, show 12-hour or 24-hour Controlled under GUI Customize, General. "close to discard time" In the Retained Jobs area of the GUI, a job's icon will be yellow when the discard time is less than one hour, and its Status will show "close to discard time". Note that an icon can have only one color. The "close to discard time" yellow icon condition overrides a "canceled by operator" black icon condition, so be aware of this when looking at jobs to see if they failed. clrfstns Command clears all dynamic information from the Infoprint Manager namespace, where you have set up a multiple-servers namespace. The command should only be invoked when all servers in the namespace are shut down. CMT Color Mapping Table Config: /usr/lpp/psf/config/cmt.cfg Colon Files AIX printer definition files, used with the following Infoprinters: 1120, 1125, 1130, 1140, 1145 (at least); and with HP LaserJet printers. In: /usr/lib/lpd/pio/predef/ These colon files are referenced when you create either an AIX DSS printer or a PSF other-driver DSS printer through IPM and when you specify particular trays from which to pull paper using IPM attributes. Colon files are available in IBM filesets such as "printers.hplj-4000.rte". You may download such files for IBM Infoprint printers by doing: Go to www.printers.ibm.com; Under Support, click Downloads & Drivers; Select your printer type; Scan the pages thereunder until you come upon an entry like "Infoprint 11XX and Color 122X Colon Files v4.6.1 for AIX" Alternately, you can search www.ibm.com for "colon files" - which you will have to do for non-IBM printers (HP et al). The HP colon files are indirectly referenced through the model type specified in IPM, as in: destination-model = hplj-4000 which implictly refers to files hplj-4000.gl hplj-4000.pcl in /usr/lib/lpd/pio/predef/. IPM for Linux does not have colon files: instead, it has PPD files. Color vs. grayscale job arrival As the IPM administrator, you may notice that PostScript print jobs destined for a grayscale printer are nevertheless arriving in color - which is pointless. What gives? The printer driver (e.g., IBM Infoprint 2105 PS) says that its destination printer is not a color printer, so one should expect the job to have its images made grayscale as part of job submission processing. What I've found in Windows printing of Web pages and documents is that there is a processing option controlling this: On a per job basis: - In the print dialog, click Properties. - In the Document Properties dialog window, click Advanced. - In the Advanced Options window, under "PostScript Options", there is "PostScript Output Option", where the choices are: Optimize for Speed (the default) Choosing this results in the job arriving with its colors. Optimize for Portability Choosing this results in the job arriving with its colors. Globally, for all job submissions: - In "Printers and Faxes", right-click on the Infoprint Select printer and choose Printing Preferences. - In the Printing Preferences dialog, click Advanced, then do as above. The "Optimize for Speed", grayscale version is signicantly faster in rasterization, and this version is a much smaller file than the "Optimize for Portability" version. However, in PDF printing, the above does *not* result in color PDFs arriving grayscale. Indeed, in PDF printing the print dialog is rather different, having a Preview area to the right, center. Columns, change order The GUI section (such as Jobs) may not have the columns in the order you would like. To change: Options -> Add/Remove Menu Items -> (select tab of interest); in "Details to show" list, click on a column to be relocated and move it using the Order up/down arrows. Command GUI field in AD PSF Command Printer Properties. Attribute: destination-command Comments PPFA: Programmer comments used to document PPFA command streams are allowed anywhere within the command stream. Comments must be enclosed with the delimiters /* and */. A comment is allowed anywhere a blank is allowed and can continue for any number of lines. Committing jobs to a printer See: Maximum concurrent jobs Common Clients CD contents See RESOURCES, near bottom of document. completed with errors See: job-state-reasons completed-with-errors See: job-state-reasons To list jobs having this condition, you can do like: pdls -c job -x'filter="job-state-reasons=completed-with-errors"' -U -r submission-time,job-owner Hostname: where the -r spec may be omitted for a simple table, or expanded for more lines of info per job. completion-time Job attribute: Identifies the time when the job completed printing or transmitting. Observed realities: For ordinary processing, this attribute simply records when the job finished printing. For rip-and-hold processing, this attribute is initially set to record when the job finished transforming, to create its AFP file: thereafter the job will likely be released to print, whereafter this attribute will be updated again to reflect when the job finished printing. After printing, this value never changes, whether the job is reprinted (move job) or if the job is resubmitted to another server. GUI label: Creation time DSS: All IPM sets the value for this attribute in the local time format; USA is "HH:MM:SS mm/dd/yy". See also: creation-time; started-printing-time; submission-time Concatenating AFP data The -c option of the PCL and PostScript transform commands allow combining multiple source data files of those types, to produce an AFP output. For concatenating pre-existing AFP data: there is the undocumented afpconcat command (q.v.). Simple, physical concatenation of AFP files will work to product a printable whole, but will be problematic if, in duplex, you don't account for the possible requirement of each contributing document needing to be front-facing, rather than possibly starting on the backside of the prior document. You can reportedly deal with this challenge by running ACIF (line2afp) on the concatenated set with the option INDEXOBJ=BDTLY: as long as your document files are complete AFP documents, ie., are enclosed with BDT/EDT, you should get the first page of each document starting (at least) on a front side. But if you intend no break between document files, don't use the BDTLY option: ACIF will then remove the BDT/EDT pairs and treat the output as a single document file. See also: ACIF Concurrency See: Maximum concurrent jobs CONDITION PPFA Traditional processing conditional processing command in a Pagedef. The CONDITION command is used to invoke conditional processing based only on the data in the current line: it is not conditional upon page position or any other factor. Conditional processing acts as a preprocessor by allowing you to test the input data before deciding which copy group and page format to use. Placement: Appears after a PRINTLINE. One or more CONDITION commands may be coded after a PRINTLINE. A condition is checked if its associated PRINTLINE command is actually processed. BEFORE causes the processing position to change before the data clump (LINE or SUBPAGE) is processed, thus allowing the data clump to be processed by the destination page format. That is, BEFORE LINE causes that line's data to be processed by the destination page format; BEFORE SUBPAGE causes all lines thus far appearing in the subpage to be processed by the destination page format, discarding any page writing done thus far by all PRINTLINEs appearing before the SUBPAGE condition took effect. This makes the purpose of the ENDSUBPAGE command clear: it serves to limit the amount of reprocessing that can be done. Because of all this, avoid having BEFORE SUBPAGE appear in an OTHERWISE clause. BEFORE SUBPAGE is particularly useful in the handling of a Form Feed as a "skip to next page" in unformatted ASCII processing. While it looks like an independent command, the CONDITION modifies the PRINTLINE just as a FIELD command following a PRINTLINE modifies it. The CONDITION may specify a PAGEFORMAT that is a forward reference. When the REPEAT and CONDITION commands are both specified for the same PRINTLINE command, every line described by the PRINTLINE command is checked for the given condition until either the condition is satisfied or there are no more lines described by the PRINTLINE command. WHEN CHANGE is always false at start of a page format. AFTER LINE: The conditional action takes place after the current line is processed. Note: Any Copy Group action (except NULL) restarts the current page format. See also: SUBPAGE CONDITION and ASCII vs. EBCDIC AFP is inherently an EBCDIC facility. The text you code in a CONDITION command for "WHEN EQ 'Some text'" is generated into the Pagedef as EBCDIC. This is insidious in an AIX environment, where you naively code some text in the CONDITION and then operate on an ASCII data stream - and find your conditional processing not working for no apparent reason. Your condition test fails because the EBCDIC in the Pagedef cannot match the ASCII in the data. PPFA is deficient in providing no means for directly specifying ASCII (like A'Some text'): the most you can do is code it in hexadecimal (X'....'), which is an obviousness/maintainability issue. conditional-terminating-return-code Transform property, to define a numerical value which, returned by your transform, will indicate that the transform was successful, but that the transform will not be returning data for further processing by IPM. IPM then regards this as if the transform had been defined to be a terminating transform which returned a successful return code, so IPM should conclude processing of the job, not sending any data to the output device. This arrangement works the same way as a terminating transform, where the arriving job is transformed and then moves to the Retained Jobs area (rather than being kept in the input queue). Indeed, the server error.log gets "5010-507 Job completed due to terminating transform." GUI label: Conditional terminating return code The compelling reason for such a separate return code is to allow the transform to return 0 to, as usual, allow the current job to go on to print, but have a separate return code for jobs which should only transform and not print. Default: None. This property is always defined for a transform, but normally has a null value, until you define one. See also: terminating-transform; Transform Confidential jobs A facility with some printers (Infoprint 1145) so that the job cannot print until you are at the printer to assure that no one else can see the output. Job submission includes a PIN; after submission, you go to the printer and enter the PIN to cause the job to print. Configuration models See: Desktop destination configuration model; Funnel destination configuration model; Hourglass destination configuration model; Pool destination configuration model Connection timeout GUI field, AD properties, Tuning tab. Attr: connection-timeout (q.v.) connection-timeout AD attribute: For TCP/IP-attached actual destinations: how long IPM waits for its first response before it stops trying to communicate with the actual destination. GUI label: Connection timeout If the connection times out without you being able to connect to the printer, manual intervention will be required to cause IPM to attempt to reconnect to the printer. (The printer icon will show red in the GUI.) This value must be long enough to give the printer time to warm up. Not used for connection types other than TCP/IP. Default: 30 (seconds) Possible: 0 - 9999 (seconds) See also: destination-release-timer; destination-timeout-period; job-retry-count-limit; job-retry-interval; Release time Console Graphic See: Check Status Copies The number of copies to be printed may be specified in command 'lpr -#N'. How does that get through to Infoprint Manager? That number of copies value is not readily available in its own attribute, as you would rightly expect it to be: instead, it ends up in the third field of the results-profile (q.v.) attribute, where the copies value there is tested by the AD attribute maximum-copies-supported. And be aware that this is only an external attribute which the submitter may or may not utilize to achieve multiple copies: if multiple copies are specified internal to the job - as in the case of the PostScript NumCopies spec - you will have no external indication of the number of copies. Copies, performance See: Optimize for copies Copies completed GUI: Job Properties, Job Progress tab Copies limit maximum-copies-supported attribute (q.v.). GUI: Actual destination, Properties, Document tab Copy Group See: COPYGROUP copy-count Attribute for the number of copies that a job will produce. This value is misleading for a Transform in that it will say '1' though a job is printing 2 copies. Instead, look at the results-profile copies element. GUI: Logical destination Job and Document Defaults, Document Other tab. The value is validated against the AD attribute maximum-copies-supported: if exceeds, the job fails with Resources Not Supported. COPYGROUP PPFA command within a Formdef, defining a subset of the Formdef. In a simple Formdef, a COPYGROUP is not needed. The first copy group within a form definition is always active when processing of a print file begins, and remains in effect unless a different copy group is selected, as via the CONDITION command in a Pagedef. AKA: Medium Map, as in an AFP Invoke Data Map (IDM) command. Note that the Copy Group name is translated into upper case in generating the binary version. If a parameter other than NULL or / is specified for COPYGROUP, the copy group restarts every time a page change occurs. Restarting a copy group forces data to a new sheet, precluding duplex printing. Msgs: 0420-509 See also: Copy Group core files to watch for IPM may produce core (dump) files in various directories. The administrator needs to watch out for and appropriately handle such files - which among other things can fill a file system... /var/psf//core Corner Staple Angle IPDS setting in an IPDS printer such as the Infoprint 2105. Lets you select [Vertical] or [Slant] for the angle of stapling. This operates in conjunction with the FINISH definition in the AFP Formdef's "OPERATION CORNER" & "REFERENCE TOPLEFT" specification, where they specify the location for the staple, but not the angle. Note that CEs dislike a setting of Slant because it causes the stapler mechanism to have to rotate 45 degrees, thus putting more strain on the mechanics. CPDS Composed Page Data Stream The original name of AFPDS. .cpp Extension seen in some messages, as with "statcode.cpp". Refers to a C++ programming language source module. creation-time Job attribute: Identifies the time when the job was created in the IPM queue, which is when the job was received by IPM. This value never changes, whether the job is reprinted (move job) or if the job is resubmitted to another server. GUI label: Creation time DSS: All IPM sets the value for this attribute in the local time format; USA is "HH:MM:SS mm/dd/yy". creation-time will equal submission-time when the job arrives; but submission-time can change if the job is reprinted. See also: completion-time; started-printing-time; submission-time CTX Composed-Text Job Information Data as appears in User Exit. CUPS See: IPP CUPS DSS This is the DSS for the Linux IPM to use the native printers in that environment, much as the AIX IPM has the AIX DSS. Jobs are submitted to InfoPrint Manager (not CUPS) and IPM makes use of CUPS backend programs to convey the jobs to the printer as-is, no transformation involved on the IPM server. The job's PDL should be one that the printer supports (PostScript, PDF, PCL) because the printer will be performing raster image transformation. Another way of saying this is that the CUPS DSS can drive any printer a CUPS printer can drive. CUPS software needs to be installed on the IPM server - and it must be running (because IPM submits PostScript jobs through CUPS). When printer "XYZ" is defined in IPM, it will also be defined in /etc/cups/printers.conf, as name "IPM_XYZ". Printer model definitions must match PPDs which you install into /usr/share/cups/model/. (You can obtain PPD files from site www.openprinting.org/printer .) After you plant such a PPD file, you can go into the admin GUI, select Printer > Create > CUPS, and in the Model field type in the name of the PPD, e.g.: HP-LaserJet_4350-Postscript.ppd In the future, when you define a next such printer, the PPD file name will be in the Model drop-down list, where you can select it rather than type it. The PPD will also show up in server attribute dynamic-destination-models, which is a non-settable field which collects names that you entered in printer definitions. The principal CUPS backend driver module is pioinfo, which supports accurate job completion and job accounting, so set wait-for-job-completion = true. The CUPS DSS destination command for the InfoPrint Manager enhanced backends is of the form: pioinfo://ip-address[:port-number] The default port number is 9100, which is the standard job submission port on most PostScript printers. The IPM doc says "You do not need to create Linux CUPS printers for InfoPrint Manager to drive your printer with an CUPS DSS." This leads you to believe that IPM PostScript printers are not defined in CUPS. In fact, they are: all PostScript printing is actually done by CUPS, running on the IPM print server system. When you define a CUPS DSS printer in IPM, IPM interfaces with CUPS to define the printer in CUPS as well, where it will have the name: IPM_ The doc also says: "For InfoPrint Manager to drive your printer with a CUPS DSS, you need to install all the necessary software (filters and driver files) that the CUPS print spooling system would need to drive your printer." This is woefully insufficient information. If you download PPD files from the Linux standard openprinting.org site, you will find that many of them depend upon the CUPS standard foomatic-rip being in place, which would be installed via the RPM package called "foomatic". See also: pioinfo; PPDs CUPS filter needs The CUPS filter needed for a particular printer is defined in its PPD, like in the PPD line: *cupsFilter: "application/vnd.cups-postscript 0 hpps" Current and pending jobs In /var/pd//pdb/suv_job/ (q.v.). current-job-state Job atribute: Identifies the current state of the job, such as "held". A read-only attribute (not modifiable). GUI label: State See also: job-state-reasons; previous-job-state current-page-printing Job attribute, like it says. Note that IPM only sporadically updates the value that is reported: printing is often in advance of the number seen. See also: ack-interval; pages-completed Customer Engineer (CE) The service technician who comes to repair your printer, per your service contract. What to expect of a CE: CEs are guys who understand the ins and outs of electrical and mechanical systems, and who should be able to diagnose and repair electromechanical problems, sometimes in conjunction with their support center. But don't expect anything beyond that. CEs typically know nothing about printer settings: what they are for, and what they do. For example, a CE may reset a printer and then go to the customer, saying that they can't reach its Web page - when they haven't reinstated the printer's network address. If you have any throughput problems with the printer, as related to (TCP/IP) networking issues, the CE will know absolutely nothing about communication protocols or what to look at. Yet, when you do have such a problem and make an issue of it with the support organization, they will inevitably assign the CE to pursue it, resulting in a complete waste of time. Printer support under Infoprint Solutions Company just isn't the same as it was under IBM. Under IBM, a problem was doggedly pursued until it was resolved. Under ISC, they don't want a CE tied up with a problem for an overly long time, and will actually instruct him to give up on it. d Units abbreviation for a Dot. See: PEL Daemon Generic term for a program which runs unattended to perform a standard service, which in Unix means "started as a background process". Some daemons are triggered automatically to perform their tasks; others operate periodically. Daemon processes are persistent, staying around indefinitely, to listen on ports or otherwise remain instantly available to perform work. This is in contrast to transient programs, started as needed, which entail overhead to initiate and which retain no ongoing knowledge of prevailing conditions. daemon A specific account in a Unix system, defined in the /etc/passwd file, conventionally having UID 1 and group number 1 (which is typically "staff"). In IPM on AIX, the transform processes (pcl2afpd, ps2afpd, ps2afpi, etc.) run as user "daemon", rather than "root" - and thus the /var/psf/ps2afp/* and like files must be owned by "daemon" so that the transforms programs (running as daemons) can read and write to them (particulary the Pipe files). Daemons Transforms are performed by service daemons, which are always present as system processes. See: pcl2afpd; ps2afpd Data Map PSF term equivalent to Page Format... A subdivision of the Pagedef, akin to the ways a Formdef may have Copy Group subdivisions. See also: Invoke Data Map Database IPM does not have a database, per se. Instead, it has conventional file system directories and files which house OIDs to track the attributes of all the elements of the server. Daylight Savings Time discrepancy After a Daylight Savings Time transition, you may see the jobcompletion log showing correct times, but the accounting logs have a time which is an hour off. The Procedures manual contains a note saying: "Following Daylight Savings Time changes, some customers have reported discrepancies in their server accounting logs and others have reported job submission failures. The problem was resolved by stopping and starting the Infoprint Manager server. If you are already experiencing these symptoms or want to avoid them in the future, arrange to have your servers restarted immediately following a Daylight Savings Time change." Some programming. This is still not fixed, even as of IPM 4.4! DCF Document Composition Facility, an IBM software product. DCS ??? Deadline Job submitted via Infoprint means may have a job-deadline-time attribute value, which the AD scheduler may be set to honor. Default printer, in server defs Hearsay suggested that there is a "default printer" in the server configuration, ostensibly put there by the install. However, this is false: a search of the manuals shows no such "default printer". default_document_name The job name found on some jobs entering IPM. These tend to be jobs sent from Mac OS X via IPP, where the CUPS on the Mac is found (in packet tracing) to not be sending the job name as an IPP job attribute. default-input-tray AD attribute specifying the name of the default input tray for a PSF actual destination (and no other DSSes). - The value must be one in the input-trays-supported or psf-tray-characteristics AD attrs. - The value is used only if the job does does not specify a medium or input tray, nor does the formdef. DSS: PSF (only) GUI label: Default input tray Example: default-input-tray = tray-2 See also: input-trays-medium default-input-tray Document attribute identifying an input tray on the printer device that contains the medium that IPM should use for normal document pages. IPM validates and schedules jobs using this attribute against the destination attribute input-trays-supported. DSS: AIX, PSF, Infoprint 2000 GUI label: Input tray requested For AIX DSS, use one of: auto-envelope-feed automatic-tray auxiliary-envelope auxiliary-paper bottom continuous-form-feed current-selected-tray envelope high-capacity-feeder large-capacity manual manual-envelope-feed middletop tray-1 tray-2 tray-3 tray-4 tray-5 tray-6 tray-7 tray-8 tray-9 tray-10 capacity-2000-sheet default-medium Job/Document Defaults attribute. Identifies the medium for document pages on which this document prints. GUI label: Medium requested This attribute is compared to the AD media-ready attribute to validate the job for scheduling. If the job is inconsistent with the printer (as in specifying Ledger paper when Letter is loaded in the printer), the job loses: it will be red-ikon'ed. (The media-ready values are typically obtained by IPM by querying the printer, where possible.) See also: media-ready; psf-tray-characteristics default-printer-resolution Initial-value Document attribute: Specifies the resolution, in pels, at which the printer device should print this document. GUI Label: Printer resolution requested DSSes: PSF, Infoprint 2000 (not AIX, BSD, Email, or others) Attempting to send a job having this attribute to an AIX DSS will cause the job to fail on a "resources not supported" condition. The best course for an AIX DSS where you want a certain resolution is to specify that as the first or only value in the AD attribute printer-resolutions-ready. Note: This attribute will not appear to the Transforms if the LD's Job and Document Defaults, Document Print Quality tab, "Printer resolution requested" = "Use default". Notes: In my experience, specifying a value for this option works fine for IPDS printers, but if used for HP printing, will cause the job to sit in the queue, white iconed, and not processing. For HP printing, leave this attribute undefined (default) and let the AD's print-qualities-supported single value govern the resolution. In AIX and BSD DSS printing, dpi resolution can be effected via the print-qualities-supported AD attribute. In AIX DSS printing, dpi resolution can alternately be effected on the pioibmnpm back end command via the "-q 600" command line option. See also: pioibmnpm Definition resources There are five definition resources which are involved in AFP/PSF printing: F1 Formdef P1 Pagedef S1 Page segment (like a logo or signature) O1 Overlay Fonts (/usr/lpp/psf/fontlib) (/usr/lpp/psf/reslib) C0: character set T1: code page X0: GT10 (which C0, T1) See also: F1; P1; S1; O1 Delete GUI selection, for removing a job entirely. Results in error.log messages: 5010-348 Starting the cancel job request 5010-349 The cancel request for the job ____ is complete. Delete And Retain GUI selection, for removing a job from pending status to move it to the Retained Jobs area, in hold state. See also: Job, delete and retain Delete in Retained Jobs column reporting in how many hours and minutes the jobs will be deleted from the retention area. If the values are oddly negative, like "-23 hours -6 minutes", it indicates that the date&time are mis-set in the system in which you are running the GUI. Delete job, effects When the operator deletes a queued job (as in the case of "rip failed" hopeless jobs), IPM will print an indication for the user, containing: 0420-094: The following messages were generated for file ____ with Job ID ____. This file printed on the Infoprint actual destination ____, which is a ____ actual destination. 0424-138: Infoprint has cancelled jobid ____ at document page 1 of copy 0. Description See: descriptor; job-comment descriptor Textual description for an AD. GUI label: Description Desktop destination configuration Simplistic printing, which models a model number of PCs, each having its own printer. Ref: Into & Planning manual, chapter Planning for configuration See also: Configuration models Destination Column in the GUI's Jobs area, showing the AD to which the job is bound when its turn comes. Note that this does not reflect an AD to which the job may have been assigned by the operator, for job isolation (which is attr actual-destinations-requested), and there is no GUI choice for showing that assigned value - which can make it a mystery as to why a job is not printing. Destination, disable 'pddisable :' Destination, enable 'pdenable :' Destination, nullify attribute 'pddisable :' 'pdset -c destination -x '==' :' 'pdenable :' Destination names In /var/pddir/default_cell/printers/ which contains AD and LD names, and .acl files where security settings have been applied to ADs. destination-command AD attribute specifying the command fundamental which IPM flesh out and use to print the job data. A single command must be specified: a Unix construct like "command1; command2" will not work. GUI: AD Printer Properties, General tab, Command field. For BSD Printer, attribute-map specs may be employed. For PSF Command Printer, no variables or attribute-map specs may be employed, which can result in the file printing on a non-PSF printer under username "root" instead of the job sender, though the job header page and IPM accounting will reflect the proper username. For a PSF Command AD, typically is: 'enq -P -dp -' For an AIX DSS, the command must be "real", in that the act of committing the definition causes IPM to evaluate the command for recognizability. (IPM does not attempt to use the command to evaluate whether it is able to speak PJL with the destination printer.) If you do 'ps' during the printing, you will see that IPM takes that command spec and in invoking it adds further operands to the end. For example, you specify: /usr/lib/lpd/pio/etc/pioibmnpm ourprinter.ourplace.com 9100 IPM runs: ksh /usr/lib/lpd/pio/etc/pioibmnpm ourprinter.ourplace.com 9100 -ustat -j1 /var/pd//pdpr1stSkf which points out why what you specify must be a single command. destination-data-stream Attribute identifying the data stream format that is output to the printer device. GUI Label: Data Stream DSS: PSF Type: Initially settable, single-valued Allowed Values: pcl4 pcl5 pcl5c pcl6 ppds ipds (not for PSF Command, Other) destination-initial-value-job Logical Destination attribute, defining the identity of the "Default job" attributes set. The set supplies values for attributes of jobs submitted to a logical destination. These values override server defaults but are overridden by job attribute values specified on the command line. If you define a Logical Destination via the GUI, the "Default job" attributes collection is given the name -dj. The Default Job attributes files live in /var/pd//pdb/iv_job/. destination-model Actual Destination attribute, for AIX or PSF: Identifies the make and model number defined by the manufacturer of the output device. This value is requested in the Model field of the GUI dialog box when defining a new printer. You can enter a text string up to 4095 characters that contains the make and model number of the output device; or you can choose to have it automatically determined via SNMP per below. Whether via SNMP or direct specification, for an AIX AD or a PSF other-driver attached AD, it must be one of the values of the server snmp-aix-printer-models attribute or must match the file prefix of a file in the /usr/lib/lpd/pio/predef directory on the AIX processor on which the AD was created, unless the destination-model is an Infoprint model such that the external name (for example, an Infoprint 20) is mapped to the predefined name for you. Example: When defining the printer in the GUI, in the Model field you enter "generic", which utilizes the "generic.*" files in the predef directory. See also: snmp-aix-printer-models destination-name AD attribute: Names the AD. Maximum name length: For AIX, CUPS, FAX, EMAIL DSS: 256 chars (as of IPM 4.4 - FAX and EMAIL used to be limited to 8) For PSF/IPDS: 64 chars as of IPM 4.4 (used to be limited to 8 chars) destination-name-requested Job attribute: Identifies the logical destination to which the job was submitted. A read-only attribute (not modifiable). Can be changed via pdresubmit. GUI label: Submitted to Length: Up to 255 chars Synonyms: printer-name-requested, printer-requested, logical-printer-requested. See also: actual-destinations-requested destination-needs-attention-time AD attribute value, recording the amount of time (Hours:minutes) that the output device has been waiting for simple intervention, such as loading paper or clearing a paper jam, when the destination-state = needs-attention. This is reference information for the IPM administrator to view. GUI label: Attention needed Destination Pass Through destination-pass-through AD attribute: Allows you to pass information to the DSS (destination driver). Infoprint does not process the information, but passes it directly to the DSS. With the AIX DSS, the information is used to update the AD's colon file. destination-pass-through LD attribute: Allows you to pass information to the DSS (destination driver). Infoprint does not process the information, but passes it directly to the DSS, and the text is presents to the transform sequence program via the %p command line option (other-transform-options). GUI label: Other options, on the Document Other tab With the AIX DSS, the information is used to update the AD's colon file. For BSD, Infoprint appends the contents of this attribute to the contents of the actual destination attribute destination-command after the mapped options. destination-pass-through Document attribute: Allows you to submit specific DSS (print driver) information along with the document. Infoprint does not process the information, but passes it directly to the DSS. GUI label: Other options DSS: AIX, BSD, PSF, Infoprint 2000 Type: Resettable, single-valued, per-job Allowed values: You can enter a text string of up to 255 characters that contains the DSS information. Default value: none Usage guidelines: - For BSD, Infoprint appends the contents of this attribute to the contents of the AD attribute destination-command after the mapped options. - When sent to an AD with a transform sequence, the information you provide with the destination-pass-through attribute is always passed to the DSS, and this information should not be used to pass transform-unique data (that is, data that the DSS does not understand) to the transform sequence. Sample value: "-H(landscape)" Normally seen value: -fl Notes: The Windows 'lpr' command has a "-C " parameter which, when used, caused a "-H" to appear in this attribute (in addition to "-fl", which is always there). destination-realization Attribute used in a 'pdcreate' to specify the type of destination that is being created: actual An AD logical An LD destination-register-threshold AD attribute: Specifies the amount of time that this actual destination will wait between attempts to communicate (register) with the server. Applies when the actual destination and the queue are in separate Infoprint servers. If the Infoprint server containing the queue is not running, the printer in the running server keeps trying to establish contact with the server that contains the queue. This attempt is made every n minutes. Value is [HH:]MM destination-release-timer AD attribute: Specifies the maximum amount of time between jobs, in seconds, before IPM gives up control of a PSF actual destination after the last contiguous job completes: printer reuse delay. Used to allow the sharing of IPDS printers, as when you have had a printer purely controlled via PSF TCP/IP and then want to add PSF Command for the same printer. A shutdown of the printer is then necessary to release it. The value must allow time for all processes to stop running gracefully as IPM gives up control of the attached PSF actual destination. That is, in sharing, you want quick release, but still allow time for graceful transition. It is recommended that the non-process-runout-timer value be set to a lower value than destination-release-timer. GUI Label: Release time (sec) under the Tuning tab. Allowed Values: 0 - 9999 Default: 9999 Specify 9999 if the device is not shared. Note that a long time value causes the printer to stay in "Printing IPDS" state for the duration. For printers such as the Infoprint 2090/2105 series, their green "printing" light thus stays on, which is quite undesirable, as operators refer to the light at a distance to know whether or not the printer is printing something, and this would be misleading. Note that releasing the printer causes loaded resources to be lost, meaning they will have to be reloaded when the releaser regains control of the printer, which is added overhead. Advice: Leave the value 9999 is ideal in terms of functionality, but will confuse people in making the printer look perpetually busy, when it's simply unreleased. A value of 30 tends to make sense: long enough for holding on to resources between job submissions which are close in time, but short enough to let go when there's no activity within a reasonable period. See also: ainhyper; Connection timeout; Printer sharing; Release time (sec) destination-state AD attribute reflecting the state of the destination. GUI: Printers section, Status tab, State field. Possible values: idle needs attention (needs-attention) Cannot connect to the output device in order to ascertain status, most commonly because the printer is turned off, or because its job submission functions are awry. IPM does not disable the AD, hoping to see it become functional in further connection attempts. The printer icon is set red. needs key operator (needs-key-operator) Can connect to the output device so as to obtain its status, which reveals that there is a serious problem with the device, such as out of toner or paper, or all feed trays are pulled out. IPM automatically disables the AD when the AD enters this state. If the AD uses SNMP, IPM automatically re-enables it when the problem is corrected. To prevent automatic re-enabling, manually disable the AD. The printer icon is set red. Error log msg: 5010-850 paused The AD was paused with the pdpause command or by a job with job-start-wait=true. printing It's outputting a job. ready shutdown The PSF AD was shut down with the 'pdshutdown' command. timed out The AD received a job, but the AD could not connect to the output device in the time specified by the printer-timeout-period AD attribute. Msg: 5010-247 See also: printer-timed-out Each of the above conditions is explored under its own topic entry. error.log msgs: 5010-371 Destination state change error.log msg: 5010-228 destination-tcpip-internet-address AD attribute specifying the dotted IP address or network name of a printer. As used for IPDS printers. (In PostScript printing, the port number is instead supplied as part of the destination-command string.) (It may be better to use the IP address rather than the network name, to eliminate the overhead of DNS lookups and susceptibility of unfathomable IPM delays when DNS service is sluggish. GUI: Configuration tab, field name "TCP/IP address". Example of setting, via command: pddisable printer1 pdset -c destination -x 'destination-tcpip-internet-address= 111.222.333.456' printer1 pdenable printer1 destination-tcpip-port-number PSF AD attribute specifying the port number to use within the addresses Internet destination. For larger Infoprint printers, the port number is usually 5001. For smaller Infoprint printers, the port number is usually 9100. Not used for HP (PostScript) printers. GUI: Configuration tab, field name "TCP/IP port". destination-timeout-period AD attribute specifying the amount of time, in seconds, that IPM allows for the server to try to connect to a shared network printer (printer device) after the AD receives a new job request. GUI: Tuning tab, "Timeout period (sec)" DSS: AIX, PSF Type: Resettable, single-valued Aka: printer-timeout-period Msgs: 5010-247 This timeout is not involved in job timeout management of PJL type printing to PostScript printers, utilizing the pioibmnpm or pioinfo backends. destinations-used The ADs used in printing the job. Normally, only one AD name will appear. But if the job got stuck on one AD, and that AD was shut down, and the job shifted over to another AD to finally get processed, then multiple AD names will appear. Msg: 5010-247 Device driver for Windows See: Infoprint Select device_controls A possible entry in the pcl2afpd.cfg and ps2afpd.cfg configuration files, to define defaults allowing document processing to reference Medium Map names to effect plex (simplex/duplex), paper tray selection, stacker offsetting, etc. There are usually sample lines in these configuration files, commented out, which the customer may tailor and activate as needed. The intention of this arrangement is to provide certain controls where the customer is allowing IPM's basic transforms to operate on submitted jobs, rather than where the customer codes a transform program and writes their own Formdefs. In basic transformation, the ps2afp and similar transforms will insert IMMs to reference the right inline Formdef Copygroup to achieve AFP duplexing according to the PostScript instructions in the .ps file, for example. Activating device_controls results in the transform generating an inline Resource Group named INLINERS ahead of the AFP for the document itself, defining the Formdef and Medium Map elements which the Pagedefs created by the transform may reference. The generated inline Resource Group may be overridden by Formdefs which the job itself carries or the Job/Document Defaults settings assign when the job is accepted in IPM. Uncomment the "device_controls = plex" line to allow the PostScript file to govern single-sided and double-sided (duplexed) output, per its native conventions, as the ps2afp transform maps to IMM commands which reference Medium Maps in the inline Resource Group. If you omit plex, the ps2afp transform creates duplex output. If you omit bin numbers, the ps2afp transform creates output that indicates that the first input tray should be used (first - tray linking within the printer will result in the use of other trays if preceding trays are empty). device_controls corresponds to the ps2afp transform command line option "-device". The upshot of device_controls is that you need employ them only if you depend upon IPM's implicit transform regimen to convert PostScript or other encoded files to AFP. The device_controls spec has no interaction with the paper size which may be specified in the PostScript: in AFP processing, the ps2afp command has its -l and -w options to define the size of the resulting AFP page (not detect it). You would have to parse the PostScript to discern its page size. See also: F100APS; Form Definition used; pcl2afpd; ps2afpd.cfg deviceControls See: ps2afp.cfg; ps2afpd.cfg DFE Digital Front End. In the original PostScript days, jobs were simply sent to printers and all the processing was effected inside the printers. While a form of distributed processing, it was primitive, inefficient, and provided no feedback to the initiating location. The needs of job management, sophisticated RIP, and output distribution made for a shift of workload to the host computer system (where, ironically, it began in the days of line printers). Infoprint Manager is one example of a DFE, where parallel RIPping can be performed, the transform can be saved in device-independent form, and be sent to a printer, mail, HTML for web page, etc. Host-resident processing allows for scaling, taking advantage of computer technology speed and N-way processors to better feed prevailing print engines. DIB Device Independent Bitmap file format. Device Independent means that colors are represented that is independent of the final output device. When a DIB image is seen on-screen or printed, the device's driver translates the colors into colors that that device can display. The snfrmain program, given a .bmp file, reports it to be "DIB." (though IPM is not programmed to work such a format). Digital Master Adobe's term for a PDF file, as used in Adobe PostScript Extreme because of its ability to fully incorporate both job data and ticket info. A PDF document and its associated Job Ticket contain essentially all the information (content, graphics, production specs, etc.) required for viewing, processing, and outputting a file in a self-contained package. Because a PDF document contains this key information, it can be thought of as a Digital Master, a complete and reliable description of a file s content and processing requirements. DIN 19309 (aka DIN 19 309) International standard for paper quality. Defines the quality of "paper for copying purposes". This standard considers both normal and recycled paper, and is concerned with paper characteristics such as roughness, relative humidity, opacity, runability, ink durability, rounding etc. Types of paper that correspond to this standard can be used unhesitatingly for copying and printing purposes. The quality of recycled paper is usually the dominant issue. For example, the Infoprint 1585 User's Reference Guide manual specifies one case of unacceptable paper as "Recycled papers containing more than 25% post-consumer waste that do not meet DIN 19 309". Arrow on ream pack: One printer manufacturer advises: "If the paper you use for printing does not have an arrow on the wrapping, it has not been manufactured according to DIN 19309 standard, which requires this arrow to indicate the side of the paper to be printed first." Why? The paper is manufactured so that it should not stick to the drum used to transfer the toner. For this it has a pre-defined curling, and needs to be loaded into the printer so that it will tend to curl away from the imaging drum, rather than tend to wrap around the drum or rollers. DIN 19309 has been replaced by the European standard EN 12281 (q.v.). Other DINs: DIN EN 12858 continuous papers DIN 6733 envelope paper DIN 19307 paper and cardboard for office purposes DiPrint Direct Print or RAW Print. Is Ricoh's name for port 9100 communication. This service uses TCP port 9100 to direct print from remote computers. (Port 9100 actually originated with HP, for JetDirect printing.) Direct file printing Allows users to submit PostScript, PCL, PDF, and ASCII text files resident on LAN servers directly to the printer without opening them in an application or using a printer driver. Disable on job mismatch Yes/No selection under printer Properties, "Load Balancing" tab, "Disable on job mismatch". Normally, a job requesting resources not currently loaded in the printer cause just that job to be disabled, and other jobs to step over it. However, there may be a printing sequence which depends upon each job printing in order, in which case you can cause the printer to disable on such a mismatch. Disable printer 'pddisable ' New incoming jobs are allowed to queue, and those in Processing state destined for that printer are allowed to complete, but no more will be sent to the printer until a later Enable is done. IPM maintains a session with an IPDS printer during its Disablement. Msgs: 5010-331 Starting the disable... 5010-332 [complete] GUI: Printer -> Disable See also: Pause; Stop; Shut down Discover printers at startup See: snmp-discovery-during-startup Disk space level warning You can configure the IPM server to monitor file systems in general - even the level of file systems not directly related to its operation - via server attribute notification-profile, disk-space-low notification event ("disk space low" in the GUI); and then out-of-disk-space. Most commonly, this will be configured to send email to the IPM administrator. IBM failed to document the file system level which triggers notification: I found it to be 80%. This will help prevent a full file system condition (JFS_FS_FULL in the AIX Error Log (errpt)). Msgs: 5010-145 Distributed servers Ref: Procedures manual, "Creating and managing servers". Getting Started manual topic "Installing secondary Infoprint servers". Ditroff fonts The following are the descriptive names of the ditroff fonts, and these names map to the names used in the AFP character sets: B TIMES NEW ROMAN LATIN1 ROMAN BOLD BI TIMES NEW ROMAN LATIN1 ITALIC BOLD C COURIER LATIN1 ROMAN MEDIUM CB COURIER LATIN1 ROMAN BOLD CBI COURIER LATIN1 ITALIC BOLD CI COURIER LATIN1 ITALIC MEDIUM H HELVETICA LATIN1 ROMAN MEDIUM HB HELVETICA LATIN1 ROMAN BOLD HBI HELVETICA LATIN1 ITALIC BOLD HI HELVETICA LATIN1 ITALIC MEDIUM I TIMES NEW ROMAN LATIN1 ITALIC MEDIUM R TIMES NEW ROMAN LATIN1 ROMAN MEDIUM SG TIMES NEW ROMAN SYMBOLS ROMAN MEDIUM SS SPECIALS Installed in: /usr/lib/font/devafp/ See also: T1 Ditroff transform /usr/lpp/psf/bin/d2afp dn Common printer model suffix characters, standing for "duplex + network", meaning that the model includes the often-optional duplexer and a network card (usually ethernet). Example: Infoprint 1145dn Document In Infoprint, an object representing a grouping of data within a job. A job can contain one or more documents. The documents in a job can differ from each other in some ways. For example, they can contain different data and can have different document formats. A document within a job can contain printable data or a resource that is not printable by itself. See file-reference document, printable document, and resource document. Document element A portion of a document at least a single page in size. Document format In Infoprint, a document format describes the type of the data and control characters in the document, such as line data or PostScript. The format of the data determines which printer devices are capable of printing the document and whether Infoprint must transform the format. Document format of a job, list 'pdls -c job -r document-format ' Document identifier A string that identifies a document within a job. It consists of a job ID followed by a period (.) and a document sequence number. For example, 12.2. Document sequence numbers are integers starting at 1. Document transfer method In Infoprint, the transfer method describes how documents are transferred to, or acquired by, servers. See: pipe-pull; with-request Document type In Infoprint, the document type describes the kind of data in the document. A printable document can only contain printable data. A resource document can only contain data such as fonts or form definitions that are not printable. A file reference document can only contain names of files entered on separate lines. document-file-name Job attribute, naming the document file at its point of origin, as distinguished from the file name. For an AIX LPD gateway submission, reflects that subsystem's file name, like: /var/spool/lpd/dfA648acsn05.1037971583 For a Windows system running Infoprint Select, the name would be like: C:\Program Files\IBM\Infoprint Select \Spool\3f43c0ac.SPL For a Mac OS X system, the name would be like: /var/spool/lpd/dfA379Js-ibook.local. 1076691710 where Js-ibook.local is the Local Hostname of the Macintosh, for local subnet sharing access. See also: job-name document-finishing Document attribute which identifies the finishing options for this document. GUI Label: Finishing options DSS: PSF Allowed Values: z-fold Default Values: none This attribute is not valid for ASCII documents. When you specify a value for document-finishing, Infoprint creates an inline Formdef; so do not use the form-definition attribute to specify another Formdef. Infoprint validates and schedules jobs using this attribute against the destination attribute document-finishings-supported. See also: Inline resources document-finishings-supported AD attribute which identifies the document finishing options that this actual destination supports. IPM compares the document attribute document-finishing to this attribute for validation and scheduling. GUI Label: Finishing options allowed document-format Specifies a single data type for the document. GUI label: Format (Document Other tab) The format is "ascii", "line-data", "modca-p" or similar standard definition. The value is used in scheduling jobs, comparing the document format against the document-formats-supported list defined for the AD. If no format is specified, IPM sniffs the job file to discern what it is. document-formats-supported AD attribute for specifying what page description language formats the AD can process. GUI: AD properties, Document tab, "Formats allowed". document-formats-supported, list 'pdls -c destination -r document-formats-supported ' document-sequence-number Job attribute: Identifies this document in relation to the other documents within a multi-document job. See also: number-of-documents Documents within job A job may contain multiple "documents". We have seen this with PostScript and PDF jobs. Each page may be a separate document. The multiple documents within a job may be identified via separator pages. See: document-sequence-number; number-of-documents Dot See: PEL DPF The PSF/2 Distributed Print Function. A component of PSF/2 that you can use to print jobs sent to PSF/2 from PSF/ (PSF/MVS, PSF/VM). DPF receives host PSF output and resources for spooling and printing with PSF/2. DPF also stores PSF/ resources in the DPF resource library, so that the host system does not have to send PSF resources each time documents are spooled. Through DPF, PSF/2 under OS/2 2.0 provides a function similar to that provided by Remote PrintManager (RPM) Version 3.0 under DOS. DPI (dpi) Dots Per Inch, specifyable on most transforms via the -r option. The IPM 4.1 product default was a mix of 300 pel (gif2afp) The IPM 4.2 product default moved to predominantly 600 pel. In a logical destination, the value is specified via the attribute default-printer-resolution. See also: default-printer-resolution; print-qualities-supported; Resolutions supported by IPM Drivers, PC Named in Logical Destination properties, Drivers tab. Attr: client-driver-names (q.v.) Ref: Procedures manual, Finishing Options See also: Infoprint Select Drivers, where to download Printer drivers can be downloaded from http://www.infoprintsolutionscompany.com by drilling down through: Support & Maintain Online Hardware & Software Support Downloads and Drivers Printer Downloads and Drivers where you would then choose a printer model, such as "Infoprint 2105ES", whereupon you will be presented with web pages containing drivers for various platforms. DSS Destination Support System; or, Device Support System. In Infoprint, the programs that an actual destination uses to communicate with the output device. Synonymous with Device Support System. See: AIX destination support system; BSD destination support system; PSF destination support system; 3170 destination support system; Infoprint 2000 DSS; email destination support system; fax destination support system dss-job-message-disposition AD attribute: How job messages about DSS-detected errors are recorded. Errors could involve areas such as data stream. GUI: AD Customize tab, "Record job messages". Multiple choice selector: Print or Log. Logged messages go to: /var/psf//jobmessage.log Duplex Defined as printing on both sides of the sheet. In AFP printing: Governed in a Formdef via "DUPLEX YES". Specified in IPM GUI via: Logical destination, Job and Document Defaults, Document Layout tab Sides to print 2 Plex to print simplex For PostScript printing (as in AIX printer type, where the PostScript is simply sent to the printer as-is): Depends upon the PostScript code: << /Duplex true /Tumble false >> setpagedevice Note well in PostScript printing to HP and similar printers that what is coded in the PostScript dictates how the job will actually be plexed, and thus will take precedence over any job attributes to the contrary. See also: AIX destination support system; Simplex DUPLEX PPFA Formdef command: Specifies whether printing is done on both sides of the sheet. This subcommand should be used only for page printers that have duplex capability. NO Duplex printing is not performed NORMAL Duplex printing is performed, with the tops of both sides printed along the same edge for side binding. TUMBLE Duplex printing is performed with the top of one side and the bottom of the other printed along the same edge of the sheet for top binding. RNORMAL Rotated normal. Duplex printing is performed with the top of one side printed along the same edge of the sheet as the bottom of the other. Used with landscape pages, N_UP 2, and N_UP 3. RTUMBLE Rotated tumble. Duplex printing is performed with the tops of both sides printed along the same edge. Used with landscape pages, N_UP 2, and N_UP 3. There is apparently no default. In IPDS terms, duplex printing is controlled through the IPDS Load Copy Control (LCC) command. Duplex, allow choice See: pcl2afpd Duplex, long-edge vs. short-edge bind A standard choice in duplex printing is to produce the output such that its pages look right when bound along an appropriate edge. Commonplace long-edge binding is as you find in books and magazines, where each page is in portrait format and binding is at the left, long edge of the sheaf. Short-edge binding is where the sheaf is held in landscape orientation and bound at the left edge of the sheaf. This is also known as "tumble duplex, where the top edge of one side is the bottom edge of the other side. When submitting the job, the submitter can specify long- or short-edge binding for the duplex. In AFP/IPDS printing, duplex processing is wholly controlled by the IPM server: specifying long- or short-edge binding within the PostScript has no effect upon the output, which is governed by server parameters (plex=simplex or plex=tumble). Duplex controls for HP printers The specs for causing duplexing to occur on HP printers derives from the Colon Files (q.v.) for those printers. Duplex detection See: ps2afp output per PostScript factors Duplex Long Edge Binding Delivers two-sided output. Landscape documents read like a calendar, and Portrait documents read like a book. Duplex printing & Copy Group If in Pagedef processing the Formdef Copy Group is restarted, it always causes a sheet eject. Thus, in duplex printing, while on the front side of a sheet, the remaining data starts on the front side of the next sheet rather than on the back side of the current sheet. Duplex printing via PJL By default, HP printers usually print in simplex mode. You can cause them to print in duplex by enveloping the PostScript file in PJL: %-12345X@PJL JOB @PJL SET DUPLEX=ON @PJL ENTER LANGUAGE = POSTSCRIPT ...PostScript file... %-12345X@PJL EOJ (The final EOJ line may be omitted.) The printer can be permanently changed to always print in duplex rather than in simplex via: @PJL DEFAULT DUPLEX=ON which should store that in NVRAM. Note that while a printer may accept PJL, you may find IPM effecting plex by sending preface PostScript like "statusdict begin true setduplexmode end", rather than via PJL. Duplex Short Edge Binding Delivers two-sided output. Landscape documents read like a book and Portrait documents read like a calendar. DUPLEX=YES Seen on the ainbe command line in AFP printing, as results from job attributes plex=simplex and sides=2. dvi (DVI; .dvi) DeVice Independent file format, as output from the TeX typesetting program. IPM does not have a transform to process DVI files; nor does it properly recognize a DVI file: it assigns the file a Format of ASCII! Early binding In Infoprint, assigning a job to an actual destination as soon as it is accepted. Early binding permits Infoprint to estimate the time when the job will be completed. Contrast with late binding. Controlled by attr assign-to-destination (q.v.). Early Binding facilitates multiprocessing, which is important in doing RIPing well ahead of printing so that the printer does not sit idle as the next job initiates RIPing. ECF Enrollment Certificate File; for storing the features purchased for a particular installation. See also: LUM .ecf Filename extension for Enrollment Certificate (license) files, as supplied with the product, according to what you paid for. See: License See also: aix_base.ecf Edge stitch To bind the output with two staples along one edge: top, bottom, left, or right. Edge-to-edge Infoprint 2085/2105 printer setting (Interpreter Settings). Turns edge-to-edge printing on or off: Off The printer maintains a border of 2 mm on each edge. On The printer allows printing up to the physical page size. Printer vendors, including IBM, recommend not printing to the edge of the paper, as toner can then get onto the mechanicals. Note that paper positioning in cut-sheet printers cannot be expected to be exact, and so this hold-back may vary from top to bottom and from sheet to sheet. Ramifications: Web browers like to add the window title, page number, and URL as page header and footer elements; but those elements tend to be much too close to the edge of the paper, often leaving just the bottom of character descenders at the top of the sheet, and the tops of tall characters at the bottom of the sheet - which can look like extraneous toner marks which may incite operators to call the vendor for service! (Some vendors have special names for edge-to-edge printing: Epson uses the trademarked term "BorderFree".) electronic-mail A notifications delivery-method, to send email to the address specified via delivery-address = "Username@Netname" form. Synonyms: e-mail; email Infoprint Select employs this method, as the Infoprint Select Notifications component on the PC is a mini SMTP server, accepting return messages of limited type. This may also result from invoking lpr with the -m option. Contrast with: message Email DSS IPM/AIX uses the email DSS to send jobs as emails to electronic mailing systems. Most commonly used to transform any input to a PDF. IPM creates the PDF as version 1.2 . IPM directly connects to the SMTP server defined in server properties (GUI label "SMTP server"). Processing command: img2fax There will be a process hierarchy consisting of: /usr/lpp/psf/bin/vp -p /usr/lpp/psf/bin/img2fax -p 2061 -sp 2062 /usr/lpp/psf/bin/sendmemo Who@Where NULL Test NULL NULL /var/psf/faxserver/Z.pdf NULL 25 Space required in: /var/psf/faxserver/ for the Z.pdf and ever-growing sendmemo.log . Msgs: 0424-225 The PDF will be emailed using: MIME-Version: 1.0 Content-type: multipart/mixed; boundary=IBM_IPM_SMTP_EMAIL_CLIENT_18208 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Type: application/pdf Content-disposition: attachment; filename="Test PDF.pdf" Content-Transfer-Encoding: base64 The resulting PDF will show: Content Creator: infoPrint FAX Manager PDF Producer: infoPrint FAX Manager Author: infoPrint FAX Manager where the email message body will be empty. Whereas Email DSS processing involves creating a PDF, rather than printing, dpi considerations do not apply, and the various *resolution* attributes are not applicable. Similarly, there is no document-level finishing. Comments: Resulting PDF image quality is excellent; but shaded areas end up with a grid effect which is not in the original image. Notes: If the email-from-address attr is missing, the job fails with 0424-225. You want to invoke like: pdpr -d emailpdf \ -x "email-to-address=joe@where \ email-from-address=me@here \ subject-text='Test PDF'" TheInputFile where the input file can be of any format. See: Infoprint Email Email DSS, create Via GUI: Other menu, Create -> Email Destination EN 12281 (aka NEN 12281) The EN 12281 standard sets the requirements on the technical properties of copying paper, to make it suitable for copying machines and laser printers. One of the things it prescribes is the runnability of copying paper of the format DIN A4. Among other things, a runnability test is carried out. A certain number of simplex and duplex copies must be made. During these tests, only a limited number of jams are permitted. For copiers with little throughput (less than 30 copes per minute), a maximum jam rate of 0.77 per mil (3.5 jams per 5,000 copies max.), for machines with a large throughput, a maximum jam rate of 0.23 per mil (2.3 jams per 10,000 copies max.) are allowed. This standard replaces DIN 19309. Enable printer 'pdenable ' Msgs: 5010-333 Starting the enable... 5010-334 ...complete enabled Not modifiable: Cannot be used in a 'pdcreate', else get error: 5010-093 Cannot modify the value of attribute enabled. End sheet GUI: Element of Printer Properties, Auxiliary/Separator Sheets tab. Possible values: 64xx blank brief full job ticket none <--- default See also: Auxiliary sheets allowed; Slip/Separator sheet; Start sheet end-message-supported AD attribute: Indicates whether the AD supports the job attribute job-end-message. Allow operators to receive messages that users specify with the job-end-message job attribute when they submit the job. This might be done to specify special handling of the printed output. GUI label: Send job completed message See also: start-message-supported ENDSUBPAGE See: CONDITION Enhanced AFP Circa 2001. An object-oriented, device-independent technology, developed to deal with changes in printing needs. This model makes the next big step in delivering information possible by supporting delivery via HTML, fax, e-mail, computer and TV screens. AFP will interact with databases under the control of layout tools such as PageFlex, Xstream and Elixir, as well as middleware such as SAP, Tivoli and PeopleSoft. With each piece being different, IBM's page-level recovery software will allow quality control of each page, and Infoprint workflow software will integrate pre- and post-processing, from database mining to driving the stuffing and mailing equipment. Enscript Utility to convert text files to PostScript for printing on a PostScript printer. Can be installed from the AIX TranScript Tools package (bos.txt.ts). Environment The proper operation of IPM very much depends upon proper environmentals. When IPM for AIX is installed, it modifies the /etc/environment file to establish environment variables as it needs them, which will (or should) be inherited by init-started processes and people logging into that server system. In particular, the PATH variable specifies IPM lpp and java resources needed for proper operation, in the order needed. One danger is in a systems person logging in to the server system with a personally tailored .cshrc or .tcshrc or other shell configuration file, which may not have needed IPM elements, or in the right order: if that individual then restarts daemons, incorrect operation or non-operation may occur. For illustration on how important correct setting are, see our notifyd notes. Environment variables Any environment variables which you deign to affect the operation of the IPM server, and which you change when the server is up, cannot take effect until the IPM server is restarted. See: PATH; PDIDTABLE; PDNOTIFY; PDPATH; PDPRINTER; PD_CONFIRM_DELETE; PD_ENABLE_TIMEOUT; PD_LISTEN_COUNT; PD_SOCKET; PDIDTABLE; POSERVERPORT; PSFDBLANK; PSFPATH; and others Ref: Reference Manual, chapter on "Infoprint environment variables". EPS and Page Segments See: Page Segment, create from PostScript Error handling, PostScript By default, Infoprint Manager cancels PostScript jobs that exhibit PostScript language errors. Check for such an error in the ps2fpd.log file that is contained in one of the following directories: /var/psf/ps2afp most printers /var/psf/ps2afp2 Infoprint 60 printer If the job is not printing correctly because of PostScript language errors, update /var/psf/ps2afp/Userinit to have: %! turnErrorHandlerOn In concert with this, in the printer change Interpreter Settings: PostScript, "Print errors:" to "On" (if the printer is RIPping PostScript). Ref: Procedures manual, "Specifying font substitution through initialization files" See also: Font substitution, PostScript Error log, server /var/pd//error.log It's normally, by default, a wrap-around log. The wrap point is marked by line "WWWWWWWWWW". When the log has wrapped, the following line will be at or near the bottom: >>> The error log file has filled and is wrapping. <<< The first char of each line in the log is a message severity indicator (followed by a space). There is no documentation of what that initial character indicates. A Advisory (informational) message. Tends to be conclusion messages, such as "5010-280 Finished processing job" and "5010-338 The shutdown request for destination ______ is complete." D Seem to identify destination processing messages. E Error condition, as when a printer has a paper jam or open cover or goes offline or times out or is low on paper; or when a transform returns a non-zero value (job fail, as when a customer-written transform reacts to a user over print quota). When the server restarts it creates a backup of this file. Oddly, no utility command is provided to logically inspect the log: the customer is left to do that by physical means. A conspicuous deficiency in the log is that, during start-up, there is no start-up record written to record when the server started or what its version, release, and PTF level are. Note: The AIX 'alog' command cannot be used to examine the log. error.log See: Error log, server ErrorLog Configuration File /var/pd/spl_error.cfg estimated-processing-time Job/Default Job attribute indicating how long the job should take. GUI: Estimated processing time IPM uses the values of the total-job-octets and job-complexity attributes to estimate the jobÕs processing time. You can change this value. But: IPM can calculate a value for this attribute only when the queue attribute assign-to-destination is set to true. Related: processing-time /etc/fst.ports Small binary file. Purpose: ??? Used if a non-DCE environment. See also: FST /etc/hosts.lpd File which can be used to control access to the lpd on the system - which in IPM terms controls use of the "LPD Gateway". /etc/inittab Invokes the rc.pd utility to automatically restart the Infoprint servers listed in /etc/rc.pd.servers during a reboot. As the administrator, you can edit the rc.pd.servers file using a text editor to include a startsrv line for each server you want to start automatically. /etc/pdserver.conf Servers configuration file. This is not a static file that you set up, but rather a dynamic file, erased by /etc/rc.pd at start-up, and recreated to contain a single line, housing the following positional entries: 1. The locale (e.g., en_US)/ 2. Port number of the IPM server (e.g., 6874). 3. The name of the directory control point for the IPM namespace (/var/pddir/default_cell). This file contains a list of the running pdservers on the machine, the port the command processor part of the pdserver is listening on, and the locale in which the pdserver is running. When a command is invoked, the first command processor port in the list in the user's locale is used. When a pdserver is started, it adds its entry to the list. When a pdserver is shutdown, it removes its entry from the list. /etc/rc.ippgw Starts the IPM IPPGW daemons, invoked in /etc/rc.local . Records that start in /tmp/rc.ippgw.out /etc/rc.licd Starts the IPM licensing daemon, invoked in /etc/rc.local . Records that start in /tmp/rc.licd.out /etc/rc.lpd Starts the IPM LPD daemons, invoked in /etc/rc.local . Records that start in /tmp/rc.lpdp.out /etc/rc.mvsd Starts the IPM MVS Download daemons, invoked in /etc/rc.local . Records that start in /tmp/rc.mvsd.out /etc/rc.notd Starts the IPM notification daemon, invoked in /etc/rc.local . Records that start in /tmp/rc.notd.out /etc/rc.net.ipr Tuning script installed by IPM, for a Basic server configuration (only: does not install this for an Advanced server configuration). Adjusts network tuning, vmtune, and other system settings. /etc/rc.pd Starts the IPM server daemons. Invoked in /etc/rc.local . Records that start in /tmp/rc.pd.out Autostart IPServer shell script started by the entry added to /etc/inittab at install time. If you run manually, remember to be root, and unlimit memory values so that the server does not run short. See also: /usr/lpp/pd/; Server /etc/rc.pd.servers List of Infoprint Manager servers to be started, via /etc/inittab running shell script /etc/rc.pd Contents are like: startsrv -F See also: pdcrdflt /etc/services Unix file for TCP/IP service name-to-port-number lookups. IPM adds entries to it, which look like: psmd 6874/tcp pdeventd 6875/tcp iprp1 2050/tcp # IPR reserved port (generated by pdinitports) ... Event Log Viewable in the Infoprint VSM administrator's GUI. event-comment Element of notification-profile, to code text which will be prepended to the event message. Can be up to 4095 chars. Exits, IPM admin GUI Under Customize tab ("show more"). External name (x-name) The file system name of an object file. as compared with its Internal name. F1* Filename prefix for Formdefs. GUI: Printer properties, AFP Resources tab, "Form definition" field See also: Definition resources; P1* F100APS The default, inline form definition generated when 'pcl2afp' or 'ps2afp' are run to generate an AFP file when "device_controls" is uncommented in their respective transform config file. May, of course, be overridden by an externally named Formdef (as via job submission options of Job/Document Defaults), to be integrated by the print-time software (commonly, 'ainbe') AFP->IPDS processing. Principal Formdef Copygroup subsections within it: D_______ Duplex Copygroups... D_000000 ...no offset stacking... D1000000 from Tray 1 D2000000 from Tray 2 D3000000 from Tray 3 D_0J0000 ...do offset stacking... D10J0000 from Tray 1 D20J0000 from Tray 2 D30J0000 from Tray 3 S_______ Simplex Copygroups... S_000000 ...no offset stacking... S1000000 from Tray 1 S2000000 from Tray 2 S3000000 from Tray 3 S_0J0000 ...do offset stacking... S10J0000 from Tray 1 S20J0000 from Tray 2 S30J0000 from Tray 3 T_______ Tumble Duplex Copygroups... T_000000 ...no offset stacking... T1000000 from Tray 1 T2000000 from Tray 2 T3000000 from Tray 3 T_0J0000 ...do offset stacking... T10J0000 from Tray 1 T20J0000 from Tray 2 T30J0000 from Tray 3 /usr/lpp/psf/reslib/F100APS This stuff constitutes a prolog in the job, providing AFP resources which the document section of the AFP may use. In particular, you will see the document section having IMM (Invoke Medium Map) entry which invokes one of those Formdef copygroups according to the plex coded in the PostScript, such as 'afpdmp -d' showing: IMM: media map name = 'D1000000' F1A00010 Form definition supplied by IBM. A zero offset, simplex, non-stapling Formdef. F1A00011 Form definition in set to use if images or data in the job prints off-center or appears to be shifting on the page. Bin: 1 Sides: 2 Presentation mode: Portrait Print Direction: Across Page position, inches: 0, 0 (X and Y from top left corner) F1A10111 Form definition, as found used for pure IPDS printer. Bin: 1 Sides: 2 Presentation mode: Portrait Print Direction: Across Page position, inches: 0.165, 0.165 (X and Y from top left corner) F1H50111 Form definition, default for PCL5 Bin: 1 Sides: 2 Presentation mode: Portrait Print Direction: Across Page position, inches: 0.165, 0.165 (X and Y from top left corner) F1MG0110 The common message-form-definition value. Has the following settings: One copy No overlay Use paper from bin 1 Related: F1MGIMP, which is identical except that it specifies offset stacking. .fde Filename extension for an Formdef. Feature An optional, extra cost component which may be acquired/licensed from IBM to add functionality to IPM. Also known as Optional Component Features, adding After you have been running the IPM product for some time, you may want to add a product feature or two, such as Workgroup Printer Feature, in order to drive HP printers. Expect the CD to arrive with a 'setup' Korn shell script on it, for installing after mounting the CD on /cdrom. Considerations: You have been living with the product for some time after initial install, and have applied maintenance over time. But the new feature is being introduced like a base level thing with no maintenance, and so it has to be brought up to date. You will experience a pop-up advising of this - you need to have the latest service PTF available. Note that minor things like basic licenses and config files to drive printers will likely have no maintenance. See also: Options installed; setup FIELD PPFA: PRINTLINE subcommand to specify both where source data appears in the input line and its destination on the output page. TEXT subcommand can be used to output literal text. Note that, by default, the text is EBCDIC, with no provision for ASCII: you are stuck having to encode the ASCII with hex (like X'414243' for 'ABC'). Tip: Use it when you want to have the same data element appear in multiple places on the page: You code one PRINTLINE to use that input data line, then have multiple FIELD commands after it, each one referring to the same area of the input data line, but specifying a different page POSITION. Remember that the FIELD command's POSITION is relative to the PRINTLINE position. Thus, if you want the FIELD to specify an absolute position, then in the PRINTLINE have its POSITION be 0 0. File system level notification See: Disk space level warning File-reference document In Infoprint, a file containing the names of other files, each entered on a separate line. Job submitters can specify this file for printing when they specify a document type of file-reference; Infoprint prints each file listed in the reference document. Fill patterns PPFA manual, appendix "Fill Patterns for DRAWGRAPHIC Commands". FINISH AFP Formdef level parameter, saying that a finishing operation is to be performed, with detailed specifications provided within that stanza. This parameter is used with printers having finishers: attachments or embedded mechanics for stapling, punching, binding, or otherwise performing modifications to the job sheets at a stage following printing. Sub-options: SCOPE As the name suggests, defines the scope of the finishing: PRINTFILE Applies to the print file as a whole. This is the default. ALL Applies individually to all documents in the file. (number) Identifies the one document as the scope. OPERATION Specifies the type of finishing, and parameters: CFOLDIN Center Fold In. CORNER Staple, at the corner defined by REFERENCE. This is the default. CUT Separation cut, along the axis of the finishing operation. EDGE Staple along the edge. FOLD Fold inward on the front sheet side of the first sheet of the collection. PERFORATE Make perforation cuts along the axis of the finishing operation. PUNCH Punch/drill holes alon the axis of the finishing operation. SADDLE Staple down the middle of the collection, as is common with catalogs, where it is implied that the collection will be folded outward. SADDLEIN Like Saddle, but with inward folding. REFERENCE Accompanying specification defining the reference corner or edge of the finishing operation: DEFAULT Let the device's definition determine it. This is the reference default. TOPLEFT The top, left corner. TOPRIGHT The top, right corner. BOTRIGHT The bottom, right corner. BOTLEFT The bottom, left corner. TOP Reference edge is at the top. BOTTOM Reference edge is at the bottom. LEFT Reference edge is at the left. RIGHT Reference edge is at the right. See "Corner Staple Angle" for more info on the effect of TOPLEFT. Notes: A finisher usually provides additional output bins to a printer. As such, you may want to use the IPM output-bin attribute to specify a bin rather than use Formdef FINISH, where you want output to go to a given bin but not be stapled. Finishing options, IPM admin GUI Under Job tab ("show more"). Attribute: job-finishing What happens on 2085: "staple top left" A diagonal corner staple. "edge stitch left" A diagonal corner staple. FOCA Font Object Content Architecture. Ref: Font Object Content Architecture Reference manual. FONT Font specification within a Pagedef. Example: FONT Courier10 4202; /* ASCII print */ Note that a FONT specification within the Pagedef overrides any font specified via the 'line2afp chars=____' command argument. Font See also: Outline font Font, capture See: Font, PostScript, capturing Font, PostScript, capturing Via the 'fontsave' utility command (/usr/lpp/psf/bin/fontsave). Ref: IPM Procedures manual, chapter "Working with fonts", "Adding non-IBM fonts to AIX for a PostScript job". Font mapping file, PostScript, create 'mkfntmap FontFile > font.map' Font size Font sizes are according to height, not width, from the baseline of one line to the baseline of the next, allowing for asenders, descenders, and the minimum white space between lines. The larger the number, the larger the font. Typewriter fonts (monospaced fonts) are often measured in pitch - the horizontal distance between character cells, measured in characters per linear inch. Font substitution, PostScript By default, Infoprint Manager cancels PostScript jobs that would require font substitution. Check for such an error in the ps2fpd.log file that is contained in one of the following directories: /var/psf/ps2afp most printers /var/psf/ps2afp2 Infoprint 60 printer To allow font substitution, edit file /var/psf/ps2afp/UserInit file to have: %! turnFontSubstitutionOn (Changes in the UserInit file take effect without having to restart daemons.) Font substitution traditionally causes the font Courier to be substituted for the missing font, because as a monospaced font, Courier stands out as an error, but allows the document to complete. (Note that, in standing in for a proportional font, the Courier text may look rather jumbly.) The odd-looking text is the only communication to the user that font substitution has occurred: no error page is produced. Font substitution can occur only within compatible alphabet systems. A job file which seeks to print Chinese symbols but doesn't carry a needed font will not, for example, cause Courier to be substituted: that just doesn't make sense. In PC printing, the device driver may have a Device Settings tab where there is a Font Substitution Table, where the user may specify, for example, "Arial: Helvetica". The PC may observe this for PostScript printing, but maybe not for PDF printing. Log msgs: in ps2afpd.log, like: Univers-Black not found, using Courier. 0424-092 ps2afpd: The transform could not find a PostScript font for use in your document. A Courier font was used instead. Missing fonts include: Univers-Black Ref: Procedures manual, "Specifying font substitution through initialization files" Note that some applications may generate PS files with erroneous font names, as in using an underscore in a font name rather than a hyphen: Helvetica_Oblique rather than Helvetica-Oblique. (Some appls will replace a blank with an underscore.) See also: Error handling, PostScript; PostScript error Fonts, IPM /usr/lpp/afpfonts/ (probably not) /usr/lpp/psf/fontlib/ AFP C0* files /usr/lpp/psf/ps/psfonts.map PS names /var/psf/psfonts/user.map Ref: Procedures manual chapter "Working with fonts" Fonts, IPM, AFP /usr/lpp/psf/fontlib C0* files Fonts, IPM, PostScript IBM PostScript Type 1 outline fonts, installed in /usr/lpp/psf/ps/fonts/. If you have other Type 1 outline fonts, you can also use them with the transform program. The fonts are listed in file: /usr/lpp/psf/ps/psfonts.map Fonts, PostScript The fonts are listed in file: /usr/lpp/psf/ps/psfonts.map AIX fileset: ipr.fnt.ps Fonts, PostScript, filename extension .pfa ASCII form. Adobe Acrobat Distiller wants fonts in this form. .pfb Binary form. /usr/lpp/psf/fonts/apl/ Use utility 'makepfa' to transform from binary into ASCII. fontsave PostScript font capture utility. /usr/lpp/psf/bin/fontsave See: Font, PostScript, capturing Form Terminology for a physical sheet of paper. See also: Page Form definition Aka Formdef. A form definition specifies how the printer controls the processing of the physical sheets of paper: it defines the placement of the logical page of data on the form, plus the following functions: - Position of a logical page on a physical page (margins, gutter). - Duplex printing. - Inclusion of overlays, which substitute for preprinted forms. - Flash (the use of a forms flash only on 3800 printers) - Selection of the number of copies for any page of data - Suppression (the exclusion of selected fields of data in one printed version of a page of data but not in another). - Jog (the offset stacking of cut-sheet output or copy marking on continuous-forms output). - Selection among paper sources (bins) in a cut-sheet printer. - Adjustment of the horizontal position of the print area on the sheet (only on 3800 printers). - Quality (selection among print quality levels). - Constant (allows front or back printing of a page without variable data). - Printing one, two, three, or four logical pages on a single side of a page - Postprocessing controls, such as selecting device-dependent functions defined by the postprocessing device. - Perforating. - Cutting. The formdef governs the external handling of the logical page, and the Page Definition controls the internals of the logical page. See also: Page definition "Form definition" IPM AD properties, AFP Resources tab field. The default formdef that the output device uses when printing or transmitting a document. Defaults to: F1A10111 Attr: form-definition (q.v.) There *must* be a default formdef in this field: if you delete the contents of the field and then commit the AD definition, the IPM default value returns. Form definition naming Like: F1A00010 Name length is up to 8 characters (deriving from MVS Partitioned Data Set member naming limitations). Positions: 1,2 Always "F1", meaning "form definition, one single copy form". 3,4 "A1" or "A0": for all AFP printers other than the 3800 "CP" for use with HP printers (PCL4, PCL5) through IPM for Windows. "C1" or "C0": 3800 compatibility "H1": 3-hole punched paper "FC": Finisher with corner staple "FE": Finisher with edge stitch "FS": Finisher with saddle stitch "FZ": Finisher with Z-fold "N2": N_Up (2 up) 5,6 00: Offset 0,0 01: Offset 0.0165, 0.0165 10: Offset 0,0; Duplex=None (Simplex) 11: Offset 0,0; Duplex=Normal (Duplex) 12: Offset 0,0; Duplex=Tumble (Duplex) 7,8 If both are characters: LA: Landscape across LD: Landscape down PA: Portrait across PD: Portrait down Position seven (only if it is a number or it is a character followed by a number in position eight): E: Envelope #: Bin number M: Manual Position eight (only if it contains a number) indicates duplexing: 0: None (Simplex) 1: Normal (Duplex) 2: Tumble (Duplex) Example: F1A00010 means: F1: Form definition, Single copy form A0: An AFP printer other than the 3800 00: Offset 0,0 1: Bin 1 0: None (Simplex) Form definition override Job submission command options can result in overriding whatever form definition is to be in effect for printing the job. For example, in 'lprafp' submission, using the -obin option will override the output bin value specified in the form definition. Form Definition used In AFP printing, a Form Definition has to come from somewhere. The order of usage is: 1. The Formdef specified at job submission time, as exemplified by the command option -oformdef=FormdefName 2. The Formdef defined in Job/Document Defaults. 3. Inline resource definitions: The resources concatenated ahead of the actual job input data, per the transform daemon device_controls, known as the Begin Resource Group section, where a Pagedef and/or Formdef may appear. 4. The default form-definition for that IPM AD. An input file can contain multiple inline form definitions, but only one form definition can be used for printing: by convention, the first formdef is used. The -oformdef=FormdefName spec is equivalent to the Infoprint document attribute form-definition. It may be perplexing that IPM commands such as 'ps2afp' do not provide a means of specifying a Formdef. Without a Formdef, and with device_controls turned on in the ps2afpd.cfg file, the act of running ps2afp causes the generation of a default inline Resource Group, having the name INLINERS, with a default Formdef (F100APS prevails these days). The Formdef which is identified in the job submission or Job/Document Defaults attributes is remembered, as the job trundles through IPM processing. It is at print time that this named Formdef is applied, as you can see as the FORMDEF= parameter on the 'ainbe' command in PSF TCP/IP printing, overriding the inline, default resources. The IPM server loads needed Formdefs and Pagedefs from /usr/lpp/psf/reslib/. With no Formdef defined in the document defaults or the job, and no device_controls in effect, basic AFP processing occurs, and no FORMDEF= appears on the ainbe command line during printing. The job comes out properly laid out on the page because of the parameters in effect in the p22afp. In such basic processing, the sides and plex job attributes are honored, where you will see DUPLEX=YES on the ainbe command line for two-sided printing. More advanced functions such as stapling cannot be effected without a Formdef. See also: device_controls Font specification (PPFA) Via the Pagedef, either in the PRINTLINE or FIELD commands, or in the TRCREF command. Fonts and jobs Users should be encouraged to have their applications include needed fonts in the body of their jobs... It is often the case that a job will require odd fonts which are not provided in IPM, and the job may end up with Courier in some places - possibly not noticed until after it may be too late (as after a paper is handed in). Foomatic Is a configurable printing filter. It uses PPD files as configuration to generate appropriate output for a given printer. It is spooler independent which means it can be used with Common Unix Printing System (CUPS), LPRng and others.[1] It uses Ghostscript in the background, using options according to the PPD file of the printer. Currently it is developed by the OpenPrinting workgroup of the Linux Foundation. form-definition Actual Destination attribute: Identifies the default Formdef that the output device uses when printing or transmitting a document, only when there is no such document/default attribute value, and if IPM does not create a Formdef using the values of other document and job attributes (as when job-finishing values are specified, for stapling or the like). Use only for true PSF/IPDS devices. GUI Label: Form definition Default Value: Standard Infoprint administrator's GUI and command line: F1A10111 Basic Infoprint administrator's GUI: F100D The AD form definition is used a "last resort", if not specified earlier in job processing. form-definition Job/Document Defaults (Initial-value-document) attribute: Identifies the form definition used when printing this document. GUI Label: Form definition If not specified in Job/Document Defaults and does not come from elsewhere, IPM uses the Formdef defined by the actual destination attribute form-definition. For PSF, if you specify a value for the document-finishing or job-finishing attribute, IPM creates its own form definition; so do not specify a value for this form-definition attribute. Specify this only for LDs feeding AFP/IPDS printers. If the LD is to feed a PostScript printer, or a combination of PostScript and IPDS printers, leave this attribute undefined: a job tagged with an AFP attribute and then going to a non-AFP printer will fail, because such an attribute is inappropriate. To deal with a mixed situation, use a transforms program which detects the "sides" attribute, to then effect a Formdef where the AD is an IPDS printer. "Formats allowed" AD GUI field specifying the page description language types serviced by the actual destination, which allows the job to go to the printer which can properly handle it, and allows limiting the types of formats that can get to an AD which has a Transform Sequence that can process only certain formats. Attr: document-formats-supported Formdef Formdefs govern paper size, orientation, position on page, and finishing (stapling). In AFP file, appears in Begin Document Resources area, which governs finishing. Ref: Reference manual, Appendix A GUI: Printer properties, AFP Resources tab, "Form definition" field Formdef, default When an AD is created, a default Formdef will be assigned to it according to its type, per Appendix D of the Reference Manual. Formdef authoring With a tool like PPFA. Formdef directory /usr/lpp/psf/reslib/ Formdef processing hierarchy IPM has to use some Formdef to print the job to an AFP printer. Its hierarchy of choice is as follows: 1. The Formdef specified at the point of job submission, as in the -of flag for the 'lprafp' command, which results in a form-definition attribute being associated with the job. 2. The Formdef specified in the Job/Document Defaults. 3. The inline form definition contained in an AFP job. 4. The default Formdef for IPM's AD. Formdefs library /usr/lpp/psf/reslib/ Formdefs source /usr/lpp/psf/ppfa/ (if PPFA installed) Forms, printer The printer Properties, Forms available Managed via admin GUI, Server -> Properties, Other Forms Flash Unit In the IBM 3800 Model 3 printer, a photographic negative which adds the image of a predesigned form to a sheet of variable data. More modern printing utilizes electronic overlays. Forms ready The forms to use with the actual destination (printer). Under printer Properties, "Load Balancing" tab. FST File Sharing and Transport FST Font Specification Tables. fstsecutil IPM security utility, for managing Access Control Lists. Formal name: FST Access Control List Utility. In /usr/lpp/pd/bin/. Operates on (binary) files within /var/pddir/default_cell/, as follows: - Command ACLs are stored under subdirectory "acl", with name form .acl. - Groups are stored in the subdirectory "acl/groups", where the ACL filename exactly equals the group name. - Queue ACLs are stored under subdirectory "queues", with name form .acl. - Printer (AD,LD) ACLs are stored under subdirectory "printers", with name form .acl. The dir will have initially null entries for all your printers. There is no man page for this command. Invoke with an unsupported option such as -help to get usage info. Options (more fully outlined below): -s Show -m Modify -d Delete "Show" Syntaxes: fstsecutil -s Example: fstsecutil -s pddelete Output: GROUP:admin:r-- Example: fstsecutil -s pdrm Output: GROUP:admin:r-- GROUP:oper:r-- *:r-- fstsecutil -s -c s|p|q where: -c is the category: s server p printer (AD or LD) q queue fstsecutil -s -g Addition/Modification Syntaxes: Add a user to a group: fstsecutil -m -g Add a user to a command: fstsecutil -m -p r|w|d or fstsecutil -m -p user|oper|admin (where user|oper|admin is another way of expressing r|w|d; and note that w and d are meaningless for commands) Add a group to a command: fstsecutil -m GROUP: -p r|w|d Add a user+permissions to a server, printer, or queue object : fstsecutil -m -p r|w|d -c s|p|q or fstsecutil -m -p user|oper|admin -c s|p|q (where user|oper|admin is another way of expressing r|w|d; and note that w and d are meaningless for commands) Add a group+permissions to a server, printer, or queue object : fstsecutil -m GROUP: -p r|w|d -c s|p|q Deletion Syntaxes: Remove a user from a command: fstsecutil -d Remove a group from a command: fstsecutil -d GROUP: Remove a user from a server, printer, or queue object: fstsecutil -d -c s|p|q Remove a user from a group: fstsecutil -d -g Remove a group from a queue: fstsecutil -d GROUP:____ -c q To delete a group, delete each entry in it: when the last entry is gone, the group will go away. The list of all groups is not obtained by this command, but rather by harvesting names from directory /var/pddir/default_cell/acl/groups/ . Deleting an object, such as a queue, clears out the ACL for that object. Ref: Procedures manual: Managing non-DCE security for Infoprint Manager for AIX See also: ACL; Infoprint Manager Security; Security fstshow Utility to view entries in the FST namespace. Invoking with -o shows what intercommunication ports are available in your system, as used by IPM servers. See also: pdinitports Funnel destination configuration model A many-to-one relationship between two or more logical destinations and one actual destination, through a single queue. Ref: Into & Planning manual, chapter Planning for configuration See also: Configuration models G3 ITU-T T.4 G3 Modified Read, a type of AFP compression. G4 ITU-T T.6 G4, a type of AFP compression. G4 MMR A type of AFP compression, as seen in the ps2afpd.log ("G4 MMR, 260"). Gateway Term for a daemon which supplements a server by providing front-end service for a protocol which the server does not inherently have, to interact with a client to make it look like the server is actually providing that service. In Infoprint Manager, the prime example of this is the LPD Gateway, where the AIX lpd daemon process provides LPD protocol service for clients, handing incoming print jobs to the Infoprint Manager server and interacting with the IPM server to service lpq queries. Gateway printer A Windows desktop printer which looks like a typical printer icon, but serves to submit a job to InfoPrint Manager. Genuine IPDS Ricoh trademark for AFP/IPDS support in their printer line: "With genuine IPDS you support many data types including PCL, Adobe PostScript and IPDS with one powerful controller and establish two-way communication with IBM host systems." Ghostscript Freely available, independently developed package for viewing and printing PostScript. Caution: Ghostscript should be considered only a "convenience" package: by no means is it "tight" or full conformant with PostScript. You will find many instances where it will, without complaint, blithely display PostScript files which contain serious errors; or, it may utterly fail to process valid PostScript. Ghostscript has a long history of unreliability. Ghostscript verification of transforms You can use Ghostscript - up to a point - to verify and visualize a PostScript transform. Be aware, however, that it may not conform to all expectations, particularly DSC comments. GIF Graphics Interchange Format, as invented by CompuServe. A standard file format for pictures that have been generated by a computer. Can contain a maximum of 256 colors. GIFs use lossless compression. They are bitmaps rather than drawing objects, but can scale reasonably well depending upon content. GIF files are heavily used as web page elements. Internally, a GIF file starts with the chars "GIF87a", where the second 3 chars represent the version. Following that are the 16-bit width, then the 16-bit height. History: In 1987, CompuServe Corporation created the GIF file format to be used for the storage and online retrieval of bitmapped graphical data. The GIF specification required the use of the LZW algorithm to compress the data stored in each GIF file. In 1984, while working for Sperry Corporation (now Unisys), Terry Welch modified the Lempel-Ziv 78 (LZ78) compression algorithm for greater efficiency for implementation in high-performance disk controllers. The result was the LZW algorithm. Although GIF itself was released as a free and open specification, Unisys maintains a patent for LZW compression. In the 1990s, developers concerned about patent enforcement devised the PNG format, intended as a patent-free replacement for GIF. Usual filename extension: .gif Ref: http://www.gearfactory.com/gifformat.php http://ptolemy.eecs.berkeley.edu/eecs20/ sidebars/images/gif.html http://www.dcs.ed.ac.uk/home/mxr/gfx/2d/ GIF87a.txt http://www.gearfactory.com/jpegvsgif.php See also: PNG GIF sample /usr/lpp/psf/jpeg2afp/sample.gif (a smallish image of a red rose with a winding green stem, on a white background) GIF transform /usr/lpp/psf/bin/gif2afp Beware that the transform likes to print by dots and, at 600 dpi, an image of 845x1156 which looks big on screen (computer display resolution is typically 72 dpi) will be little bigger than a postage stamp when printed. This points out the difficult thing about image files: they have no absolute size - only pixel dimensions. It is best for the user to print them via PostScript, where page and image size can be chosen by the originator. Perhaps the most reasonable thing to do is: extract the X,Y dimensions from the file (dot dimensions) and in the -scale option express the dimensions in terms of points, for a reasonably-sized image; and employ "-fit scale" to deal with oversized results via scaling. You also need to specify margins (-x, -y) to keep the image away from the physical paper edge, and in concert -paper or -w,-l to effect right and bottom margins. Example, leaving 1/4" margins all around letter-size paper: gif2afp -o my.afp -paper 8,10.5i -x 0.25i -y 0.25i -scale 791,790p -fit scale my.gif gif2afp GIF transform (q.v.) /usr/lpp/psf/bin/gif2afp Global job identifier The unique job identifier in Infoprint Manager. Form: ServerName:10DigitNumber Attribute: job-identifier The number consists of two adjacent 16-bit components: - A leading 5-digit number representing the "series". - In V3, that number was based on the time the first job starts in that server - which could be non-unique. - In V4, the number is more random, but is still based upon the start time of the server: if you start two IPM servers at the same time, this number will be the same on both - even if the IPM servers are on different computer systems. - An attached 5-digit job number, 00000 - 65534 . The number seems to be kept only in IPM memory: there is no file which contains the series number or next job number to be used. When the job number reaches 65534, or the server is restarted, the series and job number reset. For example, the job after 3030865534 may be 0646800000. Groups See: Security Group GT10, GT12 EBCDIC coded fonts: Gothic 10-pitch (X0GT10) and Gothic 12-pitch (X0GT12). Not provided with IPM for AIX. See also: ASCII fonts GUI Graphical User Interface, being a windowed, pictorial interface to a facility, often with icons. The IPM Administrator GUI and Operator GUI (q.v.) are examples. They are collectively known as the IPM GUI. As of 2004, the GUI is currently designed to query the server for all jobs when the GUI starts up, and then depend on events from the server to keep in sync when jobs are printed and new jobs are submitted. The start-up imposes a considerable load on the server; and when the server is already heavily loaded, the GUI may fail to sync with the server, and will not thereafter be refreshed, leaving its displayed info static and stale. It is thus possible for the GUI to get out of sync with reality: the GUI will remove a job instance from its repertoire if a query for the job fails to find it (which additionally keeps 5010-505 "cannot find" messages out of the server error.log). The GUIs are *not* extensible by any IBM-defined method. They install into directory: C:\Program Files\IBM\Infoprint GUI\ Uninstalling the GUIs does not remove your personal settings for their use. The GUIs interact with the IPM server by sending OIDs info back and forth, in TCP packets (not SNMP). When the GUI wants to make a change in a resource, it will send an OID and value to effect the change: there is no pdset or like command sent to the IPM server. Msgs: 5010-547, when the GUI starts. (It does not identify the user: you have to examine surrounding 5010-362 and 5010-363 messages to identify the user.) GUI, AIX, performance The performance of the AIX GUI can best be described as "pathetic". Even with a respectable Power processor, it's an exercise in slow motion. You're forced to depend upon the Windows-based GUIs. GUI, loss of synchronization (frozen) The GUI may lose synchronization with the server, which is apparent as printing is happening, but your GUI is not showing any change in number of jobs or progress thereof. You may have to quit and restart the GUI to fix this. Or, you could try going into Options -> Customize and making a trivial change, as to Jobs columns, which may get the GUI resynchronized much faster. Sometimes, the desynchronization is more subtle: you go to get the properties on any job listed in the GUI, and you get a dialog box reporting a job not found - where the job number is something other than the one you selected. This is a case of the GUI remembering a job, but there was some lapse in server-GUI communication such that the GUI did not get the instruction to remove the old job from its memory. GUI and multiple IPM servers If you have multiple IPM servers, you might like to manage them via a single instance of the GUI. However, the GUI is a simple facility which accesses one server at a time, not multiple servers simultaneously. But, a single server can be a gateway to other servers *if* things are set up for multiple servers to combine their operations in what is called an interoperating environment (best described in the Procedures manual). In an interoperating environment, all the servers share the same namespace (typically via NFS directory sharing) - where the namespace is resident on an AIX instance of Infoprint Manager. So, a single GUI view of multiple servers is possible only where the servers are specially configured; and in such an arrangement, the GUI is actually still looking at just one server, which houses all the information which is pooled by the multiple servers. GUI commands The commands are accessed through /usr/lpp/pd/bin/. ipguiadv Advanced Operations ipguiadvadm Advanced Administration ipguiadvs Advanced Operations, special version (to lock its config). ipguibasic Basic Operations ipguibasicadm Basic Administration ipguibasics Basic Operations, special version (to lock its config). All are symlinks to the actual executable, which lives in /usr/lpp/pd/ipgui/, which houses the Java jar files needed for execution. GUI configuration files (common) Installed in the following directory: AIX: /var/pd/gui/ Windows: where GUI was installed These files (both AIX and Windows): ipgui_p.cfg Operations ipgui_p_a.cfg Administration (older) ipgui_pa.cfg Administration (newer) ipgui_c.cfg Basic Operations ipgui_c_n.cfg Basic Admin (These are binary files.) Users can have their own configuration file: Options -> Customize, General tab: in "Configuration to use", click "Separate for each user". GUI configuration files (yours) Windows: Located in like: C:\Documents and Settings\Me as files ipgui_p.cfg, ipgui_pa.cfg GUI filter The GUI provides filtering capability. Why would you use it? One reason is to reduce the amount of information an operator would need to deal with. A more pressing reason is that in a very large printing system, GUI processing could be overwhelmed by the number of changes coming in from the server if it had to be concerned with everything going on in the server. GUI foibles See: GUI, loss of synchronization GUI PC, send a message to IPM provides no means for sending a message to a PC using the IPM GUI, as the administrator might want to do in communicating with operators. GUI performance, optimize - In Customize, Retained Jobs: Do not click box "Display retained jobs in Main window", so as to avoid the overhead of having the main window updated every time a job is added to or expired from the retained jobs list. Also, do not choose column "Delete in", as that imposes considerable overhead in having to continually update perhaps thousands of jobs as their lifetime counts down. - Avoid activating sorting where not needed. - In selecting windows, be sure to select a previously opened window from the bottom of the Window menu. If you open a window from the top of the menu, you get a new window, in addition to the old one, which is added overhead. - Start-up: When you close the GUI application by clicking on the window corner X, your current settings are saved. If you close the Retained Jobs sub-window before exiting, at next start the GUI will not try to initially pull in all the Retained Jobs info, meaning that start-up will be that much faster. GUI performance in starting Launching the GUI can be *VERY* painful, particularly with a heavily loaded server. Here's what I've seen in watching the startup of a Windows Admin GUI from a dual-processor RS/6000 box when the server is doing nothing else (no printing occurring) and several thousand retained jobs: When the "contacting server" message first appears in the GUI window, with its "busy" clock icon, the pdserver process will become the most active, consuming 100% of one CPU. This will go on for maybe 8 minutes, with no ethernet activity reflected in the Windows icon which shows network flow. Then, pdserver will consume 200% (both CPUs) for some 30 seconds, whereafter there will be a lot of intense PC ethernet activity and then the GUI will display. One has to conclude that what the server was busy doing was compiling a data amalgam for the GUI, which it transfered to it when the compilation had been completed. GUI ports The GUI communicates with the following ports on the IPM server: 6874 "psmd" 6875 "pdeventd" GUI sessions, show See: GUI users, show GUI start-up msgs in error.log 5010-426, 5010-427, 5010-454 in the server error.log will reflect the initiation of a GUI session. Here is a GUI stopping and starting: 5010-547 A client GUI has requested to unregister for events from server: *. 5010-547 A client GUI has requested to register for events from server: *. GUI timestamps The date/time values shown in the GUI are relative to the PC - they do not literally come from the server. This means that if your PC clock is mis-set (particularly, wrong time zone or failure to activate Daylight Savings Time), then the timestamps will look wrong. GUI tricks and techniques - To operate on a single item in a list (for example, Jobs) you can simply right-click on it to cause a pop-up menu to appear. (Alternately, you could less quickly left-click on the item, then go to the pull-down menus.) - To select several items in a list (for example, Jobs), click on one, then hold down the Shift key while clicking on the others of interest. Those entries will be highlighted, and you can operate on them as a collection via the pull-down menus. - To select all the items in a list (for example, Jobs), click on one (to focus in that area) then do Ctrl+A. All the entries will be highlighted, and you can operate on them as a collection via the pull-down menus...BUT: the menu action you take applies to each file in turn, not to all at once. GUI users, show In IPM 4.1 AIX, do 'lsof -p ____' on the pdnpmsrv java process ID. In its report look for who's connecting to its TCP port 6795 (the NPM server port). In all IPM 4.x AIX, do 'lsof -i :pdeventd'. GUI version The GUIs fail to specifically identify themselves. The closest you can get within the GUI is to go into the Help menu and select About, which yields the build date, like "Build Date: 11/9/02 9:32 PM". Gutter Printing: The blank area or inner margin from the printing area to the binding. Sometimes called a binding margin. See also: Margins Header page IPM terminology for the identification page which may be produced ahead of the body of the job. This is also called a Start page, or Start sheet. Contrast with: Separator page High speed printer Printer type classified as printing in the range of 117 - 1499 ppm. Previous: Low speed printer Next: High speed printer Hold job 'pdmod -x "job-hold=true" :' Putting a hold on a job that is transforming, as when it very large and taking too much time, will work if the job can make progress toward its next checkpoint, at which time the process then checks to see if a hold has been applied, indicating to the process that it should stop processing the job; but if the transform is not making progress (as due to a PostScript loop), the next checkpoint will not be reached and the process will just keep running, where the only remediation is to perform a 'kill ' on the ps2afpi process. See also: Release job Hold jobs as they arrive Done in the LD, initial-value-job attributes file, job-hold attribute. (Note that there is no job hold capability at the queue level, where you would expect it.) See: job-hold Hot Folder A directory associated with a logical destination. Putting a file into that folder causes it to be sent to that logical destination. Typically, the directory will be like a Windows mapped network drive, or an AIX NFS file system. Files are deleted from the hot folder after submission and server processing of them. By default, jobs submitted through a hot folder use the attribute values in the default document and default job associated with the logical destination. But attributes can be assigned via a correponding .att file, which should be planted before the print file. (Attributes are specified in the file in the same manner as specified via 'pdpf -X'. Notes: Files copied in with a name extension of .stg ("staging") will be ignored. This allows you to safely introduce large jobs without Infoprint trying to handle the job before it has completely arrived: you rename it after it has fully arrived. Ref: Getting Started manual Hot folder location GUI: Logical Destination properties Hourglass destination configuration A many-to-many relationship between model logical destinations and actual destinations, with a single queue in between (hence the conceptual shape and name). Provides both the workload balancing benefit of the pool model and the flexible job- and document-defaulting benefits provided by the funnel model. The hourglass model is the most flexible of the destination configuration models and perhaps the most commonly implemented. Ref: Into & Planning manual, chapter Planning for configuration See also: Configuration models Housekeeping tasks From time to time it is necessary to perform janitorial work to clean debris out of various IPM and LPD directories. Judiciously inspect and remove old, abandoned stuff from the following: - /var/pd// - /var/spool/lpd/ - /var/pd/gui/javacore*,heapdump* See also: /var/psf/interrupt/ HP 4000 Laser printer. DPI: Up to 1200 Speed: 17 ppm PostScript level: 2 (emulation) Introduced: November 1997 Discontinued: May 1999 HP 4050 Laser printer. DPI: Up to 1200 Speed: 17 ppm PostScript level: 2 (emulation) Introduced: May 1999 Discontinued: November 2001 HP 4100 Laser printer. Replacement for the HP LaserJet 4000/4050 series of printers. Speed: Letter size paper at 25 ppm DPI: 600 or 1200 (at full speed) PostScript level: 3 (emulation) Introduced: March 2001 Discontinued: February 2003. HP 4200 Laser printer. Replaced the 4100 series. Speed: 35 ppm Simplex unless optional Duplexer acquired and installed. PostScript level: 3 (emulation) Introduced: December 2002, along with the HP LaserJet 4300 series. Discontinued: June 2005; but the 4200 and 4200dtn in November 2005. Trays: #1 Multipurpose (manual feed) IPM does not see this. #2 First standard 500-sheet feeder tray, built in. IPM sees this a Tray 1. #3 Third, optional tray, installed under the printer. May hold 500 or 1500 sheets. IPM sees this a Tray 2. HP 4250 Circa 2004 45 ppm laser printer. Simplex unless optional Duplexer acquired and installed. Speed: 43 ppm PostScript level: 3 (emulation) Introduced: November 2002 Discontinued: June 2005 Trays: #1 Multipurpose (manual feed) IPM does not see this. #2 First standard 500-sheet feeder tray, built in. IPM sees this a Tray 1. #3 Third, optional tray, installed under the printer. May hold 500 or 1500 sheets. IPM sees this a Tray 2. HP 4300 Circa 2002 45 ppm laser printer. Simplex unless optional Duplexer acquired and installed. DPI: Up to 1200 Speed: 45 ppm PostScript level: 3 (emulation) Introduced: December 2002 Discontinued: June 2005 Trays: #1 Multipurpose (manual feed) IPM does not see this. #2 First standard 500-sheet feeder tray, built in. IPM sees this a Tray 1. #3 Third, optional tray, installed under the printer. May hold 500 or 1500 sheets. IPM sees this a Tray 2. HP 4350 Laser printer. DPI: Up to 1200 Speed: 52 ppm PostScript level: 3 (emulation) Introduced: November 2002 Discontinued: June 2005 Trays: #1 Multipurpose (manual feed) IPM does not see this. #2 First standard 500-sheet feeder tray, built in. IPM sees this a Tray 1. #3 Third, optional tray, installed under the printer. May hold 500 or 1500 sheets. IPM sees this a Tray 2. HP printer, IPDS printing The "IPDS 100" product is a DIMM which installs in an HP printer, causing IPDS to be one of its supported languages, emulating an IBM InfoPrint 21/32/40. www.hpgsc.com/hostprinting Another choice is The Blue Kit: http://www.mpitech.com HP printer, test access See: pjldetect HP printer use with IPM Requires the use of "Colon files" (q.v.). These are AIX environment files which live in /usr/lib/lpd/pio/predef/. Example of such file names for the HP LaserJet 8000 printer: hplj-8000.gl hplj-8000.pcl hplj-8000.ps If necessary, you could try the generic.* specs therein. HP printers reference http://en.wikipedia.org/wiki/HP_LaserJet_4000_series HP printing The way in which printing occurs from an Infoprint Manager server to an HP printer is vague and unobvious. In general terms, such a printer is defined in the server as an AIX DSS, and the job is largely just passed on to the printer in whatever language it was received (PostScript, PCL, ASCII) for the printer to RIP and print it. The AIX back end program will generate PJL instructions to direct printer handling of the job, providing plex and like defaults, but the content of the job has the final say as to processing in the printer. There is no real control provided in the IPM server for it to influence how the job is handled in the printer. If you look at the Media/Bins/Trays tab for an AIX DSS printer in the administrator GUI, you will see no controls for output bin assignment, as the most major thing you would want to control. (In contrast, a PSF DSS allows output bin designation.) Making all this more perplexing is that IPM will send an initial PJL command (@PJL SET OUTBIN = UPPER) to the printer telling to use the main, topside bin by default for job output...this, despite the absence of any way for the server administrator to explicitly control this. (That spec derives from the inscrutable processing of the HP printer model "colon file" by the AIX printing environment commands.) hpgl See: snfrmain HPLIP Hewlett-Packard Linux Imaging & Printing (HPLIP) is an HP-developed open-source Linux solution for printing, scanning, and faxing with HP inkjet and LaserJet printers. As installed, HPLIP's primary elements are device drivers, setup and installation utilities, and a device manager (aka: a toolbox) which provides access to maintenance tools, supplies levels, and status information. RPM package: hplip Installs into /usr/share/hplip/. HRI Human Readable Interpretation, for seeing what a bar code (barcode) means. i Units abbreviation for an inch. IB Two-character Manufacturer Code for IBM. "IBM AFP Printer Driver for Windows" AFP printer driver available for download from IBM. Ends up in a folder named "AFP_Driver". Seen to provide a limited selection of printer models supported, such that the user must most often choose one by printing resolution, like: IBM AFP 600 AFP drivers provide almost no choices for the user: no stapling choice, no duplex choice, etc. (because it is presumed that the application will have generated the AFP code with such instructions embedded). The AFP Driver is thus for AFP applications. As such, it is not feasible to IBM Developer Kit for Windows, Java 2, The Windows identity of the Java which 1.3.1 is installed from the Client CD selection "IBM Runtime Environment for Java 2, 1.3.1" as of at least PTF UR53740C, in Infoprint Manager 4.1. Hovering the mouse pointer over that selection says that it "is used with the Infoprint Manager GUIs (Graphical User Interfaces) and with Infoprint Manager Notifications". Installed in: C:\Program Files\IBM\ Java131\ IBM Developer Kit for Windows, Java 2, The Windows identity of the Java which 1.4.1 is required for the IPM 4.2 GUIs. IBM Infoprint 2105 PS PostScript driver for the IBM Infoprint 2105 printer (obviously). Note that whereas the printer is monochrome, the driver only does monochrome: you cannot use this driver with a color printer (e.g., HP Laserjet 5550) to get color output - you would instead just get grayscale. Will show up in the print job's PostScript prolog as: %%TargetDevice: (IBM 2705) (3011.104) 002 IBM Infoprint 2105ES PS PostScript driver for the IBM Infoprint 2105ES printer (obviously). Note that whereas the printer is monochrome, the driver only does monochrome: you cannot use this driver with a color printer (e.g., HP Laserjet 5550) to get color output - you would instead just get grayscale. IBM Network Printer 24 Cut-sheet workgroup laser printers, 24 ppm, 600 dpi, up to A3 size paper, optional duplex. Quite similar to HP office printers (e.g., HP 4000 series). PDLs: PCL5e (basic); Adobe PostScript Level 2 (optional); IPDS (optional). Discontinued mid-1998. IBM PPDS Refers to the IBM Personal Printer Data Stream. PPDS was development by IBM and was used in older IBM and Lexmark laser printers. IBM PPR Refers to the IBM Proprinter datastream. IBM PPR was developed by developed by IBM, but is used by a number of other printer manufacturers. It is used primarily in dot matrix line printers, but is also used in a number of ink jet printers. IBM printer definitions /usr/lpp/pd/bin/ibmapmtb.cfg IBM Proprinter 1980s dot matrix printer designed and manufactured by IBM to be a low cost printer for use with the IBM personal computer (IBM PC). It was designed for low cost and quick fabrication, omitting screws, springs, pulleys, and belts, utilizing as few parts as possible. In that the printer was for PC use, it was an ASCII printer, rather than EBCDIC. Model numbers: 4201-3, 4202-3, 4207-2, 4208-2 See also: IBM PPR ibmDeptPrinter IBM Departmental Printer, as in configuring AIX via SMIT to create anew printer definition. Icon blacked out Indicates the resource is disabled. Icon red Indicates the resource is in trouble, as with a backed-up print queue. ID IBM internal abbreviation for the Infoprint Documentation team, as seen in PMRs. IM images Are uncompressed raster data images. A raster pattern is composed of a series of pels arranged in scan lines. Contrast with IO images. img2fax The transform for the Email DSS. There is no documentation for invoking it manually. IMM Invoke Medium Map: the AFP command which calls for a Formdef Copygroup, by name. See also: ps2afp output per PostScript factors Impositioning The arrangement of pages so they will appear in proper sequence after press sheets are folded and bound. Infoprint A solution of software and hardware products that can supplement or replace the offset presses and copiers in print shops with high-quality, non-impact, black and white or process color printers. Infoprint takes documents from creation to the published, kitted, and shipped product. Infoprint 12 There is no on-site service for this printer, per IBM Technote P1000052. Infoprint 20 A black and white, large-format, cut-sheet, workgroup laser printer with optional duplexing and 600-dpi resolution. Model number: 4320 Infoprint 21 (4322-001) A black and white, large-format, cut-sheet, workgroup laser printer with optional duplexing and 1200-dpi resolution. 21 ppm. SNMP. Circa 2000/04. PDLs: PCL and PostScript standard; AFP/IPDS optional. Infoprint 32 IBM desktop cut-sheet laser printer, 32 ppm, 600 dpi. Model number: 4332-001 IPDS emulation: 4028, 4332 The Infoprint 1145 carried on the same printer design. http://www.printers.ibm.com/internet/ wwsites.nsf/vwwebpublished/ip32supt_ww Infoprint 40 IBM desktop cut-sheet laser printer, 40 ppm, 600 dpi. Model number: 4332-004 IPDS emulation: 4028, 4332 The Infoprint 1145 carried on the same printer design. http://www.printers.ibm.com/internet/ wwsites.nsf/vwwebpublished/ip32supt_ww Infoprint 60 A duplex, black and white, cut-sheet printer, circa 1998. It was a solid midrange printer for its time, being a floor-standing unit about 2' on each side. DPI: 240, 300, 600 PPM: 60 Languages: Adobe PostScript Level 2; AFP Machine type: 3160 Infoprint 62 A non-impact, continuous-forms printer that runs at a maximum of 62 impressions-per-minute (depending on forms size), and is factory set to run at either 240 or 300 dpi on a maximum paper size of 370.8 mm (14.6 in.). InfoPrint 1107 Machine Type (MT): 2708 Infoprint 1120 IBM machine type: 4520 Infoprint 1125 IBM machine type: 4525 Infoprint 1130 Small workgroup or personal printer, 30 ppm, 1200 dpi, ethernet. Cannot be extended with additional paper trays. IBM machine type: 4530 Infoprint 1140 IBM machine type: 4540 Infoprint 1145 IBM's best desktop, workgroup printer, as of 2003-2005. Very expandable. DISCONTINUED as of 2006/02, replaced by the Infoprint 1585. The 1145 is actually: Lexmark W820. (http://www.lexmark.com/US/products/ overview_/0,6580,MTk2MXwx,00.html) (That the printer is actually a Lexmark is implicit in all the bowing to Lexmark that is done on the backside of the title page of the Setup Guide manual.) IBM machine type: 4545 Speed: up to 45 pages per minute simplex, 38 ppm duplex. Print Quality: 300 x 300, 600 x 600 dpi, 1200 Image Quality image quality Duplexer available separately, or included with the 1145d* model. (The operation of the duplexer is a bit odd: rather than circulating the paper internally, the sheet is partially ejected from the printer to perform the flip. An over-eager user waiting for output at the printer may try to grab the sheet as it makes its appearance, and cause a jam condition.) Configuration tips: With the IPDS option card installed, the printer operates on port 9100 (as most of IBM's 1xxx printers do), not 5001 as with the Infoprint 2105 and other IBM printers larger than the 1145. If enabled for DHCP, you can see the leased IP address by either printing the network setup page, or going into the "STD NET SETUP", where the Set IP Address frame will display the DHCP address in effect at the moment. The clock (date/time) is set under the "STD NET SETUP", where there is a CLOCK MENU, which you can either set manually or, better, point to an NTP server. The date and time can be verified by printing the "Ethernet 10/100" page: UTILITIES menu, "Print Net Setup". DPI: The printer can do 1200 dpi (separately configurable for normal PCL/PS printing and AFP printing); but IPM won't go above 600 in allowable resolution settings. The 145 will post a Tray Low message when the paper tray is approximately twenty-five percent or less full. When printing, the panel shows: Busy IPDS Network When disused for some time, the panel will show like: Power Saver Tray 1 Low See also: IBM site FLASH10133 "Infoprint 11XX Printers, AFP TCP/IP-Attachment Requirements". Infoprint 1145 diagnostics See: Infoprint 1145 problem analysis Infoprint 1145 Maintenance Kit The Infoprint 1145 requires the periodic replacement of parts which wear out. This is a maintenance procedure which is to be performed by the customer. There is a "Customer-Installed Usage Kit", which "Includes a Fuser, Bias Transfer Roller (BTR) assembly and feed rollers". That is, there are parts which wear out and are replaced via a kit, by the customer. A web search on "Infoprint 1145" "rollers" turns up suppliers. The topic is presented in the Infoprint 1145 Reference Guide manual, under "Replacing the items in the maintenance kit". When the installed maintenance kit has been exhausted, the printer will display the following on its control panel: 80 Scheduled Maintenance One can anticipate the depletion by going into the printer's Web page: in Reports, select Menu Settings and then scroll down to Consumable Status", where you will find a percentage value as well as a simple bar graph showing how much is Remaining. Infoprint 1145 microcode/firmware Experience shows that IBM printers ship from the factory with old microcode. For proper operation, the microcode needs to be relatively current. (If not, error code 900 may appear on 1145s from time to time). Microcode updating is not something the customer should do: indeed, IBM does not make microcode updates available to customers - they are downloadable only by CEs who have access to a certain IBM area where an access code is required. The update file will have a name like B2722028f.ffa. The file starts with a special PJL statement which identifies a special RIP and kernel info. The file needs to be fed directly to the printer, via a print job submission method (including the Web page job submission method), when the printer is idle. The best feeding method is from a laptop attached to the printer, which eliminates all network interference. Another method is to FTP the microcode into the printer. This reportedly requires a different file format: .ffj. Experience shows, however, that the printer may be unreceptive to those methods. Infoprint 1145 PostScript is not Adobe The PostScript interpreter embedded in the 1145 is not from Adobe, meaning that exactly what it does and how it performs may exhibit issues. The Setup Guide spells out the distinction... "PostScript 3 is Adobe Systems' designation of a set of printer commands (language) and functions included in its software products. This printer is intended to be compatible with the PostScript 3 language. This means the printer recognizes PostScript 3 commands used in various application programs, and that the printer emulates the functions corresponding to the commands." In short, this is not 'real' PostScript. Ref: Lexmark W820 Technical Reference Infoprint 1145 problem analysis Sometimes, the printer initialization will stop on an error, during Self Test, as for example reporting error: 900 Service RIP Software (aka "900 RIP error") To get more info, have the printer powered off, hold down the Select and Return buttons, and flip on the power switch. This will provide detailed info - but likely only meaningful to a repair person. Power-cycling the printer usually clears the condition, whereafter the printer usually works. Infoprint 1145 web access Nowhere mentioned in the manuals, the printer provides a comprehensive, frames-based web interface! (By default, it uses Java.) Therein you can make configuration changes which the printer control panel provides no means of entering, such as a Restricted Server List. (If the printer is in Power Saver mode, going at it through the web interface will not bring the printer out of Power Saver mode.) There is no Help function in the web facility for this printer, as there is for the 2105, for example. In general, the interface seems to be incompletely developed - which would explain it not being published. You can set a printer password via the web interface: it is for administrative access, and does not affect print job submission from IPM or the interface's own job submission method. Warning: If you set a password via the web interface, but then forget it you're hosed... doing a Reset To Factory Defaults does *not* clear the password! Restricted Server List: Set via the web interface, governs both job submission and web page access - so be careful, to avoid locking yourself out! The printer's web page is, like other IBM printer web pages, organized into frames, where the left side presents a 2-line window of the printer front panel, and thereunder is a function selection. The home page reports Emulations, Print Speed, Inputs, Outputs, Connectivity, Other Features, Print Server, Contact / Locaton. URL path = home. In the left frame menu list: "Print" Allows you to print a file from the PC in which the browser is running, by entering a file name or browsing for one. Works with Windows Internet Explorer, but not Mac Safari. In any case, the function is of little value, considering that you really want jobs going through IPM. But beware users discovering this web page and using it to submit jobs subversively - which will appear outside your usual printing regimen (e.g., without a separator page, and with no print accounting). There is no provided way to restrict access to this function. "Configuration" Allows you to reconfigure the printer. You don't want civilians to have access to this function, so be sure to apply a password to your printer. URL path = port_0/config "Reports" When this works, it shows: Printer Menu Settings Reports paper sizes, various menu settings, page count, Maintenance Kit percent remaining, printer processor info, IPDS info. TN3270E/TN5250E TN3270E Connection Status TN5250E Connection Status Print Server Print Server Setup Page This is one worth seeing, as it reports the printer's network settings. NetWare Setup Page URL path = port_0/reports "Job History" Causes the display of four boxes, arranged left to right, top to bottom, containing info on the four most recent printing sessions. Though its name leads you to believe that you will see the most recent discrete jobs incoming from Infoprint Manager, what each box actually reports is an unbroken printing session of one or more jobs; that is, all contiguous printing between Ready (rest) states. Note: Under the boxes may appear the warning "Your Browser doesn't have Java Support", as with a Mac Safari browser, but it may merely be the case that the browser uses a Java which the printer web server is not programmed to handle: it may still work fine, as Safari does. "Links & Index" Just what the name says: Helpful links (no entries programmed into it yet) and helpful links to areas of the interface. URL path = port_0/links Printing the page: You may not be able to print this web interface page: because it's active java, your PC may balk at the attempt. What you can do is use a screen capture method to grab an image the then have your way with that. Infoprint 1312 Small workgroup or personal printer, 2003/04/15. Up to 20 ppm, resolution up to 1200 dpi, simplex printing, PCL 6, PostScript Level 3, PPDS, optional ethernet. Not an IPDS printer. Infoprint 1412 Small workgroup or personal printer, current as of 2005/06/30, now discontinued in favor of the 18xx series. IBM machine type: 4547 Speed: Up to 27 ppm Resolution: Up to 1200 dpi Duplex? No, simplex only. Datastreams: PostScript Level 3, PCL 6, PPDS. (Not an IPDS printer.) Connectivity: USB; parallel; 10/100 Ethernet. Infoprint 1572 Workgroup printer, announced 2005/07/12 and available 2005/09/02. $1348. Speed: Up to 50 ppm Datastreams: PostScript Level 3, PCL 6, IPDS (card). Duty cycle: 250,000 impressions/month (max) Infoprint 1585 Workgroup printer, announced 2005/07/12 and available 2005/09/02. Effectively replaces the Infoprint 1145. $3106. IBM machine type: 4539 The 1585 is actually: Lexmark W840, where the W denotes the ability to print on wide paper. (Lexmark price: $2,299) And the Xerox 5500 is the same basic printer, with a different control panel, firmware, and software. Speed: Up to 50 ppm Resolution: Up to 2400 dpi (superb!) IPDS printing optional, via installable card. Datastreams: PostScript Level 3, PCL 6, IPDS (card). Duty cycle: 300,000 impressions/month (max) Toner Cartridge Capacity: Approximately 30,000 Pages at approximately 5% coverage. (The printer Web page reports Toner Status - which may not be very accurate: after printing only a few pages, it dropped from 100% to 90%.) Ports: 9100 (common for PostScript and IPDS printing) and 5001, for IPDS only. Lpr submission queue name: /prt0 Input trays (per its IPDS manual): PRINTER IPDS IPM IPM NAME NUM. NAME BIN# "Tray 1" 0 Tray 1 1 "Tray 2" 1 Tray 2 2 "MP Feeder" 98 Tray 3 3 "Manual Paper" 99 manual 100 "Manual Env" 64 manual-2 101 The tray used first is controlled by the Paper Menu > Default Source, which is conventionall set to Tray 1. The setting can be verified via the printer web page Reports > Device Settings; or via a PJL VARIABLES query, where the LPAPERSOURCE values says what it is. The printer has a Web interface, with a dynamic interface (CGI), whereby the printer refreshes the browser windows at irregular intervals. The Web page lacks a means to print a PC file to the printer. Via the interface, you can click a box to activate "Duplex": this causes configuration pages, printed from the control panel, to print on both sides: it does NOT force host-sent simplex print jobs to be duplex. AIX printing: rq = /prt0 IPM support: Did not arrive until about 14 months after the 1585 product was released. Apply IPM 4.2 PTF5 to have "Infoprint1585" show up as a selectable Model in the Create PSF TCP/IP Printer dialog. Parts replacement: To ensure print quality and to avoid damage to the printer, the printer stops operating after the photoconductor (PC) kit has reached approximately 60,000 pages (Letter/A4), with panel message: 84 Replace PC Unit There is also a Usage Kit. Ref: User's Guide (S510-4133) Follow-on model: Infoprint 1985 See also: PC; Usage Kit Infoprint 1585 and HP PJL There is no reason to expect this IBM printer to support HP PJL - but it does! (And, there is no documentation of such support.) For example, if you telnet to its 9100 port number and enter: @PJL INFO ID it will respond with: "IBM Infoprint 1585" And it responds to other PJL commands with equal compatibility, such as: @PJL INFO STATUS @PJL INFO PAGECOUNT @PJL INFO VARIABLES @PJL INFO USTATUS Infoprint 1585 as a PostScript printer For best printing, one should add an IPDS card to a 1585; but a 1585 can certainly be used as a "PostScript printer". In doing so, employ an AIX type DSS, and define its model as an HP 4000 for best results: this is because the 1585 understands PJL, and as such can offer the best results when driven in that manner. When driven in this manner, printing will happen as follows: - IPM will send "PJL INFO USTATUS" to the printer, and look for a USTATUS results response, to assure a PJL printer. (Note that this is what the pjldetect command does.) - IPM will send requests for unsolicited status, for page-end and job-end: @PJL USTATUSOFF @PJL USTATUS JOB = ON @PJL JOB NAME = "JOB 2147483647" @PJL USTATUS PAGE = ON (The 2147483647 is sent for all jobs; has nothing to do with specific job.) - IPM will send job settings, per the job attributes: @PJL SET RESOLUTION = 600 @PJL ENTER LANGUAGE = POSTSCRIPT statusdict begin true setduplexmode 0 setpapertray end @PJL EOJ NAME = "JOB 2147483647" - The printer gets started on the PS job (which is still in the process of being sent to the printer) and sends back "Start of Job Notification": @PJL USTATUS JOB START NAME="JOB 2147483647" - The printer will therafter reach the end of the incoming job, receiving: @PJL EOJ NAME = "JOB = 2147483647" ^[%-12345X whereupon it will respond with: @PJL USTATUS JOB START - Upon finishing page 1, printer sends: @PJL USTATUS PAGE 1 - Upon finishing page 2, printer sends: @PJL USTATUS PAGE 2 - Upon finishing page 3, printer sends: @PJL USTATUS PAGE 3 - Finishes final page 4 of job, sends: @PJL USTATUS PAGE 4 @PJL USTATUS JOB END NAME="JOB 2147483647" PAGES=4 - IPM tells the printer to discontinue returning unsolicited status by sending: @PJL USTATUSOFF Be sure to set Print Timeout to 0 in the printer, to keep the printer from artificially failing large print jobs, thus causing IPM to retry the jobs, where you end up consuming reams of paper in endless reattempts. Note, however, that the PostScript interpreter in the 1585 is an emulator - not true Adobe. As such, it is not as capable, and can end up taking an inordinate amount of time to render a page, making for timeouts. Infoprint 1585 errors 900.43 Service / RIP Software Seen when the embedded PostScript interpreter is working a job, but it encounters something which it cannot handle. Tend to hang the printer. Infoprint 1585 finisher An optional unit (bigger than the printer itself!) which attaches to the right-hand side of the printer. It has a total stacking capacity of 3500 sheets: 500 sheets in Bin 1, 3000 sheets in Bin 2. Part number: 39V0945 There is a pre-requisite of either the 2 x 500-Sheet Drawer (part number 39V0943) or 2000-Sheet Dual Input Duplex Unit (part number 39V0944), so as to boost the elevation of the printer so that its output is at the right height to match the input side of the finisher. There is a bridge assembly to connect the printer output and finisher input, to get sheets across that gulf, given that the printer outputs from its left side. (The bridge of course provides one more opportunity for paper jams.) Provides the capability to staple and/or punch print jobs. Or, stapling and punching can be left off so as to have the finisher serve as a high-capacity stacker: up to 500 sheets in the upper stacker (Bin 1), and 3000 in the lower (Bin 2). The output "bins" are actually elevating trays. Bin 1 is for simple stacking, where neither stapling nor punching is done. Where stapling or punching are done, output is from Bin 2 only. The stacking can be offset, if desired. The stapler can handle 40 - 50 sheets. The minimum size print job which will support stapling is 2 sheets. The punch capacity is unknown. Without a finisher, paper emerges from the printer into its topside Standard Bin, which handles some 500 sheets. (It may be seen reported as 300 sheets.) The IPM GUI reports the output bins as follows: For a 1585 without a finisher: BIN NAME BIN NUMBER WHICH IS 1 1 Topside bin For a 1585 with a finisher: BIN NAME BIN NUMBER WHICH IS 1 1 Topside bin 2 2 Fin. stacker 3 3 Fin. stapling In IPM, GUI label "Default output bin" (attribute output-bin) can be set to one of these numbers. Staples are provided in cartridges, each holding 3,000 staples. When the quantity is down to about 20 staples left in the cartridge, a Load Staples alert appears. Note that setting "Staple Job" to Off in the Finishing menu has no effect on IPDS jobs going through the finisher, where they will still call for stapling. (But leaving the stapler empty will allow the jobs to go through and stack, with there only being a warning on the printer control panel.) Punching obviously results in the production of a lot of small paper circles, which are collected inside the finisher, which must be periodically emptied. Control: When the finisher is connected to the printer, the printer control panel and web page Finishing menu will additionally have the items: FINISH. CHOICE POSSIBLE VALUES Staple Job Off (default) Auto Front Back Dual Hole Punch Off (default) On Hole Punch Mode 2, 3; 2, 4 Offset Pages None (default) Between Copies Between Jobs Bin linking: The bin sequence for linking always starts with the standard bin and proceeds from the bin nearest to the floor to the bin farthest from the floor. Status: The addition of a finisher to the 1585 does not seem to result in a separate status indication for the finisher, unfortunately. You may see the printer icon yellow, which status from IPM indicates that the printer is "out of toner" (IPM message "5010-840 Printer _____ is out of toner."). However, the printer web page says that toner is fine. By doing a Check Status in IPM, and then "More information", the condition is further qualified in brackets as: The printer is out of toner. [Staples Empty or Misfed] which is further info not revealed elsewhere, and which is the real reason. Likewise, when the 1585 needs its Maintenance Kit replaced, the qualified message will be: The printer is out of toner. [80 Scheduled maintenance advised] where what appears in brackets is what is shown on the printer panel. Infoprint 1585 Maintenance Kit The Infoprint 1585 requires the periodic replacement of parts which wear out. This is a maintenance procedure which is to be performed by the customer. There is a "Customer-Installed Usage Kit", which "Includes a Fuser, Bias Transfer Roller (BTR) assembly and feed rollers". That is, there are parts which wear out and are replaced via a kit, by the customer. A web search on "Infoprint 1145" "rollers" turns up suppliers. The topic is presented in the Infoprint 1145 Reference Guide manual, under "Replacing the items in the maintenance kit". When the installed kit has been exhausted, the printer will display the following on its control panel: 80 Scheduled maintenance advised One can anticipate the depletion by going into the printer's Web page: in Reports, select Menu Settings and then scroll down to Consumable Status", where you will find a percentage value as well as a simple bar graph showing how much is Remaining. To reset counter: After installing the parts, you should reset the maintenance counter. To do so: hold down on the right key and the checkmark key while powering the printer on. You will see the "Config Menu" load. Select "Reset Maint Cnt" and hit the checkmark key. Infoprint 1585 password reset The standard menu system on the printer provides no means for resetting the password in the printer. To do so: Hold down on the right key and the checkmark key while powering the printer on. You will see the "Config Menu" load, wherein you can choose to reset the password. Infoprint 1585 PostScript is not Adobe The PostScript interpreter embedded in the 1585 is not from Adobe, meaning that exactly what it does and how it performs may exhibit issues. The User's Guide spells out the distinction... "PostScript 3 is Adobe Systems' designation of a set of printer commands (language) and functions included in its software products. This printer is intended to be compatible with the PostScript 3 language. This means the printer recognizes PostScript 3 commands used in various application programs, and the printer emulates the functions corresponding to the commands." In short, this is not 'real' PostScript. In practice, we have found the printer taking half an hour to rasterize a PostScript page which transformed quickly in Infoprint Manager. Ref: Lexmark W840 Technical Reference Infoprint 1585 print drivers Available at infoprintsolutionscompany.com. As of 2010, ISC seems to have moved away from "IBM Infoprint" type drivers to instead use the OEM (Lexmark) drivers. They can be found as IBM site Web documents with the title "InfoPrint 15xx/16xx/17xx PCL/PostScript Universal Drivers Version 1.6", document number P4000924. Installs into C:\PRINTER\DRIVERS\UNIVPS\ The PostScript prolog will contain the following identifying lines: %%TargetDevice: (Lexmark Universal PS3) (3010) %%LanguageLevel: 3 %%Lexmark PS System Driver Version: 3.0 --------------------------------------- Earlier drivers: The name of the downloaded file will be ibm_aau-multiwin_drivers_en.exe which includes both PCL and PostScript, where you choose to install one or the other. Will install into c:\IBM\Drivers\ like c:\IBM\Drivers\LCS\en\iiabpmui.dl_ The driver name will be: IBM Infoprint 1585 PS3 As is the case with Windoze, the PC needs to be restarted to put the printer drivers into effect. Note that there is a Universal Driver available, which is suitable for all workgroup level printers. Note: DO NOT use the LEXPSNT3 Lexmark printer driver which may arrive on a CD with the printer, as that driver will result in inordinate job failures with Infoprint Manager. Infoprint 1585 standard bin Is the output area at the top of the printer, intended for "grab output" service, as in on-demand printing rather than production stacking. Official capacity: 500 sheets; but 300 if finisher unit is added. Infoprint 1585 timeouts For PostScript printing (not IPDS or PCL), the printer firmware has a set of timeouts... Screen Timeout Specifies the number of seconds the printer waits before returning to the home screen. Default value: 30 Print Timeout Number of seconds a print job executes before it is terminated and a PostScript emulation timeout error is generated. Put another way, it is the amount of time the printer waits for an end-of-job message before canceling the remainder of the print job. Set it to 0 to disable job timeout. JobTimeout is initialized to the value of the JobTimeout system parameter at the beginning of each job. Default value: 90 Wait Timeout Number of seconds the interpreter waits to receive additional characters from the host before it terminates the current print job by executing a PostScript emulation timeout error. A value of 0 indicates an infinite timeout. WaitTimeout is initialized to the value of the WaitTimeout system parameter at the beginning of each print job. Default value: 40 Network Job Timeout (Job Timeout) The value in seconds to which the user parameter JobTimeout is initialized at the beginning of each print job. If you set the system parameter JobTimeout to a negative value, it is ignored and the previous setting of JobTimeout is used. A value of 0 (zero) indicates that the timeout is infinite. If you set a number between 1 and 14, 15 is set. Default value observed: 90 Infoprint 1585 web page elements The printer panel image, shown at the top left of the page, is a bitmap, its URL path being /cgi-bin/dynamic/config/panel.bmp InfoPrint 1832 45 ppm printer in the 1832,1852,1872 model set. Introduced 2008/10. Machine type: 4551 Max duty cycle: 200,000 pages/month. InfoPrint 1852 50 ppm printer in the 1832,1852,1872 model set. Introduced 2008/10. Machine type: 4552 Max duty cycle: 225,000 pages/month. InfoPrint 1872 55 ppm printer in the 1832,1852,1872 model set. Introduced 2008/10. Machine type: 4553 Max duty cycle: 275,000 pages/month. Infoprint 1985 Follow-on to the Infoprint 1585, with essentially the same specifications and dimensions. In fact, the 1985 accepts the 1585 toner cartridge and photoconductor unit. Announced October 13, 2009. Speed: Up to 50 ppm Processor: 800 MHz Memory: 256 MB standard; 1280 MB max Resolution: Up to 2400 dpi (superb!) Machine type: 4856 Is actually a Lexmark W850. IPDS printing optional, via installable card. Datastreams: PostScript Level 3, PCL 6, IPDS (card). PJL: Like its 1585 predecessor, the 1985 honors PJL commands Duty cycle: 300,000 impressions/month (max) Ports: 9100 for PostScript 5001 for IPDS (Note: Attempting to use port 9100 for IPDS results in garbage.) I suspect that the 1985 represents Ricoh/ISC having fully acquired the Lexmark W840 that was the OEM source of the 1585, which Ricoh/ISC then tweaked for their own manufacture. This surmise is supported by there no longer being anything resembling this printer on the Lexmark site. The MultiPurpose Feeder is the flip-down on the left. Paper size in it is not detected: you have to set Paper Size and Paper Type for the multipurpose feeder. On the panel, there is a Configure MP menu choice. Also check that the Default Source setting is approprite. Tray linking: When the Paper Size and Paper Type settings are the same for any trays, the trays are automatically linked. Query inaccuracies: - If the photoconductor is used up, the printer will superficially report that to servers as toner exhaustion. Web pages tasks: Restart printer: Reset Print Server Date/time: Set Date and Time Web pages notes: - Toner consumption is shown as a bar graph, but not Photoconductor (PC Kit) or Maintenance Kit. Infoprint 1985 finisher See: Infoprint 1585 finisher Infoprint 2000 Cut sheet printer series. The model 2000 specifically is a high duty cycle, large printing system running up to 110 ipm, with print densities of 240, 300, and 600 dpi. The 2000 is a commercial printing system, featuring a print engine (Digimaster 9110 from Heidelberg) with a straight-through paper path (as contrasted with the "race track" path of the 2085/2105 midrange). Infoprint 2060ES New mid-range IBM printer, announced 2003/11. Based upon the Ricoh Aficio 1060. DPI: 600 IPDS; 600 or 1200 for PCL, PostScript, and PDF. Print/copy speed: 60 ipm Up to 300,000 imp./month 800 MHz PowerPC 750FX processor. 40GB hard drive; 10/100/1000 BaseT Ethernet; 512 MB RAM; optional Token-Ring, up to 1.0 GB optional memory; optional wireless Price: $22,000 Infoprint 2075ES New mid-range IBM printer, announced 2003/11. Based upon the Ricoh Aficio 1075. DPI: 600 IPDS; 600 or 1200 for PCL, PostScript, and PDF. Infoprint 2090ES Successor to the Infoprint 2085, announced 2003/11. Based upon the Ricoh Aficio 2090. Infoprint 2085 85 ppm printer introduced 2002/04/31. Based upon same Ricoh printer as the model 2105. For driving from an AIX system, the printer comes with a pioibmdpm backend, to be used instead of the usual backends that are supplied with the IPM server (pioibmnpm, pioinfo). Note that web access to the printer works as long as Main Power is on in the device, even if engine power is turned off. IBM replaced the Infoprint 2085 with the Infoprint 2090ES, 2003/10/26. See also: pioibmdpm Infoprint 2085 "machine type" 2785 Infoprint 2085/2105 controller The controller consists of a card and processor, OS memory. All IBM controllers are now p-series processors (RS/6000). The 2085/2105 processor is a 500 MHz PowerPC 750L. The operating system used is a Unix called VxWorks, an embedded real-time OS (RTOS) by Wind River Systems (windriver.com) - the same operating system used on the Mars Spirit rover. Infoprint 2085/2105, reboot Panel: User Tools -> Printer Features -> Reset tab -> Reboot Printer Will result in the printer shutting down, then entering an Initializing state. Infoprint 2085/2105, reboot with job If the 2085 printer is rebooted and at active the time is processing a print job, you will thereafter get: Error 207 Paper in finisher. Open finisher cover and remove paper. Infoprint 2085/2105 capabilities Printer Home Page. Will contain like: Maximum speed: 85 Maximum resolution: 600 Duplex installed: Yes IPDS installed: Yes PS installed: Yes PCL installed: Yes Stapler installed: Yes Punch installed: No Infoprint 2085/2105 date and time, see Via web interface, Admin area, View Details, Printer Configuration Page which shows the date and time. Infoprint 2085/2105 date and time, set Via web interface, Admin area, Network Settings, Time of Day. Best settings: Time Source: Network Automatic Daylight Saving Time Settings: Adjust Using Rule Infoprint 2085/2105 device driver aixdpnls, the IBM Infoprint 2085/2105 PostScript, PCL5e and PCL6 Printer Drivers and Utilities for AIX 4.3x and AIX 5.1 Infoprint 2085/2105 duty cycle The IBM Infoprint 2085/2105 printers have an official duty cycle of 800,000 pages per month, with a "sweet spot" of around 500,000 (according to its product developer, based upon testing performed by IBM to predict service intervals). The "sweet spot" number is the level at which the printer delivers high volume while assuring reliability. Over-working the printer makes for excessive internal heat, which causes toner to "cake" inside its supply bottle. Infoprint 2085/2105 header page Network Settings: Printing Details: set "LPD separator page" to On. Infoprint 2085/2105 job queueing, Printer Settings: Storage Management, suppress Spool jobs to hard drive: When required (rather than When possible). Infoprint 2085/2105 Job Status web Displays current and recent jobs. page (The latter lingers for aabout one minute, to provide that additional perspective for a short time.) Columns: Job ID User-Host Name Job Name Status Done Spooling Printing (Includes RIP: watch Size value climb) Size Job Time Copies Waiting to print Infoprint 2085/2105 pages printed Go to the printer web site... Under View Details: Network Configuration Page, see the System Configuration section, and its Page Count. Infoprint 2085/2105 paper supply Printer Home Page. status Infoprint 2085/2105 port numbers The printers use the following TCP/IP port numbers for interaction: 80 IPP printing. 515 LPD printing. (Service name: "printer") 631 IPP printing. 2501 Raw printing port. (Used by most IBM Network and Infoprint printers for PCL and PostScript.) 2601 ??? (Present in the Network Config printer web page, but unexplained in any doc. Possibly equal in function to 2501?) 5001 IPDS printing, as from IPM. 9100 Raw printing port. (Equal to number used by HP printers.) Attr: destination-tcpip-port-number Ref: IBM Infoprint 2085/2105 Ethernet and Token Ring Configuration Guide Infoprint 2085/2105 PostScript One thing to watch out for in printing PostScript via direct submission to these printers is that there exists no "Font Substitution" choice, indicating that if a job calls for a font which does not reside in the printer then the job will print with empty space where that text should have appeared. Infoprint 2085/2105 printer status Printer Home Page. Will contain like: Name: IBM Infoprint 2085 IP address: 128.197.2.34 E-mail address: Not Set Location: Contact: Jobs waiting: 0 Toner: OK Infoprint 2085/2105 staple trimming If you are observant, you will have noticed that the stapling of jobs is uniform: same staple head width on the frontside, same distance between staple points on the backside - regardless of the thickness of the job. In that the staples are a fixed length on the supply coil, that implies that the printer is doing trimming. Indeed, if you examine the bottom left interior of the printer you will find a lot of staple trimmings on that floor. Staples are trimmed to a uniform length after penetrating the sheets, and the trimmings are supposed to fall into a black plastic collection bucket toward the back of the printer. (Some miss their mark.) Note that if this trimmings collection bucket fills, it can cause the printer to stop, and emptying it is officially an IBM CE task, though easily accomplished by a customer with a flashlight. Infoprint 2085/2105 stapler empty With the initial version of the firmware behavior (~ Fall, 2002), when the stapler ran out of staples, the printer was disabled: no further printing of any kind could occur...the printer was adamant that it get staples before it did anything further, and so jobs queued in the printer could be trapped there. With the version of the firmware available in 2003/03, under Printer Settings : Printer Configuration there is new opton Stapler Empty: it defaults to "Stop"; but "Continue" may be chosen. Infoprint 2085/2105 staples Ricoh EDP Code 316543x5 No.1101R Infoprint 2085/2105 stapling Printer Settings, Paper Configuration, "Staple:". Sets the default stapling location, which is to say that it allows you to turn turn stapling off, or on and specify the stapling position(s). This setting appears only when the staple feature is installed. Choices: Off 1L Slant P 1L Vert P <=== Most common 1L Hor P 2 Left P 1L Slant L 1L Vert L 1L Hor L 2 Left L 1R Slant P 1R Vert P 1R Hor P 2 Right P 1R Slant L 1R Vert L 1R Hor L 2 Right L 2 Top P 2 Top L Conventional choice, for ordinary stapling: In upper left corner, vertical staple: 1L Vert P Note that in LPD submission where LPD separator page production is configured, the separator page will *not* be stapled to the body of the job. Stapling overrides offsetting (as stated in printer User Guide, User Tools (Printer Features), Settings Menu). The Infoprint 2085/2105 can staple ("finish") about 80 sheets. If the job calls for stapling but is too large, the printer handles this by spewing out the blob of sheets that it had accumulated to staple, and will restart accumulating. The last accumlation, at the end of the job, will likely be small enough such that only that blob will get stapled. Infoprint 2085/2105 stapling capacity Observed to staple 85 sheets, which is impressive. Infoprint 2085/2105 status light Off: Ready, no current job; or Main power off Green, solid: A printer or copier job is active. (Once the job finishes, the light should go out.) Green, flashing: Sanning originals. Amber: Error condition. Note that the printer's firmware is not programmed to light Amber if paper tray 1 is not properly seated - a common operator failing which can stop the printer from operating. Infoprint 2085/2105 status light, Panel: System Settings -> activate General Features -> Status indicator Infoprint 2090ES Successor to the Infoprint 2085, as of 2003/10/26. Based upon the Ricoh Aficio 2090. DPI: 600 IPDS; 600 or 1200 for PCL, PostScript, and PDF. Maximum monthly usage: 800,000 images Infoprint 2105 105 ppm printer introduced 2002/04/31. Based upon same Ricoh printer as the model 2085. 500 MHz PowerPC 750L processor; 10GB hard drive. No PJL support. IBM's Machine Type for this printer is 2705. For driving from an AIX system, the printer comes with a pioibmdpm backend, to be used instead of the usual backends that are supplied with the IPM server (pioibmnpm, pioinfo). IBM replaced the Infoprint 2105 with the Infoprint 2105ES, 2003/10/26. Green light: Comes on when the printer is receiving a job to be printed. Does not necessarily go off when the job completes: the destination-release-timer value may cause it to stay lit for some time. Known problems: A knurled, green-handled gear shaft located in the stapler assembly allows the operator to rotate the stapler mechanism by turning the knob. But a fundamental mechanical engineering no-no by Ricoh causes a retaining pin hole through the shaft to be too large relative to the diameter of the shaft, severely weakening it and resulting in inevitable breakage. The part has no number on it, and the CEs apparently have no subassembly diagrams to identify it, resulting in verbal charades as they try to describe it over the phone to their supply depot, not to mention much wasted time. (The IBM part number for this is 010R3103; the OEM part number is B3024274.) See also: Infoprint 2105ES; pioibmdpm Infoprint 2105 Billing Pages count The printer itself tallies page counts, as seen in its Printer Configuration Page web page, items Print Counter-Total and Print Counter-Billing (which are seen to have the same values). So what are these numbers? They are "passes": when one side of a sheet passes through the imager, the tally is incremented to reflect this work done by the printer, which helps account for wear. How does the printer number correlate to IPM server accounting numbers? In simplex (one-sided) printing, there is a direct correlation: both the printer and server count the pages the same. In duplex (two-sided) printing, each side passed through the imager is counted - and that results in a difference from the server accounting numbers where the job contained an odd number of pages: In this case, the backside of the last sheet will be empty, but it still represents work done by the printer, and so the printer still counts it. Thus, a 7 page duplex document will be counted as 7 pages by the server, but 8 by the printer. See also: Clicks (printer billing counter) Infoprint 2105 experience Our experience with the 2105: - Duty cycle: The 2105 can meet its 500k pages per month "sweet spot maximum" if the printer receives regular preventive maintenance (PM). - Paper jams: Happen, largely due to sensor defects/failures. - Print quality: Excellent, usually, but will develop streaking after a lot of printing, requiring CE attention. (The CEs talk of a mythical automatic print quality adjustment, but there has been no evidence of it in reality.) - Speed: Right up there, meeting its published specs. (Some other printer vendors will hype speed ratings in their brochures - which their printers never actually achieve.) Infoprint 2105 paper tray numbers In the main unit, the trays are numbered 1, 2, 3, from top to bottom, with Tray 1 being the double-size one. If the optional sheet input unit is purchased and attached to the right side of the printer, its three additional trays are further numbered 4, 5, 6, from its top to bottom. See also: Media ready; psf-tray-characteristics Infoprint 2105 PCL6 driver for Downloads as file wxpp6enu.exe Windows 2000 and XP which you then invoke to install the driver, selecting 2085 or 2105. The driver name, for the LD Properties area is: IBM Infoprint 2105 PCL6 Infoprint 2105 PS driver for Downloads as file wxppsenu.exe Windows 2000 and XP which you then invoke to install the driver, selecting 2085 or 2105. The driver name, for the LD Properties area is: IBM Infoprint 2105 PS Infoprint 2105 web server, determine Telnet to printer port 80 and send: GET / HTTP/1.0\n\n and as of 2003/02 get back: HTTP/1.0 200 OK Connection: close Server: WindWeb/1.0.2 Date: THU JAN 01 09:41:12 1970 (WindWeb is a former product of Wind River Systems, www.windriver.com, now proWeb/HTTP, sold under label WindWeb HTTP Server by 3Soft, www.3soft.de) Infoprint 2105ES Successor to the Infoprint 2105, as of 2003/10/26. IBM part number: 2706. Based upon the Ricoh Aficio 2105. New features include a boost of the maximum dpi from 600 to 1200, and increased duty cycle (facilitated by heavier bearings and different page handling (registration)). One surprise is that the printer controller has been externalized: there is now a small cart attached to the back of the printer, on which sits a non-descript tower PC (IBM part number 17R8119 - not found on the IBM website); comes in a box from Foxconn, saying model TH-02, which is a generic PC. With that external PC, it is more important to shut off power in a "soft" manner, rather than by the "big red switch". Printing languages: PCL and PostScript via the PCL/PostScript feature (q.v.). No PJL support. DPI: 600 IPDS; 600 or 1200 for PCL, PostScript, and PDF. Internal Web server: Type: WindWeb/1.0.2 Protocol: HTTP 1.0 Wants request to be GET rather than HEAD. Maximum monthly usage: 1,000,000 images Issues: The printer controller has an oddball NIC, which fails to work properly when configured to 100 mbps full-duplex to match the network switch setting. Instead, the printer has to be set to autonegotiate, and *then* it will operate at 100 mbps full-duplex! Setup tips: - Go into the printer's Web page as Administrator, go into Network Settings, Time of Day, and select Time Source = Network Automatic, Time Zone to reflect your offset from GMT, and Daylight Savings Time Settings, Adjust Using Rule as appropriate for the DST GMT offset adjustment. Job submission queues/ports: For LPD printing, the printer has certain queue names, as follows: "TEXT" For ASCII printing, where the job consists of simple lines of text where each line has a CR and LF at the end. The printer will perform basic print formatting. Such print jobs cannot have long lines, and the printing of images is not possible. It is better to use PostScript. "PASS" Is for PostScript and PCL, where the job stream is passed to the printer's page description language interpreters for processing. For IPDS printing, no queue names are possible. Instead, jobs must be streamed to TCP port number 5001. For IPP printing, no queue names are possible. Instead, jobs must be submitted to TCP port number 631 or 80. Note that port number destinations are problematic for AIX printing in that remote submission is via rembak, which has no provision for port numbers. Infoprint 2105ES click charges Like other printers, the 2105ES internally accounts for pages printed, for purposes of tracking wear and measuring usage relative to the terms of the printer maintenance contract. You can see the counter by going to the Printer Configuration Page where, in the Info section, Print Counter-Total holds the count value. This printer accounts for every page side which passes through its imager - a behaviour which has some ramifiactions: If a three page job is printed duplex (double sided), the backside of the last sheet is necessarily blank. This printer counts that last blank side just as it does sides that it actually had to image, and so would advance the counter by 4 for such a job. Infoprint 2105ES "Job History" An element in the left pane of the printer Web page. Its report has the following fields: Job ID; User-Host Name; Job Name; Status; Time; Pages. Job ID is a job number generated by the printer for identifying the job: it has no correlation to any job number that the host may be using for the job. The field contents actually mean something when the printing is PostScript type, where jobs are individually queued and separately processed in the printer. IPDS printing is very different, where jobs are *not* queued in the printer, but rather job data is streamed to the printer, synchronously. In this case, the User-Host Name and Job Name columns both say "IPDS". In IPDS printing, a "job" is everything that was in a contiguous stream, which may consist of multiple host jobs. An IPDS "job" ends when the AFP process on the host disconnects from the printer. Infoprint 2105ES restart time You can see when the printer was last restarted, as during a site power outage, by entering into administrator mode on the printer Web page, then go into Printer Settings: Usage Information and there see like: Printer uptime: 05:08:20.599 from which you can readily compute the restart time. Infoprint 2190 The next generation of the 2090ES 90 ppm cut-sheet printer, announced 2007/02/05. Supports IPDS printing, that option being available 2007/05/11. Processor: 866 MHz Maximum monthly usage: 1,200,000 images Printer is actually: Rico Aficio MP9000 IPM support in PU7 (PTF U811589). PostScript driver: IBM Infoprint 2190 PS3 Infoprint 2210 The next generation of the 2105ES 105 ppm cut-sheet printer, announced 2007/02/05. Supports IPDS printing, that option being available 2007/05/11. Processor: 866 MHz Maximum monthly usage: 1,500,000 images Printer is actually: Rico Aficio MP1100 IPM support in PU7 (PTF U811589). Supports PJL. Oddities/issues: - If a job to be stapled is larger than 100 sheets (the printer's stapling capacity), no stapling will occur; but the printer will then emit the 100 sheets it could not staple and then accumulate the further sheets, rather then emit them one at a time as the 2105 printers did. This can cause the operator to think that the first 100 constitute the full job, and grab that off the stacker for giving to a waiting submitter, thus leaving the remainder of the job orphaned in the printer. - Suspend/Resume Key Error problem: Our first 2210 exhibiting a nagging problem where it falsely believed that the Suspend/Resume key (which is above and to the right of the output stacker) had been pressed, interrupting printing and resulting in a Needs Key Operator condition. ISC had the CE attempt numerous corrections, to no avail. The CE thought to try putting a toroid (balun) on the cable in that area, which seems to have helped. Reliability: Average, like 2105ES. Jams quite a bit, resulting in a lot of downtime. Disappointing, for a modern printer design. As the expression goes, curb your enthusiasm. Infoprint 2210 click charges Like other printers, the 2210 internally accounts for pages printed, for purposes of tracking wear and measuring usage relative to the terms of the printer maintenance contract. You can see the counter by going to the printer "Home" Web page and there click on the Counter tab, where you'll find the count broken down by printing and copying, plus a total of the two. Unlike the 2105ES, this printer accounts *only* for sheet sides that it actually images: If a three page job is printed duplex (double sided), the backside of the last sheet is necessarily blank. This printer will advance its counter by 3 rather than 4 for such a job. Infoprint 2210 network speed Actual setting being used can sometimes be seen in the System Log (under Configuration -> Network), as part of its system restart messages, reporting like: #[ncsd(38)]08/08/17 04:28:52 Current Interface Speed : 100Mbps(full-duplex) INFO: Infoprint 2105ES restart time You can see when the printer was last restarted, as during a site power outage, by going to its Web page, Configuration section, and there inspect the System Log, which will show system services starting, with YY/MM/DD log entry timestamps. (Make sure the printer date/time has been set properly so that the restart time can be readily determined.) Infoprint 2210 Web pages The Web pages presented by the 2210 are considerably different from what was on the previous generation (2105ES) of this printer series, reflecting Ricoh rather than IBM origins. The title of the main page is Infoprint 2210 Web Image Monitor. A bad thing about the main page is that a lot of space is wasted with a pointless, generic depiction of that printer model. And the main page is very sluggish to responde, unlike its 2105* prececessors, and so getting printer status is annoyingly slow. One good thing is that the main page is not Java-based, endlessly refreshing itself the way the 1585 page does; and another good thing is not trying to depict any control panel info in a separate Java box, as the 1585 does. Infoprint 2235 A slightly later printer, 135 ppm, to join the 2190 and 2210, announced 2007/03/27. Available 2007/05/11. IBM Machine type 2707, model 003. Maximum monthly usage: 1,900,000 images Printer is actually: Rico Aficio MP1350 IBM characterizes this as a "High Speed Printer", thus requiring a more expensive license than for the 2105. The next fastest printer is the Infoprint EMP 156 (q.v.). IPM support in PU7 (PTF U811589). Infoprint 4000 A duplex, black and white, continuous-forms printer with 600-dpi resolution. InfoPrint 4100 Large, continuous form, grayscale, toner-based printer for the high speed printing of customer bills, statements, and the like (as the 3800 used to do). Speed: 1,220 ppm for letter-sized forms. Announced 2006/05/09: AFP Color Emulation feature (grayscale representation of color, to practice for color), and 64-bit POWER5-based controller, for an 18% speed improvement. InfoPrint 4332 A workgroup printer. Models: 4332-001 InfoPrint 32 4332-004 InfoPrint 40 High-capacity input and output with full finishing options including jogging and stapling. Additional paper supply trays can be added by stacking: the printer can eventually become tall enough to stand on the floor. PDLs: PCL5e and PostScript level 3 are standard; AFP/IPDS optional. Infoprint Control Consists of the AIX GUI and command line on the server. Used to configure and manage the printing system. Spools data. Schedules and manages jobs. Provides data transforms. Provides accounting data. Drives printers. Infoprint Email Affords interoffice communication or to send emails to other addresses around the world. Send and receive data from a wide variety of sources, whether the source data is PCL, PDF, PostScript, GIF, JPEG, TIFF, or a native SAP R/3 data stream (ABAP or OTF): the Email DSS converts the data to PDF for viewing by the recipient. See also: /var/psf/segments/ Infoprint Email Infoprint Email can be used for interoffice communication or to send emails to other addresses around the world. You can take advantage of the Email option to format documents that are both viewable and printable at company workstations. Send and receive data from a wide variety of sources, whether the data is PCL, PDF, PostScript, GIF, JPEG, TIFF, or a native SAP R/3 data stream (ABAP or OTF). Incoming data can be all these types; the Email DSS converts the data to PDF for viewing, received in the email as a MIME attachment. To view output, you can use Adobe Acrobat Reader. Job submission requires special handling in being able to specify both a From and To email address, accomplished with the email-from-address and email-to-address attributes. Infoprint Select job submission accommodates email destinations via an Infoprint Email pop-up window, where the sender may fill in needed information. Limitations: This is a primitive, physical facility which is engineered to send one email message to one email destination specification. Infoprint Email provides no sophistication for efficient bulk mailing. Ref: Procedures manual See also: Email DSS; SMTP server; SMTP server port InfoPrint EMP156 156 ppm monochrome cut-sheet printer, new in May 2008. Is actually the Ricoh EMP 156, where EMP stands for Enhanced Monochrome Publisher. This is a "production printer", with an enclosed stacker as suits that class of machine, intended for bulk printing - unsuitable for on-demand, "grab output" printing. Infoprint Fax Provides an optional Fax function that allows sending fax data from anywhere in the world to be sent and routed as print jobs to printers anywhere. This function requires a Fax card within the computer system, and has limited support. Infoprint for Windows An overly casual name for the product with the proper name Infoprint Manager for Windows. Infoprint LCDS and Meta Driver An AIX PRPQ, new 2004/07, allows IPM to drive Xerox Enterprise Printing System (EPS) printers. - Converts LCDS jobs to metacode - Changes jobs so that they all use the same start environment, reducing the need for operators to interact with the printer at the start of each job - Embeds print resources in the jobs so that the resources don't have to be maintained on each individual printer. - Provides for printing selected page ranges within jobs. - Supports TCP/IP-attached printers. Infoprint Library A component of IBM Infoprint Manager for AIX. IBM Infoprint Library is a document archival and retrieval system in which job tickets and their associated resource files (graphics, fonts, images, and PostScript data) are stored and from which these data types can be retrieved for reuse. Infoprint Manager Infoprint Manager is the result of the combined evolution of the Print Services Facility (PSF) for AIX (formerly PSF/6000) and Printing Systems Manager (PSM) products and the Palladium printing system, and is part of a family of software and hardware products (both IBM and non-IBM) that use the published, non-proprietary Advanced Function Presentation (AFP) architecture. Note that Infoprint Manager is not the only product to come out of Palladium: there was also HP's Distributed Print Service (HPDPS), on HP-UX. Infoprint Manager, install new In addition to the IBM instructions on installing IPM on an AIX system, here are some additonal things to be done: - Update /etc/group to add all printing administrators to group "printq". (Various /var/pd/ directories are group printq, with no "other" privs access, so you must be in group printq to look inside.) - Plant any site user exit changes in /usr/lpp/psf/bin/, renaming the supplanted IBM modules to have a suffix name of .orig or .ibm . - Plant any site Formdefs or Pagedefs /usr/lpp/psf/reslib/. Infoprint Manager 4.1 Became available 2002/05/31. Went out of service on April 6, 2007. Infoprint Manager 4.2 Launched 2004/10/26 at Xplor 2004, to be available 2004/12/17. AIX levels: Initially, 5.1, 5.2. Support for AIX 5.3 was added in the very early PTF U802055. Goes out of service: 2010/05/31. Adds transform support for PDF 1.5. Most significantly, transform processing will be split off into a separate Infoprint Transform Manager for Linux, allowing transforms to occur on a fast server processor separate from queue management. ITM became available toward the end of 2005. Another significant change in 4.2 is in the way printers are interrogated via IPM's SNMP: In 4.1, all the OIDs in the printer's MIB were obtained, whether needed or not - an exercise which could delay server start-up as well as bringing a printer online. 4.2's SNMP goes after only the OIDs that it really needed, which greatly reduces overhead. Withdrawn from marketing: December 9, 2008, per IBM announcement 908-287 Infoprint Manager 4.3 New, December 9, 2008, per ISC announcement 208-432. Requires AIX 5.3 ML05+ or 6.1 or 7.1. Infoprint Manager 4.4 New, March 28, 2014, per announcement CRD # 14-1494-2 New: Supports Linux (RHEL 6). Is 32-bit (not 64-bit). InfoPrint Manager 4.4 for Linux base server ISO: LCD22003500.iso (463 MB - doesn't compress much) Infoprint Manager Administration GUI An administrator interface for managing Infoprint jobs and actual destinations, such as printers. It runs on multiple platforms, so you can use it either from a workstation or directly on an Infoprint Manager server console. The GUI is a Java application that is available on the AIX, Windows NT, and Windows 2000 platforms and which comes in three different views, depending on the customer's requirements... Basic view: if your Infoprint server is configured to support: Print on Demand (commercial) printing Assignment of jobs to actual destinations when they are submitted PostScript, TIFF, and variable data jobs Jobs submitted from Infoprint Submit, Infoprint Scan, or Infoprint Library. Basic view includes Printers and Logical destinations; does not include queues. Command: ipguibasicadm Advanced view: if your Infoprint server is configured to support: Data center (production) or distributed mission printing Printer pooling for workload balancing Jobs submitted from the command line, from workstation applications through Infoprint Select, or from other application programs. Advanced view includes queues. Command: ipguiadvadm Distributed view: if you are a customer service representative at a help desk who needs to locate jobs and assist customers with printing problems. Command: ipguidistadm Config file: ipgui_pa.cfg Contrast with Infoprint Visual Systems Management (VSM) TCP/IP port number: 6875 ("pdeventd") on the server, to communicate status changes to an arbitrary TCP port number on the GUI client system. See also: GUI; InfoPrint Manager Operations GUI; pdeventd Infoprint Manager Administration GUI, From CDE: Double-click the Application start Manager icon. From the AIX command line: 'ipguiadvadm' Infoprint Manager Fax A separately orderable feature that allows you to send and receive faxes. Ref: Infoprint Manager for AIX: Procedures InfoPrint Manager for AIX The software component of IBM Infoprint. IBM Infoprint Manager for AIX handles the scheduling, archiving, retrieving, and assembly of a print job and its related resource files. It also tracks the finishing and packaging of the printed product. IBM Infoprint Manager for AIX is based on Palladium technology developed at MIT/Project Athena. It conforms to the ISO DPA and POSIX standards. InfoPrint Manager for the Web Separately priced web browser interface to use InfoPrint Manager functions from a web interface, thus avoiding the need for special client software and allowing access from anywhere. Usable by both users for initiating and controlling their printing, as well as by administrators for changing configurations. There is no known manual: its Help facility provides all its info. Comments: Employs Java, which can make for "scariness" warnings in your browser. As with most other web appls, look and function varies with browser. InfoPrint Manager Message Facility of IPM Select, for receiving pop-up box messages about print jobs events (chiefly, completions) submitted via IPM Select. Not to be confused with InfoPrint Manager Notifications, which is a separately invoked application, for receiving messages about jobs submitted by other than IPM Select. InfoPrint Manager Notification Server The notifyd daemon, for servicing InfoPrint Manager Notifications (q.v.). TCP/IP port on which the notifyd process listens: 8200 (TCP. Not defined in /etc/services.) See also: notifyd InfoPrint Manager Notifications Separate application for receiving specific notification messages. Requires that the IBM Java Runtime Environment be installed on the PC: the facility is a Java GUI. The facility is for receiving messages about servers, destinations, and print jobs submitted by means other than Infoprint Select: jobs submitted via Infoprint Select will result in messages to Infoprint Select Notification, not Infoprint Manager Notifications. Operates per settings in the Notification Profile: see the notification-profile attribute. In Windows, add it to your Startup folder so that it runs automatically. Installs into Windows directory C:\Program Files\IBM\ Infoprint Notifications The executable is selectable from the Programs list as "InfoPrint Manager Notifications" First invocation brings up a "Notification Client Settings" dialog, with elements: Notif. server hostname Notification server port: [8200] Deliver Address: [You@YourPC] Locale: [English] Jump to Front: [checkbox] InfoPrint Manager Operations GUI A windowed operator interface for managing Infoprint jobs and actual destinations, such as printers. Config file: ipgui_p.cfg See also: GUI; Infoprint Manager Administration GUI Infoprint Manager Roundup "A users group for the customers of Infoprint Manager", so says 2004/10/26 IBM press release software102604pr_ww. However, no customers seem to be aware of it, as IBM has neither disseminated info about it to customers, nor provided anything in IBM's web pages about it. Roundup remains a mystery. Infoprint Manager Security A feature that you administer through AIX SMIT, allows you to protect your printing system by associating an Access Control List (ACL) with an Infoprint object or operation. An ACL is the list of users and groups who have permission to do something to or with an object, and what type of permission that is. Ref: "Infoprint Manager for AIX: Procedures": Managing non-DCE security for Infoprint Manager for AIX See also: ACL; fstsecutil; Security Infoprint Port Monitor for Windows Allows printing from Windows applications to a printer defined to z/OS Infoprint Server. IBM document number: P4000231 Download name: aopwin.msi Installs into: C:\Program Files\ IBM Infoprint Port Monitor\ See also: InfoPrint Select. InfoPrint Pro xxx New printer series from ISC, announced September 8, 2009, to replace the longstanding InfoPrint 2190, 2105, and 2210 models. These are pure printers, without the copier/scanner hardware that all prior midrange printers had. InfoPrint Pro xxx EX New printer/copier/scanner series from ISC, announced September 8, 2009, to replace the longstanding InfoPrint 2190, 2105, and 2210 models. InfoPrint Pro 907 Late 2009 successor to the InfoPrint 2190 cut sheet printer. This is purely a printer: no copier or scanner hardware as on predecessor. InfoPrint Pro 1107 Late 2009 successor to the InfoPrint 2105/2210 cut sheet printer. Speed: 110 ppm This is purely a printer: no copier or scanner hardware as on predecessor. Supports PJL. Staple capacity: 2 to 100 sheets (letter/A4). Jobs cannot be both stapled and shifted in the finisher. A job to be stapled will have its sheets accumulate in the finisher as imaging proceeds: if the job is then found to have more than 100 sheets, the 100 are ejected to the stacker as a clump (printing is cancelled by the firmware), and then the printer stacks each succeeding sheet as it is produced. IPDS: "Genuine IPDS Option" Is actually an SD "card", which is a small memory square as might be used in a camera. Emulates InfoPrint 2105 ES (4028). The IPDS Supplement manual says: "If the IPDS card is installed, items related to IPDS are displayed in the printer function screen or the User Tools menu on the control panel." InfoPrint Pro 1357 Late 2009 successor to the InfoPrint 2210 cut sheet printer. This is purely a printer: no copier or scanner hardware as on predecessor. InfoPrint ProcessDirector (IPPD) Software product and facility to help automate printing environments in terms of process management. The primary target customer is a commercial printing shop which has to manage incoming jobs, such as printing flyers and brochures, to fold and insert them into envelopes with barcodes. This involves setting up workflows and scheduling the availability of heavy equipment such as large paper roll printers, inserters, and the like. As such, there is SLA integration. Controls output equipment including IPDS printers, non-IPDS printers, most vendors' inserters (envelope stuffers), third-party composition software packages, and other Ricoh products and solutions. Built on included DB2 Universal Database and embedded IBM Web server software. Runs on AIX and Linux. Web interface for single point of control. Modular design allows adding functionality, such as indexing, reporting, SLA tracking. New in early 2006. Job submission is via special file system directory ("Hot Folder") or its own LPD software. (No Infoprint Select.) Transform processing involves deployment of the separate InfoPrint Transform Manager product. Is not a substitute for Infoprint Manager, where a "job" is simply a PostScript file to print one instance, such as a student paper. InfoPrint ProcessDirector Express A junior version of InfoPrint ProcessDirector, for medium sized shops. Infoprint Scan Provides patented grayscale scanning technology for online viewing and retrieval capability to allow publishing directly into the library via electronic submission and delivery of print requests for documents selected from the library. InfoPrint Select (IS; IPSelect) Component of Infoprint Manager that allows Windows PC users to submit print jobs to an Infoprint Manager server just as they would any printer, from the application's customary printing window, not via an interactive dialog. Runs on many versions of Windows (see the Getting Started manual for list) but the IPM 4.2 doc says: "InfoPrint Select is not supported on any 64 bit versions of Windows." But: The 2010/03 PTF adds 64-bit support. A chosen InfoPrint device driver underlies the printing by being installed into the Windows operating system. In Windows NT or 2000, for example, there is an Infoprint "port" which may be selected as part of the printing configuration one-time task on the PC. The Infoprint port might supplant the LPR port, for example, to have all jobs go through the InfoPrint Manager server rather than a Unix facility running the LPD protocol. In the server, the chosen driver (such as "IBM Infoprint 2085 PS") must be added to the Logical Destination Properties, Drivers tab. Help: There is no Help information to speak of. The best in situ information is obtained via the '?' box in the window title bar. Executables: C:\Program Files\IBM\Infoprint Select\ will contain the functions: Activate Job Settings Dialog Change the Notification port Help for InfoPrint Select InfoPrint Select Notification The Windows (7) control panel Programs and Features should show InfoPrint Select. Jobs: In the server, the jobs will reflect their PC file origin, seen in the transform program, like: C:\Program Files\IBM\Infoprint Select \Spool\3f43c0ac.SPL which exposes the PC spool directory name (also visible in the GUI on the Document Information tab, "File names" field (document-file-name attribute)). Installation: The manuals describe installing it from the Common Clients CD-ROM. Note that this is a one-PC-at-a-time method, unexpectedly dissatisfying for "enterprise" software as IPM is supposed to be. When installing, be sure that the Spool directory permissions allow writing for all users of the PC whom you want to print via IPS. (If you forget to do this and the permissions are restrictive, Windows will report that it can't print from its Windows spool area, which is the place where print jobs are first put, to then be transferred to the IPS spool directory.) Ref: Getting Started manual, "Creating Infoprint Select printers" and "Using Infoprint Select to submit a job" Contrast with InfoPrint Submit See: "Infoprint Select notifications" about the messages that come back. See also: C:\Infoprint\Select Infoprint Select attributes The standard Page Setup or Print dialog allows the user to set common printing attributes. (These are printer driver attributes, not IPM attributes, so they will be generated into the body of the PostScript as %%BeginFeature specs which preface PostScript variable defs.) ... General Select Printer Print to file [checkbox] Page Range [All, or Pages from _ to _] Number of copies Options Print frames Print all linked documents Print table of links Properties: Layout tab Orientation: Portrait|Landscape| Rotated Landscape Print on Both Sides: None| Flip on Long Edge| Flip on Short Edge| Page Order: Front to Back| Back to Front Pages Per Sheet Advanced... Paper/Quality tab Tray Selection: Paper Source: Automatically Select| Tray 1 ... Tray 6 Media: Plain, or a selection of colors and thicknesses. Note that the choice does not show up as an IPM attribute, but rather inside the PostScript file like "/MediaType (SpecialRed)" Destination tab Job name (Use application setting) User name Delivery: Print now|Print one copy and hold job|Hold job until you enter PIN |Print later|Print now and save Email Notification Type: None|Job completion only| Job completion and errors during job printing. Address: [fill in email address] Message: [fill in with text] Notes: The Email Notification actually has no effect. The specs supplied therein do not end up in the job attributes, and the ----------- In addition, the Infoprint Select application control may be set to "Activate Attributes Dialog", which will present a secondary dialog as each job is printed. That dialog window will be called Job Settings and will contain: General Job name Notify Do not display this dialog again Scheduling Print After Discard After Retention Period Change Priority Hold Messages Comment Message to operator Other Attributes file Attributes Printer options Ref: Getting Started manual Infoprint Select and a multi-user PC A Windows PC may have multiple, disparate users defined on it, such as when an organization sets up an Infoprint Manager Operator GUI for their operators to monitor IPM, with no privs (to keep them from overnight mischief); and an administrator account to make changes that the operator can't. But with such an arrangement, print jobs submitted through Infoprint Select won't work for the operator. This is a permissions problem which can be remedied by changing the permission for the group "USERS" on the folder "C:\Program Files\IBM\Infoprint Select\spool" from read execute to read write execute. Infoprint Select and Virtual PC In running a virtual Windows system (e.g., Virtual PC on a Macintosh) be careful of your networking choices. The most common VPC network setting is Shared Networking; but that employs Network Address Translation (NAT) to share your Mac's TCP/IP, resulting in implicit firewalling, with private network addresses (subnet 192.168). This can result in notifications unable to get back to the virtual Windows system and so you as a job submitter see nothing. Instead, set the VPC networking to Virtual Switch, wherein VPC uses its own, real TCP/IP address, separate from that of the Mac. No NAT. Infoprint Select and VPN In some settings a user may conduct a session from her PC using VPN technology, often for wireless security, and also to get inside the firewall to make the remote session look like it originates at the jobsite. Such usage of IPSelect often precludes getting job notifications, however. The reason for this is that VPNs tend to utilize a private network address for the PC end (e.g., 10.197.24.182, 192.168.123.112). By definition, private networks cannot be addressed from outside the private subnet. Print jobs originating from the VPNed PC are tagged with an origin IP address of the private subnet. Later, when the job completes, IPM issues mail addressed to the private network IP address. Such mail cannot possibly get sent, and may sit in Sendmail's queue until it expires; and certainly, the job originator does not get her job completion notification. Infoprint Select debugging If jobs don't flow out of the PC, remember that they first go into the Windows print queue, then the Infoprint Select queue, before going on the the IPM server. So assure that the Windows printer instance is in a Ready state in the "Printers and Faxes" window - not Offline or Paused. You can look for printing problems by going into Control Panels, then Administrative Tools, then Event Viewer, where you select System and look for Source records of type "Print", where double-clicking on an entry opens an info window and you can then go up and down in the list from that window. There will be Warning type Pause/Resume records for an ordinary user name and the installation of drivers by User "SYSTEM". Especially look for Error type entries (commonly, Event ID 6161, which I've seen for print jobs submitted by limited, non-privileged users whereas administrator user jobs have no problem flowing through). Make sure that the IPM LD is configured to support the client driver (e.g., "IBM Infoprint 2105 PS"). Check the driver name attached to the job by right-clicking in the job's Status column in the Windows queue display or on the printer icon, and then look under the Advanced tab for Driver. You can see the driver version by going into the Query Printer tab and clicking About. Try an lpr submission of a job to that LD, from the AIX server system. InfoPrint Select for Linux Available in IPM 4.4, in the Common Client ISO, "linux" folder, as filename like ipr-select-4.4.0.0.i586.rpm. Install it in standard RPM manner. Printers can also be defined via CUPS and the lpadmin command. (See the Getting Started manual.) Notes: - There is an unattended install process called Remote Install, where you invoke /ip_remote/remote_install and supply an ipin_remote file which specifies how to configure the VM. In it you supply file system sizes for IPM to create, etc. The install enforces prerequisites, one of which is that the /etc/hosts file *must* contain a line for your host system. - Printer definition uses the selpms method which Macintosh also uses. InfoPrint Select for Macintosh Available in IPM 4.4, in the Common Client ISO, "mac" folder, as filename like ipr-select-4.4.0.0.i586.pkg. (It has an i586 name because OS X is Unix and the software is an on offshoot of the Linux version.) Should run on OS X 10.7.3 or later. Double-click on the .pkg file to install. The package is not "signed" so you have to go into System Preferences > Security & Privacy, and "Allow apps downloaded from: Anywhere." Installing requires a logoff sequence. Where ths software lives: It is not an app. It shows up when you go to define a printer, in the Advanced tab, where new Type InfoPrint Select now shows up. Choosing that causes the URL field to be initially filled in with protocol identifier "selpms://". You would add to that per form: selpms://:/PrtName (The port number, usually 6874, does not default, so you must add it; else get weird error "5010-450 Cannot determine the local ip address". Example: selpms://IPMsys1/HighSpeedPrinter1 Printers can also be defined via CUPS and the lpadmin command. (See the Getting Started manual.) With IPS installed, app InfoPrint Manager Message will now be running. Located in: /opt/Ricoh/InfoPrint-Manager/ In there, running the activateipmjobsettings script will reactivate the Jobs Settings dialog. InfoPrint Select automatically launches when you boot/log in because of the presence of the following files: /Library/LaunchAgents/ com.apple.startipmnotification.plist com.apple.startselpmd.plist Infoprint Select Job Settings on/off In submitting jobs through Infoprint Select, you can choose to turn on the interjection of a Job Settings dialog. To activate this: Select Programs > Infoprint Select > Activate Job Settings dialog. There will not be any kind of acknowledgement in doing this. Now, when a job is submitted, a dialog will appear in which job settings may be chosen. To deactivate this: In the Job Settings window, check in the box for "Do not display this dialog again". Infoprint Select notification profile When you submit a print job using Infoprint Select, a default notification profile is sent with the job. That notification profile sets the event-identifiers to a default set of events and the delivery method to either e-mail (if you have the Select message window running) or to none (if you don't have it running). The Infoprint Select default notification profile overrides any notification settings you configure in the default job notification-profile attribute. Jobs arrive with event-identifiers = document-aborted-by-destination document-aborted-by-server document-cancelled-at-destination past-discard-time job-aborted-by-server job-cancelled-by-operator job-completed destination-needs-attention destination-needs-operator destinations-not-ready-for-job job-cannot-be-scheduled; delivery-method = electronic-mail delivery-address = "Username@[111.222.333.444]" locale = en_US.ISO8859-1 which effectively says that notifications are to be sent to the mini IPM SMTP server running in the Windows PC. No Comment is set, and is not influenced by the Job/Document Defaults notification profile values. There is no defined way to change this IBM-set notifications profile, and in the "C:\Program Files\IBM\Infoprint Select" directory there is no notifications configuration file; and the readme files in that directory include no info about notifications. An unfortunate thing about the event identifiers chosen by IBM is that the end user will get superfluous info, such as "5010-838 Printer ____ has a paper jam." and "5010-839 Printer ____ has an open cover.". See also: Infoprint Select notifications Infoprint Select notifications By default, Infoprint Select sends a notification profile with its submitted jobs to cause IPM to send message type notifications back to the Windows PC - via email. No server notification profile setup is needed: you don't have to tailor the Job and Document Defaults. (That is only needed for the separate Infoprint Notifications program.) The notification comes from an arbitrary IPM server TCP port (e.g., 52197), sent to the built-in Infoprint Select Notification facility (not Infoprint Manager Notifications), at its (SMTP) port 25 (or a port other than 25 once PTF U802540 or IPM 4.2 is adopted - but delivery-method = electronic-mail in the PC's notification profile may define otherwise). For this to be facilitated, the IPM server smtp-server-host and smtp-server-port attributes must be appropriately set. The IS Notification interface is a smallish, rectangular window titled "Infoprint Manager Message", which will pop up when one or more notifications arrive. The most recent message is at the top. Click its OK button and the messages accumulated in that window are erased - as having been seen - and the notifier will retire to the Taskbar with a gold-brown icon. In IPM 4.1, mail notifications go through the AIX mail spool. In IPM 4.2, they do not: notifications go directly from the IPM server to the PC. The notifier runs as Windows program ipnotify.exe per C:\Documents and Settings\All Users \Start Menu\Programs \Startup . Note that this notifier is rather intrusive, in that it comes up in the center of the screen at Windows boot time. One might take it out of the Startup folder and instead have it be a Desktop shortcut. Issues: The obvious big issue is that it's mail based, meaning: immediacy may be jeopardized by mail queue scanning frequency on the IPM server system; the mail may not be deliverable if the user in any way ended the PC session before the job printed. The email notification is constructed in /tmp, with file name ",_notif.msg". The file remains after the notification is sent. The email notification back to the PC has a body that looks like: [07/08/03 16:07:34] 5010-071 Job name My Print Job with ID 3 (acsn07:5304222522) completed successfully on printer3. The email destination is like: fred@[128.197.150.195] The email Subject is like: 5010-192 Message from Infoprint server: server7 (Such email stands out in the sendmail server log in that the destination address is always in brackets ([]). The email notification back to the PC can present a site administration issue: PC users may abruptly end their PC session immediately after submitting a print job, as when a student rushes off to class; or the probably little printer may have an hour's backlog, and the student has to go, so logs off the PC. The subsequent notification email cannot get back to the user and so sits in the operating system mail directory, where it may languish for days until it finally ages out, whereupon the virtual sender ("operator") is sent fatality email about the inability to send, which could mean having to deal with a lot of crud. In that notification type messages more than about 10 minutes old are obsolete news, such email is best discarded: something else for the site systems programmer to deal with. A "Connection refused" condition in trying to return notification email to the PC certainly means that the PC is running; but, seemingly, the user who submitted the jobs logged off and a different user logged on to it. Port conflict: If two Windows users are logged in at the same time, they both can't use IPS, as Windows will detect the port usage conflict and keep the second IPS start-up attempt from succeeding. See also: Infoprint Select notification profile Infoprint Select ports (TCP/IP) Infoprint Select uses an arbitrary local TCP port (1440, 1439, etc.) on the Windows PC to communicate with the standard "psmd" port 6874 on the IPM server. The IS client submits the job to the IPM server's port 6874 and from that port receives later message type notification. The standard notification port number is 5157. It can be changed via the "Change the Notification port" selection seen when going into InfoPrint Select from the Windows Start menu, or by launching change_notifport within the Program Files > IBM > Infoprint Select folder. Note that IS can also receive email notifications, and as such the IS client Infoprint Select Notification process is also listening on port 25 (smtp). Infoprint Select queue display To open the IS queue display: - Open the Printers control panel; - Right-click on an IS "printer" name. - Choose "View IPM queue". Or, on a locked-down PC, where there is no right-click: - Open the Printers control panel; - Click on an Infoprint Select printer icon to choose it to operate upon. - Go into the File menu, where at the bottom of the list you can choose "View IPM queue"; or, right-click on the printer icon and select "View IPM queue". You can right-click on the printer name to bring up its Properties and thereby the Print Test Page choice for sending a test job to watch in the queue window. Note that you will need to do a refresh in the queue window to see the arrival of new jobs. The command underlying this display is ipjobs.exe (in the appl dir) - a program which cannot be run in DOS mode. Who can see what: - A Windows limited user can see and manipulate only his own jobs to that LD: he cannot see jobs submitted by others. - A Windows administrator user can see all jobs submitted by that PC *and* other PCs and regardless of submission method (IS, LPR, etc.) to that LD; but can manipulate only his own jobs. (Attempting to manipulate others yields pop-up error "You are not authorized to cancel this job." There will not be any indication of attempt rejection in the IPM server error.log - it will show just a "list request" there - indicating that the limitation is imposed by IS.) - Changing the IPM server security permissions does not affect visibility, as for example setting "testuser@*" into "Add Users to Group". Infoprint Select spool area Within the Windows PC, Infoprint Select will spool the job as like: C:\Program Files\ IBM Infoprint Select\Spool\ 3e3fdff2.SPL Normally, the job will reside there only momentarily with that name, then disappear as the job is completely sent to the IPM server. (The number of unprinted jobs in the spool will be reflected under the printer name in the Printers control panel, and in the usual case would be 0.) A nuance is that when the job is sent to the IPM server that it is not actually deleted from the spool directory, but is renamed: in our example above, it would be renamed from 3e3fdff2.SPL to simply 3e3fdff2. Windows will superficially identify the file type in a directory details list as "Shockwave Flash Object" though in a properties display it will have "Opens with: Unknown application". The file will, in reality, be a PostScript data file, but Windows is too dumb to realize this. These leave-behind files will be automatically removed after a period of time. Housekeeping: Experience shows that IPS fails to clear old print jobs from this spool area, such that they pile up, indefinitely. Do not expect the Windows print queue display to reveal jobs submitted via Infoprint Select. That is, if you go into the Printers control panel and double-click the printer icon, that brings up the Windows queue display, which reflects only the first point in the path that jobs take to the printer. Infoprint Select submission timing Submitting a job from the Infoprint Select client to the Infoprint Manager server obviously takes some time - and, the busier the server and the network, the longer it make take. You can measure the submission time in several ways. In all cases, assure that your PC's clock is synchronized with a time standard, as the server is. Measuring the time from the client: Submit a small job and note the hh:mm:ss time of submission. In the IPSelect job queue window, check the Submission Time versus your noted time. Measuring the time from the server: After a small, IPSelect-submitted job has arrived on the server, note its creation-time (preferred) or its submission-time. Then examine the top of the PostScript job for the DSC comment which looks like: %%CreationDate: 4/22/2004 8:21:45 which reflects the PC clock time as the PostScript driver was generating those DSC header lines. Compare the two time values. Infoprint Select version verification Once Infoprint Select is installed on the PC, how does one thereafter verify what version is installed? Unfortunately, the Readme that is planted with it fails to provide such basic info. The best approach is to right-click on a printer, then select either View IPM Printer Status or View IPM Queue, then from the Help menu select About InfoPrint Select. This will report like "InfoPrint Select Version 4.3.0.125", which is fully useful. Another approach: right-click on a printer, then select Printer Properties and click on the Ports tab and then click on Configure Port: in the lower right corner of that window will be a version number, like: May 8 2008 4.2.0.225 (The ending digits may not be helpful; but the date should allow you to go into the Release Notes doc that accompanies each PTF to thereby isolate the PDF number (e.g., PTF U816488 May 2008). But: The .225 at the end may not be quite the same as what is reported by the Programs approach below (which reports .250 for this IPS. The lesser approach is to go into the Control Panel, select Programs -> Uninstall a program, then see the PTF level reported in the presented list (e.g., 4.2.0.250). However: the report may only include the V.R.M number (e.g., 4.3.0) and not the PTF number, so not fully informative. A more physical approach is go to into C:\Program Files\IBM\Infoprint Select and get the dominant files datestamp, which you can then correlate with PTF levels (q.v.). In this approach, be cognizant that the date on the software files may be like a week behind that of the PTF package, as it takes time for the product admistrators to prepare the assembly for the public. (Note that file Properties provide no version information.) Infoprint Server An optional feature of z/OS that uses z/OS UNIX System Services in providing the basis for a total print serving solution for the z/OS environment. It supports consolidating the printing workload from many servers onto a central z/OS print server. InfoPrint server job sources Print jobs are submitted to the (inputs) Infoprint server in a variety of ways: - InfoPrint Submit: Invoking an Infoprint client application (command line or GUI) to explicitly submit a job to the server. - InfoPrint Select: Transparent Infoprint device driver installed on the client system to allow ordinary applications to print as usual. - Putting an LPD Gateway ahead of IPM, to receive jobs and hand them over, within the server system. - Hot Folders (directories associated with a logical destinations). InfoPrint server job outlets Print jobs queued in IPM can go to any of the destination support systems (DSS). Infoprint SMIT administrator's For managing InfoPrint elements from interface outside of it, as in starting and stopping the server. Use to: - Start and stop Infoprint servers - Access migration tools - Perform troubleshooting procedures - Access Infoprint SMIT operator GUI - Perform miscellaneous configuration tasks - Submit jobs using attributes files - Manage network interfaces - Manage Infoprint name spaces - Control access to Infoprint objects - Manage the Distributed Computing Environment (DCE) - Use the Infoprint utilities Ref: "Infoprint Manager for AIX: Getting Started": "Using the Infoprint Interfaces" InfoPrint Solutions Company On January 25, 2007, IBM and Ricoh announced the creation of this joint venture printing systems company, essentially representing IBM selling off its Printing Systems Division to Ricoh (the printer manufacturer which makes IBM's mid-range cut-sheet printers). IBM's motivation was shrinking revenue in an area very peripheral to its current corporate objectives - the traditional result when a company loses interest in a product area and no longer evidences innovation and direction. Ricoh will have paid IBM $725 million in cash up front and an unspecified remainder later. Ricoh initially will own 51 percent of the new company, InfoPrint Solutions Co., and will take full ownership within three years. The new company will start with the current IBM organization, which is based in Boulder, CO. InfoPrint Submit The component of IBM Infoprint Manager for AIX Print-on-Demand feature that allows users to submit jobs with a job ticket from a Windows or Macintosh workstation. The user explicitly works with an InfoPrint client GUI to submit the job. See: Print-on-Demand Contrast with InfoPrint Select Infoprint Submit Express In IPM 4.2, part of the Print-on-Demand feature, for submitting jobs with tickets, and tracking their progress. Thus, a service bureau regimen. Infoprint Submit Express for Windows Replaced in IPM 4.2 by the Print-on-Demand feature. Infoprint Submit for Macintosh Replaced in IPM 4.2 by the Print-on-Demand feature. Infoprint Transform Manager for Linux Announced in conjunction with IPM 4.2, to split off transforms to a separate, low-cost, powerful Linux system, which will then hand back the AFP for printing by IPM. This arrangement lets IPM concentrate on job arrivals and queue management, offloading transforms so as to have more "breathing room". Available by end of 2005. Its transforms: - Adobe PDF (v1.6) to AFP - Adobe PostScript 3 to AFP - PCL (Level 6) to AFP - SAP (OTF and ABAP) to AFP - TIFF image to AFP - GIF image to AFP - JPEG image to AFP - AFP to PDF Versions run on Linux, AIX, Windows. Pricing: Per processor basis. The minimum configuration is a dual processor server; therefore, two licenses are required. Operates through port 6986. Is not documented as working with InfoPrint ProcessDirector. InfoPrint VSM Administrator's GUI DISCONTINUED IN IPM 4.1... Visual Systems Management An AIX-only control interface for managing server facilities, including fax and email destinations. Provides object oriented capabilities, beyond the iconic selections in the admin GUI. Comes in Basic and Advanced flavors. Basic works with early binding, whereas Advanced works with late binding. Infoprint Workflow IBM software product for end-to-end, customized consulting engagement and workflow management and control solution, intended to automate and transform enterprise document production and distribution to increase efficiency, improve integrity and reduce costs. Inline form definition (Formdef) An AFP jobfile may contain one or more form definitions, embedded in it: this is termed an inline form definition. When an AFP jobfile is generated, as via the 'ps2afp' command, if no form-definition attribute is in effect at the time of processing, then a default inline form definition is generated into the AFP jobfile. See also: F100APS; Formdef processing hierarchy Inline resources In AFP, the job file contains all of the resources (fonts, formdefs, overlays, page segments) needed to process the job, situated inline, at the head of the file, usually in processing order, referenced by following Pagedefs. This is as opposed to the default condition where the file only references external resources. Inline inclusion allows a job file to be archived and later reused and have all the resources it needs to successfully print. Beware that various Infoprint facilities cause the job to get (invisible) inline resources. For example, use of the IPM document-finishing attribute generates an inline Formdef. See also: job-finishing Input Manager The part of Infoprint Manager that breaks print jobs into segments to allow greater flexibility during processing. The Input Manager stores job segments in its workspace. Segments remain in the workspace either until they are manually deleted or the workspace fills up, depending on how you choose to manage the workspace. By default, the Input Manager workspace is located in directories /var/psf/segments/ and /var/psf/seglist/. See also: psfin input-trays-medium AD attribute which identifies which input medium is in which printer tray. Note that this defines the *size* of the medium: there is no provision for specifying the type within size. For example, a tray may contain letter size paper, but its type is letterhead, with a logo pre-printed at the top. Note that IPM can determine the actual tray settings via SNMP inquiry of the printer: your definition of a setting via AD attribute overrides that dynamic determination. DSS: AIX GUI label: Media ready Allowed values: auto-envelope-feed automatic-tray auxiliary-envelope auxiliary-paper bottom continuous-form-feed current-selected-tray envelope high-capacity-feeder large-capacity manual manual-envelope-feed middletop tray-1 tray-2 tray-3 tray-4 tray-5 tray-6 tray-7 tray-8 tray-9 tray-10 capacity-2000-sheet Example: input-trays-medium = tray-1:letter tray-2:letter Msgs: 5010-096; 5010-538 See also: default-input-tray; media-ready input-trays-supported AD attribute which identifies the types of input trays, such as top or envelope, supported on the printer device. GUI label: Input trays allowed Oddly, despite this attribute showing up in a full attributes listing for an AIX DSS printer, it is not revealed in the GUI. See also: medium-identifier Install CD issues You typically receive an install CD early in your life with the product, and that CD stays with you, to be reinstalled as needed in migration across computers, etc. A conspicuous problem with the executables which come on an install CD is that they are frozen in time, and are what you shall use ad infinitum as you live with that CD over the years, meaning that the executables will always be old and crusty rather than have been updated with fixes and general modernization. Another problem is that the CD cannot always be used: With an RS/6000 SP, one cannot install directly from the CD, as the node processors are embedded in the frame and have no CD drive, so the CD contents have to be copied to an NFS-mountable directory or somehow network copied to a local directory, and then used as a set. The installation procedures are optimized for CD-based installation and are typically sketchy (particularly with the 'setup' command) for non-CD installs, making for some odd results if you guess wrong. Installation Instructions Title of discontinued manual which described how to install IPM 4.1 and early 4.2. Such info is now in the Getting Started manual. Int req See: /var/psf//printer.intervention Intelligent Printer Data Stream See: IPDS Internet Printing A capability found in printers such as the Infoprint 2105ES, where a print job is submitted to the printer, but the job data are not contained in the job; rather, the URL of the data source is provided in the job, where the printer itself then pulls the data from that location, via HTTP means, to fulfill the printing request. This is "printing by reference". The concept is much like getting HTML type email, where images are not contained in the email message but rather are obtained through URLs in the message. Interoperating environment Where multiple IPM servers can interoperate. See: Namespace Interrupt printing job GUI action on a printer, to interrupt the currently printing job. May get error 5010-558 saying that the job cannot be paused because it is past the last pausable point: for an AIX DSS this may indicate that the job data has been fully transmitted to the printer, which precludes IPM from doing anything about its printing, which is wholly up to the PostScript printer. Interval to retry jobs (sec) See: job-retry-interval intervention-timer AD attribute for a PSF DSS: Specifies the maximum amount of time, in seconds, that IPM waits before it treats an intervention-required condition at the output device as a permanent error (which causes the printer icon in the GUI to go red and the printer to possibly be shut down, and jobs bound to that printer to go pending for another available printer). GUI label: Intervention timer (sec) Type: Resettable, single-valued Allowed values: 1 - 9999 (seconds). Default: 9999 A value of 240 is commonly used. Usage guidelines: A value of 9999 specifies that a permanent error condition can never occur: This would cause IPM to never recognize a problem with the printer, and thus cause it to not shut the printer down in order to allow jobs bound to it to divert to another candidate printer. It is also the case that the IPM server can get thoroughly gummed up waiting indefinitely for its printers' problems to clear. A value of a few minutes (in seconds) makes more sense, particulary with an LD having multiple ADs such that the jobs could go to another AD if the faulty one shut down and released its jobs. Notes: A TCP/IP-attached printer in an intervention-required condition often refuse connections while in this state, which may manifest itself with message 0420-020 (cannot link) in the /var/psf//.error.log . Msgs: 0420-049 0420-023 will appear in the /var/psf//error.log See also: job-retry-count-limit; job-retry-interval Invoke Data Map A line data structured field present in the line-data or unformatted ASCII file at a point that requires switching from one Page Format to another. See also: Page Format IO images Are compressed or uncompressed raster data images. Compression generally reduces the amount of data sent to the printer and should significantly save transmission time. IO images may be arbitrarily scaled and corrected for resolution differences between the scanner and the printer. Contrast with IM images. IOB Include OBject: AFP facility whereby a PostScript, PCL, or TIFF objects in AFP data streams can be reoriented and repositioned without accessing the actual objects themselves. This allows a collection of reusable objects to be kept and be included as needed, with variable transformation for tailoring to the job. IOCA Image Object Content Architecture, uncompressed. As used in line data printing. Ref: Reference manual, line2afp command IP Often seen in IPM APARs, being an abbreviation for an IBM Infoprint printer model involved in a problem scenario, as in "IP4000". IP address of printer See: destination-tcpip-internet-address IP PrintWay IBM product to send print data from the OS/390 or z/OS spool to the following printers and e-mail destinations: - A printer or host system in a TCP/IP network that supports the LPR/LPD protocol, the IPP protocol, or direct socket printing; - A printer in an SNA network that supports either the SCS or DSC/DSE data format and is defined to VTAM as an LU0, LU1, or LU3 printer; - One or more e-mail addresses ip_update Command to apply APAR or EFIX service to Infoprint Manager. Comes with the PTF package, downloaded from IBM. Usage: 'ip_update [-h] | [-s cd_mount_pt] [-C] | [-s cd_mount_pt] [-c] | [-s cd_mount_pt] [-r]' Flags: -h Displays usage. -s cd_mount_pt Specify where the Infoprint Manager APAR Service CD-ROM is mounted. The command otherwise assumes mount point directory /cdrom/. Often, you'll be working with an FTPed PTF, such that the PTF is on a system disk drive or NFS, in which case you need to supply the full path of that directory. (As of 2007, ip_update no longer likes relative directories.) -C Applies *and* commits APAR service. -c Commits previously applied APAR service. The -h help info says "Do not use with other flags.", but that is erroneous: the -s option is required. Is non-disruptive: The ip_update -c does *not* terminate any IPM services when committing maintenance, as that's an AIX clerical operation. Indeed, the IPM server error.log has nothing for that time period. -r Rejects previously applied but uncommitted APAR service. Do not use with other flags. Invocation with no flags causes the PTF to be applied but not committed, so that you can reject it if necessary. Advisories: This command will detect running IPM processes and shut them down when it starts, and restart them when it finishes. Restarting the server right after applying maintenance is A Bad Idea, as you would want to first check things out; so manually shut down the server processes beforehand, so that the command won't start them. Warning: Applying maintenance will result in some of your site changes being replaced as for example /usr/lpp/psf/bin/ainuxjobcompletion. IPDS Intelligent Printer Data Stream. The printer data stream, as contrasted with the application data stream, AFPDS (MO:DCA). IPDS consists of device commands rather than presentation space descriptions: IPDS is the result of "compiling" the presentation document to create a device-dependent stream which can drive the IPDS printer at maximum speed. IPDS elements: (1) An all-points-addressable data stream that enables users to position text, images, and graphics at any defined point on a printed page. (2) Information that the host sends to IBM IPDS printers. This information generally contains basic formatting, error recovery, and character data and enables the printers to make decisions. (3) An architected host-to-printer data stream that contains both data (text, image, graphics, and bar codes) and controls defining how the data is to be presented. IPDS provides a device-independent interface for controlling and managing all-points-addressable (APA) printers. IPDS is uniform across all IBM printers, making for consistency among a customer's existing printers, and mitigating issues in upgrading. IPDS is the device-dependent result of IPM processing from an input AFP data stream. Communication with the printer is bi-directional, allowing the printer to signal the IPDS driver in case of any problems, allowing the driver to take corrective action and notify operators. IPDS conveys data and instructions from the print server to the printer in structured fields. The printer controller processes these IPDS commands and returns acknowledgment back to the print server. With an IPDS printer, the sending host may query the printer to determine its characteristics. For job processing, the printer may request the host to send it resources needed to fulfill the printing request. Like AFPDS, IPDS is object-oriented. IPDS is a registered trademark of IBM. Ref: IPDS Handbook manual (G544-3895). See also: AFP; AFPDS IPDS Exceptions As appears on printed error page, in message number 0420-249. HEX DESCRIPTION 027C..02 Too many sheets for a finishing operation. Ref: Manual: IPDS Handbook, Chapter 2 "Exception Reporting and Sense Data", "IPDS Exceptions Reported". Note that these show up in /var/psf//error.log . See also: Action Codes IPDS port number 5001, as defined for most IPDS printing. That is, IBM printers are microcoded to expect IPDS to arrive on port 5001. Workgroup printers such as the Infoprint 1585 will accept IPDS on port 9100. Note that port 5001 is found in /etc/services to be "commplex-link". It may be worthwhile to alter that entry in /etc/services to reflect IPDS, such that inspection utilities such as 'lsof' will identify ports more obviously. See also: Ports IPDS Printer Support The list of IPDS printers supported by the several host application suites is documented in IBM White Paper P7000003. IPDS printing IPDS is a conversational data stream: the PSF process, in converting AFP to IPDS, receives responses from the printer. Once the first IPDS job goes to the printer, that printer effectively becomes dedicated to IPDS and will block all other paths until one of: - The AD is Shutdown; (Note that Disable is not enough: in that state, the IPDS session continues.) - The printer is powered off; - IPM/PSF is terminated; - The defined Release time expires. And only one IPDS process may control the printer: there is no mutualism. Trying to have two IPDS sessions from the same server invites trouble: the printer allows it, because the additional session is from the same server; but the server assumes that no one would set up multiple IPDS streams. The rationale in this control is that IPDS has established an environment and resources within the printer, and cannot have that disrupted. If the session connection is terminated for any reason, upon the next IPDS job, the set-up work must be repeated. The normal IPDS method is dedication of the printer to the single IPDS session. Sharing can be achieved via the Properties of the IPDS AD, per the Tuning tab "Release time" value being minimal instead of its default 9999, and the "Connection timeout" being relatively high to allow time for the non-IPDS stuff to process. Printing begins as soon as the first page is processed by the printer. That is, the printer does not digest the whole IPDS file datastream before it begins emitting paper. See also: destination-release-timer; Release time (sec) IPDS protocol TCP IPDS Timeout Setting in an IPDS printer to control how long the printer remains waiting after an IPDS job has been processed before it times out waiting for the next job. This corresponds to the IPM AD Release Time (destination-release-timer). The purpose of the timeout is to hold on to anything which had been set up in the IPDS area of printer memory, so as not to have to rebuild it for the next IPDS job. When the timeout occurs, temporary resources held in the printer memory for IPDS processing are released, to make that much more memory available to other tasks (perhaps PostScript job printing). The setting IPDS Timeout = Host Controlled may be preferable to an absolute value, so that the printer is not the first side to drop out of session. Some printers default to "Host Controlled" when communication occurs via port 9100 or 9102. Larger printers, such as the Infoprint 2105ES and 2210, do not have an IPDS Timeout setting: they stay in session with the host until it performs a release. IPDS vs. PostScript printer IBM printers by default operate with IPDS data flow. An optional PCL/PostScript feature allows them to instead operate with those data streams, handling them natively in the printer. While it may be appealing to have the printer be a familiar PostScript printer instead of unfamiliar IPDS, one must realize that PostScript data flow is simplistic, involving just data flowing to the printer, with no return flow of results or other information to the submitting system: you're handing the printer job data and telling it to do what it will with it, purely on its own. This is to say that you sacrifice a lot of capability in running as PostScript. IPDS provides bi-directional communication so that the printer can readily communicate with the submitting system. ipgui* Infoprint Manager GUI invocation commands, in /usr/lpp/pd/bin/. As of IPM 4.2 PTF5, these commands use IPM's own /usr/lpp/pd/jre/bin Java software, rather than that present in the operating system directories. ipguiadv The advanced Operations GUI. ipguiadvadm The advanced Administration GUI. ipguiadvs The advanced Operations GUI, special version (to lock its config). ipguibasic The basic Operations GUI. ipguibasicadm The basic Administration GUI. ipguibasics The basic Operations GUI, special version (to lock its config). ipin_response Conventional name of the unattended install responses file for the remote_install script to use via the -a option. Is provided in the templates directory on the server product install DVD as the basis for you creating your own, tailored version. See also: remote_install IPM Abbreviation for InfoPrint Manager. ipm Images per minute, a measure of cut sheet printer throughput, as with the Infoprint 2000 printer series. This measurement is more commonly ppm - pages per minute. IPM Short for Infoprint Manager. ipm_pdenq /usr/lpp/pd/bin/ipm_pdenq command, invoked by /usr/lpp/pd/bin/pdenq, in turn invoked by /usr/bin/enq, under lpd, to pass a job, incoming via lpd, to IPM. The ipm_pdenq process manages log file /var/spool/lpd/pdlpd_gateway.error_log to record problems. IPMAIX Short for Infoprint Manager on AIX. ipmlpd /usr/lpp/pd/bin/ipmlpd, a compiled, binary program. The LPD daemon, LPD gateway daemon, in IPM 4.4 for Linux. There seems to be no logging. Issues: Job titles which include a single quote don't make it into the system - the LPD lpdtrace.log shows that operation failing with message "####XXXX Job submission to Infoprint Manager failed: 5010-099 Specify a single value for attribute job-name. [f19f7b70]" due to a software design deficiency. ipmlpd, query There is no provided command for that. What you can do is issud command 'startlpd' (q.v.) which will report 5010-618 The server ipmlpd is already operational. if running. ipmlpd, start Command 'startlpd' (q.v.). ipmlpd, stop Command 'stoplpd' (q.v.). IPMMI InfoPrint Manager Management Interface. Available in IPM 4.4 for Linux, as an apparent stand-in for resource management which had been in AIX SMIT. Start via command: startipmmi IPMNT Short for Infoprint Manager on Windows NT. IPMXFORM The IPM Transform Sequences manager. IPP Internet Printing Protocol. Project of the Internet Engineering Task Force to standardize internet printing. Allows web-based printing, to a printer which is associated with a URL. Data transfer is based upon HTTP 1.1, which allows persistent connections that make a multi-message protocol be more efficient. Because IPP is layered on top of HTTP, it uses the authentication mechanisms built into HTTP. (Being built on top of HTTP does not necessarily mean that job submission has to be through a Web browser.) IPP has been supported in the software product Infoprint Manager for Windows (since W2K) and natively in hardware in various Infoprint-ers. As of 2004/07/23 it is at last also supported in the AIX version of IPM. Support of IPP is in two aspects: 1. IPP gateway, to accept jobs via the IPP protocol. 2. IPP DSS, to drive printers through their IPP protocol port. IPP's normal port number is 631, which is TCP, name "ippgw" (and is also the conventional CUPS port). IPP is the basis for CUPS, which is maintained by Apple. The IPM operating directory for IPP is /var/pd/ippgw/. Access is via an IPP-capable printing client (Mac OS X et al). To the user, IPP printing is exactly like LPD printing. Using a URI, an IPP server can be accessed via addressing that starts with ipp:// In AIX, the IPP Gateway can be controlled via SMIT: go into Infoprint Printing System, then Infoprint Utilities, then IPP Gateway Daemon. The daemon can be manually stopped via: /usr/lpp/Infoprint/install/bin/ ippgw_setup.ksh -p631 -N In AIX, the IPP Gateway can be controlled via the startippgw utility or IPMMI (InfoPrint Manager > Object > IPP Gateway). Shortcomings: As with LPD printing, there is no means of authentication associated with IPP. Logging dir: /var/pd/ippgw/ There is an IPP DSS for IPM AIX to feed IPP printers via their URL. RFCs: 2565, 2566, 2567, 2568, 2569, 2639 IPM manuals: Getting Started Ref: http://www.pwg.org/ipp/ See also: IPP Gateway; SWP IPP, start As root: 'startippgw' IPP, status 'lsippgw' IPP, stop As root: 'stopippgw' IPP authentication Typically undiscussed by vendors in their implementations. IPP itself provides no means to restrict or authentiate. The containing server must do that itself, via IP address restrictions or HTTP methods (RFCs 2068, 2069). IPP Gateway InfoPrint Manager provides a gateway service such that IPP clients (anywhere in the world) might submit jobs to your non-IPP printers. IPM 4.1 provided IPP service in the Windows version only; 4.2 added IPP support to the AIX version; 4.4 added IPP Gateway to Linux. The gateway operates, as its name implies, by listening on the standard IPP port number (631) - or some other designated port number - and directly hands incoming jobs to the IPM server. See also: LPD Gateway IPP Gateway in AIX It is implemented as a Java process, using /usr/lpp/pd/bin/ippgw.jar. As such, the command name in the AIX Process Table is "java", overall looking like: java -jar /usr/lpp/pd/bin/ippgw.jar ipp-listen-port=631 num-http-threads=20 ipm-server-host=localhost ipm-server-port=6874 ipp-base=/var/pd/ippgw The Java seems to hand the job to the IPM server via IPM API, as no command is executed to get the job there. This is good, compared to LPD, as the latter uses a series of commands with quoted strings - which runs afoul of quotes in job names. Commands: lsippgw List the ports that the IPP gateway daemon is listening on. If no daemon running, the command emits nothing. If running, its output will simply be "631". startippgw Start the IPP gateway. stopippgw Stop the IPP gateway. Logging: Minimal, in /var/pd/ippgw/, as files: ippgw.err. and ippgw.out.. Note that these files are not cut off during operation, and grow indefinitely, where the process persists on the inode number, and so does not start logging to a new instance of the log if the original is renamed. (And doing a kill -HUP on the process does not cause it to switch.) The only approach seems to be to do like 'mv ippgw.out.123 ippgw.out.20111021' just before performing a stopippgw; startippgw sequence when there is no activity. Notes: Nothing in job attributes indicates that a job arrived via the IPP gateway. The IPP Gateway is for submitting jobs, only: it does not respond to queries, such as from 'lpstat' or 'lpinfo' commands from Linux systems. (It returns a 404 error to such clients.) The HTTP service in the daemon responds to GET requests. A HEAD request results in a 501 (Not Implemented) error. This IPP server seems to be insensitive to parameters passed on the URI, of the form http:///printers/ ? See also: ippgw IPP Gateway in Linux Is problematic to implement because it wants to use the standard IPP port (631) which CUPS uses (and the CUPS DSS depends upon CUPS). Thus, to implement the IPP Gateway, some alternate port number would have to be used, which then means that all clients needing to access the IPP Gateway have to be specially configured. Start it: Command 'startippgw' (/usr/lpp/pd/bin/startippgw) or use IPPMI Stop it: Command 'stopippgw' (/usr/lpp/pd/bin/stopippgw) or use IPPMI Check it: Command 'lsippgw' In the process table, looks like: /usr/lpp/pd/jre/bin/java -jar /usr/lpp/pd/bin/ippgw.jar ipp-listen-port=632 num-http-threads=20 ipm-server-host=localhost ipm-server-port=6874 ipp-base=/home/me Logging: Minimal, in /var/pd/ippgw/, as files: ippgw.err. and ippgw.out.. Note that these files are not cut off during operation, and grow indefinitely, where the process persists on the inode number, and so does not start logging to a new instance of the log if the original is renamed. (And doing a kill -HUP on the process does not cause it to switch.) The only approach seems to be to do like 'mv ippgw.out.123 ippgw.out.20111021' just before performing a stopippgw; startippgw sequence when there is no activity. See also: startippgw; stopippgw IPP MIME type "application/ipp" IPP port number 80 or 631 IPP printing A pre-requisite is having IPP client software on your system. Then: 1. http://:631/ printers/ 2. Optionally, specify a proxy server for the client to use in order to access the printer across a firewall. 3. Optionally, enable chunking (an HTTP/1.1 feature), if the client supports it. Chunking may improve performance. To see a list of the printers available, enter the following URL form into a Web browser: http://:631/printers which will report logical destinations. Ref: IBM Infoprint 2085/2105 Ethernet and Token Ring Configuration Guide, chapter 25. IPP printing from Macintosh The Macintosh OS incorporates CUPS, so IPP printing is a natural for it. To set up... Go into System Preferences; Choose "Print & Fax"; Click the plus-sign (+) to add a new printer; Under "IP", choose the Protocol "Internet Printing Protocol - IPP", which uses IPP port 631; In the Address field enter the network address of the server, as either a network name (e.g., xxx.us.edu) or an IP address; (The Mac will probe that location with UDP SNMP packets.) In the Queue field, enter the name of a logical destination or queue within that server, or leave empty to get the default queue; (The Mac will probe that location with UDP SNMP packets.) In the Name field, enter a name by which you will recognize the print choice in a printing dialog; The Location field can be filled in with text as to the nature or location of the printer; In the Print Using field you may choose one of the numerous printer drivers which Apple supplies; Finally, click Add to create the printer definition. Usage problem: In testing, I find that a next job will not flow from the Mac to IPM until the previous job either concludes normally or is removed by the operator. The previous job will have a status of "Printing" in the Mac queue while the job sits in the IPM queue. I experimented with changing the LD's notification profile to include event job-assigned-to-queue, hoping job arrival would result in some "okay" result to be returned to the Mac, but no dice. There is no setting when defining a printer instance on the Mac that would influence this. There may be some CUPS config value for it. IPP printing from Windows Windows has had IPP client printing capability since Windows 2000. To set up its client capability: Go into the Printers control panel. Select "Add a printer". Choose to add a network printer. Select "Connect to a printer on the Internet..." In the URL field, enter: For IPP printing, the usual form is: http://:631/printers/ where an example would be: http://print-srv.us.edu:631/printers /psprt1 (Note that you have to enter the IPP port number, "631", rather than the symbolic name "ipp", as the latter will result in port 80 being used, while IPP and CUPS conventionally run on port 631.) If the Printername is not found among those defined in the server, the IPP server will return a 404 HTTP error, indicating "not found". Select an appropriate print driver. To see a list of the printers available, enter the following URL form into a Web browser: http://:631/printers Print jobs will be sent with a submitter name which is equal to the Windows logon name; so, if you logged on to your Windows box as "JaneLake", that is the name under which your print jobs will appear at the print server. See also: Windows job submission via IPP IPP protocol TCP IPP server, independent Consider implementing CUPS. www.cups.org ippgw The actual IPP Gateway binary, /usr/lpp/pd/bin/ippgw, invoked by 'startippgw', which in turn launches the Java process /usr/lpp/pd/bin/ippgw.jar. /ip_remote Unix directory/mount point and ext3 file system containing IPM installation files, created by running command mk_ip_remote, as found on the server product DVD. LV name = "ip_remote". The system which owns the /ip_remote file system is termed the InfoPrint Manager Software Server. The purpose in doing this is to create an NFS-exportable file system which can be mounted on other systems where the IPM server is to be installed. Those remote systems would also have a /ip_remote mount point directory defined, for NFS-mounting the file system, as an NFS client of the provider system. Once mounted, the following command would be invoked: /ip_remote/setup -s /ip_remote This is called a Pull type install, as a human is logged onto the target system, as root, to mount /ip_remote and then conduct an install session (which can be either GUI type or unattended). See also: mk_ip_remote; setup iprp1 ... iprp10 TCP reserved ports, generated into /etc/services by pdinitports. IPSC InfoPrint Solutions Company, the former IBM Printing Division, acquired by Ricoh. IPSelect Infoprint Select (q.v.). IPv6 support? IPM does not support IPv6, as of 2011/06 at least. ISP Image Size Parameter .jar Filename extension for Java ARchive files. Conceptually similar to Unix tar. Enables you to bundle multiple files into a single archive file. Typically a JAR file will contain the class files and auxiliary resources associated with applets and applications. Emacs understands JAR files, so you can readily browse them using the Emacs dired functions. http://java.sun.com/docs/books/tutorial/ jar/ java IPM server process, running as a child of pdnpmsrv, which serves the operator GUI's Check Status, More Information function, in presenting a real-time depiction of the checked printer control panel. Runs an snmp-trap port service. Identified in Process Table by its execution string "java Server". Problems: Can get hung, where the symptom is no More Information button shown in the Check Status windowette of the oper GUI; and running AIX cmd 'lsof' on the process will show one or more file descriptors with "TCP no PCB, CANTSENDMORE, CANTRCVMORE". Do a 'kill -9' on the process (which will cause its pdnpmsrv parent to die as well) and then restart pdnpmsrv. See also: Check Status; pdnpmsrv Java The IPM server environment made minor use of Java in 4.1, but moved into it more heavily in 4.2. The IPM 4.1 and early 4.2 server installation updated the AIX /etc/environment file to put the following at the head of the PATH: /usr/java14/jre/bin:/usr/java14/bin: This allowed the server and AIX GUI to readily and find that OS copy of Java. Dependence of the OS copy of Java became problematic, with security problems, and so as of IPM 4.2 PTF5, the server started installing and using its own, private copy of java: /usr/lpp/pd/jre/bin/java This gives the developers more control, and should result in more predictable server operation. The existing Java LPP's and /etc/environment settings were left untouched, as they may be used by other applications in the system: IPM abandons and leaves them in place. And though the pdserver process may have /usr/java14/jre/bin in its PATH, the java process under pdserver is directly invoking: /usr/lpp/pd/jre/bin/java -Xrs -classpath /usr/lpp/pd/bin/ipa.jar: /usr/lpp/pd/bin/penguin.jar: /usr/lpp/pd/bin/snmp.jar: /usr/lpp/pd/bin/modelplugin.jar com.ibm.infoprint.jlink.JlinkMain A side ramification of this change is that the Notify Daemon (notifyd) needs its /usr/lpp/pd/bin/startnotd Ksh script altered to add: export LIBPATH=/usr/lpp/pd/jre/bin/classic so that it can find and use the right libjvm.a, to avoid failures. Java, as required in Windows, for the The IPM GUIs in Windows want the running GUI Java to be the IBM-supplied Java: IBM Cross Platform Technologies for Windows (CPT) Version 2.0 Runtime Environment, IBM Build cn130-2020124. To verify this to be the Java in place, enter the following command line command: java -fullversion which should yield like: "J2RE 1.3.1 IBM Windows 32 build cn131-20020710" Installs in C:\ProgramFiles\IBM\Java13\ Refer to the README file in the JRE folder in the clients installation or maintenance CD-ROM images for details. During the install, you have the option of making this Java the default Java on your Windows system; but the GUI will run fine as a non-default install. Java version Get vial command: 'java -fullversion'. On AIX, will return like: java full version "J2RE 1.4.2 IBM AIX build ca142-20050609" Java 2, v5.0 Installed on Windows from the Common Clients CD, this installs in folder C:\Program Files\IBM\Java50\ . .jif In the computer world in general: In general parlance, the filename extension to identify a file as containing a JPEG/JIFF Image. (Jeff's Image Format) However, in IPM is means Job Information File. As seen on files in /var/psf/interrupt/. JNI Java Native Interface is a programming framework that allows Java code running in the Java virtual machine (VM) to call and be called by native applications (programs specific to a hardware and operating system platform) and libraries written in other languages, such as C, C++ and assembly. The JNI is used to write native methods to handle situations when an application cannot be written entirely in the Java programming language such as when the standard Java class library does not support the platform-dependent features or program library. It is also used to modify an existing application, written in another programming language, to be accessible to Java applications. Many of the standard library classes depend on the JNI to provide functionality to the developer and the user, e.g. I/O file reading and sound capabilities. Including performance- and platform-sensitive API implementations in the standard library allows all Java applications to access this functionality in a safe and platform-independent manner. Before resorting to using the JNI developers should make sure the functionality is not already provided in the standard libraries. Job In Infoprint, an object that represents a request to print or transmit one or more documents together in a single session. A job includes the data to be printed or transmitted, plus resources such as separator page, fonts, images, and overlays. Depending on how it was submitted, it may also include a job ticket. Synonymous with job bundle and print job. Job, cancel See: Cancel a job Job, delete (pending/processing 'pdrm -r 0 ' or: /printing jobs) 'pddelete -c job ' can delete a pending job where "-r 0" says to override any natural retention period to 0: to immediately remove the job, not wait until it expires. You will be prompted about proceeding with the operation (msg 5010-187), unless environment variable PD_CONFIRM_DELETE is set to "no". Not for removing jobs in the Retained Jobs area. If the job was printing, such that the deletion effects a "cancel", there will typically be records of the cancellation in the printer error log: see "Cancelled job records". Note: The Reference manual says: "Because of the way that Infoprint Manager pauses and cancels jobs, the totals for the pages completed could be inaccurate." See also: Job, delete and retain Job, delete (retained jobs) For this, you cannot use pdrm or pddelete, as they are for in-queue jobs, and you are trying to remove an already-processed job. You instead have to change the job's retention period to zero, thus: pdset -c job -x 'job-retention-period=0' : Job, delete and retain Your own job: 'pdrm ' Another user's job: 'pdrm :' Another user's job, and set Reason: 'pdrm -m "Reason..." :' removes the job from the pending queue and retains it per the job's natural retention period. You will be prompted about proceeding with the operation (msg 5010-187), unless environment variable PD_CONFIRM_DELETE is set to "no". If the job was printing, such that the deletion effects a "cancel", there will typically be records of the cancellation in the printer error log: see "Cancelled job records". Note: The Reference manual says: "Because of the way that Infoprint Manager pauses and cancels jobs, the totals for the pages completed could be inaccurate." See also: Job, delete Job, documents within See: document-sequence-number; number-of-documents Job, hold 'pdmod -x "job-hold=true" :' Note that you can also supply a reason for the action via the -m options. Job, release 'pdmod -x "job-hold=false" :' Example: pdmod -x "job-hold=false" ${HOST}:6014802675 Job, list one 'pdls -U :' Example: pdls -U aixsys1:5557710672 See also: Job document, list one Job, move to top of queue 'pdpromote' command. Job, pending, modify 'pdmod' command. For example, to change your job number 1234 so that it prints two copies: 'pdmod -n 2 1234' Job, reprint See: Reprint a job Job, submit for someone else See: Print for someone else Job, submit held 'pdpr -p -x job-hold=true ' Job and Document Defaults Settings of a Logical Destination, to define attributes to be pinned to incoming jobs which do not already have values assigned to those attributes. (Usually, the attributes closest to the job originator take precedence.) Job attribute, delete 'pdmod -x '==' :' Job attribute, modify See: pdmod Job attribute, set See: pdmod Example: pdmod -x 'job-hold=false' ${HOST}:1234567890 Job attributes, list 'pdls -U : -c job -r all' One thing IPM will not reveal about a job is the physical file name of its constituent documents. Job completion log /var/psf/jobcompletion.log (q.v.) Job completion log record, IPM 4.2 As described in /usr/lpp/psf/exits/ainuxjobcompletion.c Elements: 1. PrinterName (actual destination) len = 8 2. UserID (just username, no @host) len = 8 3. NodeID (sending hostname: 8 chars) len = 8 4. JobCopiesRequested len = 8 5. UserPagesStackedByBin[0] (#pages) 6. UserSheetsStackedByBin[0] (#sheets) 7. PagesStackedByBin[0] 8. SheetsStackedByBin[0] The above two numbers reflect the User values plus any error pages also stacked. 9. UserPagesStackedByBin[1] 10. UserSheetsStackedByBin[1] Values as preceding, but for next output bin. 11. PagesStackedByBin[1] 12. SheetsStackedByBin[1] 13. UserPagesStackedByBin[2] 14. UserSheetsStackedByBin[2] 15. PagesStackedByBin[2] 16. SheetsStackedByBin[2] 17. FontsUsed (count of) 18. ResidentFontsUsed 19. OverlaysUsed 20. HardSegmentsUsed 21. SoftSegmentsUsed 22. DataObjectResourcesUsed 23. StartDate When PSF starts processing the job. This can be like 5 seconds after the job was released, where the job had to wait for a preceding job to finish printing before its turn came to use the printer. MM/DD/YYYY 24. StartTime hh:mm:ss 25. EndDate When PSF finished processing the job...when the IPDS has been fully sent to the printer; but the printer may not have printed and stacked all the pages. MM/DD/YYYY (may be empty) 26. EndTime When PSF detects that all of the pages for this job have been printed and stacked. If there were errors or operator commands affecting this job, all pages may not have printed, but the pages that PSF did send have been stacked safely. hh:mm:ss (may be empty) Empty is characteristic of printer failure, such that job has to be completely reprocessed, later, on another printer. BUT: The job will have produced many pages to the stacker, and the CompletionDate will likely be populated; and, the user will thus have been charged for the printing of the ostensibly incomplete job. 27. CompletionDate Output is through finisher and stacked. MM/DD/YYYY 28. CompletionTime hh:mm:ss 29. ExtendedSpoolID (Global ID #) 30. SpoolID 31. JobInfo (Job file name) This is a 56 char field, with long job names truncated to 55 chars, and shorter names right-padded with blanks. Notes: Job attributes are not reflected: no indication of simplex vs duplex, no job size (octets, bytes), no job creation time, no job submission time, no page description language (pdl) type. (Get bytes size from accounting record field "Octets Completed".) The Jobcompletion log has been seen to not be susceptible to Daylight Savings Time discrepancies, as the accounting can be. In particular, the absence of job creation time thwarts desires to not charge a user for a job reprint, given that accounting is best done at this user exit point (where we are certain that the job is fully printed+stacked). Job completion log record, IPM 4.4 As described in /usr/lpp/psf/exits/ainuxjobcompletion.c Elements 23 and 24 are new in 4.4. 1. PrinterName (actual destination) len = 8 2. UserID (just username, no @host) len = 8 3. NodeID (sending hostname: 8 chars) len = 8 4. JobCopiesRequested len = 8 5. UserPagesStackedByBin[0] (#pages) 6. UserSheetsStackedByBin[0] (#sheets) 7. PagesStackedByBin[0] 8. SheetsStackedByBin[0] The above two numbers reflect the User values plus any error pages also stacked. 9. UserPagesStackedByBin[1] 10. UserSheetsStackedByBin[1] Values as preceding, but for next output bin. 11. PagesStackedByBin[1] 12. SheetsStackedByBin[1] 13. UserPagesStackedByBin[2] 14. UserSheetsStackedByBin[2] 15. PagesStackedByBin[2] 16. SheetsStackedByBin[2] 17. FontsUsed (count of) 18. ResidentFontsUsed 19. OverlaysUsed 20. HardSegmentsUsed 21. SoftSegmentsUsed 22. DataObjectResourcesUsed 23. DataObjectFontsUsed 24. ResidentDataObjectFontsUsed 25. StartDate When PSF starts processing the job. This can be like 5 seconds after the job was released, where the job had to wait for a preceding job to finish printing before its turn came to use the printer. MM/DD/YYYY 26. StartTime hh:mm:ss 27. EndDate When PSF finished processing the job...when the IPDS has been fully sent to the printer; but the printer may not have printed and stacked all the pages. MM/DD/YYYY (may be empty) 28. EndTime When PSF detects that all of the pages for this job have been printed and stacked. If there were errors or operator commands affecting this job, all pages may not have printed, but the pages that PSF did send have been stacked safely. hh:mm:ss (may be empty) Empty is characteristic of printer failure, such that job has to be completely reprocessed, later, on another printer. BUT: The job will have produced many pages to the stacker, and the CompletionDate will likely be populated; and, the user will thus have been charged for the printing of the ostensibly incomplete job. 29. CompletionDate Output is through finisher and stacked. MM/DD/YYYY 30. CompletionTime hh:mm:ss 31. ExtendedSpoolID (Global ID #) 32. SpoolID 33. JobInfo (Job file name) This is a 56 char field, with long job names truncated to 55 chars, and shorter names right-padded with blanks. Notes: Job attributes are not reflected: no indication of simplex vs duplex, no job size (octets, bytes), no job creation time, no job submission time, no page description language (pdl) type. (Get bytes size from accounting record field "Octets Completed".) The Jobcompletion log has been seen to not be susceptible to Daylight Savings Time discrepancies, as the accounting can be. In particular, the absence of job creation time thwarts desires to not charge a user for a job reprint, given that accounting is best done at this user exit point (where we are certain that the job is fully printed+stacked). Job document, list one 'pdls -U :.N' Example: pdls -U aixsys1:5557710672.1 See also: Job, list one Job files In server directory /var/pd/ with names like "pdpr5y4paZ". Job ID The usually 1 or 2-digit job number, which is the number by which the user can manipulate the job via conventional commands, such as lprm. See also: job-identifier Job name Job property: Name Attribute: job-name (q.v.) Job number See: Global job identifier Job page count See: Page count, job Job priority See: job-priority Job segments The Input Manager is the part of Infoprint Manager that breaks print jobs into segments to allow greater flexibility during processing. The Input Manager stores job segments in its workspace. Segments remain in the workspace either until they are manually deleted or the workspace fills up, depending on how you choose to manage the workspace. By default, the Input Manager workspace is located at /var/psf/segments. Job size See: total-job-octets Job size limit The PTF U802055 Release Notes specify that: "the server does not support transforming PCL, PDF, and PostScript datastream files larger than 2 gigabytes." Job state reason See: current-job-state Job state reasons See: job-state-reasons; Status Job state reasons for held jobs 'pdq -d -r owner,job-state-reasons -x 'filter="current-job-state==held"' ' See also: Status Job submission, restrict By setting authorize-jobs=true. Job submission and queueing IPM will accept jobs for printing if what they ask is possible for the printer, even if that capability is not available at the moment; but jobs which ask the impossible are rejected at submit time. For example, you submit a job with the page color attribute "yellow": sure, the printer can do that once yellow paper is loaded, so the job is accepted, "resources not ready". But try to submit a job to a cut-sheet printer asking for two-foot square paper and it will be rejected as not possible. Job submission method There are times you want to know how a job arrived at the IPM server: in particular, whether via LPR or IPSelect. That is, did the job reach the IPM server queue via a gateway (LPD) or via direct submission from an Infoprint-aware program. The way to tell is via the attribute document-file-name (GUI: "File names"), which reflects the closest transfer point as the job got the the IPM server. (This name is not to be confused with the job-name attribute, reflecting the name assigned to the job by its originator.) A job submitted via LPR will have a document-file-name like: /var/spool/lpd/dfA175acsn03.1082912800 or /var/spool/lpd/dfA050acsrs4.1231940231.1204304 where the long number therein is the Unix seconds-epoch timestamp of when the file arrived at the IPM LPD Gateway. (See via the Document Information tab of the GUI, "File names" field - which is attribute document-file-name. The literal following the dfA175 and preceding the period, "acsn03", is the actual system where the job originated.) A job submitted via Infoprint Select (PC) will have a file name like: C:\Program Files\IBM\Infoprint Select \Spool\408bf029.SPL Job submission timeout Server property: job-submission-timer Managed via admin GUI, Server -> Properties, General Job Time column in 2085/2105 web page Under View Details: Job Status, there is a Job Time column. In conjunction with IPM, it represents the start time of the ainhyper process for this printer - whose lifetime is determined by the AD Release Time (destination-release-timer) value. If your release time is 0 (no release) then the Job Time will be "frozen" until the AD is shut down; if the release time is a limited value, the Job Time will reset if there is a lull in processing such that the AD is released and the ainhyper process goes away. See: destination-release-timer; Release time (sec) job-attribute-supported A misspelling of attribute job-attributes-supported (q.v.). job-attributes-supported Powerful AD attribute which can be used to add job attributes which this AD will then "support". And they will then show up in the GUI, where you can then work with them that way. (For example, a BSD DSS AD would not normally have an Auxiliary/Separator Sheets tab, but one would appear if this mechanism were used to add such attribute support.) This is usually done to an AD to keep jobs from failing on job-state-reasons = required-resources-not-supported, required-resources-not-supported = actual-destinations-requested. There is no magic in this: it allows the AD to *tolerate* the presence of the usually unsupported job attribute, but the AD's standard processing does not fulfill the requirements implied in the attribute, in that the software and circumstances are incompatible with the implied requirements. For example, you can use this approach to allow a BSD DSS to accept job-rip-action=rip-and-hold in a job, but given that the attribute is for AFP printing, the job is not held after transformation. Note that there is no field in the Admin GUI for modifying this: it has to be done from the command line, or used in an attributes file. For sample usage, see the Procedures manual, topic "Allowing the auxiliary-sheet-selection job attribute with the BSD DSS" (where it is misspelled as job-attribute-supported). job-client-id Job attribute: the local identifier number for the job, aka "local ID". GUI label: ID The value can be a number from 1 to what is coded for environment variable PDIDTABLE. See also: PDIDTABLE; /var/pd//pdjobs job-comment Job/Default Job attribute: Provides information to be associated with the job - ignored by IPM, but available at an attribute value for other processing. GUI label: Description, on the Job Other tab. DSS: All Allowed values: A text string of up to 4095 characters to be associated with the job. You might use this field to pass special information (what you may consider to be "private attributes") to a transform sequence program, such as the private keyword "nosep" to suppress generation of a separator page; or instructions on what elements to generate in a header page. job-finishing Job/Default Job attribute: Identifies the finishing options for this job. GUI Label: Finishing options For PSF DSS, when you specify a value for job-finishing, IPM creates an inline form definition. Do not use the document attribute form-definition to specify another form definition. See also: Finishing options; form-definition ; Inline resources job-hold Job/Default Job attribute. GUI label: Hold Code in the initial-value-job attributes file. Specify yes/no or true/false. Null means "use default". Can be used to cause arriving jobs to be in Hold state in their queue, as to prevent processing until the operator or some site queue scanner releases them. Note that there is no such hold capability at the queue level, where you might expect to be able to say "hold all jobs entering this queue". Infoprint Select Notifications note: If hold is in effect, jobs enter the queue in hold state without the undesirable side effect of a message back to the submitter. OID: 1.0.10175.1.3.1.32, in the pdb/spl_job/ file. See also: job-rip-action job-identifier Job attribute. Identifies the job via a 10-digit number. See: Global job identifier job-log Job attribute. May exist, to contain messages added by IPM as the job processes. Operates via the job-log delivery method in IPM notifications. job-message-from-administrator Job attribute. Describes the reasons that you are changing or have changed the job - up to 4095 chars. GUI label: Message from administrator Can be set via the -m option of the 'pdmod' command, as when holding a job; or the 'pdrm' command, convenient for noting why a job failed RIP. Can be set via the -m option of the following commands: pdmod pdpause pdpromote pdresume pdrm pdset job-message-to-operator Job attribute. Provides a message that Infoprint can send to an operator when it adds the job to the queue - up to 4095 chars. GUI label: Message to operator job-name Job/Default job attribute: the job name, as typically appears on the job header page. GUI label: Name Length: Up to 256 chars See also: document-file-name job-originator Job attribute identifying the person who submitted the job or the program that initiated the job, usually plus the network identity of the host which was the last to hand the job to IPM. This attribute is established at job creation time and cannot be modified. In network submission, the job-owner will be of the form Username@Hostname, while jobs submitted locally from within the Infoprint computer system will simply be of the form Username. In the GUI, the "Sent by" column reports this name (plus the origin computer name). See also:job-owner; results-profile; user-name job-owner Job attribute identifying the owner of the job, and for whom job will print: that name will appear on the job separator page. This attribute is established at job creation time and cannot be modified. In network submission, the job-owner will be of the form Username@Hostname, while jobs submitted locally from within the Infoprint computer system will simply be of the form Username. In the GUI, the "Sent by" column reports this name (plus the origin computer name). See also:job-originator; results-profile; user-name job-page-count The job-supplied attribute which tells IPM ahead of time how many pages are in the job. Usually corresponds, and may be taken from, the document page-count value. Note that the job-page-count value may be adjusted after job completion, based upon what the printer tells IPM that the actually printed page count was. For the per-AD accounting logs, AD types which cannot get the pages completed value from the printer cause the count to be obtained from the job-page-count attribute (which can be set by the user); or in some cases, IPM obtains the count by analyzing the datastream. If neither is possible, the value will be null or the attribute undefined. (For PostScript, IPM sets that attribute from the like "%%Pages: 14" value that usually appears at the end of the job, referenced by frontal "%%Pages: (atend)". If there is no such value, the job-page-count attribute is undefined for the job. Jobs which have "%%Pages: (atend)" but no subsequent "%%Pages: nn" have job-page-count defined but no value.) In rip-and-hold processing, the job-page-count value will be set for PostScript jobs (ps2afp processing), but not for PDF jobs (pdf2afp processing). To get the PDF page count, you can capture the output of the transform, using its -v flag, as in pdf2afp -o /tmp/xxx -v Some.pdf where one of the output lines is like: Wrote 4 pages of output type AFPDS IO1 (G4 MMR, 260), at approx 27.19 ppm and afterward set the job-page-count attribute. See also: Page count; pages-completed job-priority Job/Default Job attribute: Specifies a number representing the scheduling priority for the job (within its queue, not across queues). Actual destinations that employ a priority-based scheduler use this attribute. A larger value specifies a higher priority. Possible values: 1 - 100 (highest) Default: 50 job-retention-period Initial-value Job attribute to define how long to retain jobs, if retain-forever is not in effect. GUI: Logical destination, Job and Document Defaults, Job Retain Time tab Note that changing the value does not affect the retention periods of jobs which arrived before the change. Advice: A retention period of 1 hour or less is problematic, as the icon of such jobs will start yellow - which obscures job failure conditions which would otherwise cause the icon to be black, and so the operator can fail to perceive the problems with completed jobs unless she looks at job properties. Whereas a question about a job will almost always be asked within the first hour, it is best to have the retention period be at least 2 hours, so that the icon color is indicative during that first hour. WARNING: The Java-based GUIs which interface to the server maintain data on all retained jobs. Java is an utter pig, and the more jobs you retain, the worse the Java-based GUI performs. See also: Job scheduling; Retain forever; retain-forever job-retry-count-limit AD attribute. Indicates the number of times that IPM should attempt to submit a job to this actual destination after an initial failure. GUI label: Number of times to retry jobs DSS: AIX,BSD, PSF, Fax, Passthrough, IPP, Print Optimizer Type: Resettable, single-valued Allowed values: An integer from 0 through 2147483647. Default value: 0 Usage guidelines: - Values greater than 0 are useful when poor network line quality causes temporary loss of communication between this actual destination and the backend program. A second or subsequent attempt to submit the job may succeed if communication can be reestablished. - If the job cannot be submitted within the specified number of attempts, IPM disables the AD and places it in the needs-key-operator destination-state. - The job-retry-interval AD attribute indicates the number of seconds between attempts. - If the value of this attribute is 0, the job-retry-interval attribute is ignored. - If the value of the job-retry-interval attribute is 0, this attribute is ignored. (However, the AD can still enter needs-key-operator destination-state.) See also: intervention-timer, for PSF job-retry-interval AD attribute. Indicates the number of seconds that IPM should wait between attempts to submit a job to this AD. GUI label: Interval to retry jobs (sec) DSS: AIX, BSD, PSF, Passthrough, IPP, Print Optimizer Type: Resettable, single-valued Allowed values: An integer from 0 through 2147483647. Default value: 0 A value of 30 (seconds) seems reasonable. Usage guidelines: - If the job cannot be submitted within the specified number of attempts, IPM disables the AD and places it in the needs-key-operator destination-state. - The job-retry-count-limit AD attribute indicates the number of attempts after an initial failure. - If the value of this attribute is 0, the job-retry-count-limit attribute is ignored. - If the value of the job-retry-count-limit attribute is 0, this attribute is ignored. (However, the AD can still enter needs-key-operator destination-state.) See also: intervention-timer, for PSF job-rip-action Job/Default Job (LD) attribute for how IPM should convert the job to raster image patterns, and whether to hold the RIPped job, print it, transmit it, or neither. For the initial-value-job attrs file. GUI label: Rip option Possible values: rip-and-hold rip-and-hold-ignore-ready rip-and-print rip-and-print-ignore-ready rip-only rip-only-ignore-ready See explanation of each value, individually defined. job-rip-actions-supported AD attribute indicating whether the AD supports transforming a job to AFP and then holding the job. GUI label: RIP options allowed within tab: Job DSS: PSF, Email, Generalized Fax, Infoprint 2000, Print Optimizer (not AIX or BSD) The arriving job will carry a job-rip-action attribute, whose value must be one of those supported in order for the job to proceed. See also: rip-and-hold; rip-and-print job-ripped-by-server Job/Default Job attribute for Email and Infoprint 2000 DSSes. GUI: "Override RIP at destination" Indicates whether IPM should convert the job to MOD:CA-P and transmit it as email or to be printed with the Infoprint 2000 DSS. If true, IPM converts the job into MOD:CA-P. If false, IPM determines if the job can be printed directly by the Infoprint 2000 DSS or sent directly as email without converting to MOD:CA-P. When a job cannot be handled directly without conversion, the job is requeued on the spooler. job-size-range-ready Defines the range of job sizes in bytes (octets) that this actual destination can accept and print. Values chosen must be within job-size-range-supported values. That is, the job-size-range-ready values are an arbitrary subset of the limiting job-size-range-supported values. GUI: AD properties, Job tab, Size ready (Bytes) job-size-range-supported Defines the range of job sizes in bytes (octets) that this actual destination can accept. Values chosen must be equal to or greater than the range you specify for the job-size-range-ready. That is, the job-size-range-supported are the envelope in which the job-size-range-ready values must fit. GUI: AD properties, Job tab, Size ready (Bytes) job-state-reasons Job attribute, non-settable, multi-valued. Identifies the one or more reasons that a job is in the held, terminating, or retained state. One or more of the following values will be set on the attribute: aborted-by-system cancelled-by-operator cancelled-by-user completed completed-successfully completed-with-errors Can occur if there was a paper jam in the midst of the job but it completed. Or the job requested stapling and there were too many or too few sheets for that to be possible. The error cause won't be available in job attributes; but you can usually find it in /var/psf//error.log deadline-in-jeopardy imposition-failed job-hold-set job-print-after-specified required-resource-not-ready required-resource-not-supported retained-immediately rip-and-hold-completed rip-completed rip-failed Example: resources-not-supported as in the case of a Format which no configured printer supports (e.g., TIFF). Example output from 'pdls' where a job was processed with job-rip-action = rip-and-hold: job-state-reasons = rip-and-hold-completed job-hold-set (Note that the values appear on multiple pdls output lines, where lines beyond the first are without the attribute name.) Value completed-with-errors usually indicates a job which requested stapling, but had too many sheets for a staple. If this attribute value is null, the job is not in one of these states. When the job first arrives, this attribute is null. If the job is reprinted (move job), the attribute value - which was something after its prior printing - is reset null. (Thus, you cannot use this attribute to detect whether a job is being reprinted.) GUI label: Reasons See also: current-job-state; Status job-submission-timer Server attribute to specify the maximum time that the server will try to assemble a job before it will time out if it has not assembled all the documents. After the timeout, the job submission is identified as complete and IPM sends the job to the queue. GUI label: Job submission timeout Specify a value as [hh:]mm minutes. Default: 30 (minutes) Jobs, best column settings in GUI The following columns and order are best: Submitted to Submit time Sent by Job Status Pages Format Forms Jobs, current and pending In /var/pd//pdb/suv_job/ (q.v.). Jobs, list all 'pdls -U :' Lists all current and retained jobs. Note that the output is very wide. Jobs, list for destination 'pdq -p -r all' Lists jobs in the Jobs queue, not the Retained Jobs area. Jobs, prevent submission of Oddly, there is no operational setting in IPM to allow temporarily turning off the accepting of jobs while the server is up. The only realistic choice seems to be to do a shutdown of the server. Jobs display, possible columns Batch Class Copies complete Creation time Deadline Deadline time Description Destination Est comp time Est proc time Form def Format Forms Global ID ID Job Layout format Media Output bin Overlay Pages Priming Job Print time Priority Requested Sent by Sheets Size Status Submit time Submitted to Tray Jobs in a queue, list 'pdq -p ' where DestName is the name of any LD or PD in that queue. Jog To offset-stack in the printer output tray. Offset-stacking. See also: Offset stacking allowed? Jog between copies GUI: Actual destination, Job and Document Defaults, Document Processing tab See also: Offset stacking, allow Jog between jobs For offset stacking of jobs in the output tray of the Infoprint 2000 printer. JP2000 DSS KDK JPEG file A JFIF-standard file will start with the four bytes (hex) FF D8 FF E0, followed by two variable bytes (often hex 00 10), followed by ASCII 'JFIF'. JPEG sample /usr/lpp/psf/jpeg2afp/sample.jpg (a large image of the Coast Guard square-rigged sailing ship Eagle) JPEG transform /usr/lpp/psf/bin/jpeg2afp Beware that the transform likes to print by dots and, at 600 dpi, an image of 845x1156 which looks big on screen (computer display resolution is typically 72 dpi) will be little bigger than a postage stamp when printed. This points out the difficult thing about image files: they have no absolute size - only pixel dimensions. It is best for the user to print them via PostScript, where page and image size can be chosen by the originator. JPSF An unexplained acronym which shows up in "Options installed" (q.v.). .js Filename extension for a Job Script, like in /var/pd// 2360105446.0..js Keep failed jobs Queue properties entry on General tab. Attr: requeue-failed-jobs See also: rip failed Key operator Someone trained in the operation of a printer or other device, who can deal with device problems which require specific knowledge of the device in order to restore service, such as replacing toner and clearing jams. The phrase may be deemed to mean that this "key person" is needed to deal with the problem; and it may derive from times when device doors had locks to prevent novices from tinkering with the innards, thus requiring the person with the key and requisite knowledge of the device. State: needs-key-operator This is in contrast to more trivial tasks such as refilling paper trays, which can be performed by any person, not requiring training. (This is the needs-attention destination-state.) See also: needs-attention; needs-key-operator LANG Unix environment variable. Must be set to en_US else get error "Unable to open message catalog". Late binding In Infoprint, waiting to assign a job to an actual destination until it is about to be processed. Late binding permits Infoprint to route a job to the first suitable actual destination that becomes available. Contrast with early binding. Controlled by attr assign-to-destination (q.v.). LAYOUT PPFA: The more advanced Record Format command for processing each input data line. LAYOUT cannot be used where the traditional PRINTLINE command is used: the two are mutually exclusive. See also: Record Format processing LD disabled, effects Attempting to submit from Infoprint Select to a disabled LD results in pop-up message: The following error occurred during job submission: 5010-562 Destination _____ in server _____ is disabled and cannot accept submission requests. Report this error to your system administrator. where the job then sits in the Windows spool, in Printing status, unable to advance into the IPS spool. Attempting to submit from an AIX system which is remote from the IPM system results in the local AIX spool accepting the job, which then quietly sits indefinitely, with the remote destination marked as Down, where an AIX 'enable' does no good. LD Interlock As seen in Infoprint 2105 ES printer problem messages, refers to the Laser Diode Interlock, which knows if some part of the printer is open. LDAP support Added to Infoprint Select in AIX PTF U100003 (2010/09). LEF Long Edge Feed: in the printer, paper is fed via long edge first. This is the most common method in cut-sheet printing, in that it allows more sheets to be active in the printer at one time, maximizing speed. Contrast with: SEF Letter Media (paper) size: 8.5 x 11" 2040 x 2640 pels 612 x 792 points But: This is the size of "letter" paper only in the United States and Canada: in the rest of the world, "letter" size is A4. Note that it is common in printers to disable edge-to-edge printing, to avoid toner getting onto the mechanicals, making a mess, and causing paper to jam. Printers thus enforce a "hold-back", to stay away from the edge: for Infoprint 2085/2105 that is 2 mm (0.078"; 5.67 points). See also: default-medium; Edge-to-edge Lexmark International, Inc. Maker of small and workgroup printers. IBM's smaller Infoprint printers are actually re-branded Lexmark printers. Ironically, Lexmark is the company that resulted from IBM selling its typewriter and low-end printer businesses in 1991. libApiDS.so The client API library. AIX: /usr/lpp/adsm/api/bin/libApiDS.a Unix: /usr/adsm/api/libApiDS.so License The server install contains a license file, like "aix_base.ecf". Licenses are not reflected in AIX filesets. See also: Options installed License files These are textual Enrollment Certificate Files (____.ecf), containing a variety of information about the license, the most important piece being the product password. aix_base.ecf The base license for AIX. aix_mspa.ecf Medium Speed Printer. aix_ppfa.ecf Page Printer Formatting Aid software license. aix_wgpa.ecf WorkGroup Printer. During installation, these files are references to verify entitlement. The results of the licensing operation ends up in file /usr/lpp/Infoprint/install/ipm.ini . License files directory, printers /var/pddir/default_cell/printers/license Files herein are generated from the execution of the 'setup' shell script provided on a printer feature CD-ROM, such as "Infoprint Manager Medium Speed Printer Feature". See also: Options installed Line, rotate on page PPFA: Under PRINTLINE, code DIRECTION to print the whole data line that way, or add a following FIELD command with DIRECTION on it instead to process part of a data line that way. Line data Data - traditionally, EBCDIC - prepared for printing on a line printer, where fixed-width character sizes are in effect and the first character of each text line is usually for carriage control, to govern spacing and overprinting. "Line data" really means "Line printer data". Attributes: chars; page-definition Ref: Procedures manual: "Working with the transform for line data", "About line data"; "Fonts for printing line data" Ref: PPFA manual line2afp ASCII, S/370 line data transform. To print ASCII, you must specify a page definition (pagedef option). If the pagedef does not name any fonts, and you want the whole file to print with only one font, then the input file must not contain table reference characters and you must: - Specify trc=no. - Use chars to indicate the single font in which the file should be printed. If the input file is unformatted ASCII (the usual case), but the fonts you are using contain EBCDIC, not ASCII, code points (for example, you specify CHARS=GT15), you can specify one of these exit programs via inpexit: /usr/lpp/psf/bin/apka2e (AIX) Converts ASCII stream data to EBCDIC stream data. Be aware that the chars choice needs to work hand in hand with the formdef choice, so that characters fit the lines. Sample, for ASCII: line2afp cc=no fileformat=stream inputdd=/etc/motd outputdd=line2afp.output formdef=F1H50111 pagedef=P1A06462 trc=no chars=42B2 (42B2 is 10 cpi Courier 12 pt) "inputdd=" may be omitted if the input comes from Stdin, as for example: cat file1 file2 | line2afp ... Note: The line2afp command in IPM AIX and Windows is the same module as the 'acif' command (in AIX, line2afp is a symbolic link to acif) and uses the 'acif' command parameters for conversion to produce output for printing. AIX accounting records reflect invocations of the symlink target, acif, rather than line2afp. Job page count: Note that this transform does not cause the job-page-count attribute to be set, nor does its msgdd output messages report the number of AFP pages generated. The only alternative seems to be to scan the AFP file for the count, one approach being: afpdmp | grep BPG | wc -l See also: ACIF; ASCII fonts; GT10; pdpr line2afp output file The binary output file does not contain any path names, as may be specified on the pdeflib= or ovlylib= specs. specified in the transform operation LKMA License Key Management Application. As found in IPM 4.4. Via GUI: pdlicmgm Via command line: pdlicmgm Options... Ref: Getting Started manual local job identifier (local ID) In Infoprint, a job identifier automatically generated by the server, identifying the job to the person who submitted it. Infoprint maps a local job ID to a global job ID. See also: job-client-id; /var/pd//pdjobs Locale In the IPM Linux install, is coded in the ipin_response file iprLocal=____ definition, where en_US is the standard locale for the USA. Managed via admin GUI, Server -> Properties, General Log accounting data See: Accounting data, log log-accounting-data Server/AD attribute for whether or not accounting data should be logged in individual AD log files in /var/pd//accounting.logs/ . Code: true/false or yes/no The AD definition ultimately decides, but may defer to the overall server definition. Note that this choice is a yes-no type, and does not participate in the Auxiliary/Separator Sheets regimen for user exits. See: Accounting data, log See also: Accounting data, log; accounting-exit; pdaccount Logical Column in GUI, Printers section. Reflects the Logical Destinations which feed this Actual Destination. Curiously, the names it lists appear in the order that the Logical Destinations were defined in IPM, not alphabetical. Logical Destination In Infoprint, an object to which users submit their jobs. The logical destination routes jobs to one or more actual destinations representing output devices such as printers, electronic mail systems, or fax machines. Though the queue to which such submitted jobs go may be associated with multiple physical destinations, the logical destination may be bound to a single physical destination. Contrast with Actual destination. See also: Logical Printer Logical destination, copying To make a copy of a logical destination, do not use the Copy item in the first level of the logical destination right-click: instead use the Copy under the Job and Document Defaults item of that menu, in order to have all the attributes copied. Logical destination, disable 'pddisable :' You can customize to allow enabling and disabling logical destinations through menu and toolbar actions. Disabling a logical destination causes attempted job submissions to be rejected with message 5010-562. And, when using an AIX lpd gateway, each message also occurs in the /var/spool/lpd/pdlpd_gateway.error_log. Rejection is not a good idea, so disabling is undesirable. Instead, use the GUI Hold selection to hold incoming jobs (job-hold attribute). This is more awkward to change, but has a better effect. Logical destination, enable 'pdenable :' Logical destination attribute destination-name-requested (q.v.) Logical destination Attributes, change 'pdset -c destination -x "Attribute=Value" [:]' Use attribute+=value to add a value to a multi-value attribute. Use attribute-=value to remove a value from a multi-value attribute set, or render a single-value attribute null (reset to default). Use simply "attribute==" to remove all values from the attribute so as to have it lapse to a default value. Logical destination Attributes, list 'pdls -c destination -rall :' Logical destination files In /var/pddir/default_cell/printers, along with actual destinations. Note that these files are rewritten in a server restart. Logical destination job acceptance If an LD is Disabled, it will reject jobs... An Infoprint Select job submittor will get a pop-up box saying: 5010-562 Destination ____ in server ____ is disabled and cannot accept submission requests. Alternately, the IPM administrator could go into the LD Job and Document Defaults and under tab Job General change Hold to Yes. Jobs will be accepted, but will get a Status of "held" (black icon). They can thereafter be released. This mode is desirable where you don't want jobs to process until released by the operator, and don't want to depend upon the iffiness of the corresponding AD being disabled or shut down. Logical destination job and document It is *not* under the Properties for the defaults logical destination. In the GUI, select the logical destination, click the right mouse button, select "Job and Document Defaults", then "Modify". Logical destination name attribute destination-name Up to 255 characters for the name. Note that the name is case-sensitive: users must submit to this logical destination exactly as defined. Logical destination type As in a pdcreate: destination-realization = logical Logical destinations, list 'pdls -c destination -f "destination-realization==logical" : Note: This take some time, even when " && associated-queue==____" is added. logical-destinations-assigned AD attribute: Lists the logical destinations through which submissions to this actual destination are forwarded. It is not the case that users should be submitting to ADs, but this is available to set a default redirection (which may not be appropriate in all cases). It is the case that LDs point to one or more ADs: this provides a backware reference. GUI Label: Route submitted jobs to When a job submission is received at an actual destination object with the logical-destinations-assigned set, the actual-destinations-requested attribute is set to the name of the actual destination that received the request, and then the job is submitted through the specified logical-destinations-assigned. If logical-destinations-assigned is not set in the AD, the actual destination does not accept direct job submission requests, which are rejected with an unsupported error message. logical-destinations-assigned Queue attribute: Lists the logical destinations handled by this queue. This is a non-modifiable attribute. GUI Label: Logical destinations assigned Note: Do not define this field when defining a queue: the field will be automatically populated when LDs are defined, and reduced when LDs are deleted. (If you do name LDs when defining the queue, it's too easy for the list to be outdated, where one or more of them do not actually exist, which will result in an unsettling error message when the GUI is launched.) Logical Printer In Infoprint, a type of logical destination. The logical printer routes jobs to one or more physical printers representing printing devices. In AIX, doing 'enq -A' will show, at the end of the listing, the set of logical printers. See: AIX printing commands accommodate IPM Logs In the server directory: /var/pd/ Long Edge As seen in Infoprint 2085/2105 panel message: "Load 8 1/2 x 11 Long Edge Plain in Tray 1". Refers to how paper is fed out of the tray, which is from its wider (11") edge. This is how most pageprinters print, in that this arrangement of paper in the linear paper path allows more sheets to be in the path at one time than if they were strung out lengthwise. longest-job-first In Infoprint, a queuing technique where the next job assigned to the first position in the queue is the longest job in the queue; that is, longest in terms of size, not expected processing time. Contrast with deadline, FIFO (first-in-first-out), job-priority, and shortest-job-first. Low speed printer Printer type classified as printing in the range of 63 - 91 ppm. Previous: Workgroup printer Next: Medium speed printer lpd The AIX Line Printer Daemon. Listens on port 515 (service name: "printer") and queues files in /var/spool/lpd/, with the conventional cf* and df* names. The AIX LPD is tailored for the AIX printing system, and issues the 'enq' (/usr/bin/enq) command to queue the file - which may result in it being "handed" to Infoprint Manager by virtue of 'enq' secondarily invoking the /usr/lpp/pd/bin/pdenq command, if that exists, which in turn invokes command /usr/lpp/pd/bin/ipm_pdenq. File /etc/locks/lpd contains the PID of the currently running instance of the lpd daemon. Note that lpr command invocations within the AIX system do not involve sessions with lpd. Started in: /etc/rc.tcpip LPD, start at boot (Linux) Happens because /etc/rc.local contains an entry to run /etc/rc.lpd which in turn reads /etc/rc.lpd.daemons to process any start commands therein. As installed, there is a 'startlpd' command in that file, which is commented out, with the line above it saying "Uncomment the following line to start the LPD daemon." LPD (Linux), start manually As superuser, invoke: startlpd Normal response: 5010-405 Successfully started server ipmlpd. If it was already running: 5010-618 The server ipmlpd is already operational. LPD Gateway, AIX The AIX system in which the InfoPrint Manager server runs may also run the AIX lpd (SRC) subsystem. That lpd can then feed jobs to InfoPrint Manager. Note that jobs submitted via the 'lpr' on the print server system do not go through the AIX lpd; they are directly handed to the IPM server. For background, see AIX doc: "Printers for BSD 4.3 System Managers". Ref: Getting Started: Using the LPD Gateway with Infoprint Manager for AIX See also: Windows job submission via LPR LPD Gateway, Linux InfoPrint Manager for Linux provides its own line printer daemon (ipmlpd) to receive jobs through the LPD Gateway to an InfoPrint Linux server. InfoPrint Manager LPD is a daemon that lets you submit print jobs from other operating systems using a Line Printer (LPR) client. InfoPrint Manager LPD submits the files it receives directly to an InfoPrint destination and supports the -o options that are available with some LPR clients. (-o options allow you to specify advanced InfoPrint print options, such as form definitions and page definitions. The IPM LPD stands in place of the CUPS LPD (RPM cups-lpd, which supplies /usr/lib/cups/daemon/cups-lpd). Port number: 515 ("printer"). You need to have iptables open that port to all systems needing access. There is no /etc/hosts.lpd needed with this LPD implementatioh. TO START: /usr/lpp/pd/bin/startlpd TO STOP: /usr/lpp/pd/bin/stoplpd The arrangement works as documented: there is no need to redundantly define the IPM printers in CUPS. See also: startlpd; stoplpd LPD Gateway errors /var/spool/lpd/pdlpd_gateway.error_log LPD port number 515 Service name: "printer" (in /etc/services) Manual test: telnet 515 telnet printer LPD protocol TCP LPD queue names in 2085/2105 Via printer web page: Network Settings: TCP/IP Printing Details: LPD Settings See: Queue names, in Infoprint 2085/2105 LPD separator page in 2085/2105 See: Separator page, Infoprint 2085/2105 LPD service In the Windows environment, Infoprint provides an LPD server which can replace the one in Windows (TCP/IP Print Services) so that Unix users can use LPR to submit print jobs. For full control of job specs, one can download the lprafp program from the IBM site. LPD settings in 2085/2105 Via printer web page: Network Settings: TCP/IP Printing Details /lpd/ In the Linux IPM, this is the directory which ipmlpd uses for receiving incoming LPD-submitted print jobs. This is the current working directory (cwd) for ipmlpd, which is to say that the ipmlpd process sits in this directory to do its work. If you repeatedly list the contents of this directory, you commonly see nothing, but occasionally may "catch" an incoming transmission, like: -rw-r--r-- 1 root root 188 cfA421CBA -rw-r--r-- 1 root root 720128 dfA421CBA Thus, the mtime timestamp on this directory always reflects when the latest job arrived. /lpd\cfA020JARVIS A file having a name like this is the result of the Linux ipmlpd process recording the LPD protocol control file here. Such a file should not be present for any length of time: existence indicates problems with the ipmlpd program. Such files can be deleted. /lpd\dfA020JARVIS A file having a name like this is the result of the Linux ipmlpd process staging the LPD protocol data file here. Such a file should not be present for any length of time: existence indicates problems with the ipmlpd program. Such files can be deleted. lpq AIX command to query a local print queue. lpq Status "unknown" When the lpq command is serviced and delves into IPM logical destinations, the State value reported will be "unknown" when the IPM Status is "ripping" or "printing" - due to a defect in the pdenq module which handles the report. lpr Name of usual Unix command for submitting print jobs. Conventionally submits within a system, not across systems. However, it may have a -s option to specify a remote server. But, be aware that the Linux command DOES NOT employ LPD, port 515, for the interaction: it attempts to contact the IPP server (CUPS) at port 631, using HTTP for the interaction. lpr -m This is the lpr command form for specifying that an email notification should be generated by the LPD server when the job completes, per RFC 1179 command code 'M'. IPM honors such an information request, by setting the job's notification-profile to: { event-identifiers = document-aborted-by-destination document-aborted-by-server document-cancelled-at-destination job-aborted-by-server job-cancelled-by-operator job-cancelled-by-user destination-needs-attention job-completed delivery-method = electronic-mail delivery-address = "Submitter@Addr" locale = en_US.ISO8859-1 } You notice that the notifications include far more than just job completion, allowing the submitter to receive info about other actions which may befall a job. Note that the mail attempts to go to the host from which the job was submitted: for that to work, either that host must be running a mail server or the mail environment must define a proxy host for that system. lpr -#N copies specification The number of copies specified via the lpr command (e.g., -#2) ends up in the third field of the results-profile attribute. The IPM GUI shows such a job as twice the size of a single-copy job, though in fact there is just the single-image file of the document in the server directory, half that size - which indicates that IPM is portraying the size by multiplying the basic file size by the number of copies. lpr -J '...' The lpr form for assigning an arbitrary jobname to the job, for the given string to be used for the jobname instead of the default of using the filename or URL. lpr -o The -o option is available in some versions of the lpr command, and with the rembak command. Standard lpr documentation doesn't say anything substantive about the -o option, but it appears to exist to provide a means of passing supplementary values ("additional options") to an amenable LPD daemon. The LPD Gateway description in the Procedures manual says that the AIX LPD supports passing advanced Infoprint print options, such as form definitions and page definitions. The Reference manual has an extensive description: "The -o flag for AIX print commands and the Infoprint Manager lprafp command". lpr across systems The usual Unix-included lpr command cannot submit across systems. The IPM-provided lprafp (q.v.) command can submit across systems. LPRng's lpr command can alco submit across systems. LPR sample client program IPM provides a sample LPR client, in C source form, in /usr/lpp/psf/utils/lpr/ It sends to the LPD on the AIX host where IPM is running. lprafp Compilable, IBM-provided command program to be compiled on a Unix system, allowing remote LPR-style job submission and specification of Infoprint options (via -oKeyword=Value specs). There should be an LPD daemon running on the destination system to receive the submission. Invoke as 'lprafp -\?' to see usage. lprafp can alternately be invoked as command name lprmon, to monitor a parallel printer port. Files in: /usr/lpp/psf/utils/lpr/ Ref: IPM Reference manual; its README LPS Xerox Laser Printer Systems. lsippgw IPP Gateway command to list the status of the gateway. Sadly, this command is poorly engineered, where it returns nothing, and a status of 0, if the gateway is not active, rather than returning a statement to that effect. When the gateway is active, all it returns is the port number in use (e.g., "631"). The command is just a ksh script which looks for the "ippgw.jar" process to grab its ipp-listen-port parameter. See also: IPP Gateway; startippgw; stopippgw LUM License Use Management system, new in IPM 4.2. See also: ECF m Units abbreviation for a millimeter. MA Maintenance Agreement, typically referring to the contract for software maintenance, to be able to call the vendor for resolution of problems. Mac OS X print jobs The name of the person who originated the job will be found inside the PostScript file in "%%For:". See also: document-file-name Macintosh client support Is much improved since the IBM days. There is now an InfoPrint Select client for Macintosh. Mac support generally requires: OS X 10.7.3 or later Mailbox The odd name for a printer output accessory which consists of a gang of plastic trays, each of which is to receive one copy of a multi-copy output. The Infoprint 1145 offers a Mailbox. MAIN The PostScript key name for the main, shifting output tray of an Infoprint 2085/2090/2105 printer. MAIN is the default (tray). Sample PostScript: << /OutputType (MAIN) >> setpagedevice The IBM Infoprint 2105 PS and IBM Infoprint 2105ES PS device drivers cause the generation of this spec into the PostScript job. See also: STD; UPPER Maintenance Kit See: Usage Kit Make Job First Causes the promotion-time attribute to be established for the job. Man pages /usr/share/man/en_US/cat7/ Managment Console Available only in the Windows version of IPM, this is a facility which provides administration capabilities beyond what is provided in the Admin GUI, as for example managing Access Control Lists. Absent this, the AIX IPM administrator uses SMIT to change ACLs. Margins In IPM configuration files, such as ps2afp, pdf2afp.cfg: ps_x_offset Left and right margins. -o: -x Default: zero (no margin). ps_y_offset Top and bottom margins. -o: -y Default: zero (no margin). PCL processing is slower when you use the -x flag, because the pcl2afpd daemon must stop and re-start the PCL interpreter. You may improve performance by changing the pcl_x_offset value in the pcl2afpd daemon configuration file rather than using -x on a regular basis. Note that the inner margin - the one where the job is bound/stapled - is called the "gutter" in typography terms. Ref: Procedures manual See also: Gutter MarkVision The free management tool provided by Lexmark for its printers. max-concurrent-jobs You mean: maximum-concurrent-jobs Maximum concurrent jobs GUI: AD properties, Tuning tab for attribute maximum-concurrent-jobs (q.v.). maximum-concurrent-jobs AD attribute: Defines an upper limit for the number of jobs that this actual destination can process at a time. There can be up to this many ainbe processes (managed by the IPM ProcessDirector), where each process is managed by a pdserver thread. GUI: AD properties, Tuning tab, Maximum concurrent jobs If the number is consumed by jobs in flight, no further job transforms will occur for that printer: incoming jobs will have a current-job-state = pending (even if job-rip-action = 'rip-and-hold'). The value affects early binding: that many jobs will tend to be bound to a given AD before the next AD gets jobs. Notes: For PSF TCP/IP printing, you want a value which is sufficient to keep the printer from being starved, with a normal job mix. (Yes, atrocious jobs will occasionally monopolize the transform and cause the printer to be starved for work, but this is abnormal, and should not figure into the computation.) A too-small number can be bad, because: - It can result in insufficient multiprocessing, where transformation does not always get far enough ahead of TCP conveyance to the printer so as to keep both transformation and conveyance busy to service all the incoming jobs. A large number can be bad, because: - It results in more processes for the server to juggle, resulting in server congestion. - It results in many jobs being committed to a given printer where, if that printer has a mechanical problem, the jobs will be stuck, committed there, rather than going to the next available printer. - Jobs which are active cannot have their attributes changed, making it a chore for the operator to manage the queue, as in changing job priorities. For PSF Command, though you may allow more than one job to be active, PSF Command will still work one at a time! If you watch /var/spool/qdaemon/ you will see it generating only one output job at a time. (Turning SNMP off for the AD does not improve things.) Cautions: There is a thread for each processing job. Increasing the maximum-concurrent-jobs value can greatly increase the number of threads to be managed by the server, meaning more overhead for it. maximum-copies-supported AD attribute: Limits the number of copies which a job may print, per external manifestation of the number of copies, as in job results-profile. Value can be 1 - 2147483647. The copy-count job attribute is compared against this maximum: the job fails with Resources Not Supported if exceeds. Default: 2147483647. GUI: Actual destination, Properties, Document tab, Maximum copies allowed Note: May be of no value in your environment if the number of copies is not specified by the submitter as an external attribute. For example, in PostScript printing, the NumCopies definition will specify the number of copies, internal to the job, where Infoprint Manager queue management cannot see that spec. Thus, though you specify a maximum value of 2, a job can still proceed to produce 50 copies. Media See: default-medium Media and 8.5x11" Media has no 8.5x11" selection. Instead, use "letter". Media and 8.5x14" Media has no 8.5x14" selection. Instead, use "legal". Media ready GUI label for the paper trays on a printer. Note that IPM displays only the "real" trays on the printer. For example, the HP 4200 or 9000n has three trays: 1 Flip-down, manual tray. 2 Real paper bin 3 Real paper bin IPM will show only the real paper bins, where the HP's Tray #2 is IPM's Tray 1, and the HP's Tray #3 is IPM's Tray 2. See: psf-tray-characteristics Media support in IPM IPM's support of media (paper) is thorough. A basic set of media definitions is created when you first start IPM (or, by running the pdcrdflt command). Each medium definition has a name (e.g., "letter") which has a set of qualifying attributes. The current set of media definitions can be seen via: pdls -c medium -r all : For example, "letter" has attributes: descriptor = "North American letter white medium with size 8.5in by 11in" medium-type = plain medium-size = na-letter medium-dimensions = 215.9:279.4 medium-color = white medium-sides = 2 (Dimensions are in millimeters.) Create new definitions via command pdcreate -c medium ... One may want to add a definition for the medium "letterhead". media-ready AD attribute identifying the media (paper) currently loaded in the output device. This is a derivative, rather than settable, attribute which is supposed to collectively reflect all the paper sizes in the printer... The media-loaded sub-attribute values of the psf-tray-characteristics attribute are supposed to automatically augment the list of media in this media-ready attribute. (But beware the psf-tray-characteristics not picking up the paper type loaded into a tray (via SNMP), such that media-ready may not reflect all the paper types actually present in a printer, which can cause submitted jobs seeking that paper type to be red-ikoned. Note that while this attribute name looks like it should correspond to the "Media ready" GUI attribute, it does not: media-ready is not reported by the GUI. See also: psf-tray-characteristics media-supported AD attribute identifying the types of media that the AD supports. IPM will attempt to use SNMP to get a list of what the device supports. GUI label: Media allowed Medium identifiers of medium objects are created by the pdcrmed utility. Medium Map AFP: Another name for a Formdef Copy Group. As in an AFP file Invoke Medium Map (IMM) command. See also: Copy Group; IMM Medium speed printer Printer type classified as printing in the range of 92 - 116 ppm. Previous: Low speed printer Next: High speed printer Medium Speed Printer Feature Optional cost license feature for driving Infoprint 2085/2105 printers and the like. It is known that installing this feature updates the /usr/lpp/Infoprint/install/ipm.ini file (Installation Features Log(?)), but beyond that, unknown. See also: Workgroup Printer Feature Memory See: Memory Usage; printer-memory "Memory (KBytes)" See: printer-memory Memory Usage Tab on Server Properties (show more) where you can define lower and upper memory usage actions, and queries to prevent at such times. message A notifications delivery-method, to send a job event message to the Infoprint Notifications client at the address specified via delivery-address = "_________" form. Contrast with: electronic-mail Message descriptions Use the 'pdmsg' command (q.v.). Message from administrator See: job-message-from-administrator Message numbering 5010 Server messages 0420-0424 PSF messages 0425 ACIF messages Messages, from commands In Unix, IPM sends messages resulting from the execution of commands (e.g., ps2afp) to Stderr. Some messages (e.g., 0424-092) may consist of more than one line, with only the first line prefixed with a message number. Messages manual Oddly enough, there is no IPM messages manual - just the 'pdmsg' command. Messages repository Is housed in the appropriate national language operating system directory, such as: /usr/lib/nls/msg/en_US/ where the filenames are: ipr.cat The error messages. iprhelp.cat The message explanations. Accessed by the pdmsg command. MFP Multi-function printer, as in one which prints, copies, finishes. MIB Management Information Base, part of the SNMP architecture, being a catalog of variables (objects) which are addressed by dotted numbers (OIDs). IPM internally uses the MIB arrangement to catalog all of its devices, definitions, settings, and sofware componentes: it MIBifies everything. You can see this in the subdirectories of /var/pd//pdb/ . See also: OID; SNMP; MIBs table near the bottom of this document. MICR Magnetic Ink Character Recognition. Used in the banking industry for automated check processing. Along the bottom of checks you will see blocky characters created using this special ink, in a font known as MICR E13B, readable by humans and machines. MICR E13B Font For printing checks with a laser printer and magnetic ink. Font size must be exactly 14 for scanning to work. Microsoft Word document identification You may be required to inspect mystery jobs which won't print, to ascertain their actual format. Sometimes, users dumbly send binary MSWord files directly to the printer. Such files typically have a ".doc" extension. The "signature" of an MSWord file is its leading bytes: d0 cf 11 e0 a1 b1 1a e1 followed by binary zeroes. Mirrored Output PostScript printing option as seen in Windows printing dialog boxes (under Advanced Options): print mirror image by reversing the horizontal coordinates. MIT connection, the IBM Infoprint Manager for AIX is based on Palladium technology developed at MIT/Project Athena. See also: Palladium mk_ip_remote Installation CD/DVD command to prepare a disk image of the software for NFS mounting by (remote) systems where the software is to be installed. The command needs to be copied to some hard drive location before being invoked. Particularly useful where the target system lacks a suitable removable media. The procedure will create a file system unless directed to use a directory under an existing file system. (In Linux, the file system type will be ext4, LV name "ip_remote", size 2 GB.) At conclusion, the input installation medium is unmounted. Invoke with -h to see usage info. That will show how much space is required (expect at least 1 GB). If installing the IPM server software on a local system, you don't have to go through this: just use the installation media received. Command syntax: mk_ip_remote [-h] | [-g vg_name] [-n fs_name] [-s disk_mount_pt] | [-s disk_mount_pt] [-F dir_name]" where: -h Shows usage. -g vg_name Specifies the volume group that will hold the Software Server file system. -n fs_name Specifies the name you wish to assign to the Software Server file system. -s disk_mount_pt Specifies where the InfoPrint Manager disks are to be mounted. -F dir_name Specifies the directory to hold the InfoPrint Manager software. No file system will be allocated if this flag is used. The directory will be exported for mounting as an NFS file system by your remote systems. There is no -a option for this command, to provide responses to its prompts... Do you have an InfoPrint Service disk? [Yes/No] Enter the volume group for /ip_remote: Where you can run it: You can run it on any compatible OS system: it doesn't have to be run on the system where the software will be installed. And for the Linux product, it can be run on a CentOS system. What it produces: The contents are: auto/ baklist linux.id mk_ip_remote Packages/ remote-install setup templates/ which are the same as on the install DVD. The following install DVD files and directories are excluded: allocatefs.sh autorun.sh getfingerprint html/ pubs/ setup.html (It seems, then, like the installation ISO could be used for an unattended install; but the remote_install script says "All unattended installations must be performed using an InfoPrint Manager Software Server, not the InfoPrint Manager for Linux DVD-ROMs." going through this.) See also: /ip_remote; remote_install MMC Medium Modification Control in an AFP file. Appears within a Medium Map. Uses include specifying different input source values along with either tumble or normal duplex, as in printing the front and back sides of a sheet from different input bins. MO:DCA (MODCA) Mixed Object Document Content Architecture. An element of the AFP architecture for having multiple object types in a file or stream: text, images, vector graphics, and even objects marked as 'barcodes'. A key aspect of this is that object placment on the page is by All Points Addressable means, where locatability is to any spot point on the page (more exacting than character position). A MO:DCA file consists of a sequential, ordered hierarchy of independent objects - documents, pages, data objects, and resource objects such as fonts and ICC profiles. Each object is delimited by begin/end structures, and objects to be rendered specify presentation parameters and resource requirements in structures called "environment groups". The pages in MO:DCA documents appear in sequential order, supporting stream processing and allowing presentation to start as soon as the first page is received. See also: AFP MO:DCA-P (MODCA-P) Mixed Object Document Content Architecture - Presentation. An architected, device-independent data stream for interchanging documents between different platforms. That is, MO:DCA-P is the specific interchange architecture. This is the type of output produced by AFP transforms. MO:DCA-R (MODCA-R) Mixed Object Document Content Architecture - Revisable. Mentioned in circa 1990 documentation, but not recently. Model Actual Destination GUI field corresponding to the destination-model attribute. Model identification of PSF printers All product-known PSF printer models are defined in /usr/lpp/pd/attr/ files, in the destination-model attribute in those files. For example: file psf_1823 in that directory has destination-model = InfoPrint1823 When you go through the IPM admin GUI to define a PSF TCP/IP printer and pull down the Model, you get a list reflecting the contents of that directory. Model IDs are also found in file /usr/lpp/psf/config/transform.cfg modification-time Job attribute: Identifies the time when the last modification to this job occurred, as for example when the job retention period was changed, or the job was resubmitted. GUI label: Last modified OID: 1.0.10175.1.3.1.205 Move image right (inches) Specifies the X offset of the logical page origin to the right of the physical page origin. Specify a positive or negative shift. Attr: x-image-shift Move image down (inches) Specifies the Y offset of the logical page origin below the physical page origin. Specify a positive or negative shift. Attr: y-image-shift Move image right on back side (inches) Specifies the X offset, in millimeters, of the logical page origin to the right of the physical page origin on the back side of a double-sided sheet. Specify a positive or negative shift. Attr: x-image-shift-back Move image down on back side (inches) Specifies the Y offset of the logical page origin below the physical page origin on the back side of a double-sided sheet. Specify a positive or negative shift. Attr: y-image-shift-back Move job GUI icon operation to move a job from one Logical Destination to another, or the Retained Jobs area. The pop-up Move Jobs windowette allows you to select a new LD. (You cannot type into the box, as you can with Change Requested Destination.) Note that the Move Job does *not* cause the job to have new Job and Document Defaults assigned per the new LD: the old values prevail. In particular, the Formdef will not change. However, the Requested Destinations will change. Moving a job is accomplished via the pdresubmit command. MPF Multi Purpose Feeder, as may be found on some vendor printers. Multi-copy printing through lpr/lpd Here's what happens when a user prints a multi-copy job through lpr/lpd (as illuminated by exposure of attributes in a Transform Sequence): - The user does like: 'lpr -#5 myfile' to print 5 copies. - The lpd on the originating system sends the job to the AIX system which houses IPM as one copy of the data and a control file noting the number of copies. - The AIX lpd receives the job, handing it to IPM, which translates the request into one job containing as many "documents" as the number of copies, with attribute number-of-documents set to the number of copies. Each "document" is stored as a separate file in /var/pd// and has attributes including: copy-count = 1 document-sequence-number = (1 thru N) The job attributes set contains all of the documents identified by "GlobalID:N" numbering, like: acsn07:5659103780.1 acsn07:5659103780.2 - IPM prints the job by iterating through the "documents". A Transform Sequence invocation occurs for each "document". Unfortunately, the Transform Sequence is given no indication of the sequence number of the document it is currently given to process. Multi-document jobs present? Jobs can consist of multiple documents, most commonly resulting from a Unix user performing 'lpr file1.ps file2.ps'. You can quickly test for there being any multi-document jobs by perfoming an 'ls' on directory /var/pd//pdb/document/ and looking for any filenames having a suffix of .2 or above. Multiple copies, AIX Via one of the following AIX commands, where $$ is the number of copies: 'lpr -# $$ ...' 'qprt -N $$ ...' 'enq -N $$ ...' 'pdpr -n $$ ...' 'pdpr -x "copy-count=$$" Multiple servers See: Servers, multiple Multiple-up printing Placing multiple (logical) page images onto a single physical page, as in saving paper or storage space. See also: Form; Page Multipurpose feeder A supplementary means of feeding paper into a printer, being an externalized "mouth" to take special stock for the next sheet to print on, rather than from the main paper trays. Found on printers such as the Infoprint 1145. MVS client Via DFSMSdss and DFSMShsm in MVS; or see opportunities in the Unix Client manual. MVS printing and separator page Printing in MVS's lpr involves the creation of a separator page by MVS itself. na-letter As employed in medium-size, refers to "letter" size paper as used in North America (United States of America, and Canada). Those two countries stick with letter size being 8.5 x 11", while all the rest of the world has adopted the ISO standard, where "letter" size is 8.3 11.7". Name Job property: the job name. Attribute: job-name name-of-last-accessor The identity of the last person to "handle" the job... Initially is the submittor. Otherwise is an operator or administrator. If that person does a Make Job First in the queue, then the attribute is filled in with the identity of the person who performed that action on the job. Namespace A global name repository available to all utilities and API procedures. The namespace contains mappings of object names (Actual Destinations, Logical Destinations, etc.) to other related objects. For example, the namespace provides the mapping of a logical destination to the server in which it exists. When you install an Infoprint Manager server on a system, the install process creates a namespace for that server. Physically, the namespace is a directory structure where IPM stores the location information of all of your IPM objects, including the server itself, queues and destinations, and the Access Control Lists (ACLs). Two or more Infoprint Manager servers may share the same namespace: this is called an interoperating environment. In this case, the namespace must be located on an AIX system. (It cannot reside on a Windows Infoprint Manager system.) Information sharing among the servers then occurs via NFS - which is to say a physical, outboard method rather than by any IPM server-to-server communication: thus, this is not as inate or sophisticated as it might be. See also: /etc/pdserver.conf; Servers, multiple National language environment variable PD_LANG For the US: en_US ncsd Network Control Service daemon, as found in the Infoprint 2210, etc. needs attention (needs-attention) GUI: AD Status value. The AD has a non-serious issue, such as paper supply empty or a paper jam. IPM does not disable the AD in this case, but rather leaves the AD icon red. Jobs committed to the AD via early binding remain waiting for it. (You can force them to go elsewhere by first disabling those jobs.) If an AD is in needs attention mode and had no files processing on it, new jobs will not go to it. The GUI Status tab "Attention needed" field will show how long the device has needed attention (attr destination-needs-attention-time). Also seen with: 5010-849 The SNMP connection to printer ____ has been lost. Generous values for job-retry-interval and job-retry-count-limit will allow printing to resume when the printer problem is remedied by the printer operator. Msg: 5010-371 needs key operator GUI: AD Status value. See: Key operator; needs-key-operator needs-key-operator AD destination-state attribute value: This state occurs when there is a serious problem with the output device. Either the actual destination cannot connect to the output device or there is some other problem. For example, a printer device may be out of toner, or one of its doors is open. With HP printers, this is often caused by someone causing a print job to specify use of Tray 1, which on an HP is the special flip-down manual paper feed, which is usually not in play. Also seen with: 5010-841 Printer ____ is out of paper. 5010-837 Printer ____ is offline. 5010-829 Printer ____ is running, but is low on paper. The initiation of this state is influenced by the job-retry-count-limit attribute. IPM automatically disables the AD when the AD enters this state, and no further jobs will be processed for that AD. If the AD uses SNMP, IPM automatically re-enables it when the problem is corrected. To prevent automatic re-enabling, manually disable the AD. The GUI Status tab "Operator needed" field will show how long the device has needed the attention of its operator (attr destination-needs-key-operator- attention-time). Error log msg: 5010-850 Negative Output PostScript printing option as seen in Windows printing dialog boxes (under Advanced Options): print negative image by reversing the values for black and white (not suitable for color printers). NFS job submission See: Hot Folder Non-process runout timer (sec) Element of Printer Properties, Tuning tab: Designates the amount of time, in seconds, that a continuous-forms printer device waits for the next job before it runs the forms from the print transfer station to the stacker after the last page of a job prints. (So does not pertain to cut-sheet printers.) Attr: non-process-runout-timer Possible values: 0 - 9999 (seconds) Default: 60 If you enter a value of 0, IPM does not allow the timer to expire. The value should be less than the destination-release-timer attribute. notdmon The undocumented notifyd monitor, which is started if the notifyd daemon itself claims that it started. /usr/lpp/pd/bin/notdmon, a Ksh script. Stops running when notifyd is shut down via command 'stopnotd'. PROBLEM: The notdmon script directly invokes 'notifyd' to start it, if necessary. This is problematic in that notdmon may thus attempt to start notifyd without all the environmentals which may be defined in the startnotd script! This can cause notdmon to be worse than useless, where it endlessly thrashes in a futile attempt to start notifyd for lack of proper environmentals - and bloats /var/psm/.notifyd/ as a result. (This is why overall environmentals in the AIX /etc/environment file are so important, where the IPM install has modified that file to have things in the order needed for correct operations.) See also: notifyd Notification A message of some kind sent back to the job submitter, advising of a change of state in the submitted job, to keep the user apprised of job progress, usually according to notification attributes attached to the submitted job. In constructing the reply, the IPM server may utilize work file /tmp/,_notif.msg (q.v.). Notification attributes delivery-method "none" No notification to be made. "file" Open the file for write-over. write, close. "file-add-to" Open the file for appending, write, close. end-message-supported notification-profile notify-operator start-message-supported Notification Server See: InfoPrint Manager Notification Server; notifyd Notification profile Managed via admin GUI, Server -> Properties, Other Attr: notification-profile notification-profile AD attribute: Designates which users Infoprint notifies of specified events related to this AD, and how Infoprint notifies them. This definition is populated by various sub-attributes (components): event-identifiers: Specifies the events for which the user receives messages. GUI label: Events Type: Multi-valued Allowed values: You can enter any of the values listed for the server attribute events-supported. Default values: object-deleted, object-cleaned, printer-needs-administrator, printer-needs-attention, printer-needs-operator, printer-timed-out delivery-method: Specifies how the user or file receives event messages. GUI label: Method Type: Single-valued Allowed values: You can enter one of these fixed values: Fixed Value Input Synonym electronic-mail e-mail, email file file-add-to message exit none wireless delivery-address: Where the message is to go. Must obviously be in concert with the deliver-method, as in an email address when the method is email, the full path of a file system filename when the method is file or file-add-to, etc. GUI label: Address Type: Single-valued Allowed values: You can enter a text string up to 255 characters long that contains the user name and node or the directory and file name. Default value: The login ID of the user who created this actual destination. Usage guidelines: You must specify a value for delivery-address if you specify a value of file, file-add-to, exit, or wireless for the delivery-method component. Special note: Where the delivery-method is file or file-add-to, the file can be a Unix FIFO, which you can read with a waiting program. This can be of particular value when used with a queue, where the job-assigned-to-queue notification can be used to create a job pre-processor to examine incoming jobs, in that IPM provides no user exit for looking at jobs as they arrive. With file-add-to in effect, IPM's programming seems to be sophisticated in detecting if nothing is currently reading the FIFO, so as not to write to it and be blocked: in that case, an 'ls -l' on the FIFO file will show a size of 0, meaning that IPM has held off writing data to it until something is reading it - at which time it writes all its pending data. This is good, keeping the server from being blocked. But it can get congested with pent-up messages. GUI label: Notification profile See: InfoPrint Manager Notifications notification-profile Job/Default Job attribute: Designates the people that Infoprint notifies when specified events relating to this job occur and how Infoprint notifies the people. See the AD notification-profile for basic specs. The JD attribute adds: event-comment: Provides information that IPM appends to the event msg. GUI label: Comment Type: Single-valued Allowed values: A text string of up to 4095 chars that supplies additional info. Default value: None locale: You can enter the name of any locale for which the IPM msgs in the corresponding language are installed. Type: Single-valued Default value: - For default jobs, none. - For jobs, is the locale of the user who submitted the job. Note that Infoprint Select Notifications sets its own notification profile values. Adding an event identifier elements proceeds like in the following: pdset -c initial-value-job -x 'notification-profile+= {event-identifiers= job-assigned-to-queue}' ${HOST}:LogicalDest1-dj which adds an appendage rather than changing the innards of the existing definition. notifyd daemon (notify daemon) The notifyd daemon receives and stores notification messages for all users requesting notification through the notification-profile associated with many IPM resource, via deliver-method messaging. TCP/IP port on which the notifyd process listens: 8200 (TCP; not defined in /etc/services.) Binary: /usr/lpp/pd/bin/notifyd Started via: startnotd which the IPM install added to /etc/inittab. Thus, be aware that notifyd is *not* started with the IPM server - and should not be killed off with other IPM processes when the pdserver is to be restarted. Verify: lsof -i :8200 Stopped via: stopnotd, which sends a SIGTERM (15) to the daemon, which should then shut down with message 5010-338 in its log. Note that the shutdown may not occur immediately, if the daemon is busy with accumulated work. Log: /var/pd/notifyd/error.log Contains only info about the daemon starting and stopping: there is no logging of each notification serviced. Upon restart, the daemon will cycle the current error.log to error.log.BAK.YYYYMMDDhhmmss Monitor: There is an undocumented monitor which silently starts, if notifyd itself claims that it started. The monitor's purpose is to restart notifyd if it fails. This is the cause of the error.log mysteriously being updated when notifyd is not running, due to start problems. See: notdmon Debugging: The structured thing to to is to copy notifyd_trace.cfg from /usr/lpp/pd/bin/ to /var/pd/. This will cause creation of /var/pd/notifyd/trace.log, containing some useful info, particularly when startnotd is executed. To go further, you can make a copy of startnotd and modify that script to remove the redirection around the invocation of notifyd, to reveal additional issues. Environment variables: If CLASSPATH is defined, notifyd will prepend that path to its normal one, for the Java Virtual Machine to look there for user-defined classes and packages in Java programs. It should not need to be employed, but if it is, it needs to go at Java stuff which is compatible with what is in effect for the LIBPATH, where the lib path is either that built into the notifyd binary or specified via the environment variable LIBPATH. Inconsistencies will result in notifyd failing to start, and Javacore files in /var/pd/notifyd/. LIBPATH can be used to override the level of Java to be used. Only one notification daemon needs to be running for each Infoprint Manager cell or domain; one notification daemon receives notifications from and services all Infoprint Manager servers sharing the same name space. With Infoprint Manager for AIX, you can specify that the notifyd daemon starts whenever the system starts or is rebooted by using the Infoprint Manager SMIT panels on AIX. The notifyd daemon has a monitor that will restart it if it ever stops running. (The install adds it to root's crontab, to run /usr/lpp/Infoprint/ install/bin/spacewatch.ksh .) If you want to stop it, to move it to another machine for example, use 'stopnotd'. Note that if notifyd is not running when a notification needs to be sent, the pdserver attempts to run it, as for example during IPM server shutdown. In IPM 4.2, doing lsof on the notifyd process shows it with quite a few file descriptors open in /usr/, ostensibly relating to JVM execution. See also: InfoPrint Manager; startnotd Notifications; startnotd; /var/psf/.notifyd notifyd_error.cfg Source in: /usr/lpp/pd/bin/ Live in: /var/pd/ Ref: Procedures manual, "Customizing a Notification daemon error log" NPF Network Print Facility See also: pioibmnpf NPM Network Printer Manager. MVS program number 5655-HAL. A feature of IBM TCP/IP, allows you to print MVS JES spool files and VTAM application data through PSF/6000. For more information about how NPF works, see manual "IBM TCP/IP for MVS: Network Print Facility" (SC31-8074). Reflected in driver names (pioibmnpm). Log: /var/pd/npmserv.log NPM server port 6795 Managed via admin GUI, Server -> Properties, SNMP See also: pioibmnpm npm-server-ip-address Server attribute identifying the IP address of the system where the Network Print Manager (NPM) server is running. GUI label: NPM server IP address The operator GUI Check Status function depends upon this NPM spec in order to operate. npm-server-port-number Server attribute identifying the Port Number parameter on the system where the NPM server is running. GUI label: NPM server port Default: 6795 In the IPM process family, the process named "java server" is the one which listens on this port number. The operator GUI Check Status function depends upon this NPM spec in order to operate. npmtrc.log In /usr/lpp/pd/bin/. NPRO Non-process runout. A printer function that moves the last printed sheet to the output stacker. number-of-documents Job attribute: Identifies the number of documents in the job, including resource documents such as fonts. In LPD printing, this number will be the number of copies. For example, if the user did 'lpr -#3 myfile', it will result in a job containing 3 documents. See also: document-sequence-number number-up Document attribute: Specifies the number of pages to print on a single side of the paper when the value of the output-format attribute is side-by-side-copies or simple-n-up. Possible-values: 1up 2up 3up 4up Advice: Set this for PostScript type printing, because the printer may have wacky default values. O1 Overlay name prefix. The system name identifies an overlay in the library. It has two forms: the user-access name (M1001 in the sample set of commands) and the library-resource name. Of these, you use only the user-access name. PPFA automatically adds the O1 overlay prefix to the user-access name, which identifies the resource in the library. An overlay referenced through a form definition built with PPFA, therefore, must begin with the O1 prefix. An example of the result is O1M1001, the library-resource name. See also: user-access name Offset stacking Can be effected only in IPDS printing. Allow offset stacking Offset stacking, allow (2085/2105) Printer Settings, Paper Configuration. Sets the default job offset stacking behavior. Stapling overrides offsetting (as stated in printer User Guide, User Tools (Printer Features), Settings Menu). Offset stacking, allow (IPM) GUI: Actual destination, Customize, Allow offset stacking Note that IPDS controls offset via the formdef; but whether the offset request can be passed to a printer via the PCL transform is uncertain. Offset stacking allowed? For PSF Command and PSF Other printers only. GUI: Printer Properties, "Customize" tab, Allow offset stacking See also: Jog OGL Overlay Generation Language, an IBM software product for designing forms. OID Object IDentifier, part of the SNMP architecture. These are dotted number sequences which serve to address Management Information Base variables (objects), defining a hierarchical, pyramidal arrangement of dotted addressing and objects. The hierarchy is defined in a central, world-wide registry, with number series assigned to different organizations, conceptually like IP subnet addresses. Classically, SNMP utilizes OIDs to uniquely identify network objects like routers and printers. IPM uses SNMP, MIBs, and OIDs to not only communicate with the network devices to which it sends data, but also to catalog *all* the things that it uses: AD and LD definitions, attributes, and settings (even transforms programs). These are all in the Print DataBase directory: /var/pd//pdb/ . (Today, this would more appropriately be called the Parts DataBase.) Sample OID: 1.3.18.0.44.2.3.2.13 1.3.18 is the IBM Objects tree. Print job attributes often have the OID number 1.0.10175.1.3.1.__, which seems to be defined in the purchasable ISO 10175-3 "Information Technology - Text and Office Systems - Document Printing Application (DPA)" standard. That standard is also called called the Palladium Print System (which was developed at MIT). It specifies a client-server model of printing in accordance with the Distributed-office-applications Model (ISO/IEC 10031-1). Together, the capabilities provided can enable users to create and produce high-quality office documents in a consistent and unambiguous manner within a distributed open system environment. The Document Printing Application Standard (ISO/IEC 10175) consists of three parts: Part 1: Abstract service definitions and procedures Part 2: Protocol specification Part 3: Management abstract service definition and procedures Related: RFC 2708 Web OID info: http://asn-1.com/oids.htm http://www.alvestrand.no/objectid/ (outdated - unmaintained since 1995?) See also: MIB; SNMP; /var/pd//pdb/ OIDs /usr/lpp/pd/oids/ /usr/lib/nls/msg/En_US/Pd/ibmoid.cat AIX fileset: ipr.base.oids .oly Filename extension for an Overlay. OPC Obtain Printer Characteristics, IPDS command. Allows PSF to query the printer about the additional features and functions which it supports. For example, a printer may pass info back to PSF stating that it supports a specific level of GOCA, certain device controls, can print color, has a specific resolution, or other info. Presumably, the /var/psf//opc file reflects this. Operations GUI True GUIs commands: ipguibasic Basic GUI: Printers, Retained jobs ipguibasics Basic GUI, special ipguiadv Advanced GUI ipguiadvs Advanced GUI, special (See respective command descriptions) SMIT GUI: This, naturally, is rather clunky, compared to what a real GUI should be. Started via: 'startppo' command. Ref: Getting Started, Appendix Operator GUI See: Operations GUI Optimize for copies Element of printer properties Tuning tab. Attribute: optimize-for-multiple-copies Used with the optimize-for-multiple-copies job attribute to indicate whether the printer device should save pages in order to print multiple copies of the job faster. Effects: Saving copies in the printer may tax the printer's memory and storage. Option, install Via the 'setup' script on the CD-ROM provided. See: setup Optional Component See: Feature Options installed What options do you have installed? How do you verify what you have installed? There seems to be no IPM command to allow customers to check on this; so customers have to resort to physical means... You can review what product options have been installed by inspecting the /usr/lpp/Infoprint/install/ipm.ini file, which may look something like this: Infoprint Manager Options Installed [Base] Base=Yes . [Printer] High=0 Medium=30 Low=0 Work=50 Fax=0 . [Features] Email=Yes PPFA=No SAP=No Security=No JPSF=No POD=No In the [Printer] section, the numbers refer to the number of physical printers allowed. (You may have any number of IPM definitions which make use of these printers.) Note that this is what is displayed when you have run a feature-provided 'setup' script and do View Installation Features Log. Thus, we should expect that the ipm.ini file is the Installation Features Log. See also: License ORIGIN PPFA: The top left corner of the page, as defined in the FORMDEF OFFSET command. See also: Page origin other-transform-options Transforms attribute describing the command line which executes when the transform is run. A string up to 255 chars. %i (i=%i) The name of the input-file to transform. %o (o=%o) The name of the file in which to store the output transform. %e (e=%e) The name of the file in which to store any transform info or error messages. If anything is written to this file, it is logged in the IPM server log. %j (j=%j) The original print file name, minus the path (from document-file-name attribute). %n (n=%n) The original print file name, minus the path and minus the extension (from document-file-name attribute). %d (d=%d) A string representing the document-format of the input file: ascii May actuall be one of: ASCII data, PDF data, GIF data, TIFF data. afpds AFPDS pcl PCL postscript PS %p (p=%p) The value of the destination-pass-through attribute. The value can be used as AD specific or job specific information that can be passed to the transform. %q (q=%q) The name of the AD which is doing this transform (the printer name). %# (I=%#) The 10-digit job-identifier of the job. Outline font A font-shape technology in which the graphic character shapes are represented in digital form by a series of mathematical expressions that define the outer edges of the strokes. The resulting graphic character shapes can be either solid or hollow. Outline fonts can be scaled (sized) to any size. The name of an IBM outline font character set has the prefix CZ. Output bin requested GUI: Job and Document Defaults, Document Processing tab Value is often left at "Use default", which employs the AD setting. Note that this attribute is incompatible with AIX destinations, which do not offer an output bin choice, such that "Use default" must be in effect in the job so as to prevent a red icon job failure: "resources not supported: Actual Destinations Requested". output-bin AD attribute defining the output bin to be used. GUI label: Default output bin Note that the bin specification is a text string, though it may look like a number. Can be set to one of the values shown in output-bin-numbers (GUI "Map output bin to number). In a smaller printer such as a basic Infoprint 1585, there will be a single output bin, e.g., "1", typically being the molded bin atop the printer. output-bin LD attribute defining the output bin to be used. GUI label: Output bin requested This is somewhat confusing, because the GUI presents the choices: Use default bookletmaker stacker stapler top whereas in the AD the bins are usually numbered 1, 2, 3, ... But it is the case that you can type the name of the bin into the field (e.g., "2"). In any case, if you specify an output bin here it must match one that is defined in the AD's list of bins. Overlay Generation Language Application for the creation of electronic overlays, as used with the IBM 3800 Model 3 printer (in place of physical overlays in its forms-flash unit). Overlays Overlays are stored constructs (text, graphics, images, lines, shading, and bar codes), often in complex configurations, with all the instructions needed to print. They are usually merged with variable data at print time. Overlays can be specified in a Formdef. Historically, overlays have been used for pre-designed forms, rather than page elements, which are more appropriately handled as page segments. An overlay always prints in the type style used when it was stored and can be positioned anywhere on the page (though is usually thought of as a fixed-location complementary image). Contrast with: Page Segment Can be created using the Elixir's DesignPro Tools package. www.elixir.com "Override RIP at destination" GUI field for Job and Document Defaults. Attr: job-ripped-by-server (q.v.) p Units abbreviation for a point. P1* Filename prefix for Pagedefs. See also: Definition resources; P1* P1A08682 Supplied pagedef for letter-sized paper. Page orientation: Portrait Print direction: Across Print lines per page: 86, at 8.2 lpi Recommended font: GT12 Page One side of a sheet of paper. See also: Form; Multiple-up printing Page count IPM 4.2 PTF U811589 (December 2007) added a job page count function. It is enabled by specifying a value of rip-and-hold on a new server attribute, count-job-pages. IPM updates the page-count document attribute and the job-page-count job attribute after it rips (transforms) the documents in a job that is being ripped and held. This updated page count information is displayed in the GUI. This job page count value is thus the result of the transform, not necessarily the job file as it arrived: the transform may well add a header sheet, where its presence will increase the page count. Note on job-page-count: That job attribute *may* be filled in when the job arrives in the queue, if it is of a type (PostScript) which IPM can "sniff" to quickly get a page count by virtue of information which some job formats carry. PostScript jobs may have a Document Structuring Convention comment near the bottom of the file, specifying like "%%Pages: 5", which IPM will adopt. However, many jobs may not carry such information, in which case the job-page-count attribute will be null after job arrival in the queue. See: Page count on just-arrived jobs Page count, job, determine crudely A crude but effective way to determine the job page count is to RIP the job at low res (minimal overhead) and use the afpdmp command to glean the last PAG000nn page value (e.g., PAG00008). (AFP generates physical pages for all document logical pages X copies.) Page count on just-arrived jobs With PostScript jobs, depending upon the PS driver which created them, you may see IPM display a pages count even before RIPping the PostScript job. How does it do that? IPM examines the bottom of the the file as part of "sniffing" it and, if there is a "%%Pages: 5" Document Structuring Convention comment value there, it will set the GUI "Page count" to 5. Many PostScript jobs may contain DSC comments but fail to set a final %%Pages value, in which case the GUI "Page count" will be empty. Note that while the job may contain DSC page section delimiter comments like "%%Page: 12 12", IPM will not scan the whole file to compile the number of pages. Not further that this page count is a *document* page count, not necessarily a job page count...which is a multiple of the document page count and the number of externally and/or internally specified copies. See: job-page-count; pages-completed See also: octets-completed; Pages Page printer All-points-addressable, page-oriented devices that process print data a page at a time. Page definition A page definition specifies how you want data positioned on the logical page (where the logical page's external handling is defined in the Form Definition). A page definition can control the following functions: - Dimensions of the logical page - Print direction of the logical page - Print direction of text lines and fields relative to the logical page - Conditional processing (different formats on different pages, based on content of data) - Text line spacing (number of lines per inch) - Location of individual text lines and fields - Number of text lines per page - Page segments for inclusion in printed output - Overlays for inclusion in printed output (positioned anywhere on the page) - Page-ejection points - Fonts and font rotation used on a page - Multiple-up printing (placing more than one subpage on one side of a single sheet) - Colors to be used (on printers that support this function) All page definitions require a PRINTLINE command (Traditional printing) or a LAYOUT command (Formatted printing). Comment: Pagedef coding is clunky, a lot like trying to program using JCL. Too often it is utterly unobvious and resistant to logic: code something which looks like it should certainly work, and it doesn't, leaving you bewildered. See also: Form definition Page definition naming Name length is up to 8 characters (deriving from MVS Partitioned Data Set member naming limitations). Positions: 1,2 Always "P1". Page definition used In submitting a job, you can specify the command option -opagedef=PagedefName to specify the name of the page definition Infoprint uses for the job. If you do not specify the pagedef via job submission specification, IPM looks in the input file for an inline page definition. If the input file doesn't contain a page definition, IPM uses the default page definition for that Infoprint actual destination. An input file can contain multiple page definitions, but only one page definition can be used for printing. By convention, the first pagedef is used. See also: Inline resources Page Format A subdivision of the Pagedef, akin to the ways a Formdef may have Copy Group subdivisions. Another name for Page Format is Data Map as used in PSF publications and PSF terminology. AKA: Data Map See also: Invoke Data Map Page origin The top left corner of the page, as used with the PPFA ORIGIN command. (The position derives from line printer output, where fan-fold paper fed upward and then out of the printer.) For a physical sheet of paper, the Media Origin is the top left hand corner of the sheet. For the logical page boundaries, defined by the Formdef, the top left corner can be some distance down and inward from the top left corner of the sheet, as defined by the PPFA OFFSET command. Page Segment PPFA: A resource object, like an overlay, which can be included in printing. Page segments contain text and images that you can include at any addressable point on a page or an electronic overlay. Page segments are similar to overlays, except that the construct is stored without specific instructions for type styles and position on the page. Page segments are printed in the type style in use at print time. A page segment may be included on a page via: - an IPS structured field, within the user data; or - the PRINTLINE Command (Traditional) Name length: 8 chars See also: SEGMENT Page Segment, create The various IPM transforms provide options allowing the output to be a page segment. The type name begins "pseg". The IBM AFP Driver is another approach, wherein you create the Pseg using some PC application, such as a page layour program, then specify that the output be saved to disk as a page segment (Properties -> Output Type). Page Segment, create from PostScript 'ps2afp -a PSEG_IO1_G4 -o S1______' You might think that AFP Page Segments could be generated from Encapsulated PostScript (.eps) files, as via ps2afp - but NO. A PostScript object must be a full program, including a 'showpage', to generate a Page Segment from it. The 'showpage' merely serves as to incite AFP to fully convert the EPS: it does not cause a page eject in the Page Segment. This is verified by subsequently being able to combine other elements with the Page Segment in compositing the ultimately desired page. Page Segment, using The PPFA PRINTLINE (traditional, carriage control) or LAYOUT (modern, record format) commands allow inclusion via their SEGMENT spec. Page Segment internal name 'afpdmp ' where the BPS (Begin Page Segment) line gives the internal name of the page segment. Page Segment name As employed in PPFA, via the SEGMENT keyword, the name of the file constituting the page segment can be one of: - S1______ where the portion following the S1 is 1-6 chars, upper case. - '________' quoted name, up to 8 chars, mixed case. Pagedef Page Definition. Contains the formatting controls for line data. As generated by the PPFA command. In an ASCII system (Unix), the binary result will contain a mixture of EBCDIC and ASCII: +0x22: d7d7c6c161c1c9e7 (EBCDIC for "PPFA/AIX") Note that the pagedef binary does not contain any path names. REPLACE YES serves to replace the Pagedef binary in the designated output location - not necessarily /usr/lpp/psf/reslib/. Pagedef authoring With a tool like PPFA. Pagedef debugging Pagedefs library /usr/lpp/psf/reslib/ Pagedefs source /usr/lpp/psf/ppfa/ (if PPFA installed) Pages Column in Jobs display. Reflects the incoming job-page-count value, if generated into the job by the PostScript driver, else is null. (For PostScript, IPM gets that attribute from the like "%%Pages: 14" value that usually appears at the end of the job file, in the %%Trailer section, as referenced by the prolog "%%Pages: (atend)". But, the value may be in the prolog, like: "%%Pages: 30". Jobs which have "%%Pages: (atend)" but no trailer "%%Pages: nn" have job-page-count undefined. Curiously, IPM *assumes* that programs which generate PostScript will always write the pages count in the trailer, after then have processed all pages so as to have accumulated a count: IPM will not detect a "%%Pages: 8" value in the prolog, because it doesn't look at the head of the file!) Where a PostScript job does contain a %%Pages value, IPM will show the count in its Pages column like "0 of 30" when the job is pending. And then in the Retained Jobs area, the Pages column will simply say "30". Note that Pages is only the face-value count taken from the incoming job, and does not reflect any actual pages count which IPM will have as a result of its job processing. For example: A job may claim 129 pages but only print 33, because the page count is a logical value and the job was created to image four logical pages on a physical page. pages-completed Job attribute reporting the number of pages in this job that have been printed; and if you are using the PSF DSS, stacked. Before the job is printed, this attribute will have the value 0. GUI label: Pages completed DSS: AIX, PSF, Infoprint 2000, Email, Fax The frequency of update for this number is governed by the ack-interval attr. The various DSSs for ADs report pages-completed differently. For example, ADs created using the PSF DSS report the number of IPDS pages printed, based upon the number of begin-page and end-page structured field pairs in the data. As a result, if you print a 2-up document as duplex, you could get a page count of 4 for a single sheet of paper. However, if you created an AD through the AIX DSS (which does not support number-up printing), it counts each side-sheet printed as a single page. As a result, if you print duplex, you will get a page count of 2 for each sheet printed out. This number increases as the job prints, and at least in the case of PSF is incremented only after a sheet is fully imaged, so that its pages are committed. In PJL printing to PostScript printers (e.g., HP) this value is changed as the printer reports printing each further page, via USTATUS feedback. But don't expect to always see real-time updating of this number: experience shows that IPM only updates it occasionally, so you'll see big jumps. See also: ack-interval; current-page-printing; Page count Palladium A distributed print system developed at MIT/Project Athena with participation from Digital Equipment Corporation (DEC), International Business Machines (IBM), and Hewlett-Packard (HP). It is a reference implementation for the OSI Document Printing Architecture (DPA) standard, ISO/IEC 10175. Palladium is a freshly designed, complete printing system, from command and application interfaces through printer supervisors. Palladium was selected in 1990 as the DCE distributed printing technology. Infoprint was designed using Palladium concepts. From Palladium comes the "pd" prefix used for many executables. Indeed, the Infoprint Manager product is not the only one which sprang from Palladium: there was also the HP Distributed Print Service (HPDPS), using the same commands and environment variables as IPM. Whence the name Palladium? Perhaps because it is the name of a salt used in early photographic imaging, as an alternative to silver - and the name sounds cool. Paper jam /var/pd//error.log message: 5010-838 /var/psf//error.log msg: 0420-466. (Note that there will be no msg in this log reflecting clearing of the jam.) Paper low (low on paper) error.log msg: 5010-829 Paper sizes Dimensions, as Width x Height: INCHES MILLIMETERS 4A 66.22 x 93.62 1692 x 2377.95 2A 46.81 x 66.22 1189 x 1692 A0 33.11 x 46.81 841 x 1189 A1 23.39 x 33.11 594 x 841 A2 16.54 x 23.39 420 x 594 A3 11.69 x 16.54 297 x 420 A3+ 18 x 12 457 x 305 A4 8.27 x 11.69 210 x 297 A5 5.83 x 8.27 148 x 210 A6 4.13 x 5.83 105 x 148 A7 2.91 x 4.13 74 x 105 A8 2.07 x 2.91 52 x 74 A9 37 x 52 A10 26 x 37 B0 1000 x 1414 2B 55.67 x 78.74 1414 x 1500 B0 39.37 x 55.67 1000 x 1414 B1 27.83 x 39.37 707 x 1000 B2 19.68 x 27.83 500 x 707 B3 13.90 x 19.68 353 x 500 B4 9.84 x 13.90 250 x 353 B5 6.93 x 9.84 176 x 250 B6 125 x 176 B7 88 x 125 B8 62 x 88 B9 44 x 62 B10 31 x 44 C (US) 17.00 x 22.0 C0 917 x 1297 C1 648 x 917 C2 458 x 648 C3 324 x 458 C4 229 x 324 C5 162 x 229 C6 114 x 162 C7 81 x 114 C8 57 x 81 C9 40 x 57 C10 28 x 40 D (US) 22.00 x 34.0 E (US) 34.00 x 44.0 Executive 7.5 x 10.0 F (US) 28.00 x 40.0 Folio 8.5 x 13.0 216 x 330 Ledger 11.0 x 17.0 279 x 432 Legal 8.5 x 14.0 216 x 356 Letter 8.5 x 11.0 216 x 279 SRA3 17.72 x 12.6 450 x 320 Tabloid (same as Ledger) __POINTS___ A0 2384 x 3370 A1 1684 x 2384 A2 1191 x 1684 A3 842 x 1191 A4 595 x 842 A5 420 x 595 A6 297 x 420 A7 210 x 297 A8 148 x 210 A9 105 x 148 B0 2920 x 4127 B1 2064 x 2920 B2 1460 x 2064 B3 1032 x 1460 B4 729 x 1032 B5 516 x 729 B6 363 x 516 B7 258 x 363 B8 181 x 258 B9 127 x 181 B10 91 x 127 Executive 522 x 756 Folio 595 x 936 Foolscap 612 x 936 Invoice 396 x 612 Ledger 1224 x 792 Legal 612 x 1008 Letter 612 x 792 Postcard 284 x 420 Quarto 610 x 780 Statement 396 x 612 Tabloid 792 x 1224 10x14 720 x 1008 Notes: In the ISO paper size system (A_, B_), all pages have a height-to-width ratio of square root of two (1:1.4142). This aspect ratio is especially convenient for a paper size. If you put two pages with this aspect ratio next to each other, or equivalently cut one parallel to its shorter side into two equal pieces, then the resulting page will have again the same width/height ratio. The ISO paper sizes are based on the metric system. The square-root-of-two ratio does not permit both the height and width of the pages to be nicely rounded metric lengths. Therefore, the area of the pages has been defined to have round metric values. As paper is usually specified in g/m, this simplifies calculation of the mass of a document if the format and number of pages are known. A4 is a common European paper size, as Letter is to the United States. PostScript files obtained from European sources may be composed for A4 size paper, which is problematic, in that it prevents common US printing. Command 'pdmsg 0423-791' will report common paper sizes. See also: PostScript QuickFacts Paper supply exhausted With an IPDS printer: /var/psf//error.log msg: 0420-023 Paper weight United States: For Letter size paper is given in pounds per 500 sheet ream of uncut C size paper. For Letter size paper, a C sheet is cut into 4 equal sheets so that a cut ream of letter size paper, 500 letter size sheets, weighs 5 pounds if the paper is nominally 20 pound paper. Metric: The weight of metric paper is given in grams per square meter (gms). By definition, one square meter is one A0 size sheet or 16 A4 size sheets. Passthru mode As possible with printers such as the Infoprint 2000, refers to conveying the job file directly to the printer, without transformation in IPM. Passthrough printer Jobs flow through IPM without transformation: the printer will RIP the job. See also: PJL considerations Password See: Web administrator password PATH In Unix, the environment variable defining a list of directories to search for a command which is invoked simply by name rather than full path. During IPM AIX install, /etc/environment is updated to add a line defining the PATH variable for system users to adopt, containing /usr/lpp/pd/bin and /usr/lpp/psf/bin. IPM does not search the PATH list for a command that is specified in any of the various server settings: you need to always code the full path name of executables. Pause printer To make the printer unavailable for a short period of time, as when changing toner or media. GUI: Printer -> Stop, select Pause or use the red stoplight. Msgs: 0423-409; 0423-411 Reverse this with a Resume. See also: Disable PC In the Infoprint 1585 and similar printers, refers to the Photoconductor, as in its Web page message: PC Unit Life Remaining: 84% and the panel messages: 84 PC Unit Life Warning 84 Replace PC Unit Its lifetime in a 1585 is about 60,000 pages, varying with the amount of toner deposited on the pages. See also: Photoconductor PCL Printer Control Language, developed by HP for its (low end) printers. Files are binary, consisting of a repertoire of Escape sequences embedded in a print job to govern the handling of the printing. In PCL versions before 5, its fonts were bitmap: version 5 introduced scalable fonts and version 6 improved on their capabilities. (Contrast with the more sophisticated PostScript language, which had scalable fonts from the beginning.) Example: & l 0 S selects simplex printing. File seen to begin with: E&l0o0e0F&a0l255M&f7X*c1F snfrmain reports as "HP_PCL." PCL, create from any format There may be times when you have a certain file format (PostScript, PDF, TIFF, JPEG, etc.) and want an equivalent PCL file. You can indirectly create one via the following technique: Submit the file as a job to a PSF Command type of AD, whose output is an AIX print spool file. By simply doing a 'disable' on that AIX print spool, jobs landing in there will be held, and can be copied from the /var/spool/qdaemon/ directory. Alternately, you could rig the PSF Command definition so that its destination-command spec is a command which simply writes the file to a designated place, based upon jobname. PCL 6 A complete rewrite of PCL, rather than a further enhancement of what came before. As a result, PCL 6 is substantially faster than its predecessors. PCL copies spec In PCL, the number of copies to produce for a document is internally defined via the SET QTY spec. Example: @PJL SET QTY = 5 sets the QTY environment variable to product 5 collated copies of the job. Contrast with "@PJL SET COPIES = 5", which produces five copies of each page of the job (uncollated). It is important that the PCL code to follow doesn't include the "number of copies command" (binary) within it (&l#X): such will produce uncollated copies. PCL End-of-Job marker Is Escape+'E'. The -c option of the 'pcl2afp' transform can be used to concatenate multiple input files without putting a Esc-E (end of job) characters between the files. PCL server address Under printer Properties, the Customize tab has a "PCL server address", used to define the network address of the host where a transform will be run for PCL which is embedded in AFP. Default: 127.0.0.1 Attr: pcl-server-address See also: PostScript server address PCL server port Under printer Properties, the Customize tab has a "PCL server port", used to define the network address of the host where a transform will be run for PCL which is embedded in AFP. Default: 8253 Attr: pcl-server-port See also: PostScript server port PCL transform /usr/lpp/psf/bin/pcl2afp Is transformed to bitmaps...which tend to be large, which argues for 100 Mb ethernet for feeding the printer. PCL/PostScript feature Optional functionality for the midrange Infoprint printers (2105ES et al) to provide PCL and PostScript interpreters for when you don't intend to drive the printers via IPDS. These interpreters seem to be the real thing (HP PCL and Adobe PostScript), rather then "emulation" as in the Infoprint 1585 - so expect full functionality and good performance. For the 2210: it comes with PCL; PostScript+PDF is optional. pcl2afp Command to transform PCL Data to AFP. Syntax: 'pcl2afp [-aOutputType] [-C ConfigurationFile] [-c] [-j nnnn] [-device "[plex,] [inputn=(pcl_bin=m)] [inputn=(pcl_bin=m)]"...] [-l nnnn.nnnu] [-M nnnnn] [-o OutputFile] [-P nnnnn] [-p PageRange] [-pragma pcl_x_origin nnnn.nnnu] [-pragma pcl_y_origin nnnn.nnnu] [-q] [-r nnn] [-S ServerName] [-s nnnn] [-w nnnn.nnnu] [-x nnnn.nnnu] [-y nnnn.nnnu] [InputFile ...]' pcl2afp.cfg PCL transform command configuration file, which may be located in the current directory or in IPM's /usr/lpp/psf/pcl2afp/ directory, whose use overrides the ultimate pcl2afpd.cfg daemon config file. Ref: Reference manual, pcl2afp command pcl2afpd Transform daemon to convert PCL to AFP. Manages the PCL interpreter portion of the pcl2afp transform. Must be running for the pcl2afp to operate. Started by /usr/lpp/pd/bin/startsrv via cmd: /usr/lpp/psf/bin/pcl2afpd Is not implicitly started when one runs a pcl2afp transform command. Important: This daemon, like all transform daemons, run as Unix user "daemon" rather than "root"; and their /var/psf/*2afp/* files must also be owned by "daemon" so that the transform daemon can read and write them - particularly the Pipe files. Further, the Unix Resource Limits (AIX /etc/security/limits file, and 'limit' command choices) must allow the file and memory sizes needed for production. There will likely be multiple daemons running, with different -C values. When a PCL transform is running, this daemon will have a process child named "pcl6". Config dir: /usr/lpp/psf/pcl2afp/ Config file: /usr/lpp/psf/pcl2afp/pcl2afpd.cfg Uncomment the "device_controls = plex" line to allow users to choose between single-sided and double-sided (duplexed) output. (Note that this has the effect of causing the transform to generate an inline Resource Group named INLINERS ahead of the AFP for the document itself, allowing document processing to reference Medium Map names to effect paper tray selection, stacker offsetting, etc.) Ref: Reference manual See also: daemon; ps2afpd pcl2afpd.cfg (/usr/lpp/psf/pcl2afp/pcl2afpd.cfg) The default PCL printing file configuration file used by the pcl2afpd daemon. Review its specs, particularly pcl_resolution, and device_controls for duplex printing. pcl6 Process name which shows up in the AIX Process Table when a PCL transform is running. The parent process = pcl2afpd. pd The general product prefix, chosen for the product's basis in Palladium. (Some might argue that the "pd" prefix was chosen just so there could be a 'pdq' command.) See also: Palladium PD_LANG The product national language environment variable. For the US: en_US pdaccount Administrative command to collect summary accounting info for a specified time period in a comma delimited format about jobs processed by actual destinations on one or more servers. This info can be filed and imported into a spread sheet to calculate the cost of consumables, the usage rate of printers, the cost for each user, and so forth. You can request summary info or all available info, which includes the following: - Total pages printed by a destination or a user for a specified time period; - Total octets printed by a destination or a user for a specified time period. You can also request complete records for a specified time period. When the log-accounting-data AD or server attributes are set to True, IPM creates an accounting log for each destination and stores the data into /var/pd//accounting.logs/ . See also: Accounting data, log PDB The print server database, comprising the various files found in directory /var/pd//pdb/. PDBASE IPM environment variable, whose value is "/var/pd", as set by: AIX: /etc/environment Linux: /etc/profile.d/ipm_environment.sh the AIX install. pdcapture /usr/lpp/pd/bin/ Ksh script to capture data for debugging Infoprint Control problems in conjunction with IBM IPM Support, as from a server trace. Must be run as root. Output: First creates and populates temporary work directory /var/pd//debug/ with its files, and then creates tar file /var/pd//debug.tar.gz (perhaps 16 MB in size) which can then be FTPed or emailed to Ricoh. (In the past, the command used to conclude by asking if you wanted to save the output to tape.) FTP info: ftp.infoprintsolutionscompany.com anonymous pw is your e-mail ID cd to "toinfoprint/L2" Upload the debug.tar.gz file, adding the SR # to the filename and don't include spaces in the name. If the ftp fails for any reason, you must change the name to retry as it will not overwrite existing files. See also: Ricoh, submit problem report; Server Trace pdclean Command to remove all objects from a specified destination, queue, or server. IPM prompts for confirmation in deleting the object, unless the environment variable PD_CONFIRM_DELETE is set "no". pdcrdflt Command to create Default Auxiliary Sheets, Media, and Queue in Infoprint Manager for AIX. Syntax: 'pdcrdflt [-c] ServerName' The IPM server needs to be up when this command is invoked. Successful execution results in no messages. Creates: - Default queue: /var/pd//pdb/queue/ -q - Default logical destination: /var/pd//pdb/log_printer/ -l - Default auxiliary sheets and media in a server: /var/pd//pdb/aux_sheet/ 64xx,accounting-log,blank,brief,full, job-ticket,none /var/pd//pdb/medium/ A3,A4,B4,B5,ledger,legal,letter,tabloid - Apparently also creates /var/pd/.pdcrdflt to indicate that the deed is done. The file contains the ServerName (system hostname), perhaps preceded by an option flag. The Reference manual says: "You only need to run the pdcrdflt utility if the startsrv utility failed to create all the default objects." This can be verified by looking to see if the above files have been created. Despite what the manuals says, my experience in 4.1 and 4.2 is that startsrv does *not* create the objects. pdcreate Administrative command to create Infoprint objects (except servers, logs, documents and jobs) and to set their attributes to specific values. Invoke as 'pddelete -h' to see usage. Syntax: pdcreate [-c object class] [-g] [-m "message text"] [-r requested attributes] [-s style name] [-x "attribute value pairs"] [-X attributes file name] {ServerName:AuxiliarySheetName ... | ServerName:DestinationName ... | ServerName:InitialValueDocument ... | ServerName:InitialValueJobName ... | ServerName:MediumName ... | ServerName:QueueName ... | ServerName:ResourceContextName...} pddelete Command to delete Infoprint objects. 'pddelete [-c ] [-m ] [-x ] [-X ] :|' Class is one of: destination (This is the default) job server queue auxiliary-sheet document initial-value-job initial-value-document medium resource-content transform log IPM prompts for confirmation in deleting the object, unless the environment variable PD_CONFIRM_DELETE is set "no". pddeviceop Command to perform device operation on a device associated with an AD. Employs SNMP write to make changes to the device operating mode. pddisable Command to disable various server functions, such as logging, logical destinations, or actual destinations. Note: Has no effect on a queue: invoking it on a queue returns no message saying whether it worked or that it's inappropriate. /usr/lpp/pd/bin/pddisable, a symlink to /usr/lpp/pd/bin/pdcommand. See also: pdenable pdenable Command to enable various server functions, such as logging, logical destinations, or actual destinations. /usr/lpp/pd/bin/pdenable, a symlink to /usr/lpp/pd/bin/pdcommand. Syntax: pdenable [-c ObjectClass] [-m "MessageText"] [-x "attribute=value ..."] [-X AttributesFileName] {ServerName ... | ServerName:LogName ... | [ServerName:]DestinationName ... | [ServerName:]QueueName ...} pdenable -h Environment variable: PD_ENABLE_TIMEOUT A user on the server system trying to submit to a disabled LD will get: 5010-562 Destination in server ______ is disabled and cannot accept submission requests. enq: (FATAL ERROR): 0781-364 Job submission failed. See also: pddisable pdenq Infoprint Manager's version of the AIX 'enq' command. Serves as an interface between AIX and IPM such that AIX can hand IPM a print job when the job's logical destination is defined in IPM rather than in AIX's /etc/qconfig. pdenq, in turn, invokes /usr/lpp/pd/bin/ipm_pdenq. Object module: /usr/lpp/pd/bin/pdenq There is no documentation. The AIX printing environment commands have long referenced this IPM command. See: AIX printing commands accommodate IPM See also: ipm_pdenq pdeventd /etc/services TCP port definition created at install time. Number: 6875 Is an outbound port number used by the pdserver process to communicate status changes to those running a flavor of the Infoprint Manager GUI. The GUI thereby receives updated information for its display. See usage via lsof -i :pdeventd PDF files and fonts Too often, PDFs are created by uninformed amateurs, resulting in printing problems for those who adopt the resulting files. The most important PDF creation option - which has been around since the early days of PostScript - is: embed ALL fonts used by the PDF. Too often, PDFs are created specifying relatively obscure fonts... which are often not part of the traditional PostScript font set. This makes for font substitution, and thus irregular looking output. A PDF sent directly to a printer may produce undesirable results whereas a PDF processed through Acrobat Reader and then printed (as PostScript) looks fine: why? It is because AR anticipates this, and comes equipped with a modest set of fonts commonly used in PDFs, which it can then generate into the PostScript file. Note that font embedding may be subject to licensing restrictions. See policy: http://www.adobe.com/type/browser/legal /embeddinginfo.html (A PDF or PostScript file wherein all needed fonts and images are embedded is called a blind exchange document.) PDF files and printability Often, a modern Acrobat Reader will balk at a defective PDF file ("The file is damaged and could not be repaired."); but it is not the case that if AR will display a file that the file is okay and printable. I've seen cases where AR will happily open and display a PDF - but it will not print in either PDF or translated PostScript because of Error: rangecheck; Offending Command: filter PDF pages count The -v option of pdf2afp reveals the number of AFP pages generated, as in: Wrote 8 pages of output type AFPDS IO1 (G4 MMR, 260), at approx 799.33 ppm PDF processing Occurs with the pdf2afp transform command, which is variation on the ps2afp command. Note that the PDF transform differs considerably from the PostScript transform by copying the PDF into /var/psf/ps2afp/, where it will have a file name like PDFkkQbGJ. This means that your /var/psf file system needs to be sized to accommodate large PDFs, and that the file system needs to be kept clean of core files, trace files, etc. PDF processing speed See: PostScript vs. PDF processing PDF vs. AFP PDF provides an excellent imaging model compared to AFP. One thing to keep in mind with PDF is that it is divorced from printing: while PostScript would embed instructions for selecting paper tray, simplex/duplex, and finishing, PDF architecture is independent of printing such that a PDF will never contain such info. pdfinfo Portable Document Format (PDF) document information extractor command, to display info from a PDF's internals. The command may be installed in some Linux environment - but not all. See also: Xpdf pdfprs Multi-processor PDF RIP module, to be used when your AIX RS/6000 system has four or more processors and you want to increase the performance of PDF RIPs. Writes files into /tmp (/tmp/psf6000.service.debug), Config file: /usr/lpp/psf/ps2afp/pdf2afp.cfg Advisory: This is complex stuff, which one would undertake only if there were compelling motivation. Ref: Procedures manual "Using the PDF Parallel RIP" pdf2afp Alias for the ps2afp command (q.v.), to transform PDF to AFP, using a single processor. (Use pdfprs for multi-processor.) The IPM server must be up for this command to run. Surprisingly, this task copies the PDF to /var/psf/ps2afp/ for processing - so you need to have capacity in that file system area. Messages are sent to Stderr. Note that the pdf2afp command will happily transform PostScript, rather than PDF. However, the command will not accept a mixture of PostScript and PDF, as you might want to do to conveniently create a single AFP from the combo. Reason: it sniffs the input to detect a single type, based upon the leading data, then processes by that single type. PDFs may call for but not include some fonts (Arial, Bold Arial are common), resulting in error message 0424-092 from the pdf2afp as font substitution occurs. The command returns a status of 0 nevertheless. Log: /var/psf/ps2afp/ps2afpd.log Job page count: Note that, unlike the ps2afp transform, this pdf2afp transform does not cause the job-page-count attribute to be set. To get the PDF page count, you can capture the output of the transform, using its -v flag, as in: pdf2afp -o /tmp/xxx -v Some.pdf where one of the output lines is like: Wrote 4 pages of output type AFPDS IO1 (G4 MMR, 260), at approx 27.19 ppm Transforms across systems: Via the -S and -P options, a ps2afp client on one computer system can cause the transform to occur on another IPM system. If the expected ps2afpd happens not to be running on that remote system, ps2afp exits with non-unique status code 1, and message 0423-156 ERROR: ps2afp: Server connection cannot be established (return code=-79). See also: Font substitution, PostScript PDIDTABLE Environment variable for the Palladium job ID Table (actually file /var/pd//pdjobs) which correlates job local ID numbers (1, 2, 3, 4, ...) with their 10-digit Global ID numbers. Doc: IPM 4.1 Reference manual That manual says that this number may be up to 32767 - but says nothing about a lower value. From the developers, I learned that a value of 0 results in use of default value 100. From testing, I found that a value of 1 causes the server to be unresponsive in restart. I found a low value of 5 to be safe. When a user's local job numbering reaches the limit, the numbering starts over at 1. In 2007 I pursued the pdjobs performance problem with IBM, where in APAR IZ03251 and thereby PTF level 7 (U811589) they now have the 0 value disable use of the pdjobs file. See also: job-client-id; /var/pd//pdjobs PDL Page Description Language. For example: PCL, PostScript. PDL revealed When a file is being transformed by IPM, its PDL will be revealed in the Format column. pdlicmgm License Key Management Application command, as found in IPM 4.4. Invoked without options, it brings up an Xwindows GUI, described in the Getting Started manual. Invoke with options, as summarized in the Reference manual, to perform the license registration without bringing up a GUI. pdls /usr/lpp/pd/bin/pdls -> pdcommand 'pdls [-c ObjectClass] [-f "FilterCriteria"] [-F] [-g] [-j] [-r RequestedAttribute ...] [-R serverName] [-s StyleName] [-U] [-x "attribute=value ..."] [-X AttributesFileName] [ServerName ... | ServerName:AuxiliarySheetName ... | ServerName:DefaultDocumentName ... | ServerName:DefaultJobName ... | ServerName:LogName ... | ServerName:MediumName ... | [ServerName:]DestinationName ... | [ServerName:]QueueName ... | ServerName:ResourceContextName ... | ServerName:TransformName ... | LocalJobID[.DocNumber] ... | GlobalJobId[.DocNumber] ...]' or do 'pdls -h' to get usage info. Specify "-s column" for a columnar report. ObjectClass is one of: auxiliary-sheet document initial-value-document initial-value-job log medium destination queue resource-context transform server You can request info on multiple attributes at one time by listing them in format: -r "attr1 attr2 attr3" . The results come back on successsive lines of Stdout, in the order requested. Notes: A pdls is expensive, taking time and significant CPU time to run. As such, pdls is inadvisable in IPM user exit processing, where overall user exit time should be short. Return (status) codes: 0 Can communicate with server, and good results returned. 1 Can communicate with server, but some error in the request. 2 Could not communicate with server (5010-452) Invoke pdls with attribute "when=now" for an AD to cause IPM to immediately return its most recently obtained status information about a printer or other device, and *not* communicate with the device via SNMP to discern its current status. Note that pdls has been seen to take longer - as in report lines appearing in fits and starts rather than rapid output - where there is a problem with DNS service to the computer system. Logging: The server error.log will contain the entry: 5010-362 Starting the list request for _____ objects. where the type of object (class) will be filled in. When the server has provided the list, it will log entry: 5010-363 The list request for _____ objects is complete. pdmod Modify the values of job and document attributes of previously submitted jobs. 'pdmod [-g] [-m "MessageText"] [-n CopyCount] [-r none|brief|verbose] [-s column|doccol|line] [-t JobName] [-x "attribute=value ..."] [-X AttributesFileName] {LocalJobID ... | GlobalJobID ...}' Specify: -x "attribute=value" to replace -x "attribute+=value" to add to -x "attribute-=value" to reduce -x "attribute==" to reset to default (i.e., delete the attribute from the job) Return (status) codes: 0 Can communicate with server, and good results returned. 1 Can communicate with server, but some error in the request. 2 Could not communicate with server (5010-452) 3 The job cannot be modified because it is in processing state (as in a transform). (5010-131) See list under 'pdls'. Example: pdmod -x 'job-hold=false' ${HOST}:1234567890 You can do 'pdmod -h' to get full usage info. Jobs cannot be modified if they are in the processing, printing, terminating, or unknown state: return code 1 and error 5010-131 results if you attempt to modify an active job. Note that this command is to modify the attributes of existing jobs. Use the 'pdset' command to change the attributes of other IPM resources, such as printers and transforms. pdmsg Korn shell command to view all information for a specific Infoprint error message. Valid message numbers: 0420-001 through 0423-999 and 5010-001 through 5010-999; however, not every number in these ranges has an associated message. Syntax: 'pdmsg [-d] [-t] MessageNumber' -d Display only the description of a message. -t Display only the text of a message. Example: pdmsg 5010-096 See also: Messages repository PDNOTIFY Environment variable in Infoprint Select, to be in the System Variable area of Windows: If it is set to any value, the Infoprint Select client will not create anotification-profile for the jobs it sends to the Infoprint Manager Server; but if it is not set to any value, the Infoprint Select client creates anotification-profile for the jobs it sends to the Infoprint Manager Server. pdnotify You would think that such a command would exist, to allow issuing an informative message to a job submitter from a transform program, for example, but there is no pdnotify command. pdnpmsrv Small program in /usr/lpp/pd/bin/. Referred to by IBM as "Java server", seen in Unix Process Table as "java Server". No provided documentation. Is started after pdserver. Started in: /usr/lpp/pd/bin/startsrv The start is very peculiar. You must: setenv LIBPATH /usr/lpp/pd/lib cd /usr/lpp/pd/bin /usr/lpp/pd/bin/pdnpmsrv Or, simply use the /usr/lpp/pd/bin/restart_npm_server script to restart pdnpmsrv. (Beware that this is a primitive script which sometimes doesn't work, but says nothing: you may have to do 'kill -9' on the java and pdnpmsrv processes, then issue the script.) Though successfully restarted, it may thereafter take a half hour or more for the More Information button to appear in Check Status displays. Binary: /usr/lpp/pd/bin/pdnpmsrv Depends upon /usr/lpp/pd/lib/libnpmserv.so, which must be in the LIBPATH for pdnpmsrv to start successfully (else it dies). Usually seen running in an IPM system, with a child process named "java Server", which serves real-time data to the Java-based GUIs (e.g., operator GUI) which run on Windows boxes, for the Check Status function, More Information subfunction, which displays a depiction of a printer and its changing control panel info. The printer depictions are stored in directory /usr/lpp/pd/ipgui/ com/ibm/npm/gui/printer4/. For HP printers, the prtgenc.gif (generic printer) is used. If the pdnpmsrv process is killed off, the "java Server" process lives on, as a child of Init. See also: java; NPM pdpause Operator command to pause an object that holds jobs or to pause a job. Undo this with pdresume. See also: pdresume pdpr The elemental Infoprint command for submiting a job to a logical destination in the local system. (Cannot be used to send jobs across systems. In AIX you can use the 'rembak' command to achieve that.) 'pdpr [{-d | -p} LogicalDestinationName] [-f FileName ...] [-g] [-l] [-n CopyCount] [-N NotificationMethod] [-r none | brief | verbose] [-s column | doccol | line] [-t JobName] [-x "attribute=value ..."] [-X AttributesFileName] [-Z InputFileName] {- | FileName ...}' You may set the PDPRINTER environment variable with a default printer. To print duplex: -x "sides=2 plex=simplex" The pdpr command calls line2afp to invoke ACIF. Parameters not allowed on the pdpr command can be passed to ACIF with the -x "other-transform-options" attribute. PDPRINTER AIX environment variable naming the logical printer to be used as the default logical printer. If set in /etc/environment, it defines the default printer destination for all users of the system, unless they have their own individual setting. pdq The elemental Infoprint command for querying the status of selected jobs, of all jobs submitted to a logical destination, or of all jobs assigned to an actual destination. Syntax: 'pdq [{-d | -p} destination name] [-f "filter criteria"] [-F] [-g] [-j] [-r requested attributes] [-s style name] [-U] [-x "attribute value pairs"] [-X attributes file name] [LocalJobID[.DocNumber] ... | GlobalJobID[.DocNumber] ...]' 'pdq -h' where: -d DestinationName Names the LD or AD in that queue. -g Turns off headings. -j Returns only the job attributes. -U Suppresses the default user-name filter, which is to say that rather than just going after your jobs, gather info on jobs from all users. Reports: - Relative job number - Global ID - Jobname - Current state - Intervening jobs Value is 0 if job is processing rather than pending. - Destination (LD) requested Destinations (AD) assigned Jobs are listed in the order in which the queue considers them for printing. Omitting JobID causes all jobs to be listed. To get a listing of all jobs in the queue, omit JobID and use -d or -p to specify any LD in the queue. A report element conspicuously missing in the default report is the name of the job originator/owner. You can tailor the report output by using both -r to provide to the command a comma-separated list of attributes you want reported, and -s to force the report layout you want. Note that pdq generates "human" headings for report columns - not attribute names. Unfortunately, there is no way to have the command return columns in a comma-separated list format, in that the output via -s column and -s doccol is no good for parsing in that some columns may have no values and so position information may be absent. Note that the width of the report varies with the longest jobname. If you do 'kill -STOP' on the pdserver process, the pdq command will simply hang. Command exit status: Always 0, whether or not any jobs are reported. A conventional way to invoke, to see all jobs in a queue associated with a prominent LD, is: pdq -U -d LDname pdresubmit Command to resubmit (reprint) a job, moving it to its original or different Logical Destination. (This command is how the GUI 'Move Job' function performs its task.) Simple case: 'pdresubmit ' Full: 'pdresubmit [-c ObjectClass] [-g] [-r "RequestedAttribute ..."] [-s StyleName] [-x "attribute=value ..."] [-X AttributesFileName] [ServerName:]TargetLDname {LocalJobID ... | GlobalJobID ... | [ServerName:]QueueName ... | [ServerName:]DestinationName ...}' Sample usage: pdresubmit ldest1 ourhost:0123456789 The purpose of the -X option is unknown: attempting to use it fails, "pdresubmit: 5010-003 The flag X is not valid." (This may be a case of documenters having copied the layout of other commands.) Further, attempted use of -x with general options fails, as with: "pdresubmit: 5010-033 The attribute job-hold is not supported." The command documentation seems to be grossly deficient in describing what -X and -x are for. Apparently, if you want to change some job options, you need to do it in a separate pdmod command, rather than incidentally with a pdresubmit. In resubmission, the job Create Time does not change. Presubmit resets job-state-reasons. For example, if a job aborts due to transform error, doing pdresubmit on it cause aborted-by-system, job-hold-set reasons and the job-state-reasons attribute itself to go away. pdresume Operator command to restart paused jobs, actual destinations, queues, or servers. Undoes what a pdpause did. See also: pdpause pdrm Command to remove (delete) previously submitted jobs. /usr/lpp/pd/bin/pdrm -> pdcommand IPM prompts for confirmation in deleting the job, unless the environment variable PD_CONFIRM_DELETE is set to "no". pdserver The Infoprint Manager main process, started by /etc/rc.pd (q.v.), which is started by its /etc/inittab entry. Notes: - It takes about minutes for the server to start - and the more pending and retained files present, the longer it takes. With some 5000 retained jobs, for example, it takes about 10 minutes. - The pdserver process keeps a lot of files open, particularly in the /var/pd//pdb/spl_job directory. Thus, the server, running as root, needs to have no artifical restrictions placed upon its number of open files, as controlled in AIX's /etc/security/limits file. Recorded where: There is no known file in Infoprint Manager's directories which contains the pdserver PID. WARNING: Avoid doing 'kill -9' on the pdserver process, as that can result in corruption of job information in the pdb. See also: ain3dpds; ain3dtcp pdserver, effects when not running The presence of the pdserver is obviously essential to the influx of new print jobs, both via Infoprint submission methods and via lpd. If pdserver is down, as for a restart, lpd will try to feed in jobs via the pdenq interface command - but obviously won't be able to. Evidence of such attempts can be found in the AIX /var/adm/messages log, as in entries like: lpd[64552]: 0781-208 unknown printer . (This message can also appear where someone has erroneously issued an LPR on a foreign system and there is no such LD as is specified in LPR-LPD interaction.) pdset Command to set the attributes of objects, such as destinations. Syntax: pdset -c Class -g -m "Message text" -r [none|brief|verbose] -s [doccol|column|line] -x "Attribute=Value" [-x ...] -X AttributesFilename Servername:Objectname Class is one of: destination (This is the default) job server queue auxiliary-sheet document initial-value-job initial-value-document medium p[rinter] (Same as destination) resource-content transform log The affectee must not be in an active state, for the command to work: - An actual destination must be in a disabled state. - A job must not be processing, else get error 5010-131. To set multiple attributes in one invocation, use multiple -x specifications on the command line. To change the attributes of previously submitted jobs, use the 'pdmod' command instead. See also: pdmod pdsettrace Command to control server tracing, in pursuing a problem with IPM Support. In: /usr/lpp/pd/bin/ Is a Ksh script which can be browsed for usage info. It operates on the class "log", doing pdenable and pddisable of :default_trace. Invoke with -h or -? to see usage. Syntax: pdsettrace -y|-n [-t standard|comm|verbose|all] [server-name] Where: -y Turn tracing on. -n Turn tracing off. -t Type of tracing to do: standard (or s): The standard set of trace groups. This is the default. comm (or c) : standard groups PLUS communication and notification groups verbose (or v) : comm groups PLUS attribute-set groups all (or a) : ALL trace groups WARNING: verbose and all generate a LOT of trace data and will cause frequent trace.log wraps! server-name The name of the server on which the tracing is to change. Default: this system Operates by doing a pdenable/pddisable with "-c log" for Server:default_trace. Note that the author of the pdsettrace command did not provide an option to query the state of tracing. Instead, you can do: pdls -c log -r all :default_trace And you can alternately determine if it is active by whether the /var/pd//trace.log file is growing. There will likely also be a /var/pd//cfcpp.log.0 Note that activation of server tracing impacts performance, so use sparingly. Messages: 5010-325 5010-326 5010-331 5010-332 5010-333 5010-334 See also: Server trace pdshutdown Administrative command to terminate the IPM server (the default) or shut down a PSF physical printer, fax destination, or email destination. You can shut down a server either immediately or after it finishes processing some or all of its current jobs. To shut down the server: 'pdshutdown ' To shut down an AD (a printer): 'pdshutdown -c destination ' Note that "-w now" does not immediately shut down the server - it just incites the server to begin a graceful shutdown. It may take 30 seconds or so for the shutdown to actually complete. PDT Printer Definition Table, as used when configuring a Personal Communications 5250 (or PC5250) printer session. PEL Picture ELement: a unit of measurement on a page, chiefly used by IBM in its printing. 240 PELs = 1 inch. Also referred to as a Dot in the doc. Considerations: Measuring things by dots or PELs can be problematic, as it's a relative rather than absolute measure. For example, a GIF image which has dot dimensions of 1200x1200 will print 4" square at 300 dpi, but 2" square at 600 dpi. The resulting printed output may thus be not as expected, or useful. Using absolute units (millimeters, inches, or points) makes for predictable results. See also: Point pending Job status: is in a queue, waiting for IPM to schedule and send it to an actual destination. May be because the logical destination is bound to a physical destination which is disabled; or the job itself is bound to a disabled DSS. Pennant Systems The devised name that IBM gave to their spun-off Printing Systems Division. In December 1991, as IBM's chairman and chief executive officer, John Akers, was running up against a declining mainframe market and a tough recession, IBM seemed to be prepared to spin out its enterprise printing business, and even went so far as to pay some hot-shot Madison Avenue marketeers to come up with a new name for this division - Pennant Systems - and set up a new headquarters for the division in Norwalk, Connecticut. Back then, IBM said it would eventually set this up as a wholly owned subsidiary, but it never did. Performance IPM's software engineering is such that it really requires a dedicated system in order to run well. Despite much of IPM software being written in C, IPM Performance affectors Based upon my experience with IPM and the jobs it faces: - Inefficient PostScript jobs. In a university environment in particular, there are many amateurs producing online course material PDFs from scans of books and magazines (and not always with copyright permission). Unfortunately, faculty tend to be computer illiterate, and don't make efforts to address obvious deficiencies in the material they produce. Thus, they often scan monochrome material in high-density color, which results in deep bitmaps which take an inordinate amount of time to render. (Use Ghostscript to visualize this.) To compound the problem, they make no effort to remove black areas from overscan and bindings shadows, where that "noise" has to be encoded in detail and rendered every time the job is printed. And each student in the class individually prints all the course material. Pain! A non-monochrome scan is visually apparent on-screen in often having either tinges of color, or even a full, false color (usually, yellow) background for the text. And the text appears fuzzy/grayish rather than sharp and black as in a monochrome scan. Additionally: Search for "performance" and "slower" in the manuals. .pfa Filename extension for the ASCII form of a PostScript font. .pfb Filename extension for the binary form of a PostScript font. Photoconductor In a laser printer, this is the light-sensitive drum which the laser plays over to form an image, where toner is attracted to spots where the image should be dark, and all that is then electrostatically transferred to a sheet of paper from the drum, and the toner is then heat-fused to the paper to form a permanent image. Because of laser and paper wear on the drum, the photoconductor needs to be replaced periodically. Abbreviated name: PC Alternate name: Photoreceptor drum In low-end printers, the photoconductor is built into the toner cartridge, where the toner runs out at about the same time as the PC's useful life is over. In workgroup and larger printers, the PC is a separately replaceable unit, with a usage countdown to alert the operator to when the PC will need replacing. In larger printers, the PC is often a drum, big enough to contain the whole image for a letter sized sheet of paper. In smaller printers, is may look like a large roller, where several revolutions are required to generate the image on a sheet. Physical destination, list attributes 'pdls -c destination -rall :' Physical destination files These are the containers for the current definitions and settings for the Actual Destination printers. As with all other definition files in IPM, they are MIB dictionaries. In directories: /var/pd//pdb/suv_phy_printer/ which is the progenitor /var/pd//pdb/phy_printer/ which houses working copies /var/pddir/default_cell/printers/ files for security tracking /var/psf/ It appears that suv_phy_printer is the permanent repository of physical printer definitions and that phy_printer is a working set, recreated at server restart. See also: Actual Destination files Physical printer In Infoprint, a type of actual destination that represents a printer device. See also: Printer device piobe See: AIX-usage QuickFacts pioibmdpf IBM AIX printing backend C module to send a print job to a PJL-amenable printer, with SNMP interaction. Invoked by pioibmdpm and pioibmnpm; is dependent on the various services provided by the qdaemon process. Takes the stdout data from the piobe command as stdin and transmits it over a TCP/IP connection to a network printer. It also can be used as a monitor for the printing job. If monitoring is enabled (see -ustat parameter), pioibmdpf will autodetect if the printer is a Homerun based one and will use the SNMP monitoring style. The monitoring is done for JOB status and PAGE status. This command is not intended to be invoked from the command line; rather, it is to be invoked by the qdaemon process and is dependent on the various services provided by the qdaemon process. Installed from aixpdnls.tar, an Infoprint 2090 driver package that can be downloaded from the IBM site: see document P4000155, "PS and PCL printer drivers and utilities for AIX". In: /usr/lib/lpd/pio/etc/ (but pioibmdpf may not be installed!) Syntax: pioibmdpf [-port ] [-ustat] [-verbose] [-snmp_port ] [-snmp_com ] [-snmp_retry_count ] [-snmp_timeout ] [-maxqtime ] [-retries Retry_Count>] where: IP_Address is the IP address or hostname of the destination printer. Port_No is the port number used to connect to the printer. Default: 2501 -ustat is a flag which enables JOB monitoring (PJL USTATUS actions). -verbose is a flag which enables the LOG file, as /tmp/pioibmdpf_.log Snmp_Port is the port number used by SNMP functions to connect to the printer. Default: 161 Com_Name is the SNMP community name used by the SNMP functions to connect and/or get info from the printer. (used by SNMP APIs) Default: public Snmp_Retries is the number of the retries, attempting to connect to printer. Default: 2 Snmp_Timeout is how many seconds will wait the SNMP functions in an attempt to connect or get info from the printer. (used internaly by the SNMP APIs) Default: 1 (sec) Maxqsecs The maximum waiting time to find the jobs in the MIBs. Default: 300 (secs) Retry_Count is the number of retries, when connecting to printer and sending data to it. Default: 1 Exit codes: 0 The job was successfully printed 1 An error occured during a memory allocation process 2 Wrong command line parameters 3 Error finding the printer (using the name or the IP address) 4 Wrong IP address 5 Error creating socket 6 Unable to establish a connection with the printer 7 Error writing to the printer 8 Error reading from the printer 9 Cannot create a child process 10 Cannot open the log file 11 Cannot write data to the log file 12 Cannot monitor the job 15 Unexpected (unknown) error 20 Timeout expired while getting the status informations from the printer 21 The job was aborted by the system for some reason 22 The job was canceled by the operator 23 The job was held on the printer for later printing Notes: The module is a physical writer, effectively part of the AIX realm, and as such knows nothing about IPM details, such as the job number. Ref: ??? See also: pioibmnpm pioibmdpm IPM enhanced AIX printing backend program that comes with IBM Infoprint 2085 and 2105 device driver package (downloadable), for having an AIX-queued print job sent to a network-attached 2085 or 2105 printer. In operation, it obtains device status from the job MIB (SNMP polling). This method was provided because IBM did not implement PJL in that printer series (which would allow the printer to feed back at page end and job end). Installed from aixpdnls.tar, an Infoprint 2090 driver package that can be downloaded from the IBM site: see document P4000155, "PS and PCL printer drivers and utilities for AIX". In: /usr/lib/lpd/pio/etc/ (an AIX area to which IPM adds its AIX modules) (but pioibmdpm may not be installed!) It is a small Ksh script rather than a compiled program, to then pipe to a combination of piobe and pioibmdpf. Syntax: pioibmdpm [port_no] [-ustat] [-verbose] [-snmp_port ] [-snmp_com ] [-snmp_retry_count ] [-snmp_timeout ] [-maxqtime ] [-retries ] [ otherParametersLikeIn_qprt ] Filename where Filename may refer to the output file from a transform, like /var/pd//pdprCfu2ia_xfm1 -ustat is a flag which enables JOB monitoring (PJL USTATUS actions), applicable with HP printers. where Port defaults to 2501 - the port most commonly used by IBM printers. Internally, it invokes: piobe $piobeargs | pioibmdpf $args This is why its args syntax is the same as for pioibmdpf. where args that it recognizes are passed to pioibmdpf and others to piobe. In the case of a PSF Other printer it is coded in the GUI's Printer Properties, General tab, Command field, as: /usr/lib/lpd/pio/etc/pioibmdpm printer1.bu.edu (port defaults to 2501 and is optional) Will create its own separator page, if so chosen in GUI Printer Properties, Auxiliary/Separator Sheets tab, Start sheet not "none". It is very line-printerish in appearance. The start sheet will not be stapled to the body of the job. It provides accurate job completion and job accounting for those printers. pioibmdpm should not be used with other printers; and the other IPM enhanced backends (pioibmnpm and pioinfo) should not be used with the Infoprint 2085 or 2105 printers. /usr/lib/lpd/pio/etc/pioibmdpm pioibmnpf Network Print Facility module. It conveys the given data stream to the designated networked printer, including interacting with the printer via PJL if so directed via the -u invocation option. The data stream that it operates with is typically piped to it from piobe, where piobe has augmented the job with PJL derived from the colon file associated with the printer model (as is common with HP printing). In: /usr/lib/lpd/pio/etc/ (Seems to be installed there by IPM.) Usage: pioibmnpf Ipaddr Port where: Port Defaults to 2501. Retries Is a multiplier for the number of retries that will be attempted before the queue goes down. If retries is not specified it tries forever. What this actually does is a mystery: it does not govern the number of 5-minute PJL retry intervals. There also seems to be an unrevealed -u option, which I surmise to correspond to the -ustatus invocation option of pioibmnpm, for enabling HP JOB monitoring (HP PJL USTATUS actions). Invoked by Ksh script pioibmnpm. See also: NPF pioibmnpm IPM enhanced AIX printing backend for HP and IBM printers which support PJL (excludes the IBM Infoprint 2085 or 2105 printers, which have their own pioibmdpm driver - because IBM chose not to implement PJL for them). The actual meaning of its name is unknown, but likely is "network printing, main program". Is actually a tiny Ksh script, which pipes from piobe to its pioibmnpf filter. piobe envelops the job body with PJL instructions derived from invoking piodigest against the colon file associated with the printer model. In: /usr/lib/lpd/pio/etc/ (an AIX area to which IPM adds its AIX modules) Syntax, minimal (per doc): pioibmnpm IPaddr [Port] where Port defaults to 2501 - the port most commonly used by IBM printers. For HP and other non-IBM printers, port 9100 is probably the one. Syntax, maximal (as discovered): pioibmnpm [port_no] [-ustat] where -ustat Causes the invoked pioibmnpf to be run with its -u option in effect, to enable JOB managment via PJL USTATUS actions, as applicable with HP printers and workgroup Infoprint printers made by Lexmark. This option is automatically applied if the printer destination-model matches a colon file name specifying PJL governance. Debugging can be activated by editing the script. In process executions, you will see pioibmnpm feeding HP printers with the -Y option, which is passed to piobe, where such options correspond to qprt flags: -Y 0 Simplex -Y 1 Duplex, long edge binding (the most common, for portrait) -Y 2 Duplex, short edge binding and results in plex setting values being sent to the HP printer, as described in "Duplex printing via PJL". In operation, it obtains printer status via PJL commands - see below. With an AIX DSS, the best way to achieve 600 dpi resolution is via AD attribute print-qualities-supported=high; otherwise, add qprt option -q 600 to the command line, which results in "PJL SET RESOLUTION = 600" being sent to the printer. This is necessary as the job attribute default-printer-resolution is not for AIX DSSes. Note: The wait-for-job-completion attribute doc says that this command uses PJL to obtain status from the printer: it sets USTATUS JOB = ON and USTATUS PAGE = ON. The PAGE setting causes the host to be notified after each page transition, and the JOB setting causes the job page count to be returned as "PAGES=n". Network traces show that, with newer HP printers at least, the printer absorbs the whole job, then sends back the lines @PJL USTATUS PAGE 1 at the end of printing page 1 (etc.) and then sends @PJL USTATUS JOB END PAGES=2 at the end of the job. Job progress and completion info are wholly gotten via PJL info sent by the printer: IPM does not perform SNMP queries for job status (as it does with pioibmdpm for Infoprint 2105 class printers). The module is a physical writer, effectively part of the AIX realm, and as such knows nothing about IPM details, such as the job number. As an AIX environment physical printing module, no IPM logical values (attributes) are presented to it, either as command line arguments or environment variables; so things like job Global ID are not known. An obvious question: If this module generates PJL, why is it said to drive IBM printers such as the 2105? Because the Infoprint 1585 and similar printers actually do process PJL - though there may not be documentation to say so. See also: destination-command; pioibmdpf pioinfo (AIX) IPM enhanced AIX printing backend for non-IBM printers (e.g., HP), which talks to a printer socket. Takes the place of AIX backends such as piojetd (HP Jet Direct). The driving is synchronous: the backend sticks with the job through its printing process. Should not be used with the Infoprint 2085 or 2105 printers. Syntax: pioinfo IPaddr [Port] where Port defaults to 9100 - the port most commonly used by non-IBM printers. Is: /usr/lpd/pio/etc/pioinfo being a ksh script, whose active ingredient is: /usr/lib/lpd/piobe "$@" | /usr/lib/lpd/pio/etc/pioinfoprt -x $hostname -p $port $args The printer you intend to drive must appear in the server's "AIX printer models" (snmp-aix-printer-models attr), which entails buying the right license package, such as "Low Speed Printer Engine" feature, which provides the needed modules. Note: You may also be able to specify /usr/lib/lpd/pio/etc/piojetd followed by the IP address - but there may be no piojetd in that directory. Note: the wait-for-job-completion attribute doc says that this command uses PJL to obtain status from the printer: it sets USTATUS JOB = ON and USTATUS PAGE = ON. The use of PJL means that this backend is suitable only for HP printers (and maybe some other printers which support PJL). Contrast with: pioibmnpm; rembak pioinfo (Linux) The CUPS backend printing module, used by the CUPS DSS to synchronously feed a job to a PostScript printer and stay in session with the printer in order to get back page-end and job-end info, including number of pages printed (this accomplished via PJL). /usr/lib/cups/backend/pioinfo As you would expect, prior to sending the PostScript file to the printer, it sends PJL commands, including: @PJL USTATUS JOB = ON @PJL USTATUS PAGE = ON per invocation option enable-ustat so as to stay in session with the printer and get back page-end and job-end feedback, including final job page count when the printer sends back: @PJL USTATUS JOB END NAME = "JOB 88554" PAGES=5 See also: CUPS DSS pioinfoprt Undocumented back end program, as used in pioinfo (q.v.), for HP/PJL printers. Is: /usr/lib/lpd/pio/etc/pioinfoprt pioipdm AIX DSS backend for the InfoPrint 2190, InfoPrint 2210, and InfoPrint 2235 printers. Apparently comes on a disc shipped with the printers. The port for the pioipdm backend defaults to 9100 (not 2501, as may be incorrectly found in some doc). Pipe-pull In Infoprint, a document transfer method where Infoprint saves the documents in a file and transfers the address of the file to the server. Infoprint transfers the file to the server upon the request from the server. This is an efficient transfer method for large jobs and is the default transfer method at job submission. Contrast with with-request. Pitch See: Font size PJL HP Printer Job Language. Used to set up configuration and other facilities for a printer. It can establish defaults for printing and provide direction to the printer on how to handle job items not specified by the PostScript or PCL language. A capability of particular value to a job feeder such as IPM is the USTATUS operand, to get page counts upon completion of PAGE or JOB. The PJL Reset command ^[%-12345X performs a PJL-independent reset. This allows PJL to be used with PostScript or PCL, like: ^[%-12345X@PJL @PJL RDYMSG DISPLAY = ":" @PJL USTATUSOFF @PJL USTATUS JOB = ON @PJL USTATUS DEVICE = ON @PJL USTATUS PAGE = ON @PJL USTATUS TIMED = 10 @PJL ENTER LANGUAGE = POSTSCRIPT ^D%! %!PS-Adobe-3.0 %% A page with a "1" on it. %%/Times-Roman /Courier findfont 200 scalefont setfont 72 300 moveto (1) show showpage ^D^[%-12345X@PJL @PJL RDYMSG DISPLAY = ":" @PJL EOJ NAME = ":" @PJL USTATUSOFF @PJL USTATUS JOB = ON @PJL USTATUS DEVICE = ON @PJL USTATUS PAGE = ON @PJL USTATUS TIMED = 10 @PJL RDYMSG DISPLAY = "Done: :" ^[%-12345X PJL considerations PJL communicates with the printer via the job stream channel - the path through which it submits the job to the printer (HP style port number 9100). The job submitting agent (e.g., print server) remains in session with the printer during job progress where page end and job end status is requested of the printer. A big consideration is that if the job contains difficult PostScript, the printer may be fully absorbed with RIPping the job page for up to even 20 minutes. In driving a PostScript printer via the pioibmnpm or pioinfo backends, not getting any USTATUS (unsolicited status) page progress feedback from the printer after almost 5 minutes of waiting (a subsecond before the 5 minutes are up), IPM issues PJL ECHO ARE YOU THERE (or @PJL ECHO 2147483647) to the printer - to which there is no response, because the printer is still too busy to respond. IPM then waits 5 more minutes for a response to the ECHO, at which time it gives up on the printer. Thus, if you see a job failing after exactly 10 minutes of processing, this is the scenario. In PJL communications, 5 minutes is a "magic number", being its conventional timeout value for the printer to close the communication channel if it hears nothing further from the host before that time is up. IPM will send the echo to the printer about 0.3 seconds before the 5 minutes are up in order to say that it's still there, implicitly telling the printer not to close the channel, and hoping to get a response. PJL in job files The PJL which arrives at the top of submitted job files comes from the PostScript device driver; and there is usually no print-time setting which will suppress this frontal PJL. IPM partially ignores the frontal PJL, but not entirely: it does not care about the content, but is sensitive to the line length... If a frontal PJL line is more than 132 chars long, the following error will be reported by psafp: %%[ Error: rangecheck; Offending Command: readline ]%% (The readline seems to be some internal PostScript processing performed by ps2afp.) Excessively long strings can come from Web page URLs, and are particularly useless when appearling on line @PJL RDYMSG DISPLAY = "........." where the quoted string is to appear on the printer control panel, which is often has a capacity of only 20 chars. PJL in job streams The PJL which appears in jobstreams to HP printers derives from the Colon Files (q.v.) for those printers. PJL supported by printer? Test using the 'pjldetect' command. (IBM printers do not support PJL.) PJL test See: pjldetect pjldetect Command to test a printer to detect if it supports PJL, by sending PJL to the printer. Exactly what happens: The command first sends %-12345X@PJL @PJL ECHO 1804289383 and if it gets that echo response, it further sends %-12345X@PJL @PJL INFO USTATUS to which the printer may respond like: @PJL INFO USTATUS DEVICE=OFF [3 ENUMERATED] OFF ON VERBOSE JOB=OFF [2 ENUMERATED] OFF ON PAGE=OFF [2 ENUMERATED] OFF ON TIMED=0 [2 RANGE] 5 300 Note that an AIX or CUPS DSS AD which responds to such USTATUS inquiries is the basis for the wait-for-job-completion attribute to be set True. /usr/lpp/pd/bin/pjldetect (requires libdcelibc_r.a(dcelibc_r_shr.o)). Messages are sent to Stderr. Syntax: 'pjldetect IPaddress Port' On HP printers, the port is most often 9100. Response: You hope for message: 5010-077 pjldetect: The printer at ________ supports correct job completion. [rc=0] But you may instead get one of: 5010-075 pjldetect: Error connecting to ____. [rc=5] Means that the host system is there, but port 9100 on it is not responding. 5010-078 pjldetect: The printer at ________ does not support correct job completion. 5010-076 pjldetect: Error determining job status support on printer ______. [rc=7] Means that the printer did not respond within the program's timeout interval. The response text line is without a newline at the end. Note that the command hangs on an unresponsive (turned off) printer. The IPM manual advises that sending such a PJL command to a printer *may* cause it to "print" a blank page - which will seem mysterious to the people at the printer. With HP printers, at least, I have found that no page will be printed; the only effect is to awaken a printer which is in power-saver mode. Status codes from command execution: Undocumented, but here's what I found: 0 You can access the printer from this host, and the printer does support PJL for job completion. 5 Cannot access printer, possibly because it is turned off. 7 The printer is apparently alive on the network, but can't determine if it supports PJL, probably because the printer does not allow access from this host. pjlprtrs.cfg File to be added by the customer to directory /usr/lpp/pd/bin/ naming DSS printer models which support PJL (e.g., HP printers) which support setting attribute wait-for-job-completion to True. The model spec is the same as is specified for AD attribute destination-model. In AIX this would be like: hplj-4000 hplj-8000 In Linux it is the PPD name, like: HP-LaserJet_4350-Postscript.ppd (which also needs to be in directory /usr/share/cups/model/ in Linux). The IBM doc specifies that such a file should be created if any of the following apply: - The printer supports PJL but does not support SNMP; - The printer is not on when you start the Infoprint AIX server; - The printer's AD is not using IPM's SNMP support. In reality, though, it is ESSENTIAL that you create this file, as its absence in an IPM server restart, where there is a network problem or where the printer is not turned on, can result in various functionality problems - and the VERY insidious effect that attribute wait-for-job-completion will silently be reset to False!! Note that this is a kludge that should be engineered out of the product (which I have requested that the developers do). IPM is an Enterprise level product. Requiring the customer to manually create a hokey file in the product installation directory is incongruous. Ref: Getting Started manual Plex A document or actual destination attribute used to define the placement of output images on the page. See: Duplex; Simplex plex Document/Default Document attribute: Indicates whether Infoprint conditions the page images of this document for one-sided or two-sided printing and the relative orientation of consecutive pages. Operates in conjunction with 'sides' attribute. GUI Label: Plex to print Specify one of: simplex tumble If you don't specify such a default, and the job does not internally contain such an attribute, no 'plex' attribute will be provided to a Transform Sequence. See also: sides Plex detection See: ps2afp output per PostScript factors Plex to print See: plex plexes-supported AD attribute for the plexes that it supports, indicating whether the page images of the output document are conditioned for eventual one-sided or two-sided printing, and the relative orientation of consecutive pages. GUI label: Plexes allowed DSS: AIX, BSD, PSF, Infoprint 2000, Print Optimizer Related: sides-supported PMF Print Management Facility, an IBM mainframe software product. PNG (.png) Portable Network Graphics (PNG) was developed as a replacement for the GIF standard due to legal entanglements resulting from GIF's use of the patented LZW compression scheme, and also because of GIF's many limitations. PNG is superior to GIF in many ways. IPM does not support PNG. POD Print-On-Demand feature (q.v.). See also: ainuxaccp; /var/psf/podaccount.log Point A unit of measurement on a page, chiefly used with PostScript. 72 Points = 1 inch. 1 point = 0.01388889" = 0.03527778 cm = 0.3527778 mm See also: PEL Pool destination configuration model Like the default destination configuration model; has a one-to-many relationship between a logical destination and two or more actual destinations. This model essentially dedicates a pool of printers to a single purpose. Ref: Intro & Planning manual, chapter Planning for configuration See also: Configuration models Port A term most commonly used in networking, to identify a port number within a TCP/IP communication regimen. May also be a nickname for Printer Port (q.v.). Port numbers Do 'grep IPR /etc/services' to see all the port numbers which IPM defines. The server port number is usually 6874, name "psmd". See: InfoPrint Manager Notification Server [notifyd 8200]; GUI ports; IPDS port; IPDS port; IPP port; LPD port; PCL server port; pdeventd; PostScript server; Server port port Ports For IPDS printing, IPM sends to printer port 5001. IPM defaults to reserving only 10 ports: if you want to define more than 10 server processes, you must use the 'pdinitports' utility to initialize more than 10 ports. Ref: "Infoprint Manager for AIX: Procedures": Preparing to create additional servers in a distributed environment See also: /etc/services; IPDS port number Post-print accounting Via user exit ainuxjobcompletion.c Accounting log: /var/psf/jobcompletion.log (q.v.) See also: accounting-exit PostScript driver considerations It is reasonable to expect one PostScript driver to work as well as another in generating jobs to submit to IPM for ps2afp transformation. However, experience has shown that results can vary dramatically. For example: The Infoprint 1585 printer is actually a Lexmark. You would then expect that use of the LEXPSNT3 Windows PostScript driver would be fine. However, though more rudimentary jobs transform fine with it, suspiciously many fail on image encoding defects (PostScript error: ioerror; Offending command: image). Switch to the Infoprint 2105ES PS PostScript driver and no such errors on the same jobs. PostScript can be a quagmire: one can see why Adobe invented PDF. PostScript End-of-Job marker Is Ctrl-D. The -c option of the 'ps2afp' transform can be used to concatenate multiple input files without putting a Ctrl-D character between the files. PostScript error See: "rip failed" PostScript error, on which page? The PostScript transform will report the type of PostScript error it encountered in the file - but give you no indication where in the file it was encountered. One way to narrow it down is to perform 'ps2afp -o /tmp/afp_out /var/pd//pdpr______' to produce an AFP output file, and then look in that file to see how far it got by doing: 'afpdmp /tmp/afp_out | grep PAG' which will show how many pages it successfully got through. This does not pinpoint the error, but helps a lot. PostScript error page, 2085/2105 Interpreter Settings, Print errors (No/Yes) Is in effect only when sending jobs directly to the printer, not through IPM. PostScript error logging Server error log /var/pd//error.log contains the gist of the problem, such as: "The PostScript error was: %%[ Error: configurationerror; Offending Command: setpagedevice ]%%". The actual transform error log, /var/psf/ps2afp/ps2afpd.log or /var/psf/ps2afp2/ps2afpd.log has detailed info. See also: rip failed PostScript file size The actual transform error log, /var/psf/ps2afp2/ps2afpd.log, has detailed info. In it, seek the file of interest by source files size, in bytes, and timestamp. The file size is reflected on the line, like: "received 272690 bytes in 1 seconds (266 Kb/sec)". PostScript fonts See: Fonts, PostScript PostScript interpreter, start '/usr/lpp/psf/bin/ps2afpd -C/usr/lpp/psf/ps2afp/ps2afpd.cfg' PostScript pages count The -v option of ps2afp reveals the number of AFP pages generated, as in: Wrote 8 pages of output type AFPDS IO1 (G4 MMR, 260), at approx 799.33 ppm PostScript printers AIX only: Generally speaking, non-AFP printers are usually PostScript printers, and are distinguished by having ____.dev entries in the server directory, so named like "psprinter1.dev". Such printers are also evidenced in the AIX directory /var/spool/lpd/stat/, with names like "_var_pd_oursys_psprinter1.dev". In Linux: There are no .dev files; but we can readily get a list of the IPM PostScript printers because they are in CUPS with an IPM_ name prefix: /usr/sbin/lpc status | egrep '^IPM_.+:$' PostScript printing advice Always specify exactly how the job should be printed, either in IPM attributes as part of an AIX or CUPS DSS, or within the PostScript of the job: do not take defaults - because they are seldom what you want. Printers often come configured from the vendor in a manner which will conserve paper and toner, as for example 3-up printing, at 2400 dpi, whereas what people generally expect a printer to do is print 1-up at 600 dpi. PostScript sample job /usr/lpp/psf/ps/tiger.ps See also: /usr/lpp/psf/ps/ PostScript server address Under printer Properties, the Customize tab has a "PostScript server address", used to define the network address of the host where a transform will be run for PostScript which is embedded in AFP. Default: 127.0.0.1 Attribute: postscript-server-address See also: PCL server address PostScript server port Under printer Properties, the Customize tab has a "PostScript server port", used to define the network address of the host where a transform will be run for PostScript which is embedded in AFP. Is defined in /usr/lpp/psf/ps2afp/ps2afpd.cfg as "port = 8251". Default: 8251 Attribute: postscript-server-port Errors: 0423-163 See also: PCL server port PostScript transform Is transformed to bitmaps...which tend to be large, which argues for 100 Mb ethernet for feeding the printer. PostScript transform is Adobe The PostScript transform software employed in Infoprint Manager is genuine Adobe, and is efficient. Contrast this with the "emulators" found in many PostScript printers, which can be quite inefficient. You may find, for example, that a job which quickly transforms in IPM may take a ridiculously long time to render in such a printer. (Printer makers cut costs by avoiding Adobe licensing fees, instead choosing some third party software to embed in their printers.) PostScript vs. PDF processing Experience shows that PostScript jobs tend to print faster than PDF. This should be expected, as PostScript files are processed linearly, from top to bottom, whereas processing has to hop around in PDF - where positioning happens from the bottom of the file. postscript-server-address AD attribute identifying the IP address of the host on which lives the daemon which transforms PostScript data which is embedded in an AFP data file. GUI label: PostScript server address Default: 127.0.0.1 (the local host) Note that this is *only* for the special case of PostScript embedded in AFP files: it is not to be confused with the PostScript transform ps2afpd daemon and its ps2afpi child which the ps2afp command uses. postscript-server-port AD attribute identifying the Port Number parameter of the host on which lives the daemon which transforms PostScript data which is embedded in an AFP data file. GUI label: PostScript server port Note that this is *only* for the special case of PostScript embedded in AFP files: it is not to be confused with the PostScript transform ps2afpd daemon and its ps2afpi child which the ps2afp command uses. PPD PostScript Printer Description: An ASCII file which provides device specific information to an application. A device might include any hardware or software that generates output by interpreting PostScript input. Device specific information can include finishing operations, paper dimensions, available fonts, the amount of memory, and paper or file processing options. PPDS Pro Printer Data Stream PPDs PostScript Printer Description files. CUPS wants you to add new ones to /usr/share/cups/model/. A collection of PPDs is installed in /usr/share/ppd/HP/ by the hpijs RPM package. PPFA Page Printer Formatting Aid: an IBM licensed program (Program Number 5688-190) that enables users of IBM Advanced Function Presentation (AFP) products to create their own formatting resources, called form definitions (Formdef) and page definitions (Pagedef); and to include previously created overlays in generating pages. PPFA is a cross system product that operates under: - AIX (Advanced Interactive Executive) Command: /usr/lpp/psf/bin/ppfa Source files: /usr/lpp/psf/ppfa/ Fileset: ipr.ppfa.rte Syntax: ppfa [-fpath.ext] [-ppath.ext] [-spath.ext] [-x] inputfile - MVS (Multiple Virtual Storage) - OS/400 (Operating System 400) - VM (Virtual Machine) - VSE (Virtual Storage Extended) Note that a command and its subcommands end with a semicolon. PPFA comments Are enclosed within: /* ... */ Beware that PPFA doesn't like Tab characters, and will flag them as an "invalid command": use spaces instead. ppm Pages per minute, printer rating. PPML Personalized Print Markup Language. PPML is an emerging XML-based print data stream that is divided into subsets. Infoprint Manager for AIX supports the Graphic Arts Conformance Subset for processing objects within the data stream that can consist of PostScript, PDF, TIFF, and JPEG objects. Transform: ppml2afp Ref: Procedures manual PPP IPM internals designation; refers to PSF Printing Process (?). Examples of PPPs: ainmain, ainsnaup, aintcpup. Presentation Services Programs A fancy name for printer drivers, where the output device is a printer. More generically, the software which drives an imaging device. previous-job-state Job atribute: Identifies the previous state of the job, such as "processing". A read-only attribute (not modifiable). GUI label: State See also: job-state-reasons; current-job-state prime-only Job/Default job attribute. Specifies whether or not this job should only be sent to the logical destination's priming-destination and not sent to this logical destination's associated-queue as a typical job would be. GUI Label: Only send to priming destination "Print As Image" PC printing choice, most often used when printing as PostScript yields an ioerror type error, OffendingCommand = image. This causes each page to print by means of a bitmap image instead of descriptive PostScript (vector imaging). This circumvents the defect in the originating application; but the file will be 5x - 8x larger; and bitmaps do print much slower, and cannot provide the smooth lines of vector imaging. Print As Image can also be used as a (crude) substitute for including all needed fonts in the PostScript file, to avoid any issues of font substitution on the print server in that it may not have all the fonts you request. Print As Image can also be useful where a defective PostScript driver is in effect which, for example, prints your document in mirror image form. Print As Image keeps the driver from being able to meddle with the PostScript (in that there is little PostScript left in the file). Print As Image can also get around an Out Of Memory printer problem. Print DataBase A term you'll find in various messages. Refers to the directory /var/pd//pdb/ . Print for someone else 'pdpr -x "job-owner=ThatSomeoneElse" -d LDname [-t Jobname] Filename' (Separate multiple -x attributes with a single space.) This will result in a job where the job-owner is as you specified in the command, and the job-originator is you. Note that you would usually specify the identity of the someone else as a simple username, and so the resulting job-owner attribute will not contain an '@' character, as in the typical network submission which causes the owner to appear as Username@Hostname. Note that the AIX lpr command has no provision for printing as someone else. Print job, submit Some ways: pdpr -P Example: /usr/lpp/pd/bin/pdpr -P prt1-ss tiger.ps Print job files In server directory /var/pd/ with names like "pdpr5y4paZ". Print Local File Infoprint 2085/2105 web interface selection, which is present if the IP address you are on is allowed to print that way, per admin restrictions. Print Management Facility Early mainframe software for creating Formdefs and Pagedefs. Print on both sides of paper This is called Duplexing (Duplex), as differentiated from Simplexing (Simplex), which is to print on only one side. See: Duplex Print selected page range To print a range of pages, only, from within a job, you can modify attribute page-select (GUI "Pages to process", under the Document Other tab). Keep in mind that if your system is adding header pages to the job, those will participate in the page range numbers. Note that IPM will perform a full transform of the job to AFP, and then only print the specified pages - which can entail an unexpected wait if it's a large, complex PostScript file. Print Services A high level identification in the Presentation Architecture Model for the software component which translates presentation documents (MO:DCA) into IPDS, for conveyance to and interaction with an output device. See also: PSF Print-On-Demand (POD) A feature of Infoprint Manager for AIX that includes the basic server option and support for variable data, imposition, the Infoprint Submit client, and the ditroff data stream. There is an accompanying Web Server component. When you install the Print-on-Demand Feature, the standard server environment is replaced by or extended with the basic printing environment. ----------------------------- The Submit Express component: Rather than this being a clean client-server application, it is a clumsy approach: On an InfoPrint Manager for AIX Version 4.3. system, NFS or other file sharing is required between workstations and the InfoPrint Manager server. It further requires that AIX Fast Connect be implemented, such that the Windows or Macintosh client can employ the SMB protocol to transfer jobs. print-qualities-supported AD attribute identifying the levels of print quality available on this actual destination. DSSes: AIX, BSD, CUPS Allowed values: draft; high; normal GUI label: Print qualities allowed What this does: In the absence of a print-quality attribute in the job, this AD attribute governs the resolution (dpi) of the printing, where experience shows that "normal" results in 300 dpi and "high" results in 600 dpi. print-quality LD attribute to specify the desired output quality of the printed document, as a relative value, rather than an absolute DPI. GUI label: Print quality DSS: AIX, BSD Allowed values: one of draft high normal The specified value is compared against the AD print-qualities-supported attrbute in scheduling the job. See also: default-printer-resolution; printer-resolutions-ready; printer-resolutions-supported PRINTDATA NO PPFA PRINTLINE subcommand which says to not print the corresponding line of data from the input data stream. You may instead print a Page Segment or Overlay. Printed jobs, be able to list For past printed jobs to be seen in the GUI, printing must be set up to retain jobs. Printelligence Software from Preo Software, as a partnership with Infoprint Solutions Company, around mid 2008. It is a web-based print management system that helps businesses measure and understand workgroup and distributed printing, as well as manage print in the organization. It can reduce print volume by encouraging employees to change print behavior and educating users on the cost of print and the environmental impact of their choices. The software adapts itself to each user's printing behavior and modifies the message it delivers, based on their habits, offering advice and alternatives for each print job. Printelligence adapts its responses to individual's behavior over time so that messaging stays fresh and appropriate. Printer, delete 'pddelete -c destination :' IPM prompts for confirmation in deleting the object, unless the environment variable PD_CONFIRM_DELETE is set "no". Printer, change attribute See: Actual destination Attributes, change Printer, disable 'pddisable ' Printer, enable 'pdenable ' Printer, rename IPM does not provide the ability to rename an existing printer instance: you can only define a replacement (via your set of coded pdcreate spec, or the GUI's Copy ability), then assign existing logical destinationa and then delete the original printer. Printer Attributes, list 'pdls -c destination -rall :' Note that the attributes do not identify the current running job in any way. Printer disabled Can occur logically when the printer Properties, "Load Balancing" tab, "Disable on job mismatch" is Yes. See: Disable on job mismatch Printer driver Printing software which describes the physical characteristics of a printer, plotter, or similar imaging peripheral device, used to convert graphics and text into device-specific data at the time of printing or plotting. Printer drivers, Infoprint In general, go to the Web site www.infoprintsolutionscompany.com and choose your platform. For convenience, here are some found via miscellaneous searches: PLATFORM PRINTER IBM DOC ID AIX 5.x 1xxx P4000538 Linux RH,Su 1xxx P4000452 Linux Debian 1xxx P4000451 Mac OS 8,9 2xxx P4000162 Mac OS X 2xxx P4000358 Mac OS 10.1 15xx,16xx P4000437 Mac OS 10.2 15xx,16xx P4000436 Mac OS 10.3 15xx,16xx P4000435 Windows drivers are too numerous to realistically track here. Printer error logs See: AD error logs Printer issues Will appear on AD attribute warning-message when the printer has problems. Sample value: "5010-832 Printer muggyhot is running but has an empty paper tray."|"5010-829 Printer muggyhot is running but is low on paper." Note the vertical bar separating the multiple simultaneous issues exhibited by the printer. (As commensurate with Warning, the corresponding GUI icon color is yellow.) Printer name See: destination-name Printer name instances Are create in two directories: /var/pd//pdb/suv_phy_printer /var/pddir/default_cell/printers/ Contains all destinations, actual and logical. Actual destinations are also named in directory /var/psf/, but there's also other stuff in that directory. See also: Physical destination files Printer Port In Windows, the interfact through which a printer communicates with the printer. You will become most familiar with these in Infoprint Select. Printer resolution requested On GUI "Document Print Quality" tab. No dpi value should be selected for an AIX DSS, as it is not meaningful, and will cause jobs to be red-flagged. See also: print-qualities-supported Printer sharing Only one print driver can have an open communication link with an IPDS printer at a time. Printer sharing can be accomplished, where necessary, by configuring the AD to drop the connection after a certain amount of time (destination-release-timer attribute) and having AD configured to wait long enough (connection-timeout) Ref: Introduction and Planning Guide manual See also: destination-release-timer; Release time (sec) Printer speed ranges September 2005 PTF U802540 changed the printer speed range definitions. The ranges had been: PPM Feature 0 - 49 Workgroup printers 50 - 89 Low speed printer engine 90 - 116 Medium speed printer engine 117+ High speed printer engine Now, the ranges are: PPM Feature 0 - 62 Workgroup printers 63 - 91 Low speed printer engine 92 - 116 Medium speed printer engine 117+ High speed printer engine Printer type, actual No attribute reports the actual printer model type. For example, if you define a printer instance as an Infoprint 1145 and an Infoprint 1585 is actually in place at the specified network address, IPM will not set any attribute which allows you to perceive that. To see what the model is, you have to make use of SNMP info in the GUI, or visit the printer's network-address Web page. Printer uptime If you have Net-SNMP installed on your system, you can invoke the command: snmpwalk -v1 -c public Netname system where Netname is the printer's network name or IP address. In the short output, you will see like: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (307561120) 35 days, 14:20:11.20 printer-end-sheet Attribute: Identifies the type of end sheet that this printer device uses. Possible values: accounting-log, blank, brief, full, job-ticket, none, _filename_, 64xx. (accounting-log is technically valid, but should not be used for sheet processing.) Ref: Procedures manual, "Modifying start sheets for 3170 physical printers" See also: accounting-exit; auxiliary-sheet-selection; printer-separator-sheet; printer-start-sheet printer-memory Attribute defining the amount of printer memory (in KB) for a PSF Command attached or PSF Other attached printer. Purpose and effect are undocumented. (Filed complaint with Publications 2002/07/22.) Possible values: 512 to 65535. Default: 1024 (KB = 1 MB) GUI: Printer properties, Configuration, "Memory (KBytes)". Comments: Boosting this value brings no performance improvement to PSF Command printing: jobs remain in "processing" state for a long time. printer-resolutions-ready AD attribute specifying the resolutions, in pels, which are available to service jobs sent to this destination. GUI label: Resolutions ready DSS: PSF, Print Optimizer (not AIX, BSD, or others) Allowed values: 240, 300, 480, 600 (note the absence of 1200) Note that, in the GUI, the AIX DSS's Appearance tab contains this attribute, despite documentation saying that it is unsupported for that DSS; and if a job includes default-printer-resolution, the job will fail on "resources not supported". Advice: If multiple values are present in this attribute, be sure to make the first instance be the preferred resolution, which will be used if no resolution is specified via the job's default-printer-resolution. See also: default-printer-resolution printer-resolutions-supported AD attribute specifying the resolution, in pels, at which the printer device can print PostScript and PCL jobs. GUI label: Resolutions allowed DSS: PSF, Infoprint 2000, Print Optimizer (not AIX, BSD, or others) Allowed values: 240, 300, 480, 600 (note the absence of 1200, though it is possible to type this value into into the definition via the GUI) Note that, in the GUI, the AIX DSS's Appearance tab contains this attribute, despite documentation saying that it is unsupported for that DSS; and if a job includes default-printer-resolution, the job will fail on "resources not supported". The presence of the attribute in an AIX DSS seemingly is to provide a means of forcing a resolution for all printing. See also: default-printer-resolution printer-separator-sheet Attribute: Identifies the type of separator sheet that this printer device uses. Possible values: accounting-log, blank, brief, full, job-ticket, none, _filename_, 64xx. (accounting-log is technically valid, but should not be used for sheet processing.) Ref: Procedures manual, "Modifying start sheets for 3170 physical printers" See also: accounting-exit; auxiliary-sheet-selection; printer-start-sheet; printer-end-sheet printer-start-sheet AD attribute: Identifies the type of start sheet that this printer device uses. GUI label: Start sheet Possible values: accounting-log, blank, brief, full, job-ticket, none, _filename_, 64xx. (accounting-log is technically valid, but should not be used for sheet processing.) Ref: Procedures manual, "Modifying start sheets for 3170 physical printers" See also: accounting-exit; auxiliary-sheet-selection; printer-end-sheet; printer-separator-sheet printer-timeout-period AD attribute, alias for destination-timeout-period (q.v.). Printers, discover at start-up Server property: snmp-discovery-during-startup (q.v.) Printers, names See: Printer name instances Printing Systems Division IBM's traditional printer hardware and software division, headquartered in Boulder, CO. See also: InfoPrint Solutions Company PRINTLINE PPFA: Traditional Pagedef command, for processing each line of data in the user-supplied job. More specifically, the PRINTLINE corresponds to the next logical line on the page, so if carriage control specifies "skip a line", the next PRINTLINE is skipped (as well as any FIELD or CONDITION processing associated with it). Each data line causes processing to step down the sequenct of PRINTLINEs in the Pagedef PAGEFORMAT (with possible skipping of PRINTLINEs): at the end of the PAGEFORMAT, processing returns to the first PRINTLINE in the PAGEFORMAT - processing does not continue with the next PAGEFORMAT (if any) in the Pagedef. Traditional PRINTLINE commands cannot be used where the more advanced Record Format LAYOUT command is used: the two are mutually exclusive. The "CHANNEL n" subcommand is used for data which contains carriage control characters, causing the data line to be processed by the PRINTLINE which has a CHANNEL coding which matches that of the data record, regardless of the current processing position in a series of PRINTLINE commands. So, if a data line appears with '1' in the first column, it will be processed by the PRINTLINE which contains "CHANNEL 1", regardless of where that PRINTLINE command appears in the sequence of PRINTLINEs. If using Printline to plant a page segment, remember that the segment is placed relative to the Position of the Printline - and so you may want to have a first Printline with Printdata No and a discardable data line so as to have the page segment absolutely positioned on the page. See also: CONDITION; FIELD Priority See: job-priority Priority of a job, change 'pdmod -c job -x 'job-priority=NN' :' .prn Windows file name extension for a print file created out of an application. It might actually be a PostScript file, having a .prn extension instead of the more conventional .ps; or it may even be a pure application file, such as a Microsoft Word document, which is certainly not viable as a print job. processing-time Job attribute reporting the amount of time that the job has been printing or transmitting on the output device. Observations indicate that this also includes transform time. If processing has completed, this value is the total amount of time needed to process the job. GUI label: Processing time Format: [HH:]MM Example: 0:19 IPM updates this attribute when a user queries the job (with the 'pdls' command (or GUI?)): that is, there is no point internally updating this progressing value unless someone is looking at it. IPM calculates the value by comparing the value of the started-printing-time job attribute value with the current time. Notes: Being in terms of hours and minutes, this value is a worthless measure, where most on-demand printing jobs are sub-minute. Instead, compute job processing time precisely from the accounting.log "Zulu" time fields, which have a wonderful resolution of hundredths of a second! (From the completed job, get the destinations-used value to scan the corresponding AD accounting log file for the JobID.) Related: estimated-processing-time; started-printing-time. See also: Accounting log Processes Under AIX, the IPM server is relatively robust about the loss of child processes, should you have to kill any. Product change requests Through your sales representative, you may request changes to the product. These have thus far been known as FITS requests, having IDs like MR0123456789. There are two basic request types that I know of: Suggestion and Required. My experience is that a Suggestion will go nowhere. We had one open for six years, which the vendor just ignored. If you want the request acted upon, submit it as Required. Production printer This is the term used to describe a high volume commercial printer, as in printing bills for hundreds of thousands of customers. The nature of such printing demands a no-jamming type of paper handling, which necessitates continuous form (Z-fold or large roll) paper. Printing speed is thus often measured in feet per minute. promotion-time Job attribute, established when Make Job First is done from the GUI. PROPTR Abbreviation for IBM Proprinter (q.v.). Protected attributes Managed via admin GUI, Server -> Properties, Other ps_server_timeout The ps2afp or ps2afpd configuration file variable for specifying the PostScipt/PDF interpreter (ps2afpi) remains in existence when it is idle (between jobs). Specify as: ps_server_timeout=NNNN where the value can be 1 - 9999 minutes, where 9999 means no limit. Default: 20 (minutes) ps2afp Transform command to work on PostScript and PDF input files, to generate AFP. 'ps2afp [-a OutputType] [-C ConfigurationFile] [-c] [-device"[plex], [inputw=(size,[type=x,color=y,weight=z] [inputw=(...]"] [-F FontMapFile[:FontMapFile...]] [-g PageRange] [-j ] [-l nnnn.nnnu] [-M ] [-o OutputFile] [-P ] [-p PageRange] [-pragma ps_x_origin nnnn.nnnu] [-pragma ps_y_origin nnnn.nnnu] [-q] [-r ] [-S ServerName] [-s ] [-v] [-w nnnn.nnnu] [-x nnnn.nnnu] [-y nnnn.nnnu] [InputFile ...]' where: -a Specifies the type of AFP data stream to generate. Defaults to IO1_G4. An undocumented choice is "none", to tell the software to not bother generating any output: is faster than '-o /dev/null' where the transform is merely for content testing and a page count (-v). -c Concatenates multiple input files without putting a Ctrl-D (end of job) character between the files. -v Undocumented option to provide some extra detail, normally found only in the daemon logs. The most significant value reported is the number of AFP pages generated, as in: Wrote 8 pages of output type AFPDS IO1 (G4 MMR, 260), at approx 799.33 ppm The IPM server must be up for this command to run (meaning the server named on -S, if specified, else the local system server), and ps2afpd must be present. Messages are sent to Stderr (not Stdout). The InputFile may be provided through Stdin, in which case you need to code like "-datatype ps" to explicitly tell the command what type of file is involved (as there is no filename+extension for it to inspect); and you can code "-" (lone hyphen) at the end of the command line to emphasize that the input is from Stdin, or not include such a trailing hyphen. Notes: - There is no opportunity to specify a Formdef: there is no option for one, either as a command line option or a config file line. See notes under "Form Definition used" for how processing occurs when a Formdef is not specified. If a Formdef is specified in job submission or via Document Defaults will be used at print time, showing up on the ainbe command line as FORMDEF=______, where that ainbe processing which generates IPDS from the AFP pulls in any such named library code. - The file must be wholly PostScript or PDF, but not a mixture. - Specifying -r600 may reveal PostScript errors that -r300 will not. Caution: Including -w and -l can cause the image not to appear, with a small resultant afp file. See notes under ps2afpi for reasons for delay seen after invocation. Logs: /var/psf/ps2afp/ps2afpd.log /var/psf/ps2afp2/ps2afpd.log (q.v.) See also: pdf2afp ps2afp and paper size In ps2afp PostScript transformation to AFP it is pretty much standard that page width (-w invocation option) is set to 8.5i (8-1/2") and length (-l invocation option) is set to 11i (11") for the height of the paper. This is what is termed Letter size. But: this is a size parochial to the United States and Canada. In the rest of the world, Letter size is A4. In AFP terms 8.5i x 11i results in a MO:DCA-P PGD record having an XpgSize (Page extent for the X axis = 12212 units (8.48 inch) and YpgSize (Page extent for the Y axis = 15840 units (11.00 inch). It is important to understand that the dimensions specified in the ps2afp operation fully control the AFP image size. A given PostScript file may be internally architected for Legal size paper, but running ps2afp with 8.5x11 specs will result in Letter size imaging. ps2afp and PJL frontal lines The ps2afp command does *not* simply skip over the PJL commands which a PostScript driver may add to the front of a PostScript job: it tries to basically process them, as via readline. ps2afp configuration /usr/lpp/psf/ps2afp/ps2afp.cfg /var/psf/ps2afp/UserInit Ref: Procedures manual, chapter on "Working with Infoprint transform programs" ps2afp output per PostScript factors Does the varying of PostScript instructions within the job file change the AFP that is generated by a standard ps2afp invocation? No. If you operate on the same PS file via 'ps2afp -o /tmp/Output.afp Input.ps', requesting simplex output via line << /Duplex false >> setpagedevice and then change that to duplex via << /Duplex true >> setpagedevice the generated AFP is identical, containing the same number of AFP pages (no blank pages between imaged pages, in simplex). Why no difference? Because the objective is to print the job in AFP, where an external Formdef controls plex and image position on the page. You thus cannot use an ordinary ps2afp invocation as a means of discerning if a PS file is simplex or duplex. But: There is a relatively obscure means of determining this... Invoke the transform like: 'ps2afp -o /tmp/Output.afp -device plex Input.ps' This will cause IPM to generate the AFP with a frontal collection of Formdefs which may be used later in the job; and in response to the PS plex specification, the transform will generate an IMM (Invoke Medium Map) directive into the AFP specifying a particular Formdef Copygroup, as in: IMM: media map name = 'D1000000' where the first letter is D for duplex, S for simplex, and T for tumble duplex. (You can use 'afpdmp -d' to inspect the AFP file.) ps2afp.cfg PostScript transform command configuration file, which may be located in the current directory or in IPM's /usr/lpp/psf/ps2afp/ directory, whose use overrides the ultimate ps2afpd.cfg daemon config file. Ref: Reference manual, ps2afp command ps2afpd Transform daemon to work on PostScript and PDF. The ps2afpd daemon manages the PostScript interpreter portion of the ps2afp and pdf2afp transforms: ps2afpi. Started by: /usr/lpp/pd/bin/startsrv. Note that user root launches ps2afpd, which by itself changes to run under user 'daemon'. Its directory may be found to be drwxrwsr-x 16 root printq but being owned by root doesn't make sense, as that prevents 'daemon' from writing to the directory, where the directory content then would have to be pre-established, with the files in it being owned by 'daemon'. Note that when a ps2afpd is started and its directory is writable by daemon, it will itself populate the directory with what it needs to operate. Observationally, ps2afpd is seen to use little CPU time. Important: This daemon, like all transform daemons, run as Unix user "daemon" rather than "root"; and their /var/psf/*2afp/* files must also be owned by "daemon" so that the transform daemon can read and write them - particularly the Pipe files. Further, the Unix Resource Limits (AIX /etc/security/limits file, and shell 'limit' command choices) must allow the file and memory sizes needed for production. Restarting the daemon: The Reference manual claims that doing 'ps2afpd' will "restart the ps2afpd daemon with the default configuration file". False! It cannot, because the port number is occupied by the running daemon. That *starts* the daemon, once the running one has been taken down. When the daemon starts, it parses and evaluates its ps2afpd.cfg file. If any elements in that file are invalid, the daemon will not start. It is documented as recording the erroneous cfg content, but does not: the 0423-160 msg is written to the terminal, if any. Thus, you must invoke it manually to see what's going on, when it won't start. And that doesn't point out the content problem. (You need to make backup files whenever changes are made, and this will help identify what's wrong.) Problem Handling: If the process seems to be unproductively looping, doing 'kill -TERM ' has been seen to cause that process to disappear, to be replaced by another ps2afpd. Ref: Reference manual See also: daemon; pcl2afpd ps2afpd PID 'ps -flu daemon | grep ps2afpd' (There is no known file in IPM's directories which contains the daemon's PID.) ps2afpd.cfg (/usr/lpp/psf/ps2afp/ps2afpd.cfg) The default PostScript printing file configuration file used by the ps2afpd daemon. The daemon will notice when this config file is changed, and will adopt its new values. Review its specs, particularly pcl_resolution, and device_controls for duplex printing. (Note that uncommenting "device_controls" has the effect of causing the transform to generate an inline Resource Group named INLINERS ahead of the AFP for the document itself, allowing document processing to reference Medium Map names to effect paper tray selection, stacker offsetting, etc.) The device_controls settings are reflected in the ps2afpd.log, on "deviceControls" lines. Ref: Reference manual; Procedures manual, chapter "Working with Infoprint transform programs" ps2afpd.log See: /var/psf/ps2afp/ps2afpd.log ps2afpi /usr/lpp/psf/bin/ps2afpi The PostScript/PDF-to-AFP interpreter, as specified in the ps2afpd.cfg file. It is automatically brought up by the ps2afp daemon (ps2afpd), and brought down by it in accordance with the ps2afp -s option or ps_server_timeout configuration file value, whose default is 20 minutes. (The absence of ps2afpi after a period of no activity is why the next ps2afp takes longer than usual.) How it works: An ainbe process will be shepherding a job, and under that process a RIP-appropriate transform process will run, such as ps2afp or pdf2afp. The ps2afpi processs does the actual transform work for the ps2afp process. Unfortunately, a 'ps' reveals no linkage between the two, by parentage or runtime operands, so you have to guess which job is being RIPed. The transform is serial: one job at a time. It does not parallelize. So, if the first job is a whopper, it utterly monopolizes IPM, and nothing else goes through. If you do ls -alt /var/pd/ | grep xfm it will show the active transform files, with only one being written at a time. The interpreter will do as many jobs as it can, up to the "Maximum concurrent jobs" value for all ADs, so if the actual printing is slow, you will have a stack of AFP files ready to go. Looping: A rare, mis-structured PostScript job or incomplete PDF will cause this interpreter to loop. How best to deal with it: - Determine the problem job by inspecting the end of the /var/psf/ps2afp/ps2afpd.log file. - Try a Pause/Stop Job (red traffic light in the GUI). If that doesn't work, what I have found to work best is to issue a simple 'kill ' on the ps2afpi process, which has been seen to allow ps2afpd to simply spawn a new ps2afpi, and IPM processing will continue without outage. The job that the ps2afpi was processing may go into a held state, or be thrown into the Retained Jobs area as "cancelled by operator". In our environment, when the operator does a 'kill ' on an active ps2afpi process, the job ends up with job-message-from-administrator = "PostScript error: RIP failed." See also: ps_server_timeout ps2afpi PID 'ps -flu daemon | grep ps2afpi' (There is no known file in IPM's directories which contains the daemon's PID.) ps2afpi problem handling The ps2afpi process can doggedly try to transform a bad file, such as an incomplete PDF, per its ps_server_timeout configuration file value. In such a situation it will effectively be looping, and will do so for a long time, preventing the printing of any other PostScript or PDF jobs. A looping situation can be handled by doing a simple 'kill' command on the process, which should cause it to terminate and, if the parent ps2afpd process survives the event, ps2afpi will be re-spawned in the presence of further jobs to process. But: it is often the case that the ps2afpd process will die along with the ps2afpi, whereupon all jobs that had been in a ps2afp client state will go red in the GUI, and have to be un-held after ps2afpd is restarted. ps2afpi: running more than one It is both legal and technically possible to run more than one PostScript to AFP interpreter on an IPM system. You may want to do this where you have a lot of incoming jobs to deal with, or where one queue tends to have "whopper" jobs which would monopolize a single ps2afpi process. It is feasible to have more than one where you have a multi-processor computer system where at least one processor is essentially unused (given the propensity of the ps2afpi process to consume all of one processor). If you don't have such extra capacity, running a second PostScript interpreter may impair your IPM system, where the pdserver process needs a goodly amount of CPU power to handle incoming jobs and manage printing. Set it up by establishing a runtime directory for the added ps2afpd + ps2afpi set, which user 'daemon' can write into. Copy the /usr/lpp/psf/ps2afp/ps2afpd.cfg to your own designated location, and edit the copy to: - Specify a private port number. IPM's standard daemons run on ports 8251 and 8252, such that starting your new series at 8260 makes sense. - Define the work_directory to be the one you set up, with log_file being within that. - Update the notify parameter as appropriate. - All other keywords in the file can likely be left as-is. Set up an appropriate mechanism to start ps2afpd, with its -C option pointing at your tailored configuration file. You likely don't want to modify the vendor's startsrv script: instead, add the ps2afpd start-up to your script which runs /etc/rc.pd (and thus startsrv). In that your ps2afpd instance would be supplementing the standard ps2afpd, starting the second ps2afpd a bit after the primary should be fine. PSAF Print Service Access Facility, an IBM mainframe software product. Pscript5 The PostScript printer driver (pscript5.dll) for Windows 2000 and later... the Pscript renderer, which handles text output and renders images, then sends the text and image data to the print spooler. Installing some printing-related apps may install a PostScript driver. For example, installing Acrobat 5.0.5 installs Pscript5.2 for Windows 2000. PSD IBM's Printing Systems Division. The IBM Printing Systems Company is based in Boulder, Colorado. PSF IBM Print Services Facility, a stand-alone predecessor to IPM and embedded in IPM: within IPM it performs the transforms, from application-oriented, device-independent AFPDS to device-oriented IPDS. Simply put, PSF takes AFP and feeds it to IPDS devices (printers). PSF's only data stream output is IPDS. PSF is designed to work with its native language, AFPDS, but will accommodate legacy line data (line printer data). In addition to recognizing the usual carriage control characters in the first position of each print record, PSF will recognize additional codes which identify Structured Field Records, as for Formdef and Pagedef selection. In printing, the PSF process shepherds the print job until it completes on the printer, staying with the print job until it is stacked. PSF backend See: ainbe PSF Command printer A PSF command attachment type actual destination requeues jobs to a PCL (or PPDS) printer queue - which really means that the jobs come out of IPM as PCL and, via some command you choose, can go into a queue somewhere. The command will be invoked as a filter, so it must be able to receive its input via Stdin when the input data is not specified as an invocation file name. (Note that PSF Command is not a DSS type.) IPM considers the job complete after delivering it to queue for this device. (Note that, because of this forwarding to another place, an 'lpq' command will not reveal the print jobs.) In this arrangement, IPM engages in only cursory communication with the printer: accurate job status and completion information cannot be obtained. Input data, regardless of type, is transformed into AFP, and then into PCL. That is, even incoming PCL is transformed into AFP and then back into PCL. This has the advantage of providing information such as page count. Unlike the PSF Other method, you cannot suppress transformation. Characteristics summary: - Data stream is always transformed. - Output is PCL. - Job is handed to an external queuer. - Performance is slow: generating PCL from AFP is very consumptive. - The printer-resident PCL fonts go to waste, as IPM is sending full bitmap page images. Created under GUI: Printer -> Create -> PSF -> Command Allows specification of: Name (required) Server (required) Model (required) SNMP TCP/IP address Printer command (required) Data Stream (PCL4, PCL5, PCL5C, PPDS) If you enable the Type column in the GUI's Printers list you will see the type as "PSF Command". The AIX printing command may be: enq -P____ enq -P____ -h -#____ lpr -P____ qprt -P____ See also: ain3dpds PSF Command AD, create by command 'pdcreate -x "destination-realization=actual attachment-type=command destination-model=Infoprint2085 destination-tcpip-internet-address=___ destination-command='enq -P___' destination-data-stream=pcl6 associated-queue=____" :' PSF Other printer IPM AIX method. Full name: PSF Other-driver. Transforms all incoming data streams into PCL (PCL4, PCL5, PCL5C, or PPDS), and sends them on to the printer using an AIX backend program. As such, is similar to an AIX DSS. Transformation may be suppressed via the document-formats-ripped-at-destination actual destination attribute, in which you can specify particular document-formats (such as PostScript and PCL), as in the case of an input data stream being PCL and the printer natively handling PCL, letting the RIPping occur in the printer only. Normally, input data, regardless of type, is transformed into AFP, and then into PCL. That is, even incoming PCL is transformed into AFP and then back into PCL. In the 2085 Job Status display, the job appears like: User-Host Name: root-aixsys1 Job Name: hspr1oth.5557701105.dirout2 | | | IPM Global ID AD name Characteristics summary: - Data stream is usually transformed. - Output is PCL. - Job is sent by IPM via AIX backend. - Processing seems to be synchronous: with multiple jobs, one is seen in "processing" state while all the others linger in "ripping" state. - Performance is slow: generating PCL from AFP is very consumptive. - The printer-resident PCL fonts go to waste, as IPM is sending full bitmap page images. Created under GUI: Printer -> Create -> TCP/IP Allows specification of: Name (required) Server (required) Model (required) SNMP TCP/IP address Device or Windows port name Printer command (required) Data stream (PCL4, PCL5, PCL5C, PPDS) See also: ain3dpds; pioibmdpm PSF TCP/IP printer A PSF TCP/IP attachment type actual destination drives an IPDS printer that is connected to the network. When sending IPDS to a printer, the PSF DSS uses the IBM Print Services Facility printing subsystem to communicate with the output devices. This subsystem provides excellent two way communication to the printer so Infoprint Manager has the best control and information regarding the job. Created under GUI: Printer -> Create -> TCP/IP Allows specification of: Name Server Model TCP/IP address TCP/IP port Default Formdef: F1A10111 If you enable the Type column in the GUI's Printers list you will see the type as "PSF TCP/IP". PSF Trace Performed per IBM IPM Support. To activate the PSF trace: pdshutdown -cp : smitty pd_psf_prt_sel_error_trace_options - Change ACTIVATE trace to yes - Change GROUP to trace to standard - Press Enter pdenable : psf-tray-characteristics The paper tray characteristics for an AD. GUI label: Media ready Supposedly adjusted automatically when SNMP is active; but experience shows that it may not self-adjust, as with an Infoprint 2105 printer. Sub-attributes and their GUI labels: input-tray Input tray media-loaded Media ready job-bin-number Bin number See also: media-ready psfapi.error.log You mean: /var/psf//error.log psfapid /usr/lpp/psf/bin/psfapid Undocumented command which is found running in an IPM system as a daemon; parent process is init rather than an IPM parent. Is apparently the PSF API daemon, which services PSF API calls. Talks to ainbe via TCP. Started by /usr/lpp/pd/bin/startsrv. It launches by a parent process forking a child; and if the child successfully starts, the parent process exits, leaving the child as the daemon, running as a child of init. Note that the module is programmed with several sleeps, so it can take a minute or so to start. To see usage, invoke like: psfapid \? which then outputs: usage: /usr/lpp/psf/bin/psfapid -c -h -l -s -p where: -c The psfctl command file name (/usr/lpp/psf/bin/psfctl) -h Home dir name (.) -l Log file name (/var/psf/psfapi.log) -s State file name (/var/psf/psfapi.data) -p Toggle persistence (1) ( stands for "a string") During start-up, it seems to look for an available (unused) privileged port number (0 - 1023), which it associates with a socket for TCP and UDP. So how do ainbe and other IPM processes know what port psfapid is at, so as to be able to communicate with it? Because psfapid uses portmap, where it is RPC registered like: program vers proto port service -61440 1 udp 651 -61440 1 tcp 651 which in source form is: PSFAPI, PSFAPI_VERS_1, udp PSFAPI, PSFAPI_VERS_1, tcp where: -61440 = unsigned_int 4294905856; The port number is usually a privileged port number, in range 0 - 1023. Its basic set of file descriptors are like: FD TYPE NODE NAME cwd VDIR 116883 /tmp 0r VCHR 4206 /dev/null 20u IPv4 UDP *:803 21u IPv4 TCP *:802 (LISTEN) Note that as of PTF 9, psfapid is using the bindresvport() system call to dynamically bind its socket to a reserved (privileged) port number. This is an iffy technique, and can cause psfapid to fail to run where IPM is sharing a computer with other processing which is consuming reserved port numbers - even if there are plenty of unused ports in the 0 - 1023 range. Transient TCP processes will show up as file descriptors 1 - 19. 'rpcinfo -m' shows it receiving a lot of calls, indicating that PSF API calls are heavily used in Infoprint Manager print job processing. (Note that a negative value for an RPC program number is weird, and makes it impossible to deregister the program via the -d option of the rpcinfo command, in that the cmd insists that the minus sign means that the token is an option.) Clearly, then, psfapid is an RPC program. Performance: Despite being written in C, the module issues commands (ps, grep) to gather information - a crude approach to systems programming, which results in needless delay and added overhead, particularly when sharing a system where a lot of processes are present. Signals: The process will end if a simple 'kill' command is performed on it. Exit codes: Always exits with a 0 status code - even if it fails to start. Files: /var/psf/psfapi.data /usr/lpp/psf/bin/psfctl Logs: /var/psf/psfapi.error.log Tracing: If you must create a trace, create file /tmp/psfapi.debug.trigger. This will cause tracing to be in effect immediately. The trace info is written to /var/psf/psfapi.log. However: No tracing will occur until the pdserver initiates PSF operations which require interaction with this daemon - which in turn means that psfapid must be healthy and running for tracing to occur... which means that there can be no tracing if psfapid won't run to the point of spawning a healthy child. (When I submitted a PMR about psfapid unable to start on a shared system, the developer nevertheless requested this trace - which was a waste of time in that, obviously, no tracing could occur. Duh.) Notes: This process may linger after a pdserver shutdown - and may impede pdserver restart. It is best to kill it off after the pdserver process is down. Problems: If you see multiple psfapid processes piling up, that can be due to /var/psf/ running out of space. psfin The Input Manager. /usr/lpp/psf/bin/psfin Creates and manages the segment files (/var/psf/segment/) and the corresponding segment list files (/var/psf/seglist/) as jobs are transformed into AFP. For example, the Postscript transform pipes it output as a real-time stream to the Input Manager, which carves up the incoming stream into segments (like a candy var extruder), thus allowing early pieces of the output to start going to the printer long before the full job has been transformed. The Input Manager deletes the files from the aforementioned directories when space is needed. psfin is a transient process: you will see many occurrences in the AIX process accounting records. Msgs: 0423-923; 0424-179 Ref: Configuration and Tuning Guide See also: /var/psf/ps2afp/.PXIin psfstat Command for displaying information about Infoprint Destinations and PSF Direct receivers. Ref: PSF Direct Network Configuration Guide for System/370; psfstat man page. .psg Filename extension for a Page Segment. PSM IBM Printing System Manager, a predecessor to IPM. http://publib.boulder.ibm.com/prsys/ pdfs/54439622.pdf IPM seems to use some PSM software in accepting jobs via the LPD Gateway, as when there are errors, mail files will appear in /tmp containing... Subject: Error message from PSM psmd This is the pdserver process standard port number 6874. IBM site material refers to psmd as "command server". The moniker would seem to indicate Print Services Monitor daemon. Seen to be a TCP port through which Windows PCs submit jobs via Infoprint Select. Tip: If you use the command 'lsof -p | grep psmd' you can get a list of the PCs currently in session with the IPM server. See: 6874 PTF, what changed In the past, at least, each IPM service update was explained by an APAR, named like: "IY11859 - OCT2000 INFOPRINT MANAGER V320 SERVICE UPDATE". PTF installation command See: ip_update PTF levels, installed, AIX For the basic product, enter command: lslpp -ql ipr.\* PTF levels for IPM Found on the Ricoh ISC site under "InfoPrint Manager, InfoPrint Manager for AIX, InfoPrint Manager for Windows" "Downloads". PTF levels for IPM 4.1.0 This information is available in the IBM site Technote "Infoprint Manager for AIX 4.1 Service Record" (P1000567). U483882 (2002 August APAR IY32135) * PTF1 AIX fileset 4.1.0.20 U484268 (2002 November APAR IY33202) * PU1 GUI Help->About date:11/9/02 AIX fileset 4.1.0.40 U486582 (2003 April APAR IY38416) * PTF2 GUI Help->About date: 3/11/03 AIX fileset 4.1.0.60 U483536 (2003 December APAR IY31515) PU2 AIX fileset 4.1.0.100 U496818 (2004 March APAR IY51725) PTF3 AIX fileset 4.1.0.125 U496819 (2004 July APAR IY51727) PU3 AIX fileset 4.1.0.150 U499600 (2004 November APAR IY59100) PTF4 AIX fileset 4.1.0.175 U800782 (2005 March APAR IY63876) PTF5 AIX fileset 4.1.0.200 U802553 (2005 September APAR IY68265) PTF6 AIX fileset 4.1.0.225 (* denotes PTFs with which the author has had experience) See also: Common Clients CD, under REFERENCES. PTF levels for IPM 4.2.0 This information is available in the IBM site Technote P1000700: "Infoprint Manager for AIX Service Summary for Versions 4.1 and 4.2" - but beware IBM falling seriously behind in keeping this Technote up to date. Found on the Ricoh ISC site as URL http://www.infoprintsolutionscompany.com /internet/dcfdata.nsf/vwWeb/P1000700 but is incomplete. Also, IBM Document ID TD104387 provides a simple list of available PTFs. U802055 (2005 March APAR IY66626) PU1 AIX fileset 4.2.0.25 Added support for AIX 5.3. U802540 (2005 September APAR IY68181) PU2 AIX fileset 4.2.0.50 U805617 (2005 October APAR IY76448) PTF2A AIX fileset 4.2.0.75 U805636 (2005 December APAR IY76544) PTF3 AIX fileset 4.2.0.100 GUI Build Date: 11/15/06 U806676 (2006 June APAR IY80442) PTF4 AIX fileset 4.2.0.125 Downloadable files Ref#: P4000508 U807769 (2006 December APAR IY84547) PTF5 AIX fileset 4.2.0.150 Common Clients GUI Build Date: 11/15/06 (Was this PTF withdrawn? There is a conspicuous gap in Technote P1000700.) U810963 (2007 January APAR IY93459) PTF5A AIX fileset 4.2.0.155 IBM document number: P4000552 U810787 (2007 April APAR IY92442) PTF6 AIX fileset 4.2.0.175 Downloadable files Ref#: ??? U811589 (2007 November APAR IY97356) PU7 (PTF7) AIX fileset 4.2.0.200 Downloadable files Ref#: ??? Infoprint 2190/2205/2235 support. For Windows: Java: IBM Runtime Environment for Windows, Java 2, Version 1.4.2 and Version 5.0. U815456 (2008 March APAR IZ09721) PTF8 AIX fileset 4.2.0.225 IBM document number: P4000745 U816488 2008-06-13 See IBM doc P4000748 and TD104671 PTF 9 AIX fileset 4.2.0.250 InfoPrint EMP156 printer support. Its IPS works with Windows 7, 32-bit. U823037 2009/02/20 (Windows UO00865) PTF 10 AIX fileset 4.2.0.275 See IBM doc P4000847 (misidentified as P4000857 by IBM) U824679 2009/04/24 PTF 11 AIX fileset 4.2.0.300 See IBM doc P4000872 U829045 2009/11/26 (Windows UO00965) PTF 12? AIX fileset 4.2.0.325 See IBM doc P4001004 For Windows: Java: IBM Runtime Environment for Windows, Java 2, Version 1.4.1. U833201 2010/05 (Windows UO01046) PTF 13 AIX fileset 4.2.0.350 See IBM doc P4001027 The level of a Common Clients disc can be determined by looking at the aix.id file, which will contain like: DISC:CommonClient VERSION:4.2.0 PACKAGE:20070411:1245 AIX_APAR:IY92442 PTF levels for IPM 4.3 The PTFs continue to be served by the IBM site, rather than IPSC. UO00879 AIX/UO00880 Windows (2009/04) PTF 1 IPSC document P4000853 UO00898 AIX/UO00899 Windows (2009/07) PTF 2 IPSC document P4000882 UO00917 AIX/UO00918 Windows (2009/09/14) PTF 3 IBM document number: P4000933 IPSC document P4000933 UO00966 AIX/UO00967 Windows (2009/11/16) PTF 4 IBM document number: P4000968 IPSC document P4000968 UO00979 AIX, UO00980 Windows(2010/03/26) PTF 5 IBM document number: P4001009 IPSC document P4001009 64-bit Infoprint Select, at last! U100003 AIX, U100004 Win (2010/09) PTF 6 IPSC document 0IHP3036 U100005 AIX, U100006 Windows (2010/11) PTF 7 IPSC document 0J3P0246 U110001 AIX/U110002 Windows (2011/02) PTF 8 IPSC document 1AYN2413 U110003 AIX/U110004 Windows (2011/04) PTF 9 IPSC document 1C3L1208 U110005 AIX/U110006 Windows (2011/06) PTF 10 IPSC document 1FFK0112 PTOCA Presentation Text Object Content Architecture, an IBM architecture outside of AFP. .PXIin In the /var/psf/ps2afp/ps2afpd.log, appears on line: inputFileName .PXIin See: /var/psf/ps2afp/.PXIin Queue In general, a line or list of items (jobs) waiting for processing. In Infoprint Manager, a queue is an object that manages a collection of jobs that are waiting to print. A queue receives jobs from one or more logical destinations and sends jobs to one or more actual destinations. The queue in Infoprint Manager contains the mass of jobs waiting to print, and thus is the area that the print operator will devote most attention to. Operational actions that can be taken on a queue: Pause (red traffic signal) Allows submission to continue, but jobs will not be processed - will not transform or print. Resume (green traffic signal) Back to normal. There is no queue-level action to cause jobs to be refused: that can only be performed at the LD level, by disabling the LD. In adding printers or venues to IPM, you will likely need to define a queue, with the following considerations: - Commonality: Printers and venues which have a log in common should be defined within the same queue. - Security: The ability to restrict who can do what is readily fenced via queue boundaries. - Transference: The ability to transfer jobs from one printer to another is facilitated by having all such printing within a queue. Queue, actual destinations, list 'pdls -c queue : -r actual-destinations-assigned' Returns: : actual-destinations-assigned = LD1 LD2 LD3 ... where the ADs are vertically lined up, one per line, in no particular order. This is a very inexpensive query: the results return almost instantly. Queue, jobs in, list Use the pdq command, with the -U option, with one of the destinations in that queue as an argument. Doing like: pdq -U -d duplexd will produce a nice table of jobs. Doing like: pdq -U duplexd ${HOST}: will report each job individually, in a rather messy fashion. Queue, logical destinations, list 'pdls -c queue : -r logical-destinations-assigned' Returns: : logical-destinations-assigned = LD1 LD2 LD3 ... where the LDs are vertically lined up, one per line, in no particular order. This is a very inexpensive query: the results return almost instantly. Queue, stop printing Do a pause (pdpause) on the queue: jobs can continue to be submitted, but will not transform or print. The queue pause will survive across pdserver restarts. Later, do a resume (pdresume) on the queue, at which time any jobs submitted during the pause time will transform. Queue attribute, alter 'pdset -c queue -x "Attribute=Value" :' Queue definition files In /var/pddir/default_cell/queues/ Queue name, in IPM Length: Essentially unlimited. Are case-sensitive. Queue names Obtain via command: pdls -c server -r queues-supported -g : or pdls -c queue -g : or pdls -c queue -r queue-name : Physically, the queue names are in directory /var/pd//pdb/queue/ wherein there is a file for each queue, each being an attributes repository in OIDs form. Queue names, in Infoprint 2085/2105 PASS To pass the data through without any treatment. For: PCL, PostScript, and PDF jobs; ASCII text files whose lines end with Carriage Return + Line Feed. TEXT ASCII files whose lines end with Unix newline (Line Feed char). (..) Any arbitrary queue name. Manage via printer web page: Network Settings: TCP/IP Printing Details: LPD Settings queue-assigned Job attribute identifying the queue to which the job was assigned. GUI label: Queue The value is filled in during the time that the job is in the input queue, but is null thereafter, as when the job is then in the Retained Jobs area. OID: 1.2.840.113554.1.1.3.1.229 Queues See: Queue names qstring As in PPFA manual, a quoted string, consisting of alphameric characters, enclosed in single quotes, like: 'A103QX'. Maximum length depends upon context. Quoted name As in PPFA manual, a name consisting of alphameric characters, enclosed in single quotes, like: 'A103QX'. Raster Image Processor (RIP) A processor in which a PostScript data stream is converted into dot patterns that are transferred to the final print medium. Infoprint uses an Adobe RIP to convert PostScript to IPDS for such printers as the Infoprint 4000 and Infoprint 60. "ready with warning" GUI Status column value which usually reflects a condition such as an open or empty paper tray Ream 500 sheets of paper. Record Format processing PPFA: The more modern, advanced (vs. Traditional processing) method, involving a 10-char record ID at the front of each data line (as opposed to the single "carriage control" character at the head of Traditional data. You cannot mix record format LAYOUT and traditional PRINTLINE commands in the page definition. And you cannot use record format processing on ordinary ASCII print files. "Record job messages" GUI: AD Customize tab field. Attr: dss-job-message-disposition (q.v.) Record ID In PPFA record formatting function: They occupy the first 10 characters of each line data record, and control the layout type that is selected for each given record. These 10 characters are reserved for record ids and are not included as part of a defined field or conditional area. Red The color red is used in an Infoprint GUI to flag a problem item. A print job, for example, may require a type of paper not currently available in the printer: that is, the job was accepted by Infoprint because the printer is capable of handling that paper type, but cannot be printed until that paper is loaded. Red icon See explanation under Red. Find occurrences in the IBM database by searching on "turns red" and similar variants. Release job 'pdmod -x "job-hold=false" :' See also: Hold job Release time (sec) GUI name for the attribute destination-release-timer (q.v.) relX, relY PPFA: Relative position for a segment or object. Example: -1 IN rembak AIX remote backend, for sending print jobs to a remote system's print queue, usually BSD. /usr/lib/lpd/rembak This is asynchronous driving, typically used where the remote printer incoporates its own LPD. The remote system takes the jobs as quickly as the originating system can send them, for subsequent printing. Contrast this with the various pio* backends, which synchronously drive a printer, shepherding the job through the printing process. An alternative to rembak is LPRng's lpr command, which allows direct sending of print jobs, without a local lpd, via an 'lpr -Pqueuename@hostname' construct. Contrast with: pioinfo remote_install Installation CD/DVD command for performing a non-interactive install (rather than invoking 'setup'). remote-queue Indicates whether the backend program sends data to a remote print queue rather than controlling this AIX actual destination directly. Specify True/Yes if the AD is reached directly or indirectly via rembak. GUI Label: Use remote print queue See also: "Use remote print queue" REPEAT PPFA: PRINTLINE subcommand; commonly used control in PPFA text formatting to specify the total number of PRINTLINEs in a logical page.encountered in the data records. REPLACE PPFA Formdef command: Specifies whether this form definition is to replace an existing one with the same resource name in the library. YES Replace an existing form definition of the same name in the library if there is one. If a form definition with the same name does not exist in the library, then store this form definition. NO Do not replace an existing form definition of the same name. If a form definition with the same name does not exist in the library, then store this form definition. This is the default. Report job completed when printed See: wait-for-job-completion Reprint a job Reprinting a job is problematic: Realize that a submitted job goes through Job and Document Defaults processing, to have certain destination-specific attributes attached to it. This makes it problematic to consider moving the job to a different LD. Additionally, reprinting the job through its original LD has also been found to be problematic in it not going through the transforms processing you expect - reason unknown. The IPM terminology for such a task is "resubmit": you'll find that in the manuals. Reprinted jobs are found to be logged in /var/psf/ps2afp2/ps2afpd.log instead of /var/psf/ps2afp2/ps2afpd.log where usual PostScript transformation is logged. See also: /var/psf/ps2afp2/ps2afpd.log Reprint job, by command 'pdresubmit ' See also: Print for someone else Reprinted job? Doing a "move job" is a way to reprint a job. Via job attributes, how can you tell if a job is a reprint? One obvious indication is that the submission-time and creation-time attributes greatly differ: they are the same when the job first arrives, and creation-time thereafter remains constant while submission-time reflects when the job was most recently sent on its way to be printed. Furthermore, a resubmitted job definitely has a modification-time attribute while most, untouched jobs do not. Requested GUI: Column in Jobs listing, reflecting the actual destination. required-resources-not-supported Job attribute: Lists attribute values that this job requires, but that are not supported by the actual destination to which this job is assigned, or if the job is not assigned, by the most suitable actual destination. GUI label: Resources not supported Possible values and known reasons: "actual-destinations-requested" Seen when doing pdpr with -x "default-printer-resolution=1200" and the printer properties printer-resolutions-ready (and printer-resolutions-allowed) only go up to 600. "all" How vague... This has been seen due to the job specifying a default-input-tray (e.g., "tray-2") and default-medium (e.g., "ledger"), both of which are bogus for letter size printing on an Infoprint-er. "octet-count" Seen where the job file size is greater than 2 GB. Notes: If a job is held and this indication is set, the error.log will not necessarily contain anything about it. Sadly, the resource most commonly reported is: actual-destinations-requested which is so non-specific as to be useless. See also: resources not supported Resolutions ready GUI box under the Appearance tab, listing the dpi resolutions which the printer will handle. Attr: printer-resolutions-ready Note: Some PDFs may have a Document Security setting of "Printing: Low Resolution". This may prevent some jobs from printing, as with "Error: not permitted to print PDF file". That PDF setting is overly vague, and gives no idea of the numeric resolution allowed; and a PDF like that usually employs encryption, so physical inspection of the PDF is not possible. See also: print-qualities-supported Resolutions supported by IPM Transforms documentation in the Reference manual say that for AFP printing resolutions, the only supported values are 240, 300, 480 and 600. A resolution of 1200 dpi seems to be beyond the scope of the product. See also: DPI Resource Group AFPDS defines a structure known as an Inline Resource Group which may be present at the beginning of any print file. This structure may contain resource objects to be used in printing the file. Objects found within an inline resource group will be used in preference to identically named objects in the normal system libraries. This capability makes it possible to build a completely self-contained print file that does not require any resources to be installed on the driving system before it can be printed on an AFP printer. A Resource Group will contain a Pagedef and/or Formdef resource, and perhaps also fonts. You can see this structure by performing 'afpdmp -d' on an AFP file generated by an IPM command such as 'ps2afp', reported as: BRG (Begin Resource Group) NAME INLINERS "resources not ready" GUI Jobs Status value. To determine why, select the job, go to Properties, then Job Status, where the "Resources not ready" box will contain a reason, such as "Forms". Attribute: required-resources-not-ready (synonym: resources-not-ready) Lists attribute values that this job requires, but that are not ready on the actual destination to which this job is assigned, or if the job is not assigned, on the most suitable actual destination. If a required resource is not ready, Infoprint holds the job. The required-resources-not-ready job attribute indicates the resources that a job or document attribute specifies and that are not ready on the actual destination to which the job is assigned, or, if the job is not assigned, on the most suitable actual destination. Possible values and known reasons: "Actual Destinations Requested" This, despite the AD being defined and quite ready. Can be caused by LD Job and Document Defaults, Document Print Quality being set to a numeric value where the AD is an AIX DSS - which does not support such a spec. "resources not supported" Reason for a job not printing, as evidenced in the GUI Job Status tab Reasons field (job-state-reasons attr). See GUI field "Resources not supported" (attr required-resources-not-supported) for the specific resource. May indicates that the job is specifying an attribute not available at the Actual Destination. See my explanation of message 5010-092 for a case in point. Or, may simply be that the job is of a Format, such as TIFF, which no configured printer is set up to RIP and print. Resubmit a job An operation commonly known to operators as "reprinting a job". See: Reprint... Resubmit job, by command 'pdresubmit ' Resume printer To undo a Pause, to allow printing to resume on the printer. GUI: Printer -> Resume or use the green stoplight. See also: Pause results-profile Job attribute: Specifies the delivery method for the output, and designates who is to receive the output and the number of copies for the recipient. But the attr also provides more insights... Contents: name@node:method:copies:'some text':bin (bin is not supported by the server) Note that the "name@node" element provides more accurate identification of the job submitter than do user-name, job-originator, or name-of-last-accessor where the latter may only reflect the latest system which LPD-relayed the job to Infoprint Manager, whereas the results-profile element is the actual origination point. In particular, the node will identify the computer's "name", as in the case of a Mac OS X computer, where that name is what the user chose in the System Preferences, Sharing, Computer Name field. Note that the system name in results-profile is short, containing only the hostname (e.g., "acsrs1") and not the domain (e.g., "bu.edu"), unlike the other attributes, which contain a full hostname+domainname, like "acsrs1.bu.edu". The /var/psf/jobcompletion.log's NodeID field (the 3rd) attempts to record the originating host, but whereas the field is only 8 characters, there will seldom be enough of it in there. Further, in LPD job submissions, it will be the IP address rather than hostname. Note that the pdls command will not work with -f specifying results-profile via '~=' or '*=*', apparently because of the colonized construction of results-profile. Example: rbs@aixsys1.bu.edu:pickup:2: "Retain for" GUI radio button and value field for defining how long to retain jobs. Alternate radio button: Retain forever GUI: Logical destination, Job and Document Defaults, Job Retain Time tab Attr: job-retention-period Note that changing the value does not affect the retention periods of jobs which arrived before the change. See also: Job scheduling; Retain forever; retain-forever "Retain forever" GUI radio button for choosing to retain jobs indefinitely. Alternate radio button: Retain for GUI: Logical destination, Job and Document Defaults, Job Retain Time tab Attr: retain-forever Note that changing the value does not affect the retention periods of jobs which arrived before the change. See also: Job scheduling; job-retention-period; Retain for retain-forever Attribute for selecting whether jobs should be retained indefinitely - a boolean. If false, the job-retention-period value is observed. GUI: Logical destination, Job and Document Defaults, Job Retain Time tab, "Retain forever" radio button. See "job-retention-period" for warning. See also: Job scheduling; job-retention-period; Retain for Retain jobs GUI: Logical destination, Job and Document Defaults, Job Retain Time tab Attrs: job-retention-period; retain-forever See also: Job scheduling Retained job In Infoprint, an object that represents a job that is being stored in the print system for a specified amount of time, normally after the completion of printing the job. A retained job does not reside in a queue. Can retain immediately, via Job and Document Defaults, Job Scheduling tab, Job scheduling choice "retain immediately" Retained Jobs, best column settings The following columns and order are in GUI best: Sent by Submitted to Submit time Job Global ID Status Pages Format Size Retain Delete in Note that IPM does not provide the opportunity to show a column containing the name of the destination used. Retained Jobs, list via command 'pdls -R -U :' provides a basic list, with job ID, job name, state, and logical destination. For a tailored list, proceed with a command line which specifies the attribute columns you want, like: pdls -R -U -r 'job-owner,job-name,job-identifier' -s column : Reuse delay for printer See: destination-release-timer Reverse lookup behavior Experience shows that IPM wants to perform a reverse lookup on the network address you configure to it: if an IP address, it will attempt a DNS lookup on the name, and vice versa. See my description of message 5010-087. Ricoh, submit problem report In their parlance, a problem report is a Service Request. As of 2014/09 there is no known way of submitting an SR online: you have to do it via telephone: Call 1-877-318-8968 Enter "2" for software A Ricoh person should respond, asking if it was a new or existing problem. As of mid 2014, problem reports are now called Cases, and are assigned an 8-digit number, like 00268677. Some of their technicians use the email address: aftech@ricoh.usa.com See also: pdcapture Ricoh printers Ricoh printers are engineered to emulate HP printers. In particular, Ricoh printers do PJL, and they can be fed via Raw port 9100 (which Ricoh called Direct Print, or DIPRINT). RIP Raster Image Processing (q.v.). In printing, the instructions and data contained in the job must be translated to the bit patterns which will finally create the image on the page. As written by a laser, the image is to be created one scan line at a time, in a raster, much like how an electron beam scans a television screen to create an image. That transformation is called a "rip", and the process, "ripping". See also: RIP server "rip failed" GUI Status column value indicating that something went wrong in transforming the job's instructions and data into bit patterns that the destination printer can use. ("rip failed" will occur when IPM initiates the transform itself. If using Transform Sequences, you are initiating the transform, and a non-zero return code from your procedure instead results in an "aborted by system" Status.) The most common things that go wrong, as we've seen: - The file is truncated. Somehow, the user managed to interrupt or otherwise cause the job to be incomplete as it arrived. Inspection will show the job file abruptly cut off in its midst. - EOF before first page produced. Server error log message: afpReorder: unexpected EOF before first page (No significant error indication in ps2afpd.log.) For example, at the end of the PostScript job file, you will find: %%EndProlog %%EOF That is, the file contains just a prolog. - Created for different printer. The user used a print creation method or specified things which caused the job to be created and tailored for a printer brand and model which does not match that to which the job went. The job contains device-specific instructions which are inappropriate for the printer to which the job was sent, and which that printer cannot perform. Thus, the job is invalid relative to where the user sent it. For example, the job might contain instructions which call for using an output tray which doesn't exist on the printer the job was sent to. - Requesting an unavailable paper size. Example: %%DocumentPaperSizes: a4 ... %%BeginPaperSize: a4 a4 %%EndPaperSize where the job assumes that "a4" is defined in the printer userdict - which is not necessarily the case. - Sending a raw Microsoft Word Document file to the printer. IPM thinks its Type is ASCII, but the transform fails. Examining the file, you will see "Microsoft Word Document" in amongst the binary at the bottom of the file. Such "rip failed" jobs are hopeless and should be deleted, their owners notified of job errors requiring correction. By default, failed jobs are retained, per the the requeue-failed-jobs queue attribute (GUI:"Keep failed jobs"). See also: "aborted by system"; PostScript error logging; Status; requeue-failed-jobs "RIP for" See: base-printer RIP processor See: PCL server; PostScript server RIP server See: PCL server; PostScript server rip-and-* Value choices for the Job attribute job-rip-action. The default is that none of these choices will be in effect, such that the job will queue without job-rip-action being set, thereby allowing the server to proceed in the conventional way of transforming a job and doing all that it can to print it, keeping it in pending state if the printer has to be shut down, rather than holding the job. See also: job-rip-actions-supported rip-and-hold Value choice for the Job (LD) attribute job-rip-action, which instructs IPM to always transform the job and return it to the scheduler in the held state. This attribute value will override a server setting of save-rip-files = no, so as to keep the AFP result around for a while - but only up until the job goes to the printer, where the intention is that the AFP is no longer needed, and it is removed to relieve space in the server directory. (More on this below.) Once the job is "ripped", the job-rip-action attribute value in the job changes from 'rip-and-hold' to 'rip-and-print'; and the value of the job-state-reasons becomes rip-and-hold-completed plus job-hold-set. The GUI will show job Status as "ripped", which correlates to job-state-reasons=rip-and-hold-completed. The AFP output is in the /var/pd// directory, in a file of name form ...afp like sample: 0899200081.1.Infoprint2210.afp where the printer model is taken from the AD's destination-model value. As mentioned above, when rip-and-hold is in effect it will temporarily override a server setting of save-rip-files=no. If there is a problem with the printer during the printing of such jobs, and the printer icon is shut down, the .AFP files will evaporate! IPM apparently treats this case the same as if the files had printed. If the printer is restarted the the jobs start processing again, they will be transformed again, this time with the attribute setting of job-rip-action=rip-and-print. This is obviously wasteful and confusing. To avoid it, code the save-rip-files=yes server attribute, which will keep the .AFP files around as long as the source job files (per retention). This will use more space in the server directory, but will avoid all the issues of involved with the files going away. Terminating-transform special case: When rip-and-hold is in force, and the involved transform is set to terminating-transform=true, then submitted jobs will *not* go into a ripped-held state: jobs will instead transform and transfer into the Retained Jobs area in a status of "completed" (as opposed to "completed successfully", as when a job to actually go on to print). For completeness: A rip-and-hold job does not show up in the accounting records by virtue of being ripped and held. See also: save-rip-files rip-and-hold AFP file peculiarities In initial rip-and-hold processing, the generated AFP file will often be dedicated to a printer model type, as in having filename "2224900243.1.Infoprint2105ES.afp". Let's say that a job arrives and happens to be ripped for an Infoprint 2105ES as indicated in the preceding jobname; but when the job is released, a printer of that model is not available: instead, an Infoprint 2210 is in service. What happens? The job will be ripped again, to produce AFP dedicated to that model, resulting in a filename like "2224900243.1.Infoprint2210.afp". The transform program is invoked a second time, incurring substantial overhead in the IPM server, and delaying the processing of other jobs. (It can perceived that the job is a "repeater" in that the job-rip-action attribute value is 'rip-and-print' instead of 'rip-and-hold'. On that basis the transform can avoid trying to perform any site-specific actions again for that job number.) This re-ripping behavior is obviously a particular problem in a queue served by multiple Infoprint printer models. You can often get around this problem by defining like printers as the same model. For example, in an environment having two 2105ES printers and one 2210 printer, you can get away with changing the destination-model attribute to "Infoprint2105ES", because they are printers in the same family. In an Infoprint 1585 printers environment, the generated AFP file has an identity like: "2224900579.1.none.afp", with no model identifier. Go figure. rip-and-hold and ASCII jobs There is a gross IPM defect in the handling of ASCII jobs in rip-and-hold processing: When the job arrives, initial processing transforms the job to AFP, just as PostScript is handled. But, when the job is released, instead of sending that prepared AFP to the printer, IPM stupidly sends the raw ASCII to the printer, resulting in useless output and waste. As of 2009/08, we have a PMR open on this problem (and are experiencing the usual poor handling of the problem report by InfoPrint Solutions Company). rip-and-hold and printer state Per IPM architectural conventions, jobs will not transform (rip) unless there is a printer serving the LD which is in an enabled state (not disabled or shut down). There are circumstances in which a site may want rip-and-hold to occur when a venue is closed, as where the transform program must be invoked so as to plant job entries in a database involved in that site's release based printing scheme. Having the printer icons in a shut down state overnight, for example, would thwart the scheme, where job submitters would not find their jobs listed at the release station. A way around this is for the venue to turn off their printers overnight, for electrical safety, but leave the IPM printer icons enabled: IPM will lose SNMP connectivity with the printer and be blind as to its actual state, but because the icons are still enabled, arriving jobs will be transformed and be held as sought. rip-and-hold-ignore-ready Same as rip-and-hold. (No, this setting will not allow jobs to RIP if the printer icon is in a disabled or shut down state.) rip-and-print Value choice for the Job attribute job-rip-action, which is the way that a job is flagged after it has been through rip-and-hold processing, where "rip-and-print" tells IPM that the next step for the job is printing. (Note that it is possible for the job to be RIPed again, if the printer available to it at print time is of a model which differs from the model used to originally RIP the job when it arrived in the queue, per the model number incorporated into the AFP file. rip-and-print-ignore-ready Value choice for the Job attribute job-rip-action, which instructs IPM to transform the job regardless of whether all required resources are ready. After the transform, if it is then found that all required resources are ready, the job will be printed, else it will be held until all required resources are ready, at which time the job will be automatically released. By virtue of the transform having been done, the value of the job-state-reasons attribute is set to rip-completed. Ripped files, save Admin GUI: Server -> Properties, General, "Save ripped files" ripping Job Status for when IPM performs the transform itself. (If you have a Transform Sequence in effect, "ripping" does not show up: only "processing" does.) A modest job that stays in "ripping" state for a long time, for a purely IPDS destination (PSF TCP/IP) is indicative of the printer being busy with other work, like an Infoprint 2085 currently working LPD-submission jobs. root The Unix root user is established at install time as the principal administrator, in security group "admin". Root is in security groups: acl_admin admin oper Route submitted jobs to See: logical-destinations-assigned RPPS Ricoh Production Print Solutions. Announced 2011/04/05, this new RPPS Group will encompass InfoPrint Solutions and the Ricoh Production Printing Business Group's marketing and planning resources from Japan. RPPS will report to Ricoh's Production Printing Business Group (PPBG) in Tokyo, and it will be headquartered in West Caldwell, New Jersey. The Boulder, CO headquarters (former IBM printing division) has been closed. Then, on August 2, 2011, RPPS announced that they would discontinue all Infoprint Solutions printers. RRL Request Resource List, command sent to an AFP printer, where a reply should provide a list of resources. .rtf Filename extension for a Rich Text File document, as produced by Microsoft Word. IPM has no provisions for transforming RTF: the originating application is supposed to produce a PostScript print job. RTF documents should not be submitted for printing as-is: if attempted, they will arrive at the transform as "ASCII", where your transform program may detect them (see below) and reject them, with explanatory email to the submitter. {\rtf1 At the beginning of a file, is the "signature" or "magic ID" of an RTF document file (.rtf), created per specification version 1. An entire RTF file is considered a group and must be enclosed in braces, hence the leading brace. This is immediately followed by character set spec, one of: \ansi ANSI (the default) \mac Apple Macintosh \pc IBM PC code page 437 \pca IBM PC code page 850, used by IBM Personal System/2 (not implemented in version 1 of Microsoft Word for OS/2) Sample header: {\rtf1\mac\ansicpg10000\uc1 \deff0\deflang1033\... FrameMaker can open RTF documents (it will convert Microsoft RTF). IPM's sniffer says: "Unknown, ascii.". Ref: http://netghost.narod.ru/gff/ graphics/summary/micrtf.htm Samba See redbook: Printing for Fun and Profit under AIX 5L SAP printing SAP R/3 Version 3 prints Output Text Format (OTF) data stream and the native Advanced Business Programming Application (ABAP) line data stream. Local printing is by what SAP refers to as Access Methods C and L, per how the printer is connected to the SAP System. C: supported on all Windows platforms that SAP supports for application servers; iServer eSeries. L: UNIX Remote Printing is by what SAP refers to as Access Methods S and U. U: UNIX systems, transfer via LPR/LPD; Microsoft Windows system (using a TCP/IP Print Server and SAPSprint). In the transfer, the stream is neither encrypted nor compressed. S: Microsoft Windows systems (using SAPSprint). This is a proprietary method, in which the data is encrypted and compressed. Save ripped files See: save-rip-files save-rip-files Server attribute for saving the output of transforms (usually deleted). If you decide to save them, you can thus eliminate the time to reprint, but job space requirements will approximately double, in having to save the original jobs plus the transform outputs, for the duration of job retention. Saving is normally not done, unless the site has special requirements. Default: No GUI label: Save ripped files Managed via admin GUI, Server -> Properties, General Notes: Whereas each job is associated with a given user, there is little value in employing this attribute where you would seek to use such to more efficiently print course packets or other documents which would be seen redundantly submitted by a number of users over time. This option is effectively a superset of job-rip-action = rip-and-hold, governing the whole life of the jobs on the server (not just their life before their printing occurs): if the printer icon is shut down during the printing of such jobs when the server is set to save-rip-files = no, the .AFP transform files will go away and when the printer icon is restarted, the jobs will have to be transformed afresh - this time resulting in the creation of the more common _xfm1 files rather than .AFP files. If the server is set to save-rip-files = yes, the .AFP files survive across a printer restart, and the wasteful re-transform does not have to occur. See also: rip-and-hold scheduler-sort-primary-order AD attribute for job scheduling, governing the primary test for the scheduling. If the value of this attribute is "fifo", then the value of scheduler-sort-secondary-order is cleared, because fifo always resolves without a tie. scheduler-sort-secondary-order AD attribute for job scheduling, governing the secondary test for the scheduling. Scheduling jobs (Scheduler) Governed by AD attributes scheduler-sort-primary-order and scheduler-sort-secondary-order. For on-demand printing, the best arrangement is: scheduler-sort-primary-order = job-priority scheduler-sort-secondary-order = fifo which allows the jobs to process in the order received, unless the operator alters the priorities of queued jobs. Note that if you do not specify job-priority for the primary or secondary sort order, changing a job's priority will have no effect upon its processing order. Ref: Reference manual, Appendix C. Job Validation and Scheduling Security Infoprint Manager's access restrictions are based upon an Access Control List mechanism. An ACL may contain individual users, or the names of groups of users (where the groups can be more readily maintained separately). By default, three groups are established at install time: acl_admin A list of users who can administer ACLS. admin A list of users who can do serious things to the server, as in changing the configuration of the server. oper Those who can manage jobs and destination states. A user or group can be given any combination of the following character flags: r For an object, can list attributes (as via 'pdls'). For a command, can execute it. (There is no 'x' flag.) For an AD/LD, the user can view attributes and submit jobs to it. w For an object, includes r capabilities, plus can update its attributes. Appropriate for operators to be able to manage printers and jobs in a queue. d For an object, includes w capabilities, plus can delete it (as in deleting a job). Only the administrator should have this. ACLs can be applied to commands, and to objects (queues, LDs, ADs). Commands are inherently protected by initial ACLs such that they can be invoked only by appropriate personnel, as for example the command 'pddisable' being invocable only by those in the admin or oper groups. This is a "uniform security environment", as it applies to all resources equally. Because of the default command security, in a basic configuration it is not necessary to also apply ACLs to queues and printers, because someone who somehow got ahold of a GUI could not alter queue contents or change printer states for lack of underlying command capabilities. If you want to go beyond that and, for example, give a department control of its print queue, then you need to both add them to the commands ACLs, and define ACLs for all resources, restricting them to their own queue and printers. Unfortunately, the whole is lamentably poor, even at the 4.2 level: - There is no password authentication involved in IPM access. - The ACL mechanism is based upon a trival "Username@Computer" scheme, where IPM takes the username and computer name at face value - and the computer name is whatever the user chose to call her computer! It is not based upon any TCP/IP network host identification. Thus, anyone anywhere in the world could establish an account name on their PC, and give the PC an arbitrary name, which matches an IPM security ACL and thus trivially gain control of the IPM server and wreak havoc. - The wildcard scheme is pathetic: an asterisk can be coded in the Username position and/or the Computer name position. That's it...there is no capability for wildcard access limitation to just users on a given TCP/IP subnet, for example. - There is no disallow capability: to keep one user or group away from a resource, you have to allow everyone else but them. Cautions: Applying an ACL to a queue for certain users or groups but neglecting to allow general submission to others can result in pdls failing ("5010-890 User @thishost.university.edu is not authorized..."), which is really bad when the pdls is being used in transforms - and the transform will fail even if the pdserver process is running under root. So, if you define an ACL for a queue, be sure to include in it: *@*:r-- or, more simply: *:r-- Ref: Procedures manual: Managing non-DCE security for Infoprint Manager for AIX See also: ACL; fstsecutil Security, manage Via AIX 'smit': Infoprint Printing System -> Security Security, show group 'fstsecutil -s -g ' Security files At install time, the default security files are stored in: /var/pd/acl/. These files are binary, encrypted. Creation of a server instance causes the replication of those files into: /var/pddir/default_cell/acl/, which can be consider the "runtime" security files, managed via smit (*not* IPM GUIs). Security Group A list of usernames@computernames which you can conveniently associate with command privileges, instead of having to assign individuals to each and every command. Entries are case-sensitive! For example, the command pdclean is installed with the security: pdclean: GROUP:admin:r-- When you install Infoprint Manager, three security groups are created by default: acl_admin Users who have authority to manage security by changing access control lists and groups. The default members are administrator and the user who was logged on when Infoprint Manager was installed. Install values: root@* (It's okay for the system name to be a wildcard in that this group is used only in local host administration via smit and commands.) admin Users who have administrator authority. The default members are administrator and the user who was logged on when Infoprint Manager was installed. Install values: root@* poweroff@* oper Users who have operator authority. The default member is administrator. Install values: root@* Files having these names appear in /var/pd/acl/groups/ and /var/pddir/default_cell/acl/groups/ as encrypted files. Those in the former directory seem to be the install-time versions, whereas those in the latter directory seem to be the ones updated by smit. Ref: Procedures manual, chapter "Managing non-DCE security..." Security Group, remove a user 'fstsecutil -d Username -g Groupname' Security level Default: Low Possible values: Low, Medium, None Managed via admin GUI, Server -> Properties, General Security log /var/pd//error.log Successful accesses show up containing like: "[1e90 joeuser->PCnumber1]". Failures are like: "User fred@bogushost is not authorized to perform operation pdcreate on object ____.". security-level Server attribute defining the security level for the server. In common, non-DCE environments, the level can be one of: none No security checking is performed. low Use ACL and Group security checking. There is also a medium level, where DCE controls access. Default: low (non-DCE) See also: ACL; fstsecutil SEF Short Edge Feed: in the printer, paper is fed via short edge first. Contrast with: LEF SEGMENT (PPFA PRINTLINE operand) Page Segment includer, wherein you specify the name of a segment and where it should be placed. The name is some specification of the 1-8 character S1* filename. SEGMENT (PPFA command) To require that page segments be loaded to the printer before the page begins printing. If segments are used repeatedly and need to be available in the printer, this eliminates the need to load them each time. However, they do take up raster-pattern storage. If the segments are included on a page but not in the SEGMENT command, they are loaded to the printer as they are used in the print data. Syntax: SEGMENT Name Where Name is the 1-6 character user-access name by which the S1______ page segment file is named in its file system directory. Segment See: Page Segment Segmenting Allowing the job to begin uploading before the entire RIP is done. segprof /usr/lpp/psf/bin/segprof: Permissions: -r-sr-sr-x owner/group = root/printq. Undocumented command. Operates on /var/psf/seglist/, in a physical manner, where you might as well just clean up the seglist (and segments) directory by hand rather than play with this. Usage: segprof [[ [-f] | (cancel job) [-i] | (show job status) [-o] | (delete retained jobs) [-p] | (clean up leftover segments) [-u] | (display usage statement) [-v] | (display contents of a segment list) [-x] | (delete job regardless of status ] ] Filename can be '.' where you have cd'ed into /var/psf/seglist/. selpmd InfoPrint Select Daemon In Mac OS X, is: /opt/Ricoh/InfoPrint-Manager/bin/selpmd See also: InfoPrint Select Send job completed messages See: end-message-supported Send job start messages See: start-message-supported send-mail IPM process for sending a notification, via email. Runs under process "send". Most commonly seen with Infoprint Select notifications. Separator page IPM terminology for the identification page which may be produced before each copy of a multi-copy job. Contrast with: Header page Separator page, Infoprint 2085/2105 The printer itself can produce a separator page, in LPD job submission. It applies only if the PostScript/PCL feature is installed. The separator page is printed when the LPD control file is processed, if the LPD control file requests one. (Specifically, the control file must contain an L (Print Banner Page) line. Note that the AIX 'lp' command does not produce such a line, and so no separator page. Thus, the 2085 does not reliably create a separator page in all LPD submission cases.) Normally, you want the separator page to appear ahead of the body of the job, to be the job's "front page". Control: Printer web page -> Network Settings -> TCP/IP Settings -> Printing Details: LPD Settings LPRng note: LPRng by default sends the control file first, followed by the data file, which would achieve a "front page" separator. If the LPRng option send_data_first is in effect, the separator page will appear after the body of the job. Managed via printer web page: Network Settings: TCP/IP Printing Details: LPD Settings Enabling an LPD separator page will print a page with job identification information. In order for the separator page to print correctly, the LPD data stream must be set to PCL or Autodetect (controlled at the top of the TCP/IP Settings: Printing Details web page). What appears on the separator page: User: _____ Host: _____ Class: _____ Job: Separator page, Infoprint Manager See: Start sheet; User exits Separator page, static text In Admin GUI, right-click on Logical Destination, select "Job and Document Document Defaults", then tab "Separator Sheet". Separator page and MVS See: MVS printing and separator page Separator page and Windows For its own printing, Windows supplies separator pages in c:WINNT\system32 as files: pcl.sep PCL Switches printer to PCL printing and prints a separator page before each document. pscript.sep PostScript? Not! Switches printer to PostScript printing but does NOT prints a separator page before each document: the PostScript printer must support PJL. sysprint.sep PostScript Switches printer to PostScript printing and prints a separator page before each document. sysprtj.sep ??? They may be customized. Server A server: - Manages the validation, routing, and scheduling of jobs - Manages the printing or transmission process - Contains logical destinations, queues, and actual destinations Server, create This is done by the IPM install. Obviously, there is no pdcreate to be done for the server, as that command interacts with the server, which has to be there already. Server, shut down now 'pdshutdown -w now ' Server, signals There is no documentation saying that the pdserver process in AIX will respond to Unix signals (as used via the 'kill' command), or how; but empirical results show the following: USR1 Causes server to shut down cleanly. USR2 Debugging signal: generates dbglog.dmp in /var/pd// HUP No effect; just error.log entry. ALARM No effect; just error.log entry. DANGER No effect; just error.log entry. Server, start (AIX) At AIX boot time, the servers listed in /etc/rc.pd.servers are started by /etc/inittab running the /etc/rc.pd shell script, which invokes the startsrv command. You can manually invoke /etc/rc.pd, but be sure that you are running as true root and that the various Unix resource limits in effect allow a very large file size and memory usage, so that the server does not run short. Performance: By default, this can take a considerable amount of time (5-20 minutes). This is partly due to the SNMP-discovery-during-startup attribute defaulting to True, meaning that IPM tries to converse with each defined printer to ascertain its actual status at the moment. A value of False will cause IPM to use the status it last had for the printer, and then realize actuals when it goes to use the printer. Also, the more jobs in the Retained Jobs area, the longer to start. See: startsrv See also: Shut down IPM Server, start (Linux) Automatically, at boot time: Happens because /etc/rc.local contains an entry to run /etc/rc.pd . Manually: Invoke /etc/rc.pd (Trying to run /usr/lpp/pd/bin/startsrv does not work because it expects enviroment variables to already be set.) Invoking /etc/rc.pd when the system is up does no harm, as the startsrv command that the script calls tests for the server being up (via 'pdls -c server'). Server, stop See: Shut down IPM Server attribute, set 'pdset -c server -x Attr=Value ' (Do not put a colon after , else get 5010-166.) Server attributes, show 'pdls -c server -rall :' In Unix you can usually do: pdls -c server -rall ${HOST}: Server attributes file /var/pd//pdb/spooler/ Server error log /var/pd//error.log Server LANG /etc/pdserver.conf, first token. Server performance See: pdsettrace Server PID 'ps -efl | grep pdserver' (There is no known file in IPM's directories which contains the pdserver PID.) Server port Usually: 6874 Found in AIX file /etc/pdserver.conf, second token. Server process Is: pdserver Server properties, list 'pdls -c server -rall :' Server restart time Obtainable in one of the following ways: 1. 'ps -efl | grep pdserver' 2. Observe the mtime timestamp of the /var/pd//cfcpp.log.0 file. Server trace Performed in conjunction with IPM Support. The trace is activated by doing: pdsettrace -y with a tailored trace configuration file /var/pd/spl_trace.cfg in place. This results in activity being captured in file /var/pd//trace.log in a wrap-around manner. Note that the server reads this file when it starts; so if you make changes in the file, you need to restart pdserver for the changes to be in effect. (An alternative is to use the pdset command to alter attributes which participate in that file; but note that certain attributes such as log-size cannot be pdset: they can only be defined in the cfg file.) The server latches on to this file inode for trace usage such that if you rename the file, then (re)activate the trace, you will find that tracing continues to be captured in the old (renamed) file. Note that the pdsettrace command sets trace groups unto itself, rather than honoring settings you may have coded in the /var/pd/spl_trace.cfg file. Instead of using the 'pdsettrace -y' command, you can emplace the /var/pd/spl_trace.cfg file, where the file says that tracing should be enabled, and then (re)start the server. WARNING: Having this trace file in place at pdserver restart, with its internals saying that tracing is enabled, will result in the restart taking about ten times longer than normal! Note that IBM provides a prototype trace configuration file as /usr/lpp/pd/bin/spl_trace.cfg to be copied into /var/pd/, with tailoring as needed. After the server has run for a reasonable amount of time with tracing on, stop the trace with 'pdsettrace -n' and then run 'pdcapture' and FTP the resulting /var/pd/acsrs6/debug.tar.Z file to testcase.software.ibm.com/ps/toibm/afp (Name: anonymous Password: YourEmail@Address) and then notify their problem handler. Debugging dir: /var/pd//debug See also: pdsettrace Servers, distributed Ref: Procedures manual, "Creating and managing servers". Getting Started manual topic "Installing secondary Infoprint servers". Servers, multiple Infoprint Manager for AIX can be installed on a single RS/6000, or it can be installed on multiple servers with shared information and resources, in what is called an Interoperating Environment. This allows you to manage printing through LANs and WANs with a single view of all printers and resources. Infoprint Manager for AIX servers can interoperate not only with each other, but with Infoprint Manager for Windows NT and Windows 2000 servers as well, again using shared information. You can run multiple Infoprint Manager servers on one AIX system, but you can run only one Infoprint Manager server on a Windows system. Caution: APAR IY40858 advises that multiple IPM servers can participate and interoperate in the same namespace ONLY if they are at exactly the same level (including maintenance level). This is because the OIDS in the namespace are altered to add functionality to the product they change from PTF level to PTF level and are often incompatable in such changes. See also: OID setup IPM install command to install and configure Infoprint Manager software onto local or remote AIX systems. Is typically a Ksh (Korn shell) script, supplied on the installation CD. NOTE: This script will terminate the IPM server and call for a reboot when it is done. Usages: setup [-h] setup -c -n srvr_name -p port_number [-P printer_name] [-L locale] [-R] [-s mount_point] setup [-c] [-R] [-s mount_point] [-q] -a response_file setup [-s mount_point] -m setup [-s mount_point] [-S] -M setup -x [-s mount_point] setup -X setup -y [-s mount_point] setup -Y Where: -a Specifies a response file to be used in an unattended type install (where no installer screens are attempted to be displayed). -c To force command line interface rather than GUI. -h To display usage info. Advisory: The command, as of 4.1, is misengineered so that it evaluates the AIX opsys level before processing any options, and so will fail to satisfy this innocuous information request if the level is incorrect, preventing the customer from getting such info for planning. -s Specifies the mount point where the software is. The GUI install assumes /cdrom. The product-standard place, assumed in a remote type install, is /ip_remote, being an NFS mount point for the file system created by the mk_ip_remote command, from the installation DVD. Avoid using a relative name, like '.': I've experienced a lot of odd results in trying that, so always code a full path. Moreover, you should not be in the software directory as your current working directory, else you get error 002-313 (see later in doc). If installing a feature from a subdirectory created under a mountable file system (e.g., /ipm_remote) I find that it works best to specify the subdir with a trailing slash, like: "/ipm_remote/wkgrp-feature/". To run directly off the CD: '/cdrom/setup' Sharing printers See: Printer sharing Sheets printed Se: media-sheets-completed Shortest-job-first In Infoprint, a queuing technique where the next job assigned to the first position in the queue is the shortest job in the queue; that is, shortest in terms of size, not expected processing time. Contrast with deadline, FIFO (first-in-first-out), job-priority, and longest-job-first. Show All Servers In the GUI, under the Server menu, displays all servers that are currently running in the namespace. Shut down IPM (AIX) Via SMIT, or: /usr/lpp/pd/bin/stop_server (a ksh script) or: setenv PD_LANG en_US pdshutdown But: See Caution under "startsrv". Shut down printer To dissociate IPM from the printer for an indefinite period of time. Perform via command: 'pdshutdown -c destination ' or via GUI: Stop > Shut down Causes IPM to terminate all communication with the printer (IPDS control of the printer is terminated). The printer is disabled. Contrast with Pause (which is for a brief period of time). AIX process account records record cmds: psfapid psfctl GUI: Printer -> Stop, select Shutdown See also: Disable Shutdown of server, evidence In the server error.log there will be message 5010-456 Starting a shutdown request of type now for server ____. sides AD attribute, indicating whether the printer device prints on one or two sides of the media. DSSes: PSF, Infoprint 2000, Passthrough GUI label: Sides to print The attribute's value must be one of the values of the sides-supported AD attribute. This attribute is not for AIX or BSD DSSes, presumably because native IPM transform processing provides the capability of effecting simplex/duplex printing only in AFP processsing. With the AIX and DSSes, a back end command must be chosen and specified to feed the printer, which will affect results. sides Document/Default Document attribute: Specifies the number of media sides on which this document prints. Needs to agree with the destination attribute sides-supported. DSSes: AIX, BSD, PSF, Infoprint 2000 The server validates and schedules jobs by comparing this document attribute against the AD's sides-supported attribute. Possible values: 1, 2 GUI Label: Sides to print Is ignored if form-definition document attribute is specified. If you don't specify such a default, and the job does not internally contain such an attribute, no 'plex' attribute will be provided to a Transform Sequence. See also: 0782-006; plex sides AD attribute to specify whether the printer can print on one (simplex) or both (duplex) sides of the paper. Values: 1 or 2 and must be one of the values of the sides-supported attribute. GUI: "Sides to print" (Output tab) See also: Duplex; plex sides Document attribute: Specifies the number of sides to print on a sheet. Values: 1 or 2 and must be one of the values of the sides-supported attribute. Advice: Set this for PostScript type printing, because the printer may have wacky default values. "Sides to print" GUI field for Job and Document Defaults, Document Layout tab. Attr: sides (q.v.) sides-supported AD attribute for whether the printer can print simplex (one side) or duplex (both sides of a sheet). DSS: AIX, BSD, PSF, Infoprint2000, Passthrough, Print Optimizer This attribute, rather than the "sides" attribute, is used in scheduling jobs. GUI: "Sides allowed" (Output tab) Related: plexes-supported Signals to server See: Server, signals SIGUSR1 Unix standard signal: User signal 1. PSF uses SIGUSR1 to wake up a waiting program, but not to kill applications. See also: Server, signals Simplex Defined as printing only on one side of a sheet, the other side being left blank. Governed in a Formdef via "DUPLEX NO". Governed in IPM via: Sides = 1 and Plex = simplex GUI: Logical destination, Job and Document Defaults, Document Layout tab Number of pages: A simplex document consisting of two pages of text will generate two AFP pages: there will not be any generated blank page between them. It is up to subsequent processing to observe any supplied formdef to place the page images on the front sides of two consecutive pieces of paper. See also: Duplex; plex Simplex, allow choice See: pcl2afpd Simplex detection See: ps2afp output per PostScript factors Size GUI: Column in Jobs listing, reflecting the size of the submitted file, in KB. Defect: A zero-bytes null job will be reported as 1 rather than 0. "Skip to channel" Old line printer reference for the selection of line spacing. See: 1403 Slip/Separator sheet GUI: Element of Printer Properties, Auxiliary/Separator Sheets tab. Possible values: 64xx blank brief full job ticket none <--- default See also: Auxiliary sheets allowed; End sheet; Start sheet Smart defaulting Where IPM can discern output device characteristics via SNMP, to fill in AD attributes, rather than you having to manually specify detailed information when defining an AD. Attributes involved: destination-model; input-trays-medium (also smart-defaults the attributes input-trays-supported and media-ready); media-ready; media-supported; output-bin-numbers (also smart-defaults the attribute output-bins-supported); plexes-supported; psf-tray-characteristics (also smart-defaults the attributes input-trays-supported and media-ready); sides-supported. SMIT controls The IPM installation adds an "Infoprint Printing System" entry to the main SMIT menu. Submenus: Start/Stop Servers Start a Server Stop a Server Migration Tools Create a Minimum Configuration Migrate Existing AIX Printers Troubleshooting View Server Error Log Dump Server Debug Log Capture service/debug information Enable/disable server tracing Remove unassociated pdpr files Clean a server of all jobs Reset server communications Format diskette Standardize Default Users List Local Server Processes Production Print Operations Print System Status Job Control Printer Control Queue Control Miscellaneous Customize Prod. Print Ops (PPO) Env. Load Driver onto S/370 Channel Emul. Customize the Input Manager Interrupt the Current Job on Input Dev Work with Tapes Clean up Canceled Jobs and Leftover F. Error Log and Trace Options Security Groups Access Control Infoprint Utilities Add or Remove Languages Claim New Disk for Use With Infoprint Configure Fast Connect for IPM Configure Modem for Dial-Up Diagnostic Configure Secondary Server (NFS) Create Default Users Enable/Disable Autostart Notification Daemon SAP Daemons Print Test Job Tune System Performance Ref: Getting Started manual See also: Infoprint Manager Security; Infoprint SMIT administrator's Interface SMTP server Admin GUI choice for the Infoprint Email DSS: Server -> Properties, General See also: Email DSS; Infoprint Email SMTP server port Admin GUI choice for the Infoprint Email DSS: Server -> Properties, General See also: Email DSS; Infoprint Email smtp-server-host, smtp-server-port Infoprint Manager server attributes for Infoprint Email support and notifications (most notably for Infoprint Select). Default: local AIX SMTP server. Manage via admin GUI Server -> Properties snfrmain /usr/lpp/psf/bin/snfrmain Page description language interpreter ("sniffer"). /usr/lpp/psf/bin/snfrmain Usage: snfrmain Filename Tag where Tag is 1, 2, or 3. Example: 'snfrmain myfile 1' Returns: Status value: 0 Stdout: String reflecting the file type, as in the following (where punctuation is what the program returns): DIB. [Device Independent Bitmap; .bmp] Ditroff generated with troff -Tafp. FDF. GIF. HP_GL. HP_PCL. HP_PJL. JFIF (jpeg). MODCA (afp). MPPML. PCX. PDF. PJTF. PostScript. PPDS. TIFF. Unknown, ascii. (Seen with RTF files sent to the printer, and plain ASCII) Unknown, nonascii. (Seen with Xerox metacode and random binary data.) Note that a job is reported as "PostScript." when enveloped in PJL. Sniffing the job file Colloquialism to describe IPM's cursory examination of the incoming job file, primarily to determine data format (PostScript, PDF, PCL, etc.). While doing that, it also steps through the file looking for page boundaries, as delineated by data stream definitions, which it reports in the Pages column of the GUI. See also: Pages; snfrmain SNMP Simple Network Management Protocol. Its most obvious function is as the means by which IPM communicates with the AD to ascertain device status, per server SNMP settings. IPM continues to support only SNMP V1, even as of 2010 and IPM 4.3, though printers now come with SNMP V3. IPM attempts to establish SNMP communication with a printer device when: - The IPM server is started. - The actual destination is created. - Any of the SNMP attributes of the AD are changed. - The AD is enabled and the value of the snmp-active attribute is false. The Procedures manual adds that if IPM cannot communicate with the printer using SNMP, it attempts to ping the printer. If the ping works, that tells IPM that the printer is alive and allows IPM to conclude that the printer is not an SNMP printer, and sets use-snmp=false. If the ping fails, IPM concludes that the printer is turned off or is not currently connected to the network, and thus leaves use-snmp=true, to thereafter continues trying to establish an SNMP connection with the printer. Far less obvious is that IPM uses SNMP as a general means for cataloging *all* of its own devices, definitions, settings, and allied programs (including transforms programs). Be aware that SNMP is based upon the connectionless UDP Internet protocol. (SNMP allegedly also supports TCP, but all seen printers respond only to UDP.) UDP can result in duplicate packets being sent to the printer, if the IPM server logic deems packets "lost", in not returning after what it deems a reasonable period. SNMP packets contain a Request ID, to render them logically unique, such that the server can realize that returning packets are duplicates (as the printer was obligated to respond to every one it received). Duplicates represent waste, however, and large numbers of them will burden the network and elevate the workload of both the printer and server, such that their ability to perform productive work is diminished. If the server programmer employs faulty algorithms in the design of the SNMP networking, then you can have a mysterious, invisible performance drag and LAN load. An absurd number of duplicate packets can cause server functionality problems. Note that a printer in PowerSaver mode may not return SNMP data to IPM, as for example when it is in that mode and one of its paper drawers is opened. What versions of SNMP are supported? IPM documentation fails to specify this: there is nothing in the manuals or the PTF Release Notes. Information informally obtained indicates that IPM 4.2 supports SNMP v3 (as well as earlier versions). Ref: Procedures manual, Setting Up SNMP See also: MIB; OID SNMP access test You can check that a printer's SNMP port is available by using these commands... The best to use is snmpwalk, which really does SNMP: snmpwalk -v 2c -c public PrinterNetaddr Less reliable is the the netcat command, using this form: nc -zvu NetworkAddress 161 (RPM package is: nc) But netcat may return misleading indications.) SNMP and AD queries When you query the status of a printer, via the GUI or the 'pdls' command, with use-snmp=true in effect, IPM goes out to the printer via SNMP to get its actual, current status. If you are using the pdls command and only want to IPM to tell you the status of the device which it holds from its most recent inquiry, invoke pdls with the attribute "when=now". This will greatly improve pdls performance, and can also be used when you want to retain prevailing IPM status info about the device, in special circumstances. SNMP and IPM 4.2 We discovered, the hard way, that SNMP is extremely defective in early IPM 4.2, testifying to programming and testing deficiencies. The symptoms are: - Wacky printer icon status indications with the icon falsely going red though the printer is fine (and printing!), with 5010-849 in the server error.log (but not in the printer's /var/psf/ error.log). Via an AIX iptrace I discovered a defect in early IPM 4.2, where it will bombard printers with *duplicate* SNMP packets, the number depending upon the value of the snmp-retry-count relative to the snmp-timeout value. (With a retry-count of 10,000, we have observed some 14,000 packets sprayed against the printer in one second. And this is against a printer which is in a SHUT DOWN IPM state!) I pursued this problem with IBM, starting in 2006/06 and taking almost six months to get them to accept it as a defect and write an APAR against it. Information we have received says that IPM 4.2 is trying to send a quantity of SNMP packets equal to the snmp-retry-count value, within snmp-timeout seconds - which results in completely irrational network timeout values - as little as one half of a nanosecond! The customer is in effect doing the testing that IBM failed to do. My own pursuit of this problem shows the SNMP packets coming out of the java process, which runs under the pdserver process. The java process is new in IPM 4.2, with no documentation anywhere, about it. IBM seems to have relocated the IPM SNMP programming to Java, having previously been in the C-programmed pdserver. See also: ain3dtcp SNMP files /usr/lpp/pd/bin/com/ibm/npm/util/snmp/ "SNMP is active" GUI: Field in AD properties SNMP tab. Indicates whether the server has been able to establish an SNMP session with the printer. SNMP modules IPM 4.2: /usr/lpp/pd/bin/snmp.jar (Java) snmp-active AD attribute: Reports whether SNMP is being used to monitor the AD. SNMP should be active if use-snmp=true. Not modifiable: Cannot be used in a 'pdcreate', else get error: 5010-093 Cannot modify the value of attribute snmp-active. If snmp-active=false, doing a "Check status" in the GUI will not have a "More information" clickable as a choice in the status window. In my experience, there is no way to get the IPM 4.2 server to snmp-active=true other than restarting the pdserver. Notes: Early IPM4.2 has had SNMP issues where a printer which worked well with the SNMP in IPM4.1 will show use-snmp=false in 4.2, and message 5010-849 will prevail, as the printer icon is red-flagged in the GUI. This, despite the printer being turned on and responsive to its Web page. Doing a Shutdown then Enable of the printer eliminates the red icon condition, but still have snmp-active=false. snmp-aix-printer-models Server attribute identifying the SNMP descriptive printer model names that the AIX DSS recognizes. Used for AIX and PSF-Other ADs, via destination-model. GUI label: AIX printer models Type: Non-settable, multi-valued Allowed values: IPM sets this value to a list of recognized SNMP printer models. Standard set, as of 2003/04: IBMNetworkPrinter12 IBMNetworkPrinter17 IBMNetworkPrinter24 Infoprint20 Infoprint32 Infoprint40 Infoprint21 Infoprint70 Infoprint1116 Infoprint1120 Infoprint1125 Infoprint1130 Infoprint1140 Infoprint1145 InfoprintColor1220 InfoprintColor1228 Infoprint2085 Infoprint2105 The names may come from attribute files in directory /usr/lpp/pd/attr/ which define device-support-system = aix and the printer-model attribute contains the above printer model names. See also: destination-model snmp-discovery-during-startup Server attribute specifying that during startup, the server should issue an SNMP query for each SNMP printer to obtain the most up-to-date status. The Procedures manual adds that this attribute determines whether the server gets the printer status when it periodically polls the printer. Default: True GUI label: Discover printers at startup Recommendations: A value of True can be needlessly wasteful, particularly if the IPM server has a lot of provisional and testing definitions which are seldom used: a lot of time will go to testing each, for no benefit; and it can cause the AD status to be changed from the shut down state you may have wanted. So, a value of False is probably best. WARNING: Setting the value of this attribute to False while AD attribute wait-for-job-completion = True (needed for accounting) will cause the server to fail to start where an AIX DSS is defined to drive an HP printer! To avoid this problem, you must have snmp-discovery-during-startup set True. See: pjlprtrs.cfg snmp-normal-poll-interval Server attribute for how long the server should wait after sequentially polling all the SNMP printers without known problems. Increasing the polling interval causes the server to use less CPU and network resources for SNMP polling, but it makes the currently shown printer status (for printers that are not currently printing) less accurate. GUI label: Normal poll interval (sec) The unit of measure is seconds. Value can be 0 (disable normal polling), upward. Default: 300 (seconds) The value is conventionally two or more times the duration of the snmp-problem-poll-interval value, to avoid wasting time repeatedly looking at printers which are usually okay. When normal polling detects an AD device problem, TSM may perform a Disable; then the device is polled per the snmp-problem-poll-interval. See also: snmp-problem-poll-interval snmp-problem-poll-interval Server attribute for how long the server should wait after sequentially polling all the SNMP printers with known problems. Increasing the polling interval causes the server to use less CPU and network resources for SNMP polling, but it makes the currently shown printer status (for printers that are not currently printing) less accurate. Once this process has found the device to be functional again, IPM re-enables the AD and returns the AD to the list to be polled at the normal interval. This applies to devices with which IPM has actively had problems. It does not apply to situations where IPM has lost or not yet established communications. GUI label: Problem poll interval (sec) The unit of measure is seconds. Default: 60 (seconds) Value can be 0 (disable problem polling), upward. The value is conventionally half or less than the snmp-normal-poll-interval value, so as to get printers back into service quickly following resolution of their problem (paper empty, etc.). See also: snmp-normal-poll-interval snmp-retry-count Specifies the number of times, after an initial failure, that IPM should attempt to establish SNMP communication with the printer device that this AD represents. GUI label: Number of times to retry Default: 2 A value of 2 is usually way too low: you want a value which, multiplied by the snmp-timeout value, covers the amount of time it would take for an operator to realize that a printer is out of paper and reload, as a common outage case. But you don't want a retry value so high that IPM server time is wasted trying endlessly to contact a printer which is turned off. See also: snmp-timeout; 5010-849 snmp-timeout AD attribute specifying the number of seconds that IPM should wait for SNMP operations on the printer device that this actual destination represents to complete. This is the number of seconds on each attempt, rather than a cumulative value for all attempts. Is in effect only if use-snmp is TRUE. GUI label: Timeout (sec) Value 0 causes use of the SNMP default timeout period (5 seconds). Advice: A value of a few seconds is too small, and will cause perplexing red icons with 5010-849 messages. Note that, with PostScript printing, SNMP is employed as usual to get status information from the printer, as needed; but print job progress is via job stream channel PJL interaction with many such printers, utilizing the pioibmnpm or pioinfo backends. See also: snmp-retry-count; use-snmp snmp-trap See: java Software levels, in AIX For the basic product: 'lslpp -ql ipr.\*' Oddly, the key pdserver binary contains no embedded version level to inherently identify its level. You can do 'lslpp -L all' to report all software on the system. Sonoran Font family, proportinally-spaced. As used with the 3800 Model 3, circa 1984. spacewatch.ksh This is a cron-initiated shell script to check for IPM file systems getting full. In IPM 4.1, checks the following: FILE SYSTEM BLOCKS THRESHOLD /var/pd 16384 /var/psf 8192 /var/psf/segments 16384 /ipdata 16384 Dir: /usr/lpp/InfoPrint/install/bin/ The root crontab is altered at IPM install time to append this task. Runs at 21:00 (only - once a day!). Note that file system filling is detected by AIX, and would be logged in its Error Log (review with 'errpt' cmd). A site would probably want to run their own, thorough monitoring instead of this faint task. Spacing Term meaning to move from page to page within a job. May require use of SNMP. Ref: Procedures manual, "Setting up high speed printers for spacing" spl_trace.cfg See: Server trace Spooler An informal name for the IPM server. The spooler is actually one of the three major elements in the IPM server (command processor, spooler, supervisor). SpoolID A ten-digit tracking number: First 5 digits: ??? Last 5 digits: sequential number SQL interface? No, the IPM jobs "database" has no SQL interface - just commands. Stacking See also: Jog; Offset stacking allowed? Standard Bin Common terminology for the topside output bin in a workgroup printer, being a simple cavity at the top of the printer into which output sheets are dropped. There are no sensors in such a bin, so the printer cannot know how many sheets are (still) in it, hence its Level is usually reported as Unknown. Standard server environment When you install the Infoprint Manager Server, without the Print-on-Demand Feature, a standard printing environment is created. This environment is generally appropriate for data center printing or distributed printing of many different types of data (including ASCII, ditroff, GIF, JPEG, PCL, PDF, PostScript, and TIFF data). Print jobs in the standard environment often consist of billing statements, payroll statements, and application forms. Users submit these jobs from a command line, a workstation application (such as a word processor), or an Infoprint client (such as Infoprint Select). In a standard printing environment, Infoprint Manager assigns jobs to printers through late binding: they are bound to a destination when one becomes available to serve tje job. Contrast with: Basic server Staple position, best 1L Vert L (as defined in printer) to staple in upper left portrait corner Staples exhausted in IPDS printer /var/psf//error.log message: 0424-197 Stapling Will often be controlled at the printer itself, as a default action, as for PSF Command printing. See: Corner Staple Angle; FINISH Stapling, 2085/2105 See: Infoprint 2085/2105 stapling Stapling, in PostScript printing Where printing is to a PostScript printer (rather than an AFP/IPDS printer), stapling is controlled per the PostScript in the submitted job; it cannot be governed by print server settings. (There is no stapling control parameter in the IPM job/document parameters, and thus no way to cause PJL statements such as @PJL SET FINISH=STAPLE @PJL SET STAPLEOPTION=ONE to be sent to the printer in front of the job, in pioibmnpm command processing. The printer may observe DSC comment: %%Requirements: staple Stapling, IPM The job-finishing attribute. Can be controlled, in IPDS, via a formdef, where such a definition on the LD would override the formdef at the AD level. The IBM AFP driver for Windows provides the ability for the end user to supply a formdef. GUI: Job and Document Defaults, Job General tab, Finishing options GUI: Job and Document Defaults, Document Processing tab, Output bin requested, select Stapler Attributes (job-finishing, job-finishing-supported): edge-stitch (finisher default) edge-stitch-2 (two staples) edge-stitch-3 (three staples) edge-stitch-bottom edge-stitch-left edge-stitch-right edge-stitch-top staple-bottom-left staple-bottom-right staple-top-left staple-top-right See also: job-finishing Start sheet Aka "Separator page". GUI: Element of Printer Properties, Auxiliary/Separator Sheets tab. Possible values: 64xx blank brief full <--- default job ticket none The Full style cause the following fields to appear on the page: PROGRAMMER NAME DEPARTMENT BUILDING ROOM ACCOUNT ADDRESS SPOOLID PRINTER (the physical printer name) (The values correspond to "____-text" attributes, such as "name-text".) Such data should come from data supplied when the print command was invoked. See the Reference manual chapter "The -o Flag for AIX Print Commands". See also: Auxiliary sheets allowed; End sheet; Slip/Separator sheet; User exits start-message-supported AD attribute: Indicates whether the AD supports the job attribute job-start-message. Operators can receive messages that users specify with the job-start-message job attribute when they submit the job. GUI label: Send job start message See also: end-message-supported Start-up, discover printers Server property: snmp-discovery-during-startup (q.v.) Environment variable: PD_ENABLE_TIMEOUT Start-up, server See: Server, start started-printing-time Job/Default Job attribute reporting "the time when IPM sent the job to the output device". Based upon observed reality: For basic IPM printing, this is when the job begins toward printing, thus reflecting when it entered into transform processing (which is tied to a printer), and right after that would be eligible for printing, when a printer is free and available. In rip-and-hold processing, this initially reflects when the job went to transform: later, when the job is released, this attribute is updated a second time to reflect its commitment to printing, which may be 1 second after it was released to print. GUI label: Started printing Format: HH:MM:SS mm/dd/yy See also: completion-time startipmmi See: IPMMI startippgw IPP Gateway command to start it. /usr/lpp/pd/bin/startippgw Linux syntax: startippgw [-p ListenPort] [-t Number of Threads] [-h Pdhost] [-s Pdsocket] See also: IPP Gateway; lsippgw; stopippgw startlpd IPM command to start the LPD Gateway. /usr/lpp/pd/bin/startlpd There are no command line options. Starts the special IPM LPD daemon on the standard port 515 ("printer"). Does not record the PID anywhere (nothing in /var/run/). See also: stoplpd startnotd /usr/lpp/pd/bin/startnotd Utility to start the notifyd daemon. Usual message: 5010-405 Successfully started server notifyd. No harm in repeating: 5010-618 The server notifyd is already operational. (status code 1) IMPORTANT: See notes under "Java". See also: notifyd daemon; stopnotd startsrv Command to create or restart a server. /usr/lpp/pd/bin/startsrv is a ksh script. As invoked through /etc/rc.pd.servers . 'startsrv [-c] [-F] [-l] locale [-p] port [ServerName]' -F Suppresses prompting, as when running in the background. In AIX it does: - Do 'ulimit -d 2048000' to set that Unix Resource Limit for memory data. - Save trace.log.BAK file (compressed) - Start the pdserver process - Assure that the ps2afpd's are running - Assure that the NPM server is running - Assure that pcl2afpd is running - Assure that psfapid is running - Wait for the server to fully come up Note: Does not start notifyd - that needs to be started independently. Caution: IPM provides no means for shutting down all IPM processes - all it provides is the 'stop_server' and 'pdshutdown' commands, which terminate only the pdserver, leaving all affiliated processes up. This is no good, as one or more of the affiliated processes may be damaged such that starting a fresh instance of pdserver with old affiliated processes can result in inscrutable instabilities. You would be wise to implement a site shutdown script which will terminate all IPM processes such that all processes start fresh. See also: pdcrdflt; Shut down IPM Status Column in GUI Jobs display. Attr: job-state-reasons Usual sequence: pending ripping As in PostScript to AFP transformation. processing Includes IPDS to PCL transformation for PSF Command AD. Held jobs: May be due to the operator having caused the job to be held. This will show up in job properties, with field "Last modified by:" showing the operator rather than the file owner (reflecting initial submission). Also might be: held The operator has put the job on hold. rip failed Sometimes a truncated file sometimes a job created with a driver for a different printer (incompatible due to device dependent specs) See also: Check Status; rip failed Status Column in GUI Printers display. Attr: destination-state (q.v.) STD The PostScript key name for the main output tray of an Infoprint 32/40 printer. Sample PostScript: << /OutputType (STD) >> setpagedevice See also: MAIN; UPPER STM Sense Type and Model, IPDS command. Presumably, the /var/psf//stm file reflects this. stopippgw IPP Gateway command to stop it. /usr/lpp/pd/bin/stopippgw See also: IPP Gateway; lsippgw; startippgw stoplpd IPM command to stop the LPD Gateway. /usr/lpp/pd/bin/stoplpd There are no command line options. See also: startlpd stopnotd /usr/lpp/pd/bin/stopnotd Utility to stop the notifyd daemon. Usual message: none No harm in repeating: no msg, status 0 See also: notifyd daemon; startnotd submission-time Job attribute: Identifies the time that IPM added the job to the queue for processing: the latest submission timestamp. GUI label: Submit time DSS: All Infoprint sets this value using the local time format. The USA format is "HH:MM:SS mm/dd/yy". submission-time will equal creation-time when the job arrives. If the job is later reprinted (move job), the job will receive a new submission-time. Note that in lpr printing, there will be no surviving timestamp of when the job was queued in any prior spool areas before reaching IPM. For example, a user on an AIX time-sharing system performs an lpr of a print file in their home directory, which spools to the AIX print queue. But that AIX system's definition for the IPM destination is in a DOWN state, and stays that way for several hours until an AIX administrator notices, upon which the destination is enabled and the job finally flows to IPM. There will be no indication in the job attributes of the job's lingering stay on that AIX system. See also: completion-time; creation-time; started-printing-time Submitted to GUI: Column in Jobs listing, reflecting the logical destination to which the job was submitted. Submitter Identified on attributes: user-name job-owner job-originator results-profile Subpage A subset of a Pagedef page format, which is a set of PRINTLINE commands bounded by either an ENDSUBPAGE command or, if ENDSUBPAGE is not used, then the whole page format. Subpages are used only with conditional processing. SUBPAGE PPFA: Element of a CONDITION for operating on a subpage. SWP Simple Web Printing proposal from Microsoft and HP. The PWG was submitted to the IPP group in May and was extensively discussed in a PWG IPP meeting in San Diego on May 15, 1997. The intention with the proposal was to define a leaner subset of IPP, based on the IPP Model & Semantics. After rather intensive discussions, features from the SWP proposal are now integrated in the overall IPP solution. In the process, the group decided to restructure some of the operations and to make some of them optional, but it should be noted that the SWP was never intended as an alternative or competing solution to IPP. SYS1.FDEFLIB The name of the MVS/OS390 partitioned data set housing forms definition objects for Advanced Function Printing (AFP). Corresponds to Unix directory /usr/lpp/psf/reslib/. SYS1.FONTLIB The name of the MVS/OS390 partitioned data set housing font objects for Advanced Function Printing (AFP). Corresponds to Unix directory /usr/lpp/psf/fontlib/ T1...... AFP font code pages. Installed in: /usr/lib/font/devafp/ See also: Ditroff T1001038 AFP font code page, where '1038' = registry number for DITROFF SYMBOLS (SG font only). T1001108 AFP font code page, where '1108' = registry number for DITROFF BASE (used for all fonts but SG and SS). T1001109 AFP font code page, where '1109' = registry number for DITROFF SPECIALS (SS font only). Tape dump utility 'tdump' TCRU Trained customer replacement units, introduced in late 2009 on the InfoPrint Pro printer series, to allow customers to replace parts that commonly wear out (as has been possible on workgroup printers, via Maintenance Kit modules). Terminating transform See: Transforms Msgs: 5010-507 Job completed due to terminating transform. terminating-transform Transform property for whether or not to send the job on to output through the DSS backend, or to simply stop after the transformation. GUI label: "How to process jobs", with choices "Transform only" or "Transform and print". To quickly change the property value, use the command: pdset -c transform \ -x "terminating-transform=true" \ ${HOST}:TransformName If true, and job-rip-action=rip-and-hold then submitted jobs will *not* go into a ripped-held state: jobs will instead transform and transfer into the Retained Jobs area in a status of "completed" (as opposed to "completed successfully", as when a job to actually go on to print). Status of completed jobs: With "Transform and print", the Status of a completed job will be "completed successfully". With "Transform only", the Status of a completed job will be just "completed". /var/pd//accounting.logs/* will contain entries for such jobs, but the page and octets counts are zero. The /var/psf/jobcompletion.log will not have entries for such jobs because they did not reach the AD. See also: conditional-terminating-return-code Tesselation See: AFPDS TIFF TIFF transform /usr/lpp/psf/bin/tiff2afp Timeout See: intervention-timer; job-submission-timer Timeout (sec) GUI label for snmp-timeout (q.v.). Timeout, job submission Server property: job-submission-timer Timers and timeouts destination-timeout-period When a job is ready to print on the printer, how many seconds IPM will try to connect to it. When that expires, the printer state is set to timed-out, though IPM continues to try to connect to the AD. If this timeout is reached, destination-state=timed-out (AIX and PSF Other devices only). connection-timeout For TCP-connected ADs, is the amount of time that IPM waits before it stops trying to communicate with the AD when it cannot make a connection. Default: 30 Set 0 to be ignored. intervention-timer The max seconds that IPM waits before it treats an AD intervention-required condition as a permanent error. Default: 9999 snmp-timeout The number of seconds that IPM should wait for SNMP operations on the AD to complete. Default: 5 /tmp/,_notif.msg Like: /tmp/,prtsys_notif.msg IPM server notifications prep file, in constructing the email-based message to be sent back to Infoprint Select, for example. File contents are like: To: someuser@[111.222.333.444] Subject: 5010-192 Message from Infoprint server: prtsys -------- [11/30/04 07:46:08] 5010-071 Job name Microsoft Word - Earlev[1].Fiske.doc with ID 2 (prtsys:5395401684) completed successfully on printer2. The file is left in place, with its contents from the last notification processed, to be overlaid when the next notification is processed. total-job-octets Job attribute: The size of the job, which is the sum of all printable octets (bytes) in the job. transfer-method The method by which IPM transfers the document to the print server. GUI label: Transferred to server Possible values: with-request pipe-pull Transform In IPM, a Transform is a software process which converts a non-AFP file format such as PostScript, PDF, and TIFF into MO:DCA such that the document can be handled by AFP and IPDS, for output to a device of that architecture. A key concept is that MO:DCA encodes the processing in sequential order, allowing the output device to most efficiently rasterize the image. This contrasts with PostScript, which jumps around the page as it renders the page, placing fonts and imagery according to its own optimum methods. In implementation, an IPM transform may be as simple as vanilla execution of the ps2afp command, or it may identify a customer executable written to perform more extensive processing, such as embedding a header sheet into the job. A transform-time restriction is that the attributes of the job being transformed cannot be changed, because that job is active in processing. See also: transform-sequence Transform, change attribute 'pdset -c transform -x :' For example, to change from "no printing" testing mode back to printing, do the following: 'pdset -c transform -x 'terminating-transform=false' myserver:PStransform' (There is no need for a pddisable, pdenable sequence around the pdset.) Transform, do not print See: terminating-transform Transform, list attributes 'pdls -c transform : -r all' Transform and print IPM admin GUI label for the Transform property terminating-transform, where the transform transform and also print the job, which is the customary and productive setting. Contrast with: Transform only Transform arguments See: other-transform-options Transform debugging Some PostScript or PDF jobs are defective and will fail to RIP. Unfortunately, IPM's RIP simply will not tell you exactly where the problem is, and so you cannot advise the document author of same. The only clue which IPM provides as to the location of the problem is either: 1. In the ps2afp.log, where it will tell you how many pages it successfully generated before coming upon the page with the error, like: "Wrote 2 pages of output..." 2. Or, you can do like 'ps2afp -o /tmp/the.afp job.ps' and then do 'afpdmp /tmp/the.afp | grep PAG' to get the successful page count. Transform identifier See: transform-identifier Transform Manager Short for the InfoPrint Transform Manager for Linux Transform only IPM admin GUI label for the Transform property terminating-transform, where the transform should only transform, and not also print the job. This is useful in the development of a new or changed transform. Contrast with: Transform and print Transform options See: other-transform-options Transform progress Sometimes there will be a "tough RIP" job and you want to know how far the transform has gotten in processing the job. If you do 'ls -alt /var/pd//' you will see a most recent, changing file whose name extension is _xfm1 (e.g., pdprvRtkiT_xfm1). That would be the AFP output file from the transform. You can then do the following on it: afpdmp pdpr......_xfm1 | grep BPG which will reveal page numbers. Transform Sequence Powerful IPM capability which allows you to define what happens in a transform, in one or more sequential steps. Ref: Procedures manual, "Defining a transform sequence". See: transform-sequence transform-identifier Transform attribute: Uniquely identifies a transform...names the transform. For example, for Infoprint XT, the transform-identifier is set to "x2afp". Note that the transform-identifier is not seen in the Transforms portion of the GUI: it is implicit in the names of the transforms, as appear in the top bar of windows which display transform properties. transform-sequence Server attribute to select one or more of the pre-defined transform sequence programs, to be run in the order listed. GUI label: "Transforms to use" DSS types: all (All DSS types nicely support transform sequence operations on the job before it is printed, allowing you to tailor it as appropriate.) Every job that is submitted to that AD is sent through the processing sequence. The names in the sequence identify separately defined Transforms that you have set up, representing executable programs which do what you need, such as running ps2afp and reacting to its results. (Transforms are perhaps ideally written in Perl, which is excellent for invoking such external commands.) Without any transform sequences specified, IPM will fully handle transformation according to the nature of the AD; but if you get involved, it is then up to you to specify all transformation operations yourself, for all page formatting methods (PCL, PostScript, etc.). In job-rip-action=rip-and-hold processing, the transform sequence is invoked only when the job enters the queue: it is not invoked (again) when the job is released to print. Exit codes (return codes): The spectrum of return codes is very small. When your transform program completes, it should exit with an indicative number: zero Success indication: IPM goes on to print the job. non-zero Failure indication: IPM discontinues processing the job, and leaves it in the pending queue, in state "aborted by system". (Non-zero numbers are 1-255. -1 = 255.) The number may also be that defined via conditional-terminating-return-code, indicating success but preventing subsequent printing. The transform names are defined to the server, with attributes defining the particulars, including the full path to the actual executable. Transforms IPM transforms PostScript, PCL, PDF, and various other incoming data streams into AFP. (IPM provides no customer-invocable transforms to go from AFP to other.) The input to a transform is a pre-existing file that IPM has created. Customization: Via each transform's configuration file. Daemon requirement: The PCL, PostScript, and PDF transforms all require a daemon to be running before you can use them. Transforms are defined via the GUI Server menu, and are used per the AD properties Configuration tab, "Transforms to use". In the transform definition, the "Transform options" line may specify an IPM transform utility, or your own program - and you may redirect Stdout, which is useful for capturing debugging print statement output in /tmp, for example. If IPM is to continue to print the output of the "transform", the file must have the expected name provided via the %o variable. A "terminating transform" is one which does not require IPM to go on to print the job. It must be the last in the list of transforms for the AD. The /var/pd//accounting.logs/* will contain entries for such jobs, but the page and octets counts are zero. The /var/psf/jobcompletion.log will not have entries for such jobs because they did not reach the AD. A "non-terminating transform" is one which wants IPM to go on to print the job. Notes: - Environment variables like HOST may not be dependably set. Typically, the environment variables that are set are those defined in /etc/environment. See also: other-transform-options; Transform options Transforms, list all 'pdls -c transform :' Transforms, list one 'pdls -c transform :' Transforms, list attributes of all 'pdls -c transform : -r all' Transforms, list attributes of one 'pdls -c transform : -r all' Transforms directory As a transform program starts, its current working directory (cwd) is /var/pd//. Its workfiles will end up here unless other steps are taken. "Transforms to use" GUI: AD properties Configuration tab. Attr: transform-sequence See: Transforms See also: transform-identifier Tray mapping See: Media ready Trialing software As of IPM 4.4, you can trial software for 60 days. There is no special action you have to take: you simply install and start using the software, where everything in it works. After 60 days - plus 7 days grace period - it goes dormant: you can buy a license key and anytime thereafter reactivate it. TRC Table Reference Character, for traditional carriage control printing. The carriage control appears in the first column of each data record, and the TRC in the second. Tumble duplex printing Printing on both sides of the paper, placing output images on the media in a head-to-toe format, so that the top of one image is at the same edge as the bottom of the next image. "Head over heels" printing... When you flip a portrait page, hinging on the top, short edge, the other side will appear upright - which is NOT what one wants for usual book publishing, where the binding is along the long edge. Ultra high speed printer Printer type classified as printing 1500 ppm or faster. Previous: High speed printer Next: none Units of measurement in PPFA Inches (IN), millimeters (MM), centimeters (CM), points (POINTS), or pels (PELS). Ref: PPFA User Guide manual, Chapter 8. PPFA Command Syntax, "Units of Measurement". Universal Laser Printer PS3 The PostScript driver name from IPSC's "InfoPrint 15xx/16xx/17xx PCL/PostScript Universal Drivers Version 1.6" package, on the IBM site as document P4000924. When adding a printer in Windows 7, in the "Install the printer driver" step, it should be under "Generic Printers" as Universal Laser Printer PS3. The resulting PostScript carries the OEM identifier "Lexmark Universal PS3". Universal Print Driver for Windows PCL5e and PostScript driver for all current versions Windows, to work with IBM workgroup Infoprint printers (1145 to 1585). See IBM document number P4000601. As of 2007/12, the English download file is: printer_ud0_2kxp03vista_drivers_en.exe The resulting driver Model Name is: "Universal Laser Printer" Unquoted-name See: User-access name .upr Filename extension for UNIX PostScript Resource files, as used for font incorporation by Adobe Acrobat Reader. The .upr files are created when Type1 fonts are installed. UPPER The PostScript key name for the proof output tray of an Infoprint 2085/2090/2105 printer. Sample PostScript: << /OutputType (UPPER) >> setpagedevice See also: MAIN; STD Usage Kit After printing something like 300,000 impressions on an IBM Infoprint workgroup printer, parts need to be replaced by the owner. These parts are obtained in a Usage Kit which, depending upon the design of the printer, consists of some combination of the following parts: Fixing assembly Fuser Bias Transfer Roller (BTR) assembly Feed roller set Pickup rollers Separation rollers Expect to pay $350 or so. Also known as Maintenance Kit. After replacement, there is allegedly a procedure to reset the maintenance counter: where or what that is, is unknown and unfindable. "Use default" If this is specified for an "upstream" attribute, the next specific "downstream" attribute causes that value to be used. That is, if a job, logical destination, and physical destination's values all indicate "don't care", then settings in the printer prevail. "Use remote print queue" Actual Destination properties, Configuration tab setting. See: remote-queue use-snmp AD attribute indicating whether IPM should attempt SNMP communication with the designated output device. GUI label: Use SNMP Enter one of: true (yes); false (no) If IPM fails to establish SNMP contact with an output device, it uses the ping command to test whether it is possible to communicate with the device in other ways. If the ping command succeeds, IPM concludes that the device is there but is not an SNMP device and resets this attribute to false. User exit A user exit is the vendor-sanctioned opportunity for the customer to carefully add their own software extension to the IPM server. Things to be aware of: A user exit inherits the server's open file handles, which the customer code must be careful not to interfere with. Avoid creating subsequent processes in user exits (definitely avoid using system() in user exists, for example). Ref: Procedures manual User exit samples (source code) /usr/lpp/psf/exits/ But they are meager. User exits In print file processing order: - Header (Start) page user exit. Generates page in AFP format. ainuxhdr.c Brief style. ainuxhdr2.c Full style. ainuxhdrp.c With job ticket info (POD). ainuxhdrx.c No vertical lines (64xx). pduxblkh.c Blank start sheet. GUI: Printer Properties, Auxiliary/Separator Sheets tab, Start sheet - Separator page user exit. Generates page in AFP format. ainuxsep.c Brief style. ainuxsep2.c Full style. ainuxsepp.c With job ticket info (POD). ainuxsepx.c No vertical lines (64xx). pduxblks.c Blank separator sheet. GUI: Printer Properties, Auxiliary/Separator Sheets tab, Slip/Separator sheet - Input data user exit. Default: None specified, no selection list in GUI. ainuxind.c Provides template for writing your own user-exit program. GUI: Printer Properties, "Customize" tab, where you have to type in the name. - Output data user exit ainuxout.c Provides template for writing your own user-exit program. GUI: Printer Properties, "Customize" tab, where you have to type in the name. - Accounting user exit To print an accounting sheet. ainuxacc.c Brief style. ainuxacc2.c Full style. ainacclog.c Accounting log info. (Not what appears in /var/pd//accounting.logs/) ainuxaccp.c Accounting sheet log with job ticket info (POD). GUI: Printer Properties, "Customize" tab - Audit user exit ainuxaud.c Brief style audit sheet. ainuxaud2.c Full style audit sheet. ainuxaudp.c Audit sheet with job ticket information (POD). ainaudlog.c Audit log information. GUI: Printer Properties, "Customize" tab - Trailer (End) page user exit Generates page in AFP format. ainuxtlr.c Brief style end sheet. ainuxtlr2.c Full style end sheet. ainuxtlrp.c No job ticket info (POD). ainuxtlrx.c No vertical lines (64xx). pduxblkt.c Blank end sheet. GUI: Printer Properties, Auxiliary/Separator Sheets tab, End sheet - Post-print accounting user exit ainuxjobcompletion.c Accounting log info on printed ("stacked") sheets. The ainuexit.h file contains function and structure declarations for the user exits. Testing reveals that the user exit is reloaded each time. In IPM 4.4 Linux, there is no Linux tailoring in the user exit source files: they still have "#ifdef AIX", which ostensibly covers Linux as well. Ref: Procedures manual See also: accounting-exit User exits data structures /usr/lpp/psf/exits/ainuexit.h User exits directory (executables) /usr/lpp/psf/bin/ User exits header files /usr/lpp/psf/exits/ainuexit.h User exits source /usr/lpp/psf/exits/ User group for IPM? Nope. Unlike other major IBM products (such as TSM), there is no user group or mailing list for IPM. In the IPM 4.2 announcment, IBM talked of an "Infoprint Manager Roundup - a users group for the customers of Infoprint Manager", saying that they would have roundups through 2005...but there is no sign of that having occurred. User-access name PPFA: The structured name of the resource to be included in processing, typically being a 1-6 character name. The actual file system object name is longer: PPFA adds the appropriate prefix to the user-access name (for example, F1 for form definitions, P1 for page definitions, O1 for overlays, S1 for page segments) to match the library resource name. Also known as Unquoted-name. See also: SEGMENT user-locale Job attribute for the locale. Like: en_US.ISO8859-1 user-name Job attribute identifying the job submitter. Is of form Username@Hostname. This attribute is established at job creation time and cannot be modified. See also: job-originator; job-owner; results-profile /usr/lib/lpd/pio/predef/ AIX Predefined Database (library) directory containing predefined printer attribute files (sometimes called "colon files" due to the heavy use of that character in the files). Comes with a basic repertoire (Generic, HP Laserjet, IBM 23__, IBM 40__). Vendors (Lexmark, IBM Infoprint) may add their own definitions to this library. For example, the Infoprint 2085/2105 PCL and PostScript Device Driver adds ibm2085* and ibm2105* files. These files may be referenced in AIX or PSF other-driver attached ADs. Ref: AIX doc "Printer Colon File Conventions" See also: Colon Files; destination-model; lsvirprt; mkvirprt; piopredef /usr/lpp/Infoprint/install/core Seems to be created when you are in a 'setup' feature install and do View Installation Features Log (which shows the /usr/lpp/Infoprint/install/ipm.ini file under Text Editor), and also when you exit Text Editor. /usr/lpp/Infoprint/install/ipm.ini See: Options installed /usr/lpp/pd/ Directory created by the IPM install, containing bin and lib subdirectories. /usr/lpp/pd/bin/ic70hdr.ps PostScript header page for the IBM infoColor 70 printer. /usr/lpp/pd/bin/ic70hdr.ksh, invoked with arguments: 1. File name for composite start sheet. 2. Job name 3. Global Job ID 4. Job Client ID 5. Comments 6. Job submitter processes this page to fill in the following Job Start Sheet fields: Job name: Global Job ID: Job Client ID: Comments: Job submitter: /usr/lpp/pd/jre/bin/java The Java which IPM 4.2 uses, as of PTF 5, instead of /usr/java14/jre/bin/java. See: Java /usr/lpp/psf/bin/ Home of all the ainu* user exits and various transform commands. /usr/lpp/psf/bin/ps2afpi The PostScript/PDF-to-AFP interpreter (transform). See: ps2afpi /usr/lpp/psf/exits/ Contains sample user exit modules. /usr/lpp/psf/fontlib/ Directory containing actual fixed-size fonts, named C0*, as referenced by small X0* files in /usr/lpp/psf/reslib/. Use 'afpdmp' to inspect. Corresponds to MVS/OS390 partitioned data set SYS1.FONTLIB. /usr/lpp/psf/ps/ The PostScript source materials for the product. The .ps samples provided in the directory represent tests created by the developers as they had to work with various PostScript printers, and in testing the Adobe PostScript transform in IPM. In particular, the greyscale.ps test file can be used to demonstrate the disparities in gray scale imaging across brands and models of printers, as to how a given percent gray is inconsistently portrayed. /usr/lpp/psf/ps/adobeFonts.tar Package of fonts supplied by PTF U811589 (November 2007) providing Chinese, Japanese, and Korean font package provided by Adobe. /usr/lpp/psf/ps/align6x9.ps PostScript test file: a 6" x 9" sized set of 16 pages with a set of four perimeter lines around all four edges, for testing the printer's page image alignment. /usr/lpp/psf/ps/align8.5x11.ps PostScript test file: a US Letter sized set of 16 pages with a set of four perimeter lines around all four edges, for testing the printer's page image alignment. /usr/lpp/psf/ps/fonts/ PostScript Type 1 outline fonts, as installed with IPM. Mapped by file /usr/lpp/psf/ps/psfonts.map /usr/lpp/psf/ps/greyscale.ps PostScript test file: a US Letter sized set of three pages containing 10%, 5%, and light PS greyscales, intended for comparing the greyscale performance of various printers. /usr/lpp/psf/ps/greyscale1.ps PostScript test file: a US Letter sized page containing 10% gradation PS greyscales, intended for comparing the greyscale performance of various printers. /usr/lpp/psf/ps/grid.ps PostScript test file: a US Letter sized set of 2 pages containing simple grid patterns in the upper area of the page. /usr/lpp/psf/ps/multipage.ps PostScript test file: a US Letter sized set of 4 pages providing four samples. /usr/lpp/psf/ps/onepage.ps PostScript test file: a US Letter sized page containing a text spiral, for testing transform speed. /usr/lpp/psf/ps/psfonts.map File listing the IPM PostScript fonts. /usr/lpp/psf/ps/sample.ps PostScript test file: a US Letter sized page containing a radial text strings. /usr/lpp/psf/ps/sample1.ps PostScript test file: a US Letter sized set of 15 pages of text, for testing ordinary printing of a job of some size. /usr/lpp/psf/ps/tiger.ps PostScript test file: a US Letter sized page containing a growing tiger's head, in color. /usr/lpp/psf/ps2afp/3160d.cfg PostScript-to-AFP configuration file for the Infoprint 60 (3160 machine type) and Infoprint 4000 printers. /usr/lpp/psf/ps2afp/ps2afp.cfg Config file for the 'ps2afp' command. Note that if "device_controls" is uncommented in the file, then an inline Resource Group named INLINERS will be generated ahead of the AFP for the document itself, allowing document processing to reference Medium Map names to effect paper tray selection, stacker offsetting, etc. according to what's coded in the PostScript. See also: F100APS /usr/lpp/psf/reslib/ Standard IPM Formdefs (F1*), Pagedefs (P1*), and Coded Font files (X0*). Note that these files conform to AFP historical conventions - which in particular means that they are in EBCDIC! Thus, you cannot 'grep' for strings in these files. Use the 'afpdmp' command to inspect contents, which displays them in ASCII. Permissions: The directory must have r-x privs for owner, group, and other. All files in the directory must have r priv for owner, group, and other. (You would expect that IPM, running as root, would certainly be able to access directory files having r-xr-x--- privs, but such is not the case: it would result in an error page being printed instead of the job, reporting 0420-128 error condition.) See also: ASCII fonts /usr/share/cups/model/ In IPM for Linux, this directory will house all the PPD files which you put there to support CUPS DSS printing. You can get such PPDs from site www.openprinting.org/printer Ref: IPM for Linux - Getting Started (search PDF for "cups/model" due to the string spanning lines) Utilities provided with IPM In /usr/lpp/psf/utils/. ibmafp lpr Sample C program to submit job to LPD. npf psfop reblock /var/pd File system created by install. This is the IPM spool area, where jobs arrive when submitted (as pdpr* files), and where they stay after printing per Logical Destination retention periods, until they finally expire and are deleted. If this file system fills, the pdserver process crashes. Your AIX GUI will produce Xwindows error "ava.io.IOException: There is not enough space in the file system." /var/pd/acl/ Directory containing the (binary, encrypted) security files deposited at install time, and seemingly serve as the defaults for setting up new instances of the server. Contains ACL (.acl) files for the pd* commands, plus directory "group", housing security group definitions. They are replicated into /var/pddir/default_cell/acl/ as the runtime security files. /var/pd/acl/groups/ Directory containing the (binary, encrypted) security files deposited at install time: acl_admin admin oper See also: /var/pddir/default_cell/acl/groups/ /var/pd/gui/ GUI files... heapdump*, javacore* These are some kind of Java failure data capture files. Can delete. ipgui_pa.cfg Administration GUI file. /var/pd/notifyd/ The directory in which notifyd logs its start-up and uses for traces and dumps. If you see error.log and error.log.BAK* files frequently refreshing in that directory, it indicates that notdmon is hopelessly trying to restart notifyd, and cannot due to some issue in pathing or other. The repeated restart attempts will also result in a horrendous build-up of named pipe files in directory /var/psm/.notifyd/. In such case, kill notdmon until you can succeed in manually starting notifyd, and thus have resolved its start-up issue. /var/pd//.0. Job Script file, existing when the job .js of that number is in Processing state. Each such file is around 150 bytes in size. Sample contents: i_InputDevice=file i_Filenames=/var/pd/acsrs6/pdpr1Yypn3_xfm1 %/.1.js Job Script file, existing when the job of that number is in Processing state. Each such file is around 150 bytes in size. Contents are like: JsFileType=MODCAP p_Resolution=600 oa_Formdef=F1BUDUNS i_filenames=/var/pd/sys3/pdpr1Yypn3_xfm1 i_OutExit=/usr/lpp/psf/bin/afpReorder -fltr -nostrp /var/pd//accounting.logs/ Directory containing the accounting logs for each AD. See: Accounting data, log; Accounting log; accounting-exit; pdaccount; log-accounting-data /var/pd//debug.tar.Z See: pdcapture /var/pd//error.log Server error log. When the server restarts it creates a backup of this file. See also: Error log, server /var/pd//cfjava.log.0 Purpose unknown. Seems to be a log reflecting activity in getting info from printers via SNMP. Is ostensibly written by the java process which runs under the pdserver process, but this is difficult to verify, as the file is not kept open. Notes on content: - Timestamps in this log are GMT rather than local time! Thus, times seen in the log will be 5 hours later than EST. - Network device addresses are logged as dotted decimal IPaddrs rather than host-domain names. - Whereas for SNMP, you will see a bunch of OID numbers in the log. /var/pd//pdb/ The Print DataBase directory. Contains MIB files which catalog all aspects and object settings in the product. Subdirectories: aux_sheet document error_log iv_doc iv_job log_printer Logical destinations. medium phy_printer Actual destinations. proxy_document psf_resource queue res_context spl_job Timestamps on the control files in this directory reflect the most recent job event or the last IPM server restart, rather than simply job arrival time. spooler suv_job suv_phy_printer trace_log transform /var/pd//pdb/document/ IPM server directory containing control information for each submitted job document, whether the job is pending, current, or retained. Filename sample: 0259728282.1 where the suffix indicates that the file is the first document of the job. Each file is ASCII, about 1760 bytes in size, containing OIDs stanzas, where each stanza holds a job attribute. OID 1.0.10175.1.3.1.89, for example, holds the document-file-name attribute string. The mtime timestamps of the files in this directory match the modification-time attribute value. (The file timestamps do not change as IPM is restarted, etc.) The contents of this directory shall always be consistent with the contents of /var/pd//pdb/spl_job/. /var/pd//pdb/iv_doc/ Directory containing the attribute files for each LD document initial value, meaning document defaults. /var/pd//pdb/iv_job/ Directory containing the attribute files for each LD job initial value, meaning job defaults. /var/pd//pdb/phy_printer/ See: Physical destination files /var/pd//pdb/queue/ Directory containing the attribute files for each queue. /var/pd//pdb/spl_job/ Directory containing OID files for all jobs, the directory entry names being GlobalID numbers. The contents of this directory shall always be consistent with the contents of /var/pd//pdb/document/. The timestamps of the job-numbered files in this directory change as IPM management of the directory occurs: when IPM is restarted, the mtimes of the files will reflect that time. So do not try to use this directory as a reference as to when jobs arrived: the directory /var/pd//pdb/document/ is a better reference for that. /var/pd//pdb/suv_job/ Directory containing OID files for currently active jobs (those whose status is processing or printing), the directory entry names being GlobalID numbers. Jobs which are held or pending are not reflected in this directory. /var/pd//pdb/spooler/ Server attributes file. /var/pd//pdb/ Houses AD progenitor definition files. suv_phy_printer/ Note that when an AD is defined, it not only gets created in this directory, but also /var/pddir/default_cell/printers/. The associated phy_printer directory then gets a working copy of these files. It appears that suv_phy_printer is the permanent repository of physical printer definitions and that phy_printer is a working set, recreated at server restart. See also: Physical destination files /var/pd//pdcf* Ephemeral control file, purpose unknown. Sample name: pdcfOHEeU5 /var/pd//pdjobs Text file reflecting the current state of the server's in-memory assignment of simple-integer local job ID numbers to 10-digit Global ID numbers, per submitting user. (IBM has thus far not made information about this file available in the manuals or on its Web site.) This file is updated by the server at job arrival time and, normally, when jobfiles expire and are removed. This file is not kept open by IPM. Observation shows that this file is rewritten from server memory, and thus seems to serve as a checkpoint file, rather than a reference file. (The inode number doesn't change in rewriting.) The content of this file is undefined by IPM customer documentation. Perceived contents: Record 1: A number, equal to the number of lines which follow in the file. (The number would match the output of command 'wc -l', minus one, performed on the file.) Records 2-N: One record for each originator of one or more jobs, consisting of: - Originator info, Username@Hostname. - A number, typically 101, reflecting the maximum number of jobs to track, per the PDIDTABLE environment variable value, which by default says to track 100 jobs per user - so local job ID numbers 1 - 101. If the user exceeds this number, local job ID number assignment for the user's jobs wraps to 1. - The number of jobs contained on this line of the file, e.g., 2. - Pairs of tokens consisting of the local job ID number of this job entry on the line (e.g., 1), followed by a space, and then the Job ID, of form ":<10digitGlobalIDnumber> - At the end of the line, after a space, the number 0, to denote the end of this list of jobs for one user. There is no order to the file. Most recent jobs are seen to be written to the top of the file, except where the user already had a line in the file, whereupon that line is updated in its prevailing position in the file. Note particularly the first, originator field of the record: it is unique by username *and* submitting hostname. In a university or similar setting where a user may use any number of PCs in an environment, or uses a PC which gains network access via DHCP, there can be many records for a single user, which can greatly inflate the size of the file and thus aggravate the effects upon IPM. Notes: This file accumulates a lot of antique information, as IPM server software failures cause it to fail to lose track of jobs and thus not remove them from either the job spool directory or this tracking file. The accumulation of crud in this file over time obviously poses an increasing burden on the server, as it devotes processing time, memory, and disk space in holding on to obsolete data. Unfortunately, there are no instructions for clearing old contents. And, clearly, the contents can't be pruned while the server is running, at least, as the deleted lines would only return in the next server rewrite of the file. I learned that this file can be safely renamed away from server awareness when the pdserver is down: the server will start rebuilding it after restart, as jobs arrive. Decreasing the PDIDTABLE value, across a server restart, will perform some pruning of this table, but not necessarily the obsolete data, and will result in local job ID number overflows. A drastic pruning method is to remove the file after a pdserver shutdown, causing the server to start it afresh; but that results in error message 5010-312 and loss of local job ID numbers for all currently held jobs. The failure of the IPM server to properly housekeep this file represents a software design defect and a performance issue affecting all customers. I pursued this with IPM Development, starting in 2007/06, which resulted in APAR IZ03251, where the fix is available in PTF level 7 (U811589), where a value of 0 for PDIDTABLE will allow disabling the use of the pdjobs file. Msgs: 5010-312; 5010-505 See also: PDIDTABLE /var/pd//pdpr________ The server directory filenames for jobs submitted for printing, where the server generates a random last 8 characters, resulting in file names like: pdpr-5UhzG_0. If you find such files empty (zero-length), that is indicative of a job starting to be accepted by IPM, but its content not arriving. This most commonly occurs with jobs arriving through the LPD Gateway (look in /var/spool/lpd/ and in the pdlpd_gateway.error_log file in that directory) which are typically problematic for the AIX software which conveys the job from LPD to IPM. Such empty files are useless and can be removed. There may be a file name like "pdpr4ju_PX_xfm1_err": this is created where there was a transform error, and the file contains the error condition, like: "pdls: 5010-452 Cannot communicate with the communication daemon on port 6874. Use your local problem-reporting procedure to report this message." Housekeeping: pdpr* files may be left behind after a server problem, and need to be removed from the server directory, else later problems may result from shortage of space, or when IPM goes to generate a random name and collides with an old, residual file. To safely clear old files, go into the pdb/spl_job directory and do 'ls -lt | tail' to get the timestamp of the oldest jobs: any pdpr files older than this are no longer known to IPM and should be removed. /var/pd//pdpr*_xfm1 Jobnames for the Transform Sequences work files which operate on the pdpr* job files in that directory. See also: Transform progress /var/pd/spl_trace.cfg Server trace configuration file. See: Server trace /var/pd/trans* Transformation scripts. May be old leftovers. /var/pddir Directory created by install. Contains a default_cell subdirectory, which is empty for non-DCE. /var/pddir/default_cell/acl/groups/ Directory containing the security files updated by fstsecutil: acl_admin admin oper The files are binary, encrypted. See also: /var/pd/acl/groups/ /var/pddir/default_cell/printers/ Contains physical and logical destination definition (binary) files, plus a license subdirectory. /var/pddir/default_cell/queues/ Queue definition files. /var/psf/ File system created by install. Houses transform management files and Actual Destination directories for AFP/IPDS printers. Contains the mount point for /var/psf/segments/. Sizing: The default size for this file system will typically be inadequate, resulting in serious problems down the road. A space-eater you would not expect is /var/psf//.count Job counter file. Contains nine ASCII numerals with leading zeroes, no newline. /var/psf//.profile Report contents via: mkprof -v .profile /var/psf//error.log Undocumented: A text file containing the most recent messages involving the AFP printer. Also known as the printer log. It is written by PSF, recording errors which PSF encounters with the printer. These errors do not appear in the pdserver error log. The log wraps. Some messages in the log may be worth tracking, such as when the printer ran out of staples (0424-197), when paper jams occur (0420-466), out of paper in the primary bin (0420-058), etc. Not recorded: instances of a lesser paper supply bin running out, when others are available to continue printing. The current point in the log is above a row of asterisks (****************...). /var/psf//core Seen in IPM 4.1, the result of an ainmain failure, probably a Segmentation Fault (SegFault, Signal 11) seemingly involving situation: "0420-131: ERROR: Infoprint cannot open the file...". In AIX, use 'errpt -a' to list such failures. Such a failure causes the AD to disable, and jobs bound to the AD to be requeued as Pending. APAR: IY75949 WARNING: These core files are *huge* - some 300 MB. They can easily fill /var/psf and cause transforms to fail en mass. I tried the "elegant" way of dealing with this problem by creating a "core" symlink to /dev/null - but IBM seems to do an unlink() of the filename before opening an output file descriptor, so my symlink got removed, and another 319,891,726, byte core file took its place. The only remedy, then, seems to be to have a cron job run frequently to remove these things. /var/psf//opc A file presumably containing the output of the Obtain Printer Characteristics, IPDS command, though this is yet to be verified. /var/psf//pif PSF binary file to support the backspace function, where info needs to be retained about stacked sheets in a job (all the way back to sheet one) so that an operator backspace request can be handled. Before the backspace function was introduced, once a sheet had stacked it could not be reprinted unless the entire job was resubmitted. /var/psf//printer.intervention An empty file whose timestamp reflects the most recent case of the AFP printer needing attention, as in the case of a paper jam ("needs key operator" status) or a paper supply bin being exhausted. Once such a file is created in a printer directory, there will always be an intervention file there, though the printer is currently operating well. (Observations indicate that the file never contains any descriptive data, but serves only as a null file to hold a referenceable timestamp.) /var/psf//statfile.log Undocumented: A text file, apparently contains a count of each 0420-____ message occurrence for the AFP printer. /var/psf//stm A file presumably containing the output of the IPDS Sense Type and Model command, though this is yet to be verified. /var/psf/faxserver/ Directory created during IPM install, to track activity in Fax or Email actual destinations. In that directory it creates file sendmemo.log upon the first processing of such a job, then continues appending to that file, ad infinitum. The directory will also house the transient Z.pdf in an Email DSS AD. /var/psf/interrupt/ Directory for controlling interrupted jobs, whose segments are in /var/psf/seglist/. Contents: *.jif Job Information Files reflecting the interrupted jobs, where the first element of the filename is the 1-digit job number, the next element being the Unix seconds since 1970 timestamp of creation (equals the file timestamp). interrupt.xref The control file for all the *.jif's. Administration: Leftover debris tends to accmulate in this directory, and needs periodic housekeeping. That, however, is complicated by the interrupt.xref file. As of 2004/04 the manuals fail to address such housekeeping. /var/psf/jobcompletion.log Overall, PSF post-print accounting log written by exit program /usr/lpp/psf/bin/ainuxjobcompletion. (Not written for AIX DSS jobs.) The data available to the user exit, and thus logged, reflects the results of the job's printing: its originating attributes are not reflected (and are to expensive to get in a user exit). Controlled by: accounting-exit (q.v.) (GUI tab Customize, "Accounting exit" field) specifying "accounting-log". One line is created per print job, when the printer reports back to IPM that all the pages of a job have been printed. (Jobs processed by a terminating type Transform Sequence will not cause this log to be updated, because nothing goes to the AD.) Logs one ASCII line per job. The data format is generally free-form (*not* all fixed-width!) where each token on the line is preceded and followed by one blank (hence two blanks between the end of one token and the start of the next). However, date and time fields are fixed-width, such that if a date or time is absent, blanks appear in its position. Contents can be reported by utility commands ainurpt7,8,9 (q.v.). Cut-off: The file grows indefinitely. You would naturally want to perform periodic cut-offs, monthly perhaps, to secure such a blob for historic reporting. You can do so while IPM is running by simply renaming the file: IPM will start a new one. See also: accounting-exit; Job completion log record /var/psf/podaccount.log Accounting file for the POD product. Written by the ainuxaccp user exit. /var/psf// See: /var/psf// /var/psf/ps2afp/ PostScript transform directory involved in first printing of jobs - not reprinting. The ps2afpd transform daemon, which runs as Unix user "daemon", must have read, write, and execute permissions to this directory, and must be able to read and write the files in it - particularly the Pipe files. See also: daemon; ps2afp; /var/psf/ps2afp2/ /var/psf/ps2afp/.PXIin The named pipe for the PostScript/PDF transform. The ps2afpd process writes to it, and the ps2afpi process reads from it. An lsof output looks like: COMMAND PID USER FD TYPE ... ps2afpd 1011798 daemon 7w FIFO ... ps2afpi 1048698 daemon 11r FIFO ... See also: psfin /var/psf/ps2afp/.PXIin The named pipe for the PostScript/PDF transform. The ps2afpi process writes its transformed AFP out to it, and the ps2afpd process reads the AFP from it. from it. An lsof output looks like: COMMAND PID USER FD TYPE ... ps2afpd 602322 daemon 7u FIFO ... ps2afpd 602322 daemon 10r FIFO ... ps2afpi 1048698 daemon 15w FIFO ... See also: psfin /var/psf/ps2afp/ps2afpd.log The PostScript & PDF transform log. Used for normal, queued transforms (not reprins). What's normal: The file is rewritten and stays under about 100KB, thus showing only the most recent jobs. Contents: The beginning of each transform is marked with a line of 69 hyphens (------), and the end of a transform is marked with a hyphened timestamp line, like: "--- Tue Feb 1 07:55:52 2005 ---". The log may contain entries like: deviceControls plex deviceControls plex,finishing, input1=(letter),input2=(letter), input3=(letter) which appear when there is an active device_controls line in the /usr/lpp/psf/ps2afp/ps2afpd.cfg, for the first deviceControls log line, and an active device_controls line in the /usr/lpp/psf/ps2afp/ps2afp.cfg, for the second deviceControls log line. Notes: From time to time, you may see the server hung up, and if this file does not show the ending timestamp line and the file's mtime is minutes old, it could mean that the server is somehow wedged on the latest job reflected in this log file. If so, doing a simple 'kill' on the ps2afp process for that job number has been seen to unwedge the server. Note that this log will have no mention of Formdefs. (See: ps2afp) See also: /var/psf/ps2afp2/ /var/psf/ps2afp/PSscreen/ PostScript/PDF transform directory, purpose unknown. May contain binary files named like: c24f9132.T . The ps2afpd.log will show referential entries like: "unlinking file /var/psf/ps2afp/PSscreen/c24f9132.T with a size of 14586". /var/psf/ps2afp/UserInit PostScript/PDF user initialization file as for turning on font substitution. /var/psf/ps2afp2/ PostScript transform directory involved in reprinting jobs - not first printing, as is logged in /var/psf/ps2afp/. The ps2afpd.log in /var/psf/ps2afp2/ reflects job input coming from Stdin (lone hypen at end of command line) rather than a file; and there is no -o to specify the output file, so the output goes to Stdout: the conduct of this handling is odd and undocumented. See also: /var/psf/ps2afp/ /var/psf/psfapi.data State file for psfapid (q.v.). /var/psf/psfapi.error.log See: psfapid /var/psf/seglist/ Directory in /var/psf file system. Manages the contents of /var/psf/segments/. When the Input Manager breaks a print job into segments, it creates a file known as a segment list. The segment list is used to make sure the job is reassembled in the correct order, to track job progress, and to perform other job management functions. Segment lists are stored in /var/psf/seglist/, and can either be saved or deleted when a job is finished printing. The file name begins with the 10-digit jobid of the job involved. Samples: 2116812429.0.acsrs6.pdprw3uozt_xfm1.3268 6077221957.0.acsrs6.6077221957.1. Infoprint2105ES.afp.2934 The segment list file is mostly binary but does have the full path of the segments file in it. Housekeeping: Orphan files may accumulate in this directory, where obviously-old stuff should be deleted by the administrator. See also: segprof /var/psf/seglist/.count ASCII file containing the latest suffix for files in the directory. Example: "4097", corresponding to latest file "2658610709.0. .pdprFrrzVI_xfm1.4097" in this directory, and file "2658610709.0. .pdprFrrzVI_xfm1.4097.seg3" in /var/psf/segments/. /var/psf/segments/ File system: The Input Manager is the part of Infoprint Manager that breaks print jobs into segments to allow greater flexibility during processing. Where a printer is waiting for work, it makes sense to create the AFP in smallish chunks so as to get the printer busy with that much of the job document, rather than delaying first-page-out until the whole job has been transformed. The Input Manager stores job segments in its workspace - this directory. Segments remain in the job prints and is stacked, or the workspace fills up. (However, you can set job attribute delete-segment-list False so that the segments are retained.) The segments files are binary, and typically contain a lot of EBCDIC character strings. The file name begins with the 10-digit jobid of the job involved. Sample: 1444121077.0.acsrs6.1444121077.1. Infoprint2105ES.afp.4264.seg1.end The contents of this directory or file system are managed through the directory /var/psf/seglist/. This file system is also used by Infoprint Email to send PDF files. Housekeeping: IPM supposedly manages the contents of this file system itself such that the administrator should not have to do cleanout; but reality shows ancient stuff lingering, so divine intervention required. Created by: install See: Page segments /var/psm/ IPM 4.2: Named pipes file system for inter-process communication. (In 4.1, was a subdirectory of the /var file system.) Directories: . For the pdserver. Always contains 512 entries. .notifyd For the notification server (notifyd). Number of entries can vary, but should only be a handful, for current notifyd process. Excess usually reflects server failures, where there was no graceful shutdown to allow clean-up. A large number suggests that notdmon is repeatedly and hopelessly trying to restart notifyd. Permissions: drwxrws--- root printq Each entry has a name consisting of two numbers separated by a dot (e.g., 62.737296) where the first number is the pipe number, and the second number is the process PID. In the server-named directory, the PID is naturally that of the pdserver process. In the .notifyd directory, the PID is that of a transient process (not that of the notifyd daemon). The named pipes in "." are referenced by /var/pd//pdsh______ shell script files. See the Configuration and Tuning Guide manual for details. Note: The contents of the .notifyd directory can grow to be voluminous, and detrimental to server performance. Consider cleaning very old entries out: those pre-dating the last server start are of no value. Clean-up can take the PID number from the pipe name and seek that number in /proc: if not in /proc, then no process on the pipe file, so the pipe file is of no use. Msgs: 5010-690 See also: /var/pd/notifyd/ /var/spool/lpd/ The AIX LPD printing directory, containing subdirs: pio qdir stat Additionally, the lpd directory may contain incoming files received by the lpd daemon on port 515, and will be owned by lpd. The files will have attributes and names like: lpd printq 138 cfA657fserv2.1028131564 lpd printq 70119 dfA657fserv2.1028131564 where: cfA is a constant identifier 657 is the always-three digit job #. fserv2 is the host from which the control file info came, being either a network name or N.N.N.N for IP addr. 1028131564 is the time of establishment in seconds since 1970. The mtime value of the directory will most likely reflect when the most recent lpr/lpd job arrived. /var/spool/lpd/pdlpd_gateway.error_log Log file written by ipm_pdenq as a sub-process of pdenq, to record problems in the handling of jobs given it by the AIX lpd (the "LPD Gateway) for printing on IPM destinations. Contains errors about attributes not supported by the requested server or destination, etc. Job problems almost always involve "apostrophe" (') characters in the job name, which results in problems passing args in the shell. Comments on contents: In the file you may see messages like: 5010-139 Cannot find file Chili. This is the unfortunate result of passing print job parameters at the shell level, via command line invocations. The passer tries to assure operand integrity by enclosing the operands in single quotes. But, the job as it came from the user can have one or more single quotes in the job name, which is passed via -T, and that screws things up, as for example in: -T'Joe's Chili' where the possesive apostrophe is actually a single quote and causes the operand to end there, resulting in the following stuff being taken as the job file to be processed, instead of the df file. See: Accept unsupported jobs; ipm_pdenq; pdenq Version See: Software levels, in AIX "View IPM queue" In Windows, menu selection for a printer via right-click. Allows seeing and controlling your print jobs, currently queued in the IPM server. vp The name of an IPM process in the AIX Process Table, being IPM's Virtual Printer process. Under it will run the img2fax process, which handles the mailing of PDFs. VSM DISCONTINUED IN IPM 4.1... Visual Systems Management graphical user interface (GUI) gives you the ability to perform Infoprint administrator and operator tasks from a GUI rather than from a command line. wait-for-job-completion Indicates whether IPM waits for the job to print completely before reporting the job as completed or reports the job as completed as soon as all the data has been sent to the printer. ("Reporting" means capturing attributes and logging.) DSS: AIX; PSF Other GUI label: Report job completed when printed Default: True when the printer and backend support PJL USTATUS; or False when the printer or the backend do not support PJL USTATUS. Note: Activating this option requires that the printer respond to PJL operations (in particular, USTATUS, as issued by the pjldetect command and in advance of sending a job to such a printer), and thus the physical printer must be accessible to IPM. If not accessible, error msg 5010-094. WARNING: See notes under pjlprtrs.cfg and snmp-discovery-during-startup. See also: pioibmnpm; pioinfo wait-for-job-completion-snmp-timeout AD attribute: Used with the wait-for-job-completion attribute and a destination command (backend) that is capable of using SNMP to monitor the job. The value specified tells the backend how long to wait after the printer has started accepting the job before giving up on finding an entry for the job in the printer's SNMP job MIB. DSS: AIX; PSF Other GUI label: Report job completed when printed timeout (sec) This attribute is used only when all of the following occur together: - When the AIX DSS or the PSF other-driver DSS is using pioibmdpm as the destination command - When the wait-for-job-completion attribute is True - When the physical printer being driven is an Infoprint 2085 or Infoprint 2105. Should be used where long delays are possible due to printer sharing or large, long duration jobs. Web access to printer http:// For printer status, config. Web administrator password Network Settings: Web Pages in the Infoprint 2085/2105 Web GUI Added 2011/06 in AIX PTF U110005. Web Operations GUI AKA "Web GUI". Provided by: InfoPrint Manager: Web GUI Feature The InfoPrint Manager Web Operations GUI is not installed automatically when you install the InfoPrint Manager server. Security restriction controls are the same as with the native GUIs. Runs at port numbers: 14080 for unsecured HTTPD so: http://Hostname:14080/IPM 14443 for secure access so: https://Hostname:14443/IPM Web printing Via: Web pull printing; Direct file printing; Internet Print Protocol (IPP) printing. See each. Ref: IBM Infoprint 2085/2105 Ethernet and Token Ring Configuration Guide, chapter 3. Web pull printing Allows users to submit PostScript, PCL, PDF, and ASCII text files resident on Web servers directly to the printer. The user enters the URL of the print-ready file and the printer retrieves it from the Internet without tying up the user's workstation. Web Server An IPM component you may install. It is for job submission by the Job Ticketer component of the Print-on-Demand (POD) feature. There is a Web Server CD-ROM from which to install. The Web Server must be installed before POD if the Job Ticketer is to be deployed. web-server-host, web-server-port Server attributes specifying the network address and port number of the IPM Web server. GUI labels: Web server; Web erver port Web submission of print jobs See: IPP Well In the Infoprint VSM administrator's GUI, a "sub-window": an area within a pane that contains a group of objects related to the objects in the pane; for example, a queues well within a servers pane. The well's color is conventionally violet. In the well you would typically open multiple sub-windows from the Window pull-down menu. Windows job submission via IPP Jobs will arrive job-originator and job-name specifying User@Host where User is the Windows login username and Host is the hostname in which Infoprint Manager and its IPP gateway are running. Windows job submission via LPR Jobs will arrive job-originator and job-name specifying User@Host where User is the Windows login username and Host is the Windows PC network address (not the logical name you assigned to the computer within Windows). Windows printer drivers must be signed Prior to Windows Server 2008, drivers did not have to be signed. However, in the x64 version of Windows Server 2008, all kernel-mode software (including drivers) that runs on the computer must have a signature. Windows printing Can be done by installing Infoprint Select as a method, and a chosen driver, such as "IBM Infoprint 2085 PS" (with that name being added to the Logical Destination Properties, Drivers tab). Can also be achieved via AFP Print Driver (q.v.). With-request In Infoprint, a document transfer method where the client transfers the documents directly to the server. Contrast with pipe-pull. Workgroup printer Printer type classified as printing in the range of 0 - 62 ppm. Next: Low speed printer Workgroup Printer Feature Optional cost license feature for driving small IPDS printers (Infoprint 1145 et al). IBM also wants you to have this license for driving PostScript (non-IPDS) printers, such as HP LaserJet 4050, though the absence of the license does not prevent using them under IPM. Formal name: "IBM Infoprint Manager Workgroup Printer Feature" It is known that installing this feature updates the /usr/lpp/Infoprint/install/ipm.ini file (Installation Features Log(?)), but beyond that, unknown. See also: Medium Speed Printer Feature Workgroup printers market IBM entered the workgroup printer market in 1996, complementing its products in the high-end production printing and print-on-demand arena. Write-black In electrostatic toner based printing, the image is produced by discharging the static charge from the image drum where the foreground portion of the intended image is to be generated, which is to say the lines and dots comprising the image. This process tends to yield better results than write-white. Write-white In electrostatic toner based printing, the image is produced by discharging the static charge from the image drum where the background portion of the intended image is to be generated. This process represents an erasure of the area around all the lines and dots comprising the image. This tends to cut into the image elements somewhat, with results not being quite as good as write-black technology. Write-white is how photocopiers work, in producing an image from the high intensity light reflected from the page being copied. Photocopier makers who also produce printers tend to carry the write-white method over into their printing products (e.g., Xerox). wxppsenu.exe See: Infoprint 2105 Windows 2000 and XP driver software -X IPM commands option for specifying an attributes file to be used. Example: pdmod ... -X /tmp/attrfile ... An error in the attributes file results in the command returning a status of 1, with a 5010-xxx error to Stderr. Common errors: 5010-140 Cannot open file ____. You specified a non-existent file, or the file contains an attribute in incorrect format, as for example "job-name" instead of "job-name=Blah". 5010-625 Cannot recognize attribute __. The correct "x=y" form is used, but the attribute name (x position) is not recognized. X0GT10, X0GT12 See: GT10, GT12 Xerox printers and IPM Xerox printers can be equipped with an IPS front end for printing AFP to them. Xerography Historic name for the electrostatic process of getting toner to attach to paper to form an image. In 1949, the Haloid photographic company was undertaking the development of the photocopier. Their prevailing name for the process, electro-photography, was not very catchy. An Ohio State professor suggested xerography, from the Greek words xeros for "dry" and graphos for "writing". Haloid named its first photocopier the XeroX Model A, the last X being added to make the form of the name similar to that of Kodak, another Rochester corporation. In 1958, Haloid officially changed their name to Haloid Xerox, and finally to just plain old Xerox in 1961. xforms Short for "transforms". XML printing Can be performed via IPM, using transforms xml2afp and xml2pdf. Perspective: XML is purely a data envelopment facility, with no presentation specifications as in HTML. As such, supplementary information is needed to define page layout. That is achieved via a style sheet. The Extensible Stylesheet Language (XSL) supplies such formatting, to describe how XML data is to be presented. Alternately, XML data may contain XSL formatting objects, called XSL-FO, to describe document presentation details: pagination, layout, styling (sort of what PHP is to HTML). xml2afp XML to AFP transform. Input consists of one of these: - XML files which do not contain data placement and presentation info, and an accompanying XSL style sheet; - XSL-FO files which contain XML data with XSL formatting objects. The transformation is performed via Java software. xml2pdf XML to PDF transform. Input consists of one of these: - XML files which do not contain data placement and presentation info, and an accompanying XSL style sheet; - XSL-FO files which contain XML data with XSL formatting objects. The transformation is performed via Java software. Xplor International association, formed in 1981, for those involved in document imaging, including printing. www.xplor.org Xpdf An open source viewer for Portable Document Format (PDF) files. http://www.foolabs.com/xpdf/about.html z/OS ("MVS") printing Commonly performed via the product IBM Print Services Facility (PSF) for z/OS for AFP/IPDS printing. AFP VIEWER MESSAGES: 1303: The resource ____ was not found, either in this file or in the resource path. Copy the missing resource into your resource path and reopen the file. The AFP Viewer is quite external to everything, and expects to find all the data it needs within the subject file. Make sure that the ___2afp transform you performed to create the file included everything into it. AIX RELATED MESSAGES: lpd[123456]: 0781-208 unknown printer ______________. Seen in /var/adm/messages log, when the pdserver process is defunct. IPM GUI MESSAGES: The client interface library cannot be loaded. Use local problem reporting procedures. Seen after installing the 2002/11 GUI fixes refresh, occurring with both the Operations and Administration GUI. Cause unknown, but I found that reinstalling one of the two GUIs fixes the problem with both. WARNING: Could not create system preferences directory. System preferences are unusable. [or: WARNING: Could not lock System prefs. Unix error code 979190748.] java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode Seen when trying to run the ipguiadvadm GUI command or similar GUI command on a new IPM system. First, make sure that your shell environment PATH contains the right Java directories. Then, first run the GUI as root. That produces indicative messages: Jun 6, 2007 10:18:14 AM java.util.prefs.FileSystemPreferences$3 run INFO: Created system preferences directory in java.home. What is java.home? It's not a filename: /.java/.userPrefs/ is unchanged in this operation. java.home is a system property that describes where the JRE is...its home or, supposedly, its installation area. (But, I've seen no change in the installation directory area when running the GUI as root.) If you then exit that GUI session and invoke one as non-root, no error messages. Why? Unknown at this point. /usr/bin/oslevel[7]: /usr/bin/rm_mlcache_file: cannot execute Appears when the GUI is invoked in AIX. This is because the original -r-sr-xr-x permissions were changed to -r-x------ as a result of the IBM security advisory: AIX 5.2 : Security advisories (2006.04.17) A vulnerability in rm_mlcache_file allows for arbitrary file overwrite Experience is that the GUI will run, where this then constitutes just a nuisance message. IPM GUI CONDITIONS: Doing "Check status" on a printer may not have a "More information" button between its Close and Help buttons. The "More information" button is helpful for displaying the details on an error condition, where the secondary window can also be used to dynamically display changing device state. But sometimes that button appears in your GUI, and sometimes it doesn't. What happens is that when the GUI starts it connects to the "java Server" process (AIX process name "java": If the pdserver and java processes are restarted, the GUI loses its connection to its "More information" data source, and the button will not be displayed. So, when the server is restarted, the GUI also needs to thereafter be restarted, in order to regain full access. IPM SERVER MESSAGES AND THEIR CAUSES, BASED UPON EXPERIENCE: You can use the 'pdmsg' command to see IBM's message descriptions. Note that the messages do not contain a letter, to indicate severity as TSM does with its messages (I for informational, W for warning, etc.). Note that 0420-* messages appear only in the printed PSF error sheet: they do not appear in the error.log file. 002-313 Infoprint Installer may not be run from the ____ directory. Also, no other processes should be running from ____. If processes are running from ____, your installation may fail. Not an IPM server message per se, but issued from a 'setup' execution when installing a feature, and your current working directory is the software install directory. Be outside that directory, and name it on 'setup -s ', where the DirName is a full path, with a trailing slash. 002-347 spacewatch.ksh has determined that the /var/psf file system may be running low on space. When spacewatch.ksh last ran, there were 280 1024-blocks of free space remaining on the /var/psf file system. If this file system fills up completely, it may disrupt Infoprint Manager operations. Please take steps to ensure that this does not happen. This verbiage appears in email sent, on the hour, to root. The pdmsg command has no further info on this msg. See also: spacewatch.ksh -------------- 0420-xxx msgs, in server & printer error.log --------------- 0420-020 ERROR: Cannot link to the actual destination at address xxx.xxx.xxx.xxx If this appears when you are first setting up a printer, and you are certain that the IP address is correct, then most likely the port number (destination-tcpip-port-number) is wrong. IBM's larger AFP printers employ a port number of 5001, but the smaller ones (1xxx series) utilize 9100. If the printer is an established one, it may be that the printer is in setup mode rather than Ready mode: for example, the Infoprint 1145 will reject IPM server communication attempts when it is in setup mode (such as when its control panel shows "Printing Menu, Settings"). This has also been observed where two IPM servers both have the printer (for legitimate alteration usage, with release timeout), but some operator put a Pause on the printer in one server, resulting in a usage conflict across the servers. Don't needlessly paust a printer and leave it like that. 0420-049 ERROR: Infoprint cannot communicate with the actual destination. With a PSF Command AD, the command may contain incorrect elements, as in 'enq -P____ -dp -' where "-dp" is incorrect for the enq command, belonging instead with the qprt command previously edited out of that field. Basically, you have meddled with IPM and have unintentionally told it to do something foolish. For example, you have a PSF Command AD, and in it specify a Transform Sequence which transforms various incoming formats to AFP: but a PSF Command AD is supposed to transform to AFP, and then to PCL; so IPM sees your final output as AFP and its PSF core is trying to communicate with with what it expects is an IPDS printer for outputting, but there is only an AIX spooling command there. 0420-058: The actual destination is out of paper in the primary bin; add paper. Seen in the /var/psf//error.log when the IPDS printer was out of paper; that is, "primary bin" is a euphamism for the printer paper supply in general. This is an Intervention Required situation (there will be a /var/psf//printer.intervention file with the same timestamp). 0420-093: The actual destination is not ready and must be made ready before printing can continue. Seen in the /var/psf//error.log when the IPDS printer experienced an Intervention Required situation (there will be a /var/psf//printer.intervention file with the same timestamp). With an Infoprint 1145 printer, its control panel may be displaying like: "232 Paper Jam Open Door E". Note that there may not be an explicit 0420-466 paper jam message in the printer error.log; but there may be a 5010-838 one in the server error.log. Expect there to be subsequent 0421-049 communications error messages in the error.log as the printer remains in a state where it will not accept job data. 0420-108: Infoprint could not write to the file ./pj00000.msg. This file contains error messages that print out at the end of the print job or are logged in the job message log. Job Name=_________________ Job ID=__________ Node ID=________ User ID=_______ ain3smsj.c 3171 Seen in printer error log (/var/psf//error.log) when /var/psf/ is out of space, as can be caused by absurdly large printer core files in /var/psf//. 0420-124 ERROR: Structured field EOF (X'D30000') was received when one of the following structured fields was expected: ________. Occurs when processing an AFPDS (modca-p) file. The message description from 'pdmsg' refers you to the MODCA Reference manual - but that is a fool's errand in this case, as there is no such thing as an "EOF" field. What the message is obliquely trying to say is that End Of File was encountered before it should have been: the job file is a truncated file. 0420-128 ERROR: InfoPrint cannot find or cannot access the page segment resource names S1______. This appears on a printed error page, usually appearing instead of the printed job, reflecting the inability to get at a Page Segment file in /usr/lpp/psf/reslib/ so that job processing can occur. Possible reasons: - The S1______ file does not exist in that directory. - The directory does not have r-x privs for user, group, and other. - The S1______ file does not have r priv for user, group, and other. 0420-251: ERROR: The actual destination reported an error condition that is not recognized. Job Name=________ Job ID=123567890 Node ID=______ User ID=________ IPM received some odd results back from an IPDS printer. There should be accompanying messages with additional detail, experienced like: 0420-249: InfoPrint received IPDS exception X'40E8..00', action code '1A' from the actual destination. Job Name=________ Job ID=1234567890 Node ID=________ User ID=________ 0420-252: The sense bytes received from the actual destination are X'40E81A00DE02000000000000000000000000000000000000'. The exception and sense bytes can be looked up in the IPDS Reference Manual. In this case, the X'40E8' refers to a condition where a supported input media source ID is specified but the input media source is not installed. This is probably caused by the IPDS printer being in a wacky state. Check the state of its trays, and if necessary its configuration values relating to paper handling. Rebooting the printer may cure the condition. 0420-252 The sense bytes received from the actual destination are X'________'. As seen in /var/psf//error.log. Provides the sense data which was interpreted to provide the information about printer state in the message which just preceded this one, which would be: 0420-466: The actual destination reported a paper jam; clear the jam. A common sense example is: X'40E50800BF02000000000000000000000000000000000000' where 40E5 means "Jam Recovery Needed". The sense data descriptions are found in several IPDS publications which delve into Exception Reporting and Sense Data. 0420-466 The actual destination reported a paper jam; clear the jam. This is the jam situation seen in the server error.log, for IPDS printers. (Note that the /var/psf//error.log may or may not also contain this jam message: it depends upon the printer reporting them to the server, and the printer may not do so if it is not designed to do so or is impaired...in which case only more generic 0420-093 reflecting the printer not ready will appear in the printer error.log.) See also related jam message 5010-838. 0420-509 ERROR: A Begin Medium Map (BMM) structured field with token name ________ cannot be found in form definition ________. An Invoke Medium Map (IMM) structured field specified a certain medium map name, but no Begin Medium Map (BMM) structured field with a matching token name could be found in the current Form Definition. The medium map name or the token name in the Begin Medium Map structured field might have been misspelled. See the 'Mixed Object Document Content Architecture Reference' for further information on this structured field. IPM cancels the print job, printing a PSF error page instead of the job. Note that the BMM name is what you specify on the PPFA COPYGROUP command in a Formdef. Check that the Form Definition you specify for the print job contains the medium map (COPYGROUP) referenced by the print job. If it does not, either add the medium map to the Form Definition or change the name of the medium map referred to by the print job to match the name of a medium map present in the Form Definition. You can use the 'afpdmp' command to inspect the names in the binary Formdef. This error tends to appear where you are processing jobs with your own Transform Program, indicating that you are interfering with an IPM facility which would otherwise have utilized its own in-line Formdef resource, such that your incomplete Formdef is displacing the full-function Formdef. For example, the message may reflect BMM S1000000 or D1000000. In 2002/11 server PTF U484268, PCL printing failed for lack of D01J0000 and D0100000. If you perform 'ps2afp' on a PostScript file and examine the output with 'afpdmp -d', you will see all the S1000000, S10J0000, and like BMM definitions up front, which are the inline Formdef COPYGROUPs, available to satisfy Pagedef references to them. Later in the AFP output, you will see an IMM (Invoke Medium Map) invoking "media map name = 'S10J0000'". This pops up in only some PostScript jobs because they are going after unusual resources: bins, stackers, finishers, and the like. If you examine the COPYGROUPs (BMM) in the afpdmp output, you will see what each uniquely does (simplex, duplex, tumble duplex, source drawer #2, and the like. Your Formdef needs to be as capable. -------------------- 0423-xxx msgs, in server error.log -------------------- 0423-096 ERROR: The parameter JOBNAME= must be of the form keyword=value. Experienced with a job having the name `General Hospital' gets reh... Apparently, the doofus shell processing that IPM does is not accounting for jobs having a back-tick/accent (`) character as part of the name, which as we know has special properties for shell interpretation: invoke the command following the back-tick. The only solution is to stop the job and change the (`) char to something innocuous, like a single quote. 0423-151 ERROR: ps2afpd: System error; an I/O error has occurred with file /var/psf/ps2afp/.PXIin. Seen in transform log when the ps2afpi process has been killed, as by an operator impatient for a transform to end, where ps2afpd is trying to write to the .PXIin pipe, but the ps2afpi process is no longer there to read it. This then leads to secondary error messages 0423-152 ERROR: ps2afpd: A communications error has occurred (return code=-32). SIGCHLD PX execution=-197 0423-152 ERROR: ps2afpd: A communications error has occurred (return code=-197). Worse: The ps2afpd will likely go into a half-killed state. So...don't do that! See also: /var/psf/ps2afp/.PXIin 0423-151 ERROR: ps2afpd: System error; an I/O error has occurred with file /var/psf/ps2afp/superdev.devices. Or the file name may be logged as ".PXIin". Seen in transform log when /var/psf/ is out of space, as can be caused by absurdly large printer core files in /var/psf//. In AIX, a file system truly out of space will create an AIX Error Log entry of type JFS_FS_FULL, which you would see via 'errpt'. Expect return code 60 from psf2afp. 0423-152 ERROR: ps2afp: A communications error has occurred (return code=-73). As seen in a transform. Typically due to the ps2afpd process having died, or hung. 0423-152 ERROR: ps2afpd: A communications error has occurred (return code=-9991). 0423-152 ERROR: ps2afpd: A communications error has occurred (return code=-9991). 0423-152 ERROR: ps2afpd: A communications error has occurred (return code=-32). Seen where some non-IPM process connected to a ps2afpd process. Can be reproduced by doing 'telnet localhost ____' on the port number of the ps2afpd process. 0423-153 ERROR: ps2afp: A communications protocol error has occurred. Can occur when the /usr/lpp/psf/ps2afp/ps2afp.cfg file contains an invalid keyword, such as "finishing", on the device_controls line in IPM 4.1. 0423-163 ERROR: ps2afpd: System error; cannot create the listen socket (return code=-67). Found in the /var/psf/ps2afp/ps2afpd.log, and encountered when trying to start the missing primary ps2afpd daemon via command '/usr/lpp/psf/bin/ps2afpd -C/usr/lpp/psf/ps2afp/ps2afpd.cfg'. This, after an operator thought he would try to clear a seeming server hang by attacking processes. In typically lazy IBM programming, the software could certainly help the customer out by actually reporting the details of the error, which it knows, but it fails to do so. Referring to the .cfg file, I found what it should have reported: "port = 8251". That is, the daemon is trying to open a socket on its conventional port number 8251, but cannot. Why not? The usual reason is that it's occupied by another process. Doing 'lsof -i :8251' revealed that a prior, orphaned instance of ps2afpd was still in the system - along with many other IPM processes, also orphaned by the operator slaughter. Killing off the orphans cleared the port and then a manual start of the missing daemon finally worked. IBM's programming could be far better than it is. 0423-170 ERROR: ps2afpd: System error; unable to create the correct operating environment. Seen in transform log when /var/psf/ is out of space, as can be caused by absurdly large printer core files in /var/psf//. Expect return code 60 from psf2afp. 0423-175 ERROR: ps2afpd: The input file contains PostScript commands which resulted in an error. The PostScript error was: %%[ Error: more than one page used to create page segment ]%% The .ps file contained more than one PostScript 'showpage' command. 0423-370: Infoprint will not print the job in simplex mode because duplexing was specified on the pdpr command. (Note that the message is overly parochial as to the command submitting the job: in actuality, it could be any command, such as qprt, lpr, etc.) The problem is the Job and Document Defaults specify a "Sides to print" and "Plex to print" combo other than the default, and that is conflicting with the destination. Changing them to default values allows the job to succeed. We suddenly started experiencing this with an Infoprint 2210 printer, which emitted error sheets rather than AFP/IPDS jobs. Seems to be gross firmware defect, where the printer reacts in this bizarre and inappropriate way when feed Tray 1 was left out due to a feeding problem, with the other two trays defined same Letter size as Tray 1, so should operate correctly. 0423-386: Infoprint cannot update the pif file because it is too large for the filesystem. Backspace and pause operator requests for this job may be ignored. ain3tpif.c 1027 Seen in printer error log (/var/psf//error.log) when /var/psf/ is out of space, as can be caused by absurdly large printer core files in /var/psf//. 0423-399: Infoprint cannot read the file /var/psf/seglist/.0..pdpr_pj02f_xfm1.4726. The system return code is 28. ain3tsq.c 1272 Seen in printer error log (/var/psf//error.log) when /var/psf/ is out of space, as can be caused by absurdly large printer core files in /var/psf//. (28 is errno ENOSPC) 0423-409: Infoprint is processing a pause request. Seen in the /var/psf//error.log as evidence that a Pause/Stop/Shutdown was performed in IPM (they are all the same lineage). 0423-411: Infoprint is ignoring the requested pause operation because the actual destination is already at a job boundary Seen in the /var/psf//error.log where a shutdown was abruptly performed on a printer as it was busy processing one or more jobs. In this situation, I've seen the same job printed twice - with no entries written to either the accounting log or jobcompletion log! 0423-481 Input Manager is processing file C:\Program Files\IBM\Infoprint Select\Spool\42389e2a.SPL with job script /var/pd/acsn07/1439530268.1.js. This is the recording of acceptance of a job submitted from a Windows PC via Infoprint Select, via the pdserver psmd port. 0423-515: The object x or y origin 65535, or 65535 is out of range. ??? 0423-923 Input Manager processing failed on file ____________ 0424-179 Input Manager is terminating with an exit code of 50. 5010-578 An error occurred in /usr/lpp/psf/bin/psfin. Seen after the operator altered a group of jobs, as in changing the priorities of a bunch of jobs (5010-346 Starting the modify job request. in the server error.log). We have seen that operating on jobs en masse can create problems. The job reflected by the 923 message was a good one, but got caught up as a victim of the mass operation. Resolution: I found that the lowest child under the server, a pdls involved in transform processing, when killed, freed the hang. 0424-194: The actual destination does not support document-level finishing. Finishing fidelity is CONTINUE. As seen on an error sheet at end of job, and in the /var/psf//error.log: The job requests finishing such as stapling, but the device is not capable of it. The CONTINUE means that IPM lets the job go through, avoiding requesting any finishing operations at the AD, effectively ignoring the contents of the data stream's instructions for finishing. Msg may also be seen in /var/psf//error.log . The job will show attribute job-state-reasons = completed-with-errors . This message is commonly seen for PDFs submitted for printing to workgroup printers which do not have finishers, with the PDF containing attribute "Binding: Left Edge". Experienced when GUI: Job and Document Defaults, Job General tab, "Finishing options" specifies something like "edge stitch"; but that spec is not one present in the printer. Also experienced when the Job and Document Defaults do not specify finishing, but does specify a form-definition, and that Formdef calls for a certain type of finishing. The error occurs with a PSF Command DSS because a Formdef is only appropriate for an IPDS printer. This illuminates the danger of a Logical Destination, which may feed multiple types of DSSes, but has to be carefully coded to accommodate the capabilities of all of them. Most ordinarily experienced when a job which specifies finishing is sent to a printer which does not have any finishing capability, such as a smaller desktop IPDS printer. 0424-203: The output contains too many or too few sheets to perform the requested finishing operation. Most commonly, this results from requesting stapling for a job that has more sheets than the stapler can handle. More rarely, this is due to a configuration error, where the Actual Destination is a printer which does not do stapling, but the Formdef in effect specifies finishing: use a more appropriate Formdef. 0424-225 ERROR: E-MAIL: Job sent to e-mail address Who@Where was not successful. E-mail server error code = ERROR img2fax: [10496] [img2fax: error: tried to send email to Who@Where: return code 10496 The SMTP server log in this case shows sendmail[30228]: NOQUEUE: connect from sendmail[30228]: o02HJJok030228: ruleset=check_rcpt, arg1=Who@Where, relay=, reject=553 5.5.4 Who@Where... Domain name required for sender address NULL Cause: The email-from-address attribute was not present in the pdpr command which submitted the job. 0427-018 ERROR: ps2afpd: The transform program cannot create or write to file .PXIin. Seen where the ps2afpd directory is not writeable by 'daemon'. 0782-006 -Y flag not supported for the print file type, printer language, and printer type selected for the print job. Check the flags. Appears in error.log in AIX DSS printing where the Job/Document Defaults specifies duplex (Sides to print: 2, Plex to print: simplex) printing rather than "Use default". This is an AIX error message, referring to there being no -Y flag for the 'qprt' command, or no "-o Y" option for the 'enq' command. -------------------- 5010-xxx msgs, in server error.log -------------------- 5010-002 Specify an object name. Seen when doing like: pdmod -m "Won't print" -x "job-hold=true" ourhost:0066800179 Seems to be due to the single quote inside the -m string: re-author the message without it. 5010-011 Cannot add object ____ to the print database. We encountered this one after the computer suffered an abrupt power outage (UPS failure). After restart, this message rapidly repeated in the server error log, always involving one job ID. The condition prevented printing from happening in the queue involved with the job; other queues were printing fine. We were about to whack the job, and issued a query for the full queue contents, when that seemed to cause the condition to clear, and all was then well. Behavioral psychology? 5010-020 Cannot create Java Virtual Machine. ... Message found in IPM 4.2, in /var/pd/notifyd/error.log - though the command 'startnotd' says "5010-405 Successfully started server notifyd." but you discover the reality, that notifyd is not running, so you look in its error log. IPM's formal explanation of the message is "The Java Virtual Machine could not be created". People get paid to write stuff like this?? The notifyd daemon in IPM 4.2 requires Java, where, in PTF 1 - 4, the JVM software is contained in libjvm.a, which is located in /usr/java14/jre/bin/classic/ or, less likely, /usr/java14/jre/bin/. The pre-PTF 5 /usr/lpp/pd/bin/notifyd module contains an internal LIBPATH: /usr/lib/threads:/usr/lib:/lib:/usr/java14/jre/bin/classic :/usr/java14/jre/bin:/usr/lpp/pd/lib while the PTF 5 notifyd contains the internal LIBPATH: /usr/lib/threads:/usr/lib:/lib:/usr/lpp/pd/jre/bin :/usr/lpp/pd/jre/bin/classic:/usr/lpp/pd/lib (Use the command 'dump -H /usr/lpp/pd/bin/notifyd' to verify what's currently in its LIBPATH.) IBM FLASH10448 (since removed from the IBM site, but I have a copy) notes that interference from a LIBPATH environment variable can thwart the start-up; or, a PATH spec where the java directory is not at the front can bollix things. As of PTF 5 (2006/12), the Java has changed (See "Java") such that the startnotd script now needs the following: # As of IPM 4.2 PTF 5, IPM uses its own Java, so this alteration, for # notifyd to get its libjvm.a : export LIBPATH=/usr/lpp/pd/jre/bin/classic 2005/11/22 APAR II14110 recommends: export LIBPATH=/usr/java14/jre/bin:/usr/java14/jre/bin/classic but that APAR predates the PTF 5 level, so not viable. pdrm: 5010-050 Cannot find job 0123456789 for user ____@____. Typically because the command was of the form 'pdrm ' when issued against a job other than your own. To do a pdrm against another user's job, the form must be 'pdrm :'. 5010-055 Job name ________ with ID ________ (________:________) completed on ________. As seen in an Infoprint Select Notifications message, as in sample: [11/03/09 12:02:05] 5010-055 Job name My Document with ID 2 (Ourserver:4101000093) completed on LDest5. to notify when a print job completes. There is no indication as to whether or not it was successful. This can be the case where a transform was set to "Transform only", rather than "Transform and print", or per the return code set in transform attribute conditional-terminating-return-code. Otherwise expect message 5010-071. See also: 5010-204 5010-065 Cannot find the object . See where the operator is switching their GUI to a new server. The server error log will show: 5010-547 A client GUI has requested to unregister for events from server: . 5010-071 Job name ________ with ID ________ (________:________) completed successfully on ________. As it says, the job completed, and was successful. Contrast with the 5010-055 case. 5010-087 The object ____ is not in an acceptable state for this operation. As found in the server error.log, typically because a job arrived for a printer which is disabled or shut down or has a problem like a paper jam or out of paper, usually as detected by IPM's SNMP probing of the printer. As a result of this, the printer icon will turn red in the GUI, with state "needs key operator". I have also experienced this in a perplexing situation with an HP printer where there was nothing wrong with the printer as tested by PJL and SNMP. This was where the printer was defined to IPM with an IP address, rather than network name, in that the subnet involved had no network names assigned with the positions being utilized. There should be nothing wrong with that, but there was nevertheless this exasperating problem. I deduced the problem to be that, like most server software, IPM wants to perform a "reverse lookup" on the IP address, to thus get the network from a gethostbyaddr() call, but gets nothing back. IPM thus refuses to work with the printer - but with no indication why not, which represents a software defect. May be accompanied by message 5010-306. 5010-092 The attribute auxiliary-sheet-selection is not supported by the requested server or destination. Message may appear in AIX LPD Gateway log /var/spool/lpd/pdlpd_gateway.error_log. Seen with a BSD DSS when using the AIX 'lpr' command within the IPM AIX server system - but not other AIX printing commands like 'enq', 'qprt' or 'pdpr', and not when printing from another AIX system, where the job arrives in the IPM AIX system through the AIX lpd subsystem (which somehow neutralizes things). The BSD DSS has no auxiliary-sheet-selections-supported attribute to accommodate such selection, which suggests that attribute auxiliary-sheet-selection is implied by the lpr command inciting a header or trailer page; but even doing 'lpr -h', which suppresses the burst page, still results in the error. So what's going on? The AIX lpr command invokes the AIX enq command, which hands the job to IPM via its pdenq and ipm_pdenq modules. Interception of the arguments being passed to enq and then pdenq shows that 'lpr -h' is causing lpr to employ burst option -Bnn when invoking enq, and enq invokes pdenq with the same option. Though -Bnn means "no headers, no trailers" - a null value - IPM still reacts to the very presence of the -B burst option to indicate that some form of auxiliary sheet selection is at play, and that is disallowed in BSD printing. So, the error message, because IPM is translating the -Bnn to auxiliary-sheet-selection=none rather than not instating an auxiliary-sheet-selection attribute at all for the job, as would be the case for a simple qprt or enq command. (In the GUI, a "bad" BSD job has Auxiliary/Separator sheets = none, while a "good" BSD job would have Auxiliary/Separator sheets = Use default). Conclusion: IPM is over-reacting to the -B option. For customer purposes, it should regard -Bnn as equivalent to no auxiliary sheet selection, as though -B was not present at all. What can you do: Avoid the problem by using the 'enq' command instead of the 'lpr' command, as in basic sample: enq -P ldname myfile.ps You can fix a faulty job by pursuing the following... Changing server attribute "Accept unsupported jobs" from No to Yes allows the job to queue (which will avoid ugly AIX qdaemon messages), and therein you can inspect the Job Status tab "Resources not supported", which says "Actual Destinations Requested". You can get the job to print if you use the command line to delete the auxiliary-sheet-selection attribute (pdmod -x 'auxiliary-sheet-selection==' :), or use the Admin GUI to change the job property "Auxiliary/Separator sheets" to "Use default". You can make a remedial change to the AD's definition per the Procedures manual, per its topic "Allowing the auxiliary-sheet-selection job attribute with the BSD DSS", to add support for values: none start. And also define the LD's initial value job to have auxiliary-sheet-selection=none. Doc search: unsupported attribute values 5010-092 The attribute plex is not supported by the requested server or destination. Encountered with a BSD DSS, where the server certainly supports the plex and sides attributes that are present in the job, and the AD has plexes-supported=simplex|tumble and sides-supported=1|2, as is legal for a BSD DSS. So, huh? 5010-092 The attribute sides is not supported by the requested server or destination. Experienced where the LD (initial-value-job section) specifies 'sides', but the AD does not support it per its sides-supported attribute. Experience shows that it's impossible to fix the attributes of such jobs where that and the plex attributes are both set in the job, where the LD is still set with these default attributes: IPM simply complains with this message number, repeatedly. 5010-094 Specify a value for attribute destination-command that is consistent with other attributes for the object. Seen with an AIX DSS. You filled in the GUI "Command" field with a command path which looks fine to you, but attempting to commit the definition causes IPM to evaluate the command for something it recognizes. (IPM does not actually try out the command: the pdserver module has "/usr/lib/lpd/pio/etc/" and module names like "pioibmnpm" hard-coded inside it; and experimentation shows that if you rename /usr/lib/lpd/pio/etc/pioibmnpm to /usr/lib/lpd/pio/etc/pioibmnpm.ibm and try to use that alternate name, you still get the error, despite all other things being the same - which demonstrates name sensitivity. The product is stringent.) 5010-094 Specify a value for attribute wait-for-job-completion that is consistent with other attributes for the object. Seen with an AIX or CUPS DSS. Activating this option requires that the printer respond to PJL operations, and thus the physical printer must be accessible to IPM. Getting this message indicates loss of connectivity: printer turned off; network cable disconnected from it? Another cause can be that the printer has been in a Disabled state for a very long time, with the server out of touch with it, particularly when server attribute snmp-discovery-during-startup (GUI: "Discover printers at startup") is No: do an Enable to have the server communicate with the printer in order to refresh its awareness of printer capabilities... thereafter the message should no longer appear. Attempting to get around this by doing a Printer Copy via the GUI will not work. What you need to do is add the printer model to file /usr/lpp/pd/bin/pjlprtrs.cfg. (In AIX DSS, the "printer model" is the name of the colon file for it; in CUPS DSS, the "printer model" is the name of the PPD being used.) Seen with a BSD DSS, it is simply an attribute which is illegal for that type of DSS, not making sense for it. A BSD DSS is usually fed via the rembak command, which is asynchronous. 5010-096 The value tray-1:universal-paper is not supported for attribute input-trays-medium. - or - 5010-096 The value tray-1:na-number-10-envelope is not supported for attribute input-trays-medium. Seen when defining an HP printer, with SNMP active: the definition goes after values in the printer, and may get some values which the IPM server does not understand. It is probably the case that the printer has been tinkered with from its front panel to handle some odd stock for a special job. The way around this is to start out with "use-snmp = false", then return it to true after the AD is defined. 5010-096 The value ____ is not supported for the attribute destination-model As in defining an AIX actual destination for an Infoprint2105 model: The problem is the absence of such a model in /usr/lib/lpd/pio/predef/. Such files come from the specific printer device drivers, as downloaded from the IBM site, as for example: IBM Infoprint 2085/2105 PostScript, PCL5e and PCL6 Printer Drivers and Utilities for AIX 4.3x and AIX 5.1. 5010-096 The value ____ is not supported for the attribute printer-resolutions-supported Seen when attempting to add "1200" to a AD printer definition, in the GUI Resolutions Allowed field. Scouring the IPM manuals, you will not find resolution specs above 600; and the Infoprint 2105ES printer manual stipulates that though this major new printer does 1200 dpi, AFP printing is limited to 600 dpi. All this points to IBM's AFP not going above 600 dpi. Said another way: IBM's printing regimen does not support 1200 dpi. 5010-099 Specify a single value for attribute __whatever__. In a pdcreate, you are feeding an attribute list file via -X and some of the values in the file are null. This error message tends to blame the legitimate line which immediately precedes an attribute line having a null value: it is the null value line that is the problem. 5010-099 Specify a single value for attribute job-name. Commonly seen in an LPR job submission where the -T job title is a string containing multiple words separated by blanks, and the submitter failed to enclose that complex title in quotes, such that IPM parsing based upon delimiting spaces took the next word in the title as a following command line parameter. /var/spool/lpd/pdlpd_gateway.error_log will have the evidence. 5010-100 Specify a value for the destination-model attribute. Encountered in defining an AIX DSS via Model spec "Set by SNMP printer". That is, you are telling the IPM server to go query the printer via SNMP to learn what it is; but, apparently, the printer is not talking SNMP, at least to the IPM server's IP address, so IPM cannot determine what the model actually is this way. You have to actually tell IPM what the model is. 5010-111 You must be authorized to perform this operation. Seen when trying to invoke fstsecutil to update security ACLs. (No indication is logged in the server error.log) The reason is that your username is not in the acl_admin ACL. As root, invoke smit to add same. 5010-115 The object ________ already exists. Use a unique name. May occur if you are forced to physically remove an AD definition from /var/pd//pdb/suv_phy_printer/. AD names are also created in /var/pddir/default_cell/printers/, so that needs to be addressed, too. 5010-116 The ____ server is too busy to perform the request at this time. When this exasperating message appears, the IPM server is usually hopelessly hung up, for no discernable reason, and needs to be restarted. Examination of its error.log will reveal no explanation for its infinite busy condition - which may show IPM repeatedly addressing the same job. Sometimes, this is caused by a whopping PostScript job (e.g. 700 pages of dental images) keeping a ps2afpi process 100% busy: the job will eventually finish transforming, but the "too busy" condition will hopelessly continue. Typically, no PSF printer logs will give cause. No processes look bad or looping. Killing of processes allied to the IPM server will not cure the problem. The only recourse is to kill the server process and start it afresh. And even then the same problem may recur. The Tuning Guide manual describes this condition, where setting a good PD_LISTEN_COUNT environment variable value may help; but if the error log shows the server looping on a file, that's a software defect, so fooling with the count won't help. Note that the message may appear in response to a pdls or other command attempt, but the message MAY NOT appear in the server error.log! A lingering problem might be due to some hacker conducting a denial of service attack. 5010-117 The server _______ required to process your request is not available. Use a different server or try your request again. Formal expanation: The server is not available at this time. What really may be going on: The server has been shut down, as per prior error.log msg 5010-338. 5010-120 A server error occurred. Encountered when doing 'startnotd' to start notifyd, where the startnotd ksh script looks for a notifyd process after having started it, and doesn't find one in the Process Table. Try starting notifyd via direct '/usr/lpp/pd/bin/notifyd' invocation rather than via startnotd, in order to expose error messages which it otherwise stupidly sends to /dev/null. (Who writes this stuff??) You may find it thus reporting "Failed to find VM - aborting" (q.v.). 5010-130 The server ______ does not support the requested operation. Most likely, you attempted to submit a job to the physical printer name, rather than the logical destination name. 5010-143 The maintenance period of InfoPrint Manager is over Appears around 03:10 PM each day in a server which is undergoing a software trial, and has not yet been licensed. A "nag message". The software continues to function, for the 60 day period. 5010-145 Filesystem/disk "/var" is low on space, usage is 80.0 percent. Typically seen in email to the IPM administrator, generated by the IPM server per server attribute notification-profile, disk-space-low notification event. Yes, the IPM server even monitors the level of file systems not directly related to its operation. 5010-170 Shell command /usr/sbin/piocnvt -s + -i /usr/lib/lpd/pio/predef/.ps -o /var/pd/acstmp/pdcfDEBbUa failed. Shell return code = 1. Seen under unusual circumstances, when I was forced to physically remove an AD definition from /var/pd//pdb/suv_phy_printer/ in order for the server to successfully restart; but another AD also pointed to as a destination by that LD remained in. IPM could not get info on the removed name in order to handle it, resulting in the command-utilized name being null (/usr/lib/lpd/pio/predef/.ps should end with .ps). Treated by removing both ADs, which allowed the server to come up, at which time I deleted the LD to redefine it fresh. 5010-192 Message from Infoprint server: This is what appears as the Subject in an email notification. The body of the message will contain an explanation for the notification (e.g., 5010-196 message, for job cancellation). 5010-204 Job ________ (________:________) stopped processing due to job or destination errors. Seen with Infoprint Select Notifications, as in sample: [11/03/09 12:02:05] 5010-204 Job 3 (Ourserver:4101000094) stopped processing due to job or destination errors. as when the transforms program returns control with an exit return code that is non-zero and not equal to conditional-terminating-return-code transform attribute (if any), as to reflect ps2afp or similar transform failing due to job structural problems. See also: 5010-055 5010-215 An internal error was detected in server ________ The pdserver code has a lot of serious defects, and this is how it ends up. It typically happens when you try to delete or otherwise deal with a red-iconed job file which was corrupted by the server. See also 5010-441. 5010-247 Physical printer : has timed out. IPM could not connect to or get a response from the printer in the time specified by the printer-timeout-period/destination-timeout-period AD attribute. Most commonly, the printer has been network-configured to restrict access, where the print server cannot reach it. (Attempting a telnet to the printer's printing port will verify this.) Otherwise, the printer may be in use by some other host that is sending jobs to it, or job progress at the printer has stopped. IPM continues its attempts to connect or print to the printer device. This kind of thing usually occurs with PostScript printing, where communication between host and printer is loose. I have seen this message appear in the server error log on a five minute interval. Network tracing reveals the issue: In HP printing, job control is governed by PJL protocol. The host can and usually does send the printer PJL commands saying that the printer should convey page printing progress back to the host, and communicate back once the job completes on the printer, providing a count of pages printed. In the trace that I saw, the printer received the full job, acknowledged it, sent page processing status - and then fell silent for minutes, though it had done with the last page of the job already. In concert with PJL timeout conventions, just before the 5 minute PJL timeout expires, IPM performs a PJL Echo to determine if the printer is still there - which it promptly responds to. IPM then has the printer send it a copy of its job governance settings, which verify that the printer should have communicated job completion. IPM can only conclude that the printer somehow lost the job, flags the printer icon red, and then performs a PJL conditions reset, logs this error message, and recommences the whole process of printing the job. The result at the printer will likely be the job repeatedly printing. The problem is that the printer is for some reason failing to return job completion. The fundamental problem is that the printer's PostScript interpreter or shortage of memory is causing the transformation to take an inordinate amount of time, usually with a "tough" job (like a full color scanned image). 5010-306 The destination : needs administrator attention. Results in red icon in GUI, with "needs operator attention". 5010-312 Cannot restore local job IDs. Usually because you purposely removed the file /var/pd//pdjobs (q.v.). The IBM message description talks of "the communication daemon" cannot open the pdjobs file in the server directory, in order to compile local job IDs. The description fails to identify just what "the communication daemon" is. And the pdjobs file was indeed present, with proper permissions. A wholly vague situation. Is this daemon "notifyd"? It was started at the same time as the server. 5010-338 The shutdown request for destination ______ is complete. The final message following processing of a pdshutdown on an AD. However, it DOES NOT necessarily indicate that the shutdown actually occurred...that it was successful: an 5010-669 error condition may have occurred, for example, which prevents the shutdown. 5010-346 Starting the modify job request. 5010-348 Starting the cancel job request. Sequence seen in error.log when a Disable (black light bulb in GUI) is performed on a job that is transforming, as where the operator deems that the job is too big and taking too long, and wants to stop that, so that the many waiting jobs can print. The transform will find itself interrupted, log message: 5010-631 System function IPMXFORM returned error number 137. Once the server finishes stopping the job, the following message will appear in the log: 5010-379 The server received a job completed signal request from the destination : for the job :0899200074. The job state reason was cancelled by operator. 5010-347 The modify request for job is complete. The operator, probably via GUI, invoked an operation to change the status of a job. Server defect: The server has been seen to omit the Jobname from the message where it is not possible to change the job at that point, because it is in the processing, printing, terminating, or unknown state. Here is the log sequence: 5010-131 Cannot modify job 3608004642. 5010-347 The modify request for job is complete. (The two consecutive blanks in the message is the giveaway.) The absence of the Jobname suggests the server internally having problems, as the Jobname does appear in this message when it is possible to modify the job. Further attempts to interact with the server have been seen to result in "010-116 The ____ server is too busy" - which never clears. Not trying to modify jobs which are "in flight" may help avoid the server hang-up. 5010-348 Starting the cancel job request. 5010-349 The cancel request for the job is complete. A pdrm was performed, as in moving a job from the Pending queue to the Retained Jobs queue. 5010-362 Starting the list request for ____ objects. Log entry reflecting the servicing of a 'pdls' command, which may ask for a listing of objects for any class of things, being one of: auxiliary-sheet document initial-value-document initial-value-job log medium destination queue resource-context transform server 5010-372 The server _______ completed processing a job completed signal request from the destination :. Logged in the error.log when a job has completed printing. 5010-372 The server _______ completed processing a unregister signal request from the destination :. Logged in the error.log when the AD (printer, any kind) is bowing out because an IPM shutdown is being performed. You will likely see a bunch of these, one for each printer you have defined. 5010-379 The server acsrs5 received a job completed signal request from the destination ourhost:printer1 for the job ourhost:1976900004. The job state reason was aborted by system. See with rip-and-hold processing where the AFP file created by that processs is zero-length, the result of a ps2afpd failure. Remove the AFP file from the server directory. Go into the GUI and change the RIP option to Rip And Hold, then release the job. The AFP file will be properly generated. 5010-404 Cannot start server . Check the error log for messages related to this failure. See /var/pd//error.log for causal messages. 5010-410 PSFAPI command PSFJobInitialized failed. Return code = -1001. Seen once after a pdserver restart, on one PSF printer, but not its twin. The involved printer was in "sleep" mode at the time (and later required a warm-up period before printing). Doing a status check on it at the time shows it problematic: IPM says "needs key operator". Doing an Enable cleared the problem. 5010-410 PSFAPI command PSFJobInitialized failed. Return code = -1002. Seen once after a pdserver restart, on one PSF printer, but not its twin. Doing a stop-start on the printer instance cleared it. A worse cause is /var/psf/ running out of space. 5010-417 The result-set of job (GlobalID) is submitted to the PSF backend. The "result-set" is the AFP output of the transform run shortly before (see the transform's 5010-508 msg). Seen to follow msg 5010-341. (This message is 'D' type in the IPM server error.log.) 5010-418 The request for job (/pdjobs file is accumulating an increasing number of obsolete entries, reflecting jobs from long ago, due to a server defect. This file will grow to megabytes in size, and impair IPM performance. (This is a server programming defect.) 5010-538 Unable to SNMP default attribute ____ on actual destination ______. Example: 5010-538 Unable to SNMP default attribute psf-tray-characteristics on actual destination hspr3afp. IPM was unable to default (set) this attribute using SNMP-obtained info. Apparently, IPM went out to the printer via SNMP seeking information it needed, but could not obtain it or could not understand it. This is usually a programming oversight in the IPM product, where the developer did not properly program for the MIB realities of the printer (which is often an Infoprint product, which they should fully know about). 5010-547 A client GUI has requested to register for events from server: ________. The server name will be "*" to indicate "self". A GUI is starting, and has already gotten AD, LD, queue, and jobs inventory information per preceding 5010-362 and 5010-363 messages. The GUI is now looking to get updates on all areas that it is monitoring. This will be followed by 5010-427 and 5010-454 messages. 5010-562 Destination ____ in server ____ is disabled and cannot accept submission requests. Typically seen when a logical destination is disabled. You need to enable it, as with the 'pdenable' command. 5010-556 Unknown object identifier (OID) "1.3.18.0.44.2.3.2.13" encountered. Appeared mysteriously during attempted IPM server restart, after applying AIX patches, with the server then failing to start, producing a core dump in /var/pd//. The SNMP OID number that the message is complaining about is in the /var/pd/acstmp/pdb/suv_phy_printer/ and involves an HP 4000 series printer, which had been happily used before the AIX patches went on. That OID is supposed to be cataloged in AIX's /usr/lib/nls/msg/En_US/Pd/ibmoid.cat, but not. The '44' in the number seems to be erroneous, as all other OIDs in that file have '4' in that position. It's impossible to tell from the suv_phy_printer/ file what the seemingly erroneous OID is supposed to be for, and I have been unable to find an OID registry which has such a branch in its hierarchy. Manually editing the suv_phy_printer/ file may fix the problem: beware leaving any edit backup files in the directory, as that may also flummox the server. 5010-560 A medium value for the input-trays-medium attribute is not listed as supported in the media-supported attribute. For example you attempted to change the "Media ready" for Tray 1 of an HP 4020 printer to "manual"; but that's not one of the choices in the "Media allowed" list of possible values. 5010-606 The value hpgl that was specified or defaulted for attribute document-format is not supported by the destination or by any of its associated actual destinations. Well, life is strange: you can very innocently create a simple text file and have it end up "sniffed" by IPM and interpreted as a job description language, causing the job to fail! In my case, the essence of the file consisted of two lines: File1 AAA And just that was enough to cause the file to be interpreted by IPM to be an HPGL job. I found that the second line can contain just blanks, and still be taken to be HPGL. Likewise if the first line's "File1" is shifted right on the line, or if the '1' is changed to any set of numbers. Case doesn't matter, either. For example, the following two, even more trivial lines will also cause IPM to believe the format of the file to be HPGL (quotes added here to make spaces apparent): " file1" " " (It's just as well the job fails, as you don't want ordinary text to be "executed" - who knows what may result.) 5010-606 The value start that was specified or defaulted for attribute auxiliary-sheet-selection is not supported by the destination or by any of its associated actual destinations. Host job submission command such as 'lpr' may by either default or specification create a job header page (separator page), but the destination does not support such. In the case of lpr, you have to invoke it as 'lpr -h ...' to suppress its default action of generating a header page. 5010-624 Each opening quote (' or ") must have a closing quote. Seen in a pdcreate where you have like: other-transform-options = "stuff... 'I=%#'" where the pound-sign (#) needs to have a backslash before it. This seems to be due to IPM's line parsing being inadequately programmed, failing to recognize that a pound-sign in quotes should NOT be taken as a comment starter. 5010-625 Cannot recognize attribute .... Can occur if you are using a GUI or command line client which is at a higher level thatn the server. 5010-631 System function IPMXFORM returned error number __. Message in the server error.log. The Infoprint Manager Transform Sequences manager, IPMXFORM, received a non-zero return code from the transform that it invoked. Error number 1 may be seen where IPM processes are being shut down in a pdserver restart and the ps2afp* processes go away. 5010-648 The Infoprint server ____ is using 70 percent of its available memory. 5010-642 Infoprint server acsn07 detected a memory shortage and is attempting to recover memory. Message set which one does not want to see, as it's usually fatal - contrary to pdmsg suggestions that the server will recover: you will see the server running with very high CPU and accomplishing virtually nothing. It may be that the server had been started with insufficient Unix Resource Limits and so is bumping its head on its session-imposed memory ceiling. You need to restart the server... In Csh, do 'unlimit', then 'limit', to remove limits on your session, then check the results. If you don't see "no limit" reflected for the data size, look into adjusting the AIX /etc/security/limits values for root to -1 (no limit) then try again. Note that /usr/lpp/pd/bin/startsrv has a hardcoded: ulimit -d 2048000 # data space in kbytes which may need boosting, depending upon the demands on your server. 5010-669 The requested operation could not be performed. The PSF backend return code = -1001. Seen when trying to shut down the printer icon in a new IPM server that is sharing a heavily used processor. A really dumb cause of this problem might be where the command 'host localhost' does not report 127.0.0.1, where the /etc/host file may be awry. The more substantive cause is the absence of the psfapid daemon, which should have started in startsrv, but could not, for some reason. There will be no logged evidence for why psfapid did not start, due to the choice of the developers. (My current suspicion is that the process is struggling to find usable port numbers.) 5010-669 The requested operation could not be performed. The PSF backend return code = -1002. Seen where the printer had a problem, is now functional, but the TCP feed process set is stuck from that time, like: ainhyper 25:49 00:00:00 /usr/lpp/psf/bin/./ainhyper prt1 ainhyper 21:52 00:00:00 /usr/lpp/psf/bin/./ainhyper prt1 ainmain 25:48 00:00:01 ainmain prt1 ain3dtcp 25:48 00:00:00 ain3dtcp 000 prt1 ainhyper 21:28 00:00:00 /usr/lpp/psf/bin/./ainhyper prt1 A pdshutdown on the printer won't work. You need to kill off the process set: work from the bottom upward until all of them disappear. 5010-762 Destination ____ does not support the combination of values specified in the transform-sequence and document-formats-supported attributes Oddly, even if both the "Transforms to use" and "Formats allowed" GUI blocks both allow the same thing (e.g., PostScript), you get this message. I found that by adding "MODCA-P" to the "Formats allowed" that the error goes away. It looks like IPM wants this flow-through format to also be there (no transform required). 5010-763 The request was cancelled due to a shutdown. We encounterd this lingering condition with a 1585 printer, where a 4 page job had seemingly gotten to its last page. The /var/psf/ error.log for the printer has "0423-409: InfoPrint is processing a pause request." for that job. Attempting to Resume the job gets "5010-568 Cannot resumit job ___ in server ___. The job is not paused." Attempting shutdown on the printer gets "5010-764 A similar shutdown request is already in progress". Attempting to Resume the printer gets no error, but "resume is in progress" persists. There is no AIX process in evidence involving this stuff. As a circumvention, we swapped that printer's ethernet cable with the cable for a former backup printer. The pdserver has to be restarted to clear the underlying issue. 5010-837 Printer ____ is offline. The specified printer reported, via SNMP, that it is offline. Printing on this printer is stopped until the problem is corrected. 5010-838 Printer ________ has a paper jam. Seen in the server error.log for an IPDS printer. See also related jam message 0420-466. 5010-840 Printer ________ is out of toner. May be that the printer is actually out of toner; or could have exhausted the Photoconductor, as on an Infoprint 1985 printer, with its front panel showing: 84 Replace PC Unit 5010-841 Printer ____ is out of paper. May be just that, when things are configured properly. However, when things are not as they should be on the printer, this can result where the right paper stock is not present in feed trays. An example is in PostScript printing, where the printer's trays have their paper guides adjusted to indicate that A4 paper is present, but printing requires Letter size paper. The printer control panel may then display the message MANUALLY FEED AUTO LETTER, where it deems Letter size to be the exception for the printer such that a human operator should flip down the manual feed opening (Tray 1 internal designation on an HP) to feed in a small supply of Letter paper. 5010-849 The SNMP connection to printer has been lost. IPM server error log message, which is normal for a printer that is down, and not to be concerned about if so. In trial circumstances, you may have configured the printer to use DHCP for its TCP/IP connection, and the DHCP lease expired, causing the TCP/IP connection to be lost. In the case of an AFP printer, performing a Shutdown on it, then Enabling, usually gets it back. Seen more commonly in early IPM 4.2 (where SNMP is very defective), though AD settings same as 4.1. Try boosting the snmp-timeout value. Note that these are server SNMP errors, and not printer errors: you will not see corresponding error indications in the /var/psf//error.log . 5010-890 User @ is not authorized to perform operation _____ on object _____. The username is null (nothing before the '@'). This typically results where it is a system daemon issuing pdrm/pdmod commands and the daemon was started (as a background task) without the LOGNAME environment variable being set, and thus effectively null. pdcreate: 5010-890 User ____ is not authorized to perform operation pdcreate on object . This can occur when running pdcrdflt even though the username is defined in all ACL security groups. Circumvention: Run as root (direct login, not sudo). pdls: 5010-890 User ________ is not authorized to perform operation pdls on object . A situation which doesn't make sense... The named user is trying to do a simple 'pdls -c queue :'. The pdls command allows anyone to run it. An the named queue had an ACL on it the day before, which did not include the user named in the message, but that ACL was removed, by command. The user can successfully perform the pdls on other queues (which likewise have no ACLs); so, this is an issue with that one queue. What's up? An IPM software defect, where the server seems to have stale knowledge of the removed ACL. The situation was resolved by creating an arbitrary ACL entry for the queue, then removing the ACL. Thereafter, this user could perform a pdls on the queue in question. This action seems to have straightened out the pdserver's knowledge of the ACL. 5010-890 User @ is not authorized to perform operation pddelete on object Encountered where fstsecutil security settings on the printer were: 'GROUP:admin:rwd' 'GROUP:oper:rw-' '*:r--' Doing 'fstsecutil -d 'GROUP:oper' -c p ' allowed the pddelete to then work for the administrator. This is probably because the administrator's username was also in the oper group, where the operators are naturally not given the ability to delete destinations. 5010-890 User @ is not authorized to perform operation pddelete on object . This, despite the presence of an ACL where the user has full rwd permissions on the queue, and the message identifies the user exactly as it is coded in the ACL. Can be caused by the queue having been defined with an associated-server attribute specifying a hostname other than the local system hostname, so things are rather confused. (When doing a pdcreate on a queue, let associated-server default to taking the natural hostname of the environment.) How to deal with this? Becoming root and executing the pddelete has been found not to help. Trying to delete it via the GUI yields "5010-065 Cannot find the object ". IPM AIX provides some resource creation/deletion tools in SMIT, but nothing for queue deletion. The best approach is to remove all entries from the ACL, and then the pddelete should work. "Failed to find VM - aborting" What direct invocation of /usr/lpp/pd/bin/notifyd reports, as you dig deeper into why startnotd is not starting notifyd. Caused if unable to load the Java libraries, which can be due to the notifyd binary containing a library path not reflective of the Java libraries actually needed, or incorrect permissions on the Java files. You can check the libpath via 'dump -H /usr/lpp/pd/bin/notifyd'. If you have a notifyd running okay on some AIX system, you can inspect its environment variables by doing the following, as root: 'ps eww '. killed by signal 11 Seen in the ps2afpd.log when trying to transform PostScript to AFP and the /usr/lpp/psf/bin/ps2afpd -C/usr/lpp/psf/ps2afp/ps2afpd.cfg daemon is not running. Start it to get services back. As to cause... Just above that message is the ps2afp command to transform the job. Examining the job file, I found that it contained binary garbage in fields that should contain ASCII text, specifically: @PJL LJOBINFO USERID = "" HOSTID = "WIN-I3LQJ035PKN" @PJL SET USERNAME = "" Within the PostScript proper, it had: %ADO_BeginApplicationHeaderComments %%Creator: Adobe Acrobat 10.1.0 %%For: revealing the originating application and further evidence of binary where text should be. pdrm: 5010-890 User operator@____ is not authorized to perform operation pdrm on object . You need to use SMIT to add operator to the IPM security group "oper". If you had added the user as "operator@host.", you may have to add as shown in the message, like "operator@host". pdrm: 5010-890 User @____ is not authorized to perform operation pdrm on object . Found to occur in a transform sequence, where I discovered the hard way that the transform sequence runs under no username; so if you attempt to perform a changing command like pdrm, it will fail on this error. Attempting to set environment variables USER, LOGNAME does not help: doesn't add a username. My solution was to do like: /usr/bin/su - operator -c 'setenv PD_CONFIRM_DELETE no; /usr/lpp/pd/bin/pdrm $job_identifier') & to perform the command "out of band", under a defined username. Remember to add operator to IPM security group "oper". This is the last logical destination that this actual destination is fed by, so it cannot be removed Seen in the admin GUI when trying to remove the last LD which feeds an AD, which you may be trying to do in redirecting all submissions to new printer definitions. The way around this is to perform a Copy on one of those LDs, to create a placeholder name, and leave that associated with the ADs which are not to be used. (The old ADs are being left around for a while just in case.) Unable to open message catalog This occurs when, insidiously, when environment variable LANG is set to En_US rather than en_US !! Or, /usr/lpp/pd/bin is not in your Path, such that when the 'startlpd' or like commands are invoked and internally try to invoke a simple test like 'pdmsg 123', that fails, and they put out this message. IPM SERVER START-UP MESSAGES: The server error.log will start with the following normal messages: D 09/15/03 14:07:31 [1 acsn07] 5010-676 The current number of jobs in the server is 4502. E 09/15/03 14:10:01 [90a acsn07] 5010-849 The SNMP connection to printer hspr1xt has been lost. A 09/15/03 14:10:04 [1 acsn07] 5010-432 The server is listening for requests. A 09/15/03 14:10:09 [2e2f acsn07] 5010-623 The process is listening on port 6874. D 09/15/03 14:10:09 [2728 acsn07,hspr2afp] 5010-373 The server acsn07 received a register signal request from the destination acsn07:hspr2afp. D 09/15/03 14:10:09 [2728 acsn07,hspr2afp] 5010-398 The destination acsn07:hspr2afp received a job status signal request from the server acsn07. A 09/15/03 14:10:09 [2c2d acsn07] 5010-623 The process is listening on port 2052. The following messages show an abnormal server start, where the server needs to be restarted: D 09/15/03 13:50:28 [1 acsn07] 5010-676 The current number of jobs in the server is 4520. E 09/15/03 13:54:37 [919 acsn07] 5010-849 The SNMP connection to printer hspr1xt has been lost. A 09/15/03 13:54:40 [1 acsn07] 5010-432 The server is listening for requests. E 09/15/03 13:54:45 [2d3d acsn07] 5010-314 Cannot establish communications for the Infoprint GUI application windows. E 09/15/03 13:54:45 [2e3e acsn07] 5010-315 The communication daemon is already running. A 09/15/03 13:54:45 [2c3c acsn07] 5010-623 The process is listening on port 2052. IPM SERVER PROBLEM SITUATIONS AND THEIR RESOLUTION: Actual Destination printer not printing, though printer is fine, there are jobs which show "processing" on the AD. The common reason for this is an issue with the printer, such as an Infoprint 2085/2105 with condition "061 Tray 1 not properly set. Reset tray 1.". Seen in 4.1 AIX server, at least when the AD Release Time is not 9999 (infinite): apparent software defect. Do 'ps -efl | grep ' and you will likely see an old ainhyper process, PPID==1 - far older than the same PPID 1 ainhyper for a viable AD. Also in the AIX Process Table you may find old ainbe processes for long-completed jobs. Treatment: Do a Shutdown on that AD. Look again for the processes. By virtue of the Shutdown, none should be there for that AD. If there are, then somehow, that AD ainhyper feeder process got stuck. Doing 'kill -9' on that PID has been seen to clear the situation. IPDS job repeatedly prints on a printer A given job fully comes out of the printer; then a moment later it will print again...and then again. Usually happes with Infoprint 1585. A look at the server error.log shows type D error: 5010-418 The request for job () returned from the PSF backend with the return code 64. And the /var/psf//error.log will likely contain: 0421-049: ERROR: A communications error occurred with the actual destination at address 111.222.333.444 ain3dtcp.c 1228 0420-049: ERROR: InfoPrint cannot communicate with the actual destination. where the 64 is the indication that the printer has fed back that it is having a problem, leading IPM to believe that the job did not print; hence the repetition. We saw this happen once after a 1585 had been fed a job in a PostScript printing manner, followed by an IPDS job. This is the kind of thing that a printer firmware update may resolve. Printing hangs on a PSF printer. You may encounter a limbo situation, where for example a job is part way through printing on an Infoprint 2105 but then nothing happens, and the printer Web page shows a normal status but nothing moving; and the /var/psf//error.log shows no issues. This might be caused by an old, looping ainbe process which is associated with a job which is long gone from IPM. See "ainbe" for handling. ps2afpi looping The PostScript interpreter process is looping - which can happen on an incomplete PDF, which the Adobe software tries (endlessly) to "repair". Doing 'kill ' will cause the process to regenerate and printing to resume. (Note that this situation can occur even if you manually do a pdf2afp on such a bad PDF, and ctrl-c the process: the ps2afpi associated process will still continue.) RIP fail condition suddenly starts occurring on many jobs. Typically caused by file system /var/psf filling, as can be found in the AIX Error Log (look for a JFS_FS_FULL record). The file system was probably undersized to begin with. In AIX, you need to perform 'chfs -a size=+_____ /var/psf' with an increment value equal some multiple of the number of 512-byte blocks in a Physical Partition (PP), assuming that you have sufficient leeway in the containing logical volume. INFOPRINT SELECT SITUATIONS: Spurious pop-up message Users of Infoprint Select may from time to time see something like the following in the notification pop-up box: what's up? MAILINFO:[239/2:8/35/338xpqk MAILINF2:[322/333/34:/223xpqj This is the result of a spammer (often, in Taiwan) seeking an open mail relay to facilitate spamming, and Infoprint Select employing a mail-based notification method. The spammer will attempt to send himself email through all port 25 (SMTP) responders which his program finds in scanning subnets throughout the world. The body of the mail contains the encoding as shown above, which allows him to recognize the message - if it gets through - and the IP address of the open relay, which he can subsequently exploit. Infoprint Select, of course, does not relay, so the probe fails - but the PC user wonders what this spurious message was all about. Such messages may be suppressed via IPSec filtering in Windows. With PTF U486582, Infoprint Select notifications only accepts messages from an Infoprint Manager server. If you are running an earlier level of Infoprint Manager, any extraneous messages that might be sent to the email port from another source are not discarded. MESSAGES FROM CUPS DSS PROCESSING: Filter "/usr/lib64/cups/filter/foomatic-rip" for printer "" not available: No such file or directory This message is incited by PPD files found in /usr/share/cups/model/, put into play by IPM CUPS DSS printing. This is because various PPD files, available from http://www.openprinting.org/printers and like places. If you inspect the content of some of these PPDs, you will find them say: PPD-O-MATIC (4.0.0 or newer) generated this PPD file. It is for use with all programs and environments which use PPD files for dealing with printer capability information. The printer must be configured with the "foomatic-rip" backend filter script of Foomatic 4.0.0 or newer. This file and "foomatic-rip" work together to support PPD-controlled printer driver option access with all supported printer drivers and printing spoolers. There is a Linux RPM for 'foomatic', which pulls in dependencies foomatic-db, foomatic-db-filesystem, foomatic-db-ppds. Filter "/usr/lib64/cups/filter/foomatic-rip-hplip" for printer "" not available: No such file or directory Encountered in CUPS printing because of the contents of the hp-laserjet_p4015-hpijs.ppd and hp-laserjet_p4515-hpijs.ppd files in /usr/share/cups/model/. Providing that library file would require an RPM which cannot be found. (The Unix printing environment is chaotic, with a lot of contributed stuff...which may not be well supported or well packaged, and whose pieces disappear over time.) The best remedy is to avoid these PPDs and instead use a more encompassing one, such as hp-laserjet_p4010_series-ps.ppd, which does not contain any foomatic stuff. Or use generic PostScript where possible. If you must accommodate this requirement, potentiall do what web page rpmfind.net/linux/RPM/opensuse/12.1/i586/hplip-sane-3.11.10-3.1.2.i586.html says, which is to create symlink /usr/lib/cups/filter/foomatic-rip-hplip which points to foomatic-rip. Unable to execute /usr/lib/cups/filter/hpps: No such file or directory This is called for by the active PPD (e.g. hp-laserjet_600_m601_m602_m603-ps.ppd) containing the line: *cupsFilter: "application/vnd.cups-postscript 0 hpps" The hpps filter is provided by the hplip package. See also: HPLIP PRINTER-SPECIFIC MESSAGES: 39 Page is too complex to print Seen on an Infoprint 1585 printer (OEM = Lexmark). Lexmark doc suggests adding memory: The page may not print correctly because the print information on the page is too complex (that is, too large for the printer memory). (This printer's memory = 256 MB.) This suggests that a PostScript job was sent to the printer for the printer to render, rather than IPDS. Where the printer is defined in InfoPrint Manager as PSF/IPDS, this suggests that someone submitted a job to the printer via surreptitious means, as by walking up to it and inserting a thumb drive. Load Manual Feeder With Plain Paper Letter Seen on an InfoPrint 1985 printer, on its control panel. Indicates that the job is trying to get its feed paper from the manual feeder, which on a 1985 means from the flip-down multipurpose feeder on the left side. Usually, this kind of thing is due to a PostScript job having been generated to explicitly use that feed tray. In the case that I saw, the job specified Letter size paper and going for manual feed, where that source was defined as having A4 size paper, hence the call for Letter size paper before the job can proceed. LOAD TRAY 1 PLAIN LETTER Seen on the control panel of an HP printer. Refers to the flip-down manual feed portal of an HP printer, which can accommodate about 100 sheets of paper, found on many HP models. Some host sent a job to the printer stipulating use of this manual tray, and the printer is waiting for a human to respond: until that is satisfied, the printer is hung. The IPM GUI will show a red icon for the printer and a status of "needs key operator". This situation is sometimes seen with a departmental printer which is being used for local ad hoc printing in addition to IPM driving of that printer. IPM should never want Tray 1 feeding, as that does not allow the kind of unattended printing that we need. (Note: Tray mapping can be confusing, as printers and hosts think of trays in different ways. In IPM definitions, "Tray 1" is the first auto feed tray on the printer, which in HP printers is its 500 sheet Tray 2. In IPM, if we ever did want to use the HP Tray 1, IPM would specify "Manual Feed".) A less common cause of this situation is where the PostScript driver is not matched to the printer, as for example trying to use an Infoprint 2190 PS driver on an HP printer. (Use a Universal Driver instead.) GOTCHAS TO WATCH OUT FOR: AFP/PSF error page contents: IBM made a *very* poor choice of fonts for the AFP/PSF error page: the upper case 'o' letter is completely indistinguishable from zero, so when an error message refers to something whose name contains O and 0 characters, you are at a loss. PDF TRANSFORM ERRORS: Analysis tips: - While PDFs are architecturally superior to PostScript and thus evidence fewer errors, when they do have errors they are notoriously inscrutable. - The acroread (Adobe Acrobat Reader) command will reveal PDF file defects...though not always readily. In particular, not that acroread will not reveal font issues which prevent printing: Reader is using its own font set, whereas IPM has a separate, PostScript font set for printing. - Running acroread on a sluggish processor is beneficial in being able to see the contents of a windowette which may quickly appear and disappear, too fast to be read, as acroread is starting, where that may be trying to report a problem with the file, such as "This file is damaged but is being repaired." - often followed by conclusion "There was an error opening his document. The file is damaged and could not be repaired." (In general, expect that any such start-up windowette is appearing because of a problem with the file.) - Though the PDF opens and displays (its first page), that by no means indicates that all is well with the file. In scrolling through it, you may come upon an error (often, an image) which acroread will report. - Scrolling through a PDF to seek errors is facilitated by shrinking the document window so that it "Greeks" (displays gray bars instead of resolving small text). This greatly speeds things along. The scrolling is best done by holding the mouse button down over the downward diamond. If there is an error in the file, acroread will stop on the bad page and put up an "i"nformational windowette noting the problem. (But, it does this just once on that page, thereafter remembering that the page is problematic.) Now, on with the show... %%[ Error: unable to convert PDF file to PS: (rc=40010017 (Desired operation cannot be performed on this object.)) ]%% Well, that certainly tells you nothing! Run acroread on the file. It will probably launch with a windowette reporting: "This file is damaged but is being repaired." Scroll all the way through the document, which will probably cause an "i"nformational window to pop up, interrupting the scrolling, saying: "Insufficient data for an image." Voila... bad PDF, bad. The PostScript error was: %%[ Error: not permitted to print PDF file ]%% Viewed with Acrobat Reader: under its File menu, select Document Security, revealing: "Printing: Not Allowed". When viewing such a document in Acrobat Reader, or other Adobe-compliant reader, you will find the File menu Print function grayed out (unavailable). These are PDFs with a built-in prohibition against printing, per security settings made by the PDF's author. Or, the Document Security setting may be "Printing: Low Resolution" (which lacks numericness), which may be incompatible with the dpi's handled by the printing system. (Adobe Knowledgebase article 53345 notes "Known Issue: Applying PDF 128-bit Encryption security with the 'encryptPDF' command results in a low resolution printing setting.") A Photoshop article on PDFs says "Low Resolution lets users print the document at no higher than 150-dpi resolution. Printing may be slower because each page is printed as a bitmapped image." 150 dpi is quite coarse (unproductive, as printing goes), and is normally not supported in modern printing. The Acrobat Reader help section says: "A PDF document author can choose to restrict access to a file by requiring an open password or by restricting the use of certain tools and commands." Found on the web: "You can limit access to all PDF files created by Distiller by giving the files passwords and restricting certain features such as printing and editing. You can limit the access when you first create a PDF file or any time you save the file in Acrobat. When files have restricted features, any tools and menu items related to those features are dimmed. A PDF file can have an open document password and a change security settings password. If the file has both passwords, it can be opened with either one. When a file is opened with an open document password, the security restrictions are temporarily disabled. If you set any security restrictions in your file, you should also specify a change security setting password; otherwise anyone who opens the file could remove the restrictions. Acrobat uses the RC4 method of security from RSA Corporation to secure PDF files." Obviously, there is nothing inspectable inside the PDF file relating to security. POSTSCRIPT TRANSFORM ERRORS: %%[ PrinterError: Low Printer VM ]%% %%[ Flushing: rest of job (to end-of-file) will be ignored ]%% 0423-175 ERROR: ps2afpd: The input file contains PostScript commands which resulted in an error. The PostScript error was: %%[ Flushing: rest of job (to end-of-file) will be ignored ]%% The status code out of the ps2afp is 51. We saw this with an 8-page Adobe Acrobat 11 job involving mathematical equations and a variety of fonts and sizes. The transform took 40 minutes before it failed, on the last page, where the ps2afpi transform process was using 100% cpu, thus indicating horrendous PostScript. The "Low Printer VM" error indicates bad PostScript programming, causing memory exhaustion. Later saw the same behavior with an AA11 job with Chinese fonts. A circumvention is to have the PC render the print file as images for printing. I investigated this by performing ps2afp operations on a large subject PostScript file, with increasing -M memory values. Each boost allowed the transform to get through more pages - but at the cost of much more elapsed time. It seems that Adobe Acrobat 11 is doing something to cause ever-increasing memory usage as the job progresses through more pages, though PostScript conventionally deals with each page separately. Finally got it to transform on a test server, where that took almost an hour! Horrible PostScript. This can be addressed by boosting the ps_max_memory value in /usr/lpp/psf/ps2afp/ps2afp.cfg and /usr/lpp/psf/ps2afp/ps2afpd.cfg - but be aware that this will then allow such horrid jobs to succeed in transforming, which can monopolize your server for long periods. Another approach is for the jobs to more efficiently use memory... Take a look at Adobe Acrobat 11 page: http://help.adobe.com/en_US/acrobat/using/WS58a04a822e3e50102bd615109794195ff-7bce.w.html which talks about Advanced PDF print settings for Acrobat 11. Look under "PostScript options", at the Font And Resource Policy settings, where memory consumption is described in the context of fonts. There, the Send For Each Page option seems a good choice for a student to use to get their job to print, which releases memory rather than allowing it to accumulate. size drss trss dvm prm file Part of the report output from ps2afp on AIX. Looks like: Tue Apr 16 16:11:28 2013 51.6 47.2 2.8 47.2 5% 8 size drss trss dvm prm file Meaning of the fields: drss Data resident set size trss Text resident set size dvm Data virtual memory size prm Percent real memory usage tsize Size of text dsize Current break value sdsize Data size from shared library (Fields come from the procsinfo struct in /usr/include/procinfo.h.) PRINT JOB SITUATIONS: Bogus job with Name (name-text) of "Remote Downlevel Document". From Microsoft Knowledge Base item Q162/4/47: When you print a document from a Windows 95 workstation to a printer shared on a Windows NT-based computer, multiple print jobs may appear in the printer's queue for the document. When this occurs, one print job displays a valid file size and all others display a size of zero bytes. If separator pages are specified for the printer, each print job has a separator page. Each separator page has a job number and description of "Remote Downlevel Document." Cause: This behavior can occur if anti-virus software is running on your Windows 95 workstation. To resolve this problem, one of the following methods: - Configure the anti-virus software not to scan your document files by specifying not to scan file types with extensions such as .doc and .txt. - Disable or remove the anti-virus software on the Windows 95 workstation. - Contact the anti-virus software manufacturer for updates to the program. --------- MS Article ID: 134779 addresses the same issue. --------- http://www.tech-archive.net/Archive/Win2000/microsoft.public.win2000.printing/ 2006-03/msg00057.html says: "Check the print queues on the workstations. These are probably Local Queues using a Local Port at the Print Server. If this is the case the Job will show up at the server as Remote Downlevel Document. This can be handled by using a Network Queue to the Share on the server rather than a Local Queue, the Document title will remain intact. If you have to use a Local Queue (Because it carries across Local Profiles where a Network queue does not) then enable Print Services for Unix on the Server and on the Workstations and use a Local Queue using an LPR port, rather than a Local Port. The Document title will not be replaced with Remote Downlevel Document when using an LPR port AND the document will spool a lot faster. --------- In a Job submitted through a Windows print server via SMB protocol, http://www.papercut.com/kb/Main/RemoteDownlevelDocument explains that "Remote Downlevel Document" is the default name which Windows gives to documents when the sender does not provide a document name, which in the Mac environment seems to be due to a CUPS SMB implementation shortcoming. --------- This may also be caused by Samba in old print job submission case. There were fixes to Samba to eliminate this. --------- Also seen with: %%Creator: PScript5.dll Version 5.2 which is the Pscript5 (PostScript) printer driver (pscript5.dll) for Windows 2000 and later... the Pscript renderer, which handles text output and renders images, then sends the text and image data to the print spooler. Empty print jobs with name "Remote Desktop Redirected Printer Doc" These will be seen in the queue with Format=ASCII and Size=1 (where the Size value is misleading: the job file size is actually 0 bytes). I have seen about a dozen of these arriving at one time. Web research shows that these are some odd side effect of a Windows user employing Remote Desktop Connection, likely due to a corrupt printer driver. The Samsung software Scan2PC.exe, for scanning with their multifunction printers, may be involved. The owner of the jobs may not even be aware that such jobs are being generated. One good report on the problem was found on page http://option9.blogspot.com /2009/12/random-empty-print-jobs-sent-to-network.html : "All I had to do was start a remote desktop session from a computer with network printers installed, to an XP computer on our network. I also had to choose the option to redirect local printers to the remote session for it to occur as well. Whichever network printers were installed on the local machine, and were redirected to the remote session, would receive a random amount of these empty print jobs. After scouring the internet for awhile, and involving Microsoft support, I discovered that our problem was related to a little 3rd party application called Scan2PC.exe -- which was installed with some drivers to a Dell multifunction printer that all of our executives have. So, if we started a remote desktop session to any XP computer that had this application installed, the problem happened. As soon as I removed the Dell drivers, the problem went away. Since our executives aren't planning getting rid of their brand new multifunction devices anytime soon, our current work around is to uncheck the box in the RDP session to redirect local printers to the remote session." Infoprint 2105(ES) slow: non-stapled job sheets sporadically emitted. With printing performing properly, sheets should come out of the printer one right after the other, with no delays between. In this case, the green light (Status Indicator) remains on in the continuous handling of an incoming IPDS job, but the printer will sporadically cycle up and emit a sheet of a non-stapled job, then cycle down, then repeat. With a job to be stapled, the sheets will accumulate inside the finisher area. This situation is characteristic of slow network speed, where the IPM server is sending IPDS to the printer as quickly at it can, but the printer is starved for throughput as the network speed is too slow. The network slowness could be due to improper network settings in the printer: check through its panel or web pages - and DO NOT allow an Auto setting, which is ambiguous and often wrong. The network slowness could also be due to configuration issues or capabilities in the network router/switch to which the printer's ethernet is connected. Multiple copies of a job printed: You find two printed copies of the same job, both with the same submitted time, but slightly different printed times. I've seen this where a shutdown was abruptly performed on a printer as it was busy processing one or more jobs. More odd: there will be no entries written to either the accounting log or jobcompletion log for the jobs! Expect to find a 0423-411 message in the /var/psf//error.log . PostScript printing: Image comes out small, at left edge of landscape output rather than filling a whole portrait image. This occurred because the printer's default settings were to print 3-up at 2400 dpi. You could override this via the IPM number-up attribute, but the printer setting is weird and should be normalized. In general: don't take defaults - always specify what you want; so set document and job defaults in IPM, and specify exactly what the job needs within the PostScript of the job. PRINTER WEB PAGE MESSAGES: Enter Basic Security Setup Password Building Block credentials ... As seen on an InfoPrint 1985 printer when you click on the Reports choice in the left pane, getting "Enter Basic Security Setup Password Building Block credentials for Reports Menu Remotely". It is unknown how the printer arrives in such a state that it prompts for a password like this. Such a condition needs to be cleared by forcibly resetting the printer, which has to be a physical action at the printer. Performing the reset from the printer control panel, using button hold-down methods in a power cycle, may or may not work. If not, open the printer's side hatch, which exposes part of its circuit board, and look for unoccupied or semi-occupied jumper pins, often unlabeled. (It is often called the SecurityResetJumper.) If found, power the printer down, then stick a jumper across the unused pin and its adjacent companion. Power the printer back up and see if the issue is resolved. PPFA MESSAGES: AKQ102E INVALID COMMAND / IS SPECIFIED. There is a defect in PPFA wherein a comment which begins with a line containing only "/*" is misinterpreted. Circumvent by throwing any other text onto the line. AKQ107E PARAMETER IN WHEN IS INVALID. It's objecting to something after the WHEN. A common error is to forget to code a PAGEFORMAT but not the NULL to say to continue using the same Formdef Copy Group. AKQ202E SPECIFIED INTERNAL OBJECT NAME IS NOT DEFINED. As when your Pagedef contains like "OBJECT PSG00001" but there was no OBJECT ____ ... OBXNAME ____ sequence to define that object. AKQ231E PRINTLINE or LAYOUT is not specified. Typically, when a PAGEFORMAT has been coded, but no PRINTLINE has yet been coded somewhere after it; or a SEGMENT is coded before a PAGEFORMAT rather than after it, where it is used. AKQ245E HEXADECIMAL TEXT IS INVALID. You specified an odd number of hex digits, like x'0' instead of x'00'. ARCHITECTURAL AND FUNCTIONAL DEFICIENCIES TO BE AWARE OF: Lack of printer-software integration: As jobs flow from Infoprint Manager to the printer (like 2085/2105), the identity and manageability they had in IPM is utterly lost. When they were in IPM, they had unique identifiability by ID, submitter, job name, etc. In the printer, they are assigned a wholly different sequence number, there is no evidenced job name, and no indication of the submitter. Lack of job management in the 2085/2105 printers: These printers will accept jobs submitted in a variety of ways: IPDS, LPD, IPP, etc. However, the printer interface provides no means of managing jobs once they are there... You cannot identify where jobs came from, who submitted them, or acquire other meaningful information. You cannot change the order of printing. You can only delete jobs - and there you are working in the dark, not having substantive job info. Once in the printer, there is no way to shift a job to another printer. Many open files: Using the Unix 'lsof' command, one sees a lot of open files for the pdserver process, for files in the /var/pd//pdb/spl_job/ directory. This implies that IPM can run out of Unix file handles if the system limit is not generous. Scalability: IPM has a number of architectural weaknesses which inhibit scalability. and they all resolve to the lack of a database in the product to track its jobs complement. This translates to limiting the number of jobs you can have in the system. The specific weak areas are: - Each user's jobs are tracked in flat file /var/pd//pdjobs. The frequent updating of a large, flat file is a classic performance limiter. - Individual job documents exists as individual files, all under the single directory /var/pd//. Having thousands of jobs in a single directory is a well-known performance limiter, as a directory is a very primitive, one-dimensional data structure. Output device type not reflected in accounting records: Neither the PSF printing jobcompletion.log nor the accounting records contain any indication of the type of output device. The only identification of the output device is its name. This makes monthly reporting rather awkward, as the administrator somehow has to keep track of printer types by name, often by hard-coding in the report program. For example: A site has a variety of IPDS printer types, and would like to have the monthly report accumulate statistics by type. With no such demarcation in the jobcompletion.log or accounting records, the report programmer has to maintain a table of printer types by name, keeping that up to date - a major nuisance. TIPS: Installing IPM: In AIX, it is wise to update /etc/security/limits to add the following to root's entry: fsize = -1 nofiles = -1 This will prevent functionality problems with the pdserver process in dealing with large job files/logs, and from keeping a large number of open files, as its psfapid process is prone to. To watch 2085/2105 printer state at the same time as the IPM queues: right-click on the printer destination, select Check Status, then "More information", and close the Destination Status window. This gives you an SNMP-refreshed image of the printer's panel, which will show you what's happening (slight time lag), allowing you to particularly see error conditions. How do you determine what print engine an IBM printer is based upon? IBM does not manufacture printers: they adopt the "best of breed" from established printer makers, to re-brand and tailor. So for a given model, how can you determine whose printer is really in the box? By looking up sources of consumable supplies, most conspicuos: toner. For example, if you search the web for toner for the IBM Infoprint 2060ES or 2075ES, you'll find supply vendors citing Ricoh Aficio 1060 1075 toner for those printers. ADVICE TO ADMINISTRATORS: Dedicate a server to IPM: Do not attempt to run IPM on a system which is already busy with other applications (e.g., a mail server), as this will result in a variety of functionality problems, including: - Server start-up issues, where other applications could prevent some IPM processes from getting ports they need. - Sluggish response to operations such as printer shutdown in the GUI, due to bloating of the system Process Table by other applications on the system, in conjunction with IPM's lousy programming in which object modules actually issue 'ps' commands to seek their own processes in the Process Table, rather than issue efficient system calls to gather such info. - Instances where the pdserver process sporadically fails to be responsive to client commands. This is particularly bad for jobs being sent through the LPD Gateway, where the jobs can fail to get into the IPM server ("5010-452 Cannot communicate with the communication daemon on port 6874"). Create a site control directory for IPM: Create your own control point...a directory which everyone knows to go to as the center of your administration and configuration of IPM, such as /var/Oursite/. In that directory create an IPMadmin subdirectory for all IPM administration files, under which you would have: - A file named +About_this_directory+, explaining what's in there. - A C-programs directory, for all the C programs you write for IPM. - A Definitions directory, for all your printer, logical destination, and other attribute files, for readily creating or recreating those server resources. - An Exits.development directory, wherein you develop all your IPM user exits. - A Formdefs.development directory, for Formdefs. - A Pagedefs.development directory, for Pagedefs. - A Transforms directory, for all your own job transform functions (most commonly written in Perl). - Various symlinks to useful locations in the /usr/lpp/ and /var/pd/ areas that you frequently visit, to get there quickly. The control point is of particular value after applying a PTF level, as it can be set up to point out the IPM areas where you have made changes ...changes which may be overlaid by the IBM maintenance process, and need to be reinstated by your control point tools. Create a site start-up and shutdown script for IPM: Oddly, IPM comes with no management script to thoroughly shut down and start up its environment. The only shutdown the product provides is via the stop_server command script or pdshutdown command, and those address only the pdserver process: this leaves all the affiliated processes up across a pdserver restart - which is a terrible idea. If an affiliated process is partially damaged, your new pdserver process will be running with a cripple, and that will inevitably result in server instability for which there will be no evidence in server logs, leaving you as the administrator in a situation where you have no answers. So, create an overall management script which assuredly disposes of all IPM processes across a restart. Don't leave superfluous printer definitions around: As one implements a TSM system and experiments with its facilities, there is a tendency to leave superfluous printer definitions in IPM. Don't! IPM restart involves testing every defined printer instance. At a minimum, this can delay server restart. Worse, a bad definition can cause the IPM server to fail to start! Superfluous printer definitions are an invitation to problems, and should be avoided. If you need to have a testing queue and LDs and ADs in your production server, keep them minimal, and turn off SNMP (use-snmp) where possible to reduce server overhead. Keep your IPM server software up to date: It's obvious that staying current with IPM server software adds new functionality and resolves problems. Less obvious, however, is another need: to have current transform software. Advances occur in document formats, and unless your IPM transform software also keeps up, your server may end up rejecting or failing to print perfectly viable jobs, whose features your server software simply can't recognize or process. An example is Adobe PDF "yellow hiliter", via a PDF creating application's highlighting/text markup tool, taking advantage of a new PDF capability to highlight or strike through text. On working with operators: I've found that a great, big, conspicuous, conceptual problem with the operation of IPM via a GUI on a PC is that the operators somehow get it into their heads that the job processing is occurring inside the PC!! Despite instructing them that the PC GUI is merely a window into the actual IPM server, they continue to harbor this notion. Anyone implementing IPM would do well to program their operators to understand that the IPM server is on a separate, high power processor. And, it doesn't help to restart the GUI or reboot the PC when job problems occur: that only makes things worse in losing the control point, and imposing a large Java load on the server in re-establishing the GUI's data repository. Minimizing server activity: The less your server is being called upon to do, the better it will perform, and the more stable it will be. Some elements to consider toward that end: - Don't have superfluous definitions hanging around: Having your server laden with obsolete or never used printer definitions at a minimum adds clutter to your server, and adds overhead - particularly start-up delays. Clear out the debris. You always have batch definitions files available to redefine anything that needs to be, so pointless stuff does not have to be left around in the server. - Nullify notifications unless actually needed: When a printer or other IPM resource is defined, it will get a default notification profile, enabled for various events. If you don't care about such notifications (few sites do), then change the notifications to "none", and save the server the travail. In a university or other general user service environment, be ready for any types of data: You will be amazed at the things that users think to send directly to the printer... BMP files, Microsoft Word data files, SAS data files, HTML, binary zeroes, locked PDF files. Be prepared to find red-iconed jobs being crud. Establish a site files directory: You will inevitably be tailoring IPM facilities, such as creating transforms, Formdefs, and user exits. You want a known, central location where you will either store or point to storage locations where these site resources are maintained. (This is particularly vital when there is a problem which requires quick action...which is all the more difficult when adrenaline impedes clear thought as to where things are.) So establish a site directory, such as /var/pd/Oursite/. In it, create an "+About_this_directory+" file to describe contents. Create printer (re)definition shell scripts therein, which can quickly recreate IPM definitions in case of calamity disappearance. Create symbolic links to other resource locations (documentation directory, etc.). Managing your print queue: With on-demand printing, such as in a university environment, with many incoming jobs, there is the temptation for operators to let the small ones through first, to decrease the queue numbers; but this is a bad idea, in that you will subsequently suffer from space issues as just small jobs expire first, leaving the glut of large jobs around to expire at a significantly later time. Don't over-query the IPM server: The server is quite busy handling all the work involved with jobs arriving and being printed. If the server is barraged by pdls and lpq type queries, it can bog down - and even hang. A good way to keep the server from getting too many queries is to set up a formal querying task which will populate a Web page which people can reference to see what's happening in the server. Many people can then look at that page rather than flood the server with queries. Be prepared to be disappointed by operations groups: The operations groups in computer centers are typically staffed by entry level people who generally lack interest in what's going on, and make no effort to learn. The less you expect from them, the less disappointed you will be. ADVICE TO PRINT JOB SUBMITTERS: "Pre-flight" your major jobs and reduce stress: Print Preview is a common capability in today's operating systems, which should be used to advantage to check how large jobs will/should look. Performing such a preview will save you a lot of stress and wasted time, and avoid costly paper & toner waste in iteratively printing your job until it is right. When FTPing a PDF, use Binary mode: PDFs are binary files, like compiled programs, and contain internal position pointers. Text mode FTP likes tailor what it thinks are text lines, to suit the destination platform - which can add or eliminate bytes and thus throw off internal positions. How to print directly from your Macintosh to a campus Unix system printer: Your Mac OS X is Unix, and if your campus server is also Unix, you can use the following technique to print an ASCII, PDF or Postscript file on your campus system printer, all in one step: Open the Mac Terminal utility or an X11 window and enter the following single command (here, spanning multiple lines): ssh -l YourCampusAccountName YourCampusServerName lpr -P PrintQueueName -J MyJobname < The_Filename This uses Secure SHell (encrypted) on your Mac to invoke the lpr command on ACS and print the file you redirect via standard-input to ssh, which feeds it to lpr with the assigned job name. All in one step. You can omit the "-l YourCampusAccountName" if your Mac account name is the same as your campus account name. (Some users set up informal names for themselves on their Macs, which makes things inconvenient when that interaction is required.) Keep the server clean: Experience shows that if left-behind files accumulate in the server's file systems, you will likely have stability problems: keep the house clean, and you will likely not experience problems. Pdserver restarts and job aborts might leave files behind, which IPM may "trip over" as it conducts its business. A conspicuous example is job submission files in the /var/pd// directory: IPM generates randomized file names for the jobs therein, and it is possible for a new name to randomize to one matching an old, left-behind file - which may cause pdserver to loop. Do periodic, intelligent housekeeping to avoid problems. REPORTING PROBLEMS TO IBM: See: Server trace Severity 1 Product down - need resolution ASAP 2 Severely restricts product operation 3 Does not critically impact product operation 4 Causes little impact to product operation HOW TO APPLY FIXES (PTFs, APARs) TO INFOPRINT MANAGER/AIX: See the "PTF levels ..." entries in the glossary section for an historic list of PTFs and their identifications. Resources: http://www.printers.ibm.com/R5PSC.NSF/Web/ip410ser contains information about the update and a link to the README ("IBM Infoprint Manager for AIX 4.1.0 README"). In 4.2 there is instead "Infoprint Manager Family Release Notes for AIX (Version 4.2.0) and Windows (Version 2.2.0)", Technote P1000691. ftp.software.ibm.com/printers/products/infoprint/fixes/410/ and ftp.software.ibm.com/printers/products/infoprint/fixes/420/ contains files like: Name Size Kind Last Modified UR53740C.zip 318,098K PC ZIP Archive Fri, Nov 22, 2002 cclient.U484268.tar 422,400K Unix Tape ARchive Thu, Nov 21, 2002 server.U483882.tar 297,930K Unix Tape ARchive Fri, Sep 6, 2002 server.U484268.tar 456,680K Unix Tape ARchive Thu, Nov 21, 2002 Sadly, the directory does not contain a README file as it should, to identify the contents. (This has been reported to IBM.) The following types of files can be found in the FTP area: .iso An image of the CD, around 600 MB or a bit less. This typically has to be burned to a CD to be usable in applying a PTF level. On a Macintosh, this can be easily performed via the Disk Utility. The CD could then be used directly with the ip_update command, or you may copy its contents to a directory on the AIX system, which ip_update can then work on. .zip Contains the files suitable for Windows. .tar The corresponding package to get all components to AIX. The contents would be un-tar'ed to a directory which the ip_update command could then work on. Both types of packages contain both PC and AIX elements. The files are also versioned by platform usage: In the PTF file name form, uNNNNNNx.___, the x is one of the following: c Common Clients m Macintosh Client s Server software The README is contained in FTP area ftp.software.ibm.com/printers/products/infoprint/fixes/420/info/ AIX fileset levels: _LEVEL__ _CIRCA__ 4.1.0.0 09/25/02 4.1.0.20 11/07/02 4.1.0.40 10/13/03 4.1.0.60 10/13/03 Procedure for installing client fixes: - To download the CD-image zip file, double-click on the zip file icon. - Unzip the resulting file, using WinZip, Aladdin, or like utility. - Review the README file in the unzipped directory. - The README has thus far recommended uninstalling old versions of components before installing new ones. Remember to also delete the old shortcuts that you may have created. - Double-click on the colorful LAUNCH icon to bring up the familiar "IBM Infoprint Manager Common Clients CD-ROM" buttons interface for selecting the components you want to install; Or: dive into the component directory and double-click on the colorful SETUP appl or INSTALL appl - whichever appears in the directory for that component. A "JVM not found" message in a logon after a client install usually means that you had the GUI in your startup folder, to start automatically when you log on, and the image there is a shortcut for the old version of the JVM, replaced by the new one. So you have to remove the old shortcut and create a new one. Procedure for installing server fixes (PTFs) under AIX: Note: An AIX restart has not been required for a PTF upgrade. Warning: Applying maintenance will likely replace any IBM-named modules or files which you modified for your site's purposes. Examples of such files would include: /usr/lpp/psf/bin/ainuxjobcompletion /usr/lpp/psf/ps2afp/ps2afpd.cfg So, assure that you have a backup copy of any such files before embarking upon a PTF install, for re-installing your mods thereafer. - Research available fixes on the IBM web site. The comprehensive resourse is Technote P1000700, "Infoprint Manager for AIX Service Summary for Versions 4.1 and 4.2" Also search the IBM site for APAR-number-specific material. The README explains how to use this release. PTF application may be described there, but is in the Getting Started manual. - Create and enter a subdirectory to contain it all, in a sufficiently large area on the IPM system, like: mkdir U810787.April2007 cd U810787.April2007 - FTP the server.U*.tar file from the IBM FTP site, in binary. - Un-tar the tarball so it can be used, like: tar -xvf u810787s.tar (Note that you may need to be root to do this, as we've seen the directories in the tar file have r-xr-xr-x permissions, prohibiting writing into them by a general user.) The AIX filesets will be found in the images subdirectory, which comes with a .toc already built (no need to run /usr/sbin/inutoc yourself). - Review the readme files. - When ready to apply: - Capture the image of the current maintenance level: lslpp -ql ipr.\* > pre-ptf.filesets - Shut down IPM. (The maintenance command will do this itself, and kill off *all* IPM processes - not just the server - but it's always desirable to have a clean administrative shutdown. And, by virtue of having shut down the server yourself, the maintenance command will not attempt to start it, giving you time to review results.) - Back up the current Infoprint Manager configuration, just in case. - cd into a directory where your data captures can be saved. - It is wise to employ the AIX 'script' command to capture a record of what transpires, in a non-volatile file system. (The update saves some records in /tmp, but that's relatively volatile.) - Enter the command (refer to "ip_update" entry): /...path.../U810787.April2007/ip_update -s /...path.../U810787.April2007 (where the -s spec says to use the disk directory rather than assume /cdrom/.) - Review/capture the resulting log (/tmp/ip_update.wlog). - Reapply any local mods to IBM-named modules that the PTF would have supplanted. - Start IPM and check it out. - Check that your Security ACLs are still as you set them. - If all looks good after a reasonable period of running, commit the maintenance, by one of the following two methods: /...path.../U810787.April2007/ip_update -s /...path.../U810787.April2007 -c or installp -cg ipr (You should commit maintanence prior to applying the next level of maintenance, so you can readily back out only the most recent stuff, if necessary). PERFORMANCE ANALYSIS: A properly allocated and configured IPM server system will be able to generate AFP for its printers, from average difficulty jobs, faster than the combined rated speed of its associated printers. One good way to see if this is happening is to inspect the /var/psf/psf2afp/ps2afpd.log, where the transform will record its page generation speed, like: Wrote 3 pages of output type AFPDS IO1 (G4 MMR, 260), at approx 502.02 ppm You may suffer from disk/file system performance issues. IPM hurts itself by keeping all job files - pending, processing, and retained - in a single directory (/var/pd//), which makes for directory updating congestion. Employ conventional analysis tools (iostat command, etc.) to inspect. Notes: If you repeatedly do 'tail /var/psf/ps2afp/ps2afpd.log' you may see the last line to be like: unlinking file /var/psf/ps2afp/PSscreen/c24f9132.T with a size of 14586 This does not necessarily mean that IPM is wating on a file deletion to complete in the file system. Indeed, the transform process may be well beyond that point, where that's simply the last message which appeared in that log. DEBUGGING METHODS: AIX print command options sent to IPM: As noted elsewhere in this doc, the AIX print command are peculiar in all resolving to an invocation of /usr/bin/enq, and containing an interface to IPM through its pdenq module. Thus, printing to IPM in AIX usually involves the invocation of two intervening modules, enq and pdenq. Investigation of problem situations may require knowing just what options are being passed to enq, pdenq, or both. How to determine what optinos are being passed? One method is to supplant the real module with a surrogate program for the few minutes that it takes to gather that data, where the surrogate will do nothing more than report command line arguments (very simple programming). That method is fine if you can afford to take away standard system modules during a quiet time. But if you can't, another method is to make a copy of the sending module and change its references to be the path of your own module. For example, if you want to see what options the /usr/bin/lpr command is sending to the /usr/bin/enq module, you would copy /usr/bin/lpr to a convenient directory and, using emacs or the like, change all /usr/bin/enq internal references to a same-length path to your own module, like /tmp/joe/arg, where that target module would report the arguments it received. MIBs TABLE: IPM extensively used SNMP MIBs for cataloging all the ingredients with which it operates, addressed by OIDs (dotted numbers. Here is a table of known values: (We were forced to delve into this after pursuing a problem with IBM and getting no substantive help such that we had to figure it out by ourselves.) 1.0.18.0.4.2.3.2.22 Device status. 1.0.10175.1.3.0.1 Description, as used in LD et al. 1.0.10175.1.3.0.10 Language being used (e.g., 1.0.10175.1.3.1.32 job-hold attr value, in the pdb/spl_job/ file. 1.0.10175.1.3.1.89 document-file-name attr value string. 1.0.10175.1.3.1.205 modification-time attr value. 1.0.10175.1.3.2.100 Device definition (the ___.dd file in the server directory). 1.0.10175.1.3.2.0 Logical Destination name. 1.0.10175.1.3.2.3 Model (destination-model) en_US.ISO8859-1) 1.2.840.113554.1.1.3.1.229 queue-assigned job attr value. 1.2.840.113554.1.1.3.2.3 Queue name in an AD. 1.2.840.113554.1.1.3.51.5 Name of LD which feeds an AD. List of LDs in a Queue. 1.3.18 The IBM Objects tree. 1.3.18.0.4.3.3.2.4 AD: destination-command (destination-tcpip-internet-address) 1.3.18.0.4.3.3.2.6 Device (device-name). 1.3.18.0.4.3.3.2.58 Formdef name (form-definition). 1.3.18.0.4.3.3.2.66 TCP/IP destination address 1.3.18.0.4.3.3.2.119 Device driver name in LD (client-driver-names) 1.3.18.0.4.3.3.2.151 AD: Transform to use (transform-sequence) 1.3.18.0.4.3.3.15.4 Transform options (other-transform-options) 1.3.18.0.4.3.6.2.1 Name (Queue name, Transforms program name, etc.) RESOURCES: Common Clients CD (LCD4-1917): Contains separately installable components: - Infoprint Select Allows print job submission from Windows applications and the Infoprint Manager command line to destinations managed by an Infoprint Manager server. - Infoprint Manager GUIs Allows you to administer and oversee print operations from remote systems. - Infoprint Manager Notifications Enables remote systems to receive messages from the Infoprint Manager server. - AFP Printer Driver for Windows Allows you to create a Windows printer that generates AFP output. - IBM Cross Platform Technologies for Windows (CPT) version 2.0 The IBM Windows Java Runtime Environment for the GUIs. Ref: Getting Started manual Download from: ftp://ftp.software.ibm.com/printers/products/infoprint/fixes/ as like U486582cc.zip . The contents of a typical Common Clients CD: BIN/ COLORRIPD/ DRIVERS/ HPUX/ IMAGES/ IPGUI/ JRE/ LFCLIENT/ NOTIFICATION/ PRT/ SAP CLIENT/ SELECT/ SUN/ AIX.ID AIXCLIENTREADME (HTM File) AIXCLIENTREADME (PDF) AIXCLIENTREADME (Text Document) AUTORUN CLIENTCD LAUNCH (Application) LAUNCH (Configuration Settings) README (HTM File) README (PDF) README (Text Document) SETUP Note that the Readme files provide usage instructions, but no hint of the level of the software contained on the CD. You can verify the level of the CD by inspecting the AIX:ID file, which will identify the level as like "AIX_APAR IY33202", which can be correlated with the IBM site Technote "Infoprint Manager for AIX 4.1 Service Record" (P1000567). Mailing list: AFP-L www.topica.com/lists/afp-l IBM Advanced Function Presentation: Library Catalog (including ACIF User's Guide): http://www.printers.ibm.com/R5PSC.NSF/Web/afpm Infoprint Solutions Company Information Center: (for all the new manuals since the advent of that separate company, with all older manuals to be found on IBM's site) http://publib.boulder.ibm.com/infocenter/printer/v1r1/index.jsp Advanced Function Presentation: architecture library catalog including bar codes: http://www.printers.ibm.com/R5PSC.NSF/web/archm ACIF User's Guide: http://www.printers.ibm.com/R5PSC.NSF/Web/afpm http://publib.boulder.ibm.com/epubs/pdf/ib6a9103.pdf AFP, general http://www.afpworld.com/ An assemblage of tools and resources, but could be more impressive. http://en.wikipedia.org/wiki/Advanced_Function_Presentation http://en.wikipedia.org/wiki/IBM_Advanced_Function_Printing_(AFP) University of Missouri System, AFP Guide (useful AFP fonts reference) http://system.missouri.edu/itss/ss/guides/afp-guide.html Maas AFP tools site (AFP to PDF converter): http://www.afp2web.com/ AFP & Full Color (presentation by Gary Currie, IBM UK): http://gsenl.gse.org/Werkgroepen/more-afp/afpcolor-nl%20GC.pdf AFP & related tools: http://www.compulsivecode.com/projects.html Includes AFPexplorer, AFPviewer, AFPextract. AFP Consortium: http://www.outputlinks.com/SpecialInterest/AFPColorConsortium/home.html AFP Font Collection: http://www.printers.ibm.com/R5PSC.NSF/Web/AFPfonthome AFP Printing Performance ("Factors Which Can Affect AFP Printing Performance"): http://www.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/WP100289 AFP Terms and Abbreviations http://www.isis-papyrus.com/englishweb/pages/abbreviations.html AFP Toolbox (for programmers to generate AFP-based print jobs, including bar codes (barcodes)): http://www.printers.ibm.com/R5PSC.NSF/web/toolbox Download: ftp.software.ibm.com/printers/products/toolbox/aix/afptoolboxfile1.tar ftp.software.ibm.com/printers/products/toolbox/aix/afptoolboxfile2.tar ftp.software.ibm.com/printers/products/toolbox/aix/afptoolboxfile3.tar ftp.software.ibm.com/printers/products/toolbox/aix/afptoolboxfile4.tar ftp.software.ibm.com/printers/products/toolbox/aix/afptoolboxfile5.tar ftp.software.ibm.com/printers/products/toolbox/aix/afptoolboxfile6.tar ftp.software.ibm.com/printers/products/toolbox/aix/afptoolboxfile7.tar Manual: http://publib.boulder.ibm.com/prsys/pdfs/54452924.pdf off of: http://www.printers.ibm.com/R5PSC.NSF/Web/afpm AFP User Guide For the State of Wisconsin (restricted access now?): http://deg.state.wi.us/static/e-datacenter/afp/afpuser.pdf AFP Viewer plug-in (q.v.): http://www.printers.ibm.com/R5PSC.NSF/Web/afp_viewer_plug-in Bar Codes: "Data Matrix Bar Code PPFA Programming Examples" (FLASH10231) Conventions / Exhibitions: IPEX, one of the world's top four exhibitions, focused exclusively on the print, publishing and media industry. WWW.IPEX.ORG XPLOR Datastream dump: http://www-1.ibm.com/support/manager.wss?rs=0&rt=6 &navkey=2ByDocumentCategory&nid=184054&r=10&p=1 Entitlements (licensing) site: https://ricohsoftware-entitlements.com Fonts: Font collection, with downloads: http://www.printers.ibm.com/R5PSC.NSF/web/fontcoll Font Summary for AFP Font Collection http://publib.boulder.ibm.com/prsys/pdfs/54456332.pdf AFP Conversion and Indexing Facility: User's Guide (incl. ASCII fonts) http://publib.boulder.ibm.com/epubs/pdf/ib6a9103.pdf Font utility: BitFonter (Mac): http://www.fontlab.com/html/bitfonter.html Formdefs source: ftp://service.software.ibm.com/printers/products/ppfa/source/ Hardware and software downloads for IBM printers: http://www.printers.ibm.com/R5PSC.NSF/web/download HP manuals: http://www.laserjet.co.uk/manuals.htm Infoprint Manager web page: http://www.printers.ibm.com/R5PSC.NSF/Web/ipmgrfamilyhome Infoprint 21: http://www2.ibmlink.ibm.com/cgi-bin/master?xh=c3YJJMJfMG6S2y1USenGnN9332 &request=announcements&parms=H%5f100%2d102&xfr=N Infoprint 32, Infoprint 40: http://www.printers.ibm.com/R5PSC.NSF/Web/fsip32 Brochure: ftp://ftp.software.ibm.com/printers/specs/fsip32.pdf Manuals: http://www.printers.ibm.com/R5PSC.NSF/Web/ip32m Infoprint Manager server and client PTFs: ftp://ftp.software.ibm.com/printers/products/infoprint/fixes/ On the IBM web site, you can search for docs like: "IY38416 - INFOPRINT MANAGER V410 SERVICE UPDATE 2 PTF2" See also topic: PTF levels for IPM ... Infoprint 2085/2105 manuals: http://www.printers.ibm.com/R5PSC.NSF/Web/inprt2085m Infoprint 2085 and 2105 User's Guide (English): http://publib.boulder.ibm.com/prsys/pdfs/54458240.pdf Infoprint 2085 and 2105 Quick Reference (English): http://publib.boulder.ibm.com/prsys/pdfs/54458250.pdf Infoprint 2085 and 2105 Network Configuration Guide (English): http://publib.boulder.ibm.com/prsys/pdfs/54458310.pdf Infoprint 2085 and 2105 Planning Guide (English): http://publib.boulder.ibm.com/prsys/pdfs/54458380.pdf Infoprint printers microcode: 15xx,16xx series (note that the IP 1145 is a Lexmark W820 and the 1585 is a Lexmark W840): ftp://ftp.software.ibm.com/printers/drivers/ip1500/ucode/ ftp://ftp.software.ibm.com/printers/drivers/ip1500/ucode/w820.zip Information on Printers from InfoPrint Solutions Company and IBM Printing Systems http://www-01.ibm.com/support/docview.wss?uid=nas8N1019535 IPDS general: http://en.wikipedia.org/wiki/IPDS IPDS Handbook: http://publib.boulder.ibm.com/prsys/pdfs/54438959.pdf Overview of Infoprint Manager for AIX In the redbook "Printing for Fun and Profit under AIX 5L". PDF: Adobe PDF Reference: http://www.printers.ibm.com/R5PSC.NSF/Web/ipmaixftp About: webservices.nic.in/html/aboutpdnew.pdf Printing Systems Terms Glossary: http://www.ibm.com/support/docview.wss?uid=tss1td101226 (IBM Document ID: TD101226) PCL Sample file: /usr/lpp/psf/pcl2afp/sample.pcl PCL class: www.uni-karlsruhe.de/Uni/RZ/Personen/rz65/PCL5/pcl5/Package-pcl5.html PPFA manuals page: http://www.printers.ibm.com/R5PSC.NSF/Web/ppfam (had been http://www.printers.ibm.com/R5PSC.NSF/Web/afpm) PPFA User's Guide: http://publib.boulder.ibm.com/prsys/pdfs/54452846.pdf PPFA Quick Reference: http://publib.boulder.ibm.com/prsys/pdfs/54437016.pdf Infoprint Manager General FAQs: http://www.printers.ibm.com/R5FAQ.NSF/ipmgeneral IPP Expert Test System, for Windows: http://www.qualitylogic.com/genoa_test_tools/printer/ipp.html IBM Infoprint 2085/2105 Service Guide manual is part number 75P2726 Staples for the IBM 2085/2105: UNEQ, Inc. 321 W. Exchange St., Akron, Ohio 44302 is prompt and inexpensive. Web page: www.uneq.com (which sometimes does not respond) Understanding Line Data Formats: http://www.naspa.com/PDF/2001/0201%20PDF/T0102005.pdf PJL Technical Reference Manual: 10th edition, 1997/10: http://www.lprng.com/DISTRIB/RESOURCES/DOCS/pjltkref.pdf 12th edition, 2003/06: h20000.www2.hp.com/bc/docs/support/SupportManual/bpl13208/bpl13208.pdf Printer firmware downloading: http://www.printers.ibm.com/internet/wwsites.nsf/vwwebpublished/wgsupt_ww is available for that purpose, restricted via a keycode which you can obtain as a registered customer through Technical Support. See also: Infoprint printers microcode: File formats: General: http://www.wotsit.org http://www.prepressure.com/formats/formatoverview.htm Graphics: http://www.why-not.com/articles/formats.htm BMP: http://www.daubnet.com/formats/BMP.html GIF: http://www.gifworks.com/ Includes online GIF editor. IBM JVM (Java): http://www.ibm.com/support/docview.wss?uid=swg21160795 Infoprint printers repair procedures: ftp://ftp.lexmark.com/depot/IBM/ such as: ftp://ftp.lexmark.com/depot/IBM/Info_112x_Depot_Repair_rev072406.pdf JPEG: Image File Compression: http://www.catenary.com/appnotes/jpegcomp.html Image compression FAQ: http://www.faqs.org/faqs/jpeg-faq/ Image File Fundamentals: http://www.ramsayphoto.com/basics.htm Desktop publishing tips: http://www.printstop.com/tips.html The Graphics File Formats Page http://www.dcs.ed.ac.uk/home/mxr/gfx/2d-hi.html PostScript FAQs: http://www.faqs.org/faqs/postscript/faq/ PostScript Sources: http://www.faqs.org/faqs/postscript/ IBM "Machine Type" and serial number locations for a given printer model: "Find the machine type, model and serial number for your printer": www.printers.ibm.com/internet/wwsites.nsf/vwwebpublished/machinetype_ww For cut-sheet printers: www.printers.ibm.com/internet/wwsites.nsf/vwwebpublished/serialcs_ww Infoprint Manager for AIX support: http://www.printers.ibm.com/internet/wwsites.nsf/vwwebpublished/ipmaix_ww Contains links to subject areas: Product overview; Announcements; Manuals and publications; Downloads; Technical information. Information on Printers from Various Manufacturers: https://www-304.ibm.com/support/docview.wss?uid=nas8N1019605 Maintenance/PTFs: http://rpp.ricoh-usa.com/products/software/manage/infoprint-manager Select support and then the pulldown menu (downloads & drivers) TIFF file format: http://partners.adobe.com/asn/developer/pdfs/tn/TIFF6.pdf http://www.faqs.org/faqs/graphics/fileformats-faq/part3/section-147.html http://en.viasolutions.com/paroles_expert/fichierstiff.html http://kb.indiana.edu/data/afjn.html Paper sizes: http://www.metrication.com/drafting/paper.htm International Standard Paper Sizes: http://www.cl.cam.ac.uk/~mgk25/iso-paper.html Guide to International Paper Sizes: http://home.inter.net/eds/paper/papersize.html International Paper Sizes - A Compendium of Measurements: http://home.inter.net/eds/paper/index.html Weights and Sizes of Papers: http://www.inkjetart.com/weight.html Old English Paper Sizes: http://www.baph.freeserve.co.uk/information/papersizes.html Printer images: At www.infoprintsolutionscompany.com/, go into the ABOUT INFOPRINT area, and thereunder fine Image Gallery. Workgroup printers; http://www.infoprintsolutionscompany.com/internet/wwsites.nsf/ vwwebpublished/ai_imggalwghome_us Printer manuals: http://www.retrevo.com/ Printer MIBs (SNMP): http://www.pwg.org/mib/index.html Printer PPDs and info: http://www.openprinting.org/printers There you can get files on a large number of printers. Printing RFCs: http://www.cups.org/documentation.php SNMP overview: http://www.wtcs.org/snmp4tpc/snmp.htm http://www.adventnet.com/products/snmputilities/help/quick_tour/ snmp_and_mib/snmpmib_snmpoverview.html Printers explained and reviewed: http://www.laser-printer-reviews.org/ http://www.pctechguide.com/ http://reviews.cnet.com/Printer Windows printing: Understanding Microsoft's PostScript print driver "PSINJECT": http://www.unixwiz.net/techtips/psinject.html Withdrawn printers and their replacements: "Printer replacement table" www.printers.ibm.com/internet/wwsites.nsf/vwwebpublished/replacement_ww