Re: relocation put read only FCP

2015-01-21 Thread 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 vechava...@evertecinc.com:

 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: Loading VMCP in single or emergency boot modes

2015-01-21 Thread Mark Post
 On 1/20/2015 at 05:22 PM, Vitale, Joseph joseph.vit...@bnymellon.com 
 wrote:

 Thanks for your response.  Yes, running RedHat 6.5.  Trailing a CA Linux 
 Connector product which uses VMCP to obtain guest  zVM Node.
 
 That information was not available until run level  '3'.  Product reported 
 back NULLS  until multi user mode.

Open up a bug report with CA.  There's no reason they should be using vmcp to 
get that information.  That's all in /proc/sysinfo which is available in all 
runlevels.


Mark Post

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


Re: Interrupting Linux under z/VM session

2015-01-21 Thread Hodge, Robert L
If you must do edits using the 3270 console, then learn to use ed or sed.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Beesley, 
Paul
Sent: Wednesday, January 21, 2015 6:46 AM
To: LINUX-390@VM.MARIST.EDU
Subject: EXTERNAL: Re: Interrupting Linux under z/VM session

Bingo! Thanks very much
I was entering ^c (^ is the shift 6 on the UK keyboard) When I entered ¬c (¬ is 
shift + key to the left of 1), and then :q!, I exited vi

Thank you so much

Regards and thanks
Paul



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Linker 
Harley - hlinke
Sent: Wednesday, January 21, 2015 1:27 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session

Paul,

I logged onto a 3270 console for a SLES 12 system and invoked the vi editor.  I 
was able to terminate the vi session by entering
   ¬c   (shift 6 in the Bluezone 3270 emulator)
   :q

I then tied the same test on a SLES 11 SP3 system and the same commands 
terminated the vi session.

I noticed that after I entered '¬c' that vi issued lines
   [24;1HType  :quitEnter  to exit Vim [24;63H[24;77H [24;63H1,1
 All [1;1H

I then entered ':q' to terminate the vi session as I didn't make any changes to 
the file.

I am running z/VM 6.3 but I doubt that the version of z/VM makes a difference.


Harley

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Beesley, 
Paul
Sent: Wednesday, January 21, 2015 7:10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session

escape followed by :q! doesn't work. I can't find anything that does. 
Obviously vi is unique (in many ways ...) I don't think you can IPL CMS if 
you've already booted z/Linux.

I may have found someone who has SSH access and am waiting for them to try and 
kill my vi process.
But it would be useful to know how to get out of this via z/VM for future 
occasions!

Regards and thanks
Paul



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of John 
McKown
Sent: Wednesday, January 21, 2015 12:56 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session

On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

 On Wed, 21 Jan 2015 12:06:51 +
 Beesley, Paul paul.bees...@atos.net wrote:

  Thanks for the tip, I'll try that.
  Unfortunately it doesn't get me out of my vi session. I think I'm 
  stuck there forever

 you might want to try

 ^z
 killall vi
 fg

 Berthold


​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file I 
was editing, displaying a ^Z.​ I can't duplicate the OP's environment, but I 
wonder why he can't just do the normal: escape followed by :q! to exit vi.

Sorry for my ignorance of Linux on z under z/VM, but isn't there some way to 
use SMSG to send commands to z/Linux? I.e. to send the killall vi command from 
a CMS logon?


--
​
While a transcendent vocabulary is laudable, one must be eternally careful so 
that the calculated objective of communication does not become ensconced in 
obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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/ Atos, 
Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names 
used by the Atos group. The following trading entities are registered in 
England and Wales: Atos IT Services UK Limited (registered number 01245534), 
Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited 
(registered number 08514184) and Canopy The Open Cloud Company Limited 
(registration number 08011902). The registered office for each is at 4 Triton 
Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for 
the addressee, and may contain confidential or privileged information. If you 
receive this e-mail in error, you are not authorised to copy, disclose, use or 
retain it. Please notify the sender immediately and delete this email from your 
systems. As emails may be intercepted, amended or lost, they are not secure. 
Atos therefore can accept no liability for any errors or their content. 
Although Atos endeavours to maintain a virus-free network, we do not warrant 
that this transmission is virus-free and can accept no liability for any 
damages resulting from any virus transmitted. The risks are deemed to be 
accepted by everyone who communicates with Atos by email.

Re: relocation put read only FCP

2015-01-21 Thread Grzegorz Powiedziuk
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 vechava...@evertecinc.com:

 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: Loading VMCP in single or emergency boot modes

2015-01-21 Thread Vitale, Joseph
Thanks very much.

Joe

Joseph Vitale
Technology Services Group
Mainframe Operating Systems

Pershing Plaza
95 Christopher Columbus Drive
Floor 14   
Jersey City,  N.J.  07302
Work  201-395-1509
Cell917-903-0102


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Wednesday, January 21, 2015 10:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Loading VMCP in single or emergency boot modes

 On 1/20/2015 at 05:22 PM, Vitale, Joseph joseph.vit...@bnymellon.com 
 wrote:

 Thanks for your response.  Yes, running RedHat 6.5.  Trailing a CA 
 Linux Connector product which uses VMCP to obtain guest  zVM Node.
 
 That information was not available until run level  '3'.  Product 
 reported back NULLS  until multi user mode.

Open up a bug report with CA.  There's no reason they should be using vmcp to 
get that information.  That's all in /proc/sysinfo which is available in all 
runlevels.


Mark Post

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

The information contained in this e-mail, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities.

--
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: Iaas - SCO vs IBM Wave vs xCat vs zPro

2015-01-21 Thread Kurt Acker
I'm not going to try an answer all the questions, however hopefully I can
put some context into how SCO (or IBM Cloud Orchestrator) and WAVE
complement each other or how they can be used to serve independent
purposes.

WAVE does a lot more then just provisioning.
If you have SCO, you would most likely use that for provisioning over
WAVE.
- With the WAVE hooks in your golden Linux images, clones will be
visible and accessible from WAVE.
- Simplified z/VM GUI view of even your virtual networks helps ease system
admin requirements and I like projects too.
- Projects create a great way to host and present IaaS to lines of
businesses.
- Wave also presents performance dashboards.  It is limited to z/VM with
Linux.

SCO really completes all the cloud requirements, and is not limited to
z/VM with Linux.
- Beyond the self service portal, it includes virtual machine life cycle
management, patch management, charge back etc.

Here's a SCO video that includes use of endpoint patch management for a
deployed guest:
https://www.youtube.com/watch?v=D18gEZcfgTU

Hopefully this is helpful.
Thanks and Best Regards,

Kurt Acker
IBM Smarter Planet, Smarter Data Centers
Virtualization and Enterprise System Management Technologies

--
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: Iaas - SCO vs IBM Wave vs xCat vs zPro

2015-01-21 Thread Mark Post
I find it amazing that anyone at IBM came up with a product name with the 
initials SCO.  I can't decide if they were being snarky or oblivious.


Mark Post

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


Re: Iaas - SCO vs IBM Wave vs xCat vs zPro

2015-01-21 Thread Cameron Seay
I am teaching several nainframe classes this term and a question came up:
does FICON proper provide firewall services or is that handled by RACF and
the external firewall of the network where the mainframe lives?
On Jan 21, 2015 10:08 PM, Mark Post mp...@suse.com wrote:

 I find it amazing that anyone at IBM came up with a product name with the
 initials SCO.  I can't decide if they were being snarky or oblivious.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://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/


Interrupting Linux under z/VM session

2015-01-21 Thread Beesley, Paul
Hi

We are running SLES10 under z/VM.
At the weekend, I logged onto the Linux guest via a z/VM 3270 session, and made 
the mistake of entering a PING command with no count parameter so it just 
PINGed forever.
I have no SSH access so was unable to logon anywhere else to kill the process. 
Eventually I just did a #CP LOGOFF and re-booted the guest as nobody else was 
logged on, but this is obviously a drastic solution.

Today I have managed to get into vi which obviously doesn’t work on a 3270 
screen. I can no find no way out of it. If I do #CP DISC and log back in again 
it’s still in vi.
There must be a way to interrupt a Linux command (like Ctrl-C on a putty 
session) but I can’t find it.

Any offers?
Thanks
Paul





Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading 
names used by the Atos group. The following trading entities are registered in 
England and Wales: Atos IT Services UK Limited (registered number 01245534), 
Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited 
(registered number 08514184) and Canopy The Open Cloud Company Limited 
(registration number 08011902). The registered office for each is at 4 Triton 
Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for 
the addressee, and may contain confidential or privileged information. If you 
receive this e-mail in error, you are not authorised to copy, disclose, use or 
retain it. Please notify the sender immediately and delete this email from your 
systems. As emails may be intercepted, amended or lost, they are not secure. 
Atos therefore can accept no liability for any errors or their content. 
Although Atos endeavours to maintain a virus-free network, we do not warrant 
that this transmission is virus-free and can accept no liability for any 
damages resulting from any virus transmitted. The risks are deemed to be 
accepted by everyone who communicates with Atos by email.


Re: Interrupting Linux under z/VM session

2015-01-21 Thread Michael MacIsaac
^c (Shift-6 c) usually sends a Ctrl-C signal, which kills the ping.

-Mike MacIsaac

On Wed, Jan 21, 2015 at 6:38 AM, Beesley, Paul paul.bees...@atos.net
wrote:

 Hi

 We are running SLES10 under z/VM.
 At the weekend, I logged onto the Linux guest via a z/VM 3270 session, and
 made the mistake of entering a PING command with no count parameter so it
 just PINGed forever.
 I have no SSH access so was unable to logon anywhere else to kill the
 process. Eventually I just did a #CP LOGOFF and re-booted the guest as
 nobody else was logged on, but this is obviously a drastic solution.

 Today I have managed to get into vi which obviously doesn’t work on a 3270
 screen. I can no find no way out of it. If I do #CP DISC and log back in
 again it’s still in vi.
 There must be a way to interrupt a Linux command (like Ctrl-C on a putty
 session) but I can’t find it.

 Any offers?
 Thanks
 Paul





 Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are
 trading names used by the Atos group. The following trading entities are
 registered in England and Wales: Atos IT Services UK Limited (registered
 number 01245534), Atos Consulting Limited (registered number 04312380),
 Atos Worldline UK Limited (registered number 08514184) and Canopy The Open
 Cloud Company Limited (registration number 08011902). The registered office
 for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No.
 for each is: GB232327983.

 This e-mail and the documents attached are confidential and intended
 solely for the addressee, and may contain confidential or privileged
 information. If you receive this e-mail in error, you are not authorised to
 copy, disclose, use or retain it. Please notify the sender immediately and
 delete this email from your systems. As emails may be intercepted, amended
 or lost, they are not secure. Atos therefore can accept no liability for
 any errors or their content. Although Atos endeavours to maintain a
 virus-free network, we do not warrant that this transmission is virus-free
 and can accept no liability for any damages resulting from any virus
 transmitted. The risks are deemed to be accepted by everyone who
 communicates with Atos by 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/


Re: Interrupting Linux under z/VM session

2015-01-21 Thread Beesley, Paul
Thanks for the tip, I'll try that.
Unfortunately it doesn't get me out of my vi session. I think I'm stuck there 
forever

^c


 ^22;1H^c
 ^23;63H ^23;77H
-- INSERT -- ^24;63H42,1 ^24;77HBot ^23;1H

Regards and thanks
Paul



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Michael 
MacIsaac
Sent: Wednesday, January 21, 2015 11:46 AM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session

^c (Shift-6 c) usually sends a Ctrl-C signal, which kills the ping.

-Mike MacIsaac

On Wed, Jan 21, 2015 at 6:38 AM, Beesley, Paul paul.bees...@atos.net
wrote:

 Hi

 We are running SLES10 under z/VM.
 At the weekend, I logged onto the Linux guest via a z/VM 3270 session,
 and made the mistake of entering a PING command with no count
 parameter so it just PINGed forever.
 I have no SSH access so was unable to logon anywhere else to kill the
 process. Eventually I just did a #CP LOGOFF and re-booted the guest as
 nobody else was logged on, but this is obviously a drastic solution.

 Today I have managed to get into vi which obviously doesn’t work on a
 3270 screen. I can no find no way out of it. If I do #CP DISC and log
 back in again it’s still in vi.
 There must be a way to interrupt a Linux command (like Ctrl-C on a
 putty
 session) but I can’t find it.

 Any offers?
 Thanks
 Paul





 Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are
 trading names used by the Atos group. The following trading entities
 are registered in England and Wales: Atos IT Services UK Limited
 (registered number 01245534), Atos Consulting Limited (registered
 number 04312380), Atos Worldline UK Limited (registered number
 08514184) and Canopy The Open Cloud Company Limited (registration
 number 08011902). The registered office for each is at 4 Triton Square, 
 Regent’s Place, London, NW1 3HG.The VAT No.
 for each is: GB232327983.

 This e-mail and the documents attached are confidential and intended
 solely for the addressee, and may contain confidential or privileged
 information. If you receive this e-mail in error, you are not
 authorised to copy, disclose, use or retain it. Please notify the
 sender immediately and delete this email from your systems. As emails
 may be intercepted, amended or lost, they are not secure. Atos
 therefore can accept no liability for any errors or their content.
 Although Atos endeavours to maintain a virus-free network, we do not
 warrant that this transmission is virus-free and can accept no
 liability for any damages resulting from any virus transmitted. The
 risks are deemed to be accepted by everyone who communicates with Atos by 
 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/
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading 
names used by the Atos group. The following trading entities are registered in 
England and Wales: Atos IT Services UK Limited (registered number 01245534), 
Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited 
(registered number 08514184) and Canopy The Open Cloud Company Limited 
(registration number 08011902). The registered office for each is at 4 Triton 
Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for 
the addressee, and may contain confidential or privileged information. If you 
receive this e-mail in error, you are not authorised to copy, disclose, use or 
retain it. Please notify the sender immediately and delete this email from your 
systems. As emails may be intercepted, amended or lost, they are not secure. 
Atos therefore can accept no liability for any errors or their content. 
Although Atos endeavours to maintain a virus-free network, we do not warrant 
that this transmission is virus-free and can accept no liability for any 
damages resulting from any virus transmitted. The risks are deemed to be 
accepted by everyone who communicates with Atos by email.


Re: Loading VMCP in single or emergency boot modes

2015-01-21 Thread Vitale, Joseph
Thanks for your response.  Yes, running RedHat 6.5.  Trailing a CA Linux 
Connector product which uses VMCP to obtain guest  zVM Node.

That information was not available until run level  '3'.  Product reported back 
NULLS  until multi user mode.

RedHat support of no use.  I found this which works except for Emergency run 
level:

You can specify additional modules to be loaded  by creating a new  
name.modules  file name  in  /etc/sysconfig/modules/ directory, 
where name is any descriptive name of your choice.

This does a modprobe for VMCP, file:  /etc/sysconfig/modules/ibm-vmcp

#!/bin/sh
# Load VMCP module
# Insure /dev/vmcp does NOT exist, if it does
#   then vmcp  previously loaded.
#  ! = NOT there
 if [ ! -c /dev/vmcp ] ; then
  exec /sbin/modprobe vmcp /dev/null 21
 fi

Joseph Vitale
Technology Services Group
Mainframe Operating Systems

Pershing Plaza
95 Christopher Columbus Drive
Floor 14   
Jersey City,  N.J.  07302
Work  201-395-1509
Cell917-903-0102

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Tuesday, January 20, 2015 4:49 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Loading VMCP in single or emergency boot modes

 On 1/20/2015 at 12:26 PM, Vitale, Joseph joseph.vit...@bnymellon.com 
 wrote:

 Hello,
 
 Kernel module VMCP is loaded via  /etc/rc.local   but only in Mult-User 
 mode, run level 3.  I would like to load it in earlier run levels, 
 say Single User mode.
 
 There should be a way to do that without a  script in  /etc/rc1.d.
 
 RedHat recommends I rebuild  initramfs-2.6.32-431.el6.s390x.img   via  
 /etc/dracut.conf.
 
 I would appreciate your advice on this.

Based on your description, this is prior to RHEL 7.  Please correct me if I'm 
wrong.

At the points in system startup you're talking about, the root file system has 
already been switched to the real device that holds it.  Putting something 
into your initrd would be a little superfluous since you would already have 
access to your real disk.

To me, just typing modprobe vmcp when needed is far less of a hassle than 
doing just about anything else like setting up an init script.  Or, if rc.local 
doesn't contain anything else, you could just execute _that_ manually.  (Or if 
it doesn't have anything else you don't mind executing in runlevels S, 1, or 2.)


Mark Post

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

The information contained in this e-mail, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities.

--
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: Interrupting Linux under z/VM session

2015-01-21 Thread John McKown
On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

 On Wed, 21 Jan 2015 12:06:51 +
 Beesley, Paul paul.bees...@atos.net wrote:

  Thanks for the tip, I'll try that.
  Unfortunately it doesn't get me out of my vi session. I think I'm
  stuck there forever

 you might want to try

 ^z
 killall vi
 fg

 Berthold


​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file
I was editing, displaying a ^Z.​ I can't duplicate the OP's environment,
but I wonder why he can't just do the normal: escape followed by :q! to
exit vi.

Sorry for my ignorance of Linux on z under z/VM, but isn't there some way
to use SMSG to send commands to z/Linux? I.e. to send the killall vi
command from a CMS logon?


-- 
​
While a transcendent vocabulary is laudable, one must be eternally careful
so that the calculated objective of communication does not become ensconced
in obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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: Interrupting Linux under z/VM session

2015-01-21 Thread Beesley, Paul
escape followed by :q! doesn't work. I can't find anything that does. 
Obviously vi is unique (in many ways ...)
I don't think you can IPL CMS if you've already booted z/Linux.

I may have found someone who has SSH access and am waiting for them to try and 
kill my vi process.
But it would be useful to know how to get out of this via z/VM for future 
occasions!

Regards and thanks
Paul



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of John 
McKown
Sent: Wednesday, January 21, 2015 12:56 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session

On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

 On Wed, 21 Jan 2015 12:06:51 +
 Beesley, Paul paul.bees...@atos.net wrote:

  Thanks for the tip, I'll try that.
  Unfortunately it doesn't get me out of my vi session. I think I'm
  stuck there forever

 you might want to try

 ^z
 killall vi
 fg

 Berthold


​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file I 
was editing, displaying a ^Z.​ I can't duplicate the OP's environment, but I 
wonder why he can't just do the normal: escape followed by :q! to exit vi.

Sorry for my ignorance of Linux on z under z/VM, but isn't there some way to 
use SMSG to send commands to z/Linux? I.e. to send the killall vi command from 
a CMS logon?


--
​
While a transcendent vocabulary is laudable, one must be eternally careful so 
that the calculated objective of communication does not become ensconced in 
obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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/
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading 
names used by the Atos group. The following trading entities are registered in 
England and Wales: Atos IT Services UK Limited (registered number 01245534), 
Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited 
(registered number 08514184) and Canopy The Open Cloud Company Limited 
(registration number 08011902). The registered office for each is at 4 Triton 
Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for 
the addressee, and may contain confidential or privileged information. If you 
receive this e-mail in error, you are not authorised to copy, disclose, use or 
retain it. Please notify the sender immediately and delete this email from your 
systems. As emails may be intercepted, amended or lost, they are not secure. 
Atos therefore can accept no liability for any errors or their content. 
Although Atos endeavours to maintain a virus-free network, we do not warrant 
that this transmission is virus-free and can accept no liability for any 
damages resulting from any virus transmitted. The risks are deemed to be 
accepted by everyone who communicates with Atos by email.


Re: Interrupting Linux under z/VM session

2015-01-21 Thread John McKown
On Wed, Jan 21, 2015 at 7:09 AM, Beesley, Paul paul.bees...@atos.net
wrote:

 escape followed by :q! doesn't work. I can't find anything that does.
 Obviously vi is unique (in many ways ...)
 I don't think you can IPL CMS if you've already booted z/Linux.


​I was thinking another user in CMS, not IPL'ing CMS in the same virtual
machine.​




 I may have found someone who has SSH access and am waiting for them to try
 and kill my vi process.
 But it would be useful to know how to get out of this via z/VM for future
 occasions!


​I agree, this is a very interesting phenomenon which must somehow have to
do with the 3270 session you're in. I really which that I had access to a
z/Linux system under z/VM to mess around with it. ​And it makes me wonder
why vi doesn't simply refuse to run in a 3270 environment. I guess it's
because the author never considered a terminal environment which would be
so completely different and hostile. Personally, I would possibly look at
creating a new vi shell wrapper which checks (how?) for the 3270
environment and refuses to invoke vi in that environment.




 Regards and thanks
 Paul


-- 
​
While a transcendent vocabulary is laudable, one must be eternally careful
so that the calculated objective of communication does not become ensconced
in obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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: Interrupting Linux under z/VM session

2015-01-21 Thread Linker Harley - hlinke
Paul,

I logged onto a 3270 console for a SLES 12 system and invoked the vi editor.  I 
was able to terminate the vi session by entering 
   ¬c   (shift 6 in the Bluezone 3270 emulator)
   :q

I then tied the same test on a SLES 11 SP3 system and the same commands 
terminated the vi session.  

I noticed that after I entered '¬c' that vi issued lines
   [24;1HType  :quitEnter  to exit Vim [24;63H[24;77H [24;63H1,1
 All [1;1H

I then entered ':q' to terminate the vi session as I didn't make any changes to 
the file.

I am running z/VM 6.3 but I doubt that the version of z/VM makes a difference.


Harley

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Beesley, 
Paul
Sent: Wednesday, January 21, 2015 7:10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session

escape followed by :q! doesn't work. I can't find anything that does. 
Obviously vi is unique (in many ways ...) I don't think you can IPL CMS if 
you've already booted z/Linux.

I may have found someone who has SSH access and am waiting for them to try and 
kill my vi process.
But it would be useful to know how to get out of this via z/VM for future 
occasions!

Regards and thanks
Paul



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of John 
McKown
Sent: Wednesday, January 21, 2015 12:56 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session

On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

 On Wed, 21 Jan 2015 12:06:51 +
 Beesley, Paul paul.bees...@atos.net wrote:

  Thanks for the tip, I'll try that.
  Unfortunately it doesn't get me out of my vi session. I think I'm 
  stuck there forever

 you might want to try

 ^z
 killall vi
 fg

 Berthold


​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file I 
was editing, displaying a ^Z.​ I can't duplicate the OP's environment, but I 
wonder why he can't just do the normal: escape followed by :q! to exit vi.

Sorry for my ignorance of Linux on z under z/VM, but isn't there some way to 
use SMSG to send commands to z/Linux? I.e. to send the killall vi command from 
a CMS logon?


--
​
While a transcendent vocabulary is laudable, one must be eternally careful so 
that the calculated objective of communication does not become ensconced in 
obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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/ Atos, 
Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names 
used by the Atos group. The following trading entities are registered in 
England and Wales: Atos IT Services UK Limited (registered number 01245534), 
Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited 
(registered number 08514184) and Canopy The Open Cloud Company Limited 
(registration number 08011902). The registered office for each is at 4 Triton 
Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for 
the addressee, and may contain confidential or privileged information. If you 
receive this e-mail in error, you are not authorised to copy, disclose, use or 
retain it. Please notify the sender immediately and delete this email from your 
systems. As emails may be intercepted, amended or lost, they are not secure. 
Atos therefore can accept no liability for any errors or their content. 
Although Atos endeavours to maintain a virus-free network, we do not warrant 
that this transmission is virus-free and can accept no liability for any 
damages resulting from any virus transmitted. The risks are deemed to be 
accepted by everyone who communicates with Atos by email.
***
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.

If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank You.



Re: relocation put read only FCP

2015-01-21 Thread Robert J Brenneman
Attachments don't make it through the listserve software, but I can guess
that what is happening to your system is that the relocation involves a
pause while the processor state is relocated to the new target system,
followed by an I/O recovery interrupt.

the FCP / SCSI / Multipath driver stack interprets this as an I/O error and
sets the file systems read only to preserve your data.

You can open up the timeout window that multipath uses to look for these
errors by making some settings as mentioned by Steffen on PG 30 here:
http://www.vm.ibm.com/education/lvc/LVC0924.pdf

and
http://www-01.ibm.com/support/knowledgecenter/SSB27U_6.3.0/com.ibm.zvm.v630.hcpa5/hcpa5313.htm
regarding the queue_if_no_path multipath option

On Wed, Jan 21, 2015 at 9:43 AM, Victor Echavarry Diaz 
vechava...@evertecinc.com wrote:

 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/




--
Jay Brenneman

--
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: Interrupting Linux under z/VM session

2015-01-21 Thread Berthold Gunreben
On Wed, 21 Jan 2015 12:06:51 +
Beesley, Paul paul.bees...@atos.net wrote:

 Thanks for the tip, I'll try that.
 Unfortunately it doesn't get me out of my vi session. I think I'm
 stuck there forever

you might want to try 

^z
killall vi
fg

Berthold

 
 ^c
 
 
  ^22;1H^c
  ^23;63H ^23;77H
 -- INSERT -- ^24;63H42,1 ^24;77HBot ^23;1H
 
 Regards and thanks
 Paul
 
 
 
 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of
 Michael MacIsaac Sent: Wednesday, January 21, 2015 11:46 AM
 To: LINUX-390@vm.marist.edu
 Subject: Re: Interrupting Linux under z/VM session
 
 ^c (Shift-6 c) usually sends a Ctrl-C signal, which kills the ping.
 
 -Mike MacIsaac
 
 On Wed, Jan 21, 2015 at 6:38 AM, Beesley, Paul paul.bees...@atos.net
 wrote:
 
  Hi
 
  We are running SLES10 under z/VM.
  At the weekend, I logged onto the Linux guest via a z/VM 3270
  session, and made the mistake of entering a PING command with no
  count parameter so it just PINGed forever.
  I have no SSH access so was unable to logon anywhere else to kill
  the process. Eventually I just did a #CP LOGOFF and re-booted the
  guest as nobody else was logged on, but this is obviously a drastic
  solution.
 
  Today I have managed to get into vi which obviously doesn’t work on
  a 3270 screen. I can no find no way out of it. If I do #CP DISC and
  log back in again it’s still in vi.
  There must be a way to interrupt a Linux command (like Ctrl-C on a
  putty
  session) but I can’t find it.
 
  Any offers?
  Thanks
  Paul

-- 
--
 Berthold Gunreben  Build Service Team
 http://www.suse.de/ Maxfeldstr. 5
 SUSE LINUX GmbHD-90409 Nuernberg, Germany
 GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton HRB 21284 (AG Nürnberg) 

--
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/


relocation put read only FCP

2015-01-21 Thread 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/
Jan 20 17:19:02 L209T kernel: qeth.3acf0c: 0.0.0360: The qeth device driver 
failed to recover an error on the device
Jan 20 17:19:02 L209T kernel: qeth: irb : 00 c2 40 17 7e 05 10 38 0e 02 
00 00 00 80 00 00  ..@.~..8
Jan 20 17:19:02 L209T kernel: qeth: irb 0010: 01 02 00 00 00 00 00 00 00 00 
00 00 00 00 00 00  
Jan 20 17:19:02 L209T kernel: qeth: sense data : 02 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00  
Jan 20 17:19:02 L209T kernel: qeth: sense data 0010: 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00  
Jan 20 17:19:02 L209T kernel: qeth.3acf0c: 0.0.0360: The qeth device driver 
failed to recover an error on the device
Jan 20 17:19:02 L209T kernel: qeth: irb : 00 c2 40 17 7e 05 10 38 0e 02 
00 00 00 80 00 00  ..@.~..8
Jan 20 17:19:02 L209T kernel: qeth: irb 0010: 01 02 00 00 00 00 00 00 00 00 
00 00 00 00 00 00  
Jan 20 17:19:02 L209T kernel: qeth: irb 0020: 02 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00  
Jan 20 17:19:02 L209T kernel: qeth: irb 0030: 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00  
Jan 20 17:19:02 L209T kernel: zfcp.e78dec: 0.0.7548: A QDIO problem occurred
Jan 20 17:19:02 L209T kernel: zfcp.e78dec: 0.0.7508: A QDIO problem occurred
Jan 20 17:19:02 L209T kernel: qeth.fd0b7c: 0.0.0360: A recovery process has 
been started for the device
Jan 20 17:19:02 L209T kernel: qdio: 0.0.0362 OSA on SC 2 using AI:1 QEBSM:0 
PCI:1 TDD:1 SIGA:RW A 
Jan 20 17:19:02 L209T kernel: qdio: 0.0.7508 ZFCP on SC 15 using AI:1 QEBSM:1 
PCI:1 TDD:1 SIGA: W A 
Jan 20 17:19:02 L209T kernel: qdio: 0.0.7548 ZFCP on SC 16 using AI:1 QEBSM:1 
PCI:1 TDD:1 SIGA: W A 
Jan 20 17:19:02 L209T kernel: qeth.cc0c57: 0.0.0360: MAC address 
02:78:c1:02:09:00 successfully registered on device eth0
Jan 20 17:19:02 L209T kernel: qeth.736dae: 0.0.0360: Device is a Guest LAN QDIO 
card (level: V630)
Jan 20 17:19:02 L209T kernel: with link type GuestLAN QDIO (portname: )
Jan 20 17:19:02 L209T kernel: qeth.bad88b: 0.0.0360: Device successfully 
recovered!
Jan 20 17:19:07 L209T multipathd: 8:0: mark as failed
Jan 20 17:19:07 L209T multipathd: 20017380009c51b8f: remaining active paths: 5
Jan 20 17:19:07 L209T multipathd: 8:16: mark as failed
Jan 20 17:19:07 L209T multipathd: 20017380009c51b90: remaining active paths: 5
Jan 20 17:19:07 L209T multipathd: 8:64: mark as failed
Jan 20 17:19:07 L209T multipathd: 20017380009c51cfb: remaining active paths: 5
Jan 20 17:19:07 L209T multipathd: 20017380009c51b90: sdb - directio checker 
reports path is down
Jan 20 17:19:07 L209T multipathd: 20017380009c51b8f: sda - directio checker 
reports path is down
Jan 20 17:19:07 L209T multipathd: 20017380009c51cfa: sdc - directio checker 
reports path is down
Jan 20 17:19:07 L209T multipathd: checker failed path 8:32 in map 
20017380009c51cfa
Jan 20 17:19:07 L209T multipathd: 20017380009c51cfa: remaining active paths: 5
Jan 20 17:19:07 L209T multipathd: 20017380009c51cf9: sdd - directio checker 
reports path is down
Jan 20 17:19:07 L209T multipathd: checker failed path 8:48 in map 
20017380009c51cf9
Jan 20 17:19:07 L209T multipathd: 20017380009c51cf9: remaining active paths: 5
Jan 20 17:19:07 L209T multipathd: 20017380009c51cfb: sde - directio checker 
reports path is down
Jan 20 17:19:07 L209T multipathd: 

Re: Interrupting Linux under z/VM session

2015-01-21 Thread Mauro Souza
Paul, you can IPL CMS even after booting Linux. It's a new IPL anyway.

Quitting vi under 3270 is really tricky. I would try a ^z and kill the
process.


Mauro
http://mauro.limeiratem.com - registered Linux User: 294521
Scripture is both history, and a love letter from God.

2015-01-21 11:09 GMT-02:00 Beesley, Paul paul.bees...@atos.net:

 escape followed by :q! doesn't work. I can't find anything that does.
 Obviously vi is unique (in many ways ...)
 I don't think you can IPL CMS if you've already booted z/Linux.

 I may have found someone who has SSH access and am waiting for them to try
 and kill my vi process.
 But it would be useful to know how to get out of this via z/VM for future
 occasions!

 Regards and thanks
 Paul



 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of
 John McKown
 Sent: Wednesday, January 21, 2015 12:56 PM
 To: LINUX-390@vm.marist.edu
 Subject: Re: Interrupting Linux under z/VM session

 On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

  On Wed, 21 Jan 2015 12:06:51 +
  Beesley, Paul paul.bees...@atos.net wrote:
 
   Thanks for the tip, I'll try that.
   Unfortunately it doesn't get me out of my vi session. I think I'm
   stuck there forever
 
  you might want to try
 
  ^z
  killall vi
  fg
 
  Berthold
 

 ​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file
 I was editing, displaying a ^Z.​ I can't duplicate the OP's environment,
 but I wonder why he can't just do the normal: escape followed by :q! to
 exit vi.

 Sorry for my ignorance of Linux on z under z/VM, but isn't there some way
 to use SMSG to send commands to z/Linux? I.e. to send the killall vi
 command from a CMS logon?


 --
 ​
 While a transcendent vocabulary is laudable, one must be eternally careful
 so that the calculated objective of communication does not become ensconced
 in obscurity.  In other words, eschew obfuscation.

 111,111,111 x 111,111,111 = 12,345,678,987,654,321

 Maranatha! 
 John McKown

 --
 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/
 Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are
 trading names used by the Atos group. The following trading entities are
 registered in England and Wales: Atos IT Services UK Limited (registered
 number 01245534), Atos Consulting Limited (registered number 04312380),
 Atos Worldline UK Limited (registered number 08514184) and Canopy The Open
 Cloud Company Limited (registration number 08011902). The registered office
 for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No.
 for each is: GB232327983.

 This e-mail and the documents attached are confidential and intended
 solely for the addressee, and may contain confidential or privileged
 information. If you receive this e-mail in error, you are not authorised to
 copy, disclose, use or retain it. Please notify the sender immediately and
 delete this email from your systems. As emails may be intercepted, amended
 or lost, they are not secure. Atos therefore can accept no liability for
 any errors or their content. Although Atos endeavours to maintain a
 virus-free network, we do not warrant that this transmission is virus-free
 and can accept no liability for any damages resulting from any virus
 transmitted. The risks are deemed to be accepted by everyone who
 communicates with Atos by 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/


Re: Interrupting Linux under z/VM session

2015-01-21 Thread Beesley, Paul
Bingo! Thanks very much
I was entering ^c (^ is the shift 6 on the UK keyboard)
When I entered ¬c (¬ is shift + key to the left of 1), and then :q!, I exited vi

Thank you so much

Regards and thanks
Paul



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Linker 
Harley - hlinke
Sent: Wednesday, January 21, 2015 1:27 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session

Paul,

I logged onto a 3270 console for a SLES 12 system and invoked the vi editor.  I 
was able to terminate the vi session by entering
   ¬c   (shift 6 in the Bluezone 3270 emulator)
   :q

I then tied the same test on a SLES 11 SP3 system and the same commands 
terminated the vi session.

I noticed that after I entered '¬c' that vi issued lines
   [24;1HType  :quitEnter  to exit Vim [24;63H[24;77H [24;63H1,1
 All [1;1H

I then entered ':q' to terminate the vi session as I didn't make any changes to 
the file.

I am running z/VM 6.3 but I doubt that the version of z/VM makes a difference.


Harley

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Beesley, 
Paul
Sent: Wednesday, January 21, 2015 7:10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session

escape followed by :q! doesn't work. I can't find anything that does. 
Obviously vi is unique (in many ways ...) I don't think you can IPL CMS if 
you've already booted z/Linux.

I may have found someone who has SSH access and am waiting for them to try and 
kill my vi process.
But it would be useful to know how to get out of this via z/VM for future 
occasions!

Regards and thanks
Paul



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of John 
McKown
Sent: Wednesday, January 21, 2015 12:56 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session

On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

 On Wed, 21 Jan 2015 12:06:51 +
 Beesley, Paul paul.bees...@atos.net wrote:

  Thanks for the tip, I'll try that.
  Unfortunately it doesn't get me out of my vi session. I think I'm
  stuck there forever

 you might want to try

 ^z
 killall vi
 fg

 Berthold


​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file I 
was editing, displaying a ^Z.​ I can't duplicate the OP's environment, but I 
wonder why he can't just do the normal: escape followed by :q! to exit vi.

Sorry for my ignorance of Linux on z under z/VM, but isn't there some way to 
use SMSG to send commands to z/Linux? I.e. to send the killall vi command from 
a CMS logon?


--
​
While a transcendent vocabulary is laudable, one must be eternally careful so 
that the calculated objective of communication does not become ensconced in 
obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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/ Atos, 
Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names 
used by the Atos group. The following trading entities are registered in 
England and Wales: Atos IT Services UK Limited (registered number 01245534), 
Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited 
(registered number 08514184) and Canopy The Open Cloud Company Limited 
(registration number 08011902). The registered office for each is at 4 Triton 
Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for 
the addressee, and may contain confidential or privileged information. If you 
receive this e-mail in error, you are not authorised to copy, disclose, use or 
retain it. Please notify the sender immediately and delete this email from your 
systems. As emails may be intercepted, amended or lost, they are not secure. 
Atos therefore can accept no liability for any errors or their content. 
Although Atos endeavours to maintain a virus-free network, we do not warrant 
that this transmission is virus-free and can accept no liability for any 
damages resulting from any virus transmitted. The risks are deemed to be 
accepted by everyone who communicates with Atos by email.
***
The information contained in this communication is confidential, is intended 
only for the use of the recipient named above, and may be legally privileged.

If the reader of this message is not the intended recipient, you are hereby 
notified that 

Re: Interrupting Linux under z/VM session - terminal type?

2015-01-21 Thread Vitale, Joseph

What is the Terminal type setting for a  3270  session when using vi?Mine 
shows dumb:

echo $TERM
dumb


Thanks

Joseph Vitale
Technology Services Group
Mainframe Operating Systems

Pershing Plaza
95 Christopher Columbus Drive
Floor 14   
Jersey City,  N.J.  07302
Work  201-395-1509
Cell917-903-0102


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of John 
McKown
Sent: Wednesday, January 21, 2015 7:56 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session

On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

 On Wed, 21 Jan 2015 12:06:51 +
 Beesley, Paul paul.bees...@atos.net wrote:

  Thanks for the tip, I'll try that.
  Unfortunately it doesn't get me out of my vi session. I think I'm 
  stuck there forever

 you might want to try

 ^z
 killall vi
 fg

 Berthold


​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file I 
was editing, displaying a ^Z.​ I can't duplicate the OP's environment, but I 
wonder why he can't just do the normal: escape followed by :q! to exit vi.

Sorry for my ignorance of Linux on z under z/VM, but isn't there some way to 
use SMSG to send commands to z/Linux? I.e. to send the killall vi command from 
a CMS logon?


--
​
While a transcendent vocabulary is laudable, one must be eternally careful so 
that the calculated objective of communication does not become ensconced in 
obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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/

The information contained in this e-mail, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities.


Re: Interrupting Linux under z/VM session - terminal type?

2015-01-21 Thread Linker Harley - hlinke
Mine also shows dumb.


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Vitale, 
Joseph
Sent: Wednesday, January 21, 2015 7:01 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session - terminal type?


What is the Terminal type setting for a  3270  session when using vi?Mine 
shows dumb:

echo $TERM
dumb


Thanks

Joseph Vitale
Technology Services Group
Mainframe Operating Systems

Pershing Plaza
95 Christopher Columbus Drive
Floor 14   
Jersey City,  N.J.  07302
Work  201-395-1509
Cell917-903-0102


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of John 
McKown
Sent: Wednesday, January 21, 2015 7:56 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session

On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben b...@suse.de wrote:

 On Wed, 21 Jan 2015 12:06:51 +
 Beesley, Paul paul.bees...@atos.net wrote:

  Thanks for the tip, I'll try that.
  Unfortunately it doesn't get me out of my vi session. I think I'm 
  stuck there forever

 you might want to try

 ^z
 killall vi
 fg

 Berthold


​I just tried that, vi on Linux/Intel, and the ^z got echoed into the file I 
was editing, displaying a ^Z.​ I can't duplicate the OP's environment, but I 
wonder why he can't just do the normal: escape followed by :q! to exit vi.

Sorry for my ignorance of Linux on z under z/VM, but isn't there some way to 
use SMSG to send commands to z/Linux? I.e. to send the killall vi command from 
a CMS logon?


--
​
While a transcendent vocabulary is laudable, one must be eternally careful so 
that the calculated objective of communication does not become ensconced in 
obscurity.  In other words, eschew obfuscation.

111,111,111 x 111,111,111 = 12,345,678,987,654,321

Maranatha! 
John McKown

--
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/

The information contained in this e-mail, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities.
***
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.

If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank You.