Version 8.1.4	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, z/VM, 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 pseudodevice 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 (e.g., one Adabas block consisting of two PAM blocks or one logical track consisting of four PAM blocks).

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 in RABNs per track.

Notes:

1. This device can be used with BS2000/NK4 disk types. In these cases, all direct access database files have been defined with a standard block size which is a multiple of 2.
2. Although supported, the 2007 device is not recommended for use with Adabas. Support for the 2007 will be removed in a later Adabas release.

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.

Splitting Data Sets Across Volumes

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-2014 Software AG, Darmstadt, Germany.

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