I am testing with a file in CICS which is currently allocated to local test region and its attributes when inquired (CEMT I <file name>) shows
VSA OPE ENA REA etc., with VSA being enabled. I need to change this access method to REM (Remote) as it is in production for the same file. I googled a lot and i even tried to find a resolution in this forum's old topics but could not do so. Could any one of you please let me know any solution for this. Also let me know if you need any more information on this. Thanks.
Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
AFAIK, you cannot change a file from local to remote via CEMT. You must use CEDA to do this; most applications programmers do not have authority to use CEDA (with good reason). Contact your site CICS support group to get your file changed.
Joined: 14 Jan 2008 Posts: 2504 Location: Atlanta, Georgia, USA
You need to define a REMOTE FCT entry in the current LOCAL region, which specifies the target SYSID (the region where the file will remotely reside). Actually, you could modify the current FCT entry and that would work. Then, in the new Remote region, define a LOCAL FCT entry, without the SYSID.
Do your application programs specify the KEYLENGTH in their FILE API's? If they do, then there aren't any worries. But, if they don't, they you need to specify the KEYLENGTH of the file, in both the REMOTE and LOCAL FCT entries, due to Function Shipping of the request to the new Remote region. Otherwise, an INVREQ will be raised by the given program, whenever a FILE API is issued, which requires the KEYLENGTH option, targeting this newly defined REMOTE file. IMHO, it is always a good idea to specify the KEYLENGTH in a FILE API which requires it, because if (as in your case), the file becomes REMOTE, then you don't have to worry about specifying the FCT KEYLENGTH as the KEYLENGTH will be automatically shipped for the REMOTE FILE API.
If by chance (a heads-up), you're running CICS/TS 3.2 and have applied the PTF, which allows VSAM to be Locally Threadsafe, the Threadsafe VSAM compliance goes away for Remote VSAM.
To make a long story short, in order to view the characteristics of a Remote file, you need to logon directly to the Remote region. Then, your CEMT FIL command will work as advertised.
Is there a need for an application program in a given AOR to CLO/OPE this newly defined Remote File?
Because (AFAIK), the SET FILE API is for Local files only, so keep this in mind.