ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/off3a.htm

99 lines
5.4 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>AnyMail/400 Mail Server Framework APIs</title>
<!-- Begin Header Records ========================================= -->
<!-- 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. -->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!-- OFF3A SCRIPT A converted by B2H R4.1 (346) (CMS) by HOLTJM at -->
<!-- RCHVMW2 on 4 Feb 1999 at 15:00:55 -->
<!-- File Edited November 2001 -->
<!-- 031111 JETAYLOR replaced API and/or Exit listings with -->
<!-- pagegenerator output from javascript array -->
<!-- End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<!-- Java sync-link -->
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript">
</script>
<h2>AnyMail/400 Mail Server Framework APIs</h2>
<p>The mail server framework defines the format of how the data is passed
rather than the format of the data itself. This allows it to work independently
of the format of the data. The format of the data is defined by assigning a
type to the information. The different types supported include:</p>
<ul>
<li>Address type</li>
<li>Envelope type</li>
<li>Attachment reference type</li>
<li>Message type</li>
</ul>
<p>For additional information, see <a href="off3b.htm">Using AnyMail/400 Mail
Server Framework APIs</a></p>
<p>The mail server framework APIs consist of the program calls shown in the
following list:</p>
<!-- ***** NOTE ***** Do not manually update text or links in this section. -->
<!-- Updates made in this section *will* be overlaid by automated tools -->
<!-- Notify User Technologies of needed updates to be made in XML for API finder.-->
<!--***************API BEGIN PASTE***************-->
<ul>
<li><A HREF="QZMFAADD.htm">Add Mail Server Framework Configuration</A> (QzmfAddMailCfg) generates a configuration for the mail server framework used in processing messages.</li>
<li><A HREF="QZMFACHG.htm">Change Mail Message</A> (QzmfChgMailMsg) changes information about a mail message that was previously created using the Create Mail Message (QzmfCrtMailMsg) API.</li>
<li><A HREF="QZMFACMP.htm">Complete Creation Sequence</A> (QzmfCrtCmpMailMsg) removes a previously created, reserved mail message identifier from the mail server framework's list of reserved identifiers and acknowledges that the message was created.</li>
<li><A HREF="QZMFACRT.htm">Create Mail Message</A> (QzmfCrtMailMsg) creates an electronic mail message.</li>
<li><A HREF="QZMFALST.htm">List Mail Server Framework Configuration</A> (QzmfLstMailCfg) generates a list of type configurations.</li>
<li><A HREF="QZMFAQRY.htm">Query Mail Message Identifier</A> (QzmfQryMailMsgId) queries the status of a message associated with a mail message identifier.</li>
<li><A HREF="QZMFADLT.htm">Remove Mail Server Framework Configuration</A> (QzmfRmvMailCfg) removes a configuration from the mail server framework.</li>
<li><A HREF="QZMFARMV.htm">Remove Reserved Mail Message Identifier</A> (QzmfRsvMailMsgID) removes an identifier for an electronic mail message that has been reserved using the Reserve Mail Message Identifier (QzmfRsvMailMsgId) API, but has not been used to create a message.</li>
<li><A HREF="QZMFARMI.htm">Reserve Mail Message Identifier</A> (QzmfRsvMailMsgId) reserves an identifier for an electronic mail message.</li>
<li><A HREF="QZMFARTV.htm">Retrieve Mail Message</A> (QzmfRtvMailMsg) retrieves information about an electronic mail message and returns it in the receiver variables provided by the caller.</li>
</ul>
<!--***************API END PASTE***************-->
<p>The user can write exit programs that are called by the system for the
following mail enablement exit programs:</p>
<!-- ***** NOTE ***** Do not manually update text or links in this section. -->
<!-- Updates made in this section *will* be overlaid by automated tools -->
<!-- Notify User Technologies of needed updates to be made in XML for API finder.-->
<!--***************EXIT PROGRAM BEGIN PASTE***************-->
<ul>
<li><A HREF="QZMFASPC.htm">Snap-In Call</A> exit program provides information about an electronic mail message to defined snap-in programs.</li>
<li><A HREF="QZMFATCM.htm">Track Mail Message Changes</A> exit program allows exit programs to read all the parts of a message to keep track of the message.</li>
<li><A HREF="QZMFAVDF.htm">Validate Data Field</A> exit program allows exit programs to validate the data for a message based on the type selected.</li>
</ul>
<!--***************EXIT PROGRAM END PASTE***************-->
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center">
<a href="#Top_Of_Page">Top</a> |
<a href="off1.htm">Office APIs</a> |
<a href="aplist.htm">APIs by category</a></td>
</tr>
</table>
</center>
</body>
</html>