IBM MTM: Part Three – Challenge #10

This challenge is a lot more difficult, in two ways even. It’s difficult because there’s no guidance and it’s difficult to write a blog about it as I’m not allowed to publish solutions. This time we need to locate invalid packed decimal data and fix it.

I’ll need to execute a program called ICETOOL to display and verify packed decimals inside the ZOS.PUBLIC.BBRI.CLIENTS data set. A good help for this challenge is the JCL used in Challenge #03. This challenges asumes we are aware of what the JCL does in challenge #03. I think I was aware, not sure? Uhh…

We need to be aware that only VERIFY is needed to complete the assignment. DISPLAY is not needed. VERIFY produces a return code 12 as a result of finding invalid packed decimal. However, the invalid packed decimal records are written in JCL job output.

Identify every invalid packed decimal record found within 10,000 records

IBM Master the Mainframe Part Three – Challenge #10

Well it’s pretty obvious that we’ll be using the same JCL as challenge #03 so I guess I can show you that much. I’ll just copy Z30163.JCL(SORT003) into a new file. I guess it doesn’t matter what I call the file. I’ll just navigate back to dslist and create SORT010 and just edit it from there.

So I already went ahead and changed the SETVAR to the data set we need and also deleted the DISPLAY statement as we don’t need that. Now what do I need to change? Let’s take a look at the data set.

I’ve put hex on for no reason at all. Seriously. So here we see that a row is 11 characters long. That might give you an idea on what we need to change in SORT010. I’ve changed what I needed to change but the records are written in the JCL job output.

I tried copying sort004 and write the output that way but I kept getting the error 11 BYTE RECORD LENGTH IS NOT EQUAL TO 80 BYTE LRECL FOR BAD. But when you think a little bit, IBM never said to use sort004 didn’t they? And the report is inside the JCL. So why not just XDC it?

I don’t think that just simply using XDC is enough? I am confusion.

Well I guess that just using XDC is enough. Weird.

Easy, but not easy.

I don’t really know what to think about this challenge. It just had me copy some old JCL, edit three things and copy the output using XDC. I’m not really sure if this solution is correct. I guess I’ll see later 🙂

What’s been easy but not easy for you this week?

PS: Did you notice? I published this post at 11/11/2018 11:11. Coolio!

Share this:

11 thoughts on “IBM MTM: Part Three – Challenge #10

  1. Dude these posts are so helpful thanks so much for putting them up. Really helped when i was stuck in a few challenges and pulling my hair out.

  2. I used the exact same solution, do we only need the report on TOOLMSG?
    The JCL will always return MAXCC = 12 like this right?

    1. Hi Anonymous

      VERIFY produces a return code 12 as a result of finding invalid packed decimal. So MAXCC 12 is correct. Yes indeed, we only need the TOOLMSG report and then copy that to P3.OUTPUT(#10).

      Kind regards

Leave a Reply

Your email address will not be published. Name, email and website not required.