ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzalu_5.4.0.1/rzaluafpds.htm

238 lines
12 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 1998, 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>Advanced Function Presentation data stream</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="rzaluafpds"></a>
<h4 id="rzaluafpds">Advanced Function Presentation data stream</h4>
<p>Advanced Function Presentation Data Stream is the application interface
to Advanced Function Presentation&trade; (AFP&trade;) based on the
Mixed Object:Document Content Architecture&ndash;Presentation (MO:DCA&ndash;P).
It is independent of both printers and operating systems.</p>
<p>AFP data stream is a structured data stream. Structured fields are used
to define composed text pages, line format data, and a mixture of line and
composed text data. The structured field is a self-identifying string of bytes
containing data or parameters and must have an introducer, which contains
a length field, an identifier, a flag, and a sequence number. This is followed
by parameter bytes that contain control information or data to be printed. </p>
<div class="mmobj">
<img src="rbaft530.gif" alt="AFP data stream is the application interface to Advanced Function Presentation (AFP) based on the Mixed Object:Document Content Architecture&ndash;Presentation (MO:DCA&ndash;P)." /></div>
<dl>
<dt class="bold">Length</dt>
<dd>A 2-byte field that specifies the length of the record (not including
the 5A control character).
</dd>
<dt class="bold">Identifier (ID)</dt>
<dd>A 3-byte field that specifies the type of the structured field.
</dd>
<dt class="bold">Flag byte</dt>
<dd>A 1-byte field that specifies information about the data field.
</dd>
<dt class="bold">Sequence number</dt>
<dd>A 2-byte field that identifies the record.
</dd>
<dt class="bold">Control and data</dt>
<dd>A text control code, the name of an object, or coordinates for positioning
an image or page segment. The control information is followed by the data
to be printed.
</dd>
</dl>
<p><span class="bold">Source programs that generate Advanced Function Presentation
data stream</span></p>
<p>The following IBM&reg; licensed programs generate Advanced Function Presentation
data streams: </p>
<ul>
<li>i5/OS</li>
<li>Advanced Function Presentation&trade; Utilities for iSeries&trade; (AFP Utilities for iSeries)</li>
<li>Document Composition Facility (DCF)</li>
<li>DisplayWrite/390 (DW/390)</li>
<li>Graphical Data Display Manager (GDDM&reg;)</li>
<li>zSeries&reg; Advanced Function Presentation utilities:
<ul>
<li>Page Printer Formatting Aid (PPFA)</li>
<li>Overlay Generation Language (OGL)</li>
<li>Font Library Service Facility (FLSF)</li>
<li>Print Management Facility (PMF)</li>
<li>Print Service Access Facility (PSAF)</li></ul></li></ul>
<p><span class="bold">Advanced Function Presentation</span></p>
<p>Advanced Function Presentation data stream describes what the page of data
looks like and refers to printer resource objects by name, assuming that they
are resident on the system where the actual printing is to take place and
not on the system where the output was spooled. The printer resource objects
that are resident on the system are downloaded to the printer by the processor
when needed.</p>
<p>The iSeries server uses the following objects when processing AFP data stream: </p>
<dl>
<dt class="bold">AFP data stream spool buffers</dt>
<dd>The AFP data stream print file is sent to the system in one or more
buffers. These buffers contain single or multiple contiguous structured fields.
A pointer to the buffer and the length of each buffer are passed to the system.
</dd>
<dt class="bold">AFP data stream resource objects</dt>
<dd>Resource objects contain data and control information that can be used
in printing a job. These can be shared by different pages in the same job.
A resource is composed entirely of structured fields.
<p>Types of resources
are: </p>
<ul>
<li>Fonts</li>
<li>Form definitions</li>
<li>Page segments</li>
<li>Overlays</li>
<li>Page definitions</li>
<li>Resources stored in the integrated file system</li></ul>
<p>These resources can be transmitted from a host zSeries to an iSeries server
or loaded from tape into space objects using i5/OS commands. Overlays and
page segments can be created by AFP Utilities for iSeries.</p>
</dd>
<dt class="bold">Messages</dt>
<dd>Messages generated during the processing of AFP data stream print files
are placed in the printer writer job log.
</dd>
</dl>
<p><img src="delta.gif" alt="Start of change" /><span class="bold">Mixed Object: Document Content Architecture
(MO:DCA)</span><img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" />Mixed Object Document Content Architecture (MO:DCA) is an object-oriented
data stream that is designed to allow consistent printing that is independent
of operating system or device. An object is a collection of data that can
be treated as a unit, such as text, images, and graphics. This architecture
supports:</p>
<ul>
<li>Coexistence and migration of existing IBM document architecture and printer data
streams</li>
<li>Device independence</li>
<li>Separation of functions to simplify transformation of objects into other
data streams</li>
<li>National Language Support</li>
<li>Office Document Architecture (ODA) support</li>
<li>Standard Generalized Markup Language (SGML)</li></ul><img src="deltaend.gif" alt="End of change" />
<p>The data stream for an MO:DCA document consists of various objects as well
as the logical and layout structure of the document. The logical structure
defines the logical content of the document&mdash;chapters, figures, and lists.
The following layout structure defines the way the data should be presented.</p>
<a name="wq29"></a>
<div class="fignone" id="wq29"><span class="figcap">Figure 1. MO:DCA Document Structure</span>
<div class="mmobj">
<img src="rbaft537.gif" alt="Mixed Object Document Content Architecture (MO:DCA)" /></div></div>
<dl>
<dt class="bold">BDT (Begin document)</dt>
<dd>Indicates the beginning of the document
</dd>
<dt class="bold">Resource groups</dt>
<dd>Specifies fonts, overlays, and segments so that these objects can be
transmitted as part of the data stream. They can be referred to by an MO:DCA
Include structured field.
</dd>
<dt class="bold">Master environment groups</dt>
<dd>Specifies the processing environment, such as space definitions, suppression
of data, number of copies, and internal data stream references.
</dd>
<dt class="bold">Pages</dt>
<dd>Contains objects that are part of the document. These objects could
be text, graphics, and images.
</dd>
<dt class="bold">EDT (End document)</dt>
<dd>Indicates the end of the document.
</dd>
</dl>
<p>The following different types of objects make up MO:DCA. All of these
objects are supported by IPDS&trade;: </p>
<ul>
<li>Bar Code Object Content Architecture (BCOCA)</li>
<li>Image Object Content Architecture (IOCA)</li>
<li>Graphics Object Content Architecture (GOCA)</li>
<li>Presentation Text Object Content Architecture (PTOCA)</li>
<li>Font Object Content Architecture (FOCA).</li></ul>
<dl>
<dt class="bold">Bar Code Object Content Architecture (BCOCA)</dt>
<dd>A bar-code object could contain &quot;draw rule&quot; commands or raster
data, depending on whether the bar code is to be drawn as a graphics object
or has been scanned into the data stream as an image. A bar code object containing
draw rule commands is built up using only lines of a specified length and
width. A graphics object is constructed from a number of primitives, such
as lines, arcs, symbols, shaded areas, and point arrays.
</dd>
<dt class="bold">Image Object Content Architecture (IOCA)</dt>
<dd>IOCA represents images in device-independent format. A standard set
of constructs has been defined to describe the image data, the characteristics
of that data, and manipulation functions that can be performed on the data.
The image content is inserted in an image segment.
</dd>
<dt class="bold">Graphics Object Content Architecture (GOCA)</dt>
<dd>GOCA describes complex pictures. These pictures are formed from a collection
of primitives, such as lines, arcs, characters, symbols, and shaded areas
or point arrays. Each of these primitives has its own set of attributes,
such as line width, orientation, and resolution. In addition to these attributes,
there is a set of general drawing attributes like color, which apply to all
primitives
</dd>
<dt class="bold">Presentation Text Object Content Architecture (PTOCA)</dt>
<dd>PTOCA describes the text part of a document. The presentation text
object, in common with the other objects, is designed not only to be carried
by, but to be an integral part of, the data stream, providing the following:
<ul>
<li>Structured field introducer and syntax for the structured field</li>
<li>Begin/end object structure</li>
<li>Control of alternate action selection for error recovery</li>
<li>Passing of exception conditions back to the originating process</li>
<li>Initial state of the object</li>
<li>Relationship of presentation text objects to other objects contained in
the data stream.</li></ul>
<p>Two structured fields provide the necessary presentation information
to the printer:</p>
<dl>
<dt class="bold">P T descriptor structured field</dt>
<dd>Defines several positional parameters for the object
</dd>
<dt class="bold">P T data structured field</dt>
<dd>Contains the presentation text and the control sequences for positioning
graphic characters. These graphic characters are defined within the coded
fonts.
</dd>
</dl>
</dd>
<dt class="bold">Font Object Content Architecture (FOCA)</dt>
<dd>
<p>In order to achieve uniform document presentation output, it is essential
that font resources be consistently defined and put into effect. These resources
must be identified by means of a constant, unvarying set of parameters.</p>
<p>FOCA makes it possible to achieve the required degree of consistency by defining: </p>
<ul>
<li>A common font and character definition model that can be used by all products
and architectures as the basis for font applications</li>
<li>A composite set of parameters specific to a font resource and references
to that resource</li>
<li>A device-and-technology-independent method of defining font measurements</li>
<li>The specification of formats for conveying font information to suit the
application</li></ul>
<p>FOCA defines the parameter content of: </p>
<ul>
<li>IBM font resources</li>
<li>References to the font resources</li>
<li>Information accessed by the font resources</li></ul>
</dd>
</dl>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>