Application Configuration | CCI.INI - The CCI Configuration File |
CCI Trace enables you to trace CCI function calls made by your applications. For data security reasons, this has been implemented through an internal function, to be issued by the application programmer. The application should verify the user's security before allowing the trace information to be output.
The information obtained from the trace is sent to a log file. By default this is called ccitrace.log. In addition to the trace information, CCI data and control flow information can be sent to the log file, depending on the options the application specifies.
Although the trace log file is not generally in a readable format, any data output from the CCI data buffers will not be encrypted when placed in this file.
To activate CCI Trace add the following /tr parameter setting to the Fileshare Server configuration file.
/tr cci
To prevent unauthorised access to the CCI Trace information you are prompted for the supervisor password when you invoke a Fileshare Server with CCI Trace enabled (the supervisor password is that specified for the user-ID FSVIEW in the password file so you must specify this password when you start the Fileshare Server). If the password is accepted CCI Trace is enabled and a second prompt asks if CCI Trace should be activated immediately or not.
CCI Trace can be toggled on and off using the F3 key.
You can set the CCITRACE environment variable as follows:
CCITRACE=filename [options]
where:
filename |
is the name of the log file you want the trace output
to go to. If you do not specify this parameter, the log file ccitrace.log
is created in the current directory with all options
set to their default states. |
||||||
options |
can be any one, or all, of the following, and must be
upper case:
|
Copyright © 1998 Micro Focus Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.
Application Configuration | CCI.INI - The CCI Configuration File |