Re: dasd_configure in SLES 12 SP4
Thanks for the explanation, Mark. Easy enough for me to change the dasd_configure command in my scripts to chzdev so I will do that and not bother reporting that difference from SP3. The problem with by-path not working is a little more problematic, so I've opened a SUSE ticket for that. -Original Message- From: Linux on 390 Port On Behalf Of Mark Post Sent: Friday, May 31, 2019 10:42 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] dasd_configure in SLES 12 SP4 On 5/31/19 6:47 AM, Michael MacIsaac wrote: > Why? Doing so will break scripts we have ... Because they require maintenance, cause bug reports (such as Marcy's), etc., etc. They're not going away tomorrow, but please plan ahead. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
Mark, Thanks for a thorough reply. We have been warned :)) -Mike M On Fri, May 31, 2019 at 1:43 PM Mark Post wrote: > On 5/31/19 6:47 AM, Michael MacIsaac wrote: > > Why? Doing so will break scripts we have ... > > Because they require maintenance, cause bug reports (such as Marcy's), > etc., etc. They're not going away tomorrow, but please plan ahead. > > One of the complaints we hear is that "doing X on SLES for the mainframe > is different from how it's done on RHEL." Red Hat hears the same, in > reverse. SUSE and Red Hat both approached IBM to ask them to write and > maintain a replacement set of tools for these sorts of scripts. That > way, the tools to perform persistent and transient configuration will be > the same across distributions. I haven't looked, but I'm guessing Ubuntu > for the mainframe is using them as well. > > So, IBM came up the lszdev and chzdev utilities. To provide > compatibility, I modified the existing *_configure scripts to use them > instead of the previous logic. Moving forward, SUSE will be using the > lszdev and chzdev commands in our own tools where the *_configure > scripts have been used in the past. The linuxrc program to set up the > installation environment is already doing that. > > The wrapper scripts were written solely as a means of translating the > old semantics into the ones required by IBM's commands. The lszdev and > chzdev commands provide a lot more functionality than the old > *_configure scripts did. There will be no changes to the *_configure > scripts unless there's a bug, or for some reason IBM changes the > parameters their commands accept or require. > > If you set an environment variable of DEBUG to "yes", the *_configure > scripts will display the chzdev command that gets executed, as well as > actually executing it. Besides helping in debugging, this will allow > anyone wishing to get ahead of the curve to see exactly what command > needs to be executed to accomplish the same task as before. > > The old scripts will not be removed from the SLES12 product. At this > point, we're not sure if they will be removed from future service pack > levels of SLES15 or not. They almost certainly will not be part of the > follow-on version after SLES15. (After what happened between SLES12 and > SLES15, I'm not going to even try and outguess Product Management as to > what name that's going to be.) > > Finally, this is Open Source Software. If you decide you're simply not > going to move to the new commands from IBM, you're welcome to make and > keep copies of the *_configure scripts for your own use, for ever and ever. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- -Mike MacIsaac -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
On 5/31/19 6:47 AM, Michael MacIsaac wrote: > Why? Doing so will break scripts we have ... Because they require maintenance, cause bug reports (such as Marcy's), etc., etc. They're not going away tomorrow, but please plan ahead. One of the complaints we hear is that "doing X on SLES for the mainframe is different from how it's done on RHEL." Red Hat hears the same, in reverse. SUSE and Red Hat both approached IBM to ask them to write and maintain a replacement set of tools for these sorts of scripts. That way, the tools to perform persistent and transient configuration will be the same across distributions. I haven't looked, but I'm guessing Ubuntu for the mainframe is using them as well. So, IBM came up the lszdev and chzdev utilities. To provide compatibility, I modified the existing *_configure scripts to use them instead of the previous logic. Moving forward, SUSE will be using the lszdev and chzdev commands in our own tools where the *_configure scripts have been used in the past. The linuxrc program to set up the installation environment is already doing that. The wrapper scripts were written solely as a means of translating the old semantics into the ones required by IBM's commands. The lszdev and chzdev commands provide a lot more functionality than the old *_configure scripts did. There will be no changes to the *_configure scripts unless there's a bug, or for some reason IBM changes the parameters their commands accept or require. If you set an environment variable of DEBUG to "yes", the *_configure scripts will display the chzdev command that gets executed, as well as actually executing it. Besides helping in debugging, this will allow anyone wishing to get ahead of the curve to see exactly what command needs to be executed to accomplish the same task as before. The old scripts will not be removed from the SLES12 product. At this point, we're not sure if they will be removed from future service pack levels of SLES15 or not. They almost certainly will not be part of the follow-on version after SLES15. (After what happened between SLES12 and SLES15, I'm not going to even try and outguess Product Management as to what name that's going to be.) Finally, this is Open Source Software. If you decide you're simply not going to move to the new commands from IBM, you're welcome to make and keep copies of the *_configure scripts for your own use, for ever and ever. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
On Fri, May 31, 2019 at 12:48 PM Michael MacIsaac wrote: > Mark, > > > The wrappers will be removed at some point in the future. > Why? Doing so will break scripts we have ... > > Same here. I would urge SuSE to keep them. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
Mark, > The wrappers will be removed at some point in the future. Why? Doing so will break scripts we have ... -Mike On Thu, May 30, 2019 at 5:06 PM Mark Post wrote: > On 5/30/19 4:54 PM, Marcy Cortes wrote: > > Should I just be using that chzdev command now? > > Yes. Starting with SLES12 SP4, the following SUSE-provided scripts: > ctc_configure > dasd_configure > qeth_configure > zfcp_disk_configure > zfcp_host_configure > > are simply wrappers for the chzdev command. The wrappers will be removed > at some point in the future. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- -Mike MacIsaac -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
Thanks, Mark! One more if you don't mind myhost:~ # vgextend app /dev/disk/by-path/ccw-0.0.8002-part1 Device /dev/disk/by-path/ccw-0.0.8002-part1 excluded by a filter. myhost:~ # l /dev/disk/by-path/ccw-0.0.8002-part1 lrwxrwxrwx 1 root root 12 May 30 16:00 /dev/disk/by-path/ccw-0.0.8002-part1 -> ../../dasdk1 myhost:~ # vgextend app /dev/dasdk1 Volume group "app" successfully extended I can't use the names with virtual addresses anymore? Both SP3 and SP4 seem to have this line in /etc/lvm/lvm.conf filter = [ "r|/dev/.*/by-path/.*|", "r|/dev/.*/by-id/.*|", "r|/dev/fd.*|", "r|/dev/cdrom|", "a/.*/" ] So not sure what is up with that... -Original Message- From: Linux on 390 Port On Behalf Of Mark Post Sent: Thursday, May 30, 2019 2:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] dasd_configure in SLES 12 SP4 On 5/30/19 4:54 PM, Marcy Cortes wrote: > Should I just be using that chzdev command now? Yes. Starting with SLES12 SP4, the following SUSE-provided scripts: ctc_configure dasd_configure qeth_configure zfcp_disk_configure zfcp_host_configure are simply wrappers for the chzdev command. The wrappers will be removed at some point in the future. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
On 5/30/19 4:54 PM, Marcy Cortes wrote: > Should I just be using that chzdev command now? Yes. Starting with SLES12 SP4, the following SUSE-provided scripts: ctc_configure dasd_configure qeth_configure zfcp_disk_configure zfcp_host_configure are simply wrappers for the chzdev command. The wrappers will be removed at some point in the future. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
dasd_configure in SLES 12 SP4
So it seems to return an 8 now on SP4 , which messes up my scripting :( myhost:~ # export DEBUG=yes myhost:~ # dasd_configure 0.0.8002 1 0 All the parms passed were -- '0.0.8002' '1' '0' Found the end of parms indicator: -- chzdev -e dasd --no-root-update 0.0.8002 use_diag=0 ECKD DASD 0.0.8002 configured DASD 0.0.8002 is unformatted. myhost:~ # echo $? 8 Should I just be using that chzdev command now? Seems to do the same thing. I noticed also that /etc/udev/rules.d names are changed SP3 name: 51-dasd-0.0.8000.rules SP4 name: 41-dasd-eckd-0.0.8002.rules Doesn't seem to be a problem but just throwing that out there. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
