Re: ADR144E
Peter Hunkeler wrote: >>In that OP's job, I see UNIT=3390, that is DASD, not tape. I agree that job >>is looking at VTOC, not Catalog. >How embarrassing. I don't know what fooled me to believe it was about tape >data sets. Maybe the NOTAPE DDname, but that one was OUTDDNAME, in combination >with TD as VOL=SER? I also believed initially it is about tape until I see UNIT, but hey, I also make errors too and sometimes I posted something (wrong advice for example) which really embarrasses me. [1] (Oh, you can be cruel and swap around 3490 with 3390 in you device group tables... ;-D ) >Anyway, I'm sorry for the confusion this may have caused. No need to apologize. I really value your educational postings. Please keep up with your good work! Groete / Greetings Elardus Engelbrecht [1] - There is nothing on LSoft web pages, e-mail clients and similar software with a delayed send functionality. That delay may spare some nasty ps. Apparently, WhatsApp does have a delete function, but that only works if the receiver does NOT receive (and later read it) it on its device. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ADR144E
I am trying to troubleshoot a user's job which is using ADRDSSU. >>>That job is DELETING the datasets on the selected volsers. Is that what the >>>user wants? >> >>Does it? The JCL is referring to the tape by VOL=SER=, not via catalog. > >In that OP's job, I see UNIT=3390, that is DASD, not tape. I agree that job is >looking at VTOC, not Catalog. How embarrassing. I don't know what fooled me to believe it was about tape data sets. Maybe the NOTAPE DDname, but that one was OUTDDNAME, in combination with TD as VOL=SER? Anyway, I'm sorry for the confusion this may have caused. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AW: Re: ADR144E
Peter Hunkeler wrote: >>>I am trying to troubleshoot a user's job which is using ADRDSSU. >>That job is DELETING the datasets on the selected volsers. Is that what the >>user wants? >Does it? The JCL is referring to the tape by VOL=SER=, not via catalog. In that OP's job, I see UNIT=3390, that is DASD, not tape. I agree that job is looking at VTOC, not Catalog. >Non-SMS DASD data sets are deleted from the volume but not removed from the >catalog when located via VOL=SER=. True. I don't like this way of deletion, but is very useful in case of emergency or mismatch ... >I'm not sure what the system does in the case of tape data sets. The data set >cannot be physically deleted from the tape, because there might be more data >sets after the one to be deleted. I never cared to investigate, but I assume >that deleting a tape data set will only remove the catalog entry and leave >alone the physical data on the tape. Yes, I agree with all you say. It is a real PITA to do that deletion on such tapes and their contents. You need to do a tape scan to check the tape and then instead of deletion, you rather copy the datasets you want to preserve to another tape while adjusting the LABEL one by one. Of course, with today's tape management systems with 'stacking' features, no such scenario is needed. >I'm not a storage guy, and I don't have experience with tape catalog systems >(RMM, CA-1, etc). Would those recognize the reference by VOL=SER= and delete >the entry from their inventory? For Control-T, I think the answer is no, but we have setup Control-T that only cataloged and RACF protected tape datasets are used. So I can't test out your scenario. (But there is a Control-T option + RACF profiles which allow/reject such mounts via VOL=SER= statement.) >Curious to know. Damn! Now I am also curious!!! Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: ADR144E
>>I am trying to troubleshoot a user's job which is using ADRDSSU. >> >That job is DELETING the datasets on the selected volsers. Is that what the >user wants? Does it? The JCL is referring to the tape by VOL=SER=, not via catalog. Non-SMS DASD data sets are deleted from the volume but not removed from the catalog when located via VOL=SER=. I'm not sure what the system does in the case of tape data sets. The data set cannot be physically deleted from the tape, because there might be more data sets after the one to be deleted. I never cared to investigate, but I assume that deleting a tape data set will only remove the catalog entry and leave alone the physical data on the tape. I'm not a storage guy, and I don't have experience with tape catalog systems (RMM, CA-1, etc). Would those recognize the reference by VOL=SER= and delete the entry from their inventory? Curious to know. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ADR144E
willie bunter wrote: >I am trying to troubleshoot a user's job which is using ADRDSSU. That job is DELETING the datasets on the selected volsers. Is that what the user wants? >I cannot find the reason why the job fails on a : Others kindly gave you good replies about the INCLUDE filter. Just make sure these datasets are those you want to DELETE. But at least there is that safety NORUN parameter. That parameter saved us many embarrasements over the years... ;-) Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ADR144E
John, Thanks for pointing out the error : ** - Thanks to all who responded. On Mon, 3/20/17, John McKown <john.archie.mck...@gmail.com> wrote: Subject: Re: ADR144E To: IBM-MAIN@LISTSERV.UA.EDU Received: Monday, March 20, 2017, 9:18 AM On Mon, Mar 20, 2017 at 8:12 AM, willie bunter < 001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > Good Day To All, > > I am trying to troubleshoot a user's job which is using ADRDSSU. I cannot > find the reason why the job fails on a : > > ADR144E (002)-RI03P(02), INCOMPLETE SPECIFICATION IN DATA SET REFERENCED > BY DDNAME FILTERDD > > > > Below is the FILTERDD DD (TST.FILTDD) > > INCLUDE( - > ) > > I think the problem could be with the parm DATASET(FDD I would > appreciate it someone could point out my error. > That is it. The INCLUDE doesn't have _any_ entries in it. It needs to have at least one. If you meant to select "all", then use ** as the DSN. E.g. INCLUDE( - ** - ) Or perhaps some patterns: INCLUDE(- SYS1.** - SYS2.USER.** - ) > > Thanks in advance. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- "Irrigation of the land with seawater desalinated by fusion power is ancient. It's called 'rain'." -- Michael McClary, in alt.fusion Maranatha! <>< John McKown -- 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
Re: ADR144E
On Mon, Mar 20, 2017 at 8:12 AM, willie bunter < 001409bd2345-dmarc-requ...@listserv.ua.edu> wrote: > Good Day To All, > > I am trying to troubleshoot a user's job which is using ADRDSSU. I cannot > find the reason why the job fails on a : > > ADR144E (002)-RI03P(02), INCOMPLETE SPECIFICATION IN DATA SET REFERENCED > BY DDNAME FILTERDD > > > > Below is the FILTERDD DD (TST.FILTDD) > > INCLUDE( - >) > > I think the problem could be with the parm DATASET(FDD I would > appreciate it someone could point out my error. > That is it. The INCLUDE doesn't have _any_ entries in it. It needs to have at least one. If you meant to select "all", then use ** as the DSN. E.g. INCLUDE( - ** - ) Or perhaps some patterns: INCLUDE(- SYS1.** - SYS2.USER.** - ) > > Thanks in advance. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- "Irrigation of the land with seawater desalinated by fusion power is ancient. It's called 'rain'." -- Michael McClary, in alt.fusion Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ADR144E
Shouldn't the filter be something like INCLUDE( ** )? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Monday, March 20, 2017 9:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ADR144E Good Day To All, I am trying to troubleshoot a user's job which is using ADRDSSU. I cannot find the reason why the job fails on a : ADR144E (002)-RI03P(02), INCOMPLETE SPECIFICATION IN DATA SET REFERENCED BY DDNAME FILTERDD Below is the jcl: /* //S4112 EXEC PGM=ADRDSSU,REGION=0K,PARM='TYPRUN=NORUN' //TD9101 DD UNIT=3390,VOL=SER=TD9101,DISP=SHR //TD9102 DD UNIT=3390,VOL=SER=TD9102,DISP=SHR //TD9103 DD UNIT=3390,VOL=SER=TD9103,DISP=SHR //TD9104 DD UNIT=3390,VOL=SER=TD9104,DISP=SHR //NOTAPE DD DUMMY //SYSPRINT DD SYSOUT =* //SYSUDUMP DD SYSOUT=D //SYSINDD DSN=PROD.DATALIB(SYSDAU),DISP=SHR //FILTERDD DD DSN=TST.FILTDD,DISP=SHR Below is the SYSIN DD contents: DUMP INDDNAME(TD9101) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE DUMP INDDNAME(TD9102) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE DUMP INDDNAME(TD9103) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE DUMP INDDNAME(TTD9104) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE Below is the FILTERDD DD (TST.FILTDD) INCLUDE( - ) I think the problem could be with the parm DATASET(FDD I would appreciate it someone could point out my error. Thanks in advance. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
ADR144E
Good Day To All, I am trying to troubleshoot a user's job which is using ADRDSSU. I cannot find the reason why the job fails on a : ADR144E (002)-RI03P(02), INCOMPLETE SPECIFICATION IN DATA SET REFERENCED BY DDNAME FILTERDD Below is the jcl: /* //S4112 EXEC PGM=ADRDSSU,REGION=0K,PARM='TYPRUN=NORUN' //TD9101 DD UNIT=3390,VOL=SER=TD9101,DISP=SHR //TD9102 DD UNIT=3390,VOL=SER=TD9102,DISP=SHR //TD9103 DD UNIT=3390,VOL=SER=TD9103,DISP=SHR //TD9104 DD UNIT=3390,VOL=SER=TD9104,DISP=SHR //NOTAPE DD DUMMY //SYSPRINT DD SYSOUT =* //SYSUDUMP DD SYSOUT=D //SYSINDD DSN=PROD.DATALIB(SYSDAU),DISP=SHR //FILTERDD DD DSN=TST.FILTDD,DISP=SHR Below is the SYSIN DD contents: DUMP INDDNAME(TD9101) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE DUMP INDDNAME(TD9102) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE DUMP INDDNAME(TD9103) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE DUMP INDDNAME(TTD9104) OUTDDNAME(NOTAPE) - DATASET(FDD(FILTERDD)) - DELETE PURGE Below is the FILTERDD DD (TST.FILTDD) INCLUDE( - ) I think the problem could be with the parm DATASET(FDD I would appreciate it someone could point out my error. Thanks in advance. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
