Processing sequence in Endevor package output shipping

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench
• CA 2E

Issue/Introduction

This document describes the sequence in which C1BMX000 program (Endevor package shipping utility) processes the SHIP statements submitted to it.
This sequence is NOT necessarily the same in which the statements are passed to the utility.

Resolution

Endevor utility C1BMX000 is used to perform the shipping of package outputs to its final destinations. It accepts from one to many statements in the form:

SHIP PACKAGE package name TO DESTINATION destination OPTION option  .

It is important to note that, unlike other Endevor SCL statements, the sequence of SHIP statements does NOT imply the sequence in which they will be processed.

This is because the utility will:

• Collect and verify all the statements received.
• Determine the output members to be affected by the whole process (which means the sum of all the specified SHIP statements).
• Build the host staging datasets to be transmitted to each destination by destination.

Since all the statements entered are processed as a whole entity, this means that they cannot be expected to be processed in any sequence. For example, if we submit the following sequence:

SHIP PACKAGE P1 TO DESTINATION D1.
SHIP PACKAGE P1 TO DESTINATION D2.
SHIP PACKAGE P2 TO DESTINATION D1.
SHIP PACKAGE P2 TO DESTINATION D2.

In this case, we will have statements 1 and 3 processed together, as they both go to destination D1, and statements 2 and 4 together as they go to destination D2.

The only way to influence the order in which SHIP statements are processed is to code each statement in it's own JCL step running C1BMX000.