Off the top of my head - here are a few alternatives to the system level
name/token approach :
(1) Anchor your product in a slot in the "customer table" pointed to by
ECVTCTBL - this is a technique used by many ISVs who have reserved one or more
slots with IBM (Peter Relson is the "guardian" of the slots IIRC).
- If this is just an in-house utility, then this is probably overkill
- Very efficient process to find the slot - maybe six instructions or
so?
(2) Hang the anchor address off SSCTSUSE or SSCTSUS2 for a subsystem entry
This is easily done - however if you are a shop with many subsystems it
might be prohibitive to keep performing a sequential search of the SSCT chain
each time you need to find the anchor
(3) Your STC holds an system enqueue for an agreed QNAME - you stick the anchor
in the RNAME and use ISGQUERY to find it
Not as efficient as system level name/token - however the big advantage
over other methods of being possible to achieve in problem state code.
Rob Scott
Lead Developer
Rocket Software
77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA
Tel: +1.781.684.2305
Email: [email protected]
Web: www.rocketsoftware.com
-----Original Message-----
From: IBM Mainframe Assembler List [mailto:[email protected]] On
Behalf Of Scott Ford
Sent: 10 April 2013 16:09
To: [email protected]
Subject: Re: Storage and Tokens
Sam,
This is more or less what we do
Sorry let me explain...
The code i am referring to was written in 2002 not that is bad. But it wasnt
well thought out because of time.
Here is in a nutshell what happens:
1. STC ( written in Cobol with assembler subroutines ) starts up , btw its AC=1
(TCPIP server) a. Allocates storage b. Inserts a Token after a good RC from (a)
c. Waits for incoming messages d. Once a message arrives ( the STC polls - a -
) e. The message is read and processed.
The messages are generated via a RACF exit ..
Scott J Ford
Software Engineer
http://www.identityforge.com/
________________________________
From: Sam Siegel <[email protected]>
To: [email protected]
Sent: Wednesday, April 10, 2013 10:54 AM
Subject: Re: Storage and Tokens
Scott - I guess it depends on who needs to access the data and how they access
it? Same address space? Different address space? Serialization requirements?
Etc.
Sam
On Wed, Apr 10, 2013 at 7:23 AM, Scott Ford <[email protected]> wrote:
> All:
>
> I have a storage related Assembler question, currently we :
>
> 1. Do a Storage Obtain in Key=0
> 2. Using IEANTCR insert a 16 byte storage token 3. Add data to this
> area upon finding the token - IEANTRT 4. Read data from this area
> upon finding the token - IEANTRT
>
> Is there another way , better ?
>
> Scott J Ford
> Software Engineer
> http://www.identityforge.com/
>
