Thomas Hagen ([log in to unmask]) wrote:
: Hello, I am trying to make some command files to perform compilation of
: COBOL programs I am writing.
: Now I can not see how to pass parameters from the command line to my
: command file.
: Could anyone please help?
 
: The command should work something like this :
 
: MPE_XL: compile program
 
I have a utility, which I once contributed to the CSL, that does what you
ask...and a lot more.  It deduces the language (COBOL, FORTRAN, Pascal,
SPL/SPLash, or C), and lets you embed options like "cap=ph,ds,ia" or
"nmstack=1000000" or "lib=g", or "listing requested", or "batch", ...
 
Example:
   If the first line of a Pascal source program looks like:
 
       {myprog.source.sieler  95/01/19  nm  cap=ph nmstack=1000000
        auxobj = fastlib.o  -e myprog.pub
       }
 
    then:  compile myprog
    would: 1) open "myprog.<logon>" or "myprog.source" or "myprog.module" or
              "myprog.c" (until it finds a "myprog" source file!)
           2) compile it with the NM Pascal compiler  (nm is default, but "cm"
              could have been requested)
           3) no listing is generated (implied:  pascal myprog, ..., $null)
           4) if successful, the program is linked with fastlib.o, and
              nmstack = 1000000, and cap=ia,ba,ph, and saved as myprog.pub
 
Example:
   As above, but I want the compile to be done in a batch job, and I want
   the nmstack to be 2000000 instead of the 1000000 in the source code:
 
      compile myprog batch nmstack 2000000
 
In effect, a different approach to the Unix "make" program...an approach where
the critical information is kept in the main source file, *not* some separate
file that can get lost/out-of-synch.
 
I'll try to upload it (along with the FINDACD program) on Monday/Tuesday.
 
Stan Sieler
[log in to unmask]