Second output buffer

After processing the OPERATION=CONTINUE parameter, the DFSMSrmm API continues processing. The DFSMSrmm API issues return code 4 and reason code 2, returns control to your application program. Your output buffer contains 20 structured fields.

Figure 1. CONTINUE example, second output buffer

<Begin RACK or BIN group>
  <LINE>031086  CART3480   031086  IN USE    SHELF
  <LINE>031568  CART3480   031568  IN USE    SHELF
  <LINE>031599  CART3480   031599  IN USE    TRON
    ...
    ...
  <LINE>032848  CART3480   032848  IN USE    SHELF
  <LINE>032898  CART3480   032898  IN USE    SHELF
  <MSGL>EDG3203I SEARCH COMPLETE - MORE ENTRIES MAY EXIST
  <MSGL>EDG3012I 90         ENTRIES LISTED
<End RACK or BIN group>

In Figure 1:

There are no header lines in the second output buffer.
There are only 16 output data lines (the LINE structured field introducers).
The last output data line is followed by two message lines introduced by the <MSGL> SFI.

The DFSMSrmm API returns control to your application program even though there is room in the output buffer for more data. This is because the LIMIT value of 90 was reached as indicated by the second message line.

The return code 4 and reason code 2 indicate that more entries might exist. When you use OPERATION=CONTINUE, one of these statements is likely to occur:

When there are more entries, your application program receives control back with more output data in your output buffer.
When there are no other entries, your application program receives control back with a buffer that is empty or that contains only messages.