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
|
