Gen EDGE

Hi,

We are currently implementing CA:Gen 8.5 and have problems setting up the TIML communications between the CA:Gen Cliënt Manager and our Mainframe CICS environment. Both CA and IBM are working on the problem, but haven't found the exact reason for the problem yet.

Our previous method of communications was to make use of the TICONMANAGER (via transactions TILL and TICM) which is now replaced by the CICS Multiple Socket Manager (transaction TICM).

What we are seeing is the following :

• TEST1 - LOGON to CICS environment
• Client Manager - error 621, Error Creating semaphore, cant access server.
• CICS - TISRVMSL GIVESOCKET NOT TAKEN FOR SERVER ECHO

• TEST2 -SEND TEST TRANSACTION ECHO
• Client Manager - Test Transaction ECHO Returned
• CICS - TISRVMSL LISTENER: STARTED SERVER ECHO

• TEST3 - SEND Application Transaction Y01Y
• Client Manager - TIRM629E: Error Client Manager could not send data to server
• CICS - TIRSIPIN SERVER TC ECHO DOES NOT MATCH CFB TC Y01Y

What seems to be happening is that the transaction is not completed when the first error occurs. It is somehow buffered and when Test 2 is started, this "pushes" Test 1 further for processing, whilst Test2 is again buffered. When Test 3 is started, it "pushes" Test 2 further (whilst buffering the input from Test3), which results in a CFB mismatch as it's expecting the CFB from transaction Y01Y, but is receiving the CFB from Test2 which is transaction ECHO's CFB.

If anyone has encountered the same problems and know how to solved this, your input would be highly appreciated.

Regards.

Werner Spreeuwenberg

Hi Werner,

Not sure if my colleagues may have already pointed you to KB TEC463495 ("Impact of new CICS Sockets Servers Timeout parameters") written for the TISL (TISRVLIS) which has same architecture as TIML (TISRVMSL). Here is the direct link from the Gen Product page Knowledgebase search: Impact of new CICS Sockets Servers Timeout parameters

Hope it helps.

Regards,

Lynn

Just to add this which you are probably aware of already:

For connecting to TISL/TIML the corresponding Server Config/Details in Client Manager must have "CICS Socket Listener" checked to ensure a non-persistent connection is made i.e. IEFCMN.SRV then contains "IP_PERSISTCONN = N" for that server.

Thanks. We have the correct settings on the IEFCMN.SRV file.

This reply is to confirm that the issue concerned a data consistency bug and was fixed by CA in May 2016.