General

A report function can be invoked through the PROIV Bus, and return data to the API caller application. This is specified by use of a Report Destination Type of API.

This destination type may be used anywhere a report destination type is used. These include bootstrap functions $SPOOL to specify use per-function, or $SYSDEF for all functions. Also, it may be set dynamically under PROIV application control by using the logic verb SET_RPTOPT, or the more flexible and preferred method using the @RPTOPT system variable.

Note that if you have a green screen client active in the current task, you cannot output reports over the Bus.

S/390 Product Only

Under the S/390 product, DSL output can be produced from data located in DB2, DLI, or VSAM. DSL report output is placed in CICS temporary storage queues for subsequent retrieval by the external calling application. The CICS COMMAREA used to signal task completion and that DSL output has been produced, also contains the CICS Temporary Storage queue names that contain the DSL data.

If S/390 PROIV is invoked via the PROIV Kernel Manager, the Kernel Manager automatically issues subsequent requests to retrieve DSL output. However, if the S/390 PROIV API is used and DSL is generated, the user will need to create a mechanism to retrieve the DSL from the appropriate temporary storage queue.

Comment on this topic

Topic ID: 540044