Srinivas Tadimalla’s Post

View profile for Srinivas Tadimalla, graphic

Sr. Technical Architect / Sr. Manager - Payments

As I look back on the early days of my career in Testing Services, I can’t help but feel a deep sense of gratitude for the lessons learned and the mentors who guided me. One such moment that stands out is from my time working on my first CICS PL/I document under the mentorship of my guru, Sri Rama Subbarao Kopparthi During a resource locking exercise for my document, I attempted to update the same VSAM file record simultaneously from two CICS operator screens. When one operator initiated an update, the second encountered a resource locking error—a significant learning moment! This scenario became an illustrative example of resource contention, and I was fortunate to showcase it as a case study in the Cognizant Academy for Mainframes. Encouraged by this experience, I tried to replicate the same concept with DB2 records. However, I quickly realized my mistake with help of my mentor: DB2, with its sophisticated server architecture, inherently manages its locking mechanisms, making this proof of concept infeasible. My goal is to take the similar kind of screenshot of locking error for DB2 just like VSAM which is not possible through a manual attempt with less number of resource operators attempting to update the same record. #Mainframes #CICS #VSAM #DB2 #ResourceLocking

To view or add a comment, sign in

Explore topics