Re: I forgot the VOLSER of drives (3380) I created
>> Are we running the same version of VM/CE even with fixes?
As I wrote before, I tested on a freshly downloaded VM/370 CE R1.2.
>> I want to thank you for testing this with me.
My pleasure. :-)
>> What are your thoughts on figuring out my issue? How can I diagnose this problem?
Well, like me, try it on a freshly downloaded version of VM/370 CE R1.2. If it works there, then the problem lies with your current system somehow. That would be some progress.
Cheers,
Ren¨¦ FERLAND, Montr¨¦al
|
Re: Trying to access 191 give DMSLIO109S
If I recall correctly, a 3380 only has 885 cylinders, not 886. (Unless you're using 'E' or 'K' models, but I'm not sure if VM/CE supports those.)
On Sun, May 19, 2024 at 7:18?PM Bertram Moshier via <herc370390vm= [email protected]> wrote: Hello,
I'm getting DMSLIO109S when trying to access my 191 mini-disk.? It is a 3380 (the entire drive 000 to 886).? How large of a mini-disk does VM/CE support for 3380 DASD?
Thank you.
|
Re: I forgot the VOLSER of drives (3380) I created
Hello?
Ren¨¦,
Yeah, I need to agree with you both that it is something?here and I have zero idea where to go from here.
Are we running the same version of VM/CE even with fixes?
I want to thank you for testing this with me. What are your thoughts on figuring out my issue? How can I diagnose this problem?
Bert
On Sun, May 19, 2024 at 5:49?PM Ren¨¦ Ferland via <ferland.rene= [email protected]> wrote: On Sun, May 19, 2024 at 02:27 PM, Bertram Moshier wrote:
So, what might be happening? Is this a bug, or am I doing something wrong (other than wanting more than four 3380 drives attached via DMKSYS at IPL time)?
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 wrong. What exactly? I can't tell. :-(
Cheers,
Ren¨¦ FERLAND, Montr¨¦al?
|
Trying to access 191 give DMSLIO109S
Hello,
I'm getting DMSLIO109S when trying to access my 191 mini-disk.? It is a 3380 (the entire drive 000 to 886).? How large of a mini-disk does VM/CE support for 3380 DASD?
Thank you.
|
Re: I forgot the VOLSER of drives (3380) I created
On Sun, May 19, 2024 at 02:27 PM, Bertram Moshier wrote:
So, what might be happening? Is this a bug, or am I doing something wrong (other than wanting more than four 3380 drives attached via DMKSYS at IPL time)?
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 wrong. What exactly? I can't tell. :-( Cheers, Ren¨¦ FERLAND, Montr¨¦al?
|
Re: I forgot the VOLSER of drives (3380) I created
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 (6D0-6D3 / VM14-0 through VM14-3) did become attached to the system. ===== ? ? ? ? ? ? ? ?KICKS0,VSAMIN, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
=====? ? ? ? ? ? ? ? BGM380,BGM381,BGM382,BGM383, ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?BGM384,BGM385,BGM386,BGM387, ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?VM14-0,VM14-1,VM14-2,VM14-3 ? ? ? ? ? ? ? ? ? ? ? ? ? ? X
15:59:40 DASD 380 CP SYSTEM BGM380? ?000
15:59:40 DASD 381 CP SYSTEM BGM381? ?000
15:59:40 DASD 382 CP SYSTEM BGM382? ?000
15:59:40 DASD 383 CP SYSTEM BGM383? ?000
15:59:40 DASD 6A0 CP SYSTEM GCCBRX ? 001
15:59:40 DASD 6A1 CP OWNED ?VM50-1? ?018
. . .
15:59:40 DASD 6D0 CP SYSTEM VM14-0? ?001
15:59:40 DASD 6D1 CP SYSTEM VM14-1? ?001
15:59:40 DASD 6D2 CP SYSTEM VM14-2? ?001
15:59:40 DASD 6D3 CP SYSTEM VM14-3? ?001
Next, I changed to adding the fifth 3380 (384 / BGM384) to the attached system list via DMKSYS, and it failed!
===== ? ? ? ? ? ? ? ?KICKS0,VSAMIN, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?BGM380,BGM381,BGM382,BGM383, ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?BGM384, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? X
===== ? ? ? ? ? ? ? ?VM14-0,VM14-1,VM14-2,VM14-3
The DASD list stayed the same from the above. I even verified that 384 / BGM384 was in the DMKSYS TEXT file. It looks like the maximum number of 3380 drives you can attach at IPL time is four, but why only four? I say four 3380 only because there are thirteen 3350 drives (6A0-6A8, 6AC-6AD, 6B0-6B1) attached at IPL time. So, what might be happening? Is this a bug, or am I doing something wrong (other than wanting more than four 3380 drives attached via DMKSYS at IPL time)? Bertram Moshier of Chicago
WB8ERT
|
Re: I forgot the VOLSER of drives (3380) I created
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.? This result tells me: - There is an issue with the number of 3380 drives the system can automatically attach via SYSUSR?OR
- There is an issue with the maximum number of drives (of any type) the system can bring online via SYSUSR?or total (SYSOWN?and?SYSUSR) at IPL time.
If the problem is the second (maximum drives regardless of type), some 3380 drives would be attached to the system. Yet, I see that drives VM50-5 through?VM14-3 show up, but none of the 3380 drives. Given what we're seeing in our testing, shouldn't at least two of them BGM380 and BGM381) show up?? As for the first, I doubt this is the case, but it is possible. Any thoughts on: - Where does the problem lie?
- How can I (we) go about diagnosing this issue?
Thank you, Bertram Moshier of Chicago WB8ERT
On Sun, May 19, 2024 at 4:14?AM Ren¨¦ Ferland via <ferland.rene= [email protected]> wrote: On Sun, May 19, 2024 at 12:48 AM, Bertram Moshier wrote:
Can someone try attaching it 3380 drives via SYSUSR, please?
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 rebuilt the CP nucleus, and stopped the system. After that, I created two (compressed) emulated 3380 disks with dasdinit, updated the configuration file vm370ce.conf for them (on cuu 380 and 381), and started the system. Once the IPL was complete, a query dasd shows the two disks, right at the top of the list, attached to the system. So it works for me. I have no idea what is going wrong for you.
Cheers,
Ren¨¦ FERLAND, Montr¨¦al?
|
Re: I forgot the VOLSER of drives (3380) I created
On Sun 19 May 2024 at 10:42:44 -0700, Dave Wade wrote: On Sun, May 19, 2024 at 10:59 AM, Bertram Moshier wrote:
While I have you here, what is the command syntax for edit and ee for
using updates?
Bertram Moshier
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 update file
Dave 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 to show the result (using $fn ft A). * * If you don't specify the file type, it is assumed to be ASSEMBLE * like with VMFASM. * * If you save changes, a file "$fn UPDATE" is created. * * If this file already exists when invoking this exec, * the updates are not re-done, but you can edit from where you left * off. * If you don't save changes, the temporary files are removed. * &CONTROL OFF &IF &INDEX LT 3 &GOTO -ARGS2 -ARGS3 &NAME = &1 &FT = &2 &CNTL = &3 &GOTO -ARGDON -ARGS2 &NAME = &1 &FT = ASSEMBLE &CNTL = &2 * -ARGDON &UPNM = $&NAME &ANAME = &UPNM &EDITOR = EE * -STSYS STATE &NAME &FT * &IF &RETCODE EQ 0 &GOTO -STCTL &TYPE *** &NAME &FT NOT FOUND *** &EXIT 1 * -STCTL STATE &CNTL CNTRL * &IF &RETCODE EQ 0 &GOTO -STUPD &TYPE *** &CNTL CNTRL NOT FOUND *** &EXIT 2 * Did we edit this file before? -STUPD &TYPE STATE &ANAME UPDATE A STATE &ANAME UPDATE A &IF &RETCODE EQ 0 &GOTO -DOEDIT * Do the update -FUPD UPDATE &NAME &FT * &CNTL CNTRL * ( CTL STK &IF &RETCODE EQ 40 &ANAME = &NAME &IF &RETCODE GT 12 &IF &RETCODE NE 40 &GOTO -UPDERR * Get most recent update level &IF &READFLAG EQ CONSOLE &GOTO -EXIT &READ ARGS &TEXT = &2 &READ ARGS &ARGS &2 &3 &4 &5 &6 &7 &8 &9 * &BAKFT = BAK&FT COPY &ANAME &FT A = &BAKFT = (REPLACE -DOEDIT &TYPE EDITING &ANAME &FT ... UPDATE &TEXT &EDITOR &ANAME &FT &GLOBAL0 = &RETCODE &TYPE EDITED " &NAME &FT " ... UPDATE " &TEXT " * Automatically generate some update statements from * the differences, and put them in fn UPDATE A. XCOMPARE &ANAME &BAKFT A = &FT = (CMSUPD * Did the user change something? STATE &ANAME UPDATE A &IF &RETCODE EQ 0 &GOTO -UPDATED * Since we didn't edit the file we may as well remove it ERASE &ANAME &FT A ERASE &ANAME &BAKFT A &GOTO -EXIT * -UPDATED &IF &RETCODE EQ 0 &TYPE UPDATE FILE " &ANAME UPDATE A " CREATED -EXIT &EXIT &GLOBAL0 -Olaf. -- ___ Olaf 'Rhialto' Seibert <rhialto/at/falu.nl> \X/ There is no AI. There is just someone else's work. --I. Rose
|
Re: I forgot the VOLSER of drives (3380) I created
On Sun, May 19, 2024 at 10:59 AM, Bertram Moshier wrote:
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
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 update file Dave
|
Re: I forgot the VOLSER of drives (3380) I created
On Sun, May 19, 2024 at 02:56 AM, Bertram Moshier wrote:
Did you also use shadow files?? I assume you did use shadow files.
?
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?
|
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
Read the docs:- ? VMSETUP CP EE HRCMODS MEMO F => lists all mode EE HRC011DK MEMO F => 3380 support ? Only MINIDISKS and DEDICATED supported. ? Dave ? ? 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), but VM fails to attach the drives to SYSTEM st IPL time. Ah, does VM via DMKSYS support 3380?? Just a thought, is all. Can someone try attaching it 3380 drives via SYSUSR, please?? Can 3380 drives be CP OWNED drives (e.g., paging, nucelus, spool, temp, etc)?? Maybe I missed a restriction in the 3380 support for VM/370 CE. I'm just trying where I made my mistake, or is there a bug.
|
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 see what happens.? If it is still failing, I'll try using compressing the drives. Did you also use shadow files?? I assume you did use shadow files. I will let the group know my results.
Bertram Moshier
On Sun, May 19, 2024, 04:14 Ren¨¦ Ferland via <ferland.rene= [email protected]> wrote: On Sun, May 19, 2024 at 12:48 AM, Bertram Moshier wrote:
Can someone try attaching it 3380 drives via SYSUSR, please?
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 rebuilt the CP nucleus, and stopped the system. After that, I created two (compressed) emulated 3380 disks with dasdinit, updated the configuration file vm370ce.conf for them (on cuu 380 and 381), and started the system. Once the IPL was complete, a query dasd shows the two disks, right at the top of the list, attached to the system. So it works for me. I have no idea what is going wrong for you.
Cheers,
Ren¨¦ FERLAND, Montr¨¦al?
|
Re: I forgot the VOLSER of drives (3380) I created
On Sun, May 19, 2024 at 12:48 AM, Bertram Moshier wrote:
Can someone try attaching it 3380 drives via SYSUSR, please?
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 rebuilt the CP nucleus, and stopped the system. After that, I created two (compressed) emulated 3380 disks with dasdinit, updated the configuration file vm370ce.conf for them (on cuu 380 and 381), and started the system. Once the IPL was complete, a query dasd shows the two disks, right at the top of the list, attached to the system. So it works for me. I have no idea what is going wrong for you. Cheers, Ren¨¦ FERLAND, Montr¨¦al?
|
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 ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Bertram Moshier via groups.io
Sent: Sunday, May 19, 2024 8:48 AM
To: [email protected]
Subject: Re: [h390-vm] 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), but VM fails to attach the drives to SYSTEM st IPL time. Ah, does VM via DMKSYS support 3380?? Just a thought, is all. Can someone try attaching it 3380 drives via SYSUSR, please?? Can 3380 drives be CP OWNED drives (e.g., paging, nucelus, spool, temp, etc)?? Maybe I missed a restriction in the 3380 support for VM/370 CE. I'm just trying where I made my mistake, or is there a bug.
|
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), but VM fails to attach the drives to SYSTEM st IPL time.
Ah, does VM via DMKSYS support 3380?? Just a thought, is all.
Can someone try attaching it 3380 drives via SYSUSR, please?? Can 3380 drives be CP OWNED drives (e.g., paging, nucelus, spool, temp, etc)?? Maybe I missed a restriction in the 3380 support for VM/370 CE.
I'm just trying where I made my mistake, or is there a bug.
Bertram Moshier WB8ERT
|
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 SYSIPL macro.
Examples of these are:
SYSIPL? WARM and CKPT. This would mean that if WARM fails, then go to CKPT, and if it fails, then present the prompt to the operator. If SYSIPL?was WARM, Force the system would not do a?COLD start leaving it to the operator.
Bertram Moshier
On Fri, May 17, 2024 at 6:57?PM Ren¨¦ Ferland via <ferland.rene= [email protected]> wrote: On Fri, May 17, 2024 at 04:26 PM, Bertram Moshier wrote:
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 documentation on this macro?? I should remember, but don't, where the MACLIB is for the DMKSYS macros.
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,
Rene FERLAND, Montreal
|
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 (VM50-1,TEMP),(VM50-2,PAGE),(VM50-3,TEMP),(VM50-4,PAGE)
===== ? ? ? ? ?SYSUSR VM50-5,VM50-6,VM50-7,VM50-8,VM50U0,VM50U1,GCCBRX, ? ? ?X
===== ? ? ? ? ? ? ? ?KICKS0,VSAMIN, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?VM14-0,VM14-1,VM14-2,VM14-3, ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?BGM380,BGM381,BGM382,BGM383, ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?BGM384,BGM385,BGM386,BGM387, ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
....+....|....+|...2....+....3|...+....4....+....5....+....6....+....7.|
===== ? ? ? ? ? ? ? ?BGM388,BGM389,BGM38A,BGM38B, ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?BGM38C,BGM38D,BGM38E,BGM38F
===== ? ? ? ? ?SYSRES SYSVOL=VM50-1, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? X
===== ? ? ? ? ? ? ? ?SYSRES=6A1, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? X
===== ? ? ? ? ? ? ? ?SYSTYPE=3350, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? X
===== ? ? ? ? ? ? ? ?SYSNUC=(530,19), ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?SYSWRM=(551,2,VM50-1), ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?SYSERR=(549,2,VM50-1), ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
===== ? ? ? ? ? ? ? ?SYSCKP=(553,2,VM50-1)
===== ? ? ? ? ?SYSMON AUTO=YES,USERID=MAINT
===== ? ? ? ? ?SYSJRL
The command CP Q 380-38F returns (see below), and thus, the drive VOLSERS are correct, but doing a CP Q DASD doesn't show them being attached to the system.
CP Q 380-38F
DASD 380 BGM380?
DASD 380 BGM381?
DASD 380 BGM382?
DASD 380 BGM383?
DASD 380 BGM384?
DASD 380 BGM385?
DASD 380 BGM386
DASD 380 BGM387?
DASD 380 BGM388
.??
.
.
DASD 380 BGM38F
I checked the TEXT file, and the date and time are correct.? I even edited DMKSYS TEXT and saw BGM380 - BGM38F in the text thus verifying the lines aren't comments.
One diagnostic step I am considering is moving the BGM380-BGM38F from the end to, say, before the KIKS0 volume.? It might help figure out the issue, especially if KIKS0 doesn't attach to the system.
I appreciate any help you can provide to me.
Thank you.
On Thu, May 16, 2024 at 4:17?PM Bertram Moshier via <herc370390vm= [email protected]> wrote: 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 add to the Hercules configuration file three drives, but Hercules won't accept them with shadow files.
- I can get VM to see the drives, but I can't get them attached to the system via DMKSYS.
I suspect these issues may be related, as one progresses from one to three, but I can't see the relationship (and none may exist).? The details are:
Issue One:
I can't get dasdinit to put a VOLSER on the drive.? I'm creating the drive (file) using the command dasdinit -a vm380-0.cckd 3380 BGM380
The output is:
HHC02499I Hercules utility dasdinit - DASD image file creation program - version 4.7.0.11119-SDL-gf7d2360a
HHC01414I (C) Copyright 1999-2024 by Roger Bowler, Jan Jaeger, and others
HHC01417I ** The SDL 4.x Hyperion version of Hercules **
HHC01415I Build date: Mar ?9 2024 at 20:27:46
HHC00467W Maximum cylinders supported is 65536
HHC00007I Previous message from function 'create_ckd' at dasdutil.c(1813)
HHC00462I 0:0000 CKD file vm380-0.cckd: creating 3380 volume BGM380: 886 cyls, 15 trks/cyl, 47616 bytes/track
HHC00460I 0:0000 CKD file vm380-0.cckd: 886 cylinders successfully written
HHC02423I DASD operation completed
I run the command "dasdls vm380-0.cckd" I get:
HHC02499I Hercules utility dasdls - List DASD image file contents - version 4.7.0.11119-SDL-gf7d2360a
HHC01414I (C) Copyright 1999-2024 by Roger Bowler, Jan Jaeger, and others
HHC01417I ** The SDL 4.x Hyperion version of Hercules **
HHC01415I Build date: Mar ?9 2024 at 20:27:46
HHC00403I 0:0000 CKD file vm380-0.cckd: opened r/o
HHC00414I 0:0000 CKD file vm380-0.cckd: model 3380-A cyls 886 heads 15 tracks 13290 trklen 47616
HHC02471E Format 4 DSCB record not found
HHC00007I Previous message from function 'do_ls_cif' at dasdls.c(699)
Issue Two:
In the configuration file, I'm using the entry:
0380 ? ?3380 ? ?disks/vm380-0.cckd ro sf=disks/shadows/vm380-0.shadow
Hercule fails to use the drive, giving the message:
HHC00469E 0:0380 CKD file disks/vm380-0.cckd: shadow files not supported for CKD dasd
HHC00007I Previous message from function 'ckd_dasd_init_handler' at ckddasd.c(474)
HHC01463E 0:0380 device initialization failed
When I remove the: ro sf=disks/shadows/vm380-0.shadow
I get:
HHC00414I 0:0380 CKD file disks/vm380-0.cckd: model 3380-A cyls 886 heads 15 tracks 13290 trklen 47616
Issue Three:
In VM on Maint, I'm seeing:
cp q 380
DASD 380 BGM380
cp attach 380 system BGM380
DASD 380 ATTACH TO SYSTEM BGM380
This is all good and well to this point.? I added DMKSYS the VOLSERS:? BGM380, BGM381, and BGM382 by adding them to DMKSYS (well, I thought):
SYSUSR VM50-5,VM50-6,VM50-7,VM50-8,VM50U0,VM50U1,GCCBRX, ? ? ?X
? ? ? ? ? ? ?KICKS0,VSAMIN, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?X
? ? ? ? ? ? ?VM14-0,VM14-1,VM14-2,VM14-3 ? ? ? ? ? ? ? ? ? ? ? ? ? ? X
? ? ? ? ? ? ?BGM380,BGM381,BGM382
I did a nucleus build, cp shutdown, and replied 6A1 in the Hercules console.
The problem is the drives 380-382 don't show as being attached to the system or owned by the system.? I'm seeing:
cp q 380-382
DASD 380 BGM380
DASD 381 BGM381
DASD 382 BGM382
while VM14-0 through VM14-3 are system drives.
DASD 6D0 CP SYSTEM VM14-0 ? 001
DASD 6D1 CP SYSTEM VM14-1 ? 001
DASD 6D2 CP SYSTEM VM14-2 ? 001
DASD 6D3 CP SYSTEM VM14-3 ? 001
Thank you so very much,
Bertram Moshier
WB8ERT
|
Re: SYSIPL macro in DMKSYS
On Fri, May 17, 2024 at 04:26 PM, Bertram Moshier wrote:
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 documentation on this macro?? I should remember, but don't, where the MACLIB is for the DMKSYS macros.
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, Rene FERLAND, Montreal
|
Re: I forgot the VOLSER of drives (3380) I created
Olaf 'Rhialto' Seibert wrote: [...] 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 too (.ckd given with a compression option)
probably.
If the user prefers other extensions they are on their own
(alternative: also complain but a bit less loudly). Hmmm... Not a half bad idea. Let me think on it for a while. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
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 documentation on this macro?? I should remember, but don't, where the MACLIB is for the DMKSYS macros.
Thank you in advance for your help,
Bertram Moshier
|
Ren¨¦ Ferland