Adabas Review reports can be set to start automatically whenever Review initializes.
Then RAOSAUTO, the Adabas Review autostarted report parameter generation routine, generates the report definition control statements and writes them to one of two parameter files, RVUAUT1 or RVUAUT2, alternating between them by writing to the older file.
When Adabas starts, the files are read by Adabas Review using the RVUAUT1 and RVUAUT2 statements in the job stream. Refer to the section Batch Processor Job Control Requirements for more information.
Note:
Under OS/390 and z/OS, the installation procedure defines the
statements RVUAUT1 and
RVUAUT2 so that they point to members of a PDS. To
avoid constant compression of these datasets, the statements may point to
sequential datasets.
RAOSAUTO automatically regenerates the control statements for all autostarted reports when you make changes to an autostarted report, delete an autostarted report, or modify the target definition for the database being monitored by the reports.
In exceptional circumstances (e.g., the source library becomes too full and requires compressing), you can force regeneration of the control statements for all autostarted reports by either issuing the GENAUTO command or entering the parameters manually using batch parameter statements.
Additionally, when you issue the GENCARD command, RAOSAUTO generates report parameter cards for user-specified reports and directs them to a user-specified output file.
In OS/390, z/OS, VSE/ESA, and BS2000 environments, RAOSAUTO executes as a subtask of Adabas Review and is only active when
an autostarted report definition is saved in the online system;
a database target definition is saved in the online system.
In the z/VM environment, RAOSAUTO executes as an EXEC. The GENAUTO and GENCARD commands are not available in z/VM.
