Hi David.
Just as Alan Altmark points out, check the pricing model carefully first.
We run z/VM in two separate LPARs only using IFLs, which seems to be the
most cost-effective solution.
It works very well, we are just a few persons managing nearly 200 zLinux
servers here.
Be prepared for the
Greetings from the SHARE LVM Program group!
We would like to invite anyone who may be interested in meeting with us and
learning more about the Linux and VM Program at SHARE to join us for dinner
during the next SHARE conference, which is being held in Anaheim,
California. The dinner is scheduled
I'll go. Thanks.
Melissa Dziedzic
-Original Message-
From: Jim Moling jim.mol...@gmail.com
Sender: Linux on 390 Port LINUX-390@VM.MARIST.EDU
Date: Tue, 7 Aug 2012 02:55:34
To: LINUX-390@VM.MARIST.EDU
Reply-To: Linux on 390 Port LINUX-390@VM.MARIST.EDU
Subject: SHARE Anaheim - LVM Program
Greetings from the SHARE LVM Program group!
We would like to invite anyone who may be interested in meeting with us
and learning more about the Linux and VM Program at SHARE to join us for
dinner during the next SHARE conference, which is being held in Anaheim,
California. The dinner is
I'm in the initial stage of porting my TSO/CMS program (KICKS, see
kicksfortso.com) to linux, including zlinux. KICKS is mostly GCC code,
though not open source. Several people have recommended I post to this
list for some of my questions. So I've subscribed, and looked at some
past posts, and am
Hi, Mike, --
I believe I have heard of your work before.
(1) first, does my quest seem appropriate for this list? and if so, my
first question:
Since A: you're porting to Linux and B: zLinux runs on mainframe HW
(and CISC runs on mainframe HW), it would seem appropriate, yes.
(2) TSO CMS
Here's the question: Is this the most natural unix/linux way to connect such
internal and external names?
For code running in the same process context, that's doable. If you need
multiple processes not necessarily derived from the same parent process to
access that data, you need to use a
MVS 'DD' statements strike me as the moral equivalent of Unix file
descriptors. (Same goes for CMS FILEDEF operations.) Since MVS and CMS
now possess actual Unix file descriptors, the picture is cloudy and the water
is muddy.
Not really -- one more level of indirection is involved. He's
Given that there'll be a main process which spawns child processes/threads per
transaction/user then using shell statements like:
export DDNAME_1=/pathname
And then in the program use the following to map the DD name to the pathname
for the open/fopen:
path=getenv(DDNAME_1)
fd=open(path,
