7. FILES › 7.4 Audit File › 7.4.3 Usage Considerations
7.4.3 Usage Considerations
Note the following special considerations or techniques
related to using the audit files:
1. The audit files are generation data groups and are, by
default, created on tape. Optionally the DAY1 and the
DAY2 audit files can be written to disk using the
following JCLDEF parameters.
ACCTDAY1PARM
The ACCTDAY1PARM parameter is used to generate the
unit-level DAY1 audit file on disk. This parameter
includes both keyword parameters and keyword=value
specifications. The general form of the ACCTDAY1PARM
statement is the keyword ACCTDAY1PARM followed by one
or more ACCTDAY1PARM parameters.
ACCTDAY2PARM
The ACCTDAY2PARM parameter is used to generate the
unit-level DAY2 audit file on disk. This parameter
includes both keyword parameters and keyword=value
specifications. The general form of the ACCTDAY2PARM
statement is the keyword ACCTDAY2PARM followed by one
or more ACCTDAY2PARM parameters.
The following describes each of the ACCTDAY1PARM and
ACCTDAY2PARM parameters:
o DISK
Required if you want the DAY1 or DAY2 audit file
written to a disk device. If not specified, the
file is written to tape and other parameters on the
ACCTDAY1PARM/ACCTDAY2PARM statements have no
effect.
o SPACE=spacedef
Default: No SPACE parameter specified.
Defines the space allocation parameter for the DAY1
and/or DAY2 audit file on disk. Specify this
parameter according to JCL language syntax.
o UNIT=unitname
Default: No UNIT parameter specified
The generic unit name to be used for the DAY1
and/or DAY2 audit file on disk. Specify this
parameter according to JCL language syntax. The
default will be the value used in DASDUNIT.
o VOLSER=volser
Default: No VOLSER parameter specified.
Define the VOLSER parameter if you want the DAY1
and/or DAY2 audit file written onto a specific
disk. Specify this parameter according to JCL
language syntax.
Note: If you chose to write the DAY1 and/or DAY2 audit
file to disk, the following unit jobs must be
regenerated:
ACTDAY1R - ACT Daily Audit File Recovery Job
ACTEXTU - Accounting External Files Job
ACTINITA - ACT DAY1 Audit File Initialization Job
ACTRTSIM - ACT Rate Simulation of Charges Job
AUDITRPT - ACT Component Audit Report Job
DAILY - Database Daily Job
MONTHACT - Special Accounting Dates Monthly Update
Job
MONTHLY - Standard Monthly Update Job
ACCTDAY1SMSPARM
Optional parameter for specifying System Managed
Storage (SMS) keywords (e.g., STORCLAS=storclas) to be
used for the DAY1 audit file disk/tape data set
allocations. Specify one or more SMS parameters
according to JCL language syntax. There is no default
and continuation is not allowed. This statement is
used to generate daily audit jobs at a unit level.
ACCTDAY2SMSPARM
Optional parameter for specifying System Managed
Storage (SMS) keywords (e.g., STORCLAS=storclas) to be
used for the DAY2 audit file disk/tape data set
allocations. Specify one or more SMS parameters
according to JCL language syntax. There is no default
and continuation is not allowed. This statement is
used to generate daily audit jobs at a unit level.
2. The generation of the DAY1 file containing the
month-to-date data is the most current GDG version (that
is, 0) and is modified each day in the daily CA MICS
job stream. The prior month's audit information is
contained on previous GDGs.
3. The reports show the information in this file can be
produced from the Audit Reports option of the Process
Control Menu (MWF;4;2;4;5;1). Use the selection options
on the panel to select a subset of the information from
the file.
4. The DAY1 audit file may be recreated from the DAY2
tape/disk by submitting ACTDAY1R from prefix.MICS.CNTL.
5. Since the DAY1 audit file is a "MOD" GDG, the tape is
reused every day in the DAY199 step. It may be
beneficial to change the DAY199 JCL to have the DAY1
Audit File written to a disk or a mass storage GDG to
avoid tape-handling problems. If this file is switched
to disk, you may need to change the DAY1 blocksize. To
write the DAY1 file to disk instead of to tape, you must
also change the MONTH199 JCL.
6. Use the ACTAUDRD macro in sharedprefix.MICS.MACAUTOS to
read in the ACTAUDIT, NEWAUDIT, and ACT6100 format audit
tapes.
7. A new, empty, generation of the complex-level audit tape
is created each month by the CLOSETBL job. The INVOICE
and FINRECAP jobs delete the most recent generation and
write ACTSDT01 and ACTSCT01 to a new generation. This
means that there will be gaps in the generation numbers.
These gaps do not affect either the number of generations
kept or the retention period.
8. In sharedprefix.MICS.PARMS(JCLDEFC), the ACCTMGDG
parameter determines whether audit files are maintained
at the complex level in the monthly generation data
group. If audit files are maintained, it determines how
many generations are maintained.
If, after installation, you want to start or stop
maintaining complex-level audit files or change the
number of generations maintained, follow these steps:
___ a. Edit the ACCTMGDG parameter value in
sharedprefix.MICS.PARMS(JCLDEFC). To turn off
the complex-level audit file, change the value to
zero. To change the number of generations
maintained in the monthly generation data group,
change the value to any numeric value other than
zero. If no ACCTMGDG parameter is specified, it
will default to a value of 85.
___ b. Regenerate the GDGSGENC job as follows for the
new parameter value to take effect.
- Edit sharedprefix.MICS.PARMS(JCLGENUC) so that
it contains the following line:
GDGSGENC
- Regenerate GDGSGENC by submitting JCLGENUC.
SUB 'sharedprefix.MICS.CNTL(JCLGENUC)'
___ c. Run GDGSGENC.
SUB 'sharedprefix.MICS.CNTL(GDGSGENC)'
9. In the JCL parameters at the complex or unit level, you
can optionally override individual TAPE parameter
specifications using accounting parameter statements that
apply to specific types of audit tape files. This
gives you the option to establish a common set of
defaults, which you override, as needed, for specific
tape applications.
The following are JCL parameters:
ACCTMTAPEPARM
The general form of the ACCTMTAPEPARM statement is the
keyword ACCTMTAPEPARM, followed by one or more
ACCTMTAPEPARM parameters. The ACCTMTAPEPARM parameters
are used to generate complex-level or unit-level
monthly audit jobs. The parameters include both
keyword parameters and keyword=value specifications.
You can specify the ACCTMTAPEPARM statement as many
times as you want in order to specify all of the tape
data set definitions you require. (This statement can
be used at the complex or unit level.)
ACCTMTAPESMSPARM
Optional parameter for specifying System Managed
Storage (SMS) keywords (e.g., STORCLAS=storclas) to be
used as the default for CA MICS tape data set
allocations. Specify one or more SMS parameters
according to JCL language syntax. There is no default
and continuation is not allowed. This statement is
used to generate monthly audit jobs at the complex or
unit level.
ACCTDTAPEPARM
The general form of the ACCTDTAPEPARM statement is the
keyword ACCTDTAPEPARM, followed by one or more
ACCTDTAPEPARM parameters. The ACCTDTAPEPARM parameters
are used to generate unit-level daily audit jobs. The
parameters include both keyword parameters and
keyword=value specifications. You can specify the
ACCTDTAPEPARM statement as many times as you want in
order to specify all of the tape data set definitions
you require.
ACCTDTAPESMSPARM
Optional parameter for specifying System Managed
Storage (SMS) keywords (e.g., STORCLAS=storclas) to be
used as the default for tape data set allocations.
Specify one or more SMS parameters according to JCL
language syntax. There is no default and continuation
is not allowed. This statement is used to generate
daily audit jobs at a unit level.
All keywords used on the TAPEPARM parameter can also
be used on the accounting tape specification parameters.
See the Planning, Installation, Operation, and Maintenance
Guide, Sections 2.3.1.6, 2.3.1.6.4, 2.3.3.2.1, and
2.3.3.2.1.5, for details.
Copyright © 2014 CA.
All rights reserved.
|
|