Hello and welcome to a new episode of fixing things!
Today we’re going to fix some bad JCL our intern Kevin has made last week. Oh Kevin, such a nice guy but sometimes works way too fast. It’s now up to us, senior developers, to fix his mistakes.
JCL: Identify and Correct a Syntax Error
IBM Master the Mainframe Part Two – Challenge #06
First we navigate to our Z#####.JCL, we can do so by using the primary command dslist jcl, then line command e for edit. Inhere we issue the primary command s p2ch6 to create a new member called p2ch6.
On the screenshot above we copy copy ‘zos.public.jcl(p2ch6)’ to our newly created member.
Our newly created member now has the faulty JCL.
Submit JCL and review JCL job output to identify JCL syntax error
Let’s submit ; =sd ; st so we can see the execution error.
INVALID LABEL. Labels typically begin with //. Do you remember my intro from the previous post? JCL HAS TO BE IN ALL CAPS.
THERE, I FIXED IT! ARE YOU HAPPY NOW MR. COMPILER?
The RC code is 0000. So I think Mr. Compiler is happy.
Review successful completion
Let’s check P2.OUTPUT(#06) and see if has the necessary time strings.
It has! We have completed challenge 6!
Any questions, por favor?
When will you release the rest Kevin? Can you help me with challenge 14 of part 2? Well not now, these blogs take time to write so I’m a lot slower than the competitors. I’m doing my utter best to release these as fast as I can. 7 challenges and blogs in 2 days is what I call good service 😉