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 :-
?
?
|
Re: I forgot the VOLSER of drives (3380) I created
Or use an exec like this: * * Usage: VMFEE fn ctlfile * VMFEE fn ft ctlfile * * Like VMFASM, update the given ASSEMBLE file with the UPDATES * (given as the fn of the CNTRL file) * but call EE
By
Rhialto
·
#5755
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
I have never done that! I think its a pain as EE does not support UPDATE directly. So you end up using UPDATE to generate an updated source, make a copy, edit with EE, use XCOMPARE to generate a new
By
Dave Wade
·
#5754
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
I just check: it works with or without shadow files, whether the disks are compressed or not, and whether I use SDL Hercules 4.7 or Hercules 3.13. Cheers, Ren¨¦ FERLAND, Montr¨¦al
By
Ren¨¦ Ferland
·
#5753
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Hello and thank you for the information on 3380 drives. While I have you here, what is the command syntax for edit and ee for using updates? Bertram Moshier [email protected]> wrote:
By
Bertram Moshier
·
#5752
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Hello and thank you for your reply and trying to reproduce what I am seeing. I see some noticeable differences. I am using uncompressed drives and 16 3380 drives. I will try removing BGM382-BGM38F and
By
Bertram Moshier
·
#5751
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Hello Bertram, I took a freshly downloaded copy of VM/370 CE. I started it, updated the SYSUSR statement in DMKSYS with two 3380 disks, BGM380 and BGM381, specified AFTER the VM14-* disks. Then I
By
Ren¨¦ Ferland
·
#5750
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Read the docs:- VMSETUP CP EE HRCMODS MEMO F => lists all mode EE HRC011DK MEMO F => 3380 support Only MINIDISKS and DEDICATED supported. Dave Sent: Sunday, May 19, 2024 8:48 AM To: [email protected]
By
Dave Wade
·
#5749
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Hello, I'm wondering there could be a bug-preventing VM from attaching these 3380 (380-38F, BGM380-BGM38F) via the SYSUSR macro? I can attach the drives manually (e.g., CP ATTACH 380 SYSTEM BGM380),
By
Bertram Moshier
·
#5748
·
|
|
Re: SYSIPL macro in DMKSYS
Hello, and thank you for your reply. What do people think of having VM support going down the list concerning IPL startup? By this, I mean that if WARM fails, failover to CKPT, etc., if allowed by the
By
Bertram Moshier
·
#5747
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Hello, I corrected DMKSYS ASSEMBLE by putting the comma in the correct place. ===== SYS TITLE 'DMKSYS FOR 3350 RELEASE 6' ===== DMKSYS CSECT ===== COPY OPTIONS ===== SYSOWN
By
Bertram Moshier
·
#5746
·
|
|
Re: SYSIPL macro in DMKSYS
SYSIPL seems to be an addition to VM/370 by the Hercules community. The file SYSIPL MACRO is located on minidisk 094 of MAINT. I am sure some people in this group can tell you more about it. Cheers,
By
Ren¨¦ Ferland
·
#5745
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Olaf 'Rhialto' Seibert wrote: [...] Hmmm... Not a half bad idea. Let me think on it for a while. -- "Fish" (David B. Trout) Software Development Laboratories http://www.softdevlabs.com mail:
By
Fish Fish
·
#5744
·
|
|
SYSIPL macro in DMKSYS
Hello, I've been reading through the various VM Planning guides looking for information on the SYSIPL macro, but I can't find any, even in the R6 PLC17 or VM/SP R3 manuals.? Where can I find
By
Bertram Moshier
·
#5743
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
One potential improvement to dasdinit I see is that it could check the filename extension of the dasd file. If it ends in .cckd, but no compression option is given, complain loudly. And the other case
By
Rhialto
·
#5742
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Ren¨¦ Ferland wrote: Correct. If you want the fix, you will have to either wait until the next release of officially released, or else build the development version ('develop' branch) of Hercules
By
Fish Fish
·
#5741
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Hello rene, Thank you for your useful reply and link. A missing comma, yup, it has been awhile since I was seriously programming in assember. I even thought about putting the drives on the same line
By
Bertram Moshier
·
#5740
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
This is expected behaviour for dasdls as is. Your dasdinit command creates an emulated DASD with a VOL1 label containing the VOLSER you specified but no VTOC (address) yet, and that's what dasdls is
By
Ren¨¦ Ferland
·
#5739
·
|
|
Re: I forgot the VOLSER of drives (3380) I created
Hello, I'm seeing several issues.? I'm hoping to find solutions and learn at the same time. * I create a drive (file) using the dasdinit command, but dasdls isn't finding the VOLSER. * I'm trying to
By
Bertram Moshier
·
#5738
·
|
|
Re: To merge shadow files, or not to merge shadow files ...
[email protected]> wrote: [...] 1) If your system supports SATA (which was very normal by 2009, though probably 3 MB/s) then there are SSD drives that will plug in. SATA doesn't care about the drive
By
Tony Harminc
·
#5737
·
|
|
Re: Port of SQLITE ?
I'm playing with porting SQLite to VM/370 CE CMS. It may not be possible - I have to solve a few issues around truncating files and committing data to disk. Both of those are outside the normal realm
By
Ross Patterson
·
#5736
·
|