ARCH - BOT

This page describes the initialization parameters from ARCH through BOT:
deliver
This page describes the initialization parameters from ARCH through BOT:
ARCH
The default archive criteria to be used by reports that are to be archived to CA View when no archive criteria value is specified in the ARCH field on the Report Definition Attributes panel.
Enter a value from 0 - 99 inclusive for nn (nn identifies and references archive criteria you specify with either ARCHnn initialization parameter described as follows).
For example, if you specify ARCH=2, archive criteria you specify for initialization parameter ARCH2 (ARCH2=//SAR/T, or ARCH2=DIRECT) are used by default for reports that are archived to CA View.
Specifying 0 indicates that, by default, reports are not to be archived to the CA View database.
Syntax:
ARCH=
nn
Default:
0
ARCHnn (Form 1)
ARCHnn (Form 1) specifies a set of criteria, that is identified and referenced by the value
nn
.
nn
defines the attributes for reports that are to be archived to CA View using the JES spool.
You can specify a value from 1 - 99 inclusive for nn (or 01-99 depending on your installation option). This format specifies a set of SYSOUT attributes for using the JES spool as the intermediate holding area for reports to be sent to CA View for archiving. The set of SYSOUT attributes are:
  • c
    -- The SYSOUT class
  • dddddddd
    -- The destination
  • ffffffff
    -- The forms name
  • m
    -- The archive medium, D (disk) or T (tape)
  • pppppppp
    -- The print mode
Note:
The ARCH parameter can also be used with all attributes separated by slashes (/).
ARCH
nn=c/dddddddd/ffffffff/m/pppppppp
These attributes are positional in this format.
Note:
If you do not specify an archive medium, reports are archived to disk by default.
For any report identified for archiving, the appropriate set of archival criteria is used to allocate a special SYSOUT data set to be spun off for archival by CA View.
Assume, for example, that your site has CA View installed and is archiving all SYSOUT with a forms name of SAR (the appropriate SAR initialization option is FORM=SAR). You then define two sets of archive criteria, numbered 1 and 2, for archiving reports to disk and tape as follows:
ARCH1=//SAR/D
ARCH1=(FORM=SAR,MEDIUM=D)
ARCH2=//SAR/T
ARCH2=(FORM=SAR,MEDIUM=T)
You can also define multiple specifications of an individual ARCHnn parameter for archival to multiple CA View databases.
Example
ARCH1=S///D
  • ARCH1=(CLASS=S,MEDIUM=D)
    Archive using JES spool class S
  • ARCH1=T//SAR/D
  • ARCH1=(CLASS=T,FORM=SAR,MEDIUM=D)
    Archive using JES spool class T with a forms name of SAR
Syntax:
ARCH
nn
=(CLASS=
c
,DEST=
dddddddd
,FORM=
ffffffff
,MEDIUM=
m
,PRMODE=
pppppppp
)
Default:
None
ARCHnn (Form 2)
Archive directly to a specific CA View database without passing the reports to the JES spool.
nn
is a value from 1 - 99 (or 01-99 depending on your installation option).
You can specify ARCH
nn
=DIRECT to default to the database name specified in the SAR= initialization parameter or specifically reference the CA View database prefix.
For example:
ARCH2=DIRECT/PROD.VIEW
You can also define multiple specifications of an individual ARCHnn parameter for archival to multiple CA View databases.
Example
ARCH1=DIRECT
Specifies archival to the database specified in the SAR= initialization parameter
  • ARCH1=DIRECT/TEST.VIEW
    Specifies archival to the TEST.VIEW database
  • ARCH1=DIRECT/SAR1
  • ARCH1=DIRECT/SAR2
    Specifies archival to both the SAR1 and SAR2 databases.
    Note:
    If the bundle holding copy is directed to this archival group, the holding copy resides in the first DIRECT database, that is, SAR1.
The DRAS Domain Name is optional and is only needed for the email notification feature.
The DRAS Domain Name identifies the ENF system identifier, DRAS server name, and View DRAS repository name that the OM Web Viewer is to use to access an email-attached report.
This domain name and the Web Server link (WEBSRVn initialization parameter setting) are components of the HTML WEBLINK that can be included within an email message. The format of the domain name is:
CCITASK.DRASTASK.DBNAME
  • CCITASK -- The ENF SYSID of the system where CCI is running
  • DRASTASK -- The name (unique identifier) of the DRAS task assigned on the DRASCFG configuration file SET SERVER ID(drasid) statement
  • DBNAME -- The repository name assigned to the View system by the DRAS task on the DRASCFG configuration file ACCESS REPOSITORY NAME(dbname) statement
  • Example --
    CCITASK.DRASTASK.DBNAME
Syntax:
ARCHnn=DIRECT/
database prefix
Default:
None
AUTHTID
The suffix character to be used for the security table load module, RMOATHTx.
This module is used to authorize access to database data and functions.
If the started tasks for the same database are started on multiple systems, these started tasks must use the same AUTHTID setting.
The RMODBASE utility always uses the default security table, RMOATHTB.
Syntax:
AUTHTID=
x
Default:
B
AUTOACT
Specifies whether a report can be automatically activated by CA Deliver when opened.
If AUTOACT=NO is specified, CA Deliver excludes any report from processing that has not been previously activated.
Syntax:
AUTOACT=
xxx
Default:
YES
BANNER
The name of the default model banner page used to print non-bundled reports.
To specify that no banner pages are produced for reports as a default, do not specify a value for this initialization parameter (BANNER= ).
Syntax:
BANNER=
xxxxxxxx
Default:
BANNER
BEGINDAY
The time of day in a 24-hour format (1420 represents 2:20 p.m.) when a new day starts for bundle processing.
This parameter allows the bundles to remain open and active through the daily cycle time.
Syntax:
BEGINDAY=
xxxx
Default:
BEGINDAY
BNDLBNR1
The name of the default model banner page to be used for the bundle banner page when printing a bundle.
To specify that no bundle banner pages are produced for bundles as a default, code the BNDLBNR1 option with no value (BNDLBNR1= ).
Syntax:
BNDLBNR1=
xxxxxxxx
Default:
BDFLTB
BNDLBNR2
The name of the default model banner page to be used for the distribution banner page when printing a bundle.
To specify that no distribution banner pages are produced for bundles as a default, code the BNDLBNR2 option with no value (BNDLBNR2= ).
Syntax:
BNDLBNR2=
xxxxxxxx
Default:
BDFLTD
BNDLBNR3
Specifies the name of the default model banner page to be used to print the report banner page for a bundle.
To specify that no report banner pages are produced for bundles as a default, code the BNDLBNR3 option with no value (BNDLBNR3= ).
Syntax:
BNDLBNR3=
xxxxxxxx
Default:
BDFLTR
BNDLCLS
The SYSOUT class (cannot be a held class or a class assigned to a printer) to be used for the bundle holding copy of a report that is retained in the JES spool for bundling.
The SYSOUT class defined by BNDLCLS and the destination defined by BNDLDEST are used together to output a copy of the bundle to the JES spool.
The copy must be retained on the JES spool until the bundle is complete for printing. Therefore, the combination of BNDLCLS and BNDLDEST must be unique in the installation and must never be printed by the installation.
When direct-to-View archival is in effect for a report to be bundled, no bundle holding copy of the report is created in the JES spool. Instead, the archival copy of the report on the CA View database is used when creating the bundle.
Syntax:
BNDLCLS=
x
Default:
9
BNDLCONF
Specifies whether you want the bundle confirmation facility to be activated.
Note:
Bundle confirmation can also be specified for an individual bundle on the Bundle Definition Attributes panel.
Syntax:
BNDLCONF=
xxx
Default:
NO
BNDLDEST
The SYSOUT destination to be used for the bundle holding copy of a report that is retained on the JES spool for bundling.
The destination specified in this parameter must be defined to JES. Failure to do this can result in RMOPS102 or RMOPS202 messages and a U-0002 Abend in the bundle job.
Syntax:
BNDLDEST=
xxxxxxxx
Default:
None
BNDLHDTL
Specifies whether accurate counts of lines and pages are to be available for bundled copies of reports.
This option requires that you set BNDLMOUT=YES and HDETAIL=YES in addition to installing the RMOJ2XIT, RMOFSSUX, RMOJ3X21 exits, as appropriate (depending on your environment).
Syntax:
BNDLHDTL=
xxx
Default:
NO
BNDLINT
The default bundling interval to be used for a bundle when no bundling interval is specified in the bundle definition.
Specify hours and minutes in 24-hour format (0220 represents two hours twenty minutes). If you omit this value or specify 0000, continuation bundles are not produced.
Note:
This initialization parameter specifies a time interval, not the time of day.
Syntax:
BNDLINT=
nnnn
Default:
0000
BNDLMOUT
Specifies whether a batch-submitted bundling job can use multiple DD statements to produce a bundle.
By using multiple DD statements, reports with different print attributes can be bundled but still printed with their different attributes. To ensure that the multiple DD statements are printed together, the bundling job uses the GROUPID parameter of the OUTPUT JCL statement.
Specify BNDLMOUT=YES if the following is true:
  • The batch-submitted bundling job executes on a JES2 system
  • You also specify OUTPUT=YES
  • You specify &USERSET=YES in the JES2 initialization parameters
Syntax:
BNDLMOUT=
xxx
Default:
NO
BNDLSCAN
The time interval (in minutes) that the bundle output task waits between scans of the active checkpoint when it is looking for bundles to compose or submit.
Syntax:
BNDLSCAN=
nn
Default:
2
BNDLWAIT
Specifies the default value for whether a bundle must wait for the end of a bundling interval before printing.
If BNDLWAIT=NO is specified (or defaulted), bundles do not wait but print as soon as all of the reports needed for the bundle are created (unless overridden in the bundle definition).
Syntax:
BNDLWAIT=
xxx
Default:
NO
BOT
Specifies whether the bundle output task is started at initialization time.
Syntax:
BOT=
xxx
Default:
 YES