?

On Fri, Dec 17, 2021 at 07:06 AM, Bernd Oppolzer wrote:

I only have a very old VM-370 distribution (from 2011 or so) and currently no plan
to install another one, because I am happy with what I have. Could you send me (only)
the MACLIB, if you want me to help you with it?

Bernd,

I will send you the MACLIB under separate cover. I will reiterate, the problem seems to be with the assembler, not the assembler programs in the MACLIB.

?... Mark S.

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Brian
McCullough
Sent: 20 December 2021 18:06
To: [email protected]
Subject: Re: [h390-vm] Updated Help

On Sun, Dec 19, 2021 at 05:01:23PM -0000, Dave Wade wrote:

I have done minor updates to the recent files and created a few more
help files for the likes of BASIC, COBOL, FORTRAN, PL360, PLC and PLI

Dave,

I have done a quick skim through your nice work, and have a couple of nits
for you.

In cobol.helpcommand: "downloadedfrom".

In fortran.helpcommand: "Then use the load and start to run the programs."
Perhaps "Then use the load and start commands ..." ??

Under "filename," "it must haveh fixed".

"NOPRint - Do not write a lising file."




I will make some more time later in the month to further peruse these

It's been a LONG time since I thought of PL/360!



Brian

?

I'm beginning to feel like I'm the problem child, that is the one, causing/finding problems. Ah well.

I know there are multiple programs out there to find free file modes and free virtual addresses.? On VM/370 CE, on the Y-disk is GIMME EXEC. It wants to use FREEADDR MODULE, which isn't installed in V1R1M1. So we have one half of the solution, or we need a complete one. OR ... is there one installed that I don't know about?

L GIMME * * ( DATE
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
GIMME??? EXEC???? Y2? V??? 80???? 61????? 2? 06/14/08?? 17:04
Ready; T=0.01/0.01 23:49:39
SCAN GIMME EXEC Y
Enter pattern:
FREEADDR
?
File: GIMME EXEC Y2.
22:
EXECUTIL FREEADDR
Ready; T=0.01/0.01 23:49:48
L FREEADDR * * ( DATE
File not found.
Ready(00028); T=0.01/0.01 23:49:56

Me ... I wrote a substitute for the IPF GETFMADR MODULE, and called it GETFMADR EXEC.

?... Mark S.

?

Folks,

?

? I have attempted to clean up the GCC help files and to that end have uploaded some modified files to the groups file section.

?

/g/h390-vm/files/Help%20File%20Updates

?

there are two copies, one as a zip archive of ASCII files, the other as a VMFPLC2 AWS tape. If you would like to have a look and let me know what you think.

?

Dave

?

?

On Sat, Dec 18, 2021 at 02:15 AM, Dave Wade wrote:

Drew,

?

Thanks for responding…..

?

Well yes, that’s what the module we have requires, which is why I thought we might be missing something as the documentation definitely says it should accept multiple files.

I thought, “CONCAT” but CONCAT does not work for sequential files. ?For FORTRAN I think that you should also be define FT05F001, FT05F002, FT05F003 but that does not seem to work either.

I see that WATERLOO had an append mod to FILEDEF and perhaps they used that?

If you got it, flaunt it.? :-)

(OTOH, I personally would write a smarter wrapper -- more portable. IBM's Yorktown lab was famous for shipping stuff internally that didn't work on vanilla VM systems.)?

?

?

so I think you could easily fix this on the LCM+L machine, but re-fitting the mods back to R6 might be a challenge….

…. as far as I can see the only way to do this on VM/370R6 is to copy the files before running the compiler.

The copy would be required on the LCM+L machine (VM/SP 5) as well.? It could be done in EXEC; it's just easier in IBM REXX.? (I have not used BREXX to know how well it mimics VM/SP REXX).? (The standard user configuration with a 30M temp disk on the LCM+L machine doesn't hurt either.)

?

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.