|
View previous topic :: View next topic
|
| Author |
Message |
I?aki Viggers
New User
Joined: 18 Jun 2005
Posts: 8
|
|
|
|
Hi,
I keep getting
| Code: |
IEF237I DMY ALLOCATED TO SYSPUNCH
IEF237I JES2 ALLOCATED TO SYSIN
IEF237I 148 ALLOCATED TO SYSLIB
IEF142I HELOWRLD COB HELOEXEC - STEP WAS EXECUTED - COND CODE 0012
|
when I submit on Hercules/TK4 the following:
| Code: |
000001 //HELOWRLD JOB (COBOL),'HI',CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)
000002 //HELOEXEC EXEC COBUCG
000003 //COB.SYSPUNCH DD DUMMY
000004 //COB.SYSIN DD *
000005 IDENTIFICATION DIVISION.
000006 PROGRAM-ID. FIRSTPGM.
000007 PROCEDURE DIVISION.
000008 DISPLAY 'HELLO WORLD'.
000009 STOP RUN.
000010 /*
000011 //COB.SYSLIB DD DSNAME=SYS1.COBLIB,DISP=SHR
000012 //GO.SYSOUT DD SYSOUT=*
000013 //
|
What am I missing?
I copied/simplified the JCL statements from an example included in the TK4 installation (SYS2.JCLLIB(PRIMCOB1), if it matters). Somewhere in the log it says that program IKFCBL00 gives the Return Code 12. Other than that, I don't know what other information I need to provide. |
|
| Back to top |
|
 |
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 1698
|
|
|
|
| I?aki Viggers wrote: |
| Code: |
| IEF142I HELOWRLD COB HELOEXEC - STEP WAS EXECUTED - COND CODE 0012 |
| Code: |
000001 //HELOWRLD JOB (COBOL),'HI',CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)
000002 //HELOEXEC EXEC COBUCG
000003 //COB.SYSPUNCH DD DUMMY
000004 //COB.SYSIN DD *
000005 IDENTIFICATION DIVISION.
000006 PROGRAM-ID. FIRSTPGM.
000007 PROCEDURE DIVISION.
000008 DISPLAY 'HELLO WORLD'.
000009 STOP RUN.
000010 /*
000011 //COB.SYSLIB DD DSNAME=SYS1.COBLIB,DISP=SHR
000012 //GO.SYSOUT DD SYSOUT=*
000013 //
|
What am I missing? |
The message IEF142I is produced after the step COB of your JCL procedure named COBUCG. This step is running the IBM COBOL compiler module, which has ended with RC=12. This code typically means that COBOL compiler did not finish successfully, due to one or more of thousands of possible reasons.
The detailed report (listing) on compilation issues is placed to the output location defined via //SYSPRINT DD statement of //COB EXEC step.
You need to find this compiler output, investigate it carefully, detect and understand all those specific error messages causing the COBOL compiler to stop with RC=12. |
|
| Back to top |
|
|
I?aki Viggers
New User
Joined: 18 Jun 2005
Posts: 8
|
|
|
|
Thanks, but inserting
| Code: |
| //SYSPRINT DD SYSOUT=* |
right after line (or card) 11 made no difference in the output. In other words, it is not generating any additional output that points to the reason(s) for failure. |
|
| Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 1698
|
|
|
|
| I?aki Viggers wrote: |
Thanks, but inserting
| Code: |
| //SYSPRINT DD SYSOUT=* |
right after line (or card) 11 made no difference in the output. In other words, it is not generating any additional output that points to the reason(s) for failure. |
It is not possible. COBOL compiler always produces the full compilation listing, in case it's SYSPRINT is defined correctly. At least it does so since the beginning of 1960s, with no gaps in time.
Either you must investigate your output more carefully, or present here your full SDSF output.
There is no way of guessing.
P.S.
I'm 100% sure that //SYSPRINT DD has been defined somehow within the JCL procedure COBOLCG.
You need either to verify your SDSF log in full (with the expanded procedure COBOLCG), or present this full SDSF log to the forum.
Otherwise there is no subject to discuss further. |
|
| Back to top |
|
|
|
|
