VSAM I/O return code is 28 - RPLFDBWD = X '2908001C'

harithaganna · New User Joined: 03 Jun 2008 Posts: 14 Location: chennai

Hi,
I am getting maximum error limit reached when i am loading 56,35,000 records into a VSAM file.can you please suggest me which parameter size needs to be increased while defining the VSAM file.Whether i need to increase CIsize or secondary space?
Thanks,
Haritha

expat · Posted: Tue Jul 01, 2008 12:21 pm

What is your VSAM cluster definition ?

Please post the error messages verbatim

harithaganna · New User Joined: 03 Jun 2008 Posts: 14 Location: chennai

DEFINE CL (NAME(VST0.VSAM.FLE1) -
RECSZ(800 1409) -
VOL(* * * * * * * *) -
KEYS(08 06) -
SHR(3 3) -
BUFFERSPACE(99999999) -
SPEED -
INDEXED -
DATA (NAME(VST0.VSAM.FLE1.DATA) -
CYL(800 800) -
CISZ(30720) -
IX (NAME(VST0.VSAM.FLE1.INDEX) -
CYL(10 50) -
IMBED -
REPLIACTE -
CISZ(30720))
This is my VSAM file definition i need to load the records into this VSAM file without loosing any data.But for this definition i can able to load 29,35000 records only.
Error i am getting is:
ACTION ERROR ON VST0.VSAM.FLE1
** VSAM I/O return code is 28 - RPLFDBWD = X '2908001C'
MAXIMUM ERROR LIMIT REACHED
NUMBER OF RECORDS PROCESSED WAS 2935000.
FUNCTION TERMINATED.CONDITION CODE IS 12.
IDCAMS PROCESSING COMPLETE.MAXIMUM CONDITION CODE WAS 12.

dbzTHEdinosauer · Posted: Tue Jul 01, 2008 2:08 pm

suggest you look up the error (you can use the IBM LOOKAT site)

expat · Posted: Tue Jul 01, 2008 7:27 pm

From a quick and rough geustimation on the back of a fag packet .... I'd guess that your cluster has gone to around 6 allocations, 1 primary and 5 secondary each of 800 cyls.

Looks to me as though your disk ran out of space that was able to accomodate the 7th allocation of 800 cylinders.

When I asked for the messages that get issued, the message code itself would be appreciated, e.g. IDC3009I, IEF451I, or whatever, not just the text but the message number as well.

You should get rid of IMBED and REPLICATE, or in your case REPLIACTE, as these are no long supported unless you run an ancient version of Z/OS.

Robert Sample · Posted: Tue Jul 01, 2008 9:19 pm

I believe you're probably hitting the 4 GB limit for VSAM files. Can you do a LISTCAT on the file and determine if the EXTEND attribute is set? If not, you need to delete and define the VSAM file again, changing the parameter(s) to set the EXTEND attribute to allow the file to go past 4 GB. You're also giving WAY too big a CISIZE for your index, you have obsolete parameters (IMBED, REPLICATE), and why do you need the BUFFERSPACE? Use runtime AMP parameter to give it enough buffer space, or set BUFFERSPACE to a megabyte -- which should be enough.

If you're hitting the 4 GB limit, changing neither the CISIZE nor the secondary space will make a bit of difference. To exceed 4 GB, you must have the EXTEND attribute.