IBM Mainframe Forum

Hi All,

My requiremtn is : I need to convert a VSAM file of key length 23 (which consists if two keys one 15 and one 8 ) to VSAM file of key length 15.

I copied teh Input VSAM to flat file an then created a new VSAM file say second with teh follwoing code:



after that i used the reproduce command to copy the flat file contents to the VSAM file created...

I could see that teh follwoing are happening:

IDC3314I **RECORD OUT OF SEQUENCE - KEY FOLLOWS:
000000 F7F0F0F0 F0F0F240 40404040 4040F2

IDC31467I MAXIMUM ERROR LIMIT REACHED.
IDC0005I NUMBER OF RECORDS PROCESSED WAS 172886
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12


Also...i could see that key is not copying correctly :

Input file sample data:



But in ouput VSAm file: i could see that


The zeroes that are present at the start of the key in flat file are not getting copied to the VSAM output file.

Am not sure why the records got copied till 172886 and stopped..

Can anyone let me know how i can copy the exact key and what is the exact issue is with the job abending after particular no of records copied to teh vsam file...?

Thanks in Advance

Nara_513 wrote:IDC31467I MAXIMUM ERROR LIMIT REACHED.
IDC0005I NUMBER OF RECORDS PROCESSED WAS 172886
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
Am not sure why the records got copied till 172886 and stopped..

Have your melamed explain to you the meaning of MAXIMUM ERROR LIMIT REACHED

As for the cause of those errors, show us the attributes -- the record format in particular -- of the unload data set.

Have you investigated the possibility that the VSAM file has a key length of 23 because the 15-byte key is not unique? Anc since the primary key on a VSAM file must be unique ....

Nara_513 wrote:

Select all

DEFINE CLUSTER (NAME(SECOND.FILE.MINDEX)     -
                INDEXED                               -
                KEYS(15 1)                             -
                SPEED                                 -
                SHR(3 3)                              -
                VOL(SYSDA)                           -
                RECORDSIZE(74 74))                    -
       DATA    (NAME(SECOND.FILE.MINDEX.DATA) -
                CYL(796 198)                            -
                CISZ(4096))                           -
       INDEX   (NAME(SECOND.FILE.MINDEX.INDEX) -
                TRK(67 17)                              -
                CISZ(1024))

The more I looked at these control cards, the more my suspicions were raised. I finally confirmed them by reading the fine manual (yes, even I need to do that on occasion). The second sub-parameter of KEYS is offset, not position. Positions begin at 1, offsets at 0. This is the cause of both your out-of-sequence errors and losing the first character of they key; change it to KEYS(15 0).

HI Akatsukani,

Hmm...I did tried first with the KEYS(15 0) ....but then also the same result...so i changed to KEYS(15 1) hoping it will work...

the record length of both the flat file and VSAM file are given correct...

Robert Sample wrote:Have you investigated the possibility that the VSAM file has a key length of 23 because the 15-byte key is not unique? Anc since the primary key on a VSAM file must be unique ....

Robert the key of length 15 is unique ...i mean their are no duplicates...

I think you have to do it again with the ( 15 0 ).

What are you using to produce the screen output with the VSAM data on it? If it is "something" displaying the Key followed by the Data, then the byte accidently created in front of the key will probably get "lost" from the display.

Defining the key incorrectly will generate "out of sequence" messages as long as the first two bytes of the "key" are not unique across the file, as long as the rest of the key is not always ascending.

Actual Key Sequence


Incorrect Key, Out of Sequence

Hi All,

I got it...!!!

Some of the records in my input file are not in sorted order...so i did a sort with the keylength 15 and i tried to run the repro...it worked...
Thanks to all who helped me in this...

I'm not so sure.

You have a KSDS with a 23 byte key, one component is 15 bytes, the other eight bytes.

You need to create a new KSDS with the same data, but this time a key of only 15 bytes, those same 15 bytes as the major part of the original key.

You copied the VSAM KSDS to a flat file.

You delete/define the new KSDS.

You then repro the flat file to the new KSDS.

You get a number of "out of sequence" messages and your repro stops.

This is what you described to us,

There is nothing anywhere in the above which will allow the data to get out of sequence.

The only way you can get the out-of-sequence messages from the repro is if, as the Honourable Akatsukami spotted, you get your key wrong,

Either something of the above is incorrect, or you now have a file which has misaligned data at best and is definitely not in the original order.

You sorted with a length of 15, what start position did you use? What did you use to copy the original KSDS to the flat file?

Hi ,

I am sure that i used the corret key of length 15
I used the normal sort step to copy the VSAM file to Flat file.

i did a sort with a duplicate removal step in extra:

and reran the repro with the sorted out file

I have checked both the input sort file and the output file, both have the same no of records...