|
Hello,
I created several?drives using the dasdinit command but forgot the VOLSER I set.? How do I look up the VOLSER using VM/CE?
Thank you.
|
On Fri, 26 Apr 2024 at 13:51, Bertram Moshier via <herc370390vm= [email protected]> wrote: Hello,
I created several?drives using the dasdinit command but forgot the VOLSER I set.? How do I look up the VOLSER using VM/CE?
If you VARY ON the drive at the CP level, and QUERY the address, it should show the VOLSER. You need to be using a userid like MAINT that has (IIRC) class B.
Or at the host (Hercules) level, you can just browse the CKD or CCKD file in the editor of your choice, search for the EBCDIC string "VOL1", and just after that you'll see the VOLSER.
Tony H.
|
Bertram Moshier wrote: I created several drives using the dasdinit command but forgot
the VOLSER I set. How do I look up the VOLSER using VM/CE? Using VM/CE? Probably some form of "query dasd" command I'm guessing. (I'm too lazy to look it up.) But with Hercules it's easy: just run 'dasdls' on the file: dasdls "..../foobar.cckd64" HHC02499I Hercules utility DASDLS - List DASD image file... HHC01414I (C) Copyright 1999-2024 by Roger Bowler, ... HHC01417I ** The SDL 4.x Hyperion version of Hercules ** HHC01415I Build date: Apr 16 2024 at 12:40:43 HHC00476I 0:0000 CCKD64 file '..../foobar.cckd64': opened r/o HHC00470I 0:0000 CCKD64 file '..../foobar.cckd64': model 3390-27 cyls 12250 heads 15 tracks 183750 trklen 56832 VOLSER: FOOBAR "..../foobar.cckd64" -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
Hello david/Fish,
Thank you so very much.
Bertram Moshier WB8ERT
Bertram Moshier wrote:
> I created several drives using the dasdinit command but forgot
> the VOLSER I set.? How do I look up the VOLSER using VM/CE?
Using VM/CE? Probably some form of "query dasd" command I'm guessing. (I'm too lazy to look it up.)
But with Hercules it's easy: just run 'dasdls' on the file:
? ?dasdls "..../foobar.cckd64"
? ?HHC02499I Hercules utility DASDLS - List DASD image file...
? ?HHC01414I (C) Copyright 1999-2024 by Roger Bowler, ...
? ?HHC01417I ** The SDL 4.x Hyperion version of Hercules **
? ?HHC01415I Build date: Apr 16 2024 at 12:40:43
? ?HHC00476I 0:0000 CCKD64 file '..../foobar.cckd64': opened r/o
? ?HHC00470I 0:0000 CCKD64 file '..../foobar.cckd64': model 3390-27
? ? ? ? ? ? ?cyls 12250 heads 15 tracks 183750 trklen 56832
? ?VOLSER:? FOOBAR? ? "..../foobar.cckd64"
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
Hello Fish (David),
I used the command:??
dasdls vm0380_BGM000.cckd
Hercules was not running.
Got as output:
04/29/2024 ?8:49:56.05 D:\Hercules\VM-CE\disks>dasdls vm0380_BGM000.cckd
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 vm0380_BGM000.cckd: opened r/o
HHC00414I 0:0000 CKD file vm0380_BGM000.cckd: model 3380-A cyls 885 heads 15 tracks 13275 trklen 47616
HHC02471E Format 4 DSCB record not found
HHC00007I Previous message from function 'do_ls_cif' at dasdls.c(699)
End of dasdls; rc=1
I guess I did something wrong.? When I do the command against a 3350 drive (e.g.?vm50-1.cckd) I get RC=0 and the VOLSER.
What did I do wrong?
Thank you for your help,
Bertram Moshier WB8ERT
On Fri, Apr 26, 2024 at 5:10?PM Fish Fish via <david.b.trout= [email protected]> wrote: Bertram Moshier wrote:
> I created several drives using the dasdinit command but forgot
> the VOLSER I set.? How do I look up the VOLSER using VM/CE?
Using VM/CE? Probably some form of "query dasd" command I'm guessing. (I'm too lazy to look it up.)
But with Hercules it's easy: just run 'dasdls' on the file:
? ?dasdls "..../foobar.cckd64"
? ?HHC02499I Hercules utility DASDLS - List DASD image file...
? ?HHC01414I (C) Copyright 1999-2024 by Roger Bowler, ...
? ?HHC01417I ** The SDL 4.x Hyperion version of Hercules **
? ?HHC01415I Build date: Apr 16 2024 at 12:40:43
? ?HHC00476I 0:0000 CCKD64 file '..../foobar.cckd64': opened r/o
? ?HHC00470I 0:0000 CCKD64 file '..../foobar.cckd64': model 3390-27
? ? ? ? ? ? ?cyls 12250 heads 15 tracks 183750 trklen 56832
? ?VOLSER:? FOOBAR? ? "..../foobar.cckd64"
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
Bertram Moshier I used the command: dasdls vm0380_BGM000.cckd
Hercules was not running.
Got as output:
[...] HHC02471E Format 4 DSCB record not found
I guess I did something wrong. When I do the command against
a 3350 drive (e.g. vm50-1.cckd) I get RC=0 and the VOLSER.
What did I do wrong? Nothing. What dasdls is saying is your particular dasd volume does not have a VOLSER. dasdls was designed to list a volume's VTOC (list all of a volume's datasets), the description of which is contained in a Format 4 DSCB record. The address of the VTOC (Format 4 DSCB record) is held in a field in the VOL1 record, which your volume obviously does not have. Hence the HHC02471E error. Your particular dasd was obviously initialized using the '-r' (raw) option of dasdinit(*), which creates a dasd image *without* a VOL1 record. It was probably initialized this way because VM does not use VTOCs. It uses a completely different technique for accessing files on its volumes, and thus does not need a VTOC, thereby eliminating its need for a VOL1 record too. So if you get the error you're getting ("HHC02471E Format 4 DSCB record not found"), that simply means your volume does not have a VOLSER. You did nothing wrong. -------- (*) -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
Hello,
Thank you for the explanation.
Maybe I need to ask a different question.
In VM, to bring a DASD online, I need its VOLSER.? (CP ATTACH CUU to SYSTEM VOLSER)? and to update DMKSYS.? How do I get the VOLSER onto the 3380 drives at the cuu of 380?
Basically, I'm trying to add a drive to the system for both experience and drive space for an account (userid).?
Thank you
On Mon, Apr 29, 2024 at 9:55?AM Fish Fish via <david.b.trout= [email protected]> wrote: Bertram Moshier
> I used the command:? ?dasdls vm0380_BGM000.cckd
> Hercules was not running.
>
> Got as output:
>
[...]
> HHC02471E Format 4 DSCB record not found
>
> I guess I did something wrong.? When I do the command against
> a 3350 drive (e.g. vm50-1.cckd) I get RC=0 and the VOLSER.
>
> What did I do wrong?
Nothing.
What dasdls is saying is your particular dasd volume does not have a VOLSER.
dasdls was designed to list a volume's VTOC (list all of a volume's datasets), the description of which is contained in a Format 4 DSCB record. The address of the VTOC (Format 4 DSCB record) is held in a field in the VOL1 record, which your volume obviously does not have. Hence the HHC02471E error.
Your particular dasd was obviously initialized using the '-r' (raw) option of dasdinit(*), which creates a dasd image *without* a VOL1 record. It was probably initialized this way because VM does not use VTOCs. It uses a completely different technique for accessing files on its volumes, and thus does not need a VTOC, thereby eliminating its need for a VOL1 record too.
So if you get the error you're getting ("HHC02471E Format 4 DSCB record not found"), that simply means your volume does not have a VOLSER.
You did nothing wrong.
--------
(*)
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
If it doesnt?have a VOLSER, just delete the file and use dasdinit to create a new file with a VOLSER.
Joe
On Mon, Apr 29, 2024 at 11:24?AM Bertram Moshier via <herc370390vm= [email protected]> wrote: Hello,
Thank you for the explanation.
Maybe I need to ask a different question.
In VM, to bring a DASD online, I need its VOLSER.? (CP ATTACH CUU to SYSTEM VOLSER)? and to update DMKSYS.? How do I get the VOLSER onto the 3380 drives at the cuu of 380?
Basically, I'm trying to add a drive to the system for both experience and drive space for an account (userid).?
Thank you
On Mon, Apr 29, 2024 at 9:55?AM Fish Fish via <david.b.trout= [email protected]> wrote: Bertram Moshier
> I used the command:? ?dasdls vm0380_BGM000.cckd
> Hercules was not running.
>
> Got as output:
>
[...]
> HHC02471E Format 4 DSCB record not found
>
> I guess I did something wrong.? When I do the command against
> a 3350 drive (e.g. vm50-1.cckd) I get RC=0 and the VOLSER.
>
> What did I do wrong?
Nothing.
What dasdls is saying is your particular dasd volume does not have a VOLSER.
dasdls was designed to list a volume's VTOC (list all of a volume's datasets), the description of which is contained in a Format 4 DSCB record. The address of the VTOC (Format 4 DSCB record) is held in a field in the VOL1 record, which your volume obviously does not have. Hence the HHC02471E error.
Your particular dasd was obviously initialized using the '-r' (raw) option of dasdinit(*), which creates a dasd image *without* a VOL1 record. It was probably initialized this way because VM does not use VTOCs. It uses a completely different technique for accessing files on its volumes, and thus does not need a VTOC, thereby eliminating its need for a VOL1 record too.
So if you get the error you're getting ("HHC02471E Format 4 DSCB record not found"), that simply means your volume does not have a VOLSER.
You did nothing wrong.
--------
(*)
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
Is there a method to format a drive by attaching it to say maint and running a standalone format or CP format?? I tried CMS format but it failed.
In a real world situation it would be similar to a new drive from IBM. Wouldn't the Systems Programmer need to format the drive?
Bert
If it doesnt?have a VOLSER, just delete the file and use dasdinit to create a new file with a VOLSER.
Joe
On Mon, Apr 29, 2024 at 11:24?AM Bertram Moshier via <herc370390vm= [email protected]> wrote: Hello,
Thank you for the explanation.
Maybe I need to ask a different question.
In VM, to bring a DASD online, I need its VOLSER.? (CP ATTACH CUU to SYSTEM VOLSER)? and to update DMKSYS.? How do I get the VOLSER onto the 3380 drives at the cuu of 380?
Basically, I'm trying to add a drive to the system for both experience and drive space for an account (userid).?
Thank you
On Mon, Apr 29, 2024 at 9:55?AM Fish Fish via <david.b.trout= [email protected]> wrote: Bertram Moshier
> I used the command:? ?dasdls vm0380_BGM000.cckd
> Hercules was not running.
>
> Got as output:
>
[...]
> HHC02471E Format 4 DSCB record not found
>
> I guess I did something wrong.? When I do the command against
> a 3350 drive (e.g. vm50-1.cckd) I get RC=0 and the VOLSER.
>
> What did I do wrong?
Nothing.
What dasdls is saying is your particular dasd volume does not have a VOLSER.
dasdls was designed to list a volume's VTOC (list all of a volume's datasets), the description of which is contained in a Format 4 DSCB record. The address of the VTOC (Format 4 DSCB record) is held in a field in the VOL1 record, which your volume obviously does not have. Hence the HHC02471E error.
Your particular dasd was obviously initialized using the '-r' (raw) option of dasdinit(*), which creates a dasd image *without* a VOL1 record. It was probably initialized this way because VM does not use VTOCs. It uses a completely different technique for accessing files on its volumes, and thus does not need a VTOC, thereby eliminating its need for a VOL1 record too.
So if you get the error you're getting ("HHC02471E Format 4 DSCB record not found"), that simply means your volume does not have a VOLSER.
You did nothing wrong.
--------
(*)
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
On Mon, Apr 29, 2024 at 09:34 AM, Bertram Moshier wrote:
Is there a method to format a drive by attaching it to say maint and running a standalone format or CP format?
Yes indeed, first IPL VM/370 CE, then in the Hercules console: attach 380 3380 vm0380_BGM000.cckd /vary online 380 then logon to MAINT and attach the disk to MAINT Ready; T=0.01/0.01 12:17:20 attach 380 to maint as 380 You should get the message DASD 380 ATTACHED TO MAINT. Then follow these steps: Ready; T=0.01/0.01 12:17:27 cp spool punch * Ready; T=0.01/0.01 12:17:42 punch ipl fmt s ( noh PUN FILE xxxx? TO ?MAINT ? ?COPY 01 NOHOLD Ready; T=0.01/0.01 12:17:50 order rdr xxxx Ready; T=0.01/0.01 12:17:50 ipl 00c VM/370 FORMAT/ALLOCATE PROGRAM RELEASE 6 ENTER FORMAT OR ALLOCATE: format FORMAT FUNCTION SELECTED ENTER DEVICE ADDRESS (CUU): 380 ENTER DEVICE TYPE: 3380 ENTER START CYLINDER (XXX OR XXXX) OR "LABEL": 000 ENTER END CYLINDER (XXX OR XXXX): 884 ENTER DEVICE LABEL: bgm000? ?(or what ever you want as a VOLSER)? FORMAT STARTED FORMAT DONE 000 NO. PAGE RECORDS WITH READ-CHECK ERRORS ENTER FORMAT OR ALLOCATE: #CP IPL CMS VM Community Edition V1 R1.2 Y (19E) R/O U (19D) R/O B (5E5) R/O Ready; T=0.01/0.01 12:19:39 det 380 DASD 380 DETACHED Ready; T=0.01/0.01 12:19:44 logoff After that, the disk will be CP formatted, and dasdls should show a similar output to that of vm50-1.cckd. Cheers, Rene FERLAND, Montreal
|
Dont you use IBCDASDI for that?
For instance for a 3350 -
On the PC running hercules:
dasdinit -a file.3350 3350 111111
Where 111111 is the volser (or whatever you want to call it)
Then attach the disk to hercules, mount it and run IBCDASDI in VM to format it.
Look here around page 190 or so ...?
Joe
On Mon, Apr 29, 2024 at 11:34?AM Bertram Moshier via <herc370390vm= [email protected]> wrote: Is there a method to format a drive by attaching it to say maint and running a standalone format or CP format?? I tried CMS format but it failed.
In a real world situation it would be similar to a new drive from IBM. Wouldn't the Systems Programmer need to format the drive?
Bert
If it doesnt?have a VOLSER, just delete the file and use dasdinit to create a new file with a VOLSER.
Joe
On Mon, Apr 29, 2024 at 11:24?AM Bertram Moshier via <herc370390vm= [email protected]> wrote: Hello,
Thank you for the explanation.
Maybe I need to ask a different question.
In VM, to bring a DASD online, I need its VOLSER.? (CP ATTACH CUU to SYSTEM VOLSER)? and to update DMKSYS.? How do I get the VOLSER onto the 3380 drives at the cuu of 380?
Basically, I'm trying to add a drive to the system for both experience and drive space for an account (userid).?
Thank you
On Mon, Apr 29, 2024 at 9:55?AM Fish Fish via <david.b.trout= [email protected]> wrote: Bertram Moshier
> I used the command:? ?dasdls vm0380_BGM000.cckd
> Hercules was not running.
>
> Got as output:
>
[...]
> HHC02471E Format 4 DSCB record not found
>
> I guess I did something wrong.? When I do the command against
> a 3350 drive (e.g. vm50-1.cckd) I get RC=0 and the VOLSER.
>
> What did I do wrong?
Nothing.
What dasdls is saying is your particular dasd volume does not have a VOLSER.
dasdls was designed to list a volume's VTOC (list all of a volume's datasets), the description of which is contained in a Format 4 DSCB record. The address of the VTOC (Format 4 DSCB record) is held in a field in the VOL1 record, which your volume obviously does not have. Hence the HHC02471E error.
Your particular dasd was obviously initialized using the '-r' (raw) option of dasdinit(*), which creates a dasd image *without* a VOL1 record. It was probably initialized this way because VM does not use VTOCs. It uses a completely different technique for accessing files on its volumes, and thus does not need a VTOC, thereby eliminating its need for a VOL1 record too.
So if you get the error you're getting ("HHC02471E Format 4 DSCB record not found"), that simply means your volume does not have a VOLSER.
You did nothing wrong.
--------
(*)
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
Fish, Whilst VM doesn't use the VTOC it does create one to prevent MVS trampling over VM disks so it's very happy to use a volume created with DASDINIT providing you add a label Dave G4UGM?
Bertram Moshier
> I used the command:? ?dasdls vm0380_BGM000.cckd
> Hercules was not running.
>
> Got as output:
>
[...]
> HHC02471E Format 4 DSCB record not found
>
> I guess I did something wrong.? When I do the command against
> a 3350 drive (e.g. vm50-1.cckd) I get RC=0 and the VOLSER.
>
> What did I do wrong?
Nothing.
What dasdls is saying is your particular dasd volume does not have a VOLSER.
dasdls was designed to list a volume's VTOC (list all of a volume's datasets), the description of which is contained in a Format 4 DSCB record. The address of the VTOC (Format 4 DSCB record) is held in a field in the VOL1 record, which your volume obviously does not have. Hence the HHC02471E error.
Your particular dasd was obviously initialized using the '-r' (raw) option of dasdinit(*), which creates a dasd image *without* a VOL1 record. It was probably initialized this way because VM does not use VTOCs. It uses a completely different technique for accessing files on its volumes, and thus does not need a VTOC, thereby eliminating its need for a VOL1 record too.
So if you get the error you're getting ("HHC02471E Format 4 DSCB record not found"), that simply means your volume does not have a VOLSER.
You did nothing wrong.
--------
(*)
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
Dave Wade wrote: Fish,
Whilst VM doesn't use the VTOC it does create one to prevent
MVS trampling over VM disks so it's very happy to use a volume
created with DASDINIT providing you add a label. I suspected as much but wasn't sure so I thought I'd stick with what I could remember. :) But regardless of whether the dasd image was created with or without a VOLSER, it still needs to be formatted by VM before it can be used, yes? And formatting it in VM will always assign a VOLSER as Ren¨¦ Ferland has shown, which can be different, if desired, from the one assigned to it by dasdinit. Buy my original answer still stands: you can use dasdls to quickly and easily determine a volume's VOLSER. If it doesn't have a VOL1 (and thus no VOLSER), you'll get a "HHC02471E Format 4 DSCB record not found". Otherwise if it does have a VOL1 record, dasdls will report the volume's VOLSER. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
Hello,
I've been reading?the Hercules version 4 manual pages, but I'm still having issues.? In the configuration file, I have the line:??0380 ? ?3380 ? ?disks/vm0380_BGM000.cckd to? ?I used to have a shadow file, but can't figure out how to create it.? I got errors when I had the sf parameter (forget it).? Removing the sf stopped the Hercule messages, but the drive?is read/only and the documentation doesn't talk about a :"rw" option.
Two things:
1) Please catch a fish for me (I mean, help me add 3350 and 3380 drives).
2) Help me learn how to find and understand information?in the manual.
Honestly, I've never had this much trouble understanding a piece of software. It is me, not the product, and that is why I'm asking for help learning Hercules.
Thank you.
On Mon, Apr 29, 2024 at 9:55?AM Fish Fish via <david.b.trout= [email protected]> wrote: Bertram Moshier
> I used the command:? ?dasdls vm0380_BGM000.cckd
> Hercules was not running.
>
> Got as output:
>
[...]
> HHC02471E Format 4 DSCB record not found
>
> I guess I did something wrong.? When I do the command against
> a 3350 drive (e.g. vm50-1.cckd) I get RC=0 and the VOLSER.
>
> What did I do wrong?
Nothing.
What dasdls is saying is your particular dasd volume does not have a VOLSER.
dasdls was designed to list a volume's VTOC (list all of a volume's datasets), the description of which is contained in a Format 4 DSCB record. The address of the VTOC (Format 4 DSCB record) is held in a field in the VOL1 record, which your volume obviously does not have. Hence the HHC02471E error.
Your particular dasd was obviously initialized using the '-r' (raw) option of dasdinit(*), which creates a dasd image *without* a VOL1 record. It was probably initialized this way because VM does not use VTOCs. It uses a completely different technique for accessing files on its volumes, and thus does not need a VTOC, thereby eliminating its need for a VOL1 record too.
So if you get the error you're getting ("HHC02471E Format 4 DSCB record not found"), that simply means your volume does not have a VOLSER.
You did nothing wrong.
--------
(*)
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
|
But regardless of whether the dasd image was created with or without a VOLSER, it still needs to be formatted by VM before it can be used, yes?
No, it's fine as it is. If you are using it for MINIDISKS these are formatted by the user. If using it for other purposes you may need to format those areas but you don't need to touch the label.
And formatting it in VM will always assign a VOLSER as Ren¨¦ Ferland has shown, which can be different, if desired, from the one assigned to it by dasdinit.
No, if you use the standalone format allocate program you don't need to change the label. So if you are adding a spool area to an existing volume you would format the spool area.
Buy my original answer still stands: you can use dasdls to quickly and easily determine a volume's VOLSER. If it doesn't have a VOL1 (and thus no VOLSER), you'll get a "HHC02471E Format 4 DSCB record not found". Otherwise if it does have a VOL1 record, dasdls will report the volume's VOLSER.
Yes this is the simplest way to check.
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
Dave G4UGM?
|
On Mon, Apr 29, 2024 at 02:32 PM, Fish Fish wrote:
If it doesn't have a VOL1 (and thus no VOLSER), you'll get a "HHC02471E Format 4 DSCB record not found". Otherwise if it does have a VOL1 record, dasdls will report the volume's VOLSER.
If it doesn't have a VOL1 (dasdinit with -r option), you'll get "HHC02471E VOL1 record not found", if it does have a VOL1 but no VTOC (dasdinit without -r), dasdls will report "HHC02471E Format 4 DSCB record not found". As far as I know, dasdls will display the VOLSER only if the disk has a VTOC, either after being OS-formatted, CP-formatted, or created with dasdload. I assume that's because then the VOL1 record is "complete", containing both the VOLSER and the address of an existing (possibly empty) VTOC. Cheers, Rene FERLAND, Montreal
|
Ren¨¦ Ferland wrote: [...] If it doesn't have a VOL1 (dasdinit with -r option), you'll
get "HHC02471E VOL1 record not found", if it does have a VOL1
but no VTOC (dasdinit without -r), dasdls will report
"HHC02471E Format 4 DSCB record not found". (Oops!) You are of course correct. I stand corrected. As far as I know, dasdls will display the VOLSER only if
the disk has a VTOC, either after being OS-formatted,
CP-formatted, or created with dasdload. Hmmm... You appear to be correct yet again. (Damn! I'm losing my touch! <grumble>) I assume that's because then the VOL1 record is "complete",
containing both the VOLSER and the address of an existing
(possibly empty) VTOC. I guess so. So... I guess maybe dasdinit should be changed to also create an "empty VTOC" too? (i.e. a valid Format 4 record indicating zero VTOC entries?) So... If someone can provide a hex dump of one, I'll be glad to try and update dasdinit to always create one so that dasdls always displays the VOLSER when -r is not used. OR... Even better, maybe we simply need a new very simple utility (possibly called dasdvol1?) that ONLY reports a dasd's VOL1 record fields and nothing else? You know, I hadn't thought of this before (like I said, I'm losing my touch), but if the file is a compressed CKD dasd, you can use cckddiag to easily display the VOL1 record (which of course contains the VOLSER): cckddiag64 -x -a 0 0 Q:/CCKD64/3390-9.cckd64 HHC02499I Hercules utility CCKDDIAG64 - CCKD64/CFBA64 diagnostic program - version 4.8.0.11130-SDL-DEV-ga291e7e9 HHC01414I (C) Copyright 1999-2024 by Roger Bowler, Jan Jaeger, and others HHC01417I ** The SDL 4.x Hyperion version of Hercules ** HHC01415I Build date: Apr 16 2024 at 12:40:43 [...] HHC02606I Track 0 rec[03/3] kl[4]: +0000 E5D6D3F1 VOL1 HHC02606I Track 0 rec[03/3] dl[80]: +0000 E5D6D3F1 C1C2C3F1 F2F3C000 00000101 VOL1ABC123{..... +0010 40404040 40404040 40404040 40404040 +0020 40404040 405C5C40 C8C5D9C3 E4D3C5E2 ** HERCULES +0030 405C5C40 40404040 40404040 40404040 ** +0040 40404040 40404040 40404040 40404040 HHC02601I End of track But cckddiag only works for CCKD/CCKD64 files of course, not plain CKD files, so maybe having a new 'dasdvol1' utility might be best? Thanks for keeping me on my toes, Ren¨¦. :) -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
Fish,
I wouldn't change a thing or create any new utility for this.? The proper procedure when bringing a new DASD volume online to VM is to format it with the Format/Allocate program.? This puts the proper initialization records in place on the volume for that system.? Just a few posts ago it was shown how to do this.
And for OS volumes, they should be initialized with IBCDASDI for really old systems, or for MVS 3.8 and later, initialized with IEHDASDR or ICKDSF depending on exactly what OS version you are using.
Regards,
Bob
|
Reading this I just feel out of the game. I was the one who asked
for some help just because I was dumb enough to not start a 3278
emulation to act as the VM console, and very kind people explained
to me that the error messages I was showing just said that to
people that were able to read them...
Formerly, I was the head of the applications development team in
a French research lab (now you have some explanations about my
poor English). This may explain (if not excuse for many people)
that I'm not that familiar with the VM system internals. I daily
struggle trying to have a VM-CE or a VM-ESA just operating and I
use your discussions (you ?systems? guys?) to try to discover how
to have a working DIRMAINT under VM-ESA or just how to add a
physical disk to a VM-CE machine in order to re-implant the
backups I made years ago of my own userid under a real VM-ESA
operating on a real 3090.
Please understand that a lot of people are missing VM and that
these people are not necessarily ?system? ones. There are plenty
of ?G class? users that are trying to get back such a friendly
environment (and who nerver heard about Format/Allocate). They are
all able to read Melinda's paper and the IBM documentation or red
books (they heard about) but they are also able to ask silly
questions making them look like dumb people. Please don't push
them out of your discussions they will improve (I hope I do so
keeping a track of all you say for future reference for when I
will find not like your pair but like somebody you may not
consider as plain sh*t : providing them references or advices may
help them improve drastically)
Be sure I'll not bother you in any way but I will still listen to
all what you, knowledgeable people are saying? about things I'm
still not able to fully understand? but believe that I really try
to cope with.
Sincerely
Jean-Pierre ?
toggle quoted message
Show quoted text
Le 01/05/2024 ¨¤ 14:07, Bob Polmanter a ¨¦crit?:
Fish,
I wouldn't change a thing or create any new utility for this.? The
proper procedure when bringing a new DASD volume online to VM is
to format it with the Format/Allocate program.? This puts the
proper initialization records in place on the volume for that
system.? Just a few posts ago it was shown how to do this.
And for OS volumes, they should be initialized with IBCDASDI for
really old systems, or for MVS 3.8 and later, initialized with
IEHDASDR or ICKDSF depending on exactly what OS version you are
using.
Regards,
Bob
--
J¦Ðr
|
On Tue, Apr 30, 2024 at 11:52 AM, Fish Fish wrote:
I guess maybe dasdinit should be changed to also create an "empty VTOC" too?
(i.e. a valid Format 4 record indicating zero VTOC entries?)
Can dasdls be changed to print the volser if there is a VOL1 record, but no DSCB 4? I don't understand why the lack of a DSCB 4 would prevent detection of the VOLSER?
|
Ren¨¦ Ferland
Jean-Pierre Cabani¨¦