Sender-detected error examples

The following figures show examples of sender-detected errors during paged output (or input). IMS is the sender in both figures.

Figure 1. Example of sender-detected error while sending demand-paged output message
Flow 1 and flow 2 have multiple arrows between IMS and OTHER with various labels on the arrows, such as ATTACH SCHEDULER,DQN=X,(BB)EB, DR2, and others. Both flows include the IMS /DEQUEUE command.

Flow 1 in Figure 96 shows an IMS /DEQUEUE command occurring during the second output demand page. The CANCEL command terminates the chain (page) in progress, and the LUSTATUS terminates the receiving process. If the paged output message follows another input or output message that began a bracket, the BB is not sent on the first page OIC.

Sample flow 2 is the same, except that the IMS /DEQUEUE command occurs between output pages so that the CANCEL command is unnecessary.

Figure 2. Example of sender-detected error while sending autopaged output message
Flow 1 and flow 2 have multiple arrows between IMS and OTHER with various labels on the arrows, such as ATTACH dpn=SCHEDULER,FIC,(BB), data,MIC, and others. Both flows include the IMS /DEQUEUE command.

Again, the CANCEL command terminates the chain (page) in progress and the LUSTATUS terminates the receiving process. The initial begin-bracket and the resulting bracket send/receive protocol are the same as for demand-paged output in Figure 1.

Flow 2 is the same as flow 1 in Figure 97, except that the IMS /DEQUEUE command occurs while between output pages, so that the CANCEL command is unnecessary.