Re: Taking some time

[Cohen, Sam]

Good luck with your new life, Mark.  It's been great working with you.

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Mark Post
Sent: Wednesday, February 15, 2023 08:56
To: LINUX-390@VM.MARIST.EDU
Subject: Taking some time

All,

I'm retiring from SUSE. Today is my last day on the job. I intend to stay 
involved with Linux on the mainframe, including this mailing list, but I'm not 
sure just how involved. I'll know better after I've had some time to adjust to 
my new life.

When I left EDS in 2007, the environment at the company had become very toxic, 
with layoffs every quarter of good people with decades of experience. Joining 
Novell/SUSE at that time was the best possible thing that could have happened 
to me professionally. It's been very satisfying to contribute to the creation 
of SUSE's products. It has literally been a dream job for me.

I'm thankful to the many people that have helped me over the years.
Without them, I might never have been able to make working with mainframe Linux 
my career for 20+ years.


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
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=05%7C01%7CSam.Cohen%40LRS.COM%7C2882b4e764e34dc53c3a08db0f6d52a7%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C638120734464273904%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lDZEzMWorifjy9HojG6Egk8Fp8vmqhrL6UTq5PDTeb8%3D&reserved=0

--
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: IP change for a Linux guest

[Cohen, Sam]

Peter,

If you logon to the Linux guest via a 3270 display, you'll likely see a blank 
screen after logon (and password).  Press Enter and you'll see VM READ in the 
lower right corner of the display.  Press Enter again and you should see "Enter 
password" and RUNNING in the lower right corner of the screen.  Give it some 
time until it tires of waiting for a password and asks for a userid.  Enter a 
userid with sudo authority, or "root"; enter the password when prompted.  Once 
you're logged in, you should be able to issue an "ip" command (or an "ifconfig" 
or whatever command works for you to dynamically enter a new IP address.  
Remember to update your default gateway with a "route add" command.  You should 
then be able to ssh to the Linux guest.

When you are done with the console interface, be sure the lower right corner of 
the display does NOT display CP READ, then enter the command "logout".  Once 
you are prompted for a userid, enter the CP Break Key (key PA1 is the default), 
watch for CP READ in the lower right corner, then type "DISCONNECT" and press 
Enter.  Your physical console (the 3270 terminal) will then be disconnected 
from the virtual console, and you can go about your business.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Peter
Sent: Wednesday, June 29, 2022 20:16
To: LINUX-390@VM.MARIST.EDU
Subject: IP change for a Linux guest

Hello

When an existing redhat Linux guest on zVM requires a IP change. What are files 
that I need to change to reflect with new IP address?

For an existing Linux, how do I view it's console from a 3270 emulator ?
Cause as of due to the IP change the Linux guest is not connectable via SSH.

Could someone please guide me ?

Regards
Peter

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=05%7C01%7CSam.Cohen%40LRS.COM%7C46dc80e5daa44e41f34908da5a472e55%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C637921559055544780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Os1EcNQi9oHXu3dRCdfcmNoUZDtwOKAPsS%2BNUTw6Ri8%3D&reserved=0

--
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: Problem with SLES 15 SP3 Multipath

[Cohen, Sam]

Alan,

Have you looked at updating dracut.conf?  Per the man page for dracut:

  Adding Kernel Modules
   If you need a special kernel module in the initramfs, which is not
   automatically picked up by dracut, you have the use the --add-drivers
   option on the command line or the drivers variable in the
   /etc/dracut.conf or /etc/dracut.conf.d/myconf.conf configuration file
   (see dracut.conf(5)):

   # dracut --add-drivers mymod initramfs-with-mymod.img

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Levy, Alan
Sent: Tuesday, May 24, 2022 09:44
To: LINUX-390@VM.MARIST.EDU
Subject: Problem with SLES 15 SP3 Multipath

We cloned a SLES 15 SP3 server and defined SAN to it.

When we re-booted the server, we get "failed to mount /usr/xxx", which is the 
san device, and the server goes into emergency mode.

Based on some SUSE documentation and other recommendations, we ran the 
following commands afterwards to get the SAN working again:

multipath -T > /etc/multipath.conf
vi /etc/multipath.conf   # changed 
user_friendly_names to "yes"
rescan-scsi-bus.sh -a  # rescan scsi 
just in case
multipathd reconfigure # updates the 
bindings file after edit of /etc/multipath.conf
blkid  # 
get UUID of file systems
vi /etc/fstab# define 
file systems with UUID
dracut -f --add multipath
init 6

These commands allowed the system to boot successfully and we are able to see 
and use the san.

We then ran "zypper patch" to patch the system to the latest SP3 release which 
included a kernel update. When we rebooted the server again, the same problem 
occurred (failed to mount the san).  We then ran the "dracut -f --add 
multipath" command and rebooted which allowed the server to come up 
successfully.

Our question is - how do we make the dracut -f -add multipath command permanent 
such that subsequent kernel updates will include it?

We have a case opened with SUSE but they have not come up with any solutions.

Any suggestions from the linux community would be greatly appreciated.


Alan Levy
Z/VM & Linux Administrator
NYC Department of Information
Technology and Telecommunications
W: 718-403-8020

[cid:image001.png@01D86F6B.E8086E00]





This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments. Please notify the sender immediately by reply e-mail and delete 
the e-mail from your system.

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=05%7C01%7CSam.Cohen%40LRS.COM%7C7420593c8a00469200ef08da3da4eae9%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C637890075787056761%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Xcpo4Bx4%2BSntGWiZ5ZK442%2FsZuUICXbC6lqgSYP5TCo%3D&reserved=0

--
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: Suse failed boot after move to new DS8000

[Cohen, Sam]

Tony,

I hate to ask, but is this a  new DS8, or a "new" (as in new only to this 
customer) DS8?  I'm wondering if there is some maintenance required on z/VM 6.3 
for new messages that might come from the DS8.  The last RSU for z/VM 6.3 was 
1701 and the display shows them 2 years behind that.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Tony Thigpen
Sent: Friday, February 25, 2022 13:42
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse failed boot after move to new DS8000

Working system displays:

LOGON LNXADMIN
z/VM Version 6 Release 3.0, Service Level 1501 (64-bit), built on IBM 
Virtualization Technology There is no logmsg data
FILES: 0011 RDR,   NO PRT,   NO PUN
LOGON AT 15:39:03 EST FRIDAY 02/25/22
Command complete
Command complete
HCPCPL040E Device 0600 does not exist
z/VM V6.3.02015-08-17 18:51
LNXADMIN AT OSCARVIA RSCS 2022-02-25 15:39:04 EST  FRIDAY
DMSACP723I T (592) R/O
SWPSWA0012I DIAG swap disk defined at virtual address 0300 with SWPSWA0012I 
64988 4K pages of swap space.
SWPSWA0012I DIAG swap disk defined at virtual address 0301 with SWPSWA0012I 
129980 4K pages of swap space.
OSA 0370 ATTACHED TO LNXADMIN 0370
OSA 0371 ATTACHED TO LNXADMIN 0371
OSA 0372 ATTACHED TO LNXADMIN 0372
DO YOU WANT TO IPL LINUX FROM MINIDISK 100? Y/N y Booting default (grub2)
--- (followed by a grub menu)

Non-working system displays:
---
LOGON LNXADMIN
z/VM Version 6 Release 3.0, Service Level 1501 (64-bit), built on IBM 
Virtualization Technology There is no logmsg data
FILES: 0022 RDR, 0001 PRT,   NO PUN
LOGON AT 15:40:27 EST FRIDAY 02/25/22
Command complete
Command complete
HCPCPL040E Device 0600 does not exist
z/VM V6.3.02015-08-17 18:51
LNXADMIN AT OSCARVIA *2022-02-25 15:40:27 EST  FRIDAY
DMSACP723I T (592) R/O
SWPSWA0012I DIAG swap disk defined at virtual address 0300 with SWPSWA0012I 
64988 4K pages of swap space.
SWPSWA0012I DIAG swap disk defined at virtual address 0301 with SWPSWA0012I 
129980 4K pages of swap space.
HCPATR040E Device 0370 does not exist
HCPATR040E Device 0371 does not exist
HCPATR040E Device 0372 does not exist
DO YOU WANT TO IPL LINUX FROM MINIDISK 100? Y/N

--- (nothing else)

Tony Thigpen

Fred Bader wrote on 2/25/22 15:26:
>
>
>
> This maybe a dumb question, but is the volume VMFF85 online and 
> attached to the system?  If not, when LNXADMIN logs on, it should get 
> an error message that the volume is not available and therefore MDISK 
> 0100 won't exist and can't be IPLed.
>
> It would help if we could see the console messages produced when 
> LNXADMIN was logged on or XAUTOLOGed.  I see OPERATOR is defined as 
> SECUSER, so those messages should be on the OPERATOR's console as well.
>
> Regards, Fred
> __
> ___
>
> Fred Bader, IBM Z Washington Systems Center (WSC) - IBM Systems
> IBM Corp, 470 Springpark Pl, Suite 950/1000, Herndon, VA 20170-5253
> E-mail: fba...@us.ibm.com, Phone: 720-395-, Tieline: 676-
>
> IBM Z - "The cloud you want with the privacy and security you need"
>   
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.i
> bm.com%2Fsystems%2Fz%2F&data=04%7C01%7CSam.Cohen%40LRS.COM%7Cb60a8
> b49ac144d9ca03b08d9f89f791e%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0
> %7C637814186104539080%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ
> IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Pdy3XqF1NY
> HRU2%2FH33OXxtKQViIIZDQmMXZnA6YRlJ0%3D&reserved=0 - 
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.i
> bm.com%2Fz15&data=04%7C01%7CSam.Cohen%40LRS.COM%7Cb60a8b49ac144d9c
> a03b08d9f89f791e%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C63781418
> 6104539080%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
> iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BDFZUunfTpl3338i2b9
> imzW3SVZztoZLNtPZH5rE4Is%3D&reserved=0
>
>
>
>
>
> From: "Tony Thigpen" 
> To:   LINUX-390@VM.MARIST.EDU
> Date: 02/25/2022 03:14 PM
> Subject:  [EXTERNAL] Re: [PossibleSpam] Re: Suse failed boot after move
>  to new DS8000
> Sent by:  "Linux on 390 Port" 
>
>
>
> The profile is simply:
>
> USER LNXADMIN  1G 2G BDEG
>INCLUDE LNXPDFLT
>OPTION LNKNOPAS
>MDISK 0100 3390 1 10016 VMFF85 MR LNX4VM LNX4VM LNX4VM
>MDISK 0200 3390 1 10016 VMFF86 MR LNX4VM LNX4VM LNX4VM
>
> where the profile for lnxpdflt is:
> PROFILE LNXPDFLT
>
> ***COMMON LINUX DIRMPROFILE**
> COMMAND SET SECUSER OPERATOR
> COMMAND SET RUN ON
> COMMAND TERM HOLD OFF
> COMMAND TERM MORE 001 000
> COMMAND SCRE CPO WHI NON
> COMMAND SCRE STA GRE REV
> COMMAND COUPLE 0600 TO SYSTEM VSW1
> CPU 00 BASE
> DATEFORMAT ISODATE
> IPL CMS PARM FILEPOOL LINUX AUTOCR
> MACHINE ESA 8
> IUCV ALLOW
> OPT

Re: Suse failed boot after move to new DS8000

[Cohen, Sam]

Tony,

He is apparently running some startup script that has a "say 'Boot Linux?'" in 
it's PROFILE EXEC.  The question is: what does it do next?  Did he change 
device addresses, if he's booting from a DEVNO-defined virtual disk?  If he has 
install media, he can boot from that, then try to rescue the installation.  The 
steps involved there are a bit much for a forum, though.  I usually mount the 
errant disk on another system, chroot to that system, then investigate.  This 
isn't an exercise for novices.


Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Tony Thigpen
Sent: Friday, February 25, 2022 05:21
To: LINUX-390@VM.MARIST.EDU
Subject: Suse failed boot after move to new DS8000

I am helping a customer move his 6.3 system to a new DS8000. We moved all the 
dasd using DDR. After the copy, his LNXADMIN (SUSE) user will not boot.

He says he logs onto the guest and when it asked 'boot linux?', he replies 'Y' 
and nothing seems to happen.

I am not really familiar with zLinux. Is there anything that needs to be done 
special to make it moveable by DDR?

Tony Thigpen

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CSam.Cohen%40LRS.COM%7C9b325840b12f484b744c08d9f859910d%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C637813885846268627%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=HH7aAxxeg1kqniiDx0A6mQCbJzBtJgzN451Wy9D3xCc%3D&reserved=0

--
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: Today's funny....

[Cohen, Sam]

Jerry,

What do you mean..."just in case"?  Of course it will fail, just when you need 
it the most.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Edgington, Jerry
Sent: Tuesday, December 14, 2021 08:39
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Today's funny

Sorry, Jack, but I would have to disagree with you on this. It wouldn't "buy a 
car", it would be buy multiple cars, just in case the first one fails.  :)

Jerry Edgington

-Original Message-
From: Linux on 390 Port  On Behalf Of Jack Woehr
Sent: Tuesday, December 14, 2021 10:37 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Today's funny

This message was sent from an external source outside of Western & Southern's 
network. Do not click links or open attachments unless you recognize the sender 
and know the contents are safe.


On 12/14/21 7:14 AM, Dave Jones wrote:
> The Windows IT engineer says: "Hey guys, I have an idea, how about we 
> all get out of the car and get back in"

The Windows IT engineer says, "What you say we just buy a new car."

--
Jack Woehr   # Zen is a finger pointing at the moon.
IBM Champion 2021# Some want to see the moon.
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.softwoehr.com%2F&data=04%7C01%7CSam.Cohen%40LRS.COM%7C5c5b30e8ef4e49a7cb3008d9bf190e5b%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C637750936637067285%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=omLnB3lvBQuWzWYrhlmfAnwWzqnRDAyNUpSEEBak7kM%3D&reserved=0
 # Some want to discuss the finger.

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CSam.Cohen%40LRS.COM%7C5c5b30e8ef4e49a7cb3008d9bf190e5b%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C637750936637067285%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=h5QIRo3v5dnuITsulXGkm9iYZEfNco5FRMFDa7VixVY%3D&reserved=0

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CSam.Cohen%40LRS.COM%7C5c5b30e8ef4e49a7cb3008d9bf190e5b%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C637750936637067285%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=h5QIRo3v5dnuITsulXGkm9iYZEfNco5FRMFDa7VixVY%3D&reserved=0

--
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: Warning if upgrading SLES12 to SLES15 SP3

[Cohen, Sam]

Why not just change references from /dev/disk/by-uuid to /dev/disk/by-path, 
such as in /etc/fstab and /boot/zipl/config  ?  Wouldn't that be easier in the 
long run?

Thanks,

Sam

-Original Message-
From: Linux on 390 Port  On Behalf Of Aria Bamdad
Sent: Friday, October 8, 2021 12:09
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Warning if upgrading SLES12 to SLES15 SP3

Quoting Mark Post :

> On 10/8/21 2:10 PM, Alan Altmark wrote:
>> The UUID only needs to be unique within a virtual server.  I think 
>> the trick here is to use a cloning guest that links to the disk you 
>> want to clone so that the UUID is never duplicated within the owning 
>> guest.  The cloning guest will have two copies, but it will never use 
>> those disks itself.
>>
>> This avoids having to assign new UUIDs.
>
> Perhaps, but it's still a good idea to make each clone unique. If you 
> ever need to link to another guest's disks, then duplicate UUIDs are 
> going to cause problems. And really, adding:
>
> tune2fs -U $(uuidgen) /dev/dasd??
>
> to your cloning script is pretty straightforward.
>


I clone my disks using falashcopy so outside of linux.  This would mean that 
after flashcopy, I would need to mount the disks on a utility linux server and 
change the UUID of each disk using tune2fs.
That's fine and can be done.



> I would also recommend not using chzdev when cloning disks and 
> manipulating them. Instead, use chccwdev, which doesn't cause any udev 
> rules to be written to deleted. The chzdev and lszdev commands are 
> really nice commands, but they are also more capable, and hence 
> complex, than what is needed during cloning. Use chzdev/lszdev for "normal"
> system administration tasks where you actually want those udev rules 
> to be written/deleted.
>
>

Yes, that would likely avoid all of the problems.  However, in my case, I was 
in Yast and figured I will just activate a DASD using Yast menu.  SLES12 Yast 
would call chccwdev but later versions and SLES15 now call chzdev.  Had chzdev 
issued a message that the disk I am trying to activate has a UUID that 
conflicts with an existing disk that is currently activated, the entire problem 
would have been
avoided.  Instead it allows you to activate the disk.   To make
matters worse, while you are in Yast still, you no longer can deactivate the 
disk you just activated a second ago.  Why?  Because chzdev complains and yast 
will not continue.  If we had the same complaint during activation of the disk, 
problem would have been avoided.

Mark, your suggestion of using chccwdev is the right one.  We can use chccwdev 
to online the device, mount it, fix the uuid and unmount/offline the device.

Thanks,
Aria





> 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
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.
> marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CSam.Cohen
> %40LRS.COM%7Cc99ab9efc4f144d5ebaa08d98a8f568c%7C62af9ccc42164ae2a1d306
> 614c59c315%7C1%7C0%7C637693170518903788%7CUnknown%7CTWFpbGZsb3d8eyJWIj
> oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&am
> p;sdata=zc6faPNuqKiwmvWNxcGYwydyagoJWC4%2FXerg%2FEhP4FY%3D&reserve
> d=0

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CSam.Cohen%40LRS.COM%7Cc99ab9efc4f144d5ebaa08d98a8f568c%7C62af9ccc42164ae2a1d306614c59c315%7C1%7C0%7C637693170518903788%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=zc6faPNuqKiwmvWNxcGYwydyagoJWC4%2FXerg%2FEhP4FY%3D&reserved=0

--
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: cio_ignore

[Cohen, Sam]

If you're running under z/VM with a class G (or lower) user, why use cio_ignore 
at all?  Your hypervisor will only allow you to see what should be seen.  Even 
without z/VM, you can limit the devices visible to the LPAR via IOCDS 
statements.  I don't have cio_ignore on the startup of any of my RHEL guests 
(although I do use dasd.conf and zfcp.conf).

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Viktor 
Mihajlovski
Sent: Thursday, January 7, 2021 02:02
To: LINUX-390@VM.MARIST.EDU
Subject: Re: cio_ignore

On 1/7/21 4:41 AM, Bill Head wrote:
> On RHEL 8.2 I'm having a problem with cio_ignore.  I can remove devices from 
> the blacklist but when I reboot they are exluded again:
>
> cio_ignore -L
> Devices that are not ignored:
> =
> 0.0.0009
> 0.0.0150
> 0.0.0300-0.0.0301
> 0.0.0700-0.0.0702
> 0.0.1000-0.0.1002
> 0.0.2000-0.0.2002
>
> After the reboot:
>
> cio_ignore -L
> Devices that are not ignored:
> =
> 0.0.0009
> 0.0.0150
> 0.0.0300-0.0.0301
> 0.0.0700-0.0.0702
>
> It's ignoring 1000-1002, and 2000-2002.
>
> cio_ignore settings are supposed to survive a boot, correct?
>
>

[snip]

That's not the case. Upon reboot, the kernel command line determines the 
devices seen by the operating system. In a next step the configured devices are 
been freed from the ignore list. In your example the console (0009), the boot 
disk (0150) and two QETH devices (0300-0302, 0700-0702) are removed from the 
ignore list. If you want 1000-1002 and 2000-2002 to be persistently available 
you should configure them, e.g. using chzdev(8).

--
Kind Regards,
Viktor

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=04%7C01%7CSam.Cohen%40LRS.COM%7C4914a36e82ad41d989a708d8b33822e2%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637456400978625526%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JH%2BJPDl%2FX2Xgyhi%2BdOU0y%2Bk5RCcBeExuKMTTxupu324%3D&reserved=0

--
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: Modify ifcfg-encw0.0.nnnn at DR

[Cohen, Sam]

If you can login to root at the 3270 console, you can issue an ifconfig (or an 
ip) command to change the address, then a route command to set the default 
route.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Frank M. 
Ramaekers
Sent: Tuesday, October 6, 2020 08:07
To: LINUX-390@VM.MARIST.EDU
Subject: Modify ifcfg-encw0.0. at DR

How can I change the IP address of a network adapter at D/R.  Since the IP 
address is unusable, I cannot ssh to the machine.   Attempting vi from the VM 
console is a mess.
I have two lines to change:

IPADDR="10.1.20.88"
PREFIX="16"(to 24)

Ideas?

Frank M. Ramaekers Jr.  | Systems Senior Administrator | CIS Mainframe Services 
Unisys | (512)-387-3949 | Francis.Ramaekers at Unisys.Com

[unisys_logo]

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is for use only by the intended recipient. If you received this in 
error, please contact the sender and delete the e-mail and its attachments from 
all devices.
[Grey_LI]
  [Grey_TW] 

  [Grey_GP] 

 [Grey_YT] 

 [Grey_FB] 

 [Grey_Vimeo] 

 [Grey_UB] 


--
This message contains information which is privileged and confidential and is 
solely for the use of the intended recipient. If you are not the intended 
recipient, be aware that any review, disclosure, copying, distribution, or use 
of the contents of this message is strictly prohibited. If you have received 
this in error, please destroy it immediately and notify us at 
privacy...@globe.life.

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7Cb47d4b43e5b44577185508d86a1b9945%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637376014080354894&sdata=6VzLXE6CJ%2FUOgQ4huFyUdJzfzAQ0MjN8QvPtYr6imy8%3D&reserved=0

--
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: zLINUX and z/VSE

[Cohen, Sam]

Tom,

Some of my customers use z/VSE VTAPE server in the Linux using a Hipersocket 
connection between Linux and the guests.  Most VSE tape managers support using 
VSE VTAPE.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Tom Huegel
Sent: Wednesday, June 24, 2020 11:01 AM
To: LINUX-390@VM.MARIST.EDU
Subject: zLINUX and z/VSE

I don't know if this is really a question or just a thought.

I have a customer that recently installed a new z/14.
They are a relatively small shop, they currently run z/VM and a couple of z/VSE 
guests.
The z/14 has an IFL.

The manager asked me 'what can we do with that IFL?'
I thought I'd ask here if anyone was using z/LINUX guests to support z/VSE in 
some way. If so, what are you doing?

I'm just looking for ideas, I don't have an immediate problem that I am trying 
to solve.

Thanks,
Tom

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7Cc00ee74f10274fb42e4308d81868c9c6%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637286185633580004&sdata=p1AIOGT1QO836W0SCl4IhOjPQvSoaPozKrzRZvmIXhE%3D&reserved=0

--
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: Fwd: Future-Watch: Big changes to login and /home directory handling

[Cohen, Sam]

You sure this article isn't 30 days late?

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Dave McGuire
Sent: Thursday, April 30, 2020 10:11 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Fwd: Future-Watch: Big changes to login and /home directory 
handling

On 4/30/20 10:31 AM, Dave Jones wrote:
> This might be of some interest to the folks that follow this list.
>
> Scheduled for release this year. If adopted, it has the potential for 
> good and ill. /etc/passwd and /etc/shadow going away, replaced with 
> encrypted JSON, and other changes.
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> techrepublic.com%2Farticle%2Flinux-home-directory-management-is-about-
> to-undergo-major-change%2F&data=02%7C01%7CSam.Cohen%40LRS.COM%7C7f
> 6800dbbaf545ee22c008d7ed2a10cd%7C62af9ccc42164ae2a1d306614c59c315%7C0%
> 7C0%7C637238637248689781&sdata=bCOStGrKr2QVym2%2BCvtnoO3%2FgfMNR3g
> %2FLPd0qLXMpew%3D&reserved=0

  This is one of the must absurd things I've seen in years.  Are there any 
adults left in the room there at all?

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7C7f6800dbbaf545ee22c008d7ed2a10cd%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637238637248689781&sdata=A%2F2Xcf%2F%2BSm9PZDzXsKHcrmE92BrnAqjaMnul6hRHw6o%3D&reserved=0

--
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: BCACHE errors on lvextend, on reboot goes to dracut emergency mode

[Cohen, Sam]

Probably notthe Linux world seemed easier for me to understand before all 
the "unification" efforts (like grub, systemd, et al).  Just showing my age.  
Thanks for the explanation, Mark.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Mark Post
Sent: Wednesday, April 22, 2020 8:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: BCACHE errors on lvextend, on reboot goes to dracut emergency mode

On 4/22/20 11:21 AM, Cohen, Sam wrote:
> FWIW, every time I run dracut, I then run zipl before IPLing.

If you're doing this on a SLES system that's using grub2, I'm not at all sure 
zipl is doing what you think it is. The zipl command is *only* used to re-write 
the block locations for the "grub2 kernel" and "grub2 initrd" that are located 
in /boot/zipl.


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
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7Ca87167062a3a43e7a99b08d7e6d25f21%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637231663537468614&sdata=3jPfPHpQfWGEx7elyso8FjuaqAFKLUQ5FgInAnRPCkE%3D&reserved=0

--
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: BCACHE errors on lvextend, on reboot goes to dracut emergency mode

[Cohen, Sam]

Chris,

FWIW, every time I run dracut, I then run zipl before IPLing.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Will, Chris
Sent: Wednesday, April 22, 2020 8:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: BCACHE errors on lvextend, on reboot goes to dracut emergency mode

I have a more current version of Dracut but still having issues.  I expanded 
the volume (got the BCACHE messages), ran "dracut -f" and rebooted and got a 
disabled wait.  From the other server here are some of the messages from the 
rdsosreport file.

+ cat /lib/dracut/dracut-044-10.21.1
dracut-044-10.21.1

+ command -v lvm
+ lvm pvdisplay
  Read-only locking type set. Write locks are prohibited.
  Recovery of volume group "system-vg" failed.
  Cannot process volume group system-vg
  Read-only locking type set. Write locks are prohibited.
  Recovery of standalone physical volumes failed.
  Cannot process standalone physical volumes
+ lvm vgdisplay
  Read-only locking type set. Write locks are prohibited.
  Recovery of volume group "system-vg" failed.
  Cannot process volume group system-vg
+ lvm lvdisplay
  Read-only locking type set. Write locks are prohibited.
  Recovery of volume group "system-vg" failed.
  Cannot process volume group system-vg
+ command -v dmsetup
+ dmsetup ls --tree
No devices found
+ cat /proc/mdstat
cat: /proc/mdstat: No such file or directory
+ command -v ip
+ command -v journalctl
+ journalctl -ab --no-pager -o short-monotonic

 [7.037687] nbxdv0392 kernel: sd 1:0:1:1074675735: [sdh] Attached SCSI disk
[7.103887] nbxdv0392 dracut-initqueue[358]: Scanning devices dasda2 dasdd1 
sda1 sdb1 sdc1 sdd1  for LVM logical volumes system-vg/usr-lv
[7.151664] nbxdv0392 dracut-initqueue[358]: Read-only locking type set. 
Write locks are prohibited.
[7.151770] nbxdv0392 dracut-initqueue[358]: Recovery of volume group 
"system-vg" failed.
[7.151868] nbxdv0392 dracut-initqueue[358]: Cannot process volume group 
system-vg
[7.314522] nbxdv0392 dracut-initqueue[358]: Read-only locking type set. 
Write locks are prohibited.
[7.314639] nbxdv0392 dracut-initqueue[358]: Recovery of volume group 
"system-vg" failed.
[7.314737] nbxdv0392 dracut-initqueue[358]: Cannot process volume group 
system-vg
[8.096638] nbxdv0392 dracut-initqueue[358]: Scanning devices dasda2 dasdd1 
sda1 sdb1 sdc1 sdd1 sde1 sdf1 sdg1 sdh1  for LVM logical volumes 
system-vg/usr-lv
[8.115314] nbxdv0392 dracut-initqueue[358]: Read-only locking type set. 
Write locks are prohibited.
[8.115462] nbxdv0392 dracut-initqueue[358]: Recovery of volume group 
"system-vg" failed.
[8.115631] nbxdv0392 dracut-initqueue[358]: Cannot process volume group 
system-vg
[8.229860] nbxdv0392 dracut-initqueue[358]: Read-only locking type set. 
Write locks are prohibited.
[8.230011] nbxdv0392 dracut-initqueue[358]: Recovery of volume group 
"system-vg" failed.
[8.230129] nbxdv0392 dracut-initqueue[358]: Cannot process volume group 
system-vg
[  147.100038] nbxdv0392 dracut-initqueue[358]: Warning: dracut-initqueue 
timeout - starting timeout scripts [  147.136616] nbxdv0392 
dracut-initqueue[358]: Scanning devices dasda2 dasdd1 sda1 sdb1 sdc1 sdd1 sde1 
sdf1 sdg1 sdh1  for LVM logical volumes system-vg/usr-lv [  147.182501] 
nbxdv0392 dracut-initqueue[358]: Read-only locking type set. Write locks are 
prohibited.
[  147.182674] nbxdv0392 dracut-initqueue[358]: Recovery of volume group 
"system-vg" failed.
[  147.182834] nbxdv0392 dracut-initqueue[358]: Cannot process volume group 
system-vg [  147.495921] nbxdv0392 dracut-initqueue[358]: PARTIAL MODE. 
Incomplete logical volumes will be processed.
[  147.514583] nbxdv0392 dracut-initqueue[358]: Read-only locking type set. 
Write locks are prohibited.
[  147.514703] nbxdv0392 dracut-initqueue[358]: Recovery of volume group 
"system-vg" failed.
[  147.514797] nbxdv0392 dracut-initqueue[358]: Cannot process volume group 
system-vg [  148.261379] nbxdv0392 dracut-initqueue[358]: Warning: 
dracut-initqueue timeout - starting timeout scripts

Chris Will
Enterprise Linux/UNIX (ELU)
(313) 549-9729 Cell
cw...@bcbsm.com

-Original Message-
From: Linux on 390 Port  On Behalf Of marcy cortes
Sent: Tuesday, April 21, 2020 5:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: BCACHE errors on lvextend, on reboot goes to dracut emergency mode

[External email]


Yes, we had this in two forms.   Both fixed by the dracut fix (and
rerunning it)



Subject: SR101238520451 Re dracut timeout problems after 
patching



Marcy,

   We released this fix in maint 
(dracut-044.2-10.15.2.s390x).  The other issue related to this:



SR101237346921 Re: SLES Sp4 problem with lvm 
and device names




On Tue, Apr 21, 2020 at 10:26 AM Mark Post  wrote:

> On 4/21/20 12:11 PM, Will, Chris wrote:
> > Has anyone run into something like

Re: Adding disk to root LVM with RHEL 7

[Cohen, Sam]

Sorry

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Marcy Cortes
Sent: Wednesday, April 15, 2020 8:57 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding disk to root LVM with RHEL 7

Martha not Marcy :) 


-Original Message-
From: Linux on 390 Port  On Behalf Of Cohen, Sam
Sent: Wednesday, April 15, 2020 8:55 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding disk to root LVM with RHEL 7

Marcy,

Did you check zipl.conf to see if you need to list the disk in the rd.dasd line 
or cio_ignore (which is so unnecessary when running under z/VM).

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Marcy Cortes
Sent: Wednesday, April 15, 2020 8:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding disk to root LVM with RHEL 7

I'm kind of assuming RH7 works like sles11 and doesn't use grub2, but did you 
"mkinird; zipl" after getting that disk online?

You can also "cat / run/initramfs/rdsosreport.txt" in that emergency mode to 
get more details.




-Original Message-
From: Linux on 390 Port  On Behalf Of Rick Troth
Sent: Wednesday, April 15, 2020 8:26 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding disk to root LVM with RHEL 7

Looks like you did everything right: online, dasdfmt, fdasd, lvextend, 
vgextend, and using "1" instead of the whole disk (because it's ECKD and 
requires the VTOC).

The first block where you get an error is 16380912. Maybe that's a clue?
Looks like cylinder #109206 (150 4K blocks per ECKD cyl). Someone check my 
math? And the (new) root FS looks like 110100 cyls.
The VG has two disks, correct? How big are they?
So where is this troublesome block in the grand scheme?

I don't recall resizing a filesystem *down*, but I think it can be done.
I'm always nervous about that last block (or several) in any filesystem, any 
backing store (CKD, FBA, SCSI/SAN), anymode (LVM, partitioned, whole).
Never know when the system or some program will walk to the end "just because".

-- R; <><


On 4/15/20 10:58 AM, Martha McConaghy wrote:
> I have servers that I'm setting up with RHEL 7.8 on ECKD disk.  I installed 
> it with root in an LVM, all of that worked fine.  Now, I'm testing adding a 
> 2nd ECKD disk to the LVM as I know that will be required in the future, but 
> I'm running into a confusing problem.  Everything works as I expect and the 
> disk space shows up in / as it should.  When I reboot the server, however, it 
> goes to heck and ends up in emergency mode.  The most prominent feature of 
> the console are a bunch of I/O errors on device dm-2, which is the disk I 
> just added.  Below are the steps I followed to add the disk.  Before doing 
> this, I had activated the disk, added it to /etc/dasd.conf and run zipl.  
> After doing that, I rebooted to ensure that the disk came up online, which it 
> did.  So, I'm confident that the disk is there when the system rebooted the 
> 2nd time.
>
> I have a lot of colleagues who work with Linux all the time, but don't 
> usually have root as an LVM.  They haven't seen this problem before, but they 
> work mainly on X.  Could this be specific problem to using ECKD?  I have 
> thought of going to an FBA LUN, but had spare ECKD to use.
>
> Martha
>
>
> [root@opncl42 ~]# cio_ignore -r 0.0.0200
> [root@opncl42 ~]# chccwdev --online 0.0.0200 Setting device 0.0.0200 
> online Done
> [root@opncl42 ~]# lsdasd
> Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
> ==
> 0.0.0150   active  dasda 94:0ECKD  4096   46068MB   11793420
> 0.0.0200   active  dasdb 94:4ECKD  4096   23033MB   5896620
> [root@opncl42 ~]# vi /etc/dasd.conf
> [root@opncl42 ~]# zipl
> Using config file '/etc/zipl.conf'
> Building bootmap in '/boot'
> Building menu 'zipl-automatic-menu'
> Adding #1: IPL section '3.10.0-1127.el7.s390x' (default) Adding #2: 
> IPL section '3.10.0-1127.el7.s390x_with_debugging'
> Adding #3: IPL section 'linux'
> Preparing boot device: dasda (0150).
> Done.
> [root@opncl42 ~]# reboot
> ---
> [root@opncl42 ~]# lsdasd
> Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
> ==
> 0.0.0150   active  dasda 94:0ECKD  4096   46068MB   11793420
> 0.0.0200   active  dasdb 94:4ECKD  4096   23033MB   5896620
>
> [root@opncl42 ~]# dasdfmt -p -f /dev/dasdb Please enter the blocksize 
> of t

Re: Adding disk to root LVM with RHEL 7

[Cohen, Sam]

Marcy,

Did you check zipl.conf to see if you need to list the disk in the rd.dasd line 
or cio_ignore (which is so unnecessary when running under z/VM).

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Marcy Cortes
Sent: Wednesday, April 15, 2020 8:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding disk to root LVM with RHEL 7

I'm kind of assuming RH7 works like sles11 and doesn't use grub2, but did you 
"mkinird; zipl" after getting that disk online?

You can also "cat / run/initramfs/rdsosreport.txt" in that emergency mode to 
get more details.




-Original Message-
From: Linux on 390 Port  On Behalf Of Rick Troth
Sent: Wednesday, April 15, 2020 8:26 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding disk to root LVM with RHEL 7

Looks like you did everything right: online, dasdfmt, fdasd, lvextend, 
vgextend, and using "1" instead of the whole disk (because it's ECKD and 
requires the VTOC).

The first block where you get an error is 16380912. Maybe that's a clue?
Looks like cylinder #109206 (150 4K blocks per ECKD cyl). Someone check my 
math? And the (new) root FS looks like 110100 cyls.
The VG has two disks, correct? How big are they?
So where is this troublesome block in the grand scheme?

I don't recall resizing a filesystem *down*, but I think it can be done.
I'm always nervous about that last block (or several) in any filesystem, any 
backing store (CKD, FBA, SCSI/SAN), anymode (LVM, partitioned, whole).
Never know when the system or some program will walk to the end "just because".

-- R; <><


On 4/15/20 10:58 AM, Martha McConaghy wrote:
> I have servers that I'm setting up with RHEL 7.8 on ECKD disk.  I installed 
> it with root in an LVM, all of that worked fine.  Now, I'm testing adding a 
> 2nd ECKD disk to the LVM as I know that will be required in the future, but 
> I'm running into a confusing problem.  Everything works as I expect and the 
> disk space shows up in / as it should.  When I reboot the server, however, it 
> goes to heck and ends up in emergency mode.  The most prominent feature of 
> the console are a bunch of I/O errors on device dm-2, which is the disk I 
> just added.  Below are the steps I followed to add the disk.  Before doing 
> this, I had activated the disk, added it to /etc/dasd.conf and run zipl.  
> After doing that, I rebooted to ensure that the disk came up online, which it 
> did.  So, I'm confident that the disk is there when the system rebooted the 
> 2nd time.
>
> I have a lot of colleagues who work with Linux all the time, but don't 
> usually have root as an LVM.  They haven't seen this problem before, but they 
> work mainly on X.  Could this be specific problem to using ECKD?  I have 
> thought of going to an FBA LUN, but had spare ECKD to use.
>
> Martha
>
>
> [root@opncl42 ~]# cio_ignore -r 0.0.0200
> [root@opncl42 ~]# chccwdev --online 0.0.0200 Setting device 0.0.0200 
> online Done
> [root@opncl42 ~]# lsdasd
> Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
> ==
> 0.0.0150   active  dasda 94:0ECKD  4096   46068MB   11793420
> 0.0.0200   active  dasdb 94:4ECKD  4096   23033MB   5896620
> [root@opncl42 ~]# vi /etc/dasd.conf
> [root@opncl42 ~]# zipl
> Using config file '/etc/zipl.conf'
> Building bootmap in '/boot'
> Building menu 'zipl-automatic-menu'
> Adding #1: IPL section '3.10.0-1127.el7.s390x' (default) Adding #2: 
> IPL section '3.10.0-1127.el7.s390x_with_debugging'
> Adding #3: IPL section 'linux'
> Preparing boot device: dasda (0150).
> Done.
> [root@opncl42 ~]# reboot
> ---
> [root@opncl42 ~]# lsdasd
> Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
> ==
> 0.0.0150   active  dasda 94:0ECKD  4096   46068MB   11793420
> 0.0.0200   active  dasdb 94:4ECKD  4096   23033MB   5896620
>
> [root@opncl42 ~]# dasdfmt -p -f /dev/dasdb Please enter the blocksize 
> of the formatting [4096]:
> Drive Geometry: 32759 Cylinders * 15 Heads =  491385 Tracks
>
> I am going to format the device /dev/dasdb in the following way:
>Device number of device : 0x200
>Labelling device: yes
>Disk label  : VOL1
>Disk identifier : 0X0200
>Extent start (trk no)   : 0
>Extent end (trk no) : 491384
>Compatible Disk Layout  : yes
>Blocksize   : 4096
>Mode: Full
>
> --->> ATTENTION! <<---
> All data of that device will be lost.
> Type "yes" to continue, no will leave the disk untouched: yes 
> Formatting the device. This may take a while (get yourself a coffee).
> cyl   32759 of   32759 |#|100% [2m 43s]
> Finished formatting the device.
> Rereading the part

Re: CKD for linux guest and FBA for oracle

[Cohen, Sam]

Yes, you can have borth FICON and FCP attached disk on the same Linux image.

Sam Cohen
(217) 862-9227


From: Linux on 390 Port  on behalf of Jake Anderson 

Sent: Saturday, January 11, 2020 12:04:54 PM
To: LINUX-390@VM.MARIST.EDU 
Subject: CKD for linux guest and FBA for oracle

Hello

Is it possible to build Linux guest using CKD and define SCSI seperately to
oracle running on top of the same Linux guest.?

Jake

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7C65e062ba081347cf7db408d796ca89f1%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637143668990728218&sdata=N15K4DlWQfLUwC7RzIfNfNKqdk0qkz9wxVwNv%2BNBUU0%3D&reserved=0

--
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: KVM only supports 4guests

[Cohen, Sam]

Barton,

It depends on the licensed version of Redhat that you have.  From the footnote:

This guest limit does not apply to Red Hat Enterprise Linux with Unlimited 
Guests. There is no guest limit for Red Hat Enterprise Virtualization, Red Hat 
Enterprise Linux OpenStack Platform, and the Red Hat Enterprise Linux with 
Smart Virtualization bundle.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Barton
Sent: Monday, October 21, 2019 2:54 PM
To: LINUX-390@VM.MARIST.EDU
Subject: KVM only supports 4guests

I’m hearing at gse that red hat on z only supports 4 guests on kvm on z? Here’s 
a  link, am i missIng something?  
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccess.redhat.com%2Farticles%2Frhel-kvm-limits&data=02%7C01%7CSam.Cohen%40LRS.COM%7C48d4b88bb27041ea857c08d75671af04%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637072918605890971&sdata=g%2FPSoSxYqh2SgqhLX5V5KrvdkgFPSuWcvqrkupgaKj0%3D&reserved=0

Barton


--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7C48d4b88bb27041ea857c08d75671af04%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637072918605890971&sdata=imwx9PkkgF74LtoqU5u9d2mv2nZ0HgHu5OXuUlEwqVo%3D&reserved=0

--
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: Issues trying to install RHEL 8

[Cohen, Sam]

Martha,

What is your target hardware (i.e. what model Z is it)?

Sam

Sam Cohen
(217) 862-9227


From: Linux on 390 Port  on behalf of Martha McConaghy 

Sent: Thursday, August 1, 2019 7:44:05 AM
To: LINUX-390@VM.MARIST.EDU 
Subject: Re: Issues trying to install RHEL 8

Thanks for the links.  They didn't pan out though.

FYI - another person on the team (at another location) tried to do an
install using the same image I have and got the same results.  This was
in his test environment, completely different from the one I have.  So,
we seem to have stumbled into a new problem.  The install image we are
using is dated April 4.  He checked and it seems to be the latest one
available.

Martha

On 7/31/2019 2:55 PM, R P Herrold wrote:
> On Tue, 30 Jul 2019, Martha McConaghy wrote:
>
>> Has anyone run into problems getting RHEL 8 to install on Z? I've run into a
>
> Interesting suggestions all in this thread.  /me waves 'hi' to
> Smooge ;)
>
>
> I see a couple of moving parts here:
>
> 1 missing modules in a virtualization environment
>this may still persist, as it is not a well-tested
>path
>
> 2. inability to turn up the ethernet interface (shown in your
> report) possibly due to a re-naming. p[possibly due to a
> missing module
>
>
> My research showed two possibly relevant bugs in the Red Hat
> public tracker
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D1396217&data=02%7C01%7CSam.Cohen%40LRS.COM%7C36a4019fcdd44e96769408d7167e88e3%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637002605031657487&sdata=0c6v0QhcamlvTJMnp95MiqWJW%2BSLHoN1%2B%2BFpoIWQQ7Q%3D&reserved=0
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D1396217&data=02%7C01%7CSam.Cohen%40LRS.COM%7C36a4019fcdd44e96769408d7167e88e3%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637002605031667483&sdata=6VzdmeGyBWwRR%2Fqh3mYY3mt8M7t5GuMIdL1qQ%2BkAEXk%3D&reserved=0
> missing modules in a virtualization environment
>
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D1680049&data=02%7C01%7CSam.Cohen%40LRS.COM%7C36a4019fcdd44e96769408d7167e88e3%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637002605031667483&sdata=VnCf3jwvJAT3GB6dx%2B0JlJm1F46QJQAB6pRJJ4D3PTE%3D&reserved=0
>
> "[   10.810441] localhost multipathd[933]: dasda: failed to
> get udev uid: Invalid"
> argument
>
> "[   10.367618] localhost dracut-pre-udev[534]: modprobe:
> FATAL: Module sha256 no"
> "t found in directory /lib/modules/4.18.0-32.el8.s390x"
>
> "[   10.530096] localhost systemd-udevd[834]: link_config:
> autonegotiation is uns"
> "et or enabled, the speed and duplex are not writable."
> "[   10.530308] localhost systemd-udevd[834]: Could not set
> Alias=, MACAddress= o"
> "r MTU= on eth0: Resource temporarily unavailable"
> "[   10.530334] localhost systemd-udevd[834]: Could not apply
> link config to eth0"
> ", ignoring: Resource temporarily unavailable"
> "[   10.533283] localhost systemd-udevd[756]: Process
> 'ccw_init' failed with exit"
> "code 1."
>
> comment 7
>
> The problem seems to be in an incorrect name of the network
> device specified on the kernel command line:
>
> rd.znet=qeth,0.0.a700,0.0.a701,0.0.a702,layer2=1,portno=0
> ip=10.62.40.144::10.62.40.1:24:zll0009:enccw0.0.a700:none
>
> "enccw0.0.a700" should be replaced with "enca700". It's
> because of a new naming scheme for s390x network devices
> introduced in
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsystemd%2Fsystemd%2Fcommit%2F0037a669ac9a2bbedccdb2f483111351e8ff4659&data=02%7C01%7CSam.Cohen%40LRS.COM%7C36a4019fcdd44e96769408d7167e88e3%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637002605031667483&sdata=lPyg0H1xofsUYQNOKg1Xb2%2F72y%2BoHnZHPalTmPGdpRc%3D&reserved=0
>
> comment 13
>
> Please Change the Dokumentation
> (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccess.redhat.com%2Fdocumentation%2Fen-us%2Fred_hat_enterprise_linux%2F8-beta%2Fhtml%2Finstalling_and_deploying_rhel%2Findex&data=02%7C01%7CSam.Cohen%40LRS.COM%7C36a4019fcdd44e96769408d7167e88e3%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637002605031667483&sdata=CWFurWZihpI0opeSNLan41rJ%2FJYCbsnIaz9zFbA8UiI%3D&reserved=0),
> because we used it as reference and there was no difference to
> 7.X !!!
>
> "Example 14.1. Customized generic.prm file
>
> ro ramdisk_size=4 cio_ignore=all,!condev
> inst.repo=http://example.com/path/to/repository
> rd.znet=qeth,0.0.0600,0.0.0601,0.0.0602,layer2=1,portno=0,portname=foo
> ip=192.168.17.115::192.168.17.254:24:foobar.systemz.example.com:enccw0.0.0600:none
> nameserver=192.168.17.1
> rd.dasd=0.0.0200 rd.dasd=0.0.0202
> rd.zfcp=0.0.4000,0x5005076300C213e9,0x5022
> inst.ks=http://example.com/path/to/kickstart";
>
> Thanks a lot,
>
>
> Hope this gives you the needed trail-head
>
> -- Russ herrold
>
> 

Re: Issues trying to install RHEL 8

[Cohen, Sam]

Martha,

It's been a while, but i may have seen this and was stumped.  I think i bumped 
up the virtual machine to 4G and got passed it.

Sam

Sam Cohen
(217) 862-9227


From: Linux on 390 Port  on behalf of Martha McConaghy 

Sent: Tuesday, July 30, 2019 9:52:04 PM
To: LINUX-390@VM.MARIST.EDU 
Subject: Issues trying to install RHEL 8

Has anyone run into problems getting RHEL 8 to install on Z? I've run
into a weird problem.  Two different experienced Linux guys have looked
at it, and we are all stumped.

Background:

The install is being done in a 3G virtual machine on z/VM 6.4 on a
LinuxOne (z13 generation).  We have lots of different versions of Linux
running on the same system, including RHEL 7, CentOS, Ubuntu 18 and SLES
15.  So, I don't think its a kernel/cpu type problem.

Problem:

When I run the REDHAT exec to bring up the install kernel, it starts
booting and things look like they will be OK.  Until it gets to the
point where "dracut initqueue" starts.  There is a message "7 urandom
warnings(s) missed due to ratelimiting".  It then pauses for a couple of
minutes, followed by a series of messages, "dracut-initqueue timeout -
starting timeout scripts". Eventually, it ends up in dracut in emergency
mode.  The install process never starts.  I've changed numerous
parameters, even changed what type of disk I'm using for the install.
It doesn't matter, its exactly the same problem each time.

Really scratching my head on this one.

Martha

Ý"Ý0;32m  OK  "Ý0m+ Reached target Local File Systems.""
  Starting Create Volatile Files and Directories...""
  Starting Open-iSCSI...""
Ý"Ý0;32m  OK  "Ý0m+ Started Open-iSCSI.""
Ý"Ý0;32m  OK  "Ý0m+ Started Create Volatile Files and Directories.""
Ý"Ý0;32m  OK  "Ý0m+ Reached target System Initialization.""
Ý"Ý0;32m  OK  "Ý0m+ Reached target Basic System.""
  Starting dracut initqueue hook...""
Ý6.306800+ dracut-initqueueÝ929+: RTNETLINK answers: File exists""
Ý   84.168981+ random: crng init done
Ý   84.168992+ random: 7 urandom warning(s) missed due to ratelimiting
Ý  142.340863+ dracut-initqueueÝ929+: Warning: dracut-initqueue timeout
- starting timeout scripts""
Ý  142.931884+ dracut-initqueueÝ929+: Warning: dracut-initqueue timeout
- starting timeout scripts""
Ý  143.490965+ dracut-initqueueÝ929+: Warning: dracut-initqueue timeout
- starting timeout scripts""
Ý  144.080845+ dracut-initqueueÝ929+: Warning: dracut-initqueue timeout
- starting timeout scripts""

  209.140407+ dracut-initqueueÝ929+: Warning: dracut-initqueue timeout -
starting timeout scripts""
Ý  209.700768+ dracut-initqueueÝ929+: Warning: dracut-initqueue timeout
- starting timeout scripts""
Ý  210.270398+ dracut-initqueueÝ929+: Warning: dracut-initqueue timeout
- starting timeout scripts""
Ý  210.270531+ dracut-initqueueÝ929+: Warning: Could not boot.""
  Starting Setup Virtual Console...""
Ý"Ý0;32m  OK  "Ý0m+ Started Setup Virtual Console.""
  Starting Dracut Emergency Shell...""
Warning: /dev/root does not exist

Generating "/run/initramfs/rdsosreport.txt"

--
Martha McConaghy
Marist: System Architect/Technical Lead
SHARE Association: Vice President
Marist College IT
Poughkeepsie, NY 12601

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7Cd1be4eee62ae4fdb954608d7156269e8%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C637001384749448763&sdata=x38wr4pyDSisBJ03LsaArE848qIi5q%2FGF1kh4OdXGu0%3D&reserved=0

--
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: Devices for dracut in sles 12 SP4

[Cohen, Sam]

I'm going to ask a religious questionif you're running under z/VM and 
(ideally) giving the virtual machine only what it needs, why would you use 
cio_ignore at all?  

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Mark Post
Sent: Tuesday, June 11, 2019 8:24 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Devices for dracut in sles 12 SP4

On 6/10/19 3:52 PM, Marcy Cortes wrote:
> Does anyone know how dracut is really supposed to be told about devices? I 
> was under the impression that all devices were allowed unless explicity in a 
> cio_ignore when running under z/VM.

That's been the default for new installations on z/VM for a while now.
However, if a system was upgraded from a version prior to that, the cio_ignore 
parameter will still be in your kernel parameters, and can cause problems like 
this. (Or, if someone chose to activate device blacklisting during a new 
install.)

Check /proc/cmdline to see if it's there. If it is, remove it from 
/boot/grub2/grub.cfg, and /etc/default/grub so that the next time you reboot 
things should be more reasonable.

> At least that's the impression I get reading this 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2Flinuxonibm%2Fcom.ibm.linux.
> z.lhdd%2Flhdd_r_cio_ignore_cmd.html&data=02%7C01%7CSam.Cohen%40LRS
> .COM%7C0a41595b36dc47ae1fa908d6ee813b90%7C62af9ccc42164ae2a1d306614c59
> c315%7C0%7C0%7C636958636152651551&sdata=WvsnQZwpFYclPqprameZpTTDW8
> vaet45KuaGohzP31E%3D&reserved=0

I'm not sure why you would get that impression from that page. The only 
references I see to z/VM on that page relate to adding devices to the 
cio_ignore list after booting, and what happens if that device is detached and 
later re-attached.


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
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7C0a41595b36dc47ae1fa908d6ee813b90%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C636958636152661546&sdata=EcmxBcaJl2MmxcM1DJXS%2FtGH5d9XvGC4y5WDA4lcbmI%3D&reserved=0

--
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: Problem with Hipersockets z13 SUSE 12 Sp4

[Cohen, Sam]

Marco,

It sounds like the hipersockets connection has not been made visible to the 
Linux guest in the z/VM directory.  Please verify with your z/VM administrator 
that the hipersockets connection has been defined (and that there is some other 
guest on that same hipersocket connection so you can test the communications).  
If the hipersocket link has been defined to your virtual machine, it might be 
blocked and you'll need to use cio_ignore to make it visible.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of Marco Banuelos
Sent: Tuesday, February 5, 2019 3:01 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Problem with Hipersockets z13 SUSE 12 Sp4

Hi all,

I'm experiencing some problems with SLES 12 SP4 running on z/vm 7.1, I made a 
SLES 12 SP4 installation and I configured with OSA network, now the customer 
want's to switch from OSA to Hipersocket and the HiperSocket network it's not 
showed on the SLES 12 SP4 vm, I rebooted the vm, I tried to install manually 
the driver, but it's not working.

Does anyone experienced this issue?

Thank you.
Best Regards.



Marco Antonio Bañuelos Hernández
Ingeniero de Pre-venta
marco.banue...@suse.com

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7C86fbdccec46b47f09c3608d68bcdeb80%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C1%7C636850113886160721&sdata=z69SCdWJ5rYYzKdUzDn9tmHcW1E9I72WUSYgX0mUXvY%3D&reserved=0

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: question on SWAPGEN preferences

[Cohen, Sam]

David,

Personally, I don't use SWAPGEN, I just run makeswap as part of boot.local, 
rc.local or systemd local routines.  This way, I don't have to worry about 
changes in V-disk sizes or future changes in swap disk formats.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port  On Behalf Of David Boyes
Sent: Thursday, December 27, 2018 7:38 AM
To: LINUX-390@VM.MARIST.EDU
Subject: question on SWAPGEN preferences

I'm trying to tackle some of the backlogged nits with SWAPGEN, and wanted to 
get opinions on a couple of changes.



  1.  Right now, the size of the swap disk is specified in # of blocks. Would 
it be valuable to be able to specify this in megabytes/gigabytes and let 
SWAPGEN worry about the geometry issues needed to get that amount of space? For 
backward compatibility, the default would remain # of blocks, but adding a new 
option to interpret the value as meg/gig wouldn’t break anything, eg:

SWAPGEN 300 1048576 would be treated as allocate 1048576 blocks. This would be 
the default.

SWAPGEN 300 8G ( UNITS SIZE would look at the geometry of the storage 
requested, figure out how many blocks would be needed (at the desired block 
size) to get that amount of space, and them do the deed. New option values: 
UNITS SIZE indicates by size, UNITS BLKS to get the # of blocks, default UNITS 
BLKS.

  2.  Add a BLKSIZE option to specify size of blocks (512,1024, 4096) for more 
efficient use of space.  Default would remain 512 (as now).



Thoughts?

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7C20da5b76d9804590dc2908d66c1240a1%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C636815222990736053&sdata=OIsOM6%2FkWyG%2FgWcUDrx8nrwrBvzQEOee0hnSeUtrtQM%3D&reserved=0
--
For more information on Linux on System z, visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2F&data=02%7C01%7CSam.Cohen%40LRS.COM%7C20da5b76d9804590dc2908d66c1240a1%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C636815222990736053&sdata=OghbrnNCE2iANrYwpsWPYfYZOr2nveNxxrTAXBiH85I%3D&reserved=0

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Installing Fedora 29 in an LPAR (no z/VM)

[Cohen, Sam]

Jim,

Make sure you have sufficient memory allocated in the LPAR to hold the RAM disk

Thanks,

Sam

-Original Message-
From: Linux on 390 Port  On Behalf Of Neale Ferguson
Sent: Thursday, November 15, 2018 12:35 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Installing Fedora 29 in an LPAR (no z/VM)

Your parm file is missing root=

On 11/15/18, 14:33, "Linux on 390 Port on behalf of Jim Elliott" 
 wrote:

1st time trying to install Fedora and I am doing this in an LPAR (not under
z/VM). I am booting the .iso from the HMC using FTP. The install stops
after getting the message: "Warning: /dev/ram0 does not exist".Any
suggestions from the list as to what I am doing wrong? I am following the
instructions in the RHEL 7.5 doc (which is what the Fedora site pointed me
to).

Jim Elliott
 


--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7C4f01df806ebd410a2bec08d64b31c9ad%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C636779074546221734&sdata=vJAGvbodkEjgWsOUi12vi85kuHOdMQAyBQ6V782a1wA%3D&reserved=0
--
For more information on Linux on System z, visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2F&data=02%7C01%7CSam.Cohen%40LRS.COM%7C4f01df806ebd410a2bec08d64b31c9ad%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C0%7C636779074546231743&sdata=2pslQpgOX8vEzGT0V7Cu8OuDdGarChOU85bqDDUTuRk%3D&reserved=0

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Networking flakey since latest kernel patches

[Cohen, Sam]

systemctl status device_cio_free -l
device_cio_free.service - Free all devices on startup
   Loaded: loaded (/usr/lib/systemd/system/device_cio_free.service; enabled; 
vendor preset: disabled)
   Active: active (exited) since Tue 2018-01-09 16:41:23 CST; 32s ago
  Process: 524 ExecStart=/sbin/device_cio_free (code=exited, status=0/SUCCESS)
 Main PID: 524 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/device_cio_free.service

Jan 09 16:41:23 rhel7.demo.lrsinc.org systemdÝ1¨: Started Free all devices on 
startup.



FYI:  /etc/sysconfig/network-scripts/ has ifcfg-enccw0.0.1000 and 
ifcfg-enccw0.0.e000; only difference between non-working network startup and 
working network startup is in cio_ignore list in zipl.conf:   
parameters="root=/dev/disk/by-path/ccw-0.0.0200-part1 rd.dasd=0.0.0200 
rd.dasd=0.0.0100(diag) cio_ignore=all,!0009,!1000-1002,!e000-e002 
LANG=en_US.UTF-8"

Thanks,

Sam Cohen

(217) 862-9227 (office)
(602) 327-2134 (cell)
(217) 547-0967 (fax)



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dan Horák
Sent: Tuesday, January 9, 2018 03:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Networking flakey since latest kernel patches

On Tue, 9 Jan 2018 22:10:58 +0000
"Cohen, Sam" mailto:sam.co...@lrs.com>> wrote:

> Yes.  More info:  On RHEL 7, I had to add cio_ignore -r for the QDIO
> devices (OSA and Hipersockets) in zipl.conf; that wasn't persistent.

hmm, unblocking of the devices must happen automagically, the script 
responsible for that reads the /etc/sysconfig/network-scripts/ifcfg-*
files early during boot. What's the output of "systemctl status 
device_cio_free"?


Dan


> In SLES 12, cio_ignore isn't an issue (it's turned off), but udev
> rules for the OSA VNIC disappeared (but not the Hipersockets).
> Curiouser and Curiouser
>
> Thanks,
>
> Sam Cohen
>
> (217) 862-9227 (office)
> (602) 327-2134 (cell)
> (217) 547-0967 (fax)
>
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Carey Tyler Schug Sent: Tuesday, January 9, 2018 02:57 PM
> To: LINUX-390@VM.MARIST.EDU<mailto:LINUX-390@VM.MARIST.EDU>
> Subject: Re: Networking flakey since latest kernel patches
>
> Are those the patches for the hardware bugs meltdown and spectre?  I
> think we were warned there would be problems, and this certainly
> seems compatible with the kind of fix that might be needed
> (especially virtual).
>
>
> On 01/09/2018 09:44 AM, Cohen, Sam wrote:
> > Both my RHEL7 and SLES12 guests, networking has gone flakey since
> > the latest kernel patches came in.  It looks like previously
> > remembered QDIO configurations are now forgotten and I have to run
> > znetconf then restart networking to get my OSA connections (and
> > hipersockets on RH) working.  Is anyone else seeing this?
> > Hipervisor is z/VM 6.4 with RSU 1702 (not that it should matter).
> >
> > Thanks,
> >
> > Sam Cohen
> >
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu<mailto:lists...@vm.marist.edu> with 
> > the message: INFO
> > LINUX-390 or visit
> > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ma
> > rist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%
> > 40LRS .COM%7Cb4fa9128cf1b42c2fbbd08d557ac05f7%
> > 7C62af9ccc42164ae2a1d306614c59 c315%7C0%7C1%
> > 7C636511319026563982&sdata=mAGuNsI%2F3f46L%2F%2F5qs23%2BB
> > tWIrqZbXYzQ5HBLV6raE4%3D&reserved=0
> > --
> > For more information on Linux on System z, visit
> > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.l
> > inuxvm.org%2F&data=02%7C01%7CSam.Cohen%40LRS.COM%
> > 7Cb4fa9128cf1b42c2fbb d08d557ac05f7%
> > 7C62af9ccc42164ae2a1d306614c59c315%7C0%7C1%7C63651131902
> > 6563982&sdata=xO8GD1MlWYTAKxTI96P%2F7K9bR2sztUqTtS%2FO6WfkLiY%
> > 3D&reser ved=0
> >
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to lists...@vm.marist.edu<mailto:lists...@vm.marist.edu> with the 
> message: INFO LINUX-390 or
> visit
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7Cb4fa9128cf1b42c2fbbd08d557ac05f7%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C1%7C63651131902

Re: Networking flakey since latest kernel patches

[Cohen, Sam]

Yes.  More info:  On RHEL 7, I had to add cio_ignore -r for the QDIO devices 
(OSA and Hipersockets) in zipl.conf; that wasn't persistent.  In SLES 12, 
cio_ignore isn't an issue (it's turned off), but udev rules for the OSA VNIC 
disappeared (but not the Hipersockets).  Curiouser and Curiouser

Thanks,

Sam Cohen

(217) 862-9227 (office) 
(602) 327-2134 (cell)
(217) 547-0967 (fax)



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Carey 
Tyler Schug
Sent: Tuesday, January 9, 2018 02:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Networking flakey since latest kernel patches

Are those the patches for the hardware bugs meltdown and spectre?  I think we 
were warned there would be problems, and this certainly seems compatible with 
the kind of fix that might be needed (especially virtual).


On 01/09/2018 09:44 AM, Cohen, Sam wrote:
> Both my RHEL7 and SLES12 guests, networking has gone flakey since the latest 
> kernel patches came in.  It looks like previously remembered QDIO 
> configurations are now forgotten and I have to run znetconf then restart 
> networking to get my OSA connections (and hipersockets on RH) working.  Is 
> anyone else seeing this?  Hipervisor is z/VM 6.4 with RSU 1702 (not that it 
> should matter).
>
> Thanks,
>
> Sam Cohen
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
> visit
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ma
> rist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS
> .COM%7Cb4fa9128cf1b42c2fbbd08d557ac05f7%7C62af9ccc42164ae2a1d306614c59
> c315%7C0%7C1%7C636511319026563982&sdata=mAGuNsI%2F3f46L%2F%2F5qs23%2BB
> tWIrqZbXYzQ5HBLV6raE4%3D&reserved=0
> --
> For more information on Linux on System z, visit
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.l
> inuxvm.org%2F&data=02%7C01%7CSam.Cohen%40LRS.COM%7Cb4fa9128cf1b42c2fbb
> d08d557ac05f7%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C1%7C63651131902
> 6563982&sdata=xO8GD1MlWYTAKxTI96P%2F7K9bR2sztUqTtS%2FO6WfkLiY%3D&reser
> ved=0
>

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CSam.Cohen%40LRS.COM%7Cb4fa9128cf1b42c2fbbd08d557ac05f7%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C1%7C636511319026563982&sdata=mAGuNsI%2F3f46L%2F%2F5qs23%2BBtWIrqZbXYzQ5HBLV6raE4%3D&reserved=0
--
For more information on Linux on System z, visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2F&data=02%7C01%7CSam.Cohen%40LRS.COM%7Cb4fa9128cf1b42c2fbbd08d557ac05f7%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C1%7C636511319026563982&sdata=xO8GD1MlWYTAKxTI96P%2F7K9bR2sztUqTtS%2FO6WfkLiY%3D&reserved=0

Networking flakey since latest kernel patches

[Cohen, Sam]

Both my RHEL7 and SLES12 guests, networking has gone flakey since the latest 
kernel patches came in.  It looks like previously remembered QDIO 
configurations are now forgotten and I have to run znetconf then restart 
networking to get my OSA connections (and hipersockets on RH) working.  Is 
anyone else seeing this?  Hipervisor is z/VM 6.4 with RSU 1702 (not that it 
should matter).

Thanks,

Sam Cohen


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Having trouble getting started.

[Cohen, Sam]

Probably a silly question, but are you current on your HMC code?

Thanks,

Sam Cohen

(217) 862-9227 (office) 
(602) 327-2134 (cell)



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Hamilton, 
Robert
Sent: Thursday, January 5, 2017 1:35 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Having trouble getting started.

 On 1/5/2017 at 03:51 PM, Mike Walter
> wrote:
>> Rob,
>>
>> There's an FTP exit used to authorize users on z/VM to access the HMC 
>> DVD drive.  I don't recall the name of the IBM provided sample exit, 
>> but it wasn't too difficult to find in the TCPIP manuals.
>>
>> I set ours up to authorize specific ID's, and to MSG OP when any 
>> attempt was made to FTP using the HMC DVD drive -- clearly pointing 
>> out
>invalid attempts.
>> That way both good and invalid attempts are logged.
>>
>> That exit was needed in addition to connecting the DVD drive to the 
>> proper LPAR from the HMC.
>
>That would only be true if
>1. They had z/VM installed.
>2. They were trying to have z/VM access the DVD drive for TCP/IP.
>
>Neither is the case here.
>
>
>Mark Post


The documentation on the HMC is "funny" here (Appendix H); if I need to access 
the DVD via FTP, I need to go to Configure Network Setup (or something very 
close to that), which does not seem to be an option anywhere. HA.
Then, it says I should use "Enable FTP Access to Mass Storage Media", which I 
kinda found by accident. When I go there, it asks for the IP address of the 
server that will be accessing this DVD drive, so I give it an existing IP 
address, only to have it tell me that

(A) There's no media in the drive, and
(B) I can't read it anyway because the file system is...unknown.

And then, after I Enable FTP Access Blah Blah it says I can Load from Removable 
Media. Or Server.

There is also an Access Removable Media, that also says there's no actual media 
in there.

Sohardware problem? I don't know whether this DVD drive has been used since 
the z114 was installed. What's the MTBF for something you don't use?

R;


Rob Hamilton
Sr. System Engineer
Chemical Abstracts Service
A division of the American Chemical Society


Confidentiality Notice: This electronic message transmission, including any 
attachment(s), may contain confidential, proprietary, or privileged information 
from Chemical Abstracts Service ("CAS"), a division of the American Chemical 
Society ("ACS"). If you have received this transmission in error, be advised 
that any disclosure, copying, distribution, or use of the contents of this 
information is strictly prohibited. Please destroy all copies of the message 
and contact the sender immediately by either replying to this message or 
calling 614-447-3600.

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: zLinux backup solutions

[Cohen, Sam]

Scott,

See the PPRCOPY DEFINESESSION and PPRCOPY POPULATESESSION commands.

Thanks,

Sam Cohen

(217) 862-9227 (office) 
(602) 327-2134 (cell)



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott 
Rohling
Sent: Friday, November 11, 2016 11:19 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: zLinux backup solutions

Maybe we are talking about different things...you can establish
relationships between source/target volumes -- but I don't see anything
that let's you define a consistency group -- i.e.   several volumes which
will be flashed at the exact moment in time.

Scott Rohling

On Fri, Nov 11, 2016 at 10:00 AM, Cohen, Sam  wrote:

> In the ICKDSF manual (http://www.ibm.com/support/ 
> knowledgecenter/SSB27U_6.3.0/com.ibm.zos.v2r1.ickug00/toc.htm), check 
> out the FLASHCOPY and PPRCOPY commands.
>
> Thanks,
>
> Sam Cohen
>
> (217) 862-9227 (office)
> (602) 327-2134 (cell)
>
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of 
> Scott Rohling
> Sent: Friday, November 11, 2016 10:46 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: zLinux backup solutions
>
> Please explain how to use ICKDSF to establish a consistency group and
> initiate a flashcopy I see no way to do it...
>
> Scott Rohling
>
> On Fri, Nov 11, 2016 at 9:22 AM, Cohen, Sam  wrote:
>
> >
> > CSM (or command line on the SSCP (or whatever it's called these 
> > days) can do it, as can ICKDSF on z/VM.
> >
> > Sam
> >
> > Sent from my Verizon 4G LTE smartphone
> >
> >
> >  Original message 
> > From: Scott Rohling 
> > Date: 11/11/16 10:15 (GMT-07:00)
> > To: LINUX-390@VM.MARIST.EDU
> > Subject: Re: zLinux backup solutions
> >
> > I'm talking about initiating the flashcopy  ...  not mirroring
> solutions...
> >
> >
> > CSM let's you initiate flashcopy with consistency groups.z/VM can
> only
> > do serial FLASHCOPY commands...
> >
> > Scott Rohling
> >
> > On Fri, Nov 11, 2016 at 8:48 AM, Cohen, Sam  wrote:
> >
> > > Scott,
> > >
> > > You don't need Copy Services Manager, you just need a storage 
> > > subsystem capable and enabled for Global Mirror, which is 
> > > independent and outside
> > of
> > > any operating system.  z/VM disks can be part of a consistency 
> > > group,
> > just
> > > as VSE, z/OS, Linux or TPF disks can.
> > >
> > > Sam
> > >
> > > Sent from my Verizon 4G LTE smartphone
> > >
> > >
> > >  Original message 
> > > From: Scott Rohling 
> > > Date: 11/11/16 08:20 (GMT-07:00)
> > > To: LINUX-390@VM.MARIST.EDU
> > > Subject: Re: zLinux backup solutions
> > >
> > > While z/VM can't use consistency groups -- z/OS and zLinux can with CSM
> > > (Copy Services Manager)  I'm currently involved in a project
> > where
> > > we have this running on a zLinux guest to be able to flash with
> > consistency
> > > groups.
> > >
> > > Scott Rohling
> > >
> > > On Fri, Nov 11, 2016 at 6:35 AM, Alan Altmark 
> > > 
> > > wrote:
> > >
> > > > On Thursday, 11/10/2016 at 09:12 GMT, "Ponte, Douglas C. (JMD)"
> > > >  wrote:
> > > > > Fullpack volume backups  can be run daily, weekly and 
> > > > > monthly,
> > > using
> > > > JCL with automation tools
> > > > > (existing on z/OS already, e.g. BMC Control-M or Tivoli
> Automation).
> > > > This should be done with all
> > > > > z/VM and zLinux volumes.
> > > > >
> > > > > In the full volume backup cases, stopping/shutting down is not 
> > > > > always
> > > > necessary, albeit it may be
> > > > > good practice to at least quiesce when it comes to DB?s and 
> > > > > heavy use
> > > > servers. (e.g. DB2, Oracle,
> > > > > etc)
> > > >
> > > > WARNING:  To do this reliably, you need software that is capable 
> > > > of establishing an I/O consistency group.  If you want to 
> > > > FLASHCOPY the volumes and sequentially backup the volume copies, 
> > > > that's ok, but do
> > NOT
> > > > just sequentially copy the live volumes of a running z/VM system.
> > > > (If
> > > you
> > > > wouldn't do it to a run

Re: zLinux backup solutions

[Cohen, Sam]

In the ICKDSF manual 
(http://www.ibm.com/support/knowledgecenter/SSB27U_6.3.0/com.ibm.zos.v2r1.ickug00/toc.htm),
 check out the FLASHCOPY and PPRCOPY commands.  

Thanks,

Sam Cohen

(217) 862-9227 (office) 
(602) 327-2134 (cell)



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott 
Rohling
Sent: Friday, November 11, 2016 10:46 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: zLinux backup solutions

Please explain how to use ICKDSF to establish a consistency group and
initiate a flashcopy I see no way to do it...

Scott Rohling

On Fri, Nov 11, 2016 at 9:22 AM, Cohen, Sam  wrote:

>
> CSM (or command line on the SSCP (or whatever it's called these days) 
> can do it, as can ICKDSF on z/VM.
>
> Sam
>
> Sent from my Verizon 4G LTE smartphone
>
>
>  Original message 
> From: Scott Rohling 
> Date: 11/11/16 10:15 (GMT-07:00)
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: zLinux backup solutions
>
> I'm talking about initiating the flashcopy  ...  not mirroring solutions...
>
>
> CSM let's you initiate flashcopy with consistency groups.z/VM can only
> do serial FLASHCOPY commands...
>
> Scott Rohling
>
> On Fri, Nov 11, 2016 at 8:48 AM, Cohen, Sam  wrote:
>
> > Scott,
> >
> > You don't need Copy Services Manager, you just need a storage 
> > subsystem capable and enabled for Global Mirror, which is 
> > independent and outside
> of
> > any operating system.  z/VM disks can be part of a consistency 
> > group,
> just
> > as VSE, z/OS, Linux or TPF disks can.
> >
> > Sam
> >
> > Sent from my Verizon 4G LTE smartphone
> >
> >
> >  Original message 
> > From: Scott Rohling 
> > Date: 11/11/16 08:20 (GMT-07:00)
> > To: LINUX-390@VM.MARIST.EDU
> > Subject: Re: zLinux backup solutions
> >
> > While z/VM can't use consistency groups -- z/OS and zLinux can with CSM
> > (Copy Services Manager)  I'm currently involved in a project
> where
> > we have this running on a zLinux guest to be able to flash with
> consistency
> > groups.
> >
> > Scott Rohling
> >
> > On Fri, Nov 11, 2016 at 6:35 AM, Alan Altmark 
> > 
> > wrote:
> >
> > > On Thursday, 11/10/2016 at 09:12 GMT, "Ponte, Douglas C. (JMD)"
> > >  wrote:
> > > > Fullpack volume backups  can be run daily, weekly and 
> > > > monthly,
> > using
> > > JCL with automation tools
> > > > (existing on z/OS already, e.g. BMC Control-M or Tivoli Automation).
> > > This should be done with all
> > > > z/VM and zLinux volumes.
> > > >
> > > > In the full volume backup cases, stopping/shutting down is not 
> > > > always
> > > necessary, albeit it may be
> > > > good practice to at least quiesce when it comes to DB?s and 
> > > > heavy use
> > > servers. (e.g. DB2, Oracle,
> > > > etc)
> > >
> > > WARNING:  To do this reliably, you need software that is capable 
> > > of establishing an I/O consistency group.  If you want to 
> > > FLASHCOPY the volumes and sequentially backup the volume copies, 
> > > that's ok, but do
> NOT
> > > just sequentially copy the live volumes of a running z/VM system.  
> > > (If
> > you
> > > wouldn't do it to a running z/OS system, don't do it to any other
> > system.)
> > >  This process is intimately tied to your DR strategy, too, so get 
> > > it right.
> > >
> > > If you have databases, use the backup software for the database.  
> > > If you're using hardware replication, be sure that it's supported 
> > > by the database vendor.
> > >
> > > Some people take a too-casual approach to backups and DR.  I too 
> > > often hear "Don't worry, I'm doing it from z/OS." as though z/OS 
> > > has magical powers over z/VM and Linux.  Don't fall into that 
> > > trap.  That way there
> > be
> > > dragons.
> > >
> > > Alan Altmark
> > >
> > > Senior Managing z/VM and Linux Consultant Lab Services System z 
> > > Delivery Practice IBM Systems & Technology Group 
> > > ibm.com/systems/services/labservices
> > > office: 607.429.3323
> > > mobile; 607.321.7556
> > > alan_altm...@us.ibm.com
> > > IBM Endicott
> > >
> > > --

Re: zLinux backup solutions

[Cohen, Sam]

CSM (or command line on the SSCP (or whatever it's called these days) can do 
it, as can ICKDSF on z/VM.

Sam

Sent from my Verizon 4G LTE smartphone


 Original message 
From: Scott Rohling 
Date: 11/11/16 10:15 (GMT-07:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: zLinux backup solutions

I'm talking about initiating the flashcopy  ...  not mirroring solutions...


CSM let's you initiate flashcopy with consistency groups.z/VM can only
do serial FLASHCOPY commands...

Scott Rohling

On Fri, Nov 11, 2016 at 8:48 AM, Cohen, Sam  wrote:

> Scott,
>
> You don't need Copy Services Manager, you just need a storage subsystem
> capable and enabled for Global Mirror, which is independent and outside of
> any operating system.  z/VM disks can be part of a consistency group, just
> as VSE, z/OS, Linux or TPF disks can.
>
> Sam
>
> Sent from my Verizon 4G LTE smartphone
>
>
>  Original message 
> From: Scott Rohling 
> Date: 11/11/16 08:20 (GMT-07:00)
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: zLinux backup solutions
>
> While z/VM can't use consistency groups -- z/OS and zLinux can with CSM
> (Copy Services Manager)  I'm currently involved in a project where
> we have this running on a zLinux guest to be able to flash with consistency
> groups.
>
> Scott Rohling
>
> On Fri, Nov 11, 2016 at 6:35 AM, Alan Altmark 
> wrote:
>
> > On Thursday, 11/10/2016 at 09:12 GMT, "Ponte, Douglas C. (JMD)"
> >  wrote:
> > > Fullpack volume backups  can be run daily, weekly and monthly,
> using
> > JCL with automation tools
> > > (existing on z/OS already, e.g. BMC Control-M or Tivoli Automation).
> > This should be done with all
> > > z/VM and zLinux volumes.
> > >
> > > In the full volume backup cases, stopping/shutting down is not always
> > necessary, albeit it may be
> > > good practice to at least quiesce when it comes to DB?s and heavy use
> > servers. (e.g. DB2, Oracle,
> > > etc)
> >
> > WARNING:  To do this reliably, you need software that is capable of
> > establishing an I/O consistency group.  If you want to FLASHCOPY the
> > volumes and sequentially backup the volume copies, that's ok, but do NOT
> > just sequentially copy the live volumes of a running z/VM system.  (If
> you
> > wouldn't do it to a running z/OS system, don't do it to any other
> system.)
> >  This process is intimately tied to your DR strategy, too, so get it
> > right.
> >
> > If you have databases, use the backup software for the database.  If
> > you're using hardware replication, be sure that it's supported by the
> > database vendor.
> >
> > Some people take a too-casual approach to backups and DR.  I too often
> > hear "Don't worry, I'm doing it from z/OS." as though z/OS has magical
> > powers over z/VM and Linux.  Don't fall into that trap.  That way there
> be
> > dragons.
> >
> > Alan Altmark
> >
> > Senior Managing z/VM and Linux Consultant
> > Lab Services System z Delivery Practice
> > IBM Systems & Technology Group
> > ibm.com/systems/services/labservices
> > office: 607.429.3323
> > mobile; 607.321.7556
> > alan_altm...@us.ibm.com
> > IBM Endicott
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > --
> > For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
> >
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: zLinux backup solutions

[Cohen, Sam]

Scott,

You don't need Copy Services Manager, you just need a storage subsystem capable 
and enabled for Global Mirror, which is independent and outside of any 
operating system.  z/VM disks can be part of a consistency group, just as VSE, 
z/OS, Linux or TPF disks can.

Sam

Sent from my Verizon 4G LTE smartphone


 Original message 
From: Scott Rohling 
Date: 11/11/16 08:20 (GMT-07:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: zLinux backup solutions

While z/VM can't use consistency groups -- z/OS and zLinux can with CSM
(Copy Services Manager)  I'm currently involved in a project where
we have this running on a zLinux guest to be able to flash with consistency
groups.

Scott Rohling

On Fri, Nov 11, 2016 at 6:35 AM, Alan Altmark 
wrote:

> On Thursday, 11/10/2016 at 09:12 GMT, "Ponte, Douglas C. (JMD)"
>  wrote:
> > Fullpack volume backups  can be run daily, weekly and monthly, using
> JCL with automation tools
> > (existing on z/OS already, e.g. BMC Control-M or Tivoli Automation).
> This should be done with all
> > z/VM and zLinux volumes.
> >
> > In the full volume backup cases, stopping/shutting down is not always
> necessary, albeit it may be
> > good practice to at least quiesce when it comes to DB?s and heavy use
> servers. (e.g. DB2, Oracle,
> > etc)
>
> WARNING:  To do this reliably, you need software that is capable of
> establishing an I/O consistency group.  If you want to FLASHCOPY the
> volumes and sequentially backup the volume copies, that's ok, but do NOT
> just sequentially copy the live volumes of a running z/VM system.  (If you
> wouldn't do it to a running z/OS system, don't do it to any other system.)
>  This process is intimately tied to your DR strategy, too, so get it
> right.
>
> If you have databases, use the backup software for the database.  If
> you're using hardware replication, be sure that it's supported by the
> database vendor.
>
> Some people take a too-casual approach to backups and DR.  I too often
> hear "Don't worry, I'm doing it from z/OS." as though z/OS has magical
> powers over z/VM and Linux.  Don't fall into that trap.  That way there be
> dragons.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: WWN change

[Cohen, Sam]

Chris,

If you're not replacing the target SAN disks, then there are no changes to z/VM 
or a Linux connections (as long as the IOADDRS are unchanged).  Your SAN fabric 
has to change for the new WWPNS on the z.

Sam

Sent from my Verizon 4G LTE smartphone


 Original message 
From: Christer Solskogen 
Date: 10/27/16 07:23 (GMT-07:00)
To: LINUX-390@VM.MARIST.EDU
Subject: WWN change

Hi!

We are in the process of moving our z/VMs and all of the linux systems over
to z13 from a zEC12.
And just to make it even more complicated we are moving. That also means
that the disk system is also moved (DS8870). The disk system is somehow in
sync with the old system, I'm no storage guy so I'm not sure how this work.
I only know that it works ;-)

But after the move the wwn is going to change (I guess it would have
changed anyways?) - Is there an easy way or do I have to add the luns
manually for every server once the linux system is running on z13?

Linux system disks are on 3390, but data is on SAN / zfcp.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: HMC show total re·sources?

[Cohen, Sam]

If you go into the Support Element from the HMC, you'll see "Storage 
Information" for that particular processor

Thanks,

Sam Cohen
sam.co...@lrs.com
(217) 793-3800 x1227 (office)
(602) 327-2134 (cell)

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Andrew 
Lemay
Sent: Monday, August 8, 2016 8:58 AM
To: LINUX-390@VM.MARIST.EDU
Subject: HMC show total re·sources?

Hey there,

I have been unable to find this online so I figured Id ask .
Is there a way to see how mach ram a z12 has from the hmc sysprog user?

I know you can see cpus from the "Monitors Dashboard"


Monitor
  --Environmental Efficiency Statistics
  --Monitors Dashboard

I know how many books are installed. But I would also like to see a list of 
everything installed as well. Does such thing exist?

Thanks


--
~~Andrew Lemay

mobile: +1 978 886 4740
gvoice:  +1 978 558 0413

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

Re: SWAPGEN + RHEL 7

[Cohen, Sam]

Marcy,

I use the Format/Reserve to use the DIAG driver, which I've found to be more 
efficient than the FBA driver.

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.




-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Monday, May 16, 2016 1:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SWAPGEN + RHEL 7

I'm with you Sam :)
We don't even bother with the cms format reserve and just do this in 
/etc/init.d/boot.local

/sbin/mkswap /dev/disk/by-path/ccw-0.0.ff00-part1
/sbin/mkswap /dev/disk/by-path/ccw-0.0.ff01-part1
/sbin/mkswap /dev/disk/by-path/ccw-0.0.ff02-part1
/sbin/mkswap /dev/disk/by-path/ccw-0.0.ff03-part1
/sbin/swapon /dev/disk/by-path/ccw-0.0.ff00-part1 -p 4 /sbin/swapon 
/dev/disk/by-path/ccw-0.0.ff01-part1 -p 3 /sbin/swapon 
/dev/disk/by-path/ccw-0.0.ff02-part1 -p 2 /sbin/swapon 
/dev/disk/by-path/ccw-0.0.ff03-part1 -p 1

Runs really fast on vdisk ;)

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Cohen, Sam
Sent: Monday, May 16, 2016 11:08 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SWAPGEN + RHEL 7

Alan,

Personally, I suggest abandoning SWAPGEN and just formatting/reserving the 
MDISK via CMS, then doing a mkswap /dev/disk/by-path/ccw-0.0.0xxx-part1 in your 
boot.local (or equivalent).  This assumes that you are consistent in your 
assignment of the swap disk address.  Then you don't have to worry about 
keeping some external routine up to date with changes in swap handling within a 
Linux guest. 

Religious argumentsstart your engines!

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan 
Ackerman
Sent: Monday, May 16, 2016 11:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: SWAPGEN + RHEL 7

Does anyone have SWAPGEN working with RHEL 7?
 
We are having problem with SWAPGEN EXEC. 
 
If I do not use the FBAPART option on SWAPGEN, I get these errors at the end of 
every boot:
 
08:38:52 [   24.130992] attempt to access beyond end of device
[   24.131000] dasdc1: rw=0, want=415944, limit=415941 
[   24.146104] attempt to access beyond end of device 
[   24.146108] dasdd1: rw=0, want=831896, limit=831890
 
If I do use the FBAPART option, I get these errors during every boot:
 
14:54:44 EXEC SWAPGEN 0101 ( FBAPART REUSE DEBUG  
14:54:44 SWPSWA0012I DIAG swap disk defined at virtual address 0101 with  
dasd=0.0.0100 rd.dasd=0.0.0101 rd.dasd=0.0.0102 cio_ignore=all,!0.0.0009 rd.znet
=qeth,0.0.aa00,0.0.aa01,0.0.aa02,layer2=1,portno=0 L  
[1.046050] dasdconf.sh Warning: Could not find 0.0.0101 in sysfs  
[1.046161] dasdconf.sh Warning: Could not find 0.0.0101 in sysfs   
[1.046735] dasdconf.sh Warning: Could not find 0.0.0101 in sysfs  
[1.071256] dasd-fba 0.0.0101: New FBA DASD 9336/10 (CU 6310/80) with 409 MB
and 512 B/blk 
[1.103730] dasdconf.sh Warning: 0.0.0101 is already online, not configuring
[5.881606] dasdconf.sh Warning: 0.0.0101 is already online, not configuring
["[32m  OK  "[0m] Found device /dev/disk/by-path/ccw-0.0.0101-part1.  
 Activating swap /dev/disk/by-path/ccw-0.0.0101-part1...  
["[1;31mFAILED"[0m] Failed to activate swap /dev/disk/by-path/ccw-0.0.0101-part1
. 
See 'systemctl status "dev-disk-by\\x2d0.0101\\x2dpart1.swap"' for details.
 
RHEL 7.2 on z/VM 6.3.
 
Filename Filetype Fm Format LreclRecords Blocks   Date   Time 
SWAPGEN  HELPCMS  B1 V 76279  3 2013-12-23 10:45:36
SWAPGEN  EXEC B2 V 72599  7 2013-12-17 21:52:11


--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions, send email 

Re: SWAPGEN + RHEL 7

[Cohen, Sam]

Alan,

Personally, I suggest abandoning SWAPGEN and just formatting/reserving the 
MDISK via CMS, then doing a mkswap /dev/disk/by-path/ccw-0.0.0xxx-part1 in your 
boot.local (or equivalent).  This assumes that you are consistent in your 
assignment of the swap disk address.  Then you don't have to worry about 
keeping some external routine up to date with changes in swap handling within a 
Linux guest. 

Religious argumentsstart your engines!

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan 
Ackerman
Sent: Monday, May 16, 2016 11:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: SWAPGEN + RHEL 7

Does anyone have SWAPGEN working with RHEL 7?
 
We are having problem with SWAPGEN EXEC. 
 
If I do not use the FBAPART option on SWAPGEN, I get these errors at the end of 
every boot:
 
08:38:52 [   24.130992] attempt to access beyond end of device
[   24.131000] dasdc1: rw=0, want=415944, limit=415941 
[   24.146104] attempt to access beyond end of device 
[   24.146108] dasdd1: rw=0, want=831896, limit=831890
 
If I do use the FBAPART option, I get these errors during every boot:
 
14:54:44 EXEC SWAPGEN 0101 ( FBAPART REUSE DEBUG  
14:54:44 SWPSWA0012I DIAG swap disk defined at virtual address 0101 with  
dasd=0.0.0100 rd.dasd=0.0.0101 rd.dasd=0.0.0102 cio_ignore=all,!0.0.0009 rd.znet
=qeth,0.0.aa00,0.0.aa01,0.0.aa02,layer2=1,portno=0 L  
[1.046050] dasdconf.sh Warning: Could not find 0.0.0101 in sysfs  
[1.046161] dasdconf.sh Warning: Could not find 0.0.0101 in sysfs   
[1.046735] dasdconf.sh Warning: Could not find 0.0.0101 in sysfs  
[1.071256] dasd-fba 0.0.0101: New FBA DASD 9336/10 (CU 6310/80) with 409 MB
and 512 B/blk 
[1.103730] dasdconf.sh Warning: 0.0.0101 is already online, not configuring
[5.881606] dasdconf.sh Warning: 0.0.0101 is already online, not configuring
["[32m  OK  "[0m] Found device /dev/disk/by-path/ccw-0.0.0101-part1.  
 Activating swap /dev/disk/by-path/ccw-0.0.0101-part1...  
["[1;31mFAILED"[0m] Failed to activate swap /dev/disk/by-path/ccw-0.0.0101-part1
. 
See 'systemctl status "dev-disk-by\\x2d0.0101\\x2dpart1.swap"' for details.
 
RHEL 7.2 on z/VM 6.3.
 
Filename Filetype Fm Format LreclRecords Blocks   Date   Time 
SWAPGEN  HELPCMS  B1 V 76279  3 2013-12-23 10:45:36
SWAPGEN  EXEC B2 V 72599  7 2013-12-17 21:52:11


--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Security for z/VM

[Cohen, Sam]

Rick,

You're asking for a religious argument here.  Don't forget about RACF and its 
interface with DIRMAINT.  Meanwhile,  I suggest that the better question is:  
what does "securing" mean to your company and what are the security policies 
such that you need an external security manager (as opposed to the mechanisms 
that exist within z/VM)? 

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Beard, 
Rick
Sent: Wednesday, May 04, 2016 4:34 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Security for z/VM

I would like to know if anyone has any preferences on using either CA:VMSECURE 
or CA:ACF2 for securing z/VM systems?
Is one more secure than the other?
Is one easier to use and configure over the other?


Thanks,

Rick Beard
Infrastructure Management Senior Analyst ITO Global Service Operations & 
Engineering www.atos.net
[atos_logotype]



--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: MTU size

[Cohen, Sam]

Chris,

If you look in the hardware documentation for the Open Systems Adapter (OSA), 
it has a "normal" MTU of 1492, so your Linux is matching the hardware settings. 
 The OSA does support jumbo frames (8992) if your network is configured to use 
them.

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Christer 
Solskogen
Sent: Friday, January 29, 2016 1:56 AM
To: LINUX-390@VM.MARIST.EDU
Subject: MTU size

Hi!

On all of my x86_64 Linux boxes the default MTU is 1500. But with SuSE (both 11 
and 12) on s390 they seems to be 1492. How come?

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

Re: zFCP and NPIV - limit of 32

[Cohen, Sam]

Gregory,

It is, of course, more art than science.  In my case, I've done the following:

My SYSTEM CONFIG file has EQID FCP6000 for addresses 6000 and 6100, EQID 
FCP6001 for addresses 6001 and 6101, etc.  The SAN team has zoned the virtual 
WWPNs for 6000 and 6100 in both LPARs to the same target WWPN/LUN, as well as 
having zoned the virtual WWPNs for 6001 and 6101 in both LPARs to the same 
target WWPN/LUN (but a different target than that of the 6000/6100 pair).  For 
my first Linux image, I include in the directory entry:

COMMAND ATTACH EQID FCP6000 TO * AS 6000
COMMAND ATTACH EQID FCP6000 TO * AS 6100

My second Linux image uses EQID FCP6001 against 6001 and 6101 in both LPARs and 
the directory entry includes:

COMMAND ATTACH EQID FCP6001 TO * AS 6000
COMMAND ATTACH EQID FCP6001 TO * AS 6100

It's a bit manually intensive as I have to keep track of which pair of 
addresses belongs to which guest, and the multipath.conf has to be modified for 
the correct target SCSI disk (since I use the multipath daemon to balance the 
traffic).  If I had a SAN Virtualization Controller (SVC), I wouldn't need to 
modify the multipath.conf, since I would present the same WWPN/LUN target to 
each guest and the SVC would direct the I/O to the correct physical target.

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz 
Powiedziuk
Sent: Wednesday, August 19, 2015 7:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: zFCP and NPIV - limit of 32

> On Aug 18, 2015, at 12:00 PM, Alan Altmark  wrote:
> 
> On Tuesday, 08/18/2015 at 08:50 EDT, Grzegorz Powiedziuk 
>  wrote:
> 
>> Got it! Thank you so much for spending time on explanation. That
> definitely
>> helps.
> 
> You're welcome.
> 
>> The bottom line is - I can ?over provision? (or kind of thin 
>> provision)
> fcp
>> channels as long as I keep below 32 attached paths per chpid and make
> sure that
>> I do EQIDs vertically only - separate EQID for every set of paths on 
>> two chpids  (one on each system).
> 
> That's what I would do.

I've been thinking about this and I am afraid that doing one EQID for all 
devices on one CHPID will not work for us. 
The point is to predict WWPNs which would be used if machine is being relocated 
so the storage team can add these to zone configuration beforehand. 

If the LGR process picks the first eligible device from the list with the same 
equid instead off the one with the same address then relocation with cause 
linux to lose paths. 
I've always was doing equids for every pair of fpc devices instead one eqid per 
chpid so I didn't even think about such situation before . That probably is not 
a best practice but what else can I do?
Is  doing a separate equids for every virtual machine on specific fcp devices a 
bad thing? 
For example 

EQID "Linux1z" on
6000 on system A
6000 on system B  

EQID "Linux1y" on
6100 on system A
6100 on system B

Two EQID to avoid possible reverse of order which will confuse linux. I know it 
would eventually recover but there would be a delay before it figures out that 
on a specific channel it sees a different set of target (storage) wwpns after 
the relocation. 


Gregory 

> 
> Then I would open an RFE to ask for CP to handle this automatically.  
> It may be as simple as CP noting the chpid distribution on the source 
> side and attempting to match that on the target.  I.e. If guest #1 was 
> using a PURPLE FCP on chpid X and guest #2 was using a PURPLE FCP on 
> chpid Y, then CP could map them to PURPLE FCP subchannels on chpids X' 
> and Y' on the target (if available).  Further, remember the mapping 
> and continue to use it.  That way the guests will end up with the same 
> subchannels-per-chpid distribution on the target.
> 
> This technique also applies to OSA and HiperSockets, where separation 
> is enforced (only) at the chpid boundary and you have explicitly 
> chosen devices based on their chpid association.  You don't want 
> guests that were communicating on the same chpid on system A to 
> suddenly be on separate chpids on System B.
> 
> Alan Altmark
> 
> Senior Managing z/VM and Linux Consultant Lab Services System z 
> Delivery Practice IBM Systems & Technology Group 
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit 
> http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.e

Re: Registration Error

[Cohen, Sam]

Mark,

Is this for SLES12?  I had the same issue until SUSE sent me an updated 
read_values executable.  Contact me off-line if you'd like a copy

Sam Cohen
LRS
sam.co...@lrs.com

Sent from my Verizon Wireless 4G LTE smartphone


 Original message 
From: Mark Pace 
Date: 04/24/2015 14:30 (GMT-07:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Registration Error

I just posted this on the SuSE forums also,  but to see if anyone here has
had this problem before and knows how to fix it.

Trying to register a new system for online updates. When I go through Yast
and enter my code I get an error.
Error
Registration server error.
Retry registration later.
Details: Validation failed: Uuid should be formatted as UUID

Well that doesn't make a lot of sense.
So I went and requested a new registration code for Linux Enterprise Server
on System z.
I receive an email saying that my code had been updated. So I copy and
paste the new registration code into yast and now I get a new error.

Error
Registration Failed
Details: Invalid registration code

Any ideas what I do now?

--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: having commands run after complete boot process

[Cohen, Sam]

Boot.local

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Levy, Alan
Sent: Tuesday, March 10, 2015 9:14 AM
To: LINUX-390@VM.MARIST.EDU
Subject: having commands run after complete boot process

I'm having a mind block today.

I have a script (which does an NFS mount) and rather than put it into 
/etc/init.d and rc3.d, I'd like to execute this script after everything else 
has finished executing. I remember doing this before in some kind of boot. 
file but I can't remember what it was.

Thanks.





--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: relocation put read only FCP

[Cohen, Sam]

Also, be sure your EQID for the FCP subchannels to the specific LUN are the 
same in both LPARs.

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz 
Powiedziuk
Sent: Wednesday, January 21, 2015 9:19 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: relocation put read only FCP

What Robert said might be correct. The other thing I would check if that won't 
help is:
 - hosts definition on the XIV and Zonning in SAN switches When you relocate 
virtual machine from one LPAR to another you are also switching FCP channels 
under the hood for the relocated linux guest. Which means your linux guest 
after the reloctation will talk to the XIV from different FCP channels with  
different WWPNs.  XIV must have these new WWPN in the host deffinition for this 
guest (LUN Masking). Also zone definitions in SAN Switches have to contain 
"new" WWPNs.

Regards
Gregory Powiedziuk


2015-01-21 9:43 GMT-05:00 Victor Echavarry Diaz :

> This is a multi-part MIME message.
>
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
>
> We are doing relocation testing under z/VM 6.3. We test a SLES 11SP2  
> and o= racle 10.2. We bring up on both z/vm LPARS in standalone way 
> and works fine=  on both LPARS. When we begin relocation from any of 
> the LPAR, immediately = the SAN file system goes in read only mode. 
> I'm attaching part of the log a= t the moment of failure. The SAN is a 
> XIV We are running z/VM 6.3.
>
> Thanks for your help
>
> Victor Echavarry
> System Programmer, EVERTEC LLC
>
>
>
>
>
> WARNING: This email and any files transmitted with it are confidential 
> and intended solely for the use of the individual or entity to whom 
> they are addressed. If you have received this email in error please 
> delete it immedi= ately.
> Please note that any views or opinions presented in this email are 
> solely t= hose of the author and do not necessarily represent those of 
> EVERTEC, Inc. or its affiliates. Finally, the integrity and security 
> of this message cannot be guaranteed on the Internet, and as such 
> EVERTEC, Inc. and its affiliates ac= cept no liability for any damage 
> caused by any virus transmitted by this email.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit 
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

Re: cio_ignore vs Linux in System z

[Cohen, Sam]

Mike,

This is a RedHat "feature"; it isn't an issue with SuSE.  It is an 
implementation choice by the distributor.

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mike 
Walter
Sent: Monday, January 12, 2015 10:09 AM
To: LINUX-390@VM.MARIST.EDU
Subject: cio_ignore vs Linux in System z

The cio_ignore table within Linux (at least in RHEL6.5) is used to restrict 
access devices, both real and virtual.  Being new the Linux on System z, this 
has become an occasional stumbling block for our Linux admins; when we z/VM 
sysprogs attach a new virtual or real device and the guest cannot see it 
immediately.

I'm told that on distributed x86 (at least x86 here), the servers can see all 
the hardware.  Is there a good reason that on Linux on System z the default is 
to prevent access to all devices unless they are manually removed from the  
cio_ignore table?   I understand that an authorized user could attach a wrong 
device to a zLinux guest, so let's accept that risk as having been minimized.  
Are there  other reasons to prevent every guest from accessing whatever devices 
are given to it?

Thanks!

Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not necessarily those of my 
employer.

FWIW, I subscribe in digest mode - so my responses may be slightly delayed.




--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Where to put Z/VM tools and utilities

[Cohen, Sam]

Keith,

As you can tell, it's more art than science.  My tendency matches Jay's; I 
create a NOLOG user called LCLTOOLS and place all my tools on its 191 disk.  I 
then create a nickname called TOOLS and use VMLINK TOOLS to access that disk.  
To create a nickname file, see the NAMES  command (with VMLINK option) help 
screens.

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of kwg
Sent: Monday, January 12, 2015 2:54 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Where to put Z/VM tools and utilities

I have a small z/vm system which is used to run linux and z/os test systems (I 
work for an ISV). My z/vm knowledge is mainly limited to what I have picked up 
from the z/linux Redbooks and the "Getting Started" guide.

I now want to install some tools from the VM downloads web pages. Is there a 
standard or commonly used convention for where such tools should be stored? I 
found some sample instructions for installing pipeddr where the code was 
installed on the MAINT 191 for instance. I would not expect that to be a 
suitable location.

Also, does IBM provide a list of various MAINT minidisks and their functions ?

Keith Gooding

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Problem to test relocating a Linux image to another z/VM - Device 0592

[Cohen, Sam]

Ray,

You should detach the CMS-oriented disks from your Linux guest before booting 
the Linux kernel.  Your kernel should only have disks attached that Linux will 
actually use.  Having disks attached/linked that are dedicated to one 
particular z/VM image will prevent relocation.

Thanks,


Sam Cohen
Levi, Ray & Shoup, Inc.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Chu, 
Raymond
Sent: Friday, December 19, 2014 11:36 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Problem to test relocating a Linux image to another z/VM - Device 
0592

Hi Alan and all,

The EQID on VSWITCH was fixed. When I ran the following:

vmreloc test Lnx004 zvm2

HCPRLH1940E LNX004 is not relocatable for the following reason (s): 
   
HCPRLI1996I LNX004: Virtual machine device 0592 is a link to a local minidisk   
 

Below is the definition for LNXDFLT profile for Linux images and TCPMAINT   
 

IDENTITY TCPMAINT PASSWORD   32M   64M ABCG 
 INCLUDE TCPCMSU
 BUILD ON ZVM1 USING SUBCONFIG TCPMNT-1 
 BUILD ON ZVM2 USING SUBCONFIG TCPMNT-2 
 BUILD ON ZVM3 USING SUBCONFIG TCPMNT-3 
 BUILD ON ZVM4 USING SUBCONFIG TCPMNT-4  

SUBCONFIG TCPMNT-1  
 LINK 6VMTCP30 491 491 RR   
 LINK 6VMTCP30 492 492 RR   
 MDISK 591 3390 8558 122 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN   
 MDISK 592 3390 8680 140 XX12B4 MR ALL  WTCPMAIN MTCPMAIN   
 MDISK 198 3390 8820 009 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN   
 MDISK 191 3390 8829 007 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN   

SUBCONFIG TCPMNT-2  
 LINK 6VMTCP30 491 491 RR   
LINK 6VMTCP30 492 492 RR   
 MDISK 591 3390 8558 122 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN   
 MDISK 592 3390 8680 140 XX1395 MR ALL  WTCPMAIN MTCPMAIN   
 MDISK 198 3390 8820 009 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN   
 MDISK 191 3390 8829 007 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN  

SUBCONFIG TCPMNT-3  
LINK 6VMTCP30 491 491 RR  
 LINK 6VMTCP30 492 492 RR  
 MDISK 591 3390 8558 122 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN  
 MDISK 592 3390 8680 140 XX1A06 MR ALL  WTCPMAIN MTCPMAIN  
 MDISK 198 3390 8820 009 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN  MDISK 191 3390 
8829 007 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN  
   
SUBCONFIG TCPMNT-4 
 LINK 6VMTCP30 491 491 RR  
 LINK 6VMTCP30 492 492 RR  
 MDISK 591 3390 8558 122 XX139F MR RTCPMAIN WTCPMAIN MTCPMAIN  
 MDISK 592 3390 8680 140 XX139F MR ALL  WTCPMAIN MTCPMAIN  
 MDISK 198 3390 8820 009 XX139F MR RTCPMAIN WTCPMAIN MTCPMAIN  MDISK 191 3390 
8829 007 VX139F MR RTCPMAIN WTCPMAIN MTCPMAIN  
*   

PROFILE LNXDFLT 
  COMMAND SET VSWITCH PASSWORD GRANT &USERID
  COMMAND DEFINE NIC 600 TYPE QDIO  
  COMMAND COUPLE 600 TO SYSTEM VSWPSEG1 
 *  
  COMMAND SET VSWITCH VSWPSEG2 GRANT &USERID
  COMMAND DEFINE NIC 700 TYPE QDIO  
  COMMAND COUPLE 700 TO SYSTEM VSWPSEG2 
 *  
  CPU 00 BASE   
  CPU 1 
  IPL CMS   
  MACHINE ESA 10
  IUCV ALLOW
  OPTION CHPIDV ONE 
  CONSOLE 009 3215 T
  SPOOL 000C 2540 READER *  
  SPOOL 000D 2540 PUNCH A