I have a customer who recently upgraded from Adabas v742 to v744.
They are experiencing an “interesting” situation with DASD that has
caused me to chase z/os control blocks. Following is the VTOC for a
small multi-volume test Associator spread over two volumes. Note
SEQNO 1 and 2, their LOW(C-H) and HIGH(C-H). Below that is a clip
from ADAEND showing some activity on the two volumes. Next is the
display of the DEB for the Associator during an execution under
Adabas 742. Note the two extents and their cylinder locations.
Finally is the display of the same Associator DEB during an execution
under Adabas 744. Note the single extent only for the first volume.
Was there a change to the way Adabas opens datasets between v742 and
v744 that would cause this difference?
Regards,
Jon Hudson
Hudson Consulting Services
---------------DATA SET NAME---------------- SER NO SEQNO
GSA.DBID744.ASSOR1 GSW001 1
SMS.IND LRECL KEYLEN INITIAL ALLOC 2ND ALLOC EXTEND
2544 CYLS 0
EXTENTS NO LOW(C-H) HIGH(C-H)
0 363 0 422 14
---------------DATA SET NAME---------------- SER NO SEQNO
GSA.DBID744.ASSOR1 GSW001 2
SMS.IND LRECL KEYLEN INITIAL ALLOC 2ND ALLOC EXTEND
2544 CYLS 0
EXTENTS NO LOW(C-H) HIGH(C-H)
0 703 0 742 14
Vol-ser High RABN Count
GSW001 (ASSO 16182) 113
GSW002 (ASSO 26082) 4
GSW004 (DATA 23240) 171
GSW002 (DATA 35240) 0
TOTAL 288
Ada742 ASSOR1 DEB:
Address Offset +0 +4 +8 +C
007C1CEC 00000000 037DDB08 027C1BF0 487C6928 0F001100
007C1CFC 00000010 02000000 FF000000 8F132040 047C1CC8
007C1D0C 00000020 107ACA68 0000016B 000001A6 000E0384
007C1D1C 00000030 107ACB08 000002BF 000002E6 000E0258
Ada744 ASSOR1 DEB:
Address Offset +0 +4 +8 +C
007C4D04 00000000 007DCB58 107B0BF0 48000000 0F001100
007C4D14 00000010 01000000 FF000000 8F13B000 047C4CE0
007C4D24 00000020 107ACA68 0000016B 000001A6 000E0384
007C4D34 00000030 00010002 00000000 00000000 00000000