Gadi, The way I'm reading your question, the job "ran successfully" ie it got a RC=0 but you want the job to fail instead of just giving the "not catlgd 2" message, right? If so, check your ALLOC member and change it to CATLG_ERR FAILJOB(YES) ERRORMSG(YES). This will cause the job to fail on a "NC2" message instead of just ending with RC=0. It's not a dfsort behavior per se, but a z/OS wide behavior.
Rex -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Gadi Ben-Avi Sent: Tuesday, January 28, 2020 11:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] DFSort question Hi, User ran a job the uses DFSort to copy a dataset. The output dataset is on tape. The output dataset existed on tape before the job run. Message IGD17101I was issued saying that there already was a dataset with that name. The job ended with condition code 0. Is this a DFSort behavior? If yes, can it be changed? We are using z/OS v2.2. Thanks Gadi ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
