Batch File Utility CWDDALLU

This section describes the CWDDALLU batch file utility program, used to manage BMC AMI data sets that contain either source listings, or reports created by BMC AMI DevX Abend-AID or BMC AMI DevX Abend-AID for CICS. The single utility program CWDDALLU can perform any function previously performed by the separate BMC AMI utilities CWAASDUT, CWDDLPUT, CWDDSUTL and CWFXSDUT. All four of these previous utilities remain available, however; there is no need to modify any existing JCL.

When using the older utilities CWAASDUT, CWDDLPUT, CWDDSUTL, and CWFXSDUT, you must know which kind of BMC AMI file you are processing. Each of the four utilities is appropriate only for certain types. In most cases, you can use CWDDALLU with any BMC AMI file. CWDDALLU will determine the file type and route your request to the appropriate utility code.

The four older utilities determine the file type of the data set you are using automatically and reroute your request to the appropriate utility without generating any error or warning-level return code. For example, if you invoke CWDDLPUT, which is suitable only for source listing files, but the file you are addressing is an BMC AMI DevX Abend-AID report shared directory, CWDDLPUT will reroute your request to CWAASDUT.

For more information on the other four batch utilities, see Batch-utilities in the Using-DDIO-files section.

When you must declare a file type to CWDDALLU

When you use one of the older utilities, CWAASDUT, CWDDLPUT or CWFXSDUT, the choice of utility indicates the type of data set you want to use. In terms of a TYPE= parameter, the implied type is:

• CWAASDUT: TYPE=AA
• CWDDLPUT: TYPE=SOURCE
• CWFXSDUT: TYPE=CICS

When you use CWDDSUTL against a plain source file or report file, there is never a need for a TYPE= specification, because an individual source file or report file can contain only one kind of data.

When you invoke CWDDALLU, which is capable of handling any type of data, you will have to add a TYPE= specification to indicate which data type you want to handle. When a utility command refers to an existing data set that contains only one type of data, CWDDALLU needs no TYPE= parameter, because the type is indicated from examining the data set. This leaves two situations in which you need to specify TYPE=.

1. The command does not refer to any existing data set.

   1. The two commands of this type are:
      • 
        
        • 
          
          • CREATE
          • ESTIMATE

   For these two commands, if you invoke CWDDALLU by name, you must supply a TYPE= parameter. However, if the OBJect parameter of the CREATE command specifies either SHRDIR or DBMODEL, the TYPE= parameter is not required.

2. The existing data set contains multiple data types.
   Only a shared directory can contain multiple data types, and the only two possible types are TYPE=AA (for BMC AMI DevX Abend-AID reports) and TYPE=CICS (for BMC AMI DevX Abend-AID for CICS reports). If you direct a utility command to a shared directory that contains both these types, you will need to specify TYPE=AA or TYPE=CICS. The commands to which this can apply are:
   • COPY
   • DELETE
   • DIR
   • DIRI
   • DIRX
   • EXAMINE
   • EXPORT
   • LOCK
   • MOVE
   • VERIFY
   • UNLOCK

Again, the TYPE= parameter is required for these commands 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 direct the utility command to CWDDALLU directly, via a JCL entry reading EXEC PGM=CWDDALLU.

File Structures

There are seven kinds of files that can be modified by CWDDALLU:

1. Report Files - these files contain abend reports produced by BMC AMI DevX Abend-AID.
2. Source Files - these files contain program listings processed by a BMC AMI Language Processor.
3. Transaction Databases - these files contain transaction abend reports produced by BMC AMI DevX Abend-AID for CICS.
4. Report Databases - these files contain abend reports produced by BMC AMI DevX Abend-AID.
5. Source Listing Databases - these files contain program listings produced by a BMC AMI Language Processor.
6. Report Shared Directories - these are catalogs of Report and/or Transaction Databases.
7. Source Listing Shared Directories - these are catalogs of Source Listing Databases.

A Shared Directory is a catalog of databases. The databases included are attached to the shared directory. A shared directory contains only a list of attached databases, and a combined index of all the individual items contained in any attached database. It does not contain actual report or source listing data.

Databases are distinguished from Files by being structured to permit attaching the databases to a Shared Directory. A Source File is a standalone file containing source listings processed by a BMC AMI Language Processor. It cannot be attached to a source shared directory. A Source Database is similar, but with the additional possibility of attaching the source database to a source shared directory.

Attaching databases to a shared directory makes it possible to efficiently scan multiple databases for a desired member. Long Program Name (LONGNAME) compiler support for C, VisualAge PL/I, and Enterprise PL/I must utilize Source Listing shared directory processing for member names greater than eight characters. We recommend using databases and shared directories, instead of the standalone source files and report files.

Throughout this section, the term entry or member refers to a program source listing in a source file or database, or to an individual abend report, created by BMC AMI DevX Abend-AID or BMC AMI DevX Abend-AID for CICS, in a report file or report database.

The term DDIO file refers to any of the seven types of files described above. DDIO is a proprietary BMC AMI access method.

This section provides information about the following topics: