Using OUTPUT statements

Use the OUTPUT statements to define what information you want to extract from HCL Workload Automation for Z, where to send it, and in what format. Workload Automation Programming Language writes the output from LIST or SELECT requests only if you have run OUTPUT statements for the segments encountered in these commands.

Workload Automation Programming Language provides you with many predefined OUTPUT statements. They are available either in external members that you can include with the INCLUDE command, or through in-built statements that you can specify with the LOADDEF command.

Many EQQFLxxx and EQQGRPxxx members contain the same OUTPUT definitions. The EQQFLxxx members contain also statements to escalate the severity of two messages that would indicate whether you have referenced a segment or field not supported by your current version of HCL Workload Automation for Z. By default, these messages are advisory and do not set a return code. The FILE members cause RC=4 if the OUTPUT statements following the content of the supplied member references something that is not supported. The two different approaches allow for unsupported fields to be ignored, for example, if running common code against current and earlier versions of HCL Workload Automation for Z.

Individual segment, record, or group members can still be used with error checking in place, either by adding the two SETSEV statements from the EQQFLxxxx members into your site defaults (which will turn on checking for ALL OUTPUT statements including the supplied ones) or by coding the statements in your SYSIN to issue only RC=4 for invalid references in the statements that you create.

The in-built OUTPUT definitions include every field, for every segment, that sends ILSON data to OUTDATA, and Batch Loader data to OUTBL. You can load these definitions by using the LOADDEF statement. For example, set LOADDEF AD* to load the in-built OUTPUT definitions for all the segments beginning with AD. If instead of exploiting the in-built versions, you want to load the prebuilt members from SEQQWAPL, use the INCLUDE statement.

The SEQQWAPL library must be allocated in the JCL, then an INCLUDE statement can load the relevant member. For example, set INCLUDE WAPLMAPS(EQQADW) to load the member that contains all of the OUTPUT statements for application description segments. Load the in-built OUTPUT statements only when you need all the fields for a particular segment, for example when extracting batch loader for database objects. If you do not need every field from each segment in your output, define your own OUTPUT statements. For a list of all available segment and field names, refer to the SEQQWAPL member EQQFLALL described in Alternative resource names