The problem with using "make" is that I must know *in advance* which programs I want to compile and then code a make file for that set of programs. What I want to do is more like:
Edit program1 Submit program1 to compile Edit program2 Submit program2 to compile ... How ever many times Each compile is independent of the others and I don't want to "preplan" and build a make file to compile the set of programs since I don't often know the members of the set in advance. I do see where a make file would be used as I would use a "compile proc" in MVS. I.e. to compile a C program, I must do steps 1 through 5. I could then create a generalized make file where I pass in the name of the program to compile along with any parameters. I may just be trying to force an MVS concept where it doesn't really belong. -----Original Message----- From: Ferguson, Neale [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 8:02 AM To: [EMAIL PROTECTED] Subject: Re: "batch" compiles Using a make file to script the compiles that are required will help serialize a user's compilations. You can use a flag to increase levels of parallelism if required. You can do this to put them into the background: make -f <makefile name> >& make.log & To get a bitmore fancy, use the nice command to adjust the priority of the job: nice -n <-nn> make >& make.log &
