MINDEBCL parameter: Difference between revisions
m (minor formatting) |
|||
| Line 15: | Line 15: | ||
==Description== | ==Description== | ||
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted. The purpose of this parameter is to allow a system manager to ensure upgrades to the Janus/TN3270 | The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted. The purpose of this parameter is to allow a system manager to ensure that upgrades to the Janus/TN3270 Debugger Client are done. | ||
If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place. | If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place. | ||
A message is displayed by the | A message is displayed by the Client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated. | ||
Here is an audit trail fragment showing this error ( | Here is an audit trail fragment showing this error (from [[SirScan]]): | ||
<p class="code">13303016 2 1 ER MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 | <p class="code">13303016 2 1 ER MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 | ||
debugger client connection refused | debugger client connection refused | ||
| Line 27: | Line 27: | ||
</p> | </p> | ||
If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a <var>MINDEBCL</var> rejection, a message is displayed on the terminal as well. For example: | |||
If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example: | |||
<p class="code"><b>R MINDEBCL 66 </b> | <p class="code"><b>R MINDEBCL 66 </b> | ||
MINDEBCL 66 Minimum debugger client build supported | MINDEBCL 66 Minimum debugger client build supported | ||
Revision as of 22:41, 1 August 2016
Minimum debugger client build supported
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On user's parameter line or reset by system manager
- Related products
- All
- Introduced
- Model 204 V7.7
Description
The MINDEBCL parameter holds an integer value in the range 0-500 of the minimum Debugger Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted. The purpose of this parameter is to allow a system manager to ensure that upgrades to the Janus/TN3270 Debugger Client are done.
If the Client build number is earlier than the MINDEBCL setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place. A message is displayed by the Client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.
Here is an audit trail fragment showing this error (from SirScan):
13303016 2 1 ER MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused 13303016 2 1 AD MSIR.0929: Janus/Tn3270 Debugger worker terminated: 400 Client version too old, please upgrade
If you are using the TN3270|SIRIUS DEBUG ON command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66 MINDEBCL 66 Minimum debugger client build supported TN3270 DEBUG ON DEBONLY 10.5.3.76 MSIR.0942: Debugger GUI port defaulted to 8081 MSIR.0942: Debugger Worker port defaulted to 3226 MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused MSIR.0914: Debugger Error: Please upgrade your client