Putting/Getting non-persistent messages out of syncpoint – performance

Please confirm if my understanding of the following is correct:

A distributed application puts a high volume (200-800 per second) of request messages onto ten shared mainframe queues (MQ v8.0) via SVRCONN channels . Each of these non-triggered queues have multiple CICS transactions processing these requests and putting responses onto another set of ten shared queues then read by distributed processes. All the requests are processed by MSGID and all the queues are non-persistent. CICS syncpoints are issued every 200 messages.

Improve throughput by eliminating as much of the MQ wait time as possible.

Have the application issue all puts and gets outside of syncpoint. The messages are non-persistent, the data is stale after a few seconds and the application/business is not concerned for message rollback. My understanding is that putting/getting within syncpoint will lock the message until a commit/syncpoint is issued. By modifying the application to put/get outside of syncpoint this delay will be avoided. Is this correct?

Note that these transactions are long running (with built in delays), therefore all SMF statistics are aggregate so we cannot accurately state the value of MQ wait times.

My question is really is just to ensure that my understanding of the syncpoint process in the above regard is correct.



Why does LLA get abend 878 and multiple CICS regions fail to initialize?

When initializing multiple CICS regions about the same time, the LLA service fails with abend S878 and many (but not all) of the CICS region fail to initialize. The reasons for the CICS failures can be quite different. For instance, some of the CICS failures have been:

DFHLD0001 An abend (code 0C4/AKEX) has occurred at offset X’FFFF’ in module DFHLDLD1.

DFHLD0001 An abend (code 0D5/AKEX) has occurred at offset X’FFFF’ in module DFHLDLD1.

DFHPC0401 Abend AEXZ issued by III task.

DFHLD0001 An abend (code 878/AKEX) has occurred at offset X’FFFF’ in module DFHLDDMI

DFHLD0002 A severe error (code X’6929′) has occurred in module DFHLDDM.


BAQR7062E: z/OS Connect service install failed. The provider property CICS-1.0 in the service archive file does not match any of the install service providers

I am trying to deploy a service to an embedded zCEE server running in
CICS using the new feature available in V3.0.3 of the Toolkit. When I
try try to deploy I receive message “BAQR7062E: z/OS Connect service
install failed. The provider property CICS-1.0 in the service archive
file does not match any of the install service providers”. But if
first export the SAR and the FTP it to the services directory the
service installs with no issues.


Is the traffice between rule engine and CICS/batch job encrypted?

The documentation shows that we can configure a zRule Execution Server for z/OS running in CONSOLE, TEST, or HTDS mode to use SSL for data encryption, and optionally authenticate with the server by using a client certificate.

How about the traffic between ODM rule engine and CICS/batch job, is it encrypted?


Why do I receive DFHFC0961 when CICS 5.2 starts up?

I find the following message in MSGUSR after staring up CICS 5.2:
DFHFC0961 11/23/2017 08:33:45 CICSREG Calculation of LSR pool 1
parameters incomplete. Filename DFHDBFK has no DSNAME.

This region doesn’t use IMS. Is there a way to disable DFHDBFK?