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

Return to the FAQs question page 2.

How do I send files?

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. For example, if your trading partners send you payroll information, 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/MVS 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/MVS Programming  Guide.

[Return to Questions]

Why didn´t I get my mail?

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 C in the Expedite Base/MVS Programming Guide for detailed information.

[Return to Questions]

What if there is no record of my file?

If there is no record in Information Exchange of your file being transmitted, check Expedite Base/MVS for error messages. Expedite Base/MVS uses the data set referenced by the OUTMSG DD card to provide the status of commands executed and sessions transmitted. Check this file after each Expedite Base/MVS session for error messages.

[Return to Questions]

Why didn´t my trading partner get the mail I sent?

To find out why mail was not delivered as expected, you can check your OUTMSG file for Expedite Base/MVS 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/MVS Programming Guide for detailed information.

[Return to Questions]

How are message charges applied?

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/MVS, but the values set in Information Exchange can override your preferences. Expedite Base/MVS uses a default value of 3 (receiver pays all charges), which is recommended as it allows for the greatest flexibility in payment options.

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/MVS 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]

How do I resolve EDI alias errors?

EDI alias errors are generated by either Expedite Base/MVS or Information Exchange when an alias address can not be resolved.

When an EDI alias error (17108-17408 in OUTMSG)) is generated by Expedite Base/MVS, it indicates that you did not provide the instructions needed to resolve the alias to a valid destination. A qualifier table (the QUALTBL DD card) is required to specify how Expedite Base/MVS should map the alias to an Information Exchange account and user ID. The alias and ttable parameters are used to instruct Expedite Base/MVS to reference either the Information Exchange alias tables or destination tables defined in the your JCL.

When an EDI alias error (04021) is generated by Information Exchange, it indicates that the alias was either not found on any of the tables referred to in the QUALTL DD card, or that the destination account and user ID did not constitute a valid mailbox ID. Verify the account and user ID with your trading partner, and then update the appropriate table with the correct information.

[Return to Questions]

How do I resolve time-out errors?

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

• After sending a request to end a session, Expedite Base/MVS did not receive a response from Information Exchange within the timeout limit.
• Expedite Base/MVS 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.
• 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]

Why am I getting parser errors (14020-15040) even though my profile and message commands look fine?

Parser errors can happen when line, or sequence, 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/MVS 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]

Why does Expedite Base/MVS terminate with a B37 error even though the data set size is large enough to handle the data?

Check to see if you have defined the SPACE parameter as RLSE. Specifying this value can cause Expedite Base/MVS to open an empty dataset and release all but the minimum space needed (just enough to define the data set), leaving no room for data to be written when the data set is reopened during processing.

[Return to Questions]

No, you cannot override these messages. Expedite Base/MVS writes messages to the operator´s console to report an invalid or unexpected response to a VTAM or TCP/IP command. The messages allow the operator to respond appropriately to the problem.

[Return to Questions]

What is Notification Manager?

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]

What region size should I use when running my Expedite Base/MVS job?

The manual states that Expedite Base/MVS must have a region of least 1024K. With today's more complex environments, this may be insufficient for your application. Instead of increasing the region size until your job can run, it is recommended that you use REGION=0K on your PGM=jobcard. When you specify REGION=0K, the application requests region resource as it needs it in small increments.

[Return to Questions]