client copy disadvantage

[Former Member]

Hi all

can anyone explain what is the disadvantage of running the client copy in dialogue mode?

regards

vijay

[Former Member · Accepted solution]

Dialog work processes can run for a maximum of 600 secs. After

this it would be terminated. This can be increased however using dialog work

processes to perform long running tasks is not advisable because then you would be

holding up dialog work processes and as a result they may not be available to

perform regular dialog based transactions...

Regards,

Jafer

[Former Member]

Hi Vijay,

Background jobs run in a special type of work process—the background work process—that is different from dialog work processes in two ways:

1. A dialog work process has a run-time limit that prevents users from interactively running especially long reports. By default, the system terminates any dialog work process in a transaction that exceeds 300 seconds. Although the value of the limit can be changed (in the system profile parameter

2. rdisp/max_wprun_time ), that limit is always in effect for dialog work processes. No such limit applies to background work processes. Background work processes allocate memory differently than dialog work processes so that background work processes can become as large as they need to in allocated memory to allow for processing large volumes of data.

Having special work processes for background processing provides an additional dimension for separating background processing and interactive work. Typically, background processing and interactive work on the system is separated by time of day. For example, interactive users have the system during the day, large background jobs have the system by night. But the background work process also lets you separate interactive from background use by server, since background jobs can only run on those servers that offer background work processes.

Regards,

Suraj

Message was edited by:

Suraj kumar