IBM Mainframe Forum

ERROR ***SCANED TIME OUT *** while xped setup.,can anyone help to resolve the scan time out error.,have given required jcl libraries, ddio files and message class with A.,could figure out the exact reason for scan time out erorr.,i do remember a command we used to give in command line for increasing the timelimit

Can you tell us what it's waiting for? Like, are you in CICS and waiting for a transaction to happen?

Assuming that you meant this messagewhen you posted, you most likely will need to work with your site support group to resolve the issue. Possible reasons for this problem would include (but not be limited to):
- Xpediter not being set up correctly
- Xpediter attempting to run the TYPRUN-SCAN job in the wrong job class
- No initiators being available for the job class
- Invalid JOB statement flushing job from system

As such, it is unlikely that an application programmer would have the authority to fix the problem, whatever it may be. You need to work with your site support group who will be able to make the necessary changes.

I want to make sure the original poster understands something very important...that job never actually ran. The 'typerun=scan' parameter is meant to allow you to sumbit some JCL to make sure it's OK before you try to run it.

What I want to make SURE you understand is that this is NOT an XPEDITOR error. You could have been running a simple sort and still gotten this message.

Even if you had not hit the scan time out, NOTHING would have run. The typerun=scan would have let you see a return code of 0 for the job, but there would have been no executed steps.