CICS Transaction Cancellation Process

Products

• SYSVIEW Performance Management

Issue/Introduction

Having some thresholds definitions with transaction cancellation and using the force purge method.

Sometimes the cancellation process takes time to complete. 

The cancellation process is recognized by two messages:

GSVC157I (SDCS) Tran XXXX Task  YYYYY to be cancelled by threshold

GSVC101I (SDCS) GSVCSDCS has issued a FORCEPUR for the transaction

The message indicating that the transaction ends is:

GSVC100W (TPPT) TRANEND TRANS

Is there a way to get a dedicated message when the cancellation process doesn't end?

Environment

SYSVIEW 16.0 & 17.0 - z/OS supported releases - 

Resolution

The reason for the long delay on the transaction is due to a write to the DFHLOG. 

The DWMLPROD messages show that reason as well as the attempted FORCEPURGE request. 

Wanting to take additional actions, the IBM documentation does suggest not killing transaction since it could result in the region failing.

From a SYSVIEW perspective, it does continue to issue the GSVC100W messages when the value changes, i.e. bad to worse. 

In these cases,  the GSVC101I messages can be intercepted and then wait for the TRANEND message, otherwise, trigger something in automation to signal a problem. 

With SYSVIEW, the CANCEL value can be changed to KILL to give a higher progression.  

Wanting to narrow down to a specific reason, setting CANCEL to AUTO which then uses CTRANCAN where specifying specific SuspType values, i.e. LGWRITE and DFHLOG.

Additional Information

Additional IBM documentation found at https://www.ibm.com/docs/en/cics-ts/6.1?topic=wait-log-manager-waits