Filter
Top Products
Section 5 Specifications of a Config File
Rev. 1.01 Mar. 17, 2008 Page 24 of 128
REJ10J1822-0101
(3) Server information
• SVR_NAME{…}; Server name
• SVR_ID{…}; Server ID
• SVR_VERSION{…}; Server version
• SVR_NOINIT; The server-initialization function is not to be created.
• SVR_NOSHUTDOWN; The server-shutdown function is not to be created.
• SVR_NOSTUBTBL; The server-stub function table is not to be created.
• SVR_STATIC{…}; Use of a static server
• SVR_SECTION{…}; Section name to be given to the server stub
• SVR_AUTH; How the server ID and server version will be assigned
(4) Client information
• CLNT_NOINIT; The client-initialization function is not to be created.
• CLNT_NOSHUTDOWN; The client-shutdown function is not to be created.
• CLNT_CALLCHK; Facilitates saving the return values of RPC calls
• CLNT_SECTION{…}; Section name to be given to the client stub
(5) Server functions
• RPC_FUNC{…}; Server functions
Server functions are only defined within the braces of RPC_FUNC; multiple server functions can
be defined.
5.2 Comments
Comments in config files should be written in the same way as in the C and C++ languages. The
comments that are written before the first valid definition of a keyword will be output to the
beginning of all source and header files generated by RPCGEN.