Error 'SCAN TIME OUT' in XPEDITER

gaurav_shrivastav · New User Joined: 26 Feb 2009 Posts: 5 Location: Pune

Hi,

I am getting error 'SCAN TIME OUT' in XPEDITER while specifying the JCL path in BATCH option in XPED.

Could anyone help me out in knowing the reason of this error message?

-Gaurav

rajnikantvanpratiwar · New User Joined: 01 Jul 2009 Posts: 5 Location: Pune

can check xpeditor settings

passion_sujesh · Posted: Wed Jan 25, 2012 12:45 am

Hi,
I am getting the same error message 'SCAN timed out', when I am trying to CONVERT COMPILE JCL. Can you please let me know how i can check the xpeditor settings, so that i can fix this.

Thanks in advance.

passion_sujesh · Posted: Wed Jan 25, 2012 12:59 am

The scan job is submitted and has a RC=0. But in the CONVERT COMPILE JCL screen i get this error message 'SCAN TIME OUT'.

Robert Sample · Posted: Wed Jan 25, 2012 1:00 am

Googling xtg0029 returns, among other hits, a page with this explanation:

passion_sujesh · Posted: Wed Jan 25, 2012 1:17 am

Thanks Robert,
I have checked the job and there is no '/*ROUTE PRINT' card in it.

Robert Sample · Posted: Wed Jan 25, 2012 1:19 am

In that case, you need to open a problem report with Compuware. Since they own and maintain the software, they are the ones that can identify the root problem you have and fix it.

dbzTHEdinosauer · Posted: Wed Jan 25, 2012 1:53 am

This is a common problem due to:

1. improper setup by your support.

2. the job (the file containing the jcl) also has references to datasets used as input (sysin files, for instance) that are not part of the defined paths

3. your jcl sucks or is overly complicated and the level of jclscan being used is not up-to-date.

before you bother compuware with your problem,
make sure that the setup at your site is correct.

whenever i have had these problems,
since dealing with support usually means going thru their defend-their-butt BS
i have found putting the jcl in question in a member/dataset with
simplified syntax, since all you really want are dd ref-names and dataset names.

Ed Goodman · Active Member Joined: 08 Jun 2011 Posts: 556 Location: USA

I hit this once and I was able to fix it by checking the Job card that XPEDITOR puts on the conversion job. It doesn't use the same one that ISPF uses.

Mine had some job name that made it so that I couldn't read it. I changed the job name to have my user id at the start and it worked!

In my case, someone had taken a shortcut and copied all the xpeditor tables from their ISPF to mine, so that I had their ID in my job card.

niks_jude · Posted: Sat Oct 27, 2012 8:23 am

Feeling that I am not getting enough foreground CPU time given that my JCL was very big, I had modified my PROC to keep only the required steps I wanted to run and had tried with it and it did work. You can just give it a try as an option but not sure if this was the real reason.