**** DUMMYEMM_README.TXT **** This CDSA example is an Entity Module Manager, which extends the functionality of CDSA by providing an additional category of service. It's purpose is to demonstrate the mechanics of developing a CDSA EMM (which on OpenVMS is a shareable image). It also provides the necessary CDSA code files that would be necessary to build an Entity Module Manager. The installation procedure will verify that it is built correctly. It will attach the module and execute RegisterCDSAModule(), (the definition of INSTALL_ENTRY_NAME). ******************** ** Special Note ** ******************** Sys$common:[syshlp.examples.cdsa]readme.txt contains general information that applies to all of the example programs that are signed. The necessary files to build the example on OpenVMS are included, with the exception of modselfkey.h. This include file must be generated from the certificate created for the addin module(s). See the OpenVMS book "Open Source Security for OpenVMS, Volume 1: Common Data Security Architecture", CDSA Programing Concepts, for complete instructions. Special attention should be paid to the section on Signed Application Development. A signed CDSA application will not execute until the proper credentials are generated. The DUMMYEMM example files are: CALLOUTS.C COMMON.H DUMMYEMM_BUILD.COM COMMON.C DUMMYSPI.H DUMMYEMM_SIGN.COM DUMMY.C DUMMY_MDS.H DUMMYEMM_INSTALL.COM MODINSTALL.C MAF_COLLECTN.H PUBLIC.C MAF_UTIL.H MDS_UTIL.H (MODSELFKEY.H not provided, user generated) After performing the steps to generate the application credentials and the include file, modselfkey.h, the DUMMYEMM example program can be built by copying the example files to a local build area, and executing the DUMMYEMM_BUILD command file, as follows: $ define/trans=conceal cdsa_tempdir :[.] $ set default cdsa_tempdir:[DUMMYEMM] $ copy SYS$SYSROOT:[SYSHLP.EXAMPLES.CDSA.DUMMYEMM]*.* [] $ copy CDSA_SYSDIR:[SIGN]MODSELFKEY.H [] $ @DUMMYEMM_BUILD The resulting shareable image is DUMMYEMM_SHR.EXE. ************** On the SIGNING SYSTEM run the command procedure to generate the manifest. ************** $ @DUMMYEMM_SIGN Finally back on the development system run the command procedure to install the module. $ @DUMMYEMM_INSTALL When an application program loads an addin module that is written to the SPI of this EMM, the EMM will be automatically loaded.