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

136 lines
6.7 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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>Considerations and restrictions when using line data</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="rzau6consider"></a>
<h3 id="rzau6consider">Considerations and restrictions when using line data</h3>
<p><span class="bold">Application considerations</span></p>
<p>To use line data, first determine whether your application generates an
American National Standards Institute (ANSI) control character in column 1
of your spooled output. If your application does generate an ANSI control
character as described, specify CTLCHAR(*FCFC) and DEVTYPE(*LINE) on the printer
file.</p>
<p>If your application does not generate an ANSI control character in column
1 of your spooled output, change your application to do so. To change your
application, use a language or application construct (such as a SKIP or SPACE
option on a COBOL WRITE statement), or make an RPG output specification. If
your application cannot generate ANSI control characters, specify CTLCHAR(*NONE)
and DEVTYPE(*LINE) on your printer file. The operating system will use control
information to generate machine code control characters in your data.</p>
<p><span class="bold">Specifying a page definition and form definition</span></p>
<p>When using line data, you can specify various combinations of DEVTYPE(*LINE),
PAGDFN, and FORMDF parameters on the printer file:</p>
<dl>
<dt class="bold">If you specify DEVTYPE(*LINE), PAGDFN and FORMDF</dt>
<dd>When you print to an Advanced Function Presentation&trade; (AFP&trade;) printer, Print Services Facility&trade; (PSF) uses the PAGDFN
and FORMDF parameters to transform the data to Intelligent Printer Data
Stream&trade; (IPDS&trade;).
<p>When you print to a non-AFP printer, the PAGDFN and FORMDF
parameters are ignored. The other parameters on the printer file are used
and the line data is transformed to IPDS or SNA Character Stream (SCS).</p>
</dd>
<dt class="bold">If you specify DEVTYPE(*LINE) and FORMDF (no page definition)</dt>
<dd>When you print to an AFP printer, an inline page definition is built from the
printer file parameters. PSF uses the form definition and the inline page
definition to transform the data to IPDS.
<p>When you print to a non-AFP printer,
the FORMDF parameter is ignored. The other printer file parameters are used
and the line data is transformed to IPDS or SCS.</p>
</dd>
<dt class="bold">If you specify DEVTYPE(*LINE) and PAGDFN (no form definition)</dt>
<dd>When you print to an AFP printer, an inline form definition is built from the
printer file parameters. PSF uses the page definition and the inline form
definition to transform the data to IPDS.
<p>When you print to a non-AFP printer,
the PAGDFN parameter is ignored. The other printer file parameters are used
and the line data is transformed to IPDS or SCS.</p>
</dd>
<dt class="bold">If you specify DEVTYPE(*LINE) only (no page definition or form
definition)</dt>
<dd>When you print to an AFP printer, an inline page definition and an inline form
definition are built from the printer file parameters. PSF uses the inline
form definition and the inline page definition to transform the data to IPDS.
<p>When you print to a non-AFP printer, the printer file parameters
are used and the line data is transformed to IPDS or SCS.</p>
</dd>
<dt class="bold">When specifying DEVTYPE(*AFPDSLINE)</dt>
<dd>The support for combinations of DEVTYPE(*AFPDSLINE), PAGDFN, and FORMDF
are similar to DEVTYPE(*LINE) line data. However, you should be aware of these
exceptions:
<ul>
<li>The spooled file must be printed on an AFP printer. When you send data to a non-AFP
printer, the data cannot be transformed to IPDS or to SCS.</li>
<li> You are not required to specify a page definition or form definition
with *AFPDSLINE data because they can be built inline. However, certain Advanced Function Presentation data stream (AFPDS) commands
in the data stream (for example, Invoke Medium Map) might reference named
structured fields in the page definition or form definition that do not match
those in the inline page definition and form definition.</li></ul>
</dd>
</dl>
<p><span class="bold">Supported DDS keywords</span></p>
<p>Below is a list of Data description specifications (DDS) keywords that
are supported for line data. If you use DDS keywords that are not included
on this list while processing line data, they will be ignored. </p>
<ul>
<li>ALIAS</li>
<li>BLKFOLD</li>
<li>CCSID</li>
<li>DATE</li>
<li>DATFMT</li>
<li>DATSEP</li>
<li>DFT</li>
<li>DLTEDT</li>
<li>EDTCDE</li>
<li>EDTWRD</li>
<li>FLTFIXDEC</li>
<li>FLTPCN</li>
<li>IGCALTTYP</li>
<li>IGCANKCNV</li>
<li>INDARA</li>
<li>INDTXT</li>
<li>INVDTAMAP</li>
<li>MSGCON</li>
<li>PAGNBR</li>
<li>REF</li>
<li>REFFLD</li>
<li>SKIPA</li>
<li>SKIPB</li>
<li>SPACEA</li>
<li>SPACEB</li>
<li>TEXT</li>
<li>TIME</li>
<li>TIMFMT</li>
<li>TIMSEP</li></ul>
<p><span class="bold">Restrictions when using line data or mixed data</span></p>
<ul>
<li>Externally described printer files (DDS SUPPORT) support both line and
mixed data device types.</li>
<li>In the printer file, if you specify *LINE or *AFPDSLINE for device type,
you cannot specify SPOOL(*NO). If you specify one of these combinations, Message
CPD7341, indicating the value SPOOL(*NO) is not valid with device type, is
issued.</li></ul>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>