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

This document covers the following topics:

• Introduction

• DL/I Statements

• Sets

• DAZZLER Control Statements

• z/OS JCL Requirements for DAZZLER

• z/VSE JCS Requirements for DAZZLER

Introduction

DAZZLER is a special test utility provided with the Adabas Bridge for DL/I. It is used to format DL/I calls and to monitor their results. This may be necessary, for example, to compare DL/I and Adabas performance.

DAZZLER handles up to the following maximum values:

You are most likely to want to use DAZZLER for low volume input, and for this reason the eight possible statement types have been divided into two groups of four. The first group contains those statements necessary for creating DL/I calls, and are referred to as DL/I statements. The second group consists of statements provided for the user's benefit, particularly when handling medium-to-large volumes of input. The statements in this second group are known as DAZZLER control statements, and are all optional.

All statements in both groups contain a number of validated fields. The validation rules for each field are explained in the discussion of the individual statements.

You should note that the first three positions of each statement contain an identifying title. Invalid titles, and thus the information on the statement concerned, are immediately rejected.

Blank statements are ignored.

Note:
All PSBs used for the DAZZLER program must have been created with either the PSBGEN statement option LANG=ASSEM or LANG=COBOL. Alternatively, if the PSB had been created with LANG=PLI, you must specify LANG=COBOL as DAZIFP parameter.

Appendix A shows an example of DAZZLER usage.

DL/I Statements

The following table lists the DL/I statements.

Sets

Each individual DL/I call requires that a set of statements be input — a set being defined as a group of statements beginning with a HEADER statement and ending with either the statement preceding the next HEADER or SUMMARY DL/I statement, JUMP DAZZLER control statement, or with the end of the file, as appropriate. A SUMMARY statement is considered to be a set in itself.

In other words, a set can consist of:

• only a HEADER statement,

• a HEADER statement followed by any combination of other DL/I or DAZZLER control statements (any COMMENT statements encountered will be ignored), or

• only a SUMMARY statement.

If the HEADER statement of a set is rejected by the validation routines, all the remaining statements in the same set will be rejected as well.

The following pages describe the individual statements, their layouts and the validation routines appropriate in each case.

HEADER Statement

....+....1....+....2....+....3....+....4....+....5....+....6....+.

*HD call nnn cc pp ss iiiii +++++ ssslssslssslssslssslssslssslsssl

The following pages explain the individual entries on the statement in detail.

* C = compulsory, O = optional

** Optional unless an entry has been made in "iiiii", in which case compulsory.

Example of the Iterative Overwrite Facility

Where nnn =004, iiiii contains 00100, +++++ contains 00035, and the following sssl entries are provided

ssslssslssslssslssslssslssslsssl

+....4....+....5....+....6....+.
02040352    0615    0013    1111

then the results of the coding are:

BACK Call

In addition to DL/I calls you can specify BACK as the call in the HEADER statement. This results in an Adabas BT (Backout Transaction) call which removes all data base modifications performed during the user's current logical transaction. The BACK call can only be used, if DAZZLER runs as an online batch application, i.e. with BMP, MPS or SDB as first DAZIFP parameter. To prevent conflicts with the automatic ET functionality, it is recommended to specify ET=NO as DAZIFP parameter or in the ADL Parameter Module. The BACK call can not be used while DAZZLER runs against DL/I.

IOA and SSA Statements

....+....1....+....2....+....3....+....4....+....5....+....6....+.

tit form sss ll dddddddddddddddddddddddddddddddddddddddddddddddddd

* C = compulsory, O = optional

The I/O area and the SSAs are only overwritten when this is specifically requested. If a subsequent call requires some or all of the same SSAs or the same data in the I/O area, it is not necessary for these to be recoded. You should note that the I/O area may well change as the result of a DL/I call.

SUMMARY Statement

....+....1...

SUMMARY pp

This statement causes the program to produce a table showing, for any one PCB, all the retrievable segment names and how many occurrences of each there are. The statement is NOT a part of a set as defined earlier, but rather can be considered a set in itself. When a SUMMARY statement has been encountered and validated as correct, the program issues an unqualified GU to establish position on the first segment and then issues successive GN calls until a status code of "GB" is returned. The table is then printed out and the program continues with the next statement. A SUMMARY statement may appear anywhere in the job stream and will also be recognized as ending a previous HEADER statement set.

DAZZLER Control Statements

PRINT CONTROL PARAMETER Statement

If the PRINT CONTROL PARAMETER statement is omitted, dates are printed with the format "DD/MM/YY" and a page throw occurs before each new set of statements.

The layout of the statement is as follows:

....+....1....+...

PARddtccsssssppeee

* C = compulsory, O = optional

COMMENT Statement

....+....1....+...

COM

Positions 1-3 must contain COM. This statement will be ignored by the program and is provided so that users can increase the legibility of their test streams.

JUMP and LABEL Statements

....+....

JUMP lll
LABELlll

This pair of statements is provided so that users can ignore calls in the test stream. As soon as the program reads the JUMP statement ("JUMP" in columns 1-5), it ignores all subsequent statements until the matching LABEL statement ("LABEL" in columns 1-5) is found. The match is performed on columns 6-8 (inclusive) of both statements. The three characters must match exactly for the program to restart. If no LABEL statement exists for a JUMP statement, no further calls will take place. If no JUMP statement exists for a LABEL statement, then the latter is ignored. Note that a JUMP statement forces an end of set condition (see earlier in this section).

z/OS JCL Requirements for DAZZLER

The following table lists the data sets used by the Test utility, DAZZLER.

Example

//         EXEC PGM=DAZIFP,PARM='DLI,DAZZLER,psbname'
//STEPLIB  DD DSN=ADL.LOAD,DISP=SHR
//         DD DSN=ADABAS.LOAD,DISP=SHR
//DDCARD   DD *
ADARUN PROGRAM=USER,...
//DAZOUT1  DD SYSOUT=X
//*
//*  DAZZLER DATASETS
//*
//PRNTR    DD SYSOUT=X
//CFILE    DD *
*HD GU          01
*HD GN       GB 01
/*

z/VSE JCS Requirements for DAZZLER

The following table lists the files used by the Test utility, DAZZLER.

The control input for the batch monitor (DAZIFP) and for ADARUN is read from SYSIPT. Where the control input for DAZZLER itself is also to be read from SYSIPT (by assigning SYS007 to SYSIPT), the control statements must be specified in the following order:

DLI,DAZZLER,psbname,...                                                input for DAZIFP
/*
ADARUN DB=dbid,MO=MULTI,PROGRAM=USER,...    input for ADARUN
/*
*HD GU ....                                                                       input for DAZZLER
.
.
/*

Example

// ASSGN SYS006,SYSLST
// ASSGN SYS007,SYSIPT
// EXEC DAZIFP
DLI,DAZZLER,psbname
/*
ADARUN PROGRAM=USER,...
/*
*HD GU          01
*HD GN       GB 01
/*

www.softwareag.com

Copyright © 2014 Software AG, Darmstadt, Germany.

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