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:

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:

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

Natural Security Definitions

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

Libraries

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 Blocks and Parameters for Entire Output Management

Mandatory Parameters

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)

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.

NATTASK=SAT3ST,
NSC=YES,
NSCUSER=SATMON,
NSCPSWD=SATMON

NSCUSER=NOMPRT
NSCPSWD=NOMPRT 

NSCUSER=NOMARC
NSCPSWD=NOMARC

NSCUSER=NOMREV
NSCPSWD=NOMREV

DU=OFF,
PROFILE=SATMON

PRODUCT=NOM,
PREFIX=vrs,
TYPE=SUBTASK,
APPLIB=SYSNOM,
SERVSYSF=(88,51)

Migrating from Previous Versions

• Migration from Version 3.5.1 to Version 3.5.2 on Mainframes

• Migration from Version 3.4.3 to Version 3.5.2 on Mainframes

• Migration on UNIX Systems

Migrations from earlier versions are not supported.

Migration from Version 3.5.1 to Version 3.5.2 on Mainframes

Important:

In addition to the migration procedure described below, you have to perform with Version 3.5.2 the two recatalog steps listed under Migrating from Previous Versions in the Version 3.5.2. Release Notes.

Migration Procedure

Execute the following jobs:

Migration from Version 3.4.3 to Version 3.5.2 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.2 the two recatalog steps listed under Migrating from Previous Versions in the Version 3.5.2. Release Notes.

• 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:

(*) 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, z/VSE);

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

   • temporary class is specified;

   • a reserved virtual printer must be specified (BS2000).

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.

   • If the Entire System Server node is running under z/VSE, check the LST data set of the node.

   • If the Entire Output Management Server is running under BS2000, check the SYSLST protocol files matching the following naming convention: The file name must contain the substring: L.NOMxxnnn

     where xx stands for the Entire Output Management subtask and nnn for the server number. xx = XT for the main task and 02 to 05 for subtasks.

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.