| View previous topic :: View next topic |
| Author |
Message |
ramlak
Beginner
Joined: 17 Apr 2007
Posts: 27
Topics: 6
|
 Posted: Thu May 03, 2007 6:32 pm Post subject: S0C1 |
 |
|
I am running a cobol program dont know why its giving S0C1 with reason code 000001. also says 'NO ACTIVE MODULE FOUND'
The control is not even coming to procedure divison.
It may be coz of some unresolved symbolics in the link-edit
but dont know how else to resolve it.
I indeed searched the forum but mine is too specific thats y am posting again.
any idea would help a lot.
Thanks,
Lak. |
|
| Back to top |
|
 |
CICS Guy
Intermediate
Joined: 30 Apr 2007
Posts: 292
Topics: 3
|
| Posted: Thu May 03, 2007 6:40 pm Post subject: |
|
|
If, in fact, "The control is not even coming to procedure divison" then it is not finding the module.
YOU have to put forth the abilities that you aspire to, figure out what the system is trying to tell you...... |
|
| Back to top |
|
|
vkphani
Intermediate
Joined: 05 Sep 2003
Posts: 483
Topics: 48
|
| Posted: Fri May 04, 2007 12:20 am Post subject: |
|
|
Ramlak,
Check for your load module in the load library. |
|
| Back to top |
|
|
Nic Clouston
Advanced
Joined: 01 Feb 2007
Posts: 1075
Topics: 7
Location: At Home
|
| Posted: Fri May 04, 2007 2:36 am Post subject: |
|
|
If the load module was not in the library it should gixe an x06 failure. I wouold check the link/bind to ensure the module has been marked as EXECUTABLE. If not then I would check for other messages in the link and also the compile messages - especially for references to EXTERNAL names
_________________
Utility and Program control cards are NOT, repeat NOT, JCL. |
|
| Back to top |
|
|
dz
Beginner
Joined: 02 Apr 2006
Posts: 26
Topics: 0
|
| Posted: Fri May 04, 2007 8:04 am Post subject: |
|
|
| Also check if, by accident, you have compiled a batch program with CICS precompiler. This wouls cause S0C1. |
|
| Back to top |
|
|
ramlak
Beginner
Joined: 17 Apr 2007
Posts: 27
Topics: 6
|
| Posted: Fri May 04, 2007 9:27 am Post subject: |
|
|
Thanks for all the immediate responses i will try and let you know the results
thanks |
|
| Back to top |
|
|
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12370
Topics: 75
Location: San Jose
|
| Posted: Fri May 04, 2007 9:38 am Post subject: |
|
|
ramlak,
Check the following
| Code: |
0C1
System ABEND: S0C1
Description: An attempt was made to execute an invalid machine
instruction operation code. The operation code is either
invalid or is for an instruction that is not available on
this CPU.
This failure is usually due to a branch to an invalid storage
location, as might occur in a load module with unresolved
external references, or when a branch to an address outside
of a program occurs. (Reason Code 1)
User Action: Correct the program logic or construction error and resubmit
the job. Possible causes for this abend include:
Amode was set to 24, but a branch was attempted to a
31-bit or (on z/OS) a 64-bit address
In assembler, coding 'B R14' when you meant to code 'BR R14'
Subscript error occurred
"Clobbered" code; i.e., the executing program was
corrupted in virtual storage and then a branch was
performed into the corrupted code
Tried to read a file that was not open
Misspelled DDNAME followed by attempted I/O to same file
Error in parameters passed to subroutines
Missing DD card followed by attempted I/O to same file
Recording mode was wrong, or density was incorrect
Bad load module, possible bad object deck in FORTRAN
(unresolved external references)
Missing dimension statement
Same name for an array and a subroutine
COBOL: subroutine prog ID was the same as the entry name
tried to call within COBOL sort I/O procedure
tried to call a subroutine which could not be found
incomplete DCB for SORTIN file
using sort verb, DDNAME was not SORTOUT when the
"giving" option was used.
executing sort-using after opening SORTIN file
|
Hope this helps...
Cheers
Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
Nic Clouston
Advanced
Joined: 01 Feb 2007
Posts: 1075
Topics: 7
Location: At Home
|
| Posted: Fri May 04, 2007 9:41 am Post subject: |
|
|
That reminds me...I once had a S0C1 on soemthing that 'had not changed'. seems that one of the team had changed the length of the parm being passed back and forth between external modules but hadn't done all the required changes in the other (my) module. Thanks Graham M.!
_________________
Utility and Program control cards are NOT, repeat NOT, JCL. |
|
| Back to top |
|
|
ramlak
Beginner
Joined: 17 Apr 2007
Posts: 27
Topics: 6
|
| Posted: Fri May 04, 2007 11:17 am Post subject: |
|
|
Thanks for all the tremendous replies ,
i have found that few LE modules cant be resolved in the linkedit section
i added the load library where the proc can call the loads like 'CEEBETBL,
CEESTART' etc..
thats solved my problem.
This board gives me lot of strength especailly when you think that no body to help you out. thanx guys Cheers  |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
