Q
Problem solve Get help with specific problems with your technologies, process and projects.

Need help circumventing the journal wait problem

I am faced with a grave performance problem in one of my CICS regions, particularly with a few transactions (CICS/ESA...

4.1 -- not sure when we'll go to TS). These transactions do a lot of I/O and the wait is at resource FCIOWAIT and JCIOBLOK (on system journal J01). To circumvent the journal wait problem, I am thinking of making the JNLSYNCWrite from YES to NO (so that the journalling will be asynchronous).

- Will this give any improvement?
- Are there any potential risks in doing this?
- I haven't coded the SYSWAIT=STARTIO in the JCT. Will this cause the tasks to wait for the buffers to be flushed (I read that STARTIO will be the default)?
- The primary and secondary journals switch in the interval of 2-3 minutes during peak time (worst case is 38 seconds).
- The IBM PTFs PN80128/UN89909 have been applied.

This type of query should be raised with the CICS Service organisation.

However, I am SERIOUSLY concerned that you seem, after the year end, to be planning to use a then out-of-service product: you WILL be seriously exposed by using a then unsupported version of CICS.

This was last published in October 2002

Dig Deeper on IBM system z and mainframe systems

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchWindowsServer

SearchServerVirtualization

SearchCloudComputing

Close