Direct links to fixes
APAR status
Closed as program error.
Error description
According to the manual you can set the maximum number of concurrent session per adapter however it doesn't seem to work that way, rather it appears to work at a Global level.
Local fix
STRRTC - 351025 MB/RJ Circumvention: None
Problem summary
When multiple SFTP adapters are defined on one engine, each adapter uses the combined active session count of all adapters to determine if its session count is reached. For example if Adapter1 is defined with a max session count of 1 and Adapter2 is defined with a count of 3, if one session starts on Adapter2, no sessions may start on Adapter 1. Or if one session starts on Adapter1 and 2 sessions start on Adapter2, a third session will not start on Adapter2.
Problem conclusion
Updated the SSH toolkit, which contains the fix to correctly handle the session counts between adapters.
Temporary fix
Without the fix applied, you may run each SFTP adapter in its own engine to ensure it can have its own maximum session count value.
Comments
APAR Information
APAR number
IC87649
Reported component name
STR SECURE PROX
Reported component ID
5725D0300
Reported release
330
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-10-30
Closed date
2012-11-02
Last modified date
2012-11-02
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
STR SECURE PROX
Fixed component ID
5725D0300
Applicable component levels
R331 PSY
UP
R340 PSY
UP
R341 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PNW","label":"IBM Sterling Secure Proxy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
02 November 2012