Publishing Reports to the Web - Downloads - Oracle

Debugging Options
printer that does not have the Chinese fonts installed, it will not print the Chinese
characters properly.
5.5.2 Overview of IX and PASTA
5.6 Debugging Options
5.6.1 DEBUG_SLFIND
When installed and used with Oracle Applications, Oracle Reports has an additional
utility for font embedding in PostScript output.
For character mode reports, the utility is called PASTA. For bit-mapped reports, a new
component called IX is shipped with Oracle Reports. IX allows you to embed the fonts
in the PostScript output thereby allowing you to print even if the font is not installed
on the printer. Both PASTA and IX are supported only for Oracle Reports used with
Oracle Applications.
When used for character mode reports, PASTA takes tagged character mode output
(generated via an appropriate prt file) and generates a PostScript rendition of it. IX
enables Oracle Reports to print PostScript bit-mapped reports for all character sets,
including UTF8, on a PostScript printer. With this functionality, PostScript printing in
Unicode as well as all native languages on Solaris is supported. The IX library is
turned off by default with the Oracle Reports patch.
Please refer to your Oracle Applications System Administrator’s Guide for the setup and
usage information for IX and PASTA with Oracle Reports. If you are a member of
MetaLink (http://metalink.oracle.com), you can also get this information from
MetaLink notes 189708.1 and 159225.
If you have problems with PASTA, you can use the following technique to isolate the
problem:
1. Unset the PASTA environment variable.
2. Try to perform the steps that caused the problem again.
3. If the problem reproduces without the environment variable set, then it should be
treated as a normal Oracle Reports printing problem and the diagnostic steps
provided in this document should be applied.
If the problem reproduces only with the PASTA environment variable set, then
follow the diagnostic process given in the Oracle Applications documentation.
This section explains the different environment variables and techniques available in
Oracle Reports for the debugging of UNIX printing problems.
■ DEBUG_SLFIND
■ TK_DEBUG_POSTSCRIPT
If this environment variable is set, the file-finding routine lists what was searched for
and where Oracle Reports searched for it. This information is a tremendous help if
your current configuration does not work. You can send the output to a file, stdout
(for standard output), or to stderr (for output to standard error). If you try to send
the output to a file and it cannot be written to, Oracle Reports uses stderr instead.
We recommend sending the output to a file because it is faster and the output can be
quite large. Sample output from DEBUG_SLFIND is shown below. Notice how the
5-16 Oracle Application Server Reports Services Publishing Reports to the Web