To Log in From the Command Line

1

for MVS jobs, Memname is displayed _ for other jobs, Job name is displayed

To log in from the command line:1 Choose Start => Run. 2 Enter the following command in the Open text box: emgui -u <user_name> -p <password> -m <hostname> [-vp <ViewPoint>]

CONTROL-M/Enterprise Manager window (truncated) Table 7 Log in command arametersParameter Descriptionuser_name Name of the CONTROL-M/EM user. Note: If the username or password is incorrect, the Log in dialog box is displayed. Reenter the username and password.password CONTROL-M/EM user password.Note: If the user name or password is incorrect, the Log in dialog box is displayed. Reenter the user name and password.hostname Name of the host computer on which the GUI Server is installed.ViewPoint Name of the ViewPoint that is displayed automatically when CONTROL-M/EM starts. optional.Note: If the ViewPoint name is incorrect (due to incorrect spelling or because the ViewPoint does not exist), the Open ViewPoint dialog box is displayed

2

Net Overview Miniature version of the FlowDiagram, indicating the part of the network currently displayed in the FlowDiagram. By dragging the selected area in this view to a different part of the network, you can quickly navigate in a complex environment. For more information,

3

4

5

6

Each ViewPoint contains the following components:_ Collection: Which jobs in the enterprise are loaded into memory from the CONTROL-M/EM Database. Jobs are selected for a collection according to the values in the job processing parameters specified in the job’s job processing definition._ Hierarchy: The order in which the selected jobs are displayed. The criteria available for hierarchy levels are the parameters in job processing definitions (for example, Application, Group, Cyclic, etc.), job status (for example, Ended OK) and job state (for example, Held).

7

OR

8

Choose View => Refresh Now to display these jobs. Or click

Node is nothing but control-M.

To Step In to an entity in FlowDiagram:Right-click a high-level node and choose Step In from the menu, or click . -or- Double-click the high-level node if the Tools => Options => Flowdiagram - Nodes => Double Click option is set to Step into item (the default).

9

To expand or collapse the display:1 Right-click a node, and select Collapse or Expand from the menu. -or- Double-click the node to toggle the Collapse/Expand function.To collapse or expand multiple nodes in the Flow Diagram:1 Hold down the Ctrl key and select the desired nodes. -or- Right-click a node and select Collapse or Expand from the menu.

Critical path A critical path is the maximum runtime for a series of jobs or the longest pathbetween those jobs. Critical path is calculated by selecting the nodes for the first and last jobs in the series in the FlowDiagram of the active ViewPoint. All nodes between the selected nodes are considered, and the critical path calculation returns the expected runtime for the longest possible combination of jobs between the selected nodes.To calculate a critical path:1 In the FlowDiagram, expand all relevant group nodes so all jobs to be included in the critical path are visible. 2 Select the first and last nodes in the path in the FlowDiagram. Last node should be a descendent of the first node, but not immediately below it. 3 Right-click the node and choose Critical Path, or choose Action => Critical Path to display the Critical Path dialog box.

Right-click a job in the Details list and select Export to File. A Windows Export to File dialog box is displayed.

Enhanced WhyEnhanced Why enables you to identify jobs that failed to run OK that are predecessor jobs (jobs that are In conditions for a subsequent job) of a selected job. You can choose to identify only the oldest predecessor job that failed to run OK, or all predecessor jobs. This feature can help you determine why a selected job or Group Scheduling table failed to run as expected. The Enhanced Why option is available when a single node in Wait status is selected in either the FlowDiagram or Tree View of the activeViewPoint.

10

Click details – it shows the details in above.

11

Creating ViewPoints using the ViewPoint WizardThe ViewPoint Wizard is used to create a new ViewPoint. It automatically displays screens that allow you to define new collections, global filters, and hierarchies or select existing ones. These components determine which active jobs are displayed in the ViewPoint window and how they are displayed. You are taken step-by-step through the process of creating a new ViewPoint. The ViewPoint Wizard window can be opened at any time during a CONTROL-M/EM session to create a new ViewPoint.To create a new ViewPoint using the ViewPoint Wizard:1 Choose File => New ViewPoint or click . A series of windows (called the ViewPoint Wizard) is displayed. The wizard leads you through the steps in creating a new ViewPoint. Each window contains instructions for completing the necessary step._ Click Next to accept the data entered and proceed to the next step. _ Click Back to return to the previous window.As you click Next, you will progress through the following windows, described below:ViewPoint Wizard – Collection window – Existing Collection pane

To open the ViewPoint Manager:1 Select Edit => ViewPoint Manager from the CONTROL-M/Enterprise Manager menu bar, or click . The ViewPoint Manager window is displayed:

Click New, or right-click and choose New from the menu. Specify a name for the new ViewPoint and click OK. The ViewPoint Properties window is displayed.To edit an existing ViewPoint:

12

1 Select the ViewPoint from the ViewPoint Tree and either click Edit, or right-click and choose the Edit option from the menu. -or- Double-click the ViewPoint in the ViewPoint Tree.

Creating and modifying collectionsThe ViewPoint Manager is also used to create a new collection or modify an existing one. A collection defines which jobs in the enterprise are loaded into memory. Jobs are selected for a collection according to the values in the job processing parameters specified in the job’s job processing definition.To create a new collection:1 Select the word Collections or the name of any collection in the ViewPoint. 2 Click New, or right-click and choose New from the drop-down menu. The following dialog box is displayed.

Creating filters dynamicallyDynamic Filters are defined as you need them (“on the fly”) and are discarded when you are finished with them. Dynamic filters are not defined in advance, as are global filters (also known as regular filters), which are pre-defined. _ With the desired ViewPoint open, select the File --> Dynamic Filter menu option. _ With the desired ViewPoint open, select the <Dynamic Filter> value in the ViewPoint’s Filter list.When you open the Open ViewPoint dialog box and click Dynamic Filter..., the Dynamic Filter dialog box is, by default, empty. However, once you have defined a dynamic filter for a ViewPoint, the dynamic filter definition is kept, and redisplayed whenever you click Dynamic Filter... for the ViewPoint, until you clear this filter definition. (The dynamic filter definition is displayed even if you subsequently selected a different filter from the filter selection list.)

13

Status Selection dialog box — Filtering by StatusTo dynamically filter by job status (for example, Ended OK), click the button in the Status field. This displays the Status Selection dialog box

Saved dynamic filters can be used again at a later time. Only users with access to the computer on which these filter presets are saved can access these filters.

14

Jobs managed by CONTROL-M are handled according to parameters that are specified in job processing definitions. These definitions are created using CONTROL-M/Desktop and are stored in scheduling tables (job directories) according to various criteria that you determine. For example, jobs that generally runtogether (concurrently or in sequence) should be placed in the same Scheduling table.The basic process of job definition is described below. For detailed information aboutthis process, see the CONTROL-M/Desktop User Guide.Defining job processing i1 Choose Tools => CONTROL-M/Desktop in the CONTROL-M/EM window to start CONTROL-M/Desktop.

15

2 Either create new scheduling tables and job processing definitions, or modify existing ones by loading definitions into CONTROL-M/Desktop using the following steps:A Choose File => Load jobs from CONTROL-M/EM. B Enter filter criteria to help locate the relevant data center, scheduling tables, and jobs.C Select the scheduling tables and job processing definitions to load. D Select either online or local mode. E Click Load. The jobs are loaded into the current CONTROL-M/Desktop draft. 3 Choose Edit => Job => New Job for a new job or double-click an existing job to display the Job Editing form to create or modify the job processing parameters.4 When you have finished modifying the jobs and scheduling tables: A If definitions were loaded to CONTROL-M/Desktop in local mode, choose Edit => Scheduling Tables => Write to CONTROL-M/EM to save the definitions to the CONTROL-M/EM database.B In the Scheduling Table Manager (accessed using the Edit => Scheduling Tables => Scheduling Table Manager option), select the scheduling tables and click Upload to save the definitions to the CONTROL-M database.Creating many jobs using a job template in CONTROL-M/Desktop1 Use the Mass Job Creation and Skeleton facilities to create multiple job processing definitions.2 Use the Job Editing form to modify the new job processing parameters as necessary.3 Use the FlowDiagram View in the CONTROL-M/Desktop window to create dependencies between jobs.4 Upon completion, choose Edit => Scheduling Tables => Write to CONTROL-M/EM.Other handling of scheduling tables in CONTROL-M/DesktopThe Scheduling Table Manager is a component of CONTROL-M/Desktop and is used to:_ View a list of scheduling tables_ Modify or delete an existing scheduling table, or create a new scheduling table _ Force or order a table_ Upload new or modified tables to the CONTROL-M/Server database in a specified CONTROL-M installation _ Download tablesOrdering and forcing jobs or scheduling tablesTypically, jobs are placed in the Active Jobs file when the New Day procedure or User Daily job scans job processing definitions. However, you can also manually place jobs in the Active Jobs file by using the Order or Force options. _ When you order a job, CONTROL-M examines the job’s scheduling criteria. If the criteria are satisfied, the job is placed in the Active Jobs file. The Order option is useful for newly-defined or modified jobs that did not exist or were not selected at the time the New Day or User Daily procedure was executed. _ When you force a job, CONTROL-M places the job in the Active Jobs file regardless of the job’s scheduling criteria.

16

Defining calendars in CONTROL- M/DesktopTo open the Calendar Manager window, choose Edit => Calendars in CONTROL-M/Desktop.

17

CONTROL-M, application, and group nodes are high-level nodes. You can request more details about any of these nodes by right-clicking the node, and choosing Status Summary from the popup menu.Right-click the desired node to display a pop-up menu. 2 Choose Status Summary. The Status Summary window is displayed.

18

Job node details Details about specific jobs can be used for analyzing the jobs and managing the job scheduling flow.Job details are viewed and updated using the Job Editing form. Note that updated details will affect only the parameters of the job in the Active Jobs file in CONTROL-M. The original job processing definition cannot be changed from the CONTROL-M/EM window._ Double-click the job node. _ Select the job and choose Action => Properties._ Right-click the job. Choose Properties from the popup menu.

19

Doc Lib Name of a library or directory containing the documentation file. Note: To access the documentation, the ser must be defined and have authorization on the CONTROL-M where the documentation resides. Time Zone Global time zone used to calculate the interval for time-related conditions. Command Text of the command line to be submitted for the job when the Task Type parameter is Command. Description Description of the job.

20

21

22

After editing or adding a condition in this panel, click the check button next to the condition to save the changes and/or add the condition to the list. The following buttons are available for each section of this panel:

OUT Condition DescriptionName Name of the prerequisite condition. Date Date reference. Same as IN Condition.+ / - Indicates whether to add or delete the condition.The Resources panel is used to define Quantitative and Control resources. The panel contains two sections. Quantitative resources are defined in the left section; Control resources are defined in the right section.

23

The Set panel is used to specify AutoEdit variables to be set up in the job’s script before job submission.

The Steps panel indicates conditional post processing actions to be performed, depending on the outcome of specified statements. This panel is used to define On Statements and Do Statements. It contains a list of already-defined On/Do Statements. Below the list is the Text line for defining newOn Statements. The line for defining new Do Statements is not displayed.To display the Do Statement line: 1 Click the DO button at the side of the Step Codes section.To display the On Statement line: 1 Click the ON button .After editing or creating an On/Statement Character string that is matched to the job’s log statement records. Code Character string that is searched for in the job’s log error code.

24

MVSstep

Job actionsRight click on any job

25

Bypass (MVS only)Choosing Bypass from the Action menu opens a dialog box containing a list of options with a check box or each. The default for these check boxes is unchecked, but if some options were selected in a previous Bypass action, these settings are retained. The available options are described

Confirm

26

Choose Confirm from the Action menu or job node popup menu, or click the Confirm button. When this option is chosen for a job with Wait User [pink] status, the job is confirmed and can run.

Delete Choose Delete from the Action menu or job node popup menu, or click the Delete button. This option changes the state of the job and its appearance in the CONTROL-M/Enterprise Manager window as follows:

If the job has not yet started, it is prevented from running even after all submission criteria are satisfied. The job remains visible until after the next cleanup of the Active Jobs file by the New Day procedure or by a manual request_ If the job is currently executing, the Delete option is not available._ If the job has completed executing, it cannot be manually rerun after it is deleted.

DocumentationChoosing Documentation from the Action menu or job node popup menu opens the Documentation window. This window enables you to view the documentation member (DOC MEM) of the selected job.

Edit JCL/Script Choose Edit JCL/Script from the Action menu, from the job node popup menu, or by clicking the Edit JCL/Script button. This option opens a window that in which you can edit the job script using a text editor and update the job script member in the relevant CONTROL-M installation.

Enhanced Why Selecting Enhanced Why from the Action menu or the job node popup menu displays the Enhanced Why dialog box. This feature enables you to display the predecessor jobs and Group Scheduling tables for a selected job or Group Scheduling table.

Force OK The Force OK option changes the status of the job to Ended OK and changes the color of the job node to green. It can be used for jobs with a status of Ended Not OK or for jobs in a Wait status (such as Wait Time, Wait Cond). You can activate Force OK from the Action menu, or from the job node popup menu of jobs that Ended Not OK.

27

Force OK – no Post Processing The Force OK – no Post Processing option changes the status of the job to Ended OK and changes the color of the job node to green. Job post processing actions, however, are not performed. This option can be used for jobs with a status of Ended Not OK or for jobs in a Wait status (such as Wait Time, Wait Cond). You can activate the option from the Action menu, or from the job node popup menu of jobs that Ended Not OK.Free Choose the Free option from the Action menu, the job node popup menu, or by clicking the Free

button. This option removes the padlock from the job node of Held job in the CONTROL-M/Enterprise Manager window. When freed by the user, the job resumes processing at whatever point it was stopped by the Hold option.Hold Selecting Hold from the Action menu, the job node popup menu, or clicking the Hold button, changes the state of the job. In the CONTROL-M/Enterprise Manager window, a padlock is added to the job node (shown below).

_ If the job has not started to execute, it is prevented from executing even after all submission criteria are satisfied. The job remains in this state until released using the Free option (described below)._ Any job that is executing when held will remain with Executing status until it is freed._ If the job has completed executing, it cannot be manually rerun until released by you via the Free option.Kill Choose Kill from the Action menu or from the job node popup menu. This option terminates a job that is currently running and its processes. The action is recorded in the job log.Log Choose Log from the Action menu or the job node popup menu. This option displays the log of the specified job. The Job Log window enables you to view job records extracted from the CONTROL-M log

in the CONTROL-M installation. React (MVS only) Choose React from the Action menu or the job node popup menu. This eactivates post-processing for the selected job.

Rerun Select Rerun from the Action menu or job node popup menu, or click the Rerun button. This option reruns the job.

Restart (MVS only) Choose Restart from the Action menu or the job node popup menu. This option opens the Job Restart dialog box. In this dialog box, specify the procedure and/or programsteps for the job restart. Optionally, you can also specify whether to perform abend code and condition code recapture and step adjustment, and the name of a member in the CONTROL-R PARM library that contains defaults to be applied to the restart.

28

Statistics Choose Statistics from the Action menu or job node popup menu. This option opens a popup window containing the following job statistics: _ Job ID. The Job ID of the job._ Start Time. Time when the job began to run. _ End Time. Time when the job finished running._ Elapsed. The job’s elapsed run time. _ CPU. CPU time used to process the job.Undelete Choose Undelete from the Action menu or from the job node popup menu of a job with Delete status. This option causes the job to revert to its appearance and state before the job was deleted.View JCL/Script Choose View JCL/Script from the Action menu or job node popup menu, or click the View JCL/Script button. This option opens a window that allows you to view the job script statements.

View Sysout List Choose Sysout from the Action menu or job node popup menu, or click the Sysout button. This option opens a window that displays a list of the job’s Sysout (output) information.

29

WhyChoose Why from the Action menu or job node popup menu, or click the Why button (available only for those jobs that have not begun executing). This option opens the Why window. You can use this window to: _ View the conditions, resources, etc., for which the job is waiting._ Create a missing prerequisite conditions that is needed by the job, so that the job can be submitted for execution. _ Enter a specific date for a condition with the date values **** or $$$$.

To add missing prerequisite conditions listed in this window by selecting them andthen clicking the Add Condition button.To add missing prerequisite conditions:1 Click on the line in the Why window that describes the missing condition. 2 Click the Add Condition button. A Confirm Details window is displayed. 3 Click OK to confirm the addition of the condition.

Activating ApplicationsThe Applications Activation feature enables you to insert job processing parameters from a CONTROL-M job or Group Scheduling table into a command line used to activate a third-party program. For any application, you define the command line, including the job processing parameters, using the Activate Applications Editor, and then save the Application Activation definition. The definition can then be usedwhenever needed. To use the definition to activate the application, select the desired CONTROL-M jobor Group Schedulin table in the active environment, and run the application using the application activation definition The job processing parameters in the application activation definition arereplaced at runtime

30

To define an Application Activation definition:1 Perform one of the following actions in the Activate Applications Editor: _ If you are creating a new Application Activation definition:A Click New ( ). A blank entry box is displayed in the Applications window. B Specify a unique name for the Application Activation definition. _ If you are modifying an existing Application Activation definition, select the definition in the pplications window. The current parameters for the definitionare displayed in the Program, Initial Dir and Parameters fields.2 Fill in (or modify the entries in) the Program, Initial Dir, and Parameters fields as follows: _ To browse to the desired path (relevant for the Program and Initial Dir fields):

31

A Click Browse ( ) to the right of the field. B Navigate to the desired program or directory level.C Click the mouse. The selected program or path appears in the field. _ To specify a literal value, type the value in the field. _ To insert a job processing parameter:1 Click Menu ( ) to the right of the field. Parameter categories (for example, General, Active, Execution) are displayed. 2 Place the cursor over one of the categories. Parameters in that category (for example, Job Name, Owner) are displayed.A Select the desired parameter. A specially formatted version of the parameter is inserted in the field (inTo change the name of an Application Activation definition:1 In the Applications window of the Activate Applications Editor, double-click the entry that you want to rename. 2 Edit the name as desired, and press Enter.To delete an Application Activation definition:1 In the Applications window of the Activate Applications Editor, select the name of the definition you want to delete. 2 Click Delete. 3 If a confirmation prompt is displayed, confirm the deletion. The definition is removed.To run an application using an Application Activation definition:1 Select a job or Group Scheduling table node in the flow diagram or the navigation tree.

2 Right-click the node. A popup menu is displayed, listing the Activation options for the job.3 Choose Activate Application. A list of available application action definitions is displayed.4 Select the Application Activation definition that you want to run. The popup menu closes and the program runs, using the command line and Scheduling table parameters specified in your definition.

_ In/Out Conditions – The In Conditions and Out Conditions displayed for a group scheduling table are conditions that were defined for the entire table as well as conditions defined for the individual jobs in the table. When displaying each job node in the group scheduling table, only conditions defined for the individual jobs are displayed in the flow diagram.

32

Actions – Different actions can be performed on group scheduling tables depending on the current context, for example, whether or not the group is defined for an MVS platform. Available actions are described in

Right-click the Group Scheduling Table node.2 Choose Properties from the popup menu. The Group Editing form is displayed.

33

34

35

Choose Tools => Alerts. The Alerts window is displayed, with your user name and the Global Alerts Server name shown in the title bar.

36

To focus on the job in the FlowDiagram to which an alert refers:1 Right-click the line containing the alert. 2 Choose Find Job from the pop-up menu.The relevant node is displayed and selected in the CONTROL-M/Enterprise Manager ViewPoint window.To filter the alert messages displayed:1 Click the Filter Alerts check box, and fill in the filtering criteria in the filter fields.You can supply multiple values in each field, separated by commas or semicolons. You can also use pattern-matching strings in the filter fields to simplify the task of inserting multiple criteria. To open the Alert Details window:1 Double-click the alert message in the Alerts window. The Alert Details window is displayed.

To display a Local View:1 Click , or choose Tools => Alerts to display the Alerts window.2 Select an alert from the window.3 Right-click the alert to display the pop-up menu. Choose Open into ViewPoint. A new ViewPoint is displayed in the GUI.To modify the display properties of Local View ViewPoints1 Choose Tools => Options, and in the displayed Options dialog box, select the Alerts panel.

37

A set of conditions and resources windows allows you to view and change entries in all Control resources, Quantitative resources and prerequisite conditions in the production environment. Generally, before a requested window (example: Control Resources window) is displayed, an appropriate filtering dialog box (example: Resources dialog box) is opened. Note however that no filtering dialog box is displayed before the Global Conditions window. Filtering reduces not only clutter in the window, but retrieval overhead as well. The filtering criteria last specified in the dialog box are redisplayedwhen the dialog box is reopened.2 Enter filter criteria and click OK. The Control Resources window is displayed

38

39

3 Click Add Resource. The new resource is added to the database.To delete Control resourcesIn the Control Resources window, select the resources to be deleted and click Delete. Shared Control resources can be deleted only if: _ No jobs “own” or request the resource. (The Counter field is 0 for all resource table entries for the resource.)_ No jobs are requesting the resource. (There are no table entries for this resource with a Requested resource type.)

40

The Prerequisite Conditions window lists all prerequisite conditions in the CONTROL-M environment. Conditions can be added and deleted using this window. (For detailed information describing Prerequisite (In and Out) conditions.

41

Select Resources => Global Conditions. A Global Conditions window appears.

42

To open the Communication Status window:Choose Tools => Communications => Status. The Communication Status window is displayed.

Communication between CONTROL-M/EM componentsCONTROL-M/EM must be constantly connected to the GUI server. The GUI server handles communication between each GUI and other CONTROL-M/EM components.OverviewIf the connection to the GUI server fails, CONTROL-M/EM attempts to reestablish the connection using alternate servers. CONTROL-M/EM attempts to connect to the first available alternate GUI server defined in the Reconnection panel of the Options dialog box ._ If successful, the CONTROL-M/EM GUI continues to function, restoring ViewPoints as desired. The CONTROL-M/EM GUI – Reconnect dialog box closes and a message in the status bar indicates that a communication problem was resolved. _ If unsuccessful, CONTROL-M/EM attempts to connect to the next server in the list. _ If CONTROL-M/EM cannot establish a connection with any of the alternateservers, it re-attempts connection with the servers at regular (user-defined)

43

intervals, until the maximum number of allowed retries has been attempted. If a connection still cannot be established, CONTROL-M/EM displays a message notifying you that it is about to shut down.By clicking Stop, you can stop the reconnection process to: _ Modify reconnection settings (by clicking Settings in the Advanced dialog box). _ Terminate CONTROL-M/EM (by clicking Exit Application).

Tools-environment

44

45

46

Reconnection panelThe Reconnection panel (Figure 139) contains several default settings for reconnecting to an alternative server if the connection to the CONTROL-M/EM GUI server is lost.

47

48

49

Load modes for working in CONTROL-M/Desktop_ Local mode This mode is particularly useful when many modifications must be made to a scheduling table, and exclusive access to an entire scheduling table is preferred. To prevent multiple users from updating the same scheduling table concurrently, CONTROL-M/Desktop automatically locks the entire scheduling table when it is loaded in local mode.After creating or modifying job processing definitions in a draft, the user must perform the Write to CONTROL-M/EM operation to save all definitions back to the CONTROL-M/EM database. CONTROL-M/Desktop automatically unlocks a scheduling table when it is written back by the user or when the user ends the CONTROL-M/Desktop session._ Online mode This mode is used when modifications to definitions are not extensive (meaning,small, localized corrections are necessary), and can be made without interfering with the work of other users. This mode enables all users to view and access definitions without locking the scheduling table until a user starts modifying a definition. When that user saves the modifications, the modifications are saved directly to the CONTROL-M/EM database and the scheduling table is unlocked.

50

Tree viewThe left pane of the draft window displays a tree of job processing definitions in the draft. This “tree” is based on parameters in each job processing definition and can be displayed using either of two parameter hierarchies: —CONTROL-M HierarchyCONTROL-M hierarchy is based on job processing parameters: CONTROL-M, Scheduling Table and Mem Name. —Application Hierarchy Application hierarchy is based on job processing parameters: Application, Group and Mem Name.

51

52

53

Collections A collection is a selection of jobs in a draft. CONTROL-M/Desktop allows you define a collection of the jobs upon which to work. This is especially useful for applying mass updates to all job processing definitions in a collection. By default, the collection on which you work includes all jobs in the draft. You can adjust the collection as often as needed. You can also add and delete specific jobs from a collection without having to define a new collection that would omit those jobs.Scheduling Table Manager The Scheduling Table Manager lists all scheduling tables in the CONTROL-M/EM database. It is used to modify, delete, force or order an existing scheduling table, create a new scheduling table, and upload or download scheduling tables to the CONTROL-M/Server database in the indicated CONTROL-M installation.Calendar Manager A CONTROL-M calendar contains a list of dates, usually spanning a number of months or years, which can be used as a basis for scheduling jobs. The dates on which a job can be ordered are limited by the calendars named in the scheduling parameters of the job processing definition. If no calendar is specified, the job is ordered solely on the basis of the other scheduling parameters. The Calendar Manager is used to define and edit calendars, and upload and download calendars from the CONTROL-M/EM database to the indicated CONTROL-M/Server database.Starting CONTROL-M/Desktop To start CONTROL-M/Desktop Perform either of the following: _ Choose Start => Programs => CONTROL-M Enterprise Manager => CONTROL-M/Desktop.-or- _ Select CONTROL-M/Desktop from the Tools menu in the CONTROL-M/EM GUI The following window is displayed.

54

55

To switch to List Mode view1 Select the item in the Navigation Tree. 2 Change the view using the List/Job Editing option from the View menu. The details for the selected item are displayed in list format in the work area.

56

Editing Form viewTo display the editing form for a job or group in the Work Area pane:1 Double-click the job or group in the Navigation Tree. The appropriate editing form is displayed in its own dialog box. -or- Select the job or group in the Navigation Tree, and change the view using theList/Job Editing option from the View menu. The editing form is displayed in the work area.Each entity (application, group, CONTROL-M, scheduling table, job, or group scheduling table) in the Flow Diagram is represented by a node. The smallest entity is the job node. The top part of the job node contains the Job Title. The area inside the job node is called the Job Area. Two fields from the job processing definition are displayed in the Job Area below the Job Title. The Job Title and the twofields to be displayed in the Job Area can be customized in the Flowdiagram – Nodes panel of the Options dialog box. In this same Flowdiagram - Nodes panel, the user can also request that displayedvalues be wrapped if they are too long for display on single lines (otherwise the values are truncated).

1 Select View => Flowdiagram.

57

Drafts The repository for storing and working on job processing definitions in CONTROL-M/Desktop is called a draft. Drafts can contain job processing definitions from either a single scheduling table or from multiple scheduling tables. Drafts are totally independent of CONTROL-M and the CONTROL-M production environment. Because of this independence: _ Work can be saved without undergoing validity checks. _ Users do not require direct access to CONTROL-M, or the CONTROL-M platform,to be able to work in CONTROL-M/Desktop. At sites where only the CONTROL-M administrator has direct access to CONTROL-M, personnel from other departments can still work in CONTROL-M/Desktop._ CONTROL-M does not have to be operational for job processing definitions to be created using CONTROL-M/Desktop. _ Working in CONTROL-M/To open an existing draft:

1 Choose File => Open or click Open on the toolbar.2 Choose the drive, directory, and draft, and click Open. Only one draft can be open at a time. Therefore, when you open a draft, CONTROL-M/Desktop automatically closes the previously opened draft (if it isstill open): _ If no changes have been made to the previous draft, it is closed automatically._ If changes have been made, you are prompted to save the changes. The previous draft is then closed accordingly. 3 Modify the draft as wanted, as described under “Modifying drafts.”4 Choose File => Save or click on the toolbar. To create a new draft:1 Choose File => New or click New on the toolbar. 2 Modify the draft as wanted, as described under Chapter 2, “Modifying drafts.”. 3 Choose File => Save or click on the toolbar.Loading scheduling tables and jobs from the CONTROL-M EM databaseJob processing definitions and scheduling tables can be loaded from the CONTROL-M/EM database into

the current draft. Choose File =>Load jobs from CONTROL-M/EM, or click .The Load Jobs window is

58

displayed.

When displayed for the first time in a session, the Filter Tables and Jobs fields are blank. The next time this window is opened, the fields remain populated from the previous load. _ To load all scheduling tables and jobs, click Load without specifying filter criteria. 3 In the Filter Tables and Jobs area, specify criteria which will help you locate the job processing definitions and scheduling tables you want to load (for example, the CONTROL-M on which the scheduling tables reside, the group, and so on).A When specifying values for the filter criteria: _ An And relationship exists between all specified fields._ A blank field is equivalent to specifying *, meaning all values are returned for that field if left blank._ Use commas to separate multiple values. _ When specifying a data center in the CONTROL-M field: Specify an expression by selectingB Click Apply. 4 Select the check boxes next to the desired data centers, scheduling tables and jobprocessing def initions. _ You can expand and collapse the entities as needed by clicking the plus (+) andminus (-) signs. Click Load. The Load Scheduling Table Results window is displayed.

59

Determining if you are working in online or local modeThe following are indications that you are currently working in online mode: _ The title bar of the Flow Diagram window displays the words “Online Mode” instead of the name of a draft.

To write definitions to the CONTROL-M/EM database:1 Open the draft containing the job processing definitions for the scheduling table.2 Choose Edit => Scheduling Tables => Write to CONTROL-M/EM, or click . theWrite to CONTROL-M/EM window is displayed.

3 Select the scheduling tables that you want to write to the CONTROL-M/EM database.4 Click Write. The scheduling tables are written to the CONTROL-M/EM database.

60

To select the Application hierarchy:1 Click the Application Tree button in the toolbar. -or- Choose View => Hierarchy => Application/Group/Job.To select the CONTROL-M hierarchy either:1 Click the CONTROL-M Tree button in the toolbar. -or-Choose View => Hierarchy => CONTROL-M/Sched. Table/Job. 1 Right-click the node in the Navigation Tree. 2 Choose Find In Flowdiagram from the menu.To expand or collapse multiple nodes in the Flow Diagram:Hold down the Ctrl key and select the wanted nodes. -or- Right-click a node and select Expand or Collapse from the pop-up menu.Stepping In and Out You can focus the Flow Diagram on jobs in only selected applications, groups,CONTROL-M installations or scheduling tables. This option limits the Flow Diagram to only jobs in the selected entities. Stepping In and Out of the Flow Diagram is not the same as Expanding andCollapsing. _ When you Expand a part of the Flow Diagram, the groups and applications orscheduling tables and CONTROL-M installations are still displayed in the window._ When you Step In to a part of a Flow Diagram, only the nodes in the selected entities are displayed. When you Step Out, the window returns to the previous display.

61

62

Moving jobs The location of a job in the Navigation Tree corresponds directly to the values ofcertain parameters in the job processing definition (Application, Group, CONTROL-M, and Scheduling Table). You can change the values of these parameters using either the Navigation Tree or the Job Editing form: _ If you change the location of a job in the Navigation Tree, the corresponding valuesin the job processing definitions are automatically changed accordingly.To move a job in the Navigation Tree:Use the mouse to drag the job from one location in the Navigation Tree and drop it ina different location: _ With the Application hierarchy displayed, drag a job from one group to another.Note that the destination group does not need to be in the same application. Parameters Application and Group are automatically modified to reflect the new location of the job._ With the CONTROL-M hierarchy displayed, drag a job from one scheduling table to another in the same or a different CONTROL-M. The CONTROL-M a

63

Copying jobsYou can copy a job processing definition from a source job and create a new, identical job processing definition. The new job is given the same name as the source job, and identical properties (conditions, resources, and so on). The new job is assigned a unique identification number, so that it can be differentiated from the source job. The new job is created in the same group or table as the source job, and it is added in the appropriate place in the Flow Diagram.Alternatively, you can perform a combined Edit and Copy. This operation displays the copy of the source job in the Job Editing form. You can then edit the copy of the job before you save it to the database._ Right-click the job node of the source job in the Flow Diagram, and select Copy from the pop-up menu._ In the Flow Diagram, select the job node of the source job, and choose Edit => Job => Copy.A copy of the job, with a unique identification number, is added to the Flow Diagram.To perform an Edit and Copy operation on a job (local mode only)1 Use one of the following methods to copy a job: _ Right-click the job node of the source job in the Flow Diagram, and select Edit and Copy from the pop-up menu._ In the Flow Diagram, select the job node of the source job, and choose Edit => Job => Edit and Copy.To delete an item from the Navigation Tree:1 Select the item to be deleted in the Navigation Tree. 2 Press Delete or click the Delete Job button on the toolbar. 3 Confirm the deletion in the Confirmation window that is displayed.To delete a job in List Mode view:1 Click the job to be deleted. 2 Press the Delete key. -or- Click . -or- Right-click the selected item and select Delete from the menu.3 Confirm the deletion.To delete a job from the Flow Diagram:1 click the job to be deleted. 2 Press the Delete key, click , or right-click the selected item and select Delete from the menu. 3 Confirm the deletion.To delete multiple jobs from the Flow Diagram:1 Select the jobs to be deleted by holding down the Ctrl key and clicking on each of the job nodes.2 Press the Delete key, click , or right-click the selected item and select Delete from the menu.3 Confirm the deletion. To delete all jobs in an application, group, CONTROL-M, or scheduling table from the Flow Diagram: 1 Click the appropriate application, group, CONTROL-M or scheduling table node.2 Press the Delete key, click , or right-click the selected item and select Delete from the menu.

64

3 Confirm the deletion. When an upper level node is deleted, all the lower level nodes (for example, groups, tables, or jobs) are deleted.Creating dependenciesPrerequisite conditions (In conditions and Out conditions) can be created, modified, and deleted from within the Flow Diagram.You can view and create job dependencies in the Flow Diagram. These dependencies are determined by IN and OUT statements defined in job processing definitions, and group scheduling tables. The following symbols are used to indicate job dependencies in the Flow Diagram:_ Connectors at the bottom of predecessor job nodes or group nodes represent the Out conditions._ Connectors at the top of the successor job nodes or group nodes represent the job’s In conditions._ Dependency lines drawn between Connectors represent the dependencies between the various jobs and groups.1 Click the predecessor job node and drag the mouse to the successor job node. CONTROL-M/Desktop creates the In/Out Connectors and Dependency line. When you create a dependency, CONTROL-M/Desktop automatically adds the required In conditions and Out conditions to the job processing definitions.1 Right-click the connector line.2 Select Goto In Connector or Goto Out Connector from the pop-up menu.To delete a dependency between jobs:Right-click the dependency line of the condition that you want to delete. The following popup is displayed:

Condition nodesPrerequisite conditions can be displayed as separate nodes in the Flow Diagram. When displayed, conditions appear as elliptical icons (condition nodes) linked to the various types of nodes in the Flow

Diagram. To display Condition nodes: Tools => Options, and select the Flowdiagram- LinksGroup scheduling tables can be created (in local mode only), modified, and deleted in the Flow Diagram graphical environment.To open an existing Job Editing form in the Flow Diagram:_ Double-click the job in the Navigation Tree or the job node in the Flow Diagram. -or- _ Right-click a job node in the Flow Diagram, and select Edit Job from the menu. The Job Editing form is displayed. You must close the Job Editing form using the OK or Cancel button at the bottom of the form, before you can return to the original display.To open a Job Editing form for a new job: Choose Edit => Job => New Job, or click Choose Edit => Job => New Job from the menu bar

65

Same like EM Scheduling is in desktop only

66

Resources panelThe Resources panel is used to define Quantitative and Control resources. Quantitative resources are defined in the left side of this panel. Control resources are defined in the right side.

67

To create multiple jobs with similar parameters:1 Select the Tools => Mass Create option from the menu bar. --or-Click the Mass Job Creation button on the toolbar. The Mass Create Form dialog box is displayed.Specify the number of jobs to create and the name of the Skeleton that contains the parameters to be defined for all the new job processing definitions

Number of jobs to create Number of jobs to create using the specified skeleton. Default: 10. Skeleton Skeleton to be applied to the new jobs. To select a different Skeleton, click on the arrow in the Skeleton field and select the Skeleton from the list. Skeletons can be modified or created using the Skeleton Editor form. This form is displayed by clicking the Edit Skeletons button (described below). For more information. Edit Skeletons Opens a skeleton editor for the specified skeleton. For more information.

68

Example: Create multiple jobs for various applicationsCreate 40 job processing definitions for several different applications or groups which all include a certain set of parameters and values. The recommended method for creating these jobs using one skeleton is as follows:1 Specify the wanted Skeleton name in the Mass Create Form dialog box. 2 Specify the parameters and values in the Skeleton Editor work area. 3 Specify the first Application name and Group name (e.g., App1, and Group1). 4 Click OK to save the changes. 5 Specify the number of jobs wanted for the first group (e.g., 10). 6 Click OK to create the jobs. 7 Repeat Steps 3 through 6 for each application or group.

Job skeletons click edit skeletons in tools-massupdate are templates that are used for the creation of multiple job processing definitions. Each job skeleton contains a set of parameters and values. When a job skeleton is used to create new jobs, the new jobs automatically include the parameters and values that are specified in the skeleton. By modifying a skeleton and reapplying it to related jobs, the jobs can also be modified simultaneously.All job skeletons are created and modified using the Skeleton Editor form. To open the Skeleton Editor form click the Edit Skeletons button in the Mass Create Form dialog box. The Skeleton Editor form can also be opened by selecting the Job Skeleton option on the menu bar or by clicking the Edit Skeleton

69

To create a new skeleton1 Click New. 2 Specify a name for the new Skeleton and click OK. An empty Skeleton Editor formis displayed. 3 Specify the wanted Skeleton fields and values in the work area. 4 Click OK to save the Skeleton and to close the Skeleton Editor form.To create a new skeleton based on the values of an existing skeleton1 Select the existing Skeleton in the Skeleton name list box on the CONTROL-M/Desktop tool bar.2 Click Copy. Specify a name for the new Skeleton and click OK. The new Skeleton is displayedwith the same fields and values as the Skeleton from which it was copied. 4 Make the necessary changes in the Skeleton Editor work area.5 Click OK to save the new skeleton and to close the Skeleton Editor form.To modify a skeleton1 Select a Skeleton in the Mass Create Form dialog box. 2 Click the Edit Skeletons button. The Skeleton Editor form is displayed. 3 Make the necessary changes in the Skeleton Editor work area.4 Click OK to save the changes and to close the Skeleton Editor.To delete a skeleton 1 Select the Skeleton in the Skeleton name list box at the top of the Skeleton Editor form. 2 Click the Remove button.To add a row to the Skeleton windowPlace the cursor in the last cell of the table and press <Tab>.To delete a row From the Skeleton windowPlace the cursor in any row of the table and press <Delete>.To clear all fields in the currently displayed skeletonClick the Clear button.

Defining skeletons for jobs running on specific applicationsWhen Application is clicked, the Skeleton Editor window expands to display additional controls. These controls are used to define skeletons for jobs that are run on specific external applications, such as SAP or Oracle Applications.

In conditions and Out conditionsTwo types of information can be specified about prerequisite conditions in a job skeleton.

70

_ Format for the conditions automatically defined when dependencies are created in the Flow Diagram view (by clicking on one job and dragging the cursor to the dependant job)._ Actual In conditions and Out conditions defined in the job skeleton that should be part of each job processing definition that is created using the skeleton. Each of these types of condition information is described in the following pages.

Condition FormatIn the Flow Diagram view of CONTROL-M/Desktop, you can create dependencies between jobs by clicking on a job node and dragging the mouse cursor to a dependant job. When you do this, an Out condition is automatically defined in the job processing definition of the first job, and a corresponding In condition is added to the job processing definition of the second job. The Condition Format field in the Skeleton Editor dialog box indicates the format these automatically defined conditions.

Specifying In conditions and Out conditions in a skeletonIn conditions and Out conditions specified in a job skeleton are added to each job processing definition created using that skeleton. Each In condition or Out condition contains multiple fields. Therefore, addition, modification and deletion of these conditions differs from the methods used for specifying values for other job processing definition fields.To add an In condition or Out condition to a job skeleton:1 Place the cursor in the Field column of the Skeleton Editor work area and select In Conditions or Out Conditions from the list box. A pair of braces {} is displayed in the value column.

2 Click the ellipsis button in the value column. The following dialog box is displayed.

71

3 Enter the name of the In condition or Out condition in the Name field. Values for Date and And/Or can be selected from lists or they can be entered manually. The Parentheses field is used to group conditions for implementation of And/Or logic with groups of conditions. For more information about And/Or logic and prerequisite conditions see the CONTROL-M Job Parameter and Variable ReferenceGuide.4 Click OK when finished. Multiple In conditions and Out conditions can be defined in a job skeleton.Updating multiple jobs and group scheduling tables1 Select the Tools => Mass Update. -or- Click the Mass Update button on the tool bar. The Mass Update window is displayed.

2 Fill in the table in the work area of the Mass Update window. Each line in the table can specify criteria that determine which job processing definitions are updated, or to specify a field to be added or updated. 3 Click the Draft option button to apply the changes to all jobs and group scheduling tables in the draft, or the Collection option button to apply the changes only to jobs in the current collection.4 Click Apply to perform the update. -or- Click Close to close the Mass Update window without performing the requested function.Mass updating of In conditions and Out conditionsEach In condition or Out condition contains multiple fields. Therefore, addition, modification and deletion of these conditions in the Mass Update Form dialog box differs from the methods used for specifying values for other job processing definition fields.Using the Mass Update facility, you can: _ Search for job processing definitions with various types of In conditions or Out conditions._ Update, add or remove any of the fields in each In condition. _ Add new conditions to all job processing definitions that were selected according to the find criteria in the Mass Update Form.

To find or update In condition and Out condition data:1 Select In Conditions from the list in the Field column of the Mass Update Form. The From and To fields of the form merge and an ellipsis button is displayed on the right. A pair of braces {} are displayed in the merged From/To field.

72

2 Click . The Mass Update [In Condition] dialog box is displayed.

3 Select Find/Update from the Operation list.4 Each condition is described by four fields: Name, Date, And/Or, and Parentheses. You can specify search criteria for any number of these fields. To add In conditions: 1 Select In Conditions from the list in the Field column in the Mass Update Form. The From and To fields of the In Condition line merges, and an ellipsis button is displayed on the right. A pair of braces {} are displayed in the merged To/From field.

2 Click . The Mass Update [In Condition] dialog box is displayed. To filter the draft according to specified criteria: Choose Tools => Collection or click the Edit Collection button on the toolbar. The following

dialog box is displayed:

73

Managing scheduling tables 1 In the CONTROL-M/Desktop window menu, either select Edit => Scheduling Tables => Scheduling Table Manager or click .

74

To copy a scheduling table:1 In the Scheduling Table Manager window, select the scheduling table to be copied, and click Copy (or Ctrl + C). The Copy Scheduling Table dialog box displays details of the selected scheduling table.

Jobs List windowThe Jobs List window lists the jobs and group scheduling tables comprising a selected scheduling table. By default, all jobs and group scheduling tables are displayed.

75

However, you can apply a filter to display only selected jobs.To display the Jobs List for a scheduling table:1 In the Scheduling Table Manager window, select the scheduling table from the list. 2 Click Jobs List, or double-click the selected scheduling table name. The Jobs List window is displayed.

76