@LISTSERV.UARK.EDU
08/19/2009 04:57 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Extension of MAINT 190 (S-DISK)
The not rusty IBM products are installed with VMSES, meaning a VMSES
PARTCAT is maintained on each
On 8/19/09 5:57 PM, Kris Buelens kris.buel...@gmail.com wrote:
If you invent your own product IDs, you can even catalog your own files when
copied to 19E. With a new release, VMFCOPY can be used to copy all files of a
given product ID from the old to the new 19E. That's what I did to store
@LISTSERV.UARK.EDU
08/20/2009 12:53 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Extension of MAINT 190 (S-DISK)
On 8/19/09 5:57 PM, Kris Buelens kris.buel...@gmail.com wrote:
If you invent your own product IDs, you can
On 8/20/09 1:15 PM, Bill Munson william.mun...@bbh.com wrote:
I think Jim goes into it briefly with this presentation - a follow up to
9117
9118 - Servicing and Maintaining z/VM with VM/SES - Live Demo
I've seen a previous version of this -- it covers how to apply pre-packaged
service and
190 (S-DISK)
On 8/20/09 1:15 PM, Bill Munson william.mun...@bbh.com wrote:
I think Jim goes into it briefly with this presentation - a follow up to
9117
9118 - Servicing and Maintaining z/VM with VM/SES - Live Demo
I've seen a previous version of this -- it covers how to apply
pre
Can you explain some more regarding the this process and how to set it up.
Here's the high-level version:
1) Create a PRODUCTS userid and create a reasonably large minidisk at a
known address (I use 31A for historical reasons - it was used in VM/IPF as the
shared tools disk). You
The not rusty IBM products are installed with VMSES, meaning a VMSES PARTCAT
is maintained on each minidisk that received files, and this since VM/SP Rel
6. These PARTCATs have fmode 1, meaning they are invisible on 190 and 19E
unless you perform your own ACCESS command (like ACCESS 190 T).
You
: Extension of MAINT 190 (S-DISK)
To: IBMVM@LISTSERV.UARK.EDU
Date: Monday, May 19, 2008, 10:47 AM
Thank you for this hint. Well I am also much more in favour to do the
installation on a separate disks, however in my case IBM install
instructions of the SDO (Semi-VMSES/E Licenced Products) tell
Kris,
I would also be interested in SESCOMP.
Regards,
Fox
On Mon, 19 May 2008 18:09:43 +0200, Kris Buelens [EMAIL PROTECTED]
wrote:
You forget the VMSES PARTCAT: I've got entries in VMSES PARTCAT for
all the things I store on 19E, even y own code gets a dummy prodid.
VMFCOPY can then be
Dear all,
What is the correct procedure for extending the MAINT 190 (S-Disk)? My MA
INT
190 is 82% full and I would like to prepare myself for the case of extend
ing
it. It can be that we install some products (like DCF) that reside on the
S-Disk.
Is allocation of a new mini disk and a DDR
On Mon, 19 May 2008 14:43:09 +0200, Rob van der Heij [EMAIL PROTECTED]
wrote:
OK thank you, correct. But then I would like to extend the question with
regard of the Y-Disk. Is a simple CMS copy enough or is special attention
needed.
Fox
On Mon, May 19, 2008 at 2:38 PM, Fox Blue [EMAIL
Extending the S-disk is seldom done, because not that easy. Most
people would place extra
products on the Y-disk (19E), or yet another disks, accessed by
SYSPROF. But, if you insist:
- FORMAT the new minidisk e.g. as B
- FORMAT newcuu B nnn (RECOMP
makes room for the CMS nucleus, nnn is the
On Mon, May 19, 2008 at 2:38 PM, Fox Blue [EMAIL PROTECTED] wrote:
it. It can be that we install some products (like DCF) that reside on the
S-Disk.
One does not normally install those on the S-disk but on the Y-disk.
(the S-disk is being DDR-ed from the 490)
Rob
Kris,
thank you very much for the info. Focusing now on Y-DISK. Is a simple cop
y
of the files enough after formating the new Y-DISK or are there onher pit
falls?
Fox
Extending the S-disk is seldom done, because not that easy. Most
people would place extra
products on the Y-disk (19E), or
: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Fox Blue
Sent: Monday, May 19, 2008 8:00 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Extension of MAINT 190 (S-DISK)
Kris,
thank you very much for the info. Focusing now on Y-DISK. Is a simple
cop= y of the files enough after
On Mon, May 19, 2008 at 2:47 PM, Fox Blue [EMAIL PROTECTED] wrote:
OK thank you, correct. But then I would like to extend the question with
regard of the Y-Disk. Is a simple CMS copy enough or is special attention
Since the Y-disk FST's are also kept in the CMS NSS, you need to save
CMS again
, and
constantly resaving the CMS minidisk FST's in NSS.
-Mike
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Rob van der Heij
Sent: Monday, May 19, 2008 9:17 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Extension of MAINT 190 (S-DISK)
On Mon, May 19
Hi Mike,
Thank you for this hint. Well I am also much more in favour to do the
installation on a separate disks, however in my case IBM install
instructions of the SDO (Semi-VMSES/E Licenced Products) tell to install
it
on MAINT 19E. Therefore I do it in the recommended way but only for IBM
Don't forget to do all this for your 490 minidisk as well, as there are
several processes that assume that 490 and 190 are very similar
--
Robert P. Nix Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844 Rochester, MN 55905 /( )\
Thank you for this hint. Well I am also much more in favour to do the
installation on a separate disks, however in my case IBM install
instructions of the SDO (Semi-VMSES/E Licenced Products) tell to
install
it
on MAINT 19E.
Save yourself a lot of pain. Don't. Mixing stuff up on the 19E is
We remove the Shared S or Y-stat not available messages for all
end-users; as sysprogs, we still see them.
Futhermore, our saved segment managing machine checks daily for
unshared S- or Y-stat too and -if unshared- it will resave CMS when
there are fewer than 4 copies of the CMS NSS. Similar:
You forget the VMSES PARTCAT: I've got entries in VMSES PARTCAT for
all the things I store on 19E, even y own code gets a dummy prodid.
VMFCOPY can then be used to copy all files of a prodid. And, I
wouldn't be me if I hadn't coded an exec to help with the task: my
SESCOMP first compares
In a previous life, we consistenly modified SYSPROF EXEC
to conditionally access 319 and 31A (and 19F). If they were missing:
no prob, and no error. But most users got them. We then plunked
various third party packages (or stubs) onto these disks.
The value of this was that users might trash
23 matches
Mail list logo
