Completing the Installation

#### Search Results

Search

# Completing the Installation

This section covers the following topics:

- Adapting to an Existing Environment

- Natural Profile Parameters

- Natural Security Definitions

- Entire Output Management in a Non-Security Environment

- Define Environment for Entire Output Management Server

- Migrating from Previous Versions

- Starting Entire Output Management for the First Time

- Installation Verification

## Adapting to an Existing Environment

- Step 1: Create a User Library

- Step 2: Modify the Job Skeletons

- Step 3: VTAM Definitions

- Step 4: Entire System Server Parameters

### Step 1: Create a User Library

The library `SYSNOMS` contains standard separator pages for reports and bundles, as well as job skeletons which have to be modified to suit your requirements. As the contents of `SYSNOMS` are overwritten by every new product release, copy the job skeletons you wish to modify from `SYSNOMS` to the library `SYSNOMU`, and modify them there.

If you want to use the Entire Output Management standard separation exits for reports and bundles, copy the current versions of the members `RS*` and `BS*` (with `REPLACE` option) to the library `SYSNOMU`.

Always copy the current versions of the following data areas (with the `REPLACE` option) to the library `SYSNOMU`:

- `P-UEXIT` and `P-UEXITE` (for separation exits),

- `P-PEXIT` (for printing exits),

- `NOMEXP*` and `NOMEX08E` (for user exits).

Then recatalog your user exits which use these parameter data areas.

The sample exits `UEX*` in the library `SYSNOMS` also use these parameter data areas. For further information on user exits, see the source of subprogram `UEXFRAME` in the library SYSNOMS.

### Step 2: Modify the Job Skeletons

The following tasks require job skeletons which have to be adapted to your requirements. Adapt the sources in the library `SYSNOMU` which are specified in the Source column and make them available under the Target name as shown below:

Task | Environment | Source | Target
--- | --- | --- | ---
ARCHIVE | z/OS Tape | JARCMTAP | JARCSKEL
z/OS GDG or predefined Disk VOLSERs | JARCMDSK
z/OS, SMS | JARCMSMS
REVIVE | z/OS Tape | JREVMTAP | JREVSKEL
z/OS GDG or predefined Disk VOLSERs or SMS | JREVMDSK
CONDENSE | z/OS Tape | JCDNMTAP | JCDNSKEL
z/OS GDG or predefined Disk VOLSERs | JCDNMDSK
z/OS, SMS | JCDNMSMS
PRINT | JES | SYSPRJES | SYSPRJES or user-defined
z/OS Disk | DISKMVS | DISKMVS or user-defined
z/OS Tape | TAPEMVS | TAPEMVS or user-defined

### Step 3: VTAM Definitions

To enable Entire Output Management to print to VTAM printers, add the definition from the member `NOMVTAM` in the Entire Output Management source library to your `SYS1.VTAMLST` library and activate it. If your `SYS1.VTAMLST` already contains a definition for Entire System Server, include only the definition for Entire Output Management in it.

In the Entire System Server parameters, assign the value for `SPOOLACB` as defined in your `SYS1.VTAMLST`.

### Step 4: Entire System Server Parameters

To activate the common data pool, assign a value of at least "1" to the `CDATALEN` parameter.

To run Natural subtasks, assign a value of at least "80" to the `NABS` parameter.

## Natural Profile Parameters

For all online and batch tasks which execute Entire Output Management, the following Natural profile parameters have to be set:

Parameter | Description
--- | ---
`CVMIN=ON` | Control variable modified at input.
`ID=' '` | Set input delimiter to blank.
`WH=ON` | Wait for locked Adabas records.

If UNIX or Windows platforms are to be used as external spooling system source, the following Natural profile parameters have to be set:

Parameter | Description
--- | ---
`CFICU=ON` | Unicode and code page support.
`CP=ON` | Default code page.
`XML=(ON,RDOC=ON,PARSE=ON)` | XML support.

## Natural Security Definitions

If Natural Security is installed at your site, you have to create security profiles for the following libraries and users.

### Libraries

Library | Description | with Steplibs
--- | --- | ---
`SYSNOM` | Entire Output Management online application. | `SYSSAT` `SYSNOMU` `SYSSEC` (optional) any other library containing user routines (optional) (see also note below)
`SYSNOMH1` | Entire Output Management help system (English). | -
`SYSNOMH2` | Entire Output Management help system (German). | -
`SYSNOMU` | User copy of `SYSNOMS` library. | -

Note
When a user routine is requested, the steplibs are searched sequentially in the order in which they are specified in the security profile of `SYSNOM`, and the user-routine member from the first steplib in which it is found will be used. If a user-routine member and library are specified in a report definition and this library is not specified as steplib in the `SYSNOM` security profile, it will be temporarily appended to the list of steplibs being searched. For the user-routine member from that library to be used, a member of the same name must therefore not be contained in any of the other steplibs listed before in the library profile.

### Users

Create a Natural Security user profile of user type "Person" for the user representing the Entire Output Management server, with the user ID and password identical to the `NSCUSER` and `NSCPSWD` parameters taken from the main member `SATPnnn` or `SPnnnnn`.

You can use one user ID for all or different user IDs for each server type. See also the example under Define Environment for Entire Output Management Server below.

## Entire Output Management in a Non-Security Environment

Entire Output Management's start program `MENU` is executed from `SYSSAT`. In a non-security environment, this means that `MENU` will not be found as start program. Therefore you have to rename the program `MENUNOM` in the library `SYSNOM` to `MENU`. As an alternative, you can copy the program `MENU` of the library `SYSSAT` into the library `SYSTEM`. This, however, may have the disadvantage of causing other applications to erroneously find the program `MENU` in the library `SYSTEM`, thus producing undesired results.

If Natural Security is not installed at your site, the following steplibs are automatically assigned to the library `SYSNOM`:

- `SYSSAT`

- `SYSNOMU`

## Define Environment for Entire Output Management Server

- General Layout of a Parameter Block

- Parameter Blocks and Parameters for Entire Output Management

See also the section Defining SAT, Natural and Product Parameters in the System Automation Tools Installation documentation.

For each Entire Output Management Server you must define the run-time environment in one or more Natural members in the System Automation Tools user library `SYSSATU.`

If you want to run various Entire Output Management Servers under different Entire System Server nodes nnn, you must provide startup parameters at least in the related "main" members. These must conform to the following naming convention: `SATPnnn or SPnnnnn`. In addition, you can provide further Entire Output Management-specific parameters in a second member, whose name must not match the naming convention for the main members.

### General Layout of a Parameter Block

    <Prefix> <block-identifier>[<keyword>=<value>,...]

where:

Parameter | Description
--- | ---
`<Prefix>` | `SAT` or compressed product code + prefix as specified in the `SATSTART` instruction.
`<block-identifier>` | `SATENV/NATENV/SATSTART` or product block identifier.
`[<keyword>=<value>,...]` | Block-specific parameter.

### Parameter Blocks and Parameters for Entire Output Management

#### Mandatory Parameters

Parameter Block | Parameter | Description
--- | --- | ---
`SATENV` | `NSC=YES/NO` | Indicates whether Natural Security is installed or not.
`NSCUSER=` | If Natural Security is installed, this is the user ID for logging on to it.
`NSCPSWD=` | Password for logging on to Natural Security.
`ESYUSER=` | User ID for logging on to Entire System Server, if it is installed and an interface to an external security system is activated.
`NATTASK=` | Name of the Natural subtask module for starting a server as a subtask.
`SATSTART` | `PRODUCT=NOM` | 3-byte product code.
`PREFIX=` | `PRODUCT` and `PREFIX` are compressed into a prefix which identifies the Server-specific parameters. Usually the version `vrs` is specified as `PREFIX`. However, if you run more than one Entire Output Management Monitor on the same node, you have to specify `SATSTART` blocks with different `PREFIX`es for them.
`TYPE=SUBTASK/BATCH` | Entire Output Management Servers are always started as subtasks.
`APPLIB=SYSNOM` | Name of the Natural library where Entire Output Management Server is installed.
`SERVSYSF=` | Pointer to the Entire Output Management data file (must be unique within all `SATSTART` instructions of this node).
`NOMENV` | `ETID=*` | Generate unique ETIDs for tasks.
`ETIDPREF=` | 6-byte prefix for ETIDs.
`NATENV` | `LFILE=(206,NOMSYSF-DBID,NOMSYSF-FNR)` or `LFILE=(131,SATSYSF-DBID,SATSYSF-FNR)` or `LFILE=(91,NOMACTDATA-DBID,NOMACTDATA-FNR)` | These pointers can be set either in the common Natural parameter module created for the System Automation Tools products or in a Natural parameter profile indicated by the Natural parameter `PROFILE`. Make sure that the system-file pointer coincides with the pointer to the Entire Output Management system file 1 provided with the `SERVSYSF` parameter in the `SATSTART` block.
`WH=ON` | The user is placed in "wait" status until either the requested record becomes available, or an error message is issued due to Adabas exceeding a time limit or other limit while attempting to place the record in "hold" status.

#### Optional Parameters

You can overwrite the `SATENV` and `NATENV` parameters with Entire Output Management-specific or even Entire Output Management-subtask-specific assignments. The naming convention for the prefix which identifies the parameter block is:

                                (PRT for Print Task)
    <Prefix> = NOM + <PREFIX> + (ARC for Archive Task)
                                (REV for Revive Task)

Parameter Block | Parameter
--- | ---
`SATSTART` | `MEMBER=name` | You can specify a member in which Entire Output Management-specific parameters are located.

##### Example - Contents of "Main" Member for Node 148 - SATP148 or SP00148 in SYSSATU

The member SATP148 in SYSSAT provides an example of a "main" member. You can take this as the basis for your own member: Copy it to SYSSATU and adapt it.

`SAT` | `SATENV` |
    NATTASK=SAT3ST,
    NSC=YES,
    NSCUSER=SATMON,
    NSCPSWD=SATMON
| Sets the SAT defaults for all System Automation Tools products.
`NOMvrsPRT` | `SATENV` |
    NSCUSER=NOMPRT
    NSCPSWD=NOMPRT
| Indicates that a separate user ID/password can be used for Entire Output Management's Print task.
`NOMvrsARC` | `SATENV` |
    NSCUSER=NOMARC
    NSCPSWD=NOMARC
| Indicates that a separate user ID/password can be used for Entire Output Management's Archive task.
`NOMvrsREV` | `SATENV` |
    NSCUSER=NOMREV
    NSCPSWD=NOMREV
| Indicates that a separate user ID/password can be used for Entire Output Management's Revive task.
`SAT` | `NATENV` |
    DU=OFF,
    PROFILE=SATMON
| Sets the Natural defaults for all System Automation Tools products: the Natural profile parameters are provided in the profile `SATMON`.
`SAT` | `SATSTART` |
    PRODUCT=NOM,
    PREFIX=vrs,
    TYPE=SUBTASK,
    APPLIB=SYSNOM,
    SERVSYSF=(88,51)
| Specifies that the server for Entire Output Management is to be started as a subtask.

## Migrating from Previous Versions

- Migration from Version 3.5.1 or 3.5.2 to Version 3.5.3 on Mainframes

- Migration from Version 3.4.3 to Version 3.5.3 on Mainframes

- Migration on UNIX Systems

Migrations from earlier versions are not supported.

### Migration from Version 3.5.1 or 3.5.2 to Version 3.5.3 on Mainframes

#### Migration Procedure

Execute the following jobs:

Job | Step(s) | Action
--- | --- | ---
I200 | 2811 | Start of current system-file version (MIGSTART).
2812 | Migration of printers (MIGPRT).
2814 | Migration of the Monitor (MIGMON).
2819 | Setting of current system file version (MIGEND).

#### Important:

In addition to the above migration procedure, you have to perform with Version 3.5.3 the following two recatalog steps:

- Recatalog all your user exits and all programs which use Entire Output Management application programming interfaces.

- If you use the program `NOMTP` in the library `SYSNOMS`, recatalog it (because the parameter data area `NOMTP--P` used by it has been modified).

### Migration from Version 3.4.3 to Version 3.5.3 on Mainframes

#### Important:

- Before you start the migration, make sure that:

  - the Entire System Server node on which the Entire Output Management Monitor runs is active,

  - the Entire Output Management Monitor itself is inactive.

- In addition to the migration procedure described below, you have to perform with Version 3.5.3 the following two recatalog steps:

  - Recatalog all your user exits and all programs which use Entire Output Management application programming interfaces.

  - If you use the program `NOMTP` in the library `SYSNOMS`, recatalog it (because the parameter data area `NOMTP--P` used by it has been modified).

- As of Entire Output Management Monitor Version 3.4.1 on mainframes, record spanning is required to keep long buffers in Adabas. If the Adabas parameter `MIXDSDEV` is used in the ADALOD utility, record spanning is not available. Therefore the `MIXDSDEV` parameter must be omitted.

#### Migration Procedure

Execute the following jobs:

Job | Step(s) | Action
--- | --- | ---
I082 | 2850, 2852, 2853, 2855 | Migration of system-file structure.
2851, 2854 (*) | Migration of system-file structure.
I200 | 2811 | Start of current system-file version (MIGSTART).
2812 | Migration of printers (MIGPRT).
2813 (**) | Migration of user exits (MIGUEX).
2814 | Migration of the Monitor (MIGMON).
2815 | Check of report identifications (CHCKIDNT).
2816 | Migration of the SAT logs of NOM (MIGSAT).
2819 | Setting of current system file version (MIGEND).

(*) These steps are only required if you use two Entire Output Management data files, one containing definition data and one containing active data.

(**) MIGUEX always ends with condition code 0 in order to continue the migration process. Check the output of MIGUEX for indications of missing or outdated modules.

### Migration on UNIX Systems

See Migration in the Installation and Customization on UNIX documentation.

## Starting Entire Output Management for the First Time

To start Entire Output Management for the first time:

1. Make sure that the Entire System Server node under which the Entire Output Management Monitor runs is active.

2. Log on to the library `SYSNOM`.

3. Execute the program `INSTALL`.

   This program adds the first user ID, modifies some example definitions, and asks you to specify various Entire Output Management parameters.

   Make the necessary specifications, and leave each screen with PF3

   When you have completed this step, the Entire Output Management Main Menu is displayed.

4. Enter the command `START MONITOR` in the command line to start the Entire Output Management Monitor online.

For information on how to automatically start the Entire Output Management Monitor when starting Entire System Server, see the section AUTO-START in the System Automation Tools Installation documentation.

## Installation Verification

To verify that Entire Output Management has been installed correctly, perform the following steps.

### Step 1: Verify the Startup Parameters Defined in Library SYSSATU

To do so:

1. Log on to the library `SYSSATU` where you keep your master definitions for all servers of the System Automation Tools family.

2. Check that the `SATnnnnn` entry in the member `SATDIR` points to the correct FNAT for the application `SYSSAT`.

3. Check member `SATPnnn` or `SPnnnnn` for the `SATSTART` entry with `PRODUCT=NOM`. The `TYPE` parameter should have the value `SUBTASK`; the `APPLLIB` parameter must have the value `SYSNOM`, and the `SERVSYSF` parameter must point to the correct Entire Output Management system file where the object definitions are kept.

4. Check member `SATPnnn` or `SPnnnnn` for the `SATENV` parameter `NATTASK`. The value in effect for Entire Output Management must indicate the correct Natural subtask module. This Natural module must be correctly linked and accessible in the run-time environment of the Entire System Server node nnn.

5. Check the member `SATPnnn` or `SPnnnnn` for the `SATENV` parameters `NSCUSER`, `NSCPSWD` and `ESYUSER`. If you use Natural Security, <NSCUSER> must be defined as user and must have access to the libraries SYSNOM and SYSNOMU.

   If Entire System Server is running with security (i.e.: `SECURITY<>NONE`), the user ID indicated by `<ESYUSER>` must be defined in the external security system and have sufficient authorization.

### Step 2: Verify the Monitor Defaults

To do so:

1. Log on to the library `SYSNOM` and invoke the program `MENU`.

2. Enter the direct command `8.1`. On the Default Definition Menu, select Option 1 to verify that the System Default parameters DBID and FNR parameters point to the correct Entire Output Management system file.

3. Return to the menu by pressing PF3, and then select Option 2 to verify the Monitor Defaults:

   - node, batch module and system server jobname should be correct;

   - at least one printer task should be specified;

   - at least one output class reserved for Entire Output Management is specified (z/OS);

     Note
     For JES3, these classes must be defined as `HOLD=EXTWTR`

   - temporary class is specified.

### Step 3: Start the Entire Output Management Server Automatically with Entire System Server

If the Entire System Server is active, proceed with Step 4 below, to start the Entire Output Management Server online.

If the `SATSTART` block for the Entire Output Management Server in the `SYSSATU` member `SATPnnn` or `SPnnnnn` is provided correctly, the Server is started automatically with the Entire System Server node nnn.

To do so:

1. Start the Entire System Server node nnn.

   The successful start of the Entire System Server is indicated by the console message:

   `Entire System Server IS READY - X-COM NODE nnn IS INITIALIZED`

   The successful start of the Entire Output Management Server is indicated in the Entire Output Management log (direct command `DLOG MON`):

       NOM1522 Monitor logged on to NPR UserId = NOMMON.
       NOM1510 Monitor initialization completed successfully.
       NOM1524 Number of Printer Tasks 2.
       NOM1525 Printer task Type ..... SUBTASK.
       NOM1503 Monitor minimum wait .. 30.
       NOM1504 Monitor maximum wait .. 30 .
       NOM1505 Monitor increment ..... 5.
       NOM1506 Monitor node .......... 148.
       NOM1507 Monitor DBID .......... 1.
       NOM1508 Monitor FNR ........... 37.
       NOM1527 Operating System Type . MVS/ESA.
       NOM1528 Spool Type ............ JES2.
       NOM1509 Start monitor initialization.
       NOM1511 Monitor startup.

   The corresponding console messages will be displayed:

       NOM1510 Monitor initialization completed successfully.
       NOM1603 Monitor NOMXTS dbid fnr on node node started.

2. If this sequence does not appear after a while, check the following:

   - If the Entire System Server node is running under z/OS, check the `SYSOUT` files of the node.

3. Proceed with Step 5 below.

### Step 4: Start the Entire Output Management Server Online

To do so:

- In the Entire Output Management online system, enter the direct command `START MON`.

### Step 5: Produce Sample Output in one of Entire Output Management's Reserved Classes

To do so:

1. Run any job which produces output in one of the classes defined as reserved for Entire Output Management.

2. When the job has finished, invoke the Monitor Management screen, and wake up the Monitor by pressing PF10.

   The Monitor should now start creating reports derived from the report definition `UEX-DEFAULT`.

3. Enter the direct command `LIST AREP`, and then the line command `LI` for the folder `#Inbasket` to list the active reports contained in it.

   Then enter the line command `BR` to browse the arrived reports.

### On this page

- Adapting to an Existing Environment
- Natural Profile Parameters
- Natural Security Definitions
- Entire Output Management in a Non-Security Environment
- Define Environment for Entire Output Management Server
- Migrating from Previous Versions
- Starting Entire Output Management for the First Time
- Installation Verification