CA Datacom CICS Services (DBC) Version 14.0 PTF RO77713 has SMP/e ++HOLD ACTION(ENH), What actions are needed?

Products

• Datacom
• DATACOM - AD

Issue/Introduction

Question:

CA Datacom CICS Services (DBC) Version 14.0 PTF RO77713 has SMP/e ++HOLD ACTION(ENH) causing:

GIM30206E ** APPLY PROCESSING FAILED FOR SYSMOD RO77713. HOLD REASON IDS WERE NOT RESOLVED. 

GIM35965I SYSTEM HOLD ENH ORIGINATED BY SYSMOD RO77713 WAS NOT RESOLVED. 

 

What actions do I need to take?

 

Answer:

For this specific PTF RO77713, you can APPLY with BYPASS HOLDSYS(ENH) and also refer to PDC RI79084 for the documentation on this enhancement. You must also follow the actions as documented in the ++HOLD.

Important:

For any DBC PTF that provides a new DBCVTPR macro as does PTF RO77713, it is important that each of your CICS regions's custom DBCVTPR must be reassembled whether or not you intend on using the new feature or not. Many programs depend on the changes in DBCVTPR to be there so they can work properly. 

So, you would need to apply the PTF with a BYPASS, schedule the reassemble of custom DBCVTPR macro and re-link edit of the DBCVTPR load module for each of your CICS regions. Then deploy each CICS region's new custom DBCVTPR module when you deploy the maintenance applied to the CAB1LOAD.

Additional Information:

TEC1056426 “DC00131C COMPONENTS OF THE SERVICE FACILITY ARE NOT AT THE SAME PTF LEVEL; DBCVTPR PTF = mmmmm DCCOCPR PTF = CCnnnnn”

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1056426.aspx

TEC1835604 “How to refresh/reload DBCVTPR without recycling CICS?”

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1835604.aspx

 

 

Environment

Release:
Component: DBC