An example of a BAS error result set

As an example of how you can the FEEDBACK data to obtain BAS error result set information,this example illustrates the results of issuing a PERFORM OBJECT command. In this case, PERFORM OBJECT ACTION(INSTALL) was issued to install the CONNDEF definitions in the result set referenced by TOKENC.

Figure 1. Using PERFORM OBJECT to install BAS definitions
This figure illustrates the results of issuing the PERFORM command PERFORM OBJECT ACTION(INSTALL) RESULT (TOKENC)

One of the connection definitions (CON02, z/OS® Communications Server) was not successfully installed by the PERFORM OBJECT command. There is a pointer to the FEEDBACK data.

Figure 2 shows how you can use the FEEDBACK command to retrieve the FEEDBACK records associated with the result set referenced by TOKENC.
Figure 2. Using FEEDBACK to retrieve diagnostic data for a result set
This figure illustrates the results of issuing the FEEDBACK command FEEDBACK RESULT(TOKENC) INTO (AREA5)...
The FEEDBACK data shown in Figure 2 reveals the cause of the problem. CICSPlex® SM returned RESPONSE and REASON values of TABLEERROR DATAERROR, which means that one or more connection definitions did not install successfully. Furthermore, the ERR_RESULT attribute points to an error result set which contains a single BINSTERR resource table record.
Figure 3. BINSTERR error result set
This figure illustrates the BINSTERR resource table record.
The BINSTERR error result set referenced by TOKENE, and shown in Figure 3 is accessed using a FETCH command.
Figure 4. Using FETCH to retrieve BINSTERR records
This figure illustrates the use of the FETCH command FETCH RESULT(TOKENE) INTO (AREA5)... to retrieve BINSTERR records.

Figure 4 shows how you can use the FETCH command to retrieve the BINSTERR records associated with the error result set referenced by TOKENE.



eyup1e3.html | Timestamp icon Last updated: Sunday, 4 June 2017