Data Management Library Introduction to TRANSFER Delivery System Abstract This manual is an overview of the TRANSFER delivery system and the PS MAIL application. Product Version C30 Supported Releases This manual supports C30 and all subsequent releases until otherwise indicated in a new edition. Part Number Edition Published Release ID 109426 Fifth January 1995 D30.
Document History Edition Part Number Product Version Earliest Supported Release Published First 82323 A00 -- N/A June 1982 Second 82323 B00 -- N/A April 1983 Third 82323 C00 -- N/A December 1983 Fourth 31979 C30 A03/E04 July 1991 Fifth* 109426 C30 A03/E04 January 1995 New editions incorporate any updates issued since the previous edition.
Contents About This Manual vii 1. The TRANSFER Delivery System Overview 1 What TRANSFER Does for You 4 Managing the Flow of Information 4 Distributing Transactions over a Period of Time 6 TRANSFER Applications 7 TRANSFER and Tandem Software 10 GUARDIAN 90 and EXPAND—Distributed Processing 10 GUARDIAN 90 10 EXPAND 12 PATHWAY—Online Transaction Processing 13 TMF—Transaction Monitoring for Database Consistency 16 TRANSFER—Package Transport 17 Summary of the TRANSFER Delivery System 20 2.
. The TRANSFER Environment Contents How You Use PS MAIL 6530 5 PS MAIL Profiles 7 PS MAIL Messages and Attachments 8 PS MAIL and Agents 9 4. The TRANSFER Environment Overview 1 Installing TRANSFER 2 Starting and Stopping TRANSFER 3 Administering TRANSFER with ADMIN 4 Managing TRANSFER with TMANAGER 5 Monitoring the System 6 5.
Contents Figure 2-8. Figure 3-1. Figure 3-2. Figure 3-3. Figure 5-1. 5.
5.
About This Manual This manual introduces the TRANSFER delivery system for the Tandem NonStop computer systems, describing the major features of TRANSFER and presenting an overview of the software products used with TRANSFER. Several other publications contain more detailed information of interest to TRANSFER users.
About This Manual Manuals that discuss Tandem networking products for your TRANSFER system include the following: ■ The EXPAND Reference Manual describes Tandem’s NonStop network that extends fault-tolerant operation to networks of geographically distributed NonStop systems.
1 The TRANSFER Delivery System Overview The TRANSFER delivery system is a high-level software product that supports communications between people, input-output (I/O) devices, and running programs referred to as processes. TRANSFER provides a set of processes that build, maintain, and route packages of data to requesting applications. A TRANSFER package is a collection of information.
Overview The TRANSFER Delivery System Figure 1-1.
The TRANSFER Delivery System Overview Along with the set of processes that build, maintain, and route packages of data for requesting applications, the TRANSFER product includes: ■ ADMIN, an application that lets administrators perform administrative tasks for correspondents, interest groups, distribution lists, folders, and the TRANSFER system ■ TMANAGER, an application that allows system managers to monitor and manage a TRANSFER delivery system Additionally, a TRANSFER system can include: ■ Other a
What TRANSFER Does for You The TRANSFER Delivery System What TRANSFER Does for You TRANSFER satisfies two important data management needs: the need to manage the flow of information in a business and the need to distribute transactions over an extended period of time. Managing the Flow of Information Whether a business has one small office and a handful of employees or hundreds of sites and several thousand employees, it must have ready access to correct information to make decisions.
The TRANSFER Delivery System Managing the Flow of Information Figure 1-2. A Community of Applications 2 1 Sales 3 Manufacturing 5 Purchasing 4 Legend 1 Sales receives an order. 2 Sales asks Manufacturing to fill it on a schedule: three units by January 1, five more by June 1, and so on. 3 Manufacturing requests that parts be available to satisfy the build schedule. 4 Purchasing notifies Manufacturing that the parts are available. 5 Manufacturing notifies Sales that the order has been filled.
Distributing Transactions over a Period of Time The TRANSFER Delivery System Distributing Transactions over a Period of Time The exchange of a package between a sender and a recipient is a transaction. In a typical interactive transaction processing system, an operator starts a transaction at a terminal and must wait for the transaction to complete before going on to the next transaction. Often it is not feasible, however, for a transaction to complete right away.
The TRANSFER Delivery System TRANSFER Applications TRANSFER Applications A TRANSFER application is a group of processes or PATHWAY online transaction processing systems that use TRANSFER to communicate with each other. Tandem provides several electronic mail applications: PS MAIL for Tandem 6530 terminals (or terminal emulators), PS MAIL for IBM 3270 terminals, and PS MAIL for TTY terminals. You can write extensions to your PS MAIL application to satisfy your particular package delivery requirements.
TRANSFER Applications ■ The TRANSFER Delivery System Receive notice of incoming packages Either a SCREEN COBOL program unit or a user-written server can be notified when a package arrives. The process that delivers the package notifies a SCREEN COBOL program by calling it or notifies a server by issuing a SEND to it. You can have different program units or servers receive notifications under different conditions.
The TRANSFER Delivery System TRANSFER Applications Figure 1-3.
TRANSFER and Tandem Software The TRANSFER Delivery System TRANSFER and Tandem Software By providing high-level package delivery and ways to distribute transactions over an extended period of time, TRANSFER builds upon and enhances the capabilities of other Tandem software.
The TRANSFER Delivery System GUARDIAN 90 and EXPAND—Distributed Processing Figure 1-4. Interprocess Communication Issue Request B (Server) A Request Outstanding— Do This Update Process A gathers data in the form of a request from the terminal and delivers the request to Process B. Process A is the requester. Process B receives the request and, acting as the server, examines the contents and decides to request calls for an update to the database.
GUARDIAN 90 and EXPAND—Distributed Processing The TRANSFER Delivery System As shown in Figure 1-5, to direct an I/O request to a device, a process makes a file system request and specifies the name of the device. If the device is a disk, the name of the disk is further qualified by subvolume and file names. If the device is a terminal on a multipoint line, the name of the line is qualified by a subdevice name. Figure 1-5.
The TRANSFER Delivery System PATHWAY—Online Transaction Processing PATHWAY—Online Transaction Processing PATHWAY is both an operating environment and a development tool for online transaction processing applications. In the PATHWAY environment, applications are divided into requesters and servers. PATHWAY establishes the framework for creating requesters and servers and then manages them.
PATHWAY—Online Transaction Processing The TRANSFER Delivery System Figure 1-6. Requesters and Servers in PATHWAY Requester Display to Screen Application Requester Server Accept Input Send to Server Receive Reply From Server Read Server Class A Application and Database Logic ENSCRIBE Requester Requester Server Class B Server Class C NonStop SQL Reply S8123-006 PATHWAY solves several problems for the programmer: ■ PATHWAY provides a model for dividing the work of an application.
The TRANSFER Delivery System PATHWAY—Online Transaction Processing Figure 1-7.
TMF—Transaction Monitoring for Database Consistency The TRANSFER Delivery System TMF—Transaction Monitoring for Database Consistency TMF lets an application ensure the consistency of a database, even if there is a hardware or software failure or a system crash. TMF also protects the consistency of data by allowing only one transaction, from one application, to modify particular data at one time. Consistency becomes an issue when a transaction attempts to make multiple changes in a database.
The TRANSFER Delivery System TRANSFER—Package Transport TRANSFER—Package Transport A Tandem network comprises processors, disks, terminals, and communication equipment.
TRANSFER—Package Transport The TRANSFER Delivery System Figure 1-9.
The TRANSFER Delivery System TRANSFER—Package Transport With the X400 gateway, TRANSFER capabilities are extended beyond Tandem systems. Users on a Tandem system can exchange packages with users of X.400-based messaging systems on hosts other than Tandem systems via the gateway. Figure 1-10 shows how different host systems with different messaging systems based on the X.400 standards are integrated through the TRANSFER X400 gateway. Figure 1-10.
Summary of the TRANSFER Delivery System The TRANSFER Delivery System Summary of the TRANSFER Delivery System In summary, with the Tandem TRANSFER delivery system, you are ensured of: ■ Geographic independence TRANSFER lets you define a group of correspondents who can be on a single system or on any network node where TRANSFER is installed. With one request to TRANSFER, a process can send a package to multiple destinations anywhere in an EXPAND network.
The TRANSFER Delivery System ■ Summary of the TRANSFER Delivery System Integrated data management A group of applications that use TRANSFER to coordinate their work form a single TRANSFER application.
Summary of the TRANSFER Delivery System 1-22 The TRANSFER Delivery System 109426—Introduction to TRANSFER Delivery System
2 The TRANSFER Environment Overview A TRANSFER system can be described as a community of users—or correspondents— and as a means for them to exchange information. To let correspondents communicate, TRANSFER provides these basic functions: ■ TRANSFER keeps a name directory, providing a means for correspondents to identify themselves and other correspondents. ■ TRANSFER maintains a holding area for packages and parts of packages, giving correspondents a place and a way to assemble and receive packages.
Correspondents The TRANSFER Environment Correspondents A correspondent is a sender and receiver of packages. Correspondents can be: ■ People: Electronic mail lets people send packages to each other. ■ Processes: A requester process at one node can send a package to a server process at another node. For example, a process in an order-entry application might send data to a process in an inventory application. ■ Devices: A reporting process might send the same report to several output devices.
The TRANSFER Environment Depots Depots A depot is that part of the TRANSFER database that belongs to a specific correspondent. The depot is established when the system administrator registers the correspondent name with TRANSFER. Every correspondent has one depot. A depot serves two purposes: ■ The depot describes the correspondent to TRANSFER and to applications. ■ The depot gives the correspondent a way to store, organize, and create packages. Figure 2-1 depicts a depot.
Depots The TRANSFER Environment Figure 2-1.
The TRANSFER Environment Profiles Profiles A profile is a set of records describing a correspondent or interest group. Every depot has a TRANSFER profile that contains identifying data, such as the password and operating environment parameters for the correspondent or group. The profile also indicates the privileges of the correspondent or group member. Every depot has a mail profile that contains information related to the PS MAIL application that the correspondent or group member uses.
Distribution Lists The TRANSFER Environment Distribution Lists A distribution list is a predefined list of recipient names. A recipient name can be the name of a correspondent, of a group, or of another distribution list. Distribution lists provide a simple method for a correspondent to send a package to multiple recipients.
The TRANSFER Environment Folders Folders A folder is a place to store related items and packages. A correspondent might keep separate folders for packages received from different sources or group similar packages from various correspondents in a single folder. A correspondent uses the ADMIN application or a user-written application to create new folders. The correspondent who creates a folder owns the folder.
Folders ■ The TRANSFER Environment WASTEBASKET folder When a PS MAIL correspondent specifies that an item is to be deleted, the item goes into a folder named WASTEBASKET that is assigned for each TRANSFER session. At the end of the TRANSFER session, the WASTEBASKET is automatically emptied, deleting the items. A correspondent who mistakenly deletes an item can retrieve that item from the WASTEBASKET before the end of the session.
The TRANSFER Environment Items Items An item is a collection of data such as ASCII text, binary data, or some other type of data defined by the application. An item can also have other items attached to it, including external objects. External objects are GUARDIAN 90 files that are kept as GUARDIAN 90 files, external to the TRANSFER database, which can be attached to a TRANSFER item and transported. Correspondents create items and can add to, delete, and change the contents of the items they create.
Packages The TRANSFER Environment Packages A package is a collection of information that can be sent from one correspondent to other correspondents. Correspondents assemble items into packages so that TRANSFER can move the packages from one depot to another. TRANSFER builds a package when a user creates a package header item and makes separate requests to add recipients, data, component items, and delivery parameters. Only the correspondent who creates the package header item can modify the package.
The TRANSFER Environment Packages Figure 2-3. A Package Package Header Item ID 412 Package Header Sender's Correspondent Name Date and Time Delivery Parameters Recipient List Data Component List Item ID 93 Item ID 8 Item ID 8 Package Header Item ID 93 Component List Item ID 744 Sender's Correspondent Name Item ID 106 Date and Time Delivery Parameters Recipient List Data Item ID 744 Item ID 106 Memo to John From Jim 0100101110100 0101101000101 In response to your letter of July 19, 1991...
The Way Depots Work The TRANSFER Environment The Way Depots Work Although TRANSFER correspondents care only about the external representation of the data in their depots, programmers and system managers who are concerned with the size of their database need to understand the internal structure of a depot. What does it really mean for a profile or folder to be in a depot or for a package to be in a folder? A depot is not a single file. TRANSFER assigns unique IDs to depots, folders, and items.
The TRANSFER Environment The Way Depots Work Figure 2-4.
Depot Security The TRANSFER Environment Depot Security TRANSFER protects the information in a depot from unauthorized access.
The TRANSFER Environment Wild-Card Names and Patterns Wild-Card Names and Patterns To save time and typing, a user can abbreviate correspondent names, distribution list names, and folder names, as long as the abbreviated name identifies only one correspondent, distribution list, or folder. A correspondent abbreviates a name by using a question mark (?) in place of a single character or an asterisk (*) in place of zero or more characters in the name. Such an abbreviated name is a wild-card name.
TRANSFER Processes The TRANSFER Environment TRANSFER Processes The processes in a TRANSFER system are clients, servers, TRANSFER asynchronous processes, and agents. Clients Clients are requester processes that provide the interface between correspondents and TRANSFER. Tandem supplies certain clients, such as the electronic mail applications—PS MAIL 6530, PS MAIL 3270, and PS MAIL TTY—and customers can develop their own clients. Clients allow the correspondent to interact with TRANSFER.
The TRANSFER Environment Servers Figure 2-5. Menu Screen of Client Functions YOUR MAIL CLIENT --Function Menu-- Press the key for the task you want to do: F3 F5 F7 F8 F9 F15 SF16 --Scan your mail --Read your mail --Create a message --Get a list of correspondents --Get a list of your folders --Get help for other tasks --Logoff S8123-023 Servers Servers provide the interface between requesters and the TRANSFER database, handling all work involved in accessing the TRANSFER database.
TRANSFER Asynchronous Processes The TRANSFER Environment TRANSFER Asynchronous Processes TRANSFER asynchronous processes schedule packages for delivery, route packages to the appropriate recipients, and deliver packages within the time specified by the sender. If a network node is unavailable, the processes ensure that packages destined for the node are delivered as soon as the node becomes available. The TRANSFER asynchronous processes also cancel packages and arrange for their expiration.
The TRANSFER Environment TRANSFER Asynchronous Processes Figure 2-6.
Agents The TRANSFER Environment Agents Applications that use TRANSFER can include agents. An agent is a program that is invoked by a TRANSFER asynchronous process when a package arrives at a depot. Tandem supplies two agents with its ADMIN application. ■ The vacation agent handles messages for a correspondent who is away from the terminal for an extended period of time. ■ The print-on-delivery agent automatically sends incoming packages to a specified printer.
The TRANSFER Environment Agents An agent can react to package delivery by: ■ Informing the correspondent that a package has arrived ■ Saving the package automatically in a folder at the depot ■ Filtering incoming packages; for example, sorting mail into first, second, and third class messages ■ Initiating a transaction (The arriving package can be a trigger to start a transaction or a signal that a prerequisite transaction has been completed.
Sessions The TRANSFER Environment Sessions Before a requester can access a depot to build, send, or receive packages or to do other work for a correspondent, the requester must establish a session between the correspondent and TRANSFER. A session starts when a correspondent logs on and begins communicating with TRANSFER and terminates when the correspondent logs off and ends that communication. A correspondent can have multiple sessions running at one time.
The TRANSFER Environment Sessions Figure 2-8. What Sessions Include User-initiated session The session includes work done by the applications and by the TRANSFER user interface. TRANSFER Interactive Server Requester Depot WASTEBASKET TRANSFER-initiated session The session includes package delivery and agent invocation. TRANSFER Asynchronous Processes The recipient might or might not have a session in progress.
Sessions 2-24 The TRANSFER Environment 109426—Introduction to TRANSFER Delivery System
3 PS MAIL Overview The PS MAIL 6530 application, which is supplied with TRANSFER, provides a way for a business to automate its interoffice correspondence. Using the underlying TRANSFER delivery system, PS MAIL lets correspondents communicate electronically whether at the same node, at different nodes in an EXPAND network, or—through the X400 gateway—on other host systems that support X.400 messaging system standards. PS MAIL correspondents exchange mail that consists of ASCII text.
The Electronic Desk PS MAIL Besides being an effective product for almost any business, PS MAIL acts as a model application in a TRANSFER installation. To application designers, PS MAIL offers an example of how to use TRANSFER for business applications. For people involved in application management and operations, PS MAIL is a good pilot application for developing operating procedures and practicing resource management. The Electronic Desk The correspondent sees the depot as an electronic desk.
PS MAIL The Electronic Desk Figure 3-1.
The Electronic Desk PS MAIL As illustrated in Figure 3-2, when a PS MAIL correspondent creates and sends a message, a copy of that message is automatically filed in the OUTLOG. Figure 3-2.
PS MAIL How You Use PS MAIL 6530 How You Use PS MAIL 6530 The user interface to PS MAIL 6530 consists of a set of screens. Each screen is associated with a function, including reading mail from the INBOX, scanning the contents of a folder, composing a message, sending mail for delivery to other correspondents, filing mail in folders, and discarding mail into the WASTEBASKET. A correspondent types any required information and then presses a function key to tell PS MAIL to perform the function.
How You Use PS MAIL 6530 PS MAIL Figure 3-3. Using PS MAIL 6530 SMITH-SUSAN 1 Susan Smith logs on by typing her correspondent name and password on the LOGON screen, then presses F1, the SCAN key. 2 The SCAN screen appears and displays the date, time, sender, and subject of each piece of mail in Susan’s INBOX. 3 Susan positions the cursor on the entry from Mary and presses F2, the READ key. 4 The READ screen appears and displays the message from Mary. Susan presses F4, the REPLY key.
PS MAIL PS MAIL Profiles PS MAIL Profiles Each depot includes a PS MAIL profile for the correspondent or group. The profile is created when the correspondent is registered by a system administrator.
PS MAIL Messages and Attachments PS MAIL PS MAIL Messages and Attachments TRANSFER packages in PS MAIL consist of messages and attachments. Each message resembles a business memo, having a heading and a body.
PS MAIL PS MAIL and Agents PS MAIL and Agents The PS MAIL application can take advantage of two agents that Tandem provides with TRANSFER. ■ A vacation agent can be set up for any depot to handle incoming messages when a correspondent is unavailable for an extended period of time.
PS MAIL and Agents 3-10 PS MAIL 109426—Introduction to TRANSFER Delivery System
4 The TRANSFER Environment Overview TRANSFER system management and administration involves the following tasks: ■ Setting up the hardware and software configurations required to run TRANSFER ■ Starting and stopping TRANSFER and the applications that use it ■ Continuing administration and operations, such as determining problems, tuning, and taking online dumps of database files Each installation has at least one system administrator, who is responsible for registering new correspondents with TRANSFE
Installing TRANSFER The TRANSFER Environment Installing TRANSFER TRANSFER includes the procedures that you use to install your delivery system. Your TRANSFER system comprises Base TRANSFER and other optional components, such as a PS MAIL application, the X400 gateway, or the Queue Manager. Base TRANSFER provides the set of processes that control communications within the TRANSFER environment and data files that contain information TRANSFER needs to service requests for package delivery.
The TRANSFER Environment Starting and Stopping TRANSFER Starting and Stopping TRANSFER You start your TRANSFER system with the XCOOL file, which starts the PATHWAY system that includes TRANSFER. You then use the ADMIN application to set up depots for correspondents and to change parameters, if necessary, for TRANSFER and its applications. You shut down a TRANSFER system by running the XSTOP program to shut down the PATHWAY system at each node.
Administering TRANSFER with ADMIN The TRANSFER Environment Administering TRANSFER with ADMIN The ADMIN application, which is included with TRANSFER, provides a set of screens that allow system administrators to perform administrative tasks for correspondents, interest groups, folders, and distribution lists. The application also lets correspondents change parts of their own profiles.
The TRANSFER Environment Managing TRANSFER with TMANAGER Managing TRANSFER with TMANAGER Tandem supplies the TMANAGER application to help system managers manage their systems and their resources. TMANAGER consists of three parts: ■ The TMANAGER screen interface, which gives you a set of screens for doing a variety of tasks in managing TRANSFER The TMANAGER application provides monitoring, log control, and tracing capabilities at the local node.
Monitoring the System The TRANSFER Environment Monitoring the System System managers and operators routinely use several Tandem products to monitor the TRANSFER delivery system. Tandem provides the tools to check the following: ■ PATHWAY environment PATHCOM, the PATHWAY command interface, allows you to monitor activity in a PATHWAY system, to stop terminals and processes when problems arise, to perform online load balancing, and to make temporary configuration changes.
5 Developing TRANSFER Applications Overview TRANSFER is ideal for a variety of applications that require package delivery, especially across a network, or that need transactions to be staged over time, such as: ■ Exchanging information among people; for example, interoffice mail ■ Delivering packages to multiple destinations; for example, wire service releases, corporate newsletters, or surveys ■ Moving among different kinds of applications; for example, communicating between a manufacturing system and
Deciding to Use TRANSFER Applications Developing TRANSFER Applications Deciding to Use TRANSFER Applications With all its versatility and efficiency, there are times when you might decide not to use TRANSFER. Depending on traffic, priorities, processor load, and network availability, TRANSFER cannot always guarantee that a package will arrive at a precise time. The narrower the timeframes specified for packages, the greater the chance that external factors can prevent on-time delivery.
Developing TRANSFER Applications Sample TRANSFER Application Developing Agents An agent is a program that is invoked by a TRANSFER asynchronous process when a package arrives at a depot. With the exception of the vacation agent and the print-ondelivery agent, which are supplied by Tandem, all agents are user-written. An agent can be a SCREEN COBOL requester program or a PATHWAY server.
Sample TRANSFER Application Developing TRANSFER Applications Figure 5-1.
Developing TRANSFER Applications Sample TRANSFER Application 4. At the warehouse the Inventory Control application receives the sales order and sends a request to generate a pick ticket on December 13. (On December 13 the pick ticket will be attached to the cream armchair, which will be loaded on a truck and delivered to Kate Chopin’s house on December 14.) The transaction to generate the pick ticket extends until the ticket is generated and arrives at Inventory Control on December 14. 5.
Sample TRANSFER Application 5-6 Developing TRANSFER Applications 109426—Introduction to TRANSFER Delivery System
Glossary ADMIN application. A TRANSFER application that allows administrators to perform administrative tasks for correspondents, interest groups, distribution lists, folders, and the TRANSFER system. ADMIN can be either accessed by a user-developed SCREEN COBOL module that interfaces with PS MAIL 6530 and PS MAIL 3270 or run as a standalone PATHWAY program. Agent.
Depot Glossary Depot. That part of the TRANSFER database associated with a particular correspondent or interest group. A private depot is privately owned by an individual correspondent, and a group depot is shared among all the correspondents belonging to the interest group associated with that depot. A depot includes the profiles, folders, and distribution lists that belong to the correspondent or interest group.
Glossary Process Item. A collection of data such as text, ASCII data, binary data, or some other type defined by the application. A simple item is an item with no other items connected to it; a component item is an item that is attached to a tree—other items that each can be simple or component. Local correspondent. A correspondent at the same node. Mail profile. A depot profile that contains parameters used during mail sessions initiated by the correspondent. Member.
Profile Glossary Profile. A collection of attributes that describes an individual depot, a group depot, or the system as a whole. Each depot has a TRANSFER correspondent profile and a mail profile. Any depot can also include one or more agent profiles and user-supplied profiles. In TRANSFER the attributes of the depot specified in the correspondent or group profiles are limited by the attributes that control the system, which are configured for the TRANSFER system-control profiles by the system manager.
Glossary TRANSFER database Server. Part of an application that deals with the database, handling everything related to the application computations and database access. Server class. A grouping of duplicate copies of a single server program; server processes within the class have identical attributes. Server process. A process that implements application requests and sends replies to the requester; synonymous with Server. Session.
TRANSFER delivery system Glossary TRANSFER delivery system. An information delivery system that enables organizations to move and manage information efficiently within a single Tandem system or across a network of distributed systems. TRANSFER supports communications between people, input-output devices, and processes. TRANSFER Interactive Server (TISERV). A TRANSFER server that starts and terminates sessions, services item- and package-handling requests, and implements administrative requests.
Index A B ADMIN accessing 4 and SCREEN COBOL 4, 2 defined 3 part of Base TRANSFER 2, 4 screens 4 to add distribution list 6, 4 to add folder 7, 4 to administer depot storage 4 to administer system 8, 4 to change parameters 3 to configure agent 9 to configure profile 4 to register correspondent 2, 4 to set up depot 3, 4 Administering TRANSFER system 4 Administrative privileges 14 Agent and incoming package 20 configuring 9 defined 20, 3 developing 3 functions 21 multiple 21 PATHWAY server 3 print-on-delive
E Definition programs 2 Depot administering 4 agent assigned 21 contents 3 defined 3 group 3 ID 12 security 14 setting up 3 structure 12 Depot storage statistics 4 Developing TRANSFER applications agents 3 clients 2 considerations 2 what TRANSFER does 1 what your application does 1 when not to use 2 when to use 1, 2 Distributed processing 10, 21 Distributed transactions, options 6 Distribution list abbreviating name 15 access 6 adding members 6 administering 4 creating 6 defined 6 deleting members 6 MEMBER
Index Initializing TRANSFER, XCNFG program 2 Installation definition 2 initialization 2 redefinition 2 start 2, 3 stop 2 Interest group 2, 1 Item attachment 9 defined 9 ID 12 L Load balancing 14 Locking records 16 M MEASURE 6 Messages See PS MAIL N Name directory 1, 2, 22 National language support 1 NETMON 6 Network and TRANSFER 17/19 and X400 gateway 19 defined 17 monitoring 6 O OUTLOG 7, 2, 4 P Package and agent 20 Introduction to TRANSFER Delivery System—109426 P assembling 10 canceling 7 certif
Q administering 4 changing 7 defined 5 mail 5, 7 TRANSFER 7 user-written 5 PS MAIL advantages 1 and GUARDIAN 90 file 8 and PC file 8 and SCREEN COBOL 2 and X400 gateway 1 as model application 2 attachments 8 bulletin board 1 composing a message 8 correspondent-created folders 2 courtesy copy 8 defined 3 delivery time 8 electronic desk 2 expiration 8 folder order 7 forward 8, 9 INBOX 2 incoming message 2 interest group 1 message body 8 message heading 8 outgoing message 4 OUTLOG 2, 4 printer 7 print-on-deli
Index to develop TRANSFER application 7/8 SEND statement in PATHWAY 13 in TRANSFER application 7/8 Server agent 3 available languages 13 class 14 defined 7, 13 GUARDIAN 90 10/12 in TRANSFER application 7/8 interface between requester and TRANSFER database 17 multiple 17 PATHWAY 13/16 TISERV 17, 18, 22 used by asynchronous processes 17 Session defined 22 multiple 22 TRANSFER initiated 22 user-initiated 22 what it includes 22 SMSERV 5 Software with TRANSFER 10 Starting TRANSFER, XCOOL program 2, 3 Stopping T
V monitoring 6 TMFCOM 6 transaction 16 TRANSFER application ADMIN 3, 8, 4 Courier 3 defined 7 developing 1/5 PS MAIL 3, 7, 17, 1/9 Queue Manager 3 sample 3/5 TMANAGER 3, 8, 5 typical 7 user-written 3, 7/8, 17 X400 gateway 3, 19 TRANSFER delivery system advantages 1, 17, 20/21 components 2 customizing 2 database 12 defined 1 defining a system 2 envelope 17 functions 1 initializing a system 2 installation 2 monitoring 6 package transport 17/19, 20 redefining a system 2 starting a system 2, 3 stopping a syste
