Version 8.1.4	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

This section provides information for the following device- and system file-related topics:

• installing on fixed-block addressing (FBA) devices;

• defining new devices; and

• changing defaults for sequential files.

• Supported z/VSE Device Types

• FBA Devices

• ECKD Devices

• Adding New Devices

• User ZAPs to Change Logical Units

Supported z/VSE Device Types

The standard characteristics of the device types supported by Adabas are summarized in the following table. The Adabas block sizes and RABNs per track are provided for each component for each device type.

Notes:

1. The 8350, 838n, and 839n are pseudo-device types physically contained on a 3350, 3380, and 3390 device, respectively, but for which some or all of the standard block sizes are larger.
2. The IBM RAMAC 9394 emulates devices 3390 Model 3, 3380 Model K, or 9345 Model 2.

FBA Devices

Adabas Version 8.1 users must install three zaps before defining files on FBA devices. The zap numbers vary by 8.1 release and can be found in the Knowledge Center in Software AG's Empower (https://empower.softwareag.com) web site. For more information about applying zaps, read Applying Zaps.

• For Adabas Version 8.1.2, install zaps AD812064, AD812065, and AD812066.

• For Adabas Version 8.1.3, install zaps AD813034, AD813035, and AD813036.

• For Adabas Version 8.1.4, install zaps AD814004, AD814005, and AD814006.

All device definitions for Adabas control statements for FBA disks should specify one of the following devices types:

• FBA SCSI devices: Specify a device type of 1512.

• Virtual FBA devices: Specify device types of 5121, 5122, or 5123.

Note:
Virtual FBA devices are not permanent and are, therefore, only suitable for holding temporary or work data sets.

Choose a device type based on the block sizes given in the following tables:

SCSI Device Types:

Virtual FBA Device Types:

The pseudo-cylinder for each of these devices has a different number of blocks as described below:

• 1512 cylinder = FBA blocks/777

• 5121 cylinder = FBA blocks/960

• 5122 cylinder = FBA blocks/960

• 5123 cylinder = FBA blocks/960

The size definitions for FBA devices on Adabas control statements can specify the number of pseudo-cylinders or the number of Adabas blocks (RABNs).

Make sure that the starting block and the number of FBA blocks on the z/VSE EXTENT statement are on an FBA pseudo-cylinder boundary, which is based on the device as specified above for each Adabas file comprising the database:

• An SCSI pseudo-cylinder (device type 1512) comprises 777 elements of 512 bytes each, or 388K per pseudo-cylinder. For example, an EXTENT entry for a ten cylinder SCSI device might consist of:

  // EXTENT SYS123,,,,777,7770

• A virtual FBA pseudo-cylinder comprises 960 elements of 512 bytes each, or 480K per pseudo-cylinder. For example, an EXTENT entry for a ten cylinder virtual FBA device might consist of:

  // EXTENT SYS123,,,,512,5120

ECKD Devices

Adabas supports ECKD DASD devices such as the IBM 3390 with the 3990 controller and ESCON channels.

During an open operation, ADAIOR determines which DASD device types are being used for the ASSO, DATA, WORK, SORT, and TEMP data sets. At that time, Adabas issues an informational message for each Adabas database component, where type is the component:

ADA164 ... FILE DDtype HAS BEEN OPENED IN ckd/eckd MODE - RABN SIZE rabn-size

Note:
Software AG strongly recommends that you avoid mixing ECKD and CKD extents within a file, because the file will be opened only in CKD mode. Mixing extents could degrade performance when file I/O operations are performed.

Adding New Devices

Support for new device types that include user-defined block sizes can be implemented in ADAIOR by modifying one of the table of device-constant entries (TDCEs) reserved for this purpose.

A TDCE is X'40' bytes long and the first free TDCE can be identified by X'0000' in its first two bytes (TDCDT).

For Adabas Version 8.1, TDCE entries are in the ADAIOS CSECT TDCON, which corresponds to ESDID 1EC in object module IOSVSE.OBJ. The first TDCE entry is at offset X‘19398' into IOSVSE.OBJ; the first free TDCE entry is at offset X‘19898'.

This information is valuable when adding an additional TDCE entry, and when zapping the object module and relinking ADAIOS under z/VSE.

The z/VSE MSHP control statements to add a TDCE entry at the first free entry thus take the form:

// EXEC MSHP
CORRECT 9001-ADA-00-vrs :AD99998
AFFECTS MODULE=IOSVSE,ESDID=1EC
ALTER 19898 0000 : nnnn
ALTER 1989A 0000 : nnnn
.
. (etc.)
.
INVOLVES LINK=LNKIOS
/*

• Information to be Zapped into the First Free ADAIOR TDCE

• General Rules for Defining Device Block Sizes

• Using 3480/3490 Tape Cartridge Compression (IDRC)

Information to be Zapped into the First Free ADAIOR TDCE

The information in the following tables must be zapped into the first free TDCE. The rules described in the section General Rules for Defining Device Block Sizes must be followed when changing the TDCE.

Note:
One or more z/VSE codes for identifying the device type: PUB device type from PUBDEVTY (refer to the IBM MAPDEVTY macro).

General Rules for Defining Device Block Sizes

The following general rules must be followed when defining Adabas device block sizes:

• All block sizes must be multiples of 4.

• A single block cannot be split between tracks (that is, the block size must be less than or equal to the track size).

Block Rules for ASSO/DATA

The following rules are applicable for Associator and Data Storage:

• Associator block size must be greater than one-fourth the size of the largest FDT, and should be large enough to accept definitions in the various administrative blocks (RABN 1 - 30) and in the FCB;

• The block sizes for Associator and Data Storage should be a multiple of 256, less four bytes (for example, 1020) to save Adabas buffer pool space.

• The Associator and Data Storage block sizes must be at least 32 less than the sequential block size.

• Data Storage block size must be greater than: (maximum compressed record length + 10 + padding bytes).

Block Rule for WORK

The following rule is applicable for Work::

• The Work block size must be greater than either (maximum compressed record length + 110) or (Associator block size + 110), whichever is greater.

Block Rules for TEMP/SORT

The following rules are applicable for TEMP and SORT:

• Block sizes for TEMP and SORT must be greater than the block sizes for Data Storage.

• If ADAM direct addressing is used:

  size > (maximum compressed record length + ADAM record length + 24);
  size > 277 (maximum descriptor length + 24)

TEMP and SORT are generally read and written sequentially; therefore, the larger the TEMP/SORT block size, the better.

Block Rule for PLOG or SIBA

The following rules are applicable for PLOG and SIBA:

• The PLOG or SIBA block size must be greater than either (maximum compressed record length + 110) or (Associator block size + 110), whichever is greater.

• It is also recommended that PLOG/SIBA be defined larger than the largest Data Storage block size. This avoids increased I/O caused by splitting Data Storage blocks during online ADASAV operations.

  The block size (BLKSIZE) of a sequential file is determined as follows:

  if PTTF(JCL) then BLKSIZE is taken from file assignment statement or label;
  if PTTMBS > 0 then BLKSIZE = PTTMBS;
  if PTTMBS = 0 then
  if tape then BLKSIZE = 32760;
  else BLKSIZE = TDCMSBS;
  else if BLKSIZE in file assignment statement or label then use it;
  if PTTF(OUT) then
  if QBLKSIZE > 0 then BLKSIZE = QBLKSIZE;
  if tape then BLKSIZE = 32760;
  else BLKSIZE = TDCMSBS;
  else error.
  

  Note:
  QBLKSIZE is an ADARUN parameter.

Using 3480/3490 Tape Cartridge Compression (IDRC)

The use of hardware compression (IDRC) is not recommended for protection log files. The ADARES BACKOUT function will run much longer when processing compressed data. Also, the BACKOUT function is not supported for compressed data.

User ZAPs to Change Logical Units

The specified zaps should be added to the module IOSVSE / phase ADAIOS, not to the specified utility.

PTT entries are in the ADAIOS CSECT I_PTT. The first PTT entry is at offset 0 into CSECT I_PTT.

When zapping the object module and relinking ADAIOS, note that the ADAIOS CSECT I_PTT corresponds to ESDID 000D in object module IOSVSE.OBJ. The offset of CSECT I_PTT into IOSVSE.OBJ is X'1000'.

www.softwareag.com

Copyright © 1971-2014 Software AG, Darmstadt, Germany.

SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT