This group is for all folks running the original IBM VM/370 Release 6 operating system (or later (e.g. VMTCE (Community Edition)) on Hercules. Like the other early IBM operating systems this version has always been in the public domain and so can be freely distributed. The base version as supplied by IBM is lacking in many facilities. IBM solved this by providing additional extension products which were licensed and so are not available. There are however many user enhancements available which can be installed. In addition, in order to get users up and running quickly updated "releases" of VM/370 included the most popular updates are available for download, so novices can start to learn VM without having to delve into the system internals. It is intended that this wiki will provide information on the base release and these updates.
The available versions are here :-
?
?
|
ASSIST port question
Mark Stevens, Are the files on the TAPEMAP 191 disk on VM370CE any part of the ASSIST port to CMS that you were working on? Thanks/Bob
By
Bob Bolch
·
#4100
·
|
|
Re: Minidisk allocation planning
Hi Bob, yes, my wrong...guessing free device addresses in conjunction with dev types is a bad idea. I've checked dmkrio assemble on F (not dared to change it) and looked up a free address for a 3350 -
By
Michael Grom
·
#4099
·
|
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Thanks Ren¨¦, that worked like a charm it seems. regards Michael
By
Michael Grom
·
#4098
·
|
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Michael, to avoid this problem I run the remote sessions under tmux - you can also use screen. This makes sure that losing (or hanhing up) a connection does not interfere with you hercules
By
[email protected]
·
#4097
·
|
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Michael, Maybe others can help. I just don't understand anything about your environment, because I don't have the background experience required. I can say that the startup and shutdown of VM
By
Bob Bolch
·
#4096
·
|
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Bob, the thing is, I have to start hercules from a ssh session on a remote server which is not supposed to be open all time. Normally, when the ssh session terminates, the running shell at the
By
Michael Grom
·
#4095
·
|
|
Re: Minidisk allocation planning
Hi Michael, I could better understand what you are doing if you tell me what commands you issued, what the responses are, and what the error messages say. I do know that 6D5 is defined to the system
By
Bob Bolch
·
#4094
·
|
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Michael, I do not understand what you are trying to do here. When the documented procedure to bring up VM/370 is followed, the user ID "OPERATOR" is logged on. That ID is used to issue the various
By
Bob Bolch
·
#4093
·
|
|
Hercules with VM/370 on Linux in the background - erronous behaviour
Dear Group, while fiddling with the user directory, I noticed a strange behaviour with hercules that I haven't seen from hercules running TK4- on the same machine. I usally start hercules for mvs with
By
Michael Grom
·
#4092
·
|
|
Re: Minidisk allocation planning
Thanks Bob, I will probably do so - especially because I ran into another trouble: DMKLNK117E USERID VSAMIO NOT LINKED; VOLID 191 CONFLICT what happened? created disk image using dasdinit of type 3350
By
Michael Grom
·
#4091
·
|
|
Re: Minidisk allocation planning
VMCE supplies two preconfigured empty disk packs, labelled VM50U0 and VM50U1 that are to be used only for information put there by the end user. If you use those disk packs for installation specific
By
Bob Bolch
·
#4090
·
|
|
Re: Minidisk allocation planning
Hi Dave, thanks for the pointer. Using a dedicated new pack is definitely a good point here, not meddling with the distribution packs. kind regards Michael
By
Michael Grom
·
#4089
·
|
|
Re: Minidisk allocation planning
Michael, Try ¡°DISKMAP¡±. Its on MAINT¡¯s B disk but there is a help file. I would say though if you want more minidisks add a pack for yourself. Makes upgrades simpler. Dave Sent: 14 March 2022
By
Dave Wade
·
#4088
·
|
|
Minidisk allocation planning
Dear Group, is there a way to figure out if there is place for? a (new) minidisk allocation on a volume? kind regards Michael
By
Michael Grom
·
#4087
·
|
|
Re: COBOL compile error
Found in the "extended sixpack" direct. :-) Now transferring to my VM/370 installation.. kind regards Michael
By
Michael Grom
·
#4086
·
|
|
Re: COBOL compile error
Dear Ren¨¦, downloaded your 6pack, ipl'ed VM and searched the sixpack direct up and down for that virtual machine, to no avail. kind regards Michael
By
Michael Grom
·
#4085
·
|
|
Re: COBOL compile error
Michael, Be aware, again, that in Moshix video M94, VSAMIO usage is illustrated on a cloud extended Sixpack 1.2, which is different from VM/370 CE. In particular, the VSAMIO minidisk containing the
By
Ren¨¦ Ferland
·
#4084
·
|
|
Re: COBOL compile error
Thanks :-) didn't know about that ... much easier than my MOVEFILE approach with FILEDEFs Am 13.03.2022 um 12:44 schrieb Dave Wade:
By
Bernd Oppolzer
·
#4083
·
|
|
Re: COBOL compile error
WHy? COPYFILE (REPL is fine. It creates a new file and then renames the source at the end. Dave Sent: 13 March 2022 09:20 To: [email protected] Subject: Re: [h390-vm] COBOL compile error Hello
By
Dave Wade
·
#4082
·
|
|
Re: COBOL compile error
Michael, Yes it needs FB80 so :- copy mycob cobol a = = = (repl recfm f lrecl 80 or before you save in EE do RECFM F LRECL 80 You can customize it with a PROFILE EE file to set COBOL to be FB80
By
Dave Wade
·
#4081
·
|