The environment variables that the Win32 remote debugger uses are the same as the environment variables that the normal Win32 debugger uses. For details about environment variable settings, refer to "2.3 Environment Variables of the Debugger".
This section explains environment variables that the Solaris remote debugger uses.
Since environment variables are used for batch debugging, you do not have to specify an environment variable that the Solaris remote debugger uses unless you are intending to do batch debugging. The same is true for normal debuggers.
For details about batch debugging, refer to "2.5.2.1.11 Automating Debug Operations".
@SVD_COMPATIBILITY={COBOL97 V61L10|NetCOBOL VersionLevel}You can restrict the functions of the Solaris remote debugger with this variable.
By specifying this environment variable, the initial value for the compatibility of the Solaris remote debugger can be set in the value specified by the environment variable.
When the environment variable is not specified, the default conforms to the values that were set when the debugger last ended.
In the environment variable, specify the version level of the Solaris remote debugger when the command file was created.
If you specify COBOL97, the following behavior occurs:
This is similar behavior to the COBOL97 V61L10 svd command.
If you make a few changes to the history file created using this operating mode, you can use this as the command file of the svd command that runs on Solaris.
If you specify NetCOBOL, the following behavior occurs:
This is the latest behavior.
V7.0L10 or later can be specified for VersionLevel.
For details, refer to Help of the Solaris remote debugger, about the Compatibility page of Environments dialog box.
Note
Environment variable @SVD_COMPATIBILITY is not for making svd's original command file be available for batch debugging using the Solaris remote debugger. When you use svd's original command file for batch debugging, use the svd command on Solaris.
If you do a lot of batch debugging using Solaris remote debugger, it might exert a heavy burden on the network. In this case, it is recommended that you use the svd command on Solaris for batch debugging.