Micro Focus Studio Enterprise Edition for Windows > Developing COBOL Applications > Creating COBOL Solutions and Projects > Project and File Properties and Options > Project Properties > Debug Properties

Debug Properties

The properties you specify on the Debug page of the project properties apply to the selected configuration.

Start Action

Start project: Specifies that the project is to be debugged by launching its output.
Note: This setting does not apply to managed class library projects, or to native projects that compile to multiple library files. For these project types, you must specify a different start action.
Start external program: The path to a file to be debugged.
This setting is typically used when your application is a library.
Start browser with URL: Starts debugging by opening a web page.

Start Options

Command line arguments: Program arguments to be passed.
Working directory: The directory from which the program is launched.
Use remote machine: The name of the machine on which the program to be debugged resides.

Managed Code

The following properties are specific for managed COBOL projects:

Enable SQL Server debugging: Enables the Microsoft SQL debugger.
Redirect standard output: Value of true or false, to determine whether or not standard output (such as System.Console.WriteLine) should be redirected to the debugger's output window. For Console projects, this is initially set to False, and for Windows projects it is initially set to true.
Note: This feature does not work for 64-bit applications and on 64-bit machines it is supported only by a x86 platform type.
Enable mixed mode debugging: Check this to enable debugging of C/C++ code alongside managed code.

Native Code

The following properties are specific for native COBOL projects:

Use multi-threaded run-time: Select this to specify that the project is to be debugged using the multi-threaded run-time system.
Wait for animatable attachment: Check this to debug dynamic link libraries. The debugger waits for the program to start in a separate process before attempting to attach to it.
Uncheck this if you are not debugging a dynamic link library, otherwise debugging is suspended while waiting for a separate process that doesn't exist.

CICS, JCL, IMS, Web Service and Core Dump Debug Properties

The following debug properties apply only to applications that run on an Enterprise Server. They appear on the Debug page of the Mainframe Subsystem Applications.

Click the tab for the type of service or application that you want to debug and enter its details.

Choose Active Settings

Specify whether you debug a CICS, a JCL, an IMS application, a Web service, or a coredump file.

Region

Note: These settings are available only for Mainframe Managed Subsystem Applications in Visual COBOL 2010 Enterprise Option and Server Enterprise Edition for .NET .

Specify details for connecting to a database server.

Database Server Instance: The name of the database server that hosts the application to debug.
Region Name: The name of the region that hosts the application to debug.

Properties on the CICS tab

User: The CICS user id used to start the application.
Terminal: The CICS terminal id used to start the application.
Transaction: The CICS transaction for the application.
Link-level program: The CICS invoked program at which to start debugging.

Properties on the JCL tab

Job name: The name of the job.
Job number: The number of the job in the held queue.
Step name: The step that you want to debug.
Top-level program: The program id of the program that you want to debug.

Properties on the IMS tab

User: The user id to be used when debugging this application.
Terminal: The logical terminal ID to be used when debugging this application. This is the eight-character name of the TN3270 connection within Enterprise Server that is either allocated dynamically or specified by the TN3270 client emulator.
Transaction: The transaction to be used when debugging this application.
Top-level program: The start program to be used when debugging this application.

Properties on the Web Service tab

Client IP Address: Leave this field empty to enable debugging from any IP address. Specify an IP address to allow debugging only from it.
Service: Specify the address of the web service to debug. Enter the address and any specific operation that is part of the web service in the following format - http://namespace/ServiceName#OperationName

Properties on the Core Dump tab

File Name: Specify the name and the path to the core dump file to use for debugging your application.