gtpm2m2vMigration Guide: Program Update Tapes

TPF Internet Mail Server Support (APARs PJ27784 and PJ27865)

The following section discusses the migration considerations for TPF Internet mail server support.

Prerequisite APARs

See the APEDIT for APARs PJ27784 and PJ27865 for information about prerequisite APARs.

Functional Overview

TPF Internet mail server support provides a set of servers that implement the standard Internet mail protocols on the TPF 4.1 system. Users, or mail clients, interact with the TPF Internet mail servers to send and retrieve Internet mail, also known as electronic mail (e-mail).

The TPF 4.1 system supports the following standard Internet protocols:

SMTP describes how mail messages are delivered from one computer user to another. IMAP and POP describe how mail messages that are received on a computer (that is, the mail server) are retrieved by a mail client (usually another computer, such as a workstation).

The TPF 4.1 system can support multiple domains in a single server. In addition, if a TPF processor fails, another TPF processor in your complex can seamlessly take over and continue delivering the mail.

TPF Internet mail server support takes advantage of the high-performance, availability, and reliability characteristics of the TPF 4.1 system to provide a high-volume, high-speed mail server that can scale up to handle very large numbers of users and mail items. The TPF Internet mail servers can reduce the cost of ownership of a large Internet mail service with a single-image system, simplifying system management and operations.

TPF Internet mail server support is designed for the most demanding Internet mail environments, providing a scalable architecture that is capable of handling a quarter of a billion users in a single TPF processor complex. TPF Internet mail server support provides a cost-effective backend or commercial mail serving solution as well as allowing TPF applications to readily participate in Internet mail.

Architecture

The architecture for the standard Internet protocols is defined by the following Request for Comments (RFC) documents:

For more information about these RFCs and any related extensions, go to: http://www.ietf.org

On the TPF 4.1 system, the SMTP server is based on the Secure Mailer (also known as Postfix), and the IMAP and POP servers are based on the Cyrus project. For more information about these products, go to:

The TPF Internet mail servers can run on the same TPF 4.1 system as other TPF applications. If the volume of mail (throughput) gets large, consider running the TPF Internet mail servers on a separate processor to ensure that the servers have enough resources and do not interfere with other TPF applications.

Configuration Files

The behavior of the TPF Internet mail servers is controlled by the following configuration files:

You can also create an optional access list, named /etc/postfix/access, which directs the SMTP server to selectively accept or reject mail from or to specific addresses.

You can create and update the configuration files by using one of the following methods:

See TPF Transmission Control Protocol/Internet Protocol for more information about the configuration files, including how to create and update them.

Using TPF Internet Mail Server Support

The tasks associated with using the TPF Internet mail servers are divided into two categories based on the type of user:

Administrators or Operators
As an administrator or operator, you can perform tasks related to:

Clients or End Users
As a client, you can:

See TPF Transmission Control Protocol/Internet Protocol for more information about how to configure and use TPF Internet mail server support.

Operating Environment Requirements and Planning Information

To ensure that your TPF 4.1 system performs correctly with TPF Internet mail server support, you must establish the required operating environment. The following section describes hardware and software requirements specific to TPF Internet mail server support.

Operating Environment Requirements and Planning Information provides information about the minimum system configuration requirements that are necessary to operate the TPF 4.1 system. You may find it helpful to review that chapter along with the following information.

Hardware

There are no hardware requirements.

Software (Programming Requirements)

The following section contains information about software requirements.

Communication

The following section summarizes the communication changes.

Operating Environment for TCP/IP-Based Communication

To use TPF Internet mail server support, TCP/IP native stack support must be installed on the TPF 4.1 system. See TCP/IP Native Stack Support (APAR PJ26683) for more information about TCP/IP native stack support.

Interface Changes

The following section summarizes interface changes.

C/C++ Language

The following section summarizes C/C++ language changes. This information is presented in alphabetic order by the type of C/C++ language information. See the TPF C/C++ Language Support User's Guide and TPF Application Programming for more information about the C/C++ language.

Build Scripts

Table 1023 summarizes changes to the build scripts used by the build tool. This information is presented in alphabetic order by the name of the build script.

Table 1023. Changes to Build Scripts for TPF Internet Mail Server Support

Build Script Type New, Changed, or No Longer Supported? Description of Change
JCI2BS DLM New Added for TPF Internet mail server support.

Dynamic Load Module (DLM) Stubs

Table 1024 summarizes changes to the dynamic load module (DLM) stubs. This information is presented in alphabetic order by the name of the DLM stub. See TPF Application Programming for more information about the DLM stubs.

Table 1024. Changes to Dynamic Load Module (DLM) Stubs for TPF Internet Mail Server Support

DLM Stub New or No Longer Supported?
CMNG New

General Use C/C++ Language Header Files

Table 1025 summarizes the general use C/C++ language header file changes. This information is presented in alphabetic order by the name of the general use C/C++ language header file.

General use means these header files are available for your use.

Table 1025. Changes to General Use C/C++ Language Header Files for TPF Internet Mail Server Support

C/C++ Language Header File New, Changed, or No Longer Supported? Do You Need to Recompile Segments? Segments to Recompile
c$ck2sn.h Changed No Not Applicable
c$syseq.h Changed No Not Applicable
errno.h Changed No Not Applicable
fcntl.h Changed No Not Applicable
modes.h Changed No Not Applicable
param.h Changed No Not Applicable
resolv.h Changed Yes Reassemble CNSNAM, CNSPAR, CNSPRN, CRESCO, CRESDA, CRESDB, CRESIN, CRESMK, CRESQR, CRESSN, and link-edit CTXO.
signal.h Changed No Not Applicable
socket.h Changed No Not Applicable
sys/file.h New No Not Applicable
sys/filio.h New No Not Applicable
sys/ioccom.h New No Not Applicable
sys/lock.h New No Not Applicable
sys/resource.h New No Not Applicable
sys/sockio.h New No Not Applicable
sys/sys_time.h New No Not Applicable
sys/ttycom.h New No Not Applicable
sys/un.h New No Not Applicable
tpf_mail.h New No Not Applicable
types.h Changed No Not Applicable
unistd.h Changed No Not Applicable

Implementation-Specific C/C++ Language Header Files (IBM Use Only)

Table 1026 summarizes the general use C/C++ language header file changes that are for IBM use only. This information is presented in alphabetic order by the name of the general use C/C++ language header file.

Table 1026. Changes to Implementation-Specific C/C++ Language Header Files (IBM Use Only) for TPF Internet Mail Server Support

C/C++ Language Header File (IBM Use Only) New, Changed, or No Longer Supported? Do You Need to Recompile Segments? Segments to Recompile
i$dpwd.h Changed Yes Reassemble CPWGR0 and link-edit COMX.
tpfmail.h New No Not Applicable
tpfmaild.h New No Not Applicable

Library Interface Scripts

There are no changes.

Library Members (Object Files)

Table 1027 summarizes the library member (object file) changes. This information is presented in alphabetic order by the name of the library member (object file).

Table 1027. Changes to Library Members (Object Files) for TPF Internet Mail Server Support

Library Member (Object File) Library Module Name New, Changed, or No Longer Supported? Type Description of Change
CDDNPI COMX Changed C Language Updated for TPF Internet mail server support.
CFS181 COMX Changed C Language Updated for TPF Internet mail server support.
CPWGR0 COMX Changed C Language Updated for TPF Internet mail server support.
C536 COMX Changed C Language Updated for TPF Internet mail server support.

Link-Edited Modules

Table 1028 summarizes changes to the link-edited modules shipped by IBM, which should go into a data set with attributes DCB=(RECFM=U,LRECL=80,BLKSIZE=1200). This information is presented in alphabetic order by the name of the link-edited module.

Table 1028. Changes to Link-Edited Modules for TPF Internet Mail Server Support

Link-Edited Module New, Changed, or No Longer Supported? Description of Change
CMNA New Added for TPF Internet mail server support.
CMNC New Added for TPF Internet mail server support.
CMNG New Added for TPF Internet mail server support.
CMNI New Added for TPF Internet mail server support.
CMNJ New Added for TPF Internet mail server support.
CMNZ New Added for TPF Internet mail server support.
CMN0 New Added for TPF Internet mail server support.
CMN1 New Added for TPF Internet mail server support.
CMN2 New Added for TPF Internet mail server support.
CMN3 New Added for TPF Internet mail server support.
CMN8 New Added for TPF Internet mail server support.
COMX Changed Updated for TPF Internet mail server support.
CTXO Changed Updated for TPF Internet mail server support.
JCI2 New Added for TPF Internet mail server support.

Members (Object Files)

Table 1029 summarizes changes to members (object files). This information is presented in alphabetic order by the name of the member (object file).

Notes:

  1. You must recompile or reassemble a member (object file) if it has changed.

  2. You must prelink and link a dynamic load module (DLM) if it has changed.

Table 1029. Changes to Members (Object Files) for TPF Internet Mail Server Support

Member (Object File) DLM/DLL New, Changed, or No Longer Supported? Type Description of Change
CNA2E CTXO Changed C Language Updated for TPF Internet mail server support.
CNE2A CTXO Changed C Language Updated for TPF Internet mail server support.
CRESDA CTXO Changed C Language Updated for TPF Internet mail server support.
JCI2 JCI2 New C Language Added for TPF Internet mail server support.

Object Code Only (OCO) Stubs

There are no changes.

Configuration Constant (CONKC) Tags

There are no changes.

Control Program Interface (CINFC) Tags

There are no changes.

Copy Members

Table 1030 summarizes the copy member changes. This information is presented in alphabetic order by the name of the copy member.

Table 1030. Changes to Copy Members for TPF Internet Mail Server Support

Copy Member Type CP CSECT Where Copy Member Is Located DLM Where CP CSECT Is Located New, Changed, or No Longer Supported? Description of Change
CT15 Control Program CCCTIN Not Applicable Changed Updated for TPF Internet mail server support.
CPSE Control Program CCCPSE Not Applicable Changed Updated for TPF Internet mail server support.

Fixed File Records

Table 1031 summarizes fixed file record changes. This information is presented in alphabetic order by the name of the fixed file record.

Table 1031. Changes to Fixed File Records for TPF Internet Mail Server Support

Fixed File Record New, Changed, or No Longer Supported? Description of Change
#IBMMP4 Changed Updated to include ordinals 20 - 26 for TPF Internet mail server support.
#MAILxx, where xx is a 2-character alphanumeric string. New Added for TPF Internet mail server support. See TPF Transmission Control Protocol/Internet Protocol for more information about the #MAILxx record.

Macros

The following section summarizes the macro changes. This information is presented in alphabetic order by the type of macro.

Advanced Program-to-Program Communications (APPC) Macros

There are no changes.

Communication Macros and Statements

There are no changes.

Data Macros

Table 1032 summarizes the data macro changes. This information is presented in alphabetic order by the name of the data macro.

Table 1032. Changes to Data Macros for TPF Internet Mail Server Support

Data Macro New, Changed, or No Longer Supported? Do You Need to Reassemble Programs Using This Data Macro? Programs to Reassemble
CK2SN Changed No Not Applicable
DC0DC Changed Yes Reassemble CCDCOL, JCD1, and JCS0, and link-edit CPS0.
IMAIL New No Not Applicable
LDTRT Changed No Not Applicable

General Macros

There are no changes.

Selected Equate Macros

Table 1033 summarizes the selected equate macro changes. This information is presented in alphabetic order by the name of the selected equate macro.

Table 1033. Changes to Selected Equate Macros for TPF Internet Mail Server Support

Selected Equate Macro New, Changed, or No Longer Supported? Do You Need to Reassemble Programs? Programs to Reassemble
CZ1SE Changed No Not Applicable
SYSEQ Changed No Not Applicable

Structured Programming Macros (SPMs)

There are no changes.

System Initialization Program (SIP) Skeleton and Internal Macros (Inner Macros)

Table 1034 summarizes the system initialization program (SIP) skeleton and internal macro changes. This information is presented in alphabetic order by the name of the SIP skeleton and internal macro. If the SIP skeleton and internal macro (inner macro) is changed, you must reassemble the SIP Stage I deck and run the appropriate job control language (JCL) jobs from the SIP Stage II deck.

Table 1034. Changes to SIP Skeleton and Internal Macros for TPF Internet Mail Server Support

SIP Skeleton and Internal Macro New, Changed, or No Longer Supported?
SPPGML Changed
SPRIAT Changed

System Initialization Program (SIP) Stage I Macros and Statements

There are no changes.

System Initialization Program (SIP) Stage II Macros

Table 1035 summarizes system initialization program (SIP) Stage II macro changes. This information is presented in alphabetic order by the name of the SIP Stage II macro. If IBMPAL is changed, you must run the system allocator (SALO) and load the new program allocation table (PAT) to the TPF 4.1 system.

Table 1035. Changes to SIP Stage II Macros for TPF Internet Mail Server Support

SIP Stage II Macro New, Changed, or No Longer Supported?
IBMPAL Changed

System Communication Keypoint (SCK) Generation Macros

There are no changes.

System Macros

There are no changes.

System Macros (IBM Use Only)

There are no changes.

Segments

Table 1036 summarizes segment changes. This information is presented in alphabetic order by the name of the segment.

Table 1036. Changes to Segments for TPF Internet Mail Server Support

Segment Type Link-Edit Module (Where Offline Segment Is Linked) New, Changed, or No Longer Supported? Description of Change
BKD1 Real-Time Assembler Not Applicable New Added for TPF Internet mail server support.
CTKR Real-Time Assembler Not Applicable Changed Updated for TPF Internet mail server support.
CVAB Real-Time Assembler Not Applicable Changed Updated for TPF Internet mail server support.
JCS0 Real-Time Assembler Not Applicable Changed Updated for TPF Internet mail server support.
JRA2 Offline PL/I DATAREAD Changed Updated for TPF Internet mail server support.
JRS3 Offline PL/I DATAREAD Changed Updated for TPF Internet mail server support.

System Equates

The following section summarizes system equate changes.

SYSEQ Tags

Table 1037 summarizes changes to equates that are not configuration dependent (in SYSEQ). This information is presented in alphabetic order by the name of the SYSEQ tag.

Table 1037. Changes to SYSEQ Tags for TPF Internet Mail Server Support

SYSEQ Tag Equate Value New, Changed, or No Longer Supported?
#AQ_ORD 20 New
#DQ_ORD 21 New

User Exits

There are no changes.

Functional and Operational Changes

The following section summarizes functional and operational changes. This information is presented in alphabetic order by the functional or operational change.

See Appendix A, "PUT 2-15 Interface Changes by Authorized Program Analysis Report (APAR)" for a summary of functional and operational changes by APAR.

Commands

Table 1038 summarizes command changes. This information is presented in alphabetic order by the name of the command. See TPF Operations for a complete description of all commands.

Attention: Changes to commands can impact any automation programs you are using in your complex.

Table 1038. Changes to Commads for TPF Internet Mail Server Support

Command New, Changed, or No Longer Supported? Description of Change
ZMAIL New Controls the TPF Internet mail servers.
ZMAIL CREATEMAILBOX New Creates a mailbox.
ZMAIL DELETEACLMAILBOX New Deletes a user from a mailbox.
ZMAIL DELETEMAILBOX New Deletes a mailbox.
ZMAIL LISTACLMAILBOX New Displays users for a mailbox.
ZMAIL LISTMAILBOX New Displays a list of mailboxes.
ZMAIL LISTQUOTA New Displays storage for a mailbox.
ZMAIL LISTQUOTAROOT New Displays the quota root for a mailbox.
ZMAIL PASSWORD New Sets or changes the password for an account.
ZMAIL PATH New Displays the path to an account.
ZMAIL RENAMEMAILBOX New Changes the name of a submailbox.
ZMAIL SETACLMAILBOX New Sets the list of users for a mailbox.
ZMAIL SETQUOTA New Sets the storage limit for a mailbox.

Messages and System Errors

Table 1039 summarizes message (offline and online messages) and system error changes.

The message IDs or system error numbers are listed in numeric order preceded by their alphabetic prefix. Some offline and online messages do not have a standard message ID. For these, the messages are presented in alphabetic order based on the initial message text; or for those messages that begin with variable information, the initial message text that follows that variable information. See Messages (System Error and Offline) and Messages (Online) for a complete description of all messages and system errors.

Attention: Changes to offline messages, online messages, and system errors may impact any automation programs you are using in your complex.

Table 1039. Changes to Messages and System Errors for TPF Internet Mail Server Support

Message ID or System Error Number Message Type New, Changed, or No Longer Supported?
098100 System Error New
098101 System Error New
098102 System Error New
098103 System Error New
098104 System Error New
098105 System Error New
098106 System Error New
098107 System Error New
098108 System Error New
098109 System Error New
09810A System Error New
09810B System Error New
098120 System Error New
098121 System Error New
098122 System Error New
098123 System Error New
098124 System Error New
098125 System Error New
098126 System Error New
098127 System Error New
098128 System Error New
098129 System Error New
09812A System Error New
09812B System Error New
09812C System Error New
098130 System Error New
098131 System Error New
098132 System Error New
098133 System Error New
098134 System Error New
098135 System Error New
098136 System Error New
098137 System Error New
098138 System Error New
098139 System Error New
09813A System Error New
09813B System Error New
09813C System Error New
09813D System Error New
09813E System Error New
098140 System Error New
098141 System Error New
098142 System Error New
098143 System Error New
098144 System Error New
098145 System Error New
098146 System Error New
098147 System Error New
098148 System Error New
098149 System Error New
09814A System Error New
MAIL0001I Online New
MAIL0002E Online New
MAIL0003I Online New
MAIL0007E Online New
MAIL0092E Online New
MAIL0093E Online New
MAIL0094E Online New
MAIL0098E Online New
MAIL0099E Online New
MAIL0100I Online New

Performance or Tuning Changes

There are parameters in the configuration files for the TPF Internet mail servers that you can change to further tune your mail system. See TPF Transmission Control Protocol/Internet Protocol for more information about the configuration files. In addition, there is a data reduction report, the TPF Internet mail server summary report, that contains data to help you determine how to tune some of the configuration parameters. See TPF System Performance and Measurement Reference for more information about, and an example of, this summary report.

TPF Internet mail server support uses the IDNSHOSTNAME and BINDCACHE caches. Use the ZCACH command to increase the size of these caches as needed to ensure there are enough entries. See TPF Operations for more information about the ZCACH command.

Storage Considerations and Changes

There are parameters in the configuration files for the TPF Internet mail servers that can affect how long mail items are saved and the storage used by each user. You can change these parameters as needed to further tune your mail system. See TPF Transmission Control Protocol/Internet Protocol for more information about the configuration files.

The dynamic load modules (DLMs) that are provided with TPF Internet mail server support are very large and may require additional system heap storage. Use the ZCTKA DISPLAY and the ZCTKA ALTER commands to display and change the size of system heap storage, respectively. See TPF Operations for more information about these commands.

System Initialization Program (SIP) and System Generation Changes

There are no changes.

Loading Process Changes

There are no changes.

Online System Load Changes

There are no changes.

Publication Changes

Table 1040 summarizes changes to the publications in the TPF library. This information is presented in alphabetic order by the publication title. See the TPF Library Guide for more information about the TPF library.

Table 1040. Changes to TPF Publications for TPF Internet Mail Server Support

Publication Title Softcopy File Name Description of Change
TPF Application Programming GTPAPP0D Updated with information about TPF Internet mail server support.
TPF C/C++ Language Support User's Guide GTPCLU0E Updated with information about C functions that were added or changed for TPF Internet mail server support.
TPF Concepts and Structures GTPCON0B Updated with information about TPF Internet mail server support.
TPF Database Reference GTPDBR0C Updated with recoup information about TPF Internet mail server support.
TPF Library Guide GTPDOC0E Updated with definitions for new terminology in the master glossary.
Messages (System Error and Offline) and Messages (Online) Not Applicable Updated with information about messages and system errors that were added, changed, and no longer supported for TPF Internet mail server support.
TPF Migration Guide: Program Update Tapes GTPMG204 Updated with migration considerations for TPF Internet mail server support.
TPF Operations GTPOPR0E Updated with information about the commands that were added and changed for TPF Internet mail server support.
TPF System Generation GTPSYG0E Updated with information about the new fixed file records for TPF Internet mail server support.
TPF System Performance and Measurement Reference GTPSPR0D Updated the sample data collection and reduction reports for TPF Internet mail server support.
TPF Transmission Control Protocol/Internet Protocol GTPCLW0A Updated with information about how to configure and use TPF Internet mail server support.

Host System Changes

There are no changes.

Application Programming Interface (API) Changes

With the new mail function, you can write TPF application programs to access Internet mail. See TPF C/C++ Language Support User's Guide for more information about the mail function.

Database Changes

Before you run recoup for the TPF Internet mail server database, ensure the mail server recoup descriptor (BKD1) is loaded on the TPF subsystem in which you plan to run the TPF Internet mail servers. Do not load the mail server recoup descriptor to subsystems in which the TPF Internet mail servers will not run.

In addition, you must ensure that BKD1 contains a GROUP and INDEX macro pair associated with each #MAILxx record that you have defined. Segment BKD1 is initially shipped with the macro statements needed for a mail domain associated with a #MAIL01 fixed file record type. If you define additional #MAILxx fixed file record types (such as, #MAIL02, #MAIL03, and so on) or want to use a record type value other than #MAIL01, you must update segment BKD1.

See TPF Transmission Control Protocol/Internet Protocol for more information about recoup considerations for the mail database and how to update segment BKD1. See TPF Database Reference for more information about how to run recoup.

Feature Changes

There are no changes.

Installation Validation

There are no changes.

Migration Scenarios

Before You Begin

Ensure that your TPF 4.1 system is at program update tape (PUT) 13. In particular, ensure that you have the following APARs from PUT 13 installed:

Use the following procedure to install TPF Internet mail server support on your TPF 4.1 system:

  1. Unpack PUT 14, which contains APARs PJ27784 and PJ27865 for TPF Internet mail server support. See TPF Memo to Licensees for more information about unpacking the tape.
    Note:
    If you plan to run the TPF Internet mail servers in a subsystem other than the basic subsystem (BSS), you must apply APAR PJ27758.
  2. Install the following:
  3. Run the system allocator (SALO) using IBMPAL and SPPGML additions for newly created segments to create an updated program allocation table (PAT) and system allocator (SAL) table.
  4. Update the record ID attribute table (RIAT) with the new FC55 record ID, as appropriate. See TPF System Generation for more information about the RIAT.
  5. Determine how many mail domains you need for your mail system.
  6. Determine which subsystem the TPF Internet mail servers will run on, referred to as the mail subsystem in the remainder of this information.
  7. On the mail subsystem, update the SIP RAMFIL macro input statements to the FACE table generator (FCTBG) by specifying the #MAILxx fixed file record type, where xx is a 2-character alphanumeric string. You will need a different #MAILxx record type for each domain in your mail system. Allocate 1000 #MAILxx records for each domain. See TPF System Generation for more information about the #MAILxx record type and the RAMFIL macro.
  8. On the mail subsystem, ensure that there are at least 100 #IBMMP4 records allocated.
  9. Run the FCTBG to create a new FACE table.
  10. Assemble the SIP stage I deck to create a SIP stage II deck.
  11. Run SIP stage II.
  12. Run the CBLD program for the build scripts listed in Table 1023.
  13. Reassemble or recompile the following:
  14. On the mail subsystem, verify that recoup descriptor BKD1 is coded correctly for each mail domain that you are defining. If you define a fixed file record type other than #MAIL01 or if you define more than one #MAILxx fixed file record type, you must update and reassemble segment BKD1. See TPF Transmission Control Protocol/Internet Protocol for more information about recoup considerations and how to update BKD1.
  15. Load the link-edited modules listed in Table 1028.
  16. IPL your TPF 4.1 system.
  17. On the mail subsystem, cycle the TPF 4.1 system to CRAS state or higher.
  18. On the mail subsystem, enter a ZIFIL command to initialize each #MAILxx record type that you defined. For example, enter the following to initialize the #MAIL01 records:

    ZIFIL MAIL01/FC55/00/0/999/NNN/N

  19. On the mail subsystem, enter the following on every processor to initialize the mail-related IBMMP4 records:

    ZIFIL IBMMP4/FC63/00/20/20/NNN/N

    ZIFIL IBMMP4/FC66/00/21/21/NNN/N

  20. Enter ZFILE echo "postfix::14:3::/:" >> /etc/passwd to add the postfix user ID to the password file on the TPF 4.1 system.
  21. On the mail subsystem, enter ZMAIL FLUSH to initialize the database queue pointers.
  22. Create the SMTP, IMAP and POP, and TPF configuration files. See TPF Transmission Control Protocol/Internet Protocol for more information about how to create these files.
  23. Ensure that you have a valid registered domain name.
  24. Update the external DNS servers with the domain names and IP addresses of the TPF Internet mail servers.
  25. On the mail subsystem, enter the following to add the TPF Internet mail servers to the Internet daemon configuration file (IDCF):

    ZINET ADD S-SMTP PGM-CMN0 MODEL-NOWAIT PORT-25 P-TCP IP-ANY ACT-OPER STATE-CRAS

    ZINET ADD S-IMAP PGM-CMNA MODEL-NOWAIT PORT-143 P-TCP IP-ANY ACT-OPER STATE-CRAS

    ZINET ADD S-POP3 PGM-CMNC MODEL-NOWAIT PORT-110 P-TCP IP-ANY ACT-OPER STATE-CRAS

    See TPF Operations for more information about the ZINET ADD command.

  26. On the mail subsystem, enter ZMAIL START READ to start the IMAP and POP servers.
  27. Enter the ZFILE export command to set the MAILDOMAIN environment variable to the domain in which you want to create mailboxes. See TPF Operations for more information about the ZFILE export command.
  28. On the mail subsystem, use the appropriate ZMAIL commands to create user accounts, mailboxes, and access permissions. See TPF Transmission Control Protocol/Internet Protocol for more information about how to do this. See TPF Operations for more information about the ZMAIL commands.
  29. On the mail subsystem, enter ZMAIL START ALL to start the TPF Internet mail servers.

    The mail servers are now ready for you to use.