>>>In this case an ideal search would be "NOTEMPTY" or "EMPTY" and "how do I".
My apologies. I was missing a NOT in the statement. Please read it as In this case an ideal search would be "NOTEMPTY" or "EMPTY" and NOT "how do I". Thanks, Kolusu DFSORT Development IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> wrote on 04/15/2017 04:46:00 PM: > From: Sri h Kolusu/Silicon Valley/IBM@IBMUS > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 04/15/2017 04:46 PM > Subject: Re: How can I set Non-zero return code in DFSORT when > SORTOUT record count is not zero > Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> > > >>I am guessing the OP framed the original question as "how do I set a > specific RC" and that is the sort of thing he searched for. > > Charles, > > "How do I" questions cannot be answered in application programming guide. > We have Smart DFSORT tricks page which shows you clever ways to use DFSORT > and ICETOOL to solve common problems. And for the record we already have > that trick "Set RC of 12, 8 or 4 if file is empty, has more than n > records, etc" which is available here > > http://www-01.ibm.com/support/docview.wss?uid=isg3T7000094 > > >>I just went to KC -- isn't that how we are supposed to be doing things > these days? :-( -- and searched on DFSORT plus the subject of this thread. > I did not get any hits that seemed immediately relevant, but drilling down > on PARM= I found NULLOUT, which at least should have been a start .. > > OP knew about the NULLOUT parm as his initial post mentions this "I know > that setting non-zero return code when SORTOUT record count is zero." > > >>>@Kolusu, I know how hard good documentation is. I have not looked at > your documentation -- I am just citing the empirical evidence that the OP > and @Lizette did not find the answer. > > We put in a lot of effort in designing the features to match the user > requirements. In this case an ideal search would be "NOTEMPTY" or "EMPTY" > and "how do I". So If it is used that as a search key they would have > found the answer. It gets difficult to document catering to "how do I...." > and even if we did we wouldn't cover all scenarios. > > >>"How do I ...?" questions are better answered by a Users Guide than by a > Reference Manual. For DFSORT these seem to be a single publication. But a > Users guide can't answer every "How" question. It would need to contain > an example of every possible program. > > Paul, > > DFSORT does have other publications like "Getting Started". If users are > not familiar with DFSORT and DFSORT's ICETOOL, I'd suggest reading through > "z/OS DFSORT: Getting Started". It's an excellent tutorial, with lots of > examples, that will show you how to use DFSORT, DFSORT's ICETOOL and > DFSORT Symbols. You can access it online, along with all of the other > DFSORT books, from: > > http://www.ibm.com/support/docview.wss?rs=114&uid=isg3T7000080 > > P.S: It still will not answer questions with "How do I.." type questions > > Some of the possible "how to" questions are answered via DFSORT smart > tricks page and this particular scenario is already covered in that > publication. > > >>So I wonder whether DFSORT has a construct to report failure if any > record in a transaction file is unmatched in the master file? > > DFSORT has an indicator as part of the record to indicate where the key > was found in the joined records ('B' for key found in F1 and F2, '1' for > key found in F1 only, or '2' for key found in F2 only). > > So the user can use that indicator to process/generate data/sysin cards. > > >> Let me assume that your DFSORT step generates a command SYSIN for the > "additional processing" step. Is there a construct akin to JOINKEY which > will create SORTOUT records for exactly those records in the transaction > file which are not matched in the master file? > > DFSORT does the ability to create any type of sysin control cards. There > is very little information here for me to show how to generate those > control cards. If OP can send/show his desired additional processing > control cards and Joinkeys sysin cards, I can show him a way of generated > the control cards. > > >>Ideally, your "additional processing" program should acept an empty > SYSIN, do nothing, and quietly exit with CC=0. > > This should be ideal scenario, have the sysin statements needed for > additional processing generated by DFSORT. If there are no control > statements to be generated then other step shouldn't have any problem. > just start and finish. > > Thanks, > Kolusu > DFSORT Development > > > > > ---------------------------------------------------------------------- > 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
