Version 3.2.1	SEARCH   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

With the System Defaults function you can system-wide defaults.

This section covers the following topics:

• Defining System Default Parameters

• System Defaults

• Integrating Natural Applications

• Monitor Defaults

• Defining Container Files

• Subtask Processing

• Report Processing Defaults

• Bundle Processing Defaults

• Automatic Archiving Defaults

• Defining Archiving Schedule Parameters

• User-Defined Archives

• Automatic Reviving Defaults

• Automatic Cleanup Defaults

• CMA-SPOOL Defaults

• Natural Advanced Facilities Defaults

• NOM API and User-Exit Defaults

• SAP-Spool Defaults

• UNIX Defaults

• 3GL Interface

• 3GL Interface Maintenance

Defining System Default Parameters

To define System Default parameters

1. Enter 1 in the command line of the System Administration Menu.

   The Default Definition Menu appears. From this menu, you can select the following functions:

   • 1 - System defaults

   • 2 - Monitor defaults

   • 3 - Report processing defaults

   • 4 - Bundle processing defaults

   • 5 - Automatic archiving defaults

   • 6 - Automatic reviving defaults

   • 7 - Automatic cleanup defaults

   • 8 - CMASPOOL defaults

   • 9 - Natural Advanced Facilities defaults

   • 10 - NOM API and user-exit defaults

   • 11 - SAP-Spool defaults

   • 12 - 3GL interfaces

2. To select a function, you enter its number in the command line.

System Defaults

To define default parameters for Entire Output Management

1. Enter 1 in the command line of the Default Definition Menu.

   The System Defaults screen appears.

   18:32:08 **** ENTIRE OUTPUT MANAGEMENT **** 15/04/2007 UserId UKSJU - System Defaults - NOM Data File NOM Active Data File DBID .................... 9____ DBID .................... 9 FNR ..................... 243__ FNR ..................... 243 Use Owner-ID ............... N Date format ................ E Support long names ......... Y Automatic user definition... P Daily Cleanup Time .................... _____ Next run ................ 16/04/2007 00:01 Log Types ................... _ _ _ _ _ _ _ _ _ _ Retention Period ........ 10D__ Printouts Types ................... _ _ _ Retention Period ........ _____ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Appl Menu

Special PF Keys

Fields

NOM Data File DBID/FNR

The Adabas database ID and file number of the Entire Output Management data file.

Use Owner ID

Y - Operating-system resources should be accessed with the user ID of the report owner or bundle coordinator. This allows users whose ID is not externally defined (RACF, BS2000/OSD user ID, etc.) to use Entire Output Management.

N - The Entire Output Management user must have authorization to access operating system resources.

Date Format

The date format which is used in all date input and output fields within Entire Output Management. You can select one of the following date formats.

Integrating Natural Applications

To integrate Natural applications in the Entire Output Management Main Menu

1. Press PF9 on the System Defaults screen.

   The "System Defaults > Applications" screen appears.

   10:32:00 **** Entire Output Management **** 11/11/2007 UserId XYZ - System Defaults>Applications - Title Library StartPgm Parameter ________________________________ ________ ________ _________________________ Natural Advanced Facilities_____ SYSPOOL_ MENU____ _________________________ Entire System Server Tutorial___ SYSNPE__ MENU____ _________________________ CON-NECT________________________ SYSCNT2_ MENU____ DBA DBA__________________ KIDICAP 2000____________________ KIDICAP_ MENU____ _________________________ ________________________________ ________ ________ _________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Menu

Fields

Automatic Display of other SAT Products

If other System Automation Tools products are installed at your site, they are automatically displayed in the same menu. If Natural Security is installed, a second check is performed, and a message is displayed if the user is not allowed to logon to the Application.

In this way, it is easy to "toggle" between:

• Entire Output Management and

• Entire Operations, Entire Event Management or Natural NSPF.

Monitor Defaults

• POWER / JES2

• JES3

• BS2000/OSD

The Monitor runs as one or more subtask/s under Entire System Server or as one or more batch job/s and controls the generation, printing and distribution of reports and bundles.

POWER / JES2

To define default parameters for the Entire Output Management Monitor

1. Enter 2 in the command line of the Default Definition Menu.

   The Monitor Defaults screen appears:

   17:58:10             **** ENTIRE OUTPUT MANAGEMENT ****            2007-11-08
  UserId UKSJU                - Monitor Defaults -
 
  Monitor Defaults                                      Error Handling
     Node/System/Spool Type .. 40_ MVS/ESA  JES2           Retries..... 5__
     Batch Module ............ NATSAT31                    Interval.... 300__
     System Server Jobname ... NOMX040_
     Printer Tasks ........... 2_
  Wait Factor                              Long Records
     Minimum ................. 30__           Container File DBID ..... 9____
     Maximum ................. 60__           Container File FNR ...... 247__
     Increment ............... 5__
  Classes
     Sysout .................. 8 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
     Temporary ............... T
     Print ................... X
  Jobcards
     //* TRACE=ON____________________________________________________________
     ________________________________________________________________________
     ________________________________________________________________________
 
  Command => ___________________________________________________________________
 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help        Exit  Flip  Do    Undo  CopFi Tasks Archv             Menu

Special PF Keys

Fields

JES3

JES3 has an additional field:

BS2000/OSD

BS2000/OSD has two additional fields:

Warning: Rename=N and changing contents of input files will lead to inconsistent reports unless they are all kept in the database. For this reason, reports resulting out of BS2000/OSD datasets with changing contents must always be created with 'Store in NOM DB = Y'; otherwise the source must be copied to a container file before processing.

Defining Container Files

This function is used to define Container Files for the Entire Output Management Monitor. Container Files should be used if separation processing is defined for the SYSOUT and/or if SYSOUT is to be browsed online. Data are compressed in the specified files.

To invoke this function:

1. Press PF7 on the Monitor Defaults screen.

2. A window is displayed, in which you can specify the following:

Subtask Processing

This function is used to define subtask processing for the Entire Output Management Monitor.

To invoke this function:

1. Press PF8 on the Monitor Defaults screen.

   The following screen is displayed:

   12:10:34 **** ENTIRE OUTPUT MANAGEMENT **** 2008-02-29 UserId XYZ - Monitor Task Profile - Task Scan Copy Create Manage Wait Factors Number Queues Source Reports Printout Min Max Increment 1 _ _ _ _ 30 120 10 2 X _ _ _ 60__ 300_ 30_ 3 _ X _ _ 120_ 3600 120 4 _ _ X _ 30__ 180_ 10_ 5 _ _ _ X 40__ 240_ 20_ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Menu

2. Here you can split the workload of the monitor between up to 5 different tasks, each with their own wait factors.

   The management functions of the monitor (for example, cleanup, active bundle flushing) are always done by Task 1. Task 1 will also take over work for any subtask that fails.

Report Processing Defaults

This function is used to define default parameters for report processing. These defaults apply to newly-created reports. They can be modified for each report.

To invoke this function:

1. Enter 3 in the command line of the Default Definition Menu.

   The following screen is displayed:

   17:43:25 **** ENTIRE OUTPUT MANAGEMENT **** 2007-08-24 User ID UKSJU - Report Processing Defaults - Store in NOM DB ...... N Archive directly ..... N Create Definition .... _ Report Retention Number ............ 5__ Unit .............. A Calendar .......... ________ Action ............ P Separator Pages Start ............. ________ End ............... ________ Copies ............ ___ Jobcards //NOMREPPR JOB CLASS=K,MSGCLASS=X_______________________________________ ________________________________________________________________________ ________________________________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Edit Menu

2. The values you enter on this screen are automatically written to the fields with the same names on the Report Definition screens.

   For further information on report processing, see the section Defining a Report in the User's Guide.

Special PF Keys

Fields

Bundle Processing Defaults

This function is used to define default parameters for bundle Processing. These defaults apply to newly-created bundles. They can be modified for each bundle.

For further information, see Adding a Bundle Definition in the User's Guide.

To invoke this function:

1. Enter 4 in the command line of the Default Definition Menu.

   The following window is displayed:

   +---------------------------------------------------------------------------+ ! - Bundle Processing Defaults - ! ! ! ! Retention Period ....... ___ Unit _ Calendar ________ ! ! ! ! Hold Before Print ...... _ (Y/N) ! ! Printer List ......... ________ ________ ________ ________ ________ ! ! Copies ....... ___ ___ ___ ___ ___ ! ! ! ! Separator Bundle ....... ________ (Start) ________ (End) ___ (Copies) ! ! Report ....... _ (Y/N) ! ! ! ! Print Job card ! ! ________________________________________________________________________ ! ! ! ! PF1 Help PF3 Exit PF5 Do PF6 Undo PF12 Menu ! ! ! +---------------------------------------------------------------------------+

2. The values you enter here are automatically written to the fields with the same names on the Bundle Definition screen.

Fields

Automatic Archiving Defaults

This function is used set default parameters for archiving. These parameters enable you to create archive datasets and schedule automatic archiving.

For further information on Archiving, see the sections Archive Administration and Start Archiving Task.

To invoke this function:

1. Enter 5 in the command line of the Default Definition Menu.

   The following screen is displayed:

   13:01:43 **** ENTIRE OUTPUT MANAGEMENT **** 2008-03-18 User ID BRY - Archiving Parameters - Default Retention Number ............. 20__ Time scheduled ..... Y Unit ............... D Next run ........... 2008-03-19 09:00 Skeleton .............. JARCSKEL Data set prefix Archive ............ NOM.ARC221____________ Condense ........... NOM.COND221___________ EXPDT .... _ Generic name .......... 3380____ Storage class (SMS) ... ________ Archive to disk GDG ................ N Max. generations ... Predefined VOLSERs.. USRF08 USRF09 USR005 USR006 ______ ______ Condense Threshold .... __________ Delete Empty ... _ Jobcards //NOMARC22 JOB NOM,CLASS=K,MSGCLASS=X___________________________________ ________________________________________________________________________ ________________________________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Sched UsArc Edit Menu

   The above illustration shows the screen as it appears under z/OS. Under other operating systems, the screen looks slightly different.

Special PF Keys

Fields

• Fields -All Operating Systems
• Fields - z/OS only
• Fields - z/VSE only
• Fields - BS2000/OSD only

Fields -All Operating Systems

The following fields are common to all operating systems.

Fields - z/OS only

Fields - z/VSE only

Fields - BS2000/OSD only

Defining Archiving Schedule Parameters

To define Archiving Schedule Parameters

1. Press PF8 (Sched) on the Archiving Parameters screen.

   The Archiving Parameters/Schedule screen appears:

   06:15:37 **** Entire Output Management **** 12/11/2007 User ID XYZ - Archiving Parameters/Schedule - Next run ............. 12.11.2007 13:00 Start Time ........... 13:00 Weekdays ............. MO TU WE TH FR __ __ (Su Mo Tu We Th Fr Sa) Or Monthly Days ...... ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Calendar ............. ________ Before/After Holiday . _ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Menu

Fields

User-Defined Archives

You can define up to 9 custom archive types in addition to the standard archive. This enables you to:

• create multiple hierarchies for archived reports. For example, reports which need to be revived quickly can be archived to disk, with all other reports being archived to tape.

• archive to non-standard datasets (that is, datasets which cannot be accessed as a Natural work file) such as optical disks.

The Entire Output Management monitor submits an archive job for each type which has active reports to be archived. It also submits a condense job for each type which has archive datasets to be condensed. It submits a revive job for each dataset/volume containing reports to be revived.

Notes:

1. You cannot condense datasets of different types into a single output dataset.
2. User-defined archives, which use a user exit, are assigned a logical volser of NOMUDA.

This section covers the following topics:

• Accessing User-Defined Archiving

• Adding a User-Defined Archive

• Defining Keywords for JCL Substitution

• Displaying a User-Defined Archive

• Modifying a User-Defined Archive

• Deleting a User-Defined Archive

• Renaming a User-Defined Archive

• Displaying Cross-Reference Information for a User-Defined Archive

Accessing User-Defined Archiving

To access user-defined archiving:

1. Press PF9 (UsArc) on the Archiving Parameters screen.

   The User Defined Archive Maintenance screen is displayed, listing all existing user-defined archive types:

   13:55:35 **** ENTIRE OUTPUT MANAGEMENT **** 2008-03-18 User ID XYZ - User Defined Archive Maintenance - Cmd Num Name Description ___ ___ ________ __________________________________________________ __ 1 ARCTEST1 User defined archive test - not currently used __ 2 ARCTEST2 User defined archive test __ 3 ARCTEST3 User defined archive to special SMS pool __ 4 ARCTEST4 User defined archive using exit routines __ __ __ __ __ All Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add Exit Flip - + Menu

   For each archive type, the (internally allocated) type number, the name and the short description are displayed.

Special PF Keys

Line Commands

Adding a User-Defined Archive

To add a user-defined archive:

1. Press PF2 (Add) on the User Defined Archive Maintenance screen:

2. The User Defined Archive Type screen appears:

   14:25:48 **** ENTIRE OUTPUT MANAGEMENT **** 2008-03-18 User ID XYZ - User Defined Archive Type - Name ................. ARCTYP5_ Number: 5 Description .......... __________________________________________________ DSN Prefix ........... ______________________________ Job Skeletons Archive ........... ________ Revive : ________ Condense: ________ Default Retention User Routine Number ............ ____ Library: ________ Unit .............. _ Member : ________ Archive Jobcards ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ Revive Jobcards ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Attrb Edit Menu

Special PF-Keys

Fields

Defining Keywords for JCL Substitution

Whenever any of the keywords you define here appears in a job skeleton (prefixed with "&"), it is replaced by its value.

Certain keywords are reserved for Entire Output Management. If you attempt to add a keyword with a reserved name an error message is returned. It is your own responsibility to ensure that value substitution does not result in invalid JCL (for example, truncation).

To define keywords for JCL substitution:

1. Press PF9 (Attrb) on the User Defined Archive Type screen.

2. The following screen appears:

   19:47:54 **** ENTIRE OUTPUT MANAGEMENT **** 2008-04-13 User ID XYZ - User Defined Archive Type - Job Skeleton Variables Keyword Value NOM4A001__ ARCHIVE TYPE 4 KEYWORD 001_______________________________________ NOM4A002__ ARCHIVE TYPE 4 KEYWORD 002_______________________________________ NOM4A003__ ARCHIVE TYPE 4 KEYWORD 003_______________________________________ NOM4A004__ ARCHIVE TYPE 4 KEYWORD 004_______________________________________ NOM4A005__ ARCHIVE TYPE 4 KEYWORD 005_______________________________________ NOM4A006__ ARCHIVE TYPE 4 KEYWORD 006_______________________________________ NOM4A007__ ARCHIVE TYPE 4 KEYWORD 007_______________________________________ NOM4A008__ ARCHIVE TYPE 4 KEYWORD 008_______________________________________ NOM4A009__ ARCHIVE TYPE 4 KEYWORD 009_______________________________________ NOM4A010__ ARCHIVE TYPE 4 KEYWORD 010_______________________________________ __________ _________________________________________________________________ __________ _________________________________________________________________ __________ _________________________________________________________________ __________ _________________________________________________________________ Top Of Data Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo - + Ident Menu

   You can enter up to 28 keywords.

   Special PF Keys

   Key	Name	Function
   PF9	Ident	Return to User Defined Archive Type screen.

Displaying a User-Defined Archive

To Display a user-defined archive:

• On the User Defined Archive Maintenance screen, enter DI in the command line preceding the archive type you want to display.

  The User Defined Archive Type screen appears for the selected archive.

Modifying a User-Defined Archive

To modify a user-defined archive:

1. On the User Defined Archive Maintenance screen, enter MO in the command line preceding the archive type you want to modify.

   The User Defined Archive Type screen appears for the selected archive.

2. You can modify the data displayed by simply entering new data in the input fields.

   Then you press ENTER to save your modifications.

   A message confirms the modification.

Deleting a User-Defined Archive

To delete a user-defined archive:

1. On the User Defined Archive Maintenance screen, enter DE in the command line preceding the archive type you want to delete.

   If CONFIRM is set to ON, a window opens asking you to confirm the deletion.

2. To do so, enter the name of the archive type in the window.

   A message confirms that it has been deleted.

Renaming a User-Defined Archive

To rename a user-defined archive:

1. On the User Defined Archive Maintenance screen, enter RN in the command line preceding the archive type you want to rename.

2. A window will be displayed, in which you enter the new name of the archive.

Displaying Cross-Reference Information for a User-Defined Archive

To display cross-reference information for a user-defined archive:

1. On the User Defined Archive Maintenance screen, enter XR in the command line preceding the archive type for which you want to display information.

   A window is displayed, showing how many objects use this archive type:

   +----------------------------------------------------+ ! - XREF of Archive Type - ! ! ARCTEST4 ! ! ! ! M Relation Type Number ! ! _ _________________________________ __________ ! ! _ Report 1 ! ! _ Active Report 54 ! ! _ Archive Dataset 5 ! ! ! ! ! ! ! ! ! ! ! ! PF3 = Exit ! +----------------------------------------------------+

2. In the window, mark the relation type with any character to display the list of objects.

Automatic Reviving Defaults

The Reviving Parameters function enable you to schedule Automatic Reviving.

For further information, see the section Start Reviving Task.

To define default parameters for Reviving:

1. Enter 6 in the command line of the Default Definition Menu.

   The Reviving Parameters screen appears.

   06:58:32 **** Entire Output Management **** 12/11/2007 User ID XYZ - Reviving Parameters - Skeleton ................ JREVSKEL Schedule Time scheduled ....... Y Next run ............. 12.11.2007 07:00 not before ........... 07:00 every ................ 06:00 not later ............ 19:00 Weekdays ............. MO TU WE TH FR __ __ (Su Mo Tu We Th Fr Sa) Or Monthly Days ...... ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Calendar ID .......... ________ Before/After Holiday . _ Jobcards * $$ JOB JNM=NOMREV,CLASS=0,DISP=H,LDEST=*,SYSID=_______________________ * $$ LST CLASS=Y,DISP=H_________________________________________________ ________________________________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Edit Menu

Special PF Keys

Fields

Automatic Cleanup Defaults

The Cleanup Parameters function enable you to schedule Automatic Cleanup.

Defining Cleanup Parameters

To define default parameters for Cleanup:

1. Enter 7 in the command line of the Default Definition Menu.

   The Cleanup Parameters screen appears.

   18:01:02 **** ENTIRE OUTPUT MANAGEMENT **** 2007-11-08 User ID UKSJU - Cleanup Parameters - Spool Cleanup .... Y Long records ............ _ Report Cleanup ... Y Cleanup Schedule Time scheduled . Y not before ..... 07:00 every ...... 01:01 not later ...... 23:00 Weekdays ....... __ __ __ __ __ __ __ (Su Mo Tu We Th Fr Sa) Or Monthly Days ALL ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Calendar-Id .... ________ Before/After Holiday(s) .. _ Scheduled next ... 2005-11-08 18:11 Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Menu

Fields

The following fields are used to define the automatic scheduling of the Cleanup process.

CMA-SPOOL Defaults

CMA-SPOOL, among other spooling systems, can serve as source for the output data to be processed. Here you can define whether the CMA-SPOOL interface should be active or not.

Entire Output Management scans the specified destinations and moves the output into its own database container for further processing. The destinations to be scanned should be defined as virtual printers reserved for Entire Output Management. The destination is switched to the specified Temporary Destination (also a virtual printer) in order to avoid processing the same queue entry again.

To define default parameters for CMA-SPOOL:

1. Enter 8 in the command line of the Default Definition Menu.

   The following screen appears:

   18:50:25 **** ENTIRE OUTPUT MANAGEMENT **** 15/04/2007 UserId UKSJU - CMASPOOL Defaults - Scan CMA-SPOOL queue ......... N CMA-SPOOL Interface Version .. 90 CMA-SPOOL Version (1/2) _ Temporary Destination ........ NOMTEMP_ Time Limit ............ 6_ Destination DBID FNR Destination DBID FNR ___________ ____ ___ ___________ ____ ___ NOMFIL2_ 9____ 247__ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ ________ _____ _____ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Menu

Fields

Natural Advanced Facilities Defaults

Instead of printing output from Natural programs in the Natural Advanced Facilities spool file (FSPOOL), you can route it to an Entire Output Management file (SYS2), from which it can be distributed, bundled or separated.

Here you can define whether the NAF/NOM interface is active and from which Natural Advanced Facilities environments output is to be processed. A separate Entire Output Management file can be assigned to each FSPOOL file. However, you can also assign the same Entire Output Management file to all FSPOOL files.

To define default parameters for Natural Advanced Facilities:

1. Enter 9 in the command line of the Default Definition Menu.

   The following screen appears:

   12:28:48 **** ENTIRE OUTPUT MANAGEMENT **** 2007-07-24 UserId UKSJU - NATURAL ADVANCED FACILITIES Defaults - NAF Interface active .. Y Time Limit .. 1_ FSPOOL FSPOOL DBID FNR DBID FNR DBID FNR DBID FNR ____ ___ ____ ___ ____ ___ ____ ___ __177 ___43 ____9 __212 _____ _____ _____ _____ ___10 ___60 ____9 __212 _____ _____ _____ _____ ___76 __210 ____9 __247 _____ _____ _____ _____ 11177 _1247 ____9 __247 _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Menu

Fields

NOM API and User-Exit Defaults

Defining API Defaults

To define default parameters for Entire Output Management Application Programming Interfaces

1. Enter 10 in the command line of the Default Definition Menu.

   The API Defaults screen is displayed, listing the available user exits.

2. On this screen, you can activate and deactivate the individual user exits by marking them with "Y" or "N" respectively.

Fields

User Exits

The user exits described below are located in the Natural library SYSNOMS.

User Exit	Explanation
NOMEX001	This exit is called by the Entire Output Management monitor while scanning the spool queue. A call to this function indicates that no report definition was found for the specified source and the spool exit 001 flag was set. The exit must set the "process" flag to TRUE to advise Entire Output Management to make the source as subject for its normal cleanup processing, or FALSE to advise it not to process this output. In this case, the exit must switch the output from the Entire Output Management input queue to prevent subsequent processing for the same output.
NOMEX002	This exit is called by the Entire Output Management monitor while scanning the spool queue. The function is called if the exit 002 flag is set to allow the modification of spool attributes before they are stored in the Entire Output Management database.
NOMEX003	This exit is called by Entire Output Management to allow/disallow access to Natural NSPF.
NOMEX004	This exit is called by Entire Output Management to allow suppression of log messages.
NOMEX005	This exit is called by Entire Output Management to allow modification of print job substitution variables.
NOMEX006	This exit is called by Entire Output Management to make available information about completed printouts.
NOMEX007	This exit is called by the Entire Output Management user interface when certain fields are to be modified online. This exit may set init values for the fields and prohibit modification.
NOMEX008	This exit is called by Entire Output Management to allow integration of user-written application logic with Entire Output Management, allowing to store notes for an active report or even for a specific line of an active report. The exit is invoked whenever the status of an active report changes, a documented example is distributed in library SYSNOMS. The exit is invoked using 2 different functions: GET-STATUS: to return status information (containing 10 bytes) of an active report to be displayed in the list of active reports (notes field). INTEGRATION-EVENT: invoked by the report browser, if PF2 is pressed, to store environment-site and user-specific data (i.e., notes) for an active report or a specific line of an active report.
NOMEX009	This exit is called by Entire Output Management to suppress optimization for counting lines of BS2000/OSD input datasets. Assuming 'Rename=N' (BS2000/OSD files will not be renamed). Normally, when a BS2000/OSD dataset is printed more than once by Entire Output Management, Entire Output Management will count the records in the dataset only once and pass this record count on for further processing. This makes sense, because Entire Output Management assumes that the contents of the dataset do not change. Upon special customer request, this exit was created to allow suppression of this optimization. This means that for each print to Entire Output Management the same dataset is counted again, the reason being that the dataset can change its contents and length. In this case, the flag NOMEX009-COUNT-OPTIMIZE should be set to false. Warning: Rename=N and changing contents of input files will lead to inconsistent reports unless they are all kept in the database. For this reason, reports resulting out of BS2000/OSD datasets with changing contents must always be created with Store in NOM DB = Y; otherwise the source must be copied to a container file before processing.
NOMEX010	This exit is called by Entire Output Management to get or suppress a log message.
NOMEX011	This exit is called by Entire Output Management immediately before a record is written to the required target (PC or Con-nect) and allows modification of browsed active report data as well as suppression and insertion of records. The exit is activated by setting active reports export exit to Y (in NOM API and User-Exit Defaults). The object must be in a library accessible to the Entire Output Management online system. NOM221S contains a sample NOMEX011 as well as the parameter data area P-EXPEX.
NOMEX012	Unused.
NOMEX013	This user exit is called immediately before a report is opened. It will supply attributes of the active report to be opened, spool attributes, and the source attributes. Some fields can be changed and returned to Entire Output Management. For a description of what is to be tested see the program source.

Input Parameters

Output Parameters

SAP-Spool Defaults

SAP-Spool, among other spooling systems, can serve as source for the output data to be processed. Here you can define whether the SAP-Spool interface should be active or not.

Reports can be transferred via SAP exits to Entire Output Management for further processing, instead of being printed by the SAP Spooling System. The data are stored in the specified Adabas file (Entire Output Management container file) and an entry is created for each report in an internal queue. These jobs are run if SAP-Spool interface active is set to Y.

To define default parameters for the SAP spool:

1. Enter 11 in the command line of the Default Definition Menu.

   The SAP-Spool Defaults screen appears.

2. On this screen, you can specify the following:

Fields

UNIX Defaults

• Defining a UNIX or Windows Node

• List of Nodes

• Line Commands

• Fields

• Special PF Keys

You can treat any supported UNIX or Windows platform as a source of output data. So it is possible to get the output of any UNIX or Windows application to a container file and process it as usual, including archiving, distribution, printing on a mainframe printer, bundling, and so on.

This is done via an Entire Broker communication using Entire System Server UNIX, which both have to be installed.

Defining a UNIX or Windows Node

To define a UNIX or Windows node using this function:

1. Press PF2.

   If a node is added, you will get the node definition screen:

   09:39:54 **** ENTIRE OUTPUT MANAGEMENT **** 2007-11-07 User ID FHI - Unix Node Definition - Node : ________________ Suspend (Y/N): _ Descr : __________________________________________________ Temp : _____________________________________________________________________ UserID: ________ Passw.: Container Group : ________ Conf. : Dbid Fnr ____________________________ P A T H S ___________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ __________________________________________________________________ _____ _____ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Do Undo Path

List of Nodes

The nodes that have been defined already can be seen using menu 8.1, number 13:

 10:34:53               **** ENTIRE OUTPUT MANAGEMENT ****            2007-11-07
  User ID FHI                 - Unix Node Definitions -

  Cmd Node Name        Node Description                                 Messg.
   __ ________________ ________________________________________________ ________
   __ npr_nt           node on Windows NT                               Win NT
   __ npr_unix         Unix node                                        Suspend
   __
   __
   __
   __
   __
   __
   __
   __
   __
   __
   __
   __
 All
  Command => ___________________________________________________________________
   DE delete DI display MO modify
 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help  Add   Exit  Flip               -     +                      Menu

This list of nodes shows the current status of the open system node:

Line Commands

Fields

node_name SATSRV TYPE=ACI
          BROKER-ID=...
          SERVER-CLASS=NPR
          SERVER-NAME=...
          SERVICE=node_name
          USER-ID=...
          WAIT-TIME=30S

Special PF Keys

3GL Interface

• Control Block

• Data Field

• Work Area

• Transaction Logic

• Automatic ET

• Transaction Logic Controlled by Caller

The 3GL interface can transfer output page by page to Entire Output Management for further processing. The interface provides the functions OPEN, PUT, CLOSE, which must be used as follows:

The interface consists of a control block, a data field and a work area. Several lists can be transferred to Entire Output Management at the same time, however each list must have its own control block and work area.

Control Block

Data Field

Work Area

Transaction Logic

The print lines are stored in an Adabas database. Like any other changes to a database, the stored records must be confirmed (end transaction) or rejected (backout transaction). The transaction logic can either be executed automatically by the interface or can be determined by the caller.

Automatic ET

If the field Automatic ET has a value >0, the interface performs an ET in the following situations:

1. during processing of the OPEN;

2. during processing of the PUT, if n records have been stored in the database since the last confirmation ( n = value of Automatic ET);

3. during processing of the CLOSE.

   Warning: If 'Automatic ET' has a value greater than 1, the Bytes 1-63 of the spool attributes must uniquely identify the print data. We recommend always choosing 1 as the value for 'Automatic ET'.

Transaction Logic Controlled by Caller

In addition to the OPEN, PUT, CLOSE functions, you must also perform the functions END TRANSACTION and BACKOUT TRANSACTION before calling Adabas with ET or BT.

After the CLOSE you must always perform an Adabas ET call.

Warning: Bytes 1-63 of the spool attributes must uniquely identify the report. We recommend using this option only when you are performing other database changes in your program. In all other cases, you should only work with 'Automatic ET'.

3GL Interface Maintenance

A 3GL interface, among others, can serve as source for the output data to be processed. OPEN, PUT and CLOSE transfer the list data to these 3GL interfaces

OPEN transfers the interface number+attributes (spool attributes) for identification and display purposes. PUT transfers one print line at a time. A CLOSE call tells the interface that the list is complete. An entry is created for processing of the list. For further details, see the section 3GL Interface.

The 3GL maintenance functions enable you to describe your own interface. The data entered are used to interpret the spool attributes and also to dynamically generate the Report Definition>3GL Identification and Active Reports>Spool Attributes screens.

Defining Default Parameters for 3GL Interfaces

To define default parameters for 3GL interfaces

1. Enter 12 in the command line of the Default Definition Menu.

   The following screen appears:

   11:28:08 **** Entire Output Management **** 01/06/2007 User ID XYZ - 3GL Interface Maintenance - Cmd Interface Description ___ _________ ________________________________________________________________ __ 100 NOM 3GL Interface 100 __ 101 NOM 3GL Interface 101 __ 102 NOM 3GL Interface 102 __ 103 NOM 3GL TEST EVN __ 104 User-defined Spool (3GL Interface 104) __ __ __ __ __ __ __ __ __ __ All Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add Exit Flip - + Menu

   This screen lists the defined 3GL interfaces in numerical order.

Line Commands

Fields

Modifying 3GL Interface Defaults

• Invoking the 3GL Interface Defaults Screen
• Fields

Invoking the 3GL Interface Defaults Screen

This function allows you to describe the 3GL interface with the specified interface number.

1. On the 3GL Interface Maintenance screen, enter MO in the command line preceding the interface you want to modify.

   The following screen appears:

   16:29:31 **** Entire Output Management **** 27/07/2007 UserId XYZ - 3GL Interface Defaults - 3GL Interface 104 active ..................... Y Time Limit ................. __ Description ................ User-defined Spool (3GL Interface 104)_______ NOM container file DBID ....................... 9 FNR ........................ 247 Identifying Attributes Prompt Offset Length Order Generic (*) 1040________________ 1__ 8__ 1_ Y 1041________________ 9__ 8__ 2_ N 1042________________ 17_ 8__ 3_ N ____________________ ___ ___ __ _ File identification 1043_______________ 33_ 8__ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Attrb Menu

2. Enter attributes to be used as prompt in the report definition and link them to the spool attributes as specified in the OPEN call (Offset, Length)

3. When you have finished modifying the interface, press ENTER to save your modifications.

   A message confirms the modification.

Fields

Example

In the 3GL interface 104 during OPEN, the user ID is in bytes 1 to 8, the terminal ID in bytes 9 to 16, the program name in bytes 17 to 24 and the list name for post selection in bytes 33 to 40.

The prompts User ID, Terminal ID, Program and List Name were stored via SYSERR in the texts of numbers 1040, 1041, 1042, 1043 in the library SYSNOMU. When 3GL interface 104 is selected for report identification, a screen like the 3GL Interface Defaults screen appears.

Deleting 3GL Interface Defaults

• On the 3GL Interface Maintenance screen, enter DE in the command line preceding the interface defaults you want to delete.

  If CONFIRM is set to ON, a window opens which asks you to confirm deletion by typing the name of the interface defaults again.

• Type the defaults name in the input field provided.

  A message confirms the deletion.

Displaying 3GL Interface Defaults

• On the 3GL Interface Maintenance screen, enter DI in the command line preceding the interface defaults you want to display.

  The 3GL Interface Defaults screen appears for the defaults you selected.

  In display mode, you can only view the object parameters. You cannot enter or modify data because all fields are protected.

www.softwareag.com

Copyright © Software AG 1990-2008. All rights reserved.

SEARCH   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT