Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Customer Anchor Table (was: WTO)
196 views
Skip to first unread message
Peter Relson
Dec 4, 2019, 8:18:33 AM12/4/19
to
I think that ECVTCTB2 was mentioned at a technical disclosure meeting in
Pok with the ISVs several years ago.
Regardless, this is the wording that I now provide upon "assignment" of a
slot (with nnn, xxx, yyy, zzz filled in) describing what that assignment
"gets you", and it applies to existing assignments as well:
I have assigned slot nnn to yyy.
These are the 4 bytes at offset zzz in the area pointed to
by ECVTCTBL.
You also "automatically" get entry nnn in the CICS Vendor Anchor
Table. For that, you use invocations such as
DFHKEVAT SETSLOT|GETSLOT,INDEX=nnn
If this is of interest to your company,
to get the macros, send a note to CIC...@UK.IBM.COM and request
to be a participant of the Early Test Program (ETP).
If not IBM,
As of z/OS 2.3 (not earlier releases) you also get slot
nnn (field FXEFRAT_SLOT_nnn) in the z/OS Function Registry
mapped by macro FXEFR in the area pointed to by XCVT_FRAT.
As of z/OS 2.3 (not earlier releases) you also get 8-byte slot
nnn in the area pointed to by ECVTCTB2 (the 8 bytes at offset
x'yyy')
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@listserv.ua.edu with the message: INFO IBM-MAIN
Pok with the ISVs several years ago.
Regardless, this is the wording that I now provide upon "assignment" of a
slot (with nnn, xxx, yyy, zzz filled in) describing what that assignment
"gets you", and it applies to existing assignments as well:
I have assigned slot nnn to yyy.
These are the 4 bytes at offset zzz in the area pointed to
by ECVTCTBL.
You also "automatically" get entry nnn in the CICS Vendor Anchor
Table. For that, you use invocations such as
DFHKEVAT SETSLOT|GETSLOT,INDEX=nnn
If this is of interest to your company,
to get the macros, send a note to CIC...@UK.IBM.COM and request
to be a participant of the Early Test Program (ETP).
If not IBM,
As of z/OS 2.3 (not earlier releases) you also get slot
nnn (field FXEFRAT_SLOT_nnn) in the z/OS Function Registry
mapped by macro FXEFR in the area pointed to by XCVT_FRAT.
As of z/OS 2.3 (not earlier releases) you also get 8-byte slot
nnn in the area pointed to by ECVTCTB2 (the 8 bytes at offset
x'yyy')
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@listserv.ua.edu with the message: INFO IBM-MAIN
scott Ford
Dec 4, 2019, 12:40:25 PM12/4/19
to
Peter,
Thank you for the explanation. I understand the Customer anchor table you
mentioned above.
Scott
--
*IDMWORKS *
Scott Ford
z/OS Dev.
“By elevating a friend or Collegue you elevate yourself, by demeaning a
friend or collegue you demean yourself”
www.idmworks.com
scott...@idmworks.com
Blog: www.idmworks.com/blog
*The information contained in this email message and any attachment may be
privileged, confidential, proprietary or otherwise protected from
disclosure. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, distribution, copying or
use of this message and any attachment is strictly prohibited. If you have
received this message in error, please notify us immediately by replying to
the message and permanently delete it from your computer and destroy any
printout thereof.*
Thank you for the explanation. I understand the Customer anchor table you
mentioned above.
Scott
*IDMWORKS *
Scott Ford
z/OS Dev.
“By elevating a friend or Collegue you elevate yourself, by demeaning a
friend or collegue you demean yourself”
www.idmworks.com
scott...@idmworks.com
Blog: www.idmworks.com/blog
*The information contained in this email message and any attachment may be
privileged, confidential, proprietary or otherwise protected from
disclosure. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, distribution, copying or
use of this message and any attachment is strictly prohibited. If you have
received this message in error, please notify us immediately by replying to
the message and permanently delete it from your computer and destroy any
printout thereof.*
0 new messages