Why is Jobflow Monitor (JFM) using excessive CPU at times?

Document ID : KB000021231
Last Modified Date : 14/02/2018
Show Technical Document Details

Summary:

In some cases JFM during the initial build(startup) can go into a high CPU situation.

Instructions:  

**NOTE**

Be sure to download and apply all JFM fixes before you implement.

There are three system options for the C environment to be considered:

HEAPCHK,RPTSTG AND TRACE. These should never be set to ON unless instructed by CA 7 Edition Support for debugging purposes. Another way this can present itself is if there is a CEEOPTS DD pointing to a member in the JFM STC JCL. This DD is not distributed with the default JFM proc--only use this in conjunction with the CEEDUMP DD to get the C information required for debugging purposes if requested by CA 7 Support.

The default member that is in the distributed JFM library contains the following:

DYNDUMP(*USERID,DYNAMIC,TDUMP),TERMTHDACT(UADUMP),
RPTOPTS(ON),RPTSTG(ON)

Before using, change to:

DYNDUMP(*USERID,DYNAMIC,TDUMP),TERMTHDACT(UADUMP),
RPTOPTS(ON),RPTSTG(OFF)

Recommended changes for debugging purposes only:

DYNDUMP(*USERID,DYNAMIC,TDUMP),TERMTHDACT(UADUMP),
RPTOPTS(ON),RPTSTG(OFF),
HEAPCHK(OFF,1,0,0,10),TRACE(OFF)

**Note** If you have turned on the options in the C environment at the system level, then if you specify that option with the OFF value it will disable it also. You would have to add the CEEOPTS DD with the input above.

Additional Information:

 

As always, please contact CA Technologies support for CA 7 if you have further questions.