Hi, Bob....
Bob Bolch wrote:
The support for the System Management API servers is enhanced in 5.4.0 to
use this writable saved segment for inter-process communications, rather
than use SFS to communicate between the SMAPI request servers and the worker
machines.
I wonder what prompted them to do that....was something wrong with the SFS
interface?
We tried to convince IBM during the 5.4.0 ESP that it was more appropriate
to statically define the NAMESAVE record for this segment in the source
directory entry configuration files for the SMAPI user IDs and document the
use of that segment, rather than dynamically (and secretly) add it to the
SMAPI user IDs whenever SMAPI was started. They disagreed.
Yes, I can see where that API 'SHARED_MEMORY_ACCESS_ADD_DM' call is made in the code. This
is a problem from my point of view: It's undocumented and it's not clear at all from
the doc that the directory manager *must* be up and running (in order to execute the
'SHARED_MEMORY_ACCESS_ADD_DM' function) before the SMAPI can be employed. This was not the
case in 5.3.
This strikes me as a rather bone-headed design......
Have a good one.
Bob Bolch
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Jones
Sent: Saturday, November 22, 2008 9:58 AM
To: [email protected]
Subject: new VSMDCSS in z/VM 5.4
I was taken a look around a new z/VM 5.4 install, and I've noticed that
there is a new
DCSS: VSMDCSS....I've found that it's created when VSMWORK1 is started,
but that's about
it. It's not documented in the 5.4 publication library; at least a
search for it from the
bookcase returns 0 hits.
What's it for? Thanks.
--
DJ
V/Soft
z/VM and mainframe Linux expertise, training,
consulting, and software development
www.vsoft-software.com
--
DJ
V/Soft
z/VM and mainframe Linux expertise, training,
consulting, and software development
www.vsoft-software.com
