View previous topic :: View next topic
|
Author |
Message |
ajay_dheepak
New User
Joined: 12 May 2005 Posts: 32 Location: Chennai
|
|
|
|
Hi,
Can anybody help me out in this. I had this in an interview.
How to scan a JCL for syntax errors & without submitting the JOB and without using TYPRUN=SCAN.
Thanks in advance.
Ajay |
|
Back to top |
|
|
aishwarya_singh
New User
Joined: 06 Apr 2005 Posts: 21
|
|
|
|
Hi Ajay,
You can type JSCN or JEM command on the command line after typing the jcl in the member.It will show you all the syntax errors. |
|
Back to top |
|
|
priyesh.agrawal
Senior Member
Joined: 28 Mar 2005 Posts: 1448 Location: Chicago, IL
|
|
Back to top |
|
|
subhasis_50
Moderator
Joined: 09 Mar 2005 Posts: 363 Location: Earth
|
|
|
|
Hi,
Use JCLPREP. Open the JCL in the PDS and write prep in the command line and press enter. It will show you all the syntax error. |
|
Back to top |
|
|
mfsuresh
New User
Joined: 03 Nov 2004 Posts: 5
|
|
|
|
hi ajay ,
u can also use typerun=scan in job.
same time u can use also line commands like, jem,prep,!jck(depends on ur setup) |
|
Back to top |
|
|
MGIndaco
Active User
Joined: 10 Mar 2005 Posts: 432 Location: Milan, Italy
|
|
|
|
If you have not JEM, JSCAN etc. Submit the job within the jobcard: //jobname job .....,TYPRUN=SCAN
and look the sysout in SDSF. |
|
Back to top |
|
|
Girishm
New User
Joined: 09 Mar 2005 Posts: 35 Location: Mysore
|
|
|
|
hi ajay,
In TSO go for option 26: Jobscan, next option 1 - Validate JCL. then provide Path of JCL and PROC for scan and type F in the command prompt to start scanning the JCL for errors.
_________
GM |
|
Back to top |
|
|
MGIndaco
Active User
Joined: 10 Mar 2005 Posts: 432 Location: Milan, Italy
|
|
|
|
I think that option 26 is customized...
i.e. In my environment it does not exist. |
|
Back to top |
|
|
|