On Fri, Dec 17, 2021 at 07:07 PM, Drew Derbyshire wrote:
I suspect it shipped with a smarter wrapper EXEC than the EXEC (1) exec one on the Sixpack.? (I?checked, the LCM+L uses the same ancient EXEC.)
It looks like to do multiple files, an exec would to iterate through them (if NOCONCAT) or concatenate them before the module ran (if CONCAT? specified.)
I'll happily take a smarter REXX version for the LCM+L machine Y disk.
Attempting multiple inputs per the documentation:
...
????????? Command? Language? User's? Guide).?? The? following? command
?????????? prototype may be used to invoke the WATFIV compiler.
?
????? WATFIV fn-i ... (DIsk? Concat?? NODebug NOXtype Term?? NOStats)
?????????????????????? Print NOConcat Debug?? XType?? NOTerm Stats
?????????????????????? TYpe?????????????????? NOWarn
????????????????????????????????????????????? Ext
?????????? The fn-i? (i=1,...) are? the input? filenames. They? must be
?????????? names of disk files (of type? FORTRAN or WATFIV) or *, which
-
????? USING WATFIV UNDER CMS??????????????????????????????????? Page 13
-
1
???????????????????????????????? USING WATFIV UNDER INTERACTIVE SYSTEMS
-
?????????? specifies? that input? is? to be? taken? from the? terminal.
?????????? WATFIV? will read? all? input files? as? one continuous? job
?????????? stream.?
Doesn't get very far, apparently because the EXEC doesn't support this, per Drew's comments. It also seems as if CONCAT and NOCONCAT are not supported either.
q filedef
DMSQRY324I No user defined FILEDEF's in effect.
Ready; T=0.01/0.01 16:21:52
l * fortran a ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
HELLO??? FORTRAN? A1? F??? 80??? 156???? 16? 12/18/21?? 16:16
GOODBYE? FORTRAN? A1? F??? 80??? 156???? 16? 12/18/21?? 16:14
Ready; T=0.01/0.01 16:22:00
watfiv hello goodbye ( concat
BAD OPTION
?
WATFIV FN [ ( XDEBUG | NOXDEBUG , DEBUG | DEBUGS | NODEBUG , TEST | NOTEST
FILETYPE CAN BE WATFIV OR FORTRAN
THE OPTIONS ARE ORDERED. IF YOU WANT TO SPECIFY TEST, XDEBUG AND
DEBUG OPTIONS MUST BE INCLUDED
Ready(-0001); T=0.01/0.01 16:22:24
watfiv hello goodbye ( noconcat
BAD OPTION
?
WATFIV FN [ ( XDEBUG | NOXDEBUG , DEBUG | DEBUGS | NODEBUG , TEST | NOTEST
FILETYPE CAN BE WATFIV OR FORTRAN
THE OPTIONS ARE ORDERED. IF YOU WANT TO SPECIFY TEST, XDEBUG AND
DEBUG OPTIONS MUST BE INCLUDED
Ready(-0001); T=0.01/0.01 16:22:58
watfiv hello
Ready(00003); T=0.02/0.03 16:23:09
watfiv goodbye
Ready(00003); T=0.02/0.03 16:23:20
l * fortran a ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
HELLO??? FORTRAN? A1? F??? 80??? 156???? 16? 12/18/21?? 16:16
GOODBYE? FORTRAN? A1? F??? 80??? 156???? 16? 12/18/21?? 16:14
Ready; T=0.01/0.01 16:23:39
l * listing a ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
HELLO??? LISTING? A1? F?? 133??? 206???? 35? 12/18/21?? 16:23
GOODBYE? LISTING? A1? F?? 133??? 204???? 34? 12/18/21?? 16:23
Ready; T=0.01/0.01 16:23:45
watfiv hello goodbye
BAD OPTION
?
WATFIV FN [ ( XDEBUG | NOXDEBUG , DEBUG | DEBUGS | NODEBUG , TEST | NOTEST
FILETYPE CAN BE WATFIV OR FORTRAN
THE OPTIONS ARE ORDERED. IF YOU WANT TO SPECIFY TEST, XDEBUG AND
DEBUG OPTIONS MUST BE INCLUDED
Ready(-0001); T=0.01/0.01 16:35:10
I reading through the User Guide WATFIVUG LISTING U and Jay Mosley's PDF, I found the following references, all of which seem to treat this concatenation in a MVS/MVT batch environment. Reminds me of NIU having a dedicated card reader for WATFIV jobs for a while, where your JCL around your program was the $JOB ... code ... $ENTRY ... data,? stream. I believe they used NOCONCAT, so we would each get our own output listing.
As far as doing this in CMS, the only benefit would be if you were using multiple FILEDEFs for FT05F001. This might be possible in CMS, using the CHANGE option but I'm willing to be corrected....????? Listing output options:+???? _______ ______ ________0????? DIsk???????????????????? The? program? listing? and? all? unit? 6?????????????????????????????? output is? written to? a disk? file with.¨¦th.?????????????????????????????? filename? fn-1 and? filetype LISTING? if?????????????????????????????? CONCAT? is? in effect.?? A? filename? of?????????????????????????????? WATFIV will? be generated if fn-1? is *.?????????????????????????????? The?? NOCONCAT? option?? will? cause?? a?????????????????????????????? separate output disk? file with filename?????????????????????????????? fn-i for each input file.?????? Print (PRT)????????????? The? listing? and? unit?? 6? output? are?????????????????????????????? spooled to the virtual printer.?????? TYpe (*)???????????????? The listing and unit? 6 output are typed?????????????????????????????? at the terminal.??????????? Note: If? fn-1 is *, then? TYPE will become the? default and?????????? all? options controlling? execution-time output,? diagnostic?????????? messages and job statistics will have no effect. The default?????????? CONCAT option? will cause? output to be? placed in? a WATFIV?????????? LISTING file.? In the case of? using the NOCONCAT option, if?????????? two program batches? are input to WATFIV? from the terminal,?????????? the listing file? for the second will? overwrite and destroy?????????? the listing file for the first....
???? Compiler-mode options:+???? _____________ ________?????? Concat?????????????????? This option? causes WATFIV to? treat all?????????????????????????????? input? files?? as? one?? continuous? job?????????????????????????????? stream. All output is? written to a disk?????????????????????????????? file with? a filename of the? first file?????????????????????????????? specified?? (fn-1)?? and?? filetype?? of?????????????????????????????? LISTING.? If * is specified for fn-1 the?????????????????????????????? filename will? default to? WATFIV and? a?????????????????????????????? $JOB? card? will be? generated.? Hitting?????????????????????????????? carriage? return signifies? end of? file?????????????????????????????? for terminal input.?????? NOConcat???????????????? This option causes each input file to be?????????????????????????????? treated as? a separate batch.? Input for?????????????????????????????? each? filename is? compiled? separately.?????????????????????????????? Each fn-i? should contain? at least? one?????????????????????????????? complete WATFIV job.
...????? 11.3 CONCATENTATING COMPILER INPUT??????????? WATFIV's? input stream? may consist? of? a concatenation? of?????????? distinct? data? sets.?? The? following? examples? illustrate?????????? potential uses of this feature:???? |????? 1)??? Source? program and? execution card-image? data to? be??? |??????????? read by 'card? reader' unit 5 can be? in disjoint data----????? CONCATENTATING COMPILER INPUT???????????????????????????? Page 87-1??????????????????????????????????????????? INPUT OUTPUT CONSIDERATIONS-???????????????? sets.???????????????????????????? //osjob?? JOB?? accounting???????????????????????????? //?? EXEC?? WATFIV???????????????????????????? //GO.FT05F001? DD? DDNAME=PROG???????????????????????????? //???????????? DD? DDNAME=DATA???????????????????????????? //GO.PROG????? DD? *???????????????????????????? $JOB?? id,parms?????????????????????????????????????? source program?????????????????????????????? $ENTRY???????????????????????????? //GO.DATA? DD? DSN=WATFIV.SUBSUB(DATA),DISP=SHR???????????? 2)??? Segments of the source program to be compiled can come???????????????? from different sources.?????????????????????????????? //osjob?? JOB?? accounting???????????????????????????? //?? EXEC?? WATFIV???????????????????????????? //GO.FT05F001? DD? DDNAME=JOB,DCB=BLKSIZE=800???????????????????????????? //???????????? DD? DSN=WATFIV.MAINPROG,DISP=SHR???????????????????????????? //???????????? DD? DSN=WATFIV.SUBSUB(SUB1),DISP=SHR???????????????????????????? //???????????? DD? DSN=WATFIV.SUB2,DISP=SHR???????????????????????????? //???????????? DD? DDNAME=ENTRY???????????????????????????? //GO.JOB?????? DD? *???????????????????????????? $JOB?????????? id,parms???????????????????????????? //GO.ENTRY???? DD? *???????????????????????????? $ENTRY?????????????????????????????????????????? any data?????????????????????????????? /*????????????????? (This? example? assumes the? operating? system? allows???????????????? multiple DD * data sets in the input stream.)
...?... Mark S.
Mark A. Stevens