I have a space issue on AIX and I guess my job is testing the maximum AIX allocation.
My job fails on the DEFINE AIX step with the below error:
Code:
IDC1646I 15735 EXCESS PRIME KEY VALUES FOR AIX KEY 00002CF0F0F0F0F0F1F1
IDC1653I CIGL.COT.DGL.ELEC.ITEMS.AIX.MASTER BUILT WITH ERRORS
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 4
DEFINE card:
Code:
***************************** Top of Data ******************************
/* VGLT1004 */
DEF AIX -
(NAME(CIGL.COT.DGL.ELEC.ITEMS.AIX.MASTER) -
RELATE(CIGL.COT.DGL.ELEC.ITEMS.MASTER) -
MB(1000,500) -
KEYS(15 47) SPEED -
FREESPACE(2 2) -
RECORDSIZE(9620 600000) -
NONUNIQUEKEY -
UPGRADE -
SHR(2 3)) -
DATA -
(NAME(CIGL.COT.DGL.ELEC.ITEMS.AIX.DATA) -
CISZ(22528)) -
INDEX -
(NAME(CIGL.COT.DGL.ELEC.ITEMS.AIX.INDEX) -
CISZ(2048))
**************************** Bottom of Data ****************************
In the past, whenever the job failed with the above error, we increased the maximum length on the RECORDSIZE parm, but when we tried that today, the job failed again.
But with a different error:
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
Quote:
This is a failure in our production, so immediate assistance is really appreciated.
This is a forum -- if you need kind of response, you need to pay someone for support.
As your first message set indicates, the alternate index was built. If you did not do a delete before you reran the build, the alternate index name is already in the catalog and cannot be cataloged again. Hence your second error message.
Also, WHY is the alternate index not getting built? Someone did not do a good job of analysis if you have to keep expanding the alternate index record length! And, sooner or later, you'll hit the maximum at which point someone will have to completely redesign the process since the limit on primary keys in an alternate index is an absolute limit and cannot be changed.