Chip, does ooREXX support PIPES?
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Chip Davis
Sent: Friday, December 17, 2010 11:10 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Mandatory ESMs?
At the risk of ignoring his assertion about
Hi, Stephen.
If you mean CMS Pipelines, the answer is no, simply because ooRexx has
not yet been ported to CMS.
DJ
On 12/20/2010 09:35 AM, Gentry, Stephen wrote:
Chip, does ooREXX support PIPES?
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]
We've always avoided using PAV volumes for general user (non-fullpack) CMS
minidisks. Instead we've only used DASD defined as 3390-3 so that I/O
queueing is minimized. That choice was in part due to management
decisions.
Over the past weekend we needed to move some z/VM DASD quickly -- and
Why would you NOT want PAV for CMS mds?
The IO Supervisor has not kept up with the hardware.
It still thinks of a disk device as a spinning platter when in fact it
is a rank of RAID devices striped over numerous HDs and cached in a disk
controller from where it is actually being read thereby
CMS IO can indeed profit from PAV: CP knows how to look at PAV aliases when
a disk is busy.
SFS is another story: the SFS SW knows where its minidisks are located. It
will not attempt to launch an IO to a volume to which it has an active IO.
So: if you have multiple SFS servers on a given PACK,
Thanks, Kris.
I knew about SFS (we dedicate whole volumes to individual SFS filepools
and their servers, with no volumes shared by servers), and DB2 (tho we
don't use DB2 on z/VM).
To answer George's question about why not?...'
PAV first became available for z/VM CMS mdisk use with z/VM 5.2.
One question, is the DASD subsystem you are on shared with z/OS systems
(running outside of z/VM). We have used PAVs for several years for our z/OS
systems. We have gone from what is called WLM managed PAV to HyperPAV. I have
avoided using PAVs for our z/VM lpars because I was not sure how
Mike,
We use PAV for volumes containing CMS minidisks. We turned it on a few months
ago on a system that we acquired with our last merger, and the user was quite
pleased. It took a couple of hours off of their nightly batch. PAV is also on
for volumes that contain SFS minidisks. It doesn't
Did you try the smsg command to turn on tracing? I did this and got a
trace file:
Ready;
smsg ftpserve trace on file
Ready;
15:08:48 FTPSERVE: Tracing to file has been
A little teaser (coming soon)
From a CMS prompt:
ssh root a.b.c.d ls -l
SSHCMS v0.2.1
Password:
total 130348
-rw-r--r-- 1 root root 982 Sep 24 11:38 anaconda-ks.cfg
-rw-r--r-- 1 root root 132206592 Nov 25 00:02 install.img
-rw-r--r-- 1 root root 68582 Sep 24 11:38
scpcms r...@a.b.c.d:install.log INSTALL.LOG
SCPCMS v0.2.1
Password:
Receiving:
INSTALL.LOG (68582 bytes):
|**| 8 kB
|**| 16 kB
|**| 24 kB
|**| 32 kB
|*
David,
I'd be very interested to hear more about this. Keep me up to date!
Thanks,
Kyle Black
On Mon, Dec 20, 2010 at 4:24 PM, David Boyes dbo...@sinenomine.net wrote:
A little teaser (coming soon)
From a CMS prompt:
ssh root a.b.c.d ls -l
SSHCMS v0.2.1
Password:
total
Server, too ? (Although I'm not sure how one'd manage 3270 over ssh :-)
-- Pat
On 12/20/10 3:24 PM, David Boyes wrote:
A little teaser (coming soon)
From a CMS prompt:
ssh root a.b.c.d ls -l
SSHCMS v0.2.1
Password:
total 130348
-rw-r--r-- 1 root root 982 Sep
Excellent! On both counts!
On 12/20/2010 03:26 PM, David Boyes wrote:
scpcms r...@a.b.c.d:install.log INSTALL.LOG
SCPCMS v0.2.1
Password:
Receiving:
INSTALL.LOG (68582 bytes):
|**| 8 kB
|**| 16 kB
|**
On Monday, 12/20/2010 at 12:03 EST, George Henke/NYLIC
george_he...@newyorklife.com wrote:
Why would you NOT want PAV for CMS mds?
The IO Supervisor has not kept up with the hardware.
It still thinks of a disk device as a spinning platter when in fact it
is a
rank of RAID devices
15 matches
Mail list logo
