This is a printable page that lists the questions and answers for Expedite Base/400.

Return to the FAQs question page 1.

How do I install Expedite Base/400?

Instructions for installing the product are contained in the Expedite Base/400 Programming Guide and the Expedite Base/400 installation document.
[Return to Questions]

Through the Information Exchange Common Front End, Expedite Base/400 can communicate using SNA LU 6.2 or TCP/IP protocols.

SNA LU 6.2 communications
Before you can use Expedite Base/400, you must order the logical unit (LU) name that Expedite Base/400 uses when communicating with the Information Exchange Common Front End. When you order your LU name, specify that you will use it to go in session with the Information Exchange Common Front End and to use Expedite Base/400. In the U.S., the Information Exchange Common Front End is named ibm0rely.

To enable SNA LU 6.2 communications in Expedite Base/400, you must define the LU name and identify the Information Exchange Common Front End as an active cross-domain resource (CDRSC).

TCP/IP communications
TCP/IP network connections take into account the size of your network, other applications you will be accessing through the network, and your hardware configuration. You can select standard TCP/IP communication through the AT&T network or Secure Sockets Layer (SSL) TCP/IP communication through the Internet.

Network personnel will work with your networking personnel to allow communications between Expedite Base/400 and the Information Exchange Common Front End. [Return to Questions]

How do I get documentation for Expedite Base/400?

Customers can download all current Expedite and Information Exchange publications from the EDI Services publications page. For documents specific to Expedite Base/400, go to the Expedite Base/400 publications page

[Return to Questions]

What are the costs for Expedite Base/400?

For billing or pricing questions, ordering, or sales and marketing information, Contact Us.
[Return to Questions]

What recovery level should I use?

During a session with Information Exchange, Expedite Base/400 can use a series of checkpoints (also known as commits) to make sure that the systems exchanging information are synchronized. The frequency and timing of the checkpoints depends on the recovery level you select for the session.

In addition, Information Exchange does not deliver a file until the file is entirely committed. If a session ends before the entire file has been sent, Information Exchange will not deliver the partial file. Instead, Information Exchange holds the session until you resume it and either cancel the partially sent file, or continue transmitting the remaining data.

To select the right recovery level, you need to understand how Information Exchange uses the following checkpoints.

• session-level recovery
• checkpoint-level recovery
• file-level recovery

• user-initiated recovery

Note: Do not use the same account and user ID on multiple systems. If you start another session using the same account and user ID, Expedite Base/400 will end the first session to proceed with the second session. The results of the first session will depend on the checkpoints completed successfully at the time that Expedite Base/400 ended the session. Data from the first session may be retransmitted when the session is reactivated, causing errors.

Session-level recovery
Session-level recovery is the default recovery level in Expedite Base/400. Session-level recovery does not require additional work files to run as do the other methods of data recovery. The checkpoint for session-level recovery occurs when Expedite Base/400 requests the end of the session (all data has been sent and received).

Session-level recovery is preferable if you want all  the files in a session to be delivered in one transmission or none of the files will be delivered. In the case of an error, all data in the session must be retransmitted. Session-level recovery is also well-suited for  transmitting small amounts of data. Recovering a session-level session is easy, since you simply run Expedite Base/400 again.

If you transfer a large amount of data during a session-level recovery session, you may  need to increase the amount of time that Expedite Base/400 will wait for communication from Information Exchange before terminating the connection. Information Exchange will not respond to the termination request until all sent messages have been moved to the destination mailbox. Use the timeout parameter on the TRANSMIT command to specify enough time to receive transmissions and wait for Information Exchange to acknowledge all transmissions.

For more information on session-level recovery, see the Expedite Base/400 Programming Guide. [Return to Questions]

Checkpoint-level recovery
With this type of recovery, Expedite Base/400 takes checkpoints during the session after a set number of characters has been transmitted to Information Exchange. The number of  characters between checkpoints is determined by the commitdata setting on the TRANSMIT profile command. Before using checkpoint-level recovery, you must allocate the work files that Expedite Base/400 uses to track committed files.

Checkpoint-level recovery is well suited to sessions with large or numerous files because only data still awaiting transfer after the last successful commit must be retransmitted if the session fails. Also, ending a session takes less time because transferred data is committed at each checkpoint during the session.

Running out of space in a work file can cause a session to become unrecoverable. Expedite Base/400 uses a pointer to track its position in the work file being transmitted. Reallocating a work file to a larger space and copying the contents can invalidate this pointer, making the session unrecoverable. Unrecoverable sessions must be retransmitted and manual intervention may be required to ensure that data is not duplicated or lost.

For more information on checkpoint-level recovery, see the Expedite Base/400 Programming Guide. [Return to Questions]

File-level recovery
File-level recovery is best used when a file must be committed in its entirety rather than in segments. For example, when sending EDI data, with multiple envelopes in a single file, the envelopes are sent as individual files. Using file-level  recovery, none of the envelopes will be committed until all envelopes in the session have been sent. If the session is interrupted prior to all envelopes being sent, all envelopes must be retransmitted. This will ensure that all envelopes will be available to all recipients at the same time.

For more information on file-level recovery, see the Expedite Base/400 Programming Guide. [Return to Questions]

User-initiated recovery
With user-initiated recovery, you can control exactly when Expedite Base/400 performs a commit while transmitting data. In the data set referenced by the INMSG DD card, you can place a COMMIT command following the SEND command where you want a commit to occur. Multiple SEND/COMMIT pairs can be entered in a data set.

For more information on user-initiated recovery, see the Expedite Base/400 Programming Guide. [Return to Questions]

To send files of any format to your trading partners' mailboxes, use the SEND command. To send multiple EDI-formatted files to one or more trading partners from a single file, use the SENDEDI command. To send data from the message command file (INMSG) to Information Exchange, use the SENDSTREAM command. The SENDSTREAM command is valid only when you are using session-level recovery.

The use of limiting parameters, such as class or start date, can customize the actions performed by the SEND commands. If your trading partners send you payroll information, for example, they can elect to send only the files included in the payroll class by specifying that class in the SEND command.

To send EDI-formatted files, be sure to set up the EDI receiver´s account and user ID before you try to send files using the SENDEDI command.

For more information on sending and receiving data, see the Expedite Base/400 Programming Guide.
[Return to Questions]

The RECEIVE command retrieves all files or specific files, including free-format messages, from the Information Exchange mailbox. To receive multiple EDI envelopes containing different types of data, use the RECEIVEEDI command. Using the RECEIVEEDI command with the edionly parameter set to Y will receive only EDI-formatted files; otherwise, the RECEIVEEDI will receive all file types while ensuring proper handling of EDI formats.

The use of limiting parameters, such as class or start date, can customize the actions performed by the RECEIVE commands, such as limiting the messages received to only EDI files.

For more information on sending and receiving data, see the Expedite Base/400 Programming  Guide.
[Return to Questions]

Both the sender and receiver must have the TDAccess (formerly Comm-Press) product installed on their systems. The sender and receiver may have different systems, but can still communicate using the Expedite and TDAccess products. For more information about TDAccess products, see the bTrade, Inc. Web site at www.btrade.com.

Once the required products are installed, the sender specifies COMPRESS(Y) on the SEND or SENDEDI commands. Expedite will invoke the compression routines to compress the data before sending it. On the receive side, Expedite will automatically call the decompression routines to expand the data.

For more information about using the compression and decompression routines with Expedite, refer to the appendix on "Using data compression" in the Expedite Base/400 Programming  Guide.
[Return to Questions]

If you find no mail, check your RECEIVE command to make sure you have left blank any fields that Expedite and Information Exchange are not required to match. If you have already done this step and still have no entries, you have no mail pending. You have either already received all pending mail or your trading partner was not successful in sending you mail. Ask your trading partner to verify that the send was completed successfully.

If you have mail but are unable to receive it when you run a session, check for error messages.

If you still cannot receive mail, you can use the AUDIT command to generate an audit trail report. Audit reports are not available during the session that is active when the report is requested. Expedite will load the audit report into your mailbox for  the next session.

See Appendix D in the Expedite Base/400 Programming Guide for detailed information.
[Return to Questions]

If there is no record in Information Exchange of your file being transmitted, check Expedite Base/400 for error messages. Expedite  Base/400 uses the file referenced by the OUTMSG file to provide the status of commands executed and sessions transmitted. Check this file for error messages after each Expedite Base/400 session.
[Return to Questions]

To find out why mail was not delivered as expected, you can check your OUTMSG file for Expedite Base/400 errors. If you do not find any there, you can check the Information Exchange audit trail for message status or the Information Exchange mailbox for error messages

Message Status
If the message status code is:

Error Messages
If the error message begins with 04020 and says 'owing to authorization', the cause is a payment problem between the mailboxes. You must use Information Exchange to add the  trading partner to your trading partner list or to edit the default payment options in your user profile.

If the error message begins with 04021 and says 'invalid userid/alias', either the account and  user ID are invalid or the receiver ID is not mapped to an account and user ID. If the trading partner's EDI receiver ID is not being converted to an account and user ID, you must add your trading partner to a local table on your system or to an online alias table in Information Exchange.

If the error message is no longer in your inbox, you can use the AUDIT command to generate  an audit trail report. Audit reports are not available during the session that is active when the report is requested. Expedite will load the audit report into your mailbox for a subsequent session.

See the Expedite Base/400 Programming Guide for detailed information.
[Return to Questions]

Charges for sending and receiving messages are applied using parameters set in Information Exchange. If both trading partners are on the same Information Exchange system, the send and receive charges may both be paid by the sender, both paid by the receiver, or split between the sender and the receiver. Information Exchange uses the payment level and user profile information to determine who pays charges. You can indicate your preferred payment setup when sending messages through Expedite Base/400, but the values set in Information Exchange can override your  preferences.

When you send a message to a trading partner connected to a messaging service other than your local Information Exchange system, restrictions on payment options may apply. We recommend that you set up a 50/50 payment split with your trading partners.

If you send a message to an invalid destination or use an invalid payment combination, Information Exchange places an error message in your mailbox stating that your message was not delivered and you will be charged. To avoid incurring unnecessary send-side charges, validate the destination address and payment authorization before sending a message to a new or unfamiliar trading partner.

For more information about message charges, see the Information Exchange Charges Reference.

[Return to Questions]

Error messages generated by Expedite Base/400 are written to the message response (OUTMSG) and profile response (OUTPRO) files.

Error  messages generated by Information Exchange are sent to your mailbox with a sender´s account ID of *SYSTEM* and user ID of *ERRMSG*. You must receive these messages to read the contents.
[Return to Questions]

EDI alias errors are generated by Information Exchange when a file sent previously was not delivered to your trading partner's mailbox. The send session ran and ended, but when Information Exchange tried to deliver the file, it could not find the intended recipient.

You must use Information Exchange to correctly identify the destination account and user ID or, for EDI, the EDI receiver ID.
[Return to Questions]

An Expedite Base/400 session can end with a sessionend return code for the following reasons:

• After sending a request to end a session, Expedite Base/400 did not receive a response from Information Exchange within the timeout limit.
• Expedite Base/400 received an unexpected response from Information Exchange.

To resolve the error:

• Be sure to set the timeout limit to allow for communication backlogs as well as for transmissions with a large number of files. We recommend that the WAITFILE parameter be set to at least 120 seconds. The command to change the WAITFILE parameter in the AS/400 ICF communication file is:
            CHGICFF FILE(QICDMF) WAITFILE(120).

• If you are using session-level recovery for the session, you can switch to a different recovery level to improve processing.

• If there is a communications backlog, your system may need adjustment to more efficiently handle the volume of data.

If the error is still unresolved, Contact Us.
[Return to Questions]

Parser errors can happen when line numbers are inserted in columns 76-80 by the editor used to create the data sets referenced by the profile command (INPRO) and message command (INMSG) files. Expedite Base/400 uses all the columns (1-80) for input and will attempt to process the line numbers as data (commands, parameters, or values).
[Return to Questions]

Check the joblog using the command DSPJOBLOG. If the message "CPF5379 remote location ibm0rely for program device ielu was not found" is displayed, the cause could be any of the following:

• The remote location was not defined.
• Not enough time was allowed to find the remote location.
• The combination of remote location aa, device bb, location cc, and remote network ID dd was not correct.
• There might be duplicate INPRO or INMSG files.

Try the following:

• If the remote location was not defined, add the remote location to the configuration lists APPNRMT and APPNLCL, using the WRKCFGL command. If the entry already exists, try deleting and redefining the entry in both the APPNRMT and APPNLCL lists.
• Increase the time allowed for finding the remote location by issuing the command CHGICFF using file name QICDMF. Then press Enter. Press F10 for additional parameters, and then change the Maximum file wait time from 30 to 120, and press Enter.
• Enter DSPNETA on the command line. Verify that APPN Node Type is *NETNODE. If not, use the CHGNETA command to change this value.
• Try varying the settings for the line and controller manually before issuing the call to IEBASE. To do this, use the WRKCFGSTS command to change the *LIN and *CTL parameters.
• Make sure that both Expedite libraries (expblibr and expblibrm) are defined in the customer library list.
• Verify that only one INPRO and one INMSG file exist. Delete any duplicates.
  [Return to Questions]

Expedite Notification Manager is a separate product that can be installed to receive incoming notifications from Information Exchange. You must have the appropriate profile set up in Information Exchange to receive these notifications.
[Return to Questions]