A fix is available
APAR status
Closed as program error.
Error description
There is no mechanism for enabling or disabling CICS TG request monitoring exits at runtime. Individual request monitoring exits can implement their own control mechanism specific to that exit. There is no product architected solution for managing this capability.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of CICS Transaction Gateway with * * request monitoring exits. * **************************************************************** * PROBLEM DESCRIPTION: There is no facility to enable or * * disable request monitoring exits at * * runtime. * **************************************************************** * RECOMMENDATION: * **************************************************************** It is not possible to enable and disable request monitoring exits while CICS TG is running.
Problem conclusion
CICS TG has been changed to allow request monitoring exits to be disabled and enabled while CICS TG is running. To disable request monitoring exits issue the SDSF commad: /F <jobname>,APPL=RMEXIT,DISABLE (/F <jobname>,APPL=RMEXIT,DIS) To enable request monitoring exits issue the SDSF commad: /F <jobname>,APPL=RMEXIT,ENABLE (/F <jobname>,APPL=RMEXIT,ENA) The CICS TG for z/OS information center will be updated with the following information: Topic: Java request monitoring exits Section: Controlling request monitoring user exits dynamically Request monitoring exits can be activated and deactivated dynamically using the /F <jobname>,RMEXIT,ENABLE and /F <jobname>,RMEXIT,DISABLE commands. Deactivating request monitoring exits stops the exits being driven, but does not cause the exits to be shut down. Activating request monitoring exits causes the exits to be driven for request events, but does not cause the exits to be re-initialized. Topic: Request monitoring exit control Options available for commands sent to all configured and active request monitoring user exits. To get help on the available rmexit options, issue the following command: /F <JOB_NAME>,APPL=RMEXIT,? +----------+-------+-------------------------------------------+ | Option | Short | Comments | | | form | | + ---------+-------+-------------------------------------------+ | ENABLE | ENA | Activate all request monitoring exits. | | | | Defined request monitoring exits will not | | | | be notified that request monitoring exits | | | | have been enabled. | + ---------+-------+-------------------------------------------+ | DISABLE | DIS | Deactivate all request monitoring exits. | | | | Defined request monitoring exits will not | | | | be notified that request monitoring exits | | | | have been disabled. | +----------+-------+-------------------------------------------+ | COMMAND= | CMD | The command that will be sent to all | | commmand | | configured and active request monitoring | | | | user exits. This is a string. | | | | | | | | The eventFired() method is driven with a | | | | RequestEvent command. The command input | | | | data will be included as a string in the | | | | data map with RequestData key | | | | "CommandData". | +----------+-------+-------------------------------------------+ The following messages have been added to CICS TG: CTG8289E Could not enable; request monitoring exits already active Explanation Attempted to activate request monitoring exits, but request monitoring exits are already active. System action The requested action cannot be completed. User response Correct the request and try again. CTG8290E Could not enable; no request monitoring exits defined Explanation Attempted to activate request monitoring exits, but request monitoring exits are not defined in the configuration. System action The requested action cannot be completed. User response Correct the request and try again. CTG8291E Could not disable; request monitoring exits already inactive Explanation Attempted to deactivate request monitoring exits, but request monitoring exits are already inactive. System action The requested action cannot be completed. User response Correct the request and try again. CTG8292E Could not disable; no request monitoring exits defined Explanation Attempted to deactivate request monitoring exits, but request monitoring exits are not defined in the configuration. System action The requested action cannot be completed. User response Correct the request and try again. CTG8295E Cannot specify multiple options for rmexit action Explanation The 'rmexit' action accepts only one of the 'command', 'enable', 'disable' options. System action The requested action cannot be completed. User response Correct the request and try again.
Temporary fix
Comments
APAR Information
APAR number
PM48124
Reported component name
CTG V8 FOR Z/OS
Reported component ID
5655W1000
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2011-09-19
Closed date
2011-12-14
Last modified date
2012-01-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK74806 PM54377
Modules/Macros
CTG00199 CTG00201 CTG00204 CTG00524 CTG00585
SC34712800 | SC34712900 | SC34713000 | SC34713100 | SC34713200 |
Fix information
Fixed component name
CTG V8 FOR Z/OS
Fixed component ID
5655W1000
Applicable component levels
R800 PSY UK74806
UP11/12/23 P F112
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMJ2","label":"CICS Transaction Gateway"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"8.0","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
09 August 2024