t.i.l.s. user's guide - atossupport.bull.com/ols/product/system/gcos7/gcos7... · tils...

T.I.L.S.

User's Guide

DPS

7000/XTA

NO

VASC

ALE

7000

Operating System: Tuning

REFERENCE47 A2 04US 05

DPS7000/XTANOVASCALE 7000

T.I.L.S.User's Guide

Operating System: Tuning

October 1995

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

REFERENCE47 A2 04US 05

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but notlimited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 1995

Printed in France

Suggestions and criticisms concerning the form, content, and presentation of thisbook are invited. A form is provided at the end of this book for this purpose.

To order additional copies of this book or other Bull Technical Publications, youare invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this book.

Intel® and Itanium® are registered trademarks of Intel Corporation.

Windows® and Microsoft® software are registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark in the United States of America and other countries licensed exclusively throughthe Open Group.

Linux® is a registered trademark of Linus Torvalds.

The information in this document is subject to change without notice. Bull will not be liable for errors containedherein, or for incidental or consequential damages in connection with the use of this material.

47 A2 04US Rev05 iii

Preface

INTENDED READERS

This manual is intended for system programmers responsible for installing or modifyingTDS or IOF applications. Readers of this document should be familiar with IOF and TDSproducts and the general concepts of their use, as well as OSI session services (OSI-V1and OSI-V2).

SCOPE AND OBJECTIVES

This Guide describes version 39 of TILS, the Transactional and Interactive LoadSimulator. TILS is designed to simulate a load of IOF, TDS, TDS-HA, or applicationsusing OSI session services (OSI-V1 or OSI-V2), enabling the user to observe terminalload and response time.

TILS User's Guide

iv 47 A2 04US Rev05

STRUCTURE OF THIS DOCUMENT

This guide is presented in two parts. The first eight chapters present the informationnecessary to run TILS. The last four chapters are the reference sections that describe thestatements and command syntax used with TILS.

The first part of the guide:

Chapter 1 introduces the product, its uses, and defines terms you willneed to know to work with TILS.

Chapter 2 presents examples of each major TILS concept. Theexamples are first simple, then become increasingly complexas new ideas are assimilated. After reading this chapter youshould be able to run a TILS session.

Chapter 3 explains how to prepare a TILS session and gives the GCOScommands necessary to start TILS running.

Chapter 4 provides the information needed to control TILS anddiscusses operator intervention before and during a TILSsession.

Chapter 5 explains how to use TILS to simulate a TDS-HA application.

Chapter 6 describes TILS output during the compilation, simulation andprinting phases.

Chapter 7 presents the TILS logfile and explains how to activate it. Thischapter presents the format of the different records anddescribes how to use TILS to analyze them.

Chapter 8 explains how to use TILS with OSI session services. If youare concerned only with TDS or IOF applications, this sectiondoes not concern you.

The reference section:

Chapter 9 describes the TILS Declaration file and gives the syntax ofeach statement.

Chapter 10 describes the TILS Scenario file and gives the syntax of eachstatement.

Chapter 11 describes the TILS Operator Commands and gives thesyntax of each command.

Chapter 12 describes the TILS Logfile Edit statements, and gives thesyntax and an explanation of each statement.

Preface

47 A2 04US Rev05 v

RELATED DOCUMENTS

TDS Documentation

TDS Concepts..................................................................................................47 A2 01UT

- TDS for GCOS 7-V3 and GCOS 7-V5:

TDS Administrator's Guide...............................................................................47 A2 02UTTDS Programmer's Guide................................................................................47 A2 03UTTDS Quick Reference Handbook.....................................................................47 A2 04UT

- TDS for GCOS 7-V6:

TDS Administrator's Guide...............................................................................47 A2 20UTTDS COBOL Programmer's Guide ..................................................................47 A2 21UTTDS C Programmer's Guide ............................................................................47 A2 07UTTDS Quick Reference Handbook.....................................................................47 A2 24UT

High Availability Documentation

High Availability Concepts................................................................................47 A2 22UTHigh Availability Administrator's Guide.............................................................47 A2 23UT

IOF Documentation

IOF Programmer's Manual ............................................................................... 47 A2 05UJ

- IOF for GCOS 7-V3:

IOF Terminal User's Reference Manual Part 1: Introduction to IOF ................ 47 A2 01UJIOF Terminal User's Reference Manual Part 2: GCL Commands ................... 47 A2 02UJIOF Terminal User's Reference Manual Part 3: Directives andGeneral Processor Commands........................................................................ 47 A2 03UJIOF Terminal User's Reference Manual Part 4: Appendices ........................... 47 A2 04UJIOF System Administrator's Manual................................................................. 47 A2 07UJ

- IOF for GCOS 7-V5:

IOF Terminal User's Reference Manual Part 1: Introduction to IOF ................ 47 A2 21UJIOF Terminal User's Reference Manual Part 2: GCL Commands (VBO) ........ 47 A2 22UJIOF Terminal User's Reference Manual Part 2: GCL Commands (FBO) ........ 47 A2 23UJIOF Terminal User's Reference Manual Part 3: Directives andGeneral Processor Commands........................................................................ 47 A2 24UJIOF Terminal User's Reference Manual Part 4: Appendices ........................... 47 A2 25UJ

TILS User's Guide

vi 47 A2 04US Rev05

- IOF for GCOS 7-V6

IOF Terminal User's Reference Manual Part 1: Introduction to IOF ................ 47 A2 31UJIOF Terminal User's Reference Manual Part 2: GCL Commands ................... 47 A2 32UJIOF Terminal User's Reference Manual Part 3: Directives andGeneral Processor Commands........................................................................ 47 A2 33UJIOF Terminal User's Reference Manual Part 4: Appendices ........................... 47 A2 34UJ

OSI Session Services

VCAM-ISO Reference Manual Part 1: Session Services................................ 47 A2 60UCVCAM-ISO Reference Manual Part 2: GPL Primitives.................................... 47 A2 61UCVCAM-ISO User's Guide................................................................................. 47 A2 62UC

Information about Network Generation

- Networks under GCOS 7-V3 and GCOS 7-V5:

GCOS V3A/V3B Networks: Overview and Generation ................................... 47 A2 30UC

- Networks under GCOS 7-V6:

GCOS 7-V6 Networks: Overview and Generation ......................................... 47 A2 71UC

General

System Behavior Reporter ...............................................................................47 A2 03USGCOS 7-V5 Administrator's Manual (REV1)....................................................47 A2 10USGCOS 7-V6 Administrator's Manual (REV2)....................................................47 A2 10US

- For GCOS 7-V3:

System Administrator's Manual........................................................................47 A2 08US

Preface

47 A2 04US Rev05 vii

SYNTAX NOTATION

The following conventions are used for presenting command syntax.

ITEM An item in upper case is a literal value, to be specified as shown. The uppercase is merely a convention; in practice you can specify the item in upper orlower case.

item An item in lower case is non-literal, indicating that a user-supplied value isexpected.

In most cases it gives the type and maximum length of the value:

char105 a string of up to 105 alphanumeric characters dec5 a decimal integer value of up to 5 digits name31 a name of up to 31 characters file78 a file name of up to 78 characters

In some cases, it gives the format of the value:

a a single alphabetic character nnnn a 4-digit number hh.mm a time in hours and minutes

In other cases, it is simply descriptive of the value:

media:devclass

ITEM An underlined item is a default value.

bool A boolean value which is either 1 or 0. A boolean parameter can be specified byits keyword alone, optionally prefixed by "N". Specifying the keyword alonealways sets the value to 1. Prefixing the keyword with "N" always sets it to 0.

{ } Braces indicate a choice of values. Only one may be selected.

[ ] Square brackets indicate that the enclosed item is optional. An item notenclosed in square brackets is mandatory.

( ) Parentheses indicate that a single value or a list of values can be specified. Alist of values must be enclosed by parentheses, with each value separated by acomma or a space.

... Ellipses indicate that the item concerned can be specified more than once.

+=$*/ These are literal characters to be specified as shown.

TILS User's Guide

viii 47 A2 04US Rev05

The letter that follows certain parameters in the SCENARIO and DECLARATION filesidentifies the parameter type:

A Alphanumeric (A number following "A" indicates the maximum number ofcharacters allowed; i.e. A12 is a 12 character alphanumeric name).

D Definition of a variable or an object.

F Field descriptor.

I Integer.

R Register.

RR Result register.

In addition to the parameter type, certain parameters have a code which provides furtherinformation:

ref a reference to an existing object.

refdef a reference to a definition.

Example 1:

{ }{ { IMMED } }{ WHEN={ [dd.mm.yy.]hh.mm } }{ { +nnnn{W|D|H|M} } }{ }

This means you can specify:

• Nothing at all (WHEN=IMMED applies).• WHEN=IMMED (the same as nothing at all).• WHEN=22.30 to specify a time (and today's date).• WHEN=10.11.87.22.30 to specify a date and time.• WHEN=+0002W to specify 2 weeks from now.• WHEN=+0021D to specify 21 days from now.• WHEN=+005H to specify 5 hours from now.• WHEN=+0123M to specify 123 minutes from now.

Preface

47 A2 04US Rev05 ix

Example 2:

[ PAGES=(dec4[-dec4] ...) ]

An optional parameter giving either a single value or a list of values enclosed inparentheses, with each value separated by a comma or space. Each value can consist ofeither a single number or a pair of numbers connected by a hyphen. For example:

PAGES=(2,4,10-25,33-36,78 83 90)

Example 3:

[ REPLACE ={ bool | 0 } ]

A boolean parameter whose default value is zero. You can specify:

• Nothing at all (REPLACE=0 applies)• REPLACE=0 or simply NREPLACE• REPLACE=1 or simply REPLACE

TILS User's Guide

x 47 A2 04US Rev05

47 A2 04US Rev05 xi

Table of Contents

1. Introduction to TILS ........................................................................... 1-1

1.1 PREREQUISITES FOR RUNNING A TILS SESSION ............................................... 1-3

1.2 DIFFERENCES IN THE RELEASES OF GCOS 7 WITH TILS.................................. 1-4

1.2.1 Differences in the Way Operator Commands are Treated .................................... 1-41.2.2 OSI Session Services Supported by the GCOS 7 Releases.................................. 1-4

2. TILS Concepts .................................................................................... 2-1

2.1 USING TILS ................................................................................................................ 2-2

2.2 CONTROLLING A TILS SESSION ............................................................................ 2-8

2.2.1 TILS Operator Commands........................................................................................ 2-82.2.2 The Unattended Mode .............................................................................................. 2-8

2.3 THE CONTEXT OF A PATH....................................................................................... 2-10

2.3.1 Construction of Messages ....................................................................................... 2-102.3.2 Character String Constants Associated with Paths .............................................. 2-12

2.4 CONTROL PATHS ..................................................................................................... 2-14

2.5 USING TILS WITH IOF............................................................................................... 2-17

2.5.1 Variable Thinktime .................................................................................................... 2-172.5.2 Conditional Inputs..................................................................................................... 2-1 92.5.3 Handling Menus and Forms..................................................................................... 2-20

TILS User's Guide

xii 47 A2 04US Rev05

2.6 ON CONDITIONS ....................................................................................................... 2-21

2.7 USING TILS WITH TDS.............................................................................................. 2-24

2.7.1 An Example of TILS with TDS.................................................................................. 2-242.7.2 Error Treatment ......................................................................................................... 2- 27

2.8 SYNCHRONIZATION ................................................................................................. 2-29

2.9 USING TILS WITH A DSA NETWORK ...................................................................... 2-31

2.10 COLLECTING DATA.................................................................................................. 2-33

2.10.1 Type of Data Collected ............................................................................................. 2-332.10.2 Tracing Dialogs ......................................................................................................... 2 -332.10.3 Histograms............................................................................................................... .. 2-342.10.4 Chronological Output ............................................................................................... 2-35

2.11 ACCESSING FILES.................................................................................................... 2-36

2.12 DECLARING OPERATOR PATHS............................................................................. 2-38

2.13 USING TILS WITH OSI SESSION SERVICES .......................................................... 2-40

2.13.1 OSI Path Addresses .................................................................................................. 2-402.13.2 An Example Using OSI Services.............................................................................. 2-41

3. Preparing and Starting TILS .............................................................. 3-1

3.1 ELEMENTS OF THE TILS LANGUAGE .................................................................... 3-2

3.1.1 Conventions in TILS Records.................................................................................. 3-23.1.2 Parameter Types ....................................................................................................... 3-33.1.3 Registers ................................................................................................................. ... 3-43.1.4 Field Descriptors ....................................................................................................... 3- 53.1.4.1 Examples of Field Descriptors .................................................................................... 3-63.1.4.2 Accessing Fields ......................................................................................................... 3-9

3.2 THE DECLARATION FILE ......................................................................................... 3-12

Table of Contents

47 A2 04US Rev05 xiii

3.3 THE SCENARIO FILE ................................................................................................ 3-14

3.4 HOW TO START TILS................................................................................................ 3-17

4. Running TILS ...................................................................................... 4-1

4.1 THE ARCHITECTURE OF TILS................................................................................. 4-2

4.1.1 Opening Paths........................................................................................................... 4- 34.1.2 Executing TILS Statements...................................................................................... 4-34.1.2.1 Events That Activate Sequences ................................................................................ 4-44.1.2.2 User Activated Sequences.......................................................................................... 4-44.1.3 Closing Paths ............................................................................................................ 4 -64.1.4 Ending TILS ............................................................................................................... 4-64.1.5 File Access............................................................................................................... .. 4-74.1.6 Two Way Simultaneous Mode ................................................................................. 4-74.1.7 Character Set ............................................................................................................. 4-84.1.8 Device Procedure Header......................................................................................... 4-84.1.9 Device Attributes....................................................................................................... 4- 84.1.10 States of DSA Paths.................................................................................................. 4-94.1.11 TILS and OSI Session Services ............................................................................... 4-9

4.2 TILS OPERATOR COMMANDS ................................................................................ 4-10

4.3 MARGINAL EVENTS.................................................................................................. 4-12

4.3.1 Program Errors.......................................................................................................... 4- 124.3.2 Failed Requests......................................................................................................... 4- 134.3.3 Interrupts................................................................................................................ .... 4-13

5. TILS and TDS-HA................................................................................ 5-1

5.1 HIGH AVAILABILITY.................................................................................................. 5-2

5.2 HYBRID PATHS ......................................................................................................... 5-4

5.2.1 Declaring Hybrid Paths............................................................................................. 5-45.2.2 Starting Hybrid Paths................................................................................................ 5-45.2.3 Receiving an Abnormal Termination....................................................................... 5-65.2.4 Closing Hybrid Paths................................................................................................ 5-65.2.5 Reconnecting Hybrid Paths ..................................................................................... 5-65.2.6 Saving the Connection Parameters......................................................................... 5-7

5.3 AN EXAMPLE OF TILS WITH TDS-HA ..................................................................... 5-8

TILS User's Guide

xiv 47 A2 04US Rev05

6. TILS Output ......................................................................................... 6-1

6.1 THE COMPILATION PHASE...................................................................................... 6-2

6.1.1 Listing the DECLARATION File................................................................................ 6-26.1.2 Listing the SCENARIO File ....................................................................................... 6-26.1.3 Error Reporting.......................................................................................................... 6 -46.1.4 Summary Tables........................................................................................................ 6-4

6.2 THE SIMULATION PHASE ........................................................................................ 6-5

6.2.1 Format of the External Trace, Dialog Trace, and PRINT Statement ..................... 6-56.2.2 Explanation of Simulation Phase Output ............................................................... 6-6

6.3 THE PRINTING PHASE.............................................................................................. 6-8

6.3.1 Last Input and Output Tables .................................................................................. 6-86.3.2 Statistics of Path Activities ...................................................................................... 6-96.3.3 Statistics of Hybrid Paths......................................................................................... 6-96.3.4 Histograms................................................................................................................ . 6-106.3.5 Chronological Tables................................................................................................ 6-11

7. The TILS Logfile.................................................................................. 7-1

7.1 DEFINITION OF THE LOGFILE................................................................................. 7-2

7.1.1 Record Types in the Logfile ..................................................................................... 7-47.1.2 Format of the Text Field of Record Types .............................................................. 7-4

7.2 LOGFILE EXTENSIONS FOR OSI SESSION SERVICES ........................................ 7-10

7.2.1 Format of OSI Record Headers and Record Types................................................ 7-117.2.2 Format of the Text Field of OSI Record Types....................................................... 7-13

7.3 COLLECTING DATA.................................................................................................. 7-23

7.4 EDITING THE LOGFILE............................................................................................. 7-24

7.4.1 Using TILS to Edit ..................................................................................................... 7-2 47.4.2 Editing Format........................................................................................................... 7 -25

Table of Contents

47 A2 04US Rev05 xv

8. Using TILS with OSI Session Services............................................. 8-1

8.1 OVERVIEW................................................................................................................. 8-2

8.2 TILS AS OSI SESSION SERVICE USER................................................................... 8-3

8.2.1 Types of OSI Session Services................................................................................ 8-38.2.2 OSI Session Services Versions ............................................................................... 8-48.2.3 Requesting OSI Session Services........................................................................... 8-4

8.3 PROGRAMS ASSOCIATED WITH OSI PATHS ........................................................ 8-5

8.3.1 Executing Statements............................................................................................... 8-58.3.2 Categories of Paths .................................................................................................. 8-7

8.4 CONNECTING TO OSI SESSION SERVICES........................................................... 8-8

8.4.1 Negotiating the Connection ..................................................................................... 8-88.4.2 Transferring Data ...................................................................................................... 8-98.4.3 Types of Data Transferred........................................................................................ 8-98.4.4 Receiving Data .......................................................................................................... 8- 10

8.5 ENDING AN OSI SESSION ........................................................................................ 8-11

8.5.1 User Abort................................................................................................................ .. 8-118.5.2 Requesting the Release of OSI Session Services ................................................. 8-11

8.6 TOKEN MANAGEMENT ............................................................................................ 8-13

8.6.1 Transferring Tokens ................................................................................................. 8-138.6.2 Requesting Tokens ................................................................................................... 8-14

8.7 SYNCHRONIZATION AND RESYNCHRONIZATION................................................ 8-15

8.7.1 Minor Synchronization Services.............................................................................. 8-158.7.2 Major Synchronization Services.............................................................................. 8-158.7.3 Resynchronization Services .................................................................................... 8-16

8.8 ACTIVITY MANAGEMENT......................................................................................... 8-17

8.9 USER EXCEPTION REPORT .................................................................................... 8-18

8.10 ACCESSING DATA .................................................................................................... 8-19

TILS User's Guide

xvi 47 A2 04US Rev05

9. DECLARATION File Statements ........................................................ 9-1

9.1 SUMMARY OF THE DECLARATION FILE SYNTAX................................................ 9-2

9.1.1 The Identification Statement .................................................................................... 9-29.1.2 The Path Declaration Statements ............................................................................ 9-29.1.3 The Global Control Statements ............................................................................... 9-39.1.4 The Statements for Controlling Data Collection .................................................... 9-39.1.5 The Connection Statements..................................................................................... 9-49.1.6 The Context Declaration Statements ...................................................................... 9-59.1.7 The Program Control Statements............................................................................ 9-5

9.2 DESCRIPTION OF DECLARATION FILE STATEMENTS ........................................ 9-6

10. SCENARIO File Statements ............................................................... 10-1

10.1 SUMMARY OF THE SCENARIO FILE SYNTAX ....................................................... 10-2

10.1.1 Program and Block Definitions................................................................................ 10-210.1.2 The Transmission Statements................................................................................. 10-210.1.3 The OSI Session Statements ................................................................................... 10-210.1.4 The Control Statements............................................................................................ 10-410.1.5 The Copy and Conversion Statements ................................................................... 10-510.1.6 The Register Operations .......................................................................................... 10-510.1.7 The Debugging Statements...................................................................................... 10-510.1.8 The Synchronization Statements ............................................................................ 10-610.1.9 The File Statements .................................................................................................. 10-610.1.10 The Miscellaneous Statements................................................................................ 10-6

10.2 DESCRIPTION OF SCENARIO FILE STATEMENTS ............................................... 10-7

11. TILS Operator Commands ................................................................. 11-1

11.1 SUMMARY OF TILS OPERATOR COMMAND SYNTAX.......................................... 11-2

11.2 DESCRIPTION OF TILS COMMANDS ...................................................................... 11-3

Table of Contents

47 A2 04US Rev05 xvii

12. Logfile Edit Statements...................................................................... 12-1

12.1 SUMMARY OF LOGFILE EDIT STATEMENT SYNTAX........................................... 12-2

12.2 DESCRIPTION OF LOGFILE EDIT STATEMENTS .................................................. 12-2

TILS User's Guide

xviii 47 A2 04US Rev05

Table of Contents

47 A2 04US Rev05 xix

Appendices

A. Path Status.......................................................................................... A-1

B. Execution Levels ................................................................................ B-1

C. TILS Registers .................................................................................... C-1

D. Limits of TILS Objects........................................................................ D-1

E. Error Codes......................................................................................... E-1

E.1 ERROR CODES LINKED TO FIELD DESCRIPTORS AND REGISTERS................ E-1

E.2 ERROR CODES SPECIFIC TO TILS STATEMENTS ............................................... E-2

E.3 ERROR CODES SPECIFIC TO FILE ACCESS STATEMENTS................................ E-3

E.4 ERROR CODES SPECIFIC TO OSI PATHS ............................................................. E-4

F. Terminal Types Supported ................................................................ F-1

G. Format of Generated Intermediate Code .......................................... G-1

TILS User's Guide

xx 47 A2 04US Rev05

H. Alphabetical List of Statements and Commands ............................ H-1

H.1 LIST OF DECLARATION, SCENARIO FILE ANDLOGFILE EDIT STATEMENTS.................................................................................. H-1

H.2 LIST OF TILS OPERATOR COMMANDS.................................................................. H-3

Index ............................................................................................................. i-1

Table of Contents

47 A2 04US Rev05 xxi

Illustrations

Figures

1-1 A Possible Connection of a TILS Application.............................................................. 1-22-1 TILS Connected to a DSA Network............................................................................. 2-314-1 Recoverable Error Code Format ................................................................................. 4-125-1 TILS and TDS-HA ....................................................................................................... 5-35-2 Overview of Hybrid Paths with TDS-HA ...................................................................... 5-56-1 Format of Source Records.......................................................................................... 6-36-2 Format of Intermediate Code Records........................................................................ 6-36-3 Format of Simulation Phase Output ............................................................................ 6-56-4 Format for Last Input and Output in Printing Phase.................................................... 6-86-5 Format of Histograms ................................................................................................. 6-107-1 Format of the EDIT Records ....................................................................................... 7-25G-1 Format of the Intermediate Code ................................................................................ G-1

Tables

3-1 Field Descriptors (1/2)................................................................................................. 3-73-2 Fields Accessible to TILS Programs (1/2)................................................................... 3-107-1 Format of the Record Header for Events .................................................................... 7-27-2 Logfile Record Types (Excluding OSI) ........................................................................ 7-37-3 Format of Record Header for OSI Events................................................................... 7-117-4 OSI Record Types (1/2) .............................................................................................. 7-12

TILS User's Guide

xxii 47 A2 04US Rev05

47 A2 04US Rev05 1-1

1. Introduction to TILS

The Transactional and Interactive Load Simulator, TILS, is designed to simulate a load ofeither the Interactive Operations Facility (IOF), Transaction Driven Subsystems (TDS),TDS-High Availability (TDS-HA), or applications using OSI session services (OSI-V1 orOSI-V2). In doing so, TILS can test the adequacy of system resources by simulating realworking conditions.

TILS may be executed on the same system as the IOF or TDS applications or on aremote system connected through a DSA or OSI network. This is possible because TILSis implemented at the application level and uses the session control layer of GCOS 7, theVirtual Communication Access Method (VCAM).

When a terminal user requests a connection to a given application, the DNS software,Terminal Manager, requests (from VCAM) the establishment of a logical link with theapplication. The characteristics of the connection are negotiated, then a dialog betweenthe user and an application may begin. After a connection is established, allcommunications proceed according to the negotiations. All that an application knowsabout a correspondent is the aspects that have been negotiated. Thus, if thecorrespondent pretends to be a terminal, the application will react accordingly.

TILS, like the Terminal Manager, is able to request a connection between its own objectsand an application. TILS may request the establishment of a connection and may also bethe object of connection requests. Unless otherwise specified, TILS handles all dialogs inTwo Way Alternate (TWA) mode. This means that at any given time only one of thecorrespondents has the right to transmit messages. All connections to IOF or to TDS fulfilthis requirement.

TILS offers the user a view of an application similar to that of an ordinary terminal user. Asa TILS programmer, your main concern is to provide the correct sequence of inputmessages for a given application. However, most reactions to VCAM notifications aretreated by TILS do not require your intervention.

TILS User's Guide

1-2 47 A2 04US Rev05

IO F

T ILS2

TD S2

T ILS1

TDS1

IO F

DATANET

DATANET

FEPS

FEPS

Figure 1-1. A Possible Connection of a TILS Application

TILS consists of a load module which must be executed through a batch job. This jobconsists of 3 phases:

• compilation phase• simulation phase• printing phase.

During the compilation phase the input for TILS is read from 2 files: the DECLARATIONfile and the SCENARIO file. This phase prepares the intermediate code which isinterpreted during the simulation phase of TILS.

The simulation phase is the active part of TILS, in which TILS establishes dialogs withother applications.

The printing phase prints the data collected during the simulation phase.

Introduction to TILS

47 A2 04US Rev05 1-3

1.1 PREREQUISITES FOR RUNNING A TILS SESSION

In order to run TILS, you need to have an Extended FORTRAN Run Time package and aCPU equipped with a scientific unit.

Before TILS can be started, the network generation utility CRNETGEN must be run.

If you are using TILS to load IOF, then the FEPS/TNS (Front End Processor Support)should be started first, to activate IOF. No real terminal need be present.

TILS User's Guide

1-4 47 A2 04US Rev05

1.2 DIFFERENCES IN THE RELEASES OF GCOS 7 WITH TILS

1.2.1 Differences in the Way Operator Commands are Treated

Certain V3 Operator Commands (such as the DS command) are replaced in GCOS 7Release V7 as from TS 7356 by directives of the MAIN domain, and are no longeravailable. All dynamically created commands are still available, such as those created byTDS for the TDS master operator, or commands generated by TILS. If these are the onlytype of OCL commands submitted (TDS master operator or commands generated byTILS), TILS does not modify the SCENARIO and DECLARATION files.

Now TILS allows you to submit Operator Commands directly to the operating systemthrough the OCL statement (in the DECLARATION file):

• at the beginning and end of the simulation phase• from a program executed by a path.

Unless otherwise indicated, all OCL commands are first transmitted as OperatorCommands. If the command is recognized, TILS behaves exactly as under ReleaseV3/V5. If the command is not recognized, TILS attempts to treat it as a GCL directive.

• If the command cannot be treated as a GCL directive, then no special actions aretaken; it is executed as if it were a V3 or V5 command.

• If the GCL directive is recognized, a warning is given because the semantics of theexecuted directive might differ from the intended command. In this case, you mayindicate that the text in question is an operator command (OCL) or a directive (GCL)and the command will be appropriately treated.

Use the OCL parameter of the NAME statement in the DECLARATION file to change thedefault behavior of TILS when it encounters the OCL statements:

• "OCL=ANY" indicates that only those OCL statements which specify explicitly"TYPE=GCL" might contain directives.

• "OCL=ALL" does not accept any directives; thus specifying "TYPE=GCL" leads to anerror (return code FUNCNAV).

1.2.2 OSI Session Services Supported by the GCOS 7 Releases

There are two OSI Session Services, Version 1 (OSI-V1) and Version 2 (OSI-V2), thatcan be implemented under GCOS 7.

Both of these versions are supported by GCOS 7-V7 as from TS 7356.

47 A2 04US Rev05 2-1

2. TILS Concepts

This section introduces you to the use of TILS through a series of examples. You will findinformation on TILS statements used in the DECLARATION and SCENARIO files in thechapter, "Preparing and Starting TILS" and detailed explanations of the syntax of thesestatements in the chapters "SCENARIO File Statements" and "DECLARATION FileStatements".

The examples given in this chapter are not meant to be full scale applications of TILS, butare introduced for instructional purposes. Some examples presented in this section aremore complex than others and you are advised to skip those which seem not applicable toyour work.

TILS User's Guide

2-2 47 A2 04US Rev05

2.1 USING TILS

This section introduces a simple example to illustrate the concepts of TILS. It will bemodified later as new concepts are introduced.

You can observe the behavior of GCOS 7 under a load induced by six users connected toIOF, three of whom are executing LIBMAINT to list the subfiles in a cataloged library whilethe other three are using EXEC_PG to execute a previously created COBOL program.

Each user is represented by a path. A path is a TILS entity that has certain attributesassociated with terminal users including:

• user ID• project• billing• password

and attributes generally associated with a terminal such as:

• device type• correspondent.

Each path is associated with a set of rules or conditions, which generate messages to besent to the correspondent. This set of rules is described in a program. A program maycontain:

• explicit TILS statements, indicated by the ":" in the first column• comments, indicated by "*" in the first column• implicit TILS statements (all other records).

A path may also have associated blocks of simulated input data.

To use TILS to test a load you will need to create two files:

• the DECLARATION file to declare the paths and their attributes• the SCENARIO file to contain the programs and blocks associated with the paths.

These files are created as members of a source language library.

The commented SCENARIO and DECLARATION files for this Example 1 is as follows.The line-numbers are given for easier reference.

TILS Concepts

47 A2 04US Rev05 2-3

This SCENARIO file contains 2 programs. The first program LIBMAIN1 is formed by allrecords between line 3 and line 17, the second by all records between line 22 and line 27.

Program LIBMAIN1 contains four implicit SEND statements and 2 other TILS statements,PROGRAM and EOD. The PROGRAM statement creates the entry point LIBMAIN1 forthis program.

--------------------------------------------------------------- 1 | TEXT OUTSIDE THE PROGRAM OR BLOCK IS TAKEN TO BE 2 | COMMENT. PROGRAMS BEGIN WITH A PROGRAM STATEMENT 3 | :PROGRAM LIBMAIN1 4 | * 5 | * LINES INSIDE A PROGRAM BEGINNING WITH "*" 6 | * ARE ALSO COMMENTS. 7 | * IF THE LINE BEGINS WITH NEITHER "*" NOR ":" IT 8 | * IS AN IMPLICIT SEND STATEMENT. 9 | *10 | LMN SL LIB=TEST.SL.LIB;11 | LIST *;12 | QUIT;13 | BYE;14 | *15 | * THE EOD STATEMENT ENDS THE PROGRAM LIBMAIN116 | *17 | :EOD18 |19 | PROGRAM COBOL1 IS TO BE USED BY THE PATHS20 | ACTIVATING EXEC_PG21 |22 | :PROGRAM COBOL123 | CBL SOURCE=MYPROG, INLIB=MYLIB.SL,CULIB=MYLIB.CU;24 | LINK_PG LM=MYPROG, INLIB=MYLIB.CU,LIB=MYLIB.LM;25 | EXEC_PG PG=MYPROG,LIB=MYLIB.LM;26 | BYE;27 | :EOD---------------------------------------------------------------

Example 1. Scenario File

TILS User's Guide

2-4 47 A2 04US Rev05

--------------------------------------------------------------- 1 | * THE PROGRAMS "LIBMAIN1" AND "COBOL1" MUST BE 2 | * COMPILED 3 | * 4 | PROGRAM LIBMAIN1,COBOL1 5 | * 6 | * A TIME LIMIT OF 20 MINUTES IS REQUIRED 7 | * 8 | ELAPSED 20,MIN 9 | *10 | * TILS CHECKS FOR TIMEOUT AT 2 MINUTE INTERVALS11 | *12 | WATCHDOG 2,MIN13 | *14 | * PATHS REFERRING TO "LOG" ARE LOGGED WITH THEIR15 | * DEFAULT PROJECT AND BILLING AND BLANK PASSWORD16 | *17 | LOGON LOG,PROJECT=' ',BILLING=' ',PASSWORD=' '18 | *19 | * PATHS REFERRING TO "SIM", DIALOG WITH IOF ON20 | * THE SAME SYSTEM AS TILS.21 | *22 | DESTINATION SIM,MAILBOX=IOF,NODE=' '23 | *24 | * PATHS REFERRING TO "DKU" ARE OF TYPE "DKU7005"25 | * THEY INITIATE CONNECTIONS AND THEIR26 | * CORRESPONDENT HAS THE INITIAL TURN.27 | *28 | DEVICE DKU,TYPE=DKU7005,TURN=ACCE,CONNECT=INIT29 | PATH USER1,LIBMAIN1,14000,LOGON=LOG>30 | DESTINATION=SIM,DEVICE=DKU31 | PATH USER2,LIBMAIN1,14000,LOGON=LOG>32 | DESTINATION=SIM,DEVICE=DKU33 | PATH USER3,LIBMAIN1,14000,LOGON=LOG>34 | DESTINATION=SIM,DEVICE=DKU35 | PATH USER4,COBOL1,14000,LOGON=LOG>36 | DESTINATION=SIM,DEVICE=DKU37 | PATH USER5,COBOL1,14000,LOGON=LOG>38 | DESTINATION=SIM,DEVICE=DKU39 | PATH USER6,COBOL1,14000,LOGON=LOG>40 | DESTINATION=SIM,DEVICE=DKU---------------------------------------------------------------

Example 1. Declaration File

NOTES: 1. Lines beginning with "*" are comments.

2. The ">" used as the last character of a line indicates that thefollowing line is a continuation of the current line.

The PATH statements (lines 29 to 40) are the core of the preceding DECLARATION file,declaring the paths of the TILS session.

The first parameter of the PATH statement indicates the name of the path. This name isnot internal to TILS, it must be a valid user ID in the site catalog of the target system. Theuser ID must match the project, billing and password specified in the correspondingLOGON statement (line 17). The association between the LOGON and PATH statementsis made through the LOGON parameter of the PATH statement.

TILS Concepts

47 A2 04US Rev05 2-5

The second parameter contains an entry point into a TILS program. The path isassociated with a TILS statement in the SCENARIO file. USER1, USER2 and USER3 areassociated with the statement in line 3 of the SCENARIO file in Example 1. Theremaining paths are associated with the statement in line 22 of the same example.

The third parameter indicates that 14 seconds are to elapse between the moment TILS isready to send a message to the correspondent and the moment a message is sent. Thisinterval is called thinktime.

The fourth, fifth, and sixth parameters specify the LOGON, DESTINATION and DEVICEstatements associated with the path.

The PROGRAM statement (line 4) selects the programs of the SCENARIO file to becompiled.

The ELAPSED statement (line 8) provides a time-limit for the simulation phase. Once thistime-limit is detected the simulation phase is ended independently of any TILS activity.

The WATCHDOG statement (line 12) defines a time period. Whenever this time period isreached, TILS checks whether the elapsed time-limit has been reached and if a timeouthas occurred on any path.

The LOGON statement (line 17) specifies further site catalog attributes for the pathsreferring to this statement. In the example, the project and billing will be those specifiedas default values in the site catalog and the password will be blank.

The DESTINATION statement names the correspondent for the paths which refer to thisstatement. In this example it is IOF on the system on which TILS is executing.

The DEVICE statement associates a terminal type with the path. It also determines theinitial turn, whether the path or the correspondent is to transmit the first message. TheCONNECT parameter indicates whether the path is to request the connection or whetherit may accept connection requests. The parameters in this example are those in whichthe correspondent is either an IOF or a TDS application, and TILS is a group of terminals.

The LOGON, DESTINATION, DEVICE and WATCHDOG statements of this example areoptional. They are represented by the default values and could have been omitted asshown in Example 1 - Reduced Declaration File.

The ELAPSED statement is also optional. The default time-limit is four minutes.However, it is advisable to specify a time-limit explicitly.

-------------------------------------- 1 | PROGRAM LIBMAIN1,COBOL1 2 | PATH USER1,LIBMAIN1,14000 3 | PATH USER2,LIBMAIN1,14000 4 | PATH USER3,LIBMAIN1,14000 5 | PATH USER4,COBOL1,14000 6 | PATH USER5,COBOL1,14000 7 | PATH USER6,COBOL1,14000--------------------------------------

Example 1. Reduced Declaration File

TILS User's Guide

2-6 47 A2 04US Rev05

Default LOGON, DESTINATION and DEVICE statements with the internal name ' ', arecreated by TILS and attached to any paths which do not explicitly specify such astatement. These statements are equivalent to the statements LOG, SIM and DKUdescribed in Example 1 - Declaration File.

TILS may be launched as a batch job using the appropriate JCL assigning theDECLARATION file to FILE_B and the SCENARIO file to FILE_C. For example:

$STEP H-TILS, FILE=SYS.HLMLIB;$SIZE 130;$ASSIGN FILE-B, TILSLIB,FILESTAT=CAT,SUBFILE=DECLARATION;$ASSIGN FILE-C, TILSLIB,FILESTAT=CAT,SUBFILE=SCENARIO;$ENDSTEP;

The compilation phase of TILS will then produce the following code locked in mainmemory:

• intermediate code to be interpreted by TILS during the simulation phase• tables describing the attributes of the paths.

Once the compilation phase is finished, you are notified by the message OP04 that thecommand TILS has been created. You may now start the simulation by entering the TILScommand:

TILS START ALL.

If you are logged to IOF with #JCLCOMP 0, you must use the GCL directive, "ESCAPE"before entering the TILS command.

TILS will request a connection for each path between the principal TILS mailbox and theIOF mailbox - IOF. Once the connection is established, the PATH is said to be opened orconnected. The connection of a path to IOF starts an interactive job, just like aconnection to IOF from a terminal.

The dialog between a path and a correspondent always takes place in TWA mode. Atany given moment either the path or the correspondent has the right to transmit amessage. This right to transmit is called the turn. The turn is transmitted between thepath and its correspondent together with the data.

You can follow the sequence of events for path USER1. The TILS command "START"opened the path USER1. As IOF has the initial turn, it begins to send messages toUSER1. TILS is notified that a message has arrived for USER1. This message is thenreceived in the output buffer associated with path USER1. If the message did not carrythe turn, that is, did not indicate a transfer of the right to transmit a message, TILS waitsfor the next notification. Once TILS receives a message carrying the turn, such as theIOF prompt "S:", it executes the statement currently associated with the path. In theexample, this is an implicit SEND statement.

TILS Concepts

47 A2 04US Rev05 2-7

The SEND statement causes 2 operations:

• the timer is set with the thinktime, causing TILS to wait for the next notification andputting the path in the state:

Wait for timer request

• TILS is notified that a thinktime for the PATH has elapsed, the message is moved tothe input buffer associated with the path, it is then sent to the correspondent, and thepath is in the state:

Wait for first output

Messages sent from TILS to a correspondent are called inputs. The input:

LMN SL LIB=TEST.SL.LIB;

activates LIBMAINT. The next output carrying the turn that TILS will receive for pathUSER1 is the prompt "C:". TILS answers after the thinktime with:

LIST *;

requesting the list of all members of library TEST.SL.LIB. The dialog proceeds until theinput:

BYE;

is sent, ending the IOF session for USER1 and reverting the path (USER1) to the idlestate.

You may end the simulation phase at any time by entering the STOP command. Thiscommand closes all opened paths. The correspondent sees this as an abnormaltermination similar to the failure of a terminal.

If the STOP command is not used the simulation phase will end when the time-limit isdetected even if there are paths still open.

TILS User's Guide

2-8 47 A2 04US Rev05

2.2 CONTROLLING A TILS SESSION

During the simulation phase, you may converse with TILS through a set of commands,which are called TILS Operator commands. Two examples, the START and STOPcommands, have already been introduced. Other TILS Operator commands aredescribed in the chapter "Using TILS with OSI Session Services".

The following paragraphs contain a brief discussion of the commands and introduce amethod of running TILS without the intervention of an operator.

2.2.1 TILS Operator Commands

At any time during the TILS simulation phase, you may enter any one of the operatorcommands. The general format of these commands is:

commandid commandname [,parameter-list]

The default value of commandid is "TILS". This value may be changed using the NAMEstatement in the DECLARATION file.

To obtain the list of all TILS operator commands you may use the HELP command byentering

TILS HELP.

To obtain the purpose and syntax of any of these commands use the name of thecommand as a parameter to the HELP command. For example,

TILS HELP,AUTO

displays the syntax of the AUTO command on the TILS Operator console.

GCL procedures are not provided for TILS. If TILS is launched from a console connectedto IOF, you should be logged on in a mode compatible with JCL, #JCLCOMP 2 and#NOVICE 0.

2.2.2 The Unattended Mode

By default, you must initiate the simulation phase using the TILS command START. Thesimulation phase will continue until the TILS command STOP is used or the time-limitspecified in the ELAPSED statement is reached.

However, TILS may be started without your intervention by using the CONNECTparameter of the NAME statement in the TILS DECLARATION file. You can specify thehighest rank in the DECLARATION file up to which eligible paths may request theconnection. The AUTO statement automatically ends for TILS once all paths are idle.

TILS Concepts

47 A2 04US Rev05 2-9

When the compilation phase is ended, connection requests for all six PATHS aretransmitted to the operating system (the NAME statement in line 1). The simulation phaseends once all paths are idle.

--------------------------------------------------------------- 1 | NAME CONNECT=6 2 | AUTO ENABLE 3 | PROGRAM LIBMAIN1,COBOL 4 | ELAPSED 20,MIN 5 | WATCHDOG 2,MIN 6 | LOGON LOG,PASSWORD=' ' 7 | DESTINATION SIM,MAILBOX=IOF 8 | PATH USER1,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM 9 | PATH USER2,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM10 | PATH USER3,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM11 | PATH USER4,COBOL1,14000,LOGON=LOG> | DESTINATION=SIM12 | PATH USER5,COBOL1,14000,LOGON=LOG> | DESTINATION=SIM13 | PATH USER6,COBOL1,14000,LOGON=LOG> | DESTINATION=SIM---------------------------------------------------------------

Example 1. Declaration File (Unattended Mode)

TILS User's Guide

2-10 47 A2 04US Rev05

2.3 THE CONTEXT OF A PATH

In Example 1, three paths executed the same program. Thus all three used the samelibrary.

The next example examines a case in which paths USER1, USER2 and USER3 each usetheir own cataloged library. This example introduces the notion of the context of a path.

2.3.1 Construction of Messages

Each path may access certain fields such as its output buffer, input buffer and workspace.These fields contain character strings which are addressed by the program through fielddescriptors.

A field descriptor specifies:

• the type of field

• the offset of the first character of the string in the field(If no offset is specified then offset 0 is assumed.)

• the length of the character stringIf no length is specified the total inherent length is used).

Numeric values are stored in registers. A register is designated by an either positive ornegative integer other than 0 and prefixed by "*" or "?". If the number of the register ispositive, it is a private register associated with the path executing the statement.Registers 1 to 8 are used by TILS and may only be consulted. Registers 9 to 16 arereserved for paths using OSI session services.

Each path may be associated with a workspace where messages may be constructed.Each path may also access its own name and other information about itself. The TILSprogram constructs the message,

LMN SL LIB=SL.USER1;

in the workspace of USER1 when it is executed by USER1, and the message,


in the workspace of USER2, when it is executed by USER2.

TILS Concepts

47 A2 04US Rev05 2-11

The SCENARIO and DECLARATION files for Example 2 are as follows. The SIZEstatement creates a workspace of 40 bytes and 2 registers, numbers 17 and 18, for eachpath following it.

--------------------------------------------------------------- 1 | :PROGRAM,LIBMAIN1 2 | * 3 | * CHAIN "LMN SL LIB=SL." IS COPIED TO THE START 4 | * OF THE WORKSPACE. THE FIRST FREE OFFSET IN THE 5 | * WORKSPACE IS STORED IN REGISTER 18. 6 | * 7 | :COPY *18 TARGET=(WORK)> | SOURCE=(ALPHA,'LMN SL LIB=SL.') 8 | * 9 | * THE FIRST 5 CHARACTERS OF THE NAME ARE APPENDED10 | * TO THE STRING IN THE WORKSPACE. (THE INHERENT11 | * LENGTH OF THE NAME FIELD IS 12!)12 | *13 | :COPY *18 TARGET=(WORK,*18) SOURCE=(NAME,0,5)14 | *15 | * THE MESSAGE IS COMPLETED WITH ";".16 | *17 | :COPY *18 TARGET=(WORK,*18) SOURCE=(ALPHA,';')18 | *19 | * THE CHARACTER STRING CONTAINED IN THE WORKSPACE20 | * AT OFFSET 0 WITH THE LENGTH SPECIFIED IN21 | * REGISTER 18 IS SENT TO IOF.22 | *23 | :SEND SOURCE=(WORK,0,*18)24 | LIST *;25 | QUIT26 | BYE;27 | :EOD---------------------------------------------------------------


--------------------------------------------------------------- 1 | PROGRAM LIBMAIN1 2 | ELAPSED 20,MIN 3 | LOGON LOG,PASSWORD=' ' 4 | DESTINATION SIM,MAILBOX=IOF 5 | * A WORKSPACE OF 40 BYTES AND 2 REGISTERS ARE TO 6 | * BE ASSOCIATED WITH ALL PATHS THAT FOLLOW 7 | SIZE WORKSIZE=40,REGISTER=2 8 | PATH USER1,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM 9 | PATH USER2,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM10 | PATH USER3,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM---------------------------------------------------------------


In Example 2, once path USER1 is opened, IOF, which has the initial turn, begins sendingmessages to USER1. After receiving the [S:] prompt, USER1 receives the turn and TILScan execute the statement currently associated with that user.

TILS User's Guide

2-12 47 A2 04US Rev05

That is, TILS executes the statement following the entry point of the PATH statementdefining the path USER1. TILS thus executes the COPY statement in line 7 of theSCENARIO file. It transfers the literal chain specified as source into the workspacebeginning at offset 0. The first free offset after the transfer is stored in register 18.Because this statement is neither a SEND nor a WAIT nor a SYNCHRONIZE statement,the next statement is treated immediately.

This statement is also a COPY statement. The first 5 characters of the name of the pathare copied into the workspace at the offset contained in register 18. The offset of the firstfree byte in the workspace is stored in register 18.

The third COPY statement appends the ";" of the message stored in the workspace. Thestatement on line 23 is an explicit SEND statement and is treated just like the implicitSEND statement discussed in Example 1. The input transferred is the text specified assource, that is, the content of the workspace from offset 0 onwards. The length of theinput is specified in register 18.

Path USER1 constructs this input in its workspace:


while the workspace of USER2 contains:


after USER2 executes the sequence. Each paths sends different input through thisexplicit SEND statement and are thus calling LIBMAINT on different libraries.

2.3.2 Character String Constants Associated with Paths

A certain number of constant character strings may be associated with each path. Such acharacter string is called a seed. The case as shown in Example 2 can be reproduced bystoring the different calls to LIBMAINT as seeds, as shown in Example 3. This is usefulbecause only one TILS statement needs to be interpreted during the simulation phase tocall LIBMAINT with the appropriate library, instead of four as in the previous method.

--------------------------------------------------------------- 1 | :PROGRAM,LIBMAIN1 2 | * 3 | * THE SEED ASSOCIATED WITH THE PATH CONTAINS THE 4 | * CALL TO LIBMAINT WITH THE PRIVATE LIBRARY. 5 | * 6 | :SEND SOURCE=(SEED) 7 | LIST *; 8 | QUIT 9 | BYE;10 | :EOD---------------------------------------------------------------


TILS User's Guide

2-14 47 A2 04US Rev05

2.4 CONTROL PATHS

When TILS is started in the unattended mode, after all paths execute their programs theybecome idle and TILS ends the simulation phase.

There is a way to monitor TILS activity more closely using Control paths known only toTILS, which do not dialog with any application. This approach is more complicated buthas the advantage that it can be modified to restart the simulation once all paths becomeidle.

The context of a path defines all the information accessible to a path. You have seen thateach path is able to access certain information, such as its name. Thus the name of thepath is part of the context. TILS also allows a control path to consult the context and thestate of any other path. When these paths are idle the control path ends the simulationphase.

The Control path is associated with a device of type NONE. This means that actioninvolving the communication system may not be taken on by this path. The existence ofthe Control path is internal to TILS.

Once the START command is issued for the Control path, the path is opened and the firststatement associated with it is executed. The number of declared paths minus 1(because the Control path is not counted) is stored in register 18. Every 2 minutes theloop over all declared paths is executed, except for the path Control.

The SWITCH statement allows Control to consult the context of the path whose rank inthe DECLARATION file is stored in the sharable register -2. Sharable registers areregisters that may be accessed by all paths. If a path is consulting a foreign context, onlysharable registers may be modified by it.

The LOAD statement in line 19 of the SCENARIO file stores, in byte 4 of register -3, thecurrent state of the path whose context is consulted. The AND statement masks bytes 1to 3. The mask is given by a hexadecimal integer and is represented by "%" followed byhexadecimal digits. The states are accumulated in register -1. When the loop isexecuted, register -1 contains 0, if and only if, all states equal 0. (The state of a pathequals 0 when it is idle.) If all paths are idle the TERMINATE statement in line 30 endsthe simulation phase of TILS, otherwise execution is branched to label BEGIN.

The SCENARIO and DECLARATION files for Example 4 are as follows.

TILS Concepts

47 A2 04US Rev05 2-17

2.5 USING TILS WITH IOF

By default, IOF interprets the connection of a path to IOF as a connection with a typeDKU7005, unless another type is specified in the DEVICE statement. Thus, IOF sends anend-of-page marker whenever a page is filled. This marker carries the turn but IOF doesnot expect any answer. It is represented by "+++" preceded by three control characters.

If the system variable #NOVICE is set to 1, IOF will prompt the terminal with menus.

2.5.1 Variable Thinktime

When "+++" is received, TILS is left in a permanent "wait" state. In previous versions, theSEND statements handled the transmission of messages by setting the timer with athinktime and then sending input to the correspondent when the thinktime had elapsed.However, to send messages like a response to the end-of-page marker without athinktime, you must use the variable thinktime.

When thinktime is specified as variable, it is determined by the value of register 17,interpreted in milliseconds.

• if the value of register 17 is negative, no thinktime is used and all inputs are transferredimmediately.

• if the value is 0, the thinktime specified in the PATH statement is used.• if the value is positive, it is used as the thinktime for the path. The contents of the

register are interpreted in milliseconds.

The SCENARIO and DECLARATION files for Example 5 are as follows.

TILS Concepts

47 A2 04US Rev05 2-19

--------------------------------------------------------------- 1 | PROGRAM VIP 2 | ELAPSED 20,MIN 3 | THINKTIME VARIABLE 4 | LOGON LOG,PASSWORD=' ' 5 | DESTINATION SIM,MAILBOX=IOF 6 | SIZE WORKSIZE=20 REGISTER=2 7 | * 8 | * USER1,USER2 AND USER3 ARE ASSOCIATED WITH 9 | * BLOCK LIBMAIN. THEY ARE TO STIMULATE LIBMAINT.10 | *11 | PATH USER1,VIP,14000,LOGON=LOG,DESTINATION=SIM12 | DATA USER1,LIBMAIN13 | PATH USER2,VIP,14000,LOGON=LOG,DESTINATION=SIM14 | DATA USER2,LIBMAIN15 | PATH USER3,VIP,14000,LOGON=LOG,DESTINATION=SIM16 | DATA USER3,LIBMAIN17 | *18 | * USER4,USER5 AND USER6 ARE ASSOCIATED WITH19 | * BLOCK COBOL. THEY ARE TO STIMULATE COBOL.20 | *21 | PATH USER4,VIP,14000,LOGON=LOG,DESTINATION=SIM22 | DATA USER4,COBOL23 | PATH USER5,VIP,14000,LOGON=LOG,DESTINATION=SIM24 | DATA USER5,COBOL25 | PATH USER6,VIP,14000,LOGON=LOG,DESTINATION=SIM26 | DATA USER6,COBOL---------------------------------------------------------------


NOTES: 1. All paths execute the same program but send different input to IOF.

2. In lines 26 and 37 of the SCENARIO file for Example 5, you see thecharacter chain "[X05". This represents a single "tab" character.When you are in FSE or line edit mode, you must type thissequence to insert a tab. On subsequent listings, however, thissequence will be replaced by a period (as would any other non-printing character). In TILS programs the tab key is the onlycharacter that you will need to represent this way.

2.5.2 Conditional Inputs

The end-of-page marker requires a response that carries the turn. This message mustnot be taken from the set of inputs provided by the SCENARIO but must be a dummymessage such as a sequence of blanks.

The inputs belonging to a path may be grouped into blocks. A block is a sequence ofrecords in the SCENARIO file headed by a BLOCK statement and closed by an EODstatement. Each block can be associated with one or several paths and accessed by thepath through a field descriptor. Access to these blocks is sequential.

TILS User's Guide

2-20 47 A2 04US Rev05

2.5.3 Handling Menus and Forms

Some applications use forms to accept input from a terminal. This is the case for certainapplications executing under IOF, including FSE and some TDS applications. You mustprovide these forms in linear format replacing the use of the TAB key by its hexadecimalequivalent, "05".

In the Example 5, the first input sent to IOF was "[X05 LET #NOVICE 0;". Thiscorresponds to the IOF command "LET #NOVICE 0" entered by a user after having usedthe TAB key to move the cursor to the next field of the menu.

TILS Concepts

47 A2 04US Rev05 2-21

2.6 ON CONDITIONS

In the simulation phase, TILS is driven by external events such as notification that datahas arrived or a TILS Operator Command is received.

The response to such an event is either:

• standard action taken by TILS whenever such an event occurs• programmed action planned by the TILS programmer.

In the case of notification that data has arrived for a given path, the data is received in thepath's output buffer. If the output carried the turn, it is processed according to theprogram and the statement currently associated with the path is executed.

It is only in this situation, when the output carries the turn, that TILS statements areautomatically executed. If other events are to be treated by the program, an entry pointfor the path must be associated with the condition in either the DECLARATION or theSCENARIO files. If the event of a specified condition occurs, the statements following thespecified entry point are executed. This type of statement is called an ON section. Anexecution level corresponding to the condition is associated with this path.

The ON DATA condition is a good example of condition handling. You can see inExample 6 that Path USER1 submits a job and scans the JOR (Job Occurrence Report).The RON (Run Occurrence Number) is extracted to construct the SCANNER commands.The SCENARIO and DECLARATION files for this example follow.

TILS Concepts

47 A2 04US Rev05 2-23

Path USER1 executes the job MYBATCH and analyzes all outputs until a message isfound containing "COMPLETED" or "ABORTED". The message is examined for theRON. If no RON is found, the message is erroneous and the path is closed using theTERMINATE statement. Otherwise, the RON is extracted to construct the SCANNERcommand in a workspace accessible to all paths, the pool.

The association between the entry point and the path is ended because the task of theON section is completed and there is no further need to analyze the output. The BREAKstatement generates an interrupt ending the IOF LISTEN mode.

In this example, the path did not wait for notification during execution of the ON section.The ON section must be ended by RETURN or TERMINATE statements.

TILS User's Guide

2-24 47 A2 04US Rev05

2.7 USING TILS WITH TDS

The previous examples have only considered the case where TILS is used to load a localIOF. The following subsection gives an example of TILS used to load a TDS application.

2.7.1 An Example of TILS with TDS

PLAY is a simple TDS application with 15 transactions, sufficient to demonstrate theinteraction of TDS and TILS.

Each transaction in the PLAY system comprises one transaction processing routine andone exchange. These transactions represent the fifteen lines of the Paris subway system(the Metro). The lines are numbered from 1 to 15. Lines 3 and 7 split into separate linesnamed 3A/3B and 7A/7B. The 15 transactions are referred to as "Mxxy" where:

• M is Metro line• xx varies from "01" to "15"• y is "A" or "B" when xx is one of "03" or "07" else "A".

The output is a list of all lines that connect to the line representing the input of thetransaction. Each connecting line is given in the output in the form of a PLAY transactionname.

Example:

The user enters: and receives this output:

"M03B" "===M03AM11A CONNECT"

Thus, the two lines that connect with line 3B are 3A and 11A.

A possible scenario of PLAY may be as follows:

• each path sends an initial input to activate the first transaction• the transaction that follows is determined by the output received; choosing the last

transaction cited in the output list.

TILS User's Guide

2-26 47 A2 04US Rev05

--------------------------------------------------------------- 1 | PROGRAM PLAYPLAY 2 | * 3 | * EACH SEND IS TO BE EXECUTED WITHOUT DELAY 4 | * 5 | THINKTIME INHIBIT 6 | * 7 | * 7 SHARABLE REGISTERS ARE RESERVED 8 | * 9 | COMMON REGISTER=710 | *11 | * EACH PATH MUST DISPOSE OF A WORKSPACE AND 612 | * PRIVATE REGISTERS.13 | *14 | SIZE WORKSIZE=100,OUTSIZE=100,INSIZE=100> | REGISTER=615 | *16 | * THE TDS MAILBOX BEARS THE SAME NAME AS TDS.17 | *18 | DESTINATION MEM,MAILBOX=PLAY19 | PATH,A001,PLAYPLAY,DESTINATION=MEM20 | SEED PATH=A001 TEXT='M01A'21 | PATH,A002,PLAYPLAY,DESTINATION=MEM22 | SEED PATH=A002 TEXT='M02A'23 | PATH,A003,PLAYPLAY,DESTINATI0N=MEM24 | SEED PATH=A003 TEXT='M03A'25 | PATH,A004,PLAYPLAY,DESTINATI0N=MEM26 | SEED PATH=A004 TEXT='M03B'---------------------------------------------------------------

Example 7. Declaration File (PLAY)

This program consists of 3 parts:

• initialization (the loop "MAIN" is introduced from the TEST until the DO statement)• processing of the main body of the program (loop "MAIN" and log off)• error handling.

The initialization fills the sharable registers -1 to -7 with the appropriate initial values (thispart is only executed by the first path to use the program) and transmits the first input toactivate the first transaction. This message is declared as a seed in the DECLARATIONfile.

The main body of the program consists of:

• verifying the output• extracting the output to be used as the next input to PLAY• storing this output (character string) in the first 4 positions of the workspace• sending the stored message to PLAY.

If the current output does not contain a valid input for PLAY the previous input is sent.Once a path has executed the specified number of exchanges it is logged off.

The error handling is activated if a recoverable error condition occurs on the CHECK orCOPY statements. (Details of this can be found in the chapter "Preparing and StartingTILS".) Information useful for debugging is printed on the SYSOUT, then the path isclosed. TDS views this as an abnormal termination of the connection, similar to thefailure of a terminal.

TILS User's Guide

2-28 47 A2 04US Rev05

This type of error could result, for example, from an unexpected output of a length lessthan 7. If this happened, the value in register 22 would be negative when the string"CONNECT" was searched for the output. As negative offsets are not allowed, an error isproduced. If an error label is not specified, an error message is printed and the path isdisconnected. The error label allows further information to be printed so that the sourceof the error can be traced before closing the path.

In the amended version of Example 7, the error labels are replaced by an ON ERRORstatement. This statement specifies an entry point to which execution will go whenever arecoverable error is detected. Note that an error label takes precedence over an ONERROR section.

In this example, the path is closed after the statements following the entry point ERR areexecuted. Attempts can sometimes be made to return from the ON ERROR section tothe statement following the erroneous statement, or to the erroneous statement itself.

TILS Concepts

47 A2 04US Rev05 2-29

2.8 SYNCHRONIZATION

Example 1 introduced six paths with two types of load for a local IOF:

• paths USER1, USER2, and USER3 activate LIBMAINT (library maintenance) facility• paths USER4, USER5, and USER6 activate a COBOL program.

Two programs are in process, each shared by three totally independent paths. A situationcould arise, however, where the paths might be synchronized on an event. You may wishto begin the dialog between the paths and IOF only after all paths have been opened. Todo this, a seventh path must be declared whose only purpose is to notify the other pathsthat they may proceed with their scenario. To simplify the example, assume that thepaths are using IOF to startup.

To avoid a situation where the paths send input simultaneously, each user is given adifferent thinktime using the variable thinktime mode. Thus for each PATH and SENDstatement, the thinktime is determined by the contents of register 17.

--------------------------------------------------------------- 1 | PROGRAM LIBMAIN1,COBOL1, CONTROL 2 | ELAPSED 20,MIN 3 | THINKTIME,VARIABLE,50,60000 4 | LOGON LOG,PROJECT=' ',BILLING=' ',PASSWORD=' ' 5 | DESTINATION SIM,MAILBOX=IOF,NODE=' ' 6 | DEVICE CTR,TYPE=NONE 7 | PATH USER1,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM 8 | PATH USER2,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM 9 | PATH USER3,LIBMAIN1,14000,LOGON=LOG> | DESTINATION=SIM10 | PATH USER4,COBOL1,14000,LOGON=LOG,DESTINATION=SIM11 | PATH USER5,COBOL1,14000,LOGON=LOG,DESTINATION=SIM12 | PATH USER6,COBOL1,14000,LOGON=LOG,DESTINATION=SIM13 | PATH USER7,CONTROL DEVICE=CTR---------------------------------------------------------------


TILS Concepts

47 A2 04US Rev05 2-31

2.9 USING TILS WITH A DSA NETWORK

The previous examples have only described paths connected to applications on the samesite as TILS. However, you can use TILS to load an application executing on a remotesite connected through a DSA network. This situation is, in fact, preferable since it avoidsany direct overhead of TILS on the system under observation.

T ILS

ADATANET

DATANET

IO F

B

P LA Y

C

FEPS

FEPS

FEPS

Figure 2-1. TILS Connected to a DSA Network

To observe site B under a load induced by 100 IOF users, proceed as follows:

Step 1 Specify the load to be submitted based on observing thepresent use of the system and extrapolating for future use.

Step 2 Write SCENARIO and DECLARATION files specifying aDESTINATION statement in the DECLARATION file withMAILBOX=IOF and NODE=' '.

Step 3 Adjust the SCENARIO file starting the different paths eitherindividually or in small groups, in order not to disturb thecurrent operations. Use the TILS LOGFILE to debug theSCENARIO file on site A or B.

Step 4 Install the SCENARIO and DECLARATION files on site A andspecify the NODE parameter as the session control of site B.This name is found in an RSC directive of the CNC of site A.

Step 5 Start TILS on site A when site B is available for observation.

TILS User's Guide

2-32 47 A2 04US Rev05

You may use one TILS to load several applications on the same or on different sitessimultaneously. For example, you could be connected to a third DPS 7000 on the sampleDSA network on which a TDS application, like PLAY, is executing. It is possible to extendthe SCENARIO file by adding the programs for PLAY as in Example 8 and modifying theDECLARATION file by adding program PLAYPLAY in the PROGRAM statement. (SeeExample 9). You must declare a new DESTINATION which specifies mailbox PLAY onthe session control of site C and a new path using the program PLAYPLAY pointing to thisnew DESTINATION.

---------------------------------------------------------------| PROGRAM VIP,PLAYPLAY| ....................| DESTINATION,IOFSITB,MAILBOX=IOF,NODE=H222;| PATH,USERA,VIP,14000,DESTINATION=IOFSITB;| DATA,USERA,LIBMAIN| PATH,USERB,VIP,14000,DESTINATION=IOFSITB;| PATH,USERB,COBOL| .....................| DESTINATION,TDSSITC,MAILBOX=PLAY,NODE=HB01;| PATH,A001,PLAYPLAY,DESTINATION=TDSSITC;| .....................---------------------------------------------------------------

Example 9. Extract From the Declaration File

TILS Concepts

47 A2 04US Rev05 2-33

2.10 COLLECTING DATA

This subsection provides a preliminary view of the output of a TILS session. A morecomprehensive description of TILS output is given in the chapter "TILS Output". For acomplete analysis of system performance, see the System Behavior Reporter.

2.10.1 Type of Data Collected

TILS is a tool which submits a load to interactive and transactional applications (or OSIapplications). To evaluate this load you must know its main characteristics:

• the number of exchanges executed by each path• the number of outputs for each path• the average response time for each path• the maximum response time for each path.

An exchange consists of an input message together with the application's response to thisinput. The response time is defined as the time elapsed between the transmission of aninput from the path to the application, and the reception of the first output in response.TILS also measures the elapsed time between the input and the last output in response.This is called response-time-2.

This data is recorded for each TILS execution and provides a basis for evaluating the loadinduced on the application. Depending on the purpose of the TILS session other datamay be collected:

• dialog may be traced (TRACE and LOGFILE statements)• distribution of response times may be recorded in histograms (HISTOGRAM

statement)• evolution of the exchanges, outputs and response times may be traced chronologically

(CHRONOLOGY statement)• user defined variables may be recorded in histograms.

2.10.2 Tracing Dialogs

You can trace the dialog generated by TILS in two ways, by using the external trace or thelogfile. They produce different information, but can be used at the same time.

• The external trace records each exchange on the SYSOUT. (The external tracegenerates a large overhead, so it should be used for debugging only ).

• The sequential logfile can be used to record dialogs and other events.

A logfile created during a TILS session may be analyzed by TILS using a specialDECLARATION file. This may be done selectively, specifying the name of a path, the rankof a path, or time intervals. The logfile is described in the chapter "The TILS Logfile".

TILS User's Guide

2-34 47 A2 04US Rev05

2.10.3 Histograms

A histogram for a variable's domain of values, is a partition of the variable into equal sizedboxes, plus an overflow box for all values exceeding a given maximum value if the valuesare not bounded. All histograms declared by TILS have 40 boxes, plus a box for theoverflow. The default size of these boxes is 1. A counter, associated with each box, isincremented whenever a measured value falls within the interval denoted by the box. Ahistogram thus represents the distribution of all values of a variable.

You can declare histograms to represent the distribution of response times or othervariables measured by TILS. In the case of distribution of response times, the informationis automatically collected by TILS. A path declaration following a histogram declaration isassociated with it and assumed to be a histogram of response times.

To see the distribution of response times for the paths using IQS in Example 1, and of thelength of all outputs produced by IQS which did not carry the turn, you have to establish 2histograms:

• histogram RESPBAS for the response times of all paths using IQS• histogram LGTBAS for the length of outputs without the turn.

The first histogram, associated with the paths using program IQS1, is declared on line 5before the paths are declared. TILS will fill histogram RESPBAS whenever a responsetime for these paths is measured.

The second histogram is declared after the declaration of all paths to avoid theassociation between the histogram and a path. It must be filled by the programassociated with the paths activating IQS.

--------------------------------------------------------------- 1 | PROGRAM LIBMAIN1, VIP 2 | PATH USER1,LIBMAIN1,14000; 3 | PATH USER2,LIBMAIN1,14000; 4 | PATH USER3,LIBMAIN1,14000; 5 | HISTOGRAM RESPBAS; 6 | PATH USER4,VIP,14000; 7 | DATA USER4,IQS2 8 | SEED USER4 TEXT='IQSBINLIB=IQS.QBIN4,SLLIB=IQS.QSL4,DDLIB=IQS.BIN4;'; 9 | PATH USER5,VIP,14000;10 | DATA USER5,IQS211 | SEED USER5 TEXT='IQSBINLIB=IQS.QBIN5,SLLIB=IQS.QSL5,DDLIB=IQS.BIN5;';12 | PATH USER6,VIP,14000;13 | DATA USER6,IQS214 | SEED USER6 TEXT='IQSBINLIB=IQS.QBIN6,SLLIB=IQS.QSL6,DDLIB=IQS.BIN6;';15 | HISTOGRAM LGTBAS, UNIT=50;---------------------------------------------------------------

Example 10. Declaration File (Histograms)

TILS Concepts

47 A2 04US Rev05 2-35

--------------------------------------------------------------- 1 | :PROGRAM VIP; 2 | :SEND SOURCE=(SEED); ACTIVATES IQS ON PRIV LIB 3 | :ON DATA,COLLECT; MESSAGE WITHOUT TURN IN COLLECT 4 | :LABEL GO-ON; 5 | :SEND SOURCE=(BLOCK,1); 6 | :GOTO GO-ON; LOOP ENDS AFTER "BYE;" IS SENT 7 | * 8 | * ENTER LENGTH IN HISTO. IF OUTPUT WITHOUT TURN 9 | *10 | :ENTRY COLLECT;11 | :HISTOGRAM *3 NAME=LGTBAS;REG 3 = OUTPUT LENGTH12 | :RETURN;13 | :EOD;14 | :BLOCK IQS2; INPUT FOR IQS15 | SELECT VIEW116 | LOAD QUERY117 | EXEC QUERY118 | QUIT19 | BYE;20 | :EOD21 | :PROGRAM LIBMAIN1;22 | LMN SL LIB=TEST.SL.LIB;23 | LIST *;24 | QUIT;25 | BYE;26 | :EOD;---------------------------------------------------------------


Program VIP is used by paths USER4, USER5, and USER6. The first SEND statementactivates IQS. The length of any outputs which do not carry the turn are stored in thehistogram LGTBAS. Such output is treated by TILS only if the ON statement on line 3 isactivated, with the condition:

Output without turn received.

In this case, inputs are sent from the first block associated with the path. When an outputthat did not carry the turn is received, the statements following the entry point COLLECTare executed. Thus the value found in register 3 is entered in the histogram LGTBAS. Bydefinition, this register contains the length of the last output received. The RETURNstatement leaves TILS waiting for the next notification, and the path in the state:

Wait for next output.

2.10.4 Chronological Output

When using TILS, you may observe the chronological evolution of the response times orthe number of exchanges by specifying these variables in the DECLARATION file. Tablesof these results are printed after the simulation phase.

TILS User's Guide

2-36 47 A2 04US Rev05

2.11 ACCESSING FILES

TILS allows you to access members of three (at the most) source language libraries,assigned to the internal file names (IFN) WORKLIB, WORKLIB2, WORKLIB3 in the JCLused to launch TILS. Members of these libraries will be referred to hereafter as files.

Files are accessed sequentially. They may be opened in INPUT, OUTPUT, or APPENDmodes and are referred to through unit numbers. As each unit number is relative to apathname, several paths can use the same unit number, each to access a different file.

The association between a file and a unit number is made through the OPEN statementand is ended by the CLOSE statement. Up to 750 files (250 per worklib) may be openedat a given time for all the TILS sessions, depending on the system's limits. (A single pathcannot, of course, open more than 750 files.)

Accessing files during the simulation phase of TILS will:

• slow down the simulation• increase overhead on possibly critical resources.

You should avoid this facility when using TILS for benchmarks.

Example 11 describes a scenario in which a path sends commands to the fictiveprocessor VBAD. Commands are either executed correctly or are aborted giving a returncode of the form:

RC= VBAD .....

You could start TILS to test VBAD and log return codes. The possible files for this testare shown in Example 11.

--------------------------------------------------------------- 1 | ELAPSED 120 MIN; 2 | COMMON OPEN=2; TO OPEN WORKLIB - MAX 2 SUBFILES 3 | SIZE 255 REGISTER=3; 4 | PATH USERA,LECT,1000; 5 | PROGRAM LECT;---------------------------------------------------------------


TILS User's Guide

2-38 47 A2 04US Rev05

2.12 DECLARING OPERATOR PATHS

You can declare a path with the rights of an operator. Normally, each path connected toIOF waits to receive the IOF message that carries the turn. However, these "operator"paths must issue a "break" before each command to ask for the turn. A path may do thisusing the BREAK command given certain conditions that allow TILS code to be executed.

It is therefore necessary to provide a second path, a control path, to communicate with the"operator" path whenever the operator has to issue a command. A possible way toimplement this is described in the SCENARIO and DECLARATION files of Example 12.

--------------------------------------------------------------- 1 | PROGRAM PGOPER,PGCTRL;*** select program 2 | ELAPSED 60,MIN; 3 | SEQUENCE 20; 4 | LOGON LOG,PASSWORD='OP'; 5 | DEVICE CTRL TYPE=NONE; 6 | THINKTIME VARIABLE 0,100000,UNIT=MILLI;* 7 | * 8 | * Declare operator path with WORKSPACE 100 bytes 9 | * 5 registers and associate entry CMD with the10 | * reception of the TILS command.11 | *12 | SIZE WORKSIZE=100 REGISTER=2;13 | ON COMMAND CMD;14 | PATH OPERATOR2 PGOPER LOGON=LOG;15 | DATA OPERATOR2 OPCMD;*** data to send16 | ON COMMAND;*** CONTROL without ON SECTION17 | PATH CONTROL PGCTRL DEVICE=CTRL;---------------------------------------------------------------


TILS Concepts

47 A2 04US Rev05 2-39

--------------------------------------------------------------- 1 | ****** FOR OPERATOR2 ********* 2 | :PROGRAM PGOPER; 3 | :ASSIGN *17 -1 4 | :LABEL SNDCMD; 5 | : SEND SOURCE=(BLOCK,1) ERROR=ER1; ISSUE CMD. 6 | : GOTO SNDCMD; 7 | :LABEL ER1; ERROR ON SEND 8 | : TEST *6 NE -1 LABEL=REALERR; END OF BLOCK?*** 9 | : SEND SOURCE=(ALPHA,'BYE'); END SESSION10 | :LABEL REALERR;11 | : TERMINATE TILS STATUS=500;12 | ********************************13 | * ON COMMAND SECTION14 | *********************************************15 | :ENTRY CMD;16 | : COPY *18 SOURCE=(COMMAND) TARGET=(WORK);17 | : BREAK; ISSUE BREAK TO OBTAIN TURN!18 | : RETURN; RETURN TO WAIT FOR TURN19 | :EOD;20 | ****** FOR CONTROL **************************21 | :PROGRAM PGCTRL; CONTROL PROGRAM22 | :TILS SOURCE=(ALPHA,'START PATH=OPERATOR2');23 | :LABEL WTCN;24 | : WAIT 1000;25 | : CONTROL *18 PATH=OPERATOR2 IDLE=WTCN;26 | ***** COMMAND LOOP27 | :LABEL GOON;28 | : TILS SOURCE=(ALPHA,'SEND ANY PATH=OPERATOR2');29 | : WAIT 5000;30 | : GOTO GOON;31 | :EOD;32 | ********** COMMANDS TO BE ISSUED ************33 | :BLOCK OPCMD;34 | DC MS/B1035 | DC MS/D50036 | :EOD;---------------------------------------------------------------


The path "CONTROL" determines the behavior of "OPERATOR2". It requests theconnection, waits for the connection to be completed, and communicates with"OPERATOR2" by issuing the TILS SEND command every 5 seconds.

"OPERATOR2" will wait for the turn after it is connected to IOF, then the message that aTILS SEND command has been issued will be received. The path will execute theappropriate ON section introduced by entry CMD.

The first instruction prevents constraints imposed by TILS on the use of the TILS SENDcommand. The next instruction, BREAK, issues an interrupt, ATTENTION, to IOF.Finally, RETURN ends the ON section and OPERATOR2 resumes waiting for outputcarrying the turn. This output is a result of the ATTENTION interrupt transmitted byOPERATOR2.

TILS User's Guide

2-40 47 A2 04US Rev05

2.13 USING TILS WITH OSI SESSION SERVICES

You have seen two categories of paths, those able to dialog with applications such as IOFand TDS, and those that are not able to dialog. There are two other categories of paths,those that use a set of services called the OSI session services (OSI paths), and thoseused with a TDS-HA application (Hybrid paths). If you intend to use TILS with IOF orTDS, you may skip this section and any references to "OSI session services", "OSIpaths", or "Hybrid paths" hereafter.

OSI session services (version 1 and version 2) are implemented under GCOS 7 by theVirtual Communications Access Method (VCAM) at the session services level.Applications that use communication services may chose either the BULL sessionservices internal standard known as Distributed Systems Architecture (DSA) or the OSIsession services which conform to the standard ISO8326 as defined by the InternationalStandards Organisation (ISO).

One TILS session may be used concurrently to maintain dialogs over DSA and OSIsessions. The choice of session services will depend on the applications underobservation. It is not possible to establish OSI sessions to dialog with IOF or a TDSsubsystem.

2.13.1 OSI Path Addresses

Applications using DSA sessions are identified by their "mailbox" and "session control".Applications using OSI session services are identified in a similar manner, by an addressgiven by the "Session Service Access Point (SSAP)", "Transport Service Access Point(TSAP)" and "Network Service Access Point (NSAP)". The SSAP depends on theapplication, while TSAP and NSAP are defined by the system administrator for the givenapplication.

To use OSI sessions, you have to declare a local Session Service Access Point (SSAP)for TILS and associate a PROFILE statement with each path using the services. ThePROFILE statement describes:

• the correspondent of the session• the OSI session services to be used.

TILS Concepts

47 A2 04US Rev05 2-41

2.13.2 An Example Using OSI Services

Example 13 shows how to use TILS with an application running OSI session services. Tosimplify the example, suppose that the application is running on the same DPS 7000system as TILS and that OSI session services are used to exchange data with otherapplications. These applications are identified by its "Session Service Access Point(SSAP)". Only these session services are used:

• establishment of the session• exchange of normal data• no controls specific to the session layer are imposed.

The application expects the corresponding application to send a certification message, inthis case the name of the path. Then it expects an acknowledgement of all messagessent in the form of an echo of the message.

--------------------------------------------------------------- 1 | * 2 | * OSI SESSION SERVICES EXPECT LOCAL SSAP. 3 | * 4 | NAME COMMAND=TILS SSAP=TLSSSAP 5 | * 6 | * THE PROGRAM "ECHO" MUST BE COMPILED. 7 | * 8 | PROGRAM ECHO 9 | *10 | * A TIME LIMIT OF 20 MINUTES IS REQUIRED11 | *12 | ELAPSED 20,MIN13 | *14 | * TILS CHECKS FOR TIMEOUT AT 2 MINUTE INTERVALS15 | *16 | WATCHDOG 2,MIN17 | *18 | * RESERVE REGISTERS19 | *20 | SIZE REGISTER=4;21 | *22 | * PATHS REFERRING TO "KERPRO" USE OSI SESSION23 | * SERVICES.24 | PROFILE KERPRO SSAP=OSIAPP CONNECT=INIT25 | PATH USER1,ECHO,14000,PROFILE=KERPRO26 | PATH USER2,ECHO,14000,PROFILE=KERPRO27 | PATH USER3,ECHO,14000,PROFILE=KERPRO28 | PATH USER4,ECHO,14000,PROFILE=KERPRO29 | PATH USER5,ECHO,14000,PROFILE=KERPRO30 | PATH USER6,ECHO,14000,PROFILE=KERPRO---------------------------------------------------------------


47 A2 04US Rev05 3-1

3. Preparing and Starting TILS

This section contains the information necessary to prepare a TILS session. Descriptionsof each of the statements introduced here are found in the chapters "SCENARIO FileStatements" and "DECLARATION File Statements".

The first subsection explains the rules of syntax for TILS statements. An overview of thestatements of the DECLARATION and SCENARIO files follows. The section finishes withexplanations on how to start TILS after the necessary input has been created.

TILS User's Guide

3-2 47 A2 04US Rev05

3.1 ELEMENTS OF THE TILS LANGUAGE

Before you can start TILS, you must establish the DECLARATION and the SCENARIOfiles. TILS statements follow the same rules of syntax in both of these files.

3.1.1 Conventions in TILS Records

A TILS statement may be spread over several records using the continuation character">" as the last character of the record. A record may contain only one TILS statement.The TILS statement may be delimited by ";". In this case all text following the ";" in therecord is treated as a comment.

Example:

PROGRAM DBTXDBTX,>VIP,>CONTROL

is interpreted as:

PROGRAM DBTXDBTX,VIP,CONTROL

All statements have the following form:

STATEMENTNAME,[parameterlist]

where STATEMENTNAME is the name of a TILS statement and parameterlist is thesequence of positional or keyword parameters. The statement name and parameters areseparated by a comma, sequences of blanks or a combination of both.

All statements, except the implicit form of the SEND statement, may be preceded byblanks. However, the statement indicator, ":", in the first position of a record in aSCENARIO containing explicit TILS statements, is not considered part of the statement.

Some parameters may be used with a keyword or as positional parameters. Once akeyword is used, all following parameters must be introduced by a keyword. A keyword isa reserved word followed directly by "=". The use of keywords is recommended, whereverpossible, for compatibility with future releases and legibility of the program.

The characters * ? % + - = ; ( ) ' all have special meanings within TILS. Thesecharacters, blanks, and digits are allowed as protected characters if they are enclosedwithin single quotes ('). If a quote occurs inside a protected string it must be doubled.

Preparing and Starting TILS

47 A2 04US Rev05 3-3

3.1.2 Parameter Types

Parameters of TILS statements can be of the following types:

Ax Alphanumeric, a character string of limited length, where x isthe number of characters allowed. The first character of thestring must be a letter or a protected character, a singlequote. For example, MYDEV and '123' are valid names,1DEV is not.

A Text, an alphanumeric parameter type not followed by a digitindicating the length of the string, can have a maximum of4096 characters. The first character of the string must be aletter. If text contains a delimiter (a space) or begins with aspecial character, it must be protected by a single quote (').

Example: "all is well" is not valid text because it containsdelimiters (spaces), and "40C1C2" is not valid text because itbegins with a digit.

D A definition of a variable or an object

F Field descriptor, a parameter type that begins with "(" andends with ")". It follow the same rules of syntax as a TILSstatement. This parameter type is only found in statementsof the SCENARIO file.

I Integer, any sequence of digits, preceded or not by a positiveor negative sign, or a sequence of hexadecimal digitsbeginning with a %. For example, -1 and %FFFFFFFF areinteger types.

R Registers are numbered, with or without a positive ornegative sign, and preceded by an * or a ?. When precededby an asterisk, a value is stored in the register named by thenumber following the "*". When preceded by a questionmark, the value is stored in the register designated by thenumber following the "?". Registers are only found instatements of the SCENARIO file.

RR Result register, a register where results are stored.

Reserved word One of a list of reserved words allowed at the position.Reserved words may be used as names elsewhere.

Example: ,DATA={NORMAL|TYPED|EXPEDITED|ALL}

Normal, Typed, Expedited and All are reserved words.

In addition to the parameter type, certain parameters have a code which provides furtherinformation:

ref a reference to an existing objectrefdef a reference to a definition.

TILS User's Guide

3-4 47 A2 04US Rev05

3.1.3 Registers

Registers are used to store and manipulate integer values. Registers are associated witha path (private registers), or shared by all paths (sharable registers). Private registers aredesignated by positive numbers and sharable registers by negative numbers.

Registers may be classified according to their usage as result registers, those used toprovide an address for storing integer values, and value registers, those used when thecontent of the register is to be used directly.

Registers 1 to 16 are always available, are only written to by TILS, and can be read onlyby a path. Registers 9 to 16 used only by paths using OSI session services. You canaccess register 17, the thinktime value. Either the value you enter for thinktime or thedefault value of thinktime stored here. The contents of these seventeen registers aresummarized in this table:

REGISTER CONTENTS

12345

6789

10

11

12

13

14151617

Length of last INPUT TOD of last INPUT (internal format) Length of last OUTPUT TOD of last OUTPUT (internal format) - Byte 1 contains the rank of the erroneous operand - Bytes 2 to 4 contain the offset of the operator in the code segment Error code, see Appendix E TOD of first response (internal format) Length of last accessed BLOCK or SEED -1 path is not OSI path 0 Normal data received 1 Typed data received 2 Expedited data received -1 Path is not OSI path 0 Normal data sent 1 Typed data sent 2 Expedited data sent -1 Path is not OSI path 0 Full SSDU received 1 Begin SSDU part received 2 Middle SSDU part received 3 Last SSDU part received -1 Path is not OSI path 0 Full SSDU sent 1 Begin SSDU part sent 2 Middle SSDU part sent 3 Last SSDU part sent Token control register: Byte1 - data token Byte2 - minor token Byte3 - major token Byte4 - release token Semantics: "FF"X token not available "00"X token not assigned "01"X token assigned Length of last received USERDATA Length of last received USERINFO Reason code of received user exception Value of thinktime


47 A2 04US Rev05 3-5

NOTES: 1. TOD (registers 2, 4, and 7) is stored in multiple of 256microseconds relative to the first event.

2. Register 17 has a special function for thinktime depending on theTHINKTIME statement in the DECLARATION file. All otherregisters must be declared in the DECLARATION file through theSIZE statement for private registers and the COMMON statementfor sharable registers.

Registers may be addressed either directly or indirectly. The register i, where i is aninteger number, is addressed directly by "*i" and indirectly by "?j", where j is a registercontaining the value i.

Example:

:ASSIGN *17 100; register 17 contains "100"

:ASSIGN *18 17; register 18 contains "17"

:SUBTRACT ?18 ?18 100; take the value found inregister 18 and subtract 100from the register designated bythis number.

Register 17 contains 0 after execution of these 3 statements.

3.1.4 Field Descriptors

A field descriptor designates the location of a character string in a field. Through the fielddescriptor, a character string can be accessed by a path executing a statement. Fielddescriptors are used to handle character strings in the same way that registers are usedto handle numeric values.

The field descriptor specifies:

• the location of the character string; the type identifier of the field descriptor provides thisinformation and describes other attributes of the type.

• the offset of the location in the field.• the length of the character string.

The offset and length information is optional. This may be specified directly or through adirect or indirect register. If no offset is specified, offset 0 is assumed. If no length isspecified the implicit length as described in Table 3-2 is assumed.

The general format of a field descriptor is:

(type,[OFFSET=offset-R],[LENGTH=length-R])

The parentheses, "(" and ")", are part of the field descriptor. The "type" parameter mustbe replaced by a valid type and, if necessary, by further attributes as shown in Table 3-1.

TILS User's Guide

3-6 47 A2 04US Rev05

3.1.4.1 Examples of Field Descriptors

• (OUT) names the output buffer associated with the path. The statement "SEND(OUT)" sends the last received output back as input.

• (OUT,OFFSET=0,LENGTH=* 3) denotes the same field as the field descriptor above.

• If a workspace contains DS TILS DS FNPS DS BTNS, then the statement OCLSOURCE=(WORK,9,7) transmits DS FNPS to the operating system.

• (REGISTER,* 18) addresses the content of register 18 as a character string. Forexample, if the register contains "-1", then the statement PRINT HEXASOURCE=(REGISTER,* 18) will print "FFFFFFFF" in the FLD-format.

A reference to a field descriptor of type block or seed moves the current pointer to thenext record of the block or seed respectively. If the end of the block is reached, arecoverable error of code -1 occurs but no error message is printed. A further referenceto the block repositions the current pointer to the beginning of the block. A field descriptorof type block must specify the rank of the block in the DATA statement of theDECLARATION file. This rank may be stored in a register.

Seeds are treated cyclically. When the last seed has been treated, the first seedbecomes the current seed.


47 A2 04US Rev05 3-7

Table 3-1. Field Descriptors (1/2)

Type Structure Param eter Implicit Length

IN

O UT

W O R K

SEED

BLO C K

STR ING

C O M M AND

TELE G R AM

N AM E

D ATE

D YNDAT E

TIM E

P O O L

R EG ISTER

shared/private input buffer

shared/private output buffer

workspace

current seed

current record in block

string defined in theprogram by a stringstatement

command buffer

telegram buffer

path name

date buffer

current date

time buffer

common pool

specified register

length of last input sent

length of last output received

remaining length of the workspace

length of seed text

length of record in block

length of the character string

length of command text

length of telegram text

12 characters

12 characters

12 characters

8 characters (HH:MM:SS)

size of pool

4 characters

-

-

-

-

b lock rankin D ATAsta tem ent

s tringnam e

-

-

-

-

-

-

-

num ber o freg iste r

TILS User's Guide

3-8 47 A2 04US Rev05

Table 3-2. Field Descriptors (2/2)

Type Structure Param eter Implicit Length

A L P H A

H E X A

O U T H E A D

IN H E A D

A C T IV IT Y

U S E R D A T A

U S E R IN F O

O S I_S T A T E

O P E N W A

a lphabetica l lite ra l

hexadec im al lite ra l

rece ived dev ice procedureheade r

sen t dev ice procedureheade r

s truc ture fo r AC T IV IT Ynam es

data rece ived as U S ER -D A T A by O S I pa th

like U S E R D A TA (seeA C TIV IT Y s ta tem en t)

data fo r s ta te o f O SI path

connection param eters fo rD S A pa ths

a lphabe ticcharac te r s tring

hexadec im a ls tring

-

-

-

-

-

-

-

le ng th o f characte r s tring

le ngth o f characte r s tring

le ngth o f s tructu re + 1

16 cha racte rs

16 cha racte rs

512 cha rac ters fo r O S I-V 110 ,24 0 cha rac te rs fo r O S I-V 2

512 cha rac ters fo r O S I-V 110 ,24 0 cha rac te rs fo r O S I-V 2

25 cha racte rs

344 cha racters


47 A2 04US Rev05 3-9

3.1.4.2 Accessing Fields

Fields accessible to paths are listed in Table 3-2. The telegram and command buffers areshared by all paths but are associated only with the path that received a TELEGRAM orSEND command and may only be accessed by this path. The same is true of the sharedinput and shared output buffers. Using (IN) may cause an error if the shared input bufferis used by a path.

The OPENWA field contains the connection parameters. This field is shared by all pathsbut may only be accessed one time by the path currently "owning" it. In practice, this fieldshould be in an ON OPEN or ON RECONNECT section.

Fields may be classified as dynamic if their contents are changed by the program, static ifthey are constant, and variable if the variation is independent of the program.

Dynamic fields are initialized by spaces, except when:

• register 17 is initialized with 0• the workspace initially contains the characteristics of the connection• the device procedure header used for input is initialized with "03004040" (hexadecimal),

the VIP terminal default.

The USERDATA, USERINFO, and ACTIVITY fields are relevant only for OSI paths.

The OPENWA field is relevant only for DSA paths.

TILS User's Guide

3-10 47 A2 04US Rev05

Table 3-2. Fields Accessible to TILS Programs (1/2)

Type Contents Declaration Status

SH A R EDIN P U TBU FF ER

la test inpu tif no p riva teinput buffe r

dynam ic 1 fo r a ll pa ths

SH A R EDO U T PU TBU FF ER

la test ou tpu tif no ou tpu tbu ffe r

like SHAREDINPUT BUFFER

dynam ic

1 fo r a ll pa ths

PR IV A TEIN P U TBU FF ER

la test inpu t defined by S IZEstatem ent

1 per pa th

PR IV A TEO U T PU TBU FF ER

la test ou tpu t defined by S IZEstatem ent

dynam ic 1 per pa th

W O RK-SPACE

buffe r to saveand constructm e ssag es

defined by S IZEstatem ent

dynam ic 1 per pa th

TELE G R AMBU FFER

la tes t rece ivedte leg ram

alw ays present,leng th is 80characte rs


COMMANDBUFFER

text o f lastSE N D com m and

a lw ays presen t, leng th is 256characte rs


SEED IT EM constantcha racte r s tr ingassocia tedw ith pa th

de fined by SE E Dsta tem ent

sta tic -

BLO C KITEM

da ta recordin b lock

de fined inSC EN AR IO file

sta tic -

N A M E username ofpath

a lw ays present,leng th is 12characte rs

sta tic 1 per pa th

Occurence

dynam ic

a lw ays presen t, usedepends on S IZ Esta tem ent, leng thdepends on C O M M O N sta tem en t


47 A2 04US Rev05 3-11

Table 3-2. Fields Accessible to TILS Programs (2/2)

Type Contents Declaration Status

1 fo r a ll pa ths

D ATE da te o f theexpe rim e n t

a lw ays presentlength 12

static 1 fo r a ll pa ths

D YN DAT E curren t da te a lw ays presentlength 12

dynam ic

TIME time of day(hh:mm:ss)

a lw ays presentleng th 8

variab le 1 fo r a ll pa ths

STR IN G constantcharacterstring

defined b y STR IN Gsta tem ent inSCENAR IO file

sta tic -

PO O L area access ib leto a ll pa ths

defined byCOMMONstatement


IN H EAD send dev icep rocedu reheade r

a lw ays present dynam ic 1 fo r ea ch in pu tbu ffe r

OUTHEAD rece ived devicep rocedu reheade r

a lw ays present dynam ic like IN H E AD

AC TIV ITY ACT IV ITYstruc ture

a lw ays present dynam ic 1 per pa th

a lw ays presentU SER D AT Arece ived byO S I pa th


U SERD ATA(--> ACT IV ITYsta tem ent)

a lw ays present dynam ic 1 fo r a ll pa ths

O S I sessionparam e ters

a lw ays present dynam ic 1 fo r a ll pa ths

O ccurence

U SER-D ATA

U SER-INF O

O SI_S TATE

O P E N W A connectionparam ete rs fo rD S A pa ths

a lw ays p resent dynam ic 1 fo r a ll D S Apaths

TILS User's Guide

3-12 47 A2 04US Rev05

3.2 THE DECLARATION FILE

The DECLARATION file is used to declare the number and attributes of paths along withthe global parameters of a TILS session. This file may be a sequential file of anyorganization or preferably, a member of a source language library.

The DECLARATION file consists of TILS statements and comments. A record is acomment if its first position contains an asterisk. TILS statements in the DECLARATIONfile may not contain registers nor field descriptors as parameters.

The statements in the DECLARATION file may be classified according to their relationshipwith the path statement:

Global statements concern parameters of the TILS session and all paths. If aglobal statement is used several times, the last occurrenceis taken into account and a warning is printed.

Hereditary statements specify attributes for all paths following it until the nextHereditary statement. Only the new parameters areaffected.

Pointed statements specify attributes for all paths referred to by name.

Extension statements specify attributes valid only for the path referred to in thestatement.

At least one PATH statement and one PROGRAM statement are mandatory in theDECLARATION file. All other statements are optional. A list of statements in theDECLARATION file and their purposes is shown in the following table. You can findfurther details of all statements in the chapter "DECLARATION File Statements".


47 A2 04US Rev05 3-13

List of Declaration File Statements

IDENTIFICATION STATEMENTNAME modify the name of the OCL command and the

name of the mailbox

PATH DECLARATION STATEMENTSPATH declare a pathGENPATH declare a set of paths

GLOBAL CONTROL STATEMENTSAUTO modify reaction to idle timeDUMP debug syntax analysisELAPSED set time limitOVERFLOW modify reaction to resource overflow on sendPRINT control output of compilation phaseSEQUENCE modify the number of statements executable in

sequenceTIMEOUT modify the reaction to a timeoutTHINKTIME modify the thinktime modeTRUNCATION modify reaction to truncationsWATCHDOG modify surveillance period

DATA COLLECTION STATEMENTSCHRONOLOGY activate collection of chronological dataLOGFILE control writing on the logfileTRACE control tracing on SYSOUTHISTOGRAM define a histogram

CONNECTION STATEMENTSDESTINATION determine correspondentDEVICE associate terminal characteristicsLOGON determine catalog attributesUSERINFO provide additional informationPROFILE provide OSI session attributes

CONTEXT DECLARATION STATEMENTSCOMMON define shared fields and registersDATA associate blocks with a pathSEED associate a seed with a pathSIZE determine private fields

MISCELLANEOUS STATEMENTSGROUP define a TILS name for a group of pathsOCL store OCL for transmissionON determine condition handlingPROGRAM select programs

TILS User's Guide

3-14 47 A2 04US Rev05

3.3 THE SCENARIO FILE

The SCENARIO file describes the dialog between paths and their correspondentsthrough:

• TILS programs• blocks that provide input data for programs.

The SCENARIO file is a sequential file and may be a member of a source languagelibrary. The same SCENARIO file may be used for several TILS sessions.

Records of the SCENARIO file make up programs, blocks or comments. A program isheaded by a PROGRAM statement and ended by an EOD statement. A program may notcontain a BLOCK statement. A block is headed by a BLOCK statement and ended by anEOD statement.

A record belonging to a program may contain:

• an explicit TILS statement (the record begins with " ")• a comment (the record begins with "*")• an implicit SEND statement.

The interpretation of a record belonging to a block depends entirely on the programreading the block.

Example:

Note that the first record does not contain a TILS statement since it is not in a program.

---------------------------------------------------------------:GOTO LABEL:PROGRAM PROG; program starts here:SEND SOURCE=(ALPHA,'EXPLICIT SEND'); Explicit send: PRINT ALPHA,SOURCE=(ALPHA,'YOU MAY INDENT');* COMMENTS LIKE THIS ONE ARE WELCOME:EOD:BLOCK,EXBLK; Block begins here:SEND SOURCE=(ALPHA,'THIS IS NOT A SEND STATEMENT')* THIS IS NOT A COMMENT:EOD---------------------------------------------------------------

Programs which are not selected by a PROGRAM statement in the DECLARATION fileare not compiled.

A list of statements in the SCENARIO file and their purposes is shown in the followingtable. You can find further details of all statements (listed alphabetically) in the chapter"SCENARIO File Statements".


47 A2 04US Rev05 3-15

List of Scenario File Statements (1/2)

PROGRAM AND BLOCK DEFINITIONBLOCK define a blockPROGRAM define a programEOD delimit a block or program

TRANSMISSION STATEMENTSBREAK send an interruptSEND send an input message

OSI SESSION STATEMENTSACTIVITY manage activitiesALARM request a user exception reportCAPABILITY exchange capability dataCON_RESP respond to a connection indicationGIVE_CONTROL give control to correspondentGIVE_TOKEN transfer a tokenOSI_SEND send normal,typed or expedited dataPLEASE_TOKEN request a tokenRELEASE release the sessionRESYNC resynchronizeSYNCPOINT set minor or major synchronization points

CONTROL STATEMENTSLABEL define a labelGOTO branch execution to a labelCONTROL branch according to path stateENTRY define an entry pointCALL activate a subroutineEXTERNAL activate external procedureRETURN end a subroutineON define an ON sectionDO head a loopEND end a loopCHECK compare character strings

SCAN scan for a character stringTEST compare numeric valuesTERMINATE disconnect paths or terminate TILS

COPY AND CONVERSION STATEMENTSCOPY construct a character stringCVBD convert from binary to decimalCVDB convert from decimal to binary

TILS User's Guide

3-16 47 A2 04US Rev05

List of Scenario File Statements (2/2)

REGISTER OPERATIONSADD,SUBTRACT arithmetic operationsDIVIDE,MULTIPLY arithmetic operationsABS,ASSIGN arithmetic operationsRANDOM arithmetic operationsAND,OR,NOT logical operationsLOAD context consultationSHIFT shift bits in register

DEBUGGING STATEMENTSDEBUG trace executionDISPLAY display on TILS operator consoleDUMP debug syntax analysisLOG write on a logfilePRINT print on SYSOUT

SYNCHRONIZATION STATEMENTSEVENT notify a pathSYNCHRONIZE block a path

MISCELLANEOUS STATEMENTSHISTOGRAM enter a value in histogramOCL transmit an OCL commandRESET reset a histogramSET set or consult a JCL switchSTRING define a constant character stringSWITCH modify a consulting pathTILS transmit a TILS operator commandWAIT create a delay

FILE HANDLING STATEMENTSCLOSE close a fileGET read a record from a fileNOTE note current positionOPEN open a filePOINT reposition a fieldPUT write a record


47 A2 04US Rev05 3-17

3.4 HOW TO START TILS

Before TILS may be started, a communication network must be configured by running theCRNETGEN utility. The network description may be reduced to the minimum statementsrequired.

If you are using IOF, start the FEPS/TNS by using the "STSVR" command.

To launch TILS, submit a batch job to GCOS 7. Then assign the DECLARATION file theinternal filename FILE-B and the SCENARIO file the internal filename FILE-C. Both filesmay be either sequential files or members of a source language library. You must use theSIZE statement for the H_TILS step and must specify a value of at least 130K.

If you are using LOGFILE facility (see Chapter 7 "The TILS Logfile"), assign it the internalfilename FILE_L.

If you are using the WORKLIB facility (and/or WORKLIB2, WORKLIB3), assign it to thelibrary accessed by TILS programs.

A sample JCL is shown below:

---------------------------------------------------------------$STEP H_TILS,FILE=SYS.HLMLIB,DUMP=DATA;$SIZE 130;$ASSIGN FILE_B,TILS.LIB,FILESTAT=CAT,SUBFILE=TILS_DECLARATION;$ASSIGN FILE_C,TILS.LIB,FILESTAT=CAT,SUBFILE=TILS_SCENARIO;$ASSIGN FILE_L,TILSLOG,FILESTAT=UNCAT,DVC=MT/T9,MD=LOGTAPE;$ASSIGN WORKLIB,TILS.WORK1,FILESTAT=CAT,SHARE=DIR;$ASSIGN WORKLIB2,TILS.WORK2,FILESTAT=CAT,SHARE=DIR;$ASSIGN WORKLIB3,TILS.WORK3,FILESTAT=CAT,SHARE=DIR;$ENDSTEP;---------------------------------------------------------------

Sample JCL for TILS

If you want to send output to a library member (a subfile), include a statement assigningthe internal file name H_PR to this subfile:

ASSIGN H_PR,TILSOUT,SUBFILE=O_TEST;

All output will be directed to this subfile. If you want output directed to the printer as wellthen you should insert:

SYSOUT H_PR;

before the ASSIGN statement.

TILS User's Guide

3-18 47 A2 04US Rev05

Once TILS is ready for the simulation phase, you will receive the message:

OP04: COMMAND TILS CREATED

If you use a NAME statement, the "OP04" message will contain the relevant OCLcommand instead of "TILS". You may also use the NAME statement to suppress thecreation of an OCL command. If so, you will not receive a message.

You may start the simulation by using the TILS START command. The simulation mayalso be initiated by using the TILS command START as an argument to the OCLstatement of the DECLARATION file, or by the CONNECT parameter of the NAMEstatement.

47 A2 04US Rev05 4-1

4. Running TILS

This section provides information on controlling TILS after the DECLARATION andSCENARIO files have been prepared and the TILS job has been started.

An overview of TILS architecture is presented. This describes how paths are opened andunder what conditions they may execute TILS statements. This explanation assumes youare running TILS using DSA session services. To use TILS with OSI session services,you should also refer to the chapter "Using TILS with OSI Session Services".

An outline of TILS operator commands is introduced. These commands are used tocontrol and observe TILS sessions. The section finishes with a description of howexecution errors are treated and how TILS reacts to marginal events.

TILS User's Guide

4-2 47 A2 04US Rev05

4.1 THE ARCHITECTURE OF TILS

A TILS job has three phases:

• the compilation phase, TILS generates intermediate code and control tables from theDECLARATION and SCENARIO files.

• the simulation phase, TILS loads the correspondents of the paths.• the printing phase, TILS edits and prints data collected during the simulation phase.

If no errors are detected in the DECLARATION and SCENARIO files, the systemmessage OP04 "COMMAND TILS CREATED" is displayed, the compilation phase isended, and the simulation phase begins. If another command identifier was specified inthe NAME statement, that identifier replaces "TILS" in the system message.

If an error is detected during the compilation phase TILS aborts with step completion code10001 (severity 3).

Once the system message is shown, the simulation phase begins. During this phase,TILS is driven by notifications received from the operating system. Thus, TILS is idlewhen it is not treating a notification. TILS must finish processing a notification beforehandling another one. TILS and the notifications form a queuing system where TILS isthe only server and the notifications are the customers. The queue follows the FIFO (firstin, first out) convention.

Notifications may be classified according to their origin as:

• VCAM events (notifications received from the communication system)• operator command notifications (signals that a TILS operator command has been

entered either by the TILS operator, through execution of an OCL statement in aprogram, or as the result of "OCL BEGIN" in the DECLARATION file)

• timer requests (a signal generated by TILS, informing that a specified delay haselapsed)

• notifications generated by EVENT or TILS statements.

A notification may address a particular path or may concern TILS globally. TILS handleseach notification in the same manner, independent of the choice made by the TILS user.You may, however, program specific actions to follow this processing. All actions must beexecuted by TILS on behalf of a specific path.

There are paths that may dialog with correspondents and others, those associated with aDEVICE statement of type NONE, internal to TILS, only capable of executing TILSstatements.

Running TILS

47 A2 04US Rev05 4-3

4.1.1 Opening Paths

To execute an action you have programmed, a path must be opened. To open a pathassociated with DEVICE of type NONE, issue a START command.

Opening a path that can dialog with a correspondent can be done in one of two waysdepending on the DEVICE statement associated with the path.

• If the path is the initiator (CONNECT=INIT in the DEVICE statement), the path isopened after you issue the START command and the connection with the path'scorrespondent has been successfully negotiated.

• If the path is not the initiator (CONNECT=ACCE in the DEVICE statement), the pathmay be opened when a VCAM event is received by TILS requesting the connection ofsome correspondent on the mailbox of the path.

Most frequently you will find the path as initiator as is the case when TILS loads an IOF ora TDS application. The sequence of notifications for this proceed as follows:

• The operator issues a START command. TILS is notified that a command is sent andthen receives it. The command is analyzed and the path(s) concerned are determined.A timer request is issued for these paths. The treatment of a notification (that acommand is sent) is finished and TILS begins to processing the next notification.

• When TILS receives a timer request, it determines that this is a request to connect apath and issues a connection request to the communication system.

• Upon receipt of the connection request, the correspondent (by way of thecommunication system) acknowledges the request. If the acknowledgement ispositive, the path is opened.

If TILS receives a connection request for one of its mailboxes, a search is made for asuitable path to this mailbox. Such a path must:

• be associated with a DEVICE specifying "CONNECT=ACCE" and a type other thanNONE.

• be idle and associated with an entry point in a selected program.

If a path is found, TILS accepts the connection request. If not, the request is rejected.

4.1.2 Executing TILS Statements

During the simulation phase, all paths point to a TILS statement in any one of programsselected for compilation from the SCENARIO file. When a path is opened it may executethe first statement and all subsequent statements following certain conditions.

Programs contain sequences of statements, interpreted one after the other withoutinterruption, until a SEND, SYNCHRONIZE or WAIT statement is encountered. Whenone of these three statements is executed, the chronological order of processing isinterrupted. Note that if you attempt to execute a more than a given number ofstatements (the default is 15) without handing over control, the path is disconnected.

TILS User's Guide

4-4 47 A2 04US Rev05

4.1.2.1 Events That Activate Sequences

Some sequences can be executed without requiring your intervention. For example, if apath is opened but no ON statements occur in the DECLARATION or SCENARIO files,one of several conditions can activate the processing of a sequence:

• the path has not been granted the initial turn. In this case the first sequence isactivated once an output message is received by the path carrying the turn (such as theIOF prompt "S:" if the path is connected to IOF).

• the path has been granted the initial turn or is not able to dialog (path associated with adevice of type "NONE"). In this case the first sequence is activated when the path isopened.

Then, if the sequence is ended by a WAIT statement the next sequence for this path isactivated when TILS is notified that the delay (for this path) has expired. The firststatement of the new sequence is the statement following the WAIT statement.

If the sequence is ended by a SYNCHRONIZE statement, the next sequence for this pathis executed when TILS is notified by an EVENT statement addressed to this path. Thefirst statement of the new sequence is the statement following the SYNCHRONIZEstatement.

If the sequence is ended by a SEND statement, two operations occur unless the thinktimeis suppressed:

• the timer is set with the appropriate thinktime• the message is sent when TILS is notified that the thinktime for the path has elapsed.

The way the following sequence is activated now depends on the SEND statement.When the LEVEL parameter is set (either explicitly or implicitly) to 3, its default value, thepath transmits the turn to the correspondent. When the path receives an output carryingthe turn, the next sequence is activated.

In the case where LEVEL is set to 1, TILS keeps the turn. The next sequence is activatedwhen TILS is notified by the V_CREDIT notification that the path may send the next input.

4.1.2.2 User Activated Sequences

Sometimes specific tasks are required by a TILS program to treat certain events. Forexample, when TILS receives notification that data is to be received for a path, the data isreceived. If this data did not carry the turn, TILS waits for the next notification unless youhave provided a subroutine to treat this specific event. These subroutines are called ONsections.

An execution level, associated with each path, indicates whether or not the path isexecuting an ON section. If the execution level is 0, the path is not executing an ONsection. Note that execution levels higher than 0 only occur if the path is associatedexplicitly with the ON section when the condition occurs. An execution level may bestored in a register using the LOAD statement. (See the table "Execution Level andCondition Handling").

Running TILS

47 A2 04US Rev05 4-5

Execution Level and Condition Handling

CONDITION LEVEL STATEMENT EXECUTED

Normal execution 0 Receipt of an interrupt: - ATTENTION 1 ON ATTENTION - DEMAND TURN 2 ON DMNDTURN - REJECT 3 ON REJECT - ABNORMAL TERMINATION 4 ON ABNTERM - TELEGRAM 10 ON TELEGRAM Recoverable error encountered 11 ON ERROR Connection request or acknowledgement 12 ON OPEN Receipt of TILS Operator Command "SEND" 13 ON COMMAND Receipt of output that does not carry the turn: - Enclosure level 1 14 ON DATA - Enclosure level 2 15 ON DATA Receipt of output indicating end of session (enclosure level 5)

16 ON END

User exception report indication 17 ON ALARM Activity started indication 18 ON ACT_START_IND Activity resumed indication 19 ON ACT_RESUME_IND Activity interrupted indication 20 ON ACT_INTER_IND Activity discard indication 21 ON ACT_DISCARD_IND Activity ended indication 22 ON ACT_END_IND Token request indication 23 PLEASE_TOKEN_IND Token given indication 24 GIVE_TOKEN_IND Receipt of capability data ind. 25 CAPABILITY_IND Receipt of release indication 26 RELEASE_IND Receipt of minor syncpoint ind. 27 MINOR_IND Receipt of major syncpoint ind. 28 MAJOR_IND Receipt of minor syncpoint conf. 29 MINOR_CONF Receipt of resynchronization ind. 30 RESYNC_IND Reconnection of a hybrid path 31 ON RECONNECT Receipt of connection indication 32 ON CON_IND Receipt of timeout indication 33 ON TIMEOUT End of TILS with AUTO=ENABLE 34 ON AUTOEND Session elapsed time limit reached 35 ON ELAPSED

You can change ON sections for specific conditions or dissociate an ON section from apath. This is done to avoid unnecessary overhead in the main line of the SCENARIO FileYou will find further details on the ON statement in the chapter "Using TILS with OSISession Services".

If a path has an execution level higher than 0, then SEND, SYNCHRONIZE, and WAITstatements interrupting the sequence may not be executed. If the execution level is 16 or3, the BREAK statement also cannot be executed.

Like any subroutine, ON sections are ended by the RETURN statement. The RETURNstatement of an ON ABNTERM SECTION closes the path. The RETURN statement alsoends sequences, except in the case of an ON ERROR SECTION which inserts itself intoany sequence. An ON ERROR section is also the only ON section that may be activatedwhile treating another ON section, though this may not be another ON ERROR section.

TILS User's Guide

4-6 47 A2 04US Rev05

4.1.3 Closing Paths

To disconnect a path from its correspondent or to close the path, you must distinguishbetween a normal and an abnormal disconnection.

Normal disconnection occurs if:

• the correspondent sends an output to the path indicating that the last message is sent.(This is the usual case if the correspondent is an IOF or a TDS application).

• the path sends an input specifying LEVEL=5.(You should not use this if the correspondent is an IOF or a TDS application).

Abnormal disconnection is seen by the correspondent in the same way that a powerfailure of a terminal is seen by IOF. This may be the result of several conditions:

• the simulation phase ends while the path is still open.• a RESET command entered for the path specifying that the path is to be disconnected.• the path executes a TERMINATE statement.• the path executes an EOD statement (this could be due to a desynchronization of input

sent by the path and the input expected by the correspondent).• the path executes a RETURN statement without a corresponding CALL statement

outside of an ON section (this usually corresponds to a programming error).• an error, either unrecoverable or one in which neither an error label nor an ON ERROR

section is specified, occurs for the path.• one of several conditions specified in the DECLARATION file occurred (TIMEOUT,

OVERFLOW, TRUNCATION, SEQUENCE statements).• reception of notification (an interrupt of type 3 "V_ABNTERM" ) that the correspondent

has closed the connection abnormally or other notifications from the communicationssystem that the connection cannot be maintained.

While the end of the simulation phase always closes all opened paths, the closing of allpaths does not necessarily end the simulation phase.

4.1.4 Ending TILS

To terminate a TILS session it is sufficient to end the simulation phase. The printingphase follows and once this is completed, the session is terminated.

To end the simulation phase use the TILS operator command STOP. The simulationphase may also be ended when:

• a path executes a TERMINATE statement with the appropriate parameters.• the SEQUENCE, TIMEOUT or TRUNCATION statements specify "TERMINATE" as

the ACTION parameter and the respective conditions are present.• AUTO ENABLE is specified in the DECLARATION file or by a TILS operator command,

closing the last active path.

Running TILS

47 A2 04US Rev05 4-7

If none of these conditions occur, the simulation phase is ended once the time-limitspecified in the ELAPSED statement is detected. This limit can be modified by using theELAPSED command.

TILS may abort:

• on request, when the appropriate TERMINATE statement is executed by a path• when an internal inconsistency is detected• when a process exception occurs.

The exit routine ensures, in all cases, that the printing phase is executed.

4.1.5 File Access

During the simulation phase, a path may access any subfile of the source languagelibraries assigned to WORKLIB, and/or WORKLIB2, and/or WORKLIB3. The statementsOPEN and CLOSE allow a subfile and a unit number to be associated, for a given path.GET and PUT statements allow subfiles to be written to, and read, respectively,.

Subfiles may be either in SSF or SARF format. Subfiles created by TILS are always inSSF format.

Using the file access facility is incompatible with the use of TILS to determineperformance evaluation.

4.1.6 Two Way Simultaneous Mode

This section describes the behavior of TILS when a connection uses VCAM's Two WaySimultaneous (TWS) mode of communications. If you are using TILS to load IOF or aTDS application, you can skip this subsection.

All paths with a DEVICE statement specifying "MODE=TWS" propose TWS mode whenused as initiator ("CONNECT=INIT"). The mode negotiated must be consistent with themode selected in the DEVICE statement otherwise the connection is refused.

Once a path in TWS mode is accepted, it executes the associated program. Thesequence is interrupted by:

• a WAIT statement (resumed when the delay expires)• a SYNCHRONIZE statement (resumed when a TILS event is received)• a SEND statement (resumed when the VCAM notification V_CREDIT is received).

A path in TWS mode never has status 1 (wait for output) or 2 (wait for further output). A"SEND" with "LEVEL=5" is not allowed in TWS mode. All output messages received aretreated only by ON DATA sections.

Connections may only be ended by the TERMINATE statement. The BREAK statementmay be issued, except for the DMNDTURN option.

Most of the statistics gathered are not relevant if the path is in TWS mode. Only thefollowing data is maintained:

TILS User's Guide

4-8 47 A2 04US Rev05

• the counter of input messages sent• the counter of output messages received• the elapsed time since the beginning of the connection• all protected registers except for register 7.

4.1.7 Character Set

By default TILS accepts EBCDIC, ASCII and BINARY dialog. If the negotiation does notselect EBCDIC, all dialog is translated from ASCII to EBCDIC and vice versa before beingsent to you or the correspondent.

You may control this feature by using the CODE parameter in the DEVICE statement. Ifyou specify anything other than "ALL", no translation will be made and you will have torequest a translation by the COPY statement.

4.1.8 Device Procedure Header

TILS proposes the device procedure header option for all paths. If this is negotiated, anarea is reserved to receive this header with each output. The device procedure headermay be consulted through the OUTHEAD field.

All input sent is sent with the device procedure header. The default value usedcorresponds to the standard VIP device procedure header ("03004040"X). You canmodify this value, in the INHEAD field.

4.1.9 Device Attributes

The DEVICE statement allows you to associate certain characteristics, such as the devicetype and subtype, of a terminal, with a path. Those features not specifically changeable inthe DEVICE statement are set to resemble the default device type, DKU7005. If you havespecialized knowledge of VCAM, you may use the OPTION parameter of the DEVICEstatement to adapt the device features to better represent specific terminal types.

Running TILS

47 A2 04US Rev05 4-9

4.1.10 States of DSA Paths

The introduction of several new functions, including Hybrid paths, has created new statesfor DSA paths. These new states are compatible with previous path states and aremapped directly onto previous states. The LOAD and CONTROL statements showprevious states (when there is a corresponding previous state for the new state) unlessthe OPTION parameter in the NAME statement of the Declaration file is set to 1.

The following table shows the correspondence of the previous (or old) and new states ofDSA paths.

Correspondence of Old and New States of DSA Paths

+-----+-----+----------------------------------------------+| NEW | OLD | DESCRIPTION |+-----+-----+----------------------------------------------+| 0 | 0 | path is idle || 1 | 1 | path waits for first OUTPUT || 2 | 2 | path waits for further OUTPUT || 3 | 3 | path waits for thinktime to elapse || 4 | 4 | path waits for delay to elapse || 5 | 5 | path waits for TILS event || 6 | 6 | path waits for credit || 7 | 7 | path waits for acknowledgement of normal || | | end of session (level 5) || 8 | 8 | path waits for acknowledgement of || | | connection request (V_OPENACK) || 9 | 8 | path waits for acknowledgement of abnormal || | | end of session (V_MGCLOSED) as requestor || 10 | 8 | path waits for acknowledgement of abnormal || | | end of session (V_MGCLOSED) as object of || | | the request || 11 | 0 | path waits to request connection || 12 | - | hybrid path waits for reconnection |+-----+-----+----------------------------------------------+

4.1.11 TILS and OSI Session Services

TILS may use OSI session services in parallel with DSA session services to dialog withIOF or TDS applications. Using these services does not affect the basic structure of TILS,the concepts previously described remain valid although the actions taken do varyaccording to the session service used. If you are using OSI session services, refer tochapter "Using TILS with OSI Sessions Services".

Details of the DECLARATION and SCENARIO file statements used with the OSI sessionservices are found in the chapters "SCENARIO File Statements" and "DECLARATIONFile Statements".

TILS User's Guide

4-10 47 A2 04US Rev05

4.2 TILS OPERATOR COMMANDS

A number of commands are available which allow you to change the parameters of a TILSsession and to display information about its progress. You should avoid using thesecommands too frequently while running TILS because they increase CPU overhead. Thistable explains these commands:

+-------------------------------------------------------------+| COMMAND | PURPOSE |+--------------|----------------------------------------------+| AUTO | Modifies conditions for termination || CHANGE | Attaches a new histogram || DEBUG | Traces execution of TILS statements || DELAY | Changes the thinktime || DISPLAY | Displays last INPUT and OUTPUT || DUMP | Traces syntax analysis || ELAPSED | Changes the time limit || GLOBAL | Displays number of connected paths || HELP | Displays syntax and purpose of commands || LOGFILE | Controls level of collection for LOGFILE || RESET | Disconnects paths, resets histograms || SEND | Notifies TILS and fills COMMAND field || START | Requests connection of paths || STATISTICS | Displays statistics of paths || STOP | Ends simulation phase of TILS || THINKTIME | Modifies THINKTIME mode || TRACE | Controls tracing of the dialog || WATCHDOG | Modifies surveillance interval |+-------------------------------------------------------------+

You can use TILS operator commands unless the NAME statement in theDECLARATION file specifically requests that operator commands cannot be created.Once you are notified by the system message OP04 that the OCL command has beencreated, you may enter the command on the TILS console. These commands aredisplayed on the console unless you specify in the NAME statement of theDECLARATION file that they not be displayed.

If the TILS console operates with the GCOS 7 Job Control Language (system variable#JCLCOMP not 0), the commands may be entered by prefixing the TILS command withthe OCL command as follows:

OCL-command commandname,[parameterlist]

where OCL-command is the name of the OCL command as specified in the NAMEstatement or "TILS" if no NAME statement is used. This identifier must be followed by ablank space. (Only the first 4 letters of a command name are significant). The remainderof the string must follow the rules of syntax for TILS statements explained in the chapter"TILS Operator Commands".

If the TILS console is logged to IOF in mode #JCLCOMP 0, the ESCAPE directive of GCLmust be used with the OCL command as argument.

Running TILS

47 A2 04US Rev05 4-11

Example:

To enter the TILS command SEND:

• When not in #JCLCOMP is 0, enter: "TILS SEND 'GO SUB';"

• When #JCLCOMP is 0, enter: "ESCAPE TILS SEND '''GO SUB''';"

NOTE: The entire string is analyzed by GCL before being transmitted to GCOS.

#JCLCOMP is modified by using the MODIFY_PROFILE directive (or MP) of GCL. Thus:

MP GCLMODE=JCL

will set #JCLCOMP to 2 (not 0).

Some commands address individual paths or groups of paths declared as a GROUP inthe DECLARATION file. For these commands, one of the (mutually exclusive) GROUP,PATH or RANK parameters must be used.

TILS User's Guide

4-12 47 A2 04US Rev05

4.3 MARGINAL EVENTS

During the simulation phase events may occur that lie outside the standard scenario.Such events may be:

• program errors (such as an attempt to access an undeclared register)• failure to execute a request (such as opening a path through the START command)• interrupts and other notifications from the communication system.

The occurrence of one of these events does not necessarily mean that the scenario, TILSor the environment has failed. For example, the refusal to open a path without a validuser ID in the site catalog is to be expected. Similarly, you may use the "end of block"error in a TILS program to create infinite loops.

4.3.1 Program Errors

The strategy adopted to handle programming errors consists of disconnecting the pathwhich executed the erroneous statement, unless the error is recoverable and either anerror label or an ON ERROR section is specified. An error label has precedence over anON section.

If an error is recoverable, the error code is saved in register 6 of the path. Register 5contains the rank of the operand for the error that occurred and the offset of theerroneous statement as shown in Figure 4-1. These registers may be stored inunprotected registers and manipulated by the program of the path where the erroroccurred.

reg iste r num ber

BYTE S

1 2 - 4

5 6

error code

offse t of e rroneous s ta tem ent

rank of e rroneous operand

Figure 4-1. Recoverable Error Code Format

A complete list of all error codes can be found in Appendix E. With the exception ofcode -1, all program errors are signalled on the SYSOUT, together with the name of thestatement concerned, the offset of the erroneous statement in the segment of generatedintermediate code, and the operand number.

Running TILS

47 A2 04US Rev05 4-13

4.3.2 Failed Requests

It is possible that when TILS requests an action, such as the opening of a path or thetransmission of an input, that this action may not be executed. Reasons for this areindicated by return codes, printed together with an interpretation of the codes on theSYSOUT, whenever such a failure occurs. There can be up to 5 return codes:

RC1 indicates the system componentRC2 indicates the error categorySTATUS indicates the communication subsystemREASON indicates a refusal to open the pathC_REASON provides a complementary reason for the refusal.

RC1 and RC2 are printed wherever possible in edited form.

The action taken by TILS in response to these failures is independent of any choice youmake except when TRUNCATION, OVERFLOW, and LOGON statements are specified.These statements handle the reaction of TILS in the truncation of output, of resourceoverflow on SEND, and of connection requests.

The most frequent failure encountered is the failure to open a path. The reason for thisrefusal is explained in the TILS output and on the console of the TILS operator when theSTART command is issued. In most cases this failure is due to incorrect catalogattributes of the path.

The reception or transmission of messages, output or input, may be interrupted byinterrupt notifications from the communication system. In this case, a failure is noted butthe interrupted action is resumed by TILS after the interrupt is received. An example ofthis is a telegram with the message "MAIL WAITING" encountered when using IOF withmenus.

4.3.3 Interrupts

Once a path is opened, it may receive various, solicited or unsolicited, notifications fromits correspondent. Unsolicited notifications are called "interrupts". There are four types ofinterrupts:

ATTENTION is not received by paths connected to IOF or TDSapplications.

TELEGRAM is used to transmit text outside of the usual turn. An exampleis "MAIL WAITING" message sent by IOF while menus aredisplayed.

TILS User's Guide

4-14 47 A2 04US Rev05

DMNDTURN indicates that an application is requesting the turn from thepath. If a path is connected to IOF this interrupt is received,after the path issues an ATTENTION interrupt (see BREAKstatement in the chapter "DECLARATION File Statements").

ABNTERM indicates that an application is requesting an abnormal end ofthe session.

The way TILS reacts to interrupts depends on the type of interrupt, and in the case ofDMNDTURN, on the presence or absence of an ON section:

• in the case of a TELEGRAM or ATTENTION, the event is noted and its parameters areprinted. If an ON section is specified it is executed. There is no impact on the state ofthe path.

• in the case of ABNTERM, the path is noted as closed and no TILS statements otherthan those in an ON ABNTERM section may be executed.

• in the case of DMNDTURN, the state of the path is changed to "wait for first output" andfurther reaction depends on the presence or absence of an ON DMNDTURN section:

- if an ON DMNDTURN section is not specified:The interrupted statement (WAIT, SEND or SYNCHRONIZE) is repeated when thepath has received the turn.

- if an ON DMNDTURN section is specified:The interrupted statement is lost. It is assumed that the user provided for recoveryin the ON DMNDTURN section.

47 A2 04US Rev05 5-1

5. TILS and TDS-HA

This chapter explains how to use TILS in an installation with High Availability.

This chapter consists of three topics:

• a summary of TDS-HA• Hybrid paths• using TILS with an TDS-HA application.

For more information see High Availability Concepts.

TILS User's Guide

5-2 47 A2 04US Rev05

5.1 HIGH AVAILABILITY

High Availability, or HA, is a function based on a coupled systems configuration thatreduces the down-time, or unavailability, of HA applications, such as TDS, when GCOS 7fails. A "backup" system automatically detects a system crash, activates the backupapplication, and re-establishes all services without operator intervention.

In an HA installation, all High Availability applications must be declared as protected byHA. This declaration is known as the Complex Description. The Complex Description isprocessed to generate the Complex. A Complex consists of two Members which work incooperation. (A Member is a DPS 7000 system, belonging to a Complex).

A Service is the implementation on the whole Complex of a functional component. AServer is the implementation of a Service on a member. HA Services are made of 2identical Servers:

• One Server is the Active. It runs on a Member and executes the functions of theService.

• The other Server is the Backup. It runs, or actually waits for the Active Server to failbefore participating in the Service functions.

In the Complex shown in Figure 5-1, with Member A and Member B and an HA service (aTDS named TDSx), assume that the TDSx Server is in active state on Member A and inBackup state on Member B.

When a system crash occurs on Member A, the incident is detected and the Takeoverstarts. The Takeover is the process of switching the TDS application from Member A toMember B. During the Takeover, the Server of Member B switches from Backup toActive. All actions needed to switch the TDS application from Member A to Member B areautomatically coordinated.

At the time of a crash, end users are disconnected. They are reconnected when TDSx isrestarted (warm) on Member B.

NOTES: - TILS is not an HA application.

- TILS must be executed on a system which is not a Member of theComplex, therefore the NODE parameter of the DEVICE statementmust contain the name of the system (the Member) on which theHA server is Active.

- If TILS has some paths using IOF and others using TDS-HA on thesame system, those using IOF will not be reconnected when thesystem fails.

TILS and TDS-HA

47 A2 04US Rev05 5-3

A ctiveM em ber

B ackupM e m ber

S ys tem A S ystem B

S ys tem C

TILS

H A C om plex

D a tane t

shareddisks

TD SxTD Sx

Figure 5-1. TILS and TDS-HA

TILS User's Guide

5-4 47 A2 04US Rev05

5.2 HYBRID PATHS

The introduction of TDS-HA requires TILS to allow a path to be reconnected after it hasbeen disconnected. A new class of paths, the Hybrid paths, supports this function.

If a Hybrid path is notified that a correspondent requested an abort of the current session,the notification that the session is closed does not revert the path to the idle state, but setsit to the state "WAIT FOR SESSION RECONNECTION". If a connection request(V_OPENREQ) is received for the mailbox and user name associated with the path (TDS-HA reconnects the user) the request is granted and the path reverts to the state requestedin the connection request.

Figure 5-2 summarizes how Hybrid paths work in coordination with TDS-HA and how theyhandle abnormal terminations.

5.2.1 Declaring Hybrid Paths

Hybrid paths are declared by associating a DEVICE statement with the CONNECTparameter specified as BOTH.

Hybrid paths do not have a password; they must be declared in SITE.CATALOG without apassword. If you declare them with a password, they will not be reconnected by the TDS-HA application.

During the compilation phase the DEVICE statement with CONNECT=BOTH is treated inthe same way as the DEVICE statement with CONNECT=ACCE. All paths sharing thesame DEVICE (CONNECT=BOTH) must be associated with the same mailbox.

The DEVICE statement with TURN=ANYWHERE allows the Message Path Descriptors(MPDs), which are indifferent to the initial turn, to be created. The options selected by thecorrespondent of a path associated with this DEVICE statement determine whether thepath owns the initial turn or not. You can consult register 13 to see the result of thisnegotiation.

5.2.2 Starting Hybrid Paths

If a Hybrid path is selected by the START command (or is in the scope of the CONNECTparameter of the NAME statement) it behaves like an initiator path and is eligible to start ifit is in the idle state.

TILS and TDS-HA

47 A2 04US Rev05 5-5

co nn ectio n reques t

S TA R Tcom m and

C H KP T 1

C H KP T 2

V _ A B N T E R MC R A S H

co nn ectio n reques t

"W A IT F O RR E C O N N E C T IO N "

S E S S IO NR U N N IN G

H ybridP a th

T D S - H A

E nd o f T ILS session

C H KP T 2(las t de fined checkpoint)

(las t com m itted con tex t)

tim e

S E S S IO NR U N N IN G

Figure 5-2. Overview of Hybrid Paths with TDS-HA

TILS User's Guide

5-6 47 A2 04US Rev05

5.2.3 Receiving an Abnormal Termination

The reception of a V_ABNTERM notification indicates that either the transport layer or thecorrespondent requested an emergency session closure. (Figure 5-2 shows an exampleof a system failure on the system where TDS is running). If such an event is notified for aHybrid path the occurrence is memorized and the path changes to the "WAIT FORRECONNECTION" state when V_MGCLOSED is received, instead of reverting to the idlestate.

It should be noted that the context of the path is preserved if it enters in the "WAIT FORRECONNECTION" state.

5.2.4 Closing Hybrid Paths

A Hybrid path may be closed:

• by the exchange of data with enclosure level 5

• by explicitly requesting the disconnection through the TERMINATE statement

• implicitly as a result of an error condition.

5.2.5 Reconnecting Hybrid Paths

If TILS receives a connection request (V_OPENREQ) for a TILS mailbox (this is the casewhen TDS-HA wants to reconnect the user after a failure), it searches the pathsassociated with this mailbox:

• for any path in the state "WAIT FOR RECONNECTION" whose name matches therequested USERID. A path of this type is always a Hybrid path.

• for any path in the state "WAIT FOR RECONNECTION" without searching for theUSERID. If no matching path is found, the requirement that the name should match isdropped.

• if no path waiting for reconnection is found, an acceptor path is searched according tothe standard rules of TILS.

If a Hybrid path is reconnected the new state is determined from the connectionparameters obtained from the session layer. TILS checks whether a statement iscurrently associated with the path. If no statements are associated, the execution of thepath resumes after the entry point associated with it.

TILS and TDS-HA

47 A2 04US Rev05 5-7

A specific entry (ON section) may be associated with the reconnection of a Hybrid path,ON RECONNECT. Inside an ON RECONNECT section, the path may request a jump tothe last checkpoint defined by the CHECKPT statement if the RETURN statementspecifies OPTION as SET. If OPTION=NONE is used for RETURN, then the pathresumes its execution at the statement associated with the path when the path wasdisconnected.

NOTE: TILS is not aware of commitment units performed by TDS. Thus, checkpointsinserted in TILS programs are independent of the TDS CUs. After a failure, theTDS-HA application restarts at the last committed context. Consequently, youmust design your checkpoints in accordance with TDS commitment units (do notforget implicit commitment units) in order to ensure a correct dialoguesynchronization.

5.2.6 Saving the Connection Parameters

When a workspace is allocated, the connection parameters are copied to the beginning ofthe workspace. This feature is maintained for compatibility reasons in the case of initiatoror acceptor paths, but discontinued for Hybrid paths. In order to maintain the functionalitya new field descriptor type, OPENWA, is mapped to a shared area. OPENWA may onlybe accessed once and only once by the path currently "owning" it. In practice this shouldonly be in an ON OPEN or ON RECONNECT section.

TILS User's Guide

5-8 47 A2 04US Rev05

5.3 AN EXAMPLE OF TILS WITH TDS-HA

LANCER is an imaginary TDS-HA application which can be used to demonstrate the useof Hybrid paths.

This examples shows how you can read, write, and delete a record of a file. To do this,start the TX-WRD transaction and then enter:

-> "WRITE FILE1 3 TEXTTEXTTEXT"

to write "TEXTTEXTTEXT" on the third record of file named FILE1.

-> "READ FILE1 3"

to read the third record of file named FILE1. The contents of the specified recordare output.

-> " DELETE FILE1 3"

to delete the third record of file named FILE1.

You might want to test a TX-WRD transaction. To do this, you should write a record,verify that the contents are correct, delete the contents, and then replace the contents with"#CORRECT".

TILS and TDS-HA

47 A2 04US Rev05 5-11

Path User1 activates the transaction TX-WRD and then writes "TESTTEST" in record 5 ofthe file named FILETEST. Then it reads the record and checks the contents by testingthe output buffer. If the contents are correct, the path deletes the record and rewrites"#CORRECT". If the contents are not "TESTTEST", the path goes to the ERRORHANDLING part of the program.

The first statement of the program RUNTDS is an ON RECONNECT statement. WhenTILS is notified that a connection request from LANCER is being sent to User1, andUser1 is in the state "WAIT FOR RECONNECTION" (after a TDS crash), the execution isbranched to the RECONN entry point. Inside this entry point, the statement RETURN withOPTION=SET branches the execution of the main program after the last checkpoint.

Because the path passed the "last checkpoint" (CHECKPT statement) before receivingthe V_ABNTERM notification, TDS and User1 do not restart at the same point. TDSrestarts at the last commitment unit and User1 restarts at the last checkpoint so that theyare synchronized.

TILS User's Guide

5-12 47 A2 04US Rev05

47 A2 04US Rev05 6-1

6. TILS Output

This section describes the output of a TILS session. Different parts of the output originatein different phases of TILS; each phase produces output. Some of the output is governedby choices made in the DECLARATION file.

TILS User's Guide

6-2 47 A2 04US Rev05

6.1 THE COMPILATION PHASE

The compilation phase prepares TILS to simulate a load by reading the DECLARATIONand SCENARIO files and storing the necessary information in main memory. The threetables that may be produced during this phase contain information on:

• the environment of the experiment• how this information is interpreted• the cost (in terms of memory) of executing TILS.

The first table represents information about the system on which TILS is executing. Thistable is always produced.

6.1.1 Listing the DECLARATION File

The second table produced in the compilation phase is a list of the DECLARATION file.Only the first 120 characters of records of the DECLARATION file are printed. You canrequest this table by using the PRINT statement of the DECLARATION file in the form"PRINT DECLARATION ENABLE". You may also disable this statement by selecting"INHIBIT". Thus it is possible to print only part of a DECLARATION file.

If you specify "PRINT CODE ENABLE", information on the SEED and OCL statements isprinted:

• for each seed, the name and rank of its associated path, and the location and length ofthe seed text.

• for each OCL statement, the location and length of text.

6.1.2 Listing the SCENARIO File

You can print the SCENARIO file by using the PRINT statement of the DECLARATIONfile. Only the first 80 characters of records in the SCENARIO file are printed; programsand blocks can be printed if they are selected. The listing produced contains two types oflines according to the choice made in the DECLARATION file:

• source records• intermediate code (This option should be used only in conjunction with BULL

engineering personnel for debugging purposes).

You can request a printout of the source records by choosing the option "PRINTSCENARIO ENABLE" in the PRINT statement of the DECLARATION file. You shouldexecute at least one TILS session with this option. The format of source records isillustrated in Figure 6-1. The offset shown here is referred to if the execution of astatement leads to an error.

TILS Output

47 A2 04US Rev05 6-3

To ta l le ng tho f reco rd

F irs t 80 ch a racte rs o fthe reco rd

offse t o f the gene ra tedin term ed ia te code in hexadecim al

o ffse t o f the gene ra tedin term ed ia te code in decim a l

O ffsetdecim a l

O ffse the xa

Figure 6-1. Format of Source Records

To print the intermediate code, select the option "PRINT CODE" in the PRINT statement.Each source record line is followed by lines of intermediate code. Each line ofintermediate code is preceded by "<CODE>". The format is as follows:

operands

a ll operands o fcurrent operator

T ota l len g tho f re co rd

S ym bo lcode

sym bo lic nam e fo r opera to r

o ffse t o f the gene ra tedin term ed ia te code in hexadecim al

o ffse t o f the gene ra tedin term ed ia te code in decim a l

O ffse tdecim al

O ffse thexa

O pera to r, op tion co des,an d no . o f o peran ds

Figure 6-2. Format of Intermediate Code Records

TILS User's Guide

6-4 47 A2 04US Rev05

The SCENARIO file is printed program by program, block by block. If the PRINT TABLESoption is specified in the DECLARATION file, each selected program is followed by thisinformation concerning the declared labels and literal strings:

• the number of declared labels in the preceding program and the total number.• the origin of each label in the program; i.e. the offset in the segment of generated

intermediate code and the name.• a string definition table providing the local and global index of the literal chains defined

either in the preceding program by the STRING statement, or as field descriptors oftype ALPHA or HEXA, together with their name (if appropriate), length, location andcomplete text.

This information is printed for each program and block regardless of whether they wereselected, or of the options chosen in the DECLARATION file.

6.1.3 Error Reporting

Even if the DECLARATION and the SCENARIO files are not printed, all erroneousstatements are printed, followed by their error diagnostic. Only one error per statementcan be detected. The first characters of an error line are "*** ERROR:".

If the DECLARATION or SCENARIO files contain errors, the execution of TILS ends afterthese files are analyzed and no further output is produced.

6.1.4 Summary Tables

The summary tables list information as it is interpreted by TILS. They are printed only ifthey are specified in the DECLARATION file.

These tables show:

• the attributes of the paths• the fields associated with the paths• the field descriptors declared in the programs• the attributes of programs, blocks, entry points, histograms, and devices• the number of defined objects.

A summary of memory used by TILS is also given, unless TILS is used in test mode. Inthis case, no memory is locked.

TILS Output

47 A2 04US Rev05 6-5

6.2 THE SIMULATION PHASE

During the simulation phase, the messages written on the SYSOUT are eithernotifications of particular events (an interrupt received or an error that occurred) ormessages that you prompt. You generate these messages by:

• activating the external trace• using PRINT statements in the TILS programs.

6.2.1 Format of the External Trace, Dialog Trace, and PRINT Statement

The external trace is active if a TRACE statement is used in the DECLARATION file orentered with a TILS operator command specifying a parameter other than "NONE". Theformat of the external trace is illustrated in Figure 6-3. This format is also produced by thetrace of the dialog and by the execution of the PRINT statement.

T YP E Path na m ePa thR ank

Lengthof text

Time TextT im e

H H :M M :SS

iden tifiesoutpu t

tim e in seconds re la tiveto firs t event

text according to the type

T im e o f Day in hou rs, m inutes and seconds(on ly fo r IN , O U T)

Figure 6-3. Format of Simulation Phase Output

TILS User's Guide

6-6 47 A2 04US Rev05

6.2.2 Explanation of Simulation Phase Output

The TYPE field indicates whether the output is an external trace, a dialog trace, or outputfrom a PRINT statement. The format and content of the TEXT field is dependent on thetype:

BOTH The text field is divided into an alphabetical part of 22characters, a separator of 4 blank characters, and ahexadecimal part containing the hexadecimal representationof the text in 44 characters.

ALPHA The text field is undivided and in alphabetical format.

HEXA The text field is undivided and in hexadecimal format.

The type of line in the external trace is defined in the TYPE field and can be:

OUT The text contains output received by TILS, for a given path,from a correspondent. This output is printed if the TRACEstatement or command has been used with an option otherthan NONE. If a TEXT format is not specified, format isBOTH (ALPHA and HEXA).

IN The same conditions that apply to OUT are true for IN exceptthat the text is input sent by TILS, for a given path, to thecorrespondent.

CMD The text received by TILS contains a TILS operatorcommand. The name and rank of the path are left blank asthe command text is printed before analysis.

FLD The text contains a character string described by the fielddescriptor of a PRINT statement, containing the optionsALPHA, HEXA or BOTH. These latter options determine theformat.

REG The register number and its content (in decimal andhexadecimal format) are printed for each register specified ina PRINT statement containing the REGISTER option.

HD The text contains the number and rank of the consulting pathassociated with the path cited in the PATH and RANK field ofthe line. This type results from the PRINT HEADERstatement.

BRK The text contains an interrupt type and value as well as atelegram text (if appropriate) for an interrupt transmittedthrough a BREAK statement. This type is printed only iftracing is active.

EVT The text contains the name and rank of a path that is theobject of an EVENT statement. This type is printed only iftracing is active.

TLG This type contains the text of the telegram received by a path.

TILS Output

47 A2 04US Rev05 6-7

SEM The semaphore message is printed only if TRACESEMAPHORE has been requested.

INQ The connection parameters of an accepted or requestedconnection (printed only if TRACE SEMAPHORE has beenrequested).

DEB This is a trace of the execution of TILS statements. Theoffset of the currently executed statement and the associatedoperator code are printed. The name and rank of theconsulting path are also printed if they differ from theexecuting path. This type is printed only if the DEBUGstatement or command has been issued with option TRACE.

OSI This is a trace of the execution of an OSI session services.The text indicates the service in question. Some OSI sessionservices generate further lines containing additional textincluding content of sent or received session service data.Output of this type is only generated by paths using OSIsession services.

The TYPE field may also contain:

"*** " to indicate an error during the execution of a TILS statement.

"###" to indicate the failure to execute an action by VCAM.

"**** " to indicate an error which occurred independently of any TILSstatement and which led to the closing of the executing path.

"** " to indicate an error which occurred independently of any TILSstatement but does not necessarily close the path.

The PRINT statement in a program may also be used to print histograms during thesimulation phase. The format of histograms is described in this chapter.

You may trace notifications received by TILS using the option "SEMAPHORE" in theTRACE statement or command. You may also trace the execution of TILS statements bya path or a group of paths using the DEBUG command or statement. You should onlyuse these options in conjunction with BULL engineering personnel.

All other events are reported in free format. Error messages and warnings begin with"** ". Return codes and the offset in the segment of generated intermediate code areprinted in hexadecimal format.

TILS User's Guide

6-8 47 A2 04US Rev05

6.3 THE PRINTING PHASE

When the simulation phase is complete, the printing phase begins and TILS edits theinformation collected during the previous phase. The printing phase is also executed ifTILS aborts or if an internal inconsistency is detected. In the case of such an incident,additional information is printed to assist in debugging (tables showing only the pathexecuting at the time TILS aborted and its consulting path). You can use the DEBUGcommand to get information on other paths.

The output of this phase depends on choices you made in the DECLARATION file. Theprinting phase produces:

• a table of the last input and output messages for the paths, if this information isavailable and was requested in the STOP command

• statistics concerning the activity of the paths

• statistics concerning hybrid paths when this data is available

• histograms of the response time

• chronological tables of response time, throughput, and number of inputs and outputs (ifCHRONOLOGY was requested in the DECLARATION file).

6.3.1 Last Input and Output Tables

The last input and output table is printed only if you specified PRINT in the STOPcommand. If the shared input buffer is used, only the input for the last path that executeda SEND statement is available and printed. If the shared output buffer is used, only theoutput from the last path that received any output is available and printed.

The format of this table is:

tex t of m essagein hexadecim alform at

Pa thR ank

Pa thN am e

Length o fm essage

T im eM essage

a lphabe tica lM essage

hexadecim a l

text of m essage inalphabetica l fo rm at

tim e o f recep tion in seconds,re la tive to the firs t event

Figure 6-4. Format for Last Input and Output in Printing Phase

TILS Output

47 A2 04US Rev05 6-9

6.3.2 Statistics of Path Activities

This table indicates for each path:

• the number of messages transmitted• the number of messages received• the number of exchanges• the elapsed connect time in seconds• the maximum response time in seconds (MAX)• the mean response time in seconds (MEAN)• the throughput in exchanges per second• the maximum response and output time (MAX2)• the mean response and output time (MEAN2).

The response time for a path is calculated as the delay between the transmission of amessage and the reception of the first response.

An exchange is counted once the first message is received after a transmission.

The response and output time for a path is calculated as the delay between thetransmission of a message for a terminal and the reception of the last response.

If a path uses TWS mode, only the transmitted messages, received messages andelapsed connect time counters are maintained.

A retry may occur whenever an input message is rejected by VCAM because not enoughresources could be allocated for the transmission. The number of retries per path areprinted in a separate table, as are the number of telegrams received by each path.

6.3.3 Statistics of Hybrid Paths

Error! Reference source not found.This table indicates for each path:

• the minimum reconnection time in seconds• the mean reconnection time in seconds• the maximum reconnection time in seconds.

The reconnection time is the elapsed time between the moment when the path is closedand the moment when it is reconnected.

If a hybrid path has been reconnected just once, these three reconnection times areequal.

Error! Reference source not found.

TILS User's Guide

6-10 47 A2 04US Rev05

6.3.4 Histograms

A histogram gives the distribution of values of a variable. All defined histograms areprinted. There are 2 types of histograms:

• histograms of response times• user defined histograms.

When a variable is measured, the value determines into which partition of the domain ofvalues the variable should be placed, and the counter associated with this box isincreased. All measured values over 40 units are grouped in one box. If a sequence ofboxes are empty and no value has been measured within their accumulated ranges, thecorresponding lines are replaced by a line of "=".

un it THE UNIT IS :

TOTAL NUMBER = num ber o f m easurem ents

MEAN VALUE : m ean va lue o f m easurem ents

DETAILS OF THE HISTOGRAM CONTENT

BOX >= =< COUNT CUM% ONE STAR=5%, ONE PLUS=0.1%

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

Figure 6-5. Format of Histograms

The last line of boxes where the details of the histogram content are printed may berepeated as shown in Figure 6-5. Where:

BOX is the number of the box>= is the lower limit of values for box=< is the upper limit of values for boxCOUNT is the count of measurements in box% is the percentage of measurements in boxCUM% is the cumulated percentageONE STAR=5%... is the pictogram of percentage.

TILS Output

47 A2 04US Rev05 6-11

6.3.5 Chronological Tables

If the CHRONOLOGY statement is in the DECLARATION file, data is gathered once aminute during the simulation phase. This information is printed for every path in the pathstatistic.

There are three associated tables:

• a list of the measurements for each minute• a list of the cumulated values for the measurements per minute• a list of the response times and the throughput per minute (a chronogram).

The chronology displays, for every minute, the mean response time, mean response andoutput time, mean throughput, number of exchanges, the number of outputs, andindicates whether or not the exchange is complete.

The chronology for the cumulated values contains, for every minute, the mean responsetime, mean response and output time, mean throughput, and number of receivedmessages (outputs) since the beginning of the simulation phase. This table can be usedto calculate, for example, the mean response time for a given part of the simulationjudged to be the most representative.

TILS User's Guide

6-12 47 A2 04US Rev05

47 A2 04US Rev05 7-1

7. The TILS Logfile

This section describes the TILS logfile, a facility that allows you to record a TILS sessionon a sequential file. This file may be read and edited by TILS or by programs (in anylanguage) that you have written.

This section describes:

• the logfile records and their format• how to collect data for the logfile• how to edit the logfile using a special TILS session.

TILS User's Guide

7-2 47 A2 04US Rev05

7.1 DEFINITION OF THE LOGFILE

The logfile is a sequential file (or record) used to log events such as notifications receivedby TILS from the communication system, TILS Operator commands, eventscorresponding to OSI session services, or actions taken by TILS in response notifications.For each type of event there is a corresponding record type.

Logging may take place selectively for different types of events according to predefinedlogging levels. A log record is of variable length and consist of two parts:

• a record header of a maximum of 52 bytes• record text of variable length

The name of the event is not stored on the logfile. The record header containsinformation about the fields in a record. The length of the record header is stored in thefirst field of the header and determines the actual length used. A summary of recordheader formats are in Table 7-1 and record types in Table 7-2.

Table 7-1. Format of the Record Header for Events

Class Name Data Type Leng th Contents

HEADLGLENGTHRECIDTOD

PATHID

RETCODE

LEVEL

H EA D LGLE N G T HTY PTO DN U M BERN AM ER C 1R C 2ST A TU SR EASO NLE VE L

In tegerIn tegerIn tegerIn tegerIn tegerC haracte rIn tegerIn tegerIn tegerIn tegerIn teger

4 4 4 4 412 4 4 4 4 4

length of heade rleng th o f reco rd textiden tifie rT im e O f D ayrank o f pa thnam e o f pa thle ft part o f G 4righ t part o f G 4sta tus (V C A M )reason (VC AM )VC AM m essage leve l

NOTE: The TOD contains the time elapsed since the first event was received. Thisperiod is calculated in multiples of 256*(2**CV) microseconds where CV is theconversion factor stored in the CONTROL record. The default of CV is 0.

The TILS Logfile

47 A2 04US Rev05 7-3

Table 7-2. Logfile Record Types (Excluding OSI)

Event Type Path RC1 RC2 STA RS N LVL TO D LG- TXT

--xxx-x-xxxxxxxx----xxxxx

--xxxxxxxxx-----

--------

--xxxxxxxxx-----

--------

--xxxxxxxxx-----

--------

----x--------------------

--xx8--------------------

-xxxxxxxxxxxxxxxxxxxxxxxx

88 x x x408344255 4 - 8 88 - - 16 - - - - - 16 x - 18 16 16

1 2 4 5 6 7 8 91011121314151718202122232425262728

(1 )(2 )(4 )(5 )(1 )(1 )(1 )(1 ) -(1 )(1 ) - -(6 ) - - - - -(3 )(7 ) -(9 )(A )(A )

CONTROLCOMMANDINPUTOUTPUTH_OPMGH_INQUIREH_ACPMGH_REJMGH_CLSMGH_SENDITH_RECVITV_OPENREQV_OPENACKV_MGCLOSEDV_CREDITV_INTERRUPTV_STARTUPV_SHUTDOWNV_LCCLOSEDSEMAPHOREUSERRECORDTILSEVENTMGCBDVCHDIDVCHDO

NOTES:

In the PTH column:"x" = field exists for this record"-" = field does not exist for this record

In the TXT column:(1) = see the paragraph on record types in this section for information of each type(2) = text of TILS operator command(3) = text of notification received by TILS (semaphore message)(4) = text sent from TILS(5) = text received by TILS(6) = if the path rank is out of bounds, the semaphore message is stored in the text

part and TERNAM contains "************".(7) = the character string specified in the LOG statement(8) = C_REASON (see the section "Failed Requests" in the chapter "Running TILS")(9) = the content of the "message group control block" (for more information contact

BULL engineering personnel)(A) = text contains device procedure header.

TILS User's Guide

7-4 47 A2 04US Rev05

7.1.1 Record Types in the Logfile

Of the types listed in the TYP column:

• 4 to 12 correspond to primitives called by TILS requesting a service from thecommunication system

• 13 to 22 correspond to notifications received by TILS from the communication system

• 26 is logged with types 4, 5, 10, 11, and 12 if the appropriate level has been specifiedfor the data collection through the LOGFILE statement or command.

7.1.2 Format of the Text Field of Record Types

The text field of record types is explained in this subsection. Each record type is followedby a diagram of the fields within the type, then length, type and content data is given.

The TILS Logfile

47 A2 04US Rev05 7-5

CONTROL

+-------------+-----------------------+| DATE | TIME | ENVIRONMENT | CONTROL |+-------------+-----------------------+

DATE field

Length: 12Type: CharacterContents: Date of experiment in MMM DD,YYYY format

TIME field

Length: 12Type: Integer arrayContents: 1. Hour of first event

2. Minute of first event3. Second of first event

ENVIRONMENT field

Length: 24Type: StructureContents: 1. Serial number (integer)

2. Release (4 byte character string)3. Firmware (6 byte character string)4. Reserved (2 blank characters)5. TILSid (integer): 0 TILS, 1 TILS/LS6. Vslogfile (integer) current vs 2

CONTROL field

Length: 40Type: integer arrayContents: 1. Trace: 0 NONE, 1 EXTERNAL, 2 ALPHA, 3 HEXA,

4 SEMAPHORE2. Reserved, currently contains -13. Clock: 0 INHIBIT, 1 CONSTANT, 2 RANDOM, 3 VARIABLE4. Chrono: 0 absent, 1 present5. Chrsize: size of chronological tables6. Elap: time limit in milliseconds7. Watch: surveillance period in milliseconds8. Reserved, currently contains -19. Log: 0 INHIBIT, 1 ENABLE, 2 SEMAPHORE10. CV: conversion factor for TOD

The values stored in these fields are initial values; some may be modified by TILScommands.

The CONTROL record is logged if FILE_L is assigned even if the creation of the logfile isinhibited by the LOGFILE statement in the DECLARATION FILE.

TILS User's Guide

7-6 47 A2 04US Rev05

H_ACPMG & H_REJMG

+--------+------+| VCAMID | MGIB |+--------+------+

VCAMID field

Length: 4Type: IntegerContents: VCAM identifier of message group

MGIB field (H_ACPMG only)

Length: 251Type: Byte stringContents: See MGIB field for H_OPMG

Records of this type are stored whenever TILS accepts (H_ACPMG) or rejects(H_REJMG) a connection request.

The TILS Logfile

47 A2 04US Rev05 7-7

H_RECVIT & H_SENDIT

+---------+----------+----------+| INTTYPE | INTVALUE | TELEGRAM |+---------+----------+----------+

INTTYPE field

Length: 4Type: IntegerContents: Type of interrupt

INTVALUE field

Length: 4Type: IntegerContents: Value of interrupt

TELEGRAM field (only logged if interrupt is telegram)

Length: Maximum of 80 charactersType: Character stringContents: Text of the telegram

TILS User's Guide

7-8 47 A2 04US Rev05

H_OPMG & H_INQUIRE

+------+---------+---------+--------+------+| NODE | MAILBOX | CATALOG | VCAMID | MGIB |+------+---------+---------+--------+------+ (H_OPMG) | MGIB | MPD | +--------+------+

NODE field

Length: 16Type: Character arrayContents: Destination session control (8 positions)

Local session control (8 positions)

MAILBOX field

Length: 16Type: Character arrayContents: Destination mailbox (8 positions)

Local mailbox(8 positions)

CATALOG field

Length: 36 (48 for H_INQUIRE)Type: Character arrayContents: Project (12 positions)

Billing (12 positions)Password (12 positions)

(H_INQUIRE only)Name (12 positions)

VCAMID field (H_INQUIRE only)

Length: 16Type: Integer arrayContents: 1. Identification of message group attributed by VCAM.

2. Internal terminal type identifier3. Pagelength4. Linelength

The TILS Logfile

47 A2 04US Rev05 7-9

MGIB field

Length: 248 (251 for H_OPMG)Type: Byte stringContents: 1. Message group initiation block (H_DCMGI) 42 bytes

2. Offset bytes (H_OPMG only) 3 bytes3. Inquire working area (H_DCINQ) 206 bytes

MPD field (H_OPMG only)

Length: 73 bytesType: byte stringContents: Message path description (H_DCMPD)

A record of type H_OPMG is stored after each attempt to connect a PATH.

A record of type H_INQUIRE is stored if notification of V_OPENACK or V_OPENREQ isreceived.

NOTE: The MGIB and MPD fields should be used only by engineering personnel. If youneed more information on these fields, please contact your BULLrepresentative.

TILS User's Guide

7-10 47 A2 04US Rev05

7.2 LOGFILE EXTENSIONS FOR OSI SESSION SERVICES

This section describes the impact of OSI paths on the TILS logfile. If you are not usingOSI session services (that is, you are running TILS with either IOF or a TDS application)you may ignore this subsection.

Records relative to both OSI session services and other records may coexist withoutrestrictions on a TILS logfile. If the TILS logfile is used, all dialogs and OSI sessionservices are logged. The records of the logfile corresponding to OSI session services arestructured as follows:

• the first 52 bytes contains the record header structured like the record header of typeINPUT or OUTPUT except:

- LEVEL item indicates the "enclosure"- UDATA indicates the offset in the record text of the field indicating the length of

"userdata". It has a length of four bytes and is followed by userdata text.

• the following four bytes contain the token assignment, DATA, MINOR, MAJOR, andRELEASE token.

• the following 62 bytes contain the error description structure (not significant if theRETCODE item is 0).

• the contents of the text depends on the type. This text may contain variable lengthareas usually of "userdata" text. However, the variable length areas have a prefixedlength. The userdata item in the record header indicates the offset of the length of theuserdata in the text field. If this field has the value -1, no userdata is present.

The TILS Logfile

47 A2 04US Rev05 7-11

7.2.1 Format of OSI Record Headers and Record Types

The format of record headers as well as records types associated with OSI sessionservices are shown in Tables 7-3 and 7-4.

Table 7-3. Format of Record Header for OSI Events

C lass N am e Data Type Length Contents

H EA D L GL EN G T HT YPT O DN U M BE RN AM ER C 1R C 2S T AT U SU D A T AL EV ELC O D EM SGC AU SEE VE N TD AT AM IN O RM AJO RR EL EA SE

H E AD LGLE N G T HR E C IDT O D

PA T H ID

R E T C O D EU D AT ALE VE LER R O R

T O KE N S

In tege rIn tege rIn tege rIn tege rIn tege rC ha rac te rIn tege rIn tege rIn tege rIn tege rIn tege rIn tege rC ha rac te rC ha rac te rC ha rac te rC ha rac te rC ha rac te rC ha rac te rC ha rac te r

leng th o f h eade rleng th o f reco rd te xtiden tifie rtim e o f d ayra nk o f pa thnam e o f p a thle ft pa rt o f G 4righ t part o f G 4*** unused ***o ffse t o f use rda taenc losureerro r codeerro r m essa geerro r causeerro r even tVa lue :"FF"X no t ava ilab le"0 0"X no t concern ed"0 1"X concern ed

4 4 4 4 412 4 4 4 4 4 2302010 1 1 1 1

TILS User's Guide

7-12 47 A2 04US Rev05

Table 7-4. OSI Record Types (1/2)

Event Type Explanation

S _ C O N _ R E QS _ C O N _ IN DS _ R E S PS _ C O N _ C O N FS _ D T _ R E QS _ D T _ IN DS _ T D _ R E QS _ T D _ IN DS _E X _R E QS _E X _IN DS _R E L _R E QS _R E L _IN DS _ R E L_ R E S PS _ R E L_ C O N FS _ C D _ R E QS _C D _ IN DS _ C D _R E S PS _ C D _ C O N FS _ A C TS _ R E QS _A C T S _ IN DS _ A C T I_R E QS _ A C T I_IN DS _A C T I_R E S PS _ A C TI_C O N FS _ A C TD _ R E QS _ A C T D _IN DS _A C T D _R E S PS _ A C TD _ C O N FS _ A C TR _ R E QS _ A C T R _IN DS _ A C TE _ R E QS _A C T E _ IN DS _ A C T E _R E S PS _ A C TE _ C O N FS _ P A B _ IN DS _U A B _R E Q

301129201130302149303134304133305163205164306135206136307147308140208141309142209143310128311155211156161312

connection requestconnection ind icationconnection responseconnection confirm ationno rm al da ta transfe r requestno rm al data trans fer ind icationtyped da ta trans fer requesttyped da ta transfer indicationexped ited data transfer requestexped ited da ta transfer ind ica tionre lease requestre lease ind icationre lease responsere lease confirm ationcapab ility da ta transfer requestcapab ility da ta transfer indicationcapab ility data trans fer responsecapab ility da ta transfer confirm ationactiv ity s ta rt requestactiv ity s ta rt ind ica tionactiv ity in te rrupt requestactiv ity in terrupt ind icationactiv ity in te rrup t responseactiv ity in te rrupt con firm a tionactiv ity d iscard requestactiv ity d iscard ind icationactiv ity d iscard responseactiv ity d iscard confirm ationactiv ity resum e requestactiv ity resum e ind ica tionactiv ity end requestactiv ity end indica tionactiv ity end responseactiv ity end confirm a tionprovider abord indicationuser abort request

The TILS Logfile

47 A2 04US Rev05 7-13

Table 7-5. OSI Record Types (2/2)

Event Type Explanation

S_UAB_INDS_GT_REQS_GT_INDS_PT_REQS_PT_INDS_MASY_REQS_MASY_INDS_MASY_RESPS_MASY_CONFS_MISY_REQS_MISY_INDS_MISY_RESPS_MISY_CONFS_RSYN_REQS_RSYIN_INDS_RSYN_RESPS_RSYN_CONF

162313158314149316151216152317153217154318137218138

user abort ind ica tiongive token requestg ive token ind ica tionplease token requestp lease token ind icationm a jor syncpo in t requestm ajor syncpo int indicationm a jor syncpo in t responsem ajor syncpo int con firm ationm inor syncpo in t requestm inor syncpo int indicationm inor syncpo in t responsem inor syncpo int con firm ationresynchronisa tion requestresynchron isation indica tionresynchronisa tion responseresynchron isa tion confirm ation

NOTES: 1. See the following section "Format of the Text Field of OSI RecordTypes" for an explanation of individual record types.

2. The mnemonics (codes) given above may not be used in theEVENT statement of an EDIT session DECLARATION file.

3. Events with an identifier larger than 300 correspond to requests.Events with an identifier between 200 and 300 correspond to aresponse.

7.2.2 Format of the Text Field of OSI Record Types

The text field of OSI record types is explained in this subsection. Each record type isfollowed by a diagram of the fields within the type; the length, type and content data isgiven.

TILS User's Guide

7-14 47 A2 04US Rev05

S_CON_REQ, S_CON_IND

+-----------+----------+| CON_STRUC | USERDATA |+-----------+----------+

CON_STRUC field

Length: 1002 bytesType: StructureContents:1-4 reserved for TILS5 "00" accept connections

"01" request connections"02" controlled accept

6-8 reserved for future use9 SSAP_FLAG10-11 SSAP length12-27 SSAP identifier28 TSAP flag29-60 TSAP identifier61-62 number of entries in NSAP array63-503 NSAP array - each element consists of 2 bytes for

the length and 20 bytes for the NSAP identifier.504-505 maximum size of Session Service Data Units (SSDU)506 01 HALF_DUPLEX507 01 FULL_DUPLEX508 must be zero509 01 typed data510 01 negotiated release511 01 minor synchronization512 01 major synchronization513 01 resynchronization514 01 expedited data515 01 activity management516 01 capability data517-521 reserved for future use522-525 initial syncpoint number526 01 syncpoint number used527-529 reserved for future use530 01 data token assigned531 01 minor token assigned532 01 major token assigned533 01 release token assigned534-535 length of Quality Of Service parameter536-600 Quality Of Service601-602 number of entries in array of conflicting functional units603-1002 array of conflicting functional units (each element is 20 bytes

long).

The TILS Logfile

47 A2 04US Rev05 7-15

USERDATA field

Length: length of userdata + 4Type: structureContents: 1-4 length of userdata

5-* userdata text

TILS User's Guide

7-16 47 A2 04US Rev05

S_DT_REQ, S_DT_IND,S_TD_REQ, S_TD_IND,S_EX_REQ, S_EX_IND,S_CD_REQ, S_CD_IND

+--------+| TEXT |+--------+

TEXT field

Length: length of text as indicated in the headerType: character stringContents: Session Service Data Unit ("Normal", "Typed", "Expedited" or

"Capability" according to the record type)

The TILS Logfile

47 A2 04US Rev05 7-17

S_CD_RESP, S_CD_CONF

+--------+----------+| SSDU | USERDATA |+--------+----------+

SSDU field

Length: length is text length if the USERDATA indicator is -1otherwisethe length is obtained by subtracting the userdata length fromthe text length.

Type: character stringContents: Capability Session Service Data Unit

USERDATA field

Length: length of userdata + 4Type: structureContents: 1-4 : length of userdata

5-* : userdata text

TILS User's Guide

7-18 47 A2 04US Rev05

S_CON_RESP, S_CON_CONF,S_ACTI_REQ, S_ACTI_IND, S_ACTI_RESP, S_ACTI_CONF,S_ACTD_REQ, S_ACTD_IND, S_ACTD_RESP, S_ACTD_CONF,S_ACTE_REQ, S_ACTE_IND, S_ACTE_RESP, S_ACTE_CONF,S_REL_REQ, S_REL_IND,S_UAB_REQ, S_UAB_IND,S_PT_REQ, S_PT_IND

+----------+| USERDATA |+----------+

USERDATA field


5-* userdata text

The TILS Logfile

47 A2 04US Rev05 7-19

S_ACTR_REQ, S_ACTR_IND,S_ACTS_REQ, S_ACTS_IND

+--------+----------+| TEXT | USERDATA |+--------+----------+

TEXT field

Length: 2 bytesType: structureContents: 1-2 length of activity identifier

3-8 activity identifier9-10 length of previous activity identifier11-16 previous activity identifier

NOTE: These values depend on the session services used.

USERDATA field


5-* userdata text

TILS User's Guide

7-20 47 A2 04US Rev05

S_REL_RESP, S_REL_CONF

+--------+----------+| TEXT | USERDATA |+--------+----------+

TEXT field

Length: 4 bytesType: structureContents: 1-3 reserved for future use

4 150 release accepted151 release rejected

USERDATA field


5-* userdata text

The TILS Logfile

47 A2 04US Rev05 7-21

S_MASY_REQ, S_MASY_IND, S_MASY_RESP, S_MASY_CONF,S_MISY_REQ, S_MISY_IND, S_MISY_RESP, S_MISY_CONF

+--------+----------+| TEXT | USERDATA |+--------+----------+

TEXT field

Length: 8 bytesType: structureContents: 1-4 syncpoint number

5-7 reserved for future use8 0 explicit confirmation

1 optional confirmation


USERDATA field


5-* userdata text

TILS User's Guide

7-22 47 A2 04US Rev05

S_RSYN_REQ, S_RSYN_IND, S_RSYN_RESP, S_RSYN_CONF

+--------+----------+| TEXT | USERDATA |+--------+----------+

TEXT field

Length 12 bytesType: structureContents: 1-4 syncpoint number

5 data token assignment6 minor token assignment7 major token assignment8 release token assign.9-11 reserved for future use12 restart

1 abandon2 set


USERDATA field


5-* userdata text

The TILS Logfile

47 A2 04US Rev05 7-23

7.3 COLLECTING DATA

To use the logfile, the internal filename FILE-L must be assigned to the sequential filecontaining the logged information.

Example:

$STEP H_TILS,FILE=SYS.HLMLIB,DUMP=DATA;SIZE 130;ASSIGN FILE_B,TILS.LIB,FILESTAT=CAT,SUBFILE=DECLARATION;ASSIGN FILE_C,TILSLIB,FILESTAT=CAT,SUBFILE=SCENARIO;ASSIGN FILE_L,TILSLOG,DVC=MT/T9,MD=TILSTAP;$ENDSTEP;

This is an example of JCL. The logfile could have been allocated as a disk file instead ofusing a tape file, as in the next example:

Example:

PREALLOC MYLOG, DVC=MS/M452, GLOBAL=(MD=MYDISK,SIZE=5),FILESTAT=UNCAT, UFAS=(SEQ=(CISIZE=8192,RECSIZE=4096,RECFORM=V));

The choice of CISIZE and RECSIZE depends on the expected record sizes. TILS splitslogical records if their text fields exceeds 16K.

The maximum size of the header is 52 bytes when OSI session services are not used,otherwise the header size is 632 bytes. The first record contains the total text length.Each following record has a record type of "-1" and contains its length in bytes.

To begin collecting data, you must use a LOGFILE statement specifying the parametereither as:

• ENABLE, to log all events except the types "SEMAPHORE" and "MGCB", or as• SEMAPHORE to log all events

If you assign FILE-L, the control record is written to the logfile regardless of theassignment in the LOGFILE statement.

Logging may be stopped and started again by the LOGFILE command. This commandaffects all paths. However, you can select to print any or all path(s).

If an error occurs when accessing the logfile or if the file is full, the file closes and remainsunavailable for the rest of the application. A warning is issued when this happens.

TILS User's Guide

7-24 47 A2 04US Rev05

7.4 EDITING THE LOGFILE

The logfile may be edited by:

• a user defined program written in COBOL, QUERY, or another programming language.• TILS using an EDIT session.

7.4.1 Using TILS to Edit

An Edit session is specified by an EDIT statement in the DECLARATION file. An editsession is used exclusively to edit part or all of the logfile from a previous simulation.Comments may be inserted and appear on the list after the editing parameters. Acomment line begins with a "*" and may not be longer than 110 characters.

Once an EDIT statement is encountered in the DECLARATION file, only the followingstatements are permitted:

• the EDIT statement• the SELECT statement• the EVENT statement• the DUMP statement.

Several EDIT statements may be used in one edit session. No sorting of the logfilerecords takes place so the editing of the file follows the sequence of the records on thelogfile.

Further details of these four statements are in the chapter "Logfile Edit Statements".

Edit sessions and other TILS sessions are mutually exclusive. No SCENARIO file isneeded for an edit session.

The DECLARATION file corresponding to an edit session is printed only if a "PRINTDECLARATION" statement has been used before the first EDIT statement. The relevantparameters for each session are, however, always printed before the session begins. ADECLARATION file not belonging to an edit session may not contain EDIT, SELECT, orEVENT statements.

The TILS Logfile

47 A2 04US Rev05 7-25

7.4.2 Editing Format

All records, except those of type 1 (CONTROL) are edited according to the format shownin Figure 7-1.

ID TOD TOD0

rank o f path in session file

nam e o f pa th

TO Dhh:m m :ss

14 18 33 46 54 110R ank Name Length Text

Identifies type o f event (see Tab le 7 -2 fo r lis t). A ny fo llow ing linesare b lank excep t fo r the R ecord T ex t fie ld

by tes

TO D in m illiseconds,re lative to firs t event

Figure 7-1. Format of the EDIT Records

When a return code, recorded for an event, indicates a failure, it is printed.

The control record is only edited once for each EDIT session.

Two tables are created from each EDIT session. The first table summarizes theenvironment of the logged TILS such as the date, the time of the first event, software, andfirmware releases. The second table describes the initial parameters of TILS. Some ofthese parameters may be changed in the course of the simulation; the tracing mode,activation of the chronology, the size of the chronological tables, and the time limit.

TILS User's Guide

7-26 47 A2 04US Rev05

47 A2 04US Rev05 8-1

8. Using TILS with OSI Session Services

This section explains how to run a TILS session using OSI session services. If you areusing TILS with IOF or a TDS application, you may skip this section.

Both OSI Session Services versions, OSI-V1 and OSI-V2, are supported under GCOS 7.

It is assumed that you are familiar with TILS, if not you should read the first four chaptersof this manual before beginning this section. Descriptions of the statements introducedhere in the chapters "SCENARIO File Statements" and "DECLARATION File Statements".

For a detailed explanation of how to using OSI session services on GCOS 7, refer to theVCAM-ISO User's Guide.

TILS User's Guide

8-2 47 A2 04US Rev05

8.1 OVERVIEW

Applications running under GCOS 7 may dialog with other applications on the same or ona distant host, or with terminals using a VCAM (Virtual Communications Access Method)session service.

VCAM provides the logical links between applications or between an application and aterminal. These links are referred to as sessions. You establish a link, or open a session,and you dissolve or close the session.

VCAM provides two different sets of session services:

• DSA sessions, the Distributed Systems Architecture (DSA) standard• OSI sessions, the International Standards Organization (ISO) standards.

The TILS application generates sessions between itself and other applications. Eachsession is represented by a TILS object called a path. In general, these sessions areseen by applications as dialogs with a terminal. The connection between TILS and aterminal is referred to as "connecting a path", and indicates that a session represented bya path is opened between TILS and the application.

A path can be either idle (closed) or connected (opened). An open path is either waitingfor an event or executing a program. A path may revert to the idle state either when anevent is received indicating that the session is to be closed, or when some other conditionrequiring the session to end (a TERMINATE statement, end of simulation, orunrecoverable error) is detected.

There are four types of path:

• those able to dialog with an application, using the DSA session layer (DSA paths)• those not able to dialog (Control paths)• those that dialog using OSI sessions (OSI paths)• those used when connected to TDS-HA (Hybrid paths).

Using TILS with OSI Session Services

47 A2 04US Rev05 8-3

8.2 TILS AS OSI SESSION SERVICE USER

TILS may use OSI session services if at least one local Session Service Access Point(SSAP) is declared. This may be done either in the NAME statement of theDECLARATION file or in individual PATH statements.

At least one path in TILS must be associated with a PROFILE statement. This statementdefines the OSI session services that the path as well as the application may use. EachOSI path is associated with the SSAP defined by default in the NAME statement unlessan SSAP is indicated by the SSAP parameter in the PATH statement.

An application is identified by an address, the SSAP, and in the case of an application ona remote site, by a Transport Service Access Point (TSAP) and a list of NSAPs (NetworkService Access Point).

If at least one path is associated with an SSAP, TILS opens the SSAP at the end of thecompilation phase. These access points may not be modified during the execution ofTILS.

8.2.1 Types of OSI Session Services

During the simulation phase the OSI paths may use the following OSI session services:

• request a connection with another OSI session service user.• transfer "Normal", "Typed", "Expedited", and "Capability" data• set "minor" and "major" synchronization points• request or negotiate resynchronization• start, end, resume, discard, and interrupt "activities"• request that a connection be released• request that a connection be aborted.

TILS User's Guide

8-4 47 A2 04US Rev05

8.2.2 OSI Session Services Versions

Two OSI session protocol levels are supported by TILS: OSI session services version 1and version 2.

OSI session version 2 extends the session services offered by VCAM by allowing:

• the negotiation of the ISO protocol level supported (version 1 or 2).• the possibility of exchanging userdata of lengths of up to 10 Kbytes (512 bytes for

version 1).• the segmentation of Capability data similar to the segmentation of Normal and Typed

data.

In the Declaration file, set the LEVEL parameter of the PROFILE statement to indicate theprotocol level supported by TILS:

LEVEL=1 OSI sessions version 1LEVEL=2 OSI sessions version 2LEVEL=3 OSI sessions as determined by the correspondent.Error! Reference source not found.

8.2.3 Requesting OSI Session Services

The "user exception reporting" OSI session service is not supported by TILS. Except for"provider abort", all session services must be requested by one or the other sessionservice user. When you request a session service, you are the "initiator". When youaccept a session service, you are the "acceptor".

There is a difference between confirmed and unconfirmed services. An unconfirmedsession service is complete once the acceptor is notified by the session service layer andacknowledges this notification. This acknowledgement is called an "indication".

A confirmed session service requires a "response" from the acceptor. This service iscomplete once the initiator acknowledges the notification by sending a second message,a "confirmation".

TILS requests session services according to user programs or TILS operator commands.TILS always issues implicit indications and confirmations. In the case of confirmedsession services, TILS provides default responses. You can program TILS to overridethese responses.

The session is aborted when requests, indications, responses, or confirmations arerejected by the session services provider. These types of errors are reported in the outputof the TILS simulation phase.

The first line of the output report follows the general format of error messages in thesimulation phase. The first characters, "###", containing the return code and the errorcode specific to the OSI session layer. All other information provided by the OSI sessionlayer is printed in a free format on the following lines.


47 A2 04US Rev05 8-5

8.3 PROGRAMS ASSOCIATED WITH OSI PATHS

Each OSI path is associated with a program defined in the SCENARIO file. Theseprograms are sequences of TILS statements beginning with a statement that defines theentry point of the path, and followed by other TILS statements. Programs are executedonly when the path has the right to request the transfer of data. A TILS program executesthe sequences following the PATH statement (in the DECLARATION file). An OSI pathexecutes a program once the connection request is positively confirmed or once itaccepts a connection request.

If a path uses full duplex, the default option, programs are executed when the flow controlmechanism of the session layer allows data to be transmitted. The execution of programsis thus independent of OSI session services.

If the path uses half duplex, TILS executes only those statements outside of ONCONDITIONS when the path owns the data token. There is an exception to this. Unlessthe communications are synchronized, if a statement requests "confirmed" OSI services,the path must wait for the confirmation before transmitting messages.

8.3.1 Executing Statements

A TILS program executes sequences of statements following the entry point declared inthe PATH statement (in the DECLARATION file). All statements are executed until anasynchronous statement is encountered. Asynchronous statements suspend thesequence and allow TILS to treat events on other paths. The following table summarizesasynchronous statements and shows the event that TILS waits for to continue execution.

TILS User's Guide

8-6 47 A2 04US Rev05

Table of OSI Asynchronous Statements

---------------------------------------------------------------STATEMENT CONDITION

WAIT waits the specified time then resumes execution once thedelay has elapsed

SYNCHRONIZE - waits for a TILS notification sent by an EVENT statement

OSI_SEND with CATEGORY=NORMAL- waits for thinktime to elapse- waits for credit notification- waits for data token if HALF_DUPLEX SEND- waits for thinktime to elapse- waits for credit notification

OSI_SEND with CATEGORY=TYPED (outside ON SECTION)- waits for credit notification

OSI_SEND with CATEGORY=EXPEDITED (outside ON SECTION)- waits for Expedited credit notification

GIVE_TOKEN with DATA_TOKEN=YES- waits for DATA_TOKEN

ACTIVITY option END, INTERRUPT or DISCARDCAPABILITYSYNCPT option MAJORRESYNCALARMRELEASE - waits for confirmation---------------------------------------------------------------

Unless otherwise indicated TILS statements are executed when a path has the right tosend data.

You may attach ON SECTIONS to specific events. If the execution level associated witha path is 0, the path does not execute an ON SECTION. If the execution level is not 0, itis positive. When the execution level is positive, a statement being executed cannot beasynchronous. For more information on execution levels and the corresponding ONstatements, see Appendix B.


47 A2 04US Rev05 8-7

8.3.2 Categories of Paths

TILS statements can be classified according to the category of path which executes thestatement. Attempting to execute a statement in the wrong category leads to anunrecoverable error.

Table of Paths and Corresponding Statements

---------------------------------------------------------------CATEGORY STATEMENTS

OSI paths all statements except for BREAK. The SEND statement isreinterpreted as OSI_SEND statement

DSA paths all statements except ACTIVITY, CAPABILITY,GIVE_CONTROL, GIVE_TOKEN, PLEASE_TOKEN,OSI_SEND, ALARM, CON_RESP, RESYNC and SYNCPT

CONTROL paths all statements which may be executed by a DSA statementexcept for BREAK and SEND

---------------------------------------------------------------

Some OSI services own tokens. Attempting to execute statements without these tokenscauses errors recoverable through an error label or an ON ERROR section.

TILS User's Guide

8-8 47 A2 04US Rev05

8.4 CONNECTING TO OSI SESSION SERVICES

OSI paths use OSI session services either by requesting the connection to another SS-user or by accepting a connection request. This type of request is valid if the SS-user inthe PROFILE statement is defined as an initiator of connections. These requests can bemade if:

• the OSI path is specified by the TILS operator command START. (Note that the syntaxof the START command is not affected when an OSI path is connected.)

• the automatic connection of n paths is requested in the NAME statement, and the rankof the OSI path in the list of paths is less or equal to n.

Each OSI path proposes a set of session services. These services are selected in thePROFILE statement of the DECLARATION file and correspond to the different "functionalunits" defined in the ISO norm. By default, an OSI path does not allow tokens to be usedand is thus restricted to the exchange of Normal data in full duplex mode. If an SS-useraccepts the connection but tries to negotiate a different mode, TILS requests a user abort.

When a connection request is not accepted, the ON_REJECT section of an OSI path isactivated and the path becomes idle. When TILS is the object of a connection request, itcan only accept if an idle path associated with the addressed SSAP is available. Whenthis happens, you have two possibilities:

• ignore the attributes of the path and accept the request regardless of the functionalunits required by the initiator of the connection.

• control the functional attributes selected by examining the first idle path that may acceptthe connection and compare its functional units with those described in the PROFILEstatement of the initiating path.

- If the units do not match, the connection request is rejected. If the connection isrejected, the initiator of the connection request receives the message"USER_REJECTION" and no further attempts are made to find a path whoseattributes match the requested functional units.

- A list of functional units requested but not selected in the PROFILE statementassociated with the path, is printed.

8.4.1 Negotiating the Connection

A connection indication can be received in an ON condition, the ON CON_IND section.To respond to the request, use the CON_RESP statement which also allows you to:

• modify the USERDATA associated with the accepting path• modify the proposed token assignment• propose a different initial synchronization point.

If an ON CON_IND section does not contain a CON_RESP statement, the connection isaccepted or rejected according to the options of the associated PROFILE statement. TheCON_RESP and TERMINATE statements are the only statements that call OSI sessionservices which can be used inside an ON CON_IND section.


47 A2 04US Rev05 8-9

8.4.2 Transferring Data

Once an OSI path is connected to an SS-user it may receive and transfer data accordingto the functional units negotiated for the session. TILS allows data to be transferredtransparently up to the maximum length indicated in the SIZE or the COMMON statementof the DECLARATION file. If the length of the data transferred exceeds the size of the INbuffer (defined in the SIZE or COMMON statements), a message is printed in the TILSoutput.

If the data exceeds the length specified, the action taken is determined by the optionselected in the TRUNCATION statement:

DISCONNECT closes the path by calling the user abort service in the OSI session layer

WARNING, the default option, sends you a warning message if the input is truncated

TERMINATE ends the TILS simulation phase with step completion status 0.

You can avoid truncating data by selecting an adequate size for the output buffercorresponding to the OUTSIZE parameter of the PROFILE statement.

8.4.3 Types of Data Transferred

There are four types of data to be transferred. You may declare data to be:

• "Normal" data, a part of a Normal Session Service Data Unit (NSSDU)• "Typed" data, a part of a Typed Session Service Data Unit (TSSDU)• "Expedited" data, a part of an Expedited Session Service Data Unit (XSSDU)• "Capability" data, a part of a Capability Session Service Data Unit (CSSDU).

You may also indicate whether the data is complete, the beginning, the middle, or the endof a Session Service Data Unit. However, the consistency of such a declaration is notcontrolled by TILS because TILS is transparent to the contents of the SSDUs exchanged.

With OSI session services version 1, Capability data must be complete. In OSI version 2,Capability data can be the beginning of, the middle of, the end of, or it can be thecomplete Session Service Data Unit.

When the appropriate functional units are negotiated, "Typed", "Expedited" or "Capability"data may be transmitted. If you try to send one of these types of data in violation of thenegotiated functional units, a recoverable error results.

Typed and Expedited data can be sent regardless of token restrictions. In an ON section,these may only be sent once. Typed or Expedited data is transmitted only through theOSI_SEND statement.

TILS User's Guide

8-10 47 A2 04US Rev05

In half duplex mode, Normal and Capability data may only be sent if the data token isassigned to the OSI path. Normal data is transmitted by:

• the OSI_SEND statement• the explicit SEND statement• the implicit SEND statement.

If the half duplex is not negotiated, output messages may only be treated in an ON DATAsection. TILS determines whether data received is an NSSDU, TSSDU or XSSDU byexamining the contents of register 9.

Capability data is transferred by the CAPABILITY statement, a confirmed service. Unlessan ON CAPABILITY_IND section is associated with the receiving path, TILS issues aresponse on behalf of the path without data (i.e. length of data is 0).

8.4.4 Receiving Data

There is no explicit statement to receive data. TILS may receive an SSDU at any time.The data received is stored in the OSI path's OUT field. Truncation is handled accordingto the TRUNCATION statement in the DECLARATION file. ON DATA sections areexecuted when any data except Capability data is received regardless of whether the datahas a full SSDU or not.


47 A2 04US Rev05 8-11

8.5 ENDING AN OSI SESSION

There are two ways to end an OSI session, either by evoking a user abort or byrequesting a release of the OSI session.

8.5.1 User Abort

An OSI path may close a program with a user abort at any time:

• by using the TILS statement TERMINATE• when an unrecoverable error is detected• when an error that is neither recovered by an error label nor by an ON ERROR section

is detected• at the end of the simulation phase.

Unless otherwise indicated, a return code other than "DONE" for an OSI session serviceproduces an unrecoverable error. If the TERMINATE statement is used, the programprovides 9 bytes of userdata, otherwise this data is provided by TILS according to thefollowing table:

USERDATA REASON

TLS_END end of simulation phase

TLS_ABORT abort of simulation phase

TLS_Exxxx unrecovered error with code xxxx

A path may request a user abort. When this happens, the OSI path is be notified of thetermination. The correspondent then reverts to the idle state after executing the ONABNTERM section (if applicable).

8.5.2 Requesting the Release of OSI Session Services

An OSI path may issue a "RELEASE" statement to request that a connection be released.This statement is valid only when the path is not executing an ON section. Similarly, anyOSI path may receive a request to release the connection.

If tokens are used for a connection and all the tokens negotiated at the beginning of theconnection are available, only the path that owns all the tokens may request a RELEASE.If a path tries to execute a release statement without having all of the negotiated tokens, arecoverable error is returned.

If the release token is not available, the path is closed when the RELEASE statement isissued. The path may not execute statements other than those in an "ON END" section.TILS confirms the request independent of the TILS program.

TILS User's Guide

8-12 47 A2 04US Rev05

When a release token is not available, TILS accepts the release for the path. The path isreturned to the idle state. If an ON RELEASE_IND section is associated with the path it isexecuted after the release is accepted and the path is idle. The terminate statement isthe only TILS statement that may request an OSI statement in this case. TERMINATEends the execution but does not request a user abort.

If the release token is available, the path waits for the response. If the release isaccepted, the path reverts to the idle state. If the release is not accepted the pathcontinues executing its program.

When the release token is available, TILS accepts the connection on behalf of the pathunless an ON RELEASE_IND section is associated with the path. You may issue theRELEASE statement specifying TYPE=RESP to either accept or reject the releaserequest. You may also use the TERMINATE statement to abort the session.

An ON END section may be associated with a path. This section is executed, whether thetoken is available or not, after a release request is accepted and confirmed.


47 A2 04US Rev05 8-13

8.6 TOKEN MANAGEMENT

Paths may be associated with several different PROFILE statements and thus havenegotiated different sets of functional modes. Services associated with a functional unitsmay be controlled by tokens. There are different four tokens:

• the data token• the minor token• the major token• the release token.

Statements calling services controlled by a token may cause recoverable errors if thetoken is not available or not owned by the correspondent. However, a path using halfduplex is an exception to this rule and does not execute statements outside ON sectionsunless it owns the data token.

8.6.1 Transferring Tokens

Tokens may be transferred, when available, by request from a TILS program. There aretwo ways to transfer a token. However, if either you or TILS attempt to transferunavailable tokens, a recoverable error results. You may use the explicit GIVE_TOKENstatement that transfers all available tokens or you may "add" your request to another OSIsession service by:

• transferring Normal data (OSI_SEND statement)• requesting to end an activity (ACTIVITY statement with OPTION=END and

TYPE=REQ)• requesting to set a minor or major synchronization point (SYNCPT statement with

TYPE=REQ).

The assignment of tokens is always stored in register 13. You can consult this register todetermine the current token assignment.

The ON GIVE_TOKEN section is only activated if a GIVE_TOKEN indication is received.

TILS User's Guide

8-14 47 A2 04US Rev05

8.6.2 Requesting Tokens

There are several way to request a token. You may either use the explicitPLEASE_TOKEN statement or you may add your request to another OSI session serviceby:

• responding to an activity interrupt, discard or end indication (ACTIVITY statement withTYPE=RESP and OPTION=INTERRUPT, =DISCARD, or =END)

• responding to a Capability data indication (CAPABILITY statement with TYPE=RESP)

• responding to a resynchronization indication (RESYNC statement TYPE=RESP)

• responding to the setting of a minor or major synchronization point (SYNCPT statementwith TYPE=RESP).

The LOAD statement with option TOKEN=REQ determines which token is requested.

The ON PLEASE_TOKEN condition allows the program to respond to thePLEASE_TOKEN request. If this parameter is absent, the requested tokens aretransferred by TILS using the GIVE_TOKEN session service.

The ON GIVE_TOKEN condition allows TILS to transfer a token. The transferred token isdetermined using the LOAD statement with the TOKEN_REQUEST option.


47 A2 04US Rev05 8-15

8.7 SYNCHRONIZATION AND RESYNCHRONIZATION

The synchronization and resynchronization services use the concept of synchronizationpoints to control the communications flow. A synchronization point is represented by aninteger value. One correspondent proposes a synchronization point then notifies the otherside who may or may not confirm it. TILS uses the LOAD statement to obtain the lastrequested and the last confirmed synchronization point.

A synchronization point is created if a minor or major synchronization point is requestedby the SYNCPT statement or if a path receives notification of a minor or majorsynchronization request.

8.7.1 Minor Synchronization Services

Minor synchronization services may be used to separate the flow of "Normal" and "Typed"data by setting minor synchronization points. This service is controlled by the minortoken. A path requests that a minor synchronization point be set. The path may benotified of minor synchronization points requested by a correspondent as well as of aconfirmation of a requested synchronization points.

Minor synchronization points are set and confirmed using the SYNCPT statement. Settinga minor synchronization point does not end the current sequence. The path does not waitfor the confirmation.

An ON MINOR_CONF section may be associated with the confirmation of a minorsynchronization point. By default minor synchronization points are not confirmed.

8.7.2 Major Synchronization Services

Major synchronization services allow flow of "Normal", "Typed", and "Expedited" data tobe separated by setting major synchronization points. This service is controlled by themajor token.

A path may use the SYNCPT statement to set major synchronization points. Because thisis a confirmed service, a path requesting a major synchronization point must wait for aconfirmation.

TILS User's Guide

8-16 47 A2 04US Rev05

8.7.3 Resynchronization Services

The value of the first synchronization point may be negotiated at the beginning of thesession. TILS allows paths to use the resynchronization service. If minor or major tokensare negotiated, resynchronization may occur on points within an interval between the lastconfirmed and the last synchronized point.

A LOAD statement with OPTION specified as SYNCPT_CONF allows TILS to comparethe synchronization point number set with the last SYNCPT statement. This statementmay also be used to consult the synchronization point number beyond which there may beno resynchronization.


47 A2 04US Rev05 8-17

8.8 ACTIVITY MANAGEMENT

The activity management functional mode allows you to separate a dialog into different"activities". You may select this mode in a path's PROFILE statement. Activities areidentified by a 6-byte identifier.

The right to "manage" activities is controlled by the major token. A recoverable erroroccurs if the minor token is also assigned to the correspondent. If the path owns themajor token it may:

• start an activity• interrupt the current activity• resume an interrupted activity• discard an activity• end an activity• give all tokens to the correspondent.

All of these services must be confirmed except for the request to start or to resume anactivity. Services linked to activity management ON sections may be specified to allowyou to respond to a messages.

The activity identifier may be consulted in the ACTIVITY field descriptor. In this 16-bytefield:

• bytes 1-2 store the length of the activity identifier• bytes 3-8 store the activity identifier• bytes 9-10 store the length of an identifier which has been resumed• bytes 11-16 store the identifier of the resumed activity.

If no activity is in progress the length in bytes 1-2 is -1.

If the activity management functional mode is negotiated, any statements (exceptCAPABILITY and TERMINATE) using OSI session services result in a recoverable errorwhen used outside an activity (see Appendix E for error codes).

A path can resume an activity interrupted by another path during a previous orsimultaneous connection.

TILS User's Guide

8-18 47 A2 04US Rev05

8.9 USER EXCEPTION REPORT

OSI paths may select the user exception report functional mode indicated by a parameterof the PROFILE statement. This mode can only be used if half duplex has beennegotiated.

You can then request a USER EXCEPTION REPORT in ALARM statement. This canonly be issued if the data token is assigned to the other session service user.

You can also receive user exception reports. The reason code for a report you receivedis stored in the protected TILS register 16. Use the ON ALARM section to respond to anotification that you have received a report. If this ON section is absent, TILS requests auser abort when a user exception report notification is received. After a user exceptionreport is received, only two types of statements may be used:

• those which do not involve OSI session services• those that call certain OSI session services allowed by the ISO standard to clear a user

exception report not yet be linked to other OSI session services.

You may use only the TERMINATE and GIVE_TOKEN statements inside an ON ALARMsection, and only the ACTIVITY or RESYNC statements outside the ON ALARM section.The execution level associated with the ON ALARM section is 17.

After a user exception message has been received and an OSI session service isrequested and accepted, the user exception message is cleared and you are no longerrestricted in the choice of OSI session service that you may request.


47 A2 04US Rev05 8-19

8.10 ACCESSING DATA

Output received by a path is stored in the path's OUT field. Input sent through theOSI_SEND, SEND, or CAPABILITY statements is copied to the path's IN field. The sizeand nature of these buffers is determined by the COMMON and SIZE statements of theDECLARATION file.

By default all paths share one 16K-byte buffer. TILS notes which path owns the buffer.An attempt to access the shared buffers by a path that does not own the buffer leads to arecoverable error.

Several OSI services allow up to 512 bytes (or 10 Kbytes if OSI session services 2 isused) of data designated as "userdata" to be transferred. The last userdata received by apath is stored in the USERDATA field. The length of the last userdata received is storedin register 14. The userdata field is shared by all paths. It may only be accessed onetime by the path which currently owns it and may not be modified directly by a TILSprogram.

Each OSI path may access the OSI_STATE field. Each time the field is accessed, thecurrent state of the OSI session is read. Use this facility to debug a session. The formatof the OSI_STATE field contents is described in the H_DC_SI_RD_STATE prototype (seeVCAM-ISO User's Guide).

TILS maintains registers 1 to 16 with information concerning the path. These registersmay be consulted by TILS programs, but may not be modified by a TILS program.

Each OSI path may consult other session parameters using the LOAD statement (see thechapter "DECLARATION File Statements" for further details).

TILS User's Guide

8-20 47 A2 04US Rev05

47 A2 04US Rev05 9-1

9. DECLARATION File Statements

This section describes all statements used in the DECLARATION file. A summary of allstatements is presented, grouped by type and followed by a summary of their syntax. Inthe section "Description of DECLARATION File Statements", the statements areexamined in alphabetical order.

Statements of the DECLARATION file may be classified as Global, Hereditary, Pointed, orExtension statements (see "The Declaration File" in the chapter "Preparing and StartingTILS"), depending on their relationship with the PATH statement. This relationship isshown for each statement under the Scope heading.

TILS User's Guide

9-2 47 A2 04US Rev05

9.1 SUMMARY OF THE DECLARATION FILE SYNTAX

9.1.1 The Identification Statement

NAME,COMMAND=command-id-D-A4,MAILBOX=mailbox-id-D-A8 [,SESSION=dimension-I] [,TEST={NO|YES}] [,CONNECT=rank-I] [,CONTROL={COMMAND|NONE}] [,ECHO={YES|NO}] [,OCL={ALL|ANY}] [,SSAP=ssapid-id-A16] [,NODE=tsapnsap-ref-A] [,ASCII={NO|SSAP}] [,OPTION={0|1}]

9.1.2 The Path Declaration Statements

PATH,pathnam-id-D-A12 [,entrynam-ref-A8] [,THINKTIME=thinktime-I] [,DESTINATION=destnam-ref-A8] [,LOGON=lognam-ref-A8] [,DEVICE=devnam-ref-A8] [,USERINFO=infnam-ref-A8] [,MAILBOX=mailnam-id-refdef-A8] [,PROFILE=profnam-ref-A8] [,SSAP=ssapid-id-A16] [,USERDATA=udatblk-ref-A8] [,NODE=tsapnsap-ref-A] [,QOS=qosblk-ref-A8]GENPATH,ROOT=rootnam-D-A7 [,COUNT=count-I] [,ENTRY=entrynam-ref-A8] [,THINKTIME=thinktime-I] [,DESTINATION=destnam-ref-A8] [,LOGON=lognam-ref-A8] [,DEVICE=devnam-ref-A8] [,USERINFO=infnam-ref-A8] [,MAILBOX=mailnam-id-refdef-A8] [,PROFILE=profnam-ref-A8] [,SSAP=ssapid-id-A16] [,USERDATA=udatblk-ref-A8] [,NODE=tsapnsap-ref-A] [,QOS=qosblk-ref-A8]

DECLARATION File Statements

47 A2 04US Rev05 9-3

9.1.3 The Global Control Statements

AUTO,{ENABLE|INHIBIT}DUMP,{ENABLE|INHIBIT}ELAPSED,timelimit-I[,UNIT={MILLI|SEC|MIN}]OCL,{BEGIN|END},TEXT='text-A'[,TYPE={ANY|OCL|GCL}]OVERFLOW[,COUNT=retrylimit] [,ACTION={DISCONNECT|RETRY}]PRINT,{DECLARATION|SCENARIO|CODE|TABLES|ALL|SYNTAX} [,MODE={ENABLE|INHIBIT}]SEQUENCE,number-I [,ACTION={DISCONNECT|TERMINATE}]THINKTIME,{CONSTANT|INHIBIT|VARIABLE|RANDOM} [,min-I] [,max-I] [,UNIT={MILLI|SEC|MIN}]TIMEOUT,delay-I [,ACTION={WARNING|DISCONNECT|TERMINATE|INHIBIT}]TRUNCATION,ACTION={WARNING|DISCONNECT|TERMINATE}WATCHDOG,timeperiod-I [,UNIT={MILLI|SEC|MIN}]

9.1.4 The Statements for Controlling Data Collection

CHRONOLOGY,size-IHISTOGRAM[,histnam-D-A8] [,UNIT=unit-I]LOGFILE,{ENABLE|INHIBIT|SEMAPHORE}TRACE,{NONE|EXTERNAL|BOTH|ALPHA|HEXA|SEMAPHORE}

TILS User's Guide

9-4 47 A2 04US Rev05

9.1.5 The Connection Statements

DESTINATION,destnam-D-A8 [,MAILBOX=mailbox-id-ref-A8] [,NODE=sessioncontrol-id-ref-A8]DEVICE,devnam-D-A8 [,TYPE={termtype-RWD NONE}] [,SUBTYPE={KCT|KPR|PRT|APP|CPU|CAS|KB|DSK|N}] [,MAIN=MASTER] [,TURN={THERE|HERE|ANYWHERE|ACCE|INIT}] [,CONNECT={INIT|ACCE|BOTH}] [,LINE=linelength-I] [,PAGE=pagelength-I] [,BLOCKING=N|B ] [,MODE=TWA|TWS] [,CODE={ALL|EBCDIC|ASCII|BINARY|ANY}] [,OPTION=mask-I] [,INSIZE=insize-I] [,OUTSIZE=outsize-I]LOGON,lognam-D-A8 [,BILLING=billing-id-ref-A12] [,PROJECT=project-id-ref-A12] [,PASSWORD=password-id-ref-A12] [,DELAY=connectiondelay-I] [,RETRY=retrylimit-I]PROFILE,profnam-D-A8 ,CONNECT={INIT|ACCE|CONTROL} [,SSAP=ssapid-id-A16] [,NODE=tsapnsap-id-ref-A] [,OUTSIZE=rmaxsize-I] [,DATA={NORMAL|TYPED|EXPEDITED|ALL}] [,DATA_TOKEN={NONE|NO|YES}] [,MINOR_TOKEN={NONE|NO|YES}] [,MAJOR_TOKEN={NONE|NO|YES}] [,RELEASE_TOKEN={NONE|NO|YES}] [,RESYNC={NO|YES}] [,MARK=syncptnb-I] [,ACTIVITY={NO|YES|FULL}] [,ALARM={NO|YES}] [,LEVEL={1|2|3}]USERINFO,infnam-D-A8,OPTION=optionstring-A22 [,STATION=station-id-A8]


47 A2 04US Rev05 9-5

9.1.6 The Context Declaration Statements

COMMON[,POOL=poolsize-I] [,REGISTER=numreg-I] [,OUTSIZE=outsize-I] [,INSIZE=insize-I] [,OPEN=maxfiles-I] [,WORKLIBS=worklibs-nb-I]DATA,pathnam-ref-A12,blocknam1-ref-A8,... [,blocknam8-ref-A8]SEED,PATH=pathnam-ref-A12,TEXT='text-A'SIZE[,WORKSIZE=wksize-I] [,OUTSIZE=outsize-I] [,INSIZE=insize-I] [,REGISTER=privregnum-I]

9.1.7 The Program Control Statements

ON,condition-RWD [,entry-ref-A8]PROGRAM,prognam1-ref-A8... [,prognam8-ref-A8]

TILS User's Guide

9-6 47 A2 04US Rev05

9.2 DESCRIPTION OF DECLARATION FILE STATEMENTS

Each statement of the DECLARATION file is explained in this section. The statementsare listed in alphabetical order.


47 A2 04US Rev05 9-7

AUTO

Scope:

Global

Purpose:

Automatically ends the simulation phase of TILS when the last path is closed.

Syntax:

AUTO,{ENABLE|INHIBIT}

Parameters:

ENABLE Requests automatic termination of the simulation phase.

INHIBIT No automatic end of the simulation phase is requested.This is how TILS behaves when the AUTO statement isabsent.

Notes:

This statement allows TILS to be executed without supervision by you or a control path,and without waiting for the time-limit to be detected. This statement may also be used asa TILS operator command.

TILS User's Guide

9-8 47 A2 04US Rev05

CHRONOLOGY

Scope:

Global

Purpose:

Collects statistical data for the chronological tables during the simulation phase.

Syntax:

CHRONOLOGY,size-I

Parameters:

size Gives the number of entries allowed for the collection ofdata. The maximum permitted value is 1440; the minimumvalue is 10.

Notes:

This statement gives the number of possible entries in each of the tables used to collectthe chronological data. The data is collected each minute of the simulation until all entriesare exhausted. When all entries are exhausted, a warning message is sent and thecollection is stopped. If this statement is absent no data is collected.

The chronological tables provide:

• a list, by minute, of the number of inputs, outputs, exchanges, the mean and maximumvalues for the response time, and the throughput.

• a list of cumulative measurements for each minute.

• a CHRONOGRAM, a display of the response time and throughput for each minute.


47 A2 04US Rev05 9-9

COMMON

Scope:

Global

Purpose:

Defines a field, the registers, the maximum number of subfiles which may be opened, andthe number of libraries to be used. This is information that is common to all paths.

Syntax:

COMMON[,POOL=poolsize-I][,REGISTER=numreg-I] [,OUTSIZE=outsize-I][,INSIZE=insize-I] [,OPEN=maxfiles-I][,WORKLIBS=worklibs-nb-I]

Parameters:

POOL The maximum size of the pool is 4095K. If this parameter isabsent, the pool is not available.

REGISTER This parameter determines the number of shared registers,each designated by a negative number prefixed by an "∗". IfREGISTER is absent, shared registers are not allocated.The maximum number of shared registers allowed is 65536.

OUTSIZE The size in bytes of the shared output buffer. The defaultvalue is 4096 bytes. The OUTSIZE value must be positiveand less than 32∗1024 bytes. This buffer is used by all pathsnot associated with a SIZE statement specifying a positivevalue for OUTSIZE.

INSIZE The size in bytes of the shared input buffer. The defaultvalue is 4096 bytes. The INSIZE value must be positive andless than 32∗1024 bytes. This buffer is used by all paths notassociated with a SIZE statement specifying a positive valuefor INSIZE.

OPEN The maximum number of opened subfiles in each WORKLIB.When OPEN = 0 (the default value), WORKLIBS are notopened. The maximum value is 250, thus the maximumnumber of opened subfiles is 750 when 3 WORKLIBS areused.

TILS User's Guide

9-10 47 A2 04US Rev05

COMMON

WORKLIBS The number of working libraries to be used. The maximum is3. The libraries must be assigned to the internal file names:WORKLIB, WORKLIB2, WORKLIB3. The default value is 1library (assigned to the ifn WORKLIB), if OPEN is greaterthan 0.

Notes:

If a COMMON statement is not used, the pool and shared registers are not available. Thedefault values for INSIZE, OUTSIZE and OPEN are used.

If subfiles of WORKLIB can be opened during the simulation phase, TILS is used in testmode as specified in the NAME statement.


47 A2 04US Rev05 9-11

DATA

Scope:

Extension

Purpose:

Associates blocks with the referenced path.

Syntax:

DATA,pathnam-ref-A12,blocknam1-ref-A8 [,blocknam2-ref-A8]...[,blocknam8-ref-A8]

Parameters:

pathnam The name of the path with which the referenced blocks areassociated.

blocknam The name of a block, selected in the SCENARIO file,associated with the path. Up to 8 blocks may beassociated with a path, using several DATA statements.

Notes:

Paths access blocks through field descriptors. A block is specified in the field descriptor,through its rank in the DATA statement associated with the path.

Example:

DECLARATION FILE SCENARIO FILE

PATH USER1 TOTO 14000 :PROGRAM TOTODATA USER1 BLOCK1 BLOCK2 :SEND (BLOCK,1)PATH USER2 TOTO 14000 :EODDATA USER2 BLOCK2 :BLOCK,BLOCK1 I AM GOOD :EOD :BLOCK,BLOCK2 I AM BAD :EOD

Using the same statement, PATH USER1 sends "I AM GOOD" and PATH USER2 sends"I AM BAD".

TILS User's Guide

9-12 47 A2 04US Rev05

DESTINATION

Scope:

Pointed

Purpose:

Defines a TILS name for an application.

Syntax:

DESTINATION,destnam-D-A8 [,MAILBOX=mailbox-id-ref-A8] [,NODE=sessioncontrol-id-ref-A4]

Parameters:

destnam The TILS name that identifies the application.

MAILBOX The name of an application mailbox through which the pathsreferring to this statement dialog. If this parameter is absentthen the mailbox, IOF, is assumed.

NODE The name of the session control for the application. If thisparameter is absent or blank the local session control isassumed.

Notes:

The DESTINATION statement provides the address of an application. A path using thisstatement requests a connection to an application identified by its mailbox and sessioncontrol. A DESTINATION statement is always generated for the default parameters andits name is a sequence of blanks.

OSI path restriction:

The DESTINATION statement associated with a path and a PROFILE statement (OSIpath) is ignored.


47 A2 04US Rev05 9-13

DESTINATION

Example:

DECLARATION FILE................DESTINATION SIM MAILBOX=IOFDESTINATION TIM MAILBOX=IOF NODE=H222DESTINATION GIM MAILBOX=MTDSPATH USER1 TOTO 14000 DESTINATION=SIMPATH USER2 TOTO 14000 DESTINATION=TIMPATH USER3 TDPROG 1000 DESTINATION=GIM

USER1 may be connected to the local IOF, USER2 to IOF under session control H222and USER3 to the TDS MTDS on the local session control.

TILS User's Guide

9-14 47 A2 04US Rev05

DEVICE

Scope:

Pointed

Purpose:

Associates the attributes of terminals with paths.

Syntax:

DEVICE,devnam-D-A8[,TYPE={termtype-RWD|NONE}] [,SUBTYPE={KCT|KPR|PRT|APP|CPU|CAS|KB|DSK|N}] [,MAIN=MASTER][,TURN={THERE|HERE|ANYWHERE|ACCE|INIT}] [,CONNECT={INIT|ACCE|BOTH}][,LINE=linelength-I] [,PAGE=pagelength-I][,BLOCKING=N|B ] [,MODE=TWA|TWS] [,CODE={ALL|EBCDIC|ASCII|BINARY|ANY}] [,OPTION=mask-I] [,INSIZE=insize-I] [,OUTSIZE=outsize-I]

Parameters:

devnam The TILS name that identifies the device.

TYPE The name of a terminal or device type (see list in Appendix F)or specified as "NONE". Paths associated with a device oftype "NONE" may not communicate through VCAM.

Type is specified as "HXhhhhHX" where hhhh stands for themodel code in hexadecimal. The default value for thisparameter is DKU7005. If a different device type is specified,you must take this into account when constructing theINPUT messages. For example, asynchronous types needan extra character for transmission purposes.

SUBTYPE A subtype of the terminal chosen in the TYPE parameter.No check is made on the validity of the associationbetween type and subtype. This parameter overrides thecorresponding byte (byte2) in the option mask, unless "N"is specified. "APP" may be used in place of "CPU" forcompatibility reasons.

Default is KCT (when TYPE is DKU7005).

MAIN Reserved for future use.


47 A2 04US Rev05 9-15

DEVICE

TURN If TURN is THERE, the correspondent of paths with thisDEVICE have the initial turn.

If TURN is HERE, paths have the initial turn.

If TURN is ANYWHERE, the correspondent of paths with thisDEVICE determines the initial turn. The result of the turnnegotiation is stored in register 13.

Default is THERE.

Notes: TURN is meaningless if MODE is specified as TWS.ACCE is a synonym of THERE, and INIT is a synonym ofHERE.

CONNECT If CONNECT is ACCE, paths with this DEVICE may acceptconnection requests.

If CONNECT is INIT, paths may initiate connection requests.

If CONNECT is BOTH, paths referring to this DEVICE mayinitiate connection requests and wait for reconnection (Hybridpaths).

Default is INIT.

Note: The TYPE parameter is irrelevant if CONNECT isACCE.

LINE Gives the line length of the terminal in the TYPEparameter. No control is performed on the accuracy of thevalue.

Default value is 80.

PAGE Gives the page length of the terminal in the TYPEparameter. No control is performed on the accuracy of thevalue.


BLOCKING If B is specified, a number of VCAM records may be sentwith one letter. This number depends on the record andletter size negotiated by VCAM at the beginning of thesession.

TILS User's Guide

9-16 47 A2 04US Rev05

DEVICE

MODE TWA - Two Way AlternateTWS - Two Way Simultaneous

Default is TWA.

CODE If CODE is ALL, TILS proposes EBCDIC, ASCII or BINARYcode. If EBCDIC is not selected, any data exchanged istranslated.

If CODE is EBCDIC, TILS proposes only EBCDIC.

If CODE is ASCII, TILS proposes only ASCII.

If CODE is BINARY, TILS proposes only transparent mode.

If CODE is ANY, TILS proposes EBCDIC, ASCII orBINARY code but no translation takes place.

Default is ALL.

OPTION This mask determines device attributes. The defaultvalues, shown below, corresponds to DKU7005 withsubtype KCT; a terminal type that supports tabulation, auto-linefeed and linewrap.

BYTE1: MPD_DVCAP (default "C0"X)

BYTE2: MPD_DVTYPE (default "CO"X)

BYTE3-4: MPD_DVFEATR (default "0302"X)

INSIZE Gives the maximum blocksize of input, in bytes. This valueis used by the session provider to calculate the size ofletters. It should lie between 1024 and 16*1024 bytes.Values which are not multiples of 1024 are rounded up tothe nearest multiple of 1024.

Default is 2048 bytes.

OUTSIZE Gives the maximum blocksize of output, in bytes. This valueis used by the session provider to calculate the size of letters.It should lie between 1024 and 16*1024 bytes. Values whichare not multiples of 1024 are rounded up to the nearestmultiple of 1024.

Default is 2048 bytes.


47 A2 04US Rev05 9-17

DEVICE

Notes:

Default values are adapted to the case of connections with IOF or TDS and should bechanged only on recommendation of BULL engineering personnel. A DEVICE statementfor default parameters is always generated and its name is a sequence of blanks.DEVICES specifying CONNECT as ACCE may not be associated with paths usingdifferent mailboxes.

Register 13 contains the result of the turn negotiation, and not the current turnassignment. This register is independent of the option chosen for TURN.

OSI path restrictions:

A DEVICE statement associated with a path and a PROFILE statement (OSI path) isignored.

TILS User's Guide

9-18 47 A2 04US Rev05

DUMP

Scope:

Global

Purpose:

Controls the printing of internal states of syntax analysis.

Syntax:

DUMP,{ENABLE|INHIBIT}

Parameters:

ENABLE Internal states of syntax analysis are printed until a DUMPINHIBIT statement occurs.

INHIBIT Ends printing of internal states of the syntax analysis.

Notes:

This statement should be used only in conjunction with BULL engineering personnel. Ifthis statement is absent then DUMP INHIBIT is assumed.


47 A2 04US Rev05 9-19

ELAPSED

Scope:

Global

Purpose:

Sets a time-limit for the simulation phase.

Syntax:

ELAPSED,timelimit-I[,UNIT={MILLI|SEC|MIN}]

Parameters:

timelimit Defines the maximum duration of the simulation phase, in theunit specified. The maximum value is 120 hours; theminimum value is 4 minutes.

UNIT Names the unit of measurement for the timelimit parameter:MILLI is milliseconds, SEC is seconds, MIN is minutes.

Default is MILLI.

Notes:

The simulation phase must be terminated. Any open paths at the end of the phase mustbe closed. If the ELAPSED statement is absent, the time-limit used to end the phase is 4minutes. The time-limit is counted from the reception of the first notification from thewatchdog and not the START command.

TILS User's Guide

9-20 47 A2 04US Rev05

GENPATH

Scope:

Global

Purpose:

Declares several paths simultaneously.

Syntax:

GENPATH,ROOT=rootnam-D-A7 [,COUNT=count-I] [,ENTRY=entrynam-ref-A8] [,THINKTIME=thinktime-I] [,DESTINATION=destnam-ref-A8] [,LOGON=lognam-ref-A8] [,DEVICE=devnam-ref-A8] [,USERINFO=infnam-ref-A8] [,MAILBOX=mbxnam-id-refdef-A8] [,PROFILE=profnam-ref-A8] [,SSAP=ssap-id-D-A16] [,USERDATA=udatblk-ref-A8] [,NODE=tsapnsap-id-ref-A] [,QOS=qosblk-ref-A8]

Parameters:

ROOT The root name of the generated paths. The names of allpaths generated by this statement begin with the characterstring defined in this parameter.

All names are formed by the pathroot and rank, a five digitnumber. These names must be valid user IDs in thesystem site catalog where the application is running.

If this statement is associated with a PROFILE statementthe restrictions to the site catalog do not apply.

COUNT The number of paths generated.

ENTRY The name of an entry point in a selected program. Thisparameter must be present unless the device associatedwith the path is of type NONE.


47 A2 04US Rev05 9-21

GENPATH

THINKTIME The thinktime, expressed in milliseconds, used by thegenerated group of paths if the THINKTIME statement isabsent, or if CONSTANT is specified in the THINKTIMEstatement, or if VARIABLE is specified and register 17contains 0.

Default value is 20,000 milliseconds.

DESTINATION The name of a destination (defined in the DESTINATIONstatement) that associates a correspondent with a path.This parameter is not significant if PROFILE is specified inGENPATH.

Default value is a sequence of blanks, indicating that thedefault DESTINATION statement is used.

LOGON The name of a LOGON statement associating a billing, aproject and a password with a path. These parameters mustmatch the user ID.

Default value is a sequence of blanks indicating that thedefault LOGON statement is used.

DEVICE The name of a device (defined in the DEVICE statement) thatassociates a terminal type and the characteristics of aconnection with a path. This parameter is not significant ifPROFILE is specified in GENPATH.

Default value is a sequence of blanks indicating that thedefault DEVICE statement is used.

USERINFO The name of a statement that provides the userinfo recordwhen the connection is made. This parameter is notsignificant if PROFILE is specified in GENPATH.

MAILBOX The name of the local mailbox used by a path. This name iscreated when the argument MAILBOX=name is encounteredfor the first time. The mailbox name is unique and must notconflict with the any other name of a mailbox declared underthe session control in the CNC. If no mailbox is specified, thelocal mailbox will be the principal TILS mailbox.

PROFILE The name of a profile defined in a PROFILE statement.This name associates a correspondent with a path anddefines the attributes of the path as an OSI session serviceuser. A path associated with a profile is referred to as anOSI path.

TILS User's Guide

9-22 47 A2 04US Rev05

GENPATH

SSAP The name of a local Session Service Access Point. Thisname is created when the argument SSAP = name isencountered for the first time. If an SSAP is not specified,the local SSAP declared in the NAME statement will beused. If no SSAPs are specified, the path may not beassociated with a PROFILE statement.

A PROFILE statement must be specified to use the SSAPparameter.

USERDATA The name of a block in the associated SCENARIO file.The first record of this block is sent as userdata when aconnection request is issued. Any following records in theblock are ignored. Block records may be spawned overseveral records.

A PROFILE statement must be specified to use theUSERDATA parameter.

NODE The address of the local SSAP. This parameter is only usedwith the SSAP parameter. For more information, see theNODE parameter in the NAME statement.

QOS The name of a block in the SCENARIO file. The firstrecord of this block is sent as "Quality Of Service"parameters when a connection request is issued. Anyfollowing records in the block are ignored. The blockrecords may be spawned over several records.

A PROFILE statement must be specified to use the QOSparameter.

Note:

This statement allows a set of paths sharing the same characteristics to be defined.

Example:

GENPATH ROOT=USER COUNT=5 ENTRY/PROG;

is equivalent to the following sequence of TILS statements:

PATH USER00001 PROG;PATH USER00002 PROG;PATH USER00003 PROG;PATH USER00004 PROG;PATH USER00005 PROG;


47 A2 04US Rev05 9-23

GROUP

Scope:

Hereditary

Purpose:

Defines a TILS name for a group of paths.

Syntax:

GROUP[,groupnam-D-A8]

Parameters:

groupnam Puts all paths between this and the next GROUP statementunder a common identifier. If the GROUP parameter isabsent, the paths following this statement are notassociated with any group.

Notes:

Groups are used in TILS operator commands to address all paths associated with agroup.

Example:

DECLARATION FILE................GROUP IOFMAINPATH USERA,LIBMAIN,14000PATH USERB,LIBMAIN,19000GROUP TDSMAINPATH USERC,TDX,1000

The TILS operator command, "TILS START GROUP=IOFMAIN", initiates a connectionrequest for USERA then for USERB.

TILS User's Guide

9-24 47 A2 04US Rev05

HISTOGRAM

Scope:

Hereditary

Purpose:

Defines a histogram.

Syntax:

HISTOGRAM[,histnam-D-A8][,UNIT=unit-I]

Parameters:

histnam The name of the histogram. All paths declared after thisstatement are associated with the histogram. If thisparameter is absent, a histogram is not associated withpaths declared after the statement.

UNIT An integer, greater than or equal to 1, which determines thelength of the boxes of the histogram.

Default value is 1.

Notes:

For a variable, a histogram partitions the domain of the variable's values into boxes of thesame length and if the values are not bounded, adds a box for all values exceeding thegiven maximum value. A counter, associated with each box, is increased whenever ameasured value falls within the interval defined for the box. All declared histograms have40 boxes, plus a box for the overflow.

A path is associated with a histogram if it is preceded by a histogram statement. When ahistogram is associated with a path, the path's response times fill the histogram.

Histograms may be managed through TILS programs. You must be careful to use onlyhistograms not associated with paths. You should define histograms after all paths havebeen declared.


47 A2 04US Rev05 9-25

LOGFILE

Scope:

Global

Purpose:

Determines the level of data collection for the logfile.

Syntax:

LOGFILE,{ENABLE|INHIBIT|SEMAPHORE}

Parameters:

ENABLE Logs all events except semaphore and MGCB messages.

INHIBIT Logs only the CONTROL event.

SEMAPHORE Logs all events. For IN, OUT, H_RECVIT, H_SENDIT, andH_CLSMG, the Message Group Control Block (MGCB) isalso logged.

Notes:

This statement is ignored if FILE_L is not assigned in the JCL. If LOGFILE statement isabsent, LOGFILE INHIBIT is assumed.

TILS User's Guide

9-26 47 A2 04US Rev05

LOGON

Scope:

Pointed

Purpose:

Provides catalog attributes and connection parameters.

Syntax:

LOGON,lognam-D-A8[,BILLING=billing-id-A12] [,PROJECT=project-id-A12][,PASSWORD=password-id-A12] [,DELAY=connectiondelay-I][,RETRY=retrylimit-I]

Parameters:

lognam The name in the PATH statement that refers to the log.

BILLING The billing for user IDs of paths referring to the LOGONstatement. These users must be in the current site catalog.

Default value is a sequence of blanks indicating that thedefault billing of the site catalog is used.

PROJECT The project for user IDs of paths referring to the LOGONstatement. These users must be in the current site catalog.

Default value is a sequence of blanks indicating that thedefault project of the site catalog is used.

PASSWORD The password for user IDs of paths referring to the LOGONstatement. These users must be in the current site catalog.

Default value is a sequence of blanks.

DELAY The elapsed time, in milliseconds, used to avoidsimultaneous connection requests. The value of delaymust be between 100 and 60,000 milliseconds.

Default value is 1000 milliseconds.


47 A2 04US Rev05 9-27

LOGON

RETRY The maximum number of retries allowed for connectionrequests rejected due to resource overflow (V_RESOV onH_OPMG).

Default value is 0 - no retry takes place.

Notes:

A LOGON statement for the default values is always generated. Its name is a sequenceof blanks.


The LOGON statement associated with a path and a PROFILE statement (OSI path) isignored except for the DELAY parameter.

Example:

LOGON LOG PROJECT=TILSTEST PASSWORD=US DELAY=100GROUP GR0001PATH USERA,PROG,10000,LOGON=LOGPATH USERB,PROG,10000,LOGON=LOGPATH USERC,PROG,10000,LOGON=LOGOCL BEGIN,'TILS START GROUP=GR0001'

Paths USERA, USERB and USERC issue connection requests 100, 200, and 300milliseconds, respectively, after the command TILS START GROUP=GR001 has beenreceived by TILS. All paths generate IOF jobs under project TILSTEST and usePASSWORD US.

TILS User's Guide

9-28 47 A2 04US Rev05

NAME

Scope:

Global

Purpose:

Changes the name of the command identifier and the principal mailbox of TILS.

Syntax:

NAME,COMMAND=command-id-D-A4,MAILBOX=mailbox-id-D-A8 [,SESSION=dimension-I][,TEST={NO|YES}] [,CONNECT=rank-I][,CONTROL={COMMAND|NONE}] [,ECHO={YES|NO}][,OCL={ALL|ANY}][,SSAP=ssap-id-D-A16] [,NODE=tsapnsap-id-ref-A][,ASCII={ NO|SSAP}] [,OPTION={0|1}]

Parameters:

COMMAND The name of the OCL command that you use to interact withTILS. This name should not conflict with another commandname.

Default name is TILS.

MAILBOX The name of the principal TILS mailbox. If there is a conflictwith the name of another mailbox declared in the CNC, by aTDS, or by another TILS, then the proposed name is changedto TILSnnnn where nnnn is the RON of the TILS job.

Default name is TILS.

SESSION The maximum number of simultaneously opened pathsallowed for a session. Only those paths associated with adevice of type other than NONE need to be counted. Thisparameter is reserved for use by BULL engineeringpersonnel.

Default value is the number of declared paths.


47 A2 04US Rev05 9-29

NAME

TEST If TEST is YES, TILS is used in test mode and obeys thecommon rules governing the execution of jobs under GCOS7. In this case, TILS is launched with a low hardware priority.This mode is implicit if files are assigned with the $ASSIGNWORKLIB[n] statement of the TILS step.

If TEST is NO, TILS is used to evaluate performance. Allmemory needed for the simulation is locked and thehardware priority is forced to 6 (high priority).

Default is YES

CONNECT All paths up to the specified rank are to be connected oncethe compilation phase is completed. Paths which may onlyaccept connection requests are ignored (see DEVICEstatement). If this parameter is absent or 0 no path requeststhe connection unless a START command is issued.

CONTROL If CONTROL is COMMAND, an OCL command is createdwhich allows you to interact with TILS during the simulationphase.

If CONTROL is NONE, no OCL command is created.

Default is COMMAND.

ECHO If ECHO is YES, all commands are echoed on the TILSconsole.

If ECHO is NO, the commands are not echoed.

Default is YES.

OCL This parameter allows OCL statements in theDECLARATION and SCENARIO files to be modified.

If OCL is ALL, only "TYPE=GCL" allows directives to betreated.

When the TYPE parameter is absent or "TYPE=ANY", thisparameter is equivalent to "TYPE=OCL".

If OCL is ANY, "TYPE=GCL" is not allowed, and"TYPE=ANY" or an absent TYPE parameter is equivalentto "TYPE=OCL".

SSAP The name of the principal SSAP of TILS. All OSI paths areassociated with the local SSAP unless another one isspecified in the PATH statement.

TILS User's Guide

9-30 47 A2 04US Rev05

NAME

NODE This parameter indicates the local TSAP and NSAPassociated with SSAP.

TSAPNSAP must be enclosed in quotes. The first characterafter the quote is a delimiter used to separate TSAP from theNSAP. The characters between the first and seconddelimiter name the local TSAP, those after the second namea local NSAP. All characters must be hexadecimal digits.

ASCII If ASCII is NO, SSAPs are stored in EBCDIC code.

If ASCII is SSAP, SSAPs are translated and stored inASCII code.

OPTION Determines the version of the displayed path state when aconflict occurs.

If OPTION is 0, "LOAD STATUS" and "CONTROL" return thepath state from the V37 TILS version.

If OPTION is 1, "LOAD STATUS" and "CONTROL" returnthe path state of the V38 and V39 (current) TILS versions.

Notes:

The NAME statement allows you to customize a TILS session and launch severalsessions at the same time. Only one NAME statement may be used in theDECLARATION file. NAME must precede all PATH statements.

If the NAME statement is absent, the name of the command and of the mailbox is TILS.This mailbox is the only TILS mailbox unless the MAILBOX parameter is used in a PATHstatement.

The NAME statement may be passed as an option string for the (JCL) step H_TILS. Theoption string takes precedence over the NAME statement in the DECLARATION file.

If OSI session services are used, the local Session Service Access Point must bedeclared using the NAME statement or in all relevant PATH statements.


47 A2 04US Rev05 9-31

OCL

Scope:

Global

Purpose:

Stores operator commands or directives for transmission to GCOS 7.

Syntax:

OCL,{BEGIN|END},TEXT='text-A'[,TYPE={ANY|OCL|GCL}]

Parameters:

BEGIN Transmits text to GCOS 7 at the beginning of thesimulation phase.

END Transmits text to GCOS 7 when the simulation phase ends.

TEXT Transmits the OCL command. If the command isinterpreted as a directive, its length should not exceed2048 characters.

TYPE If TYPE is ANY, the text is treated as an operatorcommand. If the command is unknown it is assumed to bea directive. If the command submitted can be processed, awarning is issued.

Default value is ANY unless the OCL parameter of theNAME statement is used.

If TYPE is OCL, the text is treated as an operatorcommand. If the OCL parameter of the NAME statement isused then this is the default.

If TYPE is GCL, the text is treated as a directive.

TILS User's Guide

9-32 47 A2 04US Rev05

OCL

Notes:

The text may be any OCL command or directive, including a TILS Operator command ifBEGIN is specified. If END is specified no TILS operator command can be used. TheOCL statement cannot be used to end the simulation phase.

You are notified if the command cannot be treated. You must decide which correctiveaction should be taken:

• RETRY submits the OCL command again• SKIP ignores the OCL command• IGNORE ignores all OCL commands of this category (i.e. BEGIN or END)• TERMINATE ends the simulation phase.

If you are not logged on IGNORE is the default action.

The total storage required for an OCL statement may not exceed 64K for either category.Each statement requires the number of characters in the text plus 4 bytes as storage.

Under release V3, when TYPE is specified as GCL, the statement is rejected. The defaultvalue for TYPE depends on the NAME statement of the DECLARATION file. If the OCLparameter is:

• absent then the default for TYPE is ANY• ALL, only "TYPE=GCL" leads to the treatment of the text as directive• ANY, only OCL commands may be submitted and "TYPE=GCL" rejects of the

statement (as under V3).

Example:

DECLARATION FILE................OCL BEGIN,'DJ TILS'OCL BEGIN,'TILS START ALL'OCL END,'DJ TILS'

In this example, (at the beginning of the simulation phase) the directive "DJ TILS" displaysthe CPU and elapsed time of a TILS job. The START command is issued for all paths.At the end of the simulation phase DJ TILS is issued again to display the total CPU andelapsed time of the TILS job.


47 A2 04US Rev05 9-33

ON

Scope:

Hereditary

Purpose:

Determines how conditions are treated.

Syntax:

ON,{OPEN|ERROR|COMMAND|DATA|END|REJECT|RECONNECT ATTENTION|TELEGRAM |DMNDTURN|ABNTERM RELEASE_IND|CAPABILITY_IND|PLEASE_TOKEN_IND| GIVE_TOKEN_IND|ACT_START_IND|ACT_RESUME_IND| ACT_INTER_IND|ACT_DISCARD_IND|ACT_END_IND|CON_IND| RESYNC_IND|ALARM|MINOR_IND|MINOR_CONF|MAJOR_IND| TIMEOUT|AUTOEND|ELAPSED} [,entrynam-ref-A8]

Parameters:

ON entry points One of the listed conditions must occur to activate the ONsection. See the conditions for all paths, for DSA pathsand for OSI paths below.

entrynam The name of an entry point in a selected program. If thisparameter is absent, no entry point is associated with thepaths following this statement.

Notes:

The ON statement associates the entry point with all paths following the statement. Itseffect may be cancelled by another ON statement in the Declaration file or in the programassociated with the path. It may also be cancelled at run time by another ON statement.

Conditions that apply to all paths

ERROR Statements following this entry point are executed if arecoverable error occurs for a path within the scope of thisstatement.

COMMAND Statements following this entry point are executed if thepath is addressed by the TILS operator command SEND.

TILS User's Guide

9-34 47 A2 04US Rev05

ON

TIMEOUT Statements following this entry point are executed ondetection of a timeout for a path within the scope of thisstatement.

AUTOEND Statements following this entry point are executed by a pathwithin the scope of this statement, if it is the last active pathand if the AUTO ENABLE function is active. The TILSsession will be stopped at the return of this ON section.

ELAPSED Statements following this entry point are executed ondetection of the time limit of the TILS session, by all pathswithin the scope of this statement. The TILS session will bestopped at the return of the last path within the scope of thisstatement.

Conditions that apply to DSA paths

OPEN Statements following this entry point are executed if a pathwithin the scope of this statement is opened.

DATA Statements following this entry point are executedwhenever a message that does not carry the turn(enclosure levels 1 or 2) is received.

END Statements following this entry point are executed whenevera message that indicates a normal termination of theconnection (enclosure level 5) is received. A BREAKcommand cannot be executed during an ON END section.

REJECT Statements following this entry point are executed if aconnection request is rejected for the path. A BREAKcommand cannot be executed during an ON REJECTsection.

Error! Reference source not found.RECONNECT Statements following this entry point are executed when a

Hybrid path is reconnected within the scope of the ONstatement.

Error! Reference source not found.ABNTERM Statements following this entry point are executed if the

session is aborted by the correspondent.

ATTENTIONTELEGRAMDMNDTURN

These ON conditions correspond to various interrupt types.

Notes:

Certain conditions for DSA paths have the same name as those that apply to OSI paths.


47 A2 04US Rev05 9-35

ON

Conditions that apply to OSI paths

OPEN Statements following this entry point are executed if theconnection request of an OSI PATH is accepted (uponreceipt of the confirmation).

CON_IND Statements following this entry point are executed when aconnection indication is received by the path. If an explicitCON_RESP statement is not used in the ON section, theconnection is accepted or rejected according to the optionsof the PROFILE statement associated with the path. Allother OSI statements except for TERMINATE, are illegalinside a CON_IND section.

REJECT Statements following this entry point are executed if theconnection request of an OSI PATH is rejected.

DATA Statements following this entry point are executedwhenever a message without the data token is received.

END Statements following this entry point are executedwhenever a release request is accepted.

ABNTERM Statements following this entry point are executedwhenever a user abort message is received.

PLEASE_TOKEN_INDGIVE_TOKEN_IND

Statements following this entry point are executedwhenever the corresponding token management messageis received.

ACT_START_INDACT_RESUME_INDACT_INTER_INDACT_DISCARD_INDACT_END_IND

Statements following this entry point are executedwhenever the corresponding activity managementmessages is received.

RELEASE_IND Statements following this entry point are executed when arelease indication is received. This condition may only beused if the release token has been negotiated.

CAPABILITY_IND Statements following this entry point are executed when acapability data indication is received.

MINOR_IND Statements following this entry point are executed when aminor synchronization point indication is received.

MINOR_CONF Statements following this entry point are executed when aminor synchronization point confirmation is received.

TILS User's Guide

9-36 47 A2 04US Rev05

ON

MAJOR_IND Statements following this entry point are executed when amajor synchronization point indication is received.

RESYNC_IND Statements following this entry point are executed when aresynchronization indication is received.

ALARM Statements following this entry point are executed when auser exception report message is received.

Notes:

Certain conditions for OSI paths have the same name as those that apply to DSA paths.An ON RELEASE_IND section may be associated with any path regardless of theavailability of the release token. If the token is not available, TILS responds to the releaseindications before executing any ON RELEASE_IND sections and then sets the path tothe idle state.

Attempting to use a TILS command to request an OSI service other than TERMINATE orRELEASE TYPE=RSP (if the token is available) inside an ON RELEASE_IND sectionleads to an unrecoverable error. A TERMINATE statement inside an ON RELEASE_INDsection initiates a user abort request when the release token is available, and when thetoken is not available, the RELEASE message is acknowledged and the path is set to idle.

Example:

DECLARATION FILE SCENARIO FILE

................ :PROGRAM INITPROGRAM INIT :ASSIGN *18 0SIZE REGISTER=2 :RETURN;ON OPEN INIT :ENTRY MAINPATH USERA,MAIN,... .............ON OPEN .............PATH USERB,MAIN,... :EOD................

USERA initializes register 18 to 0. USERB leaves the register uninitialized.


47 A2 04US Rev05 9-37

OVERFLOW

Scope:

Global

Purpose:

Determines the reaction to the resource overflow on SEND.

Syntax:

OVERFLOW[,COUNT=retrylimit] [,ACTION={DISCONNECT|RETRY}]

Parameters:

COUNT The maximum number of attempts allowed to re-execute aSEND command that could not be executed because ofresource overflow (V_RESOV). This parameter is relevantonly if the ACTION parameter specified is RETRY.


ACTION If ACTION is DISCONNECT, the path is disconnectedwhenever a resource overflow on a SEND statementoccurs.

If ACTION is RETRY, an attempt is made to re-execute theunsuccessful SEND statement.

Default is DISCONNECT.

Notes:

RETRY is not valid when the SEND statement specifies the source as block or seed.

When the OVERFLOW statement is absent, OVERFLOW ACTION=DISCONNECT isassumed and the counter is not reinitialized.

TILS User's Guide

9-38 47 A2 04US Rev05

PATH

Purpose:

Declares paths

Syntax:

PATH,pathnam-id-D-A12[,entrynam-ref-A8] [,THINKTIME=thinktime-I] [,DESTINATION=destnam-ref-A8] [,LOGON=lognam-ref-A8] [,DEVICE=devnam-ref-A8] [,USERINFO=infnam-ref-A8] [,MAILBOX=mbxnam-id-refdef-A8] [,PROFILE=profnam-ref-A8] [,SSAP=ssap-id-D-A16] [,USERDATA=udatblk-ref-A8] [,NODE=tsapnsap-id-ref-A] [,QOS=qosblk-ref-A8]

Parameters:

pathnam The name of the path. This name must be a valid user IDin the system site catalog where the application is running.

entrynam The name of an entry point in a selected program. Thisparameter must be present unless the device associatedwith this path specifies type NONE.

THINKTIME The thinktime expressed in milliseconds which is used asconstant THINKTIME if the THINKTIME statement isabsent or if it specifies "CONSTANT" or "VARIABLE" andregister 17 contains 0.

The default value is 20,000 milliseconds.

DESTINATION The name of a destination defined in a DESTINATIONstatement. It associates a correspondent with the path.This parameter is not significant if PROFILE is specified.The default value is a sequence of blanks pointing to thedefault DESTINATION statement.


47 A2 04US Rev05 9-39

PATH

LOGON The name of a LOGON statement. Thus BILLING,PROJECT and PASSWORD are associated with the path.They must match the user ID. The default value is asequence of blanks pointing to the default LOGONstatement.

DEVICE The name of a device defined in a DEVICE statement. Itassociates a terminal type and further characteristics of aconnection with the path. The default value is a sequenceof blanks pointing to the default DEVICE statement.

USERINFO The name of a USERINFO statement which provides theuserinfo record at connection time. This parameter is notsignificant if PROFILE is specified.

MAILBOX The name of the local mailbox used by the path. It iscreated for the first reference. If no mailbox is specified fora path the local mailbox will be the principal mailbox ofTILS. The name must not conflict with the name of anothermailbox declared under the same session control in theCNC.

PROFILE The name of a profile defined in a PROFILE statement,associating a correspondent with a path and defines thepath as an OSI session service user. A path associatedwith a profile is referred to as an OSI path.

SSAP The name of a local Session Service Access Point (SSAP).This name is created when the argument SSAP = name isencountered for the first time. If an SSAP is not specified,the local SSAP declared in the NAME statement will beused. If no SSAPs are specified, the path may not beassociated with a PROFILE statement.

A PROFILE statement must be specified to use the SSAPparameter.

USERDATA This parameter specifies the name of a BLOCK in theassociated SCENARIO file. The first record of this block issent by the path as userdata when a connection requestissued. Further records in the block are ignored. The blockrecords may be spawned over several records. Thisparameter may not be used unless a PROFILE is specified.

TILS User's Guide

9-40 47 A2 04US Rev05

PATH

NODE The address of the local SSAP. This parameter may onlybe specified with the SSAP parameter. See NODE in theNAME statement.

QOS This parameter specifies the name of a BLOCK in theassociated SCENARIO file. The first record of this block issent by the path as QUALITY OF SERVICE parameterwhen a connection request issued. Further records in theblock are ignored. The block records may be spawned overseveral records. This parameter may not be used unlessPROFILE is specified.

Note:

At least one path must be declared.


47 A2 04US Rev05 9-41

PRINT

Scope:

Global

Purpose:

Controls the output of the compilation phase.

Syntax:

PRINT,{DECLARATION|SCENARIO|CODE|TABLES|ALL|SYNTAX} [,MODE={ENABLE|INHIBIT}]

Parameters:

DECLARATION This statement prints the DECLARATION file.

SCENARIO This statement prints the SCENARIO file.

CODE This statement prints the intermediate code produced forinterpretation by the compilation phase.

TABLES This statement prints the tables that summarize theinformation TILS sent to the DECLARATION andSCENARIO files.

ALL This statement prints the DECLARATION and SCENARIOfiles, the intermediate code, the tables and a summary ofthe TILS syntax.

SYNTAX This statement prints a summary of the TILS syntax.

MODE If MODE is ENABLE, the object is printedIf MODE is INHIBIT, the object is not printed.

Notes:

If a PRINT statement is not specified, a table of the job environment and the use of lockedmemory is printed, along with any error messages, erroneous statements, and the namesof the programs and blocks in the SCENARIO file. There may be an unlimited number ofPRINT statements in the DECLARATION file. Records in the DECLARATION andSCENARIO files are truncated at the 120th and 80th characters respectively.

TILS User's Guide

9-42 47 A2 04US Rev05

PRINT

Example:

DECLARATION FILE................PRINT DECLARATION* LIST OF INITIAL OCL COMMANDSOCL BEGIN 'TILS START PATH=USERA'OCL BEGIN 'TILS START PATH=USERF'PRINT DECLARATION INHIBIT

Only the lines from * LIST....to PRINT DECLARATION INHIBIT are printed.


47 A2 04US Rev05 9-43

PROFILE

Scope:

Pointed

Purpose:

Associates the functional units and a correspondent with each path.

Syntax:

PROFILE,profnam-D-A8 [,SSAP=ssap-id-ref-A16] [,CONNECT={INIT|ACCE|CONTROL}] [,NODE=address-A] [,OUTSIZE=portionsize-I] [,DATA={NORMAL|TYPED|EXPEDITED|ALL}] [,DATA_TOKEN={NONE|NO|YES}] [,MINOR_TOKEN={NONE|NO|YES}] [,MAJOR_TOKEN={NONE|NO|YES|}] [,RELEASE_TOKEN={NONE|NO|YES}] [,RESYNCH={NO|YES}] [,MARK=syncpointnb-I] [,ACTIVITY={NO|YES|FULL}] [,ALARM={NO|YES}] [,LEVEL={1|2|3}]

Parameters:

profnam The TILS name used to identify this PROFILE.

SSAP The name of the Session Service Access Point (SSAP)that OSI paths use to make connections. This parameteris mandatory if CONNECT is specified as INIT.

TILS User's Guide

9-44 47 A2 04US Rev05

PROFILE

CONNECT If CONNECT is INIT, paths associated with the profile mayinitiate connections but may not accept connections.

If CONNECT is ACCE, paths associated with the profilemay accept connections but not initiate them. Any otherparameters are ignored. A search is made for pathsassociated with a given SSAP. The order of a search isdetermined by the order of the paths in the DECLARATIONfile.

If CONNECT is CONTROL, paths associated with theprofile may initiate connections but may not acceptconnections. Furthermore, connection requests arerejected if the functional units selected in the PROFILEstatement do not match the negotiated units. If theconnection is rejected no attempt is made to find a pathmatching the required functional units.

Default is INIT.

NODE This parameter specifies the Transport Service AccessPoint (TSAP) and a list of up to 20 of Network ServiceAccess Points (NSAPs) for the application. The firstcharacter is a delimiter, followed by the TSAP, then byanother delimiter, and then by the different NSAPs, eachfollowed by a delimiter.

The TSAP length may not exceed 32 characters. NSAPnames may not exceed 20 characters. TSAP and eachNSAP must be hexadecimal numbers.

NODE may only be specified if TSAP is also specified.

Default: the path's correspondent is identified by its SSAP.

OUTSIZE Maximum size of Session Service Data Unit (SSDU) whichmay be transferred without fragmentation.

Default is 16,384 bytes.


47 A2 04US Rev05 9-45

PROFILE

DATA If DATA is NORMAL, only Normal data can be transmitted.If DATA is TYPED, Normal and Typed data may betransmitted.

If DATA is EXPEDITED, Normal and Expedited data maybe transmitted.

If DATA is ALL, Normal, Typed, and Expedited data maybe transmitted.

Default is NORMAL.

DATA_TOKEN If DATA_TOKEN is NONE full-duplex is selected.

If DATA_TOKEN is NO half-duplex is selected but thetoken is not assigned to the paths associated with thisPROFILE statement.

If DATA_TOKEN is YES half-duplex is selected and thetoken is assigned to the paths associated with thisPROFILE statement.

Default is NONE.

MINOR_TOKEN If MINOR_TOKEN is NONE, the minor synchronizationfunctional unit is not selected.

If MINOR_TOKEN is NO, the minor synchronizationfunctional unit is selected but it is not assigned to the pathsassociated with this PROFILE statement.

If MINOR_TOKEN is YES, the minor synchronizationfunctional unit is selected and it is assigned to the pathsassociated with this PROFILE statement.

Default is NONE.

TILS User's Guide

9-46 47 A2 04US Rev05

PROFILE

MAJOR_TOKEN If MAJOR_TOKEN is NONE, the major synchronizationfunctional unit is not selected.

If MAJOR_TOKEN is NO, the major synchronizationfunctional unit is selected but it is not assigned to the pathsassociated with this PROFILE statement.

If MAJOR_TOKEN is YES, the major synchronizationfunctional unit is selected and it is assigned to the pathsassociated with this PROFILE statement.

Default is NONE.

RELEASE_TOKEN If RELEASE_TOKEN is NONE, the negotiated releasefunctional unit is not selected.

If RELEASE_TOKEN is NO, the negotiated releasefunctional unit is selected but it is not assigned to the pathsassociated with this PROFILE statement.

If RELEASE_TOKEN is YES, the negotiated releasefunctional unit is selected and it is assigned to the pathsassociated with this PROFILE statement.

Default is NONE.

RESYNC If RESYNC is NO, resynchronization is not supported.If RESYNC is YES, resynchronization is supported.

Default is NO.

MARK The number of the initial synchronization point. When themajor or minor synchronization functional units areselected, this parameter is mandatory.

ACTIVITY If ACTIVITY is NO, the Activity functional unit is notselected.

If ACTIVITY is YES, the Activity functional unit is selected.

If ACTIVITY is FULL, the Activity and Capability datafunctional units are selected.

Default is NO.


47 A2 04US Rev05 9-47

PROFILE

ALARM If ALARM is NO, the user exception reporting functionalunit is not selected.

If ALARM is YES, the user exception reporting functionalunit is selected. If so, DATA_TOKEN must be either YESor NO so that half duplex is selected.

Default is NO.

LEVEL If LEVEL is 1, the associated paths support only OSIsessions version 1.

Error! Reference source not found.If LEVEL is 2, the associated paths request OSI sessionsversion 2.

If LEVEL is 3 and CONNECT is INIT, the choice of the OSIsessions version is decided by the correspondent. IfCONNECT is ACCE, the path accepts the level proposed.

Default is 1.

Notes:

The PROFILE statement describes the attributes of a path in using the OSI sessionservices.

If a path is associated with a PROFILE statement the DEVICE, DESTINATION andUSERINFO statements associated with the path are ignored.

Only paths with PROFILE statements may use OSI session services.

TILS User's Guide

9-48 47 A2 04US Rev05

PROGRAM

Scope:

Global

Purpose:

Selects programs from the SCENARIO file to be compiled.

Syntax:

PROGRAM,prognam1-ref-A8,..[,prognam8-ref-A8]

Parameters:

prognam Name of a program in the SCENARIO file.

Notes:

All entry points referenced in PATH statements or inside a program must be in theselected program.

There must be at least one PROGRAM statement in the DECLARATION file. EachPROGRAM statement may select up to eight programs from the SCENARIO file.


47 A2 04US Rev05 9-49

SEED

Scope:

Extension

Purpose:

Defines a constant string associated with a path.

Syntax:

SEED,PATH=pathnam-ref-A12,TEXT='text-A'

Parameters:

PATH A previously declared path. If several paths have the sameuser ID PATH refers to the last declared path of that userID.

TEXT The text string contained in the seed.

Notes:

Several seeds may be associated with one path. A seed is referenced in the program bya field descriptor. Access to seeds is sequential. When all available seeds have beentreated, the first seed becomes the current seed.

Example:

DECLARATION FILE SCENARIO FILE................ .............PATH USERA,MAIN.... :PROGRAM MAINSEED USERA 'ALL IS WELL' :LABEL GOSEED USERA 'OK' :SEND (SEED) :GOTO GO :EOD

After it is opened, USERA sends, "ALL IS WELL" to its correspondent, then "OK", then"ALL IS WELL" again until the path is disconnected.

TILS User's Guide

9-50 47 A2 04US Rev05

SEQUENCE

Scope:

Global

Purpose:

Modifies the number of TILS statements which may be executed in sequence, andcontrols the reaction of TILS if this number is exceeded.

Syntax:

SEQUENCE,number-I [,ACTION={DISCONNECT|TERMINATE}]

Parameters:

number The maximum number of TILS statements that may beexecuted in sequence. This value must lie between 15 and100,000. If this number is greater than 100, a warning isprinted.

ACTION If ACTION is DISCONNECT, the PATH is closed when thenumber of TILS statements executed in sequence exceedsthe value specified in the number parameter.

If ACTION is TERMINATE, the simulation phase is endedwhen the number of TILS statements executed in sequenceexceeds the value specified in the number parameter.

Default is DISCONNECT.

Notes:

TILS statements are interpreted and executed without waiting for any notification; they aretreated in sequence except when SEND, WAIT, or SYNCHRONIZE statements areencountered.

The number of statements able to be executed without waiting for notification is limited to15 when the SEQUENCE statement is not used. This is important because it means thatTILS executes during the simulation phase with a priority exceeding that of the systemoperator console.


47 A2 04US Rev05 9-51

SIZE

Scope:

Hereditary

Purpose:

Defines the size of the workspace, input and output buffers, and the number of private,non-protected registers.

Syntax:

SIZE[,WORKSIZE=wksize-I][,OUTSIZE=outsize-I] [,INSIZE=insize-I][,REGISTER=privregnum-I]

Parameters:

WORKSIZE The size of the workspace in bytes. If this value is 0, noworkspace is available. The size is limited to 524,288bytes (512K).

OUTSIZE The size of the private output buffer in bytes. If thisparameter is absent or its value is 0, the shared outputbuffer whose size is defined in the COMMON statement isused. The size is limited to 4096 bytes (4K).

INSIZE The size of the private input buffer in bytes. If thisparameter is absent or its value is 0, the shared inputbuffer whose size is defined in the COMMON statement isused. The size is limited to 4096 bytes (4K).

REGISTER The number of private registers that may be read or writtenby the program associated with the path. Registers 0 to 16are reserved for TILS, but you can use the private registersnumbered from 17 to 16+n, where n is the value of thisparameter and must be greater than or equal to 1 (thedefault value).

TILS User's Guide

9-52 47 A2 04US Rev05

SIZE

Notes:

1. The SIZE statement defines the fields accessible to the programs associatedwith the paths that following the statement.

2. A path may only access input or output buffers when has an input or outputbelonging to the path.

3. The default values of the parameters apply to all paths until they are overwrittenby a SIZE statement.

4. Only the parameters which are cited are modified by a new SIZE statement, allother parameters retain the previous values.

5. The size of the cumulated workspaces cannot exceed 4,193,280 bytes (4095K).This size represents the sum of all the workspace sizes, with 4 bytes added foreach workspace.


47 A2 04US Rev05 9-53

THINKTIME

Scope:

Global

Purpose:

Switches TILS to thinktime mode and sets the time-limit for it.

Syntax:

THINKTIME,{CONSTANT|INHIBIT|VARIABLE|RANDOM} [,min-I] [,max-I] [,UNIT={MILLI|SEC|MIN}]

Parameters:

CONSTANT The thinktime specified in the path statement is used for allSEND statements.

INHIBIT All SEND statements are executed without thinktime.

VARIABLE The thinktime used depends on the content of register 17.If the value in register 17 is:

<0 - No thinktime is used.

=0 - The constant thinktime specified in the PATHstatement is used.

>0 - The contents of the register is interpreted inmilliseconds and used for the thinktime.

RANDOM A sample is taken to determine uniform distribution ofthinktime. The mean thinktime value is specified in thePATH statement. The maximum interval of thinktimevalues is twice the distance between the mean value andthe upper or lower thinktime limit.

min The minimum value of thinktime.

max The maximum value of thinktime.

UNIT The measurement unit for the limits: MILLI is milliseconds,SEC is seconds, MIN is minutes.

Default is MILLI.

TILS User's Guide

9-54 47 A2 04US Rev05

THINKTIME

Notes:

If the THINKTIME statement is absent, a constant thinktime is used. Specified thinktimesmust be a minimum of 50 milliseconds and a maximum of 1 minute.

The value of the thinktime used is not only determined by this statement, but can also bedefined by the value of the thinktime parameter in the PATH statement, or by the contentsof register 17.

The min and max parameters apply to all modes except INHIBIT.

Example:

DECLARATION FILE................THINKTIME,RANDOM,20,60,UNIT=SECPATH,USERA,TOTO,THINKTIME=30000PATH,USERB,TOTO,THINKTIME=50000PATH,USERC,TOTO,THINKTIME=40000

In this example, the thinktime is random.

For USERA, the mean value is 30 seconds.For USERB, the mean value will be 50 seconds.For USERC, the mean value will be 40 seconds.

For all users (A, B, C), all occurrences of thinktime will lie between 20 and 60 seconds.


47 A2 04US Rev05 9-55

TIMEOUT

Scope:

Hereditary

Purpose:

Specifies a timeout and the reaction to a timeout.

Syntax:

TIMEOUT,delay-I [,ACTION={WARNING|DISCONNECT|TERMINATE|INHIBIT}]

Parameters:

delay The time, in milliseconds, allowed to elapse without anypath activity, before a warning is printed and sent to you.

Default value is 3 minutes.

ACTION If ACTION is WARNING, when the first timeout is detecteda warning is printed and sent to you.

If ACTION is DISCONNECT, when a timeout is detectedthe path is closed after the warning is emitted.

If ACTION is TERMINATE, when a timeout is detected thesimulation phase is ended after the warning is emitted.

If ACTION is INHIBIT, when a timeout is detected no actionis taken.

Default is WARNING.

Notes:

A timeout for a path is detected by the watchdog if the following conditions apply:

• the path is connected and is not waiting for a timer request• the path is not associated with a device of type NONE• the time elapsed since the last output received, the last input sent, or the opening of the

path exceeds the delay specified in this statement.

The value for the delay must lie between 30 seconds and 1 hour.

TILS User's Guide

9-56 47 A2 04US Rev05

TRACE

Scope:

Global

Purpose:

Determines the trace mode.

Syntax:

TRACE,{NONE|EXTERNAL|BOTH|ALPHA|HEXA|SEMAPHORE}

Parameters:

NONE No trace of the dialog is written on the SYSOUT.

EXTERNAL All inputs and outputs are written on the SYSOUT inalphabetical and hexadecimal format.

BOTH Synonym of EXTERNAL.

ALPHA All inputs and outputs are written on the SYSOUT inalphabetical format.

HEXA All inputs and outputs are written on the SYSOUT inhexadecimal format.

SEMAPHORE All inputs, outputs, and semaphore messages are writtenon the SYSOUT in alphabetical and hexadecimal format.Furthermore, the proposed or accepted connectionparameters (MGIB) are written on the sysout inalphabetical and hexadecimal format.

Notes:

If the TRACE statement is absent no trace of the dialog is written on the SYSOUT.Traces of rare events like the opening and closing of a path, the reception of an interrupt,or the occurrence of an error is kept on the sysout regardless of the option chosen.

The format of the trace is explained in the section "Format of the External Trace, DialogTrace, and PRINT statement" in the chapter "TILS Output".

SEMAPHORE should be used only for debugging purposes in conjunction with BULLengineering personnel.


47 A2 04US Rev05 9-57

TRUNCATION

Scope:

Global

Purpose:

Determines the reaction when input and output is truncated.

Syntax:

TRUNCATION,ACTION={WARNING|DISCONNECT|TERMINATE}

Parameters:

WARNING Prints a warning message when an output is longer thanthe output buffer or when an input is longer than the inputbuffer.

DISCONNECT Closes the path.

TERMINATE Ends the simulation phase.

Notes:

If the TRUNCATION statement is absent, a warning message is printed when truncationoccurs. If the truncation is of an output, the warning is only printed when the trace modeis external or semaphore.

TILS User's Guide

9-58 47 A2 04US Rev05

USERINFO

Scope:

Pointed

Purpose:

Provides additional information about the connection.

Syntax:

USERINFO,infnam -D-A8,OPTION=optionstring-A22 [,STATION=station-id-A8]

Parameters:

infnam The name by which this statement is referred to in thePATH statement.

OPTION A string of options transmitted to the destination when a pathis opened. This string is analyzed by the application andmust have the correct syntax for the application. In the caseof IOF, for example, multiple options must be separated byblanks.

STATION The station to which the path is connected.

Notes:

The information provided by USERINFO is transmitted to the application when the path isopened.


The USERINFO statement associated with a path and a PROFILE statement (OSI path)is ignored.


47 A2 04US Rev05 9-59

USERINFO

Example:

DECLARATION FILE................DESTINATION SIM MAILBOX=IOFPATH USERA,TOTO,100,DESTINATION=SIM,USERINFO=INFUSERINFO INF OPTION='NS NM',STATION=RBF1

When USERA is opened it is connected to IOF, no startup is executed, and the pendingmail is not printed. The IOF job is associated with station RBF1.

TILS User's Guide

9-60 47 A2 04US Rev05

WATCHDOG

Scope:

Global

Purpose:

Determine the surveillance period.

Syntax:

WATCHDOG,timeperiod-I [,UNIT={MILLI|SEC|MIN}]

Parameters:

timeperiod The time interval between two periods of surveillance. Thisperiod must be between 2 minutes and 1 hour.

UNIT The unit measurement used for the timeperiod parameter:MILLI is milliseconds, SEC is seconds, MIN is minutes.

Default is MILLI.

Notes:

When TILS receives a notification, the timer is set with the timeperiod specified. Whenthis delay expires, the "watchdog" notifies TILS and a check is made to see if:

• the time-limit has elapsed• the collection of data must be stopped• a timeout has occurred for a path (see TIMEOUT statement).

Once this check is made, the timer is set with the time period. If the time-limit expiresbefore the next notification, the timer is set with an adjusted value.

If the WATCHDOG statement is absent a surveillance period of 2 minutes is used.

47 A2 04US Rev05 10-1

10. SCENARIO File Statements

This section describes all statements used in the SCENARIO file. A summary of allstatements is presented, grouped by type and followed by a summary of their syntax. Inthe section "Description of SCENARIO File Statements", the statements are examined inalphabetical order.

Although most statements may be executed by any type of path, some are specific topaths that use OSI session services and others are specific to paths that use DSAsession services. Under the Usage heading, you will find the category of paths that usethe statement. If you are using TILS to load either an IOF or a TDS application you canignore statements specific to the OSI session services.

TILS User's Guide

10-2 47 A2 04US Rev05

10.1 SUMMARY OF THE SCENARIO FILE SYNTAX

10.1.1 Program and Block Definitions

BLOCK,blocknam-D-A8 [,COMPACT={Y|N}] [,DELIMITOR=delim-D-A1] [,TYPE={ALPHA|HEXA}]PROGRAM,blocknam-D-A8 [,COMPACT={Y|N}] [,DELIMITOR=delim-D-A1]EOD

10.1.2 The Transmission Statements

BREAK[,OPTION={ATTENTION|DMNDTURN|TELEGRAM}] [,VALUE=value-R] [,SOURCE=telegram-F]SEND,SOURCE=source-F [,LEVEL={3|1|5}] [,ERROR=errlab-ref-A8] [,TYPE=type-R] [,CONTROL={NO|YES}] [,HEADER=header-F](+ any record in program without ":" or "*")

10.1.3 The OSI Session Statements

ACTIVITY,OPTION={START|INTERRUPT|DISCARD|RESUME|END} [,NAME=NAME-F] [,TYPE={ REQ|RESP}] [,MARK=syncptnb-R] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,USERINFO=userinfo-F] [,ERROR=errlab-ref-A8]ALARM[,REASON=reason-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

SCENARIO File Statements

47 A2 04US Rev05 10-3

CAPABILITY,SOURCE=source-F [,TYPE={ REQ|RESP}] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,LEVEL={FULL|BEGIN|MIDDLE|END}] [,ERROR=errlab-ref-A8]GIVE_CONTROL[,ERROR=errlab-ref-A8]GIVE_TOKEN[,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,ERROR=errlab-ref-A8]OSI_SEND,SOURCE=source-F [,CATEGORY={ NORMAL|TYPED|EXPEDITED}] [,LEVEL={ FULL|BEGIN|MIDDLE|END}] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,ERROR=errlab-ref-A8]PLEASE_TOKEN[,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]RELEASE[,TYPE={ REQ|RESP}] [,RESULT=resultreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]RESYNC[,TYPE={ REQ|RESP}] [,ACTION={ RESTART|ABANDON|SET}] [,MARK=syncpointnb-I] [,DATA={ REQUESTOR|RESPONDER|RESPCHOICE}] [,MINOR={ REQUESTOR|RESPONDER|RESPCHOICE}] [,MAJOR={ REQUESTOR|RESPONDER|RESPCHOICE}] [,RELEASE={ REQUESTOR|RESPONDER|RESPCHOICE}] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]SYNCPT[,TYPE={ REQ|RESP}] [,STYPE={ MINOR|MAJOR}] [,CONFIRM={ OPTIONAL|EXPLICIT}] [,MARK=syncpointnb-RR] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

TILS User's Guide

10-4 47 A2 04US Rev05

CON_RESP[,RESULT=resultreg-R] [,MARK=syncpointnb-RR] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

10.1.4 The Control Statements

LABEL,labnam-D-A8GOTO,labnam-ref-A8ENTRY,entnam-D-A8CHECKPT[,ERROR=errlab-ref-A8]CALL,entnam-ref-A8CONTROL,STATUS=state-RR [,PATH=name-ref-A12] [,RANK=pathrank-R] [,IDLE=labidle-ref-A8] [,SYNCWT=labsync-ref-A8]EXTERNAL,NAME=name-F,TEXT=text-F,REGISTER=regnum-R [,ERROR=errlab-ref-A8]RETURN[,OPTION={NONE|RETRY|SET}] [,TO=entnam-ref-A8]ON,{OPEN|ERROR|COMMAND|DATA|END|ATTENTION|DMNDTURN| TELEGRAM|ABNTERM|REJECT|RECONNECT| RELEASE_IND|CAPABILITY_IND| PLEASE_TOKEN_IND|GIVE_TOKEN_IND|ACT_START_IND| ACT_RESUME_IND|ACT_INTER_IND|ACT_DISCARD_IND| ACT_END_IND|RESYNC_IND|MINOR_IND|MINOR_CONF| MAJOR_IND|ALARM|CON_IND|TIMEOUT|AUTOEND|ELAPSED} [,entnam-ref-A8]DO,loopnam-D-A8,CONTROL=loopregister-RR,COUNT=loopcount-REND,loopnam-ref-A8CHECK,field1-F,{EQ|NE|LT|LE|GT|GE},field2-F ,LABEL=labnam-ref-A8 [,LENGTH={BOTH|RIGHT|LEFT}] [,ERROR=errlab-ref-A8]SCAN,FOR=field1-F,IN=field2-F,LABEL=labnam-ref-A8 ,OFFSET=resregister-RR [,ERROR=errlab-ref-A8]TEST,value1-R,{EQ|NE|LT|LE|GT|GE},value2-R ,LABEL=labnam-ref-A8TERMINATE,{PATH|TILS} [,MODE={ABORT|SYSTEM}] [,STATUS=status-R]


47 A2 04US Rev05 10-5

10.1.5 The Copy and Conversion Statements

COPY,[OFFSET=offset-RR],TARGET=target-F,SOURCE=source-F [,LENGTH={SOURCE|BOTH|TARGET}] [,TYPE={ALPHA|HEXA}] [,TARGETCODE={NONE|EBCDIC|ASCII}] [,ERROR=errlab-ref-A8]CVBD,TARGET=target-F,VALUE=value-R, [,ERROR=errlab-ref-A8]CVDB,resregister-RR,SOURCE=source-F, [,ERROR=errlab-ref-A8]

10.1.6 The Register Operations

ADD,resregister-RR,operand1-R,operand2-RSUBTRACT,resregister-RR,operand1-R,operand2-RMULTIPLY,resregister-RR,operand1-R,operand2-RAND,resregister-RR,operand1-R,operand2-ROR,resregister-RR,operand1-R,operand2-RDIVIDE,resregister-RR,operand&-R,operand2-R [,ERROR=errlab-ref-A8]ABS,resregister-RR,operandASSIGN,resregister-RR,operand [,SOURCE=source-F][,ERROR=errlab-ref-A8]RANDOM,resregister-RR,operandNOT,resregister-RR,operandLOAD,resregister-RR ,{LEVEL|TOD|INTERRUPT|RANK|PATH|SWITCH|STATUS|REASON|TYPE| CONTROL|SEC|MIN|TIME|OPEN|OSI_LEVEL|TOKEN_REQUEST| SYNCPT_REQ|SYNCPT_CONF}SHIFT,{RIGHT|LEFT} ,TARGET=resregister-RR,SOURCE=operand1-R ,OFFSET=offset-R

10.1.7 The Debugging Statements

DEBUG,{INHIBIT|TRACE|ENABLE}DISPLAY,SOURCE=source-F [,OPTION={H|N}] [,ERROR=errlab-ref-A8]DUMP,{ENABLE|INHIBIT}LOG,SOURCE=source-F [,ERROR=errlab-ref-A8]PRINT,HEADERPRINT,{ALPHA|HEXA|BOTH|LINE},SOURCE=source-F[DISPLAY=value-R] [,ERROR=errlab-ref-A8]PRINT,REGISTER,FROM=register1-RX,TO=register2-RX[DISPLAY=value-R]PRINT,HISTOGRAM[,NAME=histnam-ref-A8][,NUMBER=histnum-R]

TILS User's Guide

10-6 47 A2 04US Rev05

10.1.8 The Synchronization Statements

EVENT[,PATH=pathnam-ref-A12] [,RANK=pathrank-R] [,VALUE=value-R] [ERROR=errlab-ref-A8]SYNCHRONIZE[,REGISTER=resregister-RR]

10.1.9 The File Statements

CLOSE,UNIT=unit-R[,ERROR=errlab-ref-A8]GET,OFFSET=offset-RR,UNIT=unit-R,TARGET=target-F [,ERROR=errlab-ref-A8] [,TYPE={ALPHA|HEXA}]NOTE,resregister-RR [,FROM=field-F] [,UNIT=unit-R] [,ERROR=errlab-ref-A8]OPEN,UNIT=unit-R,NAME=name-F, [,PMD={IN|OUT|APPEND}] [,WORKLIBS=worklibs-nb-R] [,ERROR=errlab-ref-A8]POINT,FROM=key-RR [,FOR=field-F] [,UNIT=unit-R] [,ERROR=errlab-ref-A8]PUT,SOURCE=source-F,UNIT=unit-R [,ERROR=errlab-ref-A8]

10.1.10 The Miscellaneous Statements

HISTOGRAM,value-R [,NAME=histnam-ref-A8] [,NUMBER=histnum-R] [,TYPE=TIME]OCL,SOURCE=source-F [,ERROR=errlab-ref-A8] [,TYPE={ANY|OCL|GCL}]SET,SWITCH=switchnumber-R [,VALUE=value-R] [,STATUS=resreg-RR]RESET[,NAME=histnam-ref-A8] [,NUMBER=histnum-R]STRING,stringnam-D-A8,TYPE={ALPHA|HEXA},TEXT='text-A'SWITCH[,PATH=pathnam-ref-A12] [,RANK=pathrank-R]TILS,SOURCE=source-F [,ERROR=errlab-ref-A8]WAIT,delay-R


47 A2 04US Rev05 10-7

10.2 DESCRIPTION OF SCENARIO FILE STATEMENTS

Each statement of the SCENARIO file is explained in this section.

TILS User's Guide

10-8 47 A2 04US Rev05

ABS

Purpose:

Stores the absolute value of the operand in the specified register.

Usage:

All categories of paths.

Syntax:

ABS,resregister-RR,operand1-R

Parameters:

resregister The register that contains the absolute value of operand1.

operand1 The operand of the ABS operation.

Notes:

This statement belongs to the family of statements that allow integer values to be themanipulated.

Examples:

"ABS *18 -1" stores 1 in register 18.

"ABS *18 *19" stores the absolute value of the contents of register 19 inregister 18.

"ABS *18 ?19" uses the contents of register 19 to determine the number ofthe source register; stores the absolute value of the contentsof this register in register 18.


47 A2 04US Rev05 10-9

ACTIVITY

Purpose:

Starts, interrupts, discards, resumes, or ends activities.

Usage:

Paths using OSI session services.

Syntax:

ACTIVITY,OPTION={START|INTERRUPT|DISCARD|RESUME|END} [,NAME=name-F] [,TYPE={REQ|RESP}] [,MARK=syncptnb-R] [,DATA_TOKEN=datreg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,USERINFO=userinfo-F] [,ERROR=errlab-ref-A8]

Parameters:

OPTION START begins an activity

INTERRUPT interrupts the current activity

DISCARD discontinues the current activity

RESUME resumes the current activity

END ends the current activity

NAME The field that contains the activity identifier. Thisparameter is mandatory and only available if OPTION isSTART or RESUME.

TILS User's Guide

10-10 47 A2 04US Rev05

ACTIVITY

TYPE If TYPE is REQ, the activity requests the service. REQ canonly be specified if the major token is assigned to the pathexecuting the program.

If TYPE is RESP, the activity responds to the request. RESPcan only be specified in an ON ACTIVITY_IND section. Itmay not be used if OPTION is START or RESUME.

Default is REQ.

MARK The first confirmed synchronization point.

DATA_TOKEN Requests the data token. When the value is 1, the datatoken is transferred (if OPTION is START, END, orRESUME) or requested (if OPTION is DISCARD orINTERRUPT). When the value is 0, the token is notaffected.

Default is 0.

MINOR_TOKEN When the value is 1, the minor token is transferred (ifOPTION is START, END, or RESUME) or requested (ifOPTION is DISCARD or INTERRUPT). When the value is0, the token is not affected.

Default is 0.

MAJOR_TOKEN When the value is 1, the major token is transferred (ifOPTION is START, END, or RESUME) or requested (ifOPTION is DISCARD or INTERRUPT). When the value is0, the token is not affected.

Default is 0.

RELEASE_TOKEN When the value is 1, the release token is transferred (ifOPTION is START, END, or RESUME) or requested (ifOPTION is DISCARD or INTERRUPT). When the value is0, the token is not affected.

Default is 0.

USERDATA The contents of this field is transferred as userdata. Themaximum length of this data is 512 bytes if OSI sessionlevel is 1, otherwise it is 10,240 bytes. When thisparameter is absent no userdata is sent.


47 A2 04US Rev05 10-11

ACTIVITY

USERINFO If OPTION is RESUME this field specifies the activity to beresumed.

If OPTION is END and TYPE is RESP, this field containsUSERDATA to be transferred for the PLEASE_TOKENsession service bundled with the ACTIVITY END service.At least one of the token parameters must be specified.

If one of these two conditions are not met, this parametermay not be used.

ERROR Label defining where execution continues if a recoverableerror occurs (see Appendix E for error codes).

Notes:

This statement is only allowed if the ACTIVITY functional unit is negotiated. Theparameters referring to tokens are ignored if the associated functional units are notnegotiated.

A path issuing an ACTIVITY statement must wait for a confirmation unless OPTION isSTART or RESUME.

The activity field contains information about the current activity and about a previouslyinterrupted activity:

BYTES DESCRIPTION0 - 1 length of current activity identifier2 - 7 current activity identifier8 - 9 length of previous activity identifier10 - 15 previous activity identifier

Example:

ACTIVITY OPTION=START NAME=(ALPHA,'WORK') DATA_TOKEN=*19

When this statement is executed, the ACTIVITY "WORK" is started. The data token istransferred if register 19 contains 1 and the token has been negotiated.

TILS User's Guide

10-12 47 A2 04US Rev05

ADD

Purpose:

Stores the sum of the operands in the specified register.

Usage:


Syntax:

ADD,resregister-RR,operand1-R,operand2-R

Parameters:

resregister The register that contains the sum of the operands.

operand1operand2

The operands of the addition.

Notes:

This statement belongs to the family of statements that allow the manipulation that allowinteger values to be manipulated.

A fixed point data overflow exception may occur if the sum is larger than the largestinteger representable on GCOS 7.

Example:

"ADD *18 2 2"

Stores a 4 in register 18.


47 A2 04US Rev05 10-13

ALARM

Purpose:

Requests a user exception report.

Usage:


Syntax:

ALARM[,REASON=reason-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

Parameters:

REASON The reason code associated with the exception. If an invalidcode is specified, the code is replaced by 0 indicating"REASON UNSPECIFIED". For valid codes refer to VCAM-ISO documentation.

Default is 0.

USERDATA The content of this field is transferred as USERDATA. Themaximum length of this data is 512 bytes if OSI sessionlevel is 1, otherwise it is 10,240 bytes. When thisparameter is absent no userdata is sent.

ERROR Label defining where execution continues if a recoverableerror occurs. (See Appendix E for error codes).

Notes:

This statement can only be used if the user exception functional unit has been negotiated(see ALARM parameter of the PROFILE statement) and the data token is assigned to thecorrespondent.

Example:

:ALARM REASON=5;

When this statement is executed and the user exception functional unit is negotiated, thepath requests a user exception report indicating a "Local SS-user Error" (VCAM-code:5).

TILS User's Guide

10-14 47 A2 04US Rev05

AND

Purpose:

Stores the conjunction of the operands in the specified register.

Usage:


Syntax:

AND,resregister-RR,operand1-R,operand2-R

Parameters:

resregister The register that contains the conjunction of the operands.

operand1operand2

The operands of the conjunction.

Notes:

This statement belongs to the family of statements that allow integer values to bemanipulated.

Example:

The three last bytes of register 5 contain the offset of an erroneous statement. To obtainthe correct integer value the first byte must be masked:

"AND *18 *5 %00FFFFFF"

giving, in register 18, the offset of the erroneous statement.


47 A2 04US Rev05 10-15

ASSIGN

Purpose:

Stores a value in the specified register.

Usage:


Syntax:

ASSIGN,resregister-RR,[,VALUE=operand1-R] [,SOURCE=source-F] [,ERROR=errlab-ref-A8]

Parameters:

resregister The register to which a value is assigned.

VALUE The value assigned to the register.

SOURCE A field between 1 and 4 bytes long, stored in the register. Ifthe leading bit is 1, the result is stored as negative value.

Either SOURCE or VALUE must be specified.


Notes:


Examples:

ASSIGN *18 0 initializes register 18 to 0.

ASSIGN *18 *19 stores the value of register 19 in register 18.

TILS User's Guide

10-16 47 A2 04US Rev05

BLOCK

Purpose:

Defines a BLOCK.

Usage:


Syntax:

BLOCK,blocknam-D-A8[,COMPACT={Y|N}] [,DELIMITOR=delim-D-A1] [,TYPE={ALPHA|HEXA}]

Parameters:

blocknam The name of the block.

COMPACT If COMPACT is Y, trailing blanks are suppressed.

If COMPACT is N, trailing blanks are not suppressed.

Default is Y.

DELIMITOR If this parameter is specified and is not blank, the recordsread are searched from the end to the beginning (right to left)and all characters up to and including the delimiter aredisregarded. If a delimiter is not found in the record, nocharacters are disregarded.

TYPE If TYPE is ALPHA, text contained in the records of theBLOCK is in alphanumeric format.

If TYPE is HEXA, text contained in the records is inhexadecimal format and will be translated before beingstored. If characters other than "0123456789ABCDEF" arefound in the record, an error is detected at compilationtime.

Default is ALPHA.


47 A2 04US Rev05 10-17

BLOCK

Notes:

This statement introduces a block. It may not be used inside a program.

The name of the block is used by the DATA statement in the DECLARATION file toassociate the block with a path. The program of a path refers to a block through a fielddescriptor that cites the rank of the block in the DATA statement. The rank of the blockmay be contained in a register.

Example:

BLOCK MBLOCK;THIS ENTIRE RECORD IS PART OF MBLOCK:EOD:BLOCK NBLOCK,DELIMITOR='/'IN BLOCK / OUTSIDE BLOCK / RECORD OF BLANKS:EOD:BLOCK OBLOCK,DELIMITOR='?'THE OLD DELIMITOR / IS INVALID ?:EOD:BLOCK HXBLK,TYPE=HEXA;C1C2C3F0F1:EOD:PROGRAM PROG;:SEND SOURCE=(BLOCK,1) ....................:EOD

The path executing PROGRAM PROG sends "THIS ENTIRE RECORD IS PART OFMBLOCK" as input when the BLOCK MBLOCK is cited as the first block in a DATAstatement associated with the path. If BLOCK HXBLK is cited "ABC01" is sent.

TILS User's Guide

10-18 47 A2 04US Rev05

BREAK

Purpose:

Sends an interrupt to the correspondent.

Usage:

Paths using DSA session services.

Syntax:

BREAK[,OPTION={ATTENTION|DMNDTURN|TELEGRAM}] [,VALUE=value-R] [,SOURCE=telegram-F]

Parameters:

OPTION This parameter defines type of interrupt. DMNDTURN maynot be specified if the path is in TWS mode.

VALUE The value to be transmitted with the interrupt. Thisparameter is not significant if "TELEGRAM" has beenspecified for the OPTION parameter.

Default value is 0.

SOURCE A field descriptor that addresses the character string to besent as a telegram. This parameter is significant only if"TELEGRAM" is specified for the OPTION parameter.

Notes:

The default value corresponds to the use of the break key by a terminal user. Thisstatement may not be executed in an ON END section nor by a path using OSI sessionservices.


47 A2 04US Rev05 10-19

CALL

Purpose:

Executes a subroutine.

Usage:


Syntax:

CALL,entrynam-ref-A8

Parameters:

entrynam The statement following this entry is the next one executed.

Notes:

The statements following the specified entry point are executed as a subroutine. If aRETURN statement is encountered, execution is switched back to the statement followingthe CALL statement. Up to 8 calls may be nested.

The treatment of an ON condition produces a "simulated call" and is included in the 8 calllimit. If the limit is exceeded, the path is closed.

TILS User's Guide

10-20 47 A2 04US Rev05

CAPABILITY

Purpose:

Sends or responds to Capability data.

Usage:


Syntax:

CAPABILITY,SOURCE=source-F [,TYPE={REQ|RESP}] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,LEVEL={FULL|BEGIN|MIDDLE|END}] [,ERROR=errlab-ref-A8]

Parameters:

SOURCE This field contains the data to be sent.

TYPE If TYPE is REQ, data is sent as capability data.

If TYPE is RESP, responds to the request by sending data ascapability data. RESP may only be specified in an ONCAPABILITY_IND section.

Default is REQ.

DATA_TOKEN This parameter is ignored if the token is not negotiated.

If the value is 1, the path requests the data token.

If the value is 0 or TYPE is specified as REQ, the token isnot affected.

Default is 0.


47 A2 04US Rev05 10-21

CAPABILITY

MINOR_TOKEN This parameter is ignored if the token is not negotiated.

If the value is 1, the path requests the minor token.


Default is 0.

MAJOR_TOKEN This parameter is ignored if the token is not negotiated.

If the value is 1, the path requests the major token.

If the value is 0 or TYPE is specified as REQ, the token isnot affected

Default is 0.

RELEASE_TOKEN This parameter is ignored if the token is not negotiated.

If the value is 1, the path requests the release token.


Default is 0.

USERDATA The contents of this field is transferred as userdata. Themaximum length of this data is 512 bytes if OSI sessionlevel is 1, otherwise it is 10,240 bytes. When thisparameter is absent no userdata is sent.

This parameter may only be used if TYPE is RESP and atleast one of the token parameters is requested.

LEVEL If LEVEL is FULL, the input is a full Session Service DataUnit (SSDU).

Error! Reference source not found.If LEVEL is BEGIN, the input is the beginning of an SSDU.

If LEVEL is MIDDLE, the input is the middle part of an SSDU.

If LEVEL is END, the input is the last part of an SSDU.


TILS User's Guide

10-22 47 A2 04US Rev05

CAPABILITY

This parameter may not be used if OSI sessions level is 1because in this case, only full SSDUs can be sent and LEVELis forced to FULL. (See the LEVEL parameter of thePROFILE statement).

Default is FULL.


Notes:

This statement can only be used if the ACTIVITY functional unit has been negotiated andwhen no activity is in progress.

A path issuing a CAPABILITY statement with TYPE specified as REQ must wait for aresponse.

The parameters referring to tokens are ignored if the associated functional units are notnegotiated.

If no CAPABILITY_IND ON section is used, TILS responds to the reception of capabilitydata with data of length 0. (That is, TILS sends data with length = 0)


47 A2 04US Rev05 10-23

CHECK

Purpose:

Tests the contents of a field.

Usage:


Syntax:

CHECK,field1-F,{EQ|NE|LT|LE|GT|GE},field2-F ,LABEL=labnam-ref-A8 [,LENGTH={BOTH|RIGHT|LEFT}] [,ERROR=errlab-ref-A8]

Parameters:

field1 The field descriptor of the character string used as the leftargument; where the condition is:

EQ equalNE not equalLE less than or equalLT less thanGT greater thanGE greater than or equal

field2 The field descriptor of the character string used as the rightargument to the condition.

LABEL Label where execution is sent if the condition is fulfilled.

TILS User's Guide

10-24 47 A2 04US Rev05

CHECK

LENGTH If LENGTH is BOTH, the length of both character strings issignificant.

If LENGTH is LEFT, only the length of the character stringused as the left argument is significant.

If length is RIGHT, only the length of the character stringused as the right argument is significant.


Example:

:CHECK (OUT,0,7) EQ (ALPHA,'TEST OK')> LABEL=EXIT,ERROR=CHKFAIL;

This statement checks the contents of the output buffer. If "TEST OK" is found, theexecution is branched at label EXIT.


47 A2 04US Rev05 10-25

CHECKPT


Purpose:

Defines a checkpoint.

Usage:

DSA paths only.

Syntax:

CHECKPT[,ERROR=errlab-ref-A8]

Parameters:


Notes:

Once the checkpoints are defined, the RETURN statement with OPTION=SET allowsHybrid paths to resume execution at the last defined checkpoint at reconnection.

This statement is only valid for Hybrid paths. A "normal" DSA path cannot execute theCHECKPT statement; it will be ignored.

Example:

......TX-001:CHECKPT;TX-002:CHECKPT;......

This instruction inserts two checkpoints. The first one is inserted after the transaction TX-001 is called, and the second one after transaction TX-002.


TILS User's Guide

10-26 47 A2 04US Rev05

CLOSE

Purpose:

Ends the association between a unit and a file, then closes the file.

Usage:


Syntax:

CLOSE,UNIT=unit-R[,ERROR=errlab-ref-A8]

Parameters:

UNIT The unit with which the file to be closed is associated.



47 A2 04US Rev05 10-27

CON_RESP

Purpose:

Responds to a connection indication.

Usage:


Syntax:

CON_RESP[,RESULT=resultreg-R] [,MARK=syncpointnb-RR] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

Parameters:

RESULT If RESULT is 0, the connection is rejected.

If RESULT is 1, the connection is accepted.

MARK The value contained in this register is the last confirmedsynchronization point. TILS controls only that the value ispositive and less than 1,000,000.

Default is 1.

DATA_TOKEN If the value is 1, the path requests the data token. Forother values, the token is not affected.

Default is 0.

MINOR_TOKEN If the value is 1, the path requests the minor token. Forother values, the token is not affected.

Default is 0.

TILS User's Guide

10-28 47 A2 04US Rev05

CON_RESP

MAJOR_TOKEN If the value is 1, the path requests the major token. Forother values, the token is not affected.

Default is 0.

RELEASE_TOKEN If the value is 1, the path requests the release token. Forother values, the token is not affected.

Default is 0.

USERDATA The contents of this field is transferred as userdata. Themaximum length of this data is 512 bytes if OSI sessionlevel is 1, otherwise it is 10,240 bytes. When thisparameter is absent, no userdata is sent.


Note:

This statement may only be used inside an ON CON_IND section.


47 A2 04US Rev05 10-29

CONTROL

Purpose:

Consults the state of a path and controls the execution of the program accordingly.

Usage:


Syntax:

CONTROL,STATUS=state-RR [,PATH=name-ref-A12] [,RANK=pathrank-R] [,IDLE=labidle-ref-A8] [,SYNCWT=labsync-ref-A8]

Parameters:

STATUS The register that contains the state of the specified path.

PATH The name of the target path declared in the TILS session.If neither this parameter nor the RANK parameter isspecified, the state of the current path is stored in theregister.

Default: The target path is the path executing theCONTROL statement.

RANK The rank of the target path declared in the TILS session. Ifneither this parameter nor the PATH parameter isspecified, the state of the current path is stored in theregister.

IDLE The label where the execution is sent if the specified pathis idle. If this parameter is absent the statement followingthe CONTROL statement is executed.

SYNCWT The label where the execution is sent if the specified pathwaits for the reception of a TILS event. If this parameter isabsent the statement following the CONTROL statement isexecuted.

TILS User's Guide

10-30 47 A2 04US Rev05

CONTROL

Notes:

The definition of the path states is found in Appendix A.

Example:

CONTROL STATUS=*19 PATH=USERA;

This statement is equivalent to the following sequence of TILS statements:

SWITCH PATH=USERALOAD *19 STATUSAND *19 *19 %000000FFSWITCH


47 A2 04US Rev05 10-31

COPY

Purpose:

Copies character strings into the WORKSPACE, POOL, REGISTER, or INHEADlocations.

Usage:


Syntax:

COPY,[OFFSET=offset-RR],TARGET=target-F,SOURCE=source-F [,LENGTH={SOURCE|BOTH|TARGET}] [,TYPE={ALPHA|HEXA}] [,TARGETCODE={NONE|EBCDIC|ASCII}] [,ERROR=errlab-ref-A8]

Parameters:

OFFSET This register contains the offset of the first free byte in thetarget field after a transfer has occurred. If this parameteris absent, no register is filled with the offset value.

TARGET The field descriptor of the location where the characterstring is copied. TARGET must be of type WORK, POOL,REGISTER, or INHEAD.

SOURCE The field descriptor of the character string to be copied.

LENGTH If LENGTH is SOURCE, only the length of the source fieldis significant.

If LENGTH is BOTH, the length of both character strings issignificant.

If LENGTH is TARGET, only the length of the target field issignificant.

Default is SOURCE.

TILS User's Guide

10-32 47 A2 04US Rev05

COPY

TYPE If TYPE is ALPHA, the text in SOURCE is alphanumeric.

If TYPE is HEXA, the text in SOURCE is hexadecimal andmust be converted. You cannot assign both this parameterand the TARGETCODE parameter.

Default is ALPHA.

TARGETCODE If TARGETCODE is NONE, a translation is not made.

If TARGETCODE is EBCDIC, the character string istranslated from ASCII to EBCDIC.

If TARGETCODE is ASCII, the character string istranslated from EBCDIC to ASCII. The padding characteris the ASCII blank (hexadecimal 20).

Default is NONE

Note: there is no control that checks for the expectedcode.


Notes:

Protected registers (1 to 16) may not be specified as the target. If consulting andexecuting paths differ after execution of a SWITCH statement, only a sharable register orthe pool may be modified by the COPY statement.

Examples:

COPY OFFSET=*18 TARGET=(WORK) SOURCE=(ALPHA,'GO')

The WORKSPACE contains "GO" in the first 2 bytes, and register 18 the value 2.

COPY OFFSET=*18 TARGET=(WORK,OFFSET=5) SOURCE=(ALPHA,'GO')

Register 18 contains the value 7.

COPY OFFSET=*18 TARGET=(WORK) SOURCE=(ALPHA,' ') LENGTH=BOTH

The entire workspace is filled with blanks.


47 A2 04US Rev05 10-33

CVBD

Purpose:

Converts a binary number into an unsigned, unpacked decimal representation.

Usage:


Syntax:

CVBD,TARGET=target-F,VALUE=value-R[,ERROR=errlab-ref-A8]

Parameters:

TARGET The field descriptor that identifies the location of thedecimal representation. This location must be either oftype WORK or POOL. The length of the TARGET mustnot exceed 31 bytes.

VALUE The value to be converted.


Notes:

If the value is negative its absolute value is converted. If consulting and executing pathsdiffer, after execution of a SWITCH statement, only a sharable register or the pool may bemodified by the CVBD statement.

Examples:

CVBD TARGET=(WORK,0,4) VALUE=4.

The workspace contains "0004" in the first 4 bytes ("F0F0F0F4" in hexadecimal format).

CVBD TARGET=(WORK,0,4) VALUE=*18.

The WORKSPACE contains "0004" in the first 4 bytes ("F0F0F0F4" in hexadecimalformat) when the register 18 contains value 4.

TILS User's Guide

10-34 47 A2 04US Rev05

CVDB

Purpose:

Converts an unsigned, unpacked decimal representation to a binary number.

Syntax:

CVDB,resregister-RR,SOURCE=source-F[,ERROR=errlab-ref-A8]

Parameters:

resregister The register that contains the converted value.

SOURCE The field descriptor that identifies the location of thedecimal representation. The length of the SOURCE mustnot exceed 31 bytes.


Notes:

The decimal number should not be negative.

Example:

CVDB *18,SOURCE=(ALPHA,'4')

Register 18 contains the value 4 after the operation.


47 A2 04US Rev05 10-35

DEBUG

Purpose:

Controls the tracing of executed TILS statements.

Usage:


Syntax:

DEBUG,{INHIBIT|TRACE|ENABLE}

Parameters:

INHIBIT Stops further tracing of the statements executed by thepath.

TRACE Activates trace of the operator code and the offset of theexecuted statement.

ENABLE Activates full tracing.

Notes:

The format of the output generated for the option TRACE is described in Section 5-Format of the External Trace. ENABLE should be used only in conjunction with BULLengineering personnel.

This statement may cancel the effect of the TILS operator command DEBUG and viceversa.

Example:

......:DEBUG TRACE:CALL SUBPROG:ASSIGN *26 45:SEND SOURCE=(WORK,0,*18):DEBUG INHIBIT......

Only the statements between the two DEBUG statements will be debugged.

TILS User's Guide

10-36 47 A2 04US Rev05

DISPLAY

Purpose:

Displays the contents of a field on the TILS operator console.

Usage:


Syntax:

DISPLAY,SOURCE=source-F[,OPTION={ H|N}][,ERROR=errlab-ref-A8]

Parameters:

SOURCE The field descriptor indicating the location of the characterstring displayed.

OPTION If OPTION is H, the message is prefixed with the TILSRON.

If OPTION is N, no prefix identifies the source of themessage.


Notes:

This statement is ignored if the length of the field displayed is 0. The field is truncated to255 bytes if this length is exceeded.

Example:

DISPLAY SOURCE=(WORK,0,20) OPTION=N

When this statement is executed the first 20 characters of the workspace are displayedon the TILS operator console.


47 A2 04US Rev05 10-37

DIVIDE

Purpose:

Stores the quotient of the operands in the specified register.

Usage:


Syntax:

DIVIDE,resregister-RR,operand1-R,operand2-R [,ERROR=errlab-ref-A8]

Parameters:

resregister The register that contains the quotient of the operands.

operand1operand2

The operands of the division.

ERROR Label defining where execution continues if the value ofoperand2 is 0.

Notes:


Example:

DIVIDE *18 6 2

stores 3 in register 18.

TILS User's Guide

10-38 47 A2 04US Rev05

DO

Purpose:

Defines a loop.

Usage:


Syntax:

DO,loopnam-D-A8,CONTROL=loopregister-RR,COUNT=loopcount-R

Parameters:

loopnam The name of the loop.

CONTROL The register used as control variable for the loop.

COUNT The counter of the number of times the statements of theloop are executed.

Notes:

When this statement is encountered, the value specified as COUNT is stored in theCONTROL register. When the END statement corresponding to the loop is encountered,the value is decreased by 1 and tested. If the value is positive, the execution is sent tothe statement following the DO statement.

All statements of the loop are executed as least once. Up to 20 loops may be nested.

The loop register is not protected by TILS.


47 A2 04US Rev05 10-39

DO

Example:

:DO MLOP CONTROL=*19 COUNT=-1;:ASSIGN *18 0;:END MLOP; MLOP IS EXECUTED ONCE:DO MLOP1 CONTROL=*19 COUNT=100;:ASSIGN *19 0;:END MLOP1; MLOP1 IS ONLY EXECUTED ONCE:DO MLOP2 CONTROL=*19 COUNT=100;:DISPLAY SOURCE=(ALPHA,'OH NO');:END MLOP2;

MLOP2 displays "OH NO" 100 times on the TILS operator console.

TILS User's Guide

10-40 47 A2 04US Rev05

DUMP

Purpose:


Usage:


Syntax:


Parameters:

ENABLE Allows the internal states of syntax analysis to be printeduntil a DUMP INHIBIT statement occurs.


Notes:

This statement should be used only in conjunction with BULL engineering personnel.


47 A2 04US Rev05 10-41

END

Purpose:

Ends loops and transfers the execution according to the contents of the loop register.

Usage:


Syntax:

END,loopnam-ref-A8

Parameters:

loopnam The name of the loop to be closed.

Notes:

See DO statement.

TILS User's Guide

10-42 47 A2 04US Rev05

ENTRY

Purpose:

Defines an entry point.

Usage:


Syntax:

ENTRY,entrynam-D-A8

Parameters:

entrynam The name of entry point. This name must be unique withinthe programs selected by a PROGRAM statement in theDECLARATION file.

Notes:

This statement defines a subroutine that may be called from any program either throughthe CALL statement or when a condition associated with this entry through an ONstatement occurs.

Entry points are referred to in the PATH statement of the DECLARATION file anddetermine the first statement a path is to execute.

PROGRAM statements also generate entry points bearing the same name as theprogram.

Example:

......:ENTRY PRG2:ASSIGN *18 1......:RETURN......

Statements between ENTRY and RETURN are executed when the subroutine PRG2 iscalled.


47 A2 04US Rev05 10-43

EOD

Purpose:

Delimits a program or block.

Usage:


Syntax:

EOD

Notes:

The execution of an EOD statement closes a path.

If the end of the SCENARIO file is encountered and an EOD is expected, the missingEOD is assumed to be present.

TILS User's Guide

10-44 47 A2 04US Rev05

EVENT

Purpose:

Notifies a path of an event.

Syntax:

EVENT[,PATH=name-ref-A12][,RANK=pathrank-R][,VALUE=value-R] [,ERROR=errlab-ref-A8]

Parameters:

PATH The name of the target PATH declared in the current TILSsession. If neither the path name nor the rank, is specified,an event for the path executing the EVENT statement isposted.

RANK The rank of the target path declared in the TILS session. Ifthis parameter is not specified the PATH parameter shouldbe used.

VALUE The value transmitted with the notification.

ERROR Label defining where execution is branched if a recoverableerror occurs. (See Appendix E for error codes).

Notes:

This statement, in conjunction with the SYNCHRONIZE statement, allows paths to besynchronized. An event posted through an EVENT statement is ignored by paths thathave not executed the SYNCHRONIZE statement.

An unrecoverable error occurs if the total number of posted events not received by TILSexceeds half the number of declared paths, or 50 if there are more than 100 paths.

Example:

PATH 1 PATH2

...... ......:SYNCHRONIZE ............ :EVENT PATH=PATH1...... ......

PATH1 executes the SYNCHRONIZE statement and then waits for an event to be postedusing the EVENT statement by PATH2. Once the event is received, PATH1 resumes itsexecution.


47 A2 04US Rev05 10-45

EXTERNAL

Purpose:

Calls an external procedure.

Usage:


Syntax:

EXTERNAL,NAME=name-F,TEXT=text-F,REGISTER=register-RR [,ERROR=errlab-ref-A8]

Parameters:

NAME The name of a procedure linked as LKU to the sharedmodule SMTILS. This shared module must be loaded inmemory from a shared module library associated with theTILS step as "joblib".

TEXT The field communicated to the external procedure. OnlyWORK or POOL are valid field descriptor types here. If theexecuting path is not the consulting path then only POOL isallowed. The length of this field may not exceed 32K bytes.

REGISTER The content of this register is transmitted as thirdparameter to the external procedure. The value returned isstored in the same register.


TILS User's Guide

10-46 47 A2 04US Rev05

EXTERNAL

Notes:

This statement calls the external procedure cited in the NAME parameter. The externalprocedure must have these three parameters:

length-of-field (a 4-byte integer)pointer-to-field (a pointer)value (a 4-byte integer).

The EXTERNAL procedure may replace the field indicated by the pointer-to-field by thevalue in the value parameter of length specified in the length-of-field. Modificationsbeyond the length specified are not taken into account by TILS and may prove dangerous.For this reason the EXTERNAL statement is recommended for use only by BULLengineering personnel.

NOTE: This statement requires the presence of a private shared module calledSMTILS. If you are not using the EXTERNAL statement this module will notexist and results in the following warning message in the Job OccurrenceReport:

WARNING DY02 Error detected. Shared module SMTILS not found


47 A2 04US Rev05 10-47

GET

Purpose:

Reads the current record from a file associated with the path.

Usage:


Syntax:

GET,OFFSET=offset-RR,UNIT=unit-R,TARGET=target-F, [,ERROR=errlab-ref-A8][,TYPE={ALPHA|HEXA}]

Parameters:

OFFSET This register contains the offset of the first free byte in thetarget field after the record has been read.

UNIT The unit with which a file is associated as specified in theOPEN statement. This value must lie between 1 and 8.

TARGET The field descriptor indicating the location where the recordis read. TARGET must be of type WORK or POOL. OnlyPOOL is allowed if the consulting path is not the executingpath.


TYPE If TYPE is ALPHA, the record to be read is in alphanumericformat and does not need to be translated.

If TYPE is HEXA, the record is in edited hexadecimalformat and must be translated.

Default is ALPHA.

TILS User's Guide

10-48 47 A2 04US Rev05

GIVE_CONTROL

Purpose:

Gives all available tokens to the correspondent.

Usage:


Syntax:

GIVE_CONTROL[,ERROR=errlab-ref-A8]

Parameters:


Notes:

This statement may only be used if the activity management functional unit has beennegotiated and the path owns the major token.

The GIVE_CONTROL statement gives all available tokens and is not equivalent to theGIVE_TOKEN statement that gives only the specified number of tokens (between oneand four).


47 A2 04US Rev05 10-49

GIVE_TOKEN

Purpose:

Gives one or all specified tokens to the other application.

Usage:


Syntax:

GIVE_TOKEN[,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,ERROR=errlab-ref-A8]

Parameters:

DATA_TOKEN If this value is 1, the data token is transferred, if not, thetoken is not affected.

Default is 0.

MINOR_TOKEN If this value is 1, the minor token is transferred, if not, thetoken is not affected.

Default is 0.

MAJOR_TOKEN If this value is 1, the major token is transferred, if not, thetoken is not affected.

Default is 0.

RELEASE_TOKEN If this value is 1, the release token is transferred, if not, thetoken is not affected.

Default is 0.


TILS User's Guide

10-50 47 A2 04US Rev05

GIVE_TOKEN

Notes:

A recoverable error if you attempt to transfer a token which is not available or which thepath does not own.

Example:

GIVE_TOKEN DATA_TOKEN=*18 MINOR_TOKEN=*18

The data and minor tokens are transferred if register 18 contains 1.


47 A2 04US Rev05 10-51

GOTO

Purpose:

Branches execution unconditionally to a label.

Usage:


Syntax:

GOTO,labnam-ref-A8

Parameters:

labnam The name of a label within the same program.

Example:

......:LABEL SAM:DISPLAY SOURCE=(ALPHA,'PLAY IT AGAIN SAM'):GOTO SAM......

On the TILS operator console, the message "PLAY IT AGAIN SAM" is displayed"indefinitely" by the path that executes this statement.

TILS User's Guide

10-52 47 A2 04US Rev05

HISTOGRAM

Purpose:

Enters a value in a histogram.

Usage:


Syntax:

HISTOGRAM,value-R[,NAME=histnam-ref-A8][,NUMBER=histnum-R] [,TYPE=TIME]

Parameters:

value-R The value entered in the histogram. If this value isnegative, the absolute value is used.

NAME The name of the histogram.

NUMBER The rank of the histogram as declared in theDECLARATION file.

TYPE If TIME is specified, it is assumed that the value entered isa time expressed in multiples of 256 microseconds, relativeto the first event. The value is converted into secondsbefore it is entered in the histogram.

Notes:

This statement is used to increment user-defined histograms. These should be declaredusing the HISTOGRAM statement of the DECLARATION file after all paths have beendefined. Histograms may be addressed by name through the NAME parameter or by theirrank in the HISTOGRAM declarations.

The box corresponding to the proposed value is determined by dividing the proposedvalue by the unit associated with the selected histogram.


47 A2 04US Rev05 10-53

LABEL

Purpose:

Defines a label.

Usage:


Syntax:

LABEL,labnam-D-A8

Parameters:

labnam The name of the label. This name must be unique withinthe program.

TILS User's Guide

10-54 47 A2 04US Rev05

LOAD

Purpose:

Stores TILS parameters in a register.

Usage:

Depends on the option chosen.

Syntax:

LOAD,resregister-RR,{LEVEL|TOD|INTERRUPT|RANK|PATH|SWITCH| STATUS|REASON|TYPE|CONTROL|SEC|MIN|TIME|OPEN| OSI_LEVEL|TOKEN_REQUEST|SYNCPT_REQ|SYNCPT_CONF}

Parameters:

resregister The register that contains the parameter.

OPTIONS One of the specified options; some of which apply to allpaths and others only to paths using the DSA sessionlayer. These options are described by category.

Options that apply to all categories of paths

LEVEL The execution level (see Appendix B).

TOD The time relative to the first event, expressed in multiplesof 256 microseconds.

RANK The rank of the PATH executing this statement.

PATH The number of declared paths in the TILS session.

SWITCH The rank of the consulting path.

STATUS Bytes 1-3: offset of the last statement executed by the pathwhile the execution level is 0.

Byte 4: state of the path. (See Appendix A).


47 A2 04US Rev05 10-55

LOAD

SEC The time relative to the first event expressed in seconds.

MIN The time in minutes relative to the first connection of thefirst path.

TIME The time remaining, in milliseconds, until the time-limit isreached.

OPEN The number of currently opened paths.

Options that apply to DSA paths

INTERRUPT The interrupt value. This form is permitted only in thecontext of an ON section for an interrupt indication.

TYPE The record type of the last output received.

CONTROL The register contains 1 if the last output received was acontrol record, if not it contains 0.

REASON This option may only be used in an ON REJECT session.The reasons for rejection are stored in the register as follows:

Byte 1: status codeByte 2: complementary reason codeBytes 3-4: reason code.

Options that apply to OSI paths

OSI_LEVEL Specifies the OSI session level:

-1 indicates that the path is not an OSI path.

0 indicates that the path is an OSI path, but only OSIsessions version 1 are implemented.

1 indicates that the path is an OSI path, and that OSIsessions version 1 are negotiated.

Error! Reference source not found.2 indicates that the path is an OSI path, and that OSIsessions version 2 are negotiated.


TILS User's Guide

10-56 47 A2 04US Rev05

LOAD

TOKEN_REQUEST The format of this register follows the same convention asregister 13; each byte equals one token. The first byte isthe DATA token, the second, the MINOR token, the thirdbyte is the MAJOR token and last byte is the RELEASEtoken.

"FF"X the token is not available.

"00"X the token should not be loaded.

"01"X the token should be loaded.

SYNCPT_REQ The last synchronization point proposed by the session layer.

SYNCPT_CONF The last confirmed synchronization point.

Notes:

This statement allows programs to access the context of the path that execute thestatement.

Example:

:LOAD *20 OSI_LEVEL

The private register 20 contains the OSI session protocol level.


47 A2 04US Rev05 10-57

LOG

Purpose:

Writes the contents of a field to the LOGFILE.

Usage:


Syntax:

LOG,SOURCE=source-F[,ERROR=errlab-ref-A8]

Parameters:

SOURCE The field descriptor indicating the location of the characterstring written to the logfile.


Notes:

This statement is ignored if the FILE_L is not assigned in the JCL or if the use of theLOGFILE is inhibited.

Example:

LOG SOURCE=(WORK,0,20)

When this statement is executed, the first 20 characters of the workspace are written onthe logfile.

TILS User's Guide

10-58 47 A2 04US Rev05

MULTIPLY

Purpose:

Stores the product of the operands in the specified register.

Usage:


Syntax:

MULTIPLY,resregister-RR,operand1-R,operand2-R

Parameters:

resregister The register that contains the product of the operands.

operand1operand2

The operands of the multiplication.

Notes:


This statement may cause a fixed point data overflow exception if the product exceedsthe largest integer value representable on GCOS 7.

Example:

MULTIPLY *18 2 2

Stores "4" in register 18.


47 A2 04US Rev05 10-59

NOT

Purpose:

Stores the complementary bit string of the operand.

Usage:


Syntax:

NOT,resregister-RR,operand1-R

Parameters:

resregister The register that contains the result.

operand1 The value that is inverted.

Notes:


Example:

:ASSIGN *18 %FFFF0000:NOT *18 *18;

Register 18 contains "%0000FFFF" after these operations.

TILS User's Guide

10-60 47 A2 04US Rev05

NOTE

Purpose:

Stores a key that enables the access of a block record, a seed, or a file record.

Usage:


Syntax:

NOTE,resregister-RR[,FROM=field-F][,UNIT=unit-R] [,ERROR=errlab-ref-A8]

Parameters:

resregister The register that contains the key.

FROM The field descriptor designating either a block or a seed.Either FROM or UNIT, but not both, must be present.

UNIT The unit number associated with the file. This numbermust be associated with an open file in input mode. EitherFROM or UNIT, but not both, must be present


Notes:

1. This statement stores a key that enables access to, but does not modify theblock record, the seed, or the file record. The key can only be used by a path toreposition a specific field using the POINT statement.

2. Up to 4000 keys (4000 consecutive NOTE statements) can be managed byTILS at a given time for all of the paths. The TILS session will be stopped if thislimit is exceeded.


47 A2 04US Rev05 10-61

OCL

Purpose:

Sends an OCL command or directive to the operating system.

Syntax:

OCL,SOURCE=source-F[,ERROR=errlab-ref-A8][,TYPE={ANY|OCL|GCL}]

Parameters:

SOURCE The field descriptor indicating the location of the OCLcommand or directive.


TYPE If TYPE is ANY, the text is assumed to be an OCLcommand. If it is not recognized as a command then anattempt is made to treat it as a directive. If this issuccessful, a warning is sent.

If TYPE is OCL, the text is treated as an operatorcommand.

If TYPE is GCL, the text is treated as a directive.

Notes:

The OCL command is transmitted with main operator privileges.

If the OCL command is a TILS operator command, it may only be treated after the currentsequence and all notifications received by TILS prior to the command have been treatedby TILS.

The default value of TYPE is governed by the NAME statement of the DECLARATIONfile. It is ANY unless the OCL parameter of the NAME statement is used. If the TYPEparameter is specified as ALL, only "TYPE=GCL" will ensure treatment of the text as adirective.

TILS User's Guide

10-62 47 A2 04US Rev05

OCL

Examples:

OCL SOURCE=(ALPHA,'DJ EX')

When this statement is executed, the directive "DJ EX" is transmitted to the operatingsystem.

SCENARIO FILE ............. :OCL SOURCE=(ALPHA,'TILS STOP') :PRINT ALPHA SOURCE=(ALPHA,'I AM PRINTED') :WAIT 1000

The STOP command is processed only after the current sequence is treated.


47 A2 04US Rev05 10-63

ON

Purpose:

Determines how conditions are treated.

Usage:

Depends on the chosen option.

Syntax:

ON,{OPEN|ERROR|COMMAND|DATA|END|REJECT|RECONNECT| ATTENTION|TELEGRAM|DMNDTURN|ABNTERM| RELEASE_IND|CAPABILITY_IND|PLEASE_TOKEN_IND| GIVE_TOKEN_IND|ACT_START_IND|ACT_RESUME_IND| ACT_INTER_IND|ACT_DISCARD_IND|ACT_END_IND|CON_IND| RESYNC_IND|ALARM|MINOR_IND|MINOR_CONF|MAJOR_IND TIMEOUT|AUTOEND|ELAPSED} [,entrynam-ref-A8]

Parameters:

ON entry points One of the listed conditions must occur to activate the ONsection. See the description of the ON statement for theDeclaration file in the chapter "DECLARATION FileStatements".

entrynam The name of an entry point that determines the subroutine tobe executed. This subroutine may not contain anyasynchronous statements. If this parameter is absent, anyprevious ON statements for the condition are cancelled andthe association between the condition and its entry point isdissolved.

Notes:

Once this statement is executed, the subroutine determined by the entry point will beexecuted each time the condition occurs. The effect of this statement may be cancelledby a similar statement specifying no entry point.

TILS User's Guide

10-64 47 A2 04US Rev05

ON

Example:

:PROGRAM TDSINF;:ON DATA,LEV;:LABEL GOTO;TRANSACT 123:GOTO GOTO;:ENTRY LEV;:DISPLAY SOURCE=(ALPHA,'MSG WITHOUT TURN RECEIVED'):ON DATA;:RETURN;.............

The program sends "TRANSACT 123" continuously. The first time that an output withoutturn is received, you are notified by the message "MSG WITHOUT TURN RECEIVED".


47 A2 04US Rev05 10-65

OPEN

Purpose:

Opens a file and associates it with a unit number.

Usage:


Syntax:

OPEN,UNIT=unit-R,NAME=name-F[,PMD=IN|OUT|APPEND] [,WORKLIBS=worklibs-nb-R][,ERROR=errlab-ref-A8]

Parameters:

UNIT The unit with which the file is associated. The value of theunit is from 1 to 750.

NAME The name of the subfile of one WORKLIB opened andassociated with this unit. The length of this name should notexceed 31 characters.

PMD If PMD is IN , the file is opened in INPUT mode. Anunrecoverable error occurs if the file does not exist. The filemay be in SARF or SSF format. In the latter case the SSFheader and control records are ignored.

If PMD is OUT, the file is opened in OUTPUT mode. If thefile exists it is deleted and a new file is created in SSF format.

If PMD is APPEND, the file is opened in APPEND mode. Ifthe file does not exist, APPEND reacts like OUT. Otherwise,new records are appended to old files that should be in SSFformat but no controls are made by TILS.

Default is IN.

WORKLIBS The worklib number which is to contain the specified subfile.Values can be 1, 2 or 3, respectively for the ifn's WORKLIB,WORKLIB2 and WORKLIB3. The default value is 1.

TILS User's Guide

10-66 47 A2 04US Rev05

OPEN


Notes:

This statement opens a subfile of the libraries assigned to the internal file namesWORKLIB, WORKLIB2, or WORKLIB3 and associates it with a UNIT. All furtherreferences to this file are made through this unit until a CLOSE statement for the unit isexecuted. The unit may be used for another file once the initial unit is closed.


47 A2 04US Rev05 10-67

OR

Purpose:

Stores the disjunction of the operands in a specified register.

Usage:


Syntax:

OR,resregister-RR,operand1-R,operand2-R

Parameters:

resregister The register that contains the disjunction of the operands.

operand1operand2

The operands of the disjunction.

Notes:


Example:

OR *18 %FFFF0000 %0000FFFF

Stores %FFFFFFFF in register 18.

TILS User's Guide

10-68 47 A2 04US Rev05

OSI_SEND

Purpose:

Sends data as Normal, Typed or Expedited data.

Usage:


Syntax:

OSI_SEND,SOURCE=source-F [,LEVEL={FULL|BEGIN|MIDDLE|END}] [,CATEGORY={NORMAL|TYPED|EXPEDITED}] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,ERROR=errlab-ref-A8]

Parameters:

SOURCE This field contains the data to be sent. If the lengthexceeds the size of the IN buffer, the data is truncated.The lN buffer is determined by the SIZE or COMMONstatements of the DECLARATION file (the default size is16K).

If Expedited data is sent (see CATEGORY parameter), thelength may not exceed 14 bytes.

LEVEL If LEVEL is FULL, the input forms a full Session Service DataUnit (SSDU).

Error! Reference source not found.If LEVEL is BEGIN, the input forms the beginning of aSession Service Data Unit (SSDU).

If LEVEL is MIDDLE, the input forms the middle part of aSession Service Data Unit (SSDU).

If LEVEL is END, the input forms the last part of a SessionService Data Unit (SSDU).

Error! Reference source not found.Default is FULL.

This parameter is not relevant if CATEGORY is specified asEXPEDITED.


47 A2 04US Rev05 10-69

OSI_SEND

CATEGORY If CATEGORY is NORMAL, data is sent as Normal SessionService Data Unit (NSSDU).

If CATEGORY is TYPED, data is sent as Typed SessionService Data Unit (TSSDU).

If CATEGORY is EXPEDITED, data is sent as ExpeditedSession Service Data Unit (XSSDU). The length ofExpedited data may not exceed 14 bytes. If EXPEDITED isselected, the LEVEL parameter is ignored.

Default is NORMAL.

DATA_TOKEN If the value is 1, the data token is transferred, if not, the tokenis not affected.

Default is 0.

MINOR_TOKEN If this value is 1, the minor token is transferred, if not, thetoken is not affected.

Default is 0.

MAJOR_TOKEN If this value is 1, the major token is transferred, if not, thetoken is not affected.

Default is 0.

RELEASE_TOKEN If this value is 1, the release token is transferred, if not, thetoken is not affected.

Default is 0.


TILS User's Guide

10-70 47 A2 04US Rev05

OSI_SEND

Notes:

A SEND statement executed by an OSI path is equivalent to an OSI_SEND statementspecifying all parameters by their default value.

The OSI session layer of GCOS 7 does not guarantee that Session Service Data Unitssent as fragmented units will be delivered with the same fragmentation.

The parameters referring to tokens may cause recoverable errors if the correspondingfunctional units are not negotiated or if the tokens are assigned to the correspondent.

Tokens may only be transferred if the LEVEL is FULL or END, and CATEGORY isNORMAL. When a register is used to request the transfer of a token, this is detectedwhen the OSI_SEND statement is executed.

However, if the integer 1 is specified directly in for DATA_TOKEN, MINOR_TOKEN,MAJOR_TOKEN, or RELEASE_TOKEN, and LEVEL is BEGIN or MIDDLE an error isdetected during the compilation phase.

The transfer of TYPED and EXPEDITED data is always executed without thinktime.OSI_SEND may be used to transfer TYPED or EXPEDITED data if the execution level isnot zero. The sequence is not interrupted. Only one TYPED and one EXPEDITEDsession service data unit may be transferred per ON SECTION.

Example:

OSI_SEND SOURCE=(HEXA,'0AFC8C5D3D3D640E6D6D9C4')

This statement generates a request to transmit the message "HELLO WORLD" prefixedby its length as a full normal Session Service Data Unit. In place of the OSI_SENDstatement a SEND statement could have been used.


47 A2 04US Rev05 10-71

PLEASE_TOKEN

Purpose:

Requests tokens from another application.

Usage:


Syntax:

PLEASE_TOKEN[,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

Parameters:

DATA_TOKEN If the value is 1, the data token is requested, if not, thetoken is not affected.

Default is 0.

MINOR_TOKEN If this value is 1, the minor token is requested, if not, thetoken is not affected.

Default is 0.

MAJOR_TOKEN If this value is 1, the major token is requested, if not, thetoken is not affected.

Default is 0.

RELEASE_TOKEN If this value is 1, the release token is requested, if not, thetoken is not affected.

Default is 0.

USERDATA The contents of this field is transferred as userdata. Themaximal length of this data is 512 bytes if OSI session levelis 1, otherwise it is 10,240 bytes. If this parameter isabsent no userdata is sent.

TILS User's Guide

10-72 47 A2 04US Rev05

PLEASE_TOKEN


Notes:

Attempting to request a token that is not available or not owned by the path leads to arecoverable error.

Example:

PLEASE_TOKEN DATA_TOKEN=*18 MINOR_TOKEN=*18

The data and minor tokens are requested if register 18 contains 1.


47 A2 04US Rev05 10-73

POINT

Purpose:

Restores the current pointer for a seed, block, or file according to a key.

Usage:


Syntax:

POINT,FROM=key-RR[,FOR=field-F][,UNIT=unit-R] [,ERROR=errlab-ref-A8]

Parameters:

FROM Register that contains the proposed key. After the POINTstatement is executed this register contains 0.

FOR The field descriptor indicating that a BLOCK or a SEED isrestored as designated by the key in the FROM parameter.

UNIT The unit indicating that a FILE is restored as designated bythe key in the FROM parameter.

ERROR Label defining where execution continues if a recoverableerror occurs.

Notes:

1. The key must be obtained by a NOTE statement executed by the path for anobject, that is, for a seed, block, or file.

2. By using this statement, you will delete the given key, which will now be used byanother NOTE statement.

TILS User's Guide

10-74 47 A2 04US Rev05

PRINT

Purpose:

Print fields, registers, histograms, or information about the executing path, on theSYSOUT.

Usage:


Syntax:

PRINT,HEADERPRINT,REGISTER,FROM=register1-RX,TO=register2-RX[,DISPLAY=value-R]PRINT,HISTOGRAM[,NAME=histnam-ref-A8][,NUMBER=histnum-R]PRINT,{ALPHA|HEXA|BOTH|LINE},SOURCE=source-F [,DISPLAY=value-R][,ERROR=errlab-ref-A8]

Parameters:

HEADER Prints the name and rank of executing and consultingpaths. Note that these paths may be different if theSWITCH statement has been executed.

REGISTER Prints the registers. Registers must be of the same type andin numeric order.

ALPHA Prints the character string contained in field inalphanumeric format.

HEXA Prints the character string contained in field in hexadecimalformat.

BOTH Prints the character string contained in field in bothalphanumeric and hexadecimal formats on the same line.

LINE Prints the character string contained in field inalphanumeric format without line header.


47 A2 04US Rev05 10-75

PRINT

FROM Register with the lowest rank to be printed.

TO Register with the highest rank to be printed.

SOURCE Field descriptor indicating the field to be printed.


NAME Name of the histogram to be printed.

NUMBER Number of the histogram to be printed.

DISPLAY Determines whether registers or text is displayed on the TILSoperator console as well as printed. DISPLAY=1 displaysand prints registers and text, DISPLAY=0 only prints registersand text.

Notes:

The parameters of this statement must be used as shown in the four possible formats ofthe PRINT statement (see Syntax ). The use of keywords is mandatory for this statement.Registers of different types, that is, sharable, protected, or read/write registers, cannot bemixed in one PRINT statement.

The format of this output is described in Format of the External Trace in the chapter "TILSOutput.

Examples:

PRINT REGISTER,FROM=*-8,TO=*-1,DISPLAY=*20

is a legal form of the PRINT statement, printing all sharable registers from -8 to -1 anddisplaying them on the TILS operator console if register 20 contains 1.

PRINT REGISTER,FROM=*-3,TO=*20

is not a legal PRINT statement since it includes registers of different types.

PRINT REGISTER,FROM=*-1,TO=*-8

is not a legal PRINT statement since it specifies the registers in the wrong order.

TILS User's Guide

10-76 47 A2 04US Rev05

PROGRAM

Purpose:

Defines a program.

Usage:


Syntax:

PROGRAM,prognam-D-A8[,COMPACT={Y|N}][,DELIMITOR=delim-D-A1]

Parameters:

prognam The name of the program and the entry point created bythe statement.

COMPACT If COMPACT is Y, trailing blanks are suppressed.If COMPACT is N, trailing blanks are kept.

Default is Y.

DELIMITOR If this parameter is specified, and is not blank, records readare searched from the end to the beginning (right to left)and all characters up to and including the delimiter aredisregarded. If the delimiter is not found in the record, nocharacters are disregarded.

Notes:

This statement introduces a program. A second PROGRAM statement may not be usedinside a program. The statement defines an implicit entry point for the program whichmay be referenced in PATH statements of the DECLARATION file or used as argumentsin CALL or ON statements. Only those programs which are referenced in a PROGRAMstatement in the DECLARATION file are compiled.


47 A2 04US Rev05 10-77

PUT

Purpose:

Writes the contents of a field to a file associated with the path.

Usage:


Syntax:

PUT,SOURCE=source-F,UNIT=unit-R[,ERROR=errlab-ref-A8]

Parameters:

SOURCE The field descriptor that designates the character stringthat is written to the file.

UNIT The unit associated with a file where the record is written.If the unit is not associated with a file, a recoverable erroroccurs.


TILS User's Guide

10-78 47 A2 04US Rev05

RANDOM

Purpose:

Stores a random number in a specified register.

Usage:


Syntax:

RANDOM,resregister-RR,operand1-R [,NAME=U|EXPONENTIAL]

Parameters:

resregister The register which contains the random number.

operand1 The upper limit of the random number.

NAME If NAME is U, a random number for the uniform distributionis drawn.

If NAME is EXPONENTIAL, a random number for theexponential distribution is drawn.

Notes:


A random number is drawn from a sample for the uniform distribution over the intervalbetween 0 and the value specified in the operand.


47 A2 04US Rev05 10-79

RELEASE

Purpose:

Releases the OSI session.

Usage:


Syntax:

RELEASE[,TYPE={REQ|RESP}] [,RESULT=resultreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

Parameters:

TYPE If TYPE is REQ, a request for the release of the OSIsession is sent.

If TYPE is RESP, a response to a release indication issent. RESP may only be specified in an ONRELEASE_IND section and if the release token is availablebut not assigned to path executing this statement.

Default is REQ.

RESULT If the register contains 1, the request is accepted otherwiseit has any other value or is absent, it is rejected.

This parameter may only be used if TYPE is specified asRESP and the release token is available but not owned bythe path.

USERDATA The contents of this field is transferred as USERDATA.The maximum length of this data is 512 bytes if OSIsession level is 1, otherwise it is 10,240 bytes. If thisparameter is absent no userdata is sent.


TILS User's Guide

10-80 47 A2 04US Rev05

RELEASE

Notes:

A path issuing a RELEASE statement with the TYPE parameter specified as REQ mustwait for a response. (This statement with this TYPE parameter may only be issued if allavailable tokens are assigned to the path.) If the result is ACCEPT, the path isdisconnected and no further statements may be executed in the main program associatedwith the path. For other responses, the execution is resumed at the statement followingthe RELEASE statement.

If the RELEASE function unit is negotiated when an OSI session is established, a pathmay issue the RELEASE statement only when it owns the release token. Even so, thecorrespondent may reject the request.

The RELEASE statement with the TYPE parameter specified as RESP may only beissued from a ON RELEASE_IND section, an unrecoverable error occurs otherwise.


47 A2 04US Rev05 10-81

RESET

Purpose:

Erases the contents of a histogram.

Usage:


Syntax:

RESET[,NAME=histnam-ref-A8][,NUMBER=histnum-R]

Parameters:

NAME The name of the histogram whose contents is erased.

NUMBER The rank of the histogram whose contents is erased.

Notes:

The histogram must be referred to either by its name or by its rank.

Example:

DECLARATION FILE SCENARIO FILE................ .............HISTOGRAM,HIST1 :PRINT HISTOGRAM,NAME=HIST2;HISTOGRAM,HIST2 :RESET NUMBER=2;............... :PRINT HISTOGRAM,NUMBER=3;HISTOGRAM,HIST3 :RESET HISTOGRAM,NAME=HIST3;

HIST2 and HIST3 are printed and then erased.

TILS User's Guide

10-82 47 A2 04US Rev05

RESYNC

Purpose:

Resynchronizes the path and its correspondent.

Usage:


Syntax:

RESYNC[,TYPE={REQ|RESP}] [,ACTION={RESTART|ABANDON|SET}] [,MARK=syncpointnb-I] [,DATA={REQUESTOR|RESPONDER|RESPCHOICE}] [,MINOR={REQUESTOR|RESPONDER|RESPCHOICE}] [,MAJOR={REQUESTOR|RESPONDER|RESPCHOICE}] [,RELEASE={REQUESTOR|RESPONDER|RESPCHOICE}] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

Parameters:

TYPE If TYPE is REQ, the service is requested.

If TYPE is RESP, a response to the resynchronizationindication is sent. RESP may only be specified in an ONRESYNC_IND section.

Default is REQ.

ACTION If ACTION is RESTART, restarts from last agreedsyncpoint.

If ACTION is ABANDON, a new syncpoint is set to unusedvalue.

If ACTION is SET, restarts from negotiated syncpoint.Default is RESTART.

This parameter is only relevant if TYPE is REQ.


47 A2 04US Rev05 10-83

RESYNC

MARK The new initial synchronization point. Its default valuedepends on the TYPE and ACTION parameters. You maynot specify a value smaller than the last confirmedsynchronization point.

A MARK parameter is mandatory for TYPE REQ withACTION SET. It is irrelevant for ACTION ABANDON.

If this parameter is absent and TYPE is RESP, the proposedresynchronization point is used.

If this parameter is absent and ACTION is RESTART andTYPE is REQ, the last confirmed synchronization point isused.

DATA If DATA is REQUESTOR, the data token is assigned to thepath or correspondent that requested it.

If DATA is RESPONDER, the data token is assigned to thepath or correspondent that responded to a request.

If DATA is RESPCHOICE, the assignment of the data tokenis the choice of the responder.

Default: If TYPE is REQ, REQUESTOR is the DATA default.

MINOR If MINOR is REQUESTOR, the minor token is assigned tothe path or correspondent that requested it.

If MINOR is RESPONDER, the minor token is assigned tothe path or correspondent that responded to a request.

If MINOR is RESPCHOICE, the assignment of the minortoken is the choice of the responder.

Default: If TYPE is REQ, REQUESTOR is the MINORdefault.

TILS User's Guide

10-84 47 A2 04US Rev05

RESYNC

MAJOR If MAJOR is REQUESTOR, the major token is assigned tothe path or correspondent that requested it.

If MAJOR is RESPONDER, the major token is assigned tothe path or correspondent that responded to a request.

If MAJOR is RESPCHOICE, the assignment of the majortoken is the choice of the responder.

Default: If TYPE is REQ, REQUESTOR is the MAJORdefault.

RELEASE If RELEASE is REQUESTOR, the release token isassigned to the path or correspondent that requested it.

If RELEASE is RESPONDER, the release token isassigned to the path or correspondent that responded to arequest.

If RELEASE is RESPCHOICE, the assignment of therelease token is the choice of the responder.

Default: If TYPE is REQ, REQUESTOR is the RELEASEdefault.

DATA_TOKEN If the value is 1 and TYPE is RESP, the data token isrequested. Otherwise, the token is not affected.

Default is 0.

MINOR_TOKEN If the value is 1 and TYPE is RESP, the minor token isrequested. Otherwise the token is not affected.

Default is 0.

MAJOR_TOKEN If the value is 1 and TYPE is RESP, the major token isrequested. Otherwise, the token is not affected.

Default is 0.


47 A2 04US Rev05 10-85

RESYNC

RELEASE_TOKEN If the value is 1 and TYPE is RESP, the release token isrequested. Otherwise, the token is not affected.

Default is 0.

USERDATA The contents of this field is transferred as USERDATA.The maximum length of this data is 512 bytes if OSIsession level is 1, otherwise it is 10,240 bytes. If thisparameter is absent no userdata is sent.


Notes:

A path issuing a RESYNC statement with the TYPE parameter specified as REQ mustwait for the response.

There are no restrictions on tokens. However, to be able to resynchronize on a syncpoint,at least the major or minor token must have been negotiated. If neither of these twotokens are available, the path and its correspondent restart at the beginning of thesession.

The RESYNC statement with the TYPE parameter specified as RESP may only be issuedfrom a ON RESYNC_IND section otherwise an unrecoverable error occurs.

TILS User's Guide

10-86 47 A2 04US Rev05

RETURN

Purpose:

Returns control to the calling program or ends an ON-section.

Usage:


Syntax:

RETURN [,OPTION={NONE|RETRY|SET}] [,TO=entrynam-ref-A8]

Parameters:

OPTION If OPTION=NONE, execution resumes after the CALLstatement in the case of a subroutine, or is not affected inthe case of an ON section.

If OPTION=RETRY, an attempt is made to re-execute anerroneous statement. This parameter is significant only inthe context of an ON error section.

If OPTION=SET, execution resumes at the last checkpointdefined by the CHECKPT statement. If no checkpointexists, execution resumes at the statement currentlyassociated with the path when it was disconnected.

Default is NONE.

TO The name of that entry point that should be executed next.This parameter is incompatible with RETRY.

Notes:

A RETURN statement in the main program acts like TERMINATE PATH. It is ignored inON ABNTERM and ON END sections.


47 A2 04US Rev05 10-87

SCAN

Purpose:

Scans for a given string in a field.

Usage:


Syntax:

SCAN,FOR=field1-F,IN=field2-F,LABEL=labnam-ref-A8 ,OFFSET=resregister-RR[,ERROR=errlab-ref-A8]

Parameters:

FOR The field descriptor indicating the character string to besearched in a field.

IN The field descriptor indicating the field to be scanned.

LABEL The label where the execution is sent if the character stringis found.

OFFSET The result register that contains the offset of the firstcharacter in the string of a successful search.


Notes:

All parameters, except ERROR, are mandatory.

TILS User's Guide

10-88 47 A2 04US Rev05

SCAN

Examples:

SCAN FOR=(ALPHA,'AB'),IN=(ALPHA,'ABC'),LABEL=T,OFFSET=*20

Sends execution to label T and stores 0 in register 20.

SCAN FOR=(ALPHA,'BC'),IN=(ALPHA,'ABC',1),LABEL=T,OFFSET=*20

Sends execution to label T and stores 0 in register 20.


47 A2 04US Rev05 10-89

SEND

Purpose:

Sends an input message to a correspondent.

Usage:


Syntax:

SEND,SOURCE=source-F [,LEVEL=level-I] [,ERROR=errlab-ref-A8] [,TYPE=type-R] [,CONTROL={NO|YES}] [,INHEAD=header-F]

- Or an implicit send, (any record inside a PROGRAM), provided the first character isneither ":" nor "*" .

Parameters:

SOURCE The field descriptor indicating the character string to besent as input to the correspondent. The length of thecharacter string may be 0.

LEVEL This parameter must have one of the following values:

1 - the path keeps the turn.

3 - the turn is transmitted to the correspondent.

5 - the turn is transmitted and the path cannot send any moreinputs. This value may not be specified if TWS mode isselected.

Default is 3.


TILS User's Guide

10-90 47 A2 04US Rev05

SEND

TYPE The record type. The default value is 0 if CONTROL isNO, otherwise the default is 128. Values range from 0 to4095 (CONTROL is NO) or 128 to 4095 (CONTROLis YES).

CONTROL If CONTROL is NO, the message is not a control record.If CONTROL is YES, the message is a control record.

Default is NO.

INHEAD This field contains the device procedure header used withthe input. Its contents replace the current content ofINHEAD. If this parameter is absent the contents ofINHEAD is used.

The format of this field depends on the terminal typespecified in the DEVICE statement associated with thispath. The length of INHEAD may not exceed 20 bytes.

Default: Current contents of INHEAD is used.

Notes:

The implicit form of the SEND statement corresponds to a send with LEVEL=3 .

The SEND statement is treated in 2 phases unless the THINKTIME is inhibited (see alsothe THINKTIME statement in the DECLARATION file). These phases are:

• the timer is set with the appropriate thinktime and the path waits for the notification• the path is notified that the thinktime has elapsed and the input is transmitted to the

correspondent.

It is important not to modify the contents of a field in an ON section used as an argumentof the explicit SEND statement, because the SEND statement might be activated whilethe path is waiting for the thinktime to elapse.


47 A2 04US Rev05 10-91

SEND

The SEND statement may only be executed if the execution level is 0.

If the correspondent expects the input to be provided by a menu or another form, thecontrol characters used in completing the form must be represented in the characterstring designated by their hexadecimal equivalent in SOURCE.

If TWS mode is selected, the path waits for the credit notification after executing a SENDstatement.

In TWA mode (the default), the path waits for the notification that credit is available onlyafter a SEND with LEVEL=1, otherwise it waits for the first output message.

If this statement is executed by a path using OSI session services, all parameters exceptSOURCE and ERROR are ignored and the SEND statement is treated like an OSI_SENDstatement specifying the default values.

Example:

SCENARIO FILE.............:PROGRAM,SENDEX*PATHS USING THIS PROGRAM LOG*OFF IMMEDIATELY AFTER CONNECTION*TO IOF. HEXADECIMAL "05" CORRESPONDS*TO THE USE OF THE "TAB" KEY ON DKU7005*:SEND SOURCE=(ALPHA,'[X05BYE'):EOD.............:PROGRAM,SENDIM[X05BYE:EOD

The two programs are equivalent. ("[X05" stands for the horizontal tabulation characterrepresented by the hexadecimal "05").

TILS User's Guide

10-92 47 A2 04US Rev05

SET

Purpose:

Sets or reads JCL switches.

Usage:


Syntax:

SET,SWITCH=switchnumber-R[,VALUE=value-R][,STATUS=resreg-RR]

Parameters:

SWITCH A JCL switch (0 to 31). If the switch does not exist, anunrecoverable error occurs.

VALUE The value at which the switch is set; this value must be 0 or1. If another value is used, an unrecoverable error occurs.This parameter and the STATUS parameter are mutuallyexclusive. If neither is specified VALUE=1 is assumed.

STATUS The register that contains the value of the JCL switch. Ifthis parameter is specified the switch is read but notmodified.

Notes:

This statement allows interaction with JCL. The value of the switch may be tested aftercompletion of the TILS step by the JCL statement JUMP.


47 A2 04US Rev05 10-93

SHIFT

Purpose:

Shifts the contents of a register to the left or right.

Usage:


Syntax:

SHIFT,{RIGHT|LEFT},TARGET=resregister-RR ,SOURCE=operand1-R,OFFSET=offset-R

Parameters:

RIGHT Shifts the contents to the right.

LEFT Shifts the contents to the left.

TARGET The register that contains the results.

SOURCE The value to be shifted.

OFFSET The offset, in bits, by which the value is shifted. This is aninteger modulo 32.

Example:

SHIFT RIGHT,TARGET=*20 SOURCE=%00001000 OFFSET=12

stores the value 1 in register 20. The same result is obtained using OFFSET=44 insteadof OFFSET=12 as 44 equals 12 modulo 32.

TILS User's Guide

10-94 47 A2 04US Rev05

STRING

Purpose:

Defines a constant character string.

Usage:


Syntax:

STRING,stringnam-D-A8,TYPE={ALPHA|HEXA},TEXT='text-A'

Parameters:

stringnam The name of the character string.

TYPE If TYPE is ALPHA, the character string in alphanumericcharacters.

If TYPE is HEXA, the character string in hexadecimalcharacters.

Notes:

This statement is used to define a character string for future reference through a fielddescriptor.

Example:

STRING,A,TYPE=ALPHA,TEXT='ABC'

and

STRING,H,TYPE=HEXA,TEXT='C1C2C3'

define the same character string.


47 A2 04US Rev05 10-95

SUBTRACT

Purpose:

Stores the difference of two operands in a specified register.

Usage:


Syntax:

SUBTRACT,resregister-RR,operand1-R,operand2-R

Parameters:

resregister The register that contains the difference of the operands.

operand1operand2

The operands of the subtraction.

Notes:


Example:

SUBTRACT *18 4 2

stores 2 in register 18.

TILS User's Guide

10-96 47 A2 04US Rev05

SWITCH

Purpose:

Selects the context of a different path.

Usage:


Syntax:

SWITCH[,PATH=name-ref-A12][,RANK=pathrank-R]

Parameters:

PATH The name of the path whose context is used by the pathexecuting the SWITCH statement. If neither this parameternor the RANK parameter is specified, the context of theexecuting path is restored.

RANK The rank of the path whose context is used by the pathexecuting the SWITCH statement. If neither this parameternor the PATH parameter is specified, the context of theexecuting path is restored.

Notes:

The path cited in this statement is called the consulting path while the path, whichexecutes a statement is called the executing path. While executing and consulting pathsdiffer, neither part of the context may be modified except the POOL or a sharable register.The SEND, WAIT, and SYNCHRONIZE statements may not be executed after theexecution of the SWITCH statement.

Any errors cancel the SWITCH statement and restore the old context.


47 A2 04US Rev05 10-97

SWITCH

Example:

DECLARATION FILE SCENARIO FILE............ .............PROGRAM TOTO,LIBMAIN :PROGRAM TOTOPATH,USER1,TOTO :SWITCH,RANK=2;PATH,USER2,LIBMAIN :PRINT,ALPHA,SOURCE=(NAME); :SWITCH; :PRINT,ALPHA,SOURCE=(NAME);| :EOD

The first PRINT statement in TOTO prints:

USER2

the second prints:

USER1.

TILS User's Guide

10-98 47 A2 04US Rev05

SYNCHRONIZE

Purpose:

Synchronizes a path.

Usage:


Syntax:

SYNCHRONIZE[,REGISTER=resregister-RR]

Parameters:

REGISTER The register that contains the value transmitted by theEVENT statement.

Notes:

The path executing this statement waits for notification of an event posted by another pathusing the EVENT statement. This statement may be executed only if the execution levelis 0.


47 A2 04US Rev05 10-99

SYNCPT

Purpose:

Sets synchronization points.

Usage:


Syntax:

SYNCPT[,TYPE={REQ|RESP}] [,STYPE= MINOR|MAJOR] [,CONFIRM= OPTIONAL|EXPLICIT] [,MARK=syncpointnb-RR] [,DATA_TOKEN=datareg-R] [,MINOR_TOKEN=minreg-R] [,MAJOR_TOKEN=majreg-R] [,RELEASE_TOKEN=relreg-R] [,USERDATA=userdata-F] [,ERROR=errlab-ref-A8]

Parameters:

TYPE If TYPE is REQ, requests that major or minorsynchronization points be set.

If TYPE is RESP, confirms that major or minorsynchronization points when the corresponding indication isreceived. If STYPE is specified as MAJOR, RESP may onlybe specified in an ON SYNC_IND section.

Default is REQ.

STYPE If STYPE is MINOR, sets minor syncpoint.

If STYPE is MAJOR, sets major syncpoint.

Default is MINOR.

TILS User's Guide

10-100 47 A2 04US Rev05

SYNCPT

CONFIRM If CONFIRM is OPTIONAL, the correspondent may or maynot confirm the synchronization point.

If CONFIRM is EXPLICIT, explicit confirmation isrequested.

This parameter is ignored if major synchronization serviceis used.

Default is OPTIONAL.

MARK If TYPE is REQ, this register contains the proposedsynchronization point number.

If TYPE is RESP, this register contains the value of the lastconfirmed synchronization point. TILS checks that thevalue is positive and less than 1,000,000.

This parameter is irrelevant if STYPE is major and TYPE isRESP.

DATA_TOKEN If the value is 1, the data token is requested when TYPE isRESP, and transferred when TYPE is REQ. Otherwise, thetoken is not affected.

Default is 0.

MINOR_TOKEN If the value is 1, the minor token is requested when TYPEis RESP, and transferred when TYPE is REQ. Otherwise,the token is not affected.

Default is 0.

MAJOR_TOKEN If the value is 1, the major token is requested when TYPEis RESP, and transferred when TYPE is REQ. Otherwise,the token is not affected.

Default is 0.

RELEASE_TOKEN If the value is 1, the release token is requested when TYPEis RESP, and transferred when TYPE is REQ. Otherwise,the token is not affected.

Default is 0.


47 A2 04US Rev05 10-101

SYNCPT

USERDATA The contents of this field is transferred as USERDATA.The maximum length of this data is 512 bytes if OSIsession level is 1, otherwise it is 10,240 bytes. If thisparameter is absent, no userdata is sent.


Notes:

This statement may be used to set or confirm major or minor synchronization points.Using this statement outside an activity leads to a recoverable error when the activitymanagement unit is negotiated.

If a minor synchronization point is set, the path does not wait for confirmation butcontinues executing its sequence. The SYNCPT statement may be used to confirm minorsynchronization points at any point in the program.

The LOAD statement may be used with option MINOR to obtain the last syncpointproposed by the OSI session service. TILS is transparent to this value and controls onlythat the value is positive.

If a major synchronization point is set, the path waits for confirmation.

TILS User's Guide

10-102 47 A2 04US Rev05

TERMINATE

Purpose:

Disconnects the path, ends the simulation phase, or aborts TILS.

Usage:


Syntax:

TERMINATE,{PATH|TILS} [,MODE={ABORT|SYSTEM}] [,STATUS=value-R] [,USERDATA=userdata-F]

Parameters:

PATH Disconnects the path that executes this statement.

TILS Ends the simulation phase and disconnects all openedpaths.

MODE If MODE is ABORT, TILS aborts with status 10000.

If MODE is SYSTEM, a system crash is produced.

Note: MODE is incompatible with the STATUS parameter.

STATUS This parameter sets the severity code if the first parameteris TILS, otherwise it sets the reason code for thedisconnection request.

Note : STATUS is incompatible with the MODE parameter.

USERDATA This field may contain up to nine characters which aretransmitted as userdata to the correspondent. It may onlybe used if TERMINATE is specified as path.

This parameter is ignored if the path is not associated witha PROFILE statement.


47 A2 04US Rev05 10-103

TERMINATE

Notes:

The simulation phase is ended if TERMINATE TILS is executed even if there are openedpaths.

TILS User's Guide

10-104 47 A2 04US Rev05

TEST

Purpose:

Compares numeric values.

Usage:


Syntax:

TEST,value1-R,{EQ|NE|LT|LE|GT|GE},value2-R,LABEL=labnam-ref-A8

Parameters:

value1,value2 The values to be compared according to one of theseconditions:

EQ equalNE not equalLE less than or equalLT less thanGT greater thanGE greater than or equal

LABEL Label where the execution is sent if the condition is fulfilled.


47 A2 04US Rev05 10-105

TILS

Purpose:

Requests execution of a TILS operator command.

Usage:


Syntax:

TILS,SOURCE=source-F[,ERROR=errlab-ref-A8]

Parameters:

SOURCE The field descriptor indicating the location of the TILSoperator command.


Notes:

The TILS statement generates a notification that a TILS operator command must betreated. The command is taken into account once the notification has been received byTILS (see also the OCL statement of the SCENARIO file).

No check on the contents of SOURCE is made during the execution of this statement.

Example:

TILS SOURCE=(ALPHA,'STOP PRINT')

behaves like:

OCL SOURCE=(ALPHA,'TILS STOP PRINT')

The simulation phase is ended by the TILS operator command STOP once the currentsequence is ended.

TILS User's Guide

10-106 47 A2 04US Rev05

WAIT

Purpose:

Waits for a specified delay.

Usage:


Syntax:

WAIT,delay-R

Parameters:

delay The delay that elapses before the execution may resume.This value is expressed in milliseconds and must bebetween 100 and 1,800,000 milliseconds (30 minutes).

Notes:

This statement can be executed only when the execution level is 0.

47 A2 04US Rev05 11-1

11. TILS Operator Commands

This section describes all the TILS Operator Commands. A summary of all commands ispresented. In the following section, each command is examined in alphabetical order.

To use these TILS commands, you must specify the application that you are using. Forexample:

With JCL:

TILS AUTO,ENABLE

With GCL:

ESCAPE TILS AUTO,ENABLE

For information on using these commands, see TILS Operator Commands in the chapter"Running TILS".

You may change the application name from TILS using the NAME statement in theDECLARATION file.

TILS User's Guide

11-2 47 A2 04US Rev05

11.1 SUMMARY OF TILS OPERATOR COMMAND SYNTAX

AUTO,{ENABLE|INHIBIT}CHANGE[,GROUP={groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I] [,HISTOGRAM=histnam-ref-A8]DEBUG[,GROUP={groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I] [,MODE={ENABLE|TRACE|INHIBIT}] [,OBJECT=TRACEDUMP]DELAY,THINKTIME=thinktime-I [,{GROUP=groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I] [,STEP=increment-I] [,UNIT={MILLI|SECMIN}]DISPLAY[,PATH=pathnam-ref-A12] [,RANK=pathrank-I]DUMP,[,{ENABLE|INHIBIT}]ELAPSED,timelimit-I [,{UNIT=MILLI|SEC|MIN}]GLOBALHELP[,commandname-RWD]LOGFILE[,{ENABLE|INHIBIT|SEMAPHORE}]RESET[,GROUP=groupnam-ref-A8|ALL] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I] [,HISTOGRAM={HOLD|CANCEL}] [,STATISTICS={HOLD|CANCEL}] [,DISCONNECT={YES|NO}]SEND,TEXT='text-A' [,PATH=pathnam-ref-A12] [,RANK=pathrank-I]START[,GROUP={groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I] [,DELAY=delay-I] [,UNIT={MILLI|SEC|MIN}] [,LIST={NO|YES}]STATISTICS[,GROUP=groupnam-ref-A8|ALL] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I]STOP[,PRINT]THINKTIME,{CONSTANT|INHIBIT|VARIABLE|RANDOM} [,min-I][,max-I] [,UNIT={MILLI|SEC|MIN}]TRACE,{NONE|EXTERNAL|BOTH|ALPHA|HEXA|SEMAPHORE}WATCHDOG,timeperiod-I [,UNIT={MILLI|SEC|MIN}]

TILS Operator Commands

47 A2 04US Rev05 11-3

11.2 DESCRIPTION OF TILS COMMANDS

Each command is explained in this section.

TILS User's Guide

11-4 47 A2 04US Rev05

AUTO

Purpose:

Modifies the behavior of TILS after the last path is closed.

Syntax:

AUTO,{ENABLE|INHIBIT}

Parameters:

ENABLE Requests that the simulation phase is automatically ended.

INHIBIT Does not request that the simulation phase beautomatically ended.

Default is INHIBIT.


47 A2 04US Rev05 11-5

CHANGE

Purpose:

Attaches a new histogram to a path or a group of paths.

Syntax:

CHANGE[,GROUP={groupnam-ref-A8|ALL}], [,PATH=pathnam-ref-A12][,RANK=pathrank-I] [,HISTOGRAM=histnam-ref-A8]

Parameters:

GROUP Addresses a group of paths. If ALL is specified then allpaths are included.

PATH The path addressed by this command.

RANK The rank of the path addressed by this command.

HISTOGRAM The name of the histogram, attached for the responsetimes to the paths. If this parameter is absent the currentlyassociated histogram is dissociated from the paths.

Examples:

CHANGE GROUP=ALL,HISTOGRAM=SATHIST

Associates histogram SATHIST with all declared paths.

CHANGE RANK=5

Dissociates any attached histogram from the path declared in the 5th PATH statement ofthe DECLARATION file.

TILS User's Guide

11-6 47 A2 04US Rev05

DEBUG

Purpose:

Traces the execution of TILS statements and modifies the way that aborted paths aretreated.

Syntax:

DEBUG[,{GROUP=groupnam-ref-A8|ALL}], [,PATH=pathnam-ref-A12][,RANK=pathrank-I] [,MODE={ENABLE|TRACE|INHIBIT}][,OBJECT={TRACE |DUMP}]

Parameters:




MODE If MODE is ENABLE, debugging is activated.

If MODE is TRACE, the trace of the operator code and theoffset of executed statements is activated.

If MODE is INHIBIT, the debugging mode for the pathsspecified is stopped.

OBJECT If OBJECT is TRACE, the execution of TILS statements istraced.

If OBJECT is DUMP, debugging information is printed ifTILS is abnormally terminated.

Notes:

The DEBUG command cancels the effect of the DEBUG statement and vice versa. Youshould only use the ENABLE option in conjunction with BULL engineering personnel.


47 A2 04US Rev05 11-7

DELAY

Purpose:

Modifies the constant thinktime associated with a path.

Syntax:

DELAY,THINKTIME=thinktime-I [,GROUP={groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I][,STEP=increment-I] [,UNIT={MILLI|SEC|MIN}]

Parameters:

THINKTIME The constant thinktime to be associated with a path.




STEP The value used to increment new timer requests. Therequests are calculated by:

ndelay = thinktime + (n-1) * increment

where n is the rank of the path in the group. If thisparameter is not specified or is 0, the current thinktime isnot affected.

UNIT Names the unit of measurement for the thinktimeparameter: MILLI is milliseconds, SEC is seconds, MINis minutes.

TILS User's Guide

11-8 47 A2 04US Rev05

DELAY

Notes:

The new thinktime must lie within the bounds determined by the THINKTIME statement inthe DECLARATION file. These boundaries may be changed by using the THINKTIMEcommand.

Example:

DELAY 10000,GROUP=QUGROUP,STEP=50

When this is recognized by TILS, all thinktimes for paths belonging to group QUGROUPare cancelled. The timer is set with 10,000 milliseconds for the first path, 10,050milliseconds for the second path and so on.


47 A2 04US Rev05 11-9

DISPLAY

Purpose:

Displays the last input and the last output for the specified path, if available.

Syntax:

DISPLAY[,PATH=pathnam-ref-A12] [,RANK=pathrank-I]

Parameters:

PATH The path addressed by this command. If this parameter isnot specified RANK must be specified. PATH and RANKare mutually exclusive.

RANK The rank of the path addressed by this command. If thisparameter is not specified PATH must be specified. PATHand RANK are mutually exclusive.

Notes:

When you use this command, you will see this on the console :

• the first 65 characters of the last output received and the time elapsed since this outputwas received.

• the first 65 characters of the last input sent and the time elapsed since this input wassent.

• the constant thinktime associated with the path, if currently used, expressed inmilliseconds.

The output may not be available if the shared output buffer is used (see also the SIZEstatement of the DECLARATION file). This is also true for input.

Example:

S: TILS DISPLAY,USERIA;-> FROM X456 TILS DISPLAY,USERIA-> LAST INPUT FOR: USERIA SENT: 10.201 SECONDS AGO-> TEXT: BASIC LIB=TEST.BIN.LIB;-> LAST OUTPUT FOR: USERIA RECEIVED: 12.31 SECONDS AGO-> TEXT: S:-> CONSTANT THINKTIME: 2000

TILS User's Guide

11-10 47 A2 04US Rev05

DUMP

Purpose:


Syntax:

DUMP[,{ENABLE|INHIBIT}]

Parameters:



Notes:

This command should be used only in conjunction with BULL engineering personnel.


47 A2 04US Rev05 11-11

ELAPSED

Purpose:

Modifies the time-limit of the simulation phase.

Syntax:

ELAPSED,timelimit-I,[UNIT={MILLI|SEC|MIN}]

Parameters:

timelimit Denotes the maximum duration of the simulation phase inthe unit specified. The maximum value represents 120hours, the minimum value 4 minutes.

UNIT Names the unit of measurement for the timelimitparameter: MILLI is milliseconds, SEC is seconds, MINis minutes.

Notes:

The time is counted from the beginning of the simulation phase. If the new limit isreached, the you are warned and the command ignored.

Example:

You specify 240 minutes as time-limit in the DECLARATION file. If after 3 hours youdecide to extend the time limit to 360 minutes you must enter "TILS ELAPSED 360 MIN".

TILS User's Guide

11-12 47 A2 04US Rev05

GLOBAL

Purpose:

Displays the number of connected and declared paths, the remaining time, and otherstatistics for the preceding minute.

Syntax:

GLOBAL

Notes:

The command displays:

• the number of declared paths.• the number of opened paths.• the time remaining, in the format (HH:MM:SS.MS), until the time-limit is reached.• the number of inputs and outputs, and the mean response time during the minute

preceding the issue of this command, if the CHRONOLOGY statement has been usedin the DECLARATION file.

Example:

S: TILS GLOBAL--> TILS GLOBAL--> GLOBAL ACTIVITY 20 PATHS DECLARED 5 PATHS ACTIVE--> 1:24:43.004 REMAIN.--> MINUTE:20 #EXCHANGES: 202 #OUTPUT: 300 MEAN RESP.


47 A2 04US Rev05 11-13

HELP

Purpose:

Displays the syntax and purpose of TILS commands.

Syntax:

HELP[,commandname-RWD]

Parameters:

commandname The name of a TILS Operator command. If this parameteris absent, or if it does not correspond to a valid name, thelist of all commands together with an explanation of theirpurpose is displayed.

TILS User's Guide

11-14 47 A2 04US Rev05

LOGFILE

Purpose:

Controls the level of data collection for the logfile.

Syntax:

LOGFILE[,{ENABLE|INHIBIT|SEMAPHORE}]

Parameters:

ENABLE All events except semaphore messages are recorded.

INHIBIT Writing of LOGFILE is ended.

SEMAPHORE All events are recorded.

Notes:

For a complete description of the Logfile see the chapter "The TILS Logfile".


47 A2 04US Rev05 11-15

RESET

Purpose:

Disconnects paths or resets histogram or statistics.

Syntax:

RESET[,GROUP={groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I] [,HISTOGRAM={HOLD|CANCEL}] [,STATISTICS={HOLD|CANCEL}] [,DISCONNECT={YES|NO}]

Parameters:




HISTOGRAM If HISTOGRAM is HOLD, histogram contents are kept.

If HISTOGRAM is CANCEL, histogram contents areerased.

STATISTICS If STATISTICS is HOLD, the statistics are kept.

If STATISTICS is CANCEL, the statistics are erased.

DISCONNECT If DISCONNECT is YES, opened paths are closed.

If DISCONNECT is NO, the paths are not closed.

TILS User's Guide

11-16 47 A2 04US Rev05

RESET

Notes:

This statement allows you to close specific paths or suppress data collected about thesepaths without ending the simulation phase of TILS.

This command may affect other paths beside those directly addressed since histogramsmay concern several paths.

Example:

RESET ALL,STATISTICS=CANCEL,HISTOGRAM=CANCEL

Erases the previous activity, except TRACE and LOGFILE, while keeping the TILSsession executing.


47 A2 04US Rev05 11-17

SEND

Purpose:

Notifies the path and fills the command buffer.

Syntax:

SEND,TEXT='text-A'[,PATH=pathnam-ref-A12] [,RANK=pathrank-I]

Parameters:

TEXT The text sent to the path's command buffer. Text may notexceed 256 characters. The total length of the SENDcommand may not exceed 179 characters (system limit).

PATH The path addressed by this command. If this parameter isabsent the RANK parameter must be specified. PATH andRANK are mutually exclusive.

RANK The rank of the path addressed by this command. If thisparameter is absent the RANK parameter must bespecified. PATH and RANK are mutually exclusive.

Notes:

When this command is entered, the path addressed is notified and the subroutinespecified in the ON COMMAND condition is executed. This allows you to program privatecommands which are executed whenever the SEND command is used. This commandmay only be treated if an ON COMMAND section is defined for the addressed path.

The command field may only be accessed one time by a path addressed through theSEND command. This command may also be used to notify a path not waiting for a TILSevent. In that case it would be submitted by the TILS statement of the SCENARIO file.

TILS User's Guide

11-18 47 A2 04US Rev05

SEND

Example:

The following sequence can be used to instruct a command to display any part of theoutput.

: ENTRY COM;: COPY *18 SOURCE=(COMMAND,0,11) TARGET=(WORK,100);: CHECK (WORK,100,1) NE (ALPHA,'D') LABEL=RET;: CVDB *19 SOURCE=(WORK,102,4);: CVDB *20 SOURCE=(WORK,107,4);: ADD *21 *19 *20;: TEST *21 GT *3 LABEL=RET;: DISPLAY SOURCE=(OUT,*19,*20);: LABEL RET;: RETURN;: EOD

If you enter "SEND TEXT='D 0005 0002' RANK=1", the output from offset 5 on length 2 isdisplayed.


47 A2 04US Rev05 11-19

START

Purpose:

Request the connection of paths.

Syntax:

START[,GROUP={groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12] [,RANK=pathrank-I][,DELAY=delay-I] [,UNIT={MILLI|SEC|MIN}][,LIST={NO |YES}]

Parameters:




DELAY The delay after which the command is executed.

UNIT Names the unit of measurement for the delay: MILLIis milliseconds, SEC is seconds, MIN is minutes.

LIST If LIST is YES, the paths to be connected are listed.If LIST is NO, these paths are not listed.

TILS User's Guide

11-20 47 A2 04US Rev05

START

Notes:

This statement requests connection of paths after the connection delay, from the LOGONstatement of the DECLARATION file, has elapsed. This command is refused for pathswhich are not idle.

The DELAY parameter allows deferred connections.

Example:

START ALL,DELAY=60,UNIT=MIN

Requests connection of all paths one hour after this command has been received.


47 A2 04US Rev05 11-21

STATISTICS

Purpose:

Displays the statistics of paths.

Syntax:

STATISTICS[,GROUP={groupnam-ref-A8|ALL}] [,PATH=pathnam-ref-A12][,RANK=pathrank-I]

Parameters:




Notes:

For each path specified, this command displays:

• the number of outputs (O)• the number of inputs (I)• the number of completed exchanges (EX)• the elapsed time (ELAP) in seconds• the maximum response time (MAX) in seconds• the mean response time (MEAN) in seconds• the average throughput (THRU) in exchanges/seconds• the state of the PATHS (STATUS) - see Appendix A.

Example:

S: TILS STAT,PATH=USERA;-> TILS STAT,PATH=USERA-> USERA O.: 30 I.: 10 EX.: 9 ELAP.: 38.785-> MAX.:13.001 MEAN.:2.234 THRU:0.098 STATUS: 1-> USERA WAITS FOR FIRST OUTPUT

TILS User's Guide

11-22 47 A2 04US Rev05

STOP

Purpose:

Ends the simulation phase.

Syntax:

STOP[,PRINT]

Parameters:

If PRINT is specified, the last output and the last input for each path are printed (ifavailable).

Notes:

This command ends the simulation phase regardless of opened paths.


47 A2 04US Rev05 11-23

THINKTIME

Purpose:

Modifies the thinktime mode and the limits of the thinktime.

Syntax:

THINKTIME,{CONSTANT|INHIBIT|VARIABLE|RANDOM} [,min-I][,max-I][,UNIT={MILLI|SEC|MIN}]

Parameters:

CONSTANT The constant thinktime specified in the PATH statement isused for all SEND statements.

INHIBIT All SEND statements are executed without thinktime.

VARIABLE The thinktime used depends on the content of register 17.If the value in register 17 is:

<0 - No thinktime is used

=0 - The constant thinktime specified in the PATHstatement is used

>0 - The contents of the register is interpreted asmillisecond and used for the thinktime.

RANDOM A sample is taken to determine uniform distribution ofthinktime. The mean value is the thinktime specified in thePATH statement. The maximum interval is twice thedistance between the mean value and either the upper orlower limit for the thinktime.

min The minimum value of thinktime.

max The maximum value of thinktime.

UNIT The measurement unit for the limits: MILLI is milliseconds,SEC is seconds, MIN is minutes.

Default is MILLI.

Notes:

This command modifies the way that the thinktime functions. To modify the actualconstant thinktime, use the DELAY command.

TILS User's Guide

11-24 47 A2 04US Rev05

TRACE

Purpose:

Modifies the trace mode.

Syntax:

TRACE,{NONE|EXTERNAL|BOTH|ALPHA|HEXA|SEMAPHORE}

Parameters:

NONE No trace of the dialog is written on the SYSOUT.

EXTERNAL All inputs and outputs are written on the SYSOUT inalphabetical and hexadecimal format.

BOTH Synonym for EXTERNAL

ALPHA All inputs and outputs are written on the SYSOUT inalphabetic format.

HEXA All inputs and outputs are written on the SYSOUT inhexadecimal format.

SEMAPHORE All inputs, outputs, and semaphore messages are writtenon the SYSOUT in alphabetical and hexadecimal format.


47 A2 04US Rev05 11-25

WATCHDOG

Purpose:

Modifies the surveillance period.

Syntax:

WATCHDOG,timeperiod-I[,UNIT={MILLI|SEC|MIN}]

Parameters:

timeperiod The surveillance interval. This delay must be between 2minutes and 1 hour.

UNIT The measurement unit for the surveillance period: MILLIis milliseconds, SEC is seconds, MIN is minutes.

TILS User's Guide

11-26 47 A2 04US Rev05

47 A2 04US Rev05 12-1

12. Logfile Edit Statements

This chapter describes the statements used to edit the Logfile. A summary of allstatements is presented. In the section, "Description of LOGFILE Edit Statements", eachstatement is examined in alphabetical order.

TILS User's Guide

12-2 47 A2 04US Rev05

12.1 SUMMARY OF LOGFILE EDIT STATEMENT SYNTAX

DUMP,{ENABLE|INHIBIT}EDIT[,{ALPHA|HEXA}][,begtime-I][,endtime-I] [,LEVEL={DIALOG|STANDARD|SEMAPHORE|EVENT}] [,MODE={ALL|SELECT}]EVENT,eventname-RWD [,CODE=eventcode-I]SELECT[,PATH=pathnam-ref-A12][,RANK=pathrank-I]

12.2 DESCRIPTION OF LOGFILE EDIT STATEMENTS

Each command is explained in this section.

Logfile Edit Statements

47 A2 04US Rev05 12-3

DUMP

Purpose:


Syntax


Parameters



Notes:

This statement should be used only in conjunction with BULL engineering personnel.

TILS User's Guide

12-4 47 A2 04US Rev05

EDIT

Purpose:

Defines an EDIT session and the main parameters of the edition.

Syntax:

EDIT[,{ALPHA|HEXA}][,begtime-I][,endtime-I] [,LEVEL={DIALOG|STANDARD|SEMAPHORE|EVENT}] [,MODE={ALL|SELECT}]

Parameters:

ALPHA Edits records alphabetically.

HEXA Edits records in hexadecimal format.

begtime The time, in milliseconds, relative to the beginning of thelogged session, of the Time Of Day (TOD) of the firstrecord edited.

Default value is 0.

endtime The time, in milliseconds, relative to the beginning of thelogged session, of the TOD of the last record edited.

Default value is 24 hours.

LEVEL If LEVEL is DIALOG, only input and output are edited.

If LEVEL is STANDARD, all records, except semaphoresare edited.

If LEVEL is SEMAPHORE, all records are edited.

If LEVEL is EVENT, only those events specified in EVENTstatements following this EDIT statement and precedingthe next EDIT statement are handled.

Default is DIALOG.

MODE If MODE is ALL, all paths are handled.

If MODE is SELECT, only those paths specified in aSELECT statement following this EDIT statement andpreceding the next EDIT statement are handled.

Default is ALL.


47 A2 04US Rev05 12-5

EDIT

Notes:

This statement defines an EDIT session when it is the first EDIT statement. Except theDUMP and PRINT statements, all previous TILS statements are ignored if the previousEDIT statement was specified the DECLARATION file. If this is not the first EDITstatement, the LOGFILE is read and edited according to the parameters specified for theprevious EDIT statement and a new edit session is initiated.

TILS User's Guide

12-6 47 A2 04US Rev05

EVENT

Purpose:

Selects the type of records to be considered in the EDIT session.

Syntax:

EVENT,eventname-RWD [,CODE=eventcode-I]

Parameters:

eventname The name of the event to be examined (except MGCB).Either the eventname or the CODE parameter must bespecified.

CODE The numeric code associated with the event selected. Forvalues of events connected with the OSI session servicessee the chapter "Using TILS with OSI Session Services",for other events see the chapter "The TILS Logfile".

Notes:

This statement can only be used if the EDIT statement specified LEVEL=EVENT.

Events referring to OSI session services may only be selected through their codes.


47 A2 04US Rev05 12-7

SELECT

Purpose:

Selects paths to be handled in the EDIT session.

Syntax:

SELECT[,PATH=pathnam-ref-A12] [,RANK=pathrank-I]

Parameters

PATH The name of a path declared in the logged TILS session.

RANK The rank of a path declared in the logged TILS session.

Notes:

This statement can only be used if the EDIT statement specified MODE=SELECT.

TILS User's Guide

12-8 47 A2 04US Rev05

47 A2 04US Rev05 A-1

A. Path Status

CODE PATHS STATUS0 ALL PATH not connected1 ALL PATH waits for first OUTPUT2 ALL PATH waits for further OUTPUT3 ALL PATH waits for timer request (THINKTIME)4 ALL PATH waits for end of delay (WAIT)5 ALL PATH waits for TILS event6 ALL PATH waits for credit7 DSA PATH waits for OUTPUT with enclosure level 57 OSI PATH is running8 CTR PATH is running8 DSA PATH waits for V_OPENACK8 OSI PATH waits for connection confirmation9 DSA PATH waits for V_MGCLOSED as requestor9 OSI PATH waits for activity interrupt confirmation10 DSA PATH waits for V_MGCLOSED as object10 OSI PATH waits for activity discard confirmation11 OSI PATH waits for capability data confirmation11 DSA PATH waits to request connection12 DSA HYBRID PATH waits for reconnection12 OSI PATH waits for release confirmation13 OSI PATH waits for confirmation of major

synchronization point14 OSI PATH waits for activity end confirmation15 OSI PATH waits for confirmation of request to

resynchronize16 OSI PATH waits for release response

NOTES:

• ALL is all categories of paths

• CTR is Control paths

• DSA is paths using DSA session services

• OSI is paths using OSI session services

For the old states of TILS (Version 37), see the "States of DSA paths" in the chapter"Running TILS".

TILS User's Guide

A-2 47 A2 04US Rev05

47 A2 04US Rev05 B-1

B. Execution Levels

CONDITION LEVEL STATEMENT EXECUTEDNormal execution Receipt of an interrupt: 0 - ATTENTION 1 ON ATTENTION - DEMAND TURN 2 ON DMNDTURN - REJECT 3 ON REJECT - ABNORMAL TERMINATION 4 ON ABNTERM - TELEGRAM 10 ON TELEGRAMRecoverable error encountered 11 ON ERRORConnection request or acknowledgement 12 ON OPENReceipt of TILS Operator Command "SEND" 13 ON COMMANDReceipt of output that does not carry the turn: - Enclosure level 1 14 ON DATA - Enclosure level 2 15 ON DATAReceipt of output indicating end of session(enclosure level 5)

16 ON END

User exception report indication 17 ON ALARMActivity started indication 18 ON ACT_START_INDActivity resumed indication 19 ON ACT_RESUME_INDActivity interrupted indication 20 ON ACT_INTER_INDActivity discard indication 21 ON ACT_DISCARD_INDActivity ended indication 22 ON ACT_END_INDToken request indication 23 PLEASE_TOKEN_INDToken given indication 24 GIVE_TOKEN_INDReceipt of capability data ind. 25 CAPABILITY_INDReceipt of release indication 26 RELEASE_INDReceipt of minor syncpoint ind. 27 MINOR_INDReceipt of major syncpoint ind. 28 MAJOR_INDReceipt of minor syncpoint conf. 29 MINOR_CONFReceipt of resynchronization ind. 30 RESYNC_INDReconnection of hybrid path 31 ON RECONNECTReceipt of connection indication 32 ON COND_INDTimeout detection 33 ON TIMEOUTEnd of TILS with auto-enable 34 ON AUTOENDElapsed time limit reached 35 ON ELAPSED

TILS User's Guide

B-2 47 A2 04US Rev05

47 A2 04US Rev05 C-1

C. TILS Registers

REGISTER CONTENTS1 Length of last INPUT2 TOD of last INPUT (internal format)3 Length of last OUTPUT4 TOD of last OUTPUT (internal format)5 - Byte 1 contains the rank of the erroneous operand

- Bytes 2 to 4 contain the offset of the operator in the code segment

6 Error code, see Appendix E7 TOD of first response (internal format)8 Length of last accessed BLOCK or SEED9 -1 path is not OSI path

0 Normal data received 1 Typed data received 2 Expedited data received

10 -1 Path is not OSI path 0 Normal data sent 1 Typed data sent 2 Expedited data sent

11 -1 Path is not OSI path 0 Full SSDU received 1 Begin SSDU part received 2 Middle SSDU part received 3 Last SSDU part received

12 -1 Path is not OSI path 0 Full SSDU sent 1 Begin SSDU part sent 2 Middle SSDU part sent 3 Last SSDU part sent

13 Token control register: Byte1 - data token Byte2 - minor token Byte3 - major token Byte4 - release tokenSemantics: "FF"X token not available "00"X token not assigned "01"X token assigned

14 Length of last received USERDATA15 Length of last received USERINFO16 Reason code of received user exception17 Value of thinktime

TILS User's Guide

C-2 47 A2 04US Rev05

NOTES: - TOD (registers 2, 4, and 7) is stored in multiple of 256microseconds relative to the first event.

- Register 17 has a special function for thinktime depending on theTHINKTIME statement in the DECLARATION file. All the otherregisters must be declared in the DECLARATION file; through theSIZE statement for private registers and the COMMON statementfor sharable registers.

47 A2 04US Rev05 D-1

D. Limits of TILS Objects

OBJECT LIMITPATH 256 (TILS) or 4000 (TILS/LS)GROUP 2000DESTINATION 2000LOGON 2000USERINFO 2000DEVICE 400MAILBOX 239 (not principal mailbox)HISTOGRAM 300PROGRAM 2000BLOCK 4000FIELD DESCR. 32000ENTRY 4000LABEL 8000 per program and 16000 in the

SCENARIO fileLOOP 2000 per PROGRAM (each LOOP results

in an unnamed LABEL!)CHAR. STRINGCONSTANT

8000 (defined by STRING statement or through FIELD DESCRIPTOR)

NOTES: 1. Private input and output buffers, private non protected registers andconstant character strings are allocated in an expandable segmentwhose size may not exceed 4 megabytes.

2. Shared input and output buffers are allocated in two differentsegments. Programs, blocks and seeds are allocated in a secondsegment which also may not exceed 4 megabytes.

TILS User's Guide

D-2 47 A2 04US Rev05

47 A2 04US Rev05 E-1

E. Error Codes

E.1 ERROR CODES LINKED TO FIELD DESCRIPTORS AND REGISTERS

CODE DESCRIPTION OF THE ERROR -1 End of block 1 Field length negative or equal to zero 2 Field length exceeds maximum 3 Upper limit is out of field 4 Offset in field is negative 5 Offset register does not exist 6 Length register does not exist 7 Private register does not exist 8 Shared register not found 17 Offset exceeds field length 21 Block not assigned 23 BLOCK empty 24 SEED not defined 25 COMMAND field empty or not accessible 26 TELEGRAM field empty or not accessible 27 OUT field not filled for PATH 28 IN field not filled by PATH 30 Illegal access to protected register 45 BLOCK incorrectly addressed 79 Illegal access to OPENWA field 80 OPENWA inaccessible not in ON OPEN or RECONNECT 82 No WORKSPACE allowed for this path 91 USERDATA empty or not accessible150 Length exceeds 4096 characters

TILS User's Guide

E-2 47 A2 04US Rev05

E.2 ERROR CODES SPECIFIC TO TILS STATEMENTS

STATEMENT CODE DESCRIPTION OF THE ERRORCOPY R 9 target field protectedCOPY R 10 target field must be POOL or shared registerCOPY R 48 conversion from "HEXA" failedREGOP R 12 register not sharableDIVIDE R 13 division by zeroCVDB R 14 conversion of decimal failedCALL NR 15 more than 8 callsCVBD R 16 conversion of binary failedHISTOGRAM NR 18 illegal histogram numberPRINT NR 19 wrong order of registersPRINT NR 20 mixed register categoriesOCL R 22 OCL statement not executedDISPLAY R 29 DISPLAY statement not executedSET NR 32 non Boolean value for JCL switchSET NR 33 unknown JCL switchLOAD NR 34 value unavailable in contextRETURN NR 35 RETURN statement in main programBREAK NR 36 BREAK may not be used by CONTROL pathBREAK NR 37 BREAK may not be used in ON END or ON

ABNTERM sectionBREAK NR 38 DMNDTURN is not allowed in TWS modeBREAK NR 39 BREAK statement failedSWITCH NR 40 path rank out of boundsEVENT NR 41 path rank out of boundsEVENT NR 42 too many notifications on semaphoreEVENT NR 43 specified path is idleTILS R 46 TILS command exceeds 255 char.TILS R 47 no space available for commandEXTERNAL R 49 call of external procedure failedCONTROL R 90 path rank out of boundsSEND R 93 INPUT length >=32K (system limit)

NOTES: - R indicates that the error may be recovered

- NR indicates that the error may not be recovered

Error Codes

47 A2 04US Rev05 E-3

E.3 ERROR CODES SPECIFIC TO FILE ACCESS STATEMENTS

CODE DESCRIPTION OF THE ERROR50 Wrong unit51 Unit in use52 Maximum number of subfiles exceeded53 Subfile unknown54 Note failed55 Subfile already opened56 Failure to open subfile57 Subfile already closed58 Name should not exceed 31 characters59 Failure to close subfile60 Unit is not associated with opened subfile61 PMD should be "IN"62 No current record available63 Target should be POOL after "SWITCH"64 Record truncated65 Failure to get record66 PMD should not be "IN"67 Record length must not exceed 255 characters68 No more space available69 Failure to put record70 Target should be WORK or POOL71 No space available for key72 Register content is not a valid key73 Point failed74 No current seed available75 No current BLOCK record available76 Mismatch between key and statement77 "NOTE" executed by a different path

TILS User's Guide

E-4 47 A2 04US Rev05

E.4 ERROR CODES SPECIFIC TO OSI PATHS

CODE DESCRIPTION OF THE ERROR 81 CON_RESP used outside ON CON_IND section301 Activity function unit not negotiated302 Resynchronization functional unit not negotiated304 No current activity started306 Typed data may not be transferred307 Expedited data may not be transferred308 Capability data may not be transferred309 Expedited data length exceeds 14 bytes313 Activity in progress321 LEVEL contradicts token transfer331 Data token not available332 Minor token not available333 Major token not available334 Release token not available341 Data token assigned to correspondent342 Minor token assigned to correspondent343 Major token assigned to correspondent344 Release token assigned to correspondent351 Data token should be assigned to correspondent352 Minor token should be assigned to correspondent353 Major token should be assigned to correspondent354 Release token should be assigned to correspondent369 User data may not be transferred370 User data field exceeds 512 characters371 Resynchronization to inaccessible sync. point380 ACTIVITY is not interrupted381 ACTIVITY is unknown480 Statement not allowed in ON CON_IND section481 Several CON_RESP found in ON CON_IND section494 Illegal use after user exception495 Illegal in ON RELEASE_IND496 PATH may not use RELEASE RESP497 PATH is not ISO path498 RESP used without indication499 Not done

NOTE: Error codes between 400 and 600 may not be recovered.

47 A2 04US Rev05 F-1

F. Terminal Types Supported

Any one of the names in this list may be used for the TYPE parameter in the DEVICEstatement. Each NAME corresponds to an internal code used by VCAM to identify thetype of device. When an "x" is marked in column C, input sent by the device type istruncated by 1 character if the path is the initiator of the connection. TILS does not takeinto account any characteristic of a specific device such as the presence of a printer,diskette, or special character sets.

NAME CODE (hexa) CODE C DESCRIPTIONTTY33 2001 8193 xTTY35 2002 8194 xTTY37 2003 8195 xTTY38 2004 8196 xTN300 2005 8197 xTE318 2006 8198 xDTU717 2007 8199DTU7171 2008 8200 xDTU7172 2009 8201 xTTU8124 200A 8202 xTTU8126 200B 8203 xTTU8128 200C 8204 xVIP7100 200D 8205 xVIP7200 200E 8206 xTRC2811 200F 8207IBM2741 2010 8208TN1200 2011 8209 xTCV260 2012 8210TC349 2013 8211TC380 2014 8212AJ832 2015 8213 xVTE2820 2016 8214VIP7801 2017 8215 xIRISCOPE200 2018 8216DKU7001 2019 8217 xDKU7002 201A 8218 xDKU7102 201B 8219VIP7200S 201C 8220AJ833 201D 8221 xTI700 201E 8222AJ510 201F 8223

TILS User's Guide

F-2 47 A2 04US Rev05

NAME CODE (hexa) CODE C DESCRIPTIONTTX60 2020 8224TELEX 2021 8225DKU7003 2022 8226TTX35A 2023 8227 asynchronous modeMINITEL 2024 8228VIP7801T 2026 8230 text modeVIP7801V 2027 8231 VDF opt. text modeTEKTRONIX 2028 8232 x TEKTRONIX4105PC7800 2029 8233 xVIP765 2030 8240VIP775 2031 8241VIP785 2032 8242VIP7700 2033 8243MTS7500 2034 8244BTT7340 2035 8245KDS7265 2038 8248TTU8221 2039 8249VIP7760 203A 8250TTS7800 203B 8251VIP7001 203C 8252DKU7005 203D 8253VIP7804 203E 8254DKU7008 203F 8255DKU7007D 2040 8256 with disketteDKU7105 2041 8257DKU7107D 2042 8258 with disketteTTX35S 2043 8259 synchronous modeDKU7006 2044 8260DKU7211 2045 8261VIP7813 2046 8262VIP7814 2047 8263VIP7305 2048 8264VIP7201T 2049 8265 text modeVIP7804V 204A 8266 with VDF optionIRISCOPE300 2050 8272STS2840 2051 8273RBCOMP 2052 8274RBUNCOMP 2053 8275TLI5MSV2 2054 8276RCI 2055 8277A0 205A 8282A1 205B 8283A2 205C 8284IBM3741 2060 8288IBM3270 2061 8289IBM2780MONO 2062 8290 mono recordIBM2780MULTI 2063 8291 multi recordIBM3278 2064 8292IBM3780 2065 8293IBM3270P 2066 8294 with printer

Terminal Types Supported

47 A2 04US Rev05 F-3

NAME CODE (hexa) CODE C DESCRIPTIONIBM3287 2067 8295TN340 2073 8307ASPI10 2075 8309ASPI32 2076 8310ASPI38 2077 8311DY311 2078 8312MT281 2079 8313 xASPI30 207A 8314ASPI34 207B 8315TGT 2080 8320STID 2081 8321APPLICATION 1000 4096HXhhhhHX hhhh device with CODE

(hexa) hhhh

TILS User's Guide

F-4 47 A2 04US Rev05

47 A2 04US Rev05 G-1

G. Format of Generated Intermediate Code

All statements except ENTRY, LABEL, BLOCK, PROGRAM and STRING generateintermediate code according to the following format:

1 3 4 5 6

TEXT

number of operands in TEXT

O PTIO N code

O PERATO R code

tota l leng th o f O PE R ATO R b lock

Figure G-1. Format of the Intermediate Code

The TEXT part is a sequence of operands. Each operand has a TYPE and is 5 byteslong, except for TYPE 3 operands which contain the entire character string.

The first byte of an operand contains the TYPE of the operand, the remaining bytescontain an integer value depending on the TYPE. This table summarizes the contents ofthe remaining bytes for each TYPE:

TYPE CONTENTS1 Result register2 Integer value3 Character string4 Value register5 Absolute label number6 Field descriptor number7 Entry number8 Indirect result register9 Indirect value register

There is no one to one correspondence between the parameters of the statement and theoperands.

TILS User's Guide

G-2 47 A2 04US Rev05

47 A2 04US Rev05 H-1

H. Alphabetical List of Statements andCommands

H.1 LIST OF DECLARATION, SCENARIO FILE AND LOGFILE EDITSTATEMENTS

This table presents an alphabetical list of the statements in the DECLARATION,SCENARIO, and LOGFILE EDIT files, and shows in which file the statement is used.

STATEMENT FILE(S)ABS SCENARIOADD SCENARIOALARM SCENARIOAND SCENARIOASSIGN SCENARIOAUTO DECLARATIONBLOCK SCENARIOBREAK SCENARIOCALL SCENARIOCHECK SCENARIOCHECKPT SCENARIOCHRONOLOGY DECLARATIONCLOSE SCENARIOCOMMON DECLARATIONCON_RESP SCENARIOCOPY SCENARIOCVBD SCENARIOCVDB SCENARIODATA DECLARATIONDEBUG SCENARIODESTINATION DECLARATIONDEVICE DECLARATIONDISPLAY SCENARIODIVIDE SCENARIODO SCENARIODUMP DECLARATION / SCENARIO LOGFILE EDIT

TILS User's Guide

H-2 47 A2 04US Rev05

STATEMENT FILE(S)EDIT LOGFILE EDITELAPSED DECLARATIONEND SCENARIOENTRY SCENARIOEOD SCENARIOEVENT LOGFILE EDIT / SCENARIOEXTERNAL SCENARIOGET SCENARIOGOTO SCENARIOGROUP DECLARATIONHISTOGRAM DECLARATION / SCENARIOLABEL SCENARIOLOAD SCENARIOLOG SCENARIOLOGFILE DECLARATIONLOGON DECLARATIONMULTIPLY SCENARIONAME DECLARATIONNOT SCENARIONOTE SCENARIOOCL DECLARATION / SCENARIOON DECLARATION / SCENARIOOPEN SCENARIOOR SCENARIOOVERFLOW DECLARATIONPATH DECLARATIONPOINT SCENARIOPRINT DECLARATION / SCENARIOPROGRAM DECLARATION / SCENARIOPUT SCENARIORANDOM SCENARIORESET SCENARIORETURN SCENARIOSCAN SCENARIOSEED DECLARATIONSELECT LOGFILE EDITSEND SCENARIOSEQUENCE DECLARATIONSET SCENARIOSHIFT SCENARIOSIZE DECLARATIONSTRING SCENARIOSUBTRACT SCENARIOSWITCH SCENARIOSYNCHRONIZE SCENARIOTERMINATE SCENARIOTEST SCENARIOTHINKTIME DECLARATIONTILS SCENARIOTIMEOUT DECLARATIONTRACE DECLARATIONTRUNCATION DECLARATIONUSERINFO DECLARATIONWAIT SCENARIOWATCHDOG DECLARATION

Alphabetical List of Statements and Commands

47 A2 04US Rev05 H-3

H.2 LIST OF TILS OPERATOR COMMANDS

This table presents an alphabetical list of the TILS Operator commands.

STATEMENTAUTOCHANGEDEBUGDELAYDISPLAYDUMPELAPSEDGLOBALHELPLOGFILERESETSENDSTARTSTATISTICSSTOPTHINKTIMETRACEWATCHDOG

TILS User's Guide

H-4 47 A2 04US Rev05

47 A2 04US Rev05 i-1

Index

A

Abnormal termination 2-26, 4-6, 5-6ABS statement 10-5, 10-8Accessing blocks 2-19, 10-60Accessing data 8-19Accessing fields 3-9Accessing files 2-36, 4-7, 10-60Accessing seeds 10-60Activating sequences 4-4Active Service 5-2Activity 3-7, 8-3, 8-17, 10-11ACTIVITY statement 3-15, 8-6, 10-2, 10-9ADD statement 10-12Address 9-12ALARM statement 3-15, 8-18, 10-2, 10-13Alphanumeric parameter type 3-3AND statement 2-14, 10-14ASCII 4-8, 9-16, 10-32ASSIGN statement 3-17, 10-5, 10-15Asynchronous statements 8-5Attributes 9-14, 9-26AUTO command 2-8, 4-10, 11-4AUTO statement 2-8, 3-13, 9-3, 9-7

B

Backup Service 5-2Billing 2-4, 9-21, 9-26Binary 4-8, 9-16BLOCK statement 2-19, 3-14, 3-15,

10-2, 10-16Blocks 2-2, 2-19, 3-7, 6-2,

6-4, 9-11, 10-60BREAK command 2-38, 9-34BREAK statement 2-23, 3-15, 4-5,

4-7, 10-2, 10-18Buffers 2-10, 3-9

C

CALL statement 3-15, 4-6, 10-4, 10-19Capability data 8-3, 8-9, 10-20CAPABILITY statement 3-15, 8-6,

10-2, 10-20Carry the turn 2-6, 2-17, 4-4CHANGE command 4-10, 11-5Character set 4-8Character string 3-7Character string constants 2-12CHECK statement 2-26, 2-27, 3-15,

10-4, 10-23CHECKPT statement 10-25Chronogram 6-11CHRONOLOGY statement 2-33, 3-13,

6-11, 9-3, 9-8CLOSE statement 2-36, 3-16, 10-6, 10-26Closing Hybrid paths 5-6CNC 1-3, 3-17Collecting data 7-23, 9-8, 9-25, 11-14Collecting Data see also Output:

2-33Comments 7-24Commitment units 5-7COMMON statement 3-5, 3-13, 8-9,

8-19, 9-5, 9-9, C-2Compatibility of Old/New path states 4-9Compilation phase 2-6, 2-9, 4-2, 6-2, 9-41Complex 5-2Complex Description 5-2CON_RESP statement 10-27Concepts of TILS 1-1Confirmed session service 8-4CONNECT parameter 2-5, 2-8Connection 2-9, 4-3, 8-2Connection parameters 3-9, 5-6, 5-7Connection request 5-4Connection Statements 3-13Connection statements 9-4Consulting path 10-96Context Declaration Statements 3-13

TILS User's Guide

i-2 47 A2 04US Rev05

Context declaration statements 9-5Context of a path 2-10, 2-14, 10-96Continuation character 3-2Control paths 2-14, 2-38, 8-2, 8-7CONTROL statement 10-29Control Statements 3-15Controlling a TILS session 2-8Copy and Conversion Statements 3-15, 10-5COPY statement 2-12, 2-26, 2-27,

3-15, 4-8, 10-5, 10-31Correspondent 9-43CPU 1-3CRNETGEN 1-3, 3-17CSSDU see Capability data:

8-9CU see Commitment units:

5-7CVBD statement 3-15, 10-5, 10-33CVDB statement 3-15, 10-5, 10-34

D

Data Collection Statements 3-13Data collection statements 9-3DATA statement 3-13, 9-5, 9-11, 10-17Data token see Tokens:

8-13DEBUG command 4-10, 6-7, 6-8, 11-6DEBUG statement 3-16, 10-5, 10-35Debugging 2-26, 2-31, 2-33, 6-2, 8-19Debugging Statements 3-16, 10-5Declaration file 1-2, 2-35, 3-12, 9-1

Example of a DSA Network 2-32Example of calling LIBMAINT 2-13Example of Control paths 2-16Example of Histograms 2-34Example of hybrid paths 5-9Example of IOF 2-19Example of ON conditions 2-22Example of Operator Paths 2-38Example of OSI session services 2-41Example of paths usingsame program 2-4Example of Reduced file 2-5Example of synchronization 2-29Example of TDS 2-26Example of Unattended mode 2-9Example of using cataloged library 2-11Example of VBAD 2-36Printing 6-2

Declaration file statementsAlphabetical list H-1By type 3-13, 9-2Description of 9-6

Declaring Hybrid paths 5-4Definition parameter type 3-3DELAY command 4-10, 11-7Delimiter 10-16

DESTINATION statement 2-5, 2-6, 2-31, 3-13, 9-4, 9-12

Device attributes 4-8Device header 4-8DEVICE statement 2-5, 2-6, 2-17, 3-13,

4-2, 4-7, 4-8, 9-4, 9-14, F-1Device type 9-21Dialog trace 6-5Disconnect see Paths:

4-6DISPLAY command 4-10, 11-9DISPLAY statement 3-16, 10-5, 10-36Displaying SYSOUT data 10-75Distributed Systems Architecture see DSAnetworks: 2-40DIVIDE statement 10-37DO statement 3-15, 10-4, 10-38Down-time 5-2DSA network 1-1DSA networks 2-40DSA paths 3-9, 8-2, 8-7, 9-34,

10-18, 10-55Address of 2-40Correspondence of old/new states 4-9Using TILS with 2-31

DSA sessions 8-2Dummy message 2-19DUMP command 4-10, 11-10, 12-3DUMP statement 3-13, 3-16, 9-3,

9-18, 10-5, 10-40Dynamic fields 3-9

E

EBCDIC 4-8, 9-16, 10-32EDIT command 12-4Edit session 7-24Editing format 7-25ELAPSED command 4-10, 11-11ELAPSED statement 2-5, 2-8, 3-13,

9-3, 9-19Elapsed time 2-33END statement 3-15, 10-4, 10-41End-of-page marker 2-17Ending Simulation phase 2-7, 2-9Ending TILS 4-6Entry point 2-5, 2-12, 2-21, 6-4,

9-33, 10-42, 10-63ENTRY statement 3-15, 10-4, 10-42EOD statement 2-3, 2-19, 3-14, 3-15,

4-6, 10-2, 10-43Error codes E-1Error handling 2-26Error label 2-28Errors 4-12, 6-4, 8-13, 10-44, 10-96EVENT command 12-6

Index

47 A2 04US Rev05 i-3

EVENT statement 3-16, 4-2, 4-4, 7-13, 10-6, 10-44

Events 4-4, 4-12, 7-2, 7-13Exchange 2-33, 6-9Exchange see also Output:

2-33Executing path 10-96Execution level 2-21, 4-4, 8-6, B-1Expedited data 8-3, 8-9, 8-15, 10-69Extended FORTRAN Run Time package 1-3Extension type 3-12EXTERNAL statement 3-15, 10-4, 10-45External trace 2-33, 6-5

F

Failed requests 4-13FEPS 1-3, 3-17Field descriptors 2-10, 2-19, 3-5, 3-7,

6-4, 8-17Error codes E-1Parameter type 3-3

Fields 3-9, 6-4FIFO 4-2File access 2-36, 4-7File Access Statements E-3File Handling Statements 3-16, 10-6First in, first out see FIFO:

4-2FNPS 1-3, 3-17Forms 2-20Front End Network ProcessorSupport see FNPS:

1-3Front End Processor Support see FEPS:

1-3Full duplex 8-5Functional mode 8-8, 8-13Functional unit see Functional mode:

8-8

G

GCL 1-4, 2-8, 9-31GENPATH statement 9-2, 9-20GET statement 3-16, 10-6, 10-47GIVE_CONTROL statement 3-15, 10-3,

10-48GIVE_TOKEN statement 3-15, 10-3, 10-49GLOBAL command 4-10, 11-12Global Control Statements 3-13Global control statements 9-3Global type 3-12GOTO statement 3-15, 10-4, 10-51GROUP statement 9-23

H

HA 5-2Half duplex 8-5, 8-10, 8-18Header 7-23HELP command 2-8, 4-10, 11-13Hereditary type 3-12High Availability see HA:

5-2HISTOGRAM statement 2-33, 3-13, 3-16,

9-3, 9-24, 10-6, 10-52Histograms 2-34, 6-4, 6-7, 6-8, 6-10,

10-74, 10-81, 11-5, 11-15Hybrid paths 2-40, 4-9, 5-4, 6-9, 8-2

Abnormal termination 5-6Closing 5-6Declaring 5-4Reconnecting 5-6Starting 5-4

I

Identification statement 9-2Idle state 2-7, 2-9, 2-14, 8-2IFN see Internal File Name:

2-36Implicit SEND statement 10-89Initial turn 2-5Initialization 2-26Initiator 4-3, 8-4, 8-8Input/Output table 6-8Integer parameter type 3-3Interactive Operations Facility see IOF:

1-1Intermediate code 2-6, 6-2, G-1Internal File Name 2-36International StandardsOrganisation see ISO:

8-2Interrupt 4-13interrupt 10-18IOF iii, 1-1, 2-6, 2-38, 4-9,

9-58, 10-1Using TILS with 2-17, 2-29With TILS and TDS-HA 5-2

IOF Documentation vIQS 2-34ISO 2-40, 8-2

TILS User's Guide

i-4 47 A2 04US Rev05

J

JCL 2-6, 2-36, 3-17, 7-23Job Control Language see JCL:

2-6Job Occurrence Report see JOR:

2-21JOR 2-21

K

Keyword 3-2

L

LABEL statement 3-15, 10-4, 10-53LEVEL parameter 4-4LIBMAINT 2-12Library 2-7, 2-10Limits of objects D-1Line edit mode 2-19Link 8-2LOAD statement 2-14, 4-4, 8-14, 8-15,

8-16, 8-19, 10-5, 10-54, 10-101

LOG statement 3-16, 10-5, 10-57Logfile 2-33, 3-17, 7-1

Editing 7-24Errors 7-23Output 11-14

LOGFILE command 4-10, 7-23, 11-14Logfile Edit statements 12-1

Alphabetical list H-1By type 12-2

Logfile records 7-4, 7-10LOGFILE statement 3-13, 9-3, 9-25LOGON statement 2-4, 2-5, 2-6, 3-13,

4-13, 9-4, 9-26Loops 10-38, 10-41

M

Mailbox 2-6, 2-40, 4-3, 5-4, 9-21, 9-28Major sync points see Synchronization point:

8-3Major token see Tokens:

8-13Member 5-2Menus 2-20Message Path Descriptor see MPD:

5-4Messages 2-10Minor sync points see Synchronization point:

8-3

Minor token see Tokens:8-13

Mode 2-36MPD 5-4MULTIPLY statement 10-58

N

NAME statement 1-4, 2-8, 3-18, 4-2, 4-10, 8-3, 8-8, 9-2, 9-28

Network see DSA:1-1

Network Documentation viNetwork Generation Utility 1-3Network Service Access Point see NSAP:

8-3NODE parameter 2-31Normal data 8-3, 8-9, 8-15, 10-69NOT statement 10-5, 10-59NOTE statement 3-16, 10-6, 10-60Notifications 4-2, 7-4NSAP 2-40, 8-3, 9-30, 9-44NSSDU see Normal data:

8-9

O

OCL command 3-18, 9-28OCL statement 3-13, 3-16, 6-2, 9-3,

9-31, 10-6, 10-61Offset 2-12, 3-5On conditions see ON sections:

2-21ON OPEN 3-9ON RECONNECT 3-9ON sections 2-21, 4-4, 8-6, 8-9,

10-70, 10-86Ending 2-23ON ABNTERM 4-5, 4-14, 8-11, 9-34ON ACT_DISCARD_IND 8-17ON ACT_END_IND 8-17ON ACT_INTER_IND 8-17ON ACT_RESUME_IND 8-17ON ACT_START_IND 8-17ON ALARM 8-18, 9-36ON ATTENTION 4-5, 4-14, 9-34ON CAPABILITY_IND 8-10, 9-35ON COMMAND 4-5, 9-33ON CON_IND 9-35ON DATA 4-5, 8-10, 9-34ON DMNDTURM 4-14ON DMNDTURN 4-5, 9-34ON END 4-5, 8-11, 9-34

Index

47 A2 04US Rev05 i-5

ON ERROR 4-5, 4-6, 8-7, 8-11, 9-33ON GIVE_TOKEN 8-13, 8-14ON GIVE_TOKEN_IND 9-35ON MINOR_CONF 8-15ON OPEN 4-5, 9-34, 9-35ON PLEASE_TOKEN 8-14ON PLEASE_TOKEN_IND 9-35ON RECONNECT 9-34ON REJECT 4-5, 9-34, 10-55ON RELEASE_IND 8-12, 9-35ON RESYNC_IND 9-36ON TELEGRAM 4-5, 4-14, 9-34ON_REJECT 8-8

On sectionsON ERROR 2-27

ON statement 3-15, 4-4, 9-5, 9-33, 10-4, 10-63

OPEN statement 2-36, 3-16, 10-6, 10-65Operator commands see TILSOperator commands: 1-4Operator paths 2-38OR statement 10-67OSI

Full duplex 8-8OSI paths 2-10, 2-40, 3-4, 3-7,

3-9, 7-10, 8-2, 8-5, 8-7, 8-19, 9-12,

9-17, 9-27, 9-29, 9-35, 9-39, 9-58,

10-9, 10-13, 10-20, 10-48, 10-49, 10-55, 10-68, 10-71, 10-79,

10-82, 10-99Address of 2-40Error codes E-4Record header 7-11Record types 7-12

OSI session services iii, vi, 1-4, 2-40, 6-7, 8-8, 10-79

Aborting 8-4Connections 8-8Ending 8-11Errors 8-4Example of 2-41Level see OSI-V1 or OSI-V2:

1-1Requesting 8-4Types of 8-3Versions 8-4

OSI Session Statements 3-15, 10-2OSI-V1 2-40, 8-4, 9-47, 10-55OSI-V2 2-40, 8-4, 8-9, 8-19,

9-47, 10-55OSI_SEND statement 3-15, 10-3, 10-68Output 2-6, 2-7, 2-33, 2-35, 3-7,

3-17, 4-8, 6-1, 7-25, 9-16, 9-41, 10-74, 11-9, 11-24, 12-3

Chronological 2-35Dialog trace 2-33

Exchanges 2-33Response times 2-33see also SYSOUT, Logfile,Histogram: 2-33

OVERFLOW statement 3-13, 4-6, 4-13, 9-3, 9-37

P

Parameter types 3-3Alphanumeric 3-3Definition 3-3Field descriptor 3-3Integer 3-3Register 3-3Reserved word 3-3Result register 3-3Text 3-3

Password 2-4, 9-21, 9-26Path Declaration Statements 3-13Path declaration statements 9-2PATH statement 2-4, 3-12, 3-13, 8-3,

9-2, 9-38Paths 2-2, 2-10, 4-2, 8-2,

9-9, 10-1, 10-29Attributes 6-4, 8-8Categories of 8-7Closing 2-23Closing of 2-28, 4-6, 11-15Connecting 9-29, 11-19Declaring 9-20, 9-38Entry point 2-23Execution level 2-21Maximum allowed 9-28Opening of 4-3State of see Status:

2-14Statistics 6-8, 6-9, 11-21Status 2-14, A-1

PLEASE_TOKEN statement 3-15, 10-3, 10-71

POINT statement 3-16, 10-6, 10-73Pointed type 3-12Pool 2-23, 3-7, 9-9Prerequisites for Running TILS 1-3PRINT statement 3-13, 3-16, 6-5,

6-7, 9-3, 9-41, 10-5, 10-74Printing phase 4-2, 6-8Private register 2-10, 3-4PROFILE statement 2-40, 3-13, 8-3,

8-8, 8-13, 8-17, 9-4, 9-21, 9-39, 9-43

TILS User's Guide

i-6 47 A2 04US Rev05

PROGRAM statement 2-3, 2-5, 3-12, 3-14, 3-15, 9-5,

9-48, 10-2, 10-76Programs 2-2, 3-14, 6-2, 6-4, 8-5, 10-17Project 2-4Protected characters 3-2PUT statement 3-16, 10-6, 10-77

R

RANDOM statement 10-5, 10-78Rank 2-8, 8-8Reason code 10-13Reconnecting Hybrid paths 5-6Record header 7-2, 7-11Record size 7-23Record types 7-4, 7-12Records 3-2, 3-12, 3-14, 12-6Register 17 see Thinktime:

2-29Registers 2-10, 3-7, 8-19, 9-9,

9-51, 10-74, C-1Addressing a 3-5Error codes E-1Parameter type 3-3

Release see Version:1-4

RELEASE statement 3-15, 8-6, 10-3, 10-79Release token see Tokens:

8-13Requesting OSI session services 8-4Reserved word 3-3RESET command 4-6, 4-10, 11-15RESET statement 3-16, 10-6, 10-81Response times 2-33, 6-8, 6-10Result register parameter type 3-3RESYNC statement 3-15, 8-6, 10-3, 10-82Resynchronization 8-3, 8-15, 8-16,

9-46, 10-82Retry 6-9, 9-27, 10-86Return codes 4-13, 6-7, 7-25, 8-11RETURN statement 2-23, 2-35, 3-15,

4-5, 4-6, 10-4, 10-86Right to transmit see Turn:

2-6RON 2-21, 9-28Run Occurrence Number see RON:

2-21

S

SARF format 4-7SCAN statement 3-15, 10-4, 10-87SCANNER command 2-21Scenario file 1-2, 3-14, 10-1

Example of an ON ERROR section 2-27

Example of calling LIBMAINT 2-12Example of Control paths 2-15Example of Histograms 2-35Example of hybrid paths 5-10Example of IOF 2-18Example of ON conditions 2-22Example of Operator Paths 2-39Example of OSI session services 2-42Example of paths using sameprogram 2-3Example of synchronization 2-30Example of TDS 2-25Example of using cataloged library 2-11Example of VBAD 2-37Printing 6-2

Scenario file statementsAlphabetical list H-1By type 3-15, 10-2Description of 10-7

Scope 9-1Seed 2-12, 2-26, 3-7, 6-2SEED statement 3-13, 9-5, 9-49Seeds 10-60SELECT command 12-7SEND command 2-39, 3-9, 4-10, 11-17SEND statement 2-7, 2-12, 2-35, 3-15,

4-3, 4-4, 4-5, 4-7, 8-10, 9-53, 10-2, 10-70, 10-89

Sequence of records see Blocks:2-19

SEQUENCE statement 3-13, 4-6, 9-3, 9-50Sequences 4-7, 8-5, 8-15Sequences of statements 4-3Server 5-2Service 5-2Session 8-2Session Service Access Point see SSAP:

8-3Session Service Data Unit see SSDU:

10-68Session services 8-2Session Services see also OSI, DSA:

2-40SET statement 3-16, 10-6, 10-92Sharable registers 2-14, 2-26, 3-4, 9-9Shared buffers 3-9, 8-19SHIFT statement 10-5, 10-93Simulation phase 2-5, 4-2, 4-3, 4-6,

8-3, 9-8, 9-19, 9-50, 11-4, 11-11

Ending 9-7, 9-32, 10-102, 11-22Output 6-5Starting 2-8

Site Catalog 2-4, 2-5

Index

47 A2 04US Rev05 i-7

SIZE statement 2-11, 3-5, 3-13, 3-17, 8-9, 8-19,

9-5, 9-51, C-2Source 2-12, 6-3Source Language Library 3-12Source language library 2-2, 2-36, 3-14, 4-7SSAP 2-40, 8-3, 8-8, 9-22,

9-29, 9-39SSDU 8-10, 10-21, 10-68SSF format 4-7, 10-65START command 2-6, 3-18, 4-3, 4-10,

8-8, 11-19Starting Simulation phase 2-8Starting TILS 2-6Static fields 3-9Statistics 9-8, 10-29, 11-12, 11-15STATISTICS command 4-10, 11-21Status of a path 2-14, A-1STOP command 2-7, 4-6, 4-10, 6-8, 11-22String definition 6-4STRING statement 3-16, 10-6, 10-94SUBTRACT statement 10-95Summary tables 6-4Surveillance period 11-25SWITCH statement 2-14, 3-16, 10-6, 10-96Synchronization 2-29, 8-3, 8-15Synchronization point 8-3, 8-15, 10-10,

10-56, 10-83, 10-99Synchronization Statements 3-16, 10-6SYNCHRONIZE statement 2-12, 3-16, 4-3,

4-4, 4-5, 4-7, 8-6, 10-6, 10-98

SYNCPT statement 3-15, 8-15, 10-3, 10-99Syntax of statements 3-2SYSOUT 2-33, 4-12, 6-5, 9-56,

10-74, 11-24System failure 5-2System variable 2-17

T

Tab character 2-19Takeover 5-2TDS iii, 10-1

Applications 4-9Using TILS with 2-24

TDS Documentation vTDS-HA 1-1, 5-4TELEGRAM command 3-9Telegrams 3-7, 6-9Terminal Manager 1-1Terminal types 2-5, F-1Terminal types see also Device types:

F-1TERMINATE statement 2-14, 2-23, 3-15,

4-6, 4-7, 8-11, 8-12, 9-36, 10-4, 10-102

Test mode 9-29

TEST statement 3-15, 10-4, 10-104Text 7-23Text parameter type 3-3Thinktime 2-5, 2-29, 4-4, 9-21,

10-90, 11-7THINKTIME command 4-10, 11-23THINKTIME statement 3-5, 3-13, 9-3,

9-53, C-2TILS

Editing with 7-24Starting the TILS job 2-6

TILS and HA 5-2TILS console 10-75TILS Operator Commands 7-3, 9-7TILS Operator commands1-4, 2-8, 4-10, 11-1

Alphabetical list 11-3By type 11-2Default value 2-8Format of 2-8Listed Alphabetically H-3Purpose of 2-8, 11-13Syntax of 2-8, 11-13

TILS operator commandsEntering 4-10

TILS sessionAborting 4-7, 10-102Controlling 4-1Output 2-33Parameters 3-12Preparing 3-1Starting 3-17Syntax of 3-2Using in TWS mode 4-7With DSA session services 2-31, 4-1With IOF 2-17, 2-29, 3-17With OSI session services 2-40, 4-9, 8-1With TDS 2-24, 4-3

TILS statement 2-5, 3-16, 10-6, 10-105TILS Statements

Error codes E-2Executing 4-3

Time-limit 2-5, 4-7, 9-19, 9-53, 9-60, 11-11

TIMEOUT statement 3-13, 4-6, 9-3, 9-55Timer 2-17, 4-2, 4-3TM see Terminal Manager:

1-1Tokens 8-5, 8-7, 8-8, 8-11,

8-13, 8-15, 9-45, 10-10, 10-48, 10-49, 10-69, 10-71,

10-80, 10-83Requesting 8-14Transferring 8-13

TRACE command 4-10, 11-24Trace of execution 10-35, 11-6

TILS User's Guide

i-8 47 A2 04US Rev05

TRACE statement 3-13, 6-5, 6-7, 9-3, 9-56Transaction Driven Subsystems see TDS:

1-1Transferring data 8-9Transmission Statements 3-15, 10-2Transport Service Access Point see TSAP:

8-3TRUNCATION statement 3-13, 4-6, 4-13,

8-9, 8-10, 9-3, 9-57TSAP 2-40, 8-3, 9-30, 9-44TSSDU see Typed data:

8-9Turn 2-6, 9-15, 10-89TWA 2-6, 9-16, 10-91Two Way Alternate mode see TWA:

1-1TWS 4-7, 6-9, 9-16, 10-91TYPE parameter F-1Typed data 8-3, 8-9, 8-15, 10-69, 10-70Types of OSI session services 8-3

U

Unattended mode 2-8Unconfirmed session service 8-4User abort 8-11User exception report 8-18, 9-47, 10-13User ID 2-4USERDATA 10-79Userdata 8-11, 8-19USERINFO statement 3-13, 9-4, 9-58Using TILS see TILS:

2-2

V

Variable fields 3-9Variable thinktime 2-17VCAM 2-40, 4-2, 4-7, 4-8,

6-9, 8-2, F-1Version iii, 1-4, 9-32Versions of OSI session services 8-4Virtual Communication AccessMethod see VCAM:

1-1

W

WAIT statement 2-12, 2-30, 3-16, 4-3, 4-4, 4-5, 4-7, 8-6, 10-6, 10-106

Watchdog 9-55WATCHDOG command 4-10, 11-25WATCHDOG statement 2-5, 3-13, 9-3, 9-60WORKLIB 3-17, 10-65

Workspace 2-10, 2-23, 3-7, 9-51

X

XSSDU see Expedited data:8-9

Technical publication remarks form

Title : DPS7000/XTA NOVASCALE 7000 T.I.L.S. User's Guide Operating System: Tuning

Reference Nº : 47 A2 04US 05 Date : October 1995

ERRORS IN PUBLICATION

SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Your comments will be promptly investigated by qualified technical personnel and action will be taken as required.If you require a written reply, please include your complete mailing address below.

NAME : Date :

COMPANY :

ADDRESS :

Please give this technical publication remarks form to your BULL representative or mail to:

Bull - Documentation Dept.

1 Rue de ProvenceBP 20838432 ECHIROLLES [email protected]

Technical publications ordering form

To order additional publications, please fill in a copy of this form and send it via mail to:

BULL CEDOC357 AVENUE PATTONB.P.2084549008 ANGERS CEDEX 01FRANCE

Phone: +33 (0) 2 41 73 72 66FAX: +33 (0) 2 41 73 70 66E-Mail: [email protected]

CEDOC Reference # Designation Qty

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

[ _ _ ] : The latest revision will be provided if no revision number is given.

NAME: Date:

COMPANY:

ADDRESS:

PHONE: FAX:

E-MAIL:

For Bull Subsidiaries:

Identification:

For Bull Affiliated Customers:

Customer Code:

For Bull Internal Customers:

Budgetary Section:

For Others: Please ask your Bull representative.

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

47 A2 04US 05REFERENCE

t.i.l.s. user's guide - atossupport.bull.com/ols/product/system/gcos7/gcos7... · tils...

Documents