ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzau6_5.4.0.1/rzau6interact.htm

80 lines
3.9 KiB
HTML

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow"/>
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<title>How page definitions, form definitions, and printer files interact</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="rzau6interact"></a>
<h3 id="rzau6interact">How page definitions, form definitions, and printer files interact</h3>
<p><span class="bold">Page definition and the printer file</span></p>
<p>When you specify a page definition on the printer file, some printer file
parameters might be ignored when the spooled file is printed through Print Services Facility&trade; (PSF). For example, if you specify a page definition and also specify
line data or mixed data, an inline page definition is not built. In this case,
the following happens: </p>
<ul>
<li>If you send line data with a printer file to an Advanced Function Presentation&trade; (AFP&trade;) printer, PSF ignores these printer file parameters:
<ul>
<li>CDEFNT</li>
<li>CHRID</li>
<li>CPI</li>
<li>FNTCHRSET</li>
<li>FOLD</li>
<li>FONT</li>
<li>LPI</li>
<li>MULTIUP</li>
<li>PAGESIZE</li>
<li>PAGRTT</li>
<li>REDUCE</li></ul></li>
<li>If you send the line data with a page definition to a non-AFP printer
with a device type of *LINE, the page definition parameter is ignored
and the printer file parameters are used. The line data is converted to SNA
character string (SCS) or Intelligent Printer Data
Stream&trade; (IPDS&trade;).</li></ul>
<p><span class="bold">Form definition and the printer file</span></p>
<p>When using a form definition, depending on the specifications given, some
printer file parameters might be ignored when output is printed through PSF.
For example, if you specify a form definition, an inline form definition is
not built. In this case, if you send the line data with a form definition
to an AFP device, PSF ignores these printer file parameters: </p>
<ul>
<li>BACKMGN</li>
<li>CORNERSTPL</li>
<li>EDGESTITCH</li>
<li>FORMFEED</li>
<li>FRONTMGN</li>
<li>MULTIUP (N_UP)</li>
<li>PAGRTT</li>
<li>PRTQLTY</li>
<li>REDUCE (N_UP)</li>
<li>SADLSTITCH</li></ul><p class="indatacontent"> However, if you send the line data with a form definition to a non-AFP
printer with a device type of *IPDS or *SCS in this example,
the form definition parameter is ignored and the printer file parameters are
used.</p>
<p>When specifying a form definition, the values you specify on the printer
file's DRAWER and DUPLEX parameters override those values specified in the
form definition. To use the drawer and duplex values specified in the form
definition, specify DRAWER(*FORMDF) and DUPLEX(*FORMDF)
on the printer file.</p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>