155 lines
7.7 KiB
HTML
155 lines
7.7 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 lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<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))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Example: An ICF file using DDS" />
|
||
|
|
<meta name="abstract" content="This example contains DDS for transmitting data between the iSeries server and a remote system or device." />
|
||
|
|
<meta name="description" content="This example contains DDS for transmitting data between the iSeries server and a remote system or device." />
|
||
|
|
<meta name="DC.subject" content="examples of DDS, ICF file" />
|
||
|
|
<meta name="keywords" content="examples of DDS, ICF file" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafpmstexamp.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="icffileexamp" />
|
||
|
|
<meta name="DC.Language" 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. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Example: An ICF file using DDS</title>
|
||
|
|
</head>
|
||
|
|
<body id="icffileexamp"><a name="icffileexamp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: An ICF file using DDS</h1>
|
||
|
|
<div><p>This example contains DDS for transmitting data between the <span class="keyword">iSeries™</span> server and a remote system or
|
||
|
|
device.</p>
|
||
|
|
<p>The following keywords are important in the example:</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="void" border="0" rules="none"><tbody><tr><td valign="top" width="50%"> <p>CONFIRM<br />
|
||
|
|
DETACH<br />
|
||
|
|
EVOKE<br />
|
||
|
|
RCVDETACH<br />
|
||
|
|
RCVFAIL<br />
|
||
|
|
RCVCONFIRM<br />
|
||
|
|
RCVTRNRND</p>
|
||
|
|
</td>
|
||
|
|
<td valign="top" width="50%"> <p>RECID<br />
|
||
|
|
SYNLVL<br />
|
||
|
|
EOS<br />
|
||
|
|
RSPCONFIRM<br />
|
||
|
|
ALWWRT<br />
|
||
|
|
FAIL<br />
|
||
|
|
RQSWRT</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<div class="fignone" id="icffileexamp__o23"><a name="icffileexamp__o23"><!-- --></a><span class="figcap">Figure 1. ICF file</span><pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
||
|
|
00010A*
|
||
|
|
00020A* SAMPLE ICF FILE
|
||
|
|
00030A*
|
||
|
|
00040A 01 <strong>(3)</strong> EOS
|
||
|
|
00050A <strong>(2)</strong> RCVTRNRND(01 'TRNRND INDICATION')
|
||
|
|
00060A <strong>(2)</strong> RCVDETACH(02 'DETACH RECEIVED')
|
||
|
|
00070A <strong>(2)</strong> RCVCONFIRM(03 'CONFIRM REQUEST')
|
||
|
|
00080A <strong>(2)</strong> RCVFAIL(04 'FAIL RECEIVED')
|
||
|
|
00090A
|
||
|
|
00100A R CATCHALL
|
||
|
|
00110A FLD1 132A
|
||
|
|
00120A*
|
||
|
|
00130A R SNDEVOKE EVOKE(&LIBNME/&PGMNME);
|
||
|
|
00140A <strong>(1)</strong> SYNLVL(*CONFIRM) SECURITY(2 PASSWRD)
|
||
|
|
00150A <strong>(1)</strong> CONFIRM
|
||
|
|
00160A PGMNME 10A P
|
||
|
|
00170A LIBNME 10A P
|
||
|
|
00180A PASSWRD 8A P
|
||
|
|
00190A*
|
||
|
|
00200A R HEADER RECID(1 'H')
|
||
|
|
A</pre>
|
||
|
|
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
||
|
|
00210A 09 CONFIRM
|
||
|
|
00220A ID 1A
|
||
|
|
00230A <strong>(4)</strong> PART# 12A
|
||
|
|
00240A UNTCST 6S 2
|
||
|
|
00250A QTYONORDR 9B 0
|
||
|
|
00260A TOTAL 9B 0
|
||
|
|
00270A*
|
||
|
|
00280A R DETAIL RECID(1 'D') RECID(1 'E')
|
||
|
|
00290A 09 CONFIRM
|
||
|
|
00300A ID 1A
|
||
|
|
00310A <strong>(4)</strong> LOC 6A
|
||
|
|
00320A QTY 9B 0
|
||
|
|
00330A*
|
||
|
|
00340A R COMMANDS
|
||
|
|
00350A 05 <strong>(5)</strong> FALL
|
||
|
|
00360A 06 <strong>(5)</strong> ALWWRT
|
||
|
|
00370A 07 <strong>(5)</strong> DETACH
|
||
|
|
00380A 08 <strong>(5)</strong> RQSWRT
|
||
|
|
00390A 09 <strong>(5)</strong> CONFIRM
|
||
|
|
00400A 10 <strong>(5)</strong> RSPCONFIRM
|
||
|
|
A</pre>
|
||
|
|
</div>
|
||
|
|
<div class="p"><strong>Legend:</strong> <dl><dt class="dlterm">(1)</dt>
|
||
|
|
<dd>The record format SNDEVOKE causes the program specified in the field PGMNME
|
||
|
|
and the library specified in the field LIBNME to be started on the remote
|
||
|
|
system. It also establishes a synchronization level of *CONFIRM for the transaction
|
||
|
|
and passes the data in the field PASSWRD as security information. The CONFIRM
|
||
|
|
keyword requests that the remote system confirm the start of the program.</dd>
|
||
|
|
<dt class="dlterm">(2)</dt>
|
||
|
|
<dd>If the remote program performs any of the following actions: <ul><li>Requests to end sending data</li>
|
||
|
|
<li>Requests to end the transaction</li>
|
||
|
|
<li>Requests to confirm receiving the data</li>
|
||
|
|
<li>Sends a FAIL</li>
|
||
|
|
</ul>
|
||
|
|
this sets on one of the following response indicators: <ul><li>01 (the RCVTRNRND keyword)</li>
|
||
|
|
<li>02 (the RCVDETACH keyword)</li>
|
||
|
|
<li>03 (the RCVCONFIRM keyword)</li>
|
||
|
|
<li>04 (the RCVFAIL keyword)</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">(3)</dt>
|
||
|
|
<dd>The EOS keyword causes the session to end if indicator 01 is on and the
|
||
|
|
program issues an output operation.</dd>
|
||
|
|
<dt class="dlterm">(4)</dt>
|
||
|
|
<dd>The <span class="keyword">iSeries</span> server sends
|
||
|
|
and receives data in the form of header (record format HEADER) and detail
|
||
|
|
(record format DETAIL) records. If your program is sending, option indicator
|
||
|
|
09 can be set on (enabling the CONFIRM keyword) to request the remote system
|
||
|
|
to confirm receiving the data. <p>When
|
||
|
|
receiving data, the record selection processing (RECID keyword) determines
|
||
|
|
which record is received. If an H is in position 1, record format HEADER
|
||
|
|
is selected. If a D or E is in position 1, record format DETAIL is selected.
|
||
|
|
If anything else is in position 1 (unexpected record format, application
|
||
|
|
error, or indicators with no data, RCVDETACH, RCVFAIL, and so on), record
|
||
|
|
format CATCHALL is selected.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">(5)</dt>
|
||
|
|
<dd>Record format, COMMANDS, is used to request the following communications
|
||
|
|
functions: <ul><li>If indicator 05 is on, the FAIL function is performed.</li>
|
||
|
|
<li>If indicator 06 is on, the ALWWRT function is performed.</li>
|
||
|
|
<li>If indicator 07 is on, the DETACH function is performed.</li>
|
||
|
|
<li>If indicator 08 is on, the RQSWRT function is performed.</li>
|
||
|
|
<li>If indicator 09 is on, the CONFIRM function is performed.</li>
|
||
|
|
<li>If indicator 10 is on, the RSPCONFIRM function is performed.</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafpmstexamp.htm" title="This topic provides examples of data description specifications (DDS) for each type of file discussed in this topic. If you choose, you can use the examples in this topic with appropriate high-level language programs.">Examples: DDS for each file type</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|