I've been hacking on CMS Make (and losing sleep, but such is the
life of an addict!). This is so much fun! Got a long way to go.
Again, the reason for doing this is to have a 'make' tool for CMS
that works mostly like Unix 'make' even to the point of sharing
rules fi
On 11/17/06, Richard Corak <[EMAIL PROTECTED]> wrote:
>Manual scanning of the source is painful,
Actually, it's rather easy. I have a 300 line REXX command that
reads a list of LISTING files, reads the LISTINGs, parses the
"Macro and Copy Code Source Summary" section, extracts the entries,
and
Manual scanning of the source is painful,
Actually, it's rather easy. I have a 300 line REXX command that
reads a list of LISTING files, reads the LISTINGs, parses the
"Macro and Copy Code Source Summary" section, extracts the entries,
and builds dependencies (in my personal format).
Richard C
> In the case of update files, the source depends on them.
> (Most 'make' driven packages do not employ anything as sophisticated
> as CMS UPDATE. Some do use 'patch'.) What we would need is the
> "make depend" kind of thing that was already mentione
On 11/16/06, Rick Troth <[EMAIL PROTECTED]> wrote:
In the case of update files, the source depends on them.
Yes. But I would expect a CMS MAKE to know about cntrl and aux files
in some smart way. If I had to add each update file to the makefile
it's most likely getting the weake
ven packages do not employ anything as sophisticated
as CMS UPDATE. Some do use 'patch'.) What we would need is the
"make depend" kind of thing that was already mentioned. What CMS Make
then needs for that is the ability to append dependencies to a
previously established recipe.
-- R;
On 11/13/06, Rick Troth <[EMAIL PROTECTED]> wrote:
The time-stamp comparison is what I really like.
Files that depend on each other are automagically maintained. SWEET!!
I would hope you do something generic to deal with CMS update. I have
my own HLASM front-end to build text decks per updat
Make could be a common tool for Windoze, Linux, BSD Unix,
AT&T Unix, USS, OpenVM, CMS, ... anything but traditional MVS.
Even MVS might could use Make, but the datasets and/or members would
have to be time-stamped. All the other systems stamp their "files".
-- R;
would be no point in reinventing the wheel.
> What services exist to build dependencies for things
> like COPY files or MACROs, including inner MACROs
> within inner MACROs?
Traditional Unix Make has a concept of libraries and members.
I never got that far in the prior CMS Make, and h
What services exist to build dependencies for things
like COPY files or MACROs, including inner MACROs
within inner MACROs?
The idea behind 'make' has always been a good one,
but I never liked maintaining dependencies manually.
Richard Corak
Sounds interesting. Where do I find it?
Regards,
Richard Schuh
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of
Rick Troth
Sent: Monday, November 13, 2006 4:42 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject:CMS Make
In a previous
In a previous life,
I used 'make' a lot for building some VM packages.
Initially, I used the 'make' command in OpenVM, which is great!
(We should all leverage OpenVM.) But driving CMS operations from it
was a little messy. That is, when the content of interest was in
CMS space and the targets
12 matches
Mail list logo
