

Utilities › RMODSC Report Data Set Collector › Data Set Collector Considerations
Data Set Collector Considerations
Certain requirements and restrictions govern the use of the data set collector which are:
- The CA Deliver started task for the specified database must be started and running on the same system as the data set collector job.
- Non-bundled report output is produced under the job and step of the job that executes the data set collector utility.
- No distribution output is generated for monitor output (the monitored report can however be archived and/or bundled).
- UNDEF reports are not generated for non-matched job name, step name, procedure step name, data definition name, and/or report name (UNDEF reports can however be generated for non-matched stacked report pages).
- If a report definition name is designated through control statement specification or user exit determination, you need not define the report under the execution job name. The step name, procedure step name, and DDname defined under the job are also ignored but are defined to differentiate it from other reports.
- The data set collector does not carry forward any default JCL attributes for the reports. If specific attributes are required for the report, define them in the CA Deliver database within the report or distribution specifications.
Copyright © 2013 CA.
All rights reserved.
 
|
|