This sort of thing would probably make an interesting Share presentation - not
so much the SRB back into the user ASID but a more generic "Use PC-ss to add
request to a server address space to do something and get the results back".
There is lots of good stuff here :
(o) LXxxx, ATxxx and ETxxx macros
(o) Setting up PC-ss correctly with some sort of authorization
methodology (eg SAF)
(o) Usage of System-LX versus non-system LX
(o) How to maintain system integrity when dealing with input from
client caller and returning results
(o) Queue management in a multi-task mult-ASID environment
(o) Suspend/Resume services
(o) Resource manager routines and dealing with clients and servers that
"go away"
There are (I imagine) quite a few ISV developers who could do this justice -
however having the time to prepare the presentation and sample code is probably
what prevents it.
Rob Scott
Lead Developer
Rocket Software
275 Grove Street * Newton, MA 02466-2272 * USA
Tel: +1.617.614.2305
Email: [email protected]
Web: www.rocketsoftware.com
-----Original Message-----
From: IBM Mainframe Assembler List [mailto:[email protected]] On
Behalf Of McKown, John
Sent: 14 February 2011 14:03
To: [email protected]
Subject: Re: Sample code for PC-ss with SRB back to user space?
There seems to be less sharing of "system level" code today when compared to
the "days of yore". Part of it may be that the interfaces today are much more
difficult and so there are fewer who truly understand them. Or because the
knowledge itself is now considered "Intellectual Property" and must be
restricted and "monetized". Or maybe because people are afraid that some nitwit
will end up suing them when they can't get something to work and need a
scapegoat. Today's society is "nastier" than the past about this sort of thing.
Hopefully, the main reason is the first one. This whole thing is why I love
Linux and FOSS in general.
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
[email protected] * www.HealthMarkets.com
Confidentiality Notice: This e-mail message may contain confidential or
proprietary information. If you are not the intended recipient, please contact
the sender by reply e-mail and destroy all copies of the original message.
HealthMarkets(r) is the brand name for products underwritten and issued by the
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The
MEGA Life and Health Insurance Company.SM
> -----Original Message-----
> From: IBM Mainframe Assembler List
> [mailto:[email protected]] On Behalf Of Farley,
> Peter x23353
> Sent: Monday, February 14, 2011 7:47 AM
> To: [email protected]
> Subject: Sample code for PC-ss with SRB back to user space?
>
> The recent discussion of the commanality of vendor code that
> sets up an STC which runs in privileged mode and also
> supplies a subroutine or API for a user address space TCB
> program to use PC-ss to "call" that STC, which then may
> schedule an SRB to run back in the calling address space to
> accomplish the vendor's purpose brought back a question I
> have had for some time:
>
> Why isn't there any good sample code available showing how to
> do this? Or have I just not looked hard enough to find it?
>
> Such code is certainly expert-level stuff, but as a
> soi-disant assembler expert I would love to have the option
> of using that tool where it would be appropriate. Figuring
> out all the nuances and pitfalls of this technique from
> scratch seems to me to be a counter-productive use of scarce time.
>
> Peter
> --
> This message and any attachments are intended only for the
> use of the addressee and
> may contain information that is privileged and confidential.
> If the reader of the
> message is not the intended recipient or an authorized
> representative of the
> intended recipient, you are hereby notified that any
> dissemination of this
> communication is strictly prohibited. If you have received
> this communication in
> error, please notify us immediately by e-mail and delete the
> message and any
> attachments from your system.
>
>
>
