What is the purpose of the CA DADS Plus FOR CICS DADV transaction?
Article ID: 50930
Updated On:
Products
Issue/Introduction
The client is installing CA DADS Plus for CICS in a CICS region that already has an application that uses the DADV transaction ID.
CA DADS Plus for CICS also has a DADV transaction.
Since CA DADS Plus does not have the ability to rename any of its transactions, what functionally will be lost if we remove the DADV transaction from CA DADS Plus for CICS.
Environment
Z/OS
CICS
Resolution
A DADS Plus for CICS supports two High Performance Options HPO that expedite batch request processing by eliminating the wait times that normally occur when batch requests wait for the DADB CICS transaction to be scheduled.
The HPO options are HPO=EXCI and HPO=MODIFY.
The performance benefit of both of these options is they immediately start the Batch Interface online scan process (DADB) from the batch job.
If neither HPO option is used then batch jobs use the DADB SCAN= parameter (default 30 seconds) to process batch requests.
If HPO=MODIFY is specified on the APPLID record then the DADV transaction is used by DADS to drive the batch process.
If you disable the DADV transaction only HPO=MODIFY batch jobs are affected and these jobs default to the regular SCAN= value for processing.
When you specify HPO=MODIFY the following message appears in the CICS log when a batch job is submitted
15.42.08 JOB58730 MODIFY CICS8565,DADV JOB=RLS ,JOB#=0058730
If you disable the DADV transaction you will see an additional message in the CICS log
15.42.08 JOB58353 +DFHAC2008 12/01/2010 15:42:08 APPLID Transaction DADV has been disabled and cannot be used.
The batch job is processed by the default scan interval and the follow messages are generated by the batch job at completion.
CURRENT JOB=RLS .ALFILE . DSN=DADSPLUS.CICS65.TESTBIF
FUNCTION=DADS,APPLID=(XXXXXXXX,QUEUE)
REQUEST=(D,F,FILE002)
CONDITION CODE=000 DADSA460 REQUEST COMPLETED SUCCESSFULLY.
HIGH CONDITION CODE=000
Feedback
