Electronic Data Interchange (EDI) Guide

Introduction to Electronic Data Interchange (EDI)

Every business uses information of one sort or another to receive orders, send bills, make collections, pay bills, move goods, and manage its money. The information connections most frequently used to achieve these connections are the postal service and the telephone. A relatively new connection option is through electronic data communications facilities or electronic data interchange (EDI).

Electronic data interchange is the direct computer exchange of standard business info such as purchase orders, invoices, and remittance advices, as well as other computer data. EDI allows an organization prepare business forms on their computer, and their trading partner receives a copy of the information on their computer for subsequent processing.

Using EDI to send information, an organization can prepare and communicate purchase orders, change orders, material releases, and requests for quotes without printing, preparation, or mail cost. On the receiving side, an organization can receive shipping notices, bills of lading, invoices, purchase orders, purchase order acknowledgements, and price lists and input these directly into either an automated application or an electronic report viewing system.

The advantages of these electronic exchanges are reduced print, reduced processing time, and improved quality. Both the organization its trading partner have the opportunity to reduce data handling, improve productivity, and improve quality while achieving cost savings. Organizations need a better link to the source of business information to realize these goals, and that is what electronic data interchange is all about.

EDI is a system that connects one organization's computer to a business associate's computer only when it is required to exchange pertinent operational and status information. EDI may not require new equipment or dedicated communications facilities; rather, it is a means for interlinking present computer systems by employing standard information structures, standard communication protocols, and a limited number of special EDI interface computer programs.

The data transmitted originates from records in the sender's database after the sender confirms that the receiver is an authorized recipient for such data. The sender composes a transmission formatted in the EDI standards; the receiver translates the formatted message to a computer record to be processed and used internally. All transmissions are checked both checked both electronically and functionally, and the protoc procedures for error detection and corrections. Once a company has established standardized communications with another company, it is in a position to communicate with any other company that is also using the same EDI standards.

(NOTE: The above introduction to EDI was excerpted from the Electronic Data Interchange Guide published by The Information Technology Institute, September 1992.)

Administrative Responsibilities For FRS EDI

Several parties have responsibilities for various components of the Process for conducting EDI transmissions with external agencies. These responsibilities are summarized below:

FRS System Administrator

The FRS System Administrator is responsible for coordination of the schedule for FRS production jobs as they pertain to the EDI process. In addition, the system administrator is responsible for coordination of transmission schedules and related items with external agencies.

UITS Scheduling Department

The UITS Scheduling Dept. is responsible for monitoring the execut and completion of production jobs and for initiating remedial action for production job problems. They also serve as initial the contact point for external agencies if any problems with data transmission arise.

UITS Administrative Services Department

The UITS Administrative Services Department is responsible for providing technical programming support for the EDI production effort as well as serving as the initial liason for establishing an EDI application.

UITS Mainframe Services Department

The UITS Mainframe Services Department is responsible for providing technical support for those elements of the EDI process that pertain to the IBM 3725 communications controller, VTAM, and the JES remote device definition.

UITS Data Communications Department

The UITS Data Communications Department is responsible for supporting the data communications elements of the EDI process pertaining to the telephone line and the communications modem with its attendant settings.

Functional Description Of FRS EDI With Shawmut Bank

As of August 1994, FRS EDI activities consist of a simple two way exchange of data files with Shawmut Bank for the purpose of exchanging check reconciliation data. The files exchanged are in the format specified by Shawmut. On the UConn end, locally written application programs reformat data to comply with both FRS and Shawmut requirements.

Two production jobs are involved in this data file exchange process. The jobs are described in detail in the FRS EDI procedures section below. For the outgoing transmission from UConn to Shawmut, job J0317S12 is run weekly and during month-end processing to prepare the data file. This file is placced on the JES spool where it is retained until Shawmut dials in via theestablished procedure and schedule. When a successful connection is made and agency authentication satisfied, the waiting data file is automatically transmitted the bank.

The incoming transmission from Shawmut to UConn follows a similar procedure. At the scheduled time each month, Shawmut dials in to UConn and undergoes agency authentication. Upon achieving a successful connection, job J0315S92 is transmitted remotely to the UConn Job Entry Subsystem (JES) where an ACF2 security verification is performed. If this verification is successful, the job is executed, resulting in a generation data set being written to DASD. A subsequent job is then requested by the FRS System Administrator to reformat the data for FRS input and to make of a backup copy the Shawmut data on tape.

FRS EDI Procedures

This section describes the procedures for specific EDI applications with the FRS system. As additional applications are added, subsequent sections be inserted with the appropriate procedures for those applications.

Shawmut Bank Check Reconciliation Data Exchange

As explained earlier, the Shawmut check reconciliation process is a two exchange of simple data files. FRS production jobs prepare the data for transmission and, for incoming data, subsequently reformat the data for application processing.

UConn and Shawmut National Corporation Contacts

The UConn phone number for data transmission is 203-486-3798. No other phone number can be used.
SHAWMUT Operations Center (Primary UConn contact)
- Phone number: 203-728-2214 (Alternate) 203-240-1148
- Contact person(s): Mildred Colon
SHAWMUT Operations Supervisor
- Phone number: 203-548-7092
- Contact person(s): Thelma Morris
SHAWMUT Transmission Center (For unusual problems only)
- Phone number: 203-728-4517
- Contact person(s): Barbara Carlevale
SHAWMUT Account Reconcilement Service (FAX monthly transmittal letter)
- FAX number: 800-945-8062
- Phone number: 800-333-8392 (Alternate 508-793-4038)
- Contact person(s): Diane Pratt
UITS Scheduling/Production Control (Primary Shawmut contact)
- Phone number: 203-486-3732
- Contact person(s): Bill Case, Jill Stedman
UConn Accounting Office
- Phone number: 203-486-2937
- Contact person(s): Claudia Ross, Ann Jordan, Lou Gaudet

The Data TransmissionSchedule

Outgoing Transmission UConn To Shawmut

The outgoing transmission is conducted weekly on Monday afternoon at 3:00 p.m. In addition, there is one transmission per month at 3:00 p.m. the day after FRS month-end processing. This final monthly transmission will be coordinated by the FRS System Administration, since the day varies from month to month. A phone call must be placed to the Shawmut Operations Center to initiate this variable month-end transmission. In addition, the UConn Accounting Office must FAX the monthly Issue File Transmittal Letter to the Shawmut Account Reconcilement Service at the number shown above.

Any variations to this schedule due to local UConn operations must be communicated to the Shawmut Operations Center by the FRS System Administrator at in the UConn Accounting Office.

Incoming Transmission Shawmut To UConn

The incoming transmission is conducted monthly on a schedule that s concide with Shawmut's month-end account reconcilement operation. The transmission is normally occurs approximately the third business day ne of the month and is done during first shift (8:00 a.m. to 4:00 p.m.).

The Dial-Up Procedure

The dial-up procedure is initiated by the bank according to the above schedule regardless of the transmission direction. The phone line is a standard switched dial-up line which is reserved for the EDI function. The phone number is 203-486-3798.

The Data Transmission Process

For incoming data, the transmission is initiated by Shawmut personnel after they obtain confirmation of a successful dial-up connection. MVS job JCL is transmitted with imbedded data and is received by UConn's MVS JES system. Upon validation of LOGON, PASSWORD, and JCL parameters, the job is executed a and generation dataset (GDG) is created containing the data submitted.

For outgoing data, the transmission is initiated automatically after Shawmut establishes a successful dial-up connection. In this case, the o data to be transmitted is already waiting on the JES spool and thus transmission is initiated as soon as Shawmut successfully establishes establishes a JES remote session.

Production Jobs For FRS EDI

The following jobs are involved in the data transmission process:

This job is submitted remotely by Shawmut Bank to transmit check reconciliation data for Memo Bank 15. This process takes the place of the monthly tape exchange for check reconciliation data. Transmission of the JCL with imbedded data is accomplished after a successful dial-up connection is made by the bank.

- J0317S12 - Check Data Transmission UITS To Shawmut (EDI) - Bank15

This job uses a tape created in J0317M01 to create an electronic output file that will be transmitted to the bank. The data file is placed on the JES spool and is transmitted to Shawmut when the bank dials in via the established procedure.

Production Job Verification

Since standard production jobs are involved in this procedure, the process for verifying successful job execution is the same as for n all other production jobs. MVS job instructions contain procedures for ll resolution of ABENDs as well as potential data transmission problems. The JES Job Logs are routed in the standard manner to the UITS Scheduling Department following job execution. In addition, the job logs are also sent on to selected user CMSIDs for notification and verification purposes. The jobs and their respective routing information are as follows:

- J0317S12: JES Log sent to CONADM02.

Data Transmission Troubleshooting Procedures

Troubleshooting procedures for data transmission problems are out in lined the respective MVS job comments and are also presented here for ready reference.

The phone number for Shawmut to dial UConn is 203-486-3798. No other phone number can be used.
The phone number to contact the Shawmut Operations Center . is 203-728-4126.
If J0315S92 does not run because of PASSWORD expiration: Contact ACF2 Security personnel to resolve password expiration.
If Shawmut reports problems with the connection or transmission, some possible actions to take are as follows:
- Modem does not respond or does not connect:
  Contact UITS Data Communications personnel to check modem.
- Modem connects but the line does not come up for remote device :
  Contact UITS Mainframe Services (Systems Programming) personnel to verify status of VTAM and JES parameters for line and remote device .
If Shawmut reports problems with retrieving the output file or transmitting data to UConn, the following VM/CMS commands can be used to verify the status of the specific communication components:
- LNE8 line status: MVSQ $DU,LNE8
- RMT8 device status: MVSQ $DU,RMT8
- Verify output file status: $DP,R=R8 (Operator console only)

Technical Description Of FRS EDI

Technical specifications for FRS EDI are presented in the following section. The description appearing here is a brief outline of the communication protocol used to achieve the desired data file exchange with Shawmut bank.

Data communication protocol follows IBM SNA/RJE (System Network Architecture/Remote Job Entry) industry standards with 3770 data transmission device emulation. The external agency MUST initiate the transmission by dialing in to UConn, whether it is incoming to, or outgoing from UConn. The external agency acts as the REMOTE job entry station while UConn serves as HOST. These basic requirements are fixed and not subject to change.

The communication environment between Shawmut and UConn is available 24 hours a day, 7 days a week as long as the UConn mainframe and MVS system are operational. This environment can be viewed as having four or separate parts links.

The first link is the connection between standard data communications modems. This connection is achieved via a standard switched dial-up telephone line which is reserved for the EDI function. Modems on both ends of the telephone line must use compatible synchronous communications protocol. Modem communication speed is set to 9600 bps.

The second link in the communications environment is from the modem to the IBM 3725 communications controller (front-end processor) running Network Control Program (NCP). The 3725 initiates the communication process by sending its identification to the remote location following a successful synchronization status between the modems. When the remote system receives the signal from the 3725, it sends an ID number and ID block combination for verification by the 3725.

Following successful verification of these parameters, the third link is established between the 3725 and VTAM which runs on the mainframe under the MVS operating system. The communications controller passes the ID number and ID block on to VTAM for verification. When this verification has been successfully completed, VTAM then sends an acknowledgement back to the remote location which clears the way for transmission of subsequent LOGON commands. At this point, VTAM establishes the fourth and final link with the MVS JES system.

In order to establish a JES session, a remote device must have been defined to JES. The remote device for the Shawmut EDI process has four logical units defined: console, reader, printer, and punch. During receipt of a transmission from Shawmut, the READER is active. During an outgoing transmission from UConn to Shawmut, the PUNCH is active.

Upon receipt of the VTAM acknowledgement, the remote agency activates a JES session on the UConn host by transmitting the proper LOGON command. The format for this command is shown in the technical specifications section which follows.

Technical Specifications For FRS EDI

Introduction

The purpose of this section is to identify and describe the various systems components and specifications for the FRS EDI function operative here at UConn at the time of implementing the Shawmut EDI application in August 1994. These are the "standard parameters" after which we expect to pattern subsequent EDI applications with other external agencies.

UConn Data Communications Specifications

All telephone line and data communications hardware and software parameters are maintained by UITS Data Communications.

Telephone Line

The telephone line employed is a standard common carrier switched, dial-up telephone line which is reserved for the EDI function. It can be shared by multiple applications (one application at a time) since s each external agency identified separately to the mainframe system.

Communications Modem

The modem used is a Motorola CODEX 326X series modem set to operate in synchronous mode at a transmission rate of 9600 bps. Specifics about the detailed modem settings are maintained by UITS Data Communications.

UConn Mainframe System Specifications

All mainframe hardware and software parameters are maintained by UITS Mainframe Services.

Mainframe Computer and Operating System

The UConn mainframe computer is an IBM Model ES9000 running the MVS/ESA operating system.

Communications Controller

The communications controller employed is an IBM model 3725 running Net Control Program (NCP) version 4.2. The "line" between the 3725 controller, VTAM, and the mainframe host (JES) is an SNA/SDLC (Synchronous Data Link Control) line running at 9600 bps and defined for CALL=IN processing. Two lines are defined with identical parameters for redundancy. The 3725 line can dynamically support both TYPE=1 and TYPE=2 devices, however, we prefer that device be TYPE=2 which includes 3770 devices.

In the case of an SNA/RJE configuration, there are four LUs (logical units) attached to the device (console, reader, printer, punch). Only the READER and the PUNCH are used in the Shawmut simple data transfer application.

Virtual Telecommunication Access Method (VTAM)

VTAM software running under MVS uses an ID number and ID block combination (8 characters) to conduct external agency authentication and provide first level "access security". Since the caller identifies itself with the 8 character ID number and ID block which we have assigned, the device configuration of the caller is known in advance and the proper host device parameters have been pre-assigned on our host system.

Job Entry Subsystem (JES)

JES2 software running under MVS establishes and manages the mainframe communication session. Each external agency is assigned a separate remote device configuration under JES. For Shawmut Bank, the remote device identification is . The ID number and ID block are passed to JES through VTAM and are again used to authenticate the remote agency.

Following a successful authentication process, the external agency initiates a LOGON procedure to JES. Upon successful execution of the LOGON sequence, a JES session is established and data transmission can begin. The specific LOGON sequence for Shawmut is as follows:

MUT100) LOGON APPLID(JES2) LOGMODE(IBM3770) DATA(RMT8,,,SH MUT100)

UConn MVS Job Control Language (JCL) Specifications

J0315S92 ACF2 Security Parameters

Shawmut Bank is granted very limited access privileges to the UConn mainframe system as the originator of job J0315S92. A special account number and password, which are maintained by the ACF2 Security Administrator, are required in theJCL. Shawmut is allowed to create only dataset UAPFMGT.SHMT15.D0315S92 (GDG) on volumes USR002, USR016, and USR030. The job can only be submitted via the node .

J0315S92 Unique JCL Parameters

For current JCL requirements, refer to the JCL for J0315S92 located in PRO.JOBLIB. An example of the unique JCL requirements for this job are given below:


//J0315S92 JOB (9337,0004,99,,,6101),'*ADM-DP',

// TIME=15,CLASS=A,MSGCLASS=I 
 
//* 

/*ROUTE XEQ UCONNMVS 

//*LOGONID 93370004 

//*PASSWORD XXXXXXXX 

//* 
 
/*JOBPARM RESTART=N,PROCLIB=PRO 

//JOBLIB DD DSN=PRO.LOADLIB,DISP=SHR

J0317S12 OUTPUT JCL Parameters

For current JCL requirements, refer to the JCL for J0317S12 located in PRO.JOBLIB. Parameters on the OUTPUT DD for CLASS and DEST are critical and should not be changed. These parameters are shown below:

	
//REMOTE8 OUTPUT CLASS=K, 

// FORMS=STD, 

// DEST=UCONNMVS.RMT8, 

// CHARS=(GT15), 

// FCB=(8H10), 

// BURST=NO, 

// PRMODE=LINE, 

// COPIES=001

Shawmut National Corporation (SNC) Emulation Specifications

(NOTE: The following information about Shawmut National Corporation data transmission capability is excerpted from the SNC Data Transmission Link Test Form.)

SNC data transmission equipment provides binary synchronous (bisynchronous communications in point to point, half duplex mode at operating line speeds of 2400, 4800, and 9600 baud. The communication facility is the common carrier switched telephone network with various modem interfaces. (CODEX is included).

The data transmission device operates under the control of a communications program capable of emulating industry standard protocols such as IBM's 2780, 3741, 3780 and SNA/RJE. A parameterized communications feature allows for selection of record/buffer sizes, transparency, space compression, intermediate record separators, and other less used variables.

NIXDORF Minicomputer And SNA Communications Parameters

Shawmut employs a NIXDORF minicomputer running SNA/RJE communications emulation software as a data transmission device. The 600/8850 operating system will support 3274, 3276, and 3777 SNA communication using DPE X V software and an ICP. Shawmut is compatible with a system using a front end controller running NCP and can also run 3777 emulation to a system using JES2 as the RJE spooler. The host system environment varies from customer to customer. (As explained previously, UConn acts as the host for these transmissions.)