When I try to boot dos/vs 34 under VM/ESA it dies with disabled psw. The same config works fine under hercules directly. I defined VM as 370 already.

I have now proved the concept sufficiently. If you write your programs a certain way, you can stand up a clone anywhere (e.g. you can run VSE programs on z/OS). But I have my own environment - z/PDOS-generic, so that's what I am using. Here is what a VSE program looks like when running: (I renamed the executable from pdptest.exe to vsetest.exe) 18:48:59 /(0009) vsetest.exe 18:48:59 got request to open vsetest.exe 18:48:59 in LoadVSE 18:48:59 about to call app at address 04ECE818 18:48:59 got service call 0 18:48:59 len is 8 18:48:59 msg is MADE IT! 18:48:59 got service call 7 18:48:59 return from app is hex 3 18:48:59 18:48:59 enter a command That same program running under DOS/VS: 19:00:12 BG 19:00:12 * 19:00:12 BG 19:00:12 * 19:00:12 BG 19:00:12 * Now run the app 19:00:12 BG 19:00:12 * 19:00:12 BG 19:00:12 MADE IT! 19:00:12 BG 19:00:12 * 19:00:12 BG Using this JCL: * First we get the main phase off tape, and into 80-byte blocks * using objmaint * // UPSI 1 // ASSGN SYS004,TAPE // DLBL UOUT,'PDPPUNCH.DAT',0,SD // EXTENT SYS005,,,,10000,2000 SPACE-PHASE // ASSGN SYS005,SYS000 // EXEC OBJMAINT,SIZE=AUTO ./COPY /* // UPSI 0 // ASSGN SYS005,SYSLST // ASSGN SYS004,UA * * * * * * * * Then we put the phase into the CIL, using LNKEDT * // DLBL IJSYSLN,,0,SD // EXTENT SYSLNK,,,,12000,2000 SPACE-LINK ASSGN SYSLNK,SYS000 // OPTION CATAL // DLBL IJSYSIN,'PDPPUNCH.DAT' ASSGN SYSIPT,SYS000 INCLUDE CLOSE SYSIPT,READER // EXEC LNKEDT ASSGN SYSLNK,UA * * * * * * * Now run the app * // EXEC PDPTEST,SIZE=AUTO,PARM='PaulEdwards two Three' And here is the program itself: 000000 40D7C8C1 E2C540D7 C4D7E3C5 E2E36BE2 PHASE PDPTEST,S 000010 4EE77DF0 F0F0F0F5 F07D4040 40404040 +X'000050' 000020 40404040 40404040 40404040 40404040 000030 40404040 40404040 40404040 40404040 000040 40404040 40404040 40404040 40404040 000050 02C5E2C4 40404040 40400010 40400001 .ESD .. .. 000060 D7C4D7E3 C5E2E340 007000C8 40001330 PDPTEST ...H ... 000070 40404040 40404040 40404040 40404040 000080 40404040 40404040 40404040 40404040 000090 40404040 40404040 40404040 F0F0F0F1 0001 0000A0 02E3E7E3 407000C8 40400038 40400001 .TXT ..H .. .. 0000B0 47F0F010 D7C7C3E7 00000004 00000000 .00.PGCX........ 0000C0 5810F070 58101000 12114780 F02C90EC ..0.........0... 0000D0 D00C41D0 D05018CF 47F0C040 18CF187E }..}}&...0{ ...= 0000E0 5830C074 5840C078 40404040 F0F0F0F2 ..{.. {. 0002 0000F0 02E3E7E3 40700100 40400038 40400001 .TXT ... .. .. 000100 5850C07C 41D0C088 4190D050 5090D04C .&{@.}{h..}&&.}< 000110 58F0C080 05EF58F0 C07418E7 5810C070 .0{....0{..X..{. 000120 58101000 12114780 C06E5BD0 C08458E0 ........{>$}{d.\ 000130 D00C980C D01407FE 40404040 F0F0F0F3 }.q.}... 0003 000140 02E3E7E3 40700138 40400038 40400001 .TXT ... .. .. 000150 007000D4 00000003 00000004 00000005 ...M............ 000160 0070122C 00000050 00000000 00000000 .......&........ ... 001AB0 05EF1F22 18F258D0 D00458ED 000C980C .....2.}}.....q. 001AC0 D01407FE 00000000 D4C1C4C5 40C9E35A }.......MADE IT! 001AD0 00000150 00701340 40404040 F0F0F8F5 ...&... 0085 001AE0 02E3E7E3 40701328 40400038 40400001 .TXT ... .. .. 001AF0 09000000 00000000 00701344 FFFF8000 ................ 001B00 00000007 00000008 00701250 47F0F00A ...........&.00. 001B10 055F5F73 766390EC D00C58F0 D04C50D0 .^^.....}..0}<&} 001B20 F00450F0 D00818DF 40404040 F0F0F8F6 0.&0}... 0086 001B30 02E3E7E3 40701360 40400038 40400001 .TXT ..- .. .. 001B40 18B105C0 5AF0C080 50F0D04C 58A0C084 ...{!0{.&0}<..{d 001B50 5820C088 58202000 12224770 C040D203 ..{h........{ K. 001B60 D058B000 D203D05C B004D203 D060B008 }...K.}*..K.}-.. 001B70 4110D058 58F0C08C 40404040 F0F0F8F7 ..}..0{. 0087 001B80 02E3E7E3 40701398 40400038 40400001 .TXT ..q .. .. 001B90 05EF182F 5020D068 47F0C06E 5820C088 ....&.}..0{>..{h 001BA0 58202000 D203D058 B000D203 D05CB004 ....K.}...K.}*.. 001BB0 D203D060 B0085820 220C4110 D05841F0 K.}-........}..0 001BC0 200005EF 182F5020 40404040 F0F0F8F8 ......&. 0088 001BD0 02E3E7E3 407013D0 40400028 40400001 .TXT ..} .. .. 001BE0 D06858F0 D06858D0 D00458ED 000C980C }..0}..}}.....q. 001BF0 D01407FE 00000070 007013F4 007000D4 }..........4...M 001C00 007010F0 0

This has only just started working, so there may still be issues, but the linker pdld.exe has now been proven to be able to create an unloaded DOS/VS phase - offline - ie on Windows. The code is C90-compliant so should work anywhere, including VSE itself. I am planning on using the minimal possible assembler to get PDPCLIB operational - as a precursor to doing the same on CMS and MVS. And this is also the precursor to getting z/PDOS-generic to operate as a mini VSE clone similar to how PDOS-generic currently acts as a mini Amiga clone. That will require a modification to sapstart.asm to allow forwarding of SVCs to the C code. Although another way is to avoid doing the SVC calls entirely and get the VSE program to detect that it is running under an SVC-less environment and switch to doing callbacks for the SVC routine is possible. Regardless, going forward, almost everything will be in C instead of assembler, unless I'm missing something fundamental. Before you say - all the interfaces are designed as assembler macros - you need to use assembler just like on MSDOS - well - just like MSDOS, you can have C wrappers for those APIs and they all end up as calls to int86x which is the only thing that needs to be written in assembler. If you look at the MSDOS 4 source that Microsoft released, you can see that they actually did that for MSDOS - they created functions like DosWrite() very similar but not identical to OS/2 DosWrite() - but apparently didn't want people to have this C interface to MSDOS and wanted them to use OS/2 instead. To do it offline, you need an assembler too. That is from a forked binutils 2.14a, ie gas, and I call it as370.exe. Both pdld.exe and as370.exe are in the "dos" directory of the VHD available from pdos.zip at https://pdos.org (look where it says "hard drive image"). They are both Windows programs meaning you can run them under real Windows or PDOS/386 (which is effectively a mini-clone of Windows unless you want to quibble about the definition of "mini", quibble about the definition of "clone", quibble about the definition of "Windows", or quibble about the definition of "of" - you know who you are and you have way too much free time). as370.exe produces ELF. pdld.exe accepts as input either ELF or standard object code as produced by the DOS/VS assembler (and then punched - that's why I was asking how to punch object code). And you can mix them. The linker will match lowercase hello_there in an ELF object to HELLO@TH in DOS/VS object file. Note that punching a phase for transportation (similar to doing an IEBCOPY unload on MVS) produces a fully-resolved object file and it is this that pdld outputs. In fact, pdld outputs for MVS too, and it is in fact an IEBCOPY unload too (quibbling aside). So you need to process that using LNKEDT to put it in the CIL (or some equivalent for z/VSE or VSEn). The assembler as370 is only semi-hlasm-compatible. You can see what the assembler code looks like here: https://sourceforge.net/p/pdos/gitcode/ci/master/tree/pdpclib/mfsupa.asm and I test it by running this: https://sourceforge.net/p/pdos/gitcode/ci/master/tree/pdpclib/pdpvse2.bat which runs on VSE/380 (note that the documentation is wrong and the VSE380 environment variable should point to c:\vse380\run or whatever - add the "run"), but it should be simple enough to adjust for whatever VS or VSE environment you are using. The program as it currently stands just has an assembler program calling a C function that returns 6 in R15 and then the assembler goes into a loop so that you can see that in Hercules by pressing ESC. I'll switch it to do something WTO-like in the future and then expand until I have a new version of PDPCLIB almost entirely in C. And have z/PDOS-generic updated each step of the way. Note that there is no barrier to making as370 more hlasm-compatible and also I am thinking I might use the C preprocessor to have conditional assembly so that both the DOS/VS assembler and as370 can handle it while waiting for that to happen. Note that I am having fun probing the "new" environment from the safety

There is a WTO macro documented in the z/VSE manuals. But when I tried using WTO in my assembler code on DOS/VS it said there was no such macro. Does it exist, and if it does, is there something I need to do to use it? Or is there some other similar simple macro to display a message somewhere? Thanks. Paul.

Has anyone found a copy of the installation tapes for this specialized operating system. PS/44 was designed for the s/360 Model 44, and only allowed Fortran to run. John Rankin

The following files and folders have been uploaded to the Files area of the H390-DOSVS@groups.io group. /44-MPS.BAL By: Mark Waterbury <mark.s.waterbury@...> Description: Source code for MPS for 360 model 44, recovered from old SHARE SPLA tapes. The following files and folders have been uploaded to the Files area of the H390-DOSVS@groups.io group. /44-MPS_030014.pdf By: Mark Waterbury <mark.s.waterbury@...> Description: Documentation for 44-MPS, from SPLA - the SHARE Program Library Agency. The following files and folders have been uploaded to the Files area of the H390-DOSVS@groups.io group. /PS44-MPS/44-MPS_030014.pdf By: Mark Waterbury <mark.s.waterbury@...> Description: 44-MPS documentation from SHARE Program Library Agency.

The following files have been uploaded to the Files area of the H390-DOSVS@groups.io group. /dosvtp3.8.zip By: Gary Cozzolino <gcozzie@...> Description: new version of vtp for dos/vs

I distinctly remember using a product called SPM (Source Program Maintenance?) when I worked in a DOS/VS Rel 34 shop between 1977 and 1979. It was a full-screen 3270 editor, similar to SPF. I don't think I've ever seen it mentioned here. Does anyone have any info or fills? I sort of doubt that it's available but it never hurts to ask. Shawn Goodin

Does anyone have the DOS/VS R34 source files or know where to get them?

Hello everybody I know that my questions may be stupid but .. 1. How to remove (delete) BSAM dataset from DASD? In MVS I just use DISP=DELETE and IEFBR14, but how to remove sequenced dataset, previously allocated with DLBL and EXTENTs in JCL? 2. If I define DLBL and EXTENTs in JCL, but phase exuting in HOB STEP not touch (open, write) the file - will any extend will be allocated and enty in VTOC created? 3. If I have 2 extents defined, and program write data only for one extend (small record) will second extent will be allocated? I have strange observation and could not find the answers in available documentation Thanks Piotr P.S Sorry for my unfinished previous message, I've incidentally press the enter.

I worked on DOS/VS systems back in the mid- to late 1970's. While DOS/VS has some extent protections as mentioned, actual management of space on volumes is manually performed. This was usually managed by the system programmer's. The sysprog (usually only one) had to know what was where. Areas for each partition were reserved for work files. These were usually the same area on separate volumes of the same DASD type and attached to the different partitions by means of the same LU number. That would allow a programmer to have his batch programs jobs run in any of partitions with the same JCL. And while a VTOC entry can be removed, its data on the volume remains until physically overwritten, eventually. Of course, with Hercules it is extremely easy to add physical volumes to the configuration. But not quite so easy to add them to the DOS/VS Supervisor. That requires a new assembly. Like others, I am sure I forgot a lot of details since then. But the amount of human work to manage the DOS/VS system was significant. With just a single user, that is not as complicated as it sounds. I would encourage you to understand exactly how the system is set up. If you already do understand that, wonderful. If not do so. The acts of learning this information will itself educate you. DOS/VS is dumb. You are the smart one. Those who have worked with DOS/VS system you have certainly were smart. So some of what I refer to may already be inherent in the system. Still you need to understand it. WATCH THE OPERATOR CONSOLE. It will save you! Or KILL you. I worked in a shop where the operators did not understand the console or the messages. Shop was new to DOS/VS. When an operator's message came up they would just hit enter. That was hell! ENTER is in many cases NOT the right response. Harold Grovesteeen On 1/23/24 14:34, Piotr Kolasiński wrote:

I am trying to find complete source distribution for POWER II. Sadly the AWS file that we have seems to be missing at least A.POWERPRT, A.POWERPUN, A.POWERRDR, and A.POWERCOM which is the meat of POWER II. This would be for use under DOS/360. Any leads appreciated!

The following files and folders have been uploaded to the Files area of the H390-DOSVS@groups.io group. /hello_99bottles_pi.zip By: Doug Wegscheid <dwegscheid@...> Description: "Hello world" and "99 bottles of beer on the wall" in assembler, Cobol, FORTRAN, and PL/I, as well as a PL/I program to calculate digits of pi. All tested on DOS/VS, probably will work on DOS/360. A place for the neophyte to start. Some of these are directly from prior postings in this list (thank you, René!)

Hello everyone, I have been trying to run this very simple Hello World assembler program on George Shedlock 5-pack and the execution fails: PRINT ON,GEN,DATA HELLO START 0 BALR 12,0 USING *,12 OPEN PRINTER PUT PRINTER,$HELLO CLOSE PRINTER EOJ PRINTER DTFPR X BLKSIZE=81, X CTLCHR=ASA, X DEVADDR=SYSLST, X IOAREA1=PRTIO1, X IOAREA2=PRTIO2, X WORKA=YES LTORG * PRTIO1 DS CL81 PRTIO2 DS CL81 $HELLO DS 0CL81 DC C'1' DC CL15'Hello, World! ' DC 65C' ' END HELLO BG // JOB HELLO - HELLO WORLD IN DOS/VS ASSEMBLER (RF, 2020/04/18) DATE 04/19/20,CLOCK 18/09/23 BG 0S03I PROGRAM CHECK INTERRUPTION - HEX LOCATION 00000C - CONDITION CODE 0 - OPERATION EXCEPTION 0S00I JOB HELLO CANCELED BG EOJ HELLO DATE 04/19/20,CLOCK 18/09/23,DURATION 00/00/00 The program check seems to come from a missing module. After the expansion of the DTFPR macro, I can see this: 000049 000000 41+ DC VL3(IJDFAZIW) ADDR OF LOGIC MODUL3-8 76800025 and the link editor writes: UNRESOLVED EXTERNAL REFERENCES EXTRN IJDFAZIW 001 UNRESOLVED ADDRESS CONSTANTS I check the system relocatable library and while IJDFAZIZ is there, IJDFAZIW is not. Where is the missing module? Or is the problem somewhere else? Rene FERLAND, Montreal

Looking at Professor Ferland's supervisor build from the Moshix M92 video, I see that there are additional unit record devices defined. I have a sockdev reader defined in my hercules config at x'02c', running the $$a$sup1 supervisor in the Shedlock 5 pack. Submitting a job to that reader does not seem to do anything, until I did a PSTART RDR,02C. If I IPL the Beaulieu system (using the $$a$supt supervisor), I can submit jobs to the reader at x'02c' just fine without manually issuing a PSTART. Looking at GC33-5403-1 DOS/VS Power/VS Installation and Operations (Sept 74), there are probably a PSTART for the reader at 02C in the autostart deck on the Beaulieu system. How does a novice change the AUTOSTART deck?

So far, I've discovered the FFORTRAN and PL/I Compilers on the Shedlock system. Haven't tried COBOL yet. I'll probably end up just making a new supervisor with everything set up for 2314 work files. In Professor Ferland's videos, I thought I heard that RPG could be installed, as well as higher level compilers for the other languages. Can anyone point this novice in the correct direction for getting those installed?

I'm wanting to get a DOS360 or DOS/VS (preferably) running. I'm looking for something that I can just do compile and run for PL/I, Cobol, and (hopefully) FORTRAN. I grabbed the dosvs5pack-v1r0m1*.zip files from the yahoo groups archives, and got it running (had to adjust the configuration for case-sensitivity, I host on Linux). Apparently it was put together by Michel Beaulieu. I see references to a 5-pack by Shedlock. Are they the same? If not, which is preferable for my load-and-go scenarios? (and where do I find the latter?).