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.
I think it brings up too many thoughts of "Final Destination" to use as a
movie title...'cause those movies definitely were not blockbusters and were
very far from "cool" :-)
Regards,
Miguel Delapaz
z/VM TCP/IP Development
The IBM z/VM Operating System wrote on 06/25/2007
02:50:58 PM:
> On Mond
On Monday, 06/25/2007 at 11:30 ZE2, Rob van der Heij <[EMAIL PROTECTED]>
wrote:
> PS Somehow my gmail client shows me all advertising for vacation in
> Mexico or Seychelles with all posts about IBM's new service... :-)
I admit that "Destination Z" is not a luxurious vacation spot (but would
prob
On 6/25/07, Jim Bohnsack <[EMAIL PROTECTED]> wrote:
Unless I'm missing something, it looks to me like what we, in IBM, used
to call boilerplate. I hope that I'm missing something, however.
Sigh. I predict that real soon you will be required to design your own
avatar with beard and grey hair a
The point I was trying to make was that with z/VM 4.x, there are two different
nucleus programs. One for 31 bit and the other for 64 bit. And if your
hardware change, causes you to change to a different nucleus, you might have
problems, hence, something to stick in the back of your mind.
I we
On Monday, 06/25/2007 at 04:46 AST, "Les Geer (607-429-3580)"
<[EMAIL PROTECTED]> wrote:
> That is the postscript error handler RSCS sends by default prior to
> the print job. Perhaps the printer doesn't like something about this
> postscript program. This really is for handling of plain text fi
That is the postscript error handler RSCS sends by default prior to
the print job. Perhaps the printer doesn't like something about this
postscript program. This really is for handling of plain text files.
You can turn off this feature by using:
EPARM='EH=NO'
in the link parm statement.
Best R
Unless I'm missing something, it looks to me like what we, in IBM, used
to call boilerplate. I hope that I'm missing something, however.
Jim
Dave Jones wrote:
This looks 'interesting'
http://www-03.ibm.com/systems/z/destinationz/index.html
--
Jim Bohnsack
Cornell University
(60
We too: we moved our z/VM 4.4 31-bit mode from 9672 onto z9, then stepped
right to z/VM 5.2 in 64-bit mode.
2007/6/25, Jim Bohnsack <[EMAIL PROTECTED]>:
Tom--That doesn't match what I remember from when we first got the z9.
I think that we, initially, ran with the 31 bit nuc on the z9. We are
On Monday, 06/25/2007 at 02:14 EST, Joan Gerads <[EMAIL PROTECTED]>
wrote:
> Okay,
> Here is the output we are seeing: it is just a small portion of the
> output, but I was hoping someone would be able to tell me what is
> generating this output:
[snip the postscript gorp]
Joan, please post usi
Okay,
Here is the output we are seeing: it is just a small portion of the
output, but I was hoping someone would be able to tell me what is
generating this output:
%!PS
% serverloop password
/brkpage where not } dup serdict begin
statisdict begin checkpasswor
Tom--That doesn't match what I remember from when we first got the z9.
I think that we, initially, ran with the 31 bit nuc on the z9. We are
running 4.4, now, with the 64 bit option. Until recently, I ran my 2nd
level test 4.4 system using the 31 bit nuc under a 4.4 nuc running with
the 64 b
On Monday, 06/25/2007 at 02:10 AST, Rich Greenberg <[EMAIL PROTECTED]>
wrote:
> The copy/paste didn't work either. Can you post the pdf on a web site?
Better yet, just "paste special..." as text, not HTML or Rich Text.
Alan Altmark
z/VM Development
IBM Endicott
On: Mon, Jun 25, 2007 at 12:03:15PM -0500,Joan Gerads Wrote:
} We recently purchased an IBM Infoprint 6500 Line Matrix printer and are
} trying RSCS for the first time on z/VM 5.2.
}
} When we attempt to send anything to the printer from VM, we get a bunch
} of garbage output printing before the
On: Mon, Jun 25, 2007 at 01:18:58PM -0400,Anne Crabtree Wrote:
} how about i just say END!
That should work fine.
--
Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353
Eastern time. N6LRT I speak for myself & my dogs only.VM'er since CP-67
Canines:Val, Red, Shas
One small item to consider...
zVM 4.x was the dual image release. There are 2 different supervisors. A 31
bit and a 64 bit one. As you will be going to a z9, you are required to use
the 64 bit one. No big deal.
Except if you have something that is depending on your old supervisor.
A pa
Sorry, I did not realize that LISTSERV did not allow attachments...Here
is a copy and paste of just a small bit of the output:
Here is a sample of our output through RSCS that I tried to send in an
attachment in my previous request:
From: The IBM z/VM Oper
how about i just say END!
Anne D. Crabtree
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8885
Fax 304-558-1351
>>> [EMAIL PROTECTED] 6/25/2007 1:04 PM >>>
Yes, to 3338 is 3339 but MDISK 3338 is for 3338.
-Original Message-
From: The IBM z/VM Operating System
This looks 'interesting'
http://www-03.ibm.com/systems/z/destinationz/index.html
--
DJ
V/Soft
omg i should just go home... it's a wonder i'm getting anything
accomplished today...
Anne D. Crabtree
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8885
Fax 304-558-1351
>>> [EMAIL PROTECTED] 6/25/2007 12:49 PM >>>
I'm coming in a bit late but from what I see, if you go from
Joan,
I don't think the LISTSERV allows attachments... copy and pase some of your
message.
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
Behalf Of Joan Gerads
Sent: Monday, June 25, 2007 12:03 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: RSCS 3.2 and z/VM 5.2
Yes, to 3338 is 3339 but MDISK 3338 is for 3338.
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Macioce, Larry
Sent: Monday, June 25, 2007 12:50 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
I'm coming in a bit late
RSCS 3.2
z/VM 5.2
IBM Z9 BC processor
VSE 2.6 guests running under z/VM
IBM 6500 Infoprint Printer
We recently purchased an IBM Infoprint 6500 Line Matrix printer and are
trying RSCS for the first time on z/VM 5.2.
When we attempt to send anything to the printer from VM, we get a bunch
of garbag
I'm coming in a bit late but from what I see, if you go from to
3338 that IS 3339 cyls. Did I miss something?
mace
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of RPN01
Sent: Monday, June 25, 2007 11:04 AM
To: IBMVM@LISTSERV.UARK.EDU
Subj
Hello
This is just 1/2 of a CTC connection but it's my first time with a single
control unit statement and 2 CSS's involved; I understand, I need to
define the CU in one CSS, then Modify it for the second.
I think the CSS number for the Modify is the second one I believe, I need
to DEF the devices
Berry,
No, there's no logic in the TCP/IP stack to reduce the size of the buffers
once they've been expanded. It would be nice though...
Regards,
Miguel Delapaz
z/VM TCP/IP Development
The IBM z/VM Operating System wrote on 06/22/2007
03:40:44 PM:
> Hello Alan,
>
> That would get me to a que
Unless the Linux admin takes specific action to label the disk with the
current label, it will be overwritten with the Linux volume name, and will
then not be available the next time the userid is logged out and back in.
Two courses of action: Either change the minidisk to exclude cylinder zero,
m
2007/6/25, Stracka, James (GTI) <[EMAIL PROTECTED]>:
Well, there is APAR PQ75355 for sending large files to the Reader.
Which doesn't fix anything bit documents possible problems.
--
Kris Buelens,
IBM Belgium, VM customer support
Well, there is APAR PQ75355 for sending large files to the Reader.
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Friday, June 22, 2007 1:59 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: FTPing to z/VM
On Friday, 06/22/2007
Yes, I guess that should be 3339. I have 3338 all over the place.. even
on first level. I changed the MDISK statements for the LX packs to be
000 3339. Linux person hasn't really tried to use them yet so I don't
know if the 000 will be a problem or not. It seems to know that it is
labelled LX16
We've been running 4.4 on a z9 since we got the z9 in February. There
are no problems at all. We'll switch over to 5.3 later in the summer or
fall.
Jim
Antonio C Prado wrote:
Phillip, we are runnig zVM 4.3 using basic functions in a z9. So, I think
you can, but consider the upgrade as soon
Phillip, we are runnig zVM 4.3 using basic functions in a z9. So, I think
you can, but consider the upgrade as soon as possible.
Antonio Carlos PRADO
[EMAIL PROTECTED]
32 matches
Mail list logo
