z/OS DFSMSrmm Application Programming Interface
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Issue a request

z/OS DFSMSrmm Application Programming Interface
SC23-6872-00

If the open is successful, you can start a request session by issuing a TSO subcommand through the API. Sample code for this is shown in Figure 1. Place the command string in the command buffer, initialize buffers, set function code to 3 (=BEGIN), and call EDGXHINT.
Figure 1. Issue a TSO subcommand using EDGXHINT
char  command[12]  =  "SV  OWNER(*)";         // define the command
strcpy(commandStrct.commandBuffer,command);   // fill the command buffer
commandStrct.com_length = strlen(command)+2;  // set the command length
                                              // command length + 2 byte length field
strcpy(outputStrct.outputBuffer,'\0');        // clear output buffer
outputStrct.header.out_used=0;
strcpy(interStruct.messageBuf_ptr1,’\0’);     // clear message buffers
strcpy(interStruct.messageBuf_ptr2,’\0’);
interStruct.function = 3L;                    // set function code
EDGXHINT(pI);                                 // call EDGXHINT

You can evaluate the return and reason code to determine whether the command was processed successfully. From the message count, you can determine whether there are messages available in the message buffers. You will find returned data in the output buffer. This data is in SFI format and can be processed as described in Processing the output data in the output buffer. If a search command was issued, you will find one or more complete resources in the output buffer.

EDGXHINT always uses the EDGXCI MULTI=YES keyword on behalf of its callers. Therefore, all callers must be updated, if necessary, to handle a buffer containing multiple resources. A caller requiring the return of just a single resource can use the LIMIT(1) operand on the SEARCH subcommand.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014