If each operand either cannot be a Unix file or must be a Unix file then it doesn't matter whether the command uses fopen() or open(). Only if the command has an operand that can specify either a path or a ddname (or path or dsname) is there an issue.
________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Tuesday, July 19, 2022 10:48 AM To: [email protected] Subject: Re: z/OS 1.4 submit On Tue, 19 Jul 2022 13:32:29 +0000, Seymour J Metz wrote: >A command written for, e.g., *bsd, Linux, Unix, will expect file names in Unix >system and will use the library routine fopen(), which also expects Unix >syntax. The library routine fopen() accepts an expanded syntax that allows >specifying classical MVS datasets. It's not relevant to EXECIO and IEBGENER, >since they already handled datasets befor Unix System Services cames along as >OpenEdition. > In other words, it is not required that the command supports fopen() syntax. >________________________________________ >From: Paul Gilmartin [[email protected]] >Sent: Friday, July 15, 2022 9:10 AM > >On Fri, 15 Jul 2022 10:05:53 +0000, Seymour J Metz wrote: > >>Allocate an internal reader and copy the file to it. Ensure that the command >>you use supports fopen() syntax. >> >Why should "supports fopen() syntax" be necessary. I've variously used >EXECIO and IEBGERR; I doubt that either uses fopen(). > >Isn't fopen() a feature of a language (usually C) rather than of a command? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
