Server mapping enables the RPC server to correctly support special COBOL syntax such as
REDEFINEs, SIGN LEADING and OCCURS DEPENDING ON clauses,
LEVEL-88 fields, etc.
If one of these elements is used, the IDL Extractor for COBOL automatically extracts a
server mapping file in
addition to the IDL file (interface definition language).
Also, the COBOL Wrapper may generate a server mapping file for RPC server generation.
The server mapping is used at runtime to marshal and unmarshal the RPC data stream.
There are client-side mapping files (EntireX Workbench files with extension .cvm) and server-side mapping files
(Workbench files with extension .svm).
If you have not used server-side mapping, we recommend you use client-side mapping. See Server Mapping Files for COBOL in the EntireX Workbench documentation. This document covers the following
topics:
Check if a Server-side Mapping File Revision has been Deployed
Is There a Way to Smoothly Introduce Server-side Mapping Files?
See also Source Control of Server Mapping Files | Comparing Server Mapping Files | When is a Server Mapping File Required? | Migrating Server Mapping Files in the EntireX Workbench documentation.
Deploy a server-side mapping file (Workbench file with extension .svm) to the RPC server manually. See Server Mapping Files for COBOL in the EntireX Workbench documentation.
To deploy a server-side mapping file
Make sure the server-side mapping container (directory or folder) is configured. See Server-side Mapping Files in the RPC Server.
Copy the server-side mapping file to the server-side mapping container.
Undeploy a server mapping file (Workbench file with extension .svm) from the RPC server manually. See Server Mapping Files for COBOL.
To undeploy a server-side mapping file manually
Delete the server-side mapping file from the server-side mapping container (directory or folder). See Server Mapping Files for COBOL.
Under UNIX and Windows, change management for a directory or folder (server-side mapping container, see Server-side Mapping Files in the RPC Server) is similar to change management within ordinary operating system directories (folders). All updates to the directory or folder done after a backup must be kept.
All EntireX Workbench server-side mapping files (.svm) added since the last backup should be available. See Server Mapping Files for COBOL in the EntireX Workbench documentation.
Use the Windows Explorer or the UNIX ls command to list the contents of the server-side mapping container (directory or folder). See Server-side Mapping Files in the RPC Server.
Server-side mapping files in the server-side mapping container correspond to EntireX Workbench files with extension .svm (same format). See Server Mapping Files for COBOL in the EntireX Workbench documentation. Each line relates to an IDL program and contains a creation timestamp at offset 276 (decimal) in the format YYYYMMDDHHIISST. Precision is 1/10 of a second. The creation timestamp can be checked.
The timestamp can be found on the same offset in the server-side mapping files stored in the server-side mapping container (directory or folder). See Server-side Mapping Files in the RPC Server.
All EntireX RPC servers can be executed without server-side mapping files. See Server-side Mapping Files in the RPC Server. There is no need to install the server-side mapping container if the following conditions are met:
You do not use features that require server mapping; see When is a Server Mapping File Required?
Server-side type of COBOL mapping is switched on in the EntireX Workbench. If you have not used server-side mapping, we recommend you use client-side mapping. See Server Mapping Files for COBOL.
You can also call COBOL servers generated or extracted with previous versions of EntireX mixed with a COBOL server that requires server-side mapping. All EntireX RPC servers are backward compatible.