Creating and Using Dynamic Identifiers for Reports and Distribution › What is a Dynamic Report › How to Identify a Dynamic Report

How to Identify a Dynamic Report

Enter DYNAM as the value in the Type field to identify a report as dynamic. A dynamic report is defined using a fixed report definition name. The distribution specifications for the dynamic report identify the report and distribution names to be assigned to the page data.

Example

In the following example, TRJOB02-D01 and TRJOB02-D02 are fixed names for a dynamic report.

CA Deliver ---------------- Reports for Job: TRJOB02 ------------- Report saved
Command ===>                                                  Scroll ===> PAGE

 Desc    ===> UPDATE ACCOUNTS PAYABLE
 Prevrun ===>

Sel Stepname Procstep DDname     Report ID                        Type  Prevrun
    UPDTSTEP          REPTS      TRJOB02-D01                      DYNAM
                                 TRJOB02-D02                      DYNAM





******************************* Bottom of Data ********************************

Dynamic reports are similar to stacked reports. Multiple dynamic reports can be defined to a job. The DD statement, the JCL attribute overrides, report identification text, special instructions, and bundle specifications are the same.

However, the distribution specifications for a dynamic report are different. These specifications identify key information on a report page. They also help you to form a dynamic report, distribution name, or both for the page data. The report pages are distributed and printed under the dynamically generated report and distribution name. Archival copies are created for each uniquely generated report name.

DLV--Report Considerations

For CA Deliver to process dynamic reports correctly, the reports must be defined to be archived directly into at least one CA View database using the ARCHn RMOPARMs. To archive additional copies of dynamic reports into different CA View databases using SARFSS or SARSTC, use the ARCHn parameters to direct the reports to the JES class, destination, and form that SARFSS or SARSTC is defined to process.

For example, with ARCHn parameters defined as:

ARCH8=DIRECT/VIEW.SYSTEM1
ARCH8=N/D001/VIEW/D         

For all reports defined with ARCH8 on the Deliver Reports Definition Attributes screen, one copy is archived directly into the CA View database with the hlq of VIEW.SYSTEM1. One additional copy is written to the JES queue in sysout class N, destination D001, form View for either SARFSS or SARSTC to pick up.