SORT ABEND - VSAM ACCESS ERR 08058

mrgnndhmk · New User Joined: 01 Feb 2006 Posts: 51 Location: India

Hi All,

ESDS File has been defined with PRI 1000 & Sec 500 Cylinders with 160 as record length.

It contains 24,404,901 records and SORT to ESDS fails when the record count reaches 25,844,500.

CASD217E VSAM ACCESS ERR 08058

I could not get the exact reason for the RC=58 for VSAM file.

Also noticed that the file isn't moving to next volume and the volume still has enough space.

Has anybody encountered similar failure and could provide any resolution?

DEFINE CLUSTER( -
NAME(TEST.ESDS.FILE) -
FOR(9999) -
NONINDEXED -
RECORDSIZE(160 160) -
SHAREOPTIONS(2) -
SPEED) -
DATA( -
NAME(TEST.ESDS.FILE.DATA) -
CONTROLINTERVALSIZE(4096) -
CYLINDERS(1000 500) -
VOLUMES(F3105V F3104V F3103V F3102V F3101V)) -
CATALOG(UCATF31)

~Muru

Bill Woodger · Posted: Sun Dec 01, 2013 6:35 am

Can you include the full system-generated output from the JOB. Have you seen any other VSAM messages? How have you tried to find what 58 means?

Robert Sample · Posted: Sun Dec 01, 2013 9:11 am

Since you do not appear to have defined the ESDS as extended, I suspect you are hitting the 4 GB limit for a VSAM file.

mrgnndhmk · New User Joined: 01 Feb 2006 Posts: 51 Location: India

Hi Bill/Robert,

Thanks for the responses.

Other than status 58 I did not see any other VSAM messages. The status codes are given in the below link and unfortunately the link is down since 8 hours. I could not give the exact reason. As per it 58 is due to the inability of the file to grow further irrespective of whether the space is available or not. Resolution is to redefine the file and grow.

publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IESMC270/29.0?SHELF=IESVSE90&DT=20110907135057

But I am not sure how can I redefine the ESDS file with EXTEND parameter. Any generic samples would be helpful for me to try.

Is 4.3 GB limit a challenge only for ESDS and not KSDS? Because I have another KSDS file with a lot more data than this and has occupied almost 21 volumes in the catalog.

Robert Sample · Posted: Mon Dec 02, 2013 1:28 am

4 GB is a VSAM limit, not just for ESDS or KSDS. Post the LISTCAT for the KSDS file (use the Code button to preserve spacing).

mrgnndhmk · New User Joined: 01 Feb 2006 Posts: 51 Location: India

This is the exact description of the error (link is alive now)

Robert Sample · Posted: Mon Dec 02, 2013 4:01 pm

1. Unless otherwise changed, the limit for an ESDS, KSDS, or RRDS VSAM data set is 4 GB -- and your error message precisely and exactly shows that this is the problem you have.

2. IDCAMS LISTCAT and the LC you posted are completely different -- what you posted is COMPLETELY USELESS as far as diagnosis or assistance.

3. Contact your site support group for assistance in changing your ESDS definition parameters to allow it to grow past the 4 GB limit. Or you can continue posting completely useless data here and we will not be able to help you, thus delaying the resolution of your problem. The problem and its solution are now known -- implementing the solution depends upon you.

4. And if you change the CI size, you change the number of blocks per track, hence you change the number of records that can be written before hitting the 4 GB limit. This is usual and expected -- apparently to everyone but you.

mrgnndhmk · New User Joined: 01 Feb 2006 Posts: 51 Location: India

Thanks Robert for the Clarification. It is the 4 GB limit that stops copying more records. The plan is to change the ESDS to KSDS file with XXL option so that the file can accept data more than 4 GB.

P.S. Since the application is in VSE, LC provides the output in that format

Bill Woodger · Posted: Mon Dec 02, 2013 11:38 pm

Maybe LC does that, but IDCAMS LISTCAT does not, even in VSE.

Why are you not going to allow ESDS to extend beyond 4GB? If you make it a KSDS, be aware that there is a not inconsiderable overhead even in processing the data serially, as the index will be used to locate the next record, rather than the RBA.

Is it necessary that your huge ESDS has such a small data CI size?

Simply changing to KSDS will require programming changes for anything using the data.

Seems you've chosen a long way around.

mrgnndhmk · New User Joined: 01 Feb 2006 Posts: 51 Location: India

Hi Bill

There are couple of reasons why we decided to go for KSDS
1. The file is a history file for Year 2. Rest all files are KSDS and we are not sure why this file was created as ESDS
2. Only 2 Job changes are required for the VSAM change and no impact to the system

I am not very sure about making ESDS to extend. Is that going to be a system change like defining DATACLAS? Because the system does not have any extended ESDS.

It is yet to be confirmed by the system administrator. If this option is quicker than the KSDS option, we will go for it.

Thanks for the suggestions.

Bill Woodger · Posted: Tue Dec 03, 2013 12:22 am

You'll need a unique key as well for the KSDS.

Make two test files. ESDS just less than 4GB, KSDS same records (bearing in mind the key).

Read all the data on each.

Compare the resources used.

You didn't mention whether the usage is online or batch?

mrgnndhmk · New User Joined: 01 Feb 2006 Posts: 51 Location: India

Hi Bill,
Technical support also suggested to go for KSDS as beyond 4 GB, ESDS performance will not be good as it is dependent on RBA.

Since there is no major impact to the application, migrating the file to KSDS has been selected.

This is a history file and source files for these have the Keys defined. Therefore, the change is straight forward.

Thanks all for your inputs.