Commands for all DDIO files

This topic provides a detailed description of the commands available for existing all DDIO files, including valid command abbreviations and the parameters allowed for each command. With the exception of specifying REPTNUMBER, you can enter more than one parameter with a command. If REPTNUMBER is specified, all other selective parameters are ignored.

ATTACH (ATT)

The ATTACH command connects a database to a shared directory and populates the shared directory with entries from the database. A database must be attached to a shared directory before it can be used.

The following illustrates the syntax for the ATTACH command.

For a description of each parameter, see Command Parameter for all DDIO files.

CHANGE (CHG)

The CHANGE command performs the following tasks:

• It changes the AUTODELETE attribute of a database.
• It changes or sets the AUTOLOCKMAX and/or DUPMAX source duplicate-control parameters in the shared directory.
• It changes the attributes of a previously-defined DBMODEL in a specified source shared directory.

Change Command – Database AUTODELETE Attributes

The following illustrates the syntax for the CHANGE command, AUTODELETE attribute. The AutoDelete=STAGED attribute is only valid for a source database.

If AUTOLOCKMAX has been set to a value 1 - 99 in the associated shared directory (via CREATE/CHANGE) and you are attempting to change the database AD setting to NO or YES, you will receive an error message and RC=8. You must first set AUTOLOCKMAX to NO.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Change Command - Change Shared Directory autolock and duplicate-control attributes AUTOLOCKMAX & DUPMAX

The following diagram illustrates the syntax for the CHANGE command AUTOLOCKMAX and/or DUPMAX attributes, used to set the compile-time duplicate-member handling for source shared directory members.

When setting the AUTOLOCKMAX and/or DUPMAX parameters for compile-time control, you may also want to run the REFRESH utility function using these same settings to do a one-time adjustment of all duplicate source members within the shared directory.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example 1

Example 2

CHANGE Command – DBMODEL Attributes

This CHANGE syntax diagram illustrates the syntax for allocating and formatting a new Source Listing Database.

Example

CONVERT (CNVT)

The CONVERT command changes the internal format of an existing standard DDIO source file or report file (specified in the DDNAME or DSN parameter) to that of a Source Listing Database or Report Database format. It also performs the ATTACH function on the file, attaching it to an existing shared directory, specified by the DIRDD or DIRDSN parameter.

The following diagram illustrates the syntax for the CONVERT command.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

This command modifies a record in the existing DDIO file, and therefore we recommend that you perform a file backup before executing this command. The source or report DDIO file name you specified in the command parameters will remain the same for the new database format. The CONVERT command merely changes the type and function of the DDIO file. If you want the source or report database to have a different name after it becomes attached to a shared directory, you must rename the original DDIO file prior to executing the CONVERT command.

If an error occurs during the CONVERT process in the attach phase of adding members into the shared directory, the database will set attach in progress (will show on a DIRX), and the shared directory MAY contain entries for only some (but not all) of the database members. If the problem cannot be solved by another attempt at the CONVERT, then perform the following procedure to eliminate possible integrity problems:

• Run UNCONVERT on the database to clear the attach setting, remove entries added to the shared directory during the process, and reset it back to a standard DDIO file format. Then run CONVERT again after determining the cause of the original errors.
• A return code of 100 (X’64’) and message "DDIO0100 - Request is incompatible with file's format" indicates you are trying to convert a DDIO file formatted with the old non-extended format (release 5.6 & earlier). A return code of 1080 (x'438') and message "Report file is not formatted with INDEX=EXT" indicates you are trying to convert a report DDIO file formatted without the INDEX=EXT parameter. Follow the steps here:
  •  CREATE a new database using CWDDALLU.
  •  EXPORT the old DDIO file using CWDDALLU.
  •  IMPORT from this exported file into the new database using CWDDALLU

COPY

The COPY command copies selected entries in any of the following ways:

• From one report file to another report file
• From one source file to another source file
• From one database to another database
• From a database to a shared directory
• From a shared directory to a database
• From one shared directory to another shared directory

You may not use COPY to mix members of different types in a single database. The three types of members are source, BMC AMI DevX Abend-AID report, and BMC AMI DevX Abend-AID for CICS report.

Use the FROMDD and TODD parameters to specify the From and To file ddnames. When an entry is copied to or from a database, which is attached to a shared directory, the shared directory is also updated immediately. If none of the parameters are specified, then all entries are copied.

Since IDR token is a unique key within a source listing shared directory, it is possible to encounter a duplicate IDR condition during member COPY. No such situation can arise within a report shared directory. A warning message will be issued, and the member will not be copied. The remaining COPY processing continues with a return code of 4.

Copy - Source Listing

The following diagram illustrates the syntax for the COPY command.

The use of EXEC is only valid for stand-alone source DDIO files, not for shared directory and/or database files.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Copy Cobol or PL/I program from ESS load file to source DDIO file

Example

Copy - Abend-AID report

The following diagram illustrates the syntax for the COPY command.

The TYPE parameter is required for this command only if:

• The data set being acted on is a shared directory with both BMC AMI DevX Abend-AID and BMC AMI DevX Abend-AID for CICS databases attached

          AND

• You send the utility command to CWDDALLU directly, via a JCL entry reading EXEC PGM=CWDDALLU

 The use of EXEC is only valid for stand-alone BMC AMI DevX Abend-AID report DDIO files, not for shared directory and/or database files.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Copy - Abend-AID for CICS report

The following diagram illustrates the syntax for the COPY command.

 The TYPE parameter is required for this command only if:

• The data set being acted on is a shared directory with both BMC AMI DevX Abend-AID and BMC AMI DevX Abend-AID for CICS databases attached

          AND

• You send the utility command to CWDDALLU directly, via a JCL entry reading EXEC PGM=CWDDALLU

For a description of the parameters, see Command-Parameters-for-all-DDIO-files.

Example

CREATE (CRE)

The CREATE command is used to perform the following functions:

• Allocate and format a new shared directory
• Format a pre-allocated shared directory
• Allocate and format a new database
• Format a pre-allocated database
• Create a DBMODEL entry for dynamic database creation (DYNCREATE) in the specified shared directory, to be invoked during creation of a source listing member if all of the attached Source Listing Databases are full

Sample JCL Members

Sample JCL members for the CREATE command are available in CSS installation library members. See Sample JCL Members for CREATE Command for a list of the sample members.

Sample JCL Members for CREATE Command

The following diagrams illustrate the syntax used for the CREATE command based on the function you want to perform.

Allocating and Formatting a New Shared Directory:

The first CREATE syntax diagram illustrates the syntax for allocating and formatting a new shared directory.

AUTOLOCKMAX and DUPMAX are only used for source members.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Formatting a Pre-Allocated Shared Directory

This CREATE syntax diagram illustrates the syntax for a pre-allocated shared directory. 

AUTOLOCKMAX and DUPMAX are only used for source members.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Allocating and Formatting a New Database

This CREATE syntax diagram illustrates the syntax for allocating and formatting a new database. The AutoDelete=STAGED attribute is only valid for a source database (TYPE=SOURCE.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Example

Example

Formatting a Pre-Allocated Database

This CREATE syntax diagram illustrates the syntax for formatting a pre-allocated database.

Example

Creating a DBMODEL

This CREATE syntax diagram illustrates the syntax for creating a DBMODEL entry. The DBMODEL feature applies only to source shared directories.

For a description of each parameter, see Command Parameter for all DDIO files.

Example

DELETE (DEL)

The DELETE command deletes selected entries from any form of DDIO file, deletes a selected database, deletes a selected shared directory, or deletes the DBMODEL information contained in the selected shared directory.

DELETE an ENTRY from any form of DDIO file

If you delete an entry from either a shared directory or a database, the DELETE command automatically removes the entry from both files. Database entries can only be deleted if the database is attached to a shared directory. You must specify either the DIRDD or DIRDSN parameter to delete members across the shared directory (all databases), or the DDNAME or DSN parameter to delete members on a specific database within a shared directory. (To delete an entry from a database and shared directory you must specify OBJECT=ENTRY; it is not required if you are deleting an entry from a Source Listing file or Report file).

Warning:   Specifying the "DUPS=ALL" parameter in your DELETE command will be handled as an error unless one or more other selection parameters are also specified.

Delete - Source Listing

The following diagram illustrates the syntax for the DELETE command.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Delete - Abend-AID Reports

Be certain to specify OBJECT=ENTRY to delete reports from the shared directory and associated report database.

The following diagram illustrates the syntax for the DELETE command.

 For a description of the parameters see Command-Parameters-for-all-DDIO-files.

Examples

Delete- Abend-AID for CICS Reports

The following diagram illustrates the syntax for the DELETE command.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Enqueues are held on DDIO members being viewed in the BMC AMI DevX Abend-AID for CICS viewing server. You must exit members before issuing batch deletes.

Examples

DELETE a Database (and Detach It from the Shared Directory)

If the database is attached to a shared directory, DELETE also detaches it from the shared directory prior to deletion. You must specify either the DDNAME or the DSN parameter. To delete an entire database, specify OBJECT=DATABASE.

 For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

DELETE a Shared Directory

When deleting a shared directory, you can choose whether to also DELETE all attached databases (DATABASEDISP=DELETE), or DETACH all attached databases prior to the deletion (DATABASEDISP=DETACH). You must specify either the DIRDD or the DIRDSN parameter. To delete an entire shared directory, specify OBJECT=SRCEDIR or OBJECT=SHRDIR.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

All databases are deleted if you delete a shared directory using DATABASEDISP=DELETE. If there are some databases for Batch BMC AMI DevX Abend-AID reports (type AA) and some databases for Abend-AID CICS reports (type CICS), both types will be deleted.

Examples

DELETE the DBMODEL Information from the Shared Directory

For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

DETACH

The DETACH command disconnects a database from a shared directory and removes the database entries from the shared directory.

To ensure that you are aware of the shared directory from which you are detaching the database, you can optionally use the DIRDSN parameter to specify the name of the shared directory. If the shared directory is incorrectly specified, an error will be returned. If the DIRDSN is not specified, then the database will be unconditionally detached from the appropriate shared directory.

The following diagram illustrates the syntax for the DETACH command.

 For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

DIRECTORY (DIR, D) and DIRX (DX)

The DIRECTORY command lists selected entries in any form of DDIO file.

The function of the DIRX command is similar to the DIRECTORY command. The attribute and allocation information is also displayed. When a DIRX is performed on a shared directory, the attribute and allocation information for the shared directory and all databases attached to that shared directory is displayed. DBMODEL information is displayed for Source Listing Shared Directories, as well as any Autolockmax and/or Dupmax settings.

If the database or DDIO file is empty (no members) and/or no selection parameters are used, the return code set will be 0 — the NOTFOUND value is not used.

Directory (DIR, D) and DIRX (DX) - Source Listing

The following diagram illustrates the syntax for the DIRECTORY or DIRX command.

 For a description of the parameters see Command-Parameters-for-all-DDIO-files.

Example 1

Example 2

Directory (DIR, D) and DIRX (DX) - Abend-AID

The following diagram illustrates the syntax for the DIRECTORY or DIRX command.

 The TYPE parameter is required for this command only if:

• The data set being acted on is a shared directory with both BMC AMI DevX Abend-AID and BMC AMI DevX Abend-AID for CICS databases attached

AND

• You send the utility command to CWDDALLU directly, via a JCL entry reading EXEC PGM=CWDDALLU

For a description of the parameters see Command-Parameters-for-all-DDIO-files. For sample JCL for the DIRX command, see Shared Services SLCXCNTL installation library member CXAADIRX.

Example 1

Example 2

Directory (DIR, D) and DIRX (DX) - Abend-AID for CICS

The following diagram illustrates the syntax for the DIRECTORY or DIRX command.

 The TYPE parameter is required for this command only if:

• The data set being acted on is a shared directory with both BMC AMI DevX Abend-AID and BMC AMI DevX Abend-AID for CICS databases attached

AND

• You send the utility command to CWDDALLU directly, via a JCL entry reading EXEC PGM=CWDDALLU

For a description of the parameters see Command-Parameters-for-all-DDIO-files. See Shared Services SLXCNTL installation library member CXCFDIRX for sample JCL for the DIRX command.

Example 1

Example 2

DIRECTORY INFORMATION (DIRI)

The DIRI report is similar to DIRX report, where it provides information on current parameter setting and file statistics, but it does not provide any information about every member of source listing or abend-aid report. It generates lesser output compared to DIRX report and is more useful when determining the size of DDIO files, databases, shared directory for source listing and abend-aid reports.

The syntax for the DIRECTORY INFORMATION (DIRI) command is same as DIRX(DX) as illustrated below with respect to Source Listing:

Example 1

DIRECTORY SEQUENTIAL (DIRS)

The DIRS (Directory Sequential) command lists selected directory entries in a sequential file produced by the EXPORT command. If none of the parameters are specified, then all entries are listed. The LABEL parameter can be specified for multiple export files residing on tape. For more information on this parameter, see Command Parameter for all DDIO files.

Directory Sequential (DIRS)- Source Listing

The following diagram illustrates the syntax for the DIRECTORY SEQUENTIAL command.

 For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Directory Sequential (DIRS)- Abend-AID

The following diagram illustrates the syntax for the DIRECTORY SEQUENTIAL command.

 For a description of the parameters see Command-Parameters-for-all-DDIO-files.

Example

Directory Sequential (DIRS)- Abend-AID for CICS

The following diagram illustrates the syntax for the DIRECTORY SEQUENTIAL command.

 For a description of the parameters, see Command-Parameters-for-all-DDIO-files.

Example

ESTIMATE

The ESTIMATE command is used to determine a reasonable number of blocks to allocate for a shared directory when the allocation is being performed outside of CSS (i.e., through IDCAMS or File-AID product). The resulting calculation is expressed in records.

The following diagram illustrates the syntax used for the ESTIMATE command.

 For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

EXAMINE

The EXAMINE command reads, analyzes, and optionally repairs the selected shared directory to ensure the following:

• Internal shared directory structure integrity.
• Shared directory index and data components match - that is, all entries in the shared directory are accessible via an indexed search, and are selectable for abend diagnosis viewing.
• All databases attached to the shared directory still exist in the MVS catalog.
• All entries in the shared directory exist in the attached databases.

This command creates a report of any inconsistencies and optionally with the REPAIR directive specified:

• repairs shared directory index pointers
• deletes from the shared directory orphaned data entries that are not selectable via the indexed path
• deletes members from the shared directory that no longer exist in the attached database files
• deletes members from the attached databases that are no longer in the shared directory
• deletes incomplete members in the shared directory and attached databases (if DELETEIC specified)
• finds members from the attached database that are no longer in the shared directory and restores them to the shared directory

The following diagram illustrates the syntax for the EXAMINE command.

 The TYPE parameter is required for this command only if:

• The data set being acted on is a shared directory with both BMC AMI DevX Abend-AID and BMC AMI DevX Abend-AID for CICS databases attached

AND

• You send the utility command to CWDDALLU directly, via a JCL entry reading EXEC PGM=CWDDALLU

For a description of the parameters, see Command-Parameters-for-all-DDIO-files.

The REPAIR directive attempts exclusive ENQ control of the selected shared directory.

EXAMINE may be run any time, without the REPAIR and/or DELETEIC directive, to analyze the shared directory’s integrity. However, during periods of heavy compile activity, INDEX/DATA mismatches may be erroneously reported on the EXAMINE report.

An effort was made to prevent EXAMINE/REPAIR from rendering the shared directory or its contents, unusable or impaired after REPAIR processing. However, a backup of the shared directory before using REPAIR is advised.

Runtime Example

EXPAND

The EXPAND command reallocates an existing shared directory using new allocation parameters and copies all of the entries to the newly allocated shared directory. After the copy has completed successfully, the old shared directory is renamed to a temporary name, the new shared directory is renamed to the original name, and the old shared directory is then deleted. You can use this command to increase or decrease the space allocated for a shared directory and/or change the CISIZE.

When using the EXPAND command, the following rules apply:

• The shared directory must already exist (you cannot use EXPAND to create a new shared directory).
• The shared directory must not be in use.

Use the DIRDD or DIRDSN parameter to specify the existing shared directory. You can optionally use the VOLSER to specify the desired volume location for the new expanded shared directory.

The following diagram illustrates the syntax for the EXPAND command.

 For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

EXPORT

 The EXPORT command exports selected entries from any form of DDIO file to a sequential file. The sequential file can then be used as input to the IMPORT command.

The “from” file can be specified using the FROMDSN or FROMDD parameter; or the ABNLFROM DD statement.

The "to" file (sequential file) can be specified using both the TODSN (and optional TOVOL) parameter, TODD parameter, or ABNLTO DD statement. However, if you are exporting to a tape, you must use the TODD parameter. When an entry is exported from a database and DELETE=YES, the shared directory is also updated.

If no other parameters are specified, then all entries are exported.

Multiple EXPORT commands can be used, if you include a unique TODD (or TODSN and TOVOL) parameter for each output data set. If the output file is a PDS, the target member must also be specified. A command must be designated for each PDS member. If the output file is a PDS, the target member can either be specified with the DSN in the TODD/ABNLTO DD statement, or by letting the PROGRAM= parameter also define the member name to be used with the TODD/ABNLTO or TODSN parameter (and cannot be a wildcard or long name). If unique parameters are not used, each successive export will overlay the previous export. See label for information on importing multiple files from tape.

Export- Source Listing

The following diagram illustrates the syntax for the EXPORT command.

The use of EXEC is only valid for stand-alone source DDIO files, not for shared directory and/or database files.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files. See Shared Services SLCXCNTL installation library member CXLPEXPO for sample JCL for the EXPORT command.

Example

Export- Abend-AID

The following diagram illustrates the syntax for the EXPORT command.

The use of EXEC is only valid for stand-alone BMC AMI DevX Abend-AID report DDIO files, not for shared directory and/or database files.

For a description of the parameters see Command-Parameters-for-all-DDIO-files. See Shared Services SLCXCNTL installation library member CXAAEXPO for sample JCL for the EXPORT command.

Example

Export- Abend-AID for CICS

The following diagram illustrates the syntax for the EXPORT command.

For a description of the parameters, see Command-Parameters-for-all-DDIO-files. See Shared Services SLCXCNTL installation library member CXCFEXPO for sample JCL for the EXPORT command.

Example

FLAG

FLAG modifies or creates a source listing (member in a DDIO file, source database, or source shared directory) to show which of its source lines have changed since a prior version of the program. Data definition source lines as well as executable source lines are compared and flagged as appropriate.

The old or baseline version of the program is contained in the DDIO file, source database, or source shared directory specified with the BASEDDIO parameter. The current version of the program is contained in the DDIO file, source database, or source shared directory specified with the CURRDDIO parameter. FLAG compares these two versions of the program and creates a new version that looks like the current version except that lines inserted or modified since the baseline version are flagged. Flags consist of a user-specified string of characters placed at a user-specified location on the source line (within the range of columns 73-80), as denoted by the ID parameter.

The new flagged member can be created in a separate DDIO file with no alteration of either baseline or current members, or it can be created in the same DDIO file as the current member, in which case it replaces the current member. The baseline member is not altered, replaced, or deleted in either case. The FLAGGEDDDIO parameter is used to specify the separate DDIO file to receive the flagged members. If this parameter is omitted, the new flagged members replace the corresponding current members in the CURRDDIO file.

There are three ways to specify that DDIO members represent the baseline and the current versions of the program:

1.  Use the BASENUMBER= and CURRNUMBER= parameters to specify (by member number) which two members are to be compared. The BASENUMBER= value is the member number of the baseline version of the program in the DDIO file specified in the BASEDDIO parameter. The CURRNUMBER= value is the member number of the current version of the program in the DDIO file specified in the CURRDDIO parameter.
2.  Use the PROGRAM= parameter to specify the name of a program. FLAG locates members in the BASEDDIO and CURRDDIO files with this name, and selects the BASEDDIO member with the oldest compile date and time as the baseline member, and the CURRDDIO member with the most recent compile date and time as the current member. Members from different language families (Assembler, COBOL, PL/I, or C) are not compared, even if their program names match.
3.  Use the PROGRAM= parameter to specify a mask for a program name. The mask is 0-7 characters of a program name followed by an asterisk; for example, PROGRAM=ACC* or PROGRAM=*. FLAG uses this mask to identify matching program names, then proceeds as described in step 2.

FLAG locates all pairs of programs (one in BASEDDIO and one in CURRDDIO) of the same language family and with the same name, with a common name matching the mask. FLAG selects the program in BASEDDIO with the oldest compile date and time as the baseline member of the pair, and the one in CURRDDIO with the most recent compile date and time as the current member of the pair. FLAG then compares these two, and creates a new flagged member in the FLAGGEDDDIO file (or replaces the current member, if the FLAGGEDDDIO parameter was not specified).

Repeated Use of the FLAG Command

To ensure the most efficient use of I/O and CPU resources, FLAG does not reflag currently flagged members on subsequent runs when the FLAGGEDDDIO parameter is omitted.

Example

FLAG Report Output

FLAG printed output contains the following:

• The data set names of the BASEDDIO, CURRDDIO, and (if used) FLAGGEDDDIO data sets.
• The name, member number, etc., of the baseline, current, and (if FLAGGEDDDIO is used) flagged members.

If a program mask is used, there are potentially multiple pairs of members to display in the report. In this case, the report contains two sections that list members:

1. A Selection Report showing every pair of listings that will be compared. This list is created early in FLAG processing to ensure that it is available in the job output, even if the job is subsequently canceled.
2. An Action Report showing the actions taken with each pair of members in the Selection Report.

If you run with EXEC=SIMULATE, only the Selection Report is produced. This report can then be used to verify and approve all proposed comparisons. If necessary, you can use individual lines from the Selection Report to create separate FLAG commands that specify BASENUMBER= and CURRNUMBER= parameters in lieu of a PROGRAM= mask. Multiple FLAG commands can be entered in a single run of the CWDDSUTL utility.

Supported Compilers

FLAG supports all releases of COBOL, PL/I, and Assembler.

CA-OPTIMIZER products are not supported.

Flag Command Syntax

The following diagram illustrates the syntax for the FLAG command.

For a description of the parameters, see Command-Parameters-for-all-DDIO-files.

Example

FORMAT

The FORMAT command prepares a DDIO file for use after the file has been allocated, or it reformats an existing sequential DDIO file. The FORMAT command cannot be used to create or format databases or shared directories. See the CREATE command for instructions on creating a database or shared directory.

for more information about using these parameters and certain restrictions when setting up DDIO files, see Using-DDIO-files.

CAUTION:

The FORMAT command erases all of the information in the specified file.

The file being formatted is specified with the ABNLDFIL DD statement. The INDD parameter may be used to override the ddname.

• For BMC AMI DevX Abend-AID report files, all parameters are optional. Code a parameter only if a default will be changed.
• For source listing files, specify TYPE=SOURCE. All other parameters are optional.

• For BMC AMI DevX Abend-AID for CICS source listing files, when you are formatting system or user DSECT files, code SUBTYPE=FX. TYPE=CICS is the default when SUBTYPE=FX is specified. All other parameters are optional.

To reformat a VSAM DDIO file, you must first delete the file, and then reallocate it before formatting it again. If the size of the VSAM DDIO file must be increased, do not use IDCAMS and the REPRODUCE command to copy the file. Instead, allocate a new file, format the file, and use the COPY or MOVE commands to copy or move members from the old DDIO file to the new DDIO file. If you specify the SPEED parameter as part of the DEFINE CLUSTER command, the FORMAT command will execute faster.

FORMAT Command Sample Programs

Sample programs for the FORMAT command are available in CSS installation library members. See the following table for a list of sample JCL members that contain information on using the FORMAT command.

Sample Programs for FORMAT Command

Job also does VSAM file allocation.

FORMAT Command Syntax

The following diagram illustrates the syntax for the FORMAT command.

For description of the parameters, see Command-Parameters-for-all-DDIO-files.

Example 1:

Example 2:

IMPORT

The IMPORT command selectively restores previously exported entries from a sequential file to the specified DDIO file.

The “from” file (sequential file) can be specified using the FROMDD parameter, the FROMDSN (and optional FROMVOL) parameter, or the ABNLFROM DD statement.

The To DDIO file can be specified using both the TODSN and TOVOL parameters, or the TODD parameter. When an entry is imported to a database that is attached to a shared directory, the shared directory is also updated.

Multiple IMPORT commands can be used, if you include a unique FROMDD (or FROMDSN and FROMVOL) parameter for each input data set. If the input file is a PDS, the contributing member must also be specified. A command must be designated for each PDS member. If the input file is a PDS, the contributing member can either be specified with the DSN in the FROMDD (or ABNLFROM) DD statement, or by letting the PROGRAM= parameter also define the member name to be used with the FROMDD/ABNLFROM or FROMDSN parameter (and cannot be a wildcard or long name). See label for information on importing multiple files from tape.Since IDR token is a unique key within a Source Listing Shared Directory, it is possible to encounter a duplicate IDR condition during member IMPORT - a warning message will be issued and the member will not be imported. The remaining IMPORT processing continues with a return code of 4.

When exporting members of a shared directory with 2 or more attached databases of the same type, the import of these members will (generally) not have the same member distribution in the databases attached to the import's shared directory. To have the same member distribution in the databases you must do the export & import for each individual database.

Importing from multi-volume data sets is not supported. When importing from multi-volume data sets, the following message is issued: CXUTL3041S Error during POINT-RECORD DDIO/database operation in IMPORT RC=0000000C.

Import- Source Listing

If none of the parameters are specified, then all entries are imported. The following diagram illustrates the syntax for the IMPORT command.

The use of EXEC is only valid for stand-alone source DDIO files, not for shared directory and/or database files.

For a description of each parameter, see Command-Parameters-for-all-DDIO-files. See Shared Services SLCXCNTL installation library member CXLPIMPO for sample JCL for the IMPORT command.

Example

Import- Abend-AID

The following diagram illustrates the syntax for the IMPORT command.

The use of EXEC is only valid for stand-alone BMC AMI DevX Abend-AID report DDIO files, not for shared directory and/or database files.

For a description of the parameters see Command-Parameters-for-all-DDIO-files. See Shared Services SLCXCNTL installation library member CXAAIMPO for sample JCL for the IMPORT command.

Example

Import - Abend-AID for CICS

The following diagram illustrates the syntax for the IMPORT command.

For a description of the parameters see Command-Parameters-for-all-DDIO-files. See Shared Services SLCXCNTL installation library member CXCFIMPO for sample JCL for the IMPORT command.

Example

LOCK

The LOCK command locks selected entries of one or more specified DDIO files. While an entry is locked with this command (this is called manually locked), it cannot be automatically deleted when the DDIO file becomes full. At least one selective parameter must be specified on the LOCK command.

The scope of the LOCK command can be a single source file or report file, or a single database, or all databases attached to a specified shared directory. If you specify the DIRDD= or DIRDSN= parameter, and supply a DDname or data set name for a shared directory, the LOCK command will apply to every database attached to that shared directory. All other forms of the LOCK command apply only to one data set.

Lock - Source Listing

The following diagram illustrates the syntax for the LOCK command.

 For a description of each parameter, see Command-Parameters-for-all-DDIO-files.

Example

Lock - Abend-AID

The following diagram illustrates the syntax for the LOCK command.

For a description of the parameters see Command-Parameters-for-all-DDIO-files.

Example

Lock — Abend-AID for CICS

The following diagram illustrates the syntax for the LOCK command.

For a description of the parameters see Command-Parameters-for-all-DDIO-files.

Example

MOVE

The MOVE command copies selected entries from one DDIO file to another, and deletes them from the From file, provided they are successfully copied. Entries can be moved in any of the following ways:

• from one report file to another report file
• from one source file to another source file
• from one database to another database
• from a database to a shared directory
• from a shared directory to a database
• from one shared directory to another shared directory

You may not use MOVE to mix members of different types in a single database. The three types of members are source, BMC AMI DevX Abend-AID report, and BMC AMI DevX Abend-AID for CICS report.

Use the FROMDD and TODD parameters to specify the From and To file ddnames. When an entry is moved to or from a database, which is attached to a shared directory, the shared directory is also updated immediately. If none of the parameters are specified, then all entries are moved.

Only successfully copied entries are deleted from the From file.

Since IDR token is a unique key within a Source Listing Shared Directory, it is possible to encounter a duplicate IDR condition during member MOVE - a warning message will be issued and the member will not be moved. The remaining MOVE processing continues with a return code of 4.

The following diagram illustrates the syntax for the MOVE command.

Move - Source Listing

The following diagram illustrates the syntax for the MOVE command.