Work Process in PRIV Mode

[former_member182034]

Dear All,

after getting the result of transactions, Users did not close/export the resulted window for a long time as you see in below image and due to this, work process went in PRIV mode.

here If i kill the session then user complain about it that why kill the session?

what i have to do with resulted window? what will be the impact if I did not close the session?

as I shared the value of parameters if there Is any solution then please share?

Regards,

[Former Member]

Hi Abdul,

Have you set the auto log out and maximum process runtime parameters applicable for dialog work processes. You may force the users the run long jobs in background.

You may need to look into what program is doing to have further analysis.

Regards,

Deepak Kori

[former_member182034]

hi deepak,

I hope you did not see the table against PRIV which is showing nothing after refresh mean User got the result and file opened for a long time mean user did not close/export the result. please check

Regards,

[Former Member]

Hi Abdul,

I have understood your point and hence recommended to check for GUI auto log out time .

SAP parameter rdisp/gui_auto_logout. This shall kill the sessions automatically based on idle time and avoid PRIV situation.

If user is not doing anything in the system and consuming system memory, he has to be logged out of the system.

You may additionally find out what programs/tcode user is running to further fine tune the same.

Regards,

Deepak Kori

[former_member182034]

Dear Deepak,

I already set the value

rdisp/gui_auto_logout=7200

rdisp/keepalive=600

rdisp/keepalive_timeout=60

but our PM is saying that please don't use these parameter because users are getting disconnection issue ;-).

one more thing which I want to tell You that we are getting this issue against Z report and PM is saying that we have to facilitate to our users so, please do R&D about this issue and resolve it?

please mention your recommendation

Regards,

majamil1@gmail.com (Plz add)

[Former Member]

Hi Abdul,

rdisp/gui_auto_logout=7200

This value is too high on a production system. Its around 2 hrs.

Default value is 600 and you may increase it to say 900 ( 15 mins).

Any report running beyond this in foreground should be moved to background.

I hope these PRIV processes are dialog work processes. Please confirm.

As you mentioned these programs are Z-Program. Could you find out are the users really waiting after the results are on screen or do they perform some other activity ?

Regards,

Deepak Kori

[former_member182034]

Dear Deepak,

Any report running beyond this in foreground should be moved to background.

yes. issue arise in dialog work process not background.

As you mentioned these programs are Z-Program. Could you find out are the users really waiting after the results are on screen or do they perform some other activity ?

over all System performance is OK but  this issue against one Z-Report and only 3 users are executing this Z-report and execution time is not issue. issue is here that users said we need to open the result for maximum time even whole day and you please don't terminate the session.

Dear Orkun and Deepak

what I have to do mean increase the parameters value

PHYS_MEMSIZE=24576

em/address_space_MB = 8192

ztta/roll_extension_dia = 8192000000

or

rdisp/gui_auto_logout=900

(If I do then gui logout after 900 seconds while I already mentioned the users and PM's wish)

need recommendations for PM and users from your(Orkun & Deepak) end

Regards,

[Former Member]

Hi Abdul,

 issue is here that users said we need to open the result for maximum time even whole day and you please don't terminate the session.

Its a matter of change management which Project Manager has to act upon. I have never seen a situation where an ouput of an report should be kept open for entire day.

Another Alternative:

Incase its just a plain report which fetches data from tables and displays on the screen, request your abaper to add some piece of code to download this automatically on the user desktop.

Let the users view the report on the desktop for the whole day.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

>> This configuration will configure extended memory to use max 8GB memory. It means that the process will allocate the heap memory when 8GB quota level exceeded.

I noted the effect, already

[Former Member]

You can run transaction in background mode. In this case you wouldn't lock dialog workprocesses in PRIV mode. The output results are available in spool for this job at any time.

[Former Member]

>> You can run transaction in background mode. In this case you wouldn't lock dialog workprocesses in PRIV mode.

It is correct, but there's a potential 2GB memory quota restriction for the heap memory. For example, when the process try to allocate more than 2GB, the process will face with memory quota problem. To solve that "ztta/roll_extension_nondia" needs to be configured more that 2GB

Best regards,

Orkun Gedik

[Former Member]

But any message about dumps as of memory issues, only PRIV mode for process.