Once you created the name tokennpair you cant modify it. So first get the
storage. Now that you have the address create a name token while pointig to
a 16 bytes area you stored the address .  This is what we do in IronSphere
at Ipl using a subsystem. Later callers can acesys the global block of
parameters.

ITschak

בתאריך יום א׳, 3 במרץ 2019, 21:17, מאת scott Ford ‏<[email protected]>:

> All:
>
> I have a storage related question. I need a running program (STC) to
> allocate a piece of storage that has persistence. By this I mean when the
> STC shutdowns the storage is still there and available.  The storage is an
> area we want to use to store Global options for some of our code running. I
> understand I can use the ECVT but we are trying to have the STC start and
> based on control parameters store global variables for use in other
> programs later, in this case an exit. I want to make sure the Global
> storage is protected and can not be overriden. I know there is no
> guarantees but I want to be 95% sure.
>
>  Does this mean I place a IEANTCR token pointing to a piece of storage in
> SP 229,230, 249 and then do an 'Storage Obtain' for the required storage
> and populate it. This where I am a tad confused, its not the concerns its
> the technique i need to understand. Can someone be so kind as to help me
> out with a bit of an explanation or is there a better way ? I had thought
> of a Dataspace but persistence is an issue and the STC is written in
> Cobol...So i can use hiperspaces unless I write a routine to go from 31bit
> to 64bit and additionally I am not sure if I can use 64bit storage in an
> exit.
>
> --
>
>
>
> *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
>
> [email protected]
>
> 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.*
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to