CA DADS Plus CICS batch interface jobs not running when CICS is active.

Document ID : KB000122200
Last Modified Date : 30/11/2018
Show Technical Document Details
Issue:
The client is using the CA DADS Plus CICS batch interface feature. The batch Interface is started at CICS startup by the DADS PLUS PLTPI processing. Sometimes CA DADS Plus CICS batch requests are not running when CICS is active. The batch interface requests queue for the APPLID and the allocate or deallocate is not completed.
 
Environment:
Z/OS
CICS
Cause:
Some of the users submitting the batch interface requests do not have security access to the CA DADS Plus CICS batch interface transaction DADB. The batch job encounters a security violation and the DADB transaction abends due to this security violation. Once the DADB transaction abends the batch interface is no longer available on the CICS ICE chain and batch Interface jobs not be executed. They batch interface requests will QUEUE for the APPLID and not run.
Below is the error message you will see in the CICS Log.
 
DFHAC2003 11/26/2018 23:59:02 CICSTPROD Security violation has been detected term id = ????, trans id = DADB, userid = XXXXXX
Resolution:
Users who submit batch jobs have to have access to the DADB transaction.  Most sites using the batch interface are submitting  jobs from an automated scheduling package. The user ID associated with the scheduler has access to the DADB transaction.