DB Cyclic Job

Hi,

One of the DB Cyclic Job which runs for every 5 minutes consumes shared memory during every execution and doent release the memory after the job completion. Shared memory free keeps reducing every day.

How can we fix this issue. Its in our production environment and no other environments is having this issue.

Hi Noel,

Does the job allocate any memory dynamically? Can that be avoided? Does the job compete ok, or is there any error?

As you are working on a production environment please consider to raise a support case for this to seek further dedicated assistance.
When raising the case I recommend you to provide a MFESDIAGS diagnostics collection for review and also details of the shared memory increasing (showing how you monitor that), and also can you consider to share the job used (and related source files/programs) that gives the behaviour, that should help speed up the investigation.

Hi Kim,

the job is running for almost 3 years and it doesnt fail until unless if there is any application/data related or DB connectivity issues.

How can I verify about the memory allocation ? is it in ESMAC or?

Hi Noel,
As I do not have a good understanding of your environment nor application it is difficult to provide further advise through this forum, that is why I recommend you to raise the support case, as I advised previously.

Does your COBOL Application use the ALLOCATE statement, docs:
https://www.microfocus.com/documentation/enterprise-developer/ed70/ED-VS2017/GUID-EE81BF4C-1152-4654-A509-77E0C90B0444.html  if yes then would that be a reason why memory is used everytime it is being executed?

Hi Kim,

I went through one of the program(eventhough i am unaware of what is inside) i couldnt find any word as allocate or memory using the search option in notepad++.