In z/VM, from the first release on, CPLOAD contained two CP nuclei: CPLOAD32
and CPLOAD64. During IPL, the 64 bit version was be loaded if the HW was
capable, otherwise CPLOAD32 was activated.
So indeed: if you used the standards, simply switching to a z-machine caused
a switch from CP nucleus.
Eric,
Sorry for the late reply. I was using the emulated TN3270 session.
After ldev logo was updated with the new logo, we are now able to see the
new logo.
Thanks for you help !
Ann
Eric Schadow [EMAIL PROTECTED]
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
Trying to do xedit macros that deal with XEDIT in update mode, it is
rather annoying that there is no EXTRACT that will give me the name of
the control file and maybe a few more. Without it, you have to play
tricks with a wrapper to invoke XEDIT and keep parameters in GLOBALV
and parse the
On 25 Jun 2007 at 16:22, Tom Duerbusch wrote:
However, I recall when the dual image release of z/VM 4.x became
available, and was initially installed on 31 bit hardware, when the box
swap came to 64 bit hardware, there were many problems and questions on
this listserv, about what went wrong.
Tom et al,
The default on the z/890 was the 64 bit supervisor.
If for some reason, you were running the 31 bit
supervisor on your z/890 (which you can select),
your only option is the 64 bit supervisor on the z9.
Thank you all for the input.
Sounds like we can run zVM 4.4 on the z9 - no
Another item to check off the list.
One of the things I really like about the listservs, not only getting to the
meat of a problem, but the discussion of the frills that are around the problem.
Like, switching hardware might also cause a switch in operating systems, even
though you IPL the
On our z9 BC we had to give 1G out of the 8G we paid for.
Dave Lewis
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Tuesday, June 26, 2007 12:58 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: zVM 4.4 on a z9
...
What is
Not taken from the memory you pay for
Just like women...
No matter what, you're gonna pay G
It should be...
Not taken from the memory advertised for the box.
So...is 2 GB sufficient?
I'm thinking of the large shops...
60 LPARs
Thousands of 3390s under the DS8000 shared across all lpars.
Where would I increase the timeout value for a timeout to occur between
the Z/VM FTP Client and a windows server?
I have been seeing a few:
DTCFTC0334E In SendToTcp: Server not responding, closing connection.
error in SendToTcp
Abnormal inter-VM communication condition
The manual says it's a
Jim,
The timeout values are configured in the FTP DATA file. There are a few
knobs in there that you may need to twist depending on what's causing the
timeout - CCONNTIME, DATACTTIME, DCONNTIME, INACTTIME MYOPENTIME
Regards,
Miguel Delapaz
z/VM TCP/IP Development
The IBM z/VM Operating
On Tuesday, 06/26/2007 at 02:57 AST, Hughes, Jim - OIT
[EMAIL PROTECTED] wrote:
Where would I increase the timeout value for a timeout to occur between
the Z/VM FTP Client and a windows server?
I have been seeing a few:
DTCFTC0334E In SendToTcp: Server not responding, closing connection.
On Tue, 26 Jun 2007 13:57:41 -0400, Alan Altmark [EMAIL PROTECTED]
wrote:
On Tuesday, 06/26/2007 at 12:08 EST, Tom Duerbusch
[EMAIL PROTECTED] wrote:
Another item to check off the list.
One of the things I really like about the listservs, not only getting
to
the
meat of a problem, but the
12 matches
Mail list logo
