MVSFORUMS.com :: View topic - vsam error code 28

through

[^/[Print]\]

MVSFORUMS.com -> Data Management

#1: vsam error code 28 Author: suma,

Posted: Tue Mar 31, 2009 4:10 am
—
I am getting following error message while building an alternate index file...Please let me know why I am getting this type of error and What is the solution?

.KWIK-LOAD VSAM ALTERNATE INDEX BUILD - RELEASE 3.3 DATE: 03/28/09 T
. BLDINDEX INFILE=INFILE,OUTFILE=OUTFILE1, X
. AIXKEY=(12,10)
.AXS06 - UNABLE TO EXECUTE VSAM WRITE. VSAM RETURN CODE = 28
.AXS05 - UNABLE TO SORT AIX WORK RECORDS. SORT RETURN CODE = 0
.AXI02 - ALTERNATE INDEX WAS NOT BUILT DUE TO ERRORS. CONDITION CODE = 12
.AXI17 - KWIK-LOAD PROCESSING IS COMPLETED. MAXIMUM CONDITION CODE = 12

Thanks
Suma

#2: Author: expat, Location: Welsh Wales

Posted: Tue Mar 31, 2009 6:06 am
—
As you are not using IDCAMS to do this, then I suggest that you read the product documentation to find out.

#3: Author: Anuj Dhawan, Location: Mumbai,India

Posted: Tue Mar 31, 2009 7:01 am
—
Hi,

This beacomes a site specific topic now - may be searching the "utlility" under ISRDDN can tell what is executing in Back-end, we might take it from there . . .

#4: Author: RonB, Location: Orlando, FL

Posted: Tue Mar 31, 2009 9:04 am
—
VSAM return code 28 "may" indicate that you didn't allocate enough space for the Alternate Index, or that the dataset could not be extended on the volume that was allocated.

#5: Author: kolusu, Location: San Jose

Posted: Tue Mar 31, 2009 11:07 am
—
suma,

The complete description of the error 28 is

Code:

28
Data set cannot be extended because VSAM cannot allocate additional direct-access storage space. Either there is not enough space left to make the secondary allocation request, you attempted to increase the size of a data set while processing with SHROPT=4 and DISP=SHR, or the index CI is not large enough to hold the entire CA. This error could also be due to a data set trying to extend beyond 4GB on a system that does not support extended addressability.

Kolusu

#6: Author: suma,

Posted: Wed Apr 01, 2009 4:47 am
—
Thaks Kolusu,

As part of solution I have changed the TRACKS from (17000 1700) to (18000 1800)in define cluster.
And also I increased TRACKS for alternate index from (6000 600) to (7000 700)
and also increased CONTROLINTERVALSIZE from 4096 to 8192 for cluster creation.

After all these changes my job worked fine but I have confusion whether I need to change the CONTROLINTERVALSIZE for alternate index also. Please help.

DEFINE CLUSTER
(NAME(vsam.cluster)
INDEXED
TRACKS(18000 1800)
VOLUMES(vOl5)
BUFFERSPACE(11264)
NOWRITECHECK
NOREUSE
SHAREOPTIONS(3 3))
DATA(NAME(vsam.cluster.DATA)
KEYS(9 1)
/* Y2K RECORDSIZE(120 152) */
RECORDSIZE(122 156)
CONTROLINTERVALSIZE(8192)
FREESPACE(0 0)
SPEED)
INDEX(NAME(vsam.cluster.INDEX)
CONTROLINTERVALSIZE(4096))

DEFINE ALTERNATEINDEX
(NAME(vsam.cluster.AIX1)
RELATE(vsam.cluster)
TRACKS(7000 700)
VOLUMES(vol5)
SHAREOPTIONS(3 3)

NONUNIQUEKEY
UPGRADE)
DATA(NAME(vsam.cluster.AIX1.DATA)
KEYS(12 10)
RECORDSIZE(26 24576)
CONTROLINTERVALSIZE(8492)
FREESPACE(0 0))
INDEX(NAME(vsam.cluster.AIX1.INDEX)
CONTROLINTERVALSIZE(8492))
DEFINE PATH
(NAME(vsam.cluster.PATH1)
PATHENTRY(vsam.cluster.AIX1))

Thanks
Suma

MVSFORUMS.com -> Data Management

output generated using printer-friendly topic mod. All times are GMT - 5 Hours

Page 1 of 1