I pushed a little harder with IBM and found out that an SPR (Software Problem Report) has been opened for the issue on SUSE 12, which also exhibits the same behavior:
SPR # YXYX9RA56Z "Error - Unable to Bind port 443 or 80" on SUSE12.
My representative quoted one of the developers as saying:
"There is a known issue with SLES 12 where bindsock has issues. Before we can support SLES 12 and any other newer kernel with this issue, we will have to identify the issue and get it fixed - bindsock and it's code has never changed in this area so the issue is a change in behavior in the kernel".
So, there is hope that there may be a future fixpack(s)(9.0.1 FP3?) where the issue may be addressed on the bindsock side. But, as one of my favorite quotes goes,
"Hope? Let me tell you something, my friend. Hope is a dangerous thing. Hope can drive a man insane. It's got no use on the inside. You'd better get used to that idea." -Red, Shawshank Redemption
I pushed a little harder with IBM and found out that an SPR (Software Problem Report) has been opened for the issue on SUSE 12, which also exhibits the same behavior:
SPR # YXYX9RA56Z "Error - Unable to Bind port 443 or 80" on SUSE12.
My representative quoted one of the developers as saying:
"There is a known issue with SLES 12 where bindsock has issues. Before we can support SLES 12 and any other newer kernel with this issue, we will have to identify the issue and get it fixed - bindsock and it's code has never changed in this area so the issue is a change in behavior in the kernel".
So, there is hope that there may be a future fixpack(s)(9.0.1 FP3?) where the issue may be addressed on the bindsock side. But, as one of my favorite quotes goes,
"Hope? Let me tell you something, my friend. Hope is a dangerous thing. Hope can drive a man insane. It's got no use on the inside. You'd better get used to that idea." -Red, Shawshank Redemption