Attributes of a Report

#### Search Results

Search

# Attributes of a Report

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

- General Attributes

- Identification Attributes

- Distribution Attributes

- Printing 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:

       16:19:06             **** ENTIRE OUTPUT MANAGEMENT ****            2023-01-03
       User ID XYZ       - Report Definition >General Attributes -

       Report
          Name .............. ZZ-UEX1__________________ Type .. S
          Description ....... must be suspended_________________________________
          Node name ......... ________________   Node number .. 40
          Ident. source ..... ________           Spool type ... JES2

       Keywords ............. _______________ _______________ _______________
       Master Owner ......... ________
       Store in NOM DB ...... Y

       Archive directly ..... N
       Archive type ......... _
       Retention              Report     Archive   Revive
          Number ............ 2__        10__      1__
          Unit .............. A          Y         A
          Calendar .......... ________             ________
          Action ............ A

       Command => ___________________________________________________________________

       Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
             Help  Add   Exit  Flip              Ident Print Dist  Separ       Ext               Menu

2. On this screen, you specify the general attributes of a report.

   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

Field | Explanation
--- | ---
Name | You have to enter a report name before any other data when you create a new report. This field is write-protected when you modify an existing report.
Type | The type of report:
C = Created definition | A definition created automatically during the processing of a master report or default definition or copied from another created definition. You cannot define a report as type C.
D = Default definition | A definition containing identification and processing rules used to process spool data not identified by a suitable master report definition. To have a default definition for all jobs for which no suitable master definition exists, you create a default definition with the name `*` (asterisk). For a default definition to apply to all jobs without master definition whose names begin with a certain character string, you can specify a name with asterisk notation.
M = Master report definition | A definition containing identification and processing rules used to process one or more spool files.
S = Suspended definition | A definition which is currently not to be used.
Description | Enter a short description for the report.
Node name | Specify the node name the report definition is to be associated with. This node determines the environment in which the data source for the report is to be identified. Enter an asterisk (*) to select a node name. If the local node is to be used, leave this field empty.
Ident. source | This field determines for which source Identification Attributes can be defined. Enter an asterisk (*) to select a source. The sources available for selection vary depending on the node used.
Keywords | You can enter one or more keywords which will later help you select reports. For a selection list of existing keywords, you enter an asterisk (*) or a character string followed by an asterisk.
Master Owner | The user ID specified here is used to initialize the Master Owner field in the General Attributes of the resulting active report. It determines who may delete the active report. The monitor also takes this user ID to submit print jobs for reports to be scheduled for automatic printing. This field is initialized with the ID of the user who creates the report. If you wish, you can specify a different user ID.
Store In NOM DB | Enter "Y" to take report contents from the spool and store them in the Entire Output Management active-data file for later viewing or archiving. If you do not specify a storage location, the report stays in the spool.
Archive directly - Y/N/I | A report can be archived from the database or directly from the spool. Possible values: Enter "Y" to archive the report automatically after creating it and when processing is completed. The contents of an active report are then no longer available online. Enter "N" if you do not want automatic archiving. Enter "I" for immediate archiving. The active report is archived the next time the archive job runs, but it is still available for online viewing until it reaches its expiration date. After this, the active report only exists in the archive data set and has to be revived before it can be viewed or printed again.
Archive type | If the report is to be archived to a user-defined archive, enter the number of the archive type. Enter an asterisk (*) to select an archive type. Enter "0" or leave this field empty to archive the report on a standard Entire Output Management archive file.
Retention
Report | The report retention period determines how long the active report is available online for browsing and printing. If this retention period expires, the active report is either marked for archiving or deleted (see the field "Action" below).
Number | Enter the number of working days, absolute days, weeks or months the report is to be available online.
Unit | W = working days. A = absolute days. V = weeks. M = months. G = generations (instances of the active report). If you select "working days", you also have to select a calendar which distinguishes between working and non-working days.
Calendar | Select a calendar, if "working days" is the unit for the retention period. For more information on calendars, see Calendars in the System Administration documentation.
Action | Enter "A" to archive the report when the retention period expires. Enter "P" to purge (delete) the report when the retention period expires. When an active report is archived, it is no longer available online.
Archive | Enter the length of time the active report is to be kept in the archive. When this period expires, the active report is deleted from the archive data set. An active report can be archived no matter where it is stored.
Number | Enter the number of days/weeks/months/years the active report is to be kept in the archive.
Unit | D = days, W = weeks, M = months, Y = years.
Revive | Enter the length of time a revived active report is to be available online for browsing and printing. When this period expires, this "copy" of the archived report is deleted automatically. Enter values for Number, Unit and Calendar fields as described for Report above.

## Identification Attributes

A report can be identified by one of the following:

- Report Identification for BS2000

- Report Identification for JES

- Report Identification for 3GL Interface

- Report Identification for CA Spool

- Report Identification for Natural

- Report Identification for UNIX/Windows Nodes

Depending on the setting of the general attribute Ident. source, one of these is invoked by pressing PF7 (Ident) on on the Report Definition > General Attributes screen.

### Report Identification for BS2000

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

#### BS2000 Identification Attributes

The following attributes determine how a job in the BS2000 spool is identified by the report definition.

Field | Explanation
--- | ---
Identifying attributes | You have to enter a value for at least one of these three attributes. A job is considered identified if it matches at least one of the specified attributes.
Pname | If you want to identify the job by the `PNAME` option of the BS2000 print command (`/Print ...,PNAME=ADAREP`), enter the PNAME here. You can use asterisk notation (*) to for the job name. For example, to identify all jobs whose names begin with "ADA", you enter `ADA*`.
User ID | If you want to identify the job by the BS2000 user ID under which the print command was entered, enter this user ID here (for example: `PROD01`).
Form | If you want to identify the job by its `FORM` parameter, enter the form here.
Files | Use these fields to select the files whose contents are to be used as print data for the active report. For an active report to be created, at least one file of the job has to match these filter criteria. You specify a completely or partially qualified file name which identifies the report. A report definition is considered identified if, in addition to one of the identifying attributes, one of the files from the file list matches. The following special characters can be used to create a file name pattern: ? (question mark) or _ (underscore) to indicate a single position not to be checked. * (asterisk) to indicate any number of positions not to be checked. For example, if you enter `ADA*` in the Pname field and `*L.ADAREP.*` in this field, all files are identified whose `PNAME` begins with `ADA` and whose file name contains the string `L.ADAREP.`.
Code page | By default, Entire Output Management uses the code page defined for the respective node and applies it to all report definitions associated with that node. If you want to use a different code page for a particular report, select the desired code page here. If you do not want to use a report-specific page, set this field to blanks. For the definition of code pages, see Default Code Pages.

#### Carriage Control Characters

The `RECFORM` parameter of the file allows you to determine whether the print file contains carriage control characters and which ones. It is specified as follows:

`RECFORM=(x,y)`

where:

- `x` = `F` for fixed record length, or `V` for variable record length.

- `y` determines the type of carriage control characters:

  - `A` = ASA carriage control characters,

  - `M` = machine-code carriage control characters,

  - `N` = 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.

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

### Report Identification for JES

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

#### JES Identification Attributes

The following attributes determine how a job in the JES spool is identified by the report definition.

Field | Explanation
--- | ---
Identifying attributes | You have to enter a value for at least one of these four attributes. A job is considered identified if it matches at least one of the specified attributes.
Job name | To identify the job by its name, enter a job name here. You can use asterisk notation (*) for the job name. For example, to identify all jobs whose names begin with "IEE", you enter `IEE*`.
Destination | To identify the job by the `Destination` parameter, enter the destination here.
Writer | To identify the job by the `External Writer` parameter, enter the writer name. This links the report to the spool file assigned to this writer name. If you use an external writer similar to the report name, it makes identification easier.
Form | To identify the job by the `FORMS` parameter, enter the form here.
Data Sets | Use these fields to select the files whose contents are to be used as print data for the active report. For an active report to be created, at least one file of the job has to match these filter criteria. You can specify which spool files (data sets) in the identified jobs are to be assigned to the report. See Spool Files and Sequential Files below.
Code page | By default, Entire Output Management uses the code page defined for the respective node and applies it to all report definitions associated with that node. If you want to use a different code page for a particular report, select the desired code page here. If you do not want to use a report-specific page, set this field to blanks. For the definition of code pages, see Default Code Pages.

#### Spool Files

To specify the spool files in the selected jobs, you use one of the following three possibilities:

1. Specify: `file-type file-sequence-number`

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

   Examples:

   - Specify `SO 1` for the first SYSOUT file.

   - Specify `SO 1:4` for the first to fourth SYSOUT files.

2. Specify a list of full DDNAME qualifiers in the format:

   `proc-name.step-name.ddname`

   `proc-name` and `step-name` are not mandatory, and if omitted are assumed to be * (any). You can use an asterisk (*) to enter selection criteria for the file names.

   Examples:

   - `PROC1.STEP1.DDN1` is a full qualifier.

   - `*.STEP1.DDN1` refers to a spool file with `STEPNAME=STEP1`, `DDNAME=DDN1` and any procedure name.

   - `*.*.DDN1` or `*.DDN1` or `DDN1` are equivalent and refer to a spool file with `DDNAME=DDN1` in any step name or procedure name in the job.

3. Specify `TYPE=AL` to create an active report containing all System Message and SYSOUT files 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 file criterion.

Note
If more than one JES2 spool file of a job is to be processed by Entire Output Management, the job's spool files 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, for example, by a program via Entire System Server functions, 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

If the report data reside in a sequential file, enter the file name in the form `DSN=file-name`.

The following special characters can be used to create a file-name pattern:

- ? (question mark) or _ (underscore) to indicate a single position not to be checked.

- * (asterisk) to indicate any number of positions not to be checked.

Example: `DSN=NATURAL.*EMPL_YEE*`

Note
The 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

`data-set-name` may have a maximum length of 22 characters.

The `STEPNAME` to create the spool file 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

On the Report Definition > 3GL Identification screen, you define a report that relies on a general, user-defined 3GL interface.

3GL Interface Identification Attributes | Explanation
--- | ---
3GL Interface nnn Attributes | (Identifying Attributes) In this group, you can enter up to 4 attributes to be used as selection criteria for report definitions. You have to specify at least one attribute. The Identifying Attributes of the 3GL Interface Defaults determine which attributes are displayed here and which attribute can be entered with an asterisk (*).
and | (File Identification) This attribute can be used as an additional selection criterion (secondary selection). In this case, the File Identification of the 3GL Interface Defaults determines which attribute can be entered here.

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

### Report Identification for CA Spool

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

#### CA Spool Identification Attributes

These attributes determine how a job in the CA spool is identified by the report definition. A job can be identified by one of the following four attributes. You have to specify a value for at least one of these fields. A job is considered identified if it matches at least one of the specified attributes.

Field | Explanation
--- | ---
File name | To identify the job by the file name, enter the file name here as it appears on the CA screen. The file name can contain the user ID of the file creator, the job name or a parameter entered in the `OWN` field in an `OPEN` request. See the CA Spool documentation for details.
User ID | To identify the job by the ID of the user who created the list, enter the user ID here (`UID` field in `OPEN` request).
Writer | To identify the job by the `Writer` parameter, enter the writer name here (`WTR` field in `OPEN` request).
Form | To identify the job by the `FORM` parameter, enter the form here (`FOR` field in `OPEN` request).

You can use asterisk notation (*) for the file name. 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 `ADA*` for File name and`XYZ` for User ID.

### Report Identification for Natural

       09:12:27             **** ENTIRE OUTPUT MANAGEMENT ****            2019-11-11
      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.

#### Natural Identification Attributes

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

Field | Explanation
--- | ---
Natural Attributes
*USER | Enter a Natural user ID or a Natural library ID (but not both).
*LIBRARY ID
Printer Profile | Enter the name as defined in the `PROFILE` option of the `DEFINE PRINTER` statement.
Secondary identification attributes (optional)
*PROGRAM | Enter the name of a Natural program.
FORM | Enter the form as defined in the `FORMS` option of the `DEFINE PRINTER` statement.
NAME | Enter the name as defined in the `NAME` option of the `DEFINE PRINTER` statement.

A first selection is made by the primary identification attributes (Natural Attributes), considerably reducing the number of definitions. You have to specify at least one of these. 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.

You can use asterisk notation (*) for all attributes, except Printer Profile. For example, to select all programs executed by users whose IDs begin with "MRS", you specify `MRS*` as the user ID. Or, if you enter the user ID value `ABC` and the printer profile value `NOMPRT`, all print files are identified which were created either by the user "ABC" or with the printer profile "NOMPRT".

### Report Identification for UNIX/Windows Nodes

    11:37:40 ****             ENTIRE OUTPUT MANAGEMENT ****            2022-05-05
     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

The identification is done using the node name and path, and a file-name pattern. Entire Output Management will process any file found in this path, if it matches one of the specified file names or file-name patterns. Directories are not processed (no recursion).

For every matching file, an active report will be created. For this purpose, the file contents will be copied to the Entire Output Management container file. Then the file will be deleted from the path.

For any file not matching one of the criteria, Entire Output Management checks if an appropriate default report exists. If none exists, the file cannot be processed and will be moved to a temporary directory defined for this node in the Node Definitions instead.

ASCII files 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. They are stored in the container file in Base64 format. At the time of printing, they are re-converted to binary format.

In addition to the identified files, associated meta-data files can be processed. 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.

Node names, path names and file names are case-sensitive. Node names and paths have to be defined in the Node Definitions first.

Field | Explanation
--- | ---
Node name | Enter a node name.
Path | Use PF11 to select a path. Path definitions must not contain any wildcard characters. If the path definition in Node Definitions is changed, the definition in this field will not change automatically. In this case, use PF11 to select a new path. This will ensure that an "old" report definition still works, even if the defaults change.
Files | Enter up to 10 files, or file-name patterns, without path entries. File extensions are treated as part of the file name. In a file-name pattern, you use an asterisk (*) as placeholder for several characters and a question mark (?) for a single character in the file name.
Read binary | T = The report will be created from a UNIX file as a text file. A = The report will be created from a UNIX file already containing ASA control characters as a text file. B = The report will be created from a UNIX file as a binary document.

## 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 ****            2022-05-05
         User ID XYZ      - Report Definition >Distribution Attributes -
         Report
            Name .............. FVSE-DB__________________

         Distribution via NOM
            User/List ......... DC-GROUP ________ ________ ________ ________
                                ________ ________ ________ ________ ________

         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

Field | Explanation
--- | ---
User/List | Enter up to 10 user IDs or distribution list names. When the report is created, all users connected to user IDs or distribution lists entered here can access this report, and can browse, print etc. A user ID selection window or a distribution list selection window can be opened by entering an asterisk * (or a selection criterion ending in an asterisk) in this field. For more information, see the section Selecting Users to Receive a Report. AUTOPRNT To automatically print a report with a special layout, you have to define an Entire Output Management user ID `AUTOPRNT`. Then add `AUTOPRNT` to the "Distribution via NOM" list of users and give it the required layout, which will then be applied to the printed report. However the report will not actually be distributed to the user `AUTOPRNT`, so it is not possible to log on as `AUTOPRNT` and view any active reports.

### Selecting Users to Receive a Report

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

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

   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` folder of the user; in the case of a distribution list all users on the list receive the report in their `#Inbasket` folders. The user(s) can then browse and print the report.

### Report Layout Attributes

Note
You cannot combine report layout attributes with separation attributes. You can only use either one or the other.

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.

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 ****            2022-05-05
         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 ****            2022-06-06
         User ID XYZ       - Report Definition >Printing Attributes -

         Report
            Name .............. XYZ-XML__________________
         Hold Logic ........... _

         Printers        (1-5). ________ ________ ________ ________ ________
         Copies          (1-5). ___      ___      ___      ___      ___
         with Sep. Pages (1-5). X        X        X        X        X
         Separator Pages
            Start ............. ________
            End ............... ________
            Copies ............ ___
            Length ............ ___

         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

Field | Explanation
--- | ---
Hold Logic | This field controls how the report is queued for printing. Enter one of the following values: H (Hold) - The report is held in the printout queue until released manually. C (Confirm) - The report is held in the printout queue until manually confirmed by all recipients. A message requesting printing confirmation is displayed to each user in the distribution list. When all users have confirmed, the report is automatically released for printing. R (Release) - The report is printed immediately.
Printers | Enter the names of up to 5 logical printers on which to print the report when it is created. For a selection list, enter an asterisk (*). To specify more than 5 printers, use PF11; see Additional Printers below.
Copies | Enter the number of copies of the report to be printed on each printer.
with Sep. Pages | Determines whether or not the Separator Pages (see below) are printed on this printer. By default, they are printed on all printers specified, as indicated by an "X". If this is not desired, remove the "X" for an individual printer.
Separator Pages | Start | Enter the name of the separator page to be printed at the beginning of the report.
End | Enter the name of the separator page to be printed at the end of the report.
Copies | Specify how many times each separator page is to be printed.
Length | Enter a separator line length, if your separator line length is greater than your report length. The default length is the report length.
See Separator Pages for further information. To edit a separator page, position the cursor on the Start or End field, and press PF10 (Edit).
Jobcards or Additional Parameters | Enter the job cards for printing with batch jobs. The following substitution variables can be used: `§USER`, `§REPORT`, `§JOBNAME`. If you leave this field blank, the Jobcards specifications from the logical printer definition are used.

### 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. The printing attributes Printers, Copies and with Sep. Pages are the same as described above.

## Separation Attributes

Note
You cannot combine separation attributes with report layout attributes. You can only use either one or the other.

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 ****            2022-06-06
        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

Key | Name | Function
--- | --- | ---
PF9 | Param | Define parameters for the user routine or standard routine.
PF10 | Edit | Edit the Natural subprogram containing the user routine.
PF11 | Trace | Trace processing of a user routine. See Tracing Report Processing.

### Separation Attributes - Fields

Field | Explanation
--- | ---
Create Definition | When active reports are dynamically created during a standard separation or user separation process, the corresponding report definitions are usually created automatically. To suppress automatic creation, enter an "N" here. This is useful when creating unique active reports.
Standard Routine | Enter "1", "2" or "3" to indicate which standard routine is to be used. For more information on the standard routines, see Using a Standard Separation Routine.
User Routine | If a user routine is to be used, specify it in the fields below. The spool file records can be filtered on a record-to-record basis by a supplied user routine. With various action codes, the user routine can control the separation process and positioning within the output and can determine the contents of the created reports. For more information, see User Separation Routines in the System Administration documentation.
Natural Member | Enter the name of the Natural subprogram containing the user routine. Press PF10 (Edit) to edit the subprogram.
Natural Library | Enter the name of the Natural library name which contains the subprogram. A library name beginning with `SYS` must not be specified, except `SYSNOMU`.
3GL | If the user routine is written in a language other than Natural, enter its name here. This user routine is invoked by a `CALL` statement.

If no user routine or standard routine is specified, the whole identified spool file is contained in the report.

### 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 files. When you use such a routine, you have to 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. This separation 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.

#### Attributes of Standard Separation 1

Field | Explanation
--- | ---
Search
Line | Enter the line number, starting from the top of the page, where the string must appear. To determine this line number, you must also count lines containing only carriage control characters. If you do not specify Search Line, then the search string can appear anywhere on the page.
String | Enter the string to be searched for. If this string appears on a page, the 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. You can specify a search pattern like:
    *STRING1*STRING2*
or
    *STRING1%STRING2*
where * stands for any string and % stands for any character. You must bracket the string with * (for example: *string*) if it can occur anywhere within a line.
Suffix
Line | Enter the line number, starting from the top of the page, where the report suffix appears. To determine this line number, you must also count lines containing only carriage control characters. If you do not specify Suffix Line, Entire Output Management assumes that the suffix is located in the Search Line.
Start Column | Enter the position in the line where the report suffix starts (value from 1 to 251). To determine position, you must also count carriage control codes and/or table reference characters.
End Column | Enter the position in the line where the report suffix ends (value from 1 to 251). To determine position, you must also count carriage control codes and/or table reference characters.
Prefix
Reports | Enter the report prefix which is concatenated to the suffix to determine the report name. The suffix is concatenated suppressing leading and trailing blanks.
Bundles | (optional) Enter the bundle prefix which is concatenated to the suffix to determine the bundle name. The suffix is concatenated suppressing leading and trailing blanks. Up to 5 bundles can be specified. To generate bundles with fixed names, fill in this field completely. No suffix is then appended.

#### Example of 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 ****            2024-06-06
      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 file 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 file 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 prefix `DEP-` to the suffix found in the spool file, 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.

### Standard Separation 2

Standard Separation 2 separates spool data into several reports depending on up to 5 break conditions. It 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.

#### Attributes of Standard Separation 2

Field | Explanation
--- | ---
Search
Line | Same as described for Standard Separation 1.
String | Enter the string to be searched for. If this string appears on a page, the suffix is evaluated (at break of the suffix value, a new report is opened). If no string is found, the page is added to the currently opened reports. If no report is opened, the page is rejected. You can specify a search pattern like:
    *STRING1*STRING2*
or
    *STRING1%STRING2*
where * stands for any string and % stands for any character.
Suffix | You can define parameters for up to 5 suffixes in the following three fields.
Li | Enter the line number, starting from the top of the page, where the report suffix appears. To determine this line number, you must also count lines containing only carriage control characters. If you do not specify Suffix Li(ne), Entire Output Management assumes that the suffix is located in the Search Line.
CF | (column-from) Enter the position in the line where the report suffix starts (value from 1 to 251). To determine position, you must also count carriage control codes and/or table reference characters.
CT | (column-to) Enter the position in the line where the report suffix ends (value from 1 to 251). To determine position, you must also count carriage control codes and/or table reference characters.
Report Prefix | Enter the report prefix which is concatenated to the suffix to determine the report name. The suffix is concatenated suppressing leading and trailing blanks.
Bundle Prefix | (optional) Enter the bundle prefix which is concatenated to the suffix to determine the bundle name. The suffix is concatenated suppressing leading and trailing blanks. Up to 5 bundle prefixes can be specified for each suffix. To generate bundles with fixed names, fill in this field completely . No suffix is then appended. If long report and bundles names are displayed, only 1 bundle prefix is displayed for each suffix. To process the other bundle prefixes, press PF10 or PF11. The number of the currently displayed prefix appears after the title Bundle Prefix.

#### Example of 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 ****            2024-06-06
     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 file 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.

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

#### Attributes of Standard Separation 3

Feld | Erklärung
--- | ---
Search
Line | Enter the line number, starting from the top of the page, where the string must appear. To determine this line number, you must also count lines containing only carriage control characters.
String | Enter the string to be searched for. If this string appears on a page, the page is processed. If no string is found, the page is rejected. You can specify a search pattern like:
    *STRING1*STRING2*
or
    *STRING1%STRING2*
where * stands for any string and % stands for any character.
Header Lines | Enter the number of lines (0-20), starting from the top of the page, which are used as header lines. To determine this line number, you must also count lines containing only carriage control. If Header Lines = 0, no header lines are added. Otherwise, if there is on a page at least one line, which matches the separation's logical expression, the header lines are added.
Start Line | Enter the line, starting from the top of the page, from which filter processing starts. The lines preceding the Start Line are automatically excluded from the report, unless they are defined as Header Lines. To determine this line number, you must also count lines containing only carriage control characters.
and/or | Concatenates two conditions. Possible values: AND - concatenates with logical AND. OR - concatenates with logical OR. (blank) - concatenates the same variable with OR=. For an example, see below.
Col From/to | Indicates the position of the operand. Enter positions in column from which to start and at which to end filter processing (value from 1 to 251).
F | Format. Variable type (first column) and relational expression (second column). Possible variable types: A = Alphanumeric. M = Mask as described in the Natural Reference documentation. N = Numeric. Possible relational expressions:
EQ, = | Equal to
GE, >= | Greater than or equal to
GT, > | Greater than
LE, <= | Less than or equal to
LT, < | Less than
NE, ! | Not equal to
Value | Enter a numeric or alphanumeric value or a mask definition.

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 file can be deleted.

#### Example 1 of 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 ****            2022-06-06
      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 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 ****            2022-06-06
      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.

### On this page

- General Attributes
- Identification Attributes
- Distribution Attributes
- Printing Attributes
- Separation Attributes
- Using a Standard Separation Routine