Thank you Martin for that clear explanation!
Peter
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Martin Taylor
via groups.io
Sent: Saturday, January 16, 2021 11:07 AM
To: [email protected]
Subject: Re: [h390-vm] add new dasd to vm/370 sixpack
Hello,
I have had the same issue when adding DASD to a VM370 system at the 1.3 level.
Prior to this a simple create of the DASD and adding it to the machine config file
with a suitable device address (that matches the DASD type) was all that was
required. I had added new DASD to a 1.2 system many time with no issue. A
VARY all devices in AUTOLOG1 brought the DASD online. However moving my
system to 1.3 caused all the DASD I had added to become inaccessible with
message DMKLNK108E NOT LINKED NOT MOUNTED being issued when logging
on to an affected user.
The cause of the above problem is that in VM/370 1.3 a fix is implemented that
meant that the SYSUSR parameter, in DMKSYS, had to be used to have the new
DASD accessible. This means that a CP regen is required. As with the 1.2 system
once the new DASD is online it can be used to allocate mini disks space (just do
not use the first cylinder), or any other use.
Below is an explanation of what that fix was and it¡¯s implications.
¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª Start of insert¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª
¡ª¡ª¡ª¡ª¡ª¡ª-
I traced the cause of the DMKLNK108E message down to an flag setting in the
RBLOK field RDEVFLAG. When set to RDEVMOUT its considered not to be
ATTACHED/MOUNTED hence the message.
Further digging showed that adding my DASD to the SYSUSR macro and
regenning CP allowed my userid to logon correctly.
Given the above I did some more searching and found fixes that dealt with these
fields/values. This revealed fix HRC039DK which is not on the 1.2 VM/370 system
but is on the 1.3. This fix is attempted to add clarity and consistency to device
status as explained in HRC039DK MEMO.
So I would say its a pretty safe bet that the behaviour I had seen is not so must
of a bug but a correction to wooly handling of device status in the past. It does
mean that when using VM/370 beta 1.3 the use of the SYSUSR parameter in
DMKSYS is mandated, which I think is the purpose of HRC039DK. Users of the 1.3
beta who just move their directory entries over, as has worked in the past, and
expect the system to run the same as previous versions.
¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ªend of insert ¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª
¡ª¡ª¡ª¡ª¡ª¡ª¡ª
Hope this is of use, at least it documents this behaviour for those moving to 1.3
and above from 1.2 systems.
Regards,
Martin.
--
