开云体育

Minidisk allocation planning

Michael Grom All Messages By This Member #4087 Dear Group, is there a way to figure out if there is place for? a (new) minidisk allocation on a volume?? kind regards Michael
Dave Wade All Messages By This Member #4088 开云体育 Michael, Try “DISKMAP”. Its on MAINT’s B disk but there is a help file. I would say though if you want more minidisks add a pack for yourself. Makes upgrades simpler. Dave ? ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of Michael Grom Sent: 14 March 2022 09:14 To: [email protected] Subject: [h390-vm] Minidisk allocation planning ? Dear Group, is there a way to figure out if there is place for? a (new) minidisk allocation on a volume?? kind regards Michael
Michael Grom All Messages By This Member #4089 Hi Dave, thanks for the pointer. Using a dedicated new pack is definitely a good point here, not meddling with the distribution packs.? kind regards Michael
Bob Bolch All Messages By This Member #4090 VMCE supplies two preconfigured empty disk packs, labelled VM50U0 and VM50U1 that are to be used only for information put there by the end user. If you use those disk packs for installation specific minidisks, then when a new VM370CE release comes out, you can copy the user volumes to the new system release, and just add the new directory entries. Bob toggle quoted message Show quoted text On Mon, Mar 14, 2022 at 6:21 AM Michael Grom <macbaer@...> wrote: Hi Dave, thanks for the pointer. Using a dedicated new pack is definitely a good point here, not meddling with the distribution packs.? kind regards Michael
Michael Grom All Messages By This Member #4091 Thanks Bob, I will probably do so - especially because I ran into another trouble: ? DMKLNK117E USERID VSAMIO NOT LINKED; VOLID 191 CONFLICT what happened?? created disk image using dasdinit of type 3350 with label VSAMIO and attached it @ cuu = 06D5 in the config file created user vsamio in the directory with minidisk 191 for vol VSAMIO added attach 6d5 to system as VSAMIO in the profile exec of autolog1 ?kind regards Michael
Bob Bolch All Messages By This Member #4094 Hi Michael, I could better understand?what you are doing if you tell me what commands you issued, what the responses are, and what the error messages say.? I do know that 6D5 is defined to the system as a 2314 disk, not a 3350 in the DMKRIO? ASSEMBLE file. I suggest you try again using VM50U0 to define your new minidisk. /Bob? toggle quoted message Show quoted text On Mon, Mar 14, 2022 at 10:54 AM Michael Grom <macbaer@...> wrote: Thanks Bob, I will probably do so - especially because I ran into another trouble: ? DMKLNK117E USERID VSAMIO NOT LINKED; VOLID 191 CONFLICT what happened?? created disk image using dasdinit of type 3350 with label VSAMIO and attached it @ cuu = 06D5 in the config file created user vsamio in the directory with minidisk 191 for vol VSAMIO added attach 6d5 to system as VSAMIO in the profile exec of autolog1 ?kind regards Michael
Michael Grom All Messages By This Member #4099 Hi Bob, yes, my wrong...guessing free device addresses in conjunction with dev types is a bad idea. I've checked dmkrio assemble on F (not dared to change it) and looked up a free address for a 3350 - now everything worked as supposed and I restored my vsamio vmarc to that disk. Work in progress! :-)? regards Michael

Previous Topic Next Topic