Problem:
At the beginning, Remote Dynamic Debugging of an Enterprise Server is apparently set up correctly. The ES Administration page on the remote machine shows Dynamic Debugging enabled for the region. The project in Visual Studio is associated, in the Server Explorer, with the remote Enterprise Server. The directories on the remote machine holding the .gnt and .idy files are referenced in Visual Studio in Tools -> Options -> Debugging. Appropriate debug criteria are established in the debug configuration. When the debug session starts, the remote region's console log reflects this with the message:
CASCD1087I Cobdebugremote process created for Server D1CICS12, process-id = 744 11:50:51
ESMAC for the region shows the attached debugger and the criteria. A call to CBL_DEBUGBREAK is included at the start of the first CICS program invoked by login into the system.
But during the debug session, the application pauses for about 30 seconds, Visual Studio flashes 'Ready' in the lower left corner, the debug session never starts, and after the 30 seconds, the application continues running without being debugged.
Resolution:
The machine running Visual Studio, and the remote machine running Enterprise Server, both had drive mappings named F:. The VS machine also had a drive named Z: which was mapped to the remote machine's F: drive. In Visual Studio, under Tools --> Options --> Debugging, a location on the Z: drive was specified, since this seemed to point correctly to where the .gnt and .idy files were located on the remote machine.
But a remote debug session relies on the drive mappings as defined on the remote machine running Enterprise Server, instead of those defined on the local machine running Visual Studio.
Once the settings in Visual Studio under Tools --> Options --> Debugging were changed to reference F:, in accordance with the drive mappings on the remote machine, debugging worked.
(original support incident 2837296)
#MFDS
#EnterpriseDeveloper
