Yes, SMS, is involved here. I think I've learned quite a lot from this discussion and my recommendation to the user is to either catalog the dataset or since their JCL ultimately deletes the dataset, change it to a temporary name, e.g. &&F00DMY, either of which resolves the failure.
Thanks again for the discussion. -- Donald Grinsell State of Montana 406-444-2983 dgrins...@mt.gov "It is impossible to make anything foolproof, because fools are so ingenious." ~ Robert Heinlein -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shmuel Metz (Seymour J.) Sent: Sunday, May 25, 2014 9:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Friday Puzzler In <bf7d786e5c64b2469bf97db41c499fac2625b...@doaisd5231.state.mt.ads>, on 05/23/2014 at 04:02 PM, "Grinsell, Don" <dgrins...@mt.gov> said: >I have an end user job that is getting a JCL error and I know how to >fix it but I can't explain exactly why it's failing. Is FOO.DUMMY SMS managed? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see <http://patriot.net/~shmuel/resume/brief.html> We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
