> I am re-working code that does a CPOOL DELETE in what *could be* a "cleanup" > type situation where the exact state of things is unknown. Is there a CPID > value (such as zero or minus one) that never occurs in real life that I > could use as an initialization value so that the code "knew" not to issue a > CPOOL DELETE? And that I could set in storage before issuing the DELETE so > that if we came through the cleanup code again we would not issue the DELETE > again and ABEND again? (Yes, I know there are other ways to skin this cat > but I thought I would ask about this way, which is pretty straightforward if > indeed it is feasible.)
In the current implementation of CPOOL (and since its inception in MVS/XA), the CPID is an address of some storage in the subpool of the cell pool. So with this implementation, there are many CPID values that never occur. While it seems unlikely that this implementation would change after 35 years, there are no guarantees. The CPOOL documentation says nothing about possible values for CPID, and without a change to this documentation to define a CPID value which never occurs, I would not recommend making any assumptions in your code. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
