I am getting EIBRESP as 012 when trying to access a remote file. I have checked the file is defined correctly in the local region and is defined remotely in my CICS region. Also checked the definition of the file is same as the it is in production.
Not not sure why CICS is not able to find the file. Is there any access issue which prevents me to find the file.
Joined: 14 Jan 2008 Posts: 2504 Location: Atlanta, Georgia, USA
Do you know the SYSID (REMOTESYSTEM) of this file?
Using CECI from your local region, issue an INQUIRE FILE REMOTESYSTEM.
If EIBRESP is NORMAL, then issue the same without the REMOTESYSTEM and check the EIBRESP value. At screen bottom, the description associated with the EIBRESP will be displayed as well.
Using CEMT from your local region, issue a CEMT INQ FILE.
In the terminal response, place a ? next to the line and press <Enter> for result expansion. You should then be able to view the REMOTESYSTEM that's been defined to the RDO definition (FCT entry). The result should display REM (Remote).
CRTE over to the region where this file actually lives (remote region) and issue a CEMT INQ FILE. The CEMT result expansion should contain the information for this file, such as its characteristics, etc.
Have you brought this to the attention of your CICS System Programmer and/or Tech Support personnel? It could be as simple as validating the REMOTESYSTEM value in the local region RDO definition, which is actually the SYSID of the Remote region.
It could also be as simple as a spelling error (a/k/a a "Fat Finger")