 |
|||||||
|
|||||||
NeoMedia's Product SupportPDF417 Frequently Assked Questions (FAQ) General Questions MVS and OS/390 AS/400 Printing How does generating and printing PDF417 symbols differ from other barcodes?Unlike many one-dimensional barcodes (like Code 128 or Code 39), PDF417 symbols cannot be printed by simply using a special font. While NeoMedia does provide a custom font for printing a PDF417 symbol, this is done to simplify the task of printing the symbol. The majority of the work is performed by the encoder, a callable library routine. The encoder is a sophisticated piece of software that performs all of the necessary formatting, data compaction, and error correction that goes into a PDF417 symbol. In general, how does the PDF417 encoder work?NeoMedia's PDF417 product consists of two components; a callable library routine, and a special PDF417 font. Your application program must call this library routine with the data you wish to "encode" in the PDF417 symbol. The library routine returns a buffer of characters (510 characters to be precise). Your application program then sends these characters to the printer, using the PDF417 font. The complexity of this final step depends on your printing environment. What's the minimum version of MVS supported?The encoder has been tested as far back as MVS 5.2.2. The encoder may work on earlier version; however, we do not have the facilities for testing these versions. The C runtime libraries must also be present (e.g., as part of LE/370) and must be compiled in AMODE=31 (the default). Your calling program must also be running above the line to call the encoder directly. What's the minimum version of OS/390 supported?The encoder is currently support by all versions of OS/390 (V1 R1 through V2 R6). The C runtime libraries must have been installed and compiled in AMODE=31 (the default). Your calling program must also be running above the line to call the encoder directly. What programming languages are supported?The PDF417 encoder is distributed as an application callable load library (written in C). COBOL II and C are directly supported. Other languages like RPG and PL/I, while not documented, should work with the encoder. Sample programs written in a variety of languages are provided. How is the PDF417 library linked with my application?Our PDF417 routine is shipped as a load library and can be linked either statically or dynamically with your application. When the library is first installed on your system it must be linked with your C runtime libraries. JCL for this step is provided. What's the minimum version of OS/400 supported?The minimum version is V3R2M0. Are Original Programming Model languages (COBOL/400, RPG/400) supported?Yes. The PDF417 encoder is distributed as an ILE service program. However, a special ILE interface programs have been provided for OPM and EPM environments that invoke the service program for the calling program. Sample COBOL/400 and RPG/400 programs are supplied which demonstrate the calling convention. Are Integrated Language Environment languages (ILE COBOL, ILE RPG) supported?Yes. The PDF417 encoder is distributed as an ILE service program. The CRTPGM command is used to link the service program with your ILE modules. A sample ILE COBOL program is supplied which demonstrates the calling convention. How do I print the PDF417 from an AS/400?The NeoMedia PDF417 encoder returns a rectangular array of characters which need to be printed using our special PDF417 font. Furthermore, these lines must be printed using a line spacing that depends on the module size you choose for your output symbol. The simplest way on an AS/400 to print is using a DDS to an AFP capable printer. The DDS for the PDF417 record may look something like this: A CDEFNT(X0PD3309) Sample COBOL, C, and RPG programs are all provided for the AS/400. How is a PDF417 symbol printed?Normally, NeoMedia's PDF417 encoder uses font rendering to print the PDF417 symbol. The actual "output" of the encoder library is simply a series of characters (upper case letters and spaces). This data is organized in a rectangular array whose size depends on parameters you provide to the encoder. When printed using NeoMedia's PDF417 font, the correct symbol is "rendered" by the printer. For example, the output of the encoder may look like the group of characters shown below. When rendered in the NeoMedia-provided font, the result is the PDF417 symbol image shown to the right. OOEDGEALCJBNALBHNIC LFB KCJILAOMADH Which AFP/IPDS printers are supported?All AFP capable IPDS printers are supported (both 240 and 300/600/1200 DPI). It is important to note though that your operating environment must have AFP support installed and operational (specifically, our software requires a PSF host). 3800 series printers are supported only if they are operating in page mode and AFP is present on the system. Which Xerox printers are supported?NeoMedia has the ability to generate fonts for most Xerox printers. We can produce Xerox 9700 format floppy disks (5-1/2") with 5-word fonts. While we can generate fonts for other printer series (e.g., 2700 and 3700) we do not have the ability to test these, nor can we necessarily deliver these fonts on the appropriate media. Call NeoMedia for individual evaluation of your printer environment. Which PCL printers are supported?NeoMedia can provide soft fonts for HP PCL printers. These fonts will work on virtually any HP compatible laser printer. Furthermore, NeoMedia provides some basic documentation on downloading and printing with soft fonts. However, this documentation does not address generating PCL on all possible platforms (e.g., MVS and OS/400). For further support, please use our online form. |
|
 |
