The APARs are pretty specific about "IDCAMS." There is a little bit more of a *hint* on the "why" in APAR OA43330.
"My" product uses fopen() extensively for "legacy" datasets in a variety of customer environments and we have gotten no reports of issues. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Monday, September 24, 2018 4:19 PM To: [email protected] Subject: Re: TSO PREFIX, FTP and z/OS upgrade On Mon, 24 Sep 2018 17:54:29 -0500, Dave B wrote: >I had a PMR and the result was that the change in FTP prefix was attributed to >the following: > >https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.e0zm100/DFSMS_V2R2_IDCAMS_Review_Dataset_Keyword.htm > > >To work around our issues, the datasets were fully qualified with quotation >marks to ensure that the prefix would not be attempted. > Is there a good reason for this incompatible change? Whom does it benefit. o Does it affect/is it compatible with the XLC fopen() function? o Does it affect/is it compatible with UNIX /bin/cp, etc.? (Probably the same answer as XLC.) o Does it affect TRANSMIT/RECEIVE with PROFILE NOPREFIX? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
