Database Unit Tape Specifications
Tape specifications let you control the number of generation data group entries maintained for backup and archive tape files, unit names, volume count, and retention and expiration dates.
mics142
Tape specifications let you control the number of generation data group entries maintained for backup and archive tape files, unit names, volume count, and retention and expiration dates.
The following statements are described on this page:
The accounting daily, accounting monthly, backup, monthly backup, archive audit, archive history, and DETAIL tape processes all use generation data groups.
- The accounting processes are described in the Using Accounting and Chargeback.
- The backup process is described in BACKUP Operational Job.
- The monthly backup process is described in MONTHLY Operational Job.
- The two database archive processes, audit and history, are described in TheMICSAudit Archive Tape and TheMICSHistory Archive Tapes and Database Structure and Organization.
- The DETAIL tape process is described in the relevant product analyzers.
- These processes use the data set names that are itemized in Data Set Names.
The numbers that are specified for the GDG=nnn parameters on the AUDITPARM, BKUPPARM, HISTMPARM, HISTWPARM, and MBKUPPARM statements (or on the older ACCTDGDG, AUDITGDG, BCKUPGDG, HISTWGDG, and HISTMGDG statements) serve two purposes.
- The numbers define the number of entries in the respective GDG (BLDG ENTRIES=n).
- The numbers, when multiplied by the specified retention factor, provide the default JCL LABEL retention period (RETPD=days) that is used in creating the respective GDG files. For example, the AUDITGDG files are created weekly. Therefore, the retention period that is specified byMICSis the number of GDG entries you specify multiplied by 7 (days). However, any value that is specified in the EXPDT=expdt parameter overrides the calculated RETPD.
ACCTDGDG
(Optional) Only required when installing the Accounting and Chargeback Option, otherwise, this parameter is ignored if specified. This parameter specifies the number of generations of daily audit files that are maintained in the daily generation data group. The default value is 3, and the allowable range is 1 through 999.
TAPEPARM
To specify parameters that define default processing options for
MICS
tape data sets, use the TAPEPARM statement. To consolidate tape data set definitions into a single, easy-to-locate statement, the TAPEPARM statement overrides and replaces many of the individual tape data set statements. The individual old-style statements that are replaced are noted in the detailed descriptions of the TAPEPARM parameters that follow.You can, override individual TAPEPARM parameter specifications using statements that apply to specific types of
MICS
tape data sets, such as the MICS
backup, monthly backup, and archive tape files. As a result, you have the option of establishing a common set of defaults that you override, as required, for specific tape applications.The general form of the TAPEPARM statement is the keyword TAPEPARM followed by one or more TAPEPARM parameters. TAPEPARM parameters include both keyword parameters and keyword=value specifications. To specify all the tape data set definitions that you require, use the TAPEPARM statement as many times as needed. 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). You can also specify only one parameter per line. Either approach is acceptable.
TAPEPARM UNIT=unitname VOLCOUNT=n TAPEPARM EXPDT=expdt / NOEXPDT TAPEPARM COMP/NOCOMP TAPEPARM NULLUNIT=unitname NULLSER=nulser TAPEPARM STACK/NOSTACK AFF/NOAFF TAPEPARM MODEL='modeldsn' / MODEL=NOMODEL TAPEPARM DISK / TAPE SPACE=spacedef TAPEPARM VOLSER=volser
A sample TAPEPARM specification follows:
TAPEPARM UNIT=CART VOLCOUNT=10 EXPDT=1999/000 COMP TAPEPARM NULLUNIT=CART NULLSER=123456 TAPEPARM MODEL='CPM981.CMN.MICS.MODEL'
The TAPEPARM parameters detail descriptions follow:
UNIT=unitname
Defaults to UNIT=3490.
The generic unit name for tape file allocation. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating a tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and character length is one through eight in length.This parameter replaces and overrides the old-style TAPEUNIT statement.
Note:
The ASIS subparameter is not required when using the TAPEPARM statement UNIT parameter.VOLCOUNT=n
No default. 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.This parameter replaces and overrides the old-style VOLCOUNT statement.
EXPDT=expdt
No default. If no expiration date is specified, a default retention period is derived as appropriate for the specific
MICS
tape data set being created and the number of GDG entries defined.Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.
This parameter replaces and overrides the old-style EXPDT statement.
Note:
The EXPDT=expdt and NOEXPDT parameters are mutually exclusive.NOEXPDT
To omit both the EXPDT=date and RETPD=days JCL parameters from generated JCL statements for new tape data set creation, specify NOEXPDT. This option is provided for those installations where the tape management system or SMS specifications automatically control tape expiration dates, retention periods, or both.
This parameter replaces and overrides the old-style EXPDT statement.
Note:
The NOEXPDT and EXPDT=expdt parameters are mutually exclusive.COMP / NOCOMP
No default. 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. The TRTCH subparameter must be specified to generate.
This parameter replaces and overrides the old-style IDRC statement.
NULLUNIT=unitname
Defaults to the tape unit value (UNIT=unitname).
The generic unit name to be used for allocation of the NULLSER tape volume. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and the character form one through eight in length.This parameter replaces and overrides the old-style NULLUNIT statement.
NULLSER=nulser
Defaults to NULSER.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run.This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements.If a virtual tape subsystem (VTS) is used at your site for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, as well as a MOUNT from being issued by z/OS. This is imperative for JES3 customers with an ATL or VTS because the MICS operational job will not continue until the mount is satisfied.
NULLSER also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
After choosing the volume, for example, 123456, it is important to adjust and submit the following job in order to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter replaces and overrides the old-style NULLSER statement.
STACK / NOSTACK
Defaults to STACK.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. STACK is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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.AFF / NOAFF
Defaults to AFF.
Specify AFF to use a single tape unit for all related tape files. This action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.MODEL='modeldsn' / MODEL=NOMODEL
No default.
The fully qualified name of a cataloged data set to be used when defining or extending GDG entries. Ensure that the data set's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter replaces and overrides the old-style SYSTEMMODEL statement.
Note:
The MODEL='modeldsn' and MODEL=NOMODEL parameters are mutually exclusive.DISK / TAPE
Defaults to TAPE.Specify DISK if you want to write the data set to a disk instead of a tape. Specify TAPE to write the data set 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.
SPACE=spacedef
No default.
This parameter defines the space allocation parameter for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
VOLSER=volser
No default.This parameter 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.
TAPESMSPARM
Optional parameter for specifying System Managed Storage (SMS) keywords (for example, STORCLAS=storclas) to be used as the default for
MICS
tape data set allocations. Specify one or more SMS parameters according to JCL language syntax. No default. Continuation is not allowed.ACCTDTAPEPARM
Use the optional ACCTDTAPEPARM statement to specify parameters defining processing options for Accounting and Chargeback Daily Audit tape data sets. When using the Daily Audit tapes, ACCTDTAPEPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM statement.
The primary reason to specify the ACCTDTAPEPARM statement is to override the default number of daily Audit data group entries to be defined (the GDG= parameter). However, your site can direct the Accounting and Chargeback Daily Audit to a unique tape volume pool, or to a tape device type such as a virtual tape unit.
The ACCTDTAPEPARM statement allows the BLKSIZE= specification to support overriding the default BLKSIZE used for the Accounting and Chargeback Daily Audit tape files. The BLKSIZE parameter enables use of the large block interface. Use caution in defining this parameter as the blksize value
must
be compatible with your tape device or an abend occurs.Note:
Directing the Daily Audit data set to disk with the TAPEPARM DISK parameter is not supported.The general form of the ACCTDTAPEPARM statement is the keyword ACCTDTAPEPARM followed by one or more ACCTDTAPEPARM parameters. ACCTDTAPEPARM parameters include both keyword parameters and keyword=value specifications. You can specify the ACCTDTAPEPARM 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.
An ACCTDTAPEPARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.ACCTDTAPEPARM GDG=nnn UNIT=unitname VOLCOUNT=n ACCTDTAPEPARM EXPDT=expdt / RETPD=nnn / NOEXPDT ACCTDTAPEPARM COMP/NOCOMP ACCTDTAPEPARM NULLUNIT=unitname NULLSER=nulser ACCTDTAPEPARM STACK/NOSTACK AFF/NOAFF ACCTDTAPEPARM MODEL='modeldsn' / MODEL=NOMODEL ACCTDTAPEPARM BLKSIZE=nnnnnn
A sample ACCTDTAPEPARM statement follows:
ACCTDTAPEPARM GDG=3 VOLCOUNT=7
In this example, the TAPEPARM parameter values are used for most of the ACCTDTAPEPARM parameters.
ACCTDTAPEPARM parameters follow:
GDG=3
Defaults to 3.
The number of entries to be created in the GDG for each Accounting and Chargeback Daily Audit data set.
This parameter overrides and replaces the ACCTDGDG statement.
BLKSIZE
Defaults to 32004.
This parameter overrides the default block size that is used for the Accounting and Chargeback Daily Audit tape data set. This action is useful when you want to take advantage of the z/OS large block interface.
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 one through eight character generic unit name for your installation. The value is used in generating a tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and the character form one through eight 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, then 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.
This parameter 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 is derived based on the GDG=nnn value.
Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.
This parameter 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. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
NOEXPDT is specified when 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.This parameter 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 are not specified, then 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. The TRTCH subparameter must be specified to generate.
This parameter overrides the TAPEPARM statement COMP/NOCOMP parameter or the old-style IDRC statement.
NULLUNIT=unitname
Defaults to the value specified on the TAPEPARM statement or to the tape unit value.
The generic unit name that is used for the allocation of the NULLSER tape volume. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used generating tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter overrides the TAPEPARM statement NULLUNIT=unitname parameter or the old-style NULLUNIT statement.
NULLSER=nulser
Defaults to the value specified on the TAPEPARM statement or to the old-style NULLSER statement.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run. This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements.If a virtual tape subsystem (VTS) is used at your sites for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This action prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, and a MOUNT issued by z/OS. This action is imperative for JES3 customers with an ATL or VTS because the MICS operational job does not continue until the mount is satisfied.
NULLSER also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
For example, after choosing the volume123456, it is important to adjust and submit the following job to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and you let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter overrides the TAPEPARM statement NULLSER=nulser parameter.
STACK / NOSTACK
Defaults to the value specified on the TAPEPARM statement or to STACK.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. This action is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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.This parameter 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 action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.This parameter 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's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter overrides the TAPEPARM statement MODEL='modeldsn' parameter or the old-style SYSTEMMODEL statement.
ACCTDTAPESMSPARM
Defaults to the values specified on the TAPESMSPARM statement.
Optional parameter for specifying System Managed Storage (SMS) keywords for Accounting and Chargeback Daily Audit data set allocations. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.
This parameter overrides the TAPESMSPARM statement.
ACCTDAY1PARM
Use the optional ACCTDAY1PARM statement to specify parameters defining processing options for the Accounting and Chargeback DAY1 Audit data sets. When using the Daily Audit data sets, ACCTDAY1PARM parameter specifications override the data set defaults that are established by the ACCTDTAPEPARM statement.
The primary reason to specify the ACCTDAY1PARM statement is to override the default writing of the Accounting and Chargeback Daily Audit data sets to tape. With the ACCTDAY1PARM statement, the Accounting and Chargeback Daily Audit data set can be directed to a disk device.
The ACCTDAY1PARM statement allows the BLKSIZE= specification to support overriding the default BLKSIZE used for the Accounting and Chargeback Daily Audit tape files. The BLKSIZE parameter enables use of the large block interface. Use caution in defining this parameter as the blksize value must be compatible with your tape device or an abend occurs. BLKSIZE is only supported for tape data sets.
The general form of the ACCTDAY1PARM statement is the keyword ACCTDAY1PARM followed by one or more ACCTDAY1PARM parameters. ACCTDAY1PARM parameters include both keyword parameters and keyword=value specifications. Specify the ACCTDAY1PARM 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.
An ACCTDAY1PARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.ACCTDAY1PARM DISK SPACE=spacedef ACCTDAY1PARM UNIT=unitname VOLSER=volser
Samples of ACCTDAY1PARM statement follow:
ACCTDAY1PARM BLKSIZE=64K ACCTDAY1PARM DISK SPACE=(CYL,(20,10)) UNIT=SYSDA
An description of each of the ACCTDAY1PARM parameters follows:
BLKSIZE
Defaults to 32004.
Overrides the default block size that is used for the Accounting and Chargeback Daily Audit tape data set. This action is useful when you want to take advantage of the z/OS large block interface. BLKSIZE is only supported for tape data sets.
DISK
Required if you want the Accounting and Chargeback DAY1 Audit data set that is written to a disk device. If not specified, the data set is written to tape and other parameters on the ACCTDAY1PARM statement have no effect.
SPACE=spacedef
Default: No SPACE parameter specified.
This parameter defines the space allocation parameter for the Accounting and Chargeback DAY1 Audit data set on disk. Specify this parameter according to JCL language syntax.
UNIT=unitname
Default: No UNIT parameter specified.
The generic unit name to be used for the Accounting and Chargeback DAY1 Audit data set on disk. Specify this parameter according to JCL language syntax.
VOLSER=volser
Default: No VOLSER parameter specified.
This parameter defines the VOLSER parameter if you want the Accounting and Chargeback DAY1 Audit data set that is written onto a specific disk. Specify this parameter according to JCL language syntax.
ACCTDAY1SMSPARM
Optional parameter for specifying System Managed Storage (SMS) keywords for Accounting and Chargeback DAY1 Audit data set allocations on disk. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.
The parameters on this statement are effective only when the DISK parameter on the ACCTDAY1PARM statement is specified.
ACCTDAY2PARM
Use the optional ACCTDAY2PARM statement to specify parameters defining processing options for the Accounting and Chargeback DAY2 Audit data sets. When using the Daily Audit data sets, ACCTDAY2PARM parameter specifications override the data set defaults that are established by the ACCTDTAPEPARM statement.
The primary reason to specify the ACCTDAY2PARM statement is to override the default writing of the Accounting and Chargeback Daily Audit data sets to tape. With the ACCTDAY2PARM statement, the Accounting and Chargeback Daily Audit data set can be directed to a disk device.
The ACCTDAY2PARM statement allows the BLKSIZE= specification to support overriding the default BLKSIZE used for the Accounting and Chargeback Daily Audit tape files. The BLKSIZE parameter enables use of the large block interface. Use caution in defining this parameter as the blksize value must be compatible with your tape device or an abend occurs. BLKSIZE is only supported for tape data sets.
The general form of the ACCTDAY2PARM statement is the keyword ACCTDAY2PARM followed by one or more ACCTDAY2PARM parameters. ACCTDAY2PARM parameters include both keyword parameters and keyword=value specifications. You can specify the ACCTDAY2PARM 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.
An ACCTDAY2PARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.ACCTDAY2PARM DISK SPACE=spacedef ACCTDAY2PARM UNIT=unitname VOLSER=volser
Samples of ACCTDAY2PARM statements follow:
ACCTDAY2PARM BLKSIZE=64K ACCTDAY2PARM DISK SPACE=(CYL,(20,10)) UNIT=SYSDA
An description of each of the ACCTDAY2PARM parameters follows:
BLKSIZE
Defaults to 32004.
Overrides the default block size that is used for the Accounting and Chargeback Daily Audit tape data set. This action is useful when you want to take advantage of the z/OS large block interface. BLKSIZE is only supported for tape data sets.
DISK
Required if you want the Accounting and Chargeback DAY2 Audit data set that is written to a disk device. If not specified, the data set is written to tape and other parameters on the ACCTDAY2PARM statement have no effect.
SPACE=spacedef
Default: No SPACE parameter specified.
This parameter defines the space allocation parameter for the Accounting and Chargeback DAY2 Audit data set on disk. Specify this parameter according to JCL language syntax.
UNIT=unitname
Default: No UNIT parameter specified
The generic unit name to be used for the Accounting and Chargeback DAY2 Audit data set on disk. Specify this parameter according to JCL language syntax.
VOLSER=volser
Default: No VOLSER parameter specified.
Define the VOLSER parameter if you want the Accounting and Chargeback DAY2 Audit data set that is written onto a specific disk. Specify this parameter according to JCL language syntax.
ACCTDAY2SMSPARM
Optional parameter for specifying System Managed Storage (SMS) keywords for Accounting and Chargeback DAY2 Audit data set allocations on disk. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.
The parameters on this statement are effective only when the DISK parameter on the ACCTDAY2PARM statement is specified.
ACCTMTAPEPARM
Use the optional ACCTMTAPEPARM statement to specify parameters defining processing options for Accounting and Chargeback Monthly Audit tape data sets. When using the Monthly Audit tapes, the ACCTMTAPEPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM statement.
The primary reason to specify the ACCTMTAPEPARM statement is to override the default number of monthly Audit generation data group entries to be defined (the GDG= parameter). However, your site may want to direct the Accounting and Chargeback Monthly Audit to a unique tape volume pool, or to a tape device type such as a virtual tape unit.
Note:
Directing the Monthly Audit data set to disk with the TAPEPARM DISK parameter is not supported.The general form of the ACCTMTAPEPARM statement is the keyword ACCTMTAPEPARM followed by one or more ACCTMTAPEPARM parameters. ACCTMTAPEPARM parameters include both keyword parameters and keyword=value specifications. Specify the ACCTMTAPEPARM 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.
An ACCTMTAPEPARM parameter summary follows:
- Each parameter is described in detail here.
- While the following sample shows only one or two parameters per statement (line), you can specify as many parameters as you want on each statement. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.ACCTMTAPEPARM GDG=nnn UNIT=unitname VOLCOUNT=n ACCTMTAPEPARM EXPDT=expdt / NOEXPDT ACCTMTAPEPARM COMP/NOCOMP ACCTMTAPEPARM NULLUNIT=unitname NULLSER=nulser ACCTMTAPEPARM STACK/NOSTACK AFF/NOAFF ACCTMTAPEPARM MODEL='modeldsn' / MODEL=NOMODEL ACCTMTAPEPARM BLKSIZE=nnnnnn
A sample ACCTMTAPEPARM statement follows:
ACCTMTAPEPARM GDG=90 VOLCOUNT=7
In the previous example, the TAPEPARM parameter values are used for most of the ACCTMTAPEPARM parameters.
The ACCTMTAPEPARM parameters follow:
GDG=nnn
Defaults to 85.
The number of entries to be created in the GDG for each Accounting and Chargeback Monthly Audit data set.
This parameter overrides and replaces the ACCTMGDG statement.
BLKSIZE
Defaults to 32004.
This parameter overrides the default block size that is used for the Accounting and Chargeback Daily Audit tape data set. This action is useful when you want to take advantage of the z/OS large block interface.
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 one through eight 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 nonblank and one through eight characters in length.This parameter 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, then 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.This parameter 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 is derived based on the GDG=nnn value.
Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.
This parameter 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. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
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.This parameter 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, then 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. The TRTCH subparameter must be specified to generate.
This parameter overrides the TAPEPARM statement COMP/NOCOMP parameter or the old-style IDRC statement.
NULLUNIT=unitname
Defaults to the value specified on the TAPEPARM statement or to the tape unit value.
The generic unit name to be used for allocation of the NULLSER tape volume. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter overrides the TAPEPARM statement NULLUNIT=unitname parameter or the old-style NULLUNIT statement.
NULLSER=nulser
Defaults to the value specified on the TAPEPARM statement or to statement NULLSER.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run. This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements.If a virtual tape subsystem (VTS) is used at your site for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This action prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, and a MOUNT from being issued by z/OS. This is imperative for JES3 customers with an ATL or VTS because the MICS operational job will not continue until the mount is satisfied.
NULLSER also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
For example, after choosing the volume123456, it is important to adjust and submit the following job to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter overrides the TAPEPARM statement NULLSER=nulser parameter or the old-style NULLSER statement.
STACK / NOSTACK
Defaults to the value specified on the TAPEPARM statement or to STACK.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. This action is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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. You may find this option 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.This parameter 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 action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.This parameter 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's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter overrides the TAPEPARM statement MODEL='modeldsn' parameter or the old-style SYSTEMMODEL statement.
ACCTMTAPESMSPARM
Defaults to the values specified on the TAPESMSPARM statement.
Optional parameter for specifying System Managed Storage (SMS) keywords for Accounting and Chargeback Monthly Audit data set allocations. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.
This parameter overrides the TAPESMSPARM statement.
AUDITPARM
Use the optional AUDITPARM statement to specify parameters defining processing options for audit archive tape data sets. When using the audit archive tapes, the AUDITPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM statement.
The primary reason to specify the AUDITPARM statement is to override the default number of archive audit generation data group entries to be defined (the GDG= parameter). However, your site can direct the archive audit tapes to a unique tape volume pool, or to a tape device type such as a virtual tape unit, or to a DASD pool that is backed by an archive facility. The AUDITPARM statement gives you the flexibility to uniquely define tape data set parameters for archive audit tapes.
The general form of the AUDITPARM statement is the keyword AUDITPARM followed by one or more AUDITPARM parameters. AUDITPARM parameters include both keyword parameters and keyword=value specifications. You can specify the AUDITPARM 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.
An AUDITPARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.AUDITPARM GDG=nnn UNIT=unitname VOLCOUNT=n AUDITPARM EXPDT=expdt / RETPD=nnn / NOEXPDT AUDITPARM COMP/NOCOMP AUDITPARM NULLUNIT=unitname NULLSER=nulser AUDITPARM STACK/NOSTACK AFF/NOAFF AUDITPARM MODEL='modeldsn' / MODEL=NOMODEL AUDITPARM DISK / TAPE SPACE=spacedef AUDITPARM VOLSER=volser
A sample AUDITPARM statement follows:
AUDITPARM GDG=75 VOLCOUNT=6
In this example, the TAPEPARM parameter values are used for most of the AUDITPARM parameters.
AUDITPARM parameters follow:
GDG=nnn
Defaults to 53.
The number of entries to be created in the GDG for each archive audit data set. The number of entries control the number of weeks for which archive audit data is maintained for each
MICS
file. This process creates one tape of data per week, unless you have massive files.The recommended value is GDG=53. The calculated default retention period for these files is equal to the number of entries that are specified, multiplied by 7 (seven days per entry).
This parameter overrides and replaces the old-style AUDITGDG statement.
Note:
If you select to split audit archive processing out of the WEEKLY operational job and you perform the archive process in the stand-alone AUDIT operational job, specify this option:ARCHIVE AUDIT YES JOB
You can execute audit archive processing (the AUDIT job) and can audit more frequently if DASD space is inadequate for retaining sufficient DETAIL/DAYS cycles for weekly audit tape creation. For example, twice a week or daily.
In this case, it is necessary to increase the number of tape cycles (or GDG entries) retained to meet your requirements for "long-term" retention of audit tape data.
If you select this option, then add the following option to prefix.MICS.PARMS(EXECDEF)
USERDEF AUDITCWK YES
This parameter overrides the default audit archive processing, so that data for the current week is retained and copied to the new audit archive tape cycle.
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 nonblank and one through eight characters in length.This parameter 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, then 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.This parameter 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 is derived based on the GDG=nnn value.
Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.This parameter 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. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
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.This parameter 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, then 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. The TRTCH subparameter must be specified to generate.
This parameter overrides the TAPEPARM statement COMP/NOCOMP parameter or the old-style IDRC statement.
NULLUNIT=unitname
Defaults to the value specified on the TAPEPARM statement or to the tape unit value.
The generic unit name to be used for allocation of the NULLSER tape volume. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter overrides the TAPEPARM statement NULLUNIT=unitname parameter or the old-style NULLUNIT statement.
NULLSER=nulser
Defaults to the value specified on the TAPEPARM statement or to statement NULLSER.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run. This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements.If a virtual tape subsystem (VTS) is used at your sites for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This action prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, and a MOUNT issued by z/OS. This action is imperative for JES3 customers with an ATL or VTS because the MICS operational job does not continue until the mount is satisfied.
NULLSER also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
For example, after choosing the volume123456, it is important to adjust and submit the following job to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter overrides the TAPEPARM statement NULLSER=nulser parameter or the old-style NULLSER statement.
STACK / NOSTACK
Defaults to the value specified on the TAPEPARM statement or to STACK.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. This action is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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.This parameter 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 action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
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 do 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.This parameter 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's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter 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 data set to a disk instead of a tape. Specify TAPE to write the data set 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.
SPACE=spacedef
No default.
This parameter defines the space allocation parameter for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
VOLSER=volser
No default.
This parameter 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.
AUDITSMSPARM
Defaults to the values specified on the TAPESMSPARM statement.
Optional parameter for specifying System Managed Storage (SMS) keywords for archive audit tape data set allocations. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.
This parameter overrides the TAPESMSPARM statement.
BKUPPARM
Use the optional BKUPPARM statement to specify parameters defining processing options for
MICS
backup tape data sets. When using the backup tapes, the BKUPPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM statement.The primary reason to specify the BKUPPARM statement is to override the default number of backup generation data group entries to be defined (the GDG= parameter). However, your site can direct the
MICS
backup tapes 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. The BKUPPARM statement gives you the flexibility to uniquely define tape data set parameters for backup tapes.The general form of the BKUPPARM statement is the keyword BKUPPARM followed by one or more BKUPPARM parameters. BKUPPARM parameters include both keyword parameters and keyword=value specifications. You can specify the BKUPPARM 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.
A BKUPPARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.BKUPPARM GDG=nnn UNIT=unitname VOLCOUNT=n BKUPPARM EXPDT=expdt / RETPD=nnn / NOEXPDT BKUPPARM COMP/NOCOMP BKUPPARM NULLUNIT=unitname NULLSER=nulser BKUPPARM STACK/NOSTACK AFF/NOAFF BKUPPARM MODEL='modeldsn' / MODEL=NOMODEL BKUPPARM DISK / TAPE SPACE=spacedef BKUPPARM VOLSER=volser
The following is a sample BKUPPARM statement:
BKUPPARM GDG=10 VOLCOUNT=8
In this example, the TAPEPARM parameter values are used for most of the BKUPPARM parameters.
BKUPPARM parameters follow:
GDG=nnn
Defaults to 10.
The number of entries to be created in the GDG for each backup data set. The number of entries controls the number of days for which backup data is maintained for each
MICS
timespan. This process creates one tape of data per backup, unless you have massive files.The recommended value is GDG=10. The calculated default retention period for these files is derived from the number of entries that are specified and the BACKUP FREQ specification.
Overrides and replaces the old BCKUPGDG statement.
UNIT=unitname
This parameter 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 one through eight character generic unit name for your installation. The value is used in generating a tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter 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, then 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.This parameter 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 is derived based on the GDG=nnn value.
Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is 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, and, if 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.
This parameter 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. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
NOEXPDT is specified when 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.This parameter 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, then 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. The TRTCH subparameter must be specified to generate.
This parameter overrides the TAPEPARM statement COMP/NOCOMP parameter or the old-style IDRC statement.
NULLUNIT=unitname
Defaults to the value specified on the TAPEPARM statement or to the tape unit value.
The generic unit name to be used for allocation of the NULLSER tape volume. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter overrides the TAPEPARM statement NULLUNIT=unitname parameter or the old-style NULLUNIT statement.
NULLSER=nulser
Defaults to the value specified on the TAPEPARM statement or to the old-style NULLSER statement.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run. This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements.If a virtual tape subsystem (VTS) is used at your site for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This action prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, and a MOUNT issued by z/OS. This action is imperative for JES3 customers with an ATL or VTS because the MICS operational job does not continue until the mount is satisfied.
NULLSER also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
For example, after choosing the volume123456, it is important to adjust and submit the following job to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter overrides the TAPEPARM statement NULLSER=nulser parameter or the old-style NULLSER statement.
STACK / NOSTACK
Defaults to the value specified on the TAPEPARM statement or to STACK.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. This action is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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.This parameter 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 action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.This parameter 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's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter 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 data set to a disk instead of a tape. Specify TAPE to write the data set 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.
SPACE=spacedef
No default.
This parameter defines the space allocation parameter for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
VOLSER=volser
No default.
This parameter 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.
BKUPSMSPARM
Defaults to the values specified on the TAPESMSPARM statement.
Optional parameter for specifying System Managed Storage (SMS) keywords for
MICS
backup tape data set allocations. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.This parameter overrides the TAPESMSPARM statement.
MBKUPPARM
Use the optional MBKUPPARM statement to specify parameters defining processing options for
MICS
monthly backup tape data sets. When using the monthly backup tapes, the MBKUPPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM or BKUPPARM statements.The primary reason to specify the MBKUPPARM statement is to override the default number of archive audit generation data group entries to be defined (the GDG= parameter). However, your site can direct the
MICS
monthly backup tapes 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. The MBKUPPARM statement gives you the flexibility to uniquely define tape data set parameters for MICS
monthly backup tapes.The general form of the MBKUPPARM statement is the keyword MBKUPPARM followed by one or more MBKUPPARM parameters. MBKUPPARM parameters include both keyword parameters and keyword=value specifications. You can specify the MBKUPPARM 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.
An MBKUPPARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.MBKUPPARM GDG=nnn UNIT=unitname VOLCOUNT=n MBKUPPARM EXPDT=expdt / RETPD=nnn / NOEXPDT MBKUPPARM COMP/NOCOMP MBKUPPARM NULLUNIT=unitname NULLSER=nulser MBKUPPARM STACK/NOSTACK AFF/NOAFF MBKUPPARM MODEL='modeldsn' / MODEL=NOMODEL MBKUPPARM DISK / TAPE SPACE=spacedef MBKUPPARM VOLSER=volser
A sample MBKUPPARM statement follows:
MBKUPPARM GDG=6 VOLCOUNT=8
In this example, the TAPEPARM or BKUPPARM parameter values are used for most of the MBKUPPARM parameters.
MBKUPPARM parameters follow:
GDG=nnn
Defaults to 6.
The number of entries to be created in the GDG for each monthly backup data set. The number of entries control the number of months for which monthly backup data is maintained for each
MICS
timespan. This process creates one tape of data per month, unless you have massive files.The recommended value is GDG=6. The calculated default retention period for these files is equal to the number of entries that are specified, multiplied by 31 (31 days per entry).
This parameter overrides and replaces the previously hard-coded default value of 6.
UNIT=unitname
Defaults to the BKUPPARM specification or other default.
The generic unit name for tape file allocation. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating a tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter overrides the BKUPPARM specification or the default.
VOLCOUNT=n
Defaults to the BKUPPARM specification or other default.
The volume count JCL parameter for
MICS
tape data sets. Specify a decimal number from 1 to 255.This parameter overrides the BKUPPARM specification or the default.
EXPDT=expdt
Defaults to the BKUPPARM specification. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.
This parameter overrides the BKUPPARM specification.
Note:
The EXPDT=expdt, RETPD=nnn, and NOEXPDT parameters are mutually exclusive.RETPD=nnn
Defaults to the BKUPPARM specification. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
Specify a fixed retention period definition which replaces the derived default retention period (RETPD) specification. This facility is intended for use by installations with tape management systems which require specific RETPD definitions.
Note:
For some tape management systems, certain RETPD values make the tape available for scratching immediately. Such values are not
suitable for MICS
tapes.The RETPD=nnn parameter is optional, and, if omitted,
MICS
derives a default RETPD=nnn specification as appropriate for the specific MICS
tape data set being created and the number of GDG entries defined.Note:
The RETPD=nnn, EXPDT=expdt, and NOEXPDT parameters are mutually exclusive.NOEXPDT
Defaults to the BKUPPARM specification. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
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.Note:
The NOEXPDT, EXPDT=expdt, and RETPD=nnn parameters are mutually exclusive.COMP / NOCOMP
Defaults to the BKUPPARM specification or the other default.
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. The TRTCH subparameter must be specified to generate.
This parameter overrides the BKUPPARM specification or the default.
NULLUNIT=unitname
Defaults to the BKUPPARM specification or other default.
The generic unit name to be used for allocation of the NULLSER tape volume. The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter overrides the BKUPPARM specification or the default.
NULLSER=nulser
Defaults to the BKUPPARM specification or other default.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run. This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements.If a virtual tape subsystem (VTS) is used at your site for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This action prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, and a MOUNT from being issued by z/OS. This is imperative for JES3 customers with an ATL or VTS because the MICS operational job will not continue until the mount is satisfied.
It also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
For example, after choosing the volume123456, it is important to adjust and submit the following job to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter overrides the BKUPPARM specification or the default.
STACK / NOSTACK
Defaults to the BKUPPARM specification or the default.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. This action is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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.This parameter overrides the BKUPPARM specification or the default.
AFF / NOAFF
Defaults to the BKUPPARM specification or other default.
Specify AFF to use a single tape unit for all related tape files. This action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.This parameter overrides the BKUPPARM specification or default.
MODEL='modeldsn' / MODEL=NOMODEL
Defaults to the BKUPPARM specification or default.
The fully qualified name of a cataloged data set to be used when defining or extending GDG entries. Ensure that the data set's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter overrides the BKUPPARM specification or the default.
DISK / TAPE
Defaults to the BKUPPARM specification or other default.
Specify DISK if you want to write the data set to a disk instead of a tape. Specify TAPE to write the data set 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.
This parameter overrides the BKUPPARM specification or the default.
SPACE=spacedef
Defaults to the BKUPPARM specification or other default.
This parameter defines the space allocation for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
This parameter overrides the BKUPPARM specification or the default.
VOLSER=volser
Defaults to the BKUPPARM specification or other default.
This parameter 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.
This parameter overrides the BKUPPARM specification or the default.
MBKUPSMSPARM
Defaults to the values specified on (or defaulted for) the BKUPSMSPARM statement.
Optional parameter for specifying System Managed Storage (SMS) keywords for
MICS
monthly backup tape data set allocations. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.This parameter overrides the BKUPSMSPARM statement or the default.
HISTMPARM
Use the optional HISTMPARM statement to specify parameters defining processing options for Archive Monthly History tape data sets. When using the Archive Monthly History tapes, the HISTMPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM statement.
The primary reason to specify the HISTMPARM statement is to override the default number of archive monthly history generation data group entries to be defined (the GDG= parameter). However, your site can direct the archive monthly history tapes 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. The HISTMPARM statement gives you the flexibility to uniquely define tape data set parameters for archive monthly history tapes.
The general form of the HISTMPARM statement is the keyword HISTMPARM followed by one or more HISTMPARM parameters. HISTMPARM parameters include both keyword parameters and keyword=value specifications. You can specify the HISTMPARM 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.
A HISTMPARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.HISTMPARM GDG=nnn UNIT=unitname VOLCOUNT=n HISTMPARM EXPDT=expdt / RETPD=nnn / NOEXPDT HISTMPARM COMP/NOCOMP HISTMPARM NULLUNIT=unitname NULLSER=nulser HISTMPARM STACK/NOSTACK AFF/NOAFF HISTMPARM MODEL='modeldsn' / MODEL=NOMODEL HISTMPARM DISK / TAPE SPACE=spacedef HISTMPARM VOLSER=volser
A sample HISTMPARM statement follows:
HISTMPARM GDG=3 VOLCOUNT=7
In this example, the TAPEPARM parameter values are used for most of the HISTMPARM parameters.
GDG=nnn
Defaults to 5.
The number of entries to be created in the GDG for each archive monthly history data set.
The recommended value is GDG=5. The calculated default retention period for these files is equal to the number of entries that are specified, multiplied by 31 (31 days per month).
Note:
This specification is not
what determines the length of time for which archive monthly history data is kept. See the description of the "cutoff" in the prefix.MICS.PARMS(DBMODEL) in Data Retention Specifications (FILE Statement).This parameter overrides and replaces the old-style HISTMGDG statement.
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 one through eight character generic unit name for your installation. The value is used in generating a tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter 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, then 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.This parameter 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 is derived based on the GDG=nnn value.
Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.
This parameter 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. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
NOEXPDT is specified when 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.This parameter 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, then 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. The TRTCH subparameter must be specified to generate.
This parameter overrides the TAPEPARM statement COMP/NOCOMP parameter or the old-style IDRC statement.
NULLUNIT=unitname
Defaults to the value specified on the TAPEPARM statement or to the tape unit value.
The generic unit name to be used for allocation of the NULLSER tape volume The parameter value (unitname) must be a valid one through eight character generic unit name for your installation. The value is used in generating tape data set JCL DD statement UNIT parameters.
MICS
does not validate the unitname value except to verify that it is nonblank and one through eight characters in length.This parameter overrides the TAPEPARM statement NULLUNIT=unitname parameter or to the old-style NULLUNIT statement.
NULLSER=nulser
Defaults to the value specified on the TAPEPARM statement or to the old-style NULLSER statement.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run. This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements. If a virtual tape subsystem (VTS) is used at your sites for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This action prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, and a MOUNT issued by z/OS. This is imperative for JES3 customers with an ATL or VTS because the MICS operational job will not continue until the mount is satisfied.
NULLSER also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
For example, after choosing the volume123456, it is important to adjust and submit the following job to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and you let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter overrides the TAPEPARM statement NULLSER=nulser parameter or the old-style NULLSER statement.
STACK / NOSTACK
Defaults to the value specified on the TAPEPARM statement or to STACK.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. This action is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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.This parameter 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 action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.This parameter 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's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter 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 data set to a disk instead of a tape. Specify TAPE to write the data set 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.
SPACE=spacedef
No default.
This parameter defines the space allocation parameter for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
VOLSER=volser
No default.
This parameter 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.
HISTMSMSPARM
Defaults to the values specified on the TAPESMSPARM statement.
Optional parameter for specifying System Managed Storage (SMS) keywords for archive monthly history tape data set allocations. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax, which is separated by commas. Continuation is not allowed.
This parameter overrides the TAPESMSPARM statement.
HISTWPARM
Use the optional HISTWPARM statement to specify parameters defining processing options for Audit Weekly History tape data sets. When using the Audit Weekly History tapes, the HISTWPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM statement.
The primary reason to specify the HISTWPARM statement is to override the default number of archive weekly history generation data group entries to be defined (the GDG= parameter). However, your site can direct the archive weekly history tapes 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. The HISTWPARM statement gives you the flexibility to uniquely define tape data set parameters for archive weekly history tapes.
The general form of the HISTWPARM statement is the keyword HISTWPARM followed by one or more HISTWPARM parameters. HISTWPARM parameters include both keyword parameters and keyword=value specifications. You can specify the HISTWPARM 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.
A HISTWPARM parameter summary follows:
- Each parameter is described in detail here.
- 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. This statement is limited by the 72-character maximum line length. You can also specify only one parameter per line. Either approach is acceptable.HISTWPARM GDG=nnn UNIT=unitname VOLCOUNT=n HISTWPARM EXPDT=expdt / RETPD=nnn / NOEXPDT HISTWPARM COMP/NOCOMP HISTWPARM NULLUNIT=unitname NULLSER=nulser HISTWPARM STACK/NOSTACK AFF/NOAFF HISTWPARM MODEL='modeldsn' / MODEL=NOMODEL HISTWPARM DISK / TAPE SPACE=spacedef HISTWPARM VOLSER=volser
A sample HISTWPARM statement follows:
HISTWPARM GDG=3 VOLCOUNT=6
In this example, the TAPEPARM parameter values are used for most of the HISTWPARM parameters.
AUDITPARM parameters follow:
GDG=nnn
Defaults to 7.
The number of entries to be created in the GDG for each archive weekly history data set.
The recommended value is GDG=7. The calculated retention period for these files is equal to the number of entries that are specified, multiplied by 7 (seven days per week).
Note:
This specification is not
what determines the length of time for which archive monthly history data is kept. See the description of the "cutoff" in Data Retention Specifications (FILE Statement).This parameter overrides and replaces the old-style HISTWGDG statement.
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 one through eight character generic unit name for your installation. The value is used in generating a 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 eight characters in length.This parameter 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, then 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.This parameter 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 is derived based on the GDG=nnn value.
Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.This parameter 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. If no expiration date or retention period is specified, a default retention period is derived based on the GDG=nnn value.
NOEXPDT is specified when 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.This parameter 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 neither COMP nor NOCOMP is specified, then 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 not specified, no TRTCH subparameter is generated.
Overrides the TAPEPARM statement COMP/NOCOMP parameter or the old-style IDRC statement.
NULLUNIT=unitname
Defaults to the value specified on the TAPEPARM statement or to the old-style NULLUNIT statement.
The generic unit name to be used for allocation of the NULLSER tape volume. The parameter value (unitname) must be a valid 1 through 8 character generic unit name for your installation. The value is used in generating 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 eight characters in length.This parameter overrides the TAPEPARM statement NULLUNIT=unitname parameter or the old-style NULLUNIT statement.
NULLSER=nulser
Defaults to the value specified on the TAPEPARM statement or to statement or to NULLSER.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for preallocating dummy tape files when the system is first run. This technique allows MICS
to run without error even though certain input files do not exist. A trap in the macro routine recognizes the NULLSER value and generates the appropriate SET statements.If a virtual tape subsystem (VTS) is used at your site for
MICS
tape processing a VOLSER of NULSER must be added to the appropriate VTS VOLCAT definition. Use your sites process to run an IDCAMS job with the appropriate parameters. See your VTS installation and configuration guide for information on setting up the VOLCAT.To validate if a NULSER volume exists, go to your ISPF ISMF primary options menu and select option 2 (Volume), then 3 (Mountable Tape), and enter NULSER in the Volume Serial Number field. A Mountable Tape Volume List with NULSER characteristics is returned. If a list is not returned, the NULSER is not defined.
If the default value of NULSER is no longer appropriate for your sites automatic tape loader (ATL) or VTS environments, you should choose an actual volume serial number residing in the ATL or VTS that
MICS
will use when pre-allocation of a tape file is needed.This action prevents the possibility of an additional tape device outside the ATL or VTS from being allocated, and a MOUNT from being issued by z/OS. This action is imperative for JES3 customers with an ATL or VTS because the MICS operational job does not continue until the mount is satisfied.
It also prevents job abends due to a JCL error accompanied by a message, for example:
IEF391I jobname stepname ddname UNABLE TO ALLOCATE - A TAPE ALLOCATION SUBSYSTEM ELIMINATED ELIGIBLE DEVICES
For example, volume is 123456, it is important to adjust and submit the following job to put an indefinite expiry date on the volume to avoid a future surprise. If you omit the VOL=SER parameter and let z/OS mount a scratch tape, it effectively chooses the volume for you.
//jobname JOB //HOLD EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=SHR,DSN=NULLFILE //SYSUT2 DD DSN=sharedprefix.MICS.HOLDFOR.NULLSER, // DISP=(NEW,CATLG), // UNIT=nullunit, // VOL=SER=123456, // EXPDT=1999/365 //
This parameter overrides the TAPEPARM statement NULLSER=nulser parameter or the old-style NULLSER statement.
STACK / NOSTACK
Defaults to the value specified on the TAPEPARM statement or to STACK.
Specify STACK (the default) to "stack" multiple
MICS
tape files on a single tape volume. This action is the normal mode of operation where a minimum number of tape volumes are used and tape mounts are minimized. MICS
JCL statements are generated with the VOL=REF=ddname construct and unit affinity is enforced (that is, STACK also means AFF).Specify NOSTACK 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.This parameter 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 action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.This parameter 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's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter 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 data set to a disk instead of a tape. Specify TAPE to write the data set 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.
SPACE=spacedef
No default.
This parameter defines the space allocation parameter for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
VOLSER=volser
No default.
This parameter 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.
HISTWSMSPARM
Defaults to the values specified on the TAPESMSPARM statement.
Optional parameter for specifying System Managed Storage (SMS) keywords for
MICS
archive weekly history tape data set allocations. For example, STORCLAS=storclas. Specify one or more SMS parameters according to JCL language syntax separated by commas. Continuation is not allowed.This parameter defines the TAPESMSPARM statement.
AUDITGDG
Replaced by the AUDITPARM statement GDG=nnn parameter.
The number of entries to be created in the GDG for each archive audit data set. The number of entries control the number of weeks for which archive audit data is maintained for each
MICS
file for which it is kept. This process creates one tape of data per week, unless you have massive files.The recommended value for the AUDITGDG parameter is 53. The calculated retention period for these files is equal to the number of entries that are specified, multiplied by 7 (seven days per entry).
BCKUPGDG
Replaced by the BKUPPARM statement GDG=nnn parameter.
The number of generation data group entries to be maintained for the database backup files. The recommended number is 10. The calculated retention period for these files is based on BACKUP FREQ.
HISTMGDG
Replaced by the HISTMPARM statement GDG=nnn parameter.
The number of generation data group entries to be maintained for the archive monthly history files. The recommended number is 2. The retention period that is calculated by
MICS
for these files is equal to the number of entries that are specified, multiplied by 31 (31 days per month).Note:
This specification is not what determines the length of time for which archive monthly history data is kept. See the description of the "cutoff" in the prefix.MICS.PARMS(DBMODEL) in Data Retention Specifications (FILE Statement).HISTWGDG
Replaced by the HISTWPARM statement GDG=nnn parameter.
The number of generation data group entries to be maintained for the archive weekly history files. The recommended number is 7. The retention period that
MICS
calculates for these files is equal to the number of entries that are specified, multiplied by 7 (seven days per entry).Note:
This specification is not what determines the length of time for which archive weekly history data is kept. See the description of the "cutoff" in the prefix.MICS.PARMS(DBMODEL) in Data Retention Specifications (FILE Statement).DETAILTAPEPARM
Use the optional DETAILTAPEPARM statement to specify parameters defining processing options for
MICS
DETAIL tape data sets. When using the DETAIL tapes, the DETAILTAPEPARM parameter specifications override the tape data set defaults that are established by the TAPEPARM statement.The primary reason to specify the DETAILTAPEPARM statement is to override parameters such as the default number of generation data group entries to be defined (the GDG= parameter). However, your site can direct the DETAIL tapes to a unique tape volume pool, or to a tape device type such as a virtual tape unit, or to a DASD pool that is backed by an archive facility.
The DETAILTAPEPARM statement gives you the flexibility to define tape data set parameters for DETAIL tapes at the unit level.
Note:
You can specify unique DETAIL tape parameters at the component and individual data set levels with statements in the prefix.PARMS(cccOPS) members (where ccc is the component identifier). For more information, see Parameters section in the relevant Product Analyzers.The general form of the DETAILTAPEPARM statement is the keyword DETAILTAPEPARM, followed by one or more DETAILTAPEPARM parameters. 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 DETAILTAPEPARM parameters summary follows:
- Each parameter is described in detail here.
- 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
A sample DETAILTAPEPARM statement follows:
DETAILTAPEPARM GDG=3 VOLCOUNT=7
In this example, the default parameter values are used for most of the DETAILTAPEPARM parameters.
The DETAILTAPEPARM parameters follow:
GDG=nnn
Defaults to 7.
The number of entries to be created in the GDG for each DETAIL tape data set.
This parameter 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 one through eight 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 nonblank and one through eight characters in length.This parameter 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.This parameter 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 is used which equals the GDG=nnn value.
Specify an expiration date definition which replaces the derived default retention period (RETPD) specifications. This facility is intended for use by installations with tape management systems which require specific EXPDT definitions.
Note:
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, and, if 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.This parameter 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.This parameter 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. The TRTCH subparameter must be specified to generate.
This parameter overrides the TAPEPARM statement COMP/NOCOMP parameter.
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. 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. This option the generated MICS
JCL statements do not
contain the VOL=REF=ddname construct. This action 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.This parameter 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 action is the normal mode of operation where a minimum number of tape units are used and tape mounts are minimized.
MICS
JCL statements are generated with the UNIT=AFF=ddname construct. AFF is required for the STACK option.
Specify NOAFF to enable an allocation of different tape units for each
MICS
tape data set. With this option, the generated MICS
JCL statements do 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.This parameter 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's 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 that 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 data set name, the use of the model data set in the DCB specification is bypassed.
This parameter 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 data set to a disk instead of a tape. Specify TAPE to write the data set 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.
This parameter overrides the TAPEPARM statement DISK/TAPE parameter.
SPACE=spacedef
No default.
This parameter defines the space allocation parameter for a data set defined with the DISK parameter. Specify this parameter according to JCL language syntax.
This parameter overrides the TAPEPARM statement SPACE= parameter.
VOLSER=volser
No default.
This parameter 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.
This parameter overrides the TAPEPARM statement VOLSER= parameter.
DETAILTAPESMSPARM
Use the optional DETAILTAPESMSPARM statement to specify System Managed Storage (SMS) keywords to be used for DETAIL tape data sets. For example, STORCLAS=storclas. When using DETAIL tapes, the DETAILTAPESMSPARM parameter specifications override the SMS defaults that are established by the TAPESMSPARM statement. Parameters are separated by commas.
The DETAILTAPESMSPARM statement gives you the flexibility to define tape data set SMS parameters for DETAIL tapes at the unit level.
Note:
You can specify unique DETAIL tape SMS parameters at the component and individual data set level with statements in the prefix.PARMS(cccOPS) members (where ccc is the component identifier). For more information, see Parameters section in the relevant Product Analyzers.TAPEUNIT
Replaced by the TAPEPARM statement UNIT=unitname parameter and is obsolete.
The generic unit name to be used for tape file allocation. The values that are allowed for this parameter are 2400, 2400-1, 2400-2, 2400-3, 2400-4, 3400-2, 3400-3, 3400-4, 3400-5, 3400-6, 3400-9, 3480, and 3490. The default value is 3490. Specify the parameter ASIS if a non-device-dependent name (for example, TAPE) is used at your data center. A sample TAPEUNIT statement is:
TAPEUNIT TAPE ASIS
VOLCOUNT
Replaced by the TAPEPARM statement VOLCOUNT=nnn parameter and is obsolete.
Use the volume count for the backup and archive tape data sets. The volume count is a decimal number from 1 through 255. If the VOLCOUNT keyword is omitted or is null, the default volume count of 5 is used.
EXPDT
Replaced by the TAPEPARM statement EXPDT=expdt or NOEXPDT parameters and is obsolete.
Specify an expiration date definition that replaces the standard retention period (RETPD) definitions for the tape files that are used in backup, archive audit, archive weekly history, and archive monthly history. This facility is directed at data centers that use a tape management system which requires specific EXPDT definitions.
Note:
For some tape management systems, certain EXPDT values make the tape available for scratching immediately. Such values are not suitable for MICS
tapes. This statement is an option, and if omitted, results in the standard retention period being used on the tape creation DDs. The standard retention period is calculated in the manner that is described in the previous section.SYSTEMMODEL
Replaced by the TAPEPARM statement MODEL='modeldsn'/ MODEL=NOMODEL parameter and is obsolete.
The fully qualified name of a cataloged data set to be used when defining or extending GDG entries. Ensure that the data set's 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 that is defined in the configuration members that are referenced by the CONFIG DD statement. If this parameter is omitted (or left blank), a
MICS
generation job allocates a model GDG data set.If NOMODEL is specified as the model data set name, the use of the model data set in the DCB specification is bypassed.
NULLSER
Replaced by the TAPEPARM statement NULLSER=nulser parameter and is obsolete.
The value to be used to signify a dummy tape volume to
MICS
. This value is used for the archive history tape files when the system is initially run. It allows MICS
to run without error even though the files do not exist. This process is accomplished by a trap in the macro routine that recognizes the NULLSER value and generates the appropriate SET statements. The default value for this parameter is NULSER. If your site standards prevent using the NULSER value for this parameter, change this value.An example is in the case of the automatic tape loaders (ATLs). If you are adding a new file to history archive tapes in an ATL, you may need to change your NULLSER value to an actual volume serial number contained in the ATL. This action prevents an extra tape device (outside the ATL) from being allocated and a MOUNT for the volume serial NULSER. This value imperative for JES3 customers with ATLs because the job does not continue until the mount is satisfied.
NULLUNIT
Replaced by the TAPEPARM statement NULLUNIT=unitname parameter and is obsolete.
The generic unit name to be used for tape file allocation for the NULLSER. If not specified, the value of TAPEUNIT is used. The values that are allowed for this parameter are 2400, 2400-1, 2400-2, 2400-3, 2400-4, 3400-2, 3400-3, 3400-4, 3400-6, 3400-9, 3480, and 3490. Specify the parameter "ASIS" if a non-device-dependent name (for example, TAPE) is used at your site. A sample NULLUNIT statement:
NULLUNIT TAPE ASIS