Wednesday, November 17, 2010

Coexistence of DCE and SARPC?

The DCE technology that underpinned previous versions of TXSeries for Multiplatforms has now been removed. CICS processes now communicate using secure shared memory, which enhances performance and security with no configuration or administration required.
TXSeries Version 6.2 cannot coexist with DCED on the same machine; that is, you cannot run a DCED process alongside TXSeries Version 6.2 and more. This limitation arises because TXSeries Version 6.2 uses a new SARPCD process on Open Systems platforms to store and manage endpoint information of CICS regions and servers. For interoperability with previous versions of TXSeries that are running on other machines, the SARPCD process listens on port 135. This port is also used by DCED, meaning that DCED cannot coexist with SARPCD and TXSeries Version 6.2. The SARPCD process has additional capability over DCED to manage CICSIPC endpoints, local endpoints used by TXSeries Version 6.2 apart from TCP, and UDP endpoints, which prevents the DCED process being used as a replacement for the SARPCD process to manage endpoints in TXSeries Version 6.2.
CICS is trying to start CICS supplied RPC daemon and it finds DCED running. If DCED is running, CICS supplied RPC (SARPC) daemon cannot be started.But sometimes even in the newer version of TXSeries we can see this ERZ58505E mostly on HP machines because when you reboot/restart the machine DCE daemon automatically starts Therefore we recive this error
Example:
cicscp -v stop region TXWEB
ERZ058504I/0107: Starting RPC daemon.
ERZ058505E/0106: DCE daemon is running.Current version of TXSeries does not support DCE.
ERZ096003E/0004: cicscp command failed
ps -eaf | grep dce
    root  1513     1  0 21:46:10 ?         0:00 /opt/dce/sbin/rpcd
# kill -9 1513

No comments:

Post a Comment