Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
![]() Messages and message variables structured field introducers z/OS DFSMSrmm Application Programming Interface SC23-6872-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
When messages or message variables are returned to you as output
data, they are put into your output buffer as structured fields as
shown in Figure 1.
Figure 1. Structured field introducers for messages and message variables
When you use the CONTINUE operand on any SEARCH subcommand, the
DFSMSrmm API returns the continue information at the message group
with the CONT SFI as shown in Figure 2.
Figure 2. Message group with the CONT SFI
When you specify OUTPUT=LINES, messages issued by DFSMSrmm are placed in your output buffer using the LINE SFI. When you specify OUTPUT=FIELDS, only the messages listed in Table 1 are placed in your output buffer. These messages, some of which are issued only in conjunction with a subcommand parameter such as POOL or COUNT, are included in the output because they contain data and codes that can be especially useful to your application. Your application program should use the return and reason codes that it receives rather than messages to determine whether or not the subcommand request was successful. Table 1 lists:
For a detailed explanation of these messages, see z/OS MVS System Messages, Vol 5 (EDG-GFS). For DFSMSrmm return and reason codes, see z/OS DFSMSrmm Managing and Using Removable Media. ![]() ![]() ![]() |
![]() |