Dear Friends,
we have WCP v5.6.1 on BS2000, because of this we cann’t use native IP. But we want to install WCP 5.8.1 as soon as possible.
SOLARIS 9 UNIX BS2000
******
WCP v211P38 WCP v561
CSCI v1219 EXX BROKER STUB v21
EXX v711P30 NATURAL v314
ADABAS v713
*************
The Servers hang or very slowly
( aktiv conversation )!
The Users cann’t work with them.
I send to you etbfile from UNIX as attachment.
I have tried to see somethings with cscopr, and i receive this Error-Message on UNIX :
"
cscopr: disp=read
%CSCOPR-W-SEMLOST, Synchronisation semaphore lost, recreated
%CSCOPR-F-ERRNOM, errno (13): Permission denied
%CSCOPR-E-QUEUEF, Wait on semaphore failed
cscopr: disp=read
%CSCOPR-F-ERRNOM, errno (13): Permission denied
%CSCOPR-E-QUEUEF, Wait on semaphore failed
cscopr: disp=read
%CSCOPR-F-ERRNOM, errno (13): Permission denied
%CSCOPR-E-QUEUEF, Wait on semaphore failed
cscopr: quit
"
We couldn’t find a solution !
For Example we have set the values on BS2000 :
into TCP/IP DRIVER
CONNQUE=64
ACCEPTUI=Y
on UNIX NETWORK
transfer_unit = 65535
and on BS2000
* *** TCP-LINK PSAGHOST ANUP54/55
etbfileinfo.txt (3.03 KB)
Hello Sedo,
this looks like an Entire Net-work issue, I doubt that someone here can help you. I suggest to contact your regional support.
However, I have one question: I don’t understand why you are not using native TCP/IP on BS2000 to connect to the Broker on Solaris. The Broker stubs on BS2000 support TCP/IP completely independent from WCP/CSCI.
Kind regards,
Rolf
Hello Rolf,
unfortunately we haven’t time to install WCP v581. WCP v561 hasn’t native TCP/IP.
Since Installing of WCP v581 we must find the solution for this problem.
thank you !
kind Regards,
Sedo
Hello Sedo,
I think there is a misunderstanding: you only need the Broker stub on BS2000 to do TCP/IP communication to the Solaris Broker. WCP is not needed at all ! The Broker stub has build-in native TCP/IP support.
Kind regards,
Rolf
Hello Rolf,
thank you for your suggestion. We have now Natural v314 and WCP v561. Because of compatibility of Versions we must be carefully.
Now, i want to have the reason of my problem !
Perhaps, we can optimize the values of parameters.
thank you !
Sedo
We have now a solution :
" This problem cannot be solved in WCP561. The only solution is to move to WCP571 on BS2000.
Note: Similar symptoms can also appear when the partner node is a Net-Work on a Windows workstation.
A fast Unix machine will provoke the symptoms
probably sooner than a slow Unix machine. "
thank you , have a nice day !
kind Regards
Sedo :eek: