If a user does not explicitly enter these options at the time of the request, concurrent processing options default to their user profile values.
As System Administrator, you set user profile values for your end users with the System Profile Values window. Both you and your end users can set some of your own profile values using the Personal Profile Values form.
Concurrent Processing User Profile Options
|User Profile Option||Explanation|
|Concurrent: Hold Requests||"Yes" places concurrent requests on hold. "No" starts programs according to the request's priority and start time.|
|Concurrent: Multiple Time Zones||"Yes" ensures that requests are scheduled immediately regardless of the time zone your client is running in.|
|Concurrent: Report Access Level||Viewing a request's output/log files online and reprinting reports can be accessed according to: "Responsibility" - by anyone using the responsibility that submitted the request "User" - by only the user who submitted the request.|
|Concurrent: Report Copies||The number of output copies that print for each report.|
|Concurrent: Request Priority||Requests normally run according to start time, on a "first-submitted, first-run" basis. Priority overrides request start time. A higher priority request starts before an earlier request. Priorities range from 1 (highest) to 99 (lowest). The standard default is 50.|
|Concurrent: Request Start Time||The date and time requests are available to start running. If the start date and time is at or before the current date and time, requests may be run immediately.|
|Concurrent: Save Output||"Yes" saves concurrent program outputs in a standard file format. Some concurrent programs do not generate an output file.|
|Concurrent: Sequential Requests||"Yes" forces requests to run one at a time (sequentially) according to the requests' start dates and times. "No" means requests can run concurrently when their concurrent programs are compatible.|
|Concurrent: Wait for Available TM||You can specify the maximum number of seconds that the client will wait for a given transaction manager (TM) to become available before moving on to try a different TM.|
|Concurrent: URL Lifetime||This profile option determines the length of time in minutes a URL for a request ouput is retained before it is deleted from the system.|
|Concurrent: Use ICM||"Yes" enables the Internal Concurrent Manager to resolve request conflicts instead of the Conflict Resolution Manager.|
|Printer||The printer which prints your reports.|
|Table 1 - 11. (Page 2 of 2)|
Your users can change the default values for most of the concurrent processing profile options. However, they cannot set Concurrent: Request Priority, Concurrent:Use ICM, or Concurrent: Report Access Level.