This section covers the following topics:
After you have installed Entire Output Management for the first time and if Natural Security is active, you have to create security profiles in Natural Security for the Entire Output Management libraries and users, as described under Natural Security Definitions in the section Installing and Customizing Entire Output Management on Mainframes.
Important:
You have to do this before invoking the SYSPCI utility for
Entire Output Management. Otherwise, the initialization with the SYSPCI utility
will fail.
On UNIX systems, a migration to Version 3.5.2 is possible from Versions 3.5.1 and 3.4.3, but not from earlier versions.
It is sufficient 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. No further migration procedure is necessary.
On UNIX systems, a data migration of all data of the system files is required.
UNIX requires a migration of the whole Entire Output Management system file. It has to be unloaded, decompressed, recompressed, and reloaded. This is done by the installation utility with update installation. Make sure that there is enough free disk space to hold the complete Entire Output Management system file.
You have to perform the following steps for:
the system file (NOM-SYSF1_MASTER);
the active-data file (NOM-ACTIVE_DATA), if
used;
the container file (NOM-CONTAINER).
To migrate each Entire Output Management file manually:
Create a directory as a work directory and copy
$NOM_HOME/INSTALL/mig.bsh and the fdu definition file
into it, e.g. nomsysf1.fdu.
Enter an unused file number for a new Entire Output Management
system file in nomsysf1.fdu.
Make sure you have sufficient space to keep the unloaded and uncompressed system file in that directory.
Backup your database and use it exclusively.
Supposing you are using database 100 and the current system file number is 5, select a free file number (e.g. 15) and change to the created directory.
Invoke the script as follows: ./mig.bsh 100 5 nomsysf1
15
mig.bsh will renumber file 5 to 15, call several
Adabas utilities which will change and add fields to the current system file,
unload and decompress it, and change FDT options.
Then the file will be recompressed and loaded as file 5. The old file will be left in the system as file 15.
You need not specify a temporary file. If you want to replace the system file in place, invoke the utility as follows:
./mig.bsh 100 5 nomsysfl 5.
mig.bsh will write a log file
mig.bsh.log into the install directory which contains the complete
output of all Adabas utilities.
After you have performed the above steps for each file, execute the following script:
$NOM_HOME/INSTALL/migd.bsh
After you have installed your product, you need to set up a number of files, parameters and individual settings depending on your environment. These are described below. To set them up, you use the SYSPCI utility. For detailed information on this utility, see SYSPCI Utility - Product Configuration and Initialization in Natural's Tools and Utilities documentation.
Before you can define Entire Output Management system files, the
System Automation Tools system file (LFILE 131) has to be defined.
Entire Output Management requires the following Adabas system files:
NOM-SYSF1_MASTER, where the logical file number
(LFILE) is 206.
NOM-ACTIVE_DATA, where the logical file number
(LFILE) is 91.
This is optional; if NOM-ACTIVE_DATA is not
specified, NOM-SYSF1_MASTER will also be used for the active
data.
NOM-CONTAINER without a logical file number.
The database IDs and file numbers of the new/existing files
NOM-SYSF1_MASTER and NOM-ACTIVE_DATA which you
specify with the SYSPCI utility will be entered into the default parameter
files of Entire Output Management (NOMPARM) and Entire Operations
(NOPPARM, if available).
The required Adabas files can either be local or remote.
Remote Access
If the file is located in a remote database, Entire Net-Work must
be active and the database must be accessible.
Existing Local File
Before you start the SYSPCI utility, make sure that the Adabas
database containing the required files is active. With this version, you can
continue to use your existing files.
New File
Before you start the SYSPCI utility, make sure that the Adabas
database which will contain the required files is active. The SYSPCI utility
will load and initialize these files. This should be also done if another file
is required for your product.
Before you create new files with the SYSPCI utility, make sure that the ASSO and DATA sizes of your Adabas database are appropriate for these files. It is therefore recommended that you check the Adabas .fdu files in the <install-dir>/<product>/INSTALL/<product-code> directory for the used sizes. If required, change your database setup so that the files can be created.
For Entire Output Management, the SYSPCI utility offers the following optional function:
| Option | Description |
|---|---|
| Load NOM data | If marked, the Entire Output Management
data will be loaded into the Entire Output Management system file
NOM-SYSF1_MASTER.
|
In order to invoke the SYSPCI utility, you must first invoke Natural. You can then invoke the SYSPCI utility using the Direct Command window.
To invoke the SYSPCI utility
Enter the following command at the UNIX system prompt to invoke Natural:
natural
Select the menu and press ENTER to invoke the Direct Command window.
Enter the following command in the Direct Command window:
SYSPCI
For more information, see SYSPCI Utility - Product Configuration and Initialization in Natural's Tools and Utilities documentation.
It is possible to execute certain functions of the SYSPCI utility with a UNIX shell script. Two shell scripts are available in <install-dir>/Natural/INSTALL directory. They are called syspci_reuse.sh and syspci_create.sh. These scripts can be used to automatically call SYSPCI for each installed product to intialize the product.
The scripts can be used for the following tasks:
syspci_reuse.sh
This script executes the SYSPCI utility to initialize installed Natural
products with already existing Adabas files.
Note:
The necessary conversion of Adabas files to the new version has to be
done before starting this script.
syspci_create.sh
This script executes the SYSPCI utility to initialize installed Natural
products and create the required Adabas files.
For more information, see SYSPCI Utility - Product Configuration and Initialization in Natural's Tools and Utilities documentation.
After the installation, all scripts used to run Entire Output
Management (nom*.bsh) are contained in the directory
$NOM_HOME. Adapt them to suit your requirements.
| Script | Function |
|---|---|
nomarc.bsh |
Starts the archiving tasks. |
nomcdn.bsh |
Starts the condense tasks. |
nomchkpr.bsh |
Checks for finalized printouts. |
nomconfi.bsh |
Manual confirmation of printouts. |
nominit.bsh |
Loads the initial sample objects of a new Entire Output Management version. |
nommon.bsh |
Starts the monitor tasks. |
nomprt.bsh
|
Starts the printer tasks. |
nomrev.bsh |
Starts the revive tasks. |
nomrpc.bsh |
Starts an RPC server to be invoked by the Entire Output Management GUI Client or the Open Print Option (OPO). |
nomshut.bsh |
Can be used to shut down the monitor from outside of Entire Output Management. |
Make sure that the following environment variables are set appropriately:
| Environment Variable | Function | Default Value |
|---|---|---|
EOM_WORK |
A directory used by Entire Output Management to store intermediate files or log information. | $NOM_HOME/work |
EOM_ARC |
The directory in which archive files are stored. | $NOM_HOME/archive |
The environment variables must be known by the Entire System Server on UNIX which is accessed, not the Entire Output Management monitor itself (unless a monitor of type "L" (local) is used).
The Entire Output Management monitor is accessed using the user ID and the password of a UNIX node definition which can be entered via Node Definitions (menu 8.1.13).
This is an addition to the Monitor Defaults (menu 8.1.2) and has to be created for the UNIX node where the monitor is executed.
Entering "M" or "L" in the Node Status field indicates that the node is a monitor and must not be suspended by Entire Output Management. A type "M" monitor accesses Entire System Server on UNIX using EntireX, even if the destination Entire System Server resides on the same machine. However, it is possible to use an Entire System Server on the same machine by entering type "L": This will install the node as a local monitor which invokes Entire System Server as a subprogram in the same address space.
The database ID and file number of the container file
(NOM-CONTAINER), as specified with the SYSPCI utility, must also
be specified in the
Node
Definitions.
The Adabas nucleus has to be started using the following control statement:
OPTIONS=(TRUNCATION,AUTO_EXPAND)
To verify that Entire Output Management has been installed correctly, perform the following steps.
To do so:
Log on to the library SYSNOM and invoke the
program MENU.
Entire the direct command 8.1.1 on the
Default Definition Menu to verify that the System Default
parameters DBID and FNR point to the correct Entire Output Management system
file.
Press PF3 to return to the previous menu.
Select Option 2 to verify that at least one printer task is specified.
To do so:
In the Entire Output Management online system, enter the
direct command START MON.
To do so:
Create a UNIX monitor node definition using a UNIX directory owned by the Monitor.
Create a report definition which collects files from the UNIX monitor defined in item 1.
Create a file which matches the report definition in the directory of the UNIX node.
Invoke the Monitor Management screen (menu 8.6), and press PF10 to wake the monitor.
The Monitor should now start to create e report.
Enter the direct command LIST AREP and then the
line command LF for the folder #Inbasket to the list
the active reports contained in the folder.
Enter the line command BR to browse the arrived
report.