IBM Mainframe Forum

[zatlas1]

Looking to port some open source to native z/OS, the main obstacle is the make file!
That file, however is generated, tells the C compiler what to compile and how to resolve dependencies. To the best of my knowlede from the last time I have done C on the mainframe, there was no such a beast on MVS and all dependencies had to be rsolved via the JCL (correct order of libraries for headers in SYSLIB, etc.) I could not find any evidence for usage of make file in the IBM literature, but that does not mean anything.
Is there any use for make file in compiling C (or C++) under z/OS or is compiling still done only the old [JCL] way?

Thanks
ZA

[Robert Sample]

z/OS Perl uses make files in Unix System Services, but there's no JCL involved -- just OMVS or telnet to a Unix System Services port.

[zatlas1]

No i need native zos not uss

[dick scherrer]

Hello,

Whoever supports the pl/i compiler on your system should already have working compile jcl . . .

While the manual will not be knowledgable of your system configuration, it can tell you what is needed to do a compile on the mainframe.

I don't "do" pl/i, so i can't even guess at the specifics or alternatives.

[zatlas1]

Dick
a) it's C not PL/I
b) I know how to compile C and/or PL/I, COBOL or whatever have you. I've just asked whether the new C compiler on z/OS has any use for 'make' files. It seems that the answer is "NO", so I will proceed with that in mind
Thanks all
ZA

[Robert Sample]

A make file and its use would be a property of the operating system / environment; it would not be part of the language. And classic z/OS has no capability to generate or use make files. Unix System Services could generate and use make files -- for C as well as other languages -- but you've already ruled out using Unix System Services. Hence the answer to your question is that under the restrictions you have imposed, what you want to do cannot be done -- period.

[zatlas1]

Thanks
Thant what I've thought
ZA