An interesting gotcha comes to mind. A region can be run Short on
Storage by a program in a loop doing Getmain Shared and the only easy
recovery option is to recycle the region (unless the storage is tracked and
the unnecessary storage is freemained--an iffy thing at best in the middle
of an SOS condition--the task may ironically need storage to free
storage--"Catch 22"). If nonshared storage was used--the abend or end of
the task would free the storage--not so with Shared.
----- Forwarded by Joseph Fatula/PHEAA on 04/29/2005 03:33 PM -----
Sent by: CICS CICS-L@LISTSERV.UGA.EDU
Re: Using Shared Memory in CICS
Please respond to
> -----Original Message-----
> From: CICS List On Behalf Of Visser, Michael J (Mike)
> I am exploring the feasibility of using shared memory in CICS.
> What are the pitfalls?
Forgetting to serialize access to it, forgetting to explicitly FREEMAIN it
when done with it ("last task out please turn off the lights").
> Are there reasons not to use shared memory in CICS?
Apart from the "pitfalls", no.
> Other IPC considerations?
I think not.