OMMUNICATIONS - Epicor will be incorporated in new editions of the publication. ... (Direct...

OMMUNICATIONS

ii

The documentation in this publication is provided pursuant to a Sales and Licensing Contract for the Prophet 21® System entered into by and between Prophet 21 and the Purchaser to whom this documentation is provided (“License Agreement”). In addition, the licensed software to which this documentation refers may be supported in accordance with a customer support agreement by and between the same parties (“Support Agreement”). All warranties, conditions of use, transfer restrictions, and other provisions in the License Agreement or Support Agreement which are applicable to Licensed Software, are applicable to this publication. In addition, this publication may include inadvertent technical inaccuracies or typographical errors for which Prophet 21 is not responsible. Changes may be periodically made to this publication; these changes will be incorporated in new editions of the publication. Any questions about the material contained in the publication should be addressed to the Prophet 21 Customer Support Department at 1-800-ITS-PR21.

Nothing in this statement amends or extends the terms of your agreement with Prophet 21 including any warranties that may be included in our products. Warranties for such agreements are set forth in your agreement with Prophet 21.

Improvements and/or changes to the Licensed Software described in this publication may be made by Prophet 21 at any time without notice.

DOCUMENTATION CONVENTIONS ♦ The eyeglass symbol (�) indicates a field on which you can browse. ♦ The star (�) indicates the default for a field. ♦ To allow for the widest possible parameters when printing a report or performing a

function, accept the defaults for all of the parameter fields. To accept the defaults, either escape through all the fields, or press [Enter] without specifying any values. Generally, samples in the documentation are shown using the default values.

♦ Start and End parameters define the limits to a range of information you will print on a report. If information does not appear on a report, it may be because the information was excluded from the Start, End range.

♦ For a detailed explanation on how maintenance screens function, refer to the Tour Guide manual.

♦ Use the search tool in Adobe Acrobat Reader 4.05c to find which manual describes a specific module, job, or function.

9/22/05Prophet 21 Acclaim® Version 16

The Prophet 21 system and Prophet 21 Acclaim are registered trademarks, and Prophet 21 and ScratchPad are trademarks of Prophet 21. All other trademarks and registered trademarks are the property of their respective companies.

iii

Table of Contents

1 INTRODUCTION____________________________________________________8

Background _________________________________________________________8

Getting Started _____________________________________________________10 Requirements for EDI Com___________________________________________10 Summary of Procedures_____________________________________________10

Main Menu_________________________________________________________11

2 SEND/RECEIVE EDI DOCUMENTS____________________________________13

The First Step ______________________________________________________13

Send Procedure_____________________________________________________15

Receive Procedure __________________________________________________17

Modem Messages ___________________________________________________19

3 AUTO-DIAL MODE _______________________________________________23

4 MANUAL DIAL MODE_____________________________________________26

5 EDI DIRECTORY INFORMATION ____________________________________28

General Options ____________________________________________________28

ASCII Transfer Options _______________________________________________31

6 JCL SCRIPTS _____________________________________________________34

“H” for Keyword Help _________________________________________________35

“BH” for Bisync Help _________________________________________________35

JCL Command Strings _______________________________________________36

iv

JCL Fast Receive ___________________________________________________37

7 ASSIGN MODEM PORTS____________________________________________38

Deleting a Modem Assignment _________________________________________39

Setting Up Your Modem ______________________________________________39

Service IDs ________________________________________________________40

8 CONFIGURE MODEM PORTS ______________________________________41

9 MODEM INITIALIZATION TABLE ____________________________________42

Enter/Edit/Delete Modem Initialization Information __________________________42

Copy Modem Initialization Information____________________________________48

List Modem Initialization Information _____________________________________48 Sample: Modem Initialization Table Report ______________________________49

10 BISYNC COM LOG ________________________________________________50

Bisynchronous Communications for AIX Users _____________________________50 Advantis-IBM _____________________________________________________50

Send and Receive____________________________________________50 National Bank of Detroit (NBD)________________________________________51

Receive Only _________________________________________________51 Ford ____________________________________________________________51

Send ________________________________________________________51 Receive _____________________________________________________51

GM _____________________________________________________________51 Send and Receive____________________________________________51

CTX ____________________________________________________________52 Send and Receive____________________________________________52

Steelco __________________________________________________________53 Receive _____________________________________________________53

Send/Receive Procedure______________________________________________53

Bisynchronous Communications Log ____________________________________53 Sample: Bisynchronous Communications Log ____________________________54

11 JOURNALS ______________________________________________________55

v

Sent Documents ____________________________________________________55 Sample: EDI Event Journal of Sent Documents ___________________________56

Received Documents ________________________________________________57 Sample: EDI Event Journal of Received Documents _______________________57

CTX File Listing _____________________________________________________58 Sample: CTX File Listing of Inbound Files _______________________________59

12 SETTING UP JCL SCRIPTS _________________________________________60

Sample Scripts _____________________________________________________61 GE’s GEISCO_____________________________________________________61

JCL for Sending Data to GEISCO ____________________________________61 Function Commands in JCL Scripts __________________________________61 JCL for Receiving Data from GEISCO_________________________________62

Ordernet _________________________________________________________64 BT Tymenet_____________________________________________________64 CompuServe ____________________________________________________64

Kleinschmidt ______________________________________________________65 JCL for Sending Data to Kleinschmidt _________________________________65 JCL for Receiving Data from Kleinschmidt _____________________________66 JCL for Receiving Previously Received Data from Kleinschmidt_____________66

Equipment Industry Network (EIN) _____________________________________66 JCL for Sending Data to EIN ________________________________________66 JCL for receiving data from EIN______________________________________66 JCL for sending data to and receiving data from EIN _____________________67

Harbinger ________________________________________________________67 JCLs for Sending Data to and Receiving Data from Harbinger ______________67

Tymenet/MCI Network ______________________________________________70 JCL for Sending Data to and Receiving Data from Tymenet/MCI Network _____70

AT&T Easy Link ___________________________________________________70 JCL for Sending Data to AT&T ______________________________________70 JCL for Receiving Data from AT&T ___________________________________71

RAILINC _________________________________________________________71 RAILINC Directory for Sending and Receiving Data ______________________72

UPTECH_________________________________________________________72 JCL for Logging on to UPTECH______________________________________73 Sending Data to UPTECH __________________________________________73 Receiving Data from UPTECH ______________________________________73 Logging Off from UPTECH _________________________________________74

Trade Route ______________________________________________________74 Sending Data to and Receiving Data from Trade Route ___________________74

Johnson & Johnson's COACT Network _________________________________74 JCL for Sending 850 Transaction Sets to Johnson & Johnson ______________74 JCL for Receiving 855 Transaction Sets from Johnson & Johnson___________75

vi

Advantis-IBM _____________________________________________________75 JCL for Sending Data to and Receiving Data from Advantis-IBM for AIX Users _75

National Bank of Detroit (Direct Connection for AIX Users Only) ______________76 JCL for Receiving Data from NBD for AIX Users_________________________76

Ford (Direct Connection) ____________________________________________76 JCL for Sending Data to Ford for AIX Users ____________________________76 JCL for Receiving Data from Ford for AIX Users _________________________76

GM (Direct Connection) _____________________________________________77 JCL for Sending/Receiving 997 Transaction Sets to/from GM for AIX Users ___77 JCL for Sending/Receiving 843 Transaction Sets to/from GM for AIX Users ___77

CTX (Direct Connection for AIX Users Only) _____________________________77 JCL for Sending Data to and Receiving Data from CTX for AIX Users ________77 JCL for Retrieving Delivered Files ____________________________________79 JCL for Getting a List of Inbound CTX Files ____________________________80 JCL for Getting a List of Outbound CTX Files ___________________________81 JCL for Taking CTX Job Commands from an AIX File ____________________81 Writing Your Own CTX Job _________________________________________81 CLEO Commands _______________________________________________82 Configuration File _______________________________________________82 CTX Commands ________________________________________________83 Sample CTX Job ________________________________________________85

3-M _____________________________________________________________85 JCL for Sending Data to 3M ________________________________________85 JCL for Receiving Data from 3M _____________________________________85

United Stationers __________________________________________________86 JCL for Sending Data to United Stationers _____________________________86 JCL for Receiving Data from United Stationers __________________________86

Lynn Edwards_____________________________________________________86 JCL for Sending Data to Lynn Edwards________________________________86 JCL for Receiving Data from Lynn Edwards ____________________________87

Stationers ________________________________________________________87 JCL for Sending Data to and Receiving Data from Stationers_______________87

SP Richards ______________________________________________________88 JCL for Sending Data to and Receiving Data from SP Richards _____________88

O'Henry _________________________________________________________88 JCL for Sending Data to and Receiving Data from O'Henry ________________88

Lynn Edwards Wrap and Ship ________________________________________89 JCL For Sending Data to and Receiving Data from Lynn Edwards Wrap and Ship89

Boise Cascade/Associated Stationers __________________________________89 JCL For Sending Data to and Receiving Data from Boise Cascade/Associated Stationers ______________________________________________________89

Steelco __________________________________________________________90 JCL for Receiving Data from Steelco__________________________________90

File Transfer Protocols _______________________________________________90

vii

Using XMODEM ___________________________________________________91 Using Kermit______________________________________________________91

13 EDI ADMINISTRATOR______________________________________________93

Setting Up Trading Partner Information ___________________________________93

Installing Overlays on your System ______________________________________93

How to Receive Data from Your EDI Network ______________________________94

How to Process Received Data in EDI ___________________________________94

How to Send Documents on the EDI Network______________________________95 Building EDI Documents_____________________________________________95 Preparing EDI Documents ___________________________________________96 Sending EDI Documents to Your EDI Network____________________________96

How to Send Functional Acknowledgements (997s) _________________________97

How to Free a Locked Modem while Sending or Receiving ___________________97

Month-End EDI Procedures____________________________________________97

14 APPENDIX _______________________________________________________99

ASCII Control Characters _____________________________________________99

15 FAQS __________________________________________________________101 What does “Name Invalid!” mean when I try to assign a modem? _________101 When dialing out, I receive the message “modems failed to connect.” What does this mean? _______________________________________________101 What action should I take when the following message displays when receiving?101 What does “One of the assigned modems in the modem initialization table is invalid” mean? ________________________________________________101 What is the purpose of the Manual Dial option? _______________________101 How many modems can I setup to be used for EDI? ___________________102 Where do I change the phone number of my VAN? ____________________102 What does the message “phone lines accidentally disconnected” mean? ___102 How can I determine on which port my modem is assigned?_____________102 After sending or receiving transmissions, the Interactive Mode screen appears. The terminal appears to be locked. What should I do? _________________102

8

Documentation for the EDI package consists of three manuals:

EDI Communications

EDI Documents

This manual focuses on the EDI Communications module, which is used to perform the actual data communications for the EDI package.

Using EDI Com, you dial in to either network systems or your trading partners' systems, and transmit or receive EDI documents. Options are provided to allow you to dial in and perform other terminal functions, without necessarily transmitting or receiving EDI data. Assigning and configuring modems, as well as printing communications journals can also be accomplished.

Tip! Menu Options For reference purposes, the chapters in this manual are organized in the same order as the menu options of EDI Com. However, when initially setting up EDI Com, you’ll follow a different procedural order than what is laid out here. For more information on setting up EDI Com, refer to “Getting Started” on page 2.

BACKGROUND To communicate with another computer system electronically, you must first establish a connection with that system. To connect a terminal to your Prophet 21® system, you use a cable. To connect to another system, you use telephone lines. This way you can connect to any number of other systems without having direct cables to each one.

To send and receive computer signals over telephone lines, you need a special device called a modem. Modems translate computer signals into a form that can be transmitted over phone lines. A modem must be attached to the phone line at each end of the connection, and the modems must then be attached to each computer. Once they are attached and a telephone connection is made, the computers are communicating directly with each other. This is the true power of EDI; data on your system can be transferred directly to another system electronically, without having to be translated by human operators.

NTRODUCTION

1 INTRODUCTION

9

EDI COMMUNICATIONS

In general, once the connection is made, your system has access to the computer to which you have connected. The trading partner or network computer system you have dialed in to is referred to in this documentation as the host system. Generally, the commands you issue and the screen displays you see are those of the host system, not your Prophet 21 system. Because of this, you need to log on to the host system after you have connected, and log off when you have finished.

For the purposes of this documentation, the term communications session refers to the entire communications process. That is, you dial in to a remote host system, log on after a successful connection has been made, issue the appropriate commands to send or receive data, log off when you are finished, and disconnect the modem. All of these steps constitute a communications session.

The primary communications options provide three different ways of accessing other systems:

Send and Receive EDI Documents

Checks for documents that you prepare for transmission using the EDI Doc module, and allows you to transmit these to the appropriate trading partner via the third party network. This option is also used to receive EDI documents from your trading partners from your mailbox on the network you use, or from their system.

Auto-dial Mode Provides a means of dialing in and logging on to a system without checking for documents which have been prepared for that trading partner. You can either upload or download AIX files through Kermit or an Xmodem. This option does not allow you to transmit or receive EDI documents.

Manual-dial Mode Functions as a basic terminal connected directly to your modem. You can check modem settings and issue commands directly to the modem. You can also dial out and connect to another system using the modem, by issuing the appropriate modem commands manually. However, dialing out is much easier using one of the first two methods.

The first two options use the EDI Directory information that you set up to dial in automatically. The EDI Directory is used to maintain phone numbers for the modems you are dialing in to and to reference JCL (Job Control Language) scripts and other configuration information for all of your trading partners and networks. The EDI Directory maintains the phone number of the modem on the system into which you are dialing. When you use this EDI Directory information to make a connection, the system automatically issues the modem commands that dial this phone number.

Job Control Language (JCL) scripts are used to automate routine procedures, such as log-on commands. When a connection is made, any JCL script which you have specified for that directory entry is executed automatically. JCL scripts are specified in a manner similar to job-queue information in the JCM module. You specify a string of characters that is to be received from the host system. When that string is received, the corresponding command is sent by your Prophet 21 system. JCL commands are stored in JCL scripts, which consist of a sequence that is a macro for controlling the communications session.

Modem configuration is controlled by the Modem Initialization Table. This table stores configuration information for each modem. The stored information includes the commands to configure the modem before the phone number is dialed, and to control the modem during the communications session. When you set up your modems for use with the EDI package (and other packages), you designate the type of modem that is attached to each port (by specifying the entry from the modem initialization table), and a Default Service ID using the Assign Modem Ports option. This allows you to leave the modem configured in a certain way when you have finished using it, in case it will be receiving calls from other systems (e.g., if you use the modem with the On-Site Optional Package in addition to the EDI package.) For more information on setting up your modem initially, refer to page 2.

1 INTRODUCTION

10

EDI COMMUNICATIONS

For users who have purchased the Cleo Communications package, the menu includes an option to print a bisynchronous communications log.

In order to use the EDI Com module to transmit and receive EDI documents, you should follow these steps:

1. Enter all of the EDI Directory information you need for each network or trading partner with whom you are communicating.

2. Make sure that all of the EDI Setup information that you need has been created in the EDI Setup module.

3. Set up all of your modems using the procedures described on page 2.

4. Set up your JCL using procedures described on page 2.

5. Generate and envelope documents using the EDI Doc module.

6. Use the Send and Receive EDI Documents option to transmit and receive EDI documents.

7. Process any documents you receive using the EDI Doc module.

The EDI Com module provides the communications options that you need to connect with your trading partners, allowing you to transmit and receive all of your EDI documents.

GETTING STARTED

REQUIREMENTS FOR EDI COM The following requirements should be met to successfully use EDI on your system:

♦ One or more trading partners.

♦ Access to a VAN (value-added network), such as Harbinger, Geisco, Ordernet (Sterling Software), or AT&T.

♦ JCL scripts to connect to and disconnect from another system’s modem.

♦ Autobooted EDI modem.

♦ EDI overlay (trading partner specific).

SUMMARY OF PROCEDURES The following steps offer a summary of what is required to set up the EDI Com module:

1. Enter your Trading Partner Network information by using the Network option on the Trading Partner menu of EDI Setup. For more information on setting up the network record, refer to the EDI Setup manual.

2. JCL (Job Control Language) scripts need to be created to automate the dialing out of the modem, and the sending/receiving of EDI transmissions. For more information on creating JCL scripts, refer to the chapter “JCL Scripts” in this manual.

1 INTRODUCTION

11

EDI COMMUNICATIONS

3. Set up the EDI directories that hold information on the networks you use to transmit and receive documents with your trading partners. For more information on creating EDI directories, refer to the chapter “EDI Directory Information” in this manual.

4. The EDI modem needs to be set up by using the Assign option in EDI Communications. For more information on setting up your EDI modem, refer to the chapter “Assign Modem Ports” in this manual.

After these steps are accomplished, and you have your trading partner and overlay information set up in the system, you are ready to send, receive, and process EDI documents. For more information on these processes, refer to the EDI Documents manual.

MAIN MENU

Send/Receive

. . . sends and receives EDI documents. For more information on this option, refer to the next section.

Auto-Dial . . . dials in to another system using EDI Directory information. This information must already exist for a trading partner. This option does not enable you to exchange EDI interchange information with a trading partner. For more information on this feature, refer to page 2.

Manual-Dial . . . provides a “terminal” facility to allow you to access a modem directly. Modem commands, including dialing commands, can be issued, and modem configuration can be checked. For more information on this option, refer to page 2.

EDI Directory

. . . enters, edits, and deletes value-added network (VAN) directory information. For more information on this option, refer to page 2.

JCL Scripts . . . enters, edits, and deletes JCL scripts. For more information on this option, refer to page 2.

Assign . . . assigns modem ports to the TTYs (physical ports) that they connect to on the RS/6000. For more information on this option, refer to page 2.

1 INTRODUCTION

12

EDI COMMUNICATIONS

Configure . . . configures modem ports. For more information on this option, refer to page 2.

Modem Init . . . enters, edits, copies, deletes, and prints modem initialization information. For more information on this feature, refer to page 2.

Journals . . . prints EDI Com journals. For more information on this option, refer to page 2.

Note: If the optional Cleo Communications package is enabled, another option appears called Bisync com log. This option, used with the Cleo Communications package, prints and clears the log of your bisynchronous communication.

13

The Send/Receive option sends already-built and prepared EDI documents to your trading partners. EDI documents are also received from your trading partners with this option.

Before you can send or receive EDI documents, all of the necessary setup information available for all trading partners must be entered in the system. This includes all of the transaction sets (overlays) that you are exchanging with each trading partner.

To send documents, you must build and envelope the documents that you wish to send, using the EDI Doc module. Once enveloped documents have been created, they will automatically display on a scan of available documents to be sent. The scan displays all of the EDI documents that have been created for a specific network or trading partner. For more information on building and enveloping documents, refer to the appropriate sections in the EDI Documents manual. If you are sending documents to a network, you can send them to all of your trading partners.

THE FIRST STEP Sending and receiving documents are normally performed in different communications sessions. When the Send/Receive option is selected, a screen displaying your EDI Directory entries is shown. You are prompted for an EDI Directory entry for the network or trading partner into which you are dialing:

Seq . . . sequence number of the network or trading partner on the screen.

END ECEIVE OCUMENTS

2 SEND/RECEIVE EDI DOCUMENTS

14

EDI COMMUNICATIONS

EDI Code . . . code of the network or trading partner.

Name . . . name of the network or trading partner.

Modem Phone Number

. . . the phone number of the modem to which you are connecting.

Seq/Code . . . sequence number to be entered of the network or trading partner on the screen. When a letter is entered in this field, the list of EDI codes will resequence with entries starting with this letter. For example, if you enter ON, EDI codes starting with ON will display in the upper half of the screen.

For more information on setting up EDI Directory information, refer to the “Enter/Edit/Delete EDI Directory Information” chapter on page 2.

In the previous screen, EDI Directory entries are selected either by EDI Code or by their Sequence Number. You can enter either value at the Seq/Code prompt to choose a specific EDI Directory entry. Upon entry of a valid EDI Code or Sequence Number, the directory information displays for that network or trading partner in the lower half of the screen. In addition, a preview of enveloped documents displays automatically in the top window of the screen. All of the enveloped documents for trading partners that use this network are included.

TP ID . . . the trading partner ID.

Doc # . . . number of the enveloped document.

Date . . . date the document was enveloped.

Time . . . time the document was enveloped.


15

EDI COMMUNICATIONS

Comments . . . system-generated comment generated by the enveloping procedure.

Seq/Code . . . holds either the sequence number or the EDI code of the network or trading partner.

You should set up your Async Mode Control fields with values that match your VAN’s modem settings. For more information on these fields, call your network or Prophet 21’s EDI Support Team.

If you need to edit any of the EDI Directory information, you can do so now. This changes the information for this session only.

SEND PROCEDURE 1. Press [Enter] at the Field prompt on the Preview Enveloped Documents to be Sent screen to start the

communications session. The system begins by looking for a free modem. If it finds one, the system configures the modem (using the information you specified in the EDI Directory information) and dials the modem#, specified in the EDI Directory information. All of the modem commands are issued automatically and are displayed in the modem window, as shown in the following screen:

If there are any errors with the modem dialing, messages display in the modem window. For a complete list of modem errors and solutions, refer to the section titled “Modem Messages.”

2. When a connection is made, the system displays the connection information, as shown in the following screen:


16

EDI COMMUNICATIONS

Note: If data has been received, the byte count of the sent transmission is shown.

All of the data that you receive from the host system, as well as your responses, displays on a window similar to the above one that follows the Modem Input/Output Status screen.

3. When you finish the communications session, the system returns to the EDI Directory screen of the Send and Receive option. The modem window displays with any messages that occurred when the modem was disconnected. If the disconnection is successful, the following messages displays.

Depending on how you have answered the Pause for (Dis)connect field in the EDI Directory record, the prior screen flashes by quickly, or pauses for you to press a key to continue. For more information on this field, refer to page 2.

4. Press any key to return to the EDI Doc menu.


17

EDI COMMUNICATIONS

RECEIVE PROCEDURE For receiving EDI documents, the procedure is very similar to sending documents. To begin the receive process, follow these steps:

1. After choosing the Send/Receive option, select an EDI Directory entry for receiving from the EDI Directory screen:

2. Information about the directory entry you selected is displayed. Press [Enter].

Note: For a description of the screens shown in steps 1 and 2, refer to pages 2 and 2.


18

EDI COMMUNICATIONS

3. The system automatically dials and receives all the data from your mailbox. When this process is done, the system displays the byte count of the received transmission and hangs up the modem.

4. Press [Esc] and the modem will be disconnected. The system returns to the Seq/code prompt. Press [Enter] to return to the menu.

If you received data during your communications session, the transmitted information is stored in a temporary holding area while the modems are disconnected. Once the connection is completed, the data is then “despooled” automatically.

Despooling is the procedure where the system moves the transmitted data from the temporary holding area to the EDI document file systems. The despooling function separates the desired EDI data segments from the rest of the received information, and creates an X12 document with all of the received data segments. This document is assigned the type RECV, for a received document. To process this received document, use the Process (Received ASC Documents) option in the EDI Doc module.

Note: For more information on X12 documents, refer to the EDI Setup manual.

After the received data has been despooled, the system returns to the Send/Receive option of the EDI Communication screen.


19

EDI COMMUNICATIONS

MODEM MESSAGES While sending or receiving data, you may receive one of the following messages:

Problem:

Solution:

Problem:

Solution: Refer to page 2 for instructions on how to assign modems to ports on your system.


20

EDI COMMUNICATIONS

Problem: The modem you are dialing is not responding.

Solution:

Problem: The modem you are dialing is busy.

Solution: Try dialing again later.


21

EDI COMMUNICATIONS

Problem: Your modem is not connected to a telephone line.

Solution:

Problem: The phone lines used by the modems for transmission have been disconnected.

Solution:


22

EDI COMMUNICATIONS

Problem: The Service ID you have selected transmits information at a baud rate that exceeds the transmission capabilities of the modem you are using.

Solution:

Problem: Your modem is not available.

Solution: Check the hardware connections, reset the modem, and then continue.

23

This option is used to dial in to another system using the EDI Directory information that already exists for a trading partner. Auto-dial mode does not enable you to exchange EDI documents with a trading partner. It is used for online services, such as on-site order entry and bulletin board systems (BBS). After this option is selected, a screen similar to the following appears:

The fields on this screen are described beginning on page 2, in the “Send/Receive EDI Documents” section.

In the Seq/code field, EDI directory entries are selected by either their EDI Code or by their Sequence Number.

Upon entry of a valid EDI Code or Sequence Number, the directory information displays for the selected network or trading partner. For more information on the EDI Directory screen fields, refer to page 2.

UTO IAL ODE

3 AUTO-DIAL MODE

24

EDI COMMUNICATIONS

If you need to edit any of this directory information prior to making a connection, you can do so at this time. However, any changes made will only affect this communication session. The EDI Directory record will not be changed.

Pressing [Enter] at the Field prompt starts the communications session. The system begins by looking for a free modem. If it finds one, the system configures the modem (using the information you specified in the EDI Directory information) and dials the Modem#, specified in the EDI Directory information. All of the modem commands are issued automatically and are displayed in the modem window, as shown on the following screen:

For more information on any of the previous screen’s fields, refer to page 2.

If there are any errors, messages display in the modem window. For a complete list of modem errors and solutions, refer to the section titled “Modem Messages.”

3 AUTO-DIAL MODE

25

EDI COMMUNICATIONS

All JCL commands are issued after you press any key. After the JCL commands have been carried out, the Asynchronous EDI Options screen displays:

These options are used to begin and end an auto-dial communications session.

Send/Receive Data

. . . sends and receives data until a control key sequence is entered. A control key sequence value terminates communication sessions. For more information on control key sequence codes, refer to the following paragraphs.

Hang-up Your Modem

. . . disconnects the modem to terminate the session. This is the most commonly used hang-up method. You are completely disconnected from the phone line.

Without Hang-up of Modem

. . . terminates the session without disconnecting the modem. This hang-up method does not drop the modem phone line. If this method is used, you can reengage the session with Manual Dial Mode. For more information on Manual Dial Mode, refer to page 2.

To start the session, select Option #1 to send and/or receive data. This clears the screen and puts you in direct contact with the host system, the computer system into which you have dialed. Any text that you enter is sent directly to that system, except for the control key sequence value displayed in Option #1 on this screen. Entering this key sequence value breaks communication and returns you to this Asynchronous EDI Options screen, allowing you to exit this option or to return to the host system.

The control key sequence is defined by the Option Key field in the EDI Directory record. The control key sequence you specify there is the one which displays in the Option #1 text on the previous screen, and which will bring you back to the Asynchronous EDI Options screen. For more information on the Option Key field, refer to page 2.

After selecting the Send/Receive option, the screen clears and you are in direct contact with the host system. Any text that you type is sent directly to that system.

When you are ready to terminate the session, enter the control key sequence value to display the Asynchronous EDI Options screen, and select either Option #2 or Option #3 on the previous screen. In general, if you have finished using the modem, use Option #2 to disconnect it.

26

The Manual Dial Mode option provides a facility that allows you to access a modem directly. You can issue modem commands, including dialing commands, and check the modem configuration.

Option-Key . . . the control key sequence code that removes you from direct contact with the modem. The control key sequence you specify is the one that displays in Option #1 of the Asynchronous EDI Options screen shown on page 2. This control key sequence is created and defined in the EDI Directory record, described on page 2.

Service ID . . . the ID value you use to configure the modem and/or communications port that you are using.

For more information on setting up your modem(s) and using Service IDs, refer to the section titled “Setting Up Your Modem.”

Pressing [Enter] at the Field prompt takes you to the Asynchronous EDI Options screen, shown as follows.

For more information on these options, refer to page 2.

ANUAL IAL ODE

4 MANUAL DIAL MODE

27

EDI COMMUNICATIONS

This screen works similarly to the functions of auto-dial mode. To start the session, select Option #1 to clear the screen and place you in direct contact with the modem. Any text that you enter is sent directly to the modem. Entering the control key sequence brings you back to the Asynchronous EDI Options screen, allowing you to continue or terminate this session. For more information on the control key sequence value, refer to the EDI Directory Information starting on page 2.

When you are ready to terminate the session, enter the control key sequence to bring up the Asynchronous EDI Options screen, and select either Option #2 or Option #3. In general, if you have finished using the modem, you should use Option #2 to disconnect your modem when you exit.

28

The EDI Directory is a listing of the networks through which you transmit and receive documents with your trading partners. These network records are accessed by the system whenever you select the option to send/receive EDI documents.

Setting up your EDI directory records should be done after setting up your trading partner information for network, trading partner, and interchange information. For more information on setting up EDI communications, refer to the section “Initializing EDI Communications.”

After choosing an EDI code, a screen similar to the following appears:

GENERAL OPTIONS

EDI Code �

. . . code that identifies this EDI directory. The code must be unique and holds up to eight characters.

IRECTORY NFORMATION

5 EDI DIRECTORY INFORMATION

29

EDI COMMUNICATIONS

Name . . . description of the EDI directory. The name can hold up to 30 characters and is displayed on the EDI Directory Listing.

Modem Phone #

. . . phone number of the modem to which you want to connect. Type the phone number exactly how you would enter it using your company’s phone system. Spaces can be used for separations. This field holds up to 29 characters.

Tip! Entering a Modem Number If your phone system requires an extra digit, like 9, to access an outside line, enter this in this field. A “W” character can be used for a waiting, or pause, moment before the actual modem number is dialed by the system. This pause allows the system to wait for the line’s dial tone before continuing with the connection process.

For example, the previous screen of the EDI Directory record shows a modem phone number of 9 W 561 1634. The “9” accesses an outside line, and the “W” tells the system to wait a moment to acknowledge the line’s dial tone.

Type . . . indicates the type of EDI Directory entry. This one-character field can only hold one of two values:

A – The asynchronous type of communication is the most common setting. Sending or receiving data is accomplished in one communication session. You need to establish separate communication sessions for sending and receiving. This is a more reliable method of communication. Selecting asynchronous enables you to specify the Baud Rate, Data Bits, Parity, and Option Key for this entry, as well as accessing the ASCII Transfer Options (see the “ASCII Transfer Options” section on page 2 for more information on these settings). B – The bisynchronous type of communication provides sending and receiving in one communication session. This is an older style of communication that is less reliable due to increased chance of data corruption and the dropping of phone lines. This communications method is usually slower due to slower baud rates. For bisynchronous communications, the parameters, such as Baud Rate, Data Bits, and Parity, cannot be accessed. The ASCII Transfer Options will not be offered.

Baud Rate . . . transfer rate of the connection for this directory entry.

This specifies the port-to-modem speed and can be any of the following values: 1200, 2400, 4800, 9600, 19200, 38400. Some modems may automatically drop to a slower speed to decrease the number of errors in a session, or if the modem you connect to cannot go the speed you specify. The modem-to-modem speed is dictated by the Service ID, modem, and host modem.


30

EDI COMMUNICATIONS

Data Bits . . . indicates the number of data bits in each “word” of the transmission. This field can only be set to 7 or 8.

Parity . . . indicates a character’s quality of being odd or even. A data character is a group of numbers made up of binary zeroes and ones. When data characters (bits) are being transmitted, an extra bit is set so that the total number of ones equals the type of parity selected. N – No parity is defined for the data. This is the most common setting. O – The data has odd parity. There is an odd number of one (1) bits per data word. E – The data has even parity. There is an even number of one (1) bits per character.

JCL Name �

. . . identifies the Job Control Language (JCL) script to be used by this directory entry. JCL Scripts are used to automate routine processes, such as logging in to other systems, and to issue standard sets of commands, such as receiving or sending data. For more information on entering and editing scripts, refer to the chapter “JCL Scripts.” This field holds up to 10 characters.

Network Name

. . . name of the network used for this directory entry. The name you specify here must correspond with the Network Name field in the EDI Setup interchange information for this trading partner. This allows the system to check for interchanges that are ready to be sent to all of the trading partners using this network. It also identifies the network trading partner associated with receiving documents. Interchanges are checked when you use this EDI Directory entry to dial in to the network using the Send and Receive EDI Documents option. This field holds up to 15 characters.

Option Key . . . indicates the key sequence to break out of communication sessions when using this directory entry to dial in to other systems. When this directory entry is used with the Auto-Dial option, the key sequence specified in this field is the default option key. After you have connected to another system, the information you see is that of the other system, not your Prophet 21 system. When you need to disconnect from that system, or return control to your Prophet 21 system, you enter this option key sequence. Usually, this key sequence should be a “control” key sequence; that is, a key that you press while holding down the [Ctrl] key. This provides a means of generating a key sequence that will not be part of your data. If the key sequence you specify is a part of the data you send, the software will react as if you had entered the key sequence manually. Prophet 21 recommends that you use the key sequence [Ctrl][T]. Control key sequences are specified using the caret (“^” or [Shift][6]) character for the [Ctrl] key, so [Ctrl][T] would be specified in this field as “^T”. This is a two-character field.


31

EDI COMMUNICATIONS

Slow Send . . . determines whether a .1 second pause is enabled. The slow send option automatically inserts a .1 second pause between each character that is sent to the other system. This option should only be used when necessary, such as when you are experiencing flow control problems with the host system. When this field is set to:

Y - The Slow Send option is enabled, and a .1 second pause occurs. � N - No pause is made.

Redial Attempts

. . . indicates the number of redial attempts the system makes if the initial attempt to connect is unsuccessful. The system waits 10 seconds before each attempt. As each redial attempt is performed, the redial attempt number and a 10-second delay clock appear at the bottom of the modem window.

Pause for (Dis)connect

. . . determines if a pause for connect and disconnect is issued. When this field is set to: � Y - The system prompts with “Press any key to continue.” If connecting to another

modem, the system pauses and prompts you to enter terminal mode before running the JCL script. If disconnecting, the system issues the hang-up command, hangs up the modem, then prompts you to continue. N - The system does not prompt with “Press any key to continue.” If connecting with another modem, the JCL is automatically executed and the system enters terminal mode. If disconnecting, the system hangs up the modem and automatically returns to the EDI Communication main menu.

ASCII TRANSFER OPTIONS The ASCII Transfer Options control how information is sent and received. The Transmit options determine the control information used during the transmission of ASCII data to another system. The Receive options determine the control information used during the receipt of ASCII data from another system.

Most of the options are available for both transmission and receipt, and work oppositely to each other. For example, if a control sequence is specified for the End of Line String, the system sends this string value (displayed in the Transmit section) after each line it transmits. When the system is receiving data, it expects to receive this string, or it terminates the transfer.

For those features that use control characters, the control sequence must be entered in the format “^X” where X represents the control key. For a list of available control characters, refer to the appendix titled “ASCII Control Characters.”

This screen is accessed only for asynchronous type (Type A) directory entries. To view this screen, press [A]on the EDI Directory screen.


32

EDI COMMUNICATIONS

EDI Code �

. . . code that identifies this EDI Directory.

Transmit

Slow Send . . . determines whether the Slow Send option is enabled. The slow send option automatically inserts a .1 second pause between each character that is sent to the other system. This option should only be used when necessary, such as when you are experiencing flow control problems with the host system. This field holds one of 2 settings:

Y - The Slow Send option is enabled, and a .1 second pause occurs. � N - No pause is made.

Line Pacing Delay

. . . indicates the length of time the system delays between sending each line of data. The length of time is specified in .1 second increments. The decimal is not needed when entering the value. It is not mandatory to enter a value. This is a 2-digit numerical field.

Line Pacing String

. . . identifies the string to be received before sending the next line of data. This string value indicates that the last line of data was successfully received by the other system. This is a 10-digit alphanumeric field.

Time-Out Period

. . . indicates the length of time (in seconds) that the system should wait to receive the Transmit Line Pacing String from the other system. If the string is not received within this specified amount of time, the transfer is aborted. This is a 2-digit numerical field.


33

EDI COMMUNICATIONS

End of Line String

. . . identifies the string that is sent after each line of data. This string is sent in addition to any segment terminator that is included in the data. This is a 10-digit alphanumeric field.

End of Data String

. . . identifies the string that is sent after all of the data has been transmitted. This is a 10-digit alphanumeric field.

Receive

Line Pacing String

. . . specifies the string to be sent to the other system when a line of data is received. This indicates to the other system that the last line of data was successfully received. This is a 10-digit alphanumeric field.

Time-Out Period

. . . specifies the length of time, in seconds, that the system will wait for data from the sending system. If no data is received within this amount of time, the transfer is aborted. This is a 2-digit numeric field.

End of Line String

. . . specifies the string that is sent after each line of data. This string specifies the end of each record. Usually the string makes up one segment, and a segment can consist of up to two records. This is a 10-digit alphanumeric field.

End of Data String

. . . specifies the string that is sent after all the data is received. This string identifies the end of the documents. This is how the Prophet 21 system knows that all the documents have been received. This is a 10-digit alphanumeric field.

34

Each time you dial in to another computer system, either a network or a trading partner, you must log on to that system and enter instructions to send and/or receive data. JCL (Job Control Language) scripts provide a way of storing these instructions and issuing them automatically, every time you connect to a system using an entry in the EDI Directory.

When you choose JCL Scripts from the EDI Communication menu, you are prompted to enter a JCL. A screen similar to the following appears:

JCL Name �

. . . the name of the JCL script.

Lines 1 through 68

. . . hold the commands of the JCL script.

<ESC> for Next

. . . accesses the next screen of the JCL script, if there is one.

“-” for Previous

. . . retrieves the prior screen of the JCL script, if there is one.

CRIPTS

6 JCL SCRIPTS

35

EDI COMMUNICATIONS

“D” to Delete

. . . deletes a command line of the JCL script.

“I” to Insert . . . inserts a command line into the JCL script.

“DE” to delete entire JCL

. . . deletes the whole JCL script. You are prompted with a “Proceed with deletion? (Y N)” message.

“H” Keyword Help

. . . displays the Job Control Language Help screen for asynchronous communications. See page 2 for more information.

“BH” Bisync Help

. . . displays the Job Control Language Help Bisynchronous using Cleo Communication. See page 2 for more information.

“H” FOR KEYWORD HELP The commands for the JCL functions and keywords, that are executed by the JCL, are shown in the following screen. These commands are used for asynchronous communications.

“BH” FOR BISYNC HELP The keywords for the communication partners are used for bisynchronous communications, as opposed to asynchronous. Bisynchronous communication is an IBM standard usually reserved for communication with large mainframe computers, and large trading partners may require this type of communication. This requires a special modem, which is controlled in AIX by a Prophet 21 script. The following keywords are used by this script to pass user-specific information to the trading partner.

6 JCL SCRIPTS

36

EDI COMMUNICATIONS

JCL COMMAND STRINGS JCL information is specified in strings of 20 characters, preceded by a command character usually “>” or a “<”, which indicates whether the string is to be received or sent, respectively. JCL information is specified as a series of “prompts” and “responses,” much the same way that job-queues in the JCM module are specified. You indicate a string of up to 20 characters that you receive from the host system. When your Prophet 21 system receives those characters, it sends the characters that you specify, such as log on commands.

For example, with GE's GEISCO network, the first characters you receive are “U#=”. You then send a string with your user ID, password, and the command “MAILA”. The following JCL information corresponds to these commands:

If you need to specify a string longer than 20 characters, enter a new line with the rest of the string, preceded by a “-” to indicate that this line is a continuation of the previous one. The maximum number of characters you can send at one time using this function is 132. The sample JCL shown used this function to include the last three characters of the “MAILA” command.

You can also include standard ASCII characters or control characters, using the format ^X, where X is the character equivalent. For a list of available control characters, refer to the appendix titled “ASCII Control Characters.”

You can also use the command L to indicate the length of the record you are sending to the host system. Most systems take records of 80 characters, which is the default value. If you need to change this default, specify the new record length, preceded by an L. The maximum record length is 132.

6 JCL SCRIPTS

37

EDI COMMUNICATIONS

Most systems require a “carriage return” at the end of each command that you send them. To add this, specify the ASCII control character M at the end of the command, in the form ^M.

For bisynchronous communications, several special JCL commands are also available. They are described in the chapter “Setting Up JCL Scripts.” These commands cannot be used for asynchronous communications.

JCL FAST RECEIVE When you use the JCL “Receive" command (“}”), the system does not display all of the data as it is received. Instead, the screen is cleared and a message displays showing the number of bytes received. This number is updated as data is received. This makes the receive process much quicker, since the system does not have to display all of the received data.

The JCL “Receive” command (“}”) also causes the JCL to immediately disconnect from the host system after receiving the data.

38

This Assign option is used to link port numbers with EDI modems. You can use this option to assign up to 10 different asynchronous modem port numbers, one bisynchronous port, and any default configuration information for each modem.

You can use up to 10 asynchronous modems on 10 different ports. If the first modem specified here is busy, the system will check the next one, and so on, until the last modem is reached. The port you specify here must be set up for each modem using the Ports module.

This chapter assumes that you have your modem installed on the system. If you need to do this, refer to the “Setting Up Your Modem” section on page 2 for more information.

Choose the Assign option and a screen similar to the following displays:

Modem . . . identifies the sequence number of the asynchronous or bisynchronous modem.

Port # . . . identifies the physical port number of the modem.

SSIGN ODEM ORTS

7 ASSIGN MODEM PORTS

39

EDI COMMUNICATIONS

Default Service ID

. . . sets the default configuration for the specified port. The Default Service ID specifies the configuration for which the modem is set when the Configure modem ports option is used to reset all of your modems to their default configurations. For more information on Service IDs, see the “Service IDs” section on page 2.

Modem Name

. . . name of the modem.

Comm Status

. . . displays the current modem status. If the port or modem cannot be identified or negotiated, it is not available to be used. The Comm Status column will show this modem as offline.

Async . . . identifies the asynchronous modems. Up to ten asynchronous modems can be listed.

Bisync . . . identifies the port of your bisynchronous modem, if one is present. If no bisynchronous modem exists, this field can be left blank. No Service ID is specified since bisynchronous modems have only one configuration.

DELETING A MODEM ASSIGNMENT To delete a modem assignment, enter the sequence number of the modem you wish to delete. With the cursor placed at the Port # field, press [Space Bar]. This blanks out the port assignment. Once erased, press [Enter] through the rest of the fields. This deletes the modem port assignment. The blank row will be filled in from the lower port assignments moving up after you leave this screen.

Entering 9999 at the Port # field will delete all modem port assignments from the current row down.

SETTING UP YOUR MODEM To use the EDI package, you must install a modem and specify certain information so that the system can configure the modem when you use it. You control the modem setup primarily using the Modem Initialization Table. For more information on entering, editing, copying, and printing modem initialization information, refer to the “Modem Initialization Table” chapter on page 2. This table contains a record of modem commands for each modem you use on your system. These commands control the various operating characteristics of the modem during a communications session. Unless you need to change the default values for specific features, you will not need to edit the Modem Initialization Table extensively.

To set up your modems for use with the EDI package, you must know several things:

1. The port# to which each modem is attached 2. What kind of modems you own (brand, speed, etc.) 3. Whether you will be using your modems for incoming calls (e.g., with On-Site customers)

7 ASSIGN MODEM PORTS

40

EDI COMMUNICATIONS

In addition to the Modem Initialization Table, your modems are also controlled by a Service ID, which is a generic code that specifies certain characteristics of modem performance. Service IDs are usually used to control the default configuration of the modem.

When the EDI package is installed, a set of default modems is automatically entered in the Modem Initialization Table. You should check this default list to make sure that your modem is included. Check this list by selecting the Modem Init option on the EDI Communication menu, then choosing the Enter/Edit/Delete option. Browsing at the Modem Name prompt shows you all modems set up in your system. If your modem does not appear, call the EDI Support Team for assistance.

SERVICE IDS Default modem configuration information is controlled by the Service ID that you assign to a port or modem. Service IDs are found under the Assign option of the EDI Communication menu. This identification code consists of six characters that contain configuration information for the modem.

The Service ID contains information about the number of data bits, the parity, and the baud rate for which a modem should be configured. The first character indicates the number of data bits (can only be 7 or 8), and the second character indicates that the data character will have odd (O), even (E), or no (N) parity. The third and fourth characters are taken together to be the first two digits of the port to modem baud speed (96 for 9600, 19 for 19200, or 38 for 38400).

Note: These speeds do not denote the modem to modem connection speed. That is determined at time of a modem to modem successful connection.

A sample Service ID is shown as follows:

This tells the modem that a data character will have 8 bits, no parity, and a port-to-modem baud speed of 38400.

For example, United Stationers uses a Service ID of either 7E96 or 7E38. The most common values for data bits is 8 and for parity is N, so most Service IDs start with 8N such as 8N24 or 8N96.

41

The Configure option is used to return all of your modem ports to their default configurations, defined in the Assign Modem Ports option. Use this option if the original configuration settings of the modem have been changed and now the modem is not working properly.

This option makes changes to the default configurations of the modem. It does not just make temporary changes by the overriding of the Service ID during a particular session. Choose the Configure option, and a screen similar to the following appears:

All of the ports to which you have assigned modems using the Assign Modem Ports option are displayed, along with their specified Default Service IDs. Entering Y at the Continue? prompt configures all of the modems to their Default Service IDs.

When all of the ports have been configured, the following message displays:

Pressing any key takes you back to the EDI Com main menu.

ONFIGURE ODEM ORTS

42

The Modem Initialization Table holds the settings that control how your modem behaves. The purpose of this option is to provide flexibility for you to manipulate your modem. These settings determine such things as if the modem will answer incoming calls, or echo data back to the port (your screen).

Choose the Modem Init option, and you can choose to enter, edit, delete, copy, or list modem initialization information, as shown in the following screen:

Enter/Edit/Delete

. . . adding, editing, and deleting of modem initialization tables. For more information on this feature, refer to the next section.

Copy . . . duplicates an existing modem initialization table to another modem. For more information on this option, refer to page 2.

List . . . prints a listing of all modem initialization tables in your system. For more information on this option, refer to page 2.

ENTER/EDIT/DELETE MODEM INITIALIZATION INFORMATION

Maintenance functions, such as adding, editing, and deleting modem initialization information is performed in the Enter/Edit/Delete option. When this option is selected, the following screen appears:

ODEM NITIALIZATION ABLE

9 MODEM INITIALIZATION TABLE

43

EDI COMMUNICATIONS

The prior settings are part of the “Hayes AT command set.” They are software commands that the modem uses to function in specific ways. These commands are a “modem language” that is hard-wired into most, if not all, asynchronous (regular) modems.

Modem Name �

. . . identifies the initialization table information for this modem. All of the EDI options that refer to a specific modem use this field to identify the modem.

Initialization . . . initialization string that is sent to the modem to prepare it for connection and communication with another modem. The initialization string is used in both the Send and Receive EDI Documents option, and the Auto-Dial option. An Initialization help window displays automatically when you edit this field. Initialization is a 60-character field.

Dialing Prefix

. . . string that is sent to the modem prior to dialing the connection number. This string controls the modem set up for the dialing function and usually consists of the command to dial a number for this modem. A Dial Prefix help window displays automatically when you edit this field. Dialing Prefix is a 15-character field.


44

EDI COMMUNICATIONS

Dialing Suffix

. . . string that is sent to the modem after dialing the connection number. This string controls the modem set up after the dialing function. A Dial Suffix help window displays automatically when you edit this field. Dialing Suffix is a 15-character field.

Hangup Command

. . . string that is sent to the modem to hang up the phone (disconnect from the host system). This field is only used if Drop DTR to hangup is set to N. A Hangup Command help window displays automatically when you edit this field. Hangup Command is a 15-character field.

Modem Silence

. . . stores the string that is sent to the modem to put the modem in "silent" mode, where the modem's responses to the commands you issue are not sent back to the computer. Usually, when you issue modem commands, the modem responds with some kind of message indicating whether or not the command worked, or some information on the new status of the modem. Silent mode suppresses these messages. A Modem Silence help window displays automatically when you edit this field. Modem Silence is a 15-character field.

Command Accept

. . . string that the modem returns if a command is successful. If this message is received by the system, it considers the previous command to have been successful. A Command Accept help window displays automatically when you edit this field. Command Accept is a 15-character field.


45

EDI COMMUNICATIONS

Command Reject

. . . string that the modem returns if a command is unsuccessful. If this message is received by the system, it considers the previous command to have been unsuccessful. A Command Reject help window displays automatically when you edit this field. Command Reject is a 15-character field.

Drop DTR to Hangup

. . . determines how to hang up the modem. In asynchronous data communications, the Data Terminal Ready signal (DTR) indicates to the modem that your terminal is ready to receive data. When the terminal/port is ready to receive data, the DTR is set to On. At disconnection time, the signal is cleared, and the DTR is set to No. This option determines what constitutes a disconnection from the modem, whether a hang-up command (part of the Hayes’ AT command set) or clearing DTR. A Drop DTR To Hangup help window displays automatically when you edit this field.

Drop DTR before Dial

. . . determines how the DTR signal, on your asynchronous connection, acts prior to sending the initialization string to the modem. When this field is set to: Y - The system clears the DTR signal before sending the initialization string to the modem. A Yes response to this question is most common. N - The system leaves the DTR signal as it is before sending the initialization string to the modem. A Drop DTR Before Dial help window displays automatically when you edit this field.


46

EDI COMMUNICATIONS

If DCD Goes Low

. . . determines how the system reacts if the DCD signal is cleared during a connection. In asynchronous data communications, the Data Carrier Detect signal (DCD) indicates to the systems on either end of the connection that a connection exists. When a connection is successful, this signal will be set high; when a connection is broken, the signal is cleared. A signal is cleared if one of the parties involved hangs up. The setting of this field determines how your system reacts if the DCD gets cleared during a communications session. ABRT – If DCD is cleared during a session, the system aborts the session. CONT – If DCD is cleared during a session, the system ignores this and proceeds with the session. An If DCD Goes Low help window displays automatically when you edit this field.

Busy if DCD High

. . . determines how the system reacts if you attempt to use a modem and the DCD is set. If this signal is set, it usually indicates that the modem is connected to another system. When this field is set to: Y – If the DCD is set, the system reports that the modem is in use. N – The system ignores the DCD when attempting to use this modem. A Busy If DCD High help window displays automatically when you edit this field.

Primary Connect Msg

. . . string that the system waits to receive from the modem if a successful connection is made. If this string is received from the modem, and a Secondary connect msg has been specified, the system waits to receive the string specified in the Secondary connect msg field after the Primary connect msg is received. A Primary Connect Message help window displays automatically when you edit this field.


47

EDI COMMUNICATIONS

Secondary Connect Msg

. . . string that the system waits to receive from the modem if a successful connection is made. The system waits to receive the string specified in this field, after the Primary connect msg is received, before reporting a successful connection. A Secondary Connect Message help window displays automatically when you edit this field.

Connect Failed Msg 1

. . . string that the system looks for as it attempts to connect the modem to the another system. If this string, or the string specified in the Connect failed msg 2 field, is received while the modem is trying to connect to another system, the connection is reported as unsuccessful, and the system aborts its connection attempt. A Connect Failed Message help window displays automatically when you edit this field.

Connect Failed Msg 2

. . . string that the system looks for as it attempts to connect the modem. If this string, or the string specified in the Connect failed msg 1 field, is received while the modem is trying to connect to another system, the connection is reported as unsuccessful, and the system aborts its connection attempt. A Connect Failed Message help window displays automatically when you edit this field.

Wait for Connection

. . . length of time (in seconds) that the modem should wait for a connection to be established. If a connection is not established within this amount of time, the system aborts its connection attempt. A Connect Failed Message help window displays automatically when you edit this field. Wait for Connection is a 2-digit numerical field.


48

EDI COMMUNICATIONS

Modem Sync String

. . . when sent to the modem at the end of a call, the string that synchronizes the modem's baud rate with that of the modem port. This allows the modem to be used by other electronic communications modules, such as the On-Site module. A Modem Sync String help window displays automatically when you edit this field.

COPY MODEM INITIALIZATION INFORMATION The Copy option duplicates an existing modem initialization table to another modem.

Source Modem Name �

. . . name of the modem from which you want to copy the initialization information.

Destination Modem Name

. . . name of the modem that is created with the initialization table of the source modem. This name cannot be used by an existing modem.

Pressing [Enter] at the Field prompt begins the copy.

LIST MODEM INITIALIZATION INFORMATION The List option generates a report of all modem initialization tables in your system. The report prints all fields in the modem initialization table.


49

EDI COMMUNICATIONS

SAMPLE: MODEM INITIALIZATION TABLE REPORT

For more information on these fields, refer to their descriptions beginning on page 2.

50

BISYNCHRONOUS COMMUNICATIONS FOR AIX USERS This section discusses bisynchronous setup information specific to users who have purchased the Cleo SYNC cable+ package.

The EDI package currently supports bisynchronous communications with the following communications partners:

Ford GM Advantis-IBM CTX National Bank of Detroit (NBD) Steelco

In bisynchronous communications, the entire session is controlled by the host system, and transmission of data is regulated by specific JCL Script commands, most of which are set. However, the scripts require some information for each communications partner. This information is included in the JCL scripts with specific keywords that identify each piece of information you must include. The keywords and the data needed for each can appear in any order, but must all appear somewhere in the JCL script in order for the transmission to be successful.

ADVANTIS-IBM

Send and Receive

NI Must contain the following string "!NI_IIN"

AC Account Code (specified for you by Advantis-IBM)

UI User ID (specified for you by Advantis-IBM)

P1 Password to be used in the "\*LOGIN" record

P2 Password to be used in the "IELOGIN" record

NN Non-Advantis User Nickname (optional, specified for you by Advantis-IBM)

NA Nickname Account Code (specified for you by Advantis-IBM, must be completed if using a Nickname)

ISYNC OM OG

10 BISYNC COM LOG

51

EDI COMMUNICATIONS

NU Nickname User ID (specified for you by Advantis-IBM, must be completed if using a Nickname)

NS Nickname System ID (specified for you by Advantis-IBM, optionally completed if using a Nickname)

NATIONAL BANK OF DETROIT (NBD)

Receive Only

NI Must contain the following string "!NI_NBD"

DC Destination Code

FI File indicator

AV Authentication value

FORD

Send

NI Must contain the following string "!NI_FORD-SEND"

UC User Code (specified for you by Ford)

PW Password (for your User Code)

Receive

NI Must contain the following string "!NI_FORD-RECEIVE"

UC User Code (specified for you by Ford)

PW Password (for your User Code)

GM

Send and Receive

NI Must contain the following string "!NI_GM"

TC Transmission Code (specified for you by GM)

DC Destination Code (specified for you by GM)

PW Password

10 BISYNC COM LOG

52

EDI COMMUNICATIONS

NP New Password; used only when changing your Password

FN Must always contain the Filename, determined as follows:

Either "EDI997PROD" or "EDI997TEST" when sending 997s

Either "EDI843PROD" or "EDI843TEST" when sending 843s

Because GM can only accept one transaction set type per transmission, two separate JCLs (one each for the 997 and 843 Transaction Sets) must be entered. The only difference between the two is the filenames. As a result of the need for two JCLs, two EDI directories are also necessary, one for each JCL. The 997 and 843 Transaction Sets cannot be enveloped and sent together.

CTX

Send and Receive

NI Must contain the following string "!NI_CTX"

UI User ID (specified for you by CTX)

PW Password

NP New Password; used ONLY when changing your Password

SI Station ID-Deliver Command

DS Destination Station-Deliver Command

RE Reference-Deliver Command

AI Application ID-Deliver Command

MC Message Class-Deliver Command

AT ATT Message Class Code to Receive; used only when performing ATT testing

CT RETRIEVE Retrieves information from files that have already been sent to CTX

CT LIST Lists information from files that are ready to be sent by CTX

OS AIX Allows you to specify an AIX file on your system that will initiate commands on the CTX system

10 BISYNC COM LOG

53

EDI COMMUNICATIONS

STEELCO

Receive

NI Must contain the following string "!NI_STC"

UI User ID (specified for you by Steelco)

BI Batch ID (specified for you by Steelco)

SEND/RECEIVE PROCEDURE Sending and receiving procedures are performed in the same manner as those for asynchronous communications. For step-by-step instructions, refer to the “Send/Receive EDI Documents” chapter on page 2.

During the session, each step performed by the Prophet 21 system is reported on the Bisynchronous Communications Log. You do not see these steps displayed on the screen. Instead, the following message displays:

While this message displays, you must wait.

The Cleo Communications package maintains the Bisynchronous Communications Log, a journal containing the detailed description of each session. This journal file can be viewed and cleared, if Q-Mode is activated. The journal can be used to troubleshoot failed sessions, and also to track when data is sent or received.

BISYNCHRONOUS COMMUNICATIONS LOG The Cleo Communications optional package is third party software that is installed in AIX. It is necessary software for Prophet 21 to do bisynchronous communications. You would need this to control a bisynchronous modem.

The Bisync Com Log option appears when this optional package is enabled. The following screen appears when this option is selected:

To print the log, enter Yes to proceed. If Q-Mode is enabled, you are prompted to clear the log:

10 BISYNC COM LOG

54

EDI COMMUNICATIONS

Enter CL to clear the log. To avoid any modem interference that would interrupt the communications session, the bisynchronous modem should not be in use while it is being cleared.

SAMPLE: BISYNCHRONOUS COMMUNICATIONS LOG

The Bisynchronous Communications Log records the commands that go back and forth between you and your trading partner.

55

The Journals option prints EDI Communications journals for both sent and received documents, allowing you to monitor the transmissions between you and your trading partners. Choosing this option displays the following menu:

Sent . . . prints the journal of sent documents. For more information on this option, refer to the next section.

Received . . . prints the journal of received documents. For more information on this option, refer to page 2.

CTX . . . prints the CTX file list. The CTX (Chrysler Telecommunications Exchange) file list is a report of recently sent or received EDI documents residing in your CTX (Chrysler) mailbox. To see this list of documents in the CTX mailbox, dial Chrysler, download the file to the Prophet 21 system, and then print the list. For more information on this feature, refer to page 2.

When printing is complete, the system returns to the Journals menu. If no data exists to print for the selected journal, nothing is printed and the system returns to the Journals menu.

SENT DOCUMENTS The EDI Event Journal of Sent Documents lists all EDI documents sent to trading partners since the last time the journal was cleared.

OURNALS

11 JOURNALS

56

EDI COMMUNICATIONS

SAMPLE: EDI EVENT JOURNAL OF SENT DOCUMENTS

Entry Number

. . . system-assigned number given to the sent transmission. In each transmission, more than one document can be sent. Documents are listed by Detail #.

Date/Time . . . date and time the document was sent.

User ID . . . login ID of the person who sent the document.

Network Name

. . . name of the network.

Modem Port #

. . . number of the modem port. Every modem is attached to a physical port.

Directory Name

. . . name of the directory.

Detail # . . . system-assigned number to each document within the journal in chronological order.

TP ID . . . identification number of the trading partner.

Doc # . . . unique number assigned to each document. Each document number is tracked in the EDI Doc module.

11 JOURNALS

57

EDI COMMUNICATIONS

If Q-Mode is activated, journals can be cleared after they have been printed. The following message displays after the journal prints:

Pressing [Enter] takes you back to the Journals menu; entering "CL" clears the journal. The following message displays after CL is entered:

All entries have been removed from the journal. Pressing any key takes you back to the Journals menu.

RECEIVED DOCUMENTS The EDI Event Journal of Received Documents lists all EDI documents received from trading partners since the last time the journal was cleared.

SAMPLE: EDI EVENT JOURNAL OF RECEIVED DOCUMENTS

Entry Number

. . . system-assigned number given to the received transmission. In each transmission, more than one document can be received. Documents are listed by Detail #.

Date/Time . . . date and time the document was received.

11 JOURNALS

58

EDI COMMUNICATIONS

User ID . . . login ID of the person who received the document.

Network Name

. . . name of the network.

Modem Port #

. . . number of the modem port. This number is the physical port number to which the modem is attached.

Directory Name

. . . name of the directory. The directory holds the number and name of the network used to transmit documents to or from the trading partner.

Detail # . . . system-assigned number given to each document within the journal in chronological order. More than one document can be received in each transmission.

TP ID . . . identification number of the trading partner.

Doc # . . . unique number assigned to each document. Each document number is tracked in the EDI Doc module.

If Q-Mode is activated, journals can be cleared after they have been printed. The following message displays after the journal prints:

Pressing [Enter] takes you back to the Journals menu; entering "CL" clears the journal. The following message displays after CL is entered:

All entries have been removed from the journal. Pressing any key takes you back to the Journals menu.

CTX FILE LISTING CTX is Chrysler. Chrysler is one of those trading partners who require bisynchronous communications. They allow you to dial directly into their system to send and receive documents, thus bypassing the VAN. Like a VAN, Chrysler provides a “mailbox” for every trading partner in which they place documents to be received by you, and you place documents in this mailbox to be received by Chrysler.

11 JOURNALS

59

EDI COMMUNICATIONS

A CTX Listing is a listing of all documents in the mailbox. To print this report, you need to communicate with Chrysler and download the mailbox listing. This downloaded file is placed in AIX, and this report retrieves the information from this file and prints it.

The CTX option displays the listing of all CTX files in your system. This option allows you to view or print the list, but does not generate the report. To generate the CTX File Listing, run the List JCL (as described in the section entitled “Writing Your Own CTX Job”).

Important! To be sure you are printing an up-to-date list, you should dial Chrysler, using the List JCL, and download the latest mailbox listing. The following shows a sample report:

SAMPLE: CTX FILE LISTING OF INBOUND FILES

For definitions of these report headings, refer to your Chrysler documentation.

If CTX files do not exist in the system, the following message appears:

Unlike the journals, you cannot clear the CTX File List. It is replaced by a new list the next time you run the LIST JCL.

For more information on CTX and the List JCL, refer to the “CTX (Direct Connection for AIX Users Only)” section on page 2.

60

Setting up the JCL scripts for networks and proprietary trading partners involves entering the JCL and then entering the JCL’s name in the corresponding directory. In most cases, the JCLs include a password and other specific information used to send and receive data, making the dial-in process fully automated. All that is necessary to send or receive data to or from a network/trading partner is specifying the appropriate directory. The JCL scripts themselves differ from each other, but the general steps involved in using the JCL to send and receive are the same on every system.

Prophet 21 supports the following networks:

♦ General Electric's GEISCO ♦ Trade Route

♦ ORDERNET ♦ Johnson & Johnson (850 and 855 only)

♦ Kleinschmidt ♦ Advantis-IBM (bisync only)

♦ Equipment Industry Network (EIN) ♦ National Bank of Detroit (bisync only)

♦ Harbinger ♦ Ford (bisync only)

♦ Tymenet Network MCI ♦ GM (bisync only)

♦ AT&T Easy Link ♦ CTX (bisync only)

♦ 3M ♦ UPTECH

♦ Walmart (bisync only)

Prophet 21 supports the following trading partners:

♦ United Stationers

♦ Lynn Edwards

♦ Stationers

♦ SP Richards

♦ O'Henry

♦ Lynn Edwards Wrap & Ship

♦ Boise Cascade/Associated Stationers

♦ Steel Company

Unless otherwise noted, communications with these networks/trading partners take place asynchronously. Further information on bisynchronous networks is available in the section entitled "Bisynchronous Communications for AIX Users."

ETTING P CRIPTS

12 SETTING UP JCL SCRIPTS

61

EDI COMMUNICATIONS

While the EDI package can be used to dial into any host system, these are the only networks/trading partners for which Prophet 21 supplies a description of the JCL commands needed to dial in, send, and receive information. The JCL scripts themselves and any specific or suggested directory information needed for each script is included in the sections that follow. For more information on entering JCLs and directories, refer to the "JCL Scripts" and the "EDI Directory Information" chapters. Also, some of these networks and proprietary trading partners require the use of certain file transfer protocols. File transfer protocols and the networks/proprietary trading partners that use them are explained in the "File Transfer Protocols" section.

In the JCL listings that follow, the underscore character ("_") represents a space. However, you can uses spaces to enter a space between words.

SAMPLE SCRIPTS The following section describes JCL scripts for sending and receiving data.

GE’S GEISCO

JCL FOR SENDING DATA TO GEISCO

FUNCTION COMMANDS IN JCL SCRIPTS

The following symbols, or function commands, perform specific functions in a JCL script:

< . . . sends string to the receiving modem.

> . . . looks for a match to the received information.


62

EDI COMMUNICATIONS

- . . . represents a continuation of the previous command.

{ . . . sends data from the specified file. Filename follows the bracket.

} . . . receives data into the specified file. Filename follows the bracket.

L . . . sets record length.

^M . . . represents a carriage return.

More help keyword definitions are found under the “JCL Scripts” section on page 2.

All JCL scripts that apply for your networks and proprietary trading partners will need to be set up in the system. The following are sample JCL scripts that you can enter through the JCL Scripts option.

JCL FOR RECEIVING DATA FROM GEISCO JCL Name: GEISCO RCV 1 <HHH 2 >U#= 3 <LLLLLLLL,PPPPPPPP,MA (*See the following note.) 4 -ILA^M 5 >---_-------_---- 6 >SELECTION: 7 <:SET_FN,15^M 8 >SELECTION: 9 <DATA^M 10 >SELECTION: 11 <RECV^M 12 <-WAIT15- 13 >SELECTION: 14 <RET^M 15 >SELECTION: 16 <REP^M 17 >SELECTION: 18 <LIST_MAILALLL^M (*See the following note.) 19 >MAILALLL 20 }EDDONX 21 <RET^M 22 >SELECTION: 23 <HEL^M 24 >U#=

Note: In these JCL listings, the JCL names are suggested. "LLLLLLLL" represents your logon number on GEISCO; "PPPPPPPP" represents your password; and "LLL" represents the last three digits of your logon number. When entering these JCL scripts, you should substitute the logon and password provided to you by GEISCO.

The directories for each of these JCL scripts should be entered as follows.


63

EDI COMMUNICATIONS

The information in fields 1 and 2 is suggested information. Modem Phone # is assigned by GEISCO; the Baud Rate depends on your modem. The JCL Name must agree with the name entered in the corresponding JCL script; the Network Name should be the same as the Network Name specified in the Network Information screen found in the EDI Setup Trading Partner options. The remaining information must be entered as it appears here. The ASCII Transfer Options must be completed as in the following screen.


64

EDI COMMUNICATIONS

ORDERNET Users connect to Ordernet via the BT Tymenet and CompuServe networks (contact Ordernet to complete which of these two you will be using).

BT TYMENET

JCL for Sending Data to Ordernet via BT Tymenet JCL Name: ONET SND 1 <-WAIT15- 2 <O 3 >log in: 4 <^R^X 5 <-WAIT2- 6 <SSEDI;X25PDN1^M 7 >CONNECTED 8 >^M^J 9 <-WAIT3- 10 <LOGON^M^D 11 >INPUT^M^D 12 <$$ADD ID=XXXXXD BATC (*See the following note.) 13 -HID='YYYYYYY'^M (*See the following note.) 14 {EDDONX 15 <^D 16 >SUPERTRACS

JCL for Receiving Data from Ordernet via BT Tymenet JCL Name: ONET REC 1 <-WAIT15- 2 <O 3 >log in: 4 <^R^X 5 <-WAIT2- 6 <SSEDI;X25PDN1^M 7 >CONNECTED 8 >^M^J 9 <-WAIT3- 10 <LOGON^M^D 11 >INPUT^M^D 12 <$$REQUEST ID=XXXXXD (*See the following note.) 13 -BATCHID='YYYYYYY'^M^ (*See the following note.) 14 -D 15 }EDDONX

COMPUSERVE

JCL for Sending Data to Ordernet via CompuServe JCL Name: ONET SND 1 <-WAIT3- 2 <^M


65

EDI COMMUNICATIONS

3 >: 4 <+^M 5 >Host Name: 6 <ONET,SSGATE^M 7 >ONET 8 <LOGON^M 9 <-WAIT16- 10 >INPUT 11 <$$ADD ID=XXXXXD BATC (*See the following note.) 12 -HID='YYYYYYY'^M (*See the following note.) 13 {EDDONX 14 <^D 15 >SUPERTRACS

JCL for Receiving Data from Ordernet via CompuServe JCL Name: ONET REC 1 <-WAIT3- 2 <^M 3 >: 4 <+^M 5 >Host Name: 6 <ONET,SSGATE^M 7 >ONET 8 <LOGON^M 9 <-WAIT16- 10 >INPUT 11 <$$REQUEST ID=XXXXXD (*See the following note.) 12 -BATCHID='YYYYYYY'^M^ (*See the following note.) 13 -D 14 }EDDONX 15 <^D 16 >SUPERTRACS

Note: In these JCL scripts the JCL names are suggested. JCL names, "XXXXX" represents your user ID on Ordernet, and "YYYYYYY" represents your password. When entering these JCL scripts, you should substitute the user ID and password provided to you by Ordernet.

KLEINSCHMIDT

JCL FOR SENDING DATA TO KLEINSCHMIDT JCL Name: KL SND 1 <-WAIT2- 2 <^M 3 >: 4 <SIGNON XXXXXX,YYYYYY (*See the following note.) 5 -^M 6 >ACCEPTED^M^J: 7 <SET_ECHO_OFF^M 8 {EDDONX 9 <SET_ECHO_ON^M 10 <#SIGNOFF^M


66

EDI COMMUNICATIONS

JCL FOR RECEIVING DATA FROM KLEINSCHMIDT JCL Name: KL RCV 1 <-WAIT2- 2 <^M 3 >: 4 <SIGNON XXXXXX,YYYYYY (*See the following note.) 5 -^M 6 >ACCEPTED^M^J: 7 <#SEND_EDIDATA^M 8 <#EOF^M 9 }EDDONX 10 <#SIGNOFF^M

JCL FOR RECEIVING PREVIOUSLY RECEIVED DATA FROM KLEINSCHMIDT JCL Name: KL RCVP 1 <-WAIT2- 2 <^M 3 >: 4 <SIGNON_XXXXXX,YYYYYY (*See the following note.) 5 -^M 6 >ACCEPTED^M^J: 7 <#SEND_EDIDATA,PRIOR^ 8 -M 9 <#EOF^M 10 }EDDONX 11 <#SIGNOFF^M

Note: In these JCL scripts the JCL names are suggested JCL names, "XXXXXX" represents your party ID on Kleinschmidt, and "YYYYYY" represents your password. When entering these JCL scripts, you should substitute the Party ID and password provided to you by Kleinschmidt. The JCL for Receiving Previously Received Data allows you to receive the last document sent by Kleinschmidt. To receive any other previously received documents, notify Kleinschmidt of that document's Interchange Control Number, so that Kleinschmidt can reload that document. Kleinschmidt cannot reload any documents older than five days.

EQUIPMENT INDUSTRY NETWORK (EIN)

JCL FOR SENDING DATA TO EIN JCL Name: EIN SND 1 >FOR_INPUT 2 <^B$$ADD_ID=XXXXXXX_B (*See the following note.) 3 -ATCHID='YYYY_*_ORIGI (*See the following note.) 4 -NATOR EDI *'^M^J 5 {EDDONX 6 <^M^J^C 7 >FOR_INPUT

JCL FOR RECEIVING DATA FROM EIN JCL Name: EIN REC 1 >FOR_INPUT


67

EDI COMMUNICATIONS

2 <^B$$REQUEST_ID=XXXXXXX (*See the following note.) 3 -10_BATCHID='YYYY ALL (*See the following note.) 4 -'_MEDIA=BX^M^J^C 5 }EDDONX 6 >FOR_INPUT

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM EIN JCL Name: EIN BOTH 1 >FOR_INPUT 2 <^B$$ADD_ID=XXXXXXX_B (*See the following note.) 3 -ATCHID='YYYY_*_ORIGI (*See the following note.) 4 -ATOR_EDI_*'^M^J 5 {EDDONX 6 <^M^J^C 7 >FOR_INPUT 8 <^B$$REQUEST_ID=XXXXXXX (*See the following note.) 9 -XX_BATCHID='YYYY_ALL 10 -'_MEDIA=BX^M^J^C 11 }EDDONX 12 >FOR_INPUT

Note: In these JCL listings the JCL names are suggested. "XXXXXXX" represents your User Security Code on EIN, and "YYYY" represents your password. When entering these JCL scripts, you should substitute the security code and password provided to you by EIN.

HARBINGER

JCLS FOR SENDING DATA TO AND RECEIVING DATA FROM HARBINGER

1. From the EDI Communication menu, choose JCL Scripts.

2. Enter the following two JCL scripts:

JCL name: HAR-XSEND 1 <^M 2 >LOGON 3 <XXXXXXXX,YYYYYY^M (XXXXXX = Your Login ID) 4 >EDIREADY (YYYYYY = Your Login Password) 5 <TRANSFER,X,EDFROM,50 6 -000^M 7 >CONTINUE 8 >-XMODEM ON- 9 {EDDONX 10 >-XMODEM OFF- 11 >SAVED^M 12 >EDIREADY 13 <LOGOFF^M JCL name: HAR-XRCV 1 <^M 2 >LOGON 3 <XXXXXXXX,YYYYYY^M (XXXXXX = Your Login ID)


68

EDI COMMUNICATIONS

4 >EDIREADY (YYYYYY = Your Login Password) 5 <RECEIVE^M 6 >-TIMEOUT120 7 >TRANSFER,X,EDTO, 8 <CONTINUE^M 9 >-TIMEOUT10 10 >-XMODEM ON- 11 }EDDONX 12 >-XMODEM OFF- 13 <SAVED^M 14 >EDIREADY 15 <LOGOFF^M

3. From the EDI Communication menu, choose EDI Directory.

4. Edit the existing EDI directories to change the highlighted fields as indicated.

5. Change the Modem Phone # field to use the new phone number as listed.

6. Change the JCL name to HAR-XSEND.

7. Type A and press [Enter] at the Field prompt to access the ASCII data transfer options.

8. Make sure the fields on this screen are completed as shown.


69

EDI COMMUNICATIONS

9. Repeat Step 3 through Step 8 for the Harbinger Receive Directory, substituting: HAR-XRCV for the JCL name in Field 1. HARBINGER XMODEM RECV for the name in Field 2. HAR-XRCV for the JCL in Field 8.

10. Make sure the fields on this screen are completed as shown.


70

EDI COMMUNICATIONS

11. From the EDI Communication menu, choose Assign.

12. Change the modem name of your asynchronous modem to Microcom-Directrel.

TYMENET/MCI NETWORK

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM TYMENET/MCI NETWORK JCL name: BOTH 1 <-WAIT5- 2 <A 3 <-WAIT5- 4 <EDIXPC01;XPC*EDI^M 5 <-WAIT2- 6 <LLLLLLLL;PPPPPP; (*See the following note.) 7 -X130;^M 8 >EDI*NET 9 }EDDONX 10 {EDDONX 11 <Î 12 >Î 13 >Î 14 <-WAIT10-

AT&T EASY LINK

JCL FOR SENDING DATA TO AT&T JCL name: AT&T SND 1 <-WAIT5 2 <^M 3 <-WAIT1- 4 <^M


71

EDI COMMUNICATIONS

5 >Name: 6 <XXXXXXXXXX^M (*See the following note.) 7 >Password: 8 <PPPPPPPPPP^M (*See the following note.) 9 >Command: . 10 <SDEUL_USING_XMODEM_V 11 -ERSION_2^M 12 >File 13 >-XMODEM_ON- 14 <>To:_!EDI^M 15 <Content-Type:_x12^M 16 <^M 17 {EDDONX 18 >-XMODEM_EOT- 19 >Command: . 20 <QUIT^M

JCL FOR RECEIVING DATA FROM AT&T 1 <-WAIT5 2 <^M 3 <-WAIT1- 4 <^M 5 >Name: 6 <XXXXXXXXXX^M (*See the following note.) 7 >Password: 8 <PPPPPPPPPP^M (*See the following note.) 9 >Command: . 10 <SDEDL_IN.NEW_USING_X 11 -MODEM_VERSION_2^M 12 >SEND_File 13 >-XMODEM_ON- 14 }EDDONX 15 >-XMODEM_OFF- 16 >Command: . 17 <QUIT

Note: In these JCL listings the JCL names are suggested. "XXXXXXXXXX" represents your User Name on AT&T, and "PPPPPPPPPP" represents your password. When entering these JCL scripts, you should substitute the user name and password provided to You by AT&T.

RAILINC Using RAILINC does not require any JCL scripts. A Directory for connecting to RAILINC must be entered; this directory must be specified when dialing in to RAILINC. Once a connection has been made, documents are sent and received automatically.


72

EDI COMMUNICATIONS

RAILINC DIRECTORY FOR SENDING AND RECEIVING DATA

The information in field 1 is suggested information. Your RAILINC Logon and Password should be entered in the Name field in the following format: "Logon/Password". Modem Phone # is assigned by RAILINC; the Baud Rate depends on your modem. The JCL Name field should be left blank; the Network Name should be the same as the network name specified in the Network Information screen found in the EDI Setup Trading Partner options. The remaining information must be entered as it appears here. The ASCII Transfer screen must be completed as follows:

UPTECH The UPTECH dial-in process is not fully automated. You must first use the login JCL to login and then issue either the send or receive character before any information can be sent/received.


73

EDI COMMUNICATIONS

JCL FOR LOGGING ON TO UPTECH JCL name: UNION LOGON 1 <^M 2 >UPRR 3 <ISR*ZZ*XXXXXXXX*ZZ* 4 -WWWWWWWW*ALL**999

Note: In this JCL listing "UNION LOGON" is a suggested JCL name. "XXXXXXXX" is your UPTECH password, and "WWWWWWWW" is your UPTECH user ID. When entering this JCL script, you should substitute the password and user ID provided to you by UPTECH.

SENDING DATA TO UPTECH

To send data to UPTECH, issue the "Send" command after login.

This begins the transmission of all of the data stored in the EDI "send" file. You will see all of the interchanges as they are being sent. When transmission stops, you issue the "breakout" sequence ([Ctrl][D]) to signal the end of data transmission:

After you issue the "breakout" sequence, a message displaying the current system date and time displays:

You have now finished sending data. You can disconnect (by pressing [Esc]), or perform some other function.

RECEIVING DATA FROM UPTECH

To receive data from the UPTECH network, simply log on and turn on Record Mode.

You will see all of the data from all of the interchanges that you are receiving as they print to your terminal. When all of the data has been received, you can disconnect or send data.

Turn Record Mode off by issuing the "Receive" command ([{]) again.


74

EDI COMMUNICATIONS

LOGGING OFF FROM UPTECH

The UPTECH network does not require you to logout. Simply press [Esc] to disconnect the modem; you are logged out automatically.

The modem disconnect commands display in the Modem Window, and if you have received documents, the despooling information displays automatically.

TRADE ROUTE The Trade Route dial-in process is not fully automated. You must first use the login JCL script to login and issue either the send or receive character before any information can be sent/received.

JCL name: TRADE LOGON 1 <.^M 2 >DATAPAC: 3 <79400900^M 4 >USAGER? 5 <EDI.UUUUUUUUUU 6 >BBBBBBBB 7 <XXXXXXXX^M 8 >VVVVVVVV

Note: In this JCL listing, "TRADE LOGON" is a suggested JCL name. "UUUUUUUUUU" represents your Nom D'Usager (user ID) on Trade Route, and "XXXXXXXX" represents your Mot De Passe (password). When entering this JCL script, you should substitute the Nom D'Usager and Mot De Passe provided to you by Trade Route.

Trade Route requires that you change your password every three months. To change your password, contact Trade Route to receive your new password assignment and then edit this JCL to reflect this change.

SENDING DATA TO AND RECEIVING DATA FROM TRADE ROUTE

To send data to and receive data from Trade Route, login and issue either the "Send" or "Receive" command. These commands and any related procedures must be supplied to you by Trade Route. Trade Route can also supply you with the necessary information about logging out once your communications session is complete.

JOHNSON & JOHNSON'S COACT NETWORK

JCL FOR SENDING 850 TRANSACTION SETS TO JOHNSON & JOHNSON

JCL name: J&J SEND 1 <-WAIT6- 2 >REQUEST^M 3 <LOGON LLLLLLL^M^J (*See the following note.) 4 >MMMM: 5 <PPPPP^M^J (*See the following note.) 6 >READY 7 <ANSI850^M^J 8 >EDIREADY^M^J 9 <TRANSFER,A,ORDER,,60


75

EDI COMMUNICATIONS

10 -0^M^J 11 >CONTINUE^M^J 12 {EDDONX 13 <EDIEOF^M 14 >SAVED^M^J 15 <-WAIT5- 16 <LOGOFF^M^J 17 >****** 18 <-WAIT5-

JCL FOR RECEIVING 855 TRANSACTION SETS FROM JOHNSON & JOHNSON JCL name: J&J RECV 1 <-WAIT6- 2 >REQUEST^M 3 <LOGON LLLLLLL^M^J (*See the following note.) 4 >MMMM: 5 <PPPPP^M^J (*See the following note.) 6 >READY 7 <ANSI850^M 8 >EDIREADY^M^J 9 <RECEIVE^M 10 >-TIMEOUT90- 11 >CONFIRM^M^J 12 <CONTINUE^M 13 }EDDONX 14 <SAVED^M 15 <-WAIT2- 16 <LOGOFF^M 17 >****** 18 <-WAIT2-

Note: In these JCL listings, the JCL names are suggested JCL names. "LLLLLLL" represents your Johnson & Johnson login, and "PPPPP" represents your password. When entering these JCL scripts, you should substitute the login and password provided to you by Johnson & Johnson.

ADVANTIS-IBM

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM ADVANTIS-IBM FOR AIX USERS

JCL name: ADV BOTH 1 !NI_IIN 2 !AC_XXXX 3 !UI_YYYYYYY 4 !P1_ZZZZZZZ 5 !P2_VVVVVVV 6 !NN_NNN 7 !NA_XXXX 8 !NU_YYYYYYY 9 !NS_SSSSS


76

EDI COMMUNICATIONS

Note: In this JCL listing, "ADVBOTH" is a suggested JCL name. "XXXX" represents your account ID; "YYYYYYY" represents your user ID; "ZZZZZZZ" represents your I/LOGON password, and "VVVVVVV" represents your IELOGON password. When entering this JCL script, you should substitute the Account ID, User ID, and passwords provided to you by Advantis-IBM.

The remaining fields should only be used when your trading partner is not using Advantis, in other words, you are "crossing" networks. "NNN" represents the Nickname of the non-Advantis user that you intend to connect with. You must complete an account ID in Field 7 and a user ID in Field 8 for this user. "SSSSS" is an optional field and represents the system ID for the non-Advantis user. When entering this JCL, you should substitute the nickname, account ID, user ID, and system ID provided to you by Advantis-IBM.

Advantis-IBM requires that users change their password every 30 days. To change your password, you must contact Advantis-IBM in order to receive your new password assignment, and then edit the Send/Receive JCL to reflect these changes.

NATIONAL BANK OF DETROIT (DIRECT CONNECTION FOR AIX USERS ONLY)

The National Bank of Detroit (NBD) allows users to receive data; Prophet 21 does not support sending data to NBD.

JCL FOR RECEIVING DATA FROM NBD FOR AIX USERS JCL name: NBD RCV 1 !NI_NBD 2 !DC_DDDDDDDD 3 !AV_AAAAAAAA 4 !FI_FFFFFFFF

Note: In this JCL listing, "NBD RCV" is a suggested JCL name. "DDDDDDDD" represents your NBD Destination Code; "AAAAAAAA" represents your Authentication Value, and "FFFFFFFF" represents your File Indicator. When entering this JCL, you should substitute the Destination Code, Authentication Value, and File Indicator provided to you by NBD.

FORD (DIRECT CONNECTION) Ford provides a means of connecting to its computer system directly, using a bisynchronous connection. Though it is not a third-party network, it operates the same way a bisynchronous network does.

JCL FOR SENDING DATA TO FORD FOR AIX USERS JCL name: FORD SND 1 !NI_FORD-SEND 2 !UC_XXXXX 3 !PW_YYYYY

JCL FOR RECEIVING DATA FROM FORD FOR AIX USERS JCL name: FORD RCV 1 !NI_FORD-RECEIVE 2 !UC_XXXXX 3 !PW_YYYYY


77

EDI COMMUNICATIONS

Note: In these JCL listings, the JCL names are suggested. "XXXXX" represents your user code, and "YYYYY" represents your password on Ford. When entering these JCL scripts, you should substitute the user code and password provided to you by Ford.

GM (DIRECT CONNECTION) GM provides a means of connecting to its computer system directly, using a bisynchronous connection. Though it is not a third-party network, it operates the same way a bisynchronous network does.

JCL FOR SENDING/RECEIVING 997 TRANSACTION SETS TO/FROM GM FOR AIX USERS

JCL name: GM 997 BOTH 1 !NI_GM 2 !TC_XXX 3 !DC_DDD 4 !PW_YYYYY 5 !NP_ZZZZZ 6 !FN_EDI997PROD

JCL FOR SENDING/RECEIVING 843 TRANSACTION SETS TO/FROM GM FOR AIX USERS

JCL name: GM 843 BOTH 1 !NI_GM 2 !TC_XXX 3 !DC_DDD 4 !PW_YYYYY 5 !NP_ZZZZZ 6 !FN_EDI843PROD

Note: In these JCL listings, the JCL names are suggested. "XXX" represents your Transmission Code; "DDD" represents your Destination Code; "YYYYY" represents your Password, and "ZZZZZ" represents your new password on GM. When entering these JCL scripts, you should substitute this information with the appropriate information provided to you by GM.

GM requires that you change your password every six months. To change your password, include the new password in the !NP line. If you are not changing your password, the new password can be omitted.

CTX (DIRECT CONNECTION FOR AIX USERS ONLY) CTX provides a means of connecting to its computer system directly, using a bisynchronous connection. Though it is not a third-party network, it operates the same way a bisynchronous network does.

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM CTX FOR AIX USERS JCL name: CTX 1 !NI CTX 2 !UI UUUUUUUU (*See following note.) 3 !PW PPPPPPPP 4 !NP NNNNNNNN


78

EDI COMMUNICATIONS

5 !SI SSSSSSSS 6 !DS DDDDDDDD 7 !RE RRRRRRRR 8 !AI AAAAAAAA 9 !MC MMMMMMMM 10 !AT TTTTTTTT

Note: In this JCL listing, "CTX" is a suggested JCL name. Each string of letters represents a specific value:

UUUUUUUU . . . user ID. PPPPPPPP . . . password. . . . new password (to be included only when changing your password). SSSSSSSS . . . station ID.

DDDDDDDD . . . destination station. RRRRRRRR . . . reference. AAAAAAAA . . . application ID.. MMMMMMMM . . . message class. TTTTTTTT . . . AT&T message class receiving code and is for testing purposes only.

When entering this JCL script, you should substitute this information with the appropriate information provided to you by CTX.


79

EDI COMMUNICATIONS

The directory for this JCL should be entered as follows:

Important! For a 4800 baud speed modem, the modem phone number is 810-274-5055. For a 2400 baud modem, the number is 810-274-5085. The modem phone number must be the number assigned for your modem speed. Bisynchronous modems only transmit at one speed so the CTX receiving modem must match your modem’s baud rate. This is why it is important for you to assign the correct phone number based on your modem’s speed.

The information in fields 1 and 2 is suggested information; Modem Phone # is assigned by CTX. CTX is a bisynchronous network; therefore the Type must be specified as B and the Baud Rate, Parity, and Data bits fields are not used. The JCL Name must agree with the name entered in the corresponding JCL; the Network Name should be the same as the Network Name specified in the Network Information screen found in the EDI Setup Trading Partner options. The remaining information must be entered as it appears here. Bisynchronous directories do not use an ASCII Transfer screen.

In most situations, you will use the basic send/receive JCL script (shown previously). However, Prophet 21 provides you with three additional JCL scripts, which allow you to do the following: retrieve information that has already been delivered, obtain a list of CTX files, and take CTX job commands from an AIX file. These JCL scripts satisfy the needs of most users. If you find that they do not, you can also write your own custom CTX job. For more information on writing a custom CTX JCL script, refer to the section “Writing Your Own CTX Job” on page 2.

The directories for these JCL scripts are identical to the previous script shown, except for the JCL name. You can either enter separate EDI directories for these JCLs or edit the JCL name in the "Send and Receive EDI Documents" screen.

JCL FOR RETRIEVING DELIVERED FILES JCL name: LIST 1 !NI CTX 2 !UI UUUUUUUU 3 !PW PPPPPPPP 4 !NP NNNNNNNN 5 !CT RETRIEVE


80

EDI COMMUNICATIONS

Note: In this JCL listing, "RETRIEVE" is a suggested JCL name. "UUUUUUUU" represents your user ID; "PPPPPPPP" represents your password; and "NNNNNNNN" represents your new password (to be included only when changing your password). The "RETRIEVE" command allows you to recover information that has already been delivered; the command must be entered as shown. When entering this JCL, you should substitute this information with the appropriate information provided to you by CTX.

This JCL allows you to log in to the CTX system and retrieve information that has already been delivered. When you run this JCL, you are prompted to identify the information you want to retrieve.

Enter the file date and OSN at the prompts; the file will be retrieved and you will be prompted for another file date and OSN. When you are finished, press [Enter] and the following message displays.

JCL FOR GETTING A LIST OF INBOUND CTX FILES JCL name: LIST 1 !NI CTX 2 !UI UUUUUUUU 3 !PW PPPPPPPP 4 !NP NNNNNNNN 5 !CT LIST

Note: In this JCL listing, "LIST" is a suggested JCL name. "UUUUUUUU" represents your user ID; "PPPPPPPP" represents your password; and "NNNNNNNN" represents your new password (to be included only when changing your password). The "LIST" command allows you to view a list of inbound CTX files; the command must be entered as shown. When entering this JCL, you should substitute this information with the appropriate information provided to you by CTX.

This JCL script allows you to view a list of inbound CTX files. The list shows each file SOURCE, DESTINATION, APPLICATION ID, REFERENCE NUMBER, STATUS, DATE, TIME, ISN, and OSN. A sample list follows.

If no files exist, the following message displays:


81

EDI COMMUNICATIONS

JCL FOR GETTING A LIST OF OUTBOUND CTX FILES JCL name: LISTOUT 1 !NI CTX 2 !UI UUUUUUUU 3 !PW PPPPPPPP 4 !NP NNNNNNNN 5 !CT LISTOUT

Note: In this JCL listing, "LISTOUT" is a suggested JCL name. "UUUUUUUU" represents your user ID; "PPPPPPPP" represents your password; and "NNNNNNNN" represents your new password (to be included only when changing your password). The "LISTOUT" command allows you to view a list of outbound CTX files; the command must be entered as shown. When entering this JCL, you should substitute this information with the appropriate information provided to you by CTX.

This JCL allows you to view a list of outbound CTX files. The list shows each file SOURCE, DESTINATION, APPLICATION ID, REFERENCE NUMBER, STATUS, DATE, TIME, ISN, and OSN. The report is very similar to the one displayed in the previous section.

JCL FOR TAKING CTX JOB COMMANDS FROM AN AIX FILE

Important! After you run the AIX JCL, you must run a hidden option to process the files. Contact Prophet 21 for more information and instructions.

JCL name: AIX 1 !NI CTX 2 !OS AIX

Note: In this JCL listing, "AIX" is a suggested JCL name.

This JCL allows you to take CTX commands from an AIX file and run them on the CTX system. When you run this JCL script, you are prompted for an AIX filename.

Enter an AIX filename at the prompt. The following message displays:

WRITING YOUR OWN CTX JOB

The basic CTX job scripts described in the section titled "JCL for Sending Data to and Receiving Data from CTX for AIX Users" were written by programmers at Prophet 21 to allow for easy access to the CTX system. The JCLs provided allow you to send data to and receive data from CTX, to obtain a list of CTX files, and to take CTX job


82

EDI COMMUNICATIONS

commands from an AIX file. These JCLs satisfy the needs of most users. If the provided JCLs do not satisfy your needs, you can write your own custom CTX job.

Most users do not need to write their own jobs. Please contact the EDI Support Department for help when setting up these custom jobs.

CLEO COMMANDS

The CTX job is written using CLEO commands. The basic script should follow this pattern:

1. Dial the remote system. 2. List the commands to enter on the remote system. 3. Specify a modem configuration file. 4. Specify a file to receive the information. 5. Disconnect from the remote system. 6. Quit.

Use the following CLEO commands to create the script:

CLEO command: To:

AU <phone number> dial

KE <CTX command>-x key a command on the remote system (See the section labelled "CTX Commands.")

CO <configuration filename> specify a modem configuration file (See section labelled "Configuration File.")

RE <filename> specify a file to receive information

VO disconnect

QU 0 quit

CONFIGURATION FILE

The following example shows the format for a configuration file:

80 record size

4 repeat limit

4 retransmission limit

10 wait limit (a wait limit of 255 provides 3 minutes or more of holding the line)

100 delay limit

0 line type

1 terminal type


83

EDI COMMUNICATIONS

15 bid limit

0 idle time in 30 second intervals

15 receive limit

1 space compression

1 transmission blocking factor

0 protocol type terminal ID

0 RTS/CTS delay

1 modulation type

0 equalizer

0 new line suppression

0 dialing method

CTX COMMANDS

The CTX commands are used with the CLEO "KE" command and are always prefixed by "/CTX/". For example:

KE /CTX/ LOGON (PROPHET, PROPHET) -x

Use the following CTX commands in conjunction with the CLEO "KE" command:

CTX Command: To:

LOGON (user ID, password/new password) login

ENTER (MAIL) enter MAIL subsystem

LIST (parameters)

INBOUND or INBOUND = station or INBOUND = site or INBOUND SRC = stationname OUTBOUND or OUTBOUND = station or OUTBOUND = site or OUTBOUND DEST = stationname TYPE = type [dlv, undlv, all] APPL = application ID PRI = priority DAYS = number of days HOURS = number of hours MESSAGE RANGE = date, time - date, time or osn - osn

display a list


84

EDI COMMUNICATIONS

OBTAIN or OBTAIN (parameters)

INBOUND or INBOUND = station or INBOUND = site LRECL = number APPL = application ID CLASS = message class (8 characters) PRI = priority DAYS = number of days HOURS = number of hours MESSAGE RANGE = date, time - date, time or osn - osn

retrieve and download a file

DELIVER or DELIVER (parameters)

When using DELIVER (parameters), the following parameters must be specified:

SRC = source DEST = destination APPL = application ID REF = number

The following parameters are optional:

LRECL = number) BLKSIZE = blksize

deliver a file

RETRIEVE or RETRIEVE (parameters)

INBOUND = station or INBOUND = site APPL = application ID CLASS = message class (8 characters) DAYS = number of days HOURS = number of hours DATE RANGE = date, time - date, time or osn - osn

retrieve information

EXIT (MAIL subsystem) exit MAIL subsystem

LOGOFF log off


85

EDI COMMUNICATIONS

SAMPLE CTX JOB

3-M

JCL FOR SENDING DATA TO 3M JCL name: 3M-S 1 <^M 2 >Name:3M SEND 3 <MMM,X24\TARTAN^M 4 >USERNAME > 5 <UUUUUUUU -eEDI^M (*See following note.) 6 >PASSWORD > 7 <PPPP^M 8 >Edi > 9 <PUT pf-out^M 10 {EDDONX 11 <.END^M 12 >(y/n) > 13 <Y^M 14 >Edi > 15 <BYE^M 16 >Name:

JCL FOR RECEIVING DATA FROM 3M JCL name: 3M-R 1 <^M 2 >Name:3M RECEIVE 3 <MMM,X24\TARTAN^M 4 >USERNAME > 5 <UUUUUUUU -eEDI^M (*See following note.) 6 >PASSWORD > 7 <PPPP^M 8 >Edi > 9 <GET pf-test^M 10 }EDDONX 11 >(y/n) > 12 <Y^M 13 >Edi >


86

EDI COMMUNICATIONS

14 <BYE^M 15 >Name:

Note: In these JCL listings, the JCL names are suggested. "UUUUUUUU" represents your 3M user ID, and "PPPP" represents your 3M password. When entering these JCL scripts, you should substitute this information with the appropriate information provided to you by 3M.

UNITED STATIONERS

JCL FOR SENDING DATA TO UNITED STATIONERS JCL name: UNITED SND 1 >^MUS00^M 2 <BC01_AAAAAA_PPPPPPPP (*See following note.) 3 <CESF_LOGOFFÊ

BC01 tells United Stationers that this is a “send document” process.

JCL FOR RECEIVING DATA FROM UNITED STATIONERS JCL name: UNITED RCV 1 >^MUS00^M 2 <BC02_AAAAAA_PPPPPPPP (*See following note.) 3 -_TTTTT 4 - 5 -__Ê 6 >ST 7 >^M 8 }EDDONX

BC02 tells United Stationers that this is a “receive document” process.

Note: In these JCL listings, the JCL names are suggested. "AAAAAA" represents your United Stationers account number, and "PPPPPPPP" represents your United Stationers password. When entering these JCL scripts, you should substitute the account number and password provided to you by United Stationers.

LYNN EDWARDS

JCL FOR SENDING DATA TO LYNN EDWARDS JCL name: LE SND 1 <-WAIT2- 2 <H 3 <-WAIT1- 4 <H 5 >-TIMEOUT40- 6 >U#= 7 <-WAIT1- 8 <XXXXXXXX,XXXXXX^M (*See following note.) 9 >TERM= 10 <^C


87

EDI COMMUNICATIONS

11 >LOGICAL ID 12 <LLLL^C 13 >**HEL 14 <-WAIT3- 15 >-TIMEOUT10- 16 {EDDONX 17 <$*$DIS^C 18 >$$_0900_BYE

JCL FOR RECEIVING DATA FROM LYNN EDWARDS JCL name: LE RCV 1 <-WAIT2- 2 <H 3 <-WAIT1- 4 <H 5 >-TIMEOUT40- 6 >U#= 7 <-WAIT1- 8 <XXXXXXXX,XXXXXX^M (*See following note.) 9 >TERM= 10 <^C 11 >LOGICAL ID 12 <LLLL^C 13 >**HEL 14 <-WAIT2- 15 >-TIMEOUT30- 16 }EDDONX

Note: In these JCL listings, the JCL names are suggested. "XXXXXXXX,XXXXXX" represents your Marknet User password, and "LLLL" represents your logical ID. When entering these JCL scripts, you should substitute the password and logical ID provided to you by Marknet/Lynn Edwards. Once a connection has been made during receiving, you are prompted for the document number for which you wish to receive an acknowledgment.

STATIONERS

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM STATIONERS JCL name: STAT BOTH 1 >-TIMEOUT5- 2 <A^M 3 >log_in 4 <TTTTTTTT^M (*See following note.) 5 >IS_ONLINE 6 <^M 7 >: 8 <HELLO_XXXXXX 9 -,EZ.SFD^M 10 >-TIMEOUT25- 11 >? 12 >-TIMEOUT5- 13 {EDDONX


88

EDI COMMUNICATIONS

14 >-TIMEOUT10- 15 }EDDONX

Note: In this JCL listing, "STAT BOTH" is a suggested JCL name. "TTTTTTTT" represents your TYMENET ID Code, and "XXXXXX" represents your Stationers logon code. When entering this JCL script, you should substitute the ID code and logon code provided to you by Tymenet/Stationers. Only one document can be sent/received per communication session.

SP RICHARDS

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM SP RICHARDS JCL name: RICH BOTH 1 <-WAIT10- 2 <EZORDER^J 3 >@C 4 <XXXXXXXXX^J (*See following note.) 5 >@U 6 <XXXX^J 7 >@V 8 <N^J 9 >@S 10 >-TIMEOUT10- 11 {EDDONX 12 >-TIMEOUT20- 13 >@S 14 >-TIMEOUT10- 15 }EDDONX

Note: In this JCL listing, "RICH BOTH" is a suggested JCL name. "XXXXXXXXX" represents your SP Richards customer number, and "XXXX" represents your SP Richards user ID code. When entering this JCL script, you should substitute the customer number and user ID provided to you by SP Richards. Only one document can be sent/received per communication session.

O'HENRY

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM O'HENRY JCL name: OHENRY 1 <-WAIT10- 2 <^M*EXEC_OLBENTCL_^MI (User ID begins here… 3 -IIII_^MONLINE_^MPPPP and is continued here. 4 -^M^D^M Password begins on the 5 >? third line too.) 6 {EDDONX 7 >-TIMEOUT25- 8 }EDDONX

Note: In this JCL listing, "OHENRY" is a suggested JCL name. "IIII" represents your O'Henry user ID, and "PPPP" represents your O'Henry password. When entering this JCL, you should substitute the user ID and password provided to you by O'Henry. Only one document can be sent/received per communication session.


89

EDI COMMUNICATIONS

LYNN EDWARDS WRAP AND SHIP

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM LYNN EDWARDS WRAP AND SHIP

JCL name: LEWS BOTH 1 <-WAIT2- 2 <H 3 <-WAIT1- 4 <H 5 >-TIMEOUT40- 6 >U#= 7 <-WAIT1- 8 <XXXXXXXX,XXXXXX^M (*See following note.) 9 >TERM= 10 >-TIMEOUT3- 11 >^M^J 12 <-WAIT1- 13 <^C 14 >-TIMEOUT120- 15 >LOGICAL_ID 16 >-TIMEOUT40- 17 >^C 18 <-WAIT1- 19 <LLLL^C (*See following note.) 20 >-TIMEOUT60- 21 >**HEL 22 >-TIMEOUT10- 23 >^M^J^C 24 <-WAIT2- 25 <CSLE0AAAAAAAAA^C (*See following note.) 26 >-TIMEOUT30- 27 >@S^M^J^C 28 {EDDONX 29 <-WAIT30- 30 >-TIMEOUT20- 31 }EDDONX

Note: In this JCL listing, "LEWS BOTH" is a suggested JCL name. "XXXXXXXX,XXXXXX" represents your Marknet user password; "LLLL" represents your logical ID, and "AAAAAAAAA" represents your Lynn Edwards account number. When entering this JCL script, you should substitute the password, logical ID, and account number provided to you by Marknet/Lynn Edwards. Only one document can be sent/received per communication session.

BOISE CASCADE/ASSOCIATED STATIONERS

JCL FOR SENDING DATA TO AND RECEIVING DATA FROM BOISE CASCADE/ASSOCIATED STATIONERS

JCL name: BOIS BOTH 1 <-WAIT2- 2 <H


90

EDI COMMUNICATIONS

3 <-WAIT1- 4 <H 5 >-TIMEOUT20- 6 >U#= 7 <NNNNNNNN,PPPPPP^M 8 >-TIMEOUT5- 9 >==> 10 <CICS39^M 11 >-TIMEOUT20- 12 >^M^J 13 <-WAIT3- 14 <XXXXXX/YYYYYYYY^M 15 <-WAIT3- 16 <U^M 17 >UPLOAD_READY 18 >^M^J 19 {EDDONX 20 <-WAIT1- 21 <EOT^M 22 >ACCEPTED 23 <-WAIT90- 24 <D^M 25 >-TIMEOUT10- 26 }EDDONX

Note: In this JCL listing, "BOIS BOTH" is a suggested JCL name. "NNNNNNNN" represents your GE Network user number; "PPPPPP" represents your GE Network password; "XXXXXX" represents your Boise Cascade/Associated Stationers customer number, and "YYYYYYYY" represents your Boise Cascade/Associated Stationers password. When entering this JCL script, you should substitute the GE user number, GE password, Boise Cascade/Associated Stationers customer number, and Boise Cascade/Associated Stationers password provided to you by Boise Cascade/Associated Stationers.

STEELCO

JCL FOR RECEIVING DATA FROM STEELCO JCL name: STJL 1 !NI STC 2 !UI MEYRXOT 3 !BI MEYRNFZS

Note: In this JCL listing, "STEELCO" is a suggested JCL name.

FILE TRANSFER PROTOCOLS File transfer protocols are required when dialing in to certain networks and proprietary trading partners' systems. Using a file transfer protocol guarantees errorless file transfer by ensuring that information is received exactly as it was sent. Faulty telephone lines or other hardware problems can result in the scrambling of the information itself; what you send is what they get. Prophet 21 supports the use of two file transfer protocols, XMODEM and Kermit.


91

EDI COMMUNICATIONS

USING XMODEM XMODEM transfers files using a Microcom modem initialized for "direct mode" (further information on initializing your modem can be found in the "Modem Initialization Table" section). Currently, the AT&T Easy Link Value-Added Network (VAN) is the only Prophet 21 supported network that requires the use of XMODEM for file transfers. The AT&T JCL scripts must contain the following XMODEM commands:

>-XMODEM ON- Enables XMODEM file transfer mode.

>-XMODEM OFF- Exits XMODEM file download (receive) mode.

>-XMODEM OFF- Sends an EOT (end of transfer) to exit XMODEM upload (send) mode.

The JCL match command (">") is ignored while XMODEM is enabled. The send message command ("<") will include the message itself as part of the file being sent. Other JCL commands (receive, send, etc) function as normal while using XMODEM.

The following error message displays when an XMODEM file transfer is attempted when the /usr/local/bin/xmodem1 AIX file is missing.

USING KERMIT Although no Prophet 21 supported networks require the use of Kermit for file transfers, Kermit may be needed to send data to or receive data from another network, or one of your proprietary trading partners. If this is the case, the appropriate JCL scripts must contain the following Kermit JCL commands:

>-KERMIT ON- Enables normal Kermit file transfer mode.

>-FN=filename Identifies the name of the file being transferred. It should include any path necessary to reach the file.

>-KERMIT OFF- Exits Kermit file transfer.

Kermit allows you receive data two ways. Using the commands above, you connect with the host system and enable Kermit. The host system prompts you for the name of the file you want to receive. You specify the file's name, the file is transferred, and you exit Kermit.

Using the commands below, you connect with the host system, enable Kermit, and indicate the name of the file you want to receive. The host system sends the file, and you exit Kermit.

Which of the two you should use depends on the network or proprietary trading partner with which you are communicating.

>-KERMIT SG- Enables Kermit Sender Get Type Receive file transfer mode.

>-FN=filename Identifies the name of the file being transferred. It should include any path necessary to reach the file


92

EDI COMMUNICATIONS

necessary to reach the file.

>-KERMIT OFF- Exits Kermit file transfer.

The JCL match command (">") is ignored while Kermit is enabled. The send message command ("<") will include the message itself as part of the file being sent. Other JCL commands (receive, send, etc.) function as normal while using Kermit.

93

This chapter covers the initial process of sending and receiving EDI information on a daily basis, the problems that may be encountered, and monthly maintenance procedures. Please review all information carefully before you begin. If you have any questions, contact EDI Support for further assistance.

SETTING UP TRADING PARTNER INFORMATION The first step to successfully running EDI is to enter trading partner information for all the customers and vendors who are your trading partners. The following steps explain how a trading partner is set up in your system:

1. From the main EDI menu, select the Setup option.

2. On the EDI Setup menu, choose the Trading Partner option.

3. From the Trading Partner menu, select the Interchange option. From the Interchange menu, choose Enter.

4. Enter the Trading Partner ID of your trading partner in the TP ID field. This ID should be the same code as your customer or vendor code. Do not enter the vendor number of a vendor.

5. In the Network Name field, enter the name of your network. Do not enter the network name of your trading partner. The network information must already exist in the system. For more information on entering network information, refer to the EDI Setup manual.

6. Press [Esc] on the fields until you reach the Inter ID Qual (interchange ID qualifier) field. Enter the interchange ID qualifier of your trading partner. In the next field, Inter ID, enter the Interchange ID of your trading partner. If you do not have these values, contact your trading partner who can supply this information.

7. Press [Esc] on the following fields until you reach the App Code (application code) field. Enter the same number as is placed in Inter ID (interchange ID) field.

8. Press [Esc] until you reach the Field prompt at the bottom of the screen.

9. Review the fields under the Miscellaneous Information section of the screen, and change any of these values that apply to your company. For more information on any of the Trading Partner Interchange Information fields, refer to the EDI Setup manual.

INSTALLING OVERLAYS ON YOUR SYSTEM After trading partners are established in the system, overlay files can be installed. If you need a specific overlay for one of your trading partners, complete an Overlay Request Form and fax it to the Inside Sales Department. Once the order is processed and the overlays are available, they will be downloaded to your system by the EDI Support Department. Your system does not need to be stopped to accept the downloading of overlays.

DMINISTRATOR

13 EDI ADMINISTRATOR

94

EDI COMMUNICATIONS

To accept overlays, have the following information ready:

1. The Trading Partner Interchange Information record must exist in the system for the trading partner whose overlay is being downloaded.

2. The diagnostic modem must be set so that EDI Support can dial into your system.

3. AIX root and Prophet 21 system passwords must be given to EDI Support so that they can access your system.

If the overlay requires any customization, the EDI Support Department can either change it at the time of dialing-in, or will notify you of what information you need before you place a call for customization.

HOW TO RECEIVE DATA FROM YOUR EDI NETWORK It is the strong recommendation of the EDI Support Department for you not to use a FacetTerm terminal to do the sending and receiving of EDI. If you do use a FacetTerm terminal, chances of locking up both your terminal and the EDI modem are greatly increased. If you must use a FacetTerm terminal, do not leave the window you are in until the transfer is complete. The following steps explain how to receive data from your EDI network:

1. From the main EDI menu, select the Communications option.

2. On the EDI Communication menu, choose the Send/Receive option.

3. Select and enter the correct EDI network directory for receiving documents.

4. Press [Enter] after the system displays all the information about the selected directory.

5. The system automatically dials and receives all data from your mailbox.

6. When the process is complete, the system goes into Interactive Mode. Depending on the setting of the Pause for (Dis)connect field in the EDI Directory record of EDI Com, you may or may not see a prompt for continuing. When Interactive Mode is initiated, press [Esc] to disconnect the modem. The system returns to the Directory prompt mentioned in the previous step. Press [Enter] to return to the EDI Communication menu.

Note: If Harbinger is your network and an “error 040 on IO com file” appears, your mailbox is empty. This is not an error on the Prophet 21 system.

When these steps have been completed, the system has received data, if any had been in your mailbox. The next section describes how to process this data.

HOW TO PROCESS RECEIVED DATA IN EDI The following steps outline how to process data that was received from your EDI network:

1. From the main EDI menu, select the Document option.

2. On the Document menu, choose the Process option.

3. All the documents that need to be processed are displayed. Enter the Trading Partner ID for the trading partner whose documents you wish to process. A list of documents that are linked to that specific trading partner are shown.

4. Press [Enter] and you are prompted to select a printer for the output. When a printer is selected, the system starts processing the documents. A screen similar to the following appears:


95

EDI COMMUNICATIONS

5. After processing is complete, the document prints to the selected printer.

If you encounter an error in processing, contact the EDI Support Department for further assistance.

HOW TO SEND DOCUMENTS ON THE EDI NETWORK The following 3-step process describes how to send documents. The steps consist of building, preparing (enveloping), and sending the document:

BUILDING EDI DOCUMENTS The Building process is the translation of Prophet 21 transactions (orders, purchase orders, invoices, etc.) into ASC X12 transaction sets.


2. On the EDI Document menu, choose the Build option.

3. Enter the transaction set number of the document that you wish to build. For example, entering 850 would tell the system to build purchase orders. A browse on the Enter Transaction Set Number field is available.

4. Once the transaction set is chosen, enter the Trading Partner ID for the trading partner for whom you want to build documents. Performing a browse on the Trading Partner ID field displays the trading partners who have this type of document to build.

5. After the trading partner is selected, a screen similar to the following displays all the available documents that can be built:


96

EDI COMMUNICATIONS

6. Toggle the Incl value to determine whether or not a specific document should be included in the build process. Enter the sequence number of the item at the Seq prompt to change the Include value from YES to NO or from NO to YES.

7. Once all documents that you wish to build have been set to an Incl value of YES, press [S] at the Seq prompt to start the building process.

When these steps have been completed, the system has built the documents into transaction sets. The next section describes the second step in the sending process, which is how to prepare (envelope) the transaction sets for sending.

PREPARING EDI DOCUMENTS The Preparing, or enveloping process is used to envelope built EDI transaction sets before they can be sent to your trading partners. When a built document is enveloped, a new document is created that includes all of the transaction sets that were marked with YES to Include, along with the appropriate interchange information for sending to the specific trading partner.


2. From the EDI Document menu, choose the Prepare option.

3. Enter a trading partner ID at the Trading Partner ID field. Performing a browse on this field displays the trading partners who have built documents ready for enveloping.

4. Select which documents should be prepared (enveloped) by toggling the line-item’s Incl value. You are performing the same action as described in Step 6 of the prior “Building EDI Documents” section.

5. Once all documents to be enveloped are chosen, press [S] at the Seq# prompt to start the prepare process.

When these steps have been completed, the system has enveloped the documents for sending to your trading partners. The next section describes the third and final step in the sending process, which is how to send the enveloped documents.

SENDING EDI DOCUMENTS TO YOUR EDI NETWORK The Send option sends all prepared, or enveloped documents to your EDI network.

1. From the main EDI menu, select the Communications option.

2. On the EDI Communication menu, choose the Send/Receive option.

3. Select and enter the correct EDI directory for sending documents. Enveloped documents that can be sent are displayed. Press [Enter] at the Field prompt.

4. The system automatically dials and sends all of the enveloped documents to your mailbox.

5. When the sending process is complete, the system goes into Interactive Mode. Depending on the setting of the Pause for (Dis)connect field in the EDI Directory record of EDI Com, you may or may not see a prompt for continuing. When Interactive Mode is initiated, press [Esc] to disconnect the modem. When the modem is disconnected, the system returns to the Seq/Code prompt. Press [Enter] to exit from the Send/Receive option.

When these steps have been completed, the system has sent all enveloped documents to your network.


97

EDI COMMUNICATIONS

HOW TO SEND FUNCTIONAL ACKNOWLEDGEMENTS (997S)

Functional acknowledgements (the SEND type) are automatically built by the system when the actual processing of documents is initiated. You need to only prepare and send the documents to your network. For more information on preparing and sending documents, refer to the previous sections in this chapter.

HOW TO FREE A LOCKED MODEM WHILE SENDING OR RECEIVING

If the modem port becomes locked while sending or receiving data, execute the following steps to free the port:

1. Write down the modem port (tty) number and the port (tty) number of the terminal that was performing the sending or receiving. If you cannot determine the terminal port number, run the job ACTIVE to determine the port that is in the EDI-COM job.

2. Once the two port numbers are determined, go to the AIX prompt. At the root prompt (#), type: ps -t## [Enter] Note: The ## symbols in the prior command indicate the tty number that should be inserted.

3. A screen similar to the following is displayed:

You need the PID number to help unlock the terminal port.

4. To kill the locked process, type the following command at the AIX prompt: # kill -9 <PID number> [Enter] To kill the port in the previous screen, the command should be entered as follows:

5. Run this command to kill the process on both the EDI modem port and the terminal. You can

check to ensure that the processes have been freed by running the previous ps command (# ps –t##). If the TIME value from the command’s response is 0:00, then the process is cleared and the modem can be used.

MONTH-END EDI PROCEDURES The following procedure should be followed on a monthly basis to ensure the smooth operation of the EDI module. There are two things that should be done every month: purging raw documents, and purging event journals.


98

EDI COMMUNICATIONS

Before running these procedures, Q-Mode and H-Mode must be enabled.

1. On the main EDI menu, select the Document option.

2. From the EDI Document menu, choose the Print Journals option. On the Print Journals menu, select the All option to print all EDI event journals.

3. Choose a printer. Once printing is complete, type CL to clear all journals of information.

4. Any raw data still in the system should be purged at this point. On the EDI Document menu, choose the Purge Raw option. Press [Esc] through all fields on the parameter screen to reach the Field prompt.

5. The information that is purged is controlled by these parameters. Prophet 21 recommends that you keep at least one month’s worth of raw data on your system. You can clear up to one month back by changing the End Date field to a date of one month ago. The system prompts you to be sure of your actions before actually deleting any information. Answering Y purges all raw data meeting the parameter requirements.

6. Once you have purged your raw data, repeat prior Steps 1 through 3 to clear the journals once again.

99

ASCII CONTROL CHARACTERS The following table of ASCII Control Characters is provided to help you enter control characters in JCL instructions.

Character ASCII Abbreviation Function

^@ 00 NUL Null Â 01 SOH Start Of Heading ^B 02 STX Start Of Text ^C 03 ETX End Of Text ^D 04 EOT End Of Transmission Ê 05 ENQ Enquiry - request transmission ^F 06 ACK Positive Acknowledge ^G 07 BEL Audible Bell ^H 08 BS Back Space Î 09 HT Horizontal Tab ^J 10 LF Line Feed ^K 11 VT Vertical Tab ^L 12 FF Form Feed ^M 13 CR Carriage Return ^N 14 SO Shift Out Ô 15 SI Shift In ^P 16 DLE Data Line Escape ^Q 17 DC1 Device Control 1 ^R 18 DC2 Device Control 2 ^S 19 DC3 Device Control 3 ^T 20 DC4 Device Control 4 Û 21 NAK Negative Acknowledge ^V 22 SYN Synchronous Idle ^W 23 ETB End Of Transmission Block ^X 24 CAN Cancel ^Y 25 EM End Of Message

PPENDIX

14 APPENDIX

100

EDI COMMUNICATIONS

^Z 26 SUB Substitute ^[ 27 ESC Escape ^\ 28 FS Field Separator ^] 29 GS Group Separator ^^ 30 RS Record Separator ^- 31 US Unit Separator

101

“FAQs” is an abbreviation for “frequently asked questions.” This section contains the answers to the questions most often asked about EDI Communications.

What does “Name Invalid!” mean when I try to assign a modem?

The modem initialization table has not been created. To create this table, run the hidden option @$ from the main menu of EDI Communications. Once completed, re-enter the modem assignment.

When dialing out, I receive the message “modems failed to connect.” What does this mean?

The phone lines failed to make a stable connection. The modem should be reset and then try to dial out again. If the message appears again, contact your phone company to run a test on the line.

What action should I take when the following message displays when receiving?

This is not an error as the message suggests. It is that your EDI mailbox at the network is empty. Continue to receive your EDI transmissions on your normal schedule.

What does “One of the assigned modems in the modem initialization table is invalid” mean?

The modem port has been disabled. You would need to use the AIX command penable to enable the port. You may also need to kill the process currently running on the port.

What is the purpose of the Manual Dial option?

This option allows you to dial out through your EDI modem. You have the option to connect to another remote system. No JCL script is used for dialing out.

S

15 FAQS

102

PROPHET 21 ACCLAIM®

How many modems can I setup to be used for EDI?

You can use up to 10 modems for EDI. The EDI Communications module searches for available modems in the order that they are entered in the Assign Modem Ports directory. If the first modem is not available (busy), the module checks the second one, and so on down the list.

Where do I change the phone number of my VAN?

The phone number can be changed by editing the value of the Modem Phone # field of the EDI Directory record. To accomplish this, select the EDI Directory option on the EDI Communications main menu and scan for the specific network on the EDI Code field. After you select the record, return to the Modem Phone # field to change the phone number.

What does the message “phone lines accidentally disconnected” mean?

Your modem on your system did not make a reliable connection on the network end. Try to resend or rereceive. If this message appears frequently, there could be trouble on your phone line.

How can I determine on which port my modem is assigned?

From the EDI Communications main menu, select Assign modem ports. The Port # column displays the port number of the modem.

After sending or receiving transmissions, the Interactive Mode screen appears. The terminal appears to be locked. What should I do?

Press [Esc] at the Enter Response prompt. You are returned to the main menu of EDI Communications and are disconnected from your modem.

Date post:	14-May-2018
Category:	Documents
Upload:	dangquynh
View:	216 times
Download:	3 times