Server-side mapping files have the extension .svm.
Server mapping files with extension .svm are no longer supported at design time by the Designer. You can still use them at runtime in a server-side mapping container. All special COBOL syntax and features supported by server mapping files with extension .svm are also covered by server mapping files with extension .cvm. See When is a Server Mapping File Required? We recommend migrating .svm files to .cvm files. See Migrating Server Mapping Files under Server Mapping Files for COBOL in the Designer documentation. This document covers the following topics:
Check if a Server-side Mapping File Revision has been Deployed
Access Control: Secure Usage of Server Mapping Deployment Wizard
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 Designer documentation.
Under BS2000, server-side mapping corresponds to lines of Designer files with extension .svm. See Server Mapping Files for COBOL. The mapping information is stored as records within one ISAM file, the server-side mapping container. This container contains all server-side mapping entries from all Designer files with extension .svm. The unique key of the ISAM file file consists of the first 255 bytes of the record: for the type (1 byte), for the IDL library (127 bytes) and for the IDL program (127 bytes).
If one server requires a server-side mapping file (.svm),
you need to provide the server-side mapping container to the RPC server. See configuration parameter svm.
If no server requires server-side mapping (.svm) or you use server mapping files with extension .cvm only, you can execute the RPC server without the server-side mapping container.
Use the Server Mapping Deployment Wizard to undeploy a server-side mapping file (Designer file with extension .svm). See Server Mapping Files for COBOL.
To undeploy a server-side mapping file with the Server Mapping Deployment Wizard
Make sure your RPC server is active and that the Deployment Service of the RPC server is properly configured. See Deployment Service.
Make sure your IDL file is within a Designer directory (folder) without the related server-side mapping file (.svm) or renamed to extension .cvm if you are Migrating Server Mapping Files.
From the context menu of your IDL file, choose and call the Server Mapping Deployment Wizard. See Server Mapping Deployment Wizard in the Designer documentation. Because there is no related server-side mapping file (.svm) in the Designer, all server mapping information related to the IDL file in the server-side mapping container of the RPC server will be removed.
Under BS2000, change management for an ISAM file (server-side mapping container, see Server-side Mapping Files in the RPC Server) is similar to change management for an ordinary file. All updates to the ISAM file done after a backup must be kept.
All Designer server-side mapping files (.svm) added since the last backup should be available. See Server Mapping Files for COBOL in the Designer documentation.
Use the command SHOW-FILE to list the contents of the server-side mapping container. See Server-side Mapping Files in the RPC Server.
SHOW-FILE <server-mapping-file>
where <server-mapping-file> is the server-side mapping container (ISAM file) containing all server-side mapping information.
Server-side mapping records in the server-side mapping container correspond to lines of Designer file with extension .svm. See Server Mapping Files for COBOL in the Designer documentation. The records contain 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 records in the server-side mapping container (ISAM file). See Server-side Mapping Files in the RPC Server.
To control the usage of the Server Mapping Deployment Wizard, use EntireX Security if the broker is running on platforms z/OS, UNIX or Windows. See Enabling the Deployment Service.