On Thu, Mar 25, 2010 at 7:47 PM, Daniel P. Martin wrote:
> See, kids, this is what happens when you try to handle correspondence
> under the influence of cold medicine...
>
> "Nothing going on in here. Please move along."
>
> *sigh*
>
I was going to say, "FSVO 'directly'".
See, kids, this is what happens when you try to handle correspondence
under the influence of cold medicine...
"Nothing going on in here. Please move along."
*sigh*
-dan.
On 3/25/2010 6:46 PM, Daniel P. Martin wrote:
Neale: I received the following on the IBMVM moderator in-box.
Rather tha
Neale: I received the following on the IBMVM moderator in-box. Rather
than pass to the list, I've opted to pass to you directly...
-dan.
On 3/24/2010 12:52 PM, Neale Ferguson wrote:
A gentle reminder that the next meeting of Hillgang will take place on
Friday 26 March, in Herndon Virginia at
On Thursday, 03/25/2010 at 11:45 EDT, RPN01 wrote:
> Another point I?ve not seen mentioned, and I?m not sure if it?s true or
not...
>
> Given a dedicated volume to a Linux guest, won?t the guest start only
one I/O
> to the device at a time, and wait for it to complete? If you break up a
large
On Thursday, 03/25/2010 at 12:11 EDT, "Schuh, Richard"
wrote:
> With it not being a full-pack as Mike mentioned in his post, there would
always
> have to be CCW translation, would there not? The question is whether
that is a
> significant hit compared to the full pack including Cyl 0. Consid
There is maybe some misunderstanding: (leaving out PAV a while) a device can
handle only 1 IO at a time, guests know that, CP too. So indeed a linux
will not send a new IO if the previous one to that disk hasn't ended yet,
the guets will queue it. With several guests with minidisks on the same
di
One needs to understand the syntax of a COMDIR entry. In this case, the
syntax is:
: nick.IOASERVR: :Luname.*USERID OSASF
: tpn.IOASERV
means: if a program want to create an APPC connection with "resource"
IOASERVR, CP will not use AVS, nor will it look for an existing, started,
ser
Actually, the REDISP log has contained this information since day zero ..
(shift right)
Eginhard
- Original Message -
From: Kris Buelens
To: IBMVM@LISTSERV.UARK.EDU
Sent: Friday, March 12, 2010 4:24 PM
Subject: Friday gift - Perfkit ULOG
Those with RTM/ESA experience may
Bad news...
Our IBM support that is not IBM... has not the IBM contract to open a PMR for
me... Don't laugh...
If someone here could do it for me...for the community... I would appreciate...
Alain Benveniste
Le 23 mars 2010 à 18:56, Mary Hottenstein a écrit :
> I have recreated the reported
> You know the old virtualization saying, "Never depend on the kindness
> of
> guests."
>
> Alan Altmark
One might be entertaining angels unaware...8-)
And you need to bear in mind that the rules, silly or not, are probably
mandated by state law in this case. Dan's suggestion about the automated FAQ
sent to new subscribers is a good starting point, and Mike's reminder (or one
like it) when there is an occasional breach of conduct is perfectly a
Alan,
With it not being a full-pack as Mike mentioned in his post, there would always
have to be CCW translation, would there not? The question is whether that is a
significant hit compared to the full pack including Cyl 0. Considering that, in
the olden days, CP overhead was quite high compare
Another point I¹ve not seen mentioned, and I¹m not sure if it¹s true or
not...
Given a dedicated volume to a Linux guest, won¹t the guest start only one
I/O to the device at a time, and wait for it to complete? If you break up a
larger volume into several minidisks (like a mod 27 into mod 9¹s) are
On Wednesday, 03/24/2010 at 04:31 EDT, David Boyes
wrote:
> On 3/24/10 3:40 PM, "Alan Altmark" wrote:
>
> > When giving guests access to real cyl 0, I suggest:
> > 1. If using a full-pack mindisk, use the DEVNO version instead of
volser.
> > That way it doesn't matter if the guest changes the
I wrote REXX functions B2C, B2D, B2X, C2B, D2B, and X2B years ago. For example:
/*
C2B
++
||
| C2B(string)
I just used X2B(C2X(substr(result,36,1)))
Frank M. Ramaekers Jr.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Bruce Hayden
Sent: Thursday, March 25, 2010 8:49 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Capping info
Ahh... Fo
Ahh... Forgot that "c2b" was only in the internal Rexx functions
package. So, use Pipes instead:
'PIPE var result | specs 36.1 c2b 1 | var lparchar'
On Thu, Mar 25, 2010 at 9:38 AM, Frank M. Ramaekers
wrote:
> C2B?
>
> 20 +++ lparchar=c2b(substr(result,36,1))
> DMSREX478E Error 43 running STS
C2B?
20 +++ lparchar=c2b(substr(result,36,1))
DMSREX478E Error 43 running STSIX EXEC, line 20: Routine not found
Frank M. Ramaekers Jr.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Bruce Hayden
Sent
STSI can tell you if you are capped, but it can't tell you the weight.
Borrowing from the STSIUSE SAMPEXEC on MAINT 193:
/*
* Logical-partition CPUs*
*
On Thu, Mar 25, 2010 at 4:19 AM, Gabe Goldberg wrote:
> More people likely see these notices here than would on Velocity's Web site,
> so this seems a better place for them. A better solution seems to be for
> people working at companies which think they can censor information their
> employees s
20 matches
Mail list logo