120 lines
6.1 KiB
HTML
120 lines
6.1 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="reference" />
|
||
|
|
<meta name="DC.Title" content="TCPL0100 format usage notes" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiql0100.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaiqusnts" />
|
||
|
|
<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>TCPL0100 format usage notes</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiqusnts"><a name="rzaiqusnts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">TCPL0100 format usage notes</h1>
|
||
|
|
<div><div class="section"><p>For File Transfer Protocol (FTP), if any of the returned output
|
||
|
|
parameters are not valid, the FTP server will not allow the operation.
|
||
|
|
In this case, the FTP server issues the message <samp class="codeph">Data from exit program
|
||
|
|
for exit point &1 is missing or not valid</samp> to the job log.</p>
|
||
|
|
<p>For
|
||
|
|
FTP, if you encounter any exception when you call the exit program, the FTP
|
||
|
|
server issues this message: <samp class="codeph">Exception encountered for FTP exit program &1
|
||
|
|
in library &2 for exit point &3</samp></p>
|
||
|
|
<p>This table summarizes
|
||
|
|
what the FTP sever will do, depending on the value of the return code (parameter
|
||
|
|
8) that is returned to the FTP server by the exit program.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> A value
|
||
|
|
of 'Return value' indicates that the exit program must return the appropriate
|
||
|
|
value for that output parameter. The value will then be used by the FTP server
|
||
|
|
to complete the logon request process.</div>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e32">Return code</th>
|
||
|
|
<th valign="top" id="d0e34">User profile (9)</th>
|
||
|
|
<th valign="top" id="d0e36">Password (10)</th>
|
||
|
|
<th valign="top" id="d0e38">Initial lib (11)</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e32 ">0</td>
|
||
|
|
<td valign="top" headers="d0e34 ">Ignored</td>
|
||
|
|
<td valign="top" headers="d0e36 ">Ignored</td>
|
||
|
|
<td valign="top" headers="d0e38 ">Ignored</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e32 ">1</td>
|
||
|
|
<td valign="top" headers="d0e34 ">(User identifier, parameter 2)</td>
|
||
|
|
<td valign="top" headers="d0e36 ">(Password, parameter 4)</td>
|
||
|
|
<td valign="top" headers="d0e38 ">(From user profile)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e32 ">2</td>
|
||
|
|
<td valign="top" headers="d0e34 ">(User identifier, parameter 2)</td>
|
||
|
|
<td valign="top" headers="d0e36 ">(Password, parameter 4)</td>
|
||
|
|
<td valign="top" headers="d0e38 ">Return value</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e32 ">3</td>
|
||
|
|
<td valign="top" headers="d0e34 ">Return value</td>
|
||
|
|
<td valign="top" headers="d0e36 ">Return value</td>
|
||
|
|
<td valign="top" headers="d0e38 ">(From user profile)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e32 ">4</td>
|
||
|
|
<td valign="top" headers="d0e34 ">Return value</td>
|
||
|
|
<td valign="top" headers="d0e36 ">Return value</td>
|
||
|
|
<td valign="top" headers="d0e38 ">Return value</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e32 ">5</td>
|
||
|
|
<td valign="top" headers="d0e34 ">Return value</td>
|
||
|
|
<td valign="top" headers="d0e36 ">Ignored</td>
|
||
|
|
<td valign="top" headers="d0e38 ">(From user profile)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e32 ">6</td>
|
||
|
|
<td valign="top" headers="d0e34 ">Return value</td>
|
||
|
|
<td valign="top" headers="d0e36 ">Ignored</td>
|
||
|
|
<td valign="top" headers="d0e38 ">Return value</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>In the table above, the values in parentheses indicate what the
|
||
|
|
TCP/IP application uses for information when it ignores the output value.
|
||
|
|
The entry <samp class="codeph">Ignored</samp> means that it used no value; therefore
|
||
|
|
return nothing for that return code value.</p>
|
||
|
|
<p>For the FTP server (exit
|
||
|
|
point QIBM_QTMF_SVR_LOGON, application identifier 1): when the user identifier
|
||
|
|
is <samp class="codeph">ANONYMOUS</samp> and this exit point adds the exit program,
|
||
|
|
the server issues this special reply when requesting the password: <samp class="codeph">331
|
||
|
|
Guest logon in process, send complete e-mail address as password</samp>.
|
||
|
|
The application issues this message before calling the exit program.</p>
|
||
|
|
<p>After
|
||
|
|
the application accepts the server logon, the FTP server issues this reply:
|
||
|
|
<samp class="codeph">230 Guest logon accepted, access restrictions apply</samp></p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">REXEC server (application identifier 2):</h4><ol><li>If the return allow operation output parameter is not valid, the REXEC
|
||
|
|
server will not allow the operation. The REXEC server issues the message "Data
|
||
|
|
from exit program for exit point &1 is missing or not valid" to the job
|
||
|
|
log.</li>
|
||
|
|
<li>If the REXEC server encounters any exception when calling the exit program,
|
||
|
|
the REXEC server will not allow the operation. It issues the message "Exception
|
||
|
|
encountered for REXEC exit program &1 in library &2 for exit point &3,"
|
||
|
|
to the job log.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiql0100.htm">TCPL0100 exit point format</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|