Joined: 14 Jan 2008 Posts: 2504 Location: Atlanta, Georgia, USA
Is the KSDS file defined to individual regions or is it defined to a single "FOR" (File Owning Region), where all requests are Function Shipped from a given "AOR" (Application Owning Region)?
If you're dealing with individual AOR's, the UPD characteristic/keyword can only be present in one of the individual AOR's FCT entry.
This is the benefit of having a centralised "FOR" and if you don't have a "FOR", don't go messing with the SHROPTIONS, because that would be your Waterloo. For integrity, leave them as (2,3).
However, if you define the KSDS file as UPD in one of the individual regions (we'll name it the Home region for this example), then the remaining regions could treat the Home region (where it's defined with UPD capability) as a combined "AOR"/"FOR".
The FCT's in the remaining "remote" regions must include the REMOTE CHARACTERISTICS keywords, as well as the KEYLENGTH, which then allows Function Shipping requests to the Home region.
If the actual program which attempts to access the KSDS file remotely and the file API does NOT specify a KEYLENGTH and the KEYLENGTH keyword is NOT populated in the FCT entry, an INVREQ (EIBRESP=16) will be raised. Function Shipped file requests do NOT pass the KEYLENGTH to the target (Home) region.
Speak to your CICS System Programmer and/or Tech Support Group personnel about what you're trying to accomplish. I'm sure they'll be able to accommodate your request.
An issue you may face is when the Home region is down, but the other regions are still up. When the Home region is down, you won't be able to update the file. You'll only be in "Read Only" mode and this will affect your remote regions FCT entries. They would need to be changed on the fly to remove the REMOTE CHARACTERISTICS so any access would default to local.