Attributes of a Report

This section describes the attributes which are part of a report definition:

• General Attributes

• Identification Attributes

• Distribution Attributes

• Printing Attributes

• Formatting Attributes

• Separation Attributes

• Using a Standard Separation Routine

Default values for report attributes can be set by the system administrator in Report Defaults.

General Attributes

To define the general attributes of a report:

1. Press PF2 on the Report Maintenance screen.

   The Report Definition > General Attributes screen is displayed:

   15:12:25 **** Entire Output Management **** 13/10/2015 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

2. On the Report Definition > General Attributes screen, you create a report by defining its general attributes.

   Some fields are initialized with the values specified in the Report Defaults.

3. The following special PF keys are available:

   Key	Name	Function
   PF7	Ident	Define Identification Attributes, which determine how reports are identified in the spool (not possible for reports of Type "C"). .
   PF8	Print	Define Printing Attributes.
   PF9	Dist	Define Distribution Attributes.
   PF10	Separ	Define Separation Attributes, which determine how reports are separated with user routines or standard routines (not possible for reports of Type "C").
   PF21	Ext	Switch between the display of long and short report names.

   Note:
   Some of these PF-key assignments are displayed only after you have entered a report name.

General Attributes - Fields

Identification Attributes

A report can be identified by one of the following:

• 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 CA Spool

• Report Identification for Natural

• Report Identification for UNIX/Windows Nodes

The first three are invoked by pressing PF7 (Ident) on on the Report Definition > General Attributes screen.

The others are invoked by first pressing PF7 (Ident) on on the Report Definition > General Attributes screen, and then one of the following keys on the subsequent screen:.

Report Identification for POWER

   15:27:59             **** ENTIRE OUTPUT MANAGEMENT ****            2015-10-02
  User ID XYZ       - Report Definition >POWER Identification -
  Report
     Name .............. ADABAS-DEFAULT___________ 
  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 the Report Definition > POWER Identification screen, you define how a report is identified in the POWER spool.

POWER Identification Attributes

The following attribute fields determine how a report is identified in the POWER spool.

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 data set is 22.

• Maximum length of the input data set name is 26.

• Carriage control = ASA, MACHINE or NONE.

• Data set is renamed before processing.

Report Identification for BS2000/OSD

   15:20:30             **** ENTIRE OUTPUT MANAGEMENT ****            2015-08-08
  User ID NOM      - Report Definition >BS2000/OSD Identification -
  Report
     Name .............. ADAREP-DB063___________ 
  PRINT Attributes
     Pname ............. ADARE063  or  User ID ............. ________
     or Form ........... ________
  and Files ............ 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 the Report Definition > BS2000/OSD Identification screen, you define how a report is identified in the BS2000/OSD spool.

BS2000/OSD Identification Atttributes

The following attribute fields determine how a report is identified in the BS2000/OSD spool.

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.

It is recommended that files with a fixed record length be used, because positioning within them is easier than within files with a variable record length.

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

Report Identification for JES

   16:00:46             **** ENTIRE OUTPUT MANAGEMENT ****            2015-08-08
  User ID XYZ       - Report Definition >JES Identification -
  Report
     Name .............. A-SAP-DEFAULT____________ 
  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   CA    SAP   Menu

On the Report Definition > JES Identification screen, you define how a report is identified in the JES spool.

JES Identification Attributes

Spool Data Sets

To specify the spool data sets in the selected jobs which identify the report(s)

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

  file-type can be: JL = JCL statements, SI = system input, SM = system messages, SO = system output.

  For example, enter SO 1 for the first SYSOUT data set or SO 1:2 for the first and second SYSOUT data sets.

  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 data set names, for example:

  *.STEP1.DDN1

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

  *.*.DDN1, *.DDN1 or DDN1, for example, are equivalent and they refer to a spool data set 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 data sets 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 data set criterion.

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

If spool data reside in a sequential file, enter the data set name. The data set name is preceded by "DSN=". The following special characters are supported as placeholders:

NOM DSN=<data-set-name>

The maximum length of the DSN pattern to identify the data set is 22. The maximum length of the input data set name is 26. The STEPNAME to create the spool data set 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

   14:44:29             **** ENTIRE OUTPUT MANAGEMENT ****            2015-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 the Report Definition > 3GL Identification screen, you define a report that relies on a general, user-defined 3GL interface.

3GL Interface Identification Attributes

See also 3GL Interface Maintenance in the System Administration documentation.

Report Identification for SAP Spool

   16:02:29             **** ENTIRE OUTPUT MANAGEMENT ****            2015-10-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
 

On the Report Definition > SAP-Spool Identification screen, you define how a report is identified in the SAP spool.

SAP-Spool Identification Attributes

Report Identification for CA Spool

   10:48:19             **** ENTIRE OUTPUT MANAGEMENT ****            2015-10-15
  User ID XYZ       - Report Definition >CA Spool Identification -
  Report
     Name .............. ADAREP-DEFAULT___________
 
 CA 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 the Report Definition > CA Spool Identification screen, you define how a report is identified in the CA Spool.

CA Spool Identification Attributes

The report can be identified by one of the following attributes.

You can also use wildcard notation (*). For example, to identify all files whose names begin with "ADA", enter ADA*. Or, to identify all files which were either created by the user "XYZ" or whose names begin with "ADA", enter the value ADA* for File name and the value XYZ for User ID.

Report Identification for Natural

   09:12:27             **** ENTIRE OUTPUT MANAGEMENT ****            2015-10-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 the Report Definition > Natural Identification screen, you define how a report is identified which is created by Natural or its related products like Natural Advanced Facilities or Open Print Option.

Natural Identification Attributes

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

11:37:40 ****             ENTIRE OUTPUT MANAGEMENT ****            2015-11-15
 User ID XYZ            - Report Definition >UNIX Identification -
 Report
    Name ................... Report________________

 UNIX Attributes
    Node Name .................. node_name_______ Read-binary... _
    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 the Report Definition > UNIX Identification screen, you define how a report is identified on UNIX or Windows nodes.

UNIX/Windows Identification Attributes

Identification is done using node name, path, and file pattern. ASCII files are scanned in the specified directory and matched to the file pattern specified here. These files are moved to an Entire Output Management container file and can be processed as usual. An ASCII file can contain line feeds, form feeds and tabulators; any other kind of control character will be ignored and set to blank.

Binary files can be of any format. Their format is converted to Base64 format and stored in a container file. At the time of printing, the file is re-converted to binary format.

In addition to the files residing in the file system under UNIX or Windows, the Entire Output Management identification process can process meta data. If a pair of files such as file-name.extension and file-name.extension.nomxml is found, the nomxml file is treated as a meta-data file in XML format. This format corresponds to the meta-data files processed by the Open Print Option; see Installing the Open Print Option. This requires that the Monitor has to be enabled to process XML files; see Configuration of Entire Output Management on Mainframes.

Output from a UNIX or Windows application is stored as a sequential ASCII file in a directory defined here. The monitor will move (not copy!) this file to an Entire Output Management container file and create active reports. If no report definition matches the file name pattern and no default report was found, the file cannot be processed and will be moved to a temp directory that has been defined for this node by the administrator function UNIX Defaults. File and path names are case-sensitive; node name and path have to be defined in UNIX Defaults first, as well as logon data for this node.

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 **** 2015-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

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

3. You can use PF10 to specify different Report Layout Attributes for different addresses of the report.

Distribution Attributes - 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:

   • PF4 to display a list of all users; or

   • PF5 to display a list of all distribution lists.

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

3. Enter any character in the field preceding the desired user / distribution list.

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

   When the report is produced, it is distributed to the "inbasket" of the user; in the case of a distribution list all users on the list receive the report. The user(s) can then browse and print the report.

   You can also restrict users' view of the report by defining an individual report layout; see Report Layout Attributes.

Report Layout Attributes

You can restrict a user's view of the report by defining a user-specific report layout. In this layout, you specify the parts of the layout which are to be visible to the user.

You can define a different layout for each addressee of the report. If the addressee is a distribution list, all members of the list will see the specified layout.

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

To define a layout for a user or distribution list:

1. 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 **** 2015-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

2. 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. The positions are counted from the beginning of a report line (not including ASA/machine codes).

   Field	Explanation
   From / To	For each column to be displayed, you the specify the first and last position to be displayed.
   Header Lines	Here you specify the number of lines - counting from the top of the page - which are to remain in their original format.

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

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 is displayed:

   12:05:13 **** ENTIRE OUTPUT MANAGEMENT **** 2015-11-15 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.

Printing Attributes - Fields

Additional Printers

To select additional printers:

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

   The Report Definition > Additional Printers screen is displayed.

2. You can specify up to 15 additional printers.

   Field	Explanation
   Printers	Enter the names of the logical printers on which to print the report. For a selection list, enter an asterisk (*).
   Copies	Specify how many copies of the report are to be printed on each printer.

Formatting Attributes

A report which has one of the formats text, PDF or PostScript can be converted to a common multimedia file when it is loaded. The target format is the one in which the data will be stored in Entire Output Management.

For general information on report conversion, see Converting the Report Format in the Concepts and Facilities documentation.

For this report conversion, you define formatting attributes.

To define formatting attributes:

1. Press PF11 on the Report Definition > General Attributes screen.

   The Report Definition > Formatting Attributes screen is displayed.

   On this screen, you specify the formatting attributes for the file conversion. The first three attributes are mandatory, the others are optional. The attribute fields are:

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 **** 2015-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

Separation Attributes - Fields

Defining 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 data sets. When you use such a routine, you must supply parameters which tailor further processing.

Three standard separations are available:

• Standard Separation 1

• Standard Separation 2

• Standard Separation 3

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.

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).

   The Report Definition > Standard Separation 1 screen is displayed.

2. On this screen, you define the attributes described below.

Fields

*STRING1*STRING2*

*STRING1%STRING2*

Example of Report Definition with Standard Separation 1 - 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:

   15:43:45             **** ENTIRE OUTPUT MANAGEMENT ****            2015-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

This standard routine separates the spool data set 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 data set 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 data set, for example: DEP-FINA.

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.

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).

   The Report Definition > Standard Separation 2 screen is displayed.

2. On this screen, you define the attributes described below.

Fields

*STRING1*STRING2*

*STRING1%STRING2*

Example of Report Definition with Standard Separation 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:

  19:00:10             **** ENTIRE OUTPUT MANAGEMENT ****            2015-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

This standard routine separates the spool data set 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.

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 is displayed.

2. On this screen, you define the attributes described below.

Fields

*STRING1*STRING2*

*STRING1%STRING2*

Example 1 of Report Definition with Standard Separation 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):

   15:45:40             **** ENTIRE OUTPUT MANAGEMENT ****            2015-08-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 2 of Report Definition with Standard Separation 3 - Natural CATALL Report:

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

   15:45:40             **** ENTIRE OUTPUT MANAGEMENT ****            2015-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.