Mike,
I understand as we are a CMS application shop. But the CMS DCSSes
(CMSPIPES, CMSVMLIB and INSTSEG) are loaded at IPL CMS time by SYSPROF:
'SEGMENT LOAD PIPES ( SYSTEM'
'SEGMENT LOAD RXSOCKET ( SYSTEM'
'SEGMENT LOAD VMLIB ( SYSTEM'
CMSFILES is only used by the SFS SVMs.
SVM is used mostly by the DFSMS SVMs (OK, and maybe VM:Operator and
VM:Tape)
Kris' comment and my response were strictly for the CMS DCSSes; not
other application DCSSes.
So, I do not see why do you need to reserve any of the CMS DCSSes for
NOMAD. NOMAD's DCSS is another story.
Jim
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Walter
Sent: Thursday, May 10, 2007 12:26 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Testing new CMS / CMS components
Jim,
We still need SEGMENT RESERVE to ensure that applications do not
allocate into storage which is required by NSSes. For example, Nomad2
here loads at 05A00-05CFF. We've had applications allocated into that
area, then when the user tried to start Nomad, no luck. Finding out
which application allocated storage into a given area is tricky
business. Getting it unallocated (without just IPLing CMS) is
near-impossible.
So, unless I'm missing something, you're just betting that no
apps (even CMS) will allocate storage, and leave it allocated, before
some NSS attempts to load. You gun, your foot. Of course z/VM
customers running Linux, and with no (yet) CMS workload will not be
faced with this issue. It's only us old productive dinosaur CMS-app
shops that care.
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not
necessarily represent the opinions or policies of Hewitt Associates.
"Stracka, James (GTI)" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
05/10/2007 10:51 AM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Testing new CMS / CMS components
Kris,
I have not seen a need for the SEGMENT RESERVE command with our
z/VM systems. The last time we needed to do this was about 10 years ago
with reserving VSAM for NetView. This is no longer necessary.
We also used commands like:
SET SYSNAME GCSVSAM CMSVSAM
SET SYSNAME GCSBAM CMSBAM
Jim
-----Original Message-----
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens
Sent: Thursday, May 10, 2007 11:41 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Testing new CMS / CMS components
I've got a similmar tool/way of working, since VM/SP Rel 6. Look
at
http://www.vm.ibm.com/download/packages/descript.cgi?IPLER
<http://www.vm.ibm.com/download/packages/descript.cgi?IPLER>
The thing I can't resolve is that when user's code e.g. SEGMENT
RESERVE SCEE in the their PROFILE EXEC, and I plabe they should use
SCEE22 for the z/VM 5.2 CMS (and corresponding entries in SYSTEM SEGID)
In the VM/XA days there have been plans for a CP command to
assign alternate names to NSSes. That would have easily solved the
issue.
--
Kris Buelens,
IBM Belgium, VM customer support
_____
If you are not an intended recipient of this e-mail, please
notify the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it. Click here
<http://www.ml.com/email_terms/> for important additional terms relating
to this e-mail. http://www.ml.com/email_terms/
<http://www.ml.com/email_terms/>
_____
_____
The information contained in this e-mail and any accompanying
documents may contain information that is confidential or otherwise
protected from disclosure. If you are not the intended recipient of this
message, or if this message has been addressed to you in error, please
immediately alert the sender by reply e-mail and then delete this
message, including any attachments. Any dissemination, distribution or
other use of the contents of this message by anyone other than the
intended recipient is strictly prohibited.
