I should never assume anything when it comes to the Dark Side.
Thank goodness VM and VSE behave rationally.
8-)
Steve G.
Alan Altmark <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
04/08/2006 02:15 PM
Please respond to Linux on 390 Port
To: LINUX-390@VM.MARIST.EDU
cc:
TCP/IP running on z/OS and Linux both use the same means. That is, what
IP address am I trying to communicate with, and what does my routing
table tell me about how to get there?
Give your HiperSocket interfaces IP addresses that are on a different
subnet than the IP addresses on the OSA interfac
On Friday, 04/07/2006 at 10:30 AST, David Kreuter
<[EMAIL PROTECTED]> wrote:
> Seems to me CP already has most of this code path anyway. The free
> storage limit detection will stop a machine in its tracks after the
> second violation. It puts the errant machine into CP READ stopped state.
> In th
It could be that the file system where the work file is being created is
full. Thus, when you try to save your changes and exit, the changes
cannot be written to disk and then copied to /var/spool/...
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Beha
The last word we had on this subject was from Jim Elliott of IBM, back
in July of 2004. At that time, Linux/390 was not one of the platforms
that supported GPFS. Red Hat's GFS may be of some interest, if you're
looking for a shared file system. If it's all within on z/VM system,
NFS or AFS are k
On Friday, 04/07/2006 at 08:26 EST, Steve Gentry
<[EMAIL PROTECTED]> wrote:
> In VM and I think VSE you have to use 3 cuu's for each access point (ip
> addr.) on an OSA. I would assume zOS is the same. The same rules apply
> for hipersockets.
While your assumption is reasonable, Steve, that's no
