Re: Logs from Operator

[Scott Rohling]

​Similar discussion 11 years ago:
http://bit.listserv.vmesa-l.narkive.com/TUXHObxD/vm-operator-messages-to-networked-syslogd
​

Scott Rohling

On Mon, Aug 15, 2016 at 4:40 PM, Alan Ackerman 
wrote:

> You are better off with CA VM:Operator or IBM Operations Manager for z/VM.
> If you insist on rolling your own, there are presentation available on how
> to use PROP. But it's going to cost you time.
>
> If your management thinks your time is free, then have fun! You'll need to
> learn REXX and Pipelines and PROP -- but I certainly enjoyed that.
>
> Alan Ackerman
> alan.ackerma...@gmail.com
>
>
>
> > On Aug 15, 2016, at 8:56 AM, Tracy Dean  wrote:
> >
> >> From: joão paulo limberger (shoo) 
> >> To: LINUX-390@VM.MARIST.EDU
> >> Date: 08/13/2016 10:32 AM
> >> Subject: Logs from Operator
> >> Sent by: Linux on 390 Port 
> >>
> >> Hi All!
> >>
> >> I want to receive in a linux VM  all the  messages sends to the console
> > of
> >> the user Operator  ...
> >>
> >> What is the best way to do this?
> >>
> >> Thanks!!!
> >> jp
> >
> > If you have IBM Operations Manager for z/VM, you can easily capture all
> > messages to OPERATOR (or any other userid) and send them to a syslog
> > daemon running somewhere in your enterprise, including one running on a
> > Linux guest.  Feel free to contact me for more info.
> >
> > Tracy Dean, IBM
> > t...@us.ibm.com
> >
> >
> > --
> > 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: Logs from Operator

[Alan Ackerman]

You are better off with CA VM:Operator or IBM Operations Manager for z/VM. If 
you insist on rolling your own, there are presentation available on how to use 
PROP. But it's going to cost you time. 

If your management thinks your time is free, then have fun! You'll need to 
learn REXX and Pipelines and PROP -- but I certainly enjoyed that.

Alan Ackerman
alan.ackerma...@gmail.com



> On Aug 15, 2016, at 8:56 AM, Tracy Dean  wrote:
> 
>> From: joão paulo limberger (shoo) 
>> To: LINUX-390@VM.MARIST.EDU
>> Date: 08/13/2016 10:32 AM
>> Subject: Logs from Operator
>> Sent by: Linux on 390 Port 
>> 
>> Hi All!
>> 
>> I want to receive in a linux VM  all the  messages sends to the console 
> of
>> the user Operator  ...
>> 
>> What is the best way to do this?
>> 
>> Thanks!!!
>> jp
> 
> If you have IBM Operations Manager for z/VM, you can easily capture all 
> messages to OPERATOR (or any other userid) and send them to a syslog 
> daemon running somewhere in your enterprise, including one running on a 
> Linux guest.  Feel free to contact me for more info.
> 
> Tracy Dean, IBM
> t...@us.ibm.com
> 
> 
> --
> 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: Logs from Operator

[Tracy Dean]

> From: joão paulo limberger (shoo) 
> To: LINUX-390@VM.MARIST.EDU
> Date: 08/13/2016 10:32 AM
> Subject: Logs from Operator
> Sent by: Linux on 390 Port 
> 
> Hi All!
> 
> I want to receive in a linux VM  all the  messages sends to the console 
of
> the user Operator  ...
> 
> What is the best way to do this?
> 
> Thanks!!!
> jp

If you have IBM Operations Manager for z/VM, you can easily capture all 
messages to OPERATOR (or any other userid) and send them to a syslog 
daemon running somewhere in your enterprise, including one running on a 
Linux guest.  Feel free to contact me for more info.

Tracy Dean, IBM
t...@us.ibm.com


--
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: DASD usage

[Marcy Cortes]

We're all #1.  Well, that and a fair amount of NAS mounted via NFS for lower 
cost big chunks.
We make use of Hyperswap and replication services with GDPS so 3390 with that.

Marcy

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Gentry, 
Steve
Sent: Monday, August 15, 2016 7:50 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] DASD usage

There are at least 3 combinations of DASD usage for Linux implementation.
They are:

1)  Everything on 3390 storage

2)  Everything on non-3390, external disk via a fiber card

3)  A combination of 1 & 2



What are the thoughts on using these? Is one preferred over the other?

Thanks,

Steve



--
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: DASD usage

[Rick Troth]

Great question!


On 08/15/16 10:49, Gentry, Steve wrote:

There are at least 3 combinations of DASD usage for Linux implementation.
They are:

1)  Everything on 3390 storage

2)  Everything on non-3390, external disk via a fiber card

3)  A combination of 1 & 2


You left out V-Disk, but we'll just focus on physical storage. Linux can
also use DCSS for filesystems. Very handy.



What are the thoughts on using these? Is one preferred over the other?


Depends on two (or more) important things from your shop: _is z/VM going
to manage the storage?_ and _do you have cultural affinity for one or
the other? _
Also _depends on the quantity of data_. If you have large filesystems,
you're more likely to go with #3 combo. (On all Unix/Linux, not just z.)

It's reasonable that the hypervisor will carve out chunks of physical
disk to be given to the guests. On z/VM we call them minidisks, but KVM,
Xen, and VMware and the rest have the same concept. z/VM (e.g.,
VM:Secure, not CP alone) can also sliced up SAN, but you're probably
going to want that fed through as EDEV. (So it's not really limited to
3390 unless "cultural affinity" prohibits EDEV.)

The storage itself is often managed by different groups. Most shops
where I have worked had one team for z disk and another for SAN. These
people typically reside on different planets. (Sad because "disk is
disk"; see below.)

*Personal recommendation*: mix it up. "*think, then mix*" (give it some
forethought, but then *do* go with a combination)
Put the OS on smaller filesystems backed by hypervisor-managed DASD.
Keep the OS separate so you can maintain it apart from the data. Put
large quantities of data on SAN (is often more cost effective, but
there's another reason; see below). Possibly put smaller data quantities
on hypervisor-managed DASD, but in any case keep it separate from the OS.

SAN is a network. (FICON is too, but /doesn't look that way/ to zLinux.)

Keep the OS separate so it can be maintained separately.
It's a pain to have to re-install the data just because you upgraded the
operating system. But it happens.
Better to have the data (even if smaller quantities) in well though
alternative mount point(s) to be imported after op sys refresh.
(Quotes from "Mother" come to mind, and don't comingle what IBM gives
you and what you do for yourself, but here it's SUSE/RH/Debian too.)

Dirty little secret #1: disk is disk
A long time ago, I heard that 3390 would be the last disk of its kind.
Huh? Turns out that physical 3390 was the last DASD to be
washing-machine sized drum of platters. Everything since then has been
emulation of ECKD/tracks/records backed by FBA. There are reasons, some
of them good, for continuing to use 3390. (Even though it's an
illusion.) But keep in mind, in case it helps you, that the backing
store is really fixed block. You might get some advantages by going
direct. (Bypassing the CKD/track/record emulation.) Some mainframe
storage vendors even offer 9336 or 3370 presentation. (That is, FBA on
the channel, not via SAN or EDEV.)

Dirty little secret #2: SAN is cross-platform
This ties indirectly with DLS#1. SAN volumes can be used by any op sys,
any platform, any (nearly any) computing hardware in your shop.
Depending on the filesystem stamped onto a SAN volume (call it a LUN)
you might be able to share it directly with many systems. What does it
buy you? Depends on your platform needs. Maybe nothing; maybe lots. Hard
to know ahead of time what apps and systems will or will not be able to
use a LUN which was created by some other system or app. But just as
z/OS and VSE and z/VM can share ECKD DASD, so Linux and AIX and Solaris
and HP-UX and even Windows can share LUNs. Same advantages; same risks.

Of course, SAN is all fixed block, so that's how DLS#1 and DLS#2 relate.

There's also a thing about partitioning or not. (But you've heard enough
of my ranting and rambling for Monday, eh?)



Thanks,

Steve


I hope this helps.

-- R; <><




--
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: DASD usage

[Scott Rohling]

My experience (briefly):

1)   Easiest to manage, least issues with DR or moving to different
processors.Physical backups can be taken using z/VM or z/OS storage
utilities.  Same for cloning images...
2)   NPIV required for any real storage security.  Managed by fcp/wwpn/lun
- nowhere near as easy as a 3390 volume label and minidisk address.
 Complicates DR and moving as FCP/WWPN/LUN must be considered/solved.   No
mainframe storage utilities.   Storage typically managed by non-mainframe
folks and there can be techno language barriers.You can get much bigger
chunks of storage then on 3390 but should still manage using LVM for growth.
3)  This is fairly common..   The 'system' on 3390 DASD - the application
data on SAN/SCSI.You can use 3390 based recovery methods for the system
piece..   then use various methods to restore (or reconnect to) the
application data on external storage.   You still bring all the
complications of #2 with you but can simplify the core system/server piece.
4)   EDEV --   you centralize the complications of FCP/WWPN/LUN in one
place (CP) so that your zLinux guests don't need to --   FBA minidisks can
be managed just like on 3390 - and the data is available to the host (z/VM)
system and other guests via LINK.There is a performance cost for
emulation.. and the multi pathing is probably not as robust as on zLinux
(?).
5)  Combination of EDEV and directly attached FCP (for key guests where
performance/size makes directly attached a better choice).

If I need to use SCSI - my own preference is for EDEV ..if I have 3390
available then I prefer z/VM to be on 3390 and the zLinux guests to use
EDEV minidisks.

Others may (probably) have very different views..

Scott Rohling



On Mon, Aug 15, 2016 at 7:49 AM, Gentry, Steve <
steve.gen...@westernsouthernlife.com> wrote:

> There are at least 3 combinations of DASD usage for Linux implementation.
> They are:
>
> 1)  Everything on 3390 storage
>
> 2)  Everything on non-3390, external disk via a fiber card
>
> 3)  A combination of 1 & 2
>
>
>
> What are the thoughts on using these? Is one preferred over the other?
>
> Thanks,
>
> Steve
>
>
>
> --
> 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: DASD usage

[Dave Jones]

Hi, Steve.

I would suggest using option 3, a combination of ECKD and SANthe ECK
DASD for z/VM functions, like RACF (RACF requires 3390 DASD, btw), and
SAN for the Linux guests.

DJ

On 08/15/2016 09:49 AM, Gentry, Steve wrote:

There are at least 3 combinations of DASD usage for Linux implementation.
They are:

1)  Everything on 3390 storage

2)  Everything on non-3390, external disk via a fiber card

3)  A combination of 1 & 2



What are the thoughts on using these? Is one preferred over the other?

Thanks,

Steve



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



--
*David Jones **|**Managing Director for zSystems Services **|**z/VM,
Linux, and Cloud
703.237.7370 (Office) **|**281.578.7544 (Cell)*

*Information Technology Company *

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

DASD usage

[Gentry, Steve]

There are at least 3 combinations of DASD usage for Linux implementation.
They are:

1)  Everything on 3390 storage

2)  Everything on non-3390, external disk via a fiber card

3)  A combination of 1 & 2



What are the thoughts on using these? Is one preferred over the other?

Thanks,

Steve



--
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: z/VM cheatsheet

[Paul Flint]

Greetings Tito,

Got to Mark before you.

Very nice work.

Regards,

Paul Flint

On Sat, 13 Aug 2016, Tito Garrido wrote:


Date: Sat, 13 Aug 2016 10:38:29 -0300
From: Tito Garrido 
Reply-To: Linux on 390 Port 
To: LINUX-390@VM.MARIST.EDU
Subject: z/VM cheatsheet

Hi Folks,

Just sharing a simple z/VM cheatsheet that I have created:

https://www.cheatography.com/titog/cheat-sheets/z-vm-cheat-sheet/

If you want to collaborate let me know :)

Regards,

Tito

--

Linux User #387870
.
 _/_õ|__|
..º[ .-.___.-._| . . . .
.__( o)__( o).:___

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



Kindest Regards,



☮ Paul Flint
(802) 479-2360 Home
(802) 595-9365 Cell

/
Based upon email reliability concerns,
please send an acknowledgement in response to this note.

Paul Flint
17 Averill Street
Barre, VT
05641

--
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: z/VM cheatsheet

[Paul Flint]

Greetings Mark,

Very nice!

Regards,

Paul Flint

On Sat, 13 Aug 2016, Mark Post wrote:


Date: Sat, 13 Aug 2016 10:34:32 -0600
From: Mark Post 
Reply-To: Linux on 390 Port 
To: LINUX-390@VM.MARIST.EDU
Subject: Re: z/VM cheatsheet


On 8/13/2016 at 09:38 AM, Tito Garrido  wrote:

Hi Folks,

Just sharing a simple z/VM cheatsheet that I have created:

https://www.cheatography.com/titog/cheat-sheets/z-vm-cheat-sheet/

If you want to collaborate let me know :)


If you want collaboration, wiki.linuxvm.org might be a better place.


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/



Kindest Regards,



☮ Paul Flint
(802) 479-2360 Home
(802) 595-9365 Cell

/
Based upon email reliability concerns,
please send an acknowledgement in response to this note.

Paul Flint
17 Averill Street
Barre, VT
05641

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