View previous topic :: View next topic
|
Author |
Message |
koteswara
New User
Joined: 23 Sep 2009 Posts: 22 Location: Bangalore
|
|
|
|
Hi,
Please could you let us know how the data is exchanged between 2 CICS Regions.
Is there any limitation for the Commarea with respect to size if we are using this between the regions.
Thanks in advance !! |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
The limit on the length of DFHCOMMAREA does not change just because you are doing something different -- it is an absolute limit, not a relative one. |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
Isn't DFHCOMMAREA used for passing information between applications in 1 CICS region?
TS is talking about 2 CICS regions sharing info, in that case maybe CICS SPOOL is a solution? |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
|
|
commarea CAN be used to pass data between the same or different CICS regions , size is max of 32767 |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
From the CICS Application Programming Reference manual, section 1.205:
Quote: |
The valid range for the COMMAREA length is 0 through 32 763 bytes. If the length provided is outside this range, the LENGERR condition occurs. |
Elsewhere IBM recommends no more than 24K. |
|
Back to top |
|
|
koteswara
New User
Joined: 23 Sep 2009 Posts: 22 Location: Bangalore
|
|
|
|
Thanks for the response.
Is it possible to access the same address for 2 CICS Regions. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Each CICS region has its own address space. The same memory address certainly exists in both regions -- but since each is separate, the memory may be used for two totally different things. Passing an address from one region to another and expecting to get anything other than a storage violation is not a valid expectation. |
|
Back to top |
|
|
|