APAR status
Closed as program error.
Error description
Host On-Demand V10 __________________ When defining a session to be secure or non-secure, the port number used is the well-known port number associated with the protocol. When a telnet session is set up, the default port number of 23 is automatically set. When the session is changed to Telnet-SSL or Telnet-TLS, the port number changes to 992 un- less manually changed. In this situation, the customer is using port 23 as both secure and non-secure. They want the port to remain 23 regardless of what protocol is selected. If a port number that is not 23 is used, for example, 2023, the port number does not change back to 992 or 23 when the protocol is changed. A parameter is to be added to allow for use and editing of port 23 as a secure and non-secure port.
Local fix
Manually change the port to 23 each time it is changed.
Problem summary
**************************************************************** * USERS AFFECTED: Host On-Demand users changing protocol * * type in the connection panel * **************************************************************** * PROBLEM DESCRIPTION: If the Host On-Demand session port of * * 23 is used for both secure and * * non-secure, you must manually change * * the port number to 23 again for secure * * as the port number will change to 992 * * automatically as this has been * * hard-coded as the common secure port. * **************************************************************** * RECOMMENDATION: * **************************************************************** if you select the protocol property to be Telnet-TLS in a Host On-Demand session, the port will change to 992. If you manually change the port number to be 23 instead of 992 and then switch the protocol back to Telnet, the port will remain as 23. If you then change the protocol to Telnet-TLS again, the port number will change to 992 instead of remaining as 23 as you had originally edited. If you change the port number to a number other than 23 or 992, switching back and forth does not change the port number.
Problem conclusion
The design was intentional to prevent users from forgetting to change the port back to a secure or non-secure port when they changed protocols. The common non-secure port for telnet and the common secure port numbers were used. The use of 23 as a secure port was not considered as a option. A parameter of "disablePortChange" has been added. When set to true, the port number does not change even when the protocol type is changed in the connection panel. The default value for this parameter is false.
Temporary fix
Comments
APAR Information
APAR number
OA25712
Reported component name
HOD MVS
Reported component ID
5733A5900
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-01
Closed date
2008-08-14
Last modified date
2015-05-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
HOD_BEAN
Fix information
Fixed component name
HOD MVS
Fixed component ID
5733A5900
Applicable component levels
RA00 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSS9FA","label":"IBM Host On-Demand"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
19 April 2021