On Mon, 15 Aug 2022 21:44:57 -0500, Alan Altmark wrote:
>
>>o A BFS member?
>
>#include "/usr/alan/src/include/my.macro"
>
Must ot be fully qualified, or can it be relative to current working directory?
>LSEARCH(/usr/alan/src/include)
>
Same question.
--
Thanks,
gil
On Mon, 15 Aug 2022 12:40:57 -0500, Paul Gilmartin wrote:
>How can the programmer indicate:
>
>o A SFS member with a directory path?
> (Must it be accessed with a mode letter?)
There is no such capability; the directory must be accessed. You can use
LSEARCH(A,B,D), for example, to restrict
On Mon, 15 Aug 2022 10:55:17 -0500, Alan Altmark wrote:
>>...
>You specified
>#include
>instead of
>#include "my.macro"
>
><> are for system include files. These are always H files or members of a
>MACLIB.
>
>Quotes are for *user* include files. They can be any name. If not found,
On z/OS I've occasionally had to use NOLSEARCH,LSEARCH(...) to remove the
default LSEARCH to get my LSEARCH to work.
Colin
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
On Sun, 14 Aug 2022 00:49:20 +0300, Binyamin Dissen
wrote:
>I am trying to tell the C compiler to use MACRO file types for #include.
> :
>I have tried multiple versions of LSEARCH with no luck.
>
>cc **name** c * (lsearch(*.macro)
>WARNING CCN3261 Suboption *.macro is not valid for option
On Sun, 14 Aug 2022 22:17:02 +0800, David Crayford wrote:
>You will have to use macro file extension in the C code.
>
>#include “file.macro”
>
So the source code must be dual-path for CMS?:
#if CMS
#include “file.macro”
#else
#include "file.h"
#endif
Ugh! (Will the
You will have to use macro file extension in the C code.
#include “file.macro”
> On 14 Aug 2022, at 8:09 am, Paul Gilmartin
> <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
>
> On Sun, 14 Aug 2022 00:49:20 +0300, Binyamin Dissen wrote:
>
>> I am trying to tell the C compiler to use
On Sun, 14 Aug 2022 00:49:20 +0300, Binyamin Dissen wrote:
>I am trying to tell the C compiler to use MACRO file types for #include.
>
Are you the author or are you working from FOSS or other distributed source?
If the latter, consider BFS. Its directory structure may be more similar to
what
you cant do it that way.
lsearch prepends to the include...
https://www.ibm.com/docs/en/zos/2.1.0?topic=options-lsearch-nolsearch
Joe
On Sat, Aug 13, 2022 at 4:49 PM Binyamin Dissen
wrote:
> I am trying to tell the C compiler to use MACRO file types for #include.
>
> The doc states:
>
>
I am trying to tell the C compiler to use MACRO file types for #include.
The doc states:
===
COMMANDS CC All Help Information
LSEarch(opt)|NOLSEarch NOLSEARCH is the default.
10 matches
Mail list logo
