|
View previous topic :: View next topic
|
| Author |
Message |
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
I defined a sniffer program as a message handler in my provider pipeline, but I don't want it to be active all the time... to much overhead. I tried making two different pipeline definitions (one with and one without the sniffer), then deactivating one and activating the other. But, that caused all sorts of conflicts in CICS that resulted in killing CICS as the only resolution.
So, anyone have any ideas how to activate/deactivate a pipeline sniffer? |
|
| Back to top |
|
 |
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
| After much fooling around, I determined the best way to activate/ deactivate a pipeline sniffer was to restart CICS with a different pipeline definition specified. In a production environment this is not usually possible. Unfortunately, the only other option is a dummy Sniffer program you can swap with a real Sniffer in the program folder. |
|
| Back to top |
|
|
|
|
