Sysadmin User Guide

8/8/2019 Sysadmin User Guide

1/31

System Administration

Users Guide

Table of Contents

define user ........................................................................................................................................................2

MONITOR userS ......................................................................................................................................... ....4define responsibilities .................................................................................................................................... ..5

define request group ........................................................................................................................................7

define menu .....................................................................................................................................................9define request set .......................................................................................................................... ...... ...... .....11

define PRINTER ............................................................................................................................................16

define request/reports .....................................................................................................................................21

concurrent request ..........................................................................................................................................25

concurrent requests phase and status .......................................................................................................... ...27

administer concurrent managers ....................................................................................................................29

49261958.doc 1


2/31

DEFINE USERDEFINE USERResponsibility: System Administrator

Security > User > Define

Figure 2.1 Define User window

Steps:Users Window

Use this window to define an application user. An application user is an authorized user of Oracle Applications and/orOracle Self-Service Applications who is uniquely identified by an application username. Once defined, a new applicationuser can sign on to Oracle Applications and access data through Oracle Applications windows.

Users BlockUser NameAn application user enters this username to sign on to Oracle Applications.

The username must not contain more than one word.

You should use only alphanumeric characters ('A' through 'Z', and '0' through '9') in theusername.

PasswordEnter the initial password of an application user

A password must be at least five characters and can extend up to 100 characters.

You should use alphanumeric characters ('A' through 'Z', and '0' through '9') in apassword. All other characters are invalid.

This window does not display the password you enter. After you enter a password, you must re-enter it toensure you did not make a typing error.

As System Administrator, you can set an initial password or change an existing password, butyou cannot access the user's chosen password.

Person, Customer, and SupplierUse these fields to enter the name of an employee (person), customer, or supplier contact. Usethe List of Values to select a valid name.E-Mail/FaxEnter the E-mail address and/or fax number for this user.

49261958.doc 2


3/31

Figure 2.1.1 Define User window

Password ExpirationDaysEnter the maximum number of days between password changes. A pop-up window prompts an applicationuser to change her or his password after the maximum number of days you specify has elapsed.

AccessesEnter the maximum allowed number of sign-ons to Oracle Applications allowed between password changes.A pop-up window prompts an application user to change her or his password after the maximum number ofaccesses you specify has elapsed.

Effective Dates From/ToThe user cannot sign onto Oracle Applications before the start date and after the end date. The default forthe start date is the current date. If you do not enter an end date, the username is valid indefinitely.You cannot delete an application user from Oracle Applications because this information helps to provide anaudit trail. You can deactivate an Oracle Applications user at any time by setting the End Date to the currentdate.If you wish to reactivate a user, change the End Date to a date after the current date, or clear the End Datefield.

Responsibilities BlockResponsibility

Select the name of a responsibility you wish to assign to this application user. A responsibility isuniquely identified by application name and responsibility name.

From/ToYou cannot delete a responsibility because this information helps to provide an audit trail. Youcan deactivate a user's responsibility at any time by setting the End Date to the current date.If you wish to reactivate the responsibility for the user, change the End Date to a date after thecurrent date, or clear the End Date.

49261958.doc 3


4/31

MONITOR USERSMONITOR USERSResponsibility: System Administrator

Security > User > Monitor

Figure 2.2 Monitor User window

Steps:Monitor Users Window

Use this window to monitor what your application users are currently doing. You can see whichusers are signed on and what responsibilities, forms (windows), and terminals they are using.You can also see how long they have been logged in and what ORACLE processes they areusing.In addition, you can monitor all users at a site, all users accessing a specific application or aspecific responsibility, or you can monitor individual users. You can only monitor those users forwhom you have activated Sign-On Audit.

Monitor Users BlockResponsibilityThe user's responsibility only appears if you have enabled Sign-On Audit at either theResponsibility or Form audit level.Form

The user's form only appears if you have enabled Sign-On Audit at the Form audit level.LoginThe user's login name.TimeThe length of time the user has been logged on to this application.ORACLE ProcessThe ORACLE process of the user.Terminal NameThe name of the terminal that the user is working on.

49261958.doc 4


5/31

DEFINE RESPONSIBILITIESDEFINE RESPONSIBILITIESResponsibility: System Administrator

Security > Responsibility > Define

Figure 3.1 Define Responsibility window

Steps:Responsibilities Window

A responsibility determines which applications functions a user can use, which reports and concurrent programs the usercan run, and which data those reports and concurrent programs can access.

Note: Responsibilities cannot be deleted. To remove a responsibility from use, set the Effective Date's To field to

a past date. You must restart Oracle Applications to see the effect of your change.

Responsibilities BlockAn application name and a responsibility name uniquely identify a responsibility.

Responsibility NameIf you have multiple responsibilities, a pop-up window includes this name after you sign on.

ApplicationThis application name does not prevent the user of this responsibility from accessing other applications'forms and functions if you define the menu to access other applications.

Responsibility KeyThis is a unique name for a responsibility that is used by loader programs. Loaders are concurrent programsused to "load" such information as messages, user profiles and user profile values into your OracleApplications tables. To help ensure that your responsibility key is unique throughout your system, begineach Responsibility Key name with the application short name associated with this responsibility.

49261958.doc 5


6/31

Effective Dates From/ToEnter the start/end dates on which the responsibility becomes active/inactive, and if you do not enter an enddate, the responsibility is valid indefinitely.

Available FromA responsibility may be associated with only one applications system. Select between Oracle Self-ServiceWeb Applications or Oracle Applications.

Data GroupName/ApplicationThe data group defines the pairing of application and ORACLE username.Select the application whose ORACLE username forms connect to when you choose this responsibility. TheORACLE username determines the database tables and table privileges accessible by your responsibility.Transaction managers can only process requests from responsibilities assigned the same data group as thetransaction manager.

MenuThe menu whose name you enter must already be defined with Oracle Applications.

Request GroupName/ApplicationIf you do not assign a request security group to this responsibility, a user with this responsibility cannot runrequests, request sets, or concurrent programs from the Submit Requests window, except for request setsowned by the user. The user can access requests from a Submit Requests window you customize with arequest group code through menu parameters.

Menu Exclusions BlockDefine function and menu exclusion rules to restrict the application functionality accessible to aresponsibility.

TypeSelect either Function or Menu as the type of exclusion rule to apply against this responsibility.

When you exclude a function from a responsibility, all occurrences of that function throughout theresponsibility's menu structure are excluded.

When you exclude a menu, all of its menu entries, that is, all the functions and menus of functionsthat it selects, are excluded.

NameSelect the name of the function or menu you wish to exclude from this responsibility. The function or menuyou specify must already be defined in Oracle Applications.

49261958.doc 6


7/31

DEFINE REQUEST GROUPDEFINE REQUEST GROUPResponsibility: System Administrator

Security > Responsibility > Request

Figure 3.2 Define Request Group window

Steps:Request Groups Window

Use this window to define a request group. A request securitygroup is the collection of requests,request sets, and concurrent programs that a user, operating under a given responsibility, canselect from the Submit Requests window.System Administrators:

Assign a request security group to a responsibility when defining that responsibility. Aresponsibility without a request security group cannot run any requests using the SubmitRequests window.

Can add anyrequest set to a request security group. Adding a private request set to a

request security group allows other users to run that request set using the Submit Requestswindow.

Request Groups BlockGroup - Use the request group's name to assign the request group to a responsibility on theResponsibilities window.Application - Select the name of the application you wish to associate with your request group.This application name does not prevent you from assigning requests and request sets from otherapplications to this request group.Code - Assign a code to this request group.

49261958.doc 7


8/31

Requests BlockSpecify the requests and request sets in the request group.TypeChoose program or set to add one item, or choose application to include all requests in anapplication

49261958.doc 8


9/31

DEFINE MENUDEFINE MENUResponsibility: System Administrator

Application > Menu

Figure 4.1 Define Menus window

Steps:

Menus WindowDefine a new menu or modify an existing menu.

A menu is a hierarchical arrangement of functions and menus of functions. As a SystemAdministrator, you can restrict the functionality a responsibility provides by defining rulesto exclude specific functions or menus of functions.

Menus BlockMenu entries detail the options available from your menu.MenuChoose a name that describes the purpose of the menu. Users do not see this menu name.

User Menu NameYou use the user menu name when a responsibility calls a menu or when one menu callsanother.

Menu Entries BlockSequence

Enter a sequence number to specify where a menu entry appears relative to other menuentries in a menu.

49261958.doc 9


10/31

Navigator PromptEnter a user-friendly, intuitive prompt your menu displays for this menu entry. You see this menuprompt in the hierarchy list of the Navigator window.SubmenuCall another menu and allow your user to select menu entries from that menu.

49261958.doc 10


11/31

DEFINE REQUEST SETDEFINE REQUEST SETResponsibility: System Administrator

Concurrent > Set

Figure 5.1 Define Request Set window

Steps:Defining Request Sets

By defining request sets, you can submit the same set of requests regularly using a singletransaction. You use the Request Set window to create and edit request sets. Alternatively, youcan use the Request Set wizard to create simple request sets.

To create a request set:

1. Navigate to the Request Set window.2. Enter a Name for your request set.3. Enter a Short Name for your request set. This name is used internally to reference yourrequest set.4. Enter the Application with which you want to associate your request set.5. Enter a Description of your request set if you like.6. The Owner field defaults to your username and can only be changed by your systemadministrator.

7. Enter the Active Dates From and To fields to define an effective period when you and otherscan run the request set. If the current date is outside the range you define, the request set will notbe available in the Submit Requests window.8. Check the Print Together check box to send all your requests to the printer together when theycomplete, or uncheck the check box to send each request one at a time to the printer as itcompletes.9. Check the Allow Incompatibility check box to allow your system administrator to specifyprograms that this request is incompatible with (may not run with). Leave Allow Incompatibility

49261958.doc 11


12/31

unchecked to specify that this request set may run with all other concurrent requests or requestsets.10. Choose Define Stages orLink Stages if you have finished defining your stages.

Figure 5.2 Define Request Set window (Stages)

Defining Stages

1. The value for the Display Sequence is defaulted in sequence as you enter your stages. Youmay change the display order of the stages by modifying this field.2. Enter a Name for the stage.3. Enter a Description of your stage if you like.4. Enter a Short Code for the stage. This code is used internally to reference the stage.5. In the Function field of the Function region, use the List of Values to select a function. Thedefault value for this field is the Standard Stage Evaluation function. This function bases itscompletion status on the normal completion status of the requests it contains.6. Use the "The Return Value of this Stage Affects the Set Outcome" checkbox if you want toensure that the request set's completion status is equal to the completion status of this stage.

Note: If you choose this checkbox for more than one stage, the completion status of therequest set will equal the completion status of the last of these stages to run within the set.

7. Use the Allow Incompatibility check box to allow your system administrator to specify programsthat this stage is incompatible with (may not run with). Leave Allow Incompatibility unchecked tospecify that this stage of the request set may run with all other concurrent requests or requestsets.8. Choose Requests.

49261958.doc 12


13/31

Figure 5.3 Define Request Set window (Stage Requests)

Stage Requests window

In the Stage Requests window you define which requests you want to include in the stage.9. Select the report or program you want to include in your request set. A description of the

request you choose and its associated application appears in the Description and Applicationfields.The list of requests you can choose includes the requests that your responsibility's request grouplets you access from the Submit Requests form.10. The Print Options region reflects the options for the current request. Specify the number ofCopies of output to print, the Style to print, the Printer to print to, and whether to save the outputto an operating system file.

Note: Some requests may have a required Style or Printer that you cannot change.

11. Use the Allow Stage Function to Use This Program's Results check box to indicate whichprograms or reports should be included.12. When you are done with the Print Options, choose Parameters to display the RequestParameters window.

49261958.doc 13


14/31

Figure 5.3 Define Request Set window (Request Parameters)

Request Parameters Window

The Request Parameters window lets you customize the parameter values of a specific request ina request set.13. The Sequence field displays the order in which each request parameter appears when yourun the request in the Submit Requests window.

14. The Prompt field is a display-only field that shows the request parameter's prompt.15. Check the Display check box to specify that you can see a request parameter at submissiontime, or uncheck the check box to specify that a parameter should not be displayed at submissiontime.16. Check the Modify check box to specify that you can insert or change the value for a requestparameter at submission time, or uncheck the check box to specify that a parameter cannot bechanged at submission time.17. Use the Shared Parameter field to set a default value for a parameter that occurs in more thanone report or program of a request set.18. Optionally enter a Default Type and Value for the parameter.19. Save your work.20. Go back to the Stage Requests window and repeat Steps 9through11to add more requeststo the request set stage.You can select a request more than once if you want to run the same request with differentdefault parameter values.21. To start a new stage, return to the Stage window and choose New Record from the FileMenu.

49261958.doc 14
http://opt/scribd/conversion/tmp/scratch6516/@reqwin#reqwinhttp://opt/scribd/conversion/tmp/scratch6516/@reqwin#reqwinhttp://opt/scribd/conversion/tmp/scratch6516/@lststp#lststphttp://opt/scribd/conversion/tmp/scratch6516/@lststp#lststphttp://opt/scribd/conversion/tmp/scratch6516/@lststp#lststphttp://opt/scribd/conversion/tmp/scratch6516/@reqwin#reqwinhttp://opt/scribd/conversion/tmp/scratch6516/@lststp#lststp


15/31

Figure 5.4 Define Request Set window (Link Stages)

Link Stages

1. Enter the Start Stage. The stage you enter here is the first stage submitted for the request set.2. Enter the stages you want to run following the first stage in the Success, Warning, and Errorcolumns. To ensure that a particular stage follows the preceeding stage regardless of thecompletion status, enter the desired stage in all three columns. To stop the request set if a stageends in Error, leave the Error column blank. Any time you do not specifically indicate which stage

should follow for a completion status, the request set will exit on that completion status.

49261958.doc 15


16/31

DEFINE PRINTERDEFINE PRINTERResponsibility: System Administrator

Install > Printer > Register

Figure 6.1 Define Printer window

Steps:

Printers WindowRegister printers with Oracle Applications by entering the operating system's name for the printerand assigning it a printer type

You must register a printer before you can print reports from it, using Oracle Applications.

Printers BlockTypeSelect your printer type. Some reports require a printer of a specific type in order to printcorrectly.You can only select a previously defined printer type.

Use the Printer Types button to open a window to define a printer type.

49261958.doc 16


17/31

Figure 6.2 Define Printer Type window

Printer Types WindowUse this window to define a printer type and to assign print styles and their corresponding printerdrivers to the printer type.

Defining printer types allows you to assign print style and printer driver definitions to any numberof printers by registering the printers as a specific "type".

Printer Types BlockTypeEnter a name for a printer type. Example printer types might be "LINE" for a line printer or "LN03"for an LN03 model printer.You select this printer type when you register a printer using the Printers window.

Printer Drivers BlockUse this block to assign print styles and printer drivers to your printer types.

The Style button opens the Printer Styles window.

The Driver button opens the Printer Drivers window.

49261958.doc 17


18/31

Figure 6.3 Define Printer Style window

Print Styles Window

Use this window to define print styles. A print style describes how your report should be

printed. Not all reports work with all print styles. You may define additional print styles to customizeyour reports.Once defined, a print style cannot be deleted.

Print Styles BlockDefine a print style. The combination of Name and User Name uniquely identifies a print style.

SequenceEnter a number that determines the display sequence for your print style when performing a queryin this window.Style Name

Multiple print styles display alphabetically in a list window according to their Name. You cannotupdate a print style's name.User Style NameThis user name does not appear anywhere except this window.DriverEnter the name of the Oracle Reports (SRW) driver to be called when printing an applicationsreport generated by Oracle Reports. This field is used only by applications reports generated byOracle Reports.

49261958.doc 18


19/31

Suppress Header FlagReports may print with a header page that indicates who requested the report and when. Checkthe Supress Header Flag check box to define a print style that suppresses printing of this headerpage.ColumnsDefine the number of columns per page.RowsDefine the number of rows per page.OrientationOrientation of the Report Output.

Figure 6.4 Define Printer Driver window

Printer Drivers WindowUse this window to define your printer driver and printer commands.

NameThe printer driver name must be unique for a given platform.User Driver NameThis user name is referenced by Oracle Applications and must be unique for a given platform.SRW DriverEnter the name of the Oracle Reports (SRW) printer driver.

Driver Method RegionCommand - The printer driver executes within an operating system shell.Program - The printer driver executes directly as a program, not through an operating systemshell.Subroutine - The printer driver executes a predefined Oracle Applications routine.

Driver Method Parameters Region

49261958.doc 19


20/31

Spool File - Select whether the printer driver creates its own copy of a file for printing. If this checkbox is checked when the Driver Method is set to Program, the print program creates its own spoolfile.Standard Input - Select whether the printer driver accepts standard input. Uncheck this check boxwhen the Driver Method is set to Program. Unless the program accepts standard input, this checkbox should always be unchecked.Program Name - Select the name of a Program the driver invokes if the driver method isProgram.

InitializationEnter the initialization string that must be sent to the printer before the printer driver can beginprinting.

ResetEnter the reset string that returns the printer to its ready state when printing is complete.

49261958.doc 20


21/31

DEFINE REQUEST/REPORTSDEFINE REQUEST/REPORTSResponsibility: System Administrator

Request > Run

Figure 7.1 Submit a New Request window

Steps:Submitting a Request

Standard Request Submission gives you control over how you run your requests and requestsets. This section describes how you customize and submit a request using the Submit Requestwindow.

To submit a request:

1. Navigate to the Submit a New Request window (Other-> Requests -> Run).2.Check the Request option to submit single requests, or choose to submit a predefined group

of requests by checking Request Set.3. Choose OK.

49261958.doc 21


22/31

Figure 7.2 Submit Request window (Parameters window)

Steps:

4.Select the Name of the request (report or program) you want to run from the list of available

requests.5.A Parameters window automatically appears if you select a request that requires parametervalues and your profile option

6. Once you enter the values in the required parameter fields and choose OK, the Parameterswindow closes, and your parameter values are concatenated and displayed in theParameters field.

7.Choose Schedule to specify a time how you want to run your request.8.Choose Schedule to specify the printer and number of copies for the output of you request

and if you want to notify other users of your request.9. When you are done specifying scheduling and completion options, choose Submit.

Once you submit your request, the Requests window opens and provides you with the currentstatus of your request and the request ID number.Oracle Applications assigns a request ID to each request submission so that you can identifythe results of the request when it is complete. You can use the request ID to query for yourrequest output in the Requests window. Oracle Applications also assigns a new request IDnumber to each resubmission of a request and displays the request ID in the log file of theprevious request.

49261958.doc 22


23/31

Figure 7.3 Submit Request window (Schedule Request)

Defining a Submission ScheduleThe scheduling window provides you with several scheduling options. You can choose to re-usea schedule you previously defined and saved, or define a new schedule.

Choose a type of schedule from the following:Apply a Saved Schedule Allows you to re-use a previously defined and saved schedule.As Soon as Possible Submits your request as soon as possible.Once Submits your request once at the time and date you specify.Periodically Submits your request repeatedly at the interval you specify.On Specific Days Submits your request repeatedly on specific days of the week or month.

Note: Whether a request completes successfully or in error, Oracle Applications immediatelysubmits the next run only if the next requested start date and time is on or before the end dateand time you specify. If you do not specify an end date, the request or request set repeatsindefinitely until you cancel it.If your request contains date parameters, you can choose "Increment date parameters each run"to have the value for that parameter be adjusted to match the resubmission interval.

To save your schedule, check the Save this schedule check box. You must also provide a uniquename for each schedule you save. Optionally, enter a description of your schedule.

Choose OK.

49261958.doc 23


24/31

Figure 7.4 Submit Request window (Completion Option)

Defining Completion Options

In the Upon Completion... region, use the Save all Output Files to write your request output to afile. If you wish to view your output online, you must use this check box.

Specify additional people to notify, or replace your name if you do not want to be notified.

Select a language for each person notified.

Select a print style from the poplist.

Use the LOV to select the printers you want used to produce a hard copy of your report. Eachprinter will produce at least one copy of the report. If you need more than one copy for a particularprinter, use the Copies field to enter the number of copies you want printed.

Note: Some requests may have a required Style or Printer that you cannot change.

Choose OK.

49261958.doc 24


25/31

CONCURRENT REQUESTCONCURRENT REQUESTResponsibility: System Administrator

Concurrent > Request

Figure 8.1 Concurrent Request window

Steps:Using the Requests Window

Use the Requests window to view a list of all submitted concurrent requests, check whether yourrequest has run, change aspects of a request's processing options, diagnose errors, or find theposition of your request in the queues of available concurrent managers.

Each record shows you the request ID, request name, phase and status of the request, as well asthe parameters used by the request. If the request is part of a request set, the request ID for theparent request is provided in the Parent column.

Use the Refresh Data to refresh the status of your request.Use the Find Requests window to specify the types of requests you want to see.

Use the Submit New Request to submit another request.

You can Cancel a request or put it on Hold if the status of the Request is pending. If the status iscompleted, you can view the output or the logs generated by the request.

Once you have cancelled a request you cannot undone it.

Choose Details to view the details of the request submission.

49261958.doc 25


26/31

Choose Diagnostics to display a window containing information about when the requestcompleted and if it did not complete, a message explaining why not.

Choose View Log to display the request's error log file.

Choose View Output to view the request output.

49261958.doc 26


27/31


28/31

Individual Request Progress

Generally when you submit a request, its phase is Pending, which means that it has not yetstarted running. When it does start running, its phase changes to Running. Upon completion thestatus of the request becomes either Success, Warning or Error. If your request ends in warningor error, you can use the Diagnostics button in the Requests window to view any diagnosticmessages stored in the log file.

Request Set Progress for Stages

When you submit a request set, all the requests in a stage run simultaneously and the phase andstatus of the set begins as Pending Normal until an available concurrent manager can process it.When a concurrent manager becomes available, the stages's phase and status change toRunning Paused as the stage waits for all of its requests to finish. Then the stage changes fromRunning Paused to Running Normal to write completion information in the report and log files.Finally, the stage phase changes to Completed and its status becomes Success, Warning, orError.

Progress of Individual Requests in a Stage

When a stage submits its requests, all requests start as Pending Normal, then change to RunningNormal, and finally end as either Completed Success, Completed Warning, or Completed Error.

Progress of Linked StagesWhen you submit a request set with more than one stage, the request set submits all the stagesbut only runs one stage at a time, ensuring that each stage completes before submitting the next.Each stage shows a phase of Pending and a status of Normal while it waits for a concurrentmanager to process it. As the next available concurrent manager processes the stage, therequest set phase and status changes to Running and Paused, as the first stage begins to run.After each stage finishes, the request set temporarily changes to a Normal status to checkwhether the stage ended in error and to determine whether to stop or which stage should beprocessed next based on how you linked the stages when you defined the request set.

Once the check is done for a completed stage, the set goes back to Paused status during whichthe next stage runs. The set alternates between Normal and Paused status for each stage in theset. The set itself resumes running (Running Normal), after all the requests finish, to write

completion information in the report and log files. The set ends in a Completed phase, either withSuccess, Warning or Error status. A request set ends when a stage ends with a completion statusthat does not link to a subsequent stage.

49261958.doc 28


29/31


30/31

Requests Running/Requests PendingTypically, when there are requests pending, this number should be the same as the number ofactual processes. However, if there are no pending requests, or requests were just submitted, thenumber of requests running may be less thanthe number of actual processes.Moreover, if a concurrent program is incompatible with another program currently running, it doesnot start until the incompatible program has completed. In this case, the number of requestsrunning may be less than number of actual processes even when there are requests pending.

StatusThis field displays the status of a manager after you have chosen a specific action for it using thetop row of buttons near the bottom of the window.You can control concurrent managers individually or collectively by controlling the InternalConcurrent Manager. This field is blank when managers have been activated by the InternalConcurrent Manager.

In a parallel processing environment, this field displays Target node/queue unavailable when theprimary and secondary nodes (or system queues) are not available.

Controlling a Specific ManagerThe actions you can choose for controlling a manager are:

TerminateWhen you terminate requests and deactivate the Internal Concurrent Manager, all runningrequests (running concurrent programs) are terminated, and all managers are deactivated.Managers previously deactivated on an individual basis are not affected.You can terminate requests and deactivate individual managers. All running requests(running concurrent programs) handled by the manager are terminated.Once deactivated, a manager does not restart until you select the manager and choose theActivate button.

DeactivateWhen you deactivate the Internal Concurrent Manager, all other managers are deactivated aswell. Managers previously deactivated on an individual basis are not affected.You can deactivate individual managers. Once deactivated, a manager does not restart untilyou select the manager and choose the Activate button.When you deactivate a manager, including the Internal Concurrent Manager, all requests

(concurrent programs) currently running are allowed to complete before the manager(s) shutdown.

Verify This choice appears only when you select the Internal Concurrent Manager.The Internal Concurrent Manager periodically monitors the processes of each concurrentmanager. You can force this process monitoring or PMON activity to occur by choosing theVerify button.Another result of selecting this choice is that the Internal Concurrent Manager rereadsconcurrent program incompatibility rules.

Restart This choice appears only when you select an individual manager.When you restart a concurrent manager, the manager rereads its definition.You should restart a manager when you have made the following changes using the DefineConcurrent Manager form, and you wish those changes to take effect:- Change work shift assignments

- Modify the number of Target Processes- In a parallel concurrent processing environment, change node or system queue information

ActivateWhen you activate the Internal Concurrent Manager, you activate all other managers as well,except those managers that were deactivated on an individual basis.You cannot activate the Internal Concurrent Manager from the PC client. The InternalConcurrent Manager is only activated from the server.You can also activate an individual concurrent manager that is currently deactivated, so longas the Internal manager is active. If the manager is defined to work in the current work shift,then the Internal manager starts it immediately.

49261958.doc 30


31/31

Reviewing a Specific ManagerView details of a concurrent manager's operation.

ProcessesYou can view the details of the processes of a given concurrent manager. Processes that arecurrently active, migrating, or terminating, as well as processes that have been terminated ordeactivated, are displayed.

Requests For a selected manager you can view all running and pending requests handled by themanager.

Documents

Sysadmin User Guide