Command Parameters for all DDIO files
This section describes the parameters accepted by the commands that manage existing shared directories, databases, source files, report files and DBMODEL (used for dynamic creation feature). Not all parameters are available for all commands.
ABEND (A):
Selects BMC AMI DevX Abend-AID reports by abend code. Wildcard characters are valid. However, valid abend codes must begin with U or S.
AM:
Specifies the access method for the file being created. This parameter is only used when allocating or reallocating a file. Allowable values are:
VSAM: | The access method is VSAM. |
BSAM: | The access method is sequential. |
APPLID:
Selects transactions by system APPLID. Wildcard characters are valid.
AUTODELETE (AD):
Determines the action taken when an attempt is made to write a member to a DDIO file that is full. The AUTODELETE parameter specifies whether the oldest member in the DDIO file is automatically deleted when the file becomes full. An individual database, report file or source file is considered full when all of the groups (EXTENTs) in the file have been allocated or the number of members specified by REPTCOUNT has been reached.
The autodelete process is based on manual and automatic locks. Manual locks are created online using the L line command from any directory screen or with the batch utility LOCK command. Automatic locks are created whenever a member is added to a database, source file or report file formatted using the AUTODELETE=DUPS or AUTODELETE=STAGED options. The most recent member on that database is automatically locked.
Members that have been manually locked retain their locks during the autodeletion process. They may be unlocked by using the U line command online or with the UNLOCK batch command. A DELETE command in batch, or the D line command online, will unlock a member prior to executing the delete.
When a shared directory is specified in the creation of a new member, the autodelete attributes are reflected at the database level unless the AUTOLOCKMAX value has been set in the shared directory, then the autolocking is reflected at the shared directory level. First, a database is selected to receive the new member. All attached databases participate in the selection process based on their free space amounts. After selection, that database's autodelete setting determines any autodeletion and automatic locking.
For source listings, the oldest member is the program with the earliest compile date and time. For reports from Abend-AID or Abend-AID for CICS, the oldest member is the report with the earliest creation date and time. The following are valid values for AUTODELETE.
YES: | (Default): Allows new members to be written to a full DDIO file by deleting the oldest unlocked members. This method is commonly referred to as wrap-around mode, and is typically used for files where members are added as needed. AUTODELETE=YES does not automatically lock members. A file full condition will occur when AUTODELETE=YES and all members are manually locked or in use. You can resolve a file full condition by manually deleting members from the file, manually unlocking members, or using the DBMODEL feature for source shared directory files. |
DUPS: | This option ensures that one entry of each name remains in a source file, report file, or database; or, in a source shared directory if AUTOLOCKMAX is set. When a new member is added to a database, all automatically locked members with the same name are unlocked except the member with the most recent compile (for source) or creation (for reports) date and time. Members with the same name that have been manually locked using the L line command or the LOCK batch command remain locked and will not be deleted. If the DDIO file becomes full, the oldest unlocked member not in use, regardless of name, is chosen for deletion. When OBJECT=SRCEDIR or OBJECT=SHRDIR is specified for member create, each of its attached databases will participate in the selection process, but only the selected database (if it is DUPS) participates in this automatic unlock-lock process; the most current duplicate member for the selected database will be locked if it is DUPS. If AUTOLOCKMAX=n is set for a shared directory and a new source member is added ALL automatically locked members with the same name within the shared directory are unlocked except the "n" most recent compiles (manually locked members are ignored during this unlock process). After a source database is then selected the normal autodelete process is used on the selected database as needed. A file full condition will occur when all members are manually or automatically locked or in use. You can resolve a file full condition by manually deleting members from the file, manually unlocking members, by using the DBMODEL feature for source shared directories, or by limiting the number of duplicate source members via the REFRESH command or by setting the DUPMAX value in the shared directory to limit the total number of duplicates at LP compile time. |
STAGED: | This option is similar to AUTODELETE=DUPS, and is valid for source listings only. When a new member is added to a DDIO file, all automatically locked members with the same name are unlocked except the member with the most recent compile (for source) or creation (for reports) date and time. Members with the same name that have been manually locked remain locked and will not be deleted. If the DDIO file becomes full, the oldest unlocked member not in use is chosen for deletion. When OBJECT=SRCEDIR or OBJECT=SHRDIR is specified for member create, each of its attached databases will participate in the selection process, but only the selected database (if it is STAGED) participates in this automatic unlock-lock process. The most current duplicate member for the selected database will be locked (if it is STAGED). However, if all members are locked or in use, then the oldest automatically locked member not in use is deleted. If AUTOLOCKMAX=n is set for a shared directory and a new source member is added ALL automatically locked members with the same name within the shared directory are unlocked except the "n" most recent compiles (unless they are manually locked). After a source database is then selected the normal autodelete process is used on the selected database as needed. |
NO: | Prevents members from being written to a DDIO file when it becomes full. To add members to a full file, one or more members of the file must be manually deleted using the DELETE command. For example, if a Source Listing Database file holds production source listings, you may want to use AUTODELETE=NO so that the production listings are not automatically deleted before a new member is successfully added. A Source Listing Database file that holds listings from development could be formatted with AUTODELETE=DUPS or AUTODELETE=STAGED. With the AD=DUPS or AD=STAGED option, new members may be added to the full DDIO file if there are any members eligible to be automatically deleted. A file full condition will occur when the file is full. You can resolve a file full condition by manually deleting members from the file or by using the DBMODEL feature of source listing shared directories. |
A DIR/DIRX member list of the shared directory will reflect the mixture of database-level locking attributes unless AUTOLOCKMAX is set in the shared directory.
DDIO File Full Condition
A file full condition exists when new members cannot be added to a full DDIO file, in which case an error is returned. A file full condition will occur with the following AUTODELETE options:
YES: | All members are manually or automatically locked or in use. |
DUPS: | All members are manually or automatically locked or in use. |
STAGED: | All members are manually locked or in use. |
NO: | The file is full. |
Resolving a File Full Condition
You can perform the following steps to resolve a file full condition:
- Manually delete members from the file.
- Manually unlock members when AUTODELETE=YES or AUTODELETE=DUPS.
- Allocate and format a larger file, and use the MOVE or COPY commands to transfer the contents of the full file to the new file.
- Use the EXPORT command with the DELETE option to archive all or some members to a sequential file (tape or disk).
Using EXPORT, space can be freed up without losing members, since members can be imported back into the file as needed. This method also avoids the overhead created by formatting new files. - (Source Listing database and shared directory only). Set up your shared directory to perform dynamic source database creation. You must first create a DBMODEL in your shared directory, which defines the parameters that will be used to create and format a new Source Listing Database dynamically. [See the CREATE command, CREATE (CRE)].
The DYNCREATE parameter must also be set to YES. The CWPDDIO DD statement must point to your shared directory (NOT to a specific Source Listing Database). When the file-full condition is encountered, a new Source Listing Database will dynamically be created and formatted and the source member created in that database. An informational message is generated to let you know this has occurred. - (Source Listing database and shared directory only). Run the REFRESH command to delete older duplicate versions of all source programs, using the DUPMAX parameter to determine the desired number of duplicates remaining.
- (Source listing database and shared directory only). Set up the DUPMAX parameter in the shared directory to limit the total number of duplicate versions of a program automatically as a new version is added.
AUTOLOCKMAX (ALMAX):
This parameter is applicable only to shared directories of type source and is valid only for the CREATE, CHANGE & REFRESH commands. The AUTOLOCKMAX parameter, if specified, controls the number of duplicate members that will be left autolocked (L) within the specified shared directory (across all attached source databases). When this parameter is specified, ALL attached source databases must be of type AD=DUPS and/or AD=STAGED, otherwise an error message will be generated and the job will complete with a RC=8. Any manually locked member (M) will be ignored for the autolock process, and will remain manually locked in addition to the specified number of autolocked duplicates. Values 1 through 99 are valid, with NO also allowed for the CHANGE command to turn-off a previously-stored setting. When specified in the CREATE or CHANGE commands the value is stored in the shared directory and will be used at member-add time to automatically adjust the number of autolocked versions to the "n" most current versions of that program within the shared directory. When specified in the REFRESH command the value determines a one-time adjustment to the autolock settings of all programs within the shared directory.
If you have ALMAX=NO no autolock-adjustment action will be taken, resulting in a possibility for duplicate locking on different databases. For example, ALMAX=1 would unlock any existing autolocked programs with the same name as the one to be added, before adding the new program.
For example: If you have 2 occurrences of program "TEST1" and 3 occurrences of program "MYPROG" within one shared directory: using ALMAX=1 will autolock only the most recent version each of TEST1 & MYPROG; ALMAX=2 will set the autolock on the 2 most recent versions each of TEST1 & MYPROG.
BASEDDIO (BDDIO):
(FLAG command only). Specifies the ddname of the DDIO file, source database, or source shared directory that contains the baseline members. If the CURRDDIO file contains both the baseline and the current members, this DD statement is not required. The default is the ddname specified with the CURRDDIO parameter, which in turn defaults to CURRENT.
BASENUMBER (BRN):
(FLAG command only). Specifies a baseline member's listing number. This parameter is required if the PROGRAM parameter is not used.
BLKSIZE (BLK):
If you specified AM=BSAM, use this parameter to specify a blocksize for the sequential Database. The default is 27998 and the maximum BLKSIZE is 32767. The BLKSIZE should be between 2048 (or 2 KB) and the track size. If you pre-allocated your database using AM=BSAM you must still specify BLKSIZE or it will default to 27998 during format, the blocksize specified at original create is ignored.
CICSCODE:
Specifies transaction reports by transaction abend code. Wildcard characters are valid.
CISIZE:
If you specified AM=VSAM, use this parameter to specify the control interval size.
If neither the CISIZE nor the BLKSIZE parameter is specified, then the default CISIZE is 18432, and the default blocksize is 18425.
If the CISIZE parameter is not specified, but the BLKSIZE parameter is specified, then the value for CISIZE is determined by adding 7 to the value of the BLKSIZE parameter.
If the BLKSIZE parameter is not specified, but the CISIZE parameter is specified, then the blocksize is determined by subtracting 7 from the value of the CISIZE parameter.
If both the CISIZE and the BLKSIZE parameters are specified, then the specified BLKSIZE parameter value is ignored. In this case, the blocksize is determined by subtracting 7 from the value of the CISIZE parameter.
CONTINUE:
Specifies whether the command will continue if recoverable errors are detected. A value of YES (default) specifies that the command will continue, if possible, when a recoverable error occurs. A value of NO specifies that the command will be stopped when an error occurs. This parameter is valid for the EXPORT, IMPORT, COPY, and MOVE commands.
CURRDDIO (CDDIO):
(FLAG command only). Specifies the ddname of the DDIO file, source database, or source shared directory that contains the current members. If this file also contains the baseline members, the BASEDDIO parameter should not be used. This parameter is required. The default value is the CURRENT DD statement.
CURRNUMBER (CRN):
(FLAG command only). Specifies a current member's listing number. This parameter is required if the PROGRAM parameter is not used.
CYLINDERS (CYL):
To use cylinders as the unit of measure for the size of the file, use this parameter to specify the number of cylinders. This parameter is valid for both VSAM and sequential files.
DATABASEDISP (DBDISP):
When a shared directory is deleted, this parameter determines the disposition of the databases attached to the shared directory. Allowable values are:
DETACH: | (Default) Detach all attached databases from the shared directory prior to deleting the shared directory. This choice preserves the databases and allows you to attach them to another shared directory. |
DELETE: | Do not detach the databases from the shared directory. This choice deletes both the shared directory and the attached databases. |
DATACLAS:
Specifies the eight-character data class name for the Storage Management Subsystem (SMS) operating environment. This parameter is valid only for new shared directories or databases, or when the REALLOCATE parameter is set to YES.
DATEUSED:
This parameter works in conjunction with the SELECTDAYS parameter, and is used only for source listing members. DATEUSED=COMPILE is the default and specifies that the number of days set in the SELECTDAYS parameter will use the listing's compile date for selection. DATEUSED=CREATE can be specified to use the date the source listing was actually post-processed instead of the original compile date of a post-processed listing member.
For pre-processed listing members, specifying CREATE or COMPILE should result in the same selection of members.
DAYSOLD:
Allows you to select just those entries in a DDIO file that are older than nnn days. For example, using the DELETE command for a Source Listing Database with DAYSOLD=30 deletes all source listing entries that are more than 30 days old.
DDNAME (DDN):
Use this parameter for the ddname on the JCL DD statement that specifies the data set name of the DDIO file you want to direct your command to. For commands that require specifying both a database and a shared directory (ATTACH), use DDN= for the database, and DIRDD= for the shared directory.
For PRINT of an embedded source support member (OBJECT=ESS), this is the DDNAME of the load library containing the specified module name. If not specified, the default DDNAME of ABNLDFIL is used.
DELETE:
Applies only to the EXPORT command. Specifies whether successfully exported entries will be deleted from the FROM file. A value of YES specifies that the entries will be deleted. A value of NO specifies that the entries will not be deleted. The default value is NO.
DELETEIC:
Applies only to the EXAMINE command. Deletes any incomplete listings from the shared directory and attached database. Incomplete listings are partial members that did not complete due to outages or processing failures, while writing to the database.
DIRDD:
This parameter specifies the ddname on a JCL DD statement. For commands that require specifying both a database and a shared directory (ATTACH), use DDN= for the database, and DIRDD= for the shared directory. For commands that refer to only one data set, you may use DIRDD= as a synonym for DDN=.
DIRDSN:
If you need to specify a shared directory and will not be using a JCL DD statement for the data set name, use this parameter to specify the data set name of the shared directory. This parameter contains the actual data set name.
For commands that require specifying both a database and a shared directory (ATTACH), use DSN= for the database, and DIRDSN= for the shared directory. For commands that refer to only one data set, you may use DIRDSN= as a synonym for DSN=.
DIRENTS:
Applies only to the ESTIMATE command and the CREATE command for a shared directory (only). This parameter specifies the total number of members (reports or source listings) expected in the Shared Directory. The total number of directory entries is the sum of the total number of entries in each attached database. When combined with a blocksize, the DIRENTS parameter is used by CWDDALLU to calculate a reasonable number of blocks for allocation. The blocksize can be specified directly in the BLKSIZE parameter, or indirectly through the CISIZE or MODEL parameter. If you will be using an external method to allocate blocks (e.g., IDCAMS or File-AID), you can use the ESTIMATE command to determine the number of blocks you will need. See ESTIMATE for more information on the ESTIMATE command. If you use DIRENTS in the CREATE command for a shared directory the estimated number of blocks will be used to allocate the file. See CREATE for more information on the CREATE command.
Valid values of DIRENTS are any number between 1 and 999999
DIRVOL:
If you are using the CREATE command to create a shared directory, and will not be using a JCL statement for the volume serial of the shared directory, you can use this parameter to specify the volume serial number.
DSN:
If you need to specify a DDIO file and will not be using a JCL DD statement for the data set name, use this parameter to specify the data set name of the file. This parameter contains the actual data set name.
For PRINT of an embedded source support member (OBJECT=ESS), this is the data set name of the load library containing the specified module name. If not specified, the default DDNAME of ABNLDFIL is used.
If you specified OBJECT=DBMODEL, the DSN specification dbmodelname is stored and used later to dynamically build the actual DSN of the Source Listing Database that is created during the dynamic database create function (DYNCREATE). When the DSN is specified for either CREATE or CHANGE of a DBMODEL, certain tokens are allowed for specifying DSN qualifiers along with (or in place of) literals. The tokens are prefixed with an "&" and must be separated by a ".". If the combined length of literals, generated qualifiers, and separators is greater than 44, an error will occur when trying to build the name. The TEST function is available to test the actual DSN creation. The allowable tokens are:
&JOB: | insert job name as qualifier |
&STEP: | insert job step as qualifier |
&USER: | insert user/owner ID (if the user/owner ID is unavailable, the token will be treated a NULL) |
&DATE: | insert current date in Julian format preceded by the letter “D” (YYYYDDD) |
&TIME: | insert current time preceded by the letter “T” (HHMMSS format) |
&SEQ: | insert a sequentially increasing number preceded by the letter “S” (NNNNNNN) |
DUPMAX:
This parameter is applicable only to source databases and source shared directories and is valid only for the CREATE, CHANGE & REFRESH commands. The DUPMAX parameter, if specified, limits the total number of duplicate members (members with the same program name) that will be left within the specified source shared directory across all attached source databases. Any manually-locked member will be ignored for this process, and will remain in the shared directory in addition to the maximum duplicate limit specified. Any member residing on a database with the AD=NO attribute will also be ignored for this process. Any unlocked and/or autolocked duplicate members over the specified DUPMAX value will be deleted. Values 1 through 99 are valid, with NO also allowed for the CHANGE command to turn-off a previously-stored setting. When specified in the CREATE or CHANGE commands the value is stored in the shared directory and will be used when a new member is added to automatically adjust the number of duplicate members to the N most current versions of that program within the shared directory. When specified in the REFRESH command the value determines a one-time adjustment to the number of duplicates for all programs in the shared directory.
DUPMAX=1 limits the shared directory to a single, most current version of a given program - the delete action is done first, so DUPMAX=1 would delete any existing program versions with the same name as the program to be added before adding the new program.
For example: If you have 2 occurrences of program "TEST1" and 3 occurrences of program "MYPROG" within one shared directory, using DUPMAX=1 will delete the older version of TEST1 and both older versions of MYPROG, leaving just one version of each program; DUPMAX=2 would not affect TEST1, and would delete the oldest version of MYPROG, leaving 2 versions.
DUPS:
Specifies whether all entries, only locked entries, only unlocked entries, or only the latest version of each entry is selected. The available values are: ALL, LOCKED, UNLOCKED, or LATEST. The default value is ALL. The LATEST value only applies to source entries. Warning: DUPS=ALL selects ALL members matching any specified selection criteria. If no other selection parameters are specified, all members in the file will be selected.
DYNCREATE:
Specifies that dynamic database creation will be invoked if the attached databases do not have enough space to create a new source listing member. The default value is YES. Users can optionally turn it off when creating or modifying a DBMODEL. This is used only with OBJECT=DBMODEL.
ENDDATE (EDATE):
When you restrict a command to only some members of a DDIO file, you can use this parameter to specify that members with a higher date are not to be considered. For source DDIO files, ENDDATE represents the latest compile date to be considered. For report DDIO files, ENDDATE represents the last report creation date to be considered.
This parameter can be specified as either MM/DD/YY or MM/DD/YYYY. Acceptable four-digit years are 1970 through 2069. If ENDDATE is specified, then STARTDATE must also be specified. The highest valid ENDDATE is 12/31/2069.
ENDTIME (ETIME):
When you restrict a command to only some members of a DDIO file, you can use this parameter to specify that members with a higher time are not to be considered. For source DDIO files, ENDTIME represents the latest compile time to be considered. For report DDIO files, ENDTIME represents the last report creation time to be considered.
This parameter must be specified as HH:MM[:SS] or HH.MM[.SS]. If seconds are omitted, the default is 59.
This parameter must be preceded by the STARTTIME parameter. If the STARTTIME parameter is specified and the ENDTIME parameter is omitted, then ENDTIME defaults to 24:00:00.
When using STARTTIME and ENDTIME in conjunction with STARTDATE and ENDDATE, entries are first selected by date, then by time.
EXEC:
Specifies how certain commands are to be run.
Allowable values for the FLAG command:
- RUN: Creates flagged members, and provides a detailed report.
- SIMULATE: Creates a detailed report, but does not create any flagged members.
Allowable value for the REFRESH command (only valid for source shared directory): - CHECK: Does not allow the command to alter data. Instead, produce a detailed report on what actions would have taken place if the command had been run without the "CHECK" option.
Allowable values for the COPY/MOVE/IMPORT/EXPORT commands, when using a stand-alone DDIO file only (not valid for shared directory and/or database files): - SUMMARY: (default) Transfers data and produces a summary report. The summary report contains a list of transferred members and a list of deleted "from" DDIO file members (if applicable).
- CHECK: Produces a detailed report without any data being moved. In addition to the summary report, the detailed report includes the lists of attributes of the "to" and "from" DDIO files. For the MOVE, COPY and IMPORT commands, it also includes the names of the members that will be locked and/or deleted in the "to" DDIO file, provided actual data movement occurs. The detailed report produced by EXEC=CHECK may be different at RUN time if the "to" and/or "from" DDIO file is updated before the EXEC=RUN is performed. When EXEC=CHECK is specified, these commands are emulated with the header and directory blocks residing in memory. To keep the header and directory blocks in memory you may need a larger region when executing these commands.
- RUN: Transfers data and produces a detailed report. In addition to the summary report, the detailed report includes the lists of attributes of the "to" and "from" DDIO files. For the MOVE, COPY and IMPORT commands it also includes the names of locked and/or deleted members in the "to" DDIO file during execution of the command.
By coding EXEC=CHECK or SIMULATE you can make a trial run of the command, not actually altering anything, but getting a report on what would happen if you ran the command without EXEC=CHECK.
EXTENTS:
Specifies the maximum number of extents to be allocated for any one entry in a report file, a source file, or a database. If the EXTENTS parameter is not specified, the default value is 460. The maximum value is 460.
FLAGGEDDDIO (FDDIO):
(FLAG command only). Specifies the ddname of a DDIO file to receive the tagged members. If the CURRDDIO file will be used for the tagged members, this parameter should not be specified. If you omit this parameter, each new flagged member will replace the corresponding member in the CURRDDIO file. If you supply this parameter, the baseline and current members will not be altered or replaced. Instead, a new flagged member will be created in the FLAGGEDDDIO file.
The FLAGGEDDDIO file may not be a source database or source shared directory. If the BASEDDIO or CURRDDIO file is a source database or source shared directory, the FLAGGEDDIO parameter cannot be used.
FROMDD:
Specifies the JCL ddname of the DDIO file from which entries are copied, exported, or moved. It also specifies the ddname of the sequential file from which previously exported entries are imported.
FROMDSN:
Specifies the data set name of the DDIO file from which entries are copied, exported, or moved. It also specifies the data set name of the sequential file from which previously exported entries are imported.
FROMOBJECT:
This parameter is maintained for compatibility with prior releases. It is no longer necessary to supply it in your job. It specifies the type of file from which the entries are copied, exported, or moved. Allowable values are:
SHRDIR: | The from file is a shared directory. |
DATABASE: | The from file is a database. |
For compatibility with previous releases, SRCEDIR is an accepted synonym for SHRDIR.
FROMVOL:
Specifies the VOLSER of the DDIO file from which entries are copied, exported, or moved. It also specifies the VOLSER of the sequential file from which previously exported entries are imported. Unless you have not cataloged the DDIO file on your system, it is not necessary to supply this parameter.
GROUPCOUNT (GC):
Specifies the number of blocks allocated to a report file, source file, or database entry each time additional space is needed. The minimum value is 1, and the maximum value is 2048. The default value is 3 for VSAM and 2 for BSAM.
ID:
(FLAG command only). Specifies the user-defined identifier and its location. The first parameter is the ID, which has a maximum length of eight bytes. The ID must be contained within columns 73-80. The second parameter is the starting column position. The values are enclosed in parentheses. For example: ID=(BOB,73). This field will be used as a filter by the Code Coverage reporting facility.
(PRINT command with OBJECT=ESS only). Specifies the CSECT name to be used for printing an embedded source support member (OBJECT=ESS) from a load library. It must be a valid CSECT name, from 1 to 8 characters. This is an optional parameter - if the CSECT name is the same as the module name specified in the PROGRAM parameter the ID parameter does not need to be specified, and the CSECT name is assumed to be identical to the module name specified in the PROGRAM parameter.
INC:
Specifies whether to include incomplete entries in the selection. Allowable values are:
YES: | Select both complete and incomplete entries. |
NO: | Select only complete entries. |
ONLY: | Select only incomplete entries. |
INDD (I):
Specifies an alternative ddname for an input DDIO file. This parameter also specifies the ddname of a sequential file containing exported members for the DIRS command. If the INDD parameter is not specified, the default ddname ABNLDFIL is used.
INDEX:
(FORMAT command only). When used, this parameter's only permissible value of EXT allows indexes to occupy more than one block. This parameter is only useful for BMC AMI DevX Abend-AID report files. INDEX=EXT is now the default for BMC AMI DevX Abend-AID report files.
CAUTION:
You cannot COPY, MOVE, or IMPORT members from a DDIO file formatted with INDEX=EXT to a file formatted without that parameter. You can, however, COPY, MOVE, or IMPORT from a file formatted without the INDEX parameter to a file formatted with INDEX=EXT. INDEX=EXT is only useful for BMC AMI DevX Abend-AID report files.
The maximum size for DDIO files is 4 gigabytes, which is not the same as the maximum size for VSAM files.
JESID:
Specifies reports by JESID. Wildcard characters are valid.
(JESID=J12345| T12345| S12345)
JOBNAME:
Specifies abend reports by the JOB name. Wildcard characters are valid.
(JOBNAME=ACCTNG JOBNAME=A*)
LABEL:
Specifies the file number for the sequential data set on the tape for the IMPORT, EXPORT, and DIRS commands. (VOL=SER=, and other parameters should be specified on the corresponding DD statement). The default value is 1. The LABEL parameter allows you to reference multiple export files using a single ddname. This provides a means by which you can create multiple export files on a single tape. For example, to include a Source Listing Database on a tape that already contains the related source code and compiler output as files 1 and 2, you can specify LABEL=3 in the EXPORT command for that Source Listing Database. This will append the Source Listing Database on the tape as file 3. To perform a DIRS or IMPORT on that file at a later time, include LABEL=3 with the command. The LABEL parameter is valid for IMPORT, EXPORT, and DIRS. You can include the LABEL parameter in your JCL.
If you include the LABEL parameter in your JCL, but have also specified a LABEL parameter with the IMPORT or EXPORT batch command, the LABEL parameter in the JCL will be overridden.
For compatibility with the IBM Tape Management System, the label number ".Lnnn" is appended to the tape DSNAME as the last qualifier. If the combined length of the specified DSNAME and the appended label number exceeds the maximum length for DSNAME, an error message is issued.
LANGUAGE (LANG):
Specifies the available language support and the type of letter case used. Valid values are:
ENGLISH: | (Default) Mixed-case English |
USAMIX: | Alias for mixed-case English |
USAUC: | Uppercase English |
LINESIZE (LIN):
Specifies the line width of the PRINT command output. Allowable values are:
S: | (Default) Short, 80-column output |
L: | Long, 133-column output |
MGMTCLAS:
Specifies the eight-character management class name for the Storage Management Subsystem (SMS) operating environment. This parameter is only valid for new shared directories or databases, or when the REALLOCATE parameter is set to YES.
MODEL:
Use this parameter to specify the data set name of an existing shared directory or database that can be used as a template for creating a new shared directory or database with the same VSAM characteristics. When the MODEL parameter is used, you can override any of the VSAM or BSAM parameters by including the appropriate parameter with the CREATE or EXPAND command. For example, to use a particular shared directory as a template for creating a new shared directory, but with a different CISIZE, include the CISIZE parameter in the CREATE command.
MONTHSOLD:
Allows you to select just those entries in a DDIO file that are older than nnn months. For example, using the DELETE command for a Source Listing Database with MONTHSOLD=6 deletes all source listing entries older than six months.
MULTIVOLUME:
Allows a VSAM DDIO file to be allocated across multiple volumes.
- The MULTIVOLUME parameter is only applicable for VSAM DDIO files, and the VSAM cluster must be pre-allocated.
- This parameter indicates that primary allocation occurs on multiple volumes.
NOTFOUND:
Specifies whether to request a return code 00 or 04, instead of the default code 44, when an entry is not found. The valid values are:
ERROR: | (Default) Allows the default code 44. |
IGNORE: | Forces a return code 00. |
WARNING: | Forces a return code of 04. |
OBJECT (OBJ):
This parameter is required for the CREATE and DELETE commands; when dealing with a DBMODEL for a source shared directory; and, for embedded source support (ESS) with the PRINT command. It is maintained as valid for other commands, for compatibility with previous releases. OBJ= specifies the type of object being changed, deleted, locked, unlocked, created, reallocated, or formatted. Allowable values are:
SHRDIR: | A shared directory |
DATABASE: | A database |
ENTRY: | An individual member in the database or shared directory. This option is used only with the DELETE command when removing an entry from a database and the shared directory to which it is attached. |
DBMODEL: | Model database specifications for the dynamic database creation feature (DYNCREATE). |
ESS: | Using the PRINT command to print an embedded source support module/CSECT contained in the specified load library. |
For compatibility with previous releases, SRCEDIR is an accepted synonym for SHRDIR.
OUTDD (O):
Specifies the ddname for the alternative output file for the PRINT member command. If the OUTDD parameter is not specified, the output of the PRINT member command is written to the file specified by the ABNLREPT DD statement, along with all CWDDALLU messages and reports. Refer to Anyname1 on DD Statements Used with CWDDALLU for more information on this ddname and the PRINT command.
PAGESIZE (PG):
Specifies the number of lines per page for the PRINT command output. Allowable values are any number from 20 to 99. The default value is 60.
PROGRAM (P):
Specifies source listings by program name. Wildcard characters are valid, and long names are supported. Example:
REALLOCATE (REALLO):
If the shared directory or database you have specified already exists, you can use this parameter to reallocate the file. Allowable values are:
NO: | (Default) Pre-allocated (but empty) VSAM and sequential files will be formatted as a shared directory or database, as specified. A detached sequential database will be reformatted using the new specifications. |
YES: | For both VSAM and sequential files, the file will be deleted and then reallocated, using the new specifications. If a database is specified that is still attached to a shared directory, the database will first be detached. If a shared directory is specified, first ensure all databases have been detached. |
RECORDS (RECS):
If you have specified AM=VSAM and want to use records as the unit of measure for the size of the file, use this parameter to specify the number of records. This parameter is valid for VSAM files only.
REPAIR:
Attempts repair of any shared directory file structure errors and directory entry mismatches between the shared directory and all of its attached databases.
The REPAIR parameter is only valid for the EXAMINE command.
REPTCOUNT (RC):
Specifies the maximum number of entries in a report file, source file, or database. The maximum will be enforced, but may be unattainable if there is not enough space. The minimum value is 1, and the default value is 100. The maximum REPTCOUNT is 16000 depending on the formatting parameters used. However, specifying a large REPTCOUNT can greatly reduce the efficiency of your DDIO file. Refer to "DDIO Calculator - DDIOCALC" for determining the optimal formatting parameters.
REPTNUMBER (RN):
Specifies an entry's number. If this parameter is specified, all other selective parameters are ignored. Maximum length is ten digits.
RETAINRN:
Specifies whether the entry’s report number will be retained during a move or copy. Allowable values are:
NO: | (Default) Do not retain the number. |
YES: | Retain the number. In this case, if the number to be retained is already being used in the “to” file, then the next highest available number will be used. This value should only be used when moving or copying to a shared directory. |
SECTION (SECT):
(PRINT command only). Specifies which sections of a COBOL program are to be printed. Specify one or more values to indicate which section is desired. Valid values are:
DD: | Prints the data division. |
PD: | Prints the procedure division. |
DI | Prints the diagnostic information section (compiler error messages). |
If the SECTION parameter is not specified, the entire program listing will be printed.
SEEFLAGS:
(PRINT command only). Specifies whether text added by a previous run of the FLAG command should be included in the printed line. Valid values are:
YES: | (Default) Text added by the FLAG command is included in the output. |
NO: | Text added by the FLAG command is suppressed. |
SELECTDAYS:
The SELECTDAYS parameter allows selection of just those members in a DDIO file that are within "nnn" days prior and including the current date, designed primarily for use in the EXPORT, IMPORT,COPY & MOVE commands; it can also be used in the directory commands (DIR,DIRS) to show those members that would be selected. For example, to export members created today and yesterday specify SELECTDAYS=2; to select members created today specify SELECTDAYS=1. This parameter is invalid for the DELETE command.
SLSDD:
For BMC AMI DevX Abend-AID source support, this parameter specifies the ddname of the optional source listing file for which the PRINT command will provide source support. If the SLSDD parameter is not specified, the default ddname SLSF001 is used.
If the SLSDD parameter is omitted and the SLSF001 DD statement is not coded, only the basic diagnostic report will be provided by the PRINT command.
SORT:
Specifies the order in which entries are selected for the execution of a command. By default, entries are selected in descending date/time order. Entries are first ordered by date, from newest (most recent) to oldest. Entries with the same date are then ordered by time (from latest to earliest). Valid sort keys, their abbreviations, and the sorting sequence they cause are specified in Source Listing Sort Keys, Batch Abend Report Sort Keys for BMC AMI DevX Abend-AID, and Transaction Abend Report Sort Keys for BMC AMI DevX Abend-AID for CICS, the next three tables.
Source Listing Sort Keys
Sort Key | Abbreviation | Primary Sort Field | Sequence | Secondary Sort Field | Sequence | Tertiary Sort Field | Sequence |
PROGRAM | PGM | PROGRAM | Ascending | DATE/TIME | Descending | LIST-NUMBER | Descending |
NUMBER | NUM | LIST-NUMBER | Descending | ||||
DATE | DATE/TIME | Descending | LIST-NMBER | Descending | |||
RC (return code) | RC | Ascending | DATE/TIME | Descending | LIST-NUMBER | Descending | |
LANGUAGE | LANG | LANGUAGE | Ascending | DATE/TIME | Descending | LIST-NUMBER | Descending |
SIZE | SIZE | Descending | DATE/TIME | Descending | LIST-NUMBER | Descending |
Batch Abend Report Sort Keys for BMC AMI DevX Abend-AID
Sort Key | Abbreviation | Primary Sort Field | Sequence | Secondary Sort Field | Sequence | Tertiary Sort Field | Sequence |
JOBNAME | JN | JOBNAME | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending |
JESID | JESID | Descending | DATE/TIME | Descending | REPT-NUMBER | Descending | |
DESCRIPTION | DESC | DESCRIPTION | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending |
SIZE | SIZE | Descending | DATE/TIME | Descending | REPT-NUMBER | Descending | |
NUMBER | NUM | REPT-NUMBER | Descending | ||||
CODE | CODE | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending | |
DATE | DATE/TIME | Descending | REPT-NUMBER | Descending |
Transaction Database Sort Keys for BMC AMI DevX Abend-AID for CICS
Sort Key | Abbreviation | Primary Sort Field | Sequence | Secondary Sort Field | Sequence | Tertiary Sort Field | Sequence |
JOBNAME | JN | JOBNAME | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending |
TRAN | TRAN | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending | |
TERM | TERM | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending | |
SYSTEM | SYSTEM | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending | |
NETNAME | NET | NETNAME | Ascending | DATE/TIME | Descending | REPT-NUMBER | Descending |
NUMBER | NUM | NUMBER | Descending | ||||
DATE | DATE/TIME | Descending | REPT-NUMBER | Descending |
STARTDATE (SDATE):
Specifies the compile date of a source listing, or the creation date of an abend report. The STARTDATE parameter is used with the ENDDATE parameter to specify a date range. The STARTDATE parameter can be specified as either MM/DD/YY or MM/DD/YYYY. Acceptable four-digit years are 1970 through 2069. When this parameter is used alone, all entries for the specified date are selected. The earliest valid start date is 01/01/1970.
STARTTIME (STIME):
Specifies the beginning compile time of a source listing, or the creation time of an abend report. This parameter must be specified as HH:MM[:SS] or HH.MM[.SS]. If seconds are omitted, the default is 00. This parameter must precede the ENDTIME parameter (if ENDTIME is specified).
If the STARTTIME parameter is specified and the ENDTIME parameter is omitted, then ENDTIME defaults to 24:00:00.
When using STARTTIME and ENDTIME in conjunction with STARTDATE and ENDDATE, entries are first selected by date, then by time.
STORCLAS:
Specifies the eight-character storage class name for the Storage Management Subsystem (SMS) operating environment. This parameter is only valid for new shared directories or databases, or when the REALLOCATE parameter is set to YES.
SUBTYPE:
Further specifies the type of members the DDIO file can contain. This parameter is used in conjunction with the TYPE parameter.
If you are formatting source listing files for BMC AMI DevX Abend-AID for CICS and you are using user or system DSECT files, you must specify SUBTYPE=FX. The TYPE parameter defaults to TYPE=CICS.
TODD:
Specifies the ddname of the database or shared directory to which the entries are copied, imported, or moved. It also specifies the ddname of the sequential file to which entries are exported.
TODSN:
Specifies the DSN of the database or shared directory to which the entries are copied, imported, or moved. It also specifies the DSN of the sequential file to which entries are exported.
TOOBJECT:
This parameter is maintained for compatibility with prior releases. It is no longer necessary to supply it in your job. It specifies the type of file to which the entries are copied, exported, imported or moved. Allowable values are:
SHRDIR: | The to file is a shared directory. |
DATABASE: | The to file is a Source Listing database. |
For compatibility with previous releases, SRCEDIR is an accepted synonym for SHRDIR.
TOVOL:
Specifies the VOLSER of the database or shared directory to which the entries are copied, imported, or moved. It also specifies the VOLSER of the DDIO file to which previously exported entries are imported.
TRACKS (TRKS):
To use tracks as the unit of measure for the size of the file, use this parameter to specify the number of tracks. This parameter is valid for both VSAM and sequential files.
TRAN (T):
Specifies BMC AMI DevX Abend-AID for CICS transaction reports by transaction ID or by transaction and terminal ID concatenation. Wildcard characters are valid.
TYPE:
When creating a DDIO file, use this parameter to specify the type of entries the file can contain. For a Source Listing file, code TYPE=SOURCE. For a file that will contain Abend-AID reports, specify TYPE=AA. For a file that will contain BMC AMI DevX Abend-AID for CICS reports, specify TYPE=CICS.
UNIT:
If you specified AM=BSAM, use this parameter to specify a device or device type. The default is SYSDA.
VOLSER (VOL):
If you are directing a command to a database or shared directory, which you specify with the DSN= parameter, you may use this parameter to specify the volume serial number of the data set.
VSAMCAT:
If you specified AM=VSAM, use this parameter to specify the VSAM catalog in which the file will be defined. This is an optional parameter.
YEARSOLD:
Allows you to select entries in a DDIO file that are older than nnn years. For example, using the DELETE command for a Source Listing Database with YEARSOLD=1 deletes all source listing entries that are older than one year.