DBGAT - Debug Attach Server for NaturalONE

#### Search Results

Search

# DBGAT - Debug Attach Server for NaturalONE

This Natural profile parameter allows debugging of an external Natural application from a z/OS host with NaturalONE. `DBGAT` corresponds to the `NTDBGAT` macro in the Natural parameter module.

Possible settings | See DBGAT Parameter Syntax.
Default setting | none |
Dynamic specification | yes |
Specification within session | no |

For detailed information on how to debug external Natural applications, see the NaturalONE documentation.

This section covers the following topics:

- DBGAT Parameter Syntax

- NTDBGAT Macro Syntax

- Example of DBGAT Parameter

- Example of NTDBGAT Macro

## DBGAT Parameter Syntax

The `DBGAT` parameter is specified as follows:

`DBGAT=(keyword-subparameter=value,...`)

Where:

Keyword Subparameter | Value | Description
--- | --- | ---
`ACTIVE` | `ON` | `ON` means that the debug attach mechanism is active. The Natural runtime is ready for debugging.
`OFF`
`HOST` | 1 - 64 characters | Name of the debug attach server that is to be connected.
`PORT` | 0 - 65535 | Number of the port to which the debug attach server listens.
`CLID` | 1 - 64 characters | Client ID of the NaturalONE project that is to be debugged.
`SSL` | `ON` | The communication to the debug attach server uses SSL/TLS encryption.
`OFF` | The communication to the debug attach server does not use SSL/TLS encryption.
`TLS` | `ON` | See description for `SSL`.
`OFF`
`TRACE` | 1 - 8 hexadecimal digits | Trace level for attached debugging. See also Trace Level.
`VERIFY` | `ON` | Natural will verify the SSL/TLS connection to the debug attach server. Natural will first search the CA certificate in the das.client.ca.crt file stored in the location of the Natural binary. If the file does not exist, Natural will try to search in the `SSL_CERT_FILE` environment variable or `SSL_CERT_DIR` for the CA certificate location (OpenSSL standard).
`OFF` | Natural will not verify the SSL/TLS connection.

### Trace Level

Each bit of `TRACE` represents certain trace information as indicated in the following table:

Bit | Information
--- | ---
00000001 | Trace error events.
00000002 | Trace main events, such as attach debug initialization and termination.
00000008 | Dump internal storage areas.
00000004 | Trace detailed events, such start and end of functions with return code.
00000010 | Dump request and reply buffers in EBCDIC.
00000020 | Dump request and reply buffers in ASCII.
00000040 | Request processing main events.
00000080 | Request processing detailed events.

You can combine different trace options, for example, `TRACE=00000007` traces error events, main events and detailed events.

## NTDBGAT Macro Syntax

The `NTDBGAT` macro is specified as follows:

             NTDBGAT ACTIVE=value,                                          *
                   HOST=value,                                              *
                   PORT=value,                                              *
                   CLID=value,                                              *
                   TRACE=value

## Example of DBGAT Parameter

    DBGAT=(ACTIVE=ON,HOST=MYHOST,PORT=9999,CLID=MYCLIENTID,TRACE=00000097)

## Example of NTDBGAT Macro

             NTDBGAT ACTIVE=ON,                                            *
                   HOST=MYHOST,                                            *
                   PORT=50882,                                             *
                   TRACE=00000097

### On this page

- DBGAT Parameter Syntax
- NTDBGAT Macro Syntax
- Example of DBGAT Parameter
- Example of NTDBGAT Macro