APAR status
Closed as program error.
Error description
In z/os Explorer 3.0.0.6, only one successfully connected RSE connection is possible in Host Connections. Multiple RSE connections on different ports are rejected. To recreate: 1) Create a successful RSE connection on one port. 2) Create a second RSE connection on a different port. 3) Attempt to connect the second RSE connection. The first RSE connection will be disconnected.
Local fix
Problem summary
RSE Connections allow more than one to be active, so you can connect to 1, 2, 3... different RSE hosts. FTP Connections to z/OS only allow one to be active, so once the 2nd connects it disconnects the first connection. The Host Connections view that shows both RSE and FPT connections beneath the z/OS connection type, was treating RSE connections as though they could only be active one at a time which was incorrect. The Host Connections view was allowing an RSE connection to be establish through its "Connect" button/menu action. When the 2nd RSE connection was made through the Host Connections view it did a disconnect on the first connection because it was treating it as though had an FTP type behaviour where only one could be active. If an RSE Connection was made in the Remote Systems Explorer view, then this was working to allow 1, 2, 3, ... connections - but it was not notifying the Host Connections view (or trim widget) so a user would look at Host Connections and see inconsistency.
Problem conclusion
The Host Connections view and its accompanying framework (that is used by the trim widget) is updated so that when an RSE Connection is connected it does not disconnect any existing active RSE Connections. It will disconnect an FTP connection though and replace the "active" z/OS connection with the RSE one so that the UNIX files view (which is populated by RSE) gets its content from RSE. If an FTP connection is made it will disconnect an existing FTP connection, but it will not disconnect an RSE connection. Notification listeners are added into Remote Systems Explorer framework so that when an RSE Connection to a z/OS System is made the Host Connections view (and framework that provides the trim widget) is updated to show the correct status - likewise for disconnect. When an RSE Connection is made the previous connection is remembered, so that when a connection is disconnected in RSE and the z/OS perspective's user interface views, the last known connected connection is then switched to be the "active" connection so that the data sets/UNIX Files/JES tree view are populated. This APAR will be available in IBM Explorer for z/OS 3.0.1.5 Fixpack located here: https://developer.ibm.com/mainframe/products/downloads/
Temporary fix
Comments
APAR Information
APAR number
PI70907
Reported component name
EXP FOR Z/OS CL
Reported component ID
5655EXP00
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-10-18
Closed date
2017-01-26
Last modified date
2017-01-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
EXP FOR Z/OS CL
Fixed component ID
5655EXP00
Applicable component levels
R301 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSBDYH","label":"IBM Explorer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
26 January 2017