开云体育

Hello Bertram, Well, I tried with 16 disks, BGM380 to BGM38F, and guess what, it works... all 16 disks are attached to the system! So, at this point, I am inclined to say you are doing something

Hello René of Montréal and et al, I got 380-383 (BGM380-BGM383) to attach at IPL time. When I tried the next group of four (384-387 / BGM384-BGM387), none of this group showed up, but the drives

Hello René of Montréal, Again, thank you so very much for working on this issue. I successfully reproduced your success with my system. My system's DMKSYS and SYSUSR work file with two 3380 devices.

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

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

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

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:

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

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

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]

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),

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

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

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,

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:

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

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

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

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

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