RSC/MP Installation and Configuration Guide

Installation Troubleshooting RSC/MP API Logging
RSC/MP API Logging
API logging can be used to record certain details of the internal activities of the
RSC/MP API library (DLL or shared library) for diagnostic purposes. When engaged,
the logging function adds processing burden to the RSC/MP client application and
generates potentially large log files. Logging should therefore be engaged only when
required by Customer Support.
To engage API logging, use the following options: .
RSC.INI Option Description
DEBUG_TYPE = 1 Engages API logging.
DEBUG_NAME = logfilename Names the file to which logged data will be
written; a fully qualified path and file name is
recommended. If the file already exists, new log
entries are appended to it.
DEBUG_LEVEL = 3 Selects the greatest level of detail. Substitute 2
for medium detail or 1 for least detail.
DEBUG_MASK_RSC = 1 Enables logging of interactions with the
RSC/MP Host.
DEBUG_MASK_PIPE = 1 Enables logging of local interaction with the
Piccolo transport.
DEBUG_MASK_API = 1 Enables logging of entry into and exit from the
API functions and some parameter-validation
errors.
DEBUG_MASK_SNO = 1 Enables logging of unexpected internal errors
and internal states that ―Should Not Occur.‖
DEBUG_MASK_CONNECT = 1 Enables logging of interaction with the
RSCPIPE process.
Use one of the following methods to specify the API logging options:
If the client application uses the default options (RSC_DEFAULT_OPTIONS), put
the API logging options into the configuration file RSC.INI.
If the application loads options from a file explicitly, put the API logging options in
the file whose name is being passed to the RscLoadOptions function.
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration G uide — 52235 8- 013
B - 10