VSAM status code 46

Sengar.80 · New User Joined: 08 Jul 2011 Posts: 10 Location: INDIA

Hi,

I am facing VSAM status code 46 in one of my programs. In the spool its saying logical error occured.

Below is the code of my program :

PERFORM START-KEY-PARA THRU START-EXIT.
MOVE 0 TO TABLE-LEN.
PERFORM LOAD-TABLE VARYING INDEX FROM 1 BY 1
UNTIL TABLE-ID > 4386 OR
TABLE-LEN > 1000.

START-KEY-PARA.

MOVE '4386 #1' TO WS-VSAM-KEY.
MOVE WS-VSAM-KEY TO T-VSAM-KEY.
START VSAM-FILE KEY IS GREATER THAN T-VSAM-KEY.

IF FILE-STAT = '00' OR '04'
NEXT SENTENCE
ELSE
IF FILE-STAT = '10' OR '23'
DISPLAY 'ERROR'.

VSAM-READ.

READ VSAM-FILE NEXT.
MOVE SPACES TO WS-VSAM-KEY.
MOVE T-VSAM-KEY TO WS-VSAM-KEY.

IF FILE-STAT = '00' OR '04'
NEXT SENTENCE
ELSE
IF FILE-STAT = '10'
DISPLAY 'ERROR'.

START-EXIT. EXIT.

LOAD-TABL.

ADD +1 TO TABLE-LEN.
IF TABLE-LEN GREATER THAN 1000
DISPLAY 'VSAM TABLE 4386 OVERFLOW'
ELSE
MOVE WS-VSAM-KEY TO WS-TABLE(INDEX).
PERFORM VSAM-READ.
LOAD-EXIT. EXIT.

In the above code, I am starting the key from '4386' and then reading the records from there onwards and uploading them into an array. It reads and loads them into the table, but when it encountered more than 4386 say 5000 from the VSAM file, it throughs Status code 46.

Thanks.

Bill Woodger · Posted: Mon Aug 08, 2011 6:54 pm

Can you please copy/paste your code, not re-write it. There are many typo's which we won't want to wade through.

Use the Code button to retain the formatting of anything that you want to retain formatting for. Use Preview to check that it looks how you want.

Robert Sample · Posted: Mon Aug 08, 2011 6:59 pm

File status 46 in the COBOL Language Reference manual is described as

Marso · Posted: Mon Aug 08, 2011 7:56 pm

Bill Woodger · Posted: Tue Aug 09, 2011 5:09 am

Sengar.80 · New User Joined: 08 Jul 2011 Posts: 10 Location: INDIA

Hi,

Sorry to all of you, I got the status code 46 not for the VSAM file, it was for a sequential file used in the same program.

I got confused after seeing status code 46, I thought its only for VSAM file and was concentrating on the START Key code in the program. Actually I forgot to code GO TO statement to terminate the para at the end of the file after READ statement for a sequential file, hence after the AT END reached it was again trying to read the record.

I resolved the issue, sorry once again.

Thanks.

Bill Woodger · Posted: Tue Aug 09, 2011 6:09 pm

Well, you will get a 46 for your VSAM.

I'm sure there is a good chance any sequential file processing has the same sort of faults.

Are you not concerned if you say 46 is VSAM only and you fixed a different file...?

Sengar.80 · New User Joined: 08 Jul 2011 Posts: 10 Location: INDIA

Hi,

Yes I got 46 for sequential file not for VSAM. The code I coded for reading the VSAM and uploading into table was correct but when it came to read a sequential file down the line in the same program, I did not handle the at end properly for sequential file.

I misunderstood that we get 46 only for VSAM, thats why only checking the VSAM code in the program neglecting the other read like sequential file.

Thanks.

Bill Woodger · Posted: Tue Aug 09, 2011 7:29 pm

Well, well. If your code is "correct" then everything is OK.

Do you want to look through what I have posted earlier?

Sengar, we explained things about your PARM question, remember? If you are still open-minded, look at your code, then tell me it is OK.

If you still think everything is fine with your code, then I wish your organisation well with your future. They might get lucky.

Sengar.80 · New User Joined: 08 Jul 2011 Posts: 10 Location: INDIA

Hi Bill,

Yes my code is correct. Only thing I did not post the actual fields naming convention on this forum as it is a company code. Example you said you can not define INDEX as index in COBOL. Thats true, I defined with some other variable but surely not INDEX. I put the code here to just tell you what I have coded.

Thanks for remebering me on the PARM stuff.

I took your code which you have pasted above for reading the VSAM file. I did a check but I could not find any fault on what you coded and mine. Both gave the same result as status code 46. You define start-key-para and then priming-read-of-vsam, then vsam-read, then load-table para. Even if you do not define priming-read-of-vsam, that also solve the same purpose. And one more thing, we can put vsam-read para inside the start-key-para and terminate with exit. And we can give start-key-para thru statements or without thru also.

The problem was not on reading and loading the data from VSAM file. The problem was with the sequential file.

Thanks.

Bill Woodger · Posted: Wed Aug 10, 2011 4:17 am

Hi Sengar80,

You have a problem you will need to overcome to post code in these forums. Unless we see the original code, what you show to us is useless. We are not (although I did) going to go chasing code full of typos.

There is a recent long discussion in the Cobol forum about "best practice". I suggest you read through all of it.

You can stick your read in the middle of a PERFORM THRU, and you can seperately PERFORM that individual paragraph. You can have an exit paragraph which is not part of a PERFORM THRU, etc. If you do this, you have a bad program, which is difficult to understand and to maintain.

For example, someone thinks the vsam read paragraph has got put there by accident (you have no other clues in the code that it should be there, like some sort of convention for ordering the paragraphs) and moves it. Now you have a subtle problem, in that the code still "works", but only mostly.

What is someone sticks a GO TO in your vsam read paragraph? It will "work" when part of the perform through, and not work when performed on its own.

What if someone codes a GO TO for the exit that is not included in a perform thru?

It is up to you. Your code in this example is not good. If you think it is, then it will be difficult for your to learn about good code, and you will continue to write bad code for much longer than is necessary.

Phrzby Phil · Posted: Wed Aug 10, 2011 6:44 am