Authorize the Debugger: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 7: Line 7:
: 2. Once authorization is complete, issue the <var>ROCKET</var> command in your Online to verify that you have some authorized Debugger seats. The output should contain a line like the following for each debugger authorized by your key (zap):
: 2. Once authorization is complete, issue the <var>ROCKET</var> command in your Online to verify that you have some authorized Debugger seats. The output should contain a line like the following for each debugger authorized by your key (zap):


<p class="syntax"><span class="f_CodeExList">xxxx Debugger   Expires mm/dd/yyyy   Max connections nn</span></p>
: <p class="syntax"><span class="f_CodeExList">xxxx Debugger   Expires mm/dd/yyyy   Max connections nn</span></p>


[[Category:Debugger Home]]
[[Category:Debugger Home]]

Latest revision as of 19:09, 3 April 2023

1. Through your Sales representative:
a. Request a license or trial for one or more seats of the Janus Debugger and/or the TN3270 Debugger.
The number of “seats” indicates the number of programmers who will be able to use the Debugger concurrently.
b. You will be sent an authorization key (a zap), which authorizes the desired debugger(s).
2. Once authorization is complete, issue the ROCKET command in your Online to verify that you have some authorized Debugger seats. The output should contain a line like the following for each debugger authorized by your key (zap):

xxxx Debugger   Expires mm/dd/yyyy   Max connections nn