View previous topic :: View next topic |
Author |
Message |
geetha001 Beginner
Joined: 22 Jun 2005 Posts: 41 Topics: 14
|
Posted: Tue Oct 28, 2008 8:57 am Post subject: Sysout missing from the Job log |
|
|
When I execute/run a COBOL+IMS+DB2 program, I am missing the SYSOUT from the Job Log. In SDSF the JESMSGLG, JESJCL, JESYSMSG DD names appear but the SYSOUT DDNAME does not appear.
I have the display statements in the program, but I am still not able to see the SYSOUT. I do have the MSGCLASS right. I even tried to use a JCL which is running correct (showing sysout etc.,) for an existing COBOL+IMS+DB2 program and modified to use my program, but still the Sysout did not appear.
Could you please help me with this...
Thanks |
|
Back to top |
|
 |
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Tue Oct 28, 2008 9:02 am Post subject: |
|
|
You DO have //SYSOUT DD SYSOUT=* and not pointing it to a dataset? _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
 |
dbzTHEdinosauer Supermod
Joined: 20 Oct 2006 Posts: 1411 Topics: 26 Location: germany
|
Posted: Tue Oct 28, 2008 9:32 am Post subject: |
|
|
batch or online? _________________ Dick Brenholtz
American living in Varel, Germany |
|
Back to top |
|
 |
geetha001 Beginner
Joined: 22 Jun 2005 Posts: 41 Topics: 14
|
Posted: Tue Oct 28, 2008 9:51 am Post subject: |
|
|
This is a batch program.
Yes I do have //SYSOUT DD SYSOUT=*
Infact I tried both the above SYSOUT and also pointed to a dataset. When I point to the dataset, the dataset gets created but it is empty.
Is there any compiler option that I might be missing.
I have the following compiler options
PROCESS DATA(24),NOCMPR2,NOLIST,OFFSET and I think this is fine when I compare with an existing COBOL+IMS+DB2 program.
Thanks |
|
Back to top |
|
 |
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Tue Oct 28, 2008 10:01 am Post subject: |
|
|
Perhaps it is not processing the DISPLAY statements? Make sure the very first statement is a DISPLAY. If that doesn't appear then it isn't getting as far as your code, is my guess.
Do you have SYSPRINT? What does it say? _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
 |
geetha001 Beginner
Joined: 22 Jun 2005 Posts: 41 Topics: 14
|
Posted: Tue Oct 28, 2008 10:17 am Post subject: |
|
|
Actually this is an existing program and it has been running fine in Production. I modified this program with simple coding changes.
Also, I do have a SYSPRINT and even that is not appearing in the Joblog (SDSF). All I see is only JESMSGLG, JESJCL, JESYSMSG.
Also I have a display statement as the first statement right after the procedure division.
I am not sure what to look for...
Thanks |
|
Back to top |
|
 |
dbzTHEdinosauer Supermod
Joined: 20 Oct 2006 Posts: 1411 Topics: 26 Location: germany
|
Posted: Tue Oct 28, 2008 10:22 am Post subject: |
|
|
do you have anything in 'special names' ? _________________ Dick Brenholtz
American living in Varel, Germany |
|
Back to top |
|
 |
callanand Beginner

Joined: 12 Jun 2007 Posts: 23 Topics: 2
|
Posted: Tue Oct 28, 2008 10:25 am Post subject: |
|
|
Geetha001,
Are you picking up the load from the correct load library. See the proclib from where you are picking the test program if it is having the test load library mentioned or not. |
|
Back to top |
|
 |
geetha001 Beginner
Joined: 22 Jun 2005 Posts: 41 Topics: 14
|
Posted: Tue Oct 28, 2008 12:06 pm Post subject: |
|
|
Finally it worked, the issue was with picking the program from the correct library. I had a incorrect library in the Endevor listing.
Thanks for all your help. |
|
Back to top |
|
 |
|
|