Functional Overview

#### Search Results

Search

# Functional Overview

The ADAZIN utility can be used to print maintenance information about Adabas load modules and status information about the Adabas SVC on the system in which ADAZIN is run. Names of target load modules and SVC numbers can be specified to the utility to limit the range of the printed report.

Module information in the ADAZIN report includes:

- The load module name.

  Note
  Some delivered load modules such as non-executable data modules, CICS modules with a CICS-mandated prefix, non-assembly language programs, subroutines and sample programs that cannot have regular maintenance applied to them are excluded from the report.

- CSECT names (if appropriate)

- The date the module was last compiled

- The Adabas version and release of the module

- The number of the library from which the module was loaded within the concatenation list

- A list of zap numbers applied to the module for the zap base level.

ADAZIN processing varies by operating system, as described in the following sections:

- z/OS Usage Notes and Processing

- BS2000 Usage Notes and Processing

- z/VSE Usage Notes and Processing

## z/OS Usage Notes and Processing

In z/OS environments, the Adabas modules that ADAZIN reviews for the report reside in a load library (or concatenation of load libraries) defined through one of the following job control statements in the ADAZIN batch job:

- DDZIN

- STEPLIB (if no DDZIN job control statement exists in the job)

It is important that the library where ADAZIN itself resides is APF-authorized, because ADAZIN processing behaves differently if it is not:

- If the ADAZIN library is APF-authorized, then ADAZIN can load into memory any module, regardless of whether the module is already loaded in memory (possibly another version from a different load library). z/OS allows this only for APF-authorized programs.

  For example, suppose that module ADAIOR is in library X referred by DDZIN and we want to check its version and zap status. In addition, module ADAIOR is in library Y referred by the STEPLIB (where ADAZIN itself also resides). If library Y is APF-authorized, then ADAZIN will load ADAIOR from library X, regardless of the fact that ADAIOR already exists in memory, loaded from library Y. ADAZIN, in this case, will report the status of module ADAIOR from library X.

- If ADAZIN library is not APF-authorized, then z/OS cannot load into memory modules with names that match the names of modules it has already loaded into memory. So, in the example in the previous bullet, ADAZIN can never report on the ADAIOR module from library X, because it already has ADAIOR loaded from library Y. In this case, it will always report the ADAIOR status from library Y.

In addition to the module information, ADAZIN provides similar status information for the Adabas SVCs, according to the SVC or SVCRANGE parameters.

## BS2000 Usage Notes and Processing

In BS2000 environments, ADAZIN uses the BLSLIB chain. Loading modules from the DDZIN link name is not supported.

In addition to the module information, ADAZIN provides similar status information for the Adabas ID tables, except when the NOIDT parameter is specified.

Status information is available concerning the router. The SVC and SVCRANGE parameters are ignored in BS2000 environments.

## z/VSE Usage Notes and Processing

In z/VSE environments, ADAZIN uses the LIBDEF PHASE search chain to identify the libraries from which modules will be loaded. Loading modules from a library associated with DLBL DDZIN is not supported.

There is no support for providing SVC status information on z/VSE. The SVC and SVCRANGE parameters are ignored in z/VSE environments.

### On this page

- z/OS Usage Notes and Processing
- BS2000 Usage Notes and Processing
- z/VSE Usage Notes and Processing