When starting a CA Deliver system of the first time, it is a good practice to focus on the basic initialization parameters that comprise the minimum requirements for successful startup. After that occurs, examine the other initialization parameters to add more detailed processing options for your environment
Business Value:
Focusing on a basic subset of the initialization parameters simplifies a first-time installation and results in a faster implementation of CA Deliver. Additional options and parameters can be specified later, based on the evaluation of business requirements at your site.
Additional Considerations:
The following initialization parameters are the minimal requirements to specify when starting a CA Deliver system for the first time.
Set NAME to the high level qualifier of the CA Deliver database and SAR to the high level qualifier of the primary CA View database.
Set SYSID to specify the parameter that identifies the CA Deliver started task. If multiple started tasks are run on the same system image, their SYSID parameters must be different.
Set JOBCLSL to the job classes and SYSCLSL to the SYSOUT classes where Deliver intercepts reports using pre-spool processing.
Post-spool Processing
Set NETCLSL, NETDEST, and NETFORM to the SYSOUT class, destination, and form where Deliver picks up reports from JES using post-spool processing. Post-spool processing is referred to as the CA Deliver Network Input Interface. Use NETONLY to state whether CA Deliver does only post-spool processing.
Use the ARCHnn parameters to specify criteria for the archival of reports into CA View. You can specify up to 99 ARCHnn parameters.
Use ARCH to specify the default ARCH parameter to use if a report definition does not specify an ARCH parameter.
Use HDETAIL, BNDLHDTL, and MAXHIST to specify whether detail history is being kept and how many generations of historical data are to be kept.
Use BNDLMOUT and OUTPUT together to allow bundled reports with unlike attributes to be printed together.
To avoid performance degradation when multiple RMOSTCs access the same database, specify BOT=YES for only one started task. Specify BOT=NO for the other started tasks.
Use TIME, BEGINDAY, and DAYS to specify the time of day and the days of the week when the CA Deliver daily cycle and bundle cycles are to occur.
If there are multiple CA Deliver RMOSTCs accessing the same database, we suggest that BOT=YES, and TIME be set in one RMOSTC only, and BEGINDAY be set to the same value in each RMOSTC.
The other tasks should have BOT=NO and TIME=0000.
More Information:
See the “Initialization Parameters” chapter of the Reference Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|