RECORD OUT OF SEQUENCE Error on VSAM file

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

Hi All,

We have VSAM KSDS file defined with below attributes:-

expat · Posted: Mon Jul 16, 2012 3:02 pm

KSDS = unique key, therefor any duplicate keys cause the problem.

PeterHolland · Posted: Mon Jul 16, 2012 3:04 pm

F0F0F0F0 F0F5F1F4 F6F2F3F0 F9F0
0000 0514 6230 90
F0F0F0F0 F0F5F1F4 F3F8F2F3 F1F7
0000 0514 3823 17

For me that is out of sequence.

Robert Sample · Posted: Mon Jul 16, 2012 3:08 pm

expat · Posted: Mon Jul 16, 2012 3:20 pm

Possibly a misconception regarding the definition of the KSDS key, using offset against actual

Anuj Dhawan · Posted: Mon Jul 16, 2012 3:24 pm

Your interpretation does not seem correct. This

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

Peter,
There are number of records between those 2 records which you have mentioned. How it will create out of sequence only for these 2 records? What about other records in between?

Anuj / Robert,
I am also getting duplicate error message sometimes. So got confused while posting. I will post about duplicate detail as well later. As of now i am concerned about out of sequence error.

This is unload step where I am copying from VSAM to flat file using IDCAMS. Please see the below step which is giving abend while unloading:-

Bill Woodger · Posted: Mon Jul 16, 2012 5:25 pm

Read what others have written to you in reply.

You cannot get that message by REPROing any VSAM file to a "flat"/QSAM/PS file,

Look at the error message.

Now, show the messages output from the step you have having a problem with. Unless your "wrapper" program is doing something, the step is NOT abending.

Why would you feel that the presence of intervening records would argue that the data you have shown is not out of sequence anyway.

I think you need to start again. Forget everything you "know" and look at outputs to understand what is happening. You certainly do know "know" which command is failing,

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

Bill,

I am really getting that error message by REPROing VSAM to flat file. The IDCAMS step which I have shown above is from a production job itself. Sometimes job will run without any issues. and is abending only when there are out of sequence records. Could you please tell me where exactly I am wrong.

Expat,
what is misconception you are referring? I didnt understand.

Regards,
Chetan

Robert Sample · Posted: Mon Jul 16, 2012 7:15 pm

Are you running on a z/OS machine or something else like an AS/400?

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

yes.. Its z/OS machine only..

dick scherrer · Posted: Mon Jul 16, 2012 9:16 pm

Hello,

Suggest you start over as your posts are confusing at best. . .

Why a REPLACE when creating an output sequential file?

Why mention duplicates, when the error is an out of sequence?

Suggest you use your sort product and copy the vasm data to a sequential file. Then look at this sequential file for the keys identified in the error. Look at the records immediately before and after the problem records. . .

Post what you find.

expat · Posted: Mon Jul 16, 2012 9:21 pm

It seems that you are not using NATIVE IDCAMS, what product are you actually using here where you need to specify IDCAMS as a parm value.

vasanthkumarhb · Posted: Tue Jul 17, 2012 2:07 am

I assume there may be one or morel steps involved in your job. This is 100% due to VSAM key is not in ascending order.

do a test as below

1. load VSAM file with sorted sequential file .
2. Then used IDCAMS repro VSAM file to any GDG dataset or flat dataset needed.

Also check your key should be KEY(14,0). Please note that unloading VSAM file to any flat file doesn't give sequence error or duplication error.

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

expat,
Even with NATIVE IDCAMS also I am getting same error. That ADUT515 is just a utility which will use IDCAMS.

Yesterday, when I was getting out of sequence, I have sorted the file using data component and loaded that data to VSAM file using delete define command. Today same job abended with duplicate record error. Please see below:-

expat · Posted: Tue Jul 17, 2012 11:35 am

When you sort the file to remove duplicates, please show the sort card used in that job

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

Vasanth,

Yes.. there are more steps in my job. This is what it doing:-
Step1: Copy VSAM fiel to flat file using REPRO.
Step2: Process the flat file and create o/p file out of it.
Step 3: Delete and Define the VSAM.
Step 4: Load data from o/p of step 2 to VSAM file using REPRO (with REPLACE option).

Regards,
Chetan

PeterHolland · Posted: Tue Jul 17, 2012 12:16 pm

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

1. I have used data component to copy to flat file from VSAM (without REPLACE option):
This I have already posted in previous posts.

2. Using SYNCSORT removed duplicates from above file

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

Peter,

Even VERIFY is throwing same duplicate error message. Please see below:-

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

Please see the below is LISTCAT o/p as well. File was not being used when taking LISTCAT output:

PeterHolland · Posted: Tue Jul 17, 2012 3:01 pm

chetanambi · New User Joined: 21 Jan 2012 Posts: 58 Location: India

Peter,

I have looked into "VSAM Demystified" and if you see my previous messages I am doing the same 4 steps they have mentioned to correct corrupted index. But we are getting same abend occurs after few days or weeks or months.
For recovering the index:
– Use the REPRO Command to copy just the data component of the KSDS
to a sequential data set. Specify the data component name (not the
Cluster Name) in the REPRO INFILE parameter.
– Sort the sequential data set by key.
– DELETE and reDEFINE the damaged Cluster.
– REPRO from the Sorted Sequential File to the newly defined Cluster.
Record Management will rebuild the Index Component.

But I have noticed one thing in step 1 that it is copying upto the record which is causing the issue. Thru LISTCAT i found that its having 211310 records. But step 1 is copying only 202317 (and still thows return code 156).

My question is VSAM KSDS should not have out of sequence or duplicate records. rite? Why is this happening? How to avoid this?

Thanks,
Chetan

PeterHolland · Posted: Tue Jul 17, 2012 4:03 pm

Bill Woodger · Posted: Tue Jul 17, 2012 4:36 pm

I think Peter is spot on.

I've never seen anything like that, but something is trashing your KSDS such that the index is obtaining records out-of-sequence, at least on serial processing.

This explains how REPRO to a QSAM file gets your message, athough I never realised you could get that message from a sequence error on the input dataset.

Obviously you have a serious problem which may involve loss of data. As Peter suggests, check the KSDS after each completed use to find which particular program/s might be to blame and then get into that/those and find out what is going on.

Anything with Assembler accessing the KSDS? Especially if doing anything "clever"?

Just for marking something off, have you tried IDCAMS with EXEC PGM=IDCAMS rather than the "wrapper"?

VERIFY seems to spot the error, so you could try that, although I think I'd go for the REPRO as you know for certain it catches "something".

Good luck. Let us know the resolution please, as it increases our knowledge and may help someone with a similar problem in the future.

If you have more questions, someone'll be here.

Get your support/techies onto this immediately, make sure your boss is aware, there could be very serious implications. Review fault-reporting system for things which might relate to missing data or wrong data.