Troubleshooting: Testing with Db2® on z/OS systems

You can use diagnostic information to help troubleshoot common problems that you might encounter when you test with Db2® on z/OS systems.

The recording monitor Global Notifications window is the primary source for notifications about recording. You can open the window by clicking the icon to next to the monitor name within the Recording Studio Monitor Configuration view. If there are warning messages within the Global Notifications window, an icon is displayed.

In the following example, recording was started, but the agent for z/OS was not running:

The creation of a stub from a recording does not occur until you stop recording. When you stop recording, you can open the stub in the Stub editor. If you open the Stub editor, you can miss important messages in the recording monitor Global Notifications window that is related to the creation of the stub. When you finish editing the stub, it is a good practice to double check the recording monitor Global Notifications window to ensure that no problems were encountered when rows were written to the virtual database.

The stub console is the primary source of information about stubbing. In the following example, a stub was started, but the agent for z/OS was not run:

If you experience problems, but do not see any relevant errors in either the recording monitor Global Notifications window or in the stub console, you can check for information in the agent for z/OS console.