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

What Trace and Dumps has in store for you

TX Series provide features like trace and dumps .So lets take a look what trace and dumps have information about. The easiest way to enable trace is in regions environment file put CICSTRACE=1 .This will help you in generating your trace file in var/cics_regions/region name/dumps/dir1 . In this directory the trace files of various processes like cicsas,cicsam,cicspcor cicsip will be there . The details can be seen  when you format these file like by using cicstfmt <file name>.This will generate a file which is in readable format .fmt . cicspc file is generate when we use IPIC and cicsip is generated if we use TCP/IP .So now the question arises how to search the important information in the huge pool of data kept in these trace files .The data that is sent to the other region is stored in outbound datastream region and the data which is received from other region is kept in inbound datastream So we can simple use the commands
grep "cicsip outbound datastream" *.fmt
grep "cicsip inbound datastream " *.fmt

Trace and dumps store all information regarding the connection,port,IP address .More details can be found in Dumps.Similarily we ganerate dumps by doing
1) cicslterm -r <region name>
2) CEMT SET DUMP ON
3) CEMT PERFORM SNAP DUMP

This will generate the dumps file in dumps/dir1 directory of region .To format dumps we will use cicsdfmt <file name>.There also we can find the details about the communication .Therefore it becomes  a lot more easier to find the details of communication and in case of any problems or information we can analyze these trace and dumps files.