Last changes: 2017-05-31
I am currently the maintainer of an improved version of the Stanford Pascal compiler.
It runs on VM/370 Rel.6 and on MVS 3.8j on the
And it runs on today's z/OS, too (tested first by Rene Jansen in 05.2017, thanks!).
It will sure run on modern zVM, too (at the moment limited to AMODE 24, RMODE 24).
The VM and MVS versions can be downloaded from this site (including source codes), see "Resources" below.
It also runs (tested) on Windows, OS/2, Linux (x86)
and Mac OS.
On these platforms the P-Code generated by the first compiler pass is interpreted by a P-Code interpreter written in ANSI-C,
so it will probably run on every platform that has a C compiler. Please contact me, if you want to test it on other platforms.
The Windows version is available from this site, too; see "Resources" below.
This page tells the story, how I started working on this compiler (in 2011), what I did so far, and what I will do next (if I get the spare time to do it).
You can follow the development process more closely on this Facebook page:
Stanford Pascal on Facebook
Warning: no warranty at all for the software contained here; I don't recommend that you use it for any production work. The AWS Tape file may contain an older version, which is not as current as the development stories from above. The source codes will be more current, but maybe you will not be able to compile them using the older versions on the AWS Tape, because it is sometimes necessary to apply incompatible extensions to the compiler. If I have time, I will put the new version to the AWS Tape, too (if the new version is stable enough).
If you have difficulties running or compiling the actual versions, contact me directly. I will help you as soon as I can, and I would like it if you test this compiler using some Pascal sources you maybe have.
The source code of the first pass: PASCAL1.PAS
The source code of the second pass: PASCAL2.PAS
To start Pascal programs using VM/CMS: XRUNPARM.ASS
The Pascal monitor and runtime: PASMONN.ASS
The source code of the LIBX library routines: PASLIBX.PAS
The source code of the UTILS library routines: PASUTILS.PAS
The source code of the MVS snapshot routine: PASSNAP.PAS
The source code of the CMS snapshot routine: PASSNAPC.PAS
The source code of the PASFORM source formatter utility: PASFORM.PAS
The source code of the XCOMP compare utility: XCOMP.PAS
Usage Notes for the MVS version:
1) the ZIP file contains subdirectories which are named like MVS datasets;
you should transfer the files contained in the subdirectories
to such PDS libraries (omit the file extensions).
You may choose another high level qualifier than PASCALN.
Most files are text files (text FTP would be OK),
but the files contained in the directories with last name part = TEXT
are RECFM fixed LRECL 80 object files (binary FTP required).
2) to build load libraries for the compiler and the runtime, start the job INSTALL from PASCALN.COMPILER.CNTL (returncode 8 from some steps is OK, but the final two steps should return zero). You may have to customize the INSTALL job if you have chosen another HLQ than PASCALN.
3) copy the members PASNC, PASNCL, PASNCG and PASNCLG from PASCALN.COMPILER.PROCLIB to SYS2.PROCLIB (on Hercules); on another z/OS system: make sure that those JCL procedures are known to your system
4) To start the compiler, look at the example jobs in the CNTL datasets; they use the JCL procs PASNC, PASNCL, PASNCG and PASNCLG mentioned above
There is also a file PASCALN.TXT, which contains all the stuff in one file, created on the mainframe using the Pascal program DOWNLOAD.PAS (included in the ZIP file, too); the PC files in the directories with the MVS like names are created using the Pascal program SPLITPAS.PAS on Windows (which is also included in the ZIP file). Instead of transferring individual members to your target system, you could also try to transfer this file to the target system and do the unpacking there (maybe with a REXX script).
Usage Notes for the Windows version:
Unzip the ZIP file to a directory of your choice.
The EXE files are removed and the CMD files are renamed to *.CMD_TXT to make virus checkers happy.
To compile PCINT, use the file AW.CMD and a C-Compiler of your choice - for example WATCOM C.
PP <program> to compile; the program should be stored in a file <program>.PAS
PRUN <program> to run the program
set DD_<logical_filename>=<physical_filename_including_path> to assign files
please contact me directly
The Programming Language Pascal (Niklaus Wirth, 1972)
Stanford Pascal/360 Implementation Guide (1974)
P-Code Description (1978)
The Stanford Pascal compiler (1979)
Pascal/VS Language Reference Manual (1981)
LE Stack and Heap Implementation (IBM 2005)
P-Code Description (2016) - work in progress