|
|
| Author |
Message |
rohin
New User
Joined: 29 Apr 2005
Posts: 11
Location: Gurgaon, India
|
|
|
|
Hi,
Could somebody please explain or forward any relevant document on the following reasons?
1. I was getting S0C4 abend, when I used 2 copybooks in my Linkage section. This got solved when I removed one of the copybook. I understand that there is a funda that LS variable should be like
01 LS-VAR.
03 LS-VAR-LEN
03 LS-VAR-TXT....
But I have seen that in our shop, it does not give any error for multiple 01 level declarations in LS. Could anyone please explain?
2. Also, I am getting S0C4 now when my program is executing STOP RUN statement. Any explanation?
Regards,
Rohin |
|
| Back to top |
|
 |
References
|
 Posted: Sun May 11, 2008 5:33 pm Post subject: Re: S0C4 abend, when I used 2 copybooks in my Linkage section |
|
|
|
|
| Moved: Sun May 11, 2008 5:37 pm by William Thompson From DFSORT/ICETOOL to Mainframe COBOL |
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 1087
Location: At my desk
|
|
|
|
| rohin wrote: |
| But I have seen that in our shop, it does not give any error for multiple 01 level declarations in LS. Could anyone please explain? |
You can have as many 01s you want, but each needs to have addressability established before you access it.
| Quote: |
I understand that there is a funda that LS variable should be like
01 LS-VAR.
03 LS-VAR-LEN
03 LS-VAR-TXT.... |
This is true to access the JCL PARM field, but not necessarily true for other passed data in the linkage section. |
|
| Back to top |
|
|
rohin
New User
Joined: 29 Apr 2005
Posts: 11
Location: Gurgaon, India
|
|
|
|
| Thanks for your help. Could anyone please explain the occurance of S0C4 while executing STOP RUN command? |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 6935
Location: 221 B Baker St
|
|
|
|
Hello,
If the program has an internal sort, it may be that you are issuing the STOP RUN while still in the sort. This very often causes an 0c4. |
|
| Back to top |
|
|
mytags
Active User
Joined: 28 Apr 2008
Posts: 61
Location: US
|
|
|
|
Hi,
My suggestion is that it is due to mismatch of copy book .By replacing with accurate copy book for the program we can over come this error.
thanks
hari |
|
| Back to top |
|
|
|
|
