TYPRUN='SCAN' not Invoked



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

TYPRUN='SCAN' not Invoked

Postby jaggz » Fri Jul 13, 2012 9:26 am

Hi,

I am not able to see the Scanned Report for any JCL when I code with TYPRUN='SCAN'. Is it something the SCAN feature is missing in Z/OS ? If so, are there any equivalent features available ?

Jaggz
User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 4 times

Re: TYPRUN='SCAN' not Invoked

 

Re: TYPRUN='SCAN' not Invoked

Postby NicC » Fri Jul 13, 2012 10:25 am

I do not understand what you mean by 'scanned report'. All TYPRUN=SCAN does is allow your JCL to be interpreted but not executed - just sent to the output queue. TYPRUN=HOLD sends it to the input queue, in hold status, after interpretation. What were you expecting? If you have no output on the output queue then you either have a JCL error in the jobcard or you have specified a MSGCLASS that prohibits the 'printing' of JCL or you have not submitted the job.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: TYPRUN='SCAN' not Invoked

Postby BillyBoyo » Fri Jul 13, 2012 12:29 pm

I think you are thinking you are using a "JCL Checker" program: you are not.

If that is not what you are thinking, please explain more clearly and in more detail.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: TYPRUN='SCAN' not Invoked

Postby Anuj Dhawan » Sat Jul 14, 2012 7:38 pm

What DD statement do you look at in the spool? Are you at correct one?
Anuj
Anuj Dhawan
 
Posts: 274
Joined: Mon Feb 25, 2008 3:53 am
Location: Mumbai, India
Has thanked: 6 times
Been thanked: 4 times

Re: TYPRUN='SCAN' not Invoked

Postby dick scherrer » Sat Jul 14, 2012 11:21 pm

Hello,

If a TYPRUN=SCAN is run, there should be no DD statements in the spool - only the JES sysouts.

And these need to be posted here. If there are no JES sysouts, he job was flushed - probably because of an invalid JOB statement.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: TYPRUN='SCAN' not Invoked

Postby jaggz » Sun Jul 15, 2012 8:00 am

Dear Dick,

Thanks for the clarification.
User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 4 times

Re: TYPRUN='SCAN' not Invoked

Postby dick scherrer » Sun Jul 15, 2012 8:04 am

You're welcome.

Did you fnd the "scan" information?
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: TYPRUN='SCAN' not Invoked

Postby Anuj Dhawan » Sun Jul 15, 2012 12:08 pm

If you execute a Job with TYPRUN=SCAN, you'll get the following DDName listed. As Dick say they are "JES" sysouts, I referred them as "DD-Names" as shown below:

   Display  Filter  View  Print  Options  Help                                 
 -------------------------------------------------------------------------------
 SDSF JOB DATA SET DISPLAY - JOB JOBNAME(JOB28196)    LINE 1-2 (2)           
 COMMAND INPUT ===>                                            SCROLL ===> CSR 
 PREFIX=JOBNAME  DEST=LOCAL  OWNER=*  SYSNAME=                                 
 NP   DDNAME   StepName ProcStep DSID Owner    C Dest               Rec-Cnt Page
      JESMSGLG JES2                 2 Anuj  Y LOCAL                    8     
      JESJCL   JES2                 3 Anuj  Y LOCAL                   11     
one will have what you are looking for.
Anuj

These users thanked the author Anuj Dhawan for the post:
jaggz (Tue Jul 17, 2012 8:12 am)
Anuj Dhawan
 
Posts: 274
Joined: Mon Feb 25, 2008 3:53 am
Location: Mumbai, India
Has thanked: 6 times
Been thanked: 4 times

Re: TYPRUN='SCAN' not Invoked

Postby expat » Sun Jul 15, 2012 2:10 pm

Recall something similar many moons ago and using MSGLEVEL=(1,1) on the jobcard resolved the issue
expat
 
Posts: 382
Joined: Sat Jun 09, 2007 3:21 pm
Has thanked: 0 time
Been thanked: 1 time

Re: TYPRUN='SCAN' not Invoked

Postby NicC » Sun Jul 15, 2012 2:56 pm

Yup, all points that covered in my original reply - not bad for 6 in the morning before feeding the pigs.

EDIT - on the other hand 10:00am after feeding the pigs I had to edit this reply!
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Next

Return to JCL

 


  • Related topics
    Replies
    Views
    Last post