Joined: 07 Mar 2007
|I have a programme (say C) which writes to CWA.
Programme C is being called by programme B and Programme B is being called by prog A.
A -> B -> C (writes to CWA)
From my initial analysis i came to know its the EXECKEY attrib paramter while defining prog B which needs a change, change to CICS from the default USER. Still it failed, but worked when i changed the KEY of prog A as well to CICS.
1. Does all attribute paramemter of all the programmes in the flow leading to Prog C need to be changed?
2. I wonder if this is real issue? As the same programme works with EXECKEY as USER (for Prog A and B) in Prod. (Cics version in Prod is 3.1 whereas in test where it failed is 5.1). Does it got something to do with the version?
3. I as well don't understand where do we see CWAKEY parameter can be seen for my application region.
Joined: 14 Jan 2008
Location: Atlanta, Georgia, USA
Ask your System Personnel about the CWA's "Execution Key".
Or, if you'd like, review the following excerpt. The "CWAKEY" is a parm which can be specified in the CICS System Initialization Table (SIT), which is maintained (hopefully) by your System Personnel.
The CWAKEY system initialization parameter specifies the storage key for the
common work area (CWA) if you are operating CICS with storage protection
You specify how much storage you want for the CWA on the WRKAREA
parameter. The permitted values are USER (the default), or CICS:
USER CICS obtains storage for the CWA in user key. This allows a user
program executing in any key to modify the CWA.
CICS CICS obtains storage for the CWA in CICS key. This means that only
programs executing in CICS key can modify the CWA, and user-key
programs have read-only access.
If CICS is running without storage protection, the CWAKEY parameter is
ignored, and the CWA is always allocated from CICS-key storage.
User Storage is sometimes referred to as Key 9, whereas, CICS Storage is sometimes referred to as Key 8.
Welcome to the forum....