You can use option S.4 to generate JCL for _beta report batch jobs.
Adabas Audit Data Retrieval provides several skeletons and panels for the generation of JCL. You can copy these skeletons and modify them according to your needs. Adabas Audit Data Retrieval distinguishes between the reports that are provided with Adabas Audit Data Retrieval (report type System) and user-defined reports (report type User).
To generate JCL for a _beta report batch job:
This will display the available reports in a table:
PE97RP05 ------------------------------------------- Row 1 of 7
Command ===> ________________________________________________ Scroll ===> CSR_
Display Batch Report Definitions ( LEFT/RIGHT )
S - Select I - Insert C - Copy D - Delete G - Generate
Sel Report Name Report Title Type
ARCHIVE_001 ARCHIVE POOLS AND THEIR SUBPOOLS SYST
ARCHIVE_002 ARCHIVE DATASETS SYST
ARCHIVE_003 ARCHIVED LISTS SYST
ARCHIVE_004 LIST RELATED ARCHIVE INFORMATION SYST
INDEX_000 USAGE OF LIST INDEX DEFINITIONS SYST
INDEX_001 USAGE OF LIST INDEX DEFINITIONS SYST
REPORT_000 RPG BATCH REPORTS: LIBRARIES AND MEMBERS SYST
******************************** BOTTOM OF DATA ********************************
This will display an additional panel for the corresponding report, where you can specify more values.
PE97RPA2 ---------------------------------------------------------------------
Command ===> _________________________________________________________________
Report about Archive Datasets Table(s) : AGR
Pool Name ===> POOL1___ Name or Mask
Pool Owner ===> CUST001_ Name or Mask
Sorted by ===> 1 1 Volume, Dataset Name
2 Volume, File Sequence Number
3 Expiration Date
Output Dataset ===> B97ADM.TEST_________________________________
Press the ENTER key to generate the batch job.
Press the END key to return to the previous menu.
This will display the tailored JCL in the ISPF editor.
You can make your own batch report definitions under option S.4, for example, by modifying the definitions provided by Adabas Audit Data Retrieval. New and modified report definitions are of the report type User.
PE97RP10 --------------------------------------------------------------------- Command ===> _________________________________________________________________ Insert Batch Report Definition Report Name ===> INDEX_000....... Report Type : USER Report Title ===> USAGE OF LIST INDEX DEFINITIONS FOR OWNER CUST001_ Owner ===> B97ADM__ Panel Library ===> ____________________________________________ Skeleton Library ===> ____________________________________________ LangUse Tailor Panel Id ===> PE97RPI0 ===> YES (Y)es,(N)o JCL Member ===> SX97JRPG ===> NO_ (Y)es,(N)o Skeleton 1 ===> SE97RP$$ ===> YES ===> NO. (Y)es,(N)o Skeleton 2 ===> SE97RPI0 ===> YES ===> NO_ (Y)es,(N)o Skeleton 3 ===> SX97RPI0 ===> NO_ ===> NO_ (Y)es,(N)o Skeleton 4 ===> ________ ===> NO_ ===> NO_ (Y)es,(N)o Press the ENTER key to insert the definition. Press the END key to return to the previous panel. |
Field |
Description |
---|---|
Report Name |
Name (max. 16 characters) |
Report Title |
Descriptive title (max. 50 characters) |
Owner |
Owner |
Panel Library |
Name of the library containing the panel specified in the Panel ID field |
Skeleton Library |
Name of the library containing the skeletons specified in the Skeleton n fields |
Panel ID |
This panel will be displayed after entering the line command G; it is used to specify variable values, for example, selection criteria. |
JCL Member |
Member containing the JCL for the batch job |
Skeleton n |
Members containing the required statements for _beta report |
LangUse |
No When Adabas Audit Data Retrieval looks for the specified panel or skeleton, it uses the member name exactly as it has been typed in the field Yes When Adabas Audit Data Retrieval looks for the specified panel or skeleton, it replaces the second character in the member name with the current language character |
Tailor |
Yes Tailoring inserts the statements of the skeleton in the generated JCL No Tailoring inserts a DD statement for the skeleton in the generated JCL |