This section covers the following topics:
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
If you want to use the Entire Output Management standard
separation exits for reports and bundles, copy the current versions of the
option) to the library
Always copy the current versions of the following data areas
REPLACE option) to the library
P-UEXITE (for separation
P-PEXIT (for printing exits),
NOMEX08E (for user
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
in the library SYSNOMS.
The following tasks require job skeletons which have to be adapted
to your requirements. Adapt the sources in the library
which are specified in the Source column and make them available under the
Target name as shown below:
|z/VSE with DYNAM-T||JARCVCAT|
|z/OS GDG or predefined Disk VOLSERs||JARCMDSK|
|BS2000 with job variables||JARCBTJV|
|z/VSE with DYNAM-T||JREVVCAT|
|z/OS GDG or predefined Disk VOLSERs or SMS||JREVMDSK|
|BS2000 with job variables||JREVBTJV|
|z/VSE with DYNAM-T||JCDNVCAT|
|z/OS GDG or predefined Disk VOLSERs||JCDNMDSK|
|BS2000 with job variables||JCDNBTJV|
|POWER||SYSPRPWR||SYSPRPWR or user-defined|
|z/VSE Tape||TAPEVSE||TAPEVSE or user-defined|
|JES||SYSPRJES||SYSPRJES or user-defined|
|z/OS Disk||DISKMVS||DISKMVS or user-defined|
|z/OS Tape||TAPEMVS||TAPEMVS or user-defined|
|BS2000||SYSPRBS2||SYSPRBS2 or user-defined|
|BS2000 with job variables||SYSPRBJV||SYSPRBJV or user-defined|
|BS2000 for binary printing||SYSPBBS2||SYSPBBS2 or user-defined|
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
To activate the common data pool, assign a value of at least "1"
To run Natural subtasks, assign a value of at least "80" to the
For all online and batch tasks which execute Entire Output Management, the following Natural profile parameters have to be set:
||Control variable modified at input.|
||Set input delimiter to blank.|
||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:
||Unicode and code page support.|
||Default code page.|
If Natural Security is installed at your site, you have to create security profiles for the following libraries and users.
||Entire Output Management online application.||
||Entire Output Management help system (English).||-|
||Entire Output Management help system (German).||-|
||User copy of
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
parameters taken from the main member
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's start program
SYSSAT. In a non-security environment, this means
MENU will not be found as start program. Therefore you have
to rename the program
MENUNOM in the library
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
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
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:
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.
||Indicates whether Natural Security is installed or not.|
||If Natural Security is installed, this is the user ID for logging on to it.|
||Password for logging on to Natural Security.|
||User ID for logging on to Entire System Server, if it is installed and an interface to an external security system is activated.|
||Name of the Natural subtask module for starting a server as a subtask.|
||3-byte product code.|
||Entire Output Management Servers are always started as subtasks.|
||Name of the Natural library where Entire Output Management Server is installed.|
||Pointer to the Entire Output
Management data file (must be unique within all
||BS2000 user ID under which the
Monitor, Archive, Revive and Condense jobs are submitted. Default:
||Generate unique ETIDs for tasks.|
||6-byte prefix for ETIDs.|
| 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
||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.|
You can overwrite the
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)
||You can specify a member in which Entire Output Management-specific parameters are located.|
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
|Sets the SAT defaults for all System Automation Tools products.|
|Indicates that a separate user ID/password can be used for Entire Output Management's Print task.|
|Indicates that a separate user ID/password can be used for Entire Output Management's Archive task.|
|Indicates that a separate user ID/password can be used for Entire Output Management's Revive task.|
| Sets the Natural defaults for all System Automation
Tools products: the Natural profile parameters are provided in the profile
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.|
Migrations from earlier versions are not supported.
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.
Before you start the migration, make sure that the Entire Output Management Monitor 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
MIXDSDEV is used in the ADALOD utility, record
spanning is not available. Therefore the
MIXDSDEV parameter must
Execute the following jobs:
|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.
See Migration in the Installation and Customization on UNIX documentation.
To start Entire Output Management for the first time:
Make sure that the Entire System Server node under which the Entire Output Management Monitor runs is active.
Log on to the library
Execute the program
This program adds the first user ID, modifies some example definitions, and asks you to specify various Entire Output Management parameters.
When you have completed this step, the Entire Output Management Main Menu is displayed.
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.
To verify that Entire Output Management has been installed correctly, perform the following steps.
To do so:
Log on to the library
SYSSATU where you keep
your master definitions for all servers of the System Automation Tools
Check that the
SATnnnnn entry in the member
SATDIR points to the correct FNAT for the application
SPnnnnn for the
SATSTART entry with
TYPE parameter should have the value
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.
SPnnnnn for the
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.
Check the member
SPnnnnn for the
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.
To do so:
Log on to the library
SYSNOM and invoke the
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.
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);
For JES3, these classes must be defined as
temporary class is specified;
a reserved virtual printer must be specified (BS2000).
If the Entire System Server is active, proceed with Step 4 below, to start the Entire Output Management Server online.
SATSTART block for the Entire Output
Management Server in the
SPnnnnn is provided correctly, the
Server is started automatically with the Entire System Server node
To do so:
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
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.
If this sequence does not appear after a while, check the following:
If the Entire System Server node is running under z/OS,
SYSOUT files of the node.
If the Entire System Server node is running under z/VSE,
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:
where xx stands for the
Entire Output Management subtask and nnn for the
server number. xx =
XT for the main
05 for subtasks.
Proceed with Step 5 below.
To do so:
In the Entire Output Management online system, enter the
To do so:
Run any job which produces output in one of the classes defined as reserved for Entire Output Management.
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
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