开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

BUFF40 jcl/documentation Fortran


 

I have BUFF40 compiling and linking via dos/vs.? Does anyone have
any jcl and/or documentation on how to run and use this code.

Thank you
tom c


 

开云体育

I’d really like to help you Tom but I can’t find my documentation.

?

This is a paragraph from my webpage that I wrote for my 50th anniversary at SRU.

?

The first computer usage by students was in 1970 for FORTRAN classes.? Their programs were compiled with a stand-alone program called RAX.? We had to shutdown DOS in order to??RAX.? Later we acquired BUFF40, a fast FORTRAN compiler from the State University of New York at Buffalo.? It ran in DOS/360.

?

I don’t remember for sure but I think there might have been a WATFOR or WATFIV compiler that would run on DOS that came after BUFF40.

?

/Fran Hensler at Slippery Rock University of Pennsylvania USA for 52 years??????

mailto:RockFox@...?? ?

?????????????????"Yes, Virginia, there is a Slippery Rock"

?

?

From: [email protected] <[email protected]> On Behalf Of Tom Chandler
Sent: Tuesday, September 27, 2022 3:36 PM
To: [email protected]
Subject: [H390-DOSVS] BUFF40 jcl/documentation Fortran

?

I have BUFF40 compiling and linking via dos/vs.? Does anyone have
any jcl and/or documentation on how to run and use this code.

Thank you
tom c


 

From an old yahoo groups message:

"There is no doc other than what you find in the source code. BUFF40 is
a student "compile & go" system designed for high performance on small
programs. It does not generate an object deck. The language supported
is also a slight variant on standard FORTRAN IV (for example, in a few
cases blanks are significant, whereas in proper FORTRAN IV they never
are). This was done in order to catch and try to correct many common
student errors and allow execution to proceed. This was from a time
when a student would typically submit his program on punch cards and
get output back the next day, so it was frustrating to make a simple
typo and have no execution."

Joe

On Tue, Sep 27, 2022 at 2:36 PM Tom Chandler <tchandler48@...> wrote:
I have BUFF40 compiling and linking via dos/vs.? Does anyone have
any jcl and/or documentation on how to run and use this code.

Thank you
tom c


 

开云体育

>This was from a time when a student would typically submit his program on punch cards and
>get output back the next day,

?

Such luxury. I had to put coding forms in the post. It was Fortran II so things like

?

F=G*10

?

Usually fails……

?

Dave

?

From: [email protected] <[email protected]> On Behalf Of Joe Monk
Sent: 02 October 2022 22:14
To: [email protected]
Subject: Re: [H390-DOSVS] BUFF40 jcl/documentation Fortran

?

From an old yahoo groups message:

?

"There is no doc other than what you find in the source code. BUFF40 is
a student "compile & go" system designed for high performance on small
programs. It does not generate an object deck. The language supported
is also a slight variant on standard FORTRAN IV (for example, in a few
cases blanks are significant, whereas in proper FORTRAN IV they never
are). This was done in order to catch and try to correct many common
student errors and allow execution to proceed. This was from a time
when a student would typically submit his program on punch cards and
get output back the next day, so it was frustrating to make a simple
typo and have no execution."

?

Joe

?

On Tue, Sep 27, 2022 at 2:36 PM Tom Chandler <tchandler48@...> wrote:

I have BUFF40 compiling and linking via dos/vs.? Does anyone have
any jcl and/or documentation on how to run and use this code.

Thank you
tom c


 

On Sun, 2 Oct 2022 at 17:14, Joe Monk <joemonk64@...> wrote:
From an old yahoo groups message:

"There is no doc other than what you find in the source code. BUFF40 is
a student "compile & go" system designed for high performance on small
programs. It does not generate an object deck. The language supported
is also a slight variant on standard FORTRAN IV (for example, in a few
cases blanks are significant, whereas in proper FORTRAN IV they never
are). This was done in order to catch and try to correct many common
student errors and allow execution to proceed. This was from a time
when a student would typically submit his program on punch cards and
get output back the next day, so it was frustrating to make a simple
typo and have no execution."

Yes, as I said back in 2007, there is no doc other than the source code. But there is a lot of info in that very tight source, and the line-by-line comments are pretty good if you have experience in that dense style of code.

On Tue, Sep 27, 2022 at 2:36 PM Tom Chandler <tchandler48@...> wrote:
I have BUFF40 compiling and linking via dos/vs.? Does anyone have
any jcl and/or documentation on how to run and use this code.

By the way, I wouldn't say "compiling and linking" about BUFF40, unless you are talking about building it. It's very much a compile and go system - the FORTRAN is compiled into storage and executed there. There is no object deck produced, and so nothing to link.

I had thought a couple of people said they had got BUFF40 running not too long after I posted the source, but re-reading, I'm not sure anyone actually got beyond compiling it. :-( Perhaps you can be the first!

Tony H.


 

Hi,

I got it to start. It needs a file BUFF40S with between 10 and 100
cylinders. I am not sure how to create files on DOS yet. If anyone
can provide the JCL to make this. It directly calls $$BOPEN on the
file.

The first line of the job should be $COMPILE ????? starting after
column 10.

Rich


"There is no doc other than what you find in the source code.
BUFF40 is a student "compile & go" system designed for high
performance on small programs. It does not generate an object deck.
The language supported is also a slight variant on standard FORTRAN
IV (for example, in a few cases blanks are significant, whereas in
proper FORTRAN IV they never are). This was done in order to catch
and try to correct many common student errors and allow execution
to proceed. This was from a time when a student would typically
submit his program on punch cards and get output back the next day,
so it was frustrating to make a simple typo and have no execution."
Yes, as I said back in 2007, there is no doc other than the source
code. But there is a lot of info in that very tight source, and the
line-by-line comments are pretty good if you have experience in that
dense style of code.

On Tue, Sep 27, 2022 at 2:36 PM Tom Chandler <tchandler48@...>
wrote:

I have BUFF40 compiling and linking via dos/vs. Does anyone have
any jcl and/or documentation on how to run and use this code.
By the way, I wouldn't say "compiling and linking" about BUFF40,
unless you are talking about building it. It's very much a compile
and go system - the FORTRAN is compiled into storage and executed
there. There is no object deck produced, and so nothing to link.

I had thought a couple of people said they had got BUFF40 running not
too long after I posted the source, but re-reading, I'm not sure
anyone actually got beyond compiling it. :-( Perhaps you can be the
first!

Tony H.




--
==========================================================================
Richard Cornwell
rich@...

LinkedIn:
==========================================================================


 

Hi,

I managed to get BUFF40S to work. It probably will not work on
DOS/VS. I used DOS/360. You need to define a very small supervisor.
It seems it can't be bigger then 16K. BUFF40 does some LH to load
pointers to data, if they end up being over 16K they get sign
extended and will cause an address exception. Note this will not
work under POWER.

// ASSGN SYS012,X'191' <---- Disk for BUFF40S file.
// ASSGN SYS013,X'00C' <---- Where to get input from
// DLBL BUFF40S,'BUFF40.SPOOL.FILE',0,SD
// EXTENT SYS012,WRK14A,,,1100,1000 <- 10 to 1000
// UPSI 10000000 <--- Needed for format spool file.
// EXEC TSTFORT
$COMPILE
< Program goes here>
$EXECUTE
< Data goes here>
< Repeat COMPILE/EXECUTE as needed>
$COMPILEX
/*
/&

Compile supports the following options:

T=# number of seconds to allow to compile
P=# number of pages of output to allow
C=# number of input cards allowed.
E=# number of errors to allow.
L=1 enable listing.

Defaults: T=20,P=5,C=50,E=25,L=1

Many thanks to Rene Ferland for helping with how to define a
file in DOS.

Rich

-
==========================================================================
Richard Cornwell
rich@...

LinkedIn:
==========================================================================