Enforcing a minimum Client build number

Normally, when you use the TN3270 or Janus Debugger, no restrictions are placed on which build of the Client is used. The Client build number is displayed in the Audit Trail tab when the Client starts:

2016 07 30 17:21:47    The Rocket Software Debugger Client 2016 07 30 17:21:47    Build: 65 (01 August 2016) Tag: 1 GA

You can also view the build number of the Client at any time by selecting Help > About. On Debugger Client build 65 and higher, the build number is also available from the Client &&buildNumber function.

Build 64 (and higher) of the Debugger Client transmits its build number to the mainframe when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:

MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since Client builds before 64 do not transmit their build number, the mainframe side views all Client versions prior to build 64 as build 63.

Specifying a minimum build number

As of Client Build 65 or higher and Model 204 7.7 or higher, you can force Clients to have at least a minimum build number in order to invoke a debugging session with your Online.  The Model 204 system parameter MINDEBCL sets such a minimum.

If you set MINDEBCL to a positive value, use a version of the Debugger Client whose build number is less than MINDEBCL, and invoke a debugging session, the debugging session is rejected. An error message is shown in your browser and at the Client, calling for a Client upgrade. A browser example follows:

You also see the following error in the Model 204 audit trail (and on the terminal if you are using the TN3270 DEBUG ON command):

MSIR.1079: Debugger Client Build: xx < MINDEBCL: yy debugger client connection refused