S0C4 x'4' abend while reading VSAM KSDS file
in [Cobol]
|
From: Anonymous on 25 Jun 2008 13:16 In article <34975204-0adf-4ec6-84d9-ae3ec3556783(a)z24g2000prf.googlegroups.com>, <vbarathee(a)gmail.com> wrote: >Hi DD > >I think you are more concerned about the enhancemnt work when it got >outsourced to us rather than the abend. None of this is a matter of concern to me. What I am curious about is how long the code had been in your hands and running before the current enhancement was requested. When was the code outsourced to you? >I have given my answer in my >previous post , as a month back we got this enhancement work. I have >posted the original code and given my test results , this wudnt be >enough to analyze the abend ? I have analysed the ABEND to the point where I offered a suggestion that stopped it from happening... comment out the ILBOWAT0 call and the ABEND no longer occurs. DD
From: vbarathee on 25 Jun 2008 13:45 Hi This job cannot be run without the wait time logic (ILBOWATO) , as i said in my initial post , " Also we have a wait time logic in the pgm which calls ILBOWAT module so that once the threshold reaches some 250,000 in MQ , all the jobs will wait for 180 secs and then it will continue writing into MQ. This program was a generic one and used by 10 split jobs running parallely in production , recently we added the VSAM file , previously the pgm had only PS file. Now the job is getting abend with S0C4 x'4' when it waits for the threshold limit and abends exactly when it tries to read the input VSAM file." Also now the program runs fine when we use the Invalid key clause in the read statement and it goes fine with the ILBOWATO module. I have tried with all posibilities as suggested by everyone , Please let me know if (Invalid key ) this would be the only reason that causes the program to abend with S0C4 and file satus 23. Thanks Barathi.V
From: Anonymous on 25 Jun 2008 14:08 In article <8b6e1e1a-db2c-4717-8c56-2f8d6254e9a7(a)i36g2000prf.googlegroups.com>, <vbarathee(a)gmail.com> wrote: [snip] >Also now the program runs fine when we use the Invalid key clause in >the read statement and it goes fine with the ILBOWATO module. Now I'm confused... why do you need help if the program runs fine? DD
From: William M. Klein on 25 Jun 2008 15:24 You have not answered which COBOL run-time libraries you are using - and if multiple ones how/where they are concatenated. (If you don't know the answer, contact your systems programmer). You have also not told us if you are making a static or dynamic call to ILBOWAT0 - and if dynamic, if you are using the DATA(24) compiler option. If you are using a currently supported IBM compiler then the statement, * By default the compiler options would be Amode(24) ,Rmode(24)and this program has used the same." Is simply IMPOSSIBLE!!! There is no way that a currently supported IBM COBOL compiler will produce AMODE(24) output. Check the AMODE of the OBJECT deck produced by your compiler BEFORE it is link-edited. Depending on what version of ILBOABN0 and the IGZ file handler you are getting, this would EASILY explain why you get a S0C4. *** My guess is that A) you have multiple COBOL run-time libraries available at run-time and/or B) you are making static calls to ILBOABN0 (and/or linking it into your load module / program-object) and C) when you add the "INVALID KEY" phrase you aren't actually DISPLAYING the status code and what record it was looking for, so, although it LOOKS like it is running successfully, it isn't actually reading all the records that you THINK it is/should. DD is correct that with the help and information that you have received from this group, IF you have the training to do the job you are trying to do, then you should be able to solve any/all of these problems. Furthermore, with the ABEND information that you first displayed, you should have been able to identify that there was a problem reading (at least one) of the records that you are trying to read. -- Bill Klein wmklein <at> ix.netcom.com <vbarathee(a)gmail.com> wrote in message news:a70e5adb-b887-40d9-a829-3a75f63aad88(a)u36g2000prf.googlegroups.com... > Hi all > > Thanks for ur suggestions and replies. > > Here are my test results and my reply to the above queries. > > * By default the compiler options would be Amode(24) ,Rmode(24)and > this program has used the same. > > * The VSAM file was defined properly with the key and able to display > the key before the VSAM read. > > * The program ran to completion successfully when the original code > was changed like below, > > READ DSCCQUEU-FILE > INVALID KEY > MOVE SPACES TO WS-MQUEUE-NAME,WS-MQ-DATE > NOT INVALID KEY > IF WS-SUCCESSFUL-IO > MOVE QUEU-QUEUE-NAME TO WS-MQUEUE-NAME > MOVE QUEU-DATE TO WS-MQ-DATE > ELSE > SET WS-ERROR-FOUND TO TRUE > MOVE WS-DSCCQUEU-STATUS TO WS-RETURN-CODE > MOVE '**3300-READ-DSCCQUEU FAILED**' > TO ERROR-MESSAGE > PERFORM 9100-PROCESS-ERROR THRU 9100-EXIT > END-IF > END-READ. > > > * Also the program ran to completion , when the code was commented > with ILBOWATO module. > > * My shop doesnt have CEE3DLY or CEEDLYM modules. > > Please let me know ur suggestions. > > Thanks, > Barathi.v
From: Anonymous on 25 Jun 2008 17:03
In article <0Yw8k.121658$qk1.41414(a)fe02.news.easynews.com>, William M. Klein <wmklein(a)nospam.netcom.com> wrote: [snip] >DD is correct that with the help and information that you have received from >this group, IF you have the training to do the job you are trying to do, then >you should be able to solve any/all of these problems. Gosh, I'd blush... were I able to remember how. It must be one of those times of day when even a broken analogue clock is right. DD |