At 08:55 -0400 on 08/31/2006, Bob Shannon wrote about Re: ISV Anchor Table:
If I were doing it, I'd allocate a reasonable size table with room
for expansion (ie: Empty Slots past the currently assigned slot
number). A 4K table, has room for 1024 Slots/ISVs. Even a 1K table has
room for 256
If I were doing it, I'd allocate a reasonable size table with room
for expansion (ie: Empty Slots past the currently assigned slot
number). A 4K table, has room for 1024 Slots/ISVs. Even a 1K table has
room for 256 slots. Either 1K or 2K should be more than enough for the
foreseeable future needs
are the criteria for being allocated an ISV Anchor Table slot?
Presumably it's more than just ask and you'll get one.
Q2) Assuming we meet the criteria what is the process for getting one?
Q3) Assuming a slot was allocated would it be in z/OS 1.8 and above or
could it be retro fitted to earlier
an ISV Anchor Table
slot?
Presumably it's more than just ask and you'll get one.
I am not aware of any specific criteria, but I would assume that a
Partnerworld membership ought to be sufficient. In theory vendors get
exactly one slot in the table, but a few have ended up with more as a
result of MA
could answer.
Q1) What are the criteria for being allocated an ISV Anchor Table slot?
Presumably it's more than just ask and you'll get one.
Q2) Assuming we meet the criteria what is the process for getting one?
Q3) Assuming a slot was allocated would it be in z/OS 1.8 and above or
could
At 09:29 -0400 on 08/30/2006, Craddock, Chris wrote about Re: ISV Anchor Table:
The table is just a contiguous block of SQA allocated during IPL and is
(as far as I know) more than enough to accommodate all of the current
users. If the table needed to expand, I imagine IBM would deliver
service
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Craddock, Chris
[ snip ]
You build your own stuff in a block of common storage
(typically ECSA or ESQA) and place its address in your
designated slot. Once its there you can access your own stuff
from any
I don't know of any
IBM recommended prefixing for the name:token.
As with almost anything, IBM recommends that you begin the name with some
3-character prefix owned by your company/product. And that usually means
to stay away from A-I or SYS (with exceptions of course for prefixes within
A-I
Does anyone know anything about this? A table that is pointed to off the
CVT/ECVT that contains pointers for ISVs to anchor things?
I'd heard something about this in the mid-90s and I've drunk a few beers
since then.
Later,
Steve Thompson
It's called the Customer Anchor Table and it's hung off the ECVT. Any
vendor that requests a slot (FW) can get one.
Bob Shannon
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED]
In a message dated 8/25/2006 1:30:49 P.M. Central Daylight Time,
[EMAIL PROTECTED] writes:
Does anyone know anything about this? A table that is pointed to off the
CVT/ECVT that contains pointers for ISVs to anchor things?
Check the IBM-MAIN archives. Many older posts.
Bill Fairchild
@BAMA.UA.EDU
Subject: Re: ISV Anchor Table
It's called the Customer Anchor Table and it's hung off the ECVT. Any
vendor that requests a slot (FW) can get one.
Bob Shannon
/snip/
--
For IBM-MAIN subscribe / signoff / archive
Thanx to all who answered this.
I'm having a Senior Week. Ok, since I originally did work with this when
it was first announced I've had a few beers to drink. And I just
couldn't remember clearly. [And they want to blame it on us guys/gals
being older than 40!]
Later,
Steve Thompson
At 12:38 -0600 on 08/25/2006, Jeffrey D. Smith wrote about Re: ISV
Anchor Table:
Peter Relson manages the allocation of ISV slots in
table. You only get a fullword slot, so use it wisely.
Which is all you need until you want your table to be in 64-bit
addressable storage (at which point you
In a recent note, Jeffrey D. Smith said:
Date: Fri, 25 Aug 2006 12:38:30 -0600
Peter Relson manages the allocation of ISV slots in
table. You only get a fullword slot, so use it wisely.
Be sure all of your products have a common protocol
for managing it.
ECVTCTBL points to the
ECVTCTBL points to the array of customer anchors.
When is this preferable to name/token services? When is
name/token services preferable? Is there any protocol
such as prefix registration to prevent collisions in
name/token services?
Peter Relson doles out anchor table slots on
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Paul Gilmartin
Sent: Friday, August 25, 2006 3:19 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ISV Anchor Table
In a recent note, Jeffrey D. Smith said:
Date: Fri, 25 Aug 2006 12
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ISV Anchor Table
ECVTCTBL points to the array of customer anchors.
When is this preferable to name/token services? When is name/token
services preferable? Is there any protocol such as prefix
registration to prevent collisions in name/token
18 matches
Mail list logo
