server_MAP_FILE

Similar to DEFAULT_MAP_FILE, this configuration variable lets you specify a map file for use with international character translation. However, this variable specifies a map file for use with a specific server. The map file itself can be stored anywhere.

Note: To increase compatibility with Microsoft Windows, this release of extend delivers or creates configuration files in the following directories, and searches in this order by default:
  • %PROGRAMDATA%\Micro Focus\extend\x.x.x
  • %PROGRAMDATA%\Micro Focus\extend
  • \etc

Where x.x.x is the installed version number of extend.

If the required file is not found in one of the first two listed directories, it searches \etc for backward compatibility.

For example, if you include the following statement in your client application:

CALL "prog2" using my-data.

and your client configuration file includes:

CODE_PREFIX *sun3:/usr/obj *sun4:/usr/obj

then:

sun3_MAP_FILE=%PROGRAMDATA%\Micro Focus\extend\10.5.0\pc_iso_map

causes the map file pc_iso_map to be applied if prog2 is found and run on sun3 but not on sun4. As with DEFAULT_MAP_FILE, you may use AcuServer® remote name notation to point to a map file residing on a remote server running AcuServer.

Note: You can have only one DEFAULT_MAP_FILE variable specified in the client configuration file, but you can have as many server_MAP_FILE variables as you want.