POSIX(ON) tends to change everything. I suppose I should qualify my remarks about fopen() by saying I am a big believer in quotes and fully-qualified names. Of course, I am developing an "enterprise, production" product, not a user productivity tool. I suspect all of my "legacy" fopen()'s use quotes.
The product runs POSIX(ON) FWIW. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, September 25, 2018 11:05 AM To: [email protected] Subject: Re: TSO PREFIX, FTP and z/OS upgrade On Tue, 25 Sep 2018 09:40:16 -0700, Charles Mills wrote: >The APARs are pretty specific about "IDCAMS." > Yes, but the OP mentions FTP, not IDCAMS. But how broad is the reach of IDCAMS? Possible anything that employs Catalog Services? >There is a little bit more of a *hint* on the "why" in APAR OA43330. > "[L]ittle" seems to be the operant word. >"My" product uses fopen() extensively for "legacy" datasets in a variety of >customer environments and we have gotten no reports of issues. > I know an OMVS segment is needed for FTP nowadays. Is a TSO segment or UADS entry likewise needed, perhaps by the user ID/password dialogue? How does fopen() by a user having neither UADS nor RACF/TSO treat an incompletely qualified DSN (e.g. "//SYS1.SAMPLIB" as opposed to "//'SYS1.SAMPLIB'")? Does POSIX make a difference? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
