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

The standard characteristics of the device types supported by Adabas in environments under the z/OS, z/VSE, and BS2000 operating systems are summarized here.

• Supported z/OS and z/VM Device Types

• Supported z/VSE Device Types

• BS2000 Device Types and Block Sizes

Supported z/OS and z/VM Device Types

The standard characteristics of the device types supported by Adabas on z/OS and z/VM are summarized in the following table. Adabas block sizes and RABNs per track are provided for each Adabas 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 number of tracks per cylinder listed here is artificial.
3. The IBM RAMAC 9394 emulates devices 3390 Model 3, 3380 Model K, or 9345 Model 2.

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.

BS2000 Device Types and Block Sizes

The primary access method for direct access data sets used by Adabas under BS2000 is PAM (primary access method). The device types defined by Adabas establish a logical structure on a PAM data set in order to process a fixed number of consecutive PAM blocks. For example, for device 2300, one ASSO RABN (Adabas block) consists of two PAM blocks and one logical track consisting of four RABNs.

These device types are “artificial”; there is no relation to the physical devices being used. A maximum of 16 PAM blocks per track can be combined into one I/O call. For more than 16 PAM blocks per track, parameter chaining is used.

The artificial device types defined by Software AG for BS2000 systems are summarized in the following table. The ASSO, DATA, WORK, PLOG, CLOG, and TEMP/SORT/DSIM block sizes are given with PAMs/RABN and RABNs per track.

Notes:

1. The PAM Pages per Cyl (PAM pages per cylinder) column shows how many PAM pages are allocated per cylinder (for example, in an ADAFRM utility where the size does not have the suffix "B").
2. Generally, NK4-compatible containers should have an even number in the RABN STD block size.
3. 4K-rounded devices need RABN block sizes to be an exact multiple of 4K bytes. These are usually used with D3475-8F devices. When such devices are shared with UNIX machines, this is the case. Otherwise, the user can apply the optional zap AY824052 to avoid the error message: ADAAI6Y file: DDASSOR1, Device-Type 8f extension needs DEVICE=23xx
4. Support for 2001, 2003, 2004, 2007 and 2009 devices has been removed from this release onwards. Please contact Software AG if there is a problem with this.
5. This device can be added in Adabas 8.2 SP5 using zap AB825003.

If the current database device is not of a compatible type for NK4 disks and it is necessary to migrate it to those disks, you must use the ADAORD RESTRUCTUREDB utility as described in Adabas Utilities.

Container Size Calculation

To calculate the size of a container in PAM pages, take the number of RABNs for the container and multiply it by the RABN STD block size.

To check your container file, multiply the highest RABN from the ADAREP utility by the RABN STD block size, and compare it with the HIGH-US-PA field of the SHOW-FILE-ATTRIBUTES file-name,ALL command output. If the HIGH-US-PA field is less than the highest PAM page calculated from the ADAREP, you will receive a DMS0922 error from the operating system when accessing this.

Splitting Data Sets Across Volumes

In Adabas 8.2 and later versions, I/O is performed, wherever possible, in track units (see the "PAM Pages per Track" column in the device table earlier in this section). This unit is only a logical unit on this platform and is not associated with the number of PAM pages that the system allocates. If the container is to be increased onto another volume, the number of blocks allocated will be rounded automatically to the "PAM Pages per Track" value.

For private volumes, splitting is possible under every LOGON user ID:

In ISP format:

/FILE data-set,DEVICE=D3480,VOLUME=PRIV01,SPACE=60000
/FILE data-set,DEVICE=D3480,VOLUME=PRIV02,SPACE=60000

In SDF format:

/CREATE-FILE data-set,PRIV-DISK(SPACE=(60000),VOLUME=PRIV01)
/MOD-FILE-ATTR data-set,PROT=(USER-ACC=*ALL)
/MOD-FILE-ATTR data-set,SUP=PRIV-DISK(SPACE=(60000),VOLUME=PRIV02)

For public volumes, the splitting is possible under every LOGON user ID if the master catalog entry of the pubset has the attribute:

PHYSICAL-ALLOCATION=USER-ALLOWED

This attribute is set by issuing the following command under TSOS:

/MOD-MASTER-CAT CAT-ID=ABC,PHYSICAL-ALLOCATION=USER-ALLOWED

Once this attribute is set, it is possible to split a data set across two or more public volumes under any LOGON user ID that has the right of space allocation on that particular pubset.

In ISP format:

/FILE data-set,VOLUME=ABC.00,DEVICE=D3480,SPACE=60000
/FILE data-set,VOLUME=ABC.01,DEVICE=D3480,SPACE=60000

In SDF format:

/CREATE-FILE data-set,PUB(SPACE=(60000),VOLUME=ABC.00)
/MOD-FILE-ATTR data-set,PROT=(USER-ACC=*ALL)
/MOD-FILE-ATTR data-set,SUP=PUB(SPACE=(60000),VOLUME=ABC.01)

At this point, even a particular physical allocation can be made.

In ISP format:

/FILE data-set,VOLUME=ABC.02,DEVICE=D3480,SPACE=(20002,60000,ABS)

In SDF format (following the CREATE-FILE and MOD-FILE_ATTR...PROT specifications listed earlier):

/MOD-FILE-ATTR data-set,SUP=PUB(SPACE=ABSOLUTE(20002,60000),VOLUME=ABC.02)

The example extent covers physical PAM pages 20002 through 80001 on volume ABC.02. The required disk space must, of course, be available. If you are unsure of the available disk space, consult your system administrator.

Saving the Extent List of Data Sets

The utility ADAR2E converts the extent list of given data sets into a JOB containing /CREATE-FILE commands. For more information, see the section on the ADAR2E utility in the Adabas Utilities documentation.

www.softwareag.com

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

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