Sample pgm with following JCL, but recieves S0C1

Jayakrishnanm · New User Joined: 14 Jun 2007 Posts: 3 Location: MN

Hello,

I am trying to execute a sample pgm with following JCL, but recieves S0C1. Can anyone help me out?

//DFGATEST JOB (0334,221),'TESTING',MSGCLASS=R,NOTIFY=&SYSUID
//STEP01 EXEC PGM=LPGM1
//STEPLIB DD DSN=K546.WERADD.UIOP.DD.OBJLIB,DISP=SHR
//SYSOUT DD SYSOUT=*

IDENTIFICATION DIVISION.
PROGRAM-ID. PGM1.
PROCEDURE DIVISION.
DISPLAY "I DID THIS !!!".
STOP RUN.

expat · Posted: Tue May 20, 2008 1:25 pm Post subject:

Error messages may help

Jayakrishnanm · New User Joined: 14 Jun 2007 Posts: 3 Location: MN

SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001
TIME=03.25.37 SEQ=03045 CPU=0000 ASID=00B3
PSW AT TIME OF ERROR 078D0000 80000002 ILC 2 INTC 01
NO ACTIVE MODULE FOUND
NAME=UNKNOWN

sril.krishy · Posted: Tue May 20, 2008 2:20 pm Post subject:

NO ACTIVE MODULE FOUND

Please check the program which you compliled and linked and the program that you mentioned in the JCL (EXEC PGM=LPGM1 ).

Thanks
Krishy

Aaru · Posted: Tue May 20, 2008 2:23 pm Post subject: Reply to: S0C1

jaya,

enrico-sorichetti · Posted: Tue May 20, 2008 2:31 pm Post subject: Reply to: S0C1

Gnanas SNG · Posted: Tue May 20, 2008 2:40 pm Post subject:

Please refer the description & User actions for QW S0C1.

enrico-sorichetti · Posted: Tue May 20, 2008 2:47 pm Post subject: Reply to: S0C1

please remember to post suggestions available to everybody
qw implies the installation of a charge add on

Jayakrishnanm · New User Joined: 14 Jun 2007 Posts: 3 Location: MN

my Link JCL was wrong. I corrected it and everythng went fine. Thanks for the replies.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1508

enrico,

Why 0C1 and not 806?

My guess is that the objlib had a member name entry for the pgm, but the content was not assembler code.

enrico-sorichetti

Hi Jack,

all the abends related to module management are of the xx6 series

so after all, unless the loader itself was messed up
( not easy since the checking done by the loader is quite sophisticated )
a program had started executing

a wrong linkage editor might cause a wild branch,
a wild branch might easily give the false symptom "NO ACTIVE MODULE"

enrico-sorichetti

You can play lots of tricks with assembler and linkage editor..

usually people do not care to set properly the module flags,

and almost all the rubbish after a successful linkage editor get marked as "executable"

the proper approach would be to mark modules with the proper flags

fo example a table of data that gets loaded should be marked
NX ... not executable
OL ... Load only
trying to issue a link against such thing would give a 406 abend,
but the load would be successful