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

This section covers the following topics:

• General Attributes

• Life Cycles of Active Report/Attributes

• Report Identification for POWER

• Report Identification for BS2000/OSD

• Report Identification for JES

• Report Identification for 3GL Interface

• Report Identification for SAP Spool

• Report Identification for CMA-SPOOL

• Report Identification for Natural

• Report Identification for UNIX/Windows Nodes

• Printing Attributes

• Distribution Attributes

• Selecting Users to Receive a Report

• Report Layout Attributes

• Separation Attributes

• User Routine Parameters

• Using a Standard Separation Routine

General Attributes

To add a report definition:

1. Press PF2 on the "Report Maintenance" screen.

   The "Report Definition > General Attributes" screen is displayed:

   15:12:25 **** Entire Output Management **** 13/10/2008 User ID XYZ - Report Definition >General Attributes - Report Name .............. _________________________ Description ....... __________________________________________________ Type .............. M Keywords ............. _______________ _______________ _______________ Master Owner ......... ________ Store in NOM DB ...... Y Archive directly ..... N Archive type ......... _ Retention Report Archive Revive Number ............ 1__ ____ ___ Unit .............. A _ _ Calendar .......... ________ ________ Action ............ P Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add Exit Flip Ext Menu

   On this screen, you create a report by defining its general attributes: name, type, owner and certain storage, archiving and retention parameters.

   Some fields are initialized with the values specified in the Report Processing Defaults. For more information, see Report Processing Defaults in the System Administration documentation.

Special PF Keys

Note:
These PF-key assignments appear only after you have entered a report name. However, PF9 and PF21 always appear.

Fields

Life Cycles of Active Report/Attributes

Report Creation

Daily Cleanup Processing

Archive Processing

Revive Processing

Report Identification for POWER

To define or modify report identification for POWER:

1. Press PF7 (Ident) on the "Report Definition > General Attributes" screen.

   The "Report Definition > POWER Identification" screen is displayed:

   15:27:59 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >POWER Identification - Report Name .............. ADABAS-DEFAULT___________ Long records ............ N POWER Attributes Jobname ........... ADA*____ or Destination ......... ________ or Form ........... ____ and Data Sets ........ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo UNIX 3GL NAT SAP Menu

   On this screen, you define how reports are identified in the POWER spool. The report can be identified by job name, destination or form and a spool dataset qualification.

Special PF Keys

Fields

Note:
Processing of sequential files is also triggered by spool queue entries. The corresponding spool file does not contain print data, but points to the sequential file. The pointer can be created with any utility (for example, a Natural program) and must have the following attributes:

NOM DSN=<data-set-name> VOL=<volser>
NOM RECFM=<recform> RECSIZE=<record-length>
NOM BLKSIZE=<block-size> CC=<carriage-control>

• Maximum length of the DSN pattern to identify the dataset is 22.

• Maximum length of the input dataset name is 26.

• Carriage control = ASA, MACHINE or NONE.

• Dataset is renamed before processing.

Report Identification for BS2000/OSD

To define or modify report identification for BS2000/OSD:

1. Press PF7 (Ident) on the "Report Definition > General Attributes" screen.

   The "Report Definition > BS2000/OSD Identification" screen is displayed:

   15:20:30 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID NOM - Report Definition >BS2000/OSD Identification - Report Name .............. ADAREP-DB063___________ Long records ............ N PRINT Attributes Pname ............. ADARE063 or User ID ............. ________ or Form ........... ________ and Data Sets ........ L.ADAREP.063*_______________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo UNIX 3GL NAT SAP Menu

   On this screen, you define how reports are identified in the BS2000/OSD spool (queue for a virtual printer). The report can be identified by the PNAME option of the BS2000/OSD print command, by the BS2000/OSD user ID or the FORM option of the print command and by the completely or partially qualified file name.

Special PF Keys

Fields

Example: If you enter the value ADA* for Pname and the value *L.ADAREP.* for And File, all files are identified whose PNAME begins with ADA and whose file name contains the string L.ADAREP..

The following special characters are supported as placeholders:

The RECFORM parameter of the file allows you to determine whether the print file contains carriage control characters and which ones:

• (F,A),(V,A),... contains ASA carriage control characters.

• (F,M),(V,M),... contains ENDIC carriage control characters.

• (F,N),(V,N),... contains no carriage control characters.

We recommend using files with fixed record length, because positioning within them is easier than within files with variable record length.

Warning: Files with fixed record length that were expanded with OPEN-EXTENT are not supported.

Report Identification for JES

To define or modify report identification for JES:

1. Press PF7 (Ident) on the "Report Definition > General Attributes" screen.

   The "Report Definition > JES Identification" screen is displayed:

   16:00:46 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >JES Identification - Report Name .............. A-SAP-DEFAULT____________ Long records ............ N JES Attributes Jobname ........... X_______ or Destination ......... ________ or Writer ......... ________ or Form ................ ______ and Data Sets ........ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo UNIX 3GL NAT CMA SAP Menu

   On this screen, you define how reports are identified in the JES spool. The report can be identified by job name, destination, writer or form and a spool dataset qualification.

Special PF Keys

Fields

Spool Datasets

To specify the spool datasets in the selected jobs which identify the report(s):

1. Fill in these fields as follows:

   • Either enter: <file type> <file sequence number>

     File type can be:

     JL	JCL statements.
     SI	System input.
     SM	System messages.
     SO	System output.

2. Example: enter SO 1 for the first SYSOUT dataset or SO 1:2 for the first and second SYSOUT datasets.

   Or:
   Enter a list of full DDNAME qualifiers in the format:

   <PROCNAME>.<STEPNAME>.<DDNAME>

   For example:

   PROC1.STEP1.DDN1

   PROCNAME and STEPNAME are not mandatory, and when missing are assumed to be * (any). You can use an asterisk (*) to enter selection criteria for the dataset names, for example:

   *.STEP1.DDN1

   This refers to a spool dataset with STEPNAME=STEP1, DDNAME=DDN1 and any procedure name.

   *.*.DDN1, *.DDN1 or DDN1

   for example, are equivalent and they refer to a spool dataset with DDNAME=DDN1 in any procedure name or step name in the job.

   Or:
   Enter TYPE=AL to create an active report containing all System Message and SYSOUT datasets for a job matching the specified Jes attributes. The job must have at least one spool file in one of Entire Output Management's managed classes. TYPE=AL must be the only dataset criterion.

Note:
If more than one JES2 spool dataset of a job is to be processed by Entire Output Management, then the job's spool datasets, which are to be processed, must all have the same group ID and all be together in a class reserved for Entire Output Management. If this is not achieved by the DD statements, but by a program via Entire System Server functions, for example, then the view SPOOL-UPDATE should be used as follows:

PROCESS SPOOL-UPDATE
        USING  FUNCTION   = 'CHANGE'
        USING  JOB-NAME   = #JOB-NAME
        USING  JOB-NUMBER = #JOB-NUMBER
        USING  GROUP-ID   = #GROUP-ID
        USING  CLASS      = #NOM-CLASS
        USING  NODE       = #NODE
        GIVING ERROR-CODE
               ERROR-TEXT

Sequential Files

Enter dataset name, if spool data resides in a sequential file. The dataset name is preceded by DSN=. The following special characters are supported as placeholders:

Note:
Processing of sequential files is also triggered by spool queue entries. The corresponding spool file does not contain print data, but points to the sequential file. The pointer can be created with any utility and must have the following attributes: NOM DSN=<data-set-name>

• Maximum length of the DSN pattern to identify the dataset is 22. That is, it must begin with "DSN=" and can then have up to 22 characters, including wildcards.

• Maximum length of the input dataset name contained in the spool file is 26.

• The STEPNAME to create the spool dataset must be NOMDSN.

Example:

//JOB 1         JOB...
......
//NOMDSN       EXEC       PGM=IEBGENER
//SYSPRINT      DD          SYSOUT=*
//SYSUT2         DD          SYSOUT=3
//SYSIN            DD          DUMMY
//SYSUT1         DD *
NOM  DSN=OUTPUT.LISTING
/*

Report Identification for 3GL Interface

To define or modify report identification for a 3GL interface:

1. Press PF8 (3GL) on the "Report Definition > JES Identification" screen.

   The "Report Definition > 3GL Identification" screen appears:

   14:44:29 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >3GL Identification - Report Name .............. USR104-TEST______________ 3GL Interface 104 Attributes User ID ............ MRS*____ or Terminal ID ........ ________ or Program ............ ________ and List-Name .......... ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Menu

   On this screen, you define reports that rely on a general, user-defined 3GL interface. All identifying attributes can be freely chosen.

Fields

Report Identification for SAP Spool

To define or modify report identification for SAP Spool:

1. Press PF11 (SAP) on the "Report Definition > JES Identification" screen.

   The "Report Definition > SAP-Spool Identification" screen is displayed:

   16:02:29 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >SAP-Spool Identification - Report Name .............. A-SAP-DEFAULT____ SAP-Spool Attributes Destination ....... *___ or User ID ........... *___ and List IDs ......... ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Menu

Fields

Report Identification for CMA-SPOOL

To define or modify report identification for CMA-SPOOL:

1. Press PF10 (CMA) on the "Report Definition > JES Identification" screen.

   The "Report Definition > CMA-SPOOL Identification" screen is displayed:

   10:48:19 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >CMA-SPOOL Identification - Report Name .............. ADAREP-DEFAULT___________ CMA-SPOOL Attributes Filename .......... ________ or UserID ............ ________ or Writer ............ ________ or Form .............. ____ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Menu

   On this screen, you define how reports are identified in the CMA-SPOOL. The report can be identified by CMA-SPOOL attributes: Filename, UserID, Writer or Form.

Fields

Report Identification for Natural

To define or modify report identification for Natural:

• Press PF9 (NAT) on the "Report Definition > JES Identification" (or "> POWER Identification") screen.

  The "Report Definition > Natural Identification" screen is displayed:

  09:12:27 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >NATURAL Identification - Report Name .............. ADAREP-DEFAULT___________ NATURAL Attributes *USER ............. ________ or *LIBRARY ID ....... ________ or Printer Profile ... ________ and *PROGRAM .......... ________ and FORM .............. ________ and NAME .............. ________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Menu

  On this screen, you define how reports are identified in Natural Advanced Facilities. The report is identified by Natural user ID, library ID or logical printer name and can also be identified by program, form and name. See also the DEFINE PRINTER statement in the Natural documentation.

Fields

Output from Natural is produced during the processing of a specific program. This program is stored in a Natural library and executed by a Natural user. The output can have various attributes defined in the DEFINE PRINTER statement. To identify this output, specify one or more identification attributes:

Notes:

1. Use an asterisk (*) to enter selection criteria for a field, for example, MRS* for all Natural user IDs that begin with MRS. You can use asterisk notation for all attributes except Printer Profile.
2. A first selection is made by the primary attributes, considerably reducing the number of definitions. A definition is applied to the print file, if at least one primary attribute is matched. All secondary attributes for which you have entered values must be matched.

For example: If you enter the value EBU for *USER and the value SYSNOM for *LIBRARY ID, all print files are identified which were either created by user ID EBU or created in the library SYSNOM.

Report Identification for UNIX/Windows Nodes

To define or modify report identification for UNIX:

• Press PF7 (UNIX) on the "Report Definition > JES Identification" (or "> POWER Identification" or "> BS2000 Identification") screen.

  The "Report Definition > UNIX Identification" screen is displayed:

  11:37:40 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID FHI - Report Definition >UNIX Identification - Report Name ................... Report________________Long Records..........N UNIX Attributes Node Name .................. node_name_______ Path: e:/Nomdir/ and Files ......... file*_pattern_____________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Node Menu

  On this screen, you define how reports are identified on UNIX or Windows nodes. Identification is done using node name, path, and file pattern, see below. ASCII files are scanned in the specified directory and matched to the file pattern specified here. These files are moved to an EOM container file and can be processed as usual. An ASCII file can contain line feeds and form feeds; any other kind of control character will be ignored and set to blank.

Fields

Printing Attributes

To define or modify Printing Attributes:

1. Press PF8 (Print) on the "Report Definition > General Attributes" screen.

   The "Report Definition > Printing Attributes" screen appears:

   12:05:13 **** ENTIRE OUTPUT MANAGEMENT **** 2008-03-19 User ID XYZ - Report Definition >Printing Attributes - Report Name .............. XYZ-XML__________________ Hold Logic ........... _ Printers ............. ________ ________ ________ ________ ________ Copies ............... ___ ___ ___ ___ ___ Separator Pages Start ............. ________ End ............... ________ Copies ............ ___ Length ............ ___ Style.. ______________________________________________________________________ Jobcards ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Edit Prtr Menu

   On this screen, you define how reports are printed automatically.

Special PF Keys

Fields

Additional Printers

If you want to define or modify more than five printers, you use the following function.

To define or modify additional Printers:

1. Press PF11 (Prtr) on the "Report Definition > Printing Attributes" screen.

   The "Report Definition > Additional Printers" screen is displayed.

2. On this screen, you can define up to 15 additional printers for a report by specifying:

Fields

Distribution Attributes

To define or modify the Distribution Attributes:

1. Press PF9 on the "Report Definition > General Attributes" screen.

   The "Report Definition > Distribution Attributes" screen is displayed:

   15:36:54 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >Distribution Attributes - Report Name .............. FVSE-DB__________________ Distribution via NOM User/List ......... DC-GROUP ________ ________ ________ ________ ________ ________ ________ ________ ________ Distribution via CON-NECT Cabinet ........... ________ Subject ........... ____________________________________________ Mail to ........... ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Layot Menu

   On this screen, you define the recipients of a report and the facilities used for distribution.

Special PF Keys

Fields

Selecting Users to Receive a Report

To select a user or group of users on a distribution list:

1. Enter an asterisk (*), or a selection criterion ending in an asterisk, in a User/List field on the "Report Definition > Distribution Attributes" screen.

   The "Member Name" window is displayed.

2. Press one of the following keys:

   • PF4 to display a list of all users;

   • PF5 to display a list of all distribution lists.

Selecting Single User for Report

To select a single user to receive a report:

1. Press PF4 (User-List) in the "Member Name" window.

   A window is displayed, listing all users defined for your Entire Output Management system.

2. Enter any character in the field preceding the desired user.

   The user ID is written to the User/List field.

   When this report is produced, it is distributed to the "inbasket" of the user you have selected. This user can then browse and print the report. You can also restrict the user's view of the report by defining an individual report layout. For more information, see the section Report Layout Attributes.

Selecting Distribution List for Report

To select a distribution list to receive a report:

1. Press PF5 (Dist-List) in the "Member Name" window.

   A window is displayed with a list of all distribution lists defined for your Entire Output Management system.

2. Enter any character in the field preceding the desired distribution list.

   The name of the distribution list is written to the User/List field.

   All the users on the distribution list you have selected receive this report when it is produced. They can browse and print it. You can also restrict the users' view of the report by defining a report layout for the distribution list. For more information, see the section Report Layout Attributes.

Report Layout Attributes

To define or modify a report layout for an addressee:

• On the "Report Definition > Distribution Attributes" screen, place the cursor on a User/List field containing a user ID or list name and press PF10 (Layot).

  The "Report Definition > Layout Attributes" screen is displayed:

  15:40:42 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >Layout Attributes - Report Name .............. FVSE-DB__________________ User/List ......... DC-GROUP From To Layout ............ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Headerlines ....... ___ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo - + Ext Menu

  You can define up to 10 different layouts for each report to be distributed to different addressees. A report layout consists of up to 10 pairs of offsets starting from the beginning of a report line (not including ASA/machine codes).

  Note:
  These layouts are only for addressees in Entire Output Management. Addressees in Con-nect see the entire report.

  For more information on layout, see the section Modifying the Layout of an Active Report.

Fields

Separation Attributes

To define or modify Separation Attributes:

• Press PF10 (Separ) on the "Report Definition > General Attributes" screen.

  The "Report Definition > Separation Attributes" screen is displayed:

  15:41:21 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >Separation Attributes - Report Name .............. FVSE-DB__________________ Create Definition .... _ Standard Routine ..... __ User Routine NATURAL Member ..... ________ NATURAL Library .... ________ 3GL ................ ________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Param Edit Trace Menu

  On this screen, you define whether a user routine or a standard routine is to be used.

Special PF Keys

Fields

User Routine Parameters

To define or modify parameters for a user routine:

1. Press PF9 (Param) on the "Report Definition > Separation Attributes" screen.

   The "Report Definition > User Separation" window is displayed.

2. In this window, you can specify up to 5 parameters which are passed to the user routine at the start of report processing.

Using a Standard Separation Routine

A Standard Separation Routine is a method supplied by Software AG for separating or filtering spool datasets. When you use such a routine, you must supply parameters which tailor further processing.

Using Standard Separation 1

Standard Separation 1 separates spool data into several reports depending on the break of the specified suffix. The suffix need not appear in sorted order.

Standard Separation 1 searches for a defined string in a defined line or anywhere on a page. If the string appears on a page, a suffix is evaluated (at break of the suffix value, a new report is opened). If the string is not found, the page is added to the currently open report. If no report is open, the page is rejected.

Note:
When separating POWER spool datasets, make use of container files. The spool dataset is compressed and copied into a database file before processing. For more information on container files, see Monitor Defaults in the System Administration documentation.

To define or modify the use of Standard Separation 1:

1. Enter "1" in the Standard Routine field on the "Report Definition > Separation Attributes" screen and press PF9 (Param).

   If long report and bundle names are displayed by the system (see settings in System Defaults and Adding a User Profile), the "Report Definition > Standard Separation 1" screen will take the following form:

   18:36:30 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >Standard Separation 1 - Report Name .............. UEX-GO___________________ Search Line .............. ___ String ............ __________________________________________________ Suffix Line .............. ___ Start Column ...... ___ End Column ........ ___ Prefix: Reports ...... _________________________ Bundles(1-2).. _________________________ _________________________ (3-4).. _________________________ _________________________ (5).... _________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Menu

   With PF9 (Ext) you can switch to short names display.

Fields

*STRING1*STRING2*

*STRING1%STRING2*

Example1 - Salary Report

We have a salary report sorted by department number and want to separate it into the various departments. A standard routine could be defined as follows to perform an automatic separation:

Report Definition (Stand. Separation 1)

   15:43:45             **** ENTIRE OUTPUT MANAGEMENT ****            2008-11-15
  User ID XYZ       - Report Definition >Standard Separation 1 -
  Report
     Name .............. PWR-EMPL-STD1-S__________
  Search
     Line .............. 2__
     String ............ *Employee List sorted by Departments*______________
  Suffix
     Line .............. 3__
     Start Column ...... 55_
     End Column ........ 58_

  Prefix: Reports ...... DEPTS1-__________________
          Bundles(1-2).. DEP-_____________________ _________________________
                 (3-4).. _________________________ _________________________
                 (5).... _________________________

  Command => ___________________________________________________________________
 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help        Exit  Flip  Do    Undo              Ext               Menu

Note:
The bundle prefix is optional.

This standard routine separates the spool dataset on a page basis and creates reports whose names begin with DEPTS1-. The report name is created by adding the prefix DEPTS1- to the suffix found in the spool dataset in the positions defined in the example above, for example: DEPTS1-FINA.

Optionally, the report can be directed to a bundle with the prefix DEP-. The bundle name is created by adding the DEP- prefix to the suffix found in the spool dataset, for example: DEP-FINA.

Note:
When the suffix and the identifier string are not on the same line, the line parameters must be used. Enter the line numbers where the identifier string and suffix are found. This must be the absolute line number as counted from the top of the page.

Using Standard Separation 2

Standard Separation 2 separates spool data into several reports depending on up to 5 break conditions.

Standard Separation 2 searches for a defined string in a defined line or anywhere on a page. If the string appears on a page, up to 5 suffixes are evaluated (at break of a suffix value, a new report is opened for that suffix). If no string is found, the page is added to the currently opened reports. If no report is opened, the page is rejected.

Note:
When separating POWER spool datasets, make use of container files. The spool dataset is compressed and copied into a database file before processing. For more information on container files, see the section Monitor Defaults in the System Administration documentation.

To define or modify the use of Standard Separation 2:

1. Enter 2 in the Standard Routine field on the "Report Definition > Separation Attributes" screen and press PF9 (Param).

   If long report and bundle names are displayed by the system (see settings in System Defaults and Adding a User Profile), the "Report Definition > Standard Separation 2" screen will take the following form:

   19:00:10 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >Standard Separation 2 - Report Name .............. UEX-GO___________________ Search Line .............. ___ String ............ __________________________________________________ SuffixLi/CF/CT Report Prefix Bundle Prefix 1 _____________ _________________________ _________________________ ___ ___ ___ _________________________ _________________________ ___ ___ ___ _________________________ _________________________ ___ ___ ___ _________________________ _________________________ ___ ___ ___ _________________________ _________________________ ___ ___ ___ _________________________ _________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext < > Menu

   By pressing PF9 (Ext) you can switch to short names display.

Fields

*STRING1*STRING2*

*STRING1%STRING2*

Example 2 - Salary Report

We have a salary report sorted by department number and want to separate it into the various main departments and sub-departments. A standard routine could be defined as follows to perform an automatic separation:

Report Definition (Stand. Separation 2)

  19:00:10             **** ENTIRE OUTPUT MANAGEMENT ****            2008-11-15
 User ID XYZ       - Report Definition >Standard Separation 2 -
 Report
    Name .............. PWR-EMPL-STD2-S__________
 Search
    Line .............. 2__
    String ............ *Employee List sorted by*_________________________

 SuffixLi/CF/CT  Report Prefix              Bundle Prefix 1
 ______________  _________________________  _________________________
  3__  55_  58_  STD21-___________________  DEP-_____________________
  3__  55_  60_  STD22-___________________  DEP-_____________________
  ___  ___  ___  _________________________  _________________________
  ___  ___  ___  _________________________  _________________________
  ___  ___  ___  _________________________  _________________________

  Command => ___________________________________________________________________
 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help        Exit  Flip  Do    Undo              Ext    <     >    Menu

Note:
The bundle prefix is optional.

This standard routine separates the spool dataset on a page basis and creates reports whose names begin with STD21- for the main departments and STD22- for the sub-departments. The report name is created by adding the prefix STD21- to the department name (Columns 55-58 in Line 3) or by adding the prefix STD22- to the sub-department name (Columns 55-60 in Line 3) found in the spool data.

Optionally, the report can be directed to a bundle with the prefix DEP-. The bundle name is created by adding the DEP- prefix to the department or sub-department name.

Note:
When the suffix and the identifier string are not on the same line, the line parameters must be used. Enter the line numbers where the identifier string and suffix are found. This must be the absolute line number as counted from the top of the page.

Using Standard Separation 3

Standard Separation 3 searches for a defined string in a defined line. If the string appears on a page, the lines of the page are analyzed regarding the defined logical expression. If not, the whole page is rejected.

From the Start Line until end of page, the lines are added to the report, if they match the defined logical expression. Lines before the Start Line are also rejected unless they are defined as Header Lines.

To define or modify the use of Standard Separation 3:

1. Enter 3 in the Standard Routine field on the "Report Definition > Separation Attributes" screen and press PF9 (Param).

   The "Report Definition > Standard Separation 3" screen appears:

   15:45:40 **** ENTIRE OUTPUT MANAGEMENT **** 2008-11-15 User ID XYZ - Report Definition >Standard Separation 3 - Report Name .............. UEX-GO___________________ Search Line .............. ___ String ............ __________________________________________________ Header Lines ......... __ Start Line ........... ___ and/or Col From/to F Value ______ ___________ _ __ __________________________________________________ ___ ___ _ __ __________________________________________________ ___ ___ ___ _ __ __________________________________________________ ___ ___ ___ _ __ __________________________________________________ ___ ___ ___ _ __ __________________________________________________ ___ ___ ___ _ __ __________________________________________________ Command => ___________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Undo Ext Menu

Fields

*STRING1*STRING2*

*STRING1%STRING2*

Note:
If most of these lines are rejected, set "Store in NOM DB=Y" (on the Report Definition > General Attributes screen). The selected lines are copied to the Entire Output Management database and the spool dataset can be deleted.

Relational Expressions

Example 3 - Salary Report

We have a salary report sorted by department number and want to extract all employees with sex = M, personnel ID number >= 6000000 and birthday <= 50/01/01 (sub-department COMP12):

Report Definition (Stand. Separation 3)

   15:45:40             **** ENTIRE OUTPUT MANAGEMENT ****            2008-11-15
  User ID XYZ       - Report Definition >Standard Separation 3 -
  Report
     Name .............. PWR-EMPL-STD3-D3_________
  Search
     Line .............. 3__
     String ............ *COMP12*__________________________________________
  Header Lines ......... 8_
  Start Line ........... 9__
     and/or Col From/to F    Value
     ______ ___________ _ __ __________________________________________________
              55_ 62_   N GE 6000000___________________________________________
       AND    65_ 65_   A EQ M_________________________________________________
       AND    67_ 74_   A LE 50/01/01__________________________________________
       ___    ___ ___   _ __ __________________________________________________
       ___    ___ ___   _ __ __________________________________________________

  Command => ___________________________________________________________________
 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help        Exit  Flip  Do    Undo              Ext               Menu

The lines 1 to 8 are taken as header lines. The filter starts in Line 9.

Example 4: Natural CATALL Report

We have a CATALL list and want to extract all lines with error number unequal to 0.

Report Definition (Stand. Separation 3)

   15:45:40             **** ENTIRE OUTPUT MANAGEMENT ****            2008-11-15
  User ID XYZ       - Report Definition >Standard Separation 3 -
  Report
     Name .............. NOM-CATALL-ERRORS________
  Search
     Line .............. 3__
     String ............ *- Error Report -*________________________________
  Header Lines ......... __
  Start Line ........... 6__
     and/or Col From/to F    Value
     ______ ___________ _ __ __________________________________________________
              16_ 19_   N NE 0_________________________________________________
       OR_    65_ 65_   N NE 0_________________________________________________
       ___    ___ ___   _ __ __________________________________________________
       ___    ___ ___   _ __ __________________________________________________
       ___    ___ ___   _ __ __________________________________________________
  Command => ___________________________________________________________________
 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help        Exit  Flip  Do    Undo              Ext               Menu

No header lines are added. The filter starts in Line 6 on pages with the string - Error Report - in Line 3.

www.softwareag.com

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

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