Known limitations

This information contains known limitations that you might encounter when you run the CICS® DA server.

Recycling TCPIP can cause NetworkRecycledException errors in the CICS DA log.

Recycling TCPIP should be part of a managed program of maintenance. If CICS DA V5.3 is running, it must be stopped prior to TCPIP being stopped and restarted. If this procedure is not followed, multiple entries of the following messages will appear in the CICS DA server side logs
{timestamp}:WARN::EXCEPTION com.ibm.net.NetworkRecycledException: Network Recycled while accepting connection
        at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
        at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:170)
        at org.mortbay.jetty.nio.SelectChannelConnector$1.acceptChannel(SelectChannelConnector.java:75)

A client will not be informed of changes applied by another client.

In cases where you have more the one DA user on a single DA server, you might experience an out of sync issue. For example, two users update the same start policy and the first user made a mistake. When the second user, with the correct policy issues a start, the start fails or the wrong batch job to start the region is run.

If you have more than one DA user on a single DA server, always check that you are using the correct policy when users attempt to perform actions that use the server model.

Cloning a CICS region that is running on a z/OS 2.1 system might not be successful.

CICS DA does not support all of the new features of JCL that are introduced in z/OS 2.1. If you upgraded to z/OS 2.1, and changed your jobs to include the new features, then the clone operation might not be successful.



limitations.html | Timestamp icon Last updated: Friday, 11 December 2015