Q
Problem solve Get help with specific problems with your technologies, process and projects.

Storage-level related failures

I have CICS program-A reading and setting a PTR to File-A and then issue a CALL to CICS Program-B that in turn is reading the same file. When I return from Program-B, the linkage area for just this common 01 level is no longer available and I receive a storage violation when attempting to access it.

Are there any alternatives to resolving this other than removing my 01 level from linkage, eliminating my pointer set during the primary Program-A I/O? Do I need to designate the same area in Program-B or somehow prevent Program-B from releasing the storage? Both Program-A and Program-B are accessing the file as read only. Any information on what I am doing wrong or don't understand would be appreciated.


I don't claim to be any sort of COBOL expert (one of the languages I never got around to learning). However, if you think you are getting COBOL storage-level related failures, then I would abandon the approach of using these COBOL facilities.

I'd just do an XC GETMAIN in the top-level program, do something with that storage, and then just pass the pointer down to the second program.

Robert Harris
Inventor
CICS Technical Strategist -- CICS expert at Search390.com

Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .VO7aaqqaAFk.0@/search390>discussion forums.


Dig Deeper on IBM system z and mainframe systems

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchWindowsServer

SearchServerVirtualization

SearchCloudComputing

Close