Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    10
  • Views views
    472
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Micro focus region refresh process taking too long

Venkat Samuvel

Dear Everyone,


We observed that micro focus region refresh is taking too long post upgrade i.e v5.0 Pu24 where as in v4.0 Pu14 it took less than 5 mins.

Here are the observations,

1) Region is started state within a minute after clicking the start tab/issuing the start command.

2) But all the allocated SEP's are in BUSY state with the process “CICS (Facility N/A Transition)” in ES monitor and control page for longer time (30 to 40 mins).

3) CPU% remains 100% until all SEP’s became IDEL state.

4) Server slow until all the process i.e “CICS (Facility N/A Transition) PIP2" are auto cleared up from ESMAC .

5) Multiple entries in the console log with following new message “ESFEV0328I Using native mutexes for thread locking” post upgrade.


Allocated SEP: 51
Admin SEP : 3

Can you please someone assist me to fix this performance issue.

Thanks,

Labels:

Enterprise Server
Parents

  • Suggested Answer

    0  

    Hi Venkat, 


    Have all application modules and region related modules been recompiled tov5.0 Pu24? If not please check that, test again.

     When the SEP's are showing as busy you can navigate to the ESAMC > SEPs area, click on the trace button for one of the BUSY SEPs and check what events are occurring for that SEP/PID.  If that does not help you to understand what the SEPs are busy with or waiting for then I recommend you to raise a support case to seek further assistance, as this will likely require further detailed tracing analysis. Please consider to include a MFESDIAGS diagnostics collection from the time of when the issue is seen. You can download the MFESDIAGS support script from URL: marketplace.microfocus.com/.../mfesdiags

Reply

  • Suggested Answer

    0  

    Hi Venkat, 


    Have all application modules and region related modules been recompiled tov5.0 Pu24? If not please check that, test again.

     When the SEP's are showing as busy you can navigate to the ESAMC > SEPs area, click on the trace button for one of the BUSY SEPs and check what events are occurring for that SEP/PID.  If that does not help you to understand what the SEPs are busy with or waiting for then I recommend you to raise a support case to seek further assistance, as this will likely require further detailed tracing analysis. Please consider to include a MFESDIAGS diagnostics collection from the time of when the issue is seen. You can download the MFESDIAGS support script from URL: marketplace.microfocus.com/.../mfesdiags

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.