View previous topic :: View next topic
|
Author |
Message |
sainathm
New User
Joined: 09 Feb 2009 Posts: 7 Location: bangalore
|
|
|
|
Hi,
I am facing an issue in JCL.
I am not able to see a step(Program execution step) in JCL even after successful execution on JCL. |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
In what way do you not see the step? IF you cannot see it how do you know it executed?
There are 4 places to look using SDSF - system messages (usually the first dataset), expanded JCL (usually second dataset), step allocations and messages (usually 3rd dataset) and any output to spool from your program. If your step does not appear in any of these then it was not in the job.
Did you have a job terminator card (// by itself) before the step? Was the exec statement for that step commented out? Were you looking at the correct job!? |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
Check your step JCL and look for any SYSTSPRT, SYSPRINT, SYSOUT or whatever (depending on which program runs).
Is there something missing ? assigned to DUMMY or a garbage class ? |
|
Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008 Posts: 1249 Location: Richfield, MN, USA
|
|
|
|
If I remember correctly, if MSGCLASS is assigned to a "purge immediately" and all of your SYSOUT classes are *, you'll never see any output. |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 581 Location: London
|
|
|
|
Check with your local admin/sysprogs to make sure you're using the right SYSOUT class on your SYSPRINT DD and MSGCLASS on your jobcard. These are set by local standards, some classes can be set to immediate purge.
In SDSF enter the following on the command line where yourUid=your RACF ID:
OWNER yourUid; PRE **; DEST; SYSNAME ** |
|
Back to top |
|
|
|