CICS Protected Threads / DDL Break-In

Mark Madsen

CICS Protected Threads / DDL Break-In

see upload

Attachments

  • CICS Prot DDL.docx (60.8k)

Tony Saul

CICS Protected Threads / DDL Break-In
(in response to Mark Madsen)
Hi Mark,We use CICS Protected threads extensively and we had to create a process to remove them and then add them back.
I created a REXX that uses CA-SYSVIEW /CICS interface to determine the DB2Entry's in each of the CICS regions, generates a Modify CICS command  with the CEMT (/F <CICS regn>,CEMT SET DB2E(<entry name>) PROTECTNUM(0)) but also generates an dataset with the CEMT commands to set the Protected Threads back on.
You have to allow about 2 minutes from the time you set Protectnum to 0 before you try to process anything, as protected threads hang around and are re-evaluated at something like every 2 minutes. 
The DBA's then created a Job to run at the start of the REORG schedule that turns off the Protected threads, run their REORGs (and any other maintenance like Rebinds) and then run another job to turn the Protected threads back on.
Let me know if you want a copy, but if you don't have CA-Sysview then there will be a bit of rework required.
Regards, Tony

On Tuesday, 1 October 2019, 10:55:23 pm ACST, Mark Madsen <[login to unmask email]> wrote:


see upload

Attachment Links: CICS Prot DDL.docx (62 k)  
Site Links: View post online   View mailing list online   Start new thread via email   Unsubscribe from this mailing list   Manage your subscription  

This email has been sent to: [login to unmask email]
Discover the best cloning tool on the market. Try BCV5 & the new BCV5 Masking Tool.
ESAi also has powerful solutions for Buffer Pool Tuning, Log Analysis, TDM, & more.
http://www.ESAIGroup.com/idug



Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2

Tony Saul

CICS Protected Threads / DDL Break-In
(in response to Mark Madsen)
Hi Mark,We use CICS Protected threads extensively and we had to create a process to remove them and then add them back.
I created a REXX that uses CA-SYSVIEW /CICS interface to determine the DB2Entry's in each of the CICS regions, generates a Modify CICS command  with the CEMT (/F <CICS regn>,CEMT SET DB2E(<entry name>) PROTECTNUM(0)) but also generates an dataset with the CEMT commands to set the Protected Threads back on.
You have to allow about 2 minutes from the time you set Protectnum to 0 before you try to process anything, as protected threads hang around and are re-evaluated at something like every 2 minutes. 
The DBA's then created a Job to run at the start of the REORG schedule that turns off the Protected threads, run their REORGs (and any other maintenance like Rebinds) and then run another job to turn the Protected threads back on.
Let me know if you want a copy, but if you don't have CA-Sysview then there will be a bit of rework required.
Regards, Tony

On Tuesday, 1 October 2019, 10:55:23 pm ACST, Mark Madsen <[login to unmask email]> wrote:


see upload

Attachment Links: CICS Prot DDL.docx (62 k)  
Site Links: View post online   View mailing list online   Start new thread via email   Unsubscribe from this mailing list   Manage your subscription  

This email has been sent to: [login to unmask email]
Discover the best cloning tool on the market. Try BCV5 & the new BCV5 Masking Tool.
ESAi also has powerful solutions for Buffer Pool Tuning, Log Analysis, TDM, & more.
http://www.ESAIGroup.com/idug



Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2

Russell Peters

RE: CICS Protected Threads / DDL Break-In
(in response to Mark Madsen)

We also use protected threads extensively and also created a process to disable them. We have an in-house cobol program that reads the current settings and creates the commands to set them back after we set them to zero. We disable the protected threads via a batch job each night prior to the nightly batch work and another batch job that runs early each morning to reset the thread protection parameters in each cics region. So thread protection is disabled overnight and reenabled before business hours.

Mark Madsen

CICS Protected Threads / DDL Break-In
(in response to Mark Madsen)
And why do you disable protected threads nightly?
I have a CICS transaction set up as protected(PROTNUM>0) and the package is defined as RELEASE(DEALLOCATE), and we are unable to break-in w/DDL on an object that is tied to that package.
Are you saying that by simply "unprotecting" the thread allows DDL to break-in and execute?
We have PKGREL_COMMIT YES, so a BIND/REBIND can break-in, but DDL can't.

Russell Peters

RE: CICS Protected Threads / DDL Break-In
(in response to Mark Madsen)

We have some batch jobs that will escalate locks or issue lock commands, and we have some jobs that load db2 tables nightly. We had some issues with protected threads preventing the locks and the stop commands associated with table loads so we decided to disable thread protection overnight. We see the most benefit from thread protection during business hours anyway.