__asm() is perfectly valid for C++. I used it all the time. > On 30 Jul 2019, at 6:00 am, Charles Mills <charl...@mcn.org> wrote: > > Thanks. __asm is C but not C++, unfortunately. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Farley, Peter x23353 > Sent: Monday, July 29, 2019 5:37 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: XTIOT impact? > > If all you need to know is whether a DD name is allocated or not, I think the > DEVTYPE macro is the simplest method. Any non-zero return code indicates > non-existence once you have the macro invocation working (there is a "syntax" > RC that you will never get after you have it coded to work). > > And DEVTYPE is very simple to code as an "__asm" statement in XL C/C++. > > Peter > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Bernd Oppolzer > Sent: Monday, July 29, 2019 4:50 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: XTIOT impact? > > Most "practical" uses of TIOT searches are for user programs which try to > check if there is a certain DD statement in the job step JCL, used to control > a certain program action. > > For me, this is a sort of "third way" of parameter passing to programs, > besides normal JCL parameters and environment. > > Sort of nice, because it can be used in every language and the changes to > existing code are minimal (can be applied even very late - 20 years after > first delivery - and in emergency situations). > > Example: > > //USERRSAF DD DUMMY > > checking for existence of USERRSAF in TIOT, and do some program action > depending on this > > As far as I unterstand these postings, this use of TIOT scans (in whatever > language) is still valid. > > Any comments? > > Kind regards > > Bernd > >> Am 29.07.2019 um 22:40 schrieb Seymour J Metz: >> Yes, if you use one of those options then the ddname will not be in the >> TIOT. If you open a DCB/ACB for a ddname allocated with one of those >> options, DCBTIO will be zero. >> >> > -- > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. If > the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by e-mail > and delete the message and any attachments from your system. > > > ---------------------------------------------------------------------- > 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
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
