How to Get the Graphical Debugger Started Using the .jar Files

Troubleshooting

Problem

The following information describes how to get the iSeries System Graphical Debugger started using the .jar files.

Resolving The Problem

The following information describes how to get the iSeries System Graphical Debugger started using the .jar files.

1.	Pull down the tes.jar and jt400.jar from the iSeries directory /QIBM/ProdData/HTTP/Public/jt400/lib/ into a folder on your C: drive. If you FTP to the iSeries, verify that you are in binary mode. For this document, we will use the directory of C:\Debug.
2.	Pull down the jhall.jar from the Sun site: //java.sun.com/downloads/index.html and place it into the same folder on your C: drive. For this document, we will use the directory of C:\Debug. Note: The three .jar files are included at the end of this document.
3.	You need to add your classpath. On your PC, right click on my computer->properties->advanced->environment variables. You will either have to edit the CLASSPATH or add a new environment variable called CLASSPATH. It would look like the following. C:\Debug\jhall.jar;C:\Debug\tes.jar;C:\Debug\jt400.jar
4.	Make a shortcut on your desktop with the target as follows: %windir%\system32\java.exe -cp jhall.jar;tes.jar;jt400.jar utilities.DebugMgr The start-in would be set as C:\Debug.
5.	On the green screen, make sure you issue the *STRTCPSVR SERVER(DBG)** command. .
6.	You would click on the shortcut to get the system debug manager started. You should select Edit and Add System. Next, you should select Debug and Start Debug.

Authorities Required for Debugging

The user profile that you use to sign on to an iSeries system in the workbench iSeries logon dialog must have the following authorities:

o	USE authority to the Start Debug (STRDBG*) command.
o	USE authority to the End Debug (ENDDBG*) command.
o	USE authority to the Start Service Job (STRSRVJOB*) command.
o	USE authority to the End Service Job (ENDSRVJOB*) command.
o	Either CHANGE authority to the program or Java class being debugged, or USE authority to the program being debugged and *SERVICE special authority.

If the job that you are debugging is running under a different user profile than the user profile you use to sign on to the iSeries system from the debugger, the user profile that you use to sign on to the iSeries system from the debugger must have the following authorities:

o	*USE authority to the user profile that the job you are debugging is running under.
o	JOBCTL special authority if you do not explicitly use fully qualified program names (library/program). In other words, if you use CURLIB or LIBL or you do not specify a library name, you need to have JOBCTL special authority.

The group profile QPGMR gives you the correct authority to the STRDBG, ENDDBG, STRSRVJOB, and ENDSRVJOB commands and *JOBCTL special authority.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]

Historical Number

539304837

Was this topic helpful?

Document Information

Modified date:
18 December 2019

UID

nas8N1012686

Tips