gtps2m3eACF/SNA Data Communications Reference

3614/3624 Message Processing

The 3614 and 3624 Consumer Transaction Facilities are unattended self-service banking terminals. Both issue money, accept deposits, and perform various banking transactions. These units can be attached to TPF via a 37x5 communications controller or "loop" attached via a finance communication controller. Loop attachment refers to an intermediate connection (in this case, the finance controller) in the communications path. TPF cannot distinguish direct attachments from loop attachments. Therefore, applications residing in the finance controller must present a directly attached appearance.

The protocol for a 3614/3624 logical unit is unique. These logical units do not request "exception response" as do other units. Prior SNA terminology defined the 3614/3624 response as "exception reached recovery node (RRN)." Today, however, this response is generally accepted to mean a positive response (+RSP). Input messages from and output messages to a 3614 or 3624 may not be chained.

Communication between a 3614/3624 and the host typically consists of three messages. Such a sequence ends with the 3614/3624 status being sent to the host application.

                3614  or 3624               TPF
 
Transaction Request ---------->
 
                    <---------- Transaction Reply
 
Transaction Status  ---------->
 
                    <---+RRN---

3614/3624 logical units are identified during network definition. These units must be defined as multi-thread, non-recoverable. Bracket protocol is not supported for 3614/3624 logical units, nor are these units permitted to receive unsolicited messages.

3614/3624 Session Initiation and Application Considerations

TPF and 3614/3624 logical units must establish a session before data can be transmitted. Prior to session initiation, the 3614/3624 must be loaded with the "configuration image." This is a component of the IBM 3600 finance communication system. The configuration image is a combination of: 1) formatted configuration data, and 2) selected modules of financial controller data. When loaded, the configuration image defines the operations of the 3614/3624. Once the 3614/3624 is loaded, a session can be initiated.

Host applications use the ROUTC macro to send data to the 3614/3624.

TPF does not examine output data; the data content and format is not validated. Data transmitted between a 3614/3624 and a TPF application are encrypted. The CIFRC macro is used to encrypt and/or decrypt data. TPF applications issue these 3614/3624 commands:

       Change key -  Changes the encryption key
            Close -  Closes the 3614/3624
          Inquiry -  Retrieves the stored status of 3614/3624
             Open -  Opens the 3614/3624
     Request load -  Loads a new 3614/3624 configuration image
 Request recovery -  Retrieves the current transaction status
          Set key -  Sets a new encryption key
 

See the 3600 Finance Communication System 3614 Programmer's Guide and Reference and 3600 Finance Communication System 3624 Programmer's Guide for additional information.