Maintaining Job Network Versions

#### Search Results

Search

# Maintaining Job Network Versions

This section describes how to maintain and use different versions of job network.

This document covers the following topics:

- Versioning of Job Networks

- Using Network Versions for Activations

- Handling Network Version Usage Definitions

## Versioning of Job Networks

This section describes the rules and guidelines for maintaining network versions.

- Version Names

- Reserved Version Names for Networks

- Version Names Exit

- Creating Network Versions by Copying Networks

- Copying Jobs

- Deleting Network Versions

- Deleting Network Versions or Single Jobs via API

### Version Names

The following applies when creating version names:

- The name can contain up to 10 alphanumeric characters and uppercase or lowercase letters.

- Space characters and the following special characters are not allowed:

  ?<>*‚()_

- To avoid problems when porting an Entire Operations environment to another platform, do not use special characters and umlauts.

- Do not use a reserved version name (see the relevant section).

### Reserved Version Names for Networks

> blank value; in selections and in the log also: `(unnamed)`

>   Is used for an unnamed version.

>   This is the only network version that exists after migration from an earlier Entire Operations version that does not support network versioning.

>   In parameter listings (e.g., for reporting) you can use also a hyphen (`-`).

> `(current)`

>   Will be replaced by the version that is set in the activated time schedule.

>   `(current)` can be used in version references.

### Version Names Exit

With the usage of a global version name exit you can force a user-specific version name syntax. For detailed information, see Global Exit for Version Names in the Administration documentation.

### Creating Network Versions by Copying Networks

You can copy network definitions to add a new version for an existing network.

See also Copying Job Network Definitions.

### Copying Jobs

Jobs in any version can be copied out of the originating network master.

### Deleting Network Versions

You delete a network version by using the network delete function as described in Deleting a Job Network

The following applies when deleting a network version:

- You must be authorized to delete the network.

- You cannot delete a version that is defined and used in a current network activation schedule (see also Handling Network Version Usage Definitions). A version defined in an outdated schedule can be deleted.

### Deleting Network Versions or Single Jobs via API

By using the API `NOPUAC5N` (Function `D`, Run Number `-1`) you can delete single network versions and jobs.

## Using Network Versions for Activations

This section covers the following topics:

- Evaluation of Network Versions for Scheduled Activations

- Manual Activation

- Activation of a Subnetwork

- Activation as End-of-Job Action

- Activation via API

- Versions without Schedule Activation

- Daily History of Network Activations

- Reporting

- Import/Export

- Exit Functionality (Network)

- Maximum Number of Versions per Network

### Evaluation of Network Versions for Scheduled Activations

The following applies:

- If only one version exists in a network, then this version will be activated. A schedule definition will be ignored.

- If multiple versions exist in a network, then it will be checked if a version has a current activated time schedule. If this is so, then this version will be activated.

- If usage intervals are defined for a network version, but the activation date is not in this interval, then the network will not be activated although scheduled. Corresponding protocol log entries and messages will be sent.

### Manual Activation

If you choose a manual activation, then any network version can be selected. If defined, the standard version for schedule activation will be offered to you first.

### Activation of a Subnetwork

In the subnetwork definition, you can define any version or the reserved `(current)` name.

### Activation as End-of-Job Action

For the network or job activation as End-of-Job action you can define any version or the reserved `(current)` name.

### Activation via API

For the network or job activation via API `NOPUAC5N` you can define any version or the reserved `(current)` name in the field `NETWORK-VERSION`.

Note that the API may issue version-related return codes.

### Versions without Schedule Activation

In Entire Operations you can save multiple versions of job networks. Versions that are not, or are no more in the usage interval of schedule activation will not be activated automatically.

### Daily History of Network Activations

The history of the network activations contains the network version for every run.

### Reporting

Network versions will be considered.

### Import/Export

Network versions will be considered.

### Exit Functionality (Network)

Entire Operations provides user exits and APIs that perform network activation functions and support network versioning, for example, the API `NOPUAC5N`.

### Maximum Number of Versions per Network

The maximum number of network versions can be limited system wide as described in Default Setting (3) in the Administration documentation.

## Handling Network Version Usage Definitions

You can to view and define the maintenance of date ranges, in which network versions are to be used for scheduled activations.

### Viewing the Network Version Usage List

To list network version usage definitions

- On the Network Maintenance screen, type `U` in the line command input field next to the required network, and press `ENTER`.

  A Network Version Usage for scheduled Activations screen like the example below appears:

      17.12.13                ***** Entire Operations *****                17:22:07
                        Network Version Usage for scheduled Activations
       Owner SN         Network A-1
       ------------------------------------------------------------------------------
       Cmd from      to        Version     Description
           --------  --------  *---------
        _  >>>>>>>>  16.12.13  v004
        _  17.12.13  20.12.13  v20131217
        _  21.12.13  31.12.13  V00002
        _  01.01.14  >>>>>>>>  V00003

       ******************************* Bottom of Data *******************************
       D Delete  M Modify
      Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
            Help  Add   End                     Up    Down        Left  Right

  The screen lists date ranges in which network versions are to be used for scheduled activations.

  The columns and line commands available on the screen are explained in the following table:

  Column/Field | Description
  --- | ---
  Cmd | Line command input field. Possible values:
  `D` | Delete the version definition.
  `M` | Modify version definition.
  from | `>>>>>>>>` denotes that no start time is defined for activating version usage. If not start date is defined, the current day is assumed by default.
  to | `>>>>>>>>` denotes that no end date is defined for deactivating version usage. Version usage is unlimited.
  Version | Version name of the network.
  Description | Description of the version usage.

### Adding or Modifying a Network Version Usage Definition

To add a network version usage definition

1. On the Network Version Usage for scheduled Activations screen, choose PF2 (Add) if you want to add a new version usage definition.

   Or:
   On the Network Version Usage for scheduled Activations screen, type `M` in the line command input field next to the definition you want to change, and press ENTER.

   A screen like the example below appears:

        18-02-08                ***** Entire Operations *****                17:18:42
                       Network Version Usage for scheduled Activations
        Owner SAGTEST    Network SAGNET
        ------------------------------------------------------------------------------

        Network Version ==> SAGNET-V3_

        is to be used for scheduled activations

                   from ==> 01-01-18     (empty: unlimited)
                     to ==> ________     (empty: unlimited)

        Version Usage Description
        Test version for network___________________________________________

       Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
             Help        End         Save

2. Add or change the definition as required. The fields contained on the screen are explained in the following table.

   Note
   The date ranges must not overlap.

   Field | Description
   --- | ---
   Network Version | Valid version defined for the network. You can enter an asterisk (`*`) to open a window and select a version from a list.
   from | Start date of a default usage period of a network version. Empty: no start date defined. The current day is assumed by default.
   to | End date of a default usage period of a network version. Empty: no end date defined (infinite time).
   Version Usage Description | Short description of the version usage

### On this page

- Versioning of Job Networks
- Using Network Versions for Activations
- Handling Network Version Usage Definitions