TCP/IP App. Services (TAS) FORTRAN Programming Guide

!+ OS 2200 

TCP/IP Application 

Services (TAS) FORTRAN 

Programming 

Guide 

Copyright 1997 Unisys Corporation. 

All rights reserved. 

Unisys is a registered trademark of Unisys Corporation. 

Level 6R1 September 1997 

Printed in U S America 

Priced Item 3787 3247-111

The names, places, and/or events used in this publication are not intended to correspond to any 

individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, 

places, and/or events with the names of any individual, living or otherwise, or that of any group or 

association is purely coincidental and unintentional. 

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THE DOCUMENT. Any product and related 

material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly 

executed Program Product License or Agreement to purchase or lease equipment. The only warranties 

made by Unisys, if any, with respect to the products described in this document are set forth in such 

License or Agreement. Unisys cannot accept any financial or other responsibility that may be the result 

of your use of the information in this document or software material, including direct, indirect, special, 

or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies 

with the laws, rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise 

of such changes and/or additions. 

RESTRICTED - Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 

252.227-7013 and 252.11 15/FAR 52.227-14 & 52.227-19 for commercial computer software. 

Correspondence regarding this publication should be forwarded to Unisys Corporation either by using 

the Business Reply Mail form included with this document, or by addressing remarks to Unisys 

Corporation,Tredyffrin/Malvern Product Information, Malvern Development Center, P.O. Box 203, Paoli, 

PA, 19301, U.S.A.Comments about documentation can also be sent through e-mail to: 

aspgpi@unisys.com 

All other terms mentioned in this document that are known to be trademarks or service marks have been 

appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this information. Use of a 

term in this document should not be regarded as affecting the validity of any trademark or service mark.

Contents 

About This Guide :::::::::::::::::::::::::::::::::::::::::::::: xiii 

Section 1. Introduction 

1.1. What is TAS? ::::::::::::::::::::::::::::::::: 1-1 

1.2. What is the FORTRAN Interface? :::::::::::::::: 1-3 

1.3. Overview of the File Transfer Facility :::::::::::: 1-4 

1.4. Overview of the Mail Transfer Facility ::::::::::: 1-5 

Section 2. Procedures for Writing TAS FORTRAN Programs 

2.1. TAS FORTRAN Program Structure :::::::::::::: 2-1 

2.2. Including Information Packets and Storage Areas in 

a TAS FORTRAN Program :::::::::::::::::: 2-2 

2.2.1. Including Information Packets :::::::::::::::: 2-2 

2.2.2. Defining Storage Areas ::::::::::::::::::::: 2-7 

2.3. Using Subroutine Calls and INCLUDE Statements in a 

TAS FORTRAN Program :::::::::::::::::::: 2-9 

2.3.1. Subroutine Calls ::::::::::::::::::::::::::: 2-9 

2.3.2. INCLUDE Statements ::::::::::::::::::::::: 2-12 

2.3.3. Initialization Packets :::::::::::::::::::::::: 2-13 

Section 3. File Transfer Applications 

3.1. Using TAS Functions, Parameter Packets, and 

Sessions ::::::::::::::::::::::::::::::::: 3-1 

3.1.1. Using Parameter Packets for TAS Functions ::::: 3-1 

3.1.2. Opening a Session with a Remote Host ::::::::: 3-3 

3.1.3. Closing a Session with a Remote Host ::::::::: 3-4 

3.2. Allocating File Space on Remote Hosts 

(DDN$ALLO) :::::::::::::::::::::::::::::: 3-5 

3.3. Changing to Parent Directory on Remote Hosts 

(DDN$CDUP) :::::::::::::::::::::::::::::: 3-8 

3787 3247-111 iii

Contents 

3.4. Changing Work Directory on Remote Hosts 

(DDN$CWD) :::::::::::::::::::::::::::::: 3-10 

3.5. Deleting Files on Hosts (DDN$DEALLOC) ::::::::: 3-12 

3.6. Deregistering a File for Event Notification 

(DDN$DEREG) ::::::::::::::::::::::::::::: 3-14 

3.7. Remote to Local Transfer in a Session 

(DDN$FGET) :::::::::::::::::::::::::::::: 3-16 

3.8. Local to Remote Transfer in a Session 

(DDN$FPUT) :::::::::::::::::::::::::::::: 3-20 

3.9. Establishing a Session with a Remote Host 

(DDN$LOGIN) ::::::::::::::::::::::::::::: 3-24 

3.10. Making a Directory on Remote Hosts (DDN$MKD) 3-26 

3.11. Returning a Directory Name on Remote Hosts 

(DDN$PWD) ::::::::::::::::::::::::::::::: 3-28 

3.12. Ending a Session (DDN$QUIT) :::::::::::::::::: 3-30 

3.13. Registering Files for Event Notification 

(DDN$REGISTER) :::::::::::::::::::::::::: 3-31 

3.14. Renaming a File (DDN$RENAME) ::::::::::::::: 3-34 

3.15. Resuming a Checkpoint File Transfer 

(DDN$RESUME) ::::::::::::::::::::::::::: 3-36 

3.16. Removing a Directory on Remote Hosts 

(DDN$RMD) :::::::::::::::::::::::::::::: 3-38 

3.17. Sending Site-Specific Information about a File 

Transfer (DDN$SITE) ::::::::::::::::::::::: 3-40 

3.18. Getting Event Notification Status Information 

(DDN$STATUS) :::::::::::::::::::::::::::: 3-42 

3.19. Transferring Files or Elements between Hosts 

(DDN$TRANSFER) ::::::::::::::::::::::::: 3-44 

3.20. Designing a File Transfer Application :::::::::::: 3-48 

Section 4. Mail Applications 

4.1. Mail Commands :::::::::::::::::::::::::::::: 4-1 

4.1.1. Basic Format ::::::::::::::::::::::::::::: 4-2 

4.1.2. Coding Your Own Subroutines :::::::::::::::: 4-2 

4.1.3. Statements Summarized :::::::::::::::::::: 4-2 

4.1.4. Start with DDN$MAILBOX ::::::::::::::::::: 4-2 

4.2. Listing Incoming/Outgoing Mail Items 

(DDN$CHECK) :::::::::::::::::::::::::::: 4-4 

4.3. Continuing Mail Operation with Another Buffer 

(DDN$CONTINUE) ::::::::::::::::::::::::: 4-8 

4.4. Ending a Mailbox Assignment (DDN$DISCONN) ::: 4-11 

iv 3787 3247-111

Contents 

4.5. Terminating a Mail Operation (DDN$DISCONT) ::: 4-12 

4.6. Creating, Changing, or Deleting Distribution Lists 

(DDN$DIST) ::::::::::::::::::::::::::::::: 4-13 

4.7. Getting Mail from the Mailbox (DDN$GET) ::::::: 4-19 

4.8. Creating, Changing, Assigning, or Deleting 

Mailboxes (DDN$MAILBOX) ::::::::::::::::: 4-22 

4.9. Creating an Item of Mail (DDN$PREPARE) ::::::: 4-25 

4.10. Deleting Mail from a Mailbox (DDN$REMOVE) :::: 4-28 

4.11. Sending Mail to Mailboxes (DDN$SENDMAIL) ::::: 4-30 

4.12. Obtaining a Mailbox Name (DDN$VERIFY) ::::::: 4-37 

4.13. Designing a Mail Transfer Application ::::::::::: 4-39 

4.14. Using the Mail Buffer Area ::::::::::::::::::::: 4-45 

Section 5. Compiling, Linking, and Executing TAS FORTRAN 

Programs 

5.1. Preparing Programs for Execution :::::::::::::: 5-1 

5.2. Run Streams for TAS FORTRAN Programs ::::::: 5-2 

Appendix A. TAS Status Codes 

Appendix B. Conventions for Naming Hosts, Files, and Mail 

B.1. Host Identifiers ::::::::::::::::::::::::::::::: B-1 

B.2. File Conventions :::::::::::::::::::::::::::::: B-3 

B.2.1. Naming Files ::::::::::::::::::::::::::::: B-3 

B.2.2. Naming Elements :::::::::::::::::::::::::: B-4 

B.2.3. Referencing Files and Elements ::::::::::::::: B-5 

B.2.4. Examples :::::::::::::::::::::::::::::::: B-5 

B.3. Mail Processor Conventions :::::::::::::::::::: B-6 

B.3.1. Mailbox Names/Mailbox Key ::::::::::::::::: B-6 

B.3.2. Mail Identifiers :::::::::::::::::::::::::::: B-6 

B.3.3. User Names :::::::::::::::::::::::::::::: B-7 

Appendix C. File Transfer Example 

C.1. Sample File Transfer Program Run Stream :::::: C-1 

C.2. Sample File Transfer Application Program ::::::: C-2 

3787 3247-111 v

Contents 

Appendix D. Mail Transfer Example 

D.1. Sample Mail Transfer Program Run Stream ::::: D-1 

D.2. Sample Mail Transfer Application Program :::::: D-2 

Appendix E. Initialization Subroutines 

Appendix F. Register 

Appendix G. Deregister 

Glossary 

Bibliography 

F.1. Converting a File Name to a File-ID ::::::::::::: F-1 

F.2. Incoming File Transfer :::::::::::::::::::::::: F-3 

F.2.1. Overview :::::::::::::::::::::::::::::::: F-3 

F.2.2. Run Stream Selection :::::::::::::::::::::: F-3 

G.1. Deregistering File Names Associated with an 

Application-id ::::::::::::::::::::::::::::: G-1 

G.2. Deregistering File Names That Have No Associated 

Wildcard ::::::::::::::::::::::::::::::::: G-3 

G.3. Deregistering File Names That Match a Specified 

File Name :::::::::::::::::::::::::::::::: G-5 

G.4. Deregistering File Names That Were Registered With 

a Wildcard :::::::::::::::::::::::::::::::: G-7 

vi 3787 3247-111

Figures 

2-1. FORTRAN Subroutine Calls and Assignment Statements :::::::::::::: 2-9 

2-2. Referencing Information Packets through Subroutine Calls :::::::::::: 2-10 

3-1. Typical TAS FORTRAN File Transfer Block Diagram :::::::::::::::::: 3-48 

3-2. Typical TAS FORTRAN File Transfer Flow Diagram ::::::::::::::::::: 3-49 

4-1. Typical TAS FORTRAN Mail Transfer Block Diagram ::::::::::::::::: 4-39 

4-2. Mail Transfer Flow Diagram (Create Mailbox and Prepare Mail from Buffer) 4-40 

4-3. Mail Transfer Flow Diagram (Assign Mailbox and Prepare Mail from File) : 4-41 

4-4. Mail Transfer Flow Diagram (Assign Mailbox and Send Prepared Mail) ::: 4-42 

4-5. Mail Transfer Flow Diagram (Create Mail from Buffer and Send 

Immediately) ::::::::::::::::::::::::::::::::::::::::::::: 4-43 

4-6. Mail Transfer Flow Diagram (Check Incoming Mail and Get First Mail Item) 4-44 

5-1. Compile, Link, and Execute Stream for a TAS FORTRAN Program :::::: 5-3 

5-2. A Compile, Link, and Execute Stream :::::::::::::::::::::::::::: 5-4 

3787 3247-111 vii

Tables 

3-1. File Transfer Information Packets Referenced by INCLUDE Statements and 

Subroutine Calls :::::::::::::::::::::::::::::::::::::::::: 3-2 

4-1. Transfer Packets Referenced by INCLUDE Statements and Subroutine 

Calls ::::::::::::::::::::::::::::::::::::::::::::::::::: 4-3 

A-1. Class Code 192 Detail Status Values ::::::::::::::::::::::::::::: A-2 



A-4. D$PCEF Error Indicators :::::::::::::::::::::::::::::::::::::: A-19 

A-5. D$ELST Errors :::::::::::::::::::::::::::::::::::::::::::::: A-20 

3787 3247-111 ix

Examples 

C-1. UCS FORTRAN Compile and Link Stream for Sample File Transfer 

Program :::::::::::::::::::::::::::::::::::::::::::::::: C-1 

D-1. UCS FORTRAN Compile and Link Stream for Sample Mail Transfer 

Program :::::::::::::::::::::::::::::::::::::::::::::::: D-1 

3787 3247-111 xi

About This Guide 

Purpose 

Scope 

Audience 

This guide is one of a series designed to instruct and guide you in using the Unisys TCP/IP 

Application Services (TAS) software. It describes how to write TAS FORTRAN mail and 

file transfer application programs for a TCP/IP network. 

The product name TAS replaces DDN 1100 (Defense Data Network). The term TAS gives a 

clearer picture of the services available, as the use of TCP/IP has expanded far beyond the 

Defense Data Network where it originated. 

Program-to-program communication is not discussed in this document. 

Program-to-program software is now packaged as part of the operating system group and 

is discussed in the DDP-PPC TCP/IP Interface FORTRAN Programming Guide. 

The purpose of this guide is to instruct an applications programmer who wishes to: 

$ Use a Unisys-supplied FORTRAN copy library to insert TAS pre-written information 

packets and subroutine calls into a Universal Compiling System (UCS) FORTRAN 

program 

$ Write a FORTRAN application program using the TAS FORTRAN information packets 

and subroutine calls 

$ Compile the program 

$ Link the application element and TAS relocatable or object module element as one 

object module element 

$ Execute the program 

This guide provides detailed information on TAS FORTRAN subroutine calls and 

information packets. It describes how to organize the calls and packets to enable users to 

write customized FORTRAN applications that can exchange data between programs, 

transfer files or process mail in a multihost TAS network. 

The primary audience for this guide is the applications programmer. 

3787 3247-111 xiii


This person is typically a FORTRAN programmer with several years of experience. He or 

she might have a limited knowledge of communications and is dependent on reading this 

documentation to be able to write a TAS application program. 

The secondary audience for this guide is the site administrator. 

This person typically has network and data base management experience. The site 

administrator is responsible for installing and implementing new hardware and software, 

network management, data bases, and security. 

Prerequisites 

To use this manual, you must understand TCP/IP concepts and know how to write 

standard FORTRAN programs. 

How to Use This Guide 

This guide explains how to: 

$ Use INCLUDE statements to copy information packets into the program 

$ Use standard FORTRAN verbs to set the information packets to desired values 

$ Use INCLUDE statements in the program to issue TAS FORTRAN subroutine calls for 

program-to-program, file transfer, and mail transfer applications 

$ Design and construct a TAS application program 

$ Compile, link, and execute the program 

Use Section 2 to see how the FORTRAN subroutine calls and packets are organized in a 

FORTRAN program structure. Use Sections 3 and 4 for detailed information on packet 

settings, how to issue subroutine calls, and how to construct a typical file transfer or mail 

transfer application. Use Section 5 to learn how to compile, link, and execute the 

application program. See Appendixes C and D for typical examples of TAS applications. 

See Appendix E for listings of the initialization subroutines that clear unused fields in 

command packets. 

Organization 

Section 1. Introduction 

Describes what TAS FORTRAN allows you to do. Discusses TAS interaction with operating 

system communications elements. This section also explains basic terms and gives an 

overview of how to write a program. 

Section 2. Procedures for Writing TAS FORTRAN Programs 

Discusses conventional FORTRAN versus TAS FORTRAN program structure. 

xiv 3787 3247-111

Section 3. File Transfer Applications 


Describes how to issue file transfer commands from your program, how to delete files in 

remote or local hosts, and how to construct a basic TAS FORTRAN file transfer program. 

Section 4. Mail Applications 

Describes how to create, change, assign, and delete mailboxes or mailbox lists. Also 

describes how to create outgoing mail, list incoming/outgoing mail, deliver mail, obtain 

mail, and verify a user’s mailbox. The section also discusses how to construct a basic TAS 

FORTRAN mail transfer program. 

Section 5. Compiling, Linking, and Executing TAS FORTRAN Programs 

Describes the executive control language run stream used to compile, collect, and execute 

the TAS FORTRAN programs. 

Appendix A. TAS Status Codes 

Describes the status code values returned to the TAS application program by the TAS 

FORTRAN interface on completion of subroutine calls. 

Appendix B. Conventions for Naming Hosts, Files, and Mail 

Discusses naming TAS hosts, OS 1100 elements and files, and mail processor items. 

Appendix C. File Transfer Example 

Contains a working example of a TAS file transfer application. 

Appendix D. Mail Transfer Example 

Contains a working example of a TAS mail transfer application. 

Appendix E. Initialization Subroutines 

Contains listings of subroutines that clear unused fields in command packets. 

3787 3247-111 xv


Related Product Information 

Note: For all manuals, use the version that corresponds to the release level of the product 

software in use on the system. 

The following manuals provide related information you may find helpful: 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface C Language 

Programming Guide 3787 3254 

Describes how to write C Language interface programs in a TCP/IP network. 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface COBOL 


Describes how to write COBOL interface programs in a TCP/IP network. 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface FORTRAN 


Describes how to write FORTRAN interface programs in a TCP/IP network. 

OS 2200 TCP/IP Application Services (TAS) C Language Programming Guide 

4173 5135 

Describes how to use the C language to create TAS programs. 

OS 2200 TCP/IP Application Services (TAS) COBOL Programming Guide 

3787 3205 

Describes how to write TAS COBOL application programs that can exchange data with 

other programs in the same or remote computers in a TCP/IP network. 

OS 2200 TCP/IP Application Services (TAS) File Transfer User Guide 3787 3213 

Describes how to transfer files and deallocate files on remote hosts through terminal 

operator commands. 

OS 2200 TCP/IP Application Services (TAS) Implementation and Administration 

Guide 3787 3221 

Provides instructions for installing and verifying file transfer and mail processing on your 

host. 

OS 2200 TCP/IP Application Services (TAS) Mail Processor User Guide 

3787 3239 

Describes how to create, send, and receive messages on a local host or in an interactive 

multihost environment. 

xvi 3787 3247-111

Section 1 

Introduction 

1.1. What is TAS? 

TCP/IP Application Services (TAS) is a software product that communicates with other 

hosts in an X.25 Public Data Network (PDN) or in a Local Area Network (LAN) using the 

Transmission Control Protocol/Internet Protocol (TCP/IP), originally defined for the 

United States Department of Defense Data Network (DDN). The product name TAS 

replaces DDN 1100 (Defense Data Network). 

Included in this product are: 

$ The TAS File Transfer Facility 

Provides file transfer capabilities, based on the File Transfer Protocol (DDN, 

MIL-STD-1780). For complete information on the TAS File Transfer Facility, see the 

TAS File Transfer User Guide. 

$ The TAS Mail Processor 

Provides electronic mail processing capabilities, based on the Simple Mail Transfer 

Protocol (DDN, MIL-STD-1781). For complete information on the TAS Mail Processor, 

see the TAS Mail Processor User Guide. 

Language packages available with TAS are: 

$ The TAS COBOL Programming Interface 

Provides facilitiesfor writing COBOL applications programs. For complete information 

on the TAS COBOL Programming Interface, see the TAS COBOL Programming Guide. 

$ The TAS C Language Programming Interface 

Provides facilities for writing C language applications programs. For complete 

information on the TAS C Language Programming Interface, see the TAS C Language 

Programming Guide. 

$ The TAS FORTRAN Programming Interface (the subject of this manual) 

Provides facilities for writing FORTRAN applications programs that: 

v Invoke the TAS File Transfer Facility 

v Send or receive mail between hosts in a TCP/IP network 

3787 3247-111 1-1

What is TAS? 

All TAS components provide interhost processing that can be: 

$ Homogeneous (OS 2200 host-to-OS 2200 host) 

$ Heterogeneous (OS 2200 host-to-non-OS 2200 host) 

Note: Throughout this manual, when we refer to the local host, we are referring to the 

OS 2200 host. 

1-2 3787 3247-111

1.2. What is the FORTRAN Interface? 

What is the FORTRAN Interface? 

The TAS FORTRAN interface includes FORTRAN copy elements and TAS object modules. 

This interface provides two facilities for writing FORTRAN application programs. When 

the application programs are executed, they call upon the specified FORTRAN interface 

facility to send or receive information between hosts in a TAS network. The facilities are: 

$ File transfer 

$ Mail transfer 

The FORTRAN interface provides INCLUDE statements for both facilities. These 

INCLUDE statements are used in your source application program to provide information 

packets and issue requests (subroutine calls) to the TAS interface. 

You include the TAS FORTRAN interface when you compile and link your UCS FORTRAN 

application program. (See Section 5.) The output object module can be executed in the 

same way as any standard FORTRAN program. 

Multitasking of FORTRAN programs is not allowed by TAS. 

3787 3247-111 1-3

Overview of the File Transfer Facility 

1.3. Overview of the File Transfer Facility 

The file transfer facility: 

$ Transfers files within the local host 

$ Transfers files between a local host and a remote host 

$ Transfers files between two remote hosts 

$ Deletes (deallocates) a file on the local or remote host 

$ Resumes an interrupted file transfer at a desired checkpoint 

$ Renames a file on a remote host 

$ Sends protocol information about a file transfer to a remote host 

$ Registers and deregisters files for event notification 

$ Provides status information about event notification 

$ Opens and closes a communication path between hosts and allows file transfer along 

this path 

$ Allocates file space on a remote non-OS 2200 host where necessary to reserve space 

before transferring a file 

$ Creates, changes, and removes a directory on a remote non-OS 2200 host 

1-4 3787 3247-111

Overview of the Mail Transfer Facility 

1.4. Overview of the Mail Transfer Facility 

The mail transfer facility lets you: 

$ Create, change, assign, or delete mailboxes 

$ Create, change, list, or delete distribution lists 

$ Create outgoing mail 

$ List mail items in a mailbox 

$ Retrieve or delete mail items 

$ Validate other mailboxes 

$ Transfer prepared mail to addressees 

$ End mailbox assignments 

$ Continue a mail transfer operation by providing an additional buffer 

$ Discontinue a mail transfer operation 

3787 3247-111 1-5

Section 2 

Procedures for Writing TAS FORTRAN 

Programs 

2.1. TAS FORTRAN Program Structure 

Although TAS FORTRAN programs are similar to conventional programs, certain 

additional items are required. For instance, you must: 

$ Include information packets and any other necessary storage areas in the FORTRAN 

program 

$ Use INCLUDE statements or subroutine calls in the FORTRAN program 

3787 3247-111 2-1

Including Information Packets and Storage Areas in a TAS FORTRAN Program 

2.2. Including Information Packets and Storage 

Areas in a TAS FORTRAN Program 

The program supplies TAS with the information needed to control data transfer. It contains 

declaration statements in information packets. These packets correspond to the arguments 

in the TAS subroutine calls discussed in Section 3and Section 4. 

2.2.1. Including Information Packets 

Information packets supply the data transfer control information. These packets are 

constructed for you using standard subroutine calls. Just add these packets into your 

program from the FORTRAN procedure by using the INCLUDE statements for the 

appropriate applications in the program. (See 2.3.) 

The INCLUDE statements place all the necessary data declarations into your program 

when the program is compiled. 

Each command packet has an associated initialization subroutine that may be used to clear 

unused fields before specifying any parameters and issuing a function call. These 

initialization subroutines are described in Appendix E. 

The following example shows the information packets produced by including individual 

calls for specific packets in a file transfer application program. Alternatively, use the 

DDN$FTPPKTS and DDN$PCSTPKT calls to include the group of packets. 

All the fields and parameters forming the information packets for a file transfer application 

are described in detail with the related INCLUDE statement or subroutine call in Section 3. 




Portion of Application Program Containing the File Transfer Information Packets 

 

 

 

 

 

 

 

 

 

 

2-2 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 2-3


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2-4 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 2-5


The following example shows the information packets produced by including individual 

calls for specific packets in a mail transfer application program. Alternatively, use the 

DDN$SMTPPKTS and DDN$PCSTPKT calls to include the group of packets. 

All the fields and parameters forming the information packets for mail transfer applications 

are described in detail with the related INCLUDE statement or subroutine call in Section 4. 




Portion of Application Program Containing the Mail Transfer Information Packets 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2-6 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2.2.2. Defining Storage Areas 

In your program, you also define message areas, mailbox lists, and distribution lists, and 

you store error messages. These areas and values are specific to your program and are not 

supplied through INCLUDE statements. 

For file transfer application programs, no additional storage areas are needed. 

For mail transfer application programs, code the following areas in your program. Because 

they are referenced by the INCLUDE statements, you must code them even if your 

application does not use them. Include: 

$ Storage area to hold the mail (mail buffer) 

Most mail transfer commands reference this area to transfer the data. Use a maximum 

size of 3300 characters. See 4.14 for a discussion on alternative ways to define this area. 

Example: 

3787 3247-111 2-7


 

$ Storage area to hold the mailbox list 

Use a maximum of 1760 characters (20 entries of 88 characters each). 

Example: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

See 4.11 for a discussion on alternative ways to define this area. See B.3 for host- and 

mailbox-naming conventions. 

$ Storage area to hold the distribution list 

Use a maximum of 20 entries of 88 characters each. 

Example: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

See 4.11 for a discussion on alternative ways to define this area. See B.3 for mail- and 

host-naming conventions. 

2-8 3787 3247-111

Using Subroutine Calls and INCLUDE Statements in a TAS FORTRAN Program 

2.3. Using Subroutine Calls and INCLUDE 

Statements in a TAS FORTRAN Program 

Application programs use conventional FORTRAN assignment and INCLUDE statements 

and subroutine calls for input/output data transfers and FORTRAN manipulations. They 

also use assignment statements to set information fields in the information packets. See 

Figure 2-1. 

Data Files 

TAS 

FORTRAN 

Assignment 

Statement 

FORTRAN 

Application 

Program 

DDP-PPC CMS 

TAS FORTRAN 

Subroutine Call 

Status 

Data 

TAS 

Interface 

TCP/IP 

Network 

Figure 2-1. FORTRAN Subroutine Calls and Assignment Statements 

In addition, each packet contains an EQUIVALENCE statement that allows you to snap out 

the packet in octal format, for debugging ease. 

2.3.1. Subroutine Calls 

Special subroutine calls are used for program-callable file and mail transfer applications. 

Use these subroutine calls to: 

$ Enter the FORTRAN applications interface element 

$ Pass control information that is in your program 

$ Issue requests to TAS 

Figure 2-2 shows you how a subroutine call references information packets. In this case, it 

shows how to use a standard FORTRAN assignment statement to set an information 

packet field before issuing the call. 

3787 3247-111 2-9


COMMON /CPCST/D$PCID/D$PCCL,D$PCDT,D$PCML(3),D$TIME,D$BYTE,D$AVG 

DIMENSION D$PCRF(2),D$OCPC(69) 

CHARACTER*4 D$PCST,D$PCID 

INTEGER D$PCCL,D$PCDT,D$PCRF,D$PCEF,D$PCPC 

CHARACTER*8 D$TIME,D$BYTE,D$AVG 

CHARACTER*80 D$PCML 

EQUIVALENCE (D$PCCL,D$PCRF(91)) 

EQUIVALENCE (D$PCID,D$PCEF) 

EQUIVALENCE (D$PCID,D$PCST) 

EQUIVALENCE (D$PCID,D$PCPC(1)) 

* 

* 

* 

COMMON /C$LOG/D$LOHD,D$LOF1,D$LOUD,D$LOPW,D$LOPF,D$LOCL,D$LOF2, 

1 D$LOAC,D$LOPD 

DIMENSION D$OCLG(79) 

CHARACTER*4 D$LOG 

CHARACTER*18 D$LOPW 

CHARACTER*12 D$LOUD,D$LOAC,D$LOPD 

CHARACTER*2 D$LOCL,D$LOF2,D$LOPF 

CHARACTER*1 D$LOF1 

CHARACTER*255 D$LOHD 

INTEGER D$OCLG 

EQUIVALENCE (D$LOHD,D$LOG) 

EQUIVALENCE (D$OCLG(1),D$LOHD) 

* 

* 

* 

COMMON /DEAL/D$DHOS/D$DHFL,D$FILE,D$PASS,D$DPFL,D$CLEV,D$CLFL, 

1 D$USER,D$ACCT,D$PID 

DIMENSION D$OCDL(99) 

CHARACTER*255 D$HOS 

CHARACTER*18 D$PASS 

CHARACTER*12 D$USER,D$ACCT,D$PID 

CHARACTER*80 D$FILE 

CHARACTER*4 D$DEAL 

CHARACTER*2 D$DLEV,D$FIL,D$DPFL 

CHARACTER*1 D$DHFL 

INTEGER D$OCDL 

EQUIVALENCE (D$DHOS,D$DEAL) 

EQUIVALENCE (D$OCLD(1),D$DHOS) 

* 

* 

* 

D$LOHD='HOST1' 

D$LOUD='USER1' 

D$LOPW='PASS1' 

* 

* 

* 

CALL LOG$D (D$PCST,D$LOG) 

Figure 2-2. Referencing Information Packets through Subroutine Calls 

Subroutine calls are your program’s means of making requests to TAS. The format is: 

 

where: 

subroutine 

Is the 1- to 6-character name of the TAS subroutine requested by your application 

program. Specify according to FORTRAN programming syntax. 

2-10 3787 3247-111


argument 

Is the data item of the common block or declaration statement. 

The information packets are constructed so that the argument name that you use is the 

name of the common block, with a C for the common block replacing the D for the 

information packet. 

Subroutine call statements reference information packets or buffer areas contained in your 

program. (See Table 3-1 and Table 4-1.) The information packets consist of control 

information and data needed for file transfer and mail transfer applications. The buffer 

areas are used to pass data between TAS and your program. 

After processing a subroutine call, TAS returns both a general and a detailed status code. 

The general status code (class code), gives a classification value. The detailed status code 

gives an expanded description of the error that occurred. Table A-1 explains both of these 

status codes returned by TAS. 

3787 3247-111 2-11


2.3.2. INCLUDE Statements 

Use the INCLUDE statement in your program whenever you want to issue a subroutine 

call. The expansion in your program ensures the correct order of the operands in the call. 

The format for an INCLUDE statement is: 

 

where: 

file-name 

Is the name of the file to be searched for the procedure. 

procedure-name 

Is the 1- to 12-character name of the FORTRAN procedure created by the Procedure 

Definition Processor (PDP). Use the character set for FORTRAN symbolic names. For 

details on the Procedure Definition Processor, see the PDP Programming Reference 

Manual. 

LIST 

Lists the included statements whenever a subroutine call or information packet is 

coded in your application program. 

This is an example of a INCLUDE statement used to produce a TAS subroutine call with its 

information packets referenced: 

 

This produces: 

 

 

ZDDDDDDDDDD? ZDDDDDDDDDDDDDDDDDDDDDDDD? 

 

 

@DDDDDDDDDDDDDDY @DDDDDDDDDDDDDDY 

 

 

 

 

 

 

 

 

 

2-12 3787 3247-111


2.3.3. Initialization Packets 

The TAS packets contain several fields that are optional for a function. An example is the 

D$ACT1 field in the Transfer packet. TAS ignores these fields if you set them to their 

initialized values (usually spaces or zeros) prior to issuing the function call. You do this by 

either of the following: 

$ Setting each field to it’s initialized value on a field-by-field basis 

$ Using a TAS supplied subroutine to initialize the entire packet and then resetting any 

specific fields to the desired values. Use INCLUDE statements to incorporate these 

subroutines from the TAS copy library, SYS$LIB$*TAS-3. See Appendix E for a list of 

these subroutines. 

For example, to initialize the TRANSFER packet, use the following statements: 

 

 

 

 

 

3787 3247-111 2-13

Section 3 

File Transfer Applications 

3.1. Using TAS Functions, Parameter Packets, and 

Sessions 

This subsection discusses the following: 

$ Using parameter packets for TAS functions 

$ Opening a session with a remote host 

3.1.1. Using Parameter Packets for TAS Functions 

You can use FORTRAN INCLUDE statements or code your own FORTRAN subroutine 

calls to issue TAS file transfer commands from your FORTRAN program. You can direct 

these commands to the same host or to any remote host defined in the TAS network. 

When you use a FORTRAN INCLUDE statement, the associated subroutine call referencing 

the required information packets replaces the INCLUDE statement when the program is 

compiled. 

You can code the subroutine call yourself, but you must supply the information packet 

names in the correct sequential order shown in Table 3-1. See 2.2 and 2.3 for a discussion 

about using subroutine calls, information packets, and INCLUDE statements. 

Notes: 

1. All the packets contain an EQUIVALENCE statement (D$OCxx) that allows you to 

snap out the packet in octal format for use in debugging. 

2. The format of the D$PCST packet is described in 3.2and then referenced throughout 

this section. 

The subsections which follow describe the usage of each INCLUDE statement with its 

associated information packet. Only those fields that are used for that particular statement 

are discussed in detail. 

To obtain more detailed information on file transfer commands, see the TAS File Transfer 

User Guide. 

3787 3247-111 3-1

Using TAS Functions, Parameter Packets, and Sessions 

Table 3-1 lists the FORTRAN INCLUDE statements, FORTRAN subroutine calls, and 

information packets for file transfer application programs. 

Table 3-1. File Transfer Information Packets Referenced by INCLUDE Statements and 

Subroutine Calls 

TAS Function INCLUDE Statement Subroutine Call Information Packets 

Reserve storage on remote 

non-OS2200 host for the file to be 

transferred. 

Change current directory to its parent 

directory on a remote non-OS 2200 

host 

Change work directory on a remote 

non-OS 2200 host 

Delete a file from a remote non-OS 

2200 host 

INCLUDE LIBFILE. 

DDN$ALLO 


DDN$CDUP 


DDN$CWD 


DDN$DEALLOC 

Deregister a file for event notification INCLUDE LIBFILE. 

DDN$DEREG 

Transfer a file to a local host during a 

session 

Transfer a file to a remote host during 

a session 


DDN$FGET 


DDN$FPUT 

Establish a session with a remote host INCLUDE LIBFILE. 

DDN$LOGIN 

Create a directory on a remote 

non-OS2200 host 

Return name of current directory on a 

remote non-OS2200 host 


DDN$MKD 


DDN$PWD 

End a session with a remote host INCLUDE LIBFILE. 

DDN$QUIT 

Register a file for event notification INCLUDE LIBFILE. 

DDN$REGISTER 

Renameafileonaremote 


Resume a file transfer halted at a 

checkpoint in a checkpoint file 

Delete a directory on a remote 



DDN$RENAME 


DDN$RESUME 


DDN$RMD 

ALLO$D D$PCST D$DIR 

CDUP$D D$PCST D$DIR 

CWD$D D$PCST D$DIR 

DEAL$D D$PCST D$DEAL 

DREG$D D$PCST D$DREG 

FGET$D D$PCST D$XFER 

FPUT$D D$PCST D$XFER 

LOG$D D$PCST D$LOG 

MKD$D D$PCST D$DIR 

PWD$D D$PCST D$DIR 

QUIT$D D$PCST 

REG$D D$PCST D$REG 

RENM$D D$PCST D$RENM 

RESU$D D$PCST D$RESU 

RMD$D D$PCST D$DIR 

continued 

3-2 3787 3247-111


Table 3-1. File Transfer Information Packets Referenced by INCLUDE Statements and 

Subroutine Calls (cont.) 

TAS Function INCLUDE Statement Subroutine Call Information Packets 

Obtain information about a file transfer INCLUDE LIBFILE. 

DDN$SITE 

Obtain file transfer status for files with 

event notification set 

Transfer a file or element between 

hosts in the network 


DDN$STATUS 


DDN$TRANSFER 

3.1.2. Opening a Session with a Remote Host 

SITE$D D$PCST D$SITE 

FSTA$D D$PCST D$STAT 

XFER$D D$PCST D$XFER 

You can open a session between the local host and a remote host, and the session remains 

open after it is established. This allows the execution of several FTP commands between 

the hosts during that session. 

The LOGIN command LOG$D establishes a session with a remote host. When the session 

is open, you can execute FGET$D, FPUT$D, and other commands without providing a 

remote host name. However, the following commands do not need the LOGIN command to 

establish a session if they supply a remote host-id: 

 

 

 

 

 

3787 3247-111 3-3


When you execute one of these commands, the action TAS takes is determined by the 

presence of a host-id field in a parameter packet, and its value that you set: 

$ If a session is already open and: 

v The parameter packet does not have a host-id field: 

The current session remains open. 

v The host-id field in the parameter packet is set to spaces: 

The current session remains open. 

v The host-id field in the parameter packet is set to a remote host-id value: 

The current open session is closed and a new session is opened. This occurs even 

if the current and new sessions are opened to the same host. 

$ If a session is not open and: 

v The parameter packet does not have a host-id field: 

A session is not opened. Use the LOGIN command first to open a session before 

using other commands. 

v The host-id field in the parameter packet is set to a remote host-id value: 

A new session is opened to the remote host. 

Note: Closing the current open session and opening a new session involves a large 

amount of overhead processing. You incur this overhead even if you specify in 

a parameter packet a host-id that is the same as the remote host in the current 

open session. 

3.1.3. Closing a Session with a Remote Host 

You close a session with a remote host by either: 

$ Opening a new session with the same or another remote host (see Opening a Session 

with a Remote Host) 

$ Using the DDN$QUIT command 

Use the DDN$QUIT command to close the last session before terminating your 

program. Otherwise, the program terminates abnormally with a dump. 

3-4 3787 3247-111

Allocating File Space on Remote Hosts (DDN$ALLO) 

3.2. Allocating File Space on Remote Hosts 

(DDN$ALLO) 

Function 

Use DDN$ALLO to allocate file space on a remote non-OS 2200 host before you transfer 

the file. 

The subroutine call uses as parameters the D$PCST (Status) and D$DIR (Directory) 

information packets. 

TAS returns statistical information to fields in the D$PCST packet at the succussful 

completion of the FGET$D ,FPUT$D, and XFER$D function calls. 

Format 

 

or 

 

D$PCST (Status) Packet 

 

 

 

 

 

 

 

 

 

 

 

Field definitions returned by TAS: 

Field Definition 

D$PCID Packet-id. TAS places ’DDN$’ in this field after a successful call and places an 

error code in the D$PCEF field after an unsuccessful call. 

Table A-5 lists the error codes. 

D$PCCL Class code. TAS returns a general classification of status. 

See the tables in Appendix A. 

D$OK = 1 

3787 3247-111 3-5 

continued


continued 


D$PCDT Detailed status code. TAS returns a code to identify the specific status or 

error encountered. 


D$PCML Message insert. TAS returns text inserts corresponding to the errors 

detected. 


D$TIME Total transfer time. TAS returns the number of seconds between the initial 

data transfer and the completed data transfer. 

D$BYTE Bytes transferred. TAS returns the number of bytes of data transferred. 

D$AVG Average transfer time. TAS returns the average number of bytes transferred 

per second. 

D$DIR (Directory) Packet 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Field definitions set by user: 


D$DIHD Host-id. Optional. Host name with which to open the session. Use the 

characters 0-9, A-Z, dash, and period. Required if you are not currently logged 

in to the remote host where the file will be located. Do not specify a value if you 

are currently logged in to this remote host. 

D$DIF1 Ignored. 

D$DINM Ignored. 

D$DIUD User-id. Optional. User-id on the remote system. 

continued 

3-6 3787 3247-111

continued 



D$DIPW Password. Optional. Password on the remote system. 


D$DIAC Account number. Optional. Account number on the remote system. 

D$DIBY Bytes. Required. The number of bytes of storage to reserve. 

D$DIRE Records. Optional. The number of records of storage to reserve. 

Example 

Procedure Typical FORTRAN Statements 

1. Set remote host-id. D$DIHD=’HOST-SYS1’ 

2. Set remote file name. D$DIF1=’YOUR*PROG’ 

3. Set remote password. D$DIPW=’JOE’ 

4. Set remote user-id. D$DIUD=’DDNJOE’ 

5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$ALLO 

3787 3247-111 3-7

Changing to Parent Directory on Remote Hosts (DDN$CDUP) 

3.3. Changing to Parent Directory on Remote Hosts 

(DDN$CDUP) 

Function 

Use DDN$CDUP to change from the current directory to the parent of the current 

directory on a remote non-OS 2200 host. 



Format 

 

or 

 


See 3.2 for a description of the D$PCST fields. 


 

 

 

 

 

 

 

 

 

 

 

 

 

 





in to the remote host where the directory is located. Do not specify a value if 

you are currently logged in to this remote host. 


D$DINM Ignored. 

continued 

3-8 3787 3247-111

continued 

Changing to Parent Directory on Remote Hosts (DDN$CDUP) 






D$DIBY Ignored. 

D$DIRE Ignored. 

Example 




3. Set remote user-id. D$DIUD=’JOEDDN’ 

4. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$CDUP 

3787 3247-111 3-9

Changing Work Directory on Remote Hosts (DDN$CWD) 

3.4. Changing Work Directory on Remote Hosts 

(DDN$CWD) 

Function 

Use DDN$CWD to change the user’s current directory on a remote non-OS 2200 host.The 

subroutine call uses as parameters the D$PCST (Status) and D$DIR (Directory) 


Format 

 

or 

 




 

 

 

 

 

 

 

 

 

 

 

 

 

 








D$DINM Directory name. Required. Name of the target directory. 


continued 

3-10 3787 3247-111

continued 

Changing Work Directory on Remote Hosts (DDN$CWD) 







Example 



2. Set directory name. D$DINM=’USR/JOE/TEST’ 



5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$CDUP 

3787 3247-111 3-11

Deleting Files on Hosts (DDN$DEALLOC) 

3.5. Deleting Files on Hosts (DDN$DEALLOC) 

Function 

Use DDN$DEALLOC to delete files on remote hosts or on the local host. 

The subroutine call uses as parameters the D$PCST (Status) and D$DEAL (Deallocate) 


Format 

 

or 

 



D$DEAL (Deallocate) Packet 

 

 

 

 

 

 

 

 

 

 

 

 

 



D$DHOS Delete host-id. Required if the file is on a remote host and the user is 

not currently logged in to this remote host. Specify the host-id or logical 

host name of the file being deleted. Do not specify a value if you are currently 

logged in to the remote host. (See Appendix B.) 

D$FILE Delete file name. Required. Specify the fully qualified name of the file being 

deleted. 

D$PASS Delete password. Optional. Specify the password for the user on the system 

where the file is being deleted. * 

continued 

3-12 3787 3247-111

continued 


Deleting Files on Hosts (DDN$DEALLOC) 

D$CLEV Clearance level. Optional. Specify a two-numeric character clearance level. 

The default clearance level is determined by the user-id registration with the 

Exec. * 

D$USER Delete user-id. Optional. Specify the user-id for the user on the system 


D$ACCT Delete account number. Optional. Specify the account number for the user 

on the system where the file is being deleted. * 

D$PID Delete project-id. Optional. Specify the project-id for the user on the system 


*May be required if the file is on the local host and has read/write keys. 

Example 


1. Set remote host-id. D$DHOS=’HOST-SYS1’ 

2. Set remote file name. D$FILE=’USER/JOE/TEST’ 

3. Set remote password. D$PASS=’JOE’ 

4. Set remote user-id. D$USER=’JOEDDN’ 

5. Set remote acct. no. D$ACCT=’123456’ 

6. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$DEALLOC 

3787 3247-111 3-13

Deregistering a File for Event Notification (DDN$DEREG) 

3.6. Deregistering a File for Event Notification 

(DDN$DEREG) 

Function 

Use DDN$DEREG to deregister a file for event notification. When a file is deregistered, its 

associated runstream is no longer started when the file arrives at its destination host. 

See Appendix F for more information on using the Deregister command. 

The subroutine call uses as parameters the D$PCST (Status) and D$DREG (Deregister) 


Format 

 

or 

 



D$DREG (Deregister) Packet 

 

 

 

 

 

 

 

 

 

 

If the deregister function attempts to deregister the last file registered with an 

application-id and there is saved status information for that application-id, then this file 

will not be deregistered until the status information has been retrieved through the 

DDN$STATUS function. 

If D$ALL = 1 and D$DRGF is set to spaces, then all files associated with the application-id 

will be deregistered regardless of any saved status information. 

3-14 3787 3247-111


Deregistering a File for Event Notification (DDN$DEREG) 


D$DAPP Application id. Required. Specify the owner of the event notification record. 

Use 1 to 12 alphanumeric characters. 

D$DRGF File name. Required unless you want to deregister all the files registered to 

the specified application-id. Specify the name of the file you want to deregister. 

D$DWIL Wild-card character. Optional. 

Specify a wild-card character to be used to deregister a file. 

D$ALL Deregister all files. Optional. Specify whether or not to deregister one file or 

a group of files. 

Example 

0 = Deregister the file specified in D$DRGF. 

1 = If D$DRGF = spaces, then deregister all files associated with the specified 

application-id. 

If DDN-DREG-FILENAME = a file name, then deregister all files associated with 

the specified application-id that also match D$DRGF. 


1. Set application. D$DAPP = ’DMO’ 

2. Set filename. D$DFIL = ’FILENAME’ 

3. No wild character. D$DWIL = ’ ’ 

4. Do not deregister all. D$ALL = 0 

5. Issue call statement. CALL DREG$D(D$PCST,D$DREG) 

3787 3247-111 3-15

Remote to Local Transfer in a Session (DDN$FGET) 

3.7. Remote to Local Transfer in a Session 

(DDN$FGET) 

Function 

Use DDN$FGET to transfer a file from a remote host to a local host after a session has 

been established between them. 

The subroutine call uses as parameters the D$PCST (Status) and D$XFER (Transfer) 


Format 

 

or 

 



D$XFER (Transfer) Packet 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3-16 3787 3247-111




D$FRID Ignored. 

D$TOID Ignored. 

D$TFIL To (destination) file name. Required. Specify the fully qualified name of the 

file (or file and element) to receive the transfer. 

D$FFIL From (source) file name. Required. Specify the fully qualified name of the 

file (or file and element) to be sent. 

D$PAS1 Ignored. 

D$CLV1 Ignored. 

D$PAS2 Password-2. Required for files with read/write keys on the local host. 

Specify a 1- to 18-alphanumeric character password for the destination host. 

D$CLV2 Clearance level-2. Required. Required if the file on the local host has 

read/write keys and your user-id is configured to ask for a clearance level. 

Enter a number between 0 and 63 within the range of values allowed for the 

specified user-id. The default clearance level is determined by your user-id’s 

registration with the Exec. 

D$UID1 Ignored. 

D$UID2 User-id-2. Required for files with read/write keys on the local host. 

Specify a 1- to 12-alphanumeric character user identifier for the destination 

host. 

D$ACT1 Ignored. 

D$ACT2 Account number-2. Required when D$UID2 is configured to ask for the 

account number and the file on the local host has read/write keys. 

Specify a 1- to 12-character account number for the destination host. 

D$PID1 Ignored. 

D$PID2 Project-id-2. Required when D$UID2 is configured to ask for the project 

identifier and the file on the local host has read/write keys. Specify a 1to 

18-character project identifier for the destination host. 

D$POSN Position. Required. Specify the placement of the file to be transferred. 

Replace = 0 

Add = 1 

3787 3247-111 3-17 

continued


continued 


D$TRAN Translate. Required. Specify the type of data in the sending file. 

ASCII = 0 

EBCDIC = 1 

Transparent = 2 

L36 = 3 

D$XMOD Transfer mode. Required. Specify the mode of transfer. 

Stream = 0 

Compressed = 1 

Block = 2 (Block means sent as a series of blocks.) 

D$STRU Structure. Required. Specify how data in the sending host is to be sent. 

File (no record structure)= 0 

Record (sequential records) = 2 

D$XTYP Transfer type. Required. Specify the type of file or element being sent. 

Symbolic = 0 

All (entire file) = 1 

Relocatable = 2 

Absolute = 3 

Omnibus = 4 

Source = 5 

SDF = 6 

Unknown = 7 

IOW = 8 

D$RSIZ Maximum record size. Optional. Specify the size (in characters) of the 

longest record in D$TFIL. 

The largest value (and the default) permitted is 7168. 

D$CHFN Optional. Specify the fully-qualified name of the checkpoint file. An element 

name cannot be specified. 

D$CMF Optional. Specify the number of tracks to be transferred before a checkpoint 

marker is written in the checkpoint file. If this field is not specified, but a 

checkpoint file name is specified in DDN-CHKPT-FILE-NAME, 250 tracks are 

transferred before a marker is written. 

D$STIF Site information. Optional. Specifies that the server needs additional data 

from the user side that it cannot derive from the FTP protocol commands. 

3-18 3787 3247-111

Example 



1. Set the ’from’ file name. D$FFIL=’MY*FILE’ 

2. Set the ’to’ file name. D$TFIL=’YOUR*FILE’ 

3. Set position to replace. D$POSN=0 

4. Set type of data to transparent. D$TRAN=2 

5. Set transfer mode to stream. D$XMOD=0 

6. Set structure to file. D$STRU=0 

7. Set to entire file. D$XTYP=1 

8. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$FGET 

3787 3247-111 3-19

Local to Remote Transfer in a Session (DDN$FPUT) 

3.8. Local to Remote Transfer in a Session 

(DDN$FPUT) 

Function 

Use DDN$FPUT to transfer a file from a local host to a remote host after a session has 

been established between the two hosts. 



Format 

 

or 

 




 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3-20 3787 3247-111




D$FRID Ignored. 

D$TOID Ignored. 





D$PAS1 Required for files with read/write keys on the local host. Specify a 1- to 

18-alphanumeric character password for the source host. 

D$CLV1 Clearance-level-1. Required for files with read/write keys on the local 

host. Enter a number between 0 and 63 within the range of values for the 

specified user-id. The default clearance level is determined by your user-id’s 

registration with the Exec. 

D$PAS2 Ignored. 

D$CLV2 Ignored. 

D$UID1 User-id-1. Required for files with read/write keys on the local host. 

Specify a 1- to 12-character user identifier. 

D$UID2 Ignored. 

D$ACT1 Account-number-1. Required when D$UID1 is configured to solicit 

account numbers and the file on the local host has read/write keys. 

Specify a 1- to 12-character account number for the source host. 

D$ACT2 Ignored. 

D$PID1 Project-id-1. Required when D$UID1 is configured to ask for the project 

identifier and the file on the local host has read/write keys. Specify a 1to 

18-character project identifier for the source host. 

D$PID2 Ignored. 


Replace = 0 

Add = 1 


ASCII = 0 

EBCDIC = 1 


L36 = 3 

3787 3247-111 3-21 

continued


continued 



Stream = 0 







Symbolic = 0 



Absolute = 3 

Omnibus = 4 

Source = 5 

SDF = 6 

Unknown = 7 

IOW = 8 


longest record in D$TFIL. The largest value permitted is 7168 characters. 

Default value is 7168 characters. 

D$CHFN Checkpoint filename. Optional. Specify the fully-qualified name of the 

checkpoint file. An element name cannot be specified. 

You must make an entry in this field if you wish to use Resume. 

D$CMF Checkpoint marker frequency. Optional. Specify the number of tracks to 

be transferred before a checkpoint marker is written to the checkpoint file. 

If this field is not specified, but a checkpoint filename is specified in D$CHFN, 

250 tracks are transferred before a marker is written. 

D$STIF Site information. Optional. Specifies the additional FTP protocol that the 

server needs from the user side. 

3-22 3787 3247-111

Example 





3. Set to replace. D$POSN=0 





8. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$FPUT 

3787 3247-111 3-23

Establishing a Session with a Remote Host (DDN$LOGIN) 

3.9. Establishing a Session with a Remote Host 

(DDN$LOGIN) 

Function 

Use DDN$LOGIN to establish a session between a local and a remote host. 

The subroutine call uses as parameters the D$PCST (Status) and D$LOG (Login) 


Format 

 

or 

 



D$LOG (Login) Packet 

 

 

 

 

 

 

 

 

 

 

 



D$LOHD Remote host. Required. Specify the id of the host with which the session is to 

be opened. 

Legal characters are 0-9, A-Z, - (dash), and . (period). 

D$LOUD User-id of remote system. Optional. Specify the user-id of the system to 

which you wish to attach. 

D$LOPW Logon Password. Optional, but usually required by the remote system. 

Specify the password which allows access to the remote system. 

continued 

3-24 3787 3247-111

continued 

Establishing a Session with a Remote Host (DDN$LOGIN) 


D$LOCL Logon clearance level. Optional. Specify the clearance level when expected 

by the remote host. 

Specify a number between 0 and 63. 

D$LOAC Logon account number. Optional. Specify the account number for the user 

on the remote system. 

D$LOPD Logon project id. Optional. Specify the project identifier on the remote 

system. 

Example 


1. Set the login host-id. D$LOHD=’HOST-1’ 

2. Set the login user-id. D$LOUD=’JOE’ 

3. Set the login password. D$LOPW=’YOURS’ 

4. Set the login account. D$LOAC=’123456’ 

5. Set the login project-id. D$LOPD=’DDNA’ 

6. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$LOGIN 

3787 3247-111 3-25

Making a Directory on Remote Hosts (DDN$MKD) 

3.10. Making a Directory on Remote Hosts 

(DDN$MKD) 

Function 

Use DDN$MKD to create a directory or subdirectory on a remote non-OS 2200 host. 



Format 

 

or 

 




 

 

 

 

 

 

 

 

 

 

 

 

 

 





in to the remote host where you will create the directory. Do not specify a value 

if you are currently logged in to the remote host. 


D$DINM Directory name. Required. Name of the directory you are going to create. 


continued 

3-26 3787 3247-111

continued 

Making a Directory on Remote Hosts (DDN$MKD) 







Example 






5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$MKD 

3787 3247-111 3-27

Returning a Directory Name on Remote Hosts (DDN$PWD) 

3.11. Returning a Directory Name on Remote 

Hosts (DDN$PWD) 

Function 

Use DDN$PWD to return the name of the current directory on a remote non-OS 2200 host. 

TAS returns the value of the current directory in the D$DINM field of the Directory packet. 



Format 

 

or 

 




 

 

 

 

 

 

 

 

 

 

 

 

 

 









continued 

3-28 3787 3247-111

continued 

Returning a Directory Name on Remote Hosts (DDN$PWD) 









D$DINM Directory name. TAS returns the name of the current directory in this field. 

Example 





4. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$PWD 

3787 3247-111 3-29

Ending a Session (DDN$QUIT) 

3.12. Ending a Session (DDN$QUIT) 

Function 

Use DDN$QUIT to end a session between a local and a remote host. A DDN$QUIT is not 

needed following a DDN$TRANSFER. 

Always use DDN$QUIT to end the last session before terminating your program. 

Otherwise, the program terminates abnormally with a dump. 

This subroutine call uses the D$PCST (Status) information packet as a parameter. 

Format 

 

or 

 



Example 

Procedure Typical FORTRAN Statement 

1. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$QUIT 

3-30 3787 3247-111

Registering Files for Event Notification (DDN$REGISTER) 

3.13. Registering Files for Event Notification 

(DDN$REGISTER) 

Function 

Use DDN$REGISTER to register a file for event notification. If a file is registered, you are 

notified when that file is received at its new location. 

See Appendix G for more information on using the Register command. 

The subroutine call uses as parameters the D$PCST (Status) and D$REG (Register) 


Format 

 

or 

 



D$REG (Register) Packet 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 3-31




D$APPL Application id. Required. Specify the owner of the event notification record. 

The application id is used by TAS to associate registered filenames with an 

owner (to be used when deregistering all filenames). You should try to make 

this unique and use it each time you register a filename. 

Use 1-12 alphanumeric characters. 

D$AFIL File name. Required. Specify the name of the file to be registered for 

notification. The name must include a qualifier and filename. 

D$RUNA Runstream. Required. Supply the name of the run to be started when the 

registered file is received. It is this runstream that returns the information that 

the registered file has been received. The name must include a qualifier and 

filename. 

It does this by either: 

a. Starting an application program 

b. Sending a terminal message 

D$OPTN Run options. Optional. Supply the run options to be used with the run stream. 

Validoptionsare:B,C,E-L,M,N,P,R-U,andW-Z. 

The X option is supported if the user has sufficient privileges. These options are 

discussed in the OS 1100 Exec System Software Administration and Support 

Reference Manual. 

D$WILD Wild character. Optional. Supply the wild card character to be used in 

selecting a file or files for registration. This option is generally used to register 

a family of files. Use only one character. 

The choices are: a - z, A - Z, $ (dollar sign), / (slash), and 0 - 9. 

D$ONET Register one time. Optional. Specify whether or not a file is to be registered: 

1 = File is to be registered and then deregistered 

0 = File is to remain registered 

D$SAVE Save status. Optional. Specify the save status: 

1 = Save the file name and status for access by a Status Request command 

0 = Do not save file name and status 

D$CTRL Control value. Optional. Specify an octal value for the setc parameter on the 

@START ECL statement for the event notification runstream. Use an octal value 

with a leading zero and place it in the middle third (T2) of the condition word. 

Use only the digits 0 through 7. 

You can test this value with ECL statements in your runstreams. 

continued 

3-32 3787 3247-111

continued 



D$ADDS Specify how to execute the runstream: 

0 = using an @START 

1 = using an @ADD 

Example 


1. Set application. D$APPL = ’DMO’ 

2. Set file. D$AFIL = ’FILENAME’ 

3. Set runstream. D$RUNA = ’DMO*RUNS.MSG’ 

4. Set control value. D$CTRL = ’010’ 

5. No start options. D$OPTN = ’ ’ 

6. No wild character. D$WILD = ’ ’ 

7. No one time register. D$ONET = 0 

8. Set save status. D$SAVE = 1 

9. Issue call statement. CALL REG$D(D$PCST,D$REG) 

3787 3247-111 3-33

Renaming a File (DDN$RENAME) 

3.14. Renaming a File (DDN$RENAME) 

Function 

Use DDN$RENAME to rename a file on a local host. 

The subroutine call uses as parameters the D$PCST (Status) and D$RENM (Rename) 


Format 

 

or 

 



D$RENM (Rename) Packet 

 

 

 

 

 

 

 

 

 

 

 

 

 



D$RMID Rename-host-id. Required if the file is on a remote host and the user is 

not currently logged-in to the remote host. Specify the host-id of the 

remote host that contains the file being renamed. 

D$RMFM Rename from file name. Required. Specify the current name of the file 

being renamed. 

D$RMTO Rename to file name. Required. Specify the new name of the file. 

D$RMPS Rename password. Optional. Specify the password for the user on the 

system where the file is being renamed. 

continued 

3-34 3787 3247-111

continued 


Renaming a File (DDN$RENAME) 

D$RMUR Rename user-id. Optional. Specify the user-id for the user on the system 

where the file is being renamed. 

D$RMAC Rename account number. Optional. Specify the account number for the 

user on the system where the file is being renamed. 

D$RMPJ Rename project-id. Optional. Specify the project-id for the user on the 

system where the file is being renamed. 

Example 


1. Set remote host-id. D$RMID=’HOST-SYS1’ 

2. Set current file name. D$RMFM=’OLD*PROG’ 

3. Set new file name. D$RWTO=’NEW*PROG’ 

4. Set password. D$RMPS=’JAMES’ 

5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$RENAME 

3787 3247-111 3-35

Resuming a Checkpoint File Transfer (DDN$RESUME) 

3.15. Resuming a Checkpoint File Transfer 

(DDN$RESUME) 

Function 

Use DDN$RESUME to recover a file transfer that terminated abnormally at a checkpoint 

marker in a checkpoint file, provided you specified a checkpoint file name in the 

DDN$TRANSFER INCLUDE statement. 

The subroutine call uses as parameters the D$PCST (Status) and D$RESU (Resume) 


Format 

 

or 

 



D$RESU (Resume) Packet 

 

 

 

 

 

 

 

 

 

 

 



D$RFNM Resume file name. Required. Specify the fully qualified name of the 

checkpoint file as defined in the D$CHFN field of D$XFER. 

D$RMRK Resume file marker. Optional. Specify the file marker at which the file 

transfer is to resume. 

If this field is not specified, the file transfer is resumed at the last marker in the 

checkpoint file. 

continued 

3-36 3787 3247-111

continued 

Resuming a Checkpoint File Transfer (DDN$RESUME) 


D$PWS1 Resume password 1. Required when the file transfer being resumed 

required D$PAS1. Specify the same password as specified in the D$PAS1 

field of D$XFER. 

D$RCL1 Resume clearance level 1. Required when the file transfer being 

resumed required a clearance level. Specify a two-character clearance 

level. 

This clearance level is passed to the remote host, whether or not that host is an 

OS 2200. 

(The default is determined by the user-id’s registration with the Exec.) 

D$PWS2 Resume password 2. Required when the file transfer being resumed 

required D$PAS2. Specify the same password as specified in the D$PAS2 

field of D$XFER. 

D$RCL2 Resume clearance level 2. Required when the file transfer being 

resumed required a clearance level. Specify a two-number clearance level. 

Example 

If a clearance level is specified, it is passed to the remote host, whether or not 

that host is an OS 2200. 



1. Set file name. D$RFNM=’MY*CHECKFILE’ 

2. Set resume password 1. D$PWS1=’JOE’ 

3. Set resume password 2. D$PWS2=’RALPH’ 

4. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$RESUME 

3787 3247-111 3-37

Removing a Directory on Remote Hosts (DDN$RMD) 

3.16. Removing a Directory on Remote Hosts 

(DDN$RMD) 

Function 

Use DDN$RMD to delete a directory on a remote non-OS 2200 host. 



Format 

 

or 

 




 

 

 

 

 

 

 

 

 

 

 

 

 

 








D$DINM Directory name. Required. Name of the directory you are going to delete. 


continued 

3-38 3787 3247-111

continued 

Removing a Directory on Remote Hosts (DDN$RMD) 







Example 






5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$RMD 

3787 3247-111 3-39

Sending Site-Specific Information about a File Transfer (DDN$SITE) 

3.17. Sending Site-Specific Information about a 

File Transfer (DDN$SITE) 

Function 

Use DDN$SITE to send FTP protocol that TAS does not provide within subroutines. The 

information in D$STIN is sent to the remote host exactly as it appears. You must also 

include the FPT protocol itself. This functions like the FTP QUOTE command. 

The subroutine call uses as parameters the D$PCST (Status) and D$SITE (Status Request) 


Format 

 

or 

 



D$SITE (Status Request) Packet 

 

 

 

 

 

 

 

 

 

 

 

 



D$STID Site host-id. Required if not already logged in. The id of the remote host 

from which the information is sent. 

D$STIN Site information. Required. Specifies additional FTP protocol to be sent to 

theremotehost. 

D$STPS Site password. Optional. Specify the password used for site information. 

D$STUR Site user-id. Optional. Specify the user-id used for site information. 

continued 

3-40 3787 3247-111

Sending Site-Specific Information about a File Transfer (DDN$SITE) 

continued 


D$STAC Site account. Optional. Specify the account used for site information. 

D$STPJ Site project-id. Optional. Specify the project-id used for site information. 

Example 


1. Set host-id. D$STID=’HOST-SYS1’ 

2. Set information requested. D$STIN=’LIST PROTOCOLS 

SUPPORTED’ 

3. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$SITE 

3787 3247-111 3-41

Getting Event Notification Status Information (DDN$STATUS) 

3.18. Getting Event Notification Status Information 

(DDN$STATUS) 

Function 

Use DDN$STATUS to obtain TAS file transfer status for applications which were 

registered for event notification with a Save status (D$SAVE). 

The subroutine call uses as parameters the D$PCST (Status) and D$STAT (Status Event 

Notification) information packets. 

Format 

 

or 

 



D$STAT (Status Request) Packet 

 

 

 

 

 

 

 

 

 



D$SAPP Application host-id. Required. Specify the id of the application about which 

status is desired. 

D$SDNT Deregister entry. Optional. Specify: 

0 = Do not deregister this application. 

1 = Deregister this application. 

3-42 3787 3247-111

Getting Event Notification Status Information (DDN$STATUS) 



D$SFIL File name. TAS supplies the name of the file about which information was 

requested. 

D$FSTA File Status. TAS returns a file transfer status. 

Example 

01 = Transfer was successful 

19 = Exceeded storage 

21-27 = Transfer aborted 

all others = Local error 


1. Set application. D$SAPP=’DMO’ 

2. Deregister entry. D$SDNT=’0’ 

3787 3247-111 3-43

Transferring Files or Elements between Hosts (DDN$TRANSFER) 

3.19. Transferring Files or Elements between Hosts 

(DDN$TRANSFER) 

Function 

Use DDN$TRANSFER to transfer a file or element between hosts. 



Format 

 

or 

 




 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



D$FRID From host-id. Required if sending from a remote host. Specify the host-id 

or logical host name of the sending host. 

Do not specify the host-id when sending from the local host. 

(See Appendix B for host-naming conventions.) 

continued 

3-44 3787 3247-111

continued 



D$TOID To host-id. Required if sending to a remote host. Specify the host-id or 

logical host name of the receiving host. 

Do not specify the host-id when sending to the local host. 

(See Appendix B for host-naming conventions.) 





D$PAS1 Password-1. May be required for files on remote hosts or files with 

read/write keys on the local host. Specify a 1-to 18-alphanumeric character 

password. 

D$CLV1 Clearance-level-1. May be required for files on remote hosts or files 

with read/write keys on the local host. 

Enter a number between 0 and 63. 

The default user-id is determined by your user-id’s registration with the Exec. 

D$PAS2 Password-2. May be Required for files on remote hosts or files with 

read/write keys on the local host. Specify a 1- to 18-alphanumeric 

character password for the destination host. 

D$CLV2 Clearance-level-2. Required for files with read/write keys on the local 

host. Specify a number between 0 and 63. 

If a clearance level is specified, it is passed to the remote host, whether or not 

that host is an OS 2200. 


D$UID1 User-id-1. May be required for files with read/write keys on the local 

host or files on a remote host. Specify a 1- to 12-character user identifier for 

thesourcehost. 

D$UID2 User-id-2. Required for files with read/write keys on the local host or 

files on a remote host. Specify a 1- to 12-alphanumeric character user 

identifier for the destination host. 

D$ACT1 Account-number-1. May be required for files on remote hosts or when 

D$UID1 is configured to ask for the account number. Specify a 1- to 

12-character account number for the source host. 

D$ACT2 Account-number-2. May be required for files on remote hosts or when 

D$UID2 is configured to ask for the account number. Specify a 1- to 

12-character account number for the destination host. 

3787 3247-111 3-45


continued 


D$PID1 Project-id-1. May be required for files on remote hosts or when D$UID 

is configured to ask for the project identifier. Specify a 1- to 18-character 

project identifier for the destination host. 

D$PID2 Project-id-2. May be required for files on remote hosts or when D$UID 

is configured to ask for the project identifier. Specify a 1- to 18-character 

project identifier for the destination host. 


Replace = 0 

Add = 1 


ASCII = 0 

EBCDIC = 1 


L36 = 3 


Stream = 0 







Symbolic = 0 



Absolute = 3 

Omnibus = 4 

Source = 5 

SDF = 6 

Unknown = 7 

IOW = 8 


longest record in D$TFIL. The largest value permitted is 7168 characters. 

Default value is 7168 characters. 

D$CHFN Checkpoint file name. Optional. Specify the fully-qualified name of the 

checkpoint file. An element name cannot be specified. 

3-46 3787 3247-111

continued 



D$CMF Checkpoint marker frequency. Optional. Specify the number of tracks to 

be transferred before a checkpoint marker is written in the checkpoint file. 

If this field is not specified, but a file name is specified, 250 tracks are 

transferred before a marker is written. 

D$STIF Site information. Optional. Specifies the additional FTP protocol that the 

server needs from the user side. 

Example 


1. Set the ’from’ host-id. D$FRID=’HOST-SYS1’ 

2. Set the ’to’ host-id. D$TOID=’HOST-SYS2’ 



5. Set the ’from’ password. D$PAS1=’MINE’ 

6. Set the ’to’ password. D$PAS2=’YOURS’ 

7. Set the ’from’ user-id. D$UID1=’PAT’ 

8. Set the ’to’ user-id. D$UID2=’JOE’ 

9. Set the ’from’ account number. D$ACT1=’123456’ 

10. Set the ’to’ account number. D$ACT2=’789ABC’ 

11. Set the ’from’ project-id. D$PID1=’DDNA’ 

12. Set the ’to’ project-id. D$PID2=’DDNB’ 

13. Set to replace. D$POSN=0 





18. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$TRANSFER 

3787 3247-111 3-47

Designing a File Transfer Application 

3.20. Designing a File Transfer Application 

When designing a TAS file transfer application, you should lay out a block diagram of what 

you want to do. (See Figure 3-1.) 

Set Up Transfer 

Packet 

Perform Type of 

Transfer 

Figure 3-1. Typical TAS FORTRAN File Transfer Block Diagram 

Once you design the basic block diagram, you can create a flow diagram by filling in the 

blocks with FORTRAN statements (as shown in Figure 3-2) according to the requirements 

defined for each INCLUDE statement. 

In most cases, you can do this by taking the example given under each INCLUDE 

statement in 3.1 through 3.4 and placing it in the appropriate block. (Some changes from 

the example may be needed, depending upon your application.) 

Figure 3-2 shows a three-host transfer that moves an entire file from one remote host to 

another remote host. Note that in a three-way transfer; all three hosts must be OS 2200 

hosts. For simplicity, no error/status checking routines are shown. See the file transfer 

application program in Appendix C for a complete example. 

3-48 3787 3247-111

SET UP TRANSFER 

D$FRID='HOST-ID-SYS2' 

D$TOID='HOST-ID-SYS1' 

D$PAS1='PASS1' 

D$PAS2='PASS2' 

D$UID1='USER1' 

D$UID2='USER2' 

D$ACT1='111111111111' 

D$ACT2='222222222222' 

D$PID1='MYID' 

D$PID2='YOURID' 

TRANSFER ENTIRE FILE 

D$FFIL='MYID*FROMFILE1' 

D$TFIL='YOURID*TOFILE1' 

D$POSN=0 

D$TRAN=2 

D$SMOD=2 

D$STRU=0 

D$XTUP=1 

INCLUDE LIBFILE.DDN$TRANSFER 

IF (D$PCCL .NE. 1) THEN 

CALL DISPST 

END IF 

Designing a File Transfer Application 

Figure 3-2. Typical TAS FORTRAN File Transfer Flow Diagram 

3787 3247-111 3-49

Section 4 

Mail Applications 

4.1. Mail Commands 

To process mail commands, you can either: 

$ Use the FORTRAN modules which are supplied 

$ Code your own subroutine call(s) 

You can direct these commands to: 

$ Your local host 

$ Any remote host in the TAS network 

3787 3247-111 4-1

Mail Commands 

4.1.1. Basic Format 

You can use the subroutines supplied by TAS in two ways: 

$ You can code a FORTRAN INCLUDE statement followed by a subroutine call. This 

allows the required information packets to replace the INCLUDE statement when the 

program is compiled. 

Example: INCLUDE LIBFILE.DDN$CHECK 

$ You can call the subroutine directly. When you select this option you must name the 

information packets referenced. 

Example: call CHEK$D (D$PCST,D$MBUF,D$MAIL) 

4.1.2. Coding Your Own Subroutines 

You can code the subroutine call yourself, but you must then supply the information 

packet names in the sequence shown in Table 4-1. See 2.2 and 2.3 for a discussion on how 

to use subroutine calls, information packets, and INCLUDE statements. 

To obtain more detailed information on mail transfer commands, see the TAS Mail 

Processor User Guide. 

4.1.3. Statements Summarized 

Table 4-1 lists the FORTRAN INCLUDE statements, FORTRAN subroutine calls, and 

information packets for mail transfer application programs. 

Each include statement is listed in alphabetical order and discussed individually in the 

subsections which follow. 

4.1.4. Start with DDN$MAILBOX 

The first command you will want to use in your program is DDN$MAILBOX (see 4.8). 

This command creates the mailbox(es) you will need in order to use mail. After you have 

created mailboxes, you select other options for your program. 

4-2 3787 3247-111

Mail Commands 

Table 4-1. Transfer Packets Referenced by INCLUDE Statements and Subroutine Calls 

Function INCLUDE Statement Subroutine Information Packets 

Referenced by INCLUDE 

Statement/Subroutine Call 

Retrieve a list of 

incoming/outgoing mail 

Continue a mail operation 

with another buffer 

End a mailbox 

assignment 

Discontinue a mail 

operation 

Create, list, change, or 

delete lists of mailbox 

names 


DDN$CHECK 


DDN$CONTINUE 


DDN$DISCONN 


DDN$DISCONT 


DDN$DIST 

Getmailfromamailbox INCLUDE LIBFILE. 

DDN$GET 

Create, change, assign, 

or delete mailboxes 


DDN$MAILBOX 

Create outgoing mail INCLUDE LIBFILE. 

DDN$PREPARE 

Delete 

incoming/outgoing mail 

fromamailbox 


DDN$REMOVE 

Send mail to mailboxes INCLUDE LIBFILE. 

DDN$SENDMAIL 

Obtain a mailbox name 

for a given user 

Notes: 


DDN$VERIFY 

CHEK$D D$PCST D$MBUF D$MAIL 

CONT$D D$PCST D$MBUF D$MAIL 

DISC$D D$PCST 

DCNT$D D$PCST 

DIST$D D$PCST D$MBUF D$MAIL D$DIST 

D$ELST D$MLST 

GETM$D D$PCST D$MBUF D$MAIL 

MBOX$D D$PCST D$MAIL D$MBOX 

PREP$D D$PCST D$MBUF D$MAIL 

REMV$D D$PCST D$MAIL 

SENM$D D$PCST D$MBUF D$MAIL 

D$SEND D$ELST D$MLST 

D$DLST 

VRFY$D D$PCST D$VRFY 

1. The formats of the D$PCST and D$MAIL packets are the same for each INCLUDE 

statement/subroutine call. The field definitions for those packets only describe 

those fields used for that particular statement. 

2. For debugging ease, each packet contains an EQUIVALENCE statement (D$OCxx) 

that allows you to snap out the packet in octal format. 

3787 3247-111 4-3

Listing Incoming/Outgoing Mail Items (DDN$CHECK) 

4.2. Listing Incoming/Outgoing Mail Items 

(DDN$CHECK) 

Function 

Use a DDN$CHECK INCLUDE statement to retrieve a list of incoming or outgoing mail for 

your mailbox. 

The associated subroutine call references the D$PCST (Status) and D$MAIL (Mail) 

information packets. It also references the D$MBUF (Mail Buffer) storage area. 

Format 

 

or 

 


 

 

 

 

 

 

 

 

 


D$PCID Packet-id. ’DDN$’ is placed in this field after a successful call. An error code is 

placedin the D$PCEF field after an unsuccessful call. 

Table A-5 lists the error codes. 

D$PCCL Class code. Returns a general status code to classify the error status found. 


D$OK = 1 

D$PCDT Detailed status code. Identifies the specific status or error encountered. 


continued 

4-4 3787 3247-111

continued 


D$PCRF Status redefined. Redefines the status fields to allow a FORTRAN program to 

reference D$PCCL and D$PCDT as one field. This provides an easy way to test 

certain status conditions that the program may not consider to be errors. 

For example, instead of testing D$PCCL to equal 193 and D$PCDT to equal 

190, just check D$PCRF for PCMBEM. The class code for all of these fields is 

193. 

The following list equates the values in the field definitions with the detailed 

status codes in the tables in Appendix A: 

PCDUP: 50 Duplicate name 

PCMBOX: 100 Mailbox not found 

PCDMBX: 110 Duplicate mailbox 

PCBXAC: 130 Mailbox active 

PCMBEM: 190 Mailbox empty 

PCIDNF: 200 Identifier not found 

PCDUID: 220 Duplicate identifier 

PCLSNF: 260 List not found 

PCDULT: 290 Duplicate list 

PCNOMB: 370 No members 

PCRMID: 380 Remove identifier not found 

PCLSDE: 390 List deleted 

PCMBIU: 800 Mailbox in use 

PCUSAM: 945 User ambiguous 

PCUSNF: 950 User not found 

PCDBER: 1020 Database error 

D$PCML Message insert. Text corresponding to the errors detected. 


D$MBUF (Mail Buffer) Parameter 

This parameter references a storage area for a list of incoming or outgoing mail. You must 

declare this statement in your application program: 

 

The total buffer area must be less than or equal to 3300 characters (the largest message 

TAS can transfer). See 4.14 for additional information. 

3787 3247-111 4-5


D$MAIL (Mail) Packet 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


D$MTYP Type mail. Required. Indicates the type of mail. 

Incoming = 0 

Outgoing = 1 

D$BSIZ Buffer size. Required. Specify the maximum number of characters to be 

used in the mail buffer. 


This value must be a multiple of four and not greater than 3300. 

D$MTCI More to come indicator. Indicates there was incoming data remaining after 

the mail buffer was filled to capacity. 

If this indicator is set, the program must issue a DDN$CONTINUE or 

DDN$DISCONT INCLUDE statement. No other mail function can be issued until 

a DDN$DISCONT is issued. 

D$LNCT Line count. Indicates the number of lines received in the mail buffer. 

Example 


1. Check incoming mail. D$MTYP=0 

2. Set buffer size. D$BSIZ=800 

3. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$CHECK 

4-6 3787 3247-111

Additional Discussion 


The size of each line in the mail buffer after a DDN$CHECK INCLUDE statement is 80 

characters. When D$MTYP is specified as Incoming (0), the format of each line is as 

follows: 

Position Contents 

1-8 Mail identifier 

10-34 Subject 

36-55 Author 

57-64 Date received (mm/dd/yy) 

66-68 Number of pages 

70 Reply (Y or N) 

72-79 Date seen (mm/dd/yy) 

When D$MTYP is specified as Outgoing (1), the format of each line is as follows: 


1-8 Mail identifier 

10-34 Subject 

36-55 Author 

57-64 Date created (mm/dd/yy) 

66-68 Number of pages 

3787 3247-111 4-7

Continuing Mail Operation with Another Buffer (DDN$CONTINUE) 

4.3. Continuing Mail Operation with Another Buffer 

(DDN$CONTINUE) 

Function 

Use a DDN$CONTINUE statement when the buffer is not large enough to contain the data 

associated with a mail operation. This continues the mail operation by using the next 

buffer. 

This statement is only valid when used in conjunction with: 

$ Operations which pass information to TAS: 

v DDN$PREPARE with D$TLOC specified as Text in Memory 

v DDN$SENDMAIL with D$TLOC specified as Text in Memory 

$ Operations which receive information from TAS: 

v DDN$CHECK 

v DDN$DIST with D$MMOD specified as Display 

v DDN$GET with D$TLOC specified as In Memory 

To pass additional buffers (one at a time) 

Use DDN$CONTINUE with D$LBID specified as 1 (Not Last Buffer). 

To terminate this process, do either of the following: 

$ Specify 0 (Last Buffer) for D$LBID when you pass the last buffer. 

$ Issue DDN$DISCONT after you have passed the last buffer. 

To receive data in the mail buffer 

Check the D$MTCI indicator to see if there is more data to be returned after the buffer is 

filled. If the indicator is set, do either of the following: 

$ Issue DDN$CONTINUE to receive the data and check D$MTCI again to see if 

additional data remains (repeat this process as necessary). 

$ Issue DDN$DISCONT when you do not want additional data. 


information packets. It also references the D$MBUF (Message Buffer) storage area. 

Format 

 

or 

 

4-8 3787 3247-111





This parameter references a storage area for data passed to or from the TAS interface, 

depending on the mail operation. You must declare this statement in your application 

program: 

 

The total buffer area must be less than or equal to 3300 characters. This is the largest 

message that TAS can transfer. See 4.14for more information. 


 

 

 

 

 

 

 

 

 

 

 

 

 

 


D$LNCT Line count. Required if the previous operation was DDN$SENDMAIL or 

DDN$PREPARE. Specify the number of text lines in the mail buffer to be 

prepared or sent. 

D$BSIZ Buffer size. Required if previous operation was DDN$SENDMAIL or 

DDN$PREPARE. Specify the maximum number of characters to be used in the 

mail buffer.This value must be a multiple of four and not greater than 3300. 

D$LSIZ Line size. Required if previous operation was DDN$PREPARE or 

DDN$SENDMAIL. Specify the number of characters per line in the mail buffer. 

This value must not be greater than 132. 

3787 3247-111 4-9 

continued


continued 

D$LBID Last buffer indicator. Required if previous operation was 

DDN$SENDMAIL or DDN$PREPARE. Indicatesifthisisthelastbufferforthe 

mail operation. 

0 = Last Buffer 

1=NotLastBuffer 


If 1 (Not Last Buffer) is specified, the program must issue a DDN$CONTINUE 

INCLUDE statement that specifies 0 (Last Buffer) or a DDN$DISCONT INCLUDE 

statement before issuing any other mail function calls. 

D$MTCI More to come indicator. Returned if previous operation was a DDN$CHECK, 

DDN$DIST, or DDN$GET. Indicates there was incoming data remaining after the 

user’s mail buffer was filled to capacity. 


DDN$DISCONT INCLUDE statement. No other mail functions can be issued until 

a DDN$DISCONT function is issued. 

D$LNCT Line count. Returns the number of text lines received in the mail buffer, if 

previous operation was a DDN$CHECK, DDN$DIST, or DDN$GET. 

Example 


1. Set line count. D$LNCT=20 


3. Set line size. D$LSIZ=132 

4. Set last buffer indicator. D$LBID=0 

5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$CONTINUE 

4-10 3787 3247-111

Ending a Mailbox Assignment (DDN$DISCONN) 

4.4. Ending a Mailbox Assignment (DDN$DISCONN) 

Function 

You should use the DDN$DISCONN to end the mailbox assignment you established with a 

DDN$MAILBOX INCLUDE statement. 

Use it after the last DDN$MAILBOX. You do not need to issue DDN$DISCONN after every 

DDN$MAILBOX as each DDN$MAILBOX INCLUDE statement automatically ends the 

previous mailbox assignment. 

Once you issue the command, you cannot issue any more mail processor commands until 

you assign a new mailbox (DDN$MAILBOX). 

The associated subroutine call only references the D$PCST (Status) information packet. 

Format 

 

or 

 



Example 


1. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$DISCONN 

3787 3247-111 4-11

Terminating a Mail Operation (DDN$DISCONT) 

4.5. Terminating a Mail Operation (DDN$DISCONT) 

Function 

Use a DDN$DISCONT INCLUDE statement to terminate the previous mail operation. 

Before you do this, check to see if the D$MTCI indicator is set after a DDN$CHECK, 

DDN$DIST, or DDN$GET INCLUDE statement. If this indicator is set, you must either: 

$ Use DDN$CONTINUE to accept the additional information in the mail buffer 

$ Issue a DDN$DISCONT to reject additional information and terminate the operation 

See 4.3 for additional information. 

If you are passing buffers of data for DDN$PREPARE or DDN$SENDMAIL INCLUDE 

statement, you must either: 

$ Set D$LBID to 0 (Last Buffer) 

$ Issue a DDN$DISCONT INCLUDE statement to terminate the operation 

The associated subroutine call only references the D$PCST (Status) information packet. 

Format 

 

or 

 



Example 


1. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$DISCONT 

4-12 3787 3247-111

Creating, Changing, or Deleting Distribution Lists (DDN$DIST) 

4.6. Creating, Changing, or Deleting Distribution 

Lists (DDN$DIST) 

Function 

If you frequently send mail to the same set of mailboxes, it will be easier to use a 

distribution list. You can create a distribution list with the DDN$DIST INCLUDE statement 

and reference this distribution list name in the DDN$SENDMAIL INCLUDE statement. You 

can also use the DDN$DIST INCLUDE statement to: 

$ Display or delete distribution lists 

$ Insert or remove members in existing distribution lists 

The mailbox to which you are assigned when you create a distribution list owns that list. 

Only you can change or delete the list. However, anyone can display or send mail to that 

list. 

The mail processor automatically updates distribution lists when users change or delete 

their mailbox names. 

The associated subroutine call references the D$PCST (Status), D$MAIL (Mail), D$DIST 

(Distribution), and D$ELST (List Error) information packets. It also references the 

D$MBUF (Mail Buffer) and D$MLST (Mailbox List) storage areas. 

Format 

 

or 

 




When D$MMOD is 4 (Display), this parameter references a storage area for distribution list 

names owned by the currently-assigned mailbox. You must declare this statement in your 

application program: 

 

Total buffer area must be less than or equal to 3300 characters (the largest message TAS 

can transfer). See 4.14 for more information. 

3787 3247-111 4-13



 

 

 

 

 

 

 

 

 

 

 

 

 

 


D$MMOD Mode mail. Required. Indicates the operational mode of the called function. 

Create = 2 

Delete = 3 

Display = 4 

Insert = 5 

Remove = 6 

D$BSIZ Buffer size. Required if D$MMOD is 4 (Display). Specify the maximum 

number of characters to be used in the mail buffer. 



D$MTCI More to come indicator. Indicates there is incoming data remaining after the 

mail buffer was filled to capacity, if D$MMOD is 4 (Display). 


DDN$DISCONT INCLUDE statement. No other mail functions can be issued until 



D$MMOD is 4 (Display). 

D$DIST (Distribution) Packet 

 

 

 

 

 

 

 

 

4-14 3787 3247-111



D$HID Host-id. Required if D$MMOD is 4 (Display) and the distribution list 

resides on a remote host. Specify the host-id or logical host name. (See 

Appendix B.) 

D$LIST List name. Required. Specify the name of this distribution list. If the 

distribution list resides on this host or any other OS 2200 host, the name 

cannot contain more than 12 characters. (See Appendix B.) 

If *ALL is specified, and D$MMOD is 4 (Display), all distribution lists for the 

currently assigned mailbox will be displayed. 

D$NENT Number of entries. Required if D$MMOD is 2 (Create), 5 (Insert), or 6 

(Remove). Specify the number of mailbox names in D$MLST. 

D$ELST (List Error) Packet 

The maximum is 20 names of 88 characters each. (See Appendix B.) 

The D$ELST packet contains errors that are encountered while attempting to access 

members of D$MLST. Unlike errors posted in D$PCST, the list errors posted in this packet 

do not cause command termination, but give notification of any members that could not be 

accessed. 

A class code of 193 and detail status of 7010 are returned in D$PCST to indicate that list 

errors occurred and D$ELST should be examined. However, if any non-list error is 

encountered, that error will be posted in D$PCST instead of 193/7010. D$ELST may still be 

examined to see if any list errors occurred (D$ECNT is not 0) before the non-list error 

occurred. 

 

 

 

 

 

 

 

 

 

See Appendix A for a list of error codes. 


D$ECNT Error count. Indicates the number of errors encountered while accessing the 

mailboxes in D$MLST. Only the first 11 errors encountered for this command 

are posted here. 

This value also indicates the number of occurrences of D$ELE1. 

3787 3247-111 4-15 

continued


continued 

D$ELNE Error line. Contains message text describing the error that occurred. 

The first four characters contain an error number. See Table A-5. 

D$ELE1 Error lines. Breaks D$ELNE into two lines of 80 characters each. Some errors 

will only have one line of text. 

D$MLST (Mailbox List) Parameter 

This parameter references a storage area for a list of mailbox names. It is used to hold 

mailbox names that are: 

$ Used to create a distribution list 

$ Inserted into, or deleted from, an existing distribution list 

DDN$SENDMAIL references this area to send mail to more than one mailbox. 

When you are creating a distribution list, or when you are inserting or removing mailboxes 

from an existing list, set the D$NENT field of the D$DIST packet to the number of entries 

in the mailbox list (D$MLIT). 

The mailbox list can contain a maximum of 20 entries, and each entry is up to 88 

characters long. Each entry consists of a host-id with a maximum of 24 characters and a 

mailbox name with a maximum of either 64 characters (for non-OS 2200 hosts) or 8 

characters (for OS 2200 hosts). 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4-16 3787 3247-111



D$MH01...D$MH20 Host-id. Specify a host-id with a maximum of 24 characters. 

The default is the local host. 

D$ML01...D$ML20 Mailbox name. Specify a mailbox name with a maximum of 64 

characters for non-OS 1100 hosts or 8 characters for OS 2200 

hosts. 

See Appendix B for a discussion on host and mailbox-naming conventions. 

Example 


1. Set operational mode to Create (2). D$MMOD=2 

2. Specify list name. D$LIST=’MYLIST’ 

3. Specify number of entries. D$NENT=3 

4. Enter the mailbox names. D$ML01=’DDNMAIL01’ 

D$ML02=’DDNMAIL02’ 

D$ML03=’DDNMAIL03’ 

5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$DIST 

3787 3247-111 4-17


Additional Discussion 

The size of each line in the mail buffer after a DDN$DIST INCLUDE statement with 

D$MMOD specified as Display is 80 characters. The format of each line is as follows: 


1-4 Blank 

5-28 Host 

29-32 Blank 

33-52 Mailbox 

53-56 Blank 

57-76 User 

77-80 Blank 

The size of each line in the mail buffer after a DDN$DIST INCLUDE statement with *ALL 

specified in D$LIST and D$MMOD specified as Display is 80 characters. The format of each 

line is as follows: 


1-7 Blank 

8-19 Distribution list name 

20-25 Blank 


38-43 Blank 


56-61 Blank 


74-80 Blank 

4-18 3787 3247-111

Getting Mail from the Mailbox (DDN$GET) 

4.7. Getting Mail from the Mailbox (DDN$GET) 

Function 

Use the DDN$GET INCLUDE statement to retrieve and read incoming or outgoing mail for 

the mailbox currently assigned to you. Depending on the parameters you include, you can: 

$ Place the mail in the mail buffer (memory) 

$ Save the mail in a file 

$ Delete the mail from the mailbox 

$ Combine any of the above operations 

You must know the mail identifier for the mail you want to retrieve. The DDN$CHECK 

INCLUDE statement provides incoming identifiers in the first eight positions of each line 

returned. You must issue a DDN$CHECK before issuing a DDN$GET to retrieve incoming 

mail items. Outgoing mail identifiers are assigned by the user for DDN$PREPARE and 

DDN$SENDMAIL (Create and Send operation) INCLUDE statements. 



Format 

 

or 

 




This parameter references a storage area into which DDN returns incoming or outgoing 

mail. You must declare this statement in your application program: 

 

The total buffer area must be less than or equal to 3,300 characters (the largest message 

TAS can transfer). See 4.14 for more information. 

3787 3247-111 4-19



 

 

 

 

 

 

 

 

 

 

 

 

 

 


D$MTYP Mail type. Required. Specify incoming or outgoing mail. 

Incoming = 0 

Outgoing = 1 

D$IMID Incoming mail-id. Required if D$MTYP is Incoming (0). Specify 8 

characters for the mail-identifier. 

It must be zero-filled and right-justified. 

D$OMID Outgoing mail-id. Required if D$MTYP is Outgoing (1). 

Specify up to 8 characters for the mail-identifier. 

D$AUTH Author. Optional. You can specify up to 20 characters for an author’s name. 

D$BSIZ Buffer size. Required if D$GTLC is specified as 0 (In Memory). Specify 

the maximum number of characters to be used in the mail buffer. 


D$LSIZ Line size. Required if D$GTLC is specified as 0 (In Memory).Specify the 

number of characters per line in the mail buffer. 

This value must be large enough to hold the largest line in the mail item but 

must not be greater than 132. 

D$MFIL Mail file name. Required if D$GOP is specified as 1 (Get and Save) or 3 

(Get, Save, and Delete). Specify the fully qualified OS 2200 file name to be 

used to save the mail that is retrieved. 

continued 

4-20 3787 3247-111

continued 


D$GOP Get operation. Required. Specify the operation to be performed by the 

DDN$GET INCLUDE statement. 

Get = 0 

Get and Save = 1 

Get and Delete = 2 

Delete = 3 

Get (retrieves mail from the mailbox), Save (saves mail in a file), and Delete 

(deletes mail from the mailbox) 

D$GTLC Get text location. Required. Specify if the text is to be put into the mail 

buffer. 

In Memory = 0 

Not In Memory = 1 


D$MTCI More to come indicator. Indicates there was incoming data remaining after 

the user’s mail buffer was filled to capacity, if D$GTLC is specified as 0 (In 

Memory). 


DDN$DISCONT INCLUDE statement. No other mail function can be issued until 



D$GTLC is specified as 0 (In Memory). 

Example 


1. Set to get incoming mail (0). D$MTYP=0 

2. Set mail-id. D$IMID=’00000001’ 



5. Set file name. D$MFIL=’MY*FILE’ 

6. Set to Get & Save (1). D$GOP=1 

7. Specify get text location as In 

Memory (0). 

D$GTLC=0 

8. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$GET 

3787 3247-111 4-21

Creating, Changing, Assigning, or Deleting Mailboxes (DDN$MAILBOX) 

4.8. Creating, Changing, Assigning, or Deleting 

Mailboxes (DDN$MAILBOX) 

Function 

Use the DDN$MAILBOX INCLUDE statement before you use any of the other mail 

processing commands. It assigns you a specific mailbox. Once you have a mailbox, you can 

read any of the incoming mail for that mailbox. Any mail you prepare while using the 

mailbox becomes part of the outgoing mail list for that mailbox. 

In addition to assigning a mailbox, you also use the INCLUDE statement to create, change, 

or delete mailboxes. 

The associated subroutine call references the D$PCST (Status), D$MAIL (Mail), and 

D$MBOX (Mailbox) information packets. 

Format 

 

or 

 


See 4.2 for a description of the D$PCST (Status) fields. 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

Field definition set by user: 

D$MMOD Mode mail. Required. Operational mode of the called function. 

Identify (assign) = 0 

Change = 1 

Create = 2 

Delete = 3 

4-22 3787 3247-111


D$MBOX (Mailbox) Packet 

 

 

 

 

 

 

 

 

 


D$MNAM Mailbox name. Required. Specify up to 8 characters for the name of the 

mailbox. 

D$MKEY Mailbox key. Required. Specify up to 8 characters for the name of the 

mailbox key. 

D$MUSR User name. Optional. Specify up to 20 characters for the name of the user 

associated with this mailbox. 

Used only for creating mailboxes. 

D$NNAM New mailbox name. Optional. To rename a mailbox, specify up to 8 

characters for the mailbox name. 

D$NKEY New mailbox key. Optional. To rename a mailbox key, specify up to 8 

characters for the mailbox key name. 

D$NUSR New user name. Optional. To rename a user, specify up to 20 characters for 

the user name. 


D$MIND Mail indicator. This field contains the current content-state of the mailbox. 

No Mail = 0 

Check Incoming = 1 

D$MSTA Mailbox status. This field reflects concurrent access of the mailbox (other 

users present). 

Inactive = 0 

Active = 1 

3787 3247-111 4-23


Example 


1. Set the mode to Create (2). D$MMOD=2 

2. Insert the mailbox name. D$MNAM=’READING’ 

3. Insert mailbox key. D$MKEY=’RR’ 

4. Specify user name. D$MUSR=’SMITH’ 

5. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$MAILBOX 

4-24 3787 3247-111

Creating an Item of Mail (DDN$PREPARE) 

4.9. Creating an Item of Mail (DDN$PREPARE) 

Function 

Use the DDN$PREPARE INCLUDE statement to create an item of mail. You must specify 

the location of the text to be used to create the item as either: 

$ In the mail buffer (memory) 

$ In a file 

The item can then be sent at any time with a DDN$SENDMAIL INCLUDE statement. You 

can also create and send mail immediately using the DDN$SENDMAIL INCLUDE 

statement. 



Format 

 

or 

 




This parameter references a storage area which contains the mail text to be prepared when 

D$TLOC is 0 (Text in Memory). You must declare this statement in your application 

program: 

 




 

 

 

 

 

 

 

 

 

 

3787 3247-111 4-25


 

 

 

 


D$TLOC Text location. Required. Specify the location of the mail text to be prepared. 

Text in Memory = 0 

Text in File = 1 

D$OMID Outgoing mail-id. Required. Specify up to 8 characters for a user-assigned 

id. 

D$AUTH Author. Optional. You can specify up to 20 characters for an author’s name. 

D$LNCT Line count. Required if D$TLOC is specified as 0 (Text in Memory). 

Specify the number of text lines in the mail buffer to be prepared. 

D$BSIZ Buffer size. Required if D$TLOC is specified as 0 (Text in Memory). 

Specify the maximum number of characters to be used in the mail buffer. 


D$LSIZ Line size. Required if D$TLOC is specified as 0 (Text in Memory). 

Specify the number of characters per line in the mail buffer. 


D$LBID Last buffer indicator. Required if D$TLOC is specified as 0 (Text in 

Memory). Indicates if this is the last buffer of text to be supplied for this call. 




INCLUDE statement that specifies 0 (Last Buffer) or issue a DDN$DISCONT 

INCLUDE statement before issuing any other mail INCLUDE statements. 

D$MFIL Mail file name. Required if D$TLOC is specified as 1 (Text in File). 

Specify the fully qualified OS 2200 file name to be used as the source for the 

text that is to be prepared. 

D$SUBJ Subject. Optional. You can specify up to 25 characters to describe the mail. 

4-26 3787 3247-111

Example 



1. Specify location of mail as Text in 

Memory (0). 

D$TLOC=0 

2. Set mail-id. D$OMID=’MEMO’ 

3. Set author’s name. D$AUTH=’ASIMOV’ 





8. Set subject. D$SUBJ=’SCIENCE FICTION’ 

9. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$PREPARE 

3787 3247-111 4-27

Deleting Mail from a Mailbox (DDN$REMOVE) 

4.10. Deleting Mail from a Mailbox (DDN$REMOVE) 

Function 

Use the DDN$REMOVE INCLUDE statement to delete incoming or outgoing mail from 

your mailbox. To delete the mail, you must specify the mail identifier. You can also delete 

mail by specifying 2 (Get and Delete) or 3 (Get, Save, and Delete) for D$GOP. 



Format 

 

or 

 




 

 

 

 

 

 

 

 

 

 

 

 

 

 


D$MTYP Mail type. Required. Indicates the type of mail. 

Incoming = 0 

Outgoing = 1 

D$IMID Incoming mail-id. Required if D$MTYP is Incoming (0). Specify 8 

characters for the id of the incoming mail item to be deleted. 

The field must be zero-filled and right-justified. 

continued 

4-28 3787 3247-111

continued 

Deleting Mail from a Mailbox (DDN$REMOVE) 

D$RAIN Remove all incoming. Optional. This indicates that all incoming mail items 

for the currently assigned mailbox are to be deleted. 

Only *ALL can be specified in this field. 

D$OMID Outgoing mail-id. Required if D$MTYP is Outgoing (1). Specify up to 8 

characters for the id of the outgoing mail item to be deleted. 

D$RAOT Remove all outgoing. Optional. This indicates that all outgoing mail for the 

currently assigned mailbox is to be deleted. 

Example 

Only *ALL can be specified in this field. 


1. Set to remove outgoing mail (1). D$MTYP=1 

2. Set mail-id. D$OMID=’MYNAME’ 

3. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$REMOVE 

3787 3247-111 4-29

Sending Mail to Mailboxes (DDN$SENDMAIL) 

4.11. Sending Mail to Mailboxes (DDN$SENDMAIL) 

Function 

DDN$SENDMAIL sends mail to target mailboxes and distribution lists. 

You can either: 

$ Send mail previously prepared by the DDN$PREPARE statement (Send) 

$ Prepare and send mail immediately (Create and Send) 

The mail is already created 

(Send) 

Themailmustbecreated 

(Create and Send) 

If... Then ... 

In the D$SEND packet, specify D$SOP as Send 

In the D$MAIL packet, supply: 

* mail-id 

* location (Text in Mailbox) 

In the D$SEND packet, specify D$SOP as Create and Send 

In the D$MAIL packet, supply: 

* mail-id 

* location (Text in Mailbox) 

* all fields required for DDN$PREPARE 

The associated subroutine call references the D$PCST (Status), D$MAIL (Mail), D$SEND 

(Send), and D$ELST (List Error) information packets. It also references the D$MBUF (Mail 

Buffer), D$MLST (Mailbox List), and D$DLST (Distribution List) storage areas. 

Format 

 

or 

 




This parameter references a storage area for mail text to be sent when D$SOP is specified 

as 1 (Create and Send). You must declare this statement in your application program: 

 



4-30 3787 3247-111



 

 

 

 

 

 

 

 

 

 

 

 

 

 

Field definitions set by user when D$SOP is specified as Send: 

D$TLOC Text location. Required. Specify the location of the mail text to be sent as 

Text in Mailbox = 2. 

D$OMID Outgoing mail-id. Required. Specify up to 8 characters for an outgoing 

mail-id. Alternatively, you can specify an incoming mail-id for this field; it must 

be left-justified and space-filled. 

Field definitions set by user when D$SOP is specified as Create and Send: 

D$TLOC Text location. Required. Specify the location of the mail text to be sent. 

Text in Memory = 0 

Text in File = 1 

D$AUTH Author. Optional. You can specify up to 20 characters for a name. 

D$LNCT Line count. Required if D$TLOC is specified as 0 (Text in Memory). 

Specify the number of text lines in the mail buffer to be created and sent. 

D$BSIZ Buffer size. Required if D$TLOC is specified as 0 (Text in Memory). 

Specify the maximum number of characters in the mail buffer. 


D$LSIZ Line size. Required if D$TLOC is specified as 0 (Text in Memory). 

Specify the number of characters per line in the mail buffer. 


3787 3247-111 4-31 

continued


continued 

D$LBID Last buffer indicator. Required if D$TLOC is specified as 0 (Text in 

Memory). Indicates if this is the last buffer of text to be supplied for this call. 




INCLUDE statement that specifies 0 (Last Buffer) or issue a DDN$DISCONT 

INCLUDE statement before issuing any other mail INCLUDE statements. 

D$MFIL Mail file name. Required if D$TLOC is specified as 1 (Text in File). 

Specify the fully qualified OS 2200 file name to be used as the source for the 

text that is to be created and sent. 

D$SUBJ Subject. Optional. Youcanspecifyupto25characterstodescribethe 

subject matter of the mail. 

D$SEND (Send) Packet 

 

 

 

 

 

 

Field definitions set by user for Send or Create and Send: 

D$REPI Reply indicator. Required. Specify whether you want a response for this 

piece of mail. 

Not Required = 0 

Required = 1 

D$SMOD Send mode. Required. Directs the handling of mail. 

Mail = 0 

Send = 1 

SAML = 2 

SOML = 3 

D$MBCT Mailbox count. Required. Specify the number of mailbox names in D$MLST. 

The maximum is 20 names of 88 characters each. (See Appendix B.) If there 

are no names in D$MLST, specify 0, and D$DLCT must not be 0. 

D$DLCT Distribution count. Required. Specify the number of distribution list names in 

D$DLST. 

The maximum is 20, 88-character names. (See Appendix B.) If there are no 

names in D$DLST, specify 0, and D$MBCT must not be 0. 

continued 

4-32 3787 3247-111

continued 


D$SOP Send operation. Required. Specify the type of operation to be performed. 

Send = 0 

Create and Send = 1 

D$ELST (List Error) Packet 

The D$ELST packet contains errors: 

$ Encountered while attempting to access members of D$MLST or D$DLST. 

$ Which do not cause command termination, but give notification of any members that 

could not be accessed 

Examine the D$ELST field when: 

$ A class code of 193 and detail status of 7010 are returned in D$PCST 

$ A non-list error is posted in D$PCST instead of 193/7010 to check for any list errors 

(D$ECNT is not 0) before the non-list error occurred 

 

 

 

 

 

 

 

 

 

See Appendix A for a list of error codes. 


D$ECNT Error count. Indicates the number of errors encountered while accessing the 

mailboxes in D$MLST or D$DLST. 

Only the first 11 errors encountered for this command are posted. This value 

also indicates the number of occurrences of D$ELE1. 

D$ELNE Error line. Contains message text describing the error that occurred. 

The first four characters contain an error number. See Table A-5. 

D$ELE1 Error lines. Breaks D$ELNE into two lines of 80 characters each. 

Some errors will only have one line of text. 

3787 3247-111 4-33


D$MLST (Mailbox List) Parameter 

This parameter references a storage area for a list of mailbox names to which mail is sent. 

The DDN$DIST INCLUDE statement and associated subroutine call references this area to 

hold mailbox names that are: 

$ Used to create a distribution list 

$ Inserted into, or deleted from, an existing distribution list 

To use a mailbox list, set the D$MBCT field of the D$SEND packet to the number of entries 

in the mailbox list (D$MLIT). The mailbox list can contain a maximum of 20 entries, and 

each entry is up to 88 characters long. Each entry consists of a host-id with a maximum of 

24 characters and a mailbox name with a maximum of either 64 characters (for 

non-OS 2200 hosts) or 8 characters (for OS 2200 hosts). 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


D$MH01...D$MH20 Host-id. Specify a host-id with a maximum of 24 characters. 

If you do not set this field, the default is the local host. 

D$ML01...D$ML20 Mailbox name. Specify a mailbox name with a maximum of 64 

characters for non-OS 2200 hosts or 8 for OS 2200 hosts. 

See Appendix B for a discussion on host and mailbox-naming conventions. 

D$DLST (Distribution List) Parameter 

This parameter references a storage area for a list of distribution list names to which mail 

is sent. The DDN$DIST INCLUDE statement and associated subroutine call is used to 

create a distribution list which consists of a list of mailbox names. 

4-34 3787 3247-111


If you choose to use distribution lists, set the D$DLCT field of the D$SEND packet to the 

number of entries in the distribution list (D$DLPT). The distribution list can contain a 

maximum of 20 entries, and each entry is up to 88 characters long. Each entry consists of a 

host-id with a maximum of 24 characters and a distribution list name with a maximum of 

64 characters. 

Note that you do not use the double colon (::) in distribution list names. Because 

distribution list names are case-sensitive, you must specify them exactly as they were 

created in the DDN$DIST command. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


D$DH01...D$DH20 Host-id. Specify a host-id with a maximum of 24 characters. 

If you do not set this field, the default is the local host. 

D$DL01...D$DL20 Distribution list name. Specify a distribution list name with a 

maximum of 64 characters. 

See Appendix B for a discussion on host-naming conventions. 

Example (Send Operation) 



Mailbox (2). 

D$TLOC=2 

2. Set mail-id. D$OMID=’MEMO’ 

3. Set for reply requested. D$REPI=1 

4. Set mode to mail. D$SMOD=1 

5. Set number of mailbox names. D$MBCT=3 

3787 3247-111 4-35



6. Set number of distribution list 

names. 

D$DLCT=0 

7. Set operation to Send (0). D$SOP=0 

8. Enter mailbox names. D$ML01=’MBX1’ 

D$ML02=’MBX2’ 

D$ML03=’MBX3’ 

9. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$SENDMAIL 

Example (Create and Send Operation) 


1. Specify mail text. D$MBUF(1)=’LINE 1’ 

D$MBUF(2)=’LINE 2’ 





Memory (0). 

D$TLOC=0 

3. Set author’s name. D$AUTH=’ASIMOV’ 





8. Set subject. D$SUBJ=’SCIENCE FICTION’ 

9. Set for reply requested. D$REPI=1 

10. Set mode to mail. D$SMOD=0 

11. Set number of mailbox names. D$MBCT=0 

12. Set number of distribution list 

names. 

D$DLCT=2 

13. Set operation to create and send. D$SOP=1 

14. Enter distribution list names D$DL01=’LIST1’ 

D$DL02=’LIST2’ 

15. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$SENDMAIL 

4-36 3787 3247-111

Obtaining a Mailbox Name (DDN$VERIFY) 

4.12. Obtaining a Mailbox Name (DDN$VERIFY) 

Function 

Use the DDN$VERIFY INCLUDE statement to determine the mailbox name for a particular 

user. 

The associated subroutine call references the D$PCST (Status) and D$VERIFY (Verify) 


Format 

 

or 

 



D$VRFY (Verify) Packet 

 

 

 

 

 

 

 

 


D$VUSR Verify user name. Required. Specify the user name to be verified. 

If the user name is on this host or any other OS 2200 host, you cannot specify 

more than 20 characters. (See Appendix B.) 

D$VHOS Verify host-id. Required if the user name is on a remote host. Specify the 

host-id or the logical host name. (See Appendix B.) 

3787 3247-111 4-37

Obtaining a Mailbox Name (DDN$VERIFY) 


D$VAMN Associated mailbox name. The mailbox name associated with the name 

specified in D$VUSR. 

D$VAUN Associated user name. Theusernameassociatedwiththemailboxname 

returned in D$VAMN. 

D$VID Verify indicator. The status returned after a DDN$VERIFY function call. 

Example 

1 = User match (D$VUSR matches a user name on the host) 

2 = Mailbox match (D$VUSR matches a mailbox name on the host) 


1. Set user name. D$VUSR=’MYNAME’ 

2. Set host-id. D$VHOS=’HOST-SYS1’ 

3. Issue the INCLUDE statement. INCLUDE LIBFILE.DDN$VERIFY 

4-38 3787 3247-111

Designing a Mail Transfer Application 

4.13. Designing a Mail Transfer Application 

In designing a TAS mail transfer application, you should always lay out a block diagram of 

what you want to do. (See Figure 4-1.) 

Create a 

Mailbox 

Prepare the 

Mail 

Disconnect 

Figure 4-1. Typical TAS FORTRAN Mail Transfer Block Diagram 

Once you design the basic block diagram, you can create a flow diagram by filling in the 

blocks with FORTRAN procedure statements (as shown in Figure 4-2 through Figure 4-6) 

according to the requirements for each INCLUDE statement. 

In most cases, you fill in the blocks by taking the example given under each INCLUDE 

statement in 4.1 through 4.12and placing it in the appropriate block. Some changes to the 

example might have to be made for your particular application. 

Figure 4-2 shows how to create a mailbox and prepare the mail from text found in the mail 

buffer (memory). To keep the flow diagram as simple as possible, error/status checking 

routines are not shown. See the mail transfer application program in Appendix D for a 

complete working example. 

3787 3247-111 4-39


CREATE MAILBOX 

D$MMOD=2 

D$MNAM='SYSPUBS' 

D$MKEY='SP' 

D$MUSR='SMITH' 

INCLUDE LIBFILE.DDN$MAILBOX 


CALL DISTAT 

END IF 

PREPARE MAIL 

D$TLOC=0 

D$OMID='MEMO' 

D$AUTH='ASIMOV' 

D$LNCT=20 

D$BSIZ=2640 

D$LSIZ=132 

D$LBID=0 

D$SUBJ='STAR WARS' 

INCLUDE LIBFILE.DDN$PREPARE 

IF (D$PCCL .NE. 1)THEN 

CALL DISTAT 

END IF 

INCLUDE LIBFILE.DDN$DISCONN 


CALL DISTAT 

END IF 

Figure 4-2. Mail Transfer Flow Diagram (Create Mailbox and Prepare Mail from 

Buffer) 

Figure 4-3 shows how to assign a mailbox and prepare the mail from a file. To keep the 

flow diagram as simple as possible, error/status checking routines are not shown. See the 

mail transfer application program in Appendix D for a complete working example. 

4-40 3787 3247-111

ASSIGN MAILBOX 

D$MMOD=2 


D$MKEY='SP' 



CALL DISTAT 

END IF 

PREPARE MAIL 

D$TLOC=1 

D$OMID='MEMO' 

D$AUTH='ASIMOV' 

D$MFIL='MAIL*MEMO' 

D$SUBJ='STAR WARS' 

INCLUDE LIBFILE.DDN$PREPARE 


CALL DISTAT 

END IF 



CALL DISTAT 

END IF 


Figure 4-3. Mail Transfer Flow Diagram (Assign Mailbox and Prepare Mail from File) 

Figure 4-4 shows how to assign a mailbox and send the prepared mail from the mailbox to 

a distribution list. To keep the flow diagram as simple as possible, error/status checking 

routines are not shown. See the mail transfer application program in Appendix E for a 


3787 3247-111 4-41



D$MMOD=0 


D$MKEY='SP' 



CALL DISTAT 

END IF 

FILL MAILBOX LIST STORAGE AREA 

D$MLIS(1)='PAT' 

D$MLIS(2)='JOE' 

D$MLIS(3)='MARY' 

CREATE DISTRIBUTION LIST 

D$MMOD=2 

D$LIST='MYLIST' 

D$NENT=3 

INCLUDE LIBFILE.DDN$DIST 


CALL DISTAT 

END IF 

SEND PREPARED MAIL 

D$TLOC=2 

D$OMID='MEMO' 

D$REPI-1 

LIST(1)='MYLIST' 

D$SMOD=0 

D$MBCT=0 

D$DLCT=1 

D$SOF=0 

INCLUDE LIBFILE.DDN$SENDMAIL 

IF D$PCCL .NE. 1) THEN 

CALL DISTAT 

END IF 



CALL DISTAT 

END IF 

Figure 4-4. Mail Transfer Flow Diagram (Assign Mailbox and Send Prepared Mail) 

Figure 4-5 shows how to create mail from the mail buffer (memory) and send it 

immediately. To keep the flow diagram as simple as possible, error/status checking 

routines are not shown. See the mail transfer application program in Appendix D for a 


4-42 3787 3247-111


D$MMOD=0 


D$MKEY='SP' 



CALL DISTAT 

END IF 

SET DESTINATION MAILBOX LIST 

D$MLIT='TED' 

INSERT MESSAGE IN BUFFER 

WRITE 

10 FORMAT ('ENTER MAIL TEXT') 

READ (5,20) D$MBUF 

20 FORMAT (240A1) 

CREATE AND SEND. 

D$TLDC=0 

D$LNCT=5 

D$BSIZ=3300 

D$LSIZ=132 

D$DBID=0 

D$REPI=1 

D$SMOD=0 

D$MBCT=1 

D$DLCT=0 

D$SOP=1 

INCLUDE LIBFILE.DDN$SENDMAIL 


CALL DISTAT 

END IF 



CALL DISTAT 

END IF 


Figure 4-5. Mail Transfer Flow Diagram (Create Mail from Buffer and Send 

Immediately) 

Figure 4-6 shows how to check incoming mail and get the first mail item. To keep the flow 

diagram as simple as possible, error/status checking routines are not shown. See the mail 

transfer application program in Appendix D for a complete working example. 

3787 3247-111 4-43



D$MMOD=0 


D$MKEY='SP' 



CALL DISTAT 

END IF 

CHECK INCOMING MAIL 

D$MTYP=0 

D$BSIZ=2000 

INCLUDE LIBFILE.DDN$CHECK 


CALL DISTAT 

END IF 

GET INCOMING MAIL 

D$MTYP=0 

D$IMID=1 

D$BSIZ=2000 

D$LSIZ=132 

D$GOP=0 

D$GTLC=0 

INCLUDE LIBFIILE.DDN$GET 

IF (D$PCL .NE. 1) THEN 

CALL DISTAT 

END IF 



CALL DISTAT 

END IF 

Figure 4-6. Mail Transfer Flow Diagram (Check Incoming Mail and Get First Mail Item) 

4-44 3787 3247-111

4.14. Using the Mail Buffer Area 

Different functions use the mail buffer area of your program to: 

$ Pass mail text to TAS 

$ Receive mail text and other mail processor information from TAS 

Using the Mail Buffer Area 

The INCLUDE statements that use the mail buffer reference the name D$MBUF for the 

INCLUDE statements. You must define this area in storage. Alternatively, you can use 

other names for this area, but you must then use an EQUIVALENCE statement with the 

INCLUDE statements. 

Specify the size (in characters) of the mail buffer in field D$BSIZ of D$MAIL. It must be: 

$ A multiple of 4 

$ 3300 characters, or less 

You can use the buffer to hold one line or a multiple number of lines. Fields D$LSIZ and 

D$LNCT of D$MAIL are used to make this distinction. 

If you use this buffer for ... Then the buffer must be... 

DDN$CHECK or DDN$DIST At least 80 characters long 

DDN$GET Large enough to hold the largest text line in the mail item 

You can define one buffer to be used by all mail functions. For example: 

 

For DDN$CHECK and DDN$DIST, the mail information returned is 80 characters per line, 

so you may want to define the buffer as an array of 80 characters. For example: 

 

 

 

Produces the subroutine call: 

 

 

 


 

3787 3247-111 4-45

Using the Mail Buffer Area 

When creating a mail item, you can define the buffer as text lines, instead of moving the 

text lines into the buffer before issuing the subroutine call. For example: 

 

 

 

 

 

 


 

4-46 3787 3247-111

Section 5 

Compiling, Linking, and Executing TAS 

FORTRAN Programs 

5.1. Preparing Programs for Execution 

After you write your FORTRAN application programs, you compile, link, and execute the 

FORTRAN programs in the same way as any other UCS FORTRAN program. There are 

only two special requirements: 

1. If you use the supplied TAS FORTRAN INCLUDE statements in your program, you 

must issue the following statements before compiling your program: 

 

 

2. You must include TAS FORTRAN object module elements when you collect each 

program into an output object module element. The object module elements are 

NPEFORMAPPC and UCSINTFPPPC. 

3787 3247-111 5-1

Run Streams for TAS FORTRAN Programs 

5.2. Run Streams for TAS FORTRAN Programs 

To compile, link, and execute a TAS FORTRAN program, do the following: 

1. Obtain a clean compilation of the FORTRAN application program using the 

TAS-supplied FORTRAN INCLUDE statements. 

2. Link (@LINK) the object module application element obtained from the compilation, 

along with the object module TAS FORTRAN interface elements, into one output 

object module element in a program file. 

3. Then, execute the program (@XQT) using the output object module element name of 

the file and element you supplied on the @LINK statement. 

The TAS FORTRAN interface elements are supplied on your release tape. They are 

installed into files SYS$LIB$*TAS-1 and SYS$LIB$*TAS-3. To copy them into your own 

files, you must change the FTN$PF and PPPCLIB @USE statements accordingly. For 

details, see the TAS Implementation and Administration Guide. 

In the sample streams, uppercase letters must be entered exactly as shown. Lowercase 

letters are names that you can select. See Appendix Bfor file-naming conventions. 

Figure 5-1 shows a sample run stream to: 

$ Compile a UCS FORTRAN application program using TAS-supplied FORTRAN copy 

elements 

$ Collect the application program and TAS FORTRAN interface object module element 

into an output object module element 

$ Execute the output object module 

5-2 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 5-1. Compile, Link, and Execute Stream for a TAS FORTRAN Program 

Note that Steps 3 and 4 in Figure 5-1 use the UCS static linking capability. 

Alternatively, you can use dynamic linking, which is faster, by replacing these steps with 

the following: 

$ Copy the NPEFORMAPPC and UCSINTFPPPC object modules from SYS$LIB$*TAS-1 

to the same file that contains the UCS FORTRAN compiler output object module. 

$ Execute the UCS FORTRAN compiler output object module, as follows: 

 

Figure 5-2 shows a sample run stream to: 

$ Compile a UCS FORTRAN transaction processing (TIP) application program using 

TAS-supplied FORTRAN copy elements 

$ Link the application program and TAS FORTRAN interface object module element into 

an output object module element 

$ Execute the output object module 

3787 3247-111 5-3


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 5-2. A Compile, Link, and Execute Stream 

Note that Steps 3 and 4 in Figure 5-2 use the UCS static linking capability. Alternatively, 

you can use dynamic linking by replacing these steps with the following: 

$ Copy the NPEFORMAPPC and UCSINTFTIP object modules from SYS$LIB$*TAS-1 to 

the same file that contains the UCS FORTRAN compiler output object module. 

$ Execute the UCS FORTRAN compiler output object module, as follows: 

 

5-4 3787 3247-111

Appendix A 

TAS Status Codes 

TAS always returns a class code and a detailed status code to the D$PCCL and D$PCDT 

fields of program-callable status packet D$PCST in the program after processing each 

subroutine call issued by your application program. TAS also provides up to three 

additional inserts in the D$PCML field of the status packet to identify the specific error. 

Your application program should test the contents of these fields and perform routines to 

handle the conditions indicated by them. 

Class codes 192 through 194 signify TAS-specific errors (errors that are issued only by 

TAS).Error types signified by the decimal class codes and the tables in this section that 

contain the detail status codes and error message text are: 

Class Code 

Decimal Value 

Type of Error Table 

192 Program-callable Table A-1 

193 Program-callable mail transfer Table A-2 

194 Program-callable file transfer Table A-3 

In the tables, the insert fields referred to in the explanations are the specific inserts that 

the system returns in the D$PCML field of the status packet. 

Table A-4 and Table A-5 list D$PCEF error indicators and D$ELST error codes. 

Table A-1 contains message text. The decimal class code (D$PPCL or D$PCCL) for all of 

these messages is 192. The number preceding each message in the table is the decimal 

detail status code returned in the D$PPDT field of D$PPST or D$PCDT of D$PCST for that 

message. 

3787 3247-111 A-1


Table A-1. Class Code 192 Detail Status Values 

D$PPDT D$PCDT Explanation 

00001 Parameter or parameters missing for TAS subroutine call. 

00002 Required entry in [insert 1] is missing. 

00003 Entry in [insert 1] is invalid. 

00004 TAS program-callable internal error number [insert 1]. 

00005 Program-callable file transfer functions are not permitted when TAS is installed as local 

mail only. 

00006 Entry in field [inset 1] is invalid. The MAILID must be numeric when the TYPE field is 

specified as incoming. 

Table A-2 contains message text for program-callable mail transfer errors. The decimal 

class code (D$PCCL) for all of these messages is 193. The decimal number preceding each 

message in the table is the decimal detail status code returned in the D$PCDT field of 

D$PCST for that message. 


D$PCDT Explanation 

00050 The new mailbox name already exists. 

Enter the DDN$MAILBOX command with D$MMOD=CHANGE specifying another mailbox 

name. 

00100 Mailbox does not exist. 

Mailbox was never created. Enter a DDN$MAILBOX command with D$MMOD=CREATE. 

00110 Mailbox already exists. 

Mailbox is already created. Another create cannot be entered. 

Enter the DDN$MAILBOX command with D$MMOD=CREATE specifying another mailbox 

name. 

00120 Mailbox key is incorrect. 

Key does not match the key that was specified when the mailbox was created. 

00130 Cannot change or delete the mailbox. Mailbox is active for another user. 

Changing or deleting a mailbox is only permitted when only one user is accessing it. 

00140 D$MUSR= , D$MNAM= , or D$MKEY= is invalid with D$MMOD= [insert 1]. 

D$MUSR= is valid only for D$MMOD=CREATE or D$MMOD=CHANGE. 

D$MNAM= or D$MKEY= is valid only for D$MMOD=CHANGE. 

continued 

A-2 3787 3247-111

Table A-2. Class Code 193 Detail Status Values (cont.) 


00150 D$MNAM= or D$MKEY= is invalid with D$MMOD=CREATE. 

D$MNAM= or D$MKEY= is valid only for D$MMOD=CHANGE. 


00160 D$MNAM= , D$MKEY= , or D$MUSR= must be specified with D$MMOD=CHANGE. 

D$MNAM, D$MKEY, D$MUSR fields change the mailbox name, key, and user name. 

00170 Mailbox name or key cannot be greater than 8 characters. 

Mailbox name and key are separated by a slash (/). 

00180 Mailbox key was not specified. 

Mailbox key is a string containing 1 to 8 characters. 

00182 Mailbox key is separated from the mailbox name by a slash(/). 

00190 Mailbox has no mail. 

A DDN$CHECK or DDN$REMOVE command was entered for a mailbox that has no mail. 

00200 Mail-identifier does not exist. 

The identifier specified for the D$IMID or D$OMID field does not exist. 

00210 No text was input to create the mail. 

Mail item is not created. 

00220 Mail-identifier already exists. 

This mailbox already created a mail item with this mail-identifier. 

00230 If the D$IMID or D$OMID field is specified, then the D$MFIL, D$AUTH, or D$SUBJ field 

must not be specified. 

The D$IMID or D$OMID field indicates that this mail item was already created. 

00240 The D$MLxx= or D$DLxx= fields must be specified on a SEND command. 

The DDN$SENDMAIL command must send this mail item to one or more mailboxes 

and/or one or more lists. 

00250 *ALL is legal only with D$MMOD=DISPLAY. 

*ALL is used only to display the names of all the lists the mailbox owns. 

00260 The distribution list does not exist. 

Enter the DDN$DIST command with D$LIST=list name and D$MMOD=CREATE to create 

a list. 

00270 Your mailbox does not own the distribution list. 

Only the owner of a list may insert or remove members or delete the list. 

The mailbox that creates the distribution list owns the list. 

3787 3247-111 A-3 

continued




00280 Your mailbox does not own any distribution lists. 

The mailbox that creates the distribution list owns the list. 

00290 The distribution list already exists. 

The distribution list is already created. 

Enter the DDN$DIST command with D$MMOD=CREATE specifying a different list name. 

00310 The D$NENT= field must be specified with D$MMOD=CREATE, INSERT, or REMOVE. 

The D$NENT field is used to specify mailbox names to be added or removed from a list. 

00320 Maximum length for the [insert 1] field is exceeded. 

00330 A / or :: is illegal in a mailbox name. 

00340 A / is illegal in a mailbox key. 

00350 D$NENT= is invalid with D$MMOD=DISPLAY or D$MMOD=DELETE. 

D$NENT= is valid only with D$MMOD=CREATE, D$MMOD=INSERT, or 

D$MMOD=REMOVE. 

00360 The mailbox name/mailbox key was not specified. 

The mailbox name/mailbox key is a required field. 

The mailbox name and mailbox key are strings, each containing 1 to 8 characters. 

The mailbox name and mailbox key are separated by a slash (/). 

00370 Distribution list contains no members. 

The mailbox names that were in the list have been deleted by their owners. 

00390 The last member was removed; therefore, the distribution list is deleted. 

00400 MAIL PROCESSOR INTERNAL ERROR NUMBER [insert 1]. STATUS IS [insert 2]. Command 

is not completed. Your mailbox is no longer active. 

A fatal error occurred. Please report the error to the System Administrator. 

00410 INVALID SEQUENCE ERROR NUMBER [insert 1]. 

A fatal error occurred. Please report the error to the System Administrator. 

00420 DMS internal error occurred. 

The rollback error status was [insert 1]. 

The error function was [insert 2]. 

The error number was [insert 3]. 

For an explanation of these errors, see the DMS DML Programming Reference, or 

contact your System Administrator. 

continued 

A-4 3787 3247-111



00510 DDN$MAILBOX must be the first Mail Processor command. 


DDN$MAILBOX command must be entered before other Mail Processor commands can 

be used. 

00515 Mail Processor is terminating. Command is not completed. Your mailbox is no 

longeractive. 

A fatal error occurred that caused the Mail Processor to terminate. Retry your command 

after the Mail Processor is reinitialized. 

00520 Insufficient memory available to process the command. 

The Mail Processor’s pool of memory is saturated due to the large number of users at 

this time. 

Retry your command when the number of users decreases. 

00525 Mail Processor is SHUT DOWN. 

Try again later, or report condition to your System Administrator. 

00530 Too many mailbox names for the D$MLxx= field. 

The number of mailbox names allowed on the D$MLxx= field is limited to 20. 

00540 Too many list names for the D$DLxx= field. 

The number of list names allowed on the D$DLxx= field is limited to 20. 

00550 Too many mailbox names for the D$NENT= field. 

The number of mailbox names allowed on the D$NENT= field is limited to 30. 

00560 Maximum number of printed pages is exceeded. 

Further output is not allowed because quota limit is reached. 

00580 Error encountered reading user’s response to prompt question. 

Retry the command. 

00590 Error encountered reading user’s input text. 

Retry the command. 

00595 Error encountered registering termination code. Command is not completed. 

The Mail Processor encountered an error while issuing the TRMREG executive request. 

Please report the problem to the System Administrator. 

00600 The specified file name is incorrect. 

For a description of OS 2200 file-naming conventions, see Appendix B. 

For previous users of OS 2200, no element name was specified in the file name. 

3787 3247-111 A-5 

continued




00605 READ/WRITE keys are not supported in the Mail Processor. 

00608 File cannot be assigned. 

00610 File is unavailable or rolled out. 

00612 File is assigned to a run other than the Mail Processor. 

Try freeing the file. If the file is not freed, then another user has the file assigned. 

00614 File does not exist. 

Create a file. 

00616 File is designated as a private file. 

Your project-id is not one which can access this private file. 

00618 Device dependent files are not supported. 

00620 File has a read or write key. READ/WRITE keys are not supported by the Mail Processor. 

00625 File name is not unique. 

00630 You cannot write to this file. File is a read-only file or file has a write key. 

The specified file was assigned in read-only mode. 

00640 You cannot read from this file. File is a write-only file or file has a read key. 

The specified file was assigned in write-only mode. 

00650 No text was found in the input file. 

Mail item is not created. 

00660 File is not a program file. 

00670 File is too small to save the mail item. 

File may be packed or recataloged with a larger size. 

00680 Element name cannot be found. 

00700 File cannot be opened. 

00720 Mail Processor could not read the file by using SDFI. Please report the problem to the 

System Administrator. 

00730 Cannot read the file. 

00735 Cannot free the file. 

00750 File cannot be created. Pack the directory or allocate more space for the directory. 

00760 File cannot be written. Pack the directory or allocate more space for the directory. 

continued 

A-6 3787 3247-111




00780 A file containing Fieldata characters is not supported. The file must contain ASCII 

characters only. 

00800 A mail item cannot be deleted or removed while another user is accessing your mailbox. 

00830 The host [insert 1] is not available to service your command. 

00835 Your mail request to host [insert 1] cannot be completed. 

A local error occurred on that host. 

00840 Your mail request to host [insert 1] cannot be completed due to insufficient storage 

onthat host. 

00845 Syntax error on [insert 1] command to host [insert 2]. 

Please report the problem to your System Administrator or contact your Unisys 

Representative. 

00850 Syntax error in parameters or arguments on [insert 1] command to host [insert 2]. 



00855 The [insert 1] command is not implemented on host [insert 2]. 

00860 Bad sequence for [insert 1] command to host [insert 2]. 



00865 Command field on [insert 1] command to host [insert 2] is not implemented. 

00870 Your mail request to host [insert 1] is not honored. 

Mailbox [insert 2] is unavailable. 

00875 Your mail request to host [insert 1] is aborted. Storage allocation on host [insert 1] is 

exceeded. 

00880 Your mail request to host [insert 1] is not honored. The mailbox name [insert 2] is not 

allowed. 

00885 Your mail transaction to host [insert 1] failed. 

00890 DDP is currently handling the maximum number of processes possible. Please try later. 

00895 There is currently not enough memory for DDP to execute. Please try again later. 

00900 The DDP process is not up. DDP is necessary to service remote requests. Please 

contact your System Administrator to bring up the DDP process. 

3787 3247-111 A-7 

continued




00905 Communication with the remote host cannot be established because the transport 

network is down. 

Please report the problem to your System Administrator. 

00910 The TASTSU process in DDP-PPC is not up. 

Please contact your System Administrator to bring up the DDP process. 

00915 The host [insert 1] is not configured in the TAS network. 

00920 The host [insert 1] did not respond to your command. 

Please try again. 

00925 The host [insert 1] responded with no message to your command. 

This error indicates that the specified remote host never responded to the command 

your host sent to it. 

Examples of conditions causing this error are: invalid host-id, processing loop on the 

other host, database lock on the other host. 

00930 MCP reported internal error number [insert 1]. The [insert 2] failed. 



00935 SMTP received a bad response on your [insert 1] command to host [insert 2]. Please 

report the problem to your System Administrator or contact your Unisys Representative. 

00940 There are insufficient DDP resources available to service your request to host [insert 1]. 

00945 The user name you requested to be verified is associated with more than one mailbox. 

00950 Theusernameyourequestedtobeverifiedisnotfound. 

00955 You can only display the members of a remote distribution list. 

The only D$MMOD field that is legal with a remote distribution list is DISPLAY. 

00960 You specified a host name without a distribution list name or a user name. 

00965 The host name you specified is too long. 

If the Internet physical address format is used, it is a maximum of 15 characters. 

Specify n1-n2-n3-n4, where: 

n1 is the network number between 0 and 255. 

n2 is the host number between 0 and 255. 

n3 is the logical host number and is always 0. 

n4 is the IMP number between 0 and 255. 

If the logical host name format is used, it is a maximum of 24 alphanumeric characters. 

The first character must be alphabetic. 

continued 

A-8 3787 3247-111




00970 The remote Mail Processor is not able to service your mail request to host [insert 1]. Try 

again later. 

00975 The connection to host [insert 1] is aborted. The network is unable to deliver your 

message. 

00985 A network problem occurred in the connection to host [insert 1]. 

The receive reason is [insert 2]. The connection to the host is aborted. Please report the 

problem to your System Administrator or contact your Unisys Representative. 

00990 The communications processor at host [insert 1] is down. 

00995 CMS 1100 is not running. Please report the problem to your System Administrator. 

01000 Your mail request to host [insert 1] is not honored. Distribution list [insert 2] is unavailable. 

01005 Your mail request to host [insert 1] is not honored. User name [insert 2] is unavailable. 

01010 Your mail request to host [insert 1] is not honored. The user name [insert 2] is ambiguous. 

01015 You have attempted remote mail processing from a local-mail-only installation. 

The TAS product at your site was installed with MODE C or MODE L, which means that 

TAS processing is limited to local mail only (i.e., mail can be sent and received within 

your host only). 

01020 Your mail command is not completed due to database contention. 

Retry the command. If the problem persists, retry at a later time. 

A DMS 2200 run unit deadlock condition occurred because a mailbox, a mail item, or a 

distribution list involved in your command is currently being accessed by many other 

users. 

01025 Your conversation with host [insert 1] was aborted by that host. 

A problem on the remote host caused that host to issue an abort of the conversation. 

01030 The CMS 1100 Configuration for your local host is in error. Please report the problem to 

your System Administrator. 

01035 An error is encountered acquiring a dynamic bank. 

The Mail Processor requires a dynamic D bank to process your command. This dynamic 

bank could not be acquired from the OS 2200 system. 

Retry the command. If the problem persists, report the problem to your System 

Administrator. 

07001 The D$BSIZ field in D$MAIL is greater than 3300 characters. 

07002 The D$BSIZ field in D$MAIL is not a multiple of 4. 

3787 3247-111 A-9 

continued




07003 The D$MBCT and D$DLCT fields in D$SEND are zero. One of these fields must be 

nonzero. 

07004 The D$BSIZ and/or D$LSIZ fields in D$MAIL are zero. Both of these fields must be 

nonzero. 

07005 The DDN$CONTINUE command is invalid. 

07006 The DDN$CONTINUE or DDN$DCNT command expected. Current command is ignored, 

and a DDN$DCNT command is assumed. 

07007 The D$LSIZ field in D$MAIL is not large enough to hold the mail text line. 

07008 The D$BSIZ field in D$MAIL is not large enough to hold the number of lines specified in 

D$DLCT field. 

07009 The D$LSIZ field in D$MAIL is greater than 132 characters. 

07010 Errors have occurred during access of D$MLST and/or D$DLST. 

See D$ELST and Table A-3. 

07011 Entry missing in D$MLST or D$DLST. 

07014 The D$BSIZ field in D$MAIL is less than 80 characters. This is inadequate for the 

attempted command. 

Table A-3 contains message text for program-callable file transfer errors. The decimal class 

code (D$PCCL) for all of these messages is 194. The decimal number preceding each 

message in the table is the decimal detail status code returned in the D$PCDT field of the 

D$PCST packet for that message. 



00001 An entry is required in field [insert 1] when an entry is made in field [insert 2]. 

00590 MCPerrorreceivedbytheFTPuserrunona[insert2]request. 

MCP message: [insert 1] 



continued 

A-10 3787 3247-111




00595 The following MCP message was received while doing a [insert 2] command to host 

[insert 3]. 

MCP message: [insert 1] 

Please retry your command. If the problem persists, please report it to your System 

Administrator or contact your Unisys Representative. 

05995 Host [insert 1] will be available to process your command in [insert 2] minutes. Please 

retry your command after the specified amount of time. 

06000 Host [insert 1] is not available to process your command. 

Host [insert 1] is not accepting remote requests at this time. The TELNET connection is 

being closed. You may try again later. 

06005 Host [insert 1] is unable to open the data connection. 

Remote host msg: [insert 2] 

06010 The transfer of file [insert 1] is aborted. 


06015 File [insert 1] on host [insert 2] is currently assigned to another job. 

You may try again later. 

06020 An error occurred on host [insert 1]. Your command is aborted. 


06025 There are insufficient resources on host [insert 1] to complete your command. 

You may retry your command. If the problem persists, please contact your System 

Administrator. 

06030 A syntax error was detected on a [insert 1] command to host [insert 2]. 



06035 A syntax error was detected in the fields of a [insert 1] command to host [insert 2]. 



06038 The [insert 1] command is not supported by host [insert 2]. 

06045 The [insert 1] command sent to host [insert 2] is out of sequence. 



06050 The value you entered for the [insert 1] field of the DDN$TRANSFER command is not 

supported by host [insert 2]. 

3787 3247-111 A-11 

continued




06055 TAS File Transfer was unable to log you onto the remote host. 

Reason: [insert 1] 

Please check the value you entered for that field and try again. 

06080 The account information was not supplied to host [insert 1] for a STOR command. 



06085 File [insert 1] on host [insert 2] is not available. 


06095 Storage allocation on host [insert 1] is exceeded. 


07000 [insert 1] is not a valid file name on host [insert 2]. 


Please check the syntax for file names on the host. You may retry your command after 

making any necessary corrections. 

07003 Requested action not taken; TAS received an error message from host [insert 1]. 

Message: [insert 2] 



07007 A bad response was received from host [insert 1] during connection establishment. 



07015 [Insert 1] 

07017 Command processing successfully completed. Statistics are unavailable from the hosts 

[insert 1] and [insert 2]. 

07020 Command not supported from FSITE command. This command is available through the 

standard TAS commands. Enter this command through the standard TAS interface. 

07025 Command not supported. 

07030 SITEINFO parameter successfully completed. [insert 1] bytes were transmitted in [insert 

2] seconds ([insert 3] Kbytes/second). 

07037 SITEINFO parameter successfully completed. Statistics are unavailable from the hosts 

[host 1] and [host 2]. 

07040 Requested action not taken; if D$XTYP=RELOCATABLE, ABSOLUTE, OMNIBUS or ALL, 

D$TRAN must equal TRANSPARENT. 

continued 

A-12 3787 3247-111




07050 Requested action not taken; only D$XTYP=IOW valid if you transfer a full program file. 

07055 There is an illegal character specified in the host name. 

A physical host name may only contain a numeric or a hyphen. 

Ex: 50-1-0-100. 

A logical host name must begin with an alphabetic character. 

Ex: abc-01. 

07060 TAS File Transfer encountered internal error [insert 1] while doing output to the terminal. 



07068 Requested action not taken; you may not transfer a full program file to a single element. 

07070 File [insert 1] on the local host cannot be accessed. 


07075 D$XTYP=SDF or IOW is not supported for OS 2200 to OS 2200 or remote transfer. 

07080 The [insert 1] field of DDN$TRANSFER command must be a program file element or SDF 

file. 

07090 All hosts must be OS 2200 for a three-host transfer. 

07125 The file name you specified on the [insert 1] field contains an illegal character in position 

[insert 2]. 

For a description of OS 2200 file naming conventions, see Appendix B. 

07130 You did not enter a password on the remote [insert 1] command. 

For TAS FTP to log you on to the remote host, you must supply a valid password. 

07135 You entered conflicting values for the D$FFIL and D$XTYP fields of the DDN$TRANSFER 

command. 

If you specify an element to be transferred in D$FFIL, you must use the D$XTYP field. The 

value of the D$XTYP field may not be ALL. 

07140 TAS File Transfer does not have enough memory to process your command at this time. 

This situation should be temporary. Please try again later. 

07145 TAS File Transfer encountered memory management error [insert 1]. 



3787 3247-111 A-13 

continued




07150 The host-id you entered on the [insert 1] field of the [insert 2] command is too long. 

The maximum length for a physical host-id is 15 characters. 

The maximum length for a logical host-id is 255 characters. Please check the host-id you 

are using and try again. 

07155 The D$RMRK checkpoint-id you entered on the DDN$RESUME command is too long. 

The maximum length for a checkpoint-id is 12 characters. Please verify the checkpoint-id 

you are using and try again. 

07160 You did not enter a file name on the [insert 1] field of the [insert 2] command. 

You must specify a file name. Please retry your command. 

07165 A password you entered on the [insert 1] command is too long. 

The maximum length for a password is 18 characters. Please check the password or 

passwords you are using and try again. 

07170 A user-id you entered on the [insert 1] command is too long. 

The maximum length for a user-id is 12 characters. Please check the user-id or user-ids 

you are using and try again. 

07175 An account number you entered on the [insert 1] command is too long. 

The maximum length for an account number is 25 characters. 

If you specified an account and a project-id, they must be separated by a blank. Account 

number and project-id can each only contain a maximum of 12 characters. Please check 

the account number or account numbers you are using and try again. 

07180 You entered too many values on the [insert 1] field of the DDN$TRANSFER command. 

[insert 2] is your local host-id; therefore you need only one value on the [insert 1] field. 

You may enter two values for this field only if both hosts named on the DDN$TRANSFER 

commandareremotehosts. 

07190 The value you entered on the [insert 1] field of the [insert 2] command is too long. 

The maximum length is 335. Up to 255 characters may be used for the host-id, if 

specified. Up to 80 characters may be used for the file name. 

Please make the necessary corrections and try again. 

07195 The file name you entered on the [insert 1] field of the [insert 2] command is too long. 

The maximum length for a file name is 80 characters. Please check the file name you are 

using and try again. 

07200 You entered conflicting values for the D$TRAN and D$XTYP fields of the DDN$TRANSFER 

command. 

If you use D$XTYP=OMNI, then you must also use D$TRAN=TRANSPARENT or L36. 

continued 

A-14 3787 3247-111




07205 You must specify D$XMOD=BLOCK or D$XMOD=COMPRESSED if you want to use the 

D$CHFN field. 

07210 Requested action not taken; D$XTYP=SDF or IOW only valid if D$TRAN=TRANSPARENT 

and D$STRU=FILE. 

07215 You may not name an element on the D$FILE field of the DDN$DEALLOC command. 

You may use the DDN$DEALLOC command only to remove an entire file. 

07220 The value you entered on the [insert 1] field of the [insert 2] command is too long. 

07225 Element [insert 1] does not exist in file [insert 2] on the local host. 

For a further explanation of this error, please contact your Unisys Representative. 

07230 File Transfer is unable to read file [insert 1] on the local host. 



07235 File Transfer is unable to write to file [insert 1] on the local host. 



07240 File [insert 1] on the local host is not a program file. 

07245 File Transfer cannot add element [insert 1] to file [insert 2] on the local host. 



07250 I/O ERROR occurred during File Transfer. 

Error: [insert 1] 




File: [insert 2] 




File: [insert 2] 

Element: [insert 3] 


3787 3247-111 A-15 

continued




07275 A network problem has occurred in making the connection to host [insert 1]. 

07280 The file specified on the DDN$RESUME command does not contain valid checkpoint file 

entries. Please verify the file name and try again. 

07285 You entered conflicting values on the D$STRU and D$TRAN fields of the DDN$TRANSFER 

command. 

If you use D$XTYP=SYM, the combination of D$STRU=RECORD and 

D$TRAN=TRANSPARENT or L36 is not allowable. 

07290 You may not specify REL or ABS for the D$XTYP field of the DDN$TRANSFER command. 

The values of REL and ABS for the D$XTYP field are restricted for remote-to-local and 

local-to-remote transfers. These values are meaningful only for local-to-local transfers. 

07295 The host-id you entered on the [insert 1] field of the [insert 2] command is homogeneous. 

07300 The D$FFIL file you specify must be an element in a program file or an SDF file if you 

want to use D$XTYP=SOURCE. 

07305 Requested action not taken; D$TRAN=EBCDIC only valid if D$STRU=RECORD and 

D$XTYP=SYMBOLIC. 

07307 Requested action not taken; you may not transfer an element to a file. The destination file 

must have an element specified. 

07310 File [insert 1] on the local host is a full program file and can only be transferred with 

D$TRAN=TRANSPARENT or L36. If D$TRAN = ASCII or EBCDIC, only full SDF files or 

program file elements of D$XTYP=SOURCE may be transferred to or from a remote host. 

07315 The value you entered for the D$RMRK field on the DDN$RESUME is invalid. The value 

may only contain numeric digits and one hyphen. A numeric value must appear before the 

hyphen. 

07317 The value you entered on the D$CHFN field of the DDN$TRANSFER command is too long. 

The maximum length is 45 characters. 

Please verify the file name you are using and try again. 

07320 When specifying D$POSN=ADD, only program file elements can be transferred. 

07325 The value you entered on the D$RFNM field of DDN$RESUME is too long. The maximum 

length is 48 characters. Please verify the file name you are using and try again. 

07330 You may not restart a file transfer which was successfully completed. 

07335 An error was received on the Checkpoint file. 

File Name: [insert 1] 


07340 You must specify the D$CHFN field if you want to use the D$CMF option. 

continued 

A-16 3787 3247-111




07345 The D$CMF option of the DDN$TRANSFER command is not meaningful when doing a 

Store on the local host. 

On a Checkpoint operation, mark value is determined by the host doing the Send. 

07350 File Transfer is unable to write to the specified checkpoint file. 

07355 File Transfer is unable to read the specified checkpoint file. 

07360 A 110 msg was received as a secondary response to a RETR on a 3-host Transfer. This 

is invalid. Please report this problem to your system administrator or contact your Unisys 

representative. 

07365 The checkpoint file does not contain enough information to restart the transfer process. 

You must re-enter the DDN$TRANSFER command. 

07370 The value you entered on the D$RMRK field of the DDN$RESUME command does not 

match any of the markers in the specified checkpoint file. Please verify the value entered 

and try again. 

09000 TAS File Transfer encountered an error. 


Please retry your command. If the problem persists, report it to your System 

Administrator or contact your Unisys Representative. 

09005 When D$POSN is specified as ADD, you must specify D$STRU=RECORD and 

D$TRAN=ASCII. 

09010 When POSITION is specified as ADD, you must specify TRANSLATE = ASCII or EBCDIC. 

09015 Requested action not taken; MODE=COMPRESSED only valid if STRUCTURE = FILE or 

RECORD AND TRANSLATE = ASCII or EBCDIC. 

09020 The ALLO (Allocate) command requires a value for the BYTES parameter. 

09025 The ALLO (Allocate) command requires a value for the BYTES parameter even when a 

value is given for RECORDS. 

09030 The directory name you entered for the [insert 1] command is too long. 

09050 Requested action not taken; an invalid wildcard character was entered. The valid 

characters are a-z, A-Z, 0-9, - (dash), and $ (dollar sign). 

09060 Requested action not taken; the filename parameter is invalid. 

09070 Requested action not taken; the runstream parameter is invalid. 

09080 Requested action not taken; the filename parameter is already registered to this or 

another application. The filename parameter must be unique. 

09090 Requested action not taken; the filename could not be deregistered because it does not 

match any registered filename. 

3787 3247-111 A-17 

continued




09100 Requested action not taken; there are no filenames registered for the requested 

application. 

09110 Requested action not taken; there is no Saved status for the requested application. 

09120 Requested action not taken; the last filename can not be deregistered with Saved status. 

Use a Status request to obtain the Save status or override with a Deregister All option. 

09130 Requested action not taken; the application-id could not be found. The application-id was 

entered incorrectly or was never registered. 

09140 Requested action not taken; an invalid filename was entered on the Register command. 

Please correct and re-enter. 

09150 Requested action not taken; an invalid start option was entered on the Register 

command. Please correct and re-enter. 

09160 Requested action not taken; an invalid application-id was entered. Valid characters are 

a-z, A-Z, and 0-9. 

09170 Warning status removed for: 

FILE: [insert 1] 

STATUS: [insert 2] 

09180 Requested action not taken; an invalid Control value was entered. This value must be an 

octal number (digits 0 to 7) of 1 to 4 digits with a leading zero. 

09300 You can not specify a host name on the [insert 1] parameter of the [insert 2] command. 

The host name from your Login command is used. 

09310 The host-id value for the [insert 1] parameter of the [P4] command is non-blank. 

09320 Requested action not taken; FGET or FPUT command allowed only after a session with 

theremotehostisopened(Login). 

09330 Requested action not taken; QUIT command only valid when a session with a remote host 

is active. 

09340 You must specify the host id parameter of the [insert 1] command if a session with the 

remote host is active. 

09350 Requested action not taken; POSTSKEL must be run before any FTP command can be 

executed. 

Error indicator values representing the INCLUDE statement/subroutine call in error are 

returned in the D$PCEF field of the D$PCST packet. Table A-4lists the error indicator 

values. 

A-18 3787 3247-111

Table A-4. D$PCEF Error Indicators 

INCLUDE Statement Error Code 

DDN$LOGIN 28 

DDN$FGET 29 

DDN$FPUT 30 

DDN$TRANSFER 31 

DDN$DEALLOC 32 

DDN$RESUME 33 

DDN$RENAME 37 

DDN$SITE 38 

DDN$QUIT 39 

DDN$MAILBOX 41 

DDN$CHECK 42 

DDN$GET 43 

DDN$PREPARE 44 

DDN$DIST 45 

DDN$SENDMAIL 46 

DDN$VERIFY 47 

DDN$REMOVE 48 

DDN$DISCON 49 

DDN$CONTINUE 50 

DDN$DCNT 51 

DDN$REGISTER 53 

DDN$DEREG 54 

DDN$STATUS 55 

DDN$CWD 56 

DDN$CDUP 57 

DDN$MKD 58 

DDN$RMD 59 

continued 

3787 3247-111 A-19 

TAS Status Codes


Table A-4. D$PCEF Error Indicators (cont.) 

INCLUDE Statement Error Code 

DDN$PWD 60 

DDN$ALLO 61 

Table A-5 contains error code values for errors that may be encountered while attempting 

to access members of D$MLST and/or D$DLST. A D$PCCL of 193 and D$PCDT of 7010 are 

returned in the D$PCST to indicate that list errors have occurred. The following list error 

codes are returned as the first four characters in D$ELNE of the D$ELST packet. 

Table A-5. D$ELST Errors 

Number Description 

7020 Mailbox m-name, specified on DDN$SENDMAIL command, does not exist 

7021 Mailbox m-name, specified on DDN$DIST command, does not exist 

7022 Mailbox m-name, specified on DDN$DIST command, is a duplicate 

7023 Mailbox m-name, specified on DDN$DIST command, not a member of the list 

7024 Distribution list l-name, specified on DDN$SENDMAIL command, does not exist 

7025 Distribution list l-name, specified on DDN$SENDMAIL command, has no members 

7026 Maximum length exceeded for mailbox m-name 

7027 Maximum length exceeded for distribution list l-name 

7028 The following incorrect path name was received : bad-path-name 

7029 You did not specify a mailbox name or distribution list name following host-id: h-name 

7030 Host-id beginning with h-name exceeds maximum 

7031 There are insufficient DDP resources available to service your request to host h-name 

7032 Host h-name responded with no msg to your command (Note: This error indicates that 

the specified remote host never responded to the command your host sent.) 

7033 SMTP received a bad response on your c-name command to host h-name 

7034 Host h-name forwarded mail you sent to mailbox : m-name 

7035 Host h-name is not available to service your command 

7036 Host h-name did not process request for unavailable mailbox : m-name 

continued 

A-20 3787 3247-111

Table A-5. D$ELST Errors (cont.) 

Number Description 


7037 Your mail request to host h-name cannot be completed. A local error occurred on that 

host. 

7038 Your mail request to host h-name cannot be completed due to insufficient storage on that 

host 

7039 Syntax error on c-name command to host h-name 

7040 Syntax error in fields or arguments on c-name command to host h-name 

7041 The c-name command is not implemented on host h-name 

7042 Bad sequence for c-name command to host h-name 

7043 Command field on c-name command to host h-name is not implemented 

7044 Request to host h-name failed due to unavailability of mailbox : m-name 

7045 Host h-name does not have the following mailbox : m-name 

7046 Your mail request to host h-name is aborted. Storage allocation exceeded on that host. 

7047 Request to host h-name failed. Following mailbox not allowed : m-name 

7048 Your mail transaction to host h-name failed 

7049 Host h-name is not configured in the TAS network 

7050 Host h-name did not respond to your command 

7051 The remote Mail Processor is not able to service your request to host h-name. Try again 

later. 

7052 The connection to host h-name is aborted. The network is unable to deliver your 

message. 

7053 Connection to host h-name aborted due to a network problem. The receive reason is nn. 

Report problem to your System Administrator. 

7054 The communications processor at host h-name is down 

7055 The TASTSU process in your local DDP-PPC is not up. Please contact your System 

Administrator to bring up DDP. 

7056 Request to host h-name failed. Following distribution list is unavailable : l-name 

7057 Conversation with host h-name aborted by that host 

7058 Host-id h-name contains an invalid character 

3787 3247-111 A-21

Appendix B 

Conventions for Naming Hosts, Files, 

and Mail 

B.1. Host Identifiers 

TAS hosts can be local or remote. The local host is the system on which your program is 

running. A remote host is any system in the network, other than your local host. 

Each host system has its own host identifier (host-id). To define a host-id, you can choose 

from two format types: 

$ Internet physical address 

This format is always valid for specifying a host-id. 

$ Logical host name 

This format is valid depending upon how your site administrator configured the Telcon 

software. 

An internet physical address format host-id is: 

 

where: 

n1 

n2 

n3 

n4 

Is the network number (0-223). 

Is the host number (0-255). 

Is the logical host number (0-255 (currently always 0)). 

Is the interface message processor (IMP) number (0-255). 

For example: 

 

Always include the dashes when you use this format. 

3787 3247-111 B-1

Host Identifiers 

A logical host name: 

$ Can contain up to 255 characters 

$ Must begin with an alphabetic character 

$ Can include alphanumerics as well as the minus sign (-) and the period (.) 

For example: 

 

This particular logical name represents the geographical location and system number of 

the host. The logical name translates to the physical address of the host. So, if you define a 

logical name, you can then specify a host-id by using either the logical host name or the 

physical address. 

You use host-ids in some TAS commands. If you omit a host-id in a command, the local 

host-id is assumed by default. 

You can obtain host-id information from your site administrator. 

Notes: 

1. Non-OS 2200 hosts sometimes use periods rather than dashes in the physical 

address format host-id. However, all host-ids entered in TAS commands must 

contain dashes. Using periods causes an error message. 

2. Throughout this manual, when we refer to the local host, we are referring to the 

OS 2200 host. 

B-2 3787 3247-111

B.2. File Conventions 

This section discusses the OS 2200 conventions for: 

$ Naming files 

$ Naming elements 

$ Referencing files and elements 

File Conventions 

It should help you understand the conventions for naming files and elements and the 

notation used in OS 2200 software manuals that do not apply directly to TAS processing. 

These manuals may feature the OS 2200 Executive Control Language (ECL) instead of or in 

addition to the IPF 2200 Command Language. 

B.2.1. Naming Files 

The following ECL notation specifies a file name: 

 

where: 

qualifier 

Establishes the differences between files that have the same basic name. May contain 

from 1 to 12 characters selected from the set: A through Z, 0 to 9, the dash (-), and the 

dollar sign ($). 

file-name 

Is the basic name of the file. May contain from 1 to 12 characters selected from the set: 

A through Z, 0 to 9, the dash (-), and the dollar sign ($). 

Note: File names without a qualifier get a default qualifier of the project-id for 

the FORTRAN program run. 

F-cycle 

Identifies a particular file from a set of related files that have the same qualifier and file 

name. 

read-key 

Obtains read access to the file. 

write-key 

Obtains write access to the file. 

All parameters except file-name are optional when you name a file. The Executive provides 

a standard default for those parameters that are omitted. 

3787 3247-111 B-3


B.2.2. Naming Elements 

OS 2200 recognizes five different types of elements: 

1. Symbolic elements (including procedure elements) 

Contain text, source language images for language or system processors (or 

Executive control language statements), and data to be processed by other control 

statements. 

2. Relocatable elements 

The output of certain processors such as COBOL and FORTRAN. 

3. Absolute elements 

The output of the OS 2200 Collector. 

4. Omnibus elements 

Arbitrary format elements used to store any kind of information. 

5. Object module elements 

The output of certain processors such as COBOL and FORTRAN. 

Elements of any or all of the four types are contained in program files on mass storage. 

Each element is uniquely identified within a file by its element type and element name and 

version. The following notation is used to specify element names: 

 

where: 

file-name 

Is the basic name of the file. May contain from 1 to 12 characters selected from the set: 

A through Z, 0 to 9, the dash (-), and the dollar sign ($). 

element-name 

Is the basic name of the element. May contain from 1 to 12 characters selected from 

the set: A through Z, 0 to 9, the dash (-), and the dollar sign ($). 

version 

Establishes the uniqueness between elements in the same file that have the same type 

and element name. May contain from 1 to 12 characters selected from the set: A 

through Z, 0 to 9, the dash (-), and the dollar sign ($). 

element-cycle 

Specifies a particular update of a symbolic element. Element cycles are not used for 

relocatable, absolute, and omnibus elements. They are maintained in a manner similar 

to that of file cycles (F-cycles). 

Note: Element cycles cannot be used in current TAS systems. 

All parameters except element-name are optional when naming an element. For those 

parameters omitted, the Executive supplies values according to standard rules. 

B-4 3787 3247-111


When element-cycle is omitted for a symbolic element (as it must be for TAS commands), a 

relative element cycle of 0 is supplied in order to select the most recent element-cycle. 

When the version is omitted, blanks are supplied. The file name must refer to a program 

file. 

B.2.3. Referencing Files and Elements 

When you specify a file name, use this format: 

 

When you specify both a file name and an element name, use this format: 

 

If a file name is required, but the file name information packet field is left empty, TAS 

returns an error status indicating a missing file name. 

Note that when all optional parameters are dropped from a file name or element name, the 

operating system cannot distinguish between a file and element name where either may be 

used. In such cases, the absence of a period in the specification implies that it is an 

element name. 

Always use a period after a file name, regardless of whether you use an element name. 

The following example references an element (name-2) in a specific file (name-1): 

 

The following example references a file: 

 

When you do not specify F-cycle (file cycle) or element cycle, TAS assumes that you want 

the most recent or newest element cycle. 

B.2.4. Examples 

PAYROLL*BACKUP. 

References file BACKUP with a qualifier of PAYROLL. 

COST*PROG.EDIT 

References element EDIT in the file COST*PROG. 

*BACKUP.TLU/TWO 

References version TWO of element TLU in file BACKUP. Qualifier is taken from the 

last @QUAL control statement encountered, or the project-id parameter if no @QUAL 

control statement was used. 

SORT. 

References file SORT. 

3787 3247-111 B-5

Mail Processor Conventions 

B.3. Mail Processor Conventions 

This section lists mail-naming conventions for: 

$ Mailbox names/mailbox keys 

$ Mail identifiers 

$ User names 

If a program creates mailbox names, mailbox keys, outgoing mail identifiers, or distribution 

list names, and the mail database is accessed through IPF 2200, follow the rules for IPF 

2200 string expressions. See the IPF 2200 Command Language Operations Guide. 

B.3.1. Mailbox Names/Mailbox Key 

The mail processor delivers messages to their destinations according to mailbox-names. 

Each mailbox has a unique name that consists of alphanumeric characters. Do not use the 

slash (/) or double colon (::) in mailbox names. Names of mailboxes that reside on OS 2200 

hosts have a maximum of eight characters. The number of characters for mailboxes that 

reside on non-OS 2200 hosts can vary from system to system, but can not exceed a 

maximum of 64 characters. 

Examples of valid mailbox names are: 

$ B104 

$ 104B 

$ MICHAELS 

Examples of invalid mailbox names are: 

$ /104 

$ 104:: 

$ MICHAELSON 

Mailbox keys are required for the DDN$MAILBOX command and are used to restrict 

access to the mailbox. Mailbox keys consist of one to eight alphanumeric characters. Do 

not use the slash (/) character in mailbox keys. 

B.3.2. Mail Identifiers 

Each incoming and outgoing message requires a mail identifier. The mail processor 

retrieves and delivers mail according to these identifiers. 

You assign a mail identifier to each outgoing mail item you create. A mail identifier for 

outgoing mail is from one to eight alphanumeric characters long. 

B-6 3787 3247-111

Mail Processor Conventions 

Outgoing mail identifiers are case-sensitive, which means that they must be specified in 

mail commands exactly as they were created by either the DDN$PREPARE command or 

the create and send operation of the DDN$SENDMAIL command. 

Examples of valid outgoing mail identifiers are: 

$ NOV19 

$ MEMO 

Examples of invalid outgoing mail identifiers are: 

$ NOVEMBER19 

$ MEMORANDUM 

Incoming mail identifiers are assigned by the mail processor and put into the mail buffer 

when a check command is used. A mail identifier for incoming mail is a number from 1 to 8 

digit number. 

B.3.3. User Names 

User names are required for the DDN$VERIFY command and are optional for the 

DDN$MAILBOX command. User names consist of 1 to 20 alphanumeric characters and can 

contain embedded blanks. User names are also case sensitive, which means that they must 

be specified in mail commands exactly as they were created in the DDN$MAILBOX 

command. 

3787 3247-111 B-7

Appendix C 

File Transfer Example 

This appendix contains the source coding for a UCS FORTRAN file transfer application 

program and the corresponding compile and link stream. 

C.1. Sample File Transfer Program Run Stream 

 

 

 

 

 

 

 

 

 

 

 

 

Example C-1. UCS FORTRAN Compile and Link Stream for Sample File Transfer 

Program 

3787 3247-111 C-1

Sample File Transfer Application Program 

C.2. Sample File Transfer Application Program 

The following example is the source code for a file transfer application program The 

program:. 

$ Transfers (replaces) an entire file from one host to another host 

$ Transfers (replaces) an element of a file from one host to an element of a file on 

another host 

$ Transfers a file on one host to another with checkpoint 

$ Deallocates a file 

$ Resumes a halted checkpoint file transfer 

$ Renames a file 

$ Obtains site information 

If any errors are encountered, appropriate messages are displayed on the printer. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

C-2 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 C-3


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

C-4 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 C-5


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

C-6 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 C-7

Appendix D 

Mail Transfer Example 

This appendix contains the source coding for a UCS FORTRAN mail transfer application 

program and the corresponding compile and link run stream. 

D.1. Sample Mail Transfer Program Run Stream 

 

 

 

 

 

 

 

 

 

 

 

 

Example D-1. UCS FORTRAN Compile and Link Stream for Sample Mail Transfer 

Program 

3787 3247-111 D-1

Sample Mail Transfer Application Program 

D.2. Sample Mail Transfer Application Program 

The following example is the source code for a mail transfer application program The 

program:. 

$ Creates a mailbox 

$ Checks for incoming mail 

$ Gets the mail if there is any 

$ Prepares an outgoing mail item 

$ Creates a distribution list 

$ Sends the mail to all mailboxes on the distribution list 

$ Disconnects the mailbox 

If any errors are encountered, appropriate messages are displayed on the printer. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

D-2 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 D-3


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

D-4 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 D-5


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

D-6 3787 3247-111


3787 3247-111 D-7


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

D-8 3787 3247-111


3787 3247-111 D-9


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

D-10 3787 3247-111


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 D-11


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

D-12 3787 3247-111


3787 3247-111 D-13

Appendix E 

Initialization Subroutines 

As discussed in Section 2, each command packet has an associated initialization 

subroutine that can be used to clear unused fields before specifying any parameters and 

issuing a function call. 

The following example lists the subroutines to initialize the TAS file transfer information 

packets. 

Subroutines to Initialize File Transfer Packets 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 E-1


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

E-2 3787 3247-111


3787 3247-111 E-3


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The following example lists the subroutines to initialize the TAS mail transfer information 

packets. 

E-4 3787 3247-111

Subroutine to Initialize Mail Transfer Packets 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


3787 3247-111 E-5


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

E-6 3787 3247-111


3787 3247-111 E-7

Appendix F 

Register 

When you issue a Register command, the file name you enter with the command is 

converted into a file-id. TAS then checks the list of previously registered file-ids. This 

check determines if there already is a registered file-id that exactly matches the file-id that 

you want to register. 

In this comparison, a wild card indicator is treated as a normal character. Thus, wild card 

indicators must match corresponding wild card indicators for the file-ids to match. 

If TAS finds a match with a previously registered file name, the command is rejected; 

otherwise the new file name is included in the list of registered files. 

You must provide at least a qualifier and filename when registering a file. 

F.1. Converting a File Name to a File-ID 

TAS separates the submitted file name into seven parts to create the file-id. These are: 

Part Length 

Qualifier 1-12 chars 

filename 1v12 chars 

f-cycle 0v3chars 

read key 0v6chars 

write key 0v6chars 

element name 0v12 chars 

version 0v12 chars 

If the information submitted for a part is less than the maximum length for that part, TAS 

adds trailing blanks to expand the part to its maximum length. 

If a wild card character is provided as part of the Register command, TAS replaces all 

instances of that wild card character found in the file name with a wild card indicator 

(semicolon). If the wild card character is found as the last character in one of the parts, 

any remaining characters for that part will be stored as wild card indicators. 

3787 3247v111 Fv1

Converting a File Name to a File-ID 

Example 1: 

The following file name: 

 

is converted to file-id: 

 

 

 

Example 2: 

The following file name with "Z" indicated as a wild card: 

 

is converted to file-id: 

 

 

 

F-2 3787 3247-111

F.2. Incoming File Transfer 

F.2.1. Overview 

Incoming File Transfer 

When a file is transferred to the 2200 as a result of a PUT command from a remote FTP 

client, TAS converts the incoming file name to a file-id and checks to see if the incoming 

file-id matches a previously registered file-id. If a match is found, the run stream associated 

with the registered file-id is executed (Add or Start). 

F.2.2. Run Stream Selection 

To determine which run stream to initiate, a comparison is made between the incoming 

file-id and every registered file-id in the registered list to determine the best match. In this 

comparison, a wild card indicator in the registered file-id always matches its corresponding 

character in the incoming file-id. Consequently, more than one match may be found. 

An algorithm is used to determine the best match. It assumes that a match with a wild card 

indicator is not as good as a match with a character. 

All characters of a registered file-id are compared against the incoming file-id. If there is a 

mismatch, a new compare is started using the next registered file-id. If there is no 

mismatch, a comparison value is generated. After all registered file-ids are compared, the 

registered file-id with the highest comparison value is determined to be the best match. 

The run stream associated with this file-id is then executed. 

If two files have the same comparison value, the best match is determined by ranking the 

file-id parts in the following order (most important to least important): 

File-id Parts In Order Of Importance 

Qualifier 

Fillename 

F Cycle 

Element 

Read Key 

Write Key 

Version 

The file that has the higher comparison value for a file-id part (in the order of importance) 

is considered the best match. 

3787 3247-111 F-3


For example, if: 

File A and file B both have a total comparison value of 65 

File A and file B both have a QUALIFIER part comparison value of 12 

File A has a FILENAME part comparison value of 10 and file B has a FILENAME 

part comparison value of 8 

then file A is the best match. 

Example 

Assume that the file name received on a transfer command is: 

 

This is converted to the following file-id: 

 

 

 

Assume there are the following two previously registered file names: 

 

where B is a wild card. 

File 1 has the following file-id: 

 

 

 

 

where Z is a wild card. 

File 2 has the following file-id: 

 

 

 

F-4 3787 3247-111

The comparison values assigned to the file-id would then be: 

Part File 1 Values File 2 Values 

Qualifier 11 10 

Filename 8 12 

Element 2 12 

Cycle 3 3 

Read-Key 6 6 

Write-Key 6 6 

Element Name 12 12 

Element Version 12 12 

Total 60 73 


Both file-ids are acceptable, because the incoming file-id matches all the characters in both 

the registered file-ids. However, file 2 has a higher total comparison value (73) than file 1. 

File 2 is therefore the best match. 

3787 3247-111 F-5

Appendix G 

Deregister 

When a user issues the Deregister command, the optional keywords specified as part of the 

command determine the action that the command performs against files registered with 

the specified application-id. The optional keywords are: 

Keyword Description 

FILENAME Specifies the file name that you should use to find the 

file name or names to deregister. 

WILDCARD Specifies which character TAS should replace with a 

wild card indicator when it creates the deregister 

file-id. 

ALL Specifies whether or not TAS should deregister all 

matches or just an exact match. 

G.1. Deregistering File Names Associated with an 

Application-id 

To deregister file names associated with an application-id, set the keyword ALL to yes, and 

the FILENAME keyword to blanks. 

Example 

The registered files associated with application-id AAA are: 

 

 

 

 

 

 

 

 

The registered files associated with application-id BBG are: 

 

 

 

 

3787 3247-111 G-1

Deregistering File Names Associated with an Application-id 

 

 

 

 

The user’s Deregister command is: 

Application-id = AAA 

Filename = Blank 

Wild Card = Blank 

All = Yes 

The result is: 

Both entries under application-id AAA are removed. 

G-2 3787 3247-111

Deregistering File Names That Have No Associated Wildcard 

G.2. Deregistering File Names That Have No 

Associated Wildcard 

To deregister file names that have no associated wildcard, set the FILENAME keyword to 

the file name that you want to deregister, and the WILDCARD keyword to blanks. 

Example 


 

 

 

 

 

 

 

 


 

 

 

 

 

 

 

 

 

 

 

 


Application-id = BBG 

Filename = opt*abc.ggh 

Wild Card = Blank 

All = No 

3787 3247-111 G-3

Deregistering File Names That Have No Associated Wildcard 

The file-id generated from the Deregister command filename is: 

 

 

 


Only File 2 under application-id BBG is removed. 

G-4 3787 3247-111

Deregistering File Names That Match a Specified File Name 

G.3. Deregistering File Names That Match a 

Specified File Name 

To deregister file names that match a specified file name, set the FILENAME keyword to 

the file name that you want to deregister, the WILDCARD keyword to the wildcard 

character to be used to deregister a file, and the ALL keyword to yes. 

Example 


 

 

 

 

 

 

 

 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 G-5

Deregistering File Names That Match a Specified File Name 



Filename = Zbc*ZefZ 

Wild Card = Z 

All = Yes 


 

 

 


Files 1, 4, and 5 under application-id BBG are deregistered. 

G-6 3787 3247-111

Deregistering File Names That Were Registered With a Wildcard 

G.4. Deregistering File Names That Were 

Registered With a Wildcard 

To deregister file names that were registered with a wildcard, set the FILENAME keyword 

to the file name that you want to deregister, the WILDCARD keyword to the wildcard 

character to be used to deregister a file, and the ALL keyword to no. 

Example 


 

 

 

 

 

 

 

 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3787 3247-111 G-7

Deregistering File Names That Were Registered With a Wildcard 

 

 

 

 

 

 

 

 



Filename = Zbc*ZefZ 

Wild Card = Z 

All = No 


 

 

 


File 6 under application-id BBG is removed. 

G-8 3787 3247-111

Glossary 

A 

absolute 

An element type for an OS 2200 program file. An absolute element is an executable 

machine-language element produced by the OS 2200 collector from relocatable elements. 

absolute element 

An element containing a complete program in executable form. 

alphanumeric character string 

A string that contains letters, digits, special characters, and the space character. 

C 

checkpoint marker 

Coding used to indicate error recovery restart points in case of failure during data 

transmission. In an OSI environment, this is known as a serial point synchronization 

number. 

CMS 1100 

Communications management system; the system software program that provides all 

communications and network capabilities under OS 2200. 

collect 

collector 

To use the OS 2200 collector (MAP processor) to process object module elements and 

produce absolute elements. Collectand map are used synonymously in OS 2200 

documentation. 

The OS 2200 MAP processor, which processes object module elements and produces 

absolute elements. The collector is a component of the OS 2200 system control software. 

configuration 

The arrangement of a computer system or network as defined by the nature, number, and 

the chief characteristics of its functional units. The term may refer to a hardware or a 

software configuration. This can also refer to the devices and programs that make up a 

system, subsystem, or network. 

3787 3247-111 Glossary-1

Glossary 

D 

DCA 

DCP 

DDN 

See distributed communications architecture. 

See distributed communications processor. 

See defense data network. 

defense data network (DDN) 

Previous name for TAS. 

distributed communications architecture (DCA) 

The proprietary architecture for Unisys computer systems; the Unisys network 

architecture that draws together all aspects of the communications products by defining a 

set of logical concepts and rules (protocols and interfaces). These guidelines are used in 

the design of hardware, software, and network products. 

distributed communications processor (DCP) 

A programmable communications processor hardware unit that executes Telcon and DCP 

operating system (DCP/OS) software and serves as a communications subsystem that 

provides connections between hosts in a network; a modular communications processor 

that can be tailored to the needs of a broad range of users who implement Unisys 

distributed communications architecture. It performs the network management function, 

rather than the host. 

dump 

The contents of main storage at a particular moment, usually for a particular processor or 

program. A dump can be printed or placed in a mass storage or tape file. Specifically 

$ A formatted dump is a dump that has been processed then printed to present the main 

storage bits in an orderly or condensed manner that is easier for a person to read than 

a continuous series of 0 and 1 characters. 

$ An online dump occurs without interrupting execution of the system, processor, or 

program. 

$ An automatic dump can occur when the system, processor, or program terminates 

abnormally due to an error. 

Glossary-2 3787 3247-111

H 

Glossary 

heterogeneous network 

A network comprised of hosts using different operating systems; in this case, both OS 2200 

and non-OS 2200 hosts. 

homogeneous network 

A network comprised of hosts using the same operating systems; in this case, OS 2200 

systems. 

host 

host id 

I 

interface 

A computer system, personal computer, or work station connected to a data transmission 

facility (a data transmission network in the case of DDP) that executes application or 

system programs on behalf of its users. 

The identifier for a local or remote host in the network, defined in the TCP/IP configuration 

and specified in internet physical address format or in logical host name format. 

A facility provided by a software product to enable a computer user or program to use the 

product or exchange input and output with the product. 

internet physical address 

A host-id specified in a format that consists of a network number, a host number, and an 

interface message processor number, each separated by a hyphen or period. Often 

associated with a logical host name for ease of use. 

L 

LAN 

See local area network. 

local area network (LAN) 

A data communications network with high-speed communications capabilities. 

local host 

The host to which you are physically attached. 

logical host name 

A descriptive, easy-to-use host-id that is associated with, and translates to, an internet 

physical address. For example, three hosts at a site in New York could be given the logical 

host names of NY01, NY02, and NY03. 

3787 3247-111 Glossary-3

Glossary 

N 

network 

O 

omnibus 

Two or more independent computers (hosts) that are logically or geographically separated 

and electronically linked by data communications devices for the purpose of exchanging 

information. 

An element type for an OS 2200 program file. Programmers specify an omnibus element 

type when absolute, relocatable, or symbolic is not appropriate. 

object module element 

An element containing part of a program in a form that is combined with other object 

module elements to produce an executable program (output object module element). An 

object module element is the output of a language processor. 

P 

packet switching 

A data conversion routine usually used in public data networks to split a message into 

uniformly sized packets for transmission and restored at the destination to its original form. 

PDN 

See public data network. 

program-callable interface 

Software routines that enable a software product to exchange input and output with a 

program written in a particular programming language. These routines consist of a limited 

set of statements or function calls that are compatible with the programming language. 

protocol 

A set of rules which controls network communication by defining the structure, content, 

sequencing procedures, and error detection and recovery techniques for data transmission. 

public data network (PDN) 

A network of line connections to various points furnished by a regulated carrier such as a 

telephone company. A communication network developed for the transmission of data and 

usually made accessible only to subscribers who share the network. 

Glossary-4 3787 3247-111

Q 

qualifier 

R 

A prefix for a file name on an OS 2200 system. An asterisk (*) character separates the 

qualifier and the rest of the file name. 

remote host 

Any host in the network other than the one to which you are physically attached. 

run stream (runstream) 

A series of OS 2200 executive control language statements and any input, data, 

or programs associated with them. 

S 

SDF 

session 

See system data format. 

Glossary 

A logical connection between two network-addressable units (termination systems, end 

users, etc.) that can be activated, tailored to provide various protocols, and deactivated, as 

requested. The session activation request and response can determine options for the rate 

and concurrency of data exchange, the control of contention and error recovery, and the 

characteristics of the data stream. Sessions compete for network resources, such as the 

links within the path control network. 

source host 

The host that sends a file or records in any transfer operation. 

symbolic element 

An element type for an OS 2200 program file. A symbolic element can contain a source 

program or subprogram written in a programming language, directives to an OS 2200 

software processor, executive control language statements, or input for a program or 

OS 2200 software processor. Symbolic elements contain text in system data format (SDF). 

Typically, OS 2200 text editors create symbolic elements. 

system data format (SDF) 

A sequential record format used by OS 2200 software for store data. SDF recognizes data 

records and control records. Data records contain the data (the text of a record, for 

example). Control records provide special control information about the data, such as line 

numbers, page, and size. Symbolic elements are assumed to use SDF. 

3787 3247-111 Glossary-5

Glossary 

T 

TCP/IP 

Telcon 

TIP 

See transmission control protocol/internet protocol. 

A Unisys program product that is a distributed communications operating system for 

implementation of distributed communications architecture (DCA). The software resides 

and executes in a distributed communications processor (DCP). 

Transaction processing; allows the execution of transaction processing programs. These 

programs may be written in assembler language or in a high-level compiler language. OS 

2200 TIP provides a general transaction processing capability that allows a remote terminal 

operator to initiate the execution of a preregistered program at the central computer site. 

Once in execution, the transaction program has access to the full capabilities of the OS 

2200 executive system, as well as to the specialized capabilities and services of TIP. 

transmission control protocol/internet protocol 

Called TCP/IP, this is a set of data transmission protocols originally defined for the United 

States Department of Defense data network. This is now a widely used transmission 

protocol and is not limited to use by the Department of Defense. 

U 

Universal Compiling System (UCS) FORTRAN 

The FORTRAN programming language used to write programs for the OS 2200 Universal 

Compiling System (UCS) FORTRAN compiler (UFTN). Symbolic elements written in the 

FORTRAN language, then compiled by the UCS FORTRAN compiler, produce output 

object module elements. 

UDLC 

Seeuniversal data link control. 

universal data link control 

The Unisys line control method for data transfer over communication lines. 

user name 

A 1- to 20-character name that identifies you on your host. 

Glossary-6 3787 3247-111

X 

Glossary 

X.25 public data network 

A packet-switched public data network that conforms to Consultative Committee for 

International Telegraph and Telephone (CCITT) standard X.25, which defines a protocol 

for communication between packet-switched public data networks and devices operating 

in packet-switched mode. 

3787 3247-111 Glossary-7

Bibliography 

OS 1100 Universal Compiling System (UCS) FORTRAN Programming Reference 

Manual (7830 7477). Unisys Corporation. 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface C Language 

Programming Guide (3787 3254). Unisys Corporation. 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface COBOL 


OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface FORTRAN 


OS 2200 Distributed Data Processing (DDP-PPC/DDP-FJT) Messages Reference Manual 

(3787 3528). Unisys Corporation. 

OS 2200 Interactive Processing Facility (IPF 1100) Command Language Operations 

Guide (7833 3788). Unisys Corporation. 

OS 2200 TCP/IP Application Services (TAS) C Language Programming Guide 


OS 2200 TCP/IP Application Services (TAS) COBOL Programming Guide (3787 3205). 

Unisys Corporation. 

OS 2200 TCP/IP Application Services (TAS) File Transfer User Guide (3787 3213). 


OS 2200 TCP/IP Application Services (TAS) Installation and Administration Guide 


OS 2200 TCP/IP Application Services (TAS) Mail Processor User Guide (3787 3239). 


3787 3247-111 Bibliography-1

TCP/IP App. Services (TAS) FORTRAN Programming Guide

Create successful ePaper yourself

Delete template?

Save as template?