Using the Entire Operations Business Functionality

#### Search Results

Search

# Using the Entire Operations Business Functionality

Complementing the details on using the application's access and presentation functionality (character-based user interface, help system, etc.) described in the chapter Using Entire Operations in Online Mode, this chapter provides a brief introduction to the structure and use of the application's business logic, i.e. the operation planning and control functions provided by Entire Operations to define, update and execute job networks, jobs, and ancillary objects.

This document covers the following topics:

- Structure of the Application and its Documentation

- Required Knowledge

- Authorization

- Overview of Objects in Entire Operations

- Overview of the Object-specific Maintenance Functions in Entire Operations

- Three Steps to an Executable Job Network

- Using Control and Monitoring Functions for Job Networks

- Performing ad hoc Actions on Active Jobs in the Active Database

- Creating Ancillary Objects for a Job Network or Job

- Using Monitoring and Evaluation Functions

- Using Sample Networks

## Structure of the Application and its Documentation

For the maintenance and execution of the object data, the classic character-based (CUI) maintenance screens are used in an Entire Operations (NOP) mainframe and UNIX environment. In a Windows environment, the Entire Operations GUI Client (OGC) is used, which provides a tree view and dialogs. All existing records (definitions) for an object type (owner, job network, job, etc.) are clearly arranged and readily accessible. They can be invoked and used by means of line commands (CUI) or context menu commands (GUI).

The order in which the objects are arranged in the application essentially corresponds to the workflows. These are mapped accordingly in the structure of this user manual and within the individual object-specific chapters. Each chapter describes the functions that can be performed on an object type and explains the input and output fields available.

Objects whose maintenance requires the rights of an administrator are described in the Administration document. You can display the associated data also as a general user, for example to view the settings in your user profile and the authorizations granted to you for a particular activity in the various functional domains of the system, or to view the definitions of system-wide resources that can be referenced in a job. If you need to change any of these details, please contact your system administrator.

## Required Knowledge

The following basic knowledge is required:

- Knowledge of the operating systems used

- Knowledge of the job control language (JCL) used

- Knowledge of the Natural programming language

## Authorization

Access to the business functionality and the definitions created can be granted in mutiple places within the application:

1. In your user profile, see User Definition and Profile Settings in the Systemverwaltung documentation.

2. In the Owner Maintenance function.

3. In the definition of a job network, see Granting Definition: Authorizing Other Users or Owners to Access a Network.

## Overview of Objects in Entire Operations

The following graphic provides an overview of objects you can maintain in Entire Objects in order to set up a job network:

Note
Click on a symbol in the diagram above for more information on the respective object.

For an overview of how these objects interrelate, see Entire Operations Object Relationship in the Concepts and Facilities documentation.

## Overview of the Object-specific Maintenance Functions in Entire Operations

The Entire Operations application is structured in such a way that all important object-specific maintenance functions are accessible as quickly and logically as possible. The order of the objects in the main menu and in the maintenance screens of the application essentially corresponds to the workflows. This is reflected in the structure of this user manual and within the individual chapters. There, the functions available for an object are first presented in an overview, and then their use and all inputs and outputs are described in detail.

#### Primary Maintenance and Control Functions for Job Network and Job Definitions

- Owner Maintenance

- Network Maintenance

- Job Maintenance

- Active Job Network and Active Job Maintenance

#### Maintenance Functions for Global Object Definitions

- Schedules

- Calendars

- Mailboxes

- Symbol Tables and Symbols

#### Monitoring and Evaluation Functions

- Log Information /Activity Monitoring

- Reports

- Cross-References

#### Interface Programming

- API Routines

- User Exits

## Three Steps to an Executable Job Network

The creation of a job network is essentially done in three main steps. These steps are always required to define an executable job network. The resulting definitions are stored in the master database.

- Step 1: Determine owner
  The central object of the Entire Operations application is the owner and the user(s) associated with it. See also Owner Maintenance.

  The name of the owner at logon is displayed in the Owner field of the Entire Operations Main Menu (e.g. `EXAMPLE`). This is the default owner name that is used when a new job network is created. You can choose a different owner as described in Listing Owners.

  If the required owner is not available in the selection list, refer to Adding and Removing User/Owner Links and Owners and/or contact your system administrator.

- Step 2: Define job network

  Choose the Network and Job Maintenance option on the Main Menu screen.

  Choose PF2 (Add) on the Network Maintenance screen. A Network Addition window opens.

  Proceed as described in Adding a Network Definition

  After you have filled in all the mandatory fields, you can already save the new network definition.

  You can open the record again at any time to display or modify the existing data or enter data, e.g. to define different runtimes. You can use subfunction screens with additional fields for special purposes.

  Close the function to return to the Network Maintenance screen.

  You also have other options for maintaining a record in the master database. These are listed in the overview of the Network Maintenance chapter under Job Network Maintenance and Maintenance Functions for Job Network Definitions.

- Step 3: Create job definition(s)
  In the previously created job network, you can now define a job.

  On the Network Maintenance screen, type `L` in the line command field of the network for which you wish to add a job and press ENTER. A Job Maintenance screen appears.

  Choose PF2 (Add). A Job Definition (Master) window opens.

  Proceed as described in Adding a Job Definition

  After you have filled in all mandatory fields, you can use the subfunctions there with additional fields to enter further details. Press PF5 to save the job definition, and subsequently PF3 to close the Job Definition (Master) window, or press PF2 to stay in this window and define the next job definition for this network.

  When you save the job definition(s), the Job Maintenance screen is displayed.

  You also have other options for maintaining a record in the master database. These are listed in the overview of the Job Maintenance chapter.

## Using Control and Monitoring Functions for Job Networks

A job network is activated either automatically by the Entire Operations monitor according to the defined schedule data, or by a user on demand.

After you have properly defined a job network, you can activate it, i.e., submit it for immediate or scheduled execution. The following control functions, among others, are available to you for this purpose:

- Activating a Job Network Manually

- Deactivating Active Runs for a Network

- Displaying Next Network Starts - Single Network

- Displaying Next Network Starts - System-Wide

- Checking for a Loop in a Job Network

- Displaying the Network Execution History

## Performing ad hoc Actions on Active Jobs in the Active Database

Even after a job network has been activated, you can still change specifications in an active job network or an active job (in the active database) without changing the original network or job definition in the master database.

- Maintening Active Job Networks and Active Jobs (active jobs, active conditions, active JCL)

## Creating Ancillary Objects for a Job Network or Job

You can define globally defined ancillary objects in Entire Operations at any time and reference them in the job network and/or job definitions.

- Defining schedules that can be referenced in the definitions of multiple job networks

- Defining calendars that can be used as a basis of time tables for jobs and job networks

- Using mailboxes to send network-related messages and requests to users or groups of users

- Defining symbol tables and symbols

- Using functions for symbol replacement

- Using resource maintenance functions

- Maintaining mailbox definitions

## Using Monitoring and Evaluation Functions

You can use the following monitoring and evaluation functions:

- Displaying Logged Information or Monitoring Entire Operations Activities

- Viewing Job/Network Accounting Information to obtain information on the start and end times, elapsed time and CPU time for previous runs of a job

- Generating Reports to generate reports that help overview your network environment to define objects, monitor the system and plan workloads

- Using Cross-Reference Functions to cross-check the use of individual Entire Operations objects and produce a report from the data found

## Using Sample Networks

You may ask your system administrator to load the sample networks supplied for self training. You can modify a copy to gain initial experience in using the job network maintenance features of Entire Operations.

### On this page

- Using the Entire Operations Business Functionality
- Structure of the Application and its Documentation
- Required Knowledge
- Authorization
- Overview of Objects in Entire Operations
- Overview of the Object-specific Maintenance Functions in Entire Operations
- Three Steps to an Executable Job Network
- Using Control and Monitoring Functions for Job Networks
- Performing ad hoc Actions on Active Jobs in the Active Database
- Creating Ancillary Objects for a Job Network or Job
- Using Monitoring and Evaluation Functions
- Using Sample Networks