Thanks, @John and @Gil. Sounds like this is slightly bleeding edge. I think I will try to sync my "code management" processes (C versus HLASM) a little more closely together but continue to keep HLASM source and object in a PDSE.
Too bad, frankly. I wish there were more embrace of HFS by "traditional" programs. Perhaps I am spoiled: the C library does such a nice job of bridging the differences. In my product I don't know which I am dealing with unless I bother to look. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Wednesday, October 26, 2016 12:00 AM To: [email protected] Subject: Re: Does anyone use HFS files extensively with HLASM? On Tue, Oct 25, 2016 at 6:49 PM, Charles Mills <[email protected]> wrote: <snip> Yes. I did an entire project (for myself, not work) using z/OS UNIX as the repository for the files, both SYSIN and SYSLIB (the latter is a bit weird). I also used the "as" UNIX command to do my assemblies. Which were driven using the UNIX "make" command. One thing which made this much easier was FLOWASM ( ftp://ftp.phoenixsoftware.com/pub/demo/asmmods.xmi ), ref: http://planetmvs.com/hlasm/tips.html . FLOWASM is an HLASM user exit program for reading the SYSIN & SYSLIB. It makes HLASM "free format". Quite nice! This was a case of "eating your own dog food" because I was developing some UNIX utilities. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
