Output buffer examples

The examples in this section illustrate the:

SEARCH type subcommands (and LISTCONTROL) might require your application program to use one or more OPERATION=CONTINUE calls to the DFSMSrmm API to receive all of the search results.
Your application program should expect to receive more than one set of return and reason codes. In the example, DFSMSrmm issued a different set of codes for each output buffer:
- Return code 0, reason code 4.
- Return code 4, reason code 2.
- Return code 4, reason code 4.
Depending on the subcommand that you specify, the search criteria that you specify (fully or partially qualified names), and whether you specify a LIMIT value or LIMIT(*), DFSMSrmm can also issue these return codes and reason codes.
- Return code 0, reason code 0.
- Return code 4, reason code 8.
For more information about the return codes and reason codes that the API returns, see Table 1.
Header lines for search lists are placed at the beginning of the first output buffer of each set of buffers: The first output buffer after OPERATION=BEGIN, and the first output buffer after OPERATION=CONTINUE in response to the return code 4 and reason code 2.
Messages issued by DFSMSrmm and that are placed in your output buffers are introduced by <MSGL> structured field introducers rather than <LINE> structured field introducers.
The number of output data lines that are placed in your buffer is dependent upon the interaction of:
- The total number of searched records (entries).
- The size of your output buffer.
- The LIMIT value used for the search.

Figure 1, Figure 1, and Figure 1 display the contents of the output buffers when:

Your application program issues an OPERATION=BEGIN, OUTPUT=LINES for a SEARCHRACK RACK(*) LIMIT(90) subcommand.
Your application program is using a minimum size (4096 bytes) output buffer.
There are 130 records in the RMM inventory.