S0C4 error in ASM JCL



High Level Assembler(HLASM) for MVS & VM & VSE

Re: S0C4 error in ASM JCL

Postby shagnwrx » Wed Sep 03, 2008 3:14 am

This almost sounds like a random data problem. We had a problem with random S0C4's and Storage Violations when using Xpediter on programs of ours that moved large variable length records. Here's why ours were so random:

With the latest release of Enterprise COBOL 3.4, the limit of working with fields greater than 16k bytes was lifted. The variable data we were using would only "break" Xpediter if the record being processed on THAT particular run through the code was over 16k bytes. Xpediter could only store the data lengths in a halfword area. They changed it to a full word and it resolved our problems.

Now with that in mind, Is it possible that the COBOL program could be trying to reference large records or fields like this, and perhaps trying to pass it to the ASM program?
shagnwrx
 
Posts: 3
Joined: Wed Sep 03, 2008 2:29 am
Has thanked: 0 time
Been thanked: 0 time

Re: Re: S0C4 error in ASM JCL

 

Re: S0C4 error in ASM JCL

Postby dick scherrer » Wed Sep 03, 2008 5:29 am

Hello and welcome to the forums,

Is it possible that the COBOL program could be trying to reference large records or fields like this
Possibly, but i would hope that the same "large records" would cause the same problem on the re-run.

I'm still leery of the link on the abended runs. . . :|
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Previous

Return to Assembler

 


  • Related topics
    Replies
    Views
    Last post