The EZASOKET configuration file (EZACONFG) is a VSAM file that contains details of CICS regions (that is, enterprise servers capable of running CICS applications) and the CICS listeners within those regions. The file can be shared by multiple enterprise servers.
The EZACONFG file is a VSAM file with an associated FCT entry. After adding DFHEZA group to your region startup list, running EZAC transaction will create the file for the associated FCT entry if the file does not exist.
The file's actual location and name used by your Enterprise Server are governed by an EZACONFG FCT entry, which resolves to a physical file exactly as any other FCT entry (such as via a catalog DSN entry, to an explicit file path and filename, or to the default File Path and name EZACONFG).
For each CICS region that supports EZASOKET and is controlled by the configuration file, there is an associated object (referred to as a CICS object) in the configuration file. The object is identified by the APPLID of the CICS region. There is also a listener object for each listener defined for a CICS region.
The first task you will perform is to use the EZAC transaction to define a CICS object in the configuration file for your CICS region. If the configuration file does not exist, EZAC will create it.
In an out-of-the-box IVP installation, the Map Path field in the configuration is blank, so CICS will use the default map directory. That default map directory is where the EZACICM.MOD file is located. This path does not have to be set explicitly in an out-of-the-box install.
However, it is quite common to set a different Map Path when customizing Enterprise Server regions, to add directories where customer application map files are kept. If that is done, you may have to explicitly add the default directory to ensure EZACICM.MOD is found. The Enterprise Server will find the system directory with its EZACICM.MOD file after it finds the customer directory with its EZACICM.MOD file, so you may have to place the directory containing the EZACICM.MOD file so that it is found first.
It is preferable to rename the application files to avoid conflicts if possible.