IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Error 'SCAN TIME OUT' in XPEDITER


IBM Mainframe Forums -> Compuware & Other Tools
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
gaurav_shrivastav

New User


Joined: 26 Feb 2009
Posts: 5
Location: Pune

PostPosted: Mon Jun 15, 2009 1:20 pm
Reply with quote

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
Back to top
View user's profile Send private message
rajnikantvanpratiwar

New User


Joined: 01 Jul 2009
Posts: 5
Location: Pune

PostPosted: Thu Jul 02, 2009 4:32 pm
Reply with quote

can check xpeditor settings
Back to top
View user's profile Send private message
passion_sujesh

New User


Joined: 14 Mar 2008
Posts: 74
Location: India,Chennai

PostPosted: Wed Jan 25, 2012 12:45 am
Reply with quote

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.
Back to top
View user's profile Send private message
passion_sujesh

New User


Joined: 14 Mar 2008
Posts: 74
Location: India,Chennai

PostPosted: Wed Jan 25, 2012 12:59 am
Reply with quote

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'.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Wed Jan 25, 2012 1:00 am
Reply with quote

Googling xtg0029 returns, among other hits, a page with this explanation:
Quote:
When the CONVERT option is used for JCL processing and the
JCL has a '/*ROUTE PRINT' card in it, then the output from
Xpediter's TYPRUN=SCAN can go to another LPAR preventing
Xpediter from processing it. Thus, the '/*ROUTE PRINT'
card results in a 'SCAN timed out' message being received.
This issue can occur in both online (option 2) processing
as well as batch (option 3.1)
Back to top
View user's profile Send private message
passion_sujesh

New User


Joined: 14 Mar 2008
Posts: 74
Location: India,Chennai

PostPosted: Wed Jan 25, 2012 1:17 am
Reply with quote

Thanks Robert,
I have checked the job and there is no '/*ROUTE PRINT' card in it.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Wed Jan 25, 2012 1:19 am
Reply with quote

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.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne

PostPosted: Wed Jan 25, 2012 1:53 am
Reply with quote

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.
Back to top
View user's profile Send private message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Wed Jan 25, 2012 8:52 pm
Reply with quote

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.
Back to top
View user's profile Send private message
niks_jude
Warnings : 1

Active User


Joined: 01 Dec 2006
Posts: 144
Location: Mumbai

PostPosted: Sat Oct 27, 2012 8:23 am
Reply with quote

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.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> Compuware & Other Tools

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts To get the the current time DFSORT/ICETOOL 13
No new posts RC query -Time column CA Products 3
Search our Forums:

Back to Top