WEB DETAIL Tape Processing Overview
This article discusses the role of DETAIL Tape processing in the WEB analyzer and describes related statements.
micsrm140
This article also lists the procedures for activating and deactivating DETAIL Tape.
For certain high volume files, the
MICS
architecture enables you to create optional DETAIL timespan data sets. These optional data sets are separate from the normal MICS database
and have the following characteristics:- They are created during the component step execution: during either an incremental update or the DAILY update run. Each DETAIL tape file has a separate DD statement in the DAILY or incremental update job that specifies the data set name and other data set characteristics.
- The data set name (DSN) for each DETAIL tape in a component step is:tapeprefix.tmics.DETAIL.iiifff(+1)
tapeprefix
The tape prefix value that is specified with the TAPEPREFIX statement in
prefix.MICS.PARMS(JCLDEF).
tmics
Null when NOMICSLEVEL is specified, or MICS if MICSLEVEL is specified with the TAPEPREFIX statement in
prefix.MICS.PARMS(JCLDEF).
iii
The three character
MICS
information that is associated with the filefff
The three character
MICS
file identifierExample:
For the MICS Db2 Analyzer
, if DETAIL tape processing were activated for the DB2DSU file, the following prefix.MICS.PARMS(JCLDEF)
statement:TAPEPREFIX CPLXA.U1T NOMICSLEVEL
yields the following DETAIL tape DSN:
CPLXA.U1T.DETAIL.DB2DSU(+1)
- There is no cycle aging associated with these data sets. Instead, each DETAIL tape data set created is an 01 cycle (for example, DB2DSU01), and multiple instances are managed using Generation Data Groups (GDGs).
- The creation of DETAIL tape data sets is independent of anysharedprefix.MICS.GENLIBcustomization choices. You can have one or more cycles of a file that is written to and managed in the unit DETAIL timespan database, and also use the DETAIL tape feature to create independent data sets for that same file.
- The decision to create DETAIL tape data sets is made at the unit level. Choose to create DETAIL tape data sets for a component file in unit A, but not in unit B.
- While the expectation is that these files will be written to tape, you can make JCL choices to target other media such as DASD. The SAS sequential tape engine will be used to write these files for both DASD and tape data sets.
- Unique output exits are provided to permit manipulation and subsetting of the records that are written to the DETAIL tape data sets. This manipulation and subsetting, however, has no impact on files written to the standardMICS database.
The activation of DETAIL tape data sets is accomplished by specifying a TAPEfff statement in
prefix.MICS.PARMS(cccOPS)
.Customization of the JCL used to create each data set is accomplished using a cascading hierarchy of parameters beginning with choices made with the TAPEPARM statement in
prefix.PARMS(JCLDEF)
.WEB DETAIL Tape Supported Files
The
MICS
WEB Analyzer supports DETAIL tape processing for the following files:Overview of JCL Customization Parameters
The JCL for DETAIL tape data sets is constructed using tape-related parameters that are specified in
prefix.MICS.PARMS(JCLDEF)
and prefix.MICS.PARMS(cccOPS)
.Each DETAIL tape data set has a unique DD in the component step. The JCL for each DETAIL tape data set is customized according to user-specified JCL parameters such as the number of generation data group (GDG) entries that are maintained, unit names, volume count, retention, and expiration dates, and System Managed Storage (SMS) keywords. For example, STORCLAS=storclas.
MICS
provides a hierarchical means to specify tape-related JCL parameters suitable for each data center.The hierarchy, as it applies to DETAIL tape specification, is described:
Unit Level - TAPEPARM and TAPESMSPARM
Used for all tape data sets created by all components in the unit. Specified in
prefix.MICS.PARMS(JCLDEF)
Unit DETAIL Tape Level - DETAILTAPEPARM and DETAILTAPESMSPARM
Used for all DETAIL tape data sets created by all components in the unit. Overrides the choices that were made in TAPEPARM and TAPESMSPARM.
Specified in
prefix.MICS.PARMS(JCLDEF)
.Component Level - DETAILTAPEPARM and DETAILTAPESMSPARM
Used for all DETAIL tape data sets created by a particular component. Overrides all choices that were made in JCLDEF. Specified in
prefix.MICS.PARMS(cccOPS)
, where ccc represents the component.File Level - TAPEfff and TAPEfffSMS
Used for a particular DETAIL tape data set.
fff
Identifies the specific DETAIL file. Overrides all choices that were made in JCLDEF and the choices that were made with DETAILTAPEPARM and DETAILTAPESMSPARM in prefix.MICS.PARMS(cccOPS). Specified in prefix.MICS.PARMS(cccOPS), where ccc represents the component.
The JCL parameter specification hierarchy that is used for DETAIL tape customization is shown graphically in the following diagram:
DETAIL Tape JCL Parameter Hierarchy
+---------------------------+ | prefix.MICS.PARMS(JCLDEF) | +---------------------------+ | | | +----------------+ | | | TAPEPARM |----------> Defaults for all tape | | TAPESMSPARM | | data sets in unit | +-------+--------+ | | | | | +--+ | | | | | V | Defaults for all | +-------+---------+ | DETAIL tape data sets | | DETAILTAPEPARM |------> in unit. Overrides | |DETAILTAPESMSPARM| | TAPEPARM and | +-------+---------+ | TAPESMSPARM choices. | | | +------------|--------------+ | | V +---------------------------+ | prefix.MICS.PARMS(cccOPS) | +---------------------------+ | | Defaults for all | +-----------------+ | DETAIL tape data sets | | DETAILTAPEPARM |---------> for the component. | |DETAILTAPESMSPARM| | Overrides all choices | +-----------------+ | made in (JCLDEF). | | | | +--+ | | | | | V | Individual data set | +-------+--------+ | choices for one file | | TAPEfff |-------> (fff). Overrides | | TAPEfffSMS | | all other tape | +----------------+ | specifications. | | +---------------------------+ | V // DD statements and GDG generation
TAPEfff Statement
The TAPEfff statement is used to:
- Activate DETAIL tape data set creation for the file indicated by fff. The component files that are eligible for DETAIL tape processing are listed in a previous section.
- Override, for the indicated file, any JCL-related tape specifications that were made inprefix.MICS.PARMS(JCLDEF)andprefix.MICS.PARMS(cccOPS)with TAPEPARM or DETAILTAPEPARM statements.
The syntax is as follows:
TAPEfff <optional parameters>
fff
The unique 3-character file identifier
The optional parameters include both keyword parameters and keyword=value specifications. You can include multiple TAPEfff statements if required to specify the desired optional parameters. If you specify a parameter multiple times, the last instance defines the value in effect.
You can specify as many parameters as you want on each statement, but each TAPEfff statement must end by column 72. You have the option to specify only one parameter per TAPEfff statement. Either approach is acceptable.
The following are the optional parameters that are available for the TAPEfff statement:
TAPEfff GDG=nnn UNIT=unitname VOLCOUNT=n TAPEfff EXPDT=expdt / RETPD=nnn / NOEXPDT TAPEfff COMP/NOCOMP TAPEfff STACK/NOSTACK AFF/NOAFF TAPEfff MODEL='modeldsn' / MODEL=NOMODEL TAPEfff DISK / TAPE SPACE=spacedef TAPEfff VOLSER=volser
The following is a sample TAPEfff statement:
TAPEfff GDG=3 VOLCOUNT=7
In this sample, only the number of generation data groups (GDGs) and VOLCOUNT parameters are explicitly specified for the file fff. All other JCL-related parameters for the data set are set according to specifications made with TAPEPARM and DETAILTAPEPARM statements according to the hierarchy described in a previous section.
The optional parameters for the TAPEfff statement are identical to the parameters that are supported by the DETAILTAPEPARM statement. A detailed description of the optional parameters is presented immediately following the DETAILTAPEPARM statement description.
DETAILTAPEPARM Statement
In
prefix.MICS.PARMS(cccOPS)
, the optional DETAILTAPEPARM statement is used to specify parameters defining processing options for MICS
DETAIL tape data sets at the component (ccc) level.When specified in
prefix.MICS.PARMS(cccOPS)
, the DETAILTAPEPARM parameter specifications override unit level tape data set defaults that are established by TAPEPARM and DETAILTAPEPARM statements in prefix.MICS.PARMS(JCLDEF)
.For unit level TAPEPARM and DETAILTAPEPARM statements in prefix.MICS.PARMS(JCLDEF), see Installing.
The primary reason to include a DETAILTAPEPARM statement in
prefix.MICS.PARMS(cccOPS)
is to specify unique parameters for the DETAIL tapes that are created for a particular component (ccc).For example, your site can direct the
MICS
DETAIL tapes for a particular component (ccc) to a unique tape volume pool, or to a tape device type such as a virtual tape unit, or to a DASD pool backed by an archive facility. If so, you can accomplish this by including the appropriate DETAILTAPEPARM statements in prefix.MICS.PARMS(cccOPS)
.DETAILTAPEPARM <parameters>
Note:
In prefix.MICS.PARMS(cccOPS)
, all DETAILTAPEPARM statements must precede any TAPEfff or TAPEfffSMS statements.The general form of the DETAILTAPEPARM statement is the keyword DETAILTAPEPARM, followed by one or more DETAILTAPEPARM parameters. The DETAILTAPEPARM parameters include both keyword parameters and keyword=value specifications. You can specify the DETAILTAPEPARM statement as many times as you want to specify all of the tape data set definitions that you require. If you specify a parameter multiple times, the last instance defines the value in effect.
The following examples summarize the DETAILTAPEPARM parameters and describe them in detail.
Note:
While the following syntax sample shows only one or two parameters per statement (line), you can specify as many parameters as you want on each statement (limited only by the 72-character maximum line length).DETAILTAPEPARM GDG=nnn UNIT=unitname VOLCOUNT=n DETAILTAPEPARM EXPDT=expdt / RETPD=nnn / NOEXPDT DETAILTAPEPARM COMP/NOCOMP DETAILTAPEPARM STACK/NOSTACK AFF/NOAFF DETAILTAPEPARM MODEL='modeldsn' / MODEL=NOMODEL DETAILTAPEPARM DISK / TAPE SPACE=spacedef DETAILTAPEPARM VOLSER=volser
The following is a sample DETAILTAPEPARM statement:
DETAILTAPEPARM GDG=3 VOLCOUNT=7
In this example, the default parameter values are used for most of the DETAILTAPEPARM parameters.
The following definitions describe each of the DETAILTAPEPARM parameters:
GDG=nnn
Defaults to 7.
The number of entries to be created in the GDG for each DETAIL tape data set.
Overrides the TAPEPARM statement GDG=nnn.
UNIT=unitname
Defaults to the value specified on the TAPEPARM statement or to UNIT=3490 if UNIT=unitname is not specified on the TAPEPARM statement.
The generic unit name for tape file allocation. The parameter value (unitname) must be a valid 1 through 8 character generic unit name for your installation. The value is used in generated tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is non-blank and no more than 8 characters in length.
Overrides the TAPEPARM statement UNIT=unitname Value, the old-style TAPEUNIT statement, or both.
VOLCOUNT=n
Defaults to the value specified on the TAPEPARM statement. If no VOLCOUNT is specified, the z/OS default volume count of 5 applies.
The volume count JCL parameter for
MICS
tape data sets. Specify a decimal number from 1 to 255.
Overrides the TAPEPARM statement VOLCOUNT=nnn parameter or the old-style VOLCOUNT statement.
EXPDT=expdt
Defaults to the value specified on the TAPEPARM statement. If no expiration date or retention period is specified, a default retention period that equals the GDG=nnn value is used.
Specify an expiration date definition that replaces the derived default retention period (RETPD) specifications. This facility is specifically intended for use by installations with tape management systems which require specific EXPDT definitions.
For some tape management systems, certain EXPDT values make the tape available for scratching immediately. Such values are NOT suitable for
MICS
tapes. The EXPDT=expdt parameter is optional. If the parameter is omitted, MICS
derives a RETPD=nnn specification as appropriate for the specific MICS
tape data set being created and the number of GDG entries defined.Overrides the TAPEPARM statement EXPDT=expdt or NOEXPDT parameter, or the old-style EXPDT statement.
Note:
The EXPDT=expdt, RETPD=nnn, and NOEXPDT parameters are mutually exclusive.NOEXPDT
Defaults to the value specified on the TAPEPARM statement.
Specify NOEXPDT if you want
MICS
to omit both the EXPDT=date and RETPD=days JCL parameters from generated JCL statements for new tape data set creation. This option is provided for those installations where the tape management system or SMS specifications automatically control tape expiration dates, retention periods, or both.
Overrides the TAPEPARM statement EXPDT=expdt or NOEXPDT parameters, or the old-style EXPDT statement.
Note:
The NOEXPDT, EXPDT=expdt, and RETPD=nnn parameters are mutually exclusive.COMP / NOCOMP
Defaults to the value specified on the TAPEPARM statement. If COMP or NOCOMP is not specified, the z/OS default for the selected tape unit type applies.
This parameter specifies data compaction (COMP) or no data compaction (NOCOMP) for a tape device that is enabled for hardware compaction. Data compaction is only supported for IBM standard labels. If specified, the value is coded in the TRTCH subparameter of the DCB JCL parameter. If the value is not specified, no TRTCH subparameter is generated.
Overrides the TAPEPARM statement COMP/NOCOMP parameter or the old-style IDRC statement.
STACK / NOSTACK
Defaults to NOSTACK for DETAIL tapes.
Specify STACK to place multiple
MICS
tape files on a single tape volume. This mode of operation uses a minimum number of tape volumes and tape mounts are minimized. The MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).
Specify NOSTACK (the default) to place exactly one
MICS
tape file on a tape volume. With this option, the generated MICS
JCL statements do NOT contain the VOL=REF=ddname construct. This option is useful if your implementation of a virtual tape system prohibits "stacked" tape volumes, or if you are directing MICS
tape files to a DASD pool backed with an archival facility.
Overrides the TAPEPARM statement STACK/NOSTACK parameter.
AFF / NOAFF
Defaults to the value specified on the TAPEPARM statement or to AFF.
Specify AFF to use a single tape unit for all related tape files. This is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized. The
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.
Specify NOAFF to enable allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements will NOT contain the UNIT=AFF=ddname construct. This option is useful with certain virtual tape system implementations, or where you are directing MICS
tape files to a DASD pool backed with an archival facility.
Note:
If you specify NOAFF, then NOSTACK is automatically set.Overrides the TAPEPARM statement AFF/NOAFF parameter.
MODEL='modeldsn' / MODEL=NOMODEL
Defaults to the value specified on the TAPEPARM statement.
The fully qualified name of a cataloged data set to be used when defining or extending GDG entries. Ensure that the data set DCB characteristics are LRECL=0 and BLKSIZE=0. Coding BLKSIZE=0 causes SAS to use the blocksize that is defined by the BLKSIZE(TAPE) option. BLKSIZE(TAPE) is defined in the configuration members that are referenced by the CONFIG DD statement. If this parameter is omitted, a
MICS
generation job allocates a default model GDG data set.
If NOMODEL is specified as the model dataset name, the use of the model dataset in the DCB specification is bypassed.
Overrides the TAPEPARM statement MODEL='modeldsn' parameter or the old-style SYSTEMMODEL statement.
DISK / TAPE
Defaults to TAPE.
Specify DISK if you want to write the dataset to a disk instead of a tape. Specify TAPE to write the dataset to a tape.
When you specify DISK, ensure that you have both a UNIT parameter with a generic unit name of a disk device and a SPACE parameter defining disk space. You can also define a VOLSER parameter to direct the data to a specific disk.
Overrides the TAPEPARM statement DISK/TAPE parameter.
SPACE=spacedef
No default.
Defines the space allocation parameter for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
Overrides the TAPEPARM statement SPACE= parameter.
VOLSER=volser
No default.
Defines the volume serial number of a disk for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
Overrides the TAPEPARM statement VOLSER= parameter.
DETAILTAPESMSPARM and TAPEfffSMS Statements
In
prefix.MICS.PARMS(cccOPS)
, the optional DETAILTAPESMSPARM and TAPEfffSMS statements allow you to specify System Managed Storage (SMS) keywords (for example, STORCLAS=storclass) for DETAIL tape data sets at the component and individual file level, respectively.DETAILTAPESMSPARM
When specified in
prefix.MICS.PARMS(cccOPS)
, the DETAILTAPESMSPARM parameter specifications override unit level tape data set SMS defaults that are established by TAPESMSPARM and DETAILTAPESMSPARM statements in prefix.MICS.PARMS(JCLDEF)
.For more information about unit level TAPESMSPARM and DETAILTAPESMSPARM statements in
prefix.MICS.PARMS(JCLDEF),
see Installing.The primary reason to include a DETAILTAPESMSPARM statement in
prefix.MICS.PARMS(cccOPS)
is to specify unique SMS parameters for the DETAIL tapes that are created for a particular component (ccc).For example, your site can direct the
MICS
DETAIL tapes for a particular component (ccc) to a unique storage class.
Sample DETAILTAPESMSPARM statement:
DETAILTAPESMSPARM STORCLAS=DTPCLASS
In this example, the JCL for all DETAIL tape data sets for the component will include the SMS STORCLAS=DTPCLASS assignment.
TAPEfffSMS
The TAPEfffSMS statement is only permitted in
prefix.MICS.PARMS(cccOPS)
. It is not supported in prefix.MICS.PARMS(JCLDEF)
. TAPEfffSMS keyword specifications override, for the indicated file, any SMS-related tape specifications that are made in prefix.MICS.PARMS(JCLDEF)
and prefix.MICS.PARMS(cccOPS)
with TAPESMSPARM or DETAILTAPESMSPARM statements.The primary reason to include a TAPEfffSMS statement in
prefix.MICS.PARMS(cccOPS)
is to specify the unique SMS parameters for a specific DETAIL tape file (fff).
Sample TAPEfffSMS statement:
TAPEfffSMS STORCLAS=fffCLASS
In this example, the JCL for the DETAIL tape data set for file ffft includes the SMS STORCLAS=fffCLASS assignment.
DETAIL Tape User Exits
A user exit is invoked just befre the output of each record to a DETAIL tape file. The exits are named _USRTfff, where fff matches the file identifier for the DETAIL tape file.
For more information about a complete description of the DETAIL tape user exits, WEB Modifying.
Activating DETAIL Tape Checklist
To activate the DETAIL tape checklist, follow these steps:
- Add or modify the desired TAPEfff and TAPEfffSMS statements inprefix.MICS.PARMS(cccOPS).
- fff
- The three-character file identifier for the file to be written to tape
- Submitprefix.MICS.CNTL(cccPGEN).
- Editprefix.MICS.PARMS(JCLGENU)so that it reads:cccGDGGN DAILYIf Incremental Update is active, add the following:INCRccc
- Submitprefix.MICS.CNTL(JCLGENU)to regenerate the JCL for DAILY and cccGDGGN.Note:If you want to use specific JCL and SMS parameter values for your DETAIL tape data sets, ensure that you coded the appropriate DETAILTAPEPARM or DETAILTAPESMSPARM statements inprefix.MICS.PARMS(JCLDEF)for unit level, orprefix.MICS.PARMS(cccOPS)for component level DETAIL tape JCL parameters. See the previous sections for details about JCL parameters available for DETAIL tape data sets.
- Submitprefix.MICS.CNTL(cccGDGGN)to define the tape GDG.Note:If you want to override the number of entries that are kept in a GDG with cataloged data sets for a TAPEfff file, you must delete and redefine the index with the new limit for GDG entries. Follow the checklist in the Generation Data Group Catalog Index Creation section in Generate and Allocate the Database.You have just activated DETAIL tape for one or more database files.
As mentioned in the DETAIL Tape Processing Overview section, the choice to create DETAIL tape files is independent of, and does not affect the creation of DETAIL files in the unit database.
When you create one or more cycles of the files that you activated for DETAIL tape in your unit
prefix.MICS.DETAIL
timespan, your DAILY update job will continue to do so.As you create DETAIL tape cycles for the files, you can deactivate or limit the number of DETAIL cycles written to the unit DETAIL timespan database.
System Modification contains instructions to change the number of cycles of a file and instructions to deactivate the DETAIL timespan of a file.
If you deactivate the files in the DETAIL timespan, ensure that you delete the existing cycles to free up space in the
prefix.MICS.DETAIL
database. If you reduce the number of cycles, ensure that you delete any existing cycles in prefix.MICS.DETAIL
beyond the new cycle limit.The following JCL can be used to delete specific cycles of a file from the DETAIL timespan. Ensure that you replace 'x' with the unit identifier:
- Delete all cycles for file fff (01-nn)//DELETE EXEC MICSDBx //SYSIN DD * PROC DATASETS DDNAME=%DDNx(TS=DETAIL); DELETE cccfff01 cccfff02 ... cccfffnn ; RUN;
- Delete cycles 02, 03, and 04 for file fff://DELETE EXEC MICSDBx //SYSIN DD * PROC DATASETS DDNAME=%DDNx(TS=DETAIL); DELETE cccfff02 cccfff03 cccfff04 ; RUN;
Deactivating DETAIL Tape Checklist
- Delete the desired TAPEfff and TAPEfffSMS statements from prefix.MICS.PARMS(cccOPS).
- If there are no longer any TAPEfff statements in prefix.MICS.PARMS(cccOPS), delete any DETAILTAPEPARM and DETAILTAPESMSPARM statements.
- Submit prefix.MICS.CNTL(cccPGEN).
- Edit prefix.MICS.PARMS(JCLGENU) so that it reads:DAILYIf Incremental Update is active, add this:INCRccc
- Submit prefix.MICS.CNTL(JCLGENU) to regenerate the JCL for the DAILY job.
- (Optional) Delete the index and the cataloged datasets for each TAPEfff statement deleted in step.