Version 4.6.2	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

Adabas Review may be used in batch processing mode to monitor resource usage for applications and databases by extracting data fields from the command log files generated by Adabas or Adabas Review.

Note:
Reports can also be started automatically when the Review system starts. For more information, read Running Autostarted Reports and Autostarted Reports.

To produce batch reports, the Adabas Review processor requires parameter statements and job control to run against the command log records. Report parameter statements can be manually created or they can be generated using the GENCARD command and subsequently edited, if required. Once the report statements are set up, the user submits the job stream for batch execution.

This part of the documentation describes how to use the GENCARD command to generate batch parameter statements. It also describes the statements required and presents guidelines for creating batch parameter statements without using the GENCARD command. It covers the following topics:

• Generating Batch Report Parameters

• Using Batch Report Statements

• Batch Processor Job Control Requirements

Generating Batch Report Parameters

The GENCARD command creates batch report parameter statements from field and report processing information you provide through the Edit Report (ER) function. The GENCARD command also uses the target database information it obtains from the List Target Definitions (LT) function.

By using the GENCARD command to generate batch report parameters, you can run any online report in batch mode.

To use the GENCARD command:

1. Access the Edit Report (ER) function.

2. Create the report definition in the same way that you create an online report definition; then save it by pressing PF5.

   For more information, read Maintaining Report Definitions.

3. Enter the command GENCARD or GC on the command line.

   The Generate Report Definition Cards window appears as shown in the example below:

   Generate Report Definition Cards Please enter the following information for generation File/DDNAME for output .... RVUCARD Report Definition Prefix .. ________________________________

4. On the line labeled "File/DDNAME for output", type the file or DD name for the sequential file where the batch report parameter statements are to be written.

   The default name RVUCARD appears on this line.

5. On the line labeled Report Definition Prefix, type the report name and press ENTER.

   To generate batch parameters for a series of reports, you may use an asterisk for "wildcard" prefixing and suffixing.

   For example, to generate batch parameters for all reports with names beginning with "T", enter T* on the Report Definition Prefix line. For all reports with names ending with "test", enter *test.

   You receive a message that the generation process has been started; however, you do not receive a message when the process is complete.

6. To ensure that the batch parameters were generated, examine the sequential data set where the parameters were to be written.

This section covers the following topics:

• Sample Statements

Sample Statements

The following is an example of the batch statements generated by the GENCARD command for a sample report:

INPUT   FILETYPE=SEQUENTIAL,      
        BUFFERS-4K=124,          
        BUFFERS-32K=15,
        FILES=1,
        REVIEW-COMMANDS=NO
REPORT  TYPE=SUMMARY,
        TITLE='GENERATE EXAMPLE',
        PROGRAM=RD-00055,
        RESTART=Y,
        HISTORY-INTERVAL=15,
        MAXSTORE=8
DISPLAY SEQUENCE,CMD,RSP,TPUSERID,NATAPPL,NATPROG
SUM     IOS,CMDRESP,ADADURA
AVERAGE IOS,CMDRESP,ADADURA
PERCENT IOS,CMDRESP,ADADURA
INCLUDE RSP-(0,3,17,148),JOBNAME=(JOB1*-JOB3*)
COPY    FILETYPE=ADABAS,HUB=221,FNR=002,SVC=237
LOG     DSN=RVLOG,
        EXIT=LOGEX1,
        LOGIO=YES

For a more detailed description of these statements, refer to the section Using Batch Report Statements.

Using Batch Report Statements

This section describes the syntax to be used if you are entering the batch statements manually or are making changes to statements generated by the GENCARD command.

Here is a summary table of the batch statements used by the Adabas Review processor. For information about the data fields used with the statements, refer to the Field Reference.

Parameter Statement Syntax

A parameter statement consists of a statement name followed by at least one blank and one or more optional (positional or keyword) parameters separated by commas:

The following syntax rules pertain to parameter statements:

• Statements may be entered in positions 1-71.

• At least one blank must separate the statement name and the first parameter.

• Multiple parameters must be separated by commas.

• Blanks are not permitted within a parameter entry, except when enclosed within apostrophes.

• A statement with multiple parameters may be continued by ending the line with a comma followed by a blank, and entering the next parameter on the next line beginning in any position between 1-71.

• Comment lines may be inserted by entering an asterisk in position 1. Comment lines may also be inserted following the blank that ends the statement.

• Positional Parameters
• Keyword Parameters

Positional Parameters

Positional parameters specify the data fields to be summarized and/or displayed as part of the Adabas Review report.

A positional parameter is a single value, usually an Adabas command log field name. Refer to the Field Reference for information about individual data fields.

Keyword Parameters

Keyword parameters either specify input record selection criteria or define specific parameter statement options. A keyword parameter consists of a keyword name, a keyword separator, and a parameter value.

Keyword names vary depending on the particular parameter statement. Field names referencing Adabas data fields are used as keyword names when specifying input record selection criteria. When defining a specific parameter statement option, specific keyword reserved words are used as keyword names.

Valid keyword separators include:

 =, <,>, and ¬ 

These relational symbols (equal to, less than, greater than, and not equal to, respectively) are used to define selection criteria for Adabas Review report processing.

Parameter values are numeric, alphanumeric, or hexadecimal in format. Note that a hexadecimal value must be enclosed in apostrophes and be preceded by an "X". A list of values is identified by enclosing the list in parentheses with the values separated by commas. For a range of values, a hyphen is used to separate the low and high values of the range.

AVERAGE Statement

The AVERAGE statement specifies the data fields for which average values are to be calculated for an Adabas Review summary report.

The AVERAGE statement is applicable to summary reports only. Average values are calculated only for the valid data fields specified in this statement. Average values are summarized and printed on the summary report at each control break defined by the parameter statement for all data fields for which average values have been calculated. Average values are printed to one more rounded decimal place than the field data being averaged.

Example:

Print average values for the Adabas command log fields ASSOIO, WORKIO, and DATAIO on the summary report.

AVERAGE ASSOIO,WORKIO,DATAIO

COPY Statement

where DBID , FILE , and SVC represent the Adabas Review repository.

The COPY statement specifies that input detail records to be copied to an Adabas file.

The keyword parameter FILETYPE specifies whether the data is to be copied to a sequential data set or to Adabas. The following functions can be performed using this statement:

• Copy detail records to a sequential data set.
  The user can select subsets of detailed log records and copy them to different sequential data sets. These data sets can then be used as future input to Adabas Review.

• Copy detailed or summary data to Adabas.
  The user can write specified information back into the Adabas Review repository where it can be viewed using either the online history functions or Adabas applications written by the user.

The physical command log may be created with less overhead for the Adabas nucleus by using this function with the Adabas Review processor running interactively.

The keyword parameter LIMIT specifies the maximum number of records to be copied. The default is to copy all records.

Examples:

1. Copy all input detail records satisfying the selection criteria specified on the INCLUDE statement to the sequential data set RVUCOPnn, where nn is incremented sequentially beginning with 01 for the first copied file.

   REPORT TYPE=DETAIL
   INCLUDE  ...
   DISPLAY  ...
   COPY FILETYPE=SEQUENTIAL

2. Copy all summary data records to the Adabas Review repository.

   REPORT TYPE=SUMMARY
   DISPLAY  ...
   COPY FILETYPE=ADABAS,DBID=133,FILE=3

COST Statement

The COST statement, which is used only in summary reports, specifies the factors to be used in calculating resource costs and the data fields to which the cost factors are to be applied. The costs calculated for the specified data fields are automatically printed on the output report. If costs are calculated for more than one data field, a combined total cost column is printed as the column to the far right on the summary report. The special reserved word FIXED specifies that a fixed cost is to be applied to each input detail record.

Valid arithmetic operators are: *, +, -, and @. The first three operators specify that the value of the designated data field is to be multiplied by the indicated cost factor (*), that a constant factor is to be added to the value of the data field (+), or that a constant value is to be subtracted from the value of the data field (-). The remaining operator (@) is used only with FIXED to specify that a fixed cost is to be applied to each input detail record.

Cost factors can be positive or negative numeric values containing up to four decimal places. Negative values can be used only with the operators * and @. Costs are calculated only for those data fields for which cost factors are specified.

Examples:

1. Calculate costs by multiplying the CMDRESP field by .0025 and multiplying the total IO count by 2.50.

   COST CMDRESP*.0025,IO*2.50

2. Calculate costs by applying a fixed cost of 5.00 to each input detail record.

   COST FIXED@5.00

3. Calculate costs by adding 1.5 to the value of the ASSOIO field, multiplying the DATAIO field by a negative 1.25, multiplying the WORKIO field by a positive 2.

   COST ASSOIO+1.5,DATAIO*-1.25,WORKIO*

DISPLAY Statement

The DISPLAY statement defines the control break fields for Review summary reports. Data is summarized at each control break specified in this statement for all data fields for which calculations have been performed.

One DISPLAY statement must be specified with at least one field for a summary report.

The DISPLAY statement is also used to specify the data fields to be printed on Review detailed reports.

Examples:

1. Print data summarized by Adabas COMMAND within file number (FNR) within JOBNAME on the summary report.

   DISPLAY JOBNAME,FNR,COMMAND

2. Print the data fields SEQUENCE, DATE, USERID, and CMDRESP on the detailed report in the order specified.

   DISPLAY SEQUENCE,DATE,USERID,CMDRESP

ENV Statement

Note:
Adabas Review makes no claim to be able to recover or report actual CPU time.

If you are not satisfied with the values you receive in the Adabas Review CMDRESP field, you can use the ENV control statement to adjust the values.

"nnnnn.nnnn" is the factor to be multiplied by the value reported in the Adabas Review field CMDRESP to adjust it to the total Adabas nucleus session CPU time reported by the operating system. All digits must be specified. The default value is 1.0000; the maximum value is 99999.9999.

To implement the ENV control statement:

1. Run your Adabas nucleus with an autostarted Review report that shows the total of all command response time for the nucleus session (CMDRESP field).

2. When the database is stopped, examine the output report and note the total CMDRESP value as reported by Adabas Review.

3. Obtain the total CPU time used by the Adabas nucleus session as reported by the operating system.

4. Compare the two values and determine the relationship between them.

5. For the next Adabas nucleus session, you can adjust the Adabas Review value to more closely approximate the operating system value by inserting the ENV control statement into the RVUAUT1/2 or RVUPARM after the INPUT statement and before the first REPORT statement.

Examples:

1. Review CMDRESP=100.0000; CPU time reported by the operating system=50.0000.

   The ratio between the two values is 2:1 where the Adabas Review CMDRESP field value is two times the Adabas nucleus session CPU time reported by the operating system.

   To adjust this for the next Adabas session, set the ENV control statement parameter ENV-FACTOR to 0.5000 so that Review divides the CMDRESP value by 2.

   The RVUAUT statements may be similar to the following:

   INPUT   FILETYPE=SEQUENTIAL,      
         BUFFERS-4K=124,          
         BUFFERS-32K=15,
         FILES=1,
         REVIEW-COMMANDS=YES
   ENV ENV-FACTOR=0.5000
   REPORT TYPE=SUMMARY,
          TITLE='TOTAL CMDRESP',
          PROGRAM=RD-00089,
          RESTART=Y,
          MAXSTORE=8
          TARGET=00nnn
   DISPLAY DBNAME
   SUM COMMANDS,IOS,CMDRESP
   

2. Review CMDRESP=25.0000; CPU time reported by the operating system=100.0000.

   The ratio between the two values is 1:4 where the Adabas Review CMDRESP field value is one quarter of the Adabas nucleus session CPU time reported by the operating system.

   To adjust this for the next Adabas session, set the ENV control statement parameter ENV-FACTOR to 4.0000 so that Review multiplies the CMDRESP value by 4.

ENVIRONMENT Statement

The ENVIRONMENT statement specifies the identification number of the CPU or database from which the Adabas command log originated. The ENVIRONMENT statement should only be used with the COPY statement (see COPY Statement for more information).

EXCLUDE Statement

The EXCLUDE parameter statement defines specific input detail records that are to be excluded from processing, based on the values of specified fields.

Note:
EXCLUDE parameter statements with multiple field names have different logical meanings if the field names are entered as multiple EXCLUDE statements rather than as a single continuous statement. If entered as a single statement, the Boolean operator AND is implied; if entered as multiple statements, the Boolean operator OR is implied.

Relational symbols specify the test that should be conducted on a field value. Input detail records are excluded if the value of the designated data field passes the test specified by the relational symbol. For example, if the specified field is equal to, less than, greater than, or not equal to the value indicated in the parameter statement, it is excluded. Valid relational symbols that can be specified are:

Note:
The symbol for "not equal to" varies; it may be either "^" or "¬". The hexadecimal equivalent is the same on all machines.

Parameter values may be in numeric, alphanumeric, or hexadecimal format.

• Hexadecimal values must be enclosed in apostrophes and preceded by an "X". In addition, hexadecimal values should be padded with blanks (X'40') to ensure that every available field byte is specified. The blank padding can be specified either at the beginning or the end of the value specification. For example, to exclude all input detail records with a hexadecimal 8-byte NATAPPL field value of "ABC", enter the statement as:

  EXCLUDE  NATAPPL=(X'C1C2C34040404040')
  

• Alphanumeric fields may use an asterisk (*) for wildcard prefixing and suffixing. For example, to exclude all job names beginning with "A" and all job names ending with "TEST", enter the statement as:

  EXCLUDE  JOBNAME=(A*,*TEST)

To specify a list of values, enclose the values in parentheses an separate them with commas. For example, the following specification excludes input detail records with JOBNAME field values equal to "AAAAAAAA", "BBBBBBBB", or "CCCCCCCC":

EXCLUDE JOBNAME=(AAAAAAAA,BBBBBBBB,CCCCCCCC)

To specify a range of values, the low and high values of the range should be separated by a hyphen. For example, the following specification excludes input detail records with NATAPPL field values in the range from "AA" through "X" or with the value "AABC":

EXCLUDE NATAPPL=(AA-X,AABC)

If one of the values itself contains a hyphen, enclose it in quotes. For example, the following specification excludes input detail records with NATAPPL field value "AA-X" or with the value "AABC":

EXCLUDE NATAPPL=('AA-X',AABC)

Examples

1. The following example excludes input detail records from processing if the value of the SEQUENCE field is less than 100 AND the value of the JOBNAME field is equal to "AAAAAAAA" or is within the range "XXXXXXXX" through "ZZZZZZZZ".

   EXCLUDE
   SEQUENCE<100,JOBNAME=(AAAAAAAA,XXXXXXXX-ZZZZZZZZ)

2. The following example excludes input detail records from processing if the value of the SEQUENCE field is less than 100 OR the value of the JOBNAME field is equal to "AAAAAAAA" or is within the range "XXXXXXXX" through "ZZZZZZZZ".

   EXCLUDE SEQUENCE<100
   EXCLUDE JOBNAME=(AAAAAAAA,XXXXXXXX-ZZZZZZZZ)

INCLUDE Statement

The INCLUDE parameter statement defines specific input detail records to be included in processing, based on the values of specified fields. An individual field name may only be specified once in an INCLUDE statement. For example, the following INCLUDE statement is invalid because it specifies the SEQUENCE field twice:

INCLUDE  SEQUENCE>100,SEQUENCE=3 

Note:
INCLUDE parameter statements with multiple field names have different logical meanings if the field names are entered as multiple INCLUDE statements rather than as a single continuous statement. If entered as a single statement, the Boolean operator AND is implied; if entered as multiple statements, the Boolean operator OR is implied.

Relational symbols specify the test that should be conducted on a field value. Input detail records are included if the value of the designated data field passes the test specified by the relational symbol. For example, if the specified field is equal to, less than, greater than, or not equal to the value indicated in the parameter statement, it is included. Valid relational symbols that can be specified are:

Note:
The symbol for "not equal to" varies; it may be either "^" or "¬". The hexadecimal equivalent is the same on all machines.

Parameter values may be in numeric, alphanumeric, or hexadecimal format.

• Hexadecimal values must be enclosed in apostrophes and preceded by an "X". In addition, hexadecimal values should be padded with blanks (X'40') to ensure that every available field byte is specified. The blank padding can be specified either at the beginning or the end of the value specification. For example, to include all input detail records with a hexadecimal 8-byte NATAPPL field value of "ABC", enter the statement as:

  INCLUDE  NATAPPL=(X'C1C2C34040404040')
  

• Alphanumeric fields may use an asterisk (*) for wildcard prefixing and suffixing. For example, to include all job names beginning with "A" and all job names ending with "TEST", enter the statement as:

  INCLUDE  JOBNAME=(A*,*TEST)

To specify a list of values, enclose the values in parentheses an separate them with commas. For example, the following specification includes input detail records with JOBNAME field values equal to "AAAAAAAA", "BBBBBBBB", or "CCCCCCCC":

INCLUDE JOBNAME=(AAAAAAAA,BBBBBBBB,CCCCCCCC)

To specify a range of values, the low and high values of the range should be separated by a hyphen. For example, the following specification includes input detail records with NATAPPL field values in the range from "AA" through "X" or with the value "AABC":

INCLUDE NATAPPL=(AA-X,AABC)

If one of the values itself contains a hyphen, enclose it in quotes. For example, the following specification includes input detail records with NATAPPL field value "AA-X" or with the value "AABC":

INCLUDE NATAPPL=('AA-X',AABC)

Examples

1. Include input detail records in Adabas Review processing only if the value of the SEQUENCE field is greater than 100, AND the value of the JOBNAME field is equal to "AAAAAAAA" or "ZZZZZZZZ", AND the value of the response code field (RSP) is within the range 9 through 150.

   Note:
   The same field name may not be used more than once for a particular INCLUDE statement.

   INCLUDE 
   SEQUENCE>100,JOBNAME=(AAAAAAAA,ZZZZZZZZ),RSP=(9-150)

2. Include input detail records in Adabas Review processing if the value of the SEQUENCE field is greater than 100, OR if the value of the JOBNAME field is equal to "AAAAAAAA" or "ZZZZZZZZ", OR if the value of the response code (RSP) field is within the range 9 through 150.

   INCLUDE  SEQUENCE>100
   INCLUDE  JOBNAME=(AAAAAAAA,ZZZZZZZZ)
   INCLUDE  RSP=(9-150)

INPUT Statement

—where FILES is used only under z/VSE.

The INPUT parameter statement defines the characteristics of the input records to be processed by the Adabas Review processor. The statement format is described in the following table:

LOG Statement

The LOG statement determines how Adabas Review is to perform physical command logging or summary logging; i.e., what information is to be logged and where it is to be written.

The following table describes the parameters within the LOG statement:

MAXIMUM Statement

The MAXIMUM parameter statement applies only to Adabas Review summary reports. It specifies the data fields for which maximum values are to be printed on these reports. Maximum values are printed only for the valid data fields specified in this statement.

Maximum values are summarized and printed on the summary report at each control break defined by the DISPLAY parameter statement for all data fields for which maximum values have been determined.

Example:

Determine maximum values for the Adabas log fields ASSOIO, WORKIO, and DATAIO and print them on the summary report.

MAXIMUM  ASSOIO,WORKIO,DATAIO

MINIMUM Statement

The MINIMUM parameter statement applies only to Adabas Review summary reports. It specifies the data fields for which minimum values are to be printed on these reports. Minimum values are printed only for the valid data fields specified in this statement.

Minimum values are summarized and printed on the summary report at each control break defined by the DISPLAY parameter statement for all data fields for which minimum values have been determined.

Example:

Determine minimum values for the Adabas log fields ASSOIO, WORKIO, and DATAIO and print them on the summary report.

MINIMUM  ASSOIO,WORKIO,DATAIO

PERCENT Statement

The PERCENT parameter statement applies only to Adabas Review summary reports. It specifies the data fields for which percentage values are to be printed on these reports. Percentage values are printed only for the valid data fields specified in this statement.

Percentage values are summarized and printed on the summary report at each control break defined by the DISPLAY parameter statement for all data fields for which percentage values have been determined.

Example:

Determine percentage values for the Adabas log fields ASSOIO, WORKIO, and DATAIO and print them on the summary report. The sum of the percentage values for each specified data field is 100 percent.

PERCENT  ASSOIO,WORKIO,DATAIO

RATE Statement

The RATE parameter statement applies only to Adabas Review summary reports. It specifies the data fields for which rate values are to be printed on these reports. Rate values are printed only for the valid data fields specified in this statement.

Rate values are summarized and printed on the summary report at each control break defined by the DISPLAY parameter statement for all data fields for which rate values have been determined.

Example:

Determine rate values for the Adabas log fields ASSOIO, WORKIO, and DATAIO and print them on the summary report. The rate will be calculated as the amount of data collected per second.

RATE  ASSOIO,WORKIO,DATAIO

REPORT Statement

The REPORT statement is critical in that it indicates that all of the following statements up to the next REPORT statement define the contents of the current report.

The REPORT statement defines the type of report to be generated by the Adabas Review processor. The following table describes the parameters in the REPORT statement:

Example:

Define a summary report with the title "A Report with Exit" to collect data from database 12345. The display program RD-00001 is to be used if the report results are displayed online. The maximum storage limit for the report will be 16 kilobytes and the report will be automatically reactivated when the maximum storage limit is exceeded. The user-written exit MYEXIT will be called whenever a command log record is selected for the report.

REPORT  TYPE=SUMMARY,TITLE='A REPORT WITH
EXIT',
PROGRAM=RD-00001,TARGET=12345,RESTART=Y,
REPORT-EXIT=MYEXIT,MAXSTORE=16

See the section Parameter Statement Processing for another example.

ROUND Statement

The ROUND parameter statement applies only to Adabas Review summary reports. It specifies the data fields for which rounding is to occur on these reports. The fields specified on the ROUND statement must also be specified on the DISPLAY statement.

Example:

Round the Adabas DURATION field up to .05 of a second.

ROUND DURATION=.05

SUM Statement

The SUM parameter statement applies only to Adabas Review summary reports. It specifies the data fields for which value totals are to be calculated on these reports. Values are printed on the summary report at each control break defined by the DISPLAY parameter statement for all data fields that have been summed.

Example:

Print the summed values for the DURATION field, Associator IOs, Data Storage IOs, and Work IOs on the summary report.

SUM     DURATION,ASSOIO,DATAIO,WORKIO

Parameter Statement Processing

This section discusses the processing order of Adabas Review parameter statements and the effect of that order on the contents of detailed and summary reports.

• Defining Reports
• Multiple Parameter Statements
• INCLUDE/EXCLUDE Statements

Defining Reports

The most critical parameter statement is the REPORT statement. It indicates that all of the following statements up to the next REPORT statement define the contents of the current report.

Example:

REPORT   TYPE=DETAIL
INCLUDE  ...
DISPLAY  ...

REPORT   TYPE=SUMMARY
EXCLUDE  ...
DISPLAY  ...
AVERAGE  ...
SUM      ...

REPORT   TYPE=DETAIL
DISPLAY  ...

There are three distinct reports: the first and third reports are detailed reports; the second report is a summary report. Each report includes/excludes different input records; different statistics are compiled and printed for each report.

Multiple Parameter Statements

A parameter statement containing multiple parameter entries can be entered as one continuous statement or as several statements, each containing one or more parameter entries. For all parameter statements except the INCLUDE, EXCLUDE, and DISPLAY statements, either method will produce the same results.

Examples:

1. Print the sum for the values in the data fields COMMANDS, ASSOIO, and DATAIO on the report.

   SUM    COMMANDS, ASSOIO, DATAIO

2. Example 2 produces the same results as example 1:

SUM    COMMANDS
SUM    ASSOIO
SUM    DATAIO

INCLUDE/EXCLUDE Statements

INCLUDE/EXCLUDE parameter statements with multiple parameters have different logical meanings based on whether the parameters are entered as separate statements or as a single continuous statement.

Examples:

1. In this example, logical AND is implied between the SEQUENCE parameter and JOBNAME and RSP parameters. Input detail records must satisfy all three conditions in order to be selected for processing:

   INCLUDE 
   SEQUENCE>100,JOBNAME=AAAAAAAA,RSP<150

2. In this example, logical OR is implied between each INCLUDE statement. Input detail records meet the selection criteria by satisfying any of the three conditions specified in the statements:

   INCLUDE  SEQUENCE>100
   INCLUDE  JOBNAME=AAAAAAAA
   INCLUDE  RSP<150

3. In this example, logical AND is implied between the SEQUENCE parameter and the JOBNAME and DATE parameters entered on the first INCLUDE statement. Input detail records must satisfy all three conditions in order to be selected for processing. No further checking is done on the records satisfying these conditions; they are included in the processing regardless of whether they satisfy the conditions set by the remaining parameter statements:

   INCLUDE 
   SEQUENCE>100,JOBNAME=AAAAAAAA,DATE<90201
   EXCLUDE  RSP>0
   INCLUDE  MONTH=12,DAY>15
   EXCLUDE  FNR<101

   Note:
   It is not possible to use a field (parameter) more than once in a single INCLUDE statement; that is, in a logical AND operation.

   Input detail records that do not satisfy the conditions specified on the first INCLUDE statement are checked against the selection criteria specified on the next EXCLUDE statement. All records satisfying this condition (i.e., RSP>0) are excluded from processing and no further checking is done on these records.

   The detail records that have not been specifically included or excluded from processing by the first two parameter statements are checked against the selection criteria specified on the next INCLUDE statement. Again, logical AND is implied between the MONTH and DAY parameters entered on this statement, and both conditions must be met in order for records to be selected for processing. No further checking is performed on the records satisfying these conditions; they are included in the processing regardless of whether they satisfy the conditions set by the final EXCLUDE statement. The remaining input detail records are then checked against the final EXCLUDE statement. All records satisfying the specified condition (i.e., FNR<101) are excluded from processing.

   Note that all records not excluded by the final EXCLUDE statement are included in the processing. If the final statement is an INCLUDE statement, all records satisfying the specified conditions for inclusion are included in the processing.

Batch Processor Job Control Requirements

This section covers the following topics:

• For z/OS Environments

• For z/VSE Environments

• For BS2000 Environments

For z/OS Environments

The job shown below is contained in member REVIEWB of the Adabas Review source library and can be used to execute the Adabas Review processor in batch.

To modify the job before submitting it:

1. Change vrs to the current version, revision, and system maintenance level of the product.

2. Modify the job statement, if necessary.

3. Modify the DD statement for RVUSEQ as necessary. Point to a command log file generated by Adabas or Adabas Review.

4. Add any additional RVUPRTxx or RVUCOPxx DD statements as necessary depending on your report definitions (where xx is a value from "01" through "99").

   //REVIEWB  JOB 
   (LOCATION),`REVIEW',MSGCLASS=X,CLASS=A
   //*
   //REVIEWB  EXEC PGM=REVIEWB,REGION=512K
   //STEPLIB  DD DISP=SHR,DSN=REVIEW.Vvrs.LOAD
   //         DD DSN=SHR,DSN=ADABAS.Vv.LOAD
   //*
   //RVUSEQ   DD DSN=SHR,DSN=ADABAS.COMMAND.LOG.FILE.
   //         DCB=(RECFM=VB,BLKSIZE=10000)
   //RVUFLD   DD DSN=SHR,DSN=REVIEW.Vvrs.SOURCE(RVUFLD)
   //*
   //RVUPRT00 DD SYSOUT=X,LRECL=80
   //RVUPRT01 DD SYSOUT=X,LRECL=160
   //RVUPRT02 DD SYSOUT=X,LRECL=160
   //SYSUDUMP DD SYSOUT=X
   //TRACEOUT DD SYSOUT=X,LRECL=160
   //*
   //RVUPARM  DD *
   INPUT   FILETYPE=SEQUENTIAL,LIMIT=1000
   *
   REPORT  TYPE=SUMMARY,TITLE=`SAMPLE REPORT'
   AVERAGE DURATION,ASSO-IO,DATA-IO,CMDRESP
   MINIMUM DURATION,ASSO-IO,DATA-IO,CMDRESP
   MAXIMUM DURATION,ASSO-IO,DATA-IO,CMDRESP
   DISPLAY JOB
   *
   /*

The following DD statements are required, or optional where noted, for executing the Adabas Review processor in interactive or batch mode:

Note:
Command log files generated by Adabas must be in sequential (DDLOG) format. You must not use a dual command log file directly as input to Adabas Review. If you are using Adabas dual command logging, the command log file must first be copied out to a sequential file using the Adabas utility ADARES function CLCOPY.

For z/VSE Environments

The job shown below is contained in member REVIEWB of the Adabas Review source library and can be used to execute the Adabas Review processor in batch.

To modify the job before submitting it:

1. Change "vrs" to the current version, revision, and system maintenance level of the product.

2. Modify the job statements, if necessary.

3. Modify the job control statement for RVUSEQ as necessary. Point to one of the command log files.

4. Add any additional RVUPRTxx or RVUCOPxx job control statements as necessary, depending on your report definitions (where "xx" is a value 01 through 99).

   //  JOB REVIEWB                             sample
   Review job
   //  EXEC  PROC=REVvrs                       Review private libraries
   //  ASSGN SYS005,SYSIPT                     RVUPARM - statements
   //  ASSGN SYS006,DISK,VOL=VVVVVV,SHR        RVUSEQ - tape
   //  ASSGN SYS007,IGN                        MAY be IGN for batch
   //  ASSGN SYS020,PRINTER                    RVUPRT0 - printer
   //  ASSGN SYS021,CUU                        RVUPRT1 - printer
   //  DLBL RVUSEQ, 'ADABAS.Vvr.COMMAND.LOG'   RVUSEQ - command
   log
   //  EXTENT SYS006,VVVVVV
   //  EXEC REVIEWB,SIZE=(AUTO,64K)
   INPUT    FILETYPE=SEQUENTIAL,LIMIT=1000
   REPORT   TYPE=SUMMARY,TITLE='SAMPLE REPORT'
   AVERAGE  DURATION
   MINIMUM  DURATION,ASSO-IO,DATA-IO,CMDRESP
   MAXIMUM  DURATION,ASSO-IO,DATA-IO,CMDRESP
   DISPLAY  JOB
   /*

   Note:
   The logical units shown in the example above may be reassigned if there are conflicts with your site-specific logical units. Refer to the Adabas Review z/VSE Installation Guide documentation for more information.

The following job control statements are required, or optional where noted, for executing the Adabas Review processor in interactive mode or batch mode:

Note:
Command log files generated by Adabas must be in sequential (DDLOG) format. You must not use a dual command log file directly as input to Adabas Review. If you are using Adabas dual command logging, the command log file must first be copied out to a sequential file using the Adabas utility ADARES function CLCOPY.

For BS2000 Environments

The job shown below is contained in member P.REVBATCH of the Adabas Review source library and can be used to execute the Adabas Review processor in batch.

Modify the job before submitting it, as described in the following steps:

1. Set &ADAL to the Adabas Library.

2. Set &BATCH to the output file prefix.

3. Set &CLOG to the command log generated by Adabas or Adabas Review.

4. Set &LIC to the Software AG product license required for Adabas and Adabas Review.

5. Set &REVL to the Adabas Review Library.

6. Modify the parameters following the /STA-PROG EDT statements to those required for the job.

   /BEGIN-PROC C,PROC-PAR=( -
   / &ADAL=$SAG.ADABAS.MOD,-
   / &BATCH=BATCH,-
   / &CLOG=$SAG.DB00099.CLOGR1,-
   / &DB=00099,-
   / &DUMP=YES,-
   / &LIC=$SAG.ADABAS.LICENSE,-
   / &REVL=$SAG.REVIEW.MOD -
   / ),ESC-CHAR='&'
   /REMARK
   /REMARK          ****************************************************
   /REMARK          *    START REVIEW BATCH                            *
   /REMARK          ****************************************************
   /REMARK
   /MOD-TEST        DUMP=&DUMP
   /DEL-F #RVUPARM
   /SET-JOB-STEP
   /CRE-FILE #RVUPARM ,PUB()
   /SE-FILE-LINK EDTSAM ,#RVUPARM ,REC-FORM=F, REC-SIZE=80
   /MOD-J-SW ON=(4,5)
   /ASS-SYSDTA *SYSCMD
   /STA-PROG EDT
   INPUT  FILETYPE=SEQUENTIAL,LIMIT=1000
   REPORT TYPE=SUMMARY,TITLE='SAMPLE REPORT'
   AVERAGE DURATION,ASSO-IO,DATA-IO,CMDRESP
   MINIMUM DURATION,ASSO-IO,DATA-IO,CMDRESP
   MAXIMUM DURATION,ASSO-IO,DATA-IO,CMDRESP
   DISPLAY JOB
   @W '#RVUPARM' O
   @H
   /SET-JOB-STEP
   /MOD-J-SW OFF=(4,5)
   /SET-JOB-STEP
   /DEL-F &BATCH..RVUPRT00
   /SET-JOB-STEP
   /CRE-FILE &BATCH..RVUPRT00  ,PUB()
   /SE-FILE-LINK EDTSAM ,&BATCH..RVUPRT00 ,REC-FORM=F, REC-SIZE=80
   /MOD-J-SW ON=(4,5)
   /ASS-SYSDTA *SYSCMD
   /STA-PROG EDT
   *
   @W '&BATCH..RVUPRT00' O
   @H
   /SET-JOB-STEP
   /MOD-J-SW OFF=(4,5)
   /SET-JOB-STEP
   /DEL-F &BATCH..RVUPRT01
   /SET-JOB-STEP
   /CRE-FILE &BATCH..RVUPRT01  ,PUB()
   /SE-FILE-LINK EDTSAM ,&BATCH..RVUPRT01 ,REC-FORM=F, REC-SIZE=160
   /MOD-J-SW ON=(4,5)
   /ASS-SYSDTA *SYSCMD
   /STA-PROG EDT
   *
   @W '&BATCH..RVUPRT01' O
   @H
   /SET-JOB-STEP
   /MOD-J-SW OFF=(4,5)
   /SET-JOB-STEP
   /DEL-F &BATCH..RVUPRT02
   /SET-JOB-STEP
   /CRE-FILE &BATCH..RVUPRT01  ,PUB()
   /SE-FILE-LINK EDTSAM ,&BATCH..RVUPRT01 ,REC-FORM=F, REC-SIZE=160
   /MOD-J-SW ON=(4,5)
   /ASS-SYSDTA *SYSCMD
   /STA-PROG EDT
   *
   @W '&BATCH..RVUPRT02' O
   @H
   /SET-JOB-STEP
   /MOD-J-SW OFF=(4,5)
   /SET-JOB-STEP
   *                                                             *
   /DEL-F #RVUFLD
   /SET-JOB-STEP
   /CRE-FILE #RVUFLD  ,PUB()
   /SE-FILE-LINK EDTSAM ,#RVUFLD  ,REC-FORM=F, REC-SIZE=80
   /MOD-J-SW ON=(4,5)
   /ASS-SYSDTA *SYSCMD
   /STA-PROG EDT
   ***************************************************************
   NAME=USERFLD1
        LEN=1
        INTYPE=B
        OUTTYPE=H
        OFFSET=16
        DISPLEN=2
        HEADER=BUFFTYPE
        CALC=N
   NAME=USERFLD2
        LEN=1
        INTYPE=B
        OUTTYPE=H
        OFFSET=18
        DISPLEN=2
        HEADER=CMDTYPE
        CALC=N
   NAME=USERFLD3
        LEN=4
        INTYPE=C
        OUTTYPE=C
        OFFSET=136
        DISPLEN=4
        HEADER=ADD2CHAR
        CALC=N
   @W '#RVUFLD' O
   @H
   /SET-JOB-STEP
   /MOD-J-SW OFF=(4,5)
   /SET-JOB-STEP
   /ASS-SYSLST   L.REV&DB..BAT.L
   /REMA ASS-SYSOUT   L.REV&DB..BAT.O
   /ASS-SYSDTA *SYSCMD
   /SE-F-LI         RVUAUT1,*DUMMY
   /SE-F-LI         RVUAUT2,*DUMMY
   /SE-F-LI         RVUPRT00,&BATCH..RVUPRT00
   /SE-F-LI         RVUPRT01,&BATCH..RVUPRT01
   /SE-F-LI         RVUPRT02,&BATCH..RVUPRT02
   /SE-F-LI         RVUSEQ,&CLOG
   /SE-F-LI         RVUPARM,#RVUPARM
   /SE-F-LI         RVUFLD,#RVUFLD
   /REMA
   /SE-F-LI         DDLIC,&LIC
   /SE-F-LI         DDLIB,&ADAL
   /SE-F-LI         REVLIB,&REVL
   /SE-F-LI         BLSLIB00,&REVL
   /SE-F-LI         BLSLIB01,&ADAL
   /SET-JOB-STEP
   /STA-PROGRAM   (&REVL,REVBATCH),PR-MO=A,RUN-M=ADV(A-L=YES)
   /REMA SET-JOB-STEP
   /ASS-SYSLST *PRIM
   /REMA ASS-SYSOUT *PRIM
   /ASS-SYSDTA *PRIM
   /END-PROC

The following link statements are required (or are optional where noted), for executing the Adabas Review processor in interactive or batch mode:

Notes:

1. Adabas Review uses two parameter files for the report definition control statements and alternates between them by writing to the older file. See the section Autostarted Reports.
2. Command log files generated by Adabas must be in sequential (DDLOG) format. You must not use a dual command log file directly as input to Adabas Review. If you are using Adabas dual command logging, the command log file must first be copied out to a sequential file using the Adabas utility ADARES function CLCOPY.

www.softwareag.com

Copyright © 2013 Software AG, Darmstadt, Germany.

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