mptmon

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MPTMON USER MANUAL

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– ALL 213 PAGES AT EDITION 013 COMPUTER GENERATED (IDSS) ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

013 DATE–NO:15.06.91 SIGN:J.Tiekenheinrich 211 31515 AAAA EA 1

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– PREFACE _______ This User Manual is written for testers which have experience in integration testing using ICE86 as test support tool. For those testers not familiar with ICE86, it is recommended that they refer to the ICE86 Reference Manual in case of any basic uncertainty. Effort is given to provide a precise, but short syntax definition and command description of MPTMON. The author is looking forward for any contribution to improve or extend the scope of this document. An alphabetical index comprising all command areas with their related commands, is attached at the end of this document, to provide a quick reference to the page where the item is described. A reference card giving a survey of all commands and its syntax may be attached as the last page of this document.

013 211 31515 AAAA EA 2

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– CONTENTS ________

1. GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3 Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4 Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.5 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.6 Referenced Documents . . . . . . . . . . . . . . . . . . . . . . . . 12 2. SYNTAX DEFINITION . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.1 Lexicon Conventions . . . . . . . . . . . . . . . . . . . . . . . . 13 2.2 Key–words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3 Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.4 Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.5 Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3. COMMAND DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.1 Test session commands . . . . . . . . . . . . . . . . . . . . . . . 22 3.2 Control element commands . . . . . . . . . . . . . . . . . . . . . . 26 3.3 Memory display and modify commands . . . . . . . . . . . . . . . . . 32 3.4 Symbol commands . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3.5 Macro commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.6 Compound commands . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.7 Breakpoint commands . . . . . . . . . . . . . . . . . . . . . . . . 50 3.8 Message commands . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.9 Call commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 3.10 SW trace commands . . . . . . . . . . . . . . . . . . . . . . . . . 71 3.11 HW trace commands . . . . . . . . . . . . . . . . . . . . . . . . . 82 3.12 Display commands . . . . . . . . . . . . . . . . . . . . . . . . . 96 3.13 Library commands . . . . . . . . . . . . . . . . . . . . . . . . . 100 3.14 File handling commands . . . . . . . . . . . . . . . . . . . . . . 106 3.15 MMC interface commands . . . . . . . . . . . . . . . . . . . . . . 110 3.16 Event handling commands . . . . . . . . . . . . . . . . . . . . . . 116 3.17 Work areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.18 Resident macro tables . . . . . . . . . . . . . . . . . . . . . . . 122 3.19 Run time options . . . . . . . . . . . . . . . . . . . . . . . . . 124 3.20 Miscellaneous Commands . . . . . . . . . . . . . . . . . . . . . . 130 4. TEST CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . 134 4.1 Terminal Connections . . . . . . . . . . . . . . . . . . . . . . . . 134 4.2 Terminal Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 4.3 Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 5. TESTING NOTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 5.1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . 143 5.2 General Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . 143

013 211 31515 AAAA EA 3

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

.

Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A. EXAMPLES . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 A.1 Session Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 A.2 Basic Help Macro . . . . . . . . . . . . . . . . . . . . . . . . . . 153 A.3 Data Display Macros . . . . . . . . . . . . . . . . . . . . . . . . 155 A.4 Message Handling Macros . . . . . . . . . . . . . . . . . . . . . . 159 A.5 Breakpoint Handling Macros . . . . . . . . . . . . . . . . . . . . . 162 A.6 HW Trace Macros . . . . . . . . . . . . . . . . . . . . . . . . . . 165 A.7 MMC Handling Macros . . . . . . . . . . . . . . . . . . . . . . . . 170 A.8 Menu Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 A.9 Relation Display Macros . . . . . . . . . . . . . . . . . . . . . . 175 A.10 Data Base Access Macros . . . . . . . . . . . . . . . . . . . . . . 178 A.11 Command Table Generator Macro. . . . . . . . . . . . . . . . . . . 180 APPENDIX B. DATA STRUCTURES . . . . . . . . . . . . . . . . . . . . . . . 183 B.1 Message buffer layout . . . . . . . . . . . . . . . . . . . . . . . 183 B.2 Data Base Access (DB–V2) . . . . . . . . . . . . . . . . . . . . . . 185 B.3 Data Base Access (DB–V4) . . . . . . . . . . . . . . . . . . . . . . 187 APPENDIX C. DEBUG MONITOR . . . . . . . . . . . . . . . . . . . . . . . . 190 APPENDIX D. ERROR MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . 191 APPENDIX E. SYSTEM 12 IOS COMPLETION CODES . . . . . . . . . . . . . . . . 193 APPENDIX F. DATABASE STATUS INFORMATION . . . . . . . . . . . . . . . . . 195 APPENDIX G. OSN PRIMITIVES IN ALPHABETICAL ORDER . . . . . . . . . . . . . 196 APPENDIX H. OSN PRIMITIVES IN NUMERICAL ORDER . . . . . . . . . . . . . . 200 APPENDIX I. PRIVATE NOTES . . . . . . . . . . . . . . . . . . . . . . . . 204 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

013 211 31515 AAAA EA 4

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

.

Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 1. GENERAL INFORMATION ______________________

1.1 Scope __________

The MPTMON is a test tool intended for system level testing, performing ICE86 like functions in a System 12 multi–processor environment. It may be used as well for local integration level testing when the required MPTMON HW test configuration is installed. This User Manual describes briefly MPTMON’s functioning, defines its syntax and explains how to use it.

1.2 Introduction _________________ The concept of MPTMON allows the access from one or more dedicated processors (PTCE) containing a command handler (called MPTMON–Controller) to any other processor in a System 12 exchange containing a command executer (called MPTMON–Slave). The MPTMON–Controller may drive one or more asynchronous interfaces connected to a dedicated MPTMON VDU or another computer e.g. a PC or a VAX. The Controller is basically responsible for the command syntax checks and preparation of command buffers which are sent via a user controlled path (UCP) to a Slave. The Slave executes simple commands, like memory read or write, and prepares a response buffer which is formatted and displayed by the Controller. Furthermore, the Controller has to evaluate expressions, process macros and analyse compound commands. If required for this processing, access is made to the Slave to get memory values. Commands can be input from a keyboard and read as well from files, residing on a System 12 IOS device. The figure hereafter gives an overview of the most essential interfaces of MPTMON modules to other modules in System 12. Some interfaces are not shown here, e.g. to some SSM’s, to keep the figure simple. Beside entering commands on a dedicated terminal connected to the PTCE, commands can be entered as well on a System Terminal connected to the PLCE after a test session has been started by using a normal ORJ. This operation mode requires of course that the PLCE is up and running.

013 211 31515 AAAA EA 5

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

+––––––––––––––––––––––––––+ +–––––––––––––––––+ VAX | PTCE | | TARGET CE | | | +–––+ +––––––––––––+ | | +–––––––––––+ | OBC +––––––+––| A | +–| PADS | | +––––+––| Relay FMM |––+–––> +–––––+ | | S |–| +––––––––––––+ | | | +–––––––––––+ | | VDU |–––+––| Y | | | | | | | +–––––+ | +–––+ | +––––––––––––+ | | | +–––––––––––+ | | |–| Controller |––+–––/ /–––+––| Slave FMM | | | +–––+ | | and | | UCP | +–––––––––––+ | +–––––+ | | S |–+ | Routines | | | | | | VDU |–––+––| I | +––––––––––––+ | | +–––––––––––+ | +–––––+ | +–––+ | | | | | | Slave SSM | | or | | | | | | +–––––––––––+ | VAX +––––––––––––––+––+––+–––––+ +–––––––––––––––––+ | | | | | | +–––––––––––––––––+ | | | | PLCE | | | | VP | +–––––––––––+ | Disk | | +–––––––––/ /–––+––| I O S |––+––––> | | | +–––––––––––+ | | | VP | +–––––––––––+ | | +––––––––––––/ /–––+––| R T S H | | | | +–––––––––––+ | | VP | +–––––––––––+ | System +–––––––––––––––/ /–––+––| VDU–FH |––+––––> | +–––––––––––+ | Terminal +–––––––––––––––––+ MPTMON’s Environment and Interfaces

1.3 Responsibility ___________________ Responsible for the design and maintenance of MPTMON are: – J. Tiekenheinrich SEL Stuttgart (Tel.0711–8265....), Ext.: 2021 Features and Syntax definition. Design and maintenance of the MPTMON Controller. – J. Langton SEL Stuttgart, Ext.: 2024 Design and maintenance of MPTMON Slave FMM. – G. Abele SEL Stuttgart, Ext.: 2023 Design and maintenance of MPTMON Slave SSM. – R. Fassbender SEL Stuttgart, Ext.: 2024 Design and maintenance of the drivers. – H. Herb SEL Stuttgart, Ext.: 2361 VAX MPTMON interface.

013 211 31515 AAAA EA 6

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 1.4 Change History ___________________ This edition covers the new features and changes implemented in MPTMON V3.9 re–delivered for SKR 6 (use GSM’s FARBTA12, YWNLTA10, MSCLTA09, FHHVTA09, FFKKTA10 and MJRRTA02). The new or modified features compared with the first release of MPTMON V2.6 (User Guide edition 11) are: – the ”START–MPTMON” ORJ will be also accepted from the binary device handler. – a new keyword PID has the process identity of the process on breakpoint, the new keyword OBC has the number of the selected OBC (”2.2 Key–words” on page 13). – in order to support testing in a Release 6 mixed hardware environment new keywords like TMC, MP, ROMD and IDT have been introduced to be able to write generic macros which are as independent as possible from the hardware of the selected CE. Furthermore the new keywords GDT and LDT give access to the descriptor tables for processors running in virtual mode (”2.2 Key–words” on page 13). – the priority of the operators ”AND” and ”OR” have been changed and a new boolean operator ”XOR” (exclusive OR) has been added (”2.4 Operators” on page 18). – comparisons on pointers are now considered as unsigned comparisons on the offset. For integers the sign oriented operations are kept (”2.5 Expressions” on page 19). – an additional parameter with the ’LIS ON’ command allows logging on other files than the default list file (”3.1.3 List On” on page 24). – booting of a control element may be performed with or without fast test of the processor board (”3.2.9 Boot control element” on page 30). – the ”CE LOAD” command can handle core image records up to 64K and is able to load an 80386 target CE as well. For an 80386 target CE it is also possible to stop after loading. Then the ROM Debug Monitor (RODEM) may be activated to check or modify the memory contents of the CE (”3.2.10 Load control element” on page 31). – MPTMON’s 8086/80286 disassembler is extended to 80386 instructions. (”3.3.7 Disassemble code” on page 35). – The line assembler now supports an in–line segment override prefix (”3.3.8 Patch code” on page 36). – the GSM name of a Release 6 compiled module fetched by a FET FMM or FET SSM command is displayed on the screen. The actual start address of the GSM code is stored in register IP (”3.7.1 Fetch FMM location” on page 51 and ”3.7.2 Fetch SSM location” on page 52). – a new command ”RES REG” restores the registers of a process on breakpoint after corruption by – for example – a fetch command (”3.7.7 Restore breakpoint registers” on page 57). 013 211 31515 AAAA EA 7

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– – a new command ”DB4 ACC” provides a low level interface to the new database V4 routines (”3.9.3 Call database interface (DB–V4)” on page 67). – a new command ”TRC PID” allows tracing of all messages sent or received by a specified process (”3.10.5 Trace process” on page 74). – SSM tracing and database tracing are new features introduced with support of the new OSN variants (”3.10.8 Trace SSM” on page 77 and ”3.10.9 Trace relation” on page 77 ). – a new command ”TRC ENV” allows tracing of a whole FMM environment, i.e. tracing all messages of the qualified FMM, all SSM calls and all database accesses (”3.10.10 Trace FMM environment” on page 78). – a new command ”TRC” without any parameter displays the currently active trace condition of the selected CE (”3.10.12 Trace display” on page 78). – during collection of MPTMON trace buffers on an IOS device the number of lost items are stored as well now (”3.10.14 Collect trace buffers” on page 80). – a new command ”SHO TRF” displays the actual status of the hardware tracer (”3.11.9 Show TRF status” on page 93). – ”BAS=Y” selects the binary output base (”3.12.6 Set output base” on page 98). – ”SUF=Y” selects the binary input base (”3.12.7 Set input base” on page 99). – All library commands changing the contents of a non default library are now put under password control (”3.19.1 Command authorizations” on page 124). – a batch process now informs the originator about successful completion before it terminates. Moreover it is easily possible to process a macro instead of an include file (”3.14.4 Start batch process to include from SYSTEM 12 IOS” on page 108). – a new command has been added to a abort a batch process (”3.14.5 Abort batch process” on page 109). – MMC access from a NSC–MPTMON to a remote exchange is now possible (”3.15.3 Set global MMC password” on page 113). This covers as well MMC access to an isolated P&L processor. – the command ”COP MEM” allows a user work area (UWA) as third parameter for the destination (”3.17.2 Copy memory” on page 119). – the command ”DIR TAB” can optionally select a macro table (”3.18.3 Directory macro table” on page 123). – the command ”SET TRC” provides variable trace length for messages and user buffers as well as cyclic tracing (”3.19.5 Set trace length” on page 126).

013 211 31515 AAAA EA 8

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– – for expressions giving a result less than 256 the binary representation and the corresponding ASCII character (if displayable) are shown as well using the command ”EVA” (”3.20.1 Evaluate expression” on page 130). – a new command ”FET PID” gives information about a certain process (”3.20.4 Fetch process” on page 132). – the ”FET REL” command displays the name of the relation which is fetched (”3.20.3 Fetch relation” on page 131). – a new command ”ERT” converts error types to error mnemonics (”3.20.5 Display error type mnemonic” on page 132). – a ”HELP” command supports a macro driven information on the SYSTEM 12 disk (”3.20.6 Help command” on page 132). – MPTMON’s default configuration is now stored in a relation which can be modified using normal GDMH commands (”4.1 Terminal Connections” on page 134). – the default authorisation for a MPTMON session started from a System VDU is restricted to read–authorisation (”4.1 Terminal Connections” on page 134). – the Hewlett Packard Terminal is not supported any longer. – since the Hewlett Packard Terminal was the only one with a proper handling of formatted screens, menus and forms, the commands ”Format screen” and ”Enter screen” have been deleted. – a list of all OSN primitives and their corresponding numbers are now part of the appendix of this document.

013 211 31515 AAAA EA 9

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 1.5 Abbreviations __________________ CE Control Element CMD Command CHILL CCITT High Level Language DBCS Database Control System DLS Data Load Segment FCB FMM Control Block FMM Finite Message Machine GDMH Generic Data Manipulation Handler GDT Global Descriptor Table GLS Generic Load Segment GSM Generic Software Module HW Hardware ICE86 In Circuit Emulator 8086 IDT Interrupt Descriptor Table IOS Input Output System ISDN Integrated Service Digital Network LDT Local Descriptor Table MCUA/MCUB Module Control Unit type A / type B MDS Micro Computer Development System MMC Man Machine Communication HILTI HIgh Level Test Instrument MPTMON Multi Processor Test Monitor MULTIPOL Multi Problem Oriented Languages NSC Network Service Center OBC On Board Controller ORJ Operator Request Job OS Operating System OSN Operating System Nucleus 013 211 31515 AAAA EA 10

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– OSNL Operating System Nucleus Language PADS Patch Distribution System PBA Printed Board Assembly PCS Product Change Status PID Process Identity PTCE Permanent Test Control Element RODEM ROM Debug Monitor RSU Remote Subscriber Unit RTSH Report and Task Supervision Handler SCB SSM Control Block SCRIPTGEN Test Script Generator SI Serial Interface SLT System Load Tape SRASM Standard Relocatable Assembler SSM System Support Machine TCB Timer Control Block TCPA/TCPB/TCPC Terminal Control Processor type A / type B / type C TI Terminal Interface TRFA/TRFB/TRFE TRace Facility type A / type B / type E UCP User Controlled Path VAX Virtual Address Extension VDU Visual Display Unit

013 211 31515 AAAA EA 11

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 1.6 Referenced Documents _________________________ 1. INTEL Manual ICE86 In Circuit Emulator Operating Instructions (Order Number 9800714A) 2. TDV 2242S Tandberg VDU (Part no.408727) 3. EK–VT100–UG–002 VT100 User Guide 4. 160 05109 XXXX–DS Visual Display Unit (Olivetti) 5. 211 26469 AAAA–EA UMA–OS User Manual 6. 211 31502 AAAA–EA UMA–OS Reference Manual 7. 211 31504 AAAA–PQ DAS–OSN Data Description Manual 8. 163 00567 AAAA–PW HILTI User Guide 9. 163 33002 AAAA–PW PADS User Guide 11. 163 33003 AAAA–PW SCRIPTGEN User Guide 10. 211 37728 AAAA–DS PBA–TRFA Trace Facility 11. 211 37854 AAAA–DS PBA–TRFB Trace Facility 12. 214 78812 AAAA–DS PBA–TRFE Trace Facility

013 211 31515 AAAA EA 12

http://dms.alcatel.be/Dms/NSF/dms.nsf/Calldoc?OpenAgent&dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxx&code=_160/_05/_109/_xxxx/_ds____.pl

http://dms.alcatel.be/Dms/NSF/dms.nsf/Calldoc?OpenAgent&dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxx&code=_211/_26/_469/_aaaa/_ea____.pl

http://dms.alcatel.be/Dms/NSF/dms.nsf/Calldoc?OpenAgent&dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxx&code=_211/_31/_502/_aaaa/_ea____.pl

http://dms.alcatel.be/Dms/NSF/dms.nsf/Calldoc?OpenAgent&dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxx&code=_211/_31/_504/_aaaa/_pq____.pl

http://dms.alcatel.be/Dms/NSF/dms.nsf/Calldoc?OpenAgent&dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxx&code=_163/_00/_567/_aaaa/_pw____.pl



http://dms.alcatel.be/Dms/NSF/dms.nsf/Calldoc?OpenAgent&dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxx&code=_211/_37/_728/_aaaa/_ds____.pl



ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 2. SYNTAX DEFINITION ____________________

The syntax of each command is structured in the same manner: it begins with a main command keyword, symbol reference or macro reference, followed by an optional command specifying keyword, optional parameters, an optional comment and ends with a command line terminator, carriage return (cr). Comments must start with a semicolon ’;’ and may be given after any command inclusive the NULL command. A command line must not exceed 80 characters (upper case only) i.e. one screen line; all characters exceeding one line are ignored until a carriage return is entered.

2.1 Lexicon Conventions ________________________ A simple syntax definition is used: – Key–words are shown in capitals, and used unchanged (e.g. INI). – User parameters are indicated by descriptive names in lower case, and must be replaced by suitable values as defined in the command description. – The punctuation marks, comma ’,’, equal sign ’=’, period ’.’, colon ’:’, and semicolon ’;’ must be reproduced in statements. – Square brackets ’[]’ enclose optional elements of commands. – An oblique stroke ’!’ separating elements indicates that one (and only one) of these elements must be chosen in each command. – Three points ’,...’ indicate an optional list of items of the same type, i.e. a possible repetition of a pattern, e.g. a list of names, parameters, etc. The general command syntax as described in ”2. SYNTAX DEFINITION” on this page is defined as follows: [MAIN–CMD [CMD–SPEC]] [parameter,...] [;comment] cr [symbol–ref] ! [macro–ref] [parameter,...] ;comment cr

2.2 Key–words ______________ Only the first two or three characters (depending on the number of characters provided) of a keyword are evaluated. No checks are made on the uniqueness of a keyword if only two characters are given; in such a case the first matching keyword from MPTMON’s table is taken; however, if the full three character keyword as specified in the command description is used, ambiguity can not occur.

013 211 31515 AAAA EA 13

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Four types of keywords are distinguished: 1. Command keywords identifying a particular command. These keywords are described in ”3. COMMAND DESCRIPTION” on page 22, e.g. ACT, CE, WOR, etc. 2. Parameter keywords to specify parameters for a command. Though most commands have position defined parameters to reduce the typing effort, some commands use name defined parameters as a consequence of their complexity. 3. Synonym keywords which are used in expressions, instead of explicitly given values. These keywords are: Generally used: FALSE the internal representation of the boolean value FALSE. TRUE the internal representation of the boolean value TRUE. PTCE the network address of the PTCE in which the MPTMON Controller resides. ANY a process number to specify any process in breakpoint commands. Related to MPTMON local areas and internal variables: LWA a local work area of 2048 bytes located within the PTCE. Access to this area is direct, i.e. does not require a CE activation. It is intended to be used as a scratch buffer to hold dynamic data for macro execution (e.g. work–areas, etc) or to pass parameters between macros. IEC the MPTMON internal error code for command execution control. For the assignment of error numbers see ”APPENDIX D. Error Messages” on page 191. EVC the MPTMON event code for command execution control. For detailed information see ”3.16 Event handling commands” on page 116. MSP the MPTMON’s Stack Pointer used to access and modify local data of MPTMON. It provides access to symbol and macro directories for special operations like saving macros and symbols in memory resident tables, switching between symbol tables, etc. Its use is however restricted to very special applications (”3.18.1 Select macro table” on page 122). Related to Target dependent variables and areas: TMC the target machine code of the selected CE. Possible values are: – 0 for 8086 processors (real mode) – 1 for 80286 or 80386 processors in real mode – 2 for 80286 processors (virtual mode) – 3 for 80386 processors (virtual 16–Bit mode) 013 211 31515 AAAA EA 14

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– CBU Call buffer, an area of 32 bytes in the target processor for OSN and SSM primitive calls. MSG an area of 64 bytes in the target processor, containing the last received non MPTMON message. PID the process identity of the process on breakpoint if any. OBC the number if the OBC if an OBC is selected. MP the actual location of the S12 master pointers. ROMD the actual location of the ROM data area. IDT the actual location of the interrupt descriptor table or the interrupt vector table respectively. GDT the actual location of the global descriptor table LDT the actual location of the local descriptor table Related to MMC processing: JSQ the job sequence number of a MMC generated job in the system. RBF the pointer to a report buffer received from an ORJ FMM. This gives access to the first translated report buffer in ASCII format. The ”SCAN” command can be used for own report verification (see ”3.17.3 Scan table” on page 119). Access to this buffer is direct, i.e. does not require a CE activation. If the MMC translation is suppressed the binary report buffer is stored (see ”3.19.9 Suppress MMC translation” on page 128). RRN the report reference number of the last MMC report received. RSQ the report sequence number of an ORJ generated report received by MPTMON. 4. Register keywords as defined by ICE86 (see ref. 1). Due to the nature of MPTMON which runs in real time and not able to halt the processor, the contents of the 8086 registers changes continuously. Therefore the contents of these registers is only a snapshot of the micro processor status at that moment when a SW breakpoint is matched (see as well ”3.7.6 Display / modify registers” on page 57). The register keywords are: – Segment registers: SS, ES, DS, CS – General registers: RAX, RBX, RCX, RDX – Index registers: DI, SI – Pointer registers: BP, SP, IP – Flag register: FLA

013 211 31515 AAAA EA 15

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Some register keywords are used to hold data not related to the actual processor register contents: a. After a ”FETCH FMM” command: – CS:IP = start address of the FMM code – DS = data segment of the FMM – RAX = FCB number – FLA = FCB flag word – ES:DI = start address of the FCB entry b. After a ”FETCH SSM” command: – CS:IP = start address of the SSM code – DS = data segment of the SSM – RAX = SCB number – RCX = number of SSM procedures – ES:DI = start address of the SCB entry c. After a ”FETCH RELATION” command: – DS:SI = absolute relation address – RDX = relation size (no of bytes) – RCX = actual number of tuples present – RAX = tuple size – ES:DI = start address of the local/global directory entry – CS:IP = start address for a procedural relation d. After a ”FETCH PROCESS” command: – CS:IP = actual program address of the process. – RAX = FMM identity. – RDX = status of the process – FLA = OSN flags of the process. – DS = data segment of the FMM. – SS:SP = actual stack pointer of the process. – ES:DI = start address of the process control block (PCB).

013 211 31515 AAAA EA 16

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– e. After a ”CE xxxx: Debug Monitor Entered”: – RAX = Batch device identity – RBX = Batch file identity – RCX = network address of the CE – RDX = user parameter – FLA = flags from R_FEATURES f. After a ”TRF Trigger”: – RAX = HIGH timer word – RBX = LOW timer word – RCX = occurrence counter value g. After a ”SCAN TABLE” command: – DS:SI = address where the element was found – RCX = actual element number – RDX = relative offset where the element was found h. After a ”TI” command: – RAX = TI reply word

2.3 Identifiers ________________ Identifiers or names must start with an alphabetic character (’A’ to ’Z’) or the at–sign (’@’) followed by maximal 7 alphanumeric characters inclusive the at–sign and underscore. Identifiers or names specified with more then 8 characters are truncated without giving a warning message. Symbol references are made by a point ’.’ concatenated by a symbol name, e.g. ’.SYM_123’. Macro references (i.e. invocations) are made by a colon ’:’ concatenated by a macro name, e.g. ’:MACRO1’.

013 211 31515 AAAA EA 17

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 2.4 Operators ______________ The set of MPTMON operators is the full set of ICE86. The available operators and their priorities are: Prio Operator Effect –––– –––––––– –––––– 1 currently not used 2 SEG designates a value that is the segment of a pointer 3 OFF designates a value that is the offset of a pointer 4 : segment – offset connector to build a pointer 5 / integer devision; the remainder is lost 6 * integer multiplication; the overflow is lost 7 – binary subtraction 8 + binary addition 9 LEN repetition factor (ignored for most commands) 10 POI contents operators 11 WOR which work 12 BYT on the selected 13 POR target CE. 14 <> boolean notequal; the result is TRUE or FALSE 15 = boolean equal 16 > boolean larger 17 >= boolean larger or equal 18 < boolean less 19 <= boolean less or equal 20 AND logical AND (operands bit–wise AND’ed) 21 OR logical OR (operands bit–wise OR’ed) 22 XOR logical exclusive OR (operands bit–wise XOR’ed) The unary subtraction and addition operators are implemented as binary operators on a default operand with value 0. The contents operators POI, WOR and BYT have a function that is equivalent to the CHILL de–reference operator, i.e. they must have as operand a pointer, and they return memory contents stored at the given address (4, 2, and 1 byte resp.). The contents operator POR must have as operand an integer and it returns the contents of the given port–number as 1 byte.

013 211 31515 AAAA EA 18

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Example: The MPTMON command sequence: DEF.A=4040:6 DEF.B DEF.C .B = POI.A .C = WOR.B is equivalent to the CHILL statement set: DCL A PTR INIT:=(:6,4040:); /* in this form chill syntax error */ DCL B PTR; DCL C INT; B := A–>PTR; C := A–>INT; or the one MPTMON command: DEF.C=WOR(POI 4040:6)

NOTE: The relative priority of the SEG and OFF operators to the ’:’ operato _____ differs from ICE86. The priorities as chosen above offer some advantages in constructing new pointers from others, e.g. ’SEG.A:OFF.B’ is allowed in contrast to ICE86.

2.5 Expressions ________________ An expression is a formula that evaluates to an integer or pointer value. A boolean is considered to be an integer with the value ’0’ for the FALSE value and any other value for the TRUE value. A pointer or address is a pair of 16 bit integers. One integer is called segment and the other offset. This Manual uses the notation segment:offset to denote an address. MPTMON does not allow the direct use of an integer for memory references; the mode must be of pointer, i.e. the operator ’:’ has to be used. Expressions and comparisons on pointers are considered as unsigne ________ integer operations on the offset of the pointer. An integer is a single 16 bit signed integer and can not be considered as _______ special case of a pointer with segment value equal to 0. Unsigned integers are not supported. Expressions appear in MPTMON as command parameters to specify numeric values or boolean conditions. They are evaluated from the left to the right using a strategy of pairing operands and operators, and comparing the priority of the operator of the actual pair to the previous one to decide if an operation has to be performed or not. Parentheses can be used to group pairs of operators and operands to define own operational relations between these groups. I.e. an expression like WOR(POI.A–2*3+4/2)+64 is evaluated as follows (W, X, Y, and Z are intermediate operands):

013 211 31515 AAAA EA 19

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– WOR(POI.A–2*3+4/2)+64; ;separate in pairs WOR (POI .A– 2* 3+ 4/ 2)+ 64 ;compute 2*3 WOR (POI .A– 6+ 4/ 2)+ 64 ;compute 4/2 WOR (POI .A– 6+ 2)+ 64 ;compute .A–6 WOR (POI .W+ 2)+ 64 ;compute .W+2 WOR (POI .X)+ 64 ;compute POI.X WOR .Y+ 64 ;compute .Y+64 WOR .Z ;compute WOR.Z ;result known A few examples are given to further illustrate this concept: 1. The simplest form of an expression is a single value. The default input base is hexa–decimal. Decimal entry can be made by appending the character ’T’ to the value or by setting the input base to decimal (see ”3.12.7 Set input base” on page 99). FFFE –> –2T 10 –> 16T 10H –> 16T 0A12T –> syntax error 2. The next form shows simple arithmetics. 10 + 10T * 2 –> 36T –2 * 5 + 32T / 2 –> 6T 3. The priority of an operator may be overwritten using parentheses (10 + 10T) * 2 –> 52T 3 * (5 + 2T) / 2 –> 9T 4. Symbols may be used as well to refer to values (.SYM2 and .A are of the mode integer). .SYM2:OFF.POINTER + 3 * .A 5. Indirect references to memory locations. WOR(POI(POI 407F:6)+18) 6. Reference to strings or arrays (e.g. to write a text string located in the Local Work Area, LWA of the mode pointer). BYT LWA+.N*10 LEN 10 NOTE: You may refer to the value of an expression by embedding it betwee _____ parenthesis and prefixing it by a ’%’, i.e. %(5+6). Such a construct is replaced by a text string representing the value of the expression in an output base as set up by the command ’BAS’ (see ”3.12.6 Set output base” on page 98). If the output base is ASCII, the maximum length of the text string referred to, is 32 bytes (see the example). The use of the value replacement is only where text strings are expected by MPTMON, e.g. in MMC commands, symbol names, member names, etc. Example:

013 211 31515 AAAA EA 20

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF.A=0 BAS=T COU 16T ;define 16 symbols DEF .ABS%(.A) = .A .A=.A+1 END REM .A ;symbol .ABS13 has value 13T

Example: BYT LWA = ’EVA 0’ ;compose text in memory BAS=A ;output base is ASCII %(BYT LWA LEN 5) ;execute EVA command stored in memory

013 211 31515 AAAA EA 21

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3. COMMAND DESCRIPTION ______________________

All command descriptions have got examples, apart from their full description, to explain the syntax more clearly. Complete examples, i.e. an example test session and example macros can be found in ”APPENDIX A. Examples” on page 147. An alphabetical index, which lists all commands –over 100– defined in this chapter, is provided for quick reference at the end of this document.

3.1 Test session commands __________________________ An MPTMON test session can be started in various ways. Basically, upon the initialisation of the PTCE control element, processes are created to handle one dedicated terminal and one terminal connected to a host computer. One process is reserved for a test session started on a VDU. In some special applications the standard PTCE HW–configuration is not provided but instead, one or more SPARE control elements equipped with a TCPx–processor or MCUx–processor board are foreseen to execute the PTCE Software package. Such a configuration could be chosen for example, for cost reduction purposes. If MPTMON is loaded in such a SPARE configuration, it will create a process to handle a terminal connected via the asynchronous serial port of these processor boards. Some keys have special functions assigned during a test session (though may not be supported on all terminal types). They are: 1. CR–key: ”input termination”. 2. ESC–key: ”abort execution” 3. BREAK–key: ”abort execution” 4. CNTL–X: ”abort wait state” 5. CNTL–S: ”output hold” 6. CNTL–Q: ”output continue” 7. CNTL–R: ”line recall backward” 8. CNTL–F: ”line recall forward” 9. ENTER: ”screen transfer” During a test session, a lot of results are produced, which may be needed later e.g. for documentation, regression test or verification purposes. Running a test session at a VDU all data is lost, unless there is a hardcopy facility where you can print screen images. In order to overcome these shortcomings a list file –often called log file– can be opened during a session, and all data, i.e. inputs and outputs are written to it. Such a file shows clearly what had been input and what were the responses or results. Logging is supported by some additional commands, like display of the current date and time to obtain a comprehensive test documentation.

013 211 31515 AAAA EA 22

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– The following commands relate to session handling and are outlined in the next sections: – Start a session. – Terminate a session. – Turn list on – Turn list off – Display current date and time – Change VDU baud rate

3.1.1 Start a Session ______________________

The start of a test session differs for dedicated terminals from the dynamically allocated System terminal. After the dedicated terminal initialisation, MPTMON displays automatically its sign–on header, including its version and PCS, and prompts for the ”debug” password. The correctly entered password enables you to execute any valid command, like target processor activation or memory commands to run a test session. If no password has been entered, i.e. only a carriage return, or an invalid one, all commands requiring CE access are disabled preventing unauthorized accesses to CE’s. If the password has been mistyped by accident it can be reentered using the SET AUT run time option, as explained in ”3.19.1 Command authorizations” on page 124. The logon procedure to start a test session on a dynamically allocated System terminal differs from the dedicated VDU’s as the VDU must be explicitely seized from the S12 IOS in contrast to the dedicated one’s. An MPTMON ORJ has been defined to start–up such a test session. The ORJ has to be entered as follows: START–MPTMON; Successful/unsuccessful start–up is confirmed by a MPTMON Session Report. Thus, if the start–up succeeded, MPTMON displays its sign–on header on the allocated System VDU and prompts for the first command; i.e. MPTMON doesn’t prompt for a password, since a password is already supplied for the ORJ. See for further details the section ”4. Test Configurations” on page 134.

3.1.2 Terminate a Session __________________________ Syntax: TER [SES]

013 211 31515 AAAA EA 23

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– After test session completion you should enter the TERMINATE command, to releases all resources allocated to this session. All active CE’s are deactivated, the list file closed, allocated devices released, user buffers returned to the OSN and the process handling the session terminates. If the command is executed at one of the dedicated ports (connected to a terminal or host computer), the process is recreated to handle a new session; i.e. the MPTMON sign–on header is displayed and MPTMON prompts for the session password, i.e. the TERMINATE command performs implicitely a logon request to start a new session.

3.1.3 List On ______________ Syntax: LIS device [,file] [,EXT] device The IOS device number on which the list file shall be allocated. file The IOS file identity specifying the list file. EXT The keyword ”EXT” can be used to indicate that a possibly existing list file should be extended with new information without overwriting existing information of a previous test session. Opens a list file on the specified device. If no file parameter is given the logical file identity 971T is used by MPTMON as a default. Otherwise the given file must have a record size less than 82T (one line on the VDU screen). If such a file is already opened a warning message is generated and the original list file is kept open (no new file opened). All subsequent input and output is written to the list file as well as to the VDU screen. List files can be allocated on any device type. But it is recommended to use either disk or tape to not slow down your test session. If a hardcopy is required it can be simply obtained by using the ORJ COPY–FILE to copy the list file at a later point in time to a printer. The old list file is deleted per default if the ”EXT” keyword is omitted. Note that this keyword makes only sense when the list file is defined on a disk. List files written on printers or tape files can not be deleted. Example: LIS ON 24T ;list e.g. on printer LIS ON 1,EXT ;list e.g. on disk and append LIS ON 1,950T ;list e.g. on disk, but file 950T

3.1.4 List Off _______________ Syntax: LIS OFF

013 211 31515 AAAA EA 24

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Closes a list file. If such a file is not opened the command is ignored. Logging of input and output is terminated upon issue of this command. Example: LIS OFF

3.1.5 Display Time ___________________ Syntax: TIM [DIS] Displays the current PTCE SW date and time; i.e. MPTMON obtains it from the OSN using the primitive GET_REAL_TIME. The actual layout is found in ”APPENDIX A. Examples” on page 147. This command offers the facility to supply list files with the actual test session execution date and time. Example: TIME

3.1.6 Change VDU baud rate ___________________________ Syntax: BDR rate rate Expression which calculates to a VDU baud rate. Changes the MPTMON VDU baud rate to the specified value. This is basically only necessary, if you would like to print the contents of the VDU screen in parallel on a slow printer, connected serially to the VDU interfacing line. You can chose only baud rates which are supported by the connected VDU. The baudrate switch at the VDU has to be turned within 2 seconds. Example: BDR 300T BDR 1200T

013 211 31515 AAAA EA 25

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.2 Control element commands _____________________________ The features described in this section are an extension of the ICE86 syntax required to handle a multi processor environment. Every 8086, 80286 or 80386 processor of a control element (CE) in a System 12 exchange may be the target of test commands, even the PTCE itself. The concept of MPTMON requires that a Slave (SLV) is part of the SW package of every CE. The commands described in this section allow you to perform the following functions: – Activate a CE – Deactivate a CE – Select an OBC – Deactivate an OBC – Display the status of one or all CE’s and OBC’s activated – Initialise Slave – Initialise OBC It is assumed that the user testing SW in an OBC (on–board controller) environment, is familiar with the fundamental functional differences between a normal CE using OSNB, and the OBC using OSNC. Some of the more obvious being that there are no user controlled paths on the OBC, no overlay FMM’S are possible, and that messages can only be simply BASIC or DIRECTED with no further attributes. Testing may require not only the observation of a CE but also to perform actions onto it, which require a stronger impact than just to read and write to memory or to trace messages. MPTMON has a set of commands which take into account this consideration. MPTMON is able to: – Restart a Control Element – Boot a Control Element – Load a CE NOTE: All these commands rely on the fact that a communication link is or ca _____ be established to a CE. Therefore it is not possible to get access to a CE for restart or boot purposes in case of malfunctioning if no communication can be established.

3.2.1 Activate Control Element _______________________________ Syntax: ACT network–address network–address The network address in the form ’ZYXW’. The keyword PTCE can be used to specify symbolically the network address of 013 211 31515 AAAA EA 26

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– the CE where the MPTMON Controller executes. The numbering scheme includes the addresses of RSU’s connected to the host exchange. This command establishes the communication interface to a CE via a UCP. If the communication is set up successfully, the CE is selected as the target for all subsequent commands. In other words, all commands requiring a CE access like display memory, are routed to the last activated CE. An entry is made in the active CE directory for later reference, or display of status information. All internal tables of the Slave (like breakpoint tables and trace buffers) are initialized if the communication is set up for the first time, otherwise they are left unchanged (MPTMON relies to a certain extent, on its own RW data being not corrupted after a process termination or processor restart to simplify the operator interface and to allow access to trace and breakpoint information after a restart). The specified CE will only be selected as target CE if the CE is already active, i.e. the existing UCP is used and all internal tables left unchanged. The most common error in executing the ACT command is that the communication path could not be established, because the target processor is not running or the CE is not equipped. A time supervision of 30 seconds is applied to supervise the command execution and an error message is issued in case that the timer expires. CAUTION: When the downloading of a Slave from the P+L disk (in case th ________ Slave is defined as an overlay FMM for a particular processor) takes more than the command supervision time of 30 seconds malfunctioning occurs. A ”SLAVE BUSY” error message is given when you try to activate the CE again). The INI SLV command will clean up this situation (see ”3.2.6 Initialise Slave” on page 29). Example: ACT PTCE ;local CE ACT 25 ;target CE with absolute specified address ACT WOR.NETW_TAB ;target CE with address read out ;of the memory of another selected CE

3.2.2 Deactivate Control Element _________________________________ Syntax: DAC [network–address [,continue–trace]] network–address The network address in the form ’ZYXW’. continue–trace A boolean value to continue tracing or not (default is FALSE) This command deactivates a CE as target for the next commands entered and removes all breakpoints, if any present. If a message trace was active and 013 211 31515 AAAA EA 27

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– the continue–trace is set to FALSE, tracing is stopped. After a successful deactivation the entry in the active CE directory is cleared and the UCP, used to the specified CE returned. The keyword ”ALL” can be used instead of a network–address to deactivate all CEs using one command. Example: DAC ;Currently selected CE DAC 25 ;target CE with absolute specified address DAC 1C,TRUE ;continue tracing after deactivation DAC ALL ;all active CEs

3.2.3 Select On–Board Controller _________________________________ Syntax: OBC [network–address:] OBC–number network–address The network address in the form ’ZYXW’. OBC–number The OBC number in the range from 0 to 255. Selects one of the OBC’s connected to the specified or currently activated CE as the target of all subsequent given MPTMON commands until another OBC is selected, or the OBC is deactivated. Note that some test commands are not supported in an OBC environment, like: Fetch Relation, Call commands (except CAL OBC). Example: ACT 25 ;activate target CE TRC SSM 223T ;set trace condition in target CE OBC 5 ;select target OBC 5 at network address 0025 WOR ROMD ;display memory of OBC OBC 26:1F ;select target OBC 1F at network address 0026

3.2.4 Deactivate OBC–connection ________________________________ Syntax: DAC OBC Deactivates the currently selected OBC–processor as target and re–activate the controlling CE. The standard deactivate command ”DAC” tears down the whole connection to the CE. A possibly selected OBC is at the same time deactivated. Example:

013 211 31515 AAAA EA 28

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– ACT 25 ;activate target ce OBC 5 ;select target OBC 5 at network address 0025 WOR ROMD LEN 10 ;display memory of OBC DAC OBC ;deactivate OBC WOR ROMD LEN 10 ;display from CE DAC ;deactivate CE

3.2.5 Display CE directory ___________________________ Syntax: CE [DIR] [network–address] network–address The network address in the form ’ZYXW’. All active CE’s if this parameter is omitted. This command displays information of one or all active CE’s and OBC’s from MPTMON’s directory. This information is formatted into seven columns: 1. the CE which is selected by means of a ’–’ indication, 2. the CE network address (ADDR), 3. the CE logical processor identity (LCE) or ’OBC’, 4. the CE virtual path identity (PROC) or OBC number, 5. the CE status which can be either: active, tracing, on breakpoint or debug, 6. the PID of a process which is on a breakpoint, 7. the PCS of the MPTMON–Slave FMM executing. Example: CE ;display all activated CE’s CE PTCE

3.2.6 Initialise Slave _______________________ Syntax: INI [SLV] network–address network–address The network address in the form ’ZYXW’. This command should only be used if the ACT command results in a ”SLAVE BUSY” message. This indicates that the MPTMON Slave is already activated by another tester or due to a timeout of a previous ACT command. To gain control over this Slave again, you are prompted for a password to make sure that you do not accidently destroy a test session of another tester. If the

013 211 31515 AAAA EA 29

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– correct password is given, the Slave initialises itself again and performs all actions as described in the ACT command. Example: >ACT 224 ;activate slave on address 224 *** ERROR: SLAVE BUSY ;MPTMON’S error message >INI SLV 224 ;initialise slave again PASSWORD: ;enter password (CARE) > ;enter next command

3.2.7 Initialise OBC _____________________ Syntax: INI OBC [network–address:] OBC–number network–address The network address in the form ’ZYXW’. OBC–number The OBC number in the range from 0 to 255. This command should only be used if the OBC command results in a ”SLAVE BUSY” message. This indicates that the MPTMON Relay is already activated by another tester or due to a timeout of a previous ACT command. To gain control over this Relay again, you are prompted for a password to make sure that you do not accidently destroy a test session of another tester. If the correct password is given, the Relay initialises itself again and performs all actions as described in the OBC command.

3.2.8 Restart control element ______________________________ Syntax: CE RES Restarts a CE using an OSN SW interrupt supplying restart level CE_RESTART. As the communication path will be released during a control element restart, you have to activate the CE again by means of the ACT command, if further communication is required.

3.2.9 Boot control element ___________________________ Syntax: CE BOO [fast–test] fast–test A boolean value to perform a fast test of the processor board or not (default is FALSE = no fast test) Causes the CE to perform an autonomous bootstrap request to the PLCE, which subsequently will cause a Control Element reload.

013 211 31515 AAAA EA 30

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.2.10 Load control element ____________________________ Syntax: CE LOA network–address, vp–identity [,RODEM–feature] MPTMON is able to load GLSC format files (GLS, DLS, PLS files) directly into a target processor’s memory via the digital network. These binary files must be sent to MPTMON via the asynchronous communication line or via the serial interface port using a special protocol. Consequently this command is only supported if the line is connected to a host computer (VAX or PC) running a MPTMON–interface program. The syntax of this interface program defines the user interface for loading (”4.1.3.1 HILTI” on page 136). A password protection is applied on this command to prevent that it is executed interactively by a tester working on a normal directly connected VDU. While transferring the binary records of 2044 bytes to MPTMON, the complete PTCE is put under direct control of the MPTMON–loader to achieve a transmission rate of 9600 Baud for the load process instead of the normal 1200 Baud rate for normal ASCII operation. No other functions will run in the PTCE during loading, as the OSN is completely disabled. The OSN only gets control to send the load packets over the network, and afterwards returns to normal when the load process is finished or aborted. The main application of this command is the loading of ”hot PLS’s” in a target processor for integration testing. It can however be used as well for module testing to load a complete processor in small test configurations not equipped with a PLCE processor. The PTCE itself can of course not be loaded with this command. Other design–center dependent tools should be used instead (e.g. Piggy Back boards, GESTOM, etc.). For an 80386 target CE it is also possible to stop after loading. Then the ROM Debug Monitor (RODEM) may be activated to check or modify the memory contents of the CE. Afterwards a normal ”GO” commands exits the RODEM and starts software execution. NOTE: It is not possible to load a simplex running PLCE as it will directl _____ boot from its own disk, instead of waiting being loaded via the network.

013 211 31515 AAAA EA 31

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.3 Memory display and modify commands _______________________________________ The syntax of commands discussed hereafter uses a subset of the corresponding ICE86 command syntax. Eight commands are provided: – Display memory words – Display memory bytes – Display byte port – Modify memory words – Modify memory bytes – Modify byte port – Disassemble memory contents – Patch memory contents

3.3.1 Display memory words ___________________________ Syntax: WOR memory–address [LEN no–words] memory–address The address from which the first word, i.e. the contents of two adjacent bytes in memory, must be displayed. The most significant byte displayed corresponds with the high address of the byte pair. no–words The number of adjacent words to be displayed. The display is formatted in groups of 8 words together with their start address. A check is made if the addressed memory is equipped and an error message given if this check fails. NOTE: The command interface to the Slave allows only the passing of 8 word _____ at a time. Consequently for each line a CE access is made. Example: WOR ROMD ;the network address of the CE ;selected WOR (POI.DLS+25H) ;the contents of the address stored ;in .DLS+25 is displayed WOR SS:SP LEN 20 ;the stack of a process which is ;stopped on a breakpoint WOR MSG+C LEN 2 ;source PID of last received message ;using the keyword ’MSG’ WOR (POI(POI.A+26)) ;two levels of indirection

013 211 31515 AAAA EA 32

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.3.2 Display memory bytes ___________________________ Syntax: BYT memory–address [LEN no–bytes] memory–address The address of the first byte to be displayed. no–bytes The number of adjacent bytes to be displayed. The display is formatted in groups of 16 bytes together with their start address. Refer to the display word command for the checks made and notes. Example: BYT SS:BP+4 LEN 20 ;local data of a process which is ;stopped on a breakpoint BYT .DLS+2 ;a single byte value is displayed

3.3.3 Display byte port ________________________ Syntax: POR port–number port–number An integer value in the range of 0 to 65535. A port contents may change continuously in real time, so a snapshot is taken and displayed as a byte value. Due to the real time environment in which MPTMON is running, it may not be possible to evaluate a port contents consistently. Example: POR 16 ;programmable interval timer POR 0 ;processor control register POR 22 ;programmable interrupt controller

3.3.4 Modify memory words __________________________ Syntax: WOR memory–address = expression [,...] memory–address The address of the first word to be modified. expression An expression which can be evaluated into an integer or pointer value. A pointer is treated as 2 integer parameters, first the offset followed by the segment of the parameter. Maximal 16 words can be modified with one command. A repetition factor using the keyword LEN may be used as well to define a set of values in one 013 211 31515 AAAA EA 33

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– expression; the LEN keyword is however, only valid in conjunction with a contents operator. Checks are made if the memory segment to be modified is physically existing and write–protected. In the latter case, the sum–check of the write–protected data (as defined by the write–protection map in the DLS) will be updated to prevent an error call after a CE restart. Example: WOR LWA = WOR .FCB LEN 16T ;copy 16 words to ;the local work area WOR .DLS+2 = 34,22,90 ;modify three words WOR .DLS = 90 LEN 8 ;syntax error WOR .A = WOR(POI.B+7)+59 ;copy one word WOR .A = WOR LWA LEN 8 ;copy 8 words from the LWA ;to the target CE WOR LWA = 0,4040 ;this is identical to WOR LWA = 4040:0 ;or DEF .A = 4040:0 WOR LWA = .A ;or WOR LWA = OFF(.A),SEG(.A) ;or

3.3.5 Modify memory bytes __________________________ Syntax: BYT memory–address = int–expr [,...] memory–address The address of the first byte to be modified. int–expr An expression which can be evaluated into an integer value. If the integer value exceeds 255T, only the low byte of the integer is taken and no warning message issued. Maximal 16 bytes can be modified with one command. A repetition factor using the keyword LEN may be used as well to define a set of values in one expression; the LEN keyword is, however, only valid in conjunction with a contents operator. Refer to the description of the modify word command for more details. Example: BYT LWA=’ABCDEFG’ ;load a text string in the ;local work area BYT.A=WOR.B+7 ;copy the low byte from ;location .B+7 BYT.A=BYT.B LEN 8 ;copy 8 bytes BYT.DLS+2=34,22,90 LEN 5 ;syntax error

013 211 31515 AAAA EA 34

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.3.6 Modify byte port _______________________ Syntax: POR port–number = int–expr port–number An integer value in the range of 0 to 65535. int–expr An expression which can be evaluated into an integer value. If the integer value exceeds 255T, only the low byte of the integer is taken and no warning message issued. Only 1 byte port can be modified at a time. The operator LEN is not supported. Example: POR 16 = 30 ;disable sanity timer POR 0 = 1 ;reset error flags POR 22 = FF ;disable interrupts

3.3.7 Disassemble code _______________________ Syntax: ASM code–address [LEN no–bytes] code–address The address from which the first instruction shall be displayed. no–bytes The number of adjacent bytes to be disassembled. MPTMON’s 8086/80386 disassembler displays memory contents in a formatted manner and assists you to plant breakpoints on instruction boundaries or cross–checking memory contents with listings. It is advisable to define the start address on an instruction boundary, otherwise the first instructions displayed are wrong until the disassembler is synchronized with the actual instructions. The display is formatted into three columns with one header line. 1. the first column provides either the absolute address, or a symbol and a relative offset, to ease the referencing to a code listing. 2. the second column has the operation code of the instruction using mnemonics as specified by ITT’s SRASM–syntax. 3. the third column provides the operand of the instruction using the ITT’s SRASM–syntax as well. Jump instructions have absolute instead of relative addresses to the instruction pointer to ease the tracing of program flow. Example:

013 211 31515 AAAA EA 35

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– ASM .FMM+17 ;disassemble one instruction ASM .VDU+5286 LEN 1K ;ASM 1024 bytes of code ASM CS:IP ;ASM the next instruction to be ;executed by a process on BRP

3.3.8 Patch code _________________ Syntax: PAT code–address code–address The start address of the instruction which should be patched. MPTMON’s 8086/80286 line assembler allows temporary code correction using assembler instructions as specified by ITT’s SRASM–syntax. After calling the line assembler MPTMON starts prompting with the code address in front of the larger sign ’>’. Then the tester may enter the required assembler instruction. The syntax is the same as used by the disassembler with the same limitations (see NOTE). If the syntax of the given instruction is not correct, MPTMON prompts for correction. Otherwise the translated bytes are written directly into the memory of the selected target CE and MPTMON prompts for the next assembler instruction using the new calculated code address. To exit the line assembler the tester just has to type a CR as next instruction. In batch files the backslash can be used to exit the line assembler. NOTE: Jump instructions and calls have absolute instead of relativ _____ addresses to the instruction pointer. Only simple expressions, like symbol + offset, are allowed as argument, but you may refer to a keyword (e.g. CBU) or a complex expression by embedding it between parenthesis and prefixing it by a ’%’. The line assembler can not be called from a macro. CAUTION: MPTMON transfers the HEX code to the target CE instruction b ________ instruction. So the tester has to be very careful and secure that the affected code is not being executed during modification. Example: >PAT .SUT+1078 .SUT+1078 >MOV AX,(BP)–2 .SUT+107B >CMP AX,#4711 .SUT+107F >JNE .SUT+1084 .SUT+1081 > END OF ASSEMBLER

013 211 31515 AAAA EA 36

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.4 Symbol commands ____________________ Symbols may be used to refer to fixed values, fixed addresses or variables. This MPTMON feature assist you in recalling or referring to certain values symbolically without knowing them explicitly. A symbolic reference is made by a point concatenated with a symbol name as defined in ”2.3 Identifiers” on page 17. The commands available to handle symbols are: – Define a symbol – Add a symbol – Change a symbol value – Remove one or more symbols – Display symbols and their values. MPTMON’s implementation of the symbol table uses a kind of symbol stack, where every symbol added is put on the stack as the last symbol, and any symbol reference is resolved by searching the symbol stack from the top to the first matching symbol. On macro entry the number of symbols defined is saved and on exit in most cases restored in order to remove all symbols used locally within that macro. This information may help you to understand the logic of some command within this chapter.

3.4.1 Define symbol ____________________ Syntax: DEF .name[=expression] [,...] name Unique name of the symbol to be defined, used for later reference. expression An expression that evaluates to an integer or pointer value. If omitted, the null–value is assumed. Defines one or more symbols and assign them an integer or pointer value. A warning message is displayed if the symbol was already defined; the new value as specified by the command is then assigned. A special command exists to define symbols within macros (refer to ”3.4.2 Add symbol” on page 38). It is strongly recommended to use this command instead of ”DEF” within macros. Example: DEF .LOOPI = 1 ;defines a temp. symbol DEF .MPTMON = 867B:0 ;a GSM start address DEF .VN = POI(POI 407F:6)+24 ;a table pointer, etc. DEF .A,.B,.C=5,.D,.E ;a set of symbols

013 211 31515 AAAA EA 37

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.4.2 Add symbol _________________ Syntax: ADD .name[=expression] [,...] name Unique name of the symbol to be defined, used for later reference. expression An expression that evaluates to an integer or pointer value. If omitted, the null–value is assumed. Adds one or more symbols and assign them an integer or pointer value. No checks are made if the symbol exists already. Consequently, the same symbol can be defined a number of times. The command should be used to define symbols within a macro, when all symbols of that macro are not required externally; i.e. when the lifetime and scope of symbols defined within a macro is limited to that macro. The ”ADD” command has some major advantages over the define symbol ”DEF” command: 1. It increases macro processing speed, as no checks are performed if the symbol exists already or not. 2. If a symbol with the same name exists already, it is not overwritten. 3. Symbols which are added within a macro are automatically removed on exit, return or abortion of that macro. 4. The remove symbol ”REM” command is not required anymore within macros to remove local macro symbols. Example: ADD.LOOPI=0,.VN = POI(POI 407F:6)+24 ;a table pointer, etc. ADD.A,.B,.C=5,.D,.E ;a set of local symbols

NOTE: All symbols defined within a macro with ”DEF” are remove _____ automatically if at least one is added with ”ADD” within that macro. I.e. the number of symbols on exit, return or abortion is always restored if at least one ”ADD” command was executed.

3.4.3 Modify symbol value __________________________ Syntax: [LET] .symbol–name = expression symbol–name Unique name of the symbol whose value is to be changed. expression An expression that evaluates to an integer or pointer value. Modifies the associated value of a previously defined symbol. The new value may be of another mode as the current one and may as well refer to itself. 013 211 31515 AAAA EA 38

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Example: .SYM = 6 ;set initial value .SYM = .SYM + 1 ;increase loop count LET.A = WOR(SEG.VDU_FH:(WOR.FMM+24*5T))+2592

3.4.4 Remove symbol ____________________ Syntax: REM [.name [,...]] name Unique name of the symbol which is to be removed from MPTMON’s symbol stack. Removes one or more global symbols from the symbol stack. If no name is entered, all symbols at the current level are removed. This means that all symbols present are removed if the command is given at the interactive level –which is the highest level–, but within a macro only those symbols which are defined within that macro and any macro called by that macro. Example: REM .I,.J,.L ;remove specified symbols REM ;remove all symbols at the current level

NOTE: Symbols added to the stack with the ”ADD” command, don’t have to b _____ removed, as the stack–pointer (number of symbols defined) is automatically restored when a macro returns (refer to ”3.4.2 Add symbol” on page 38).

3.4.5 Display symbol _____________________ Syntax: .symbol–name ! SYM [.symbol–name,...] symbol–name Unique name of the symbol which assigned value is to be displayed. Displays one or more symbols from the symbol stack and their assigned values. If only the command keyword SYM is entered, all symbols are displayed. Example: SYM ;display all symbols SYM .VP,.VN ;or a subset .MPTMON ;or a single symbol

013 211 31515 AAAA EA 39

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.5 Macro commands ___________________ The macro features described in this chapter enhance the operation of the MPTMON by extending the power of the simple MPTMON commands. A macro is a possibly parameterized block of commands referenced by a name as defined in ”2.3 Identifiers” on page 17. When a block of commands is defined as a macro, it is stored within the MPTMON memory so that it can be executed more than once without having to enter the commands each time. The macro commands described in this chapter allow you to perform the following functions: – Define a macro – Call a macro (from memory or library) – Remove one or more macros – Display the text of any macro – Display the names of all macros currently defined – Return from a macro – Edit a macro Some commands related to macro handling are not described in this chapter (see ”3.18 Resident macro tables” on page 122) as they serve a special application of MPTMON to implement user defined Macro Languages. Formal and Actual Parameters ____________________________ A formal parameter marks a place in an MPTMON command where variable text can be entered in when the macro gets called. It represents a text string of maximum 80 characters, containing any valid character. A macro definition can contain up to 10 formal parameters. A formal parameter has the form: %n where n is a decimal digit in the range from 0 to 9. Formal parameters can appear in a macro body in any order, and each one can appear any number of times. However, one or more parameters can be omitted from the sequence; the effect of omitting a formal parameter is to ignore the actual parameter in the call that corresponds to the omitted formal parameter. A macro call can contain as many actual parameters as desired. Actual parameters are entered as a list, i.e. separated by commas. The first actual parameter in the list is substituted at all points where %0 appears in the macro body. The second parameter substitutes for %1, and so on. Two extra parameters are set up to support macro–parameter evaluation: %N which is replaced by the number of actual parameters given with the macro call. %L which is replaced by the number of characters of the first actual parameter, i.e. the length of this parameter.

013 211 31515 AAAA EA 40

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– An actual parameter can have a ’null’ value, causing MPTMON to substitute nothing for the formal parameter to which it corresponds. You can pass a null parameter to a macro in two ways: – Enter no actual parameter between consecutive commas. – Omit one or more parameters from the end of the list. If too few actual parameters are entered, MPTMON supplies null values for the remaining formal parameters. If too many actual parameters are entered, the extra actual parameters are ignored. If any actual parameter contains a comma the entire parameter must be enclosed in single quotes to mark it as a single actual parameter. If an actual parameter is a text string (e.g. for a WRITE command) it must be enclosed in double single quotes. Inquiry Parameters __________________ An inquiry parameter marks a place in an MPTMON command where variable text can be entered interactively after a special prompt is presented to the operator. It represents a text string of maximum 80 characters. A macro definition can contain as many inquiry parameters as desired, though it is strongly recommended to write an explanatory prompt string, before the inquiry parameter is executed, to inform the operator what kind of information should be entered. The inquiry parameter has the form: %Q where Q stands for Query Inquiry parameters can appear in a macro body at any place. The actual parameters are not given in the parameter list when the macro is called, but interactively prompted when the command comprising the inquiry parameter is parsed. Expression Parameters _____________________ An expression parameter is replaced by a text string representing the value of the expression in a output base as set up by the command ”BASE”. The expression parameter has the form: %(expr) where ”expr” stands for any evaluatable MPTMON expression, for example: %(WOR.MSP+15A8) is replaced by ”0112” if the memory contents was 0112H. This type of parameter is mainly used in MMC commands to generate text strings in a command line to be sent to the MMC dialogue translator. NOTE: All macros kept in memory, i.e. not saved in a table, library or file _____ are lost if a PTCE restart occurs due to any reason whatsoever. Consequently these macros have to be reloaded or redefined after a PTCE restart.

3.5.1 Define macro ___________________ Syntax: DEF MAC macro–name [(formal–parameter,...)] 013 211 31515 AAAA EA 41

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– macro–name Unique name of the macro to be defined, used for later reference purposes. formal–parameter Text string naming each formal parameter. The formal parameter list is only considered as comment by MPTMON, as formal parameters are identified by %n, where n is the parameter number. Defines a macro, specifying the macro name, the command block (macro body) i.e. the following commands, and any formal parameters (points where text can be filled in at the time of the macro invocation). The macro definition is terminated using the EM command. NOTE: A macro definition may not appear within a compound command or anothe _____ macro definition. The macro body can include any command except another DEF MAC command. Example: DEF MACRO LCE_ID (network–address) ACT %0 WRI ’LCE_ID OF NA ’, %0, WOR .DLS+42 EM DEF MAC TEST WRI ’ENTER CE NETWORK ADDRESS –––––’,& ACT %Q WRI ’NETWORK ADDRESS IS = ’,WOR ROMD DAC EM

3.5.2 End macro definition ___________________________ Syntax: EM Defines the end of a macro body, i.e. it indicates the macro end. When the macro is being defined, the macro is put into the macro directory, otherwise when it executes, it returns to the calling level.

3.5.3 Call macro _________________ Syntax: :macro–name [actual–parameter–list] Fetches a macro definition from MPTMON’s directory or (if not found there) from a selected library and execute it. To call a macro, enter the macro name preceded by a colon ’:’. Macro definitions can include calls to other macros, but a macro shall not invoke itself recursively. Any macros called from within a macro must have been defined previously. Macro calls can be nested, i.e. one macro calls 013 211 31515 AAAA EA 42

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– another, which calls another, and so on. The level of nesting is limited only by the amount of MPTMON’s process stack size required to ’stack’ the macro calls and compound commands. When a macro is called the following actions will occur: – The text of each actual parameter in the call is substituted for the corresponding formal parameter in a command line. – Command lines get executed if the command is valid as expanded. – An inquiry parameter, if present is prompted. – The macro ends. Control returns either to the VDU console with a prompt character or to a previous calling macro in case of a nested call. Example: :DEVMAINT ALL,1,230,’2,5,7’ :LCB 232,’’ATCE’’

3.5.4 Return from a macro __________________________ Syntax: RET MAC This command provides a user controlled return from the currently executing macro to the calling level disregarding any compound command nesting level. All local symbols defined within the macro are removed. Example: RET MAC

3.5.5 Abort macro execution ____________________________ Syntax: ABO MAC The ABORT command provides an immediate, unstructured, unconditional exit from any level of nested macro execution, irrespective of the status of any command processing. It returns back to the outermost level, i.e. the interactive mode of operation and has consequently the same effect as pressing the escape key. All local symbols defined within the macro(s) being executed are removed. Example: IF IEC = 23 ABO MAC END 013 211 31515 AAAA EA 43

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.5.6 Remove a macro _____________________ Syntax: REM MAC [macro–name [, macro–name]...] macro–name Name of the macro to be removed. Removes one or more macros from the macro directory. If no macro–name is entered all macros are removed. Example: REM MAC PCB, FCB

3.5.7 Display a macro definition _________________________________ Syntax: MAC [macro–name,...] macro–name Name of the macro to be displayed. Displays one or more macros from MPTMON’s directory or (if not found there) from a selected library. If no macro–name is entered all macros from the local MPTMON directory are displayed. A hardcopy of a macro is printed when the listing option is set before this command is given (see ”3.1.3 List On” on page 24). Example: MAC LCE, CONVERT

3.5.8 Display macro directory ______________________________ Syntax: DIR [MAC] Displays the names of all macros in the directory. Example: DIR MAC

3.5.9 Edit a macro definition ______________________________ Syntax: EDI macro–name [=template] 013 211 31515 AAAA EA 44

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– The MPTMON macro editor makes use of the local VDU edit capabilities. It switches the VDU into the buffered operation mode without any operator intervention. During edit all the edit keys can be used to edit the VDU screen contents (see as well ref. 3 and 4 for further details). The whole edit is done locally within the VDU’s screen memory (no character transfers are done to MPTMON while editing). After typing the EDIT command MPTMON clears the VDU screen. If the specified macro is already defined the whole macro definition is copied to the VDU; otherwise another macro definition can optionally be used as a template for the new one. The latter option allows for to copy and rename existing macros. If you have finished your edit press the ENTER or SEND key to get the edited macro definition transferred and saved into the MPTMON on–line macro directory. Additionally the VDU is reconfigured to its default setting. The EDIT command is quit by pressing the BREAK key to terminate edit without saving the screen contents. The screen contents is not saved either when the ”$” character is put on the home position of the screen. The detailed operation of this command depends on the VDU–type used; refer therefore to the section ”4.2 Terminal Types” on page 140 for some peculiarities. NOTE: The description of this command does not apply for a VAX terminal _____ Instead the following sequence is invoked by MPTMON automatically to reduce your typing effort (it assumes that the original macro is kept in the current VAX directory using the file extension .MAC): 1. REM MAC <macro–name> ;remove the macro from memory 2. #EDI <macro–name>.MAC ;invoke VAX editor 3. #BAT <macro–name>.MAC ;include VAX file Example: EDIT VPT ;edit existing or new macro EDI LCETAB=VIRTAB ;use VIRTAB as skeleton for LCETAB

013 211 31515 AAAA EA 45

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.6 Compound commands ______________________ Compound commands enable you to build control structures around zero or more commands. These structures may describe conditional and repetitive execution of commands. Compound commands can be nested as required and nesting is only limited by the available size of MPTMON’s internal work buffer (see ”4.3 Dimensioning” on page 141). To analyse the control structure, MPTMON stores the complete text of a single or nested compound command in a work buffer. If this buffer overflows, the command is aborted immediately. An exit out of a compound command can be programmed or be forced manually by pressing the ESC key. Though macro calls are as well a kind of compound command, they are not considered as such and described therefore in a separate chapter. The commands discussed here are the: – IF command – COUNT command – REPEAT command. – EXIT command.

3.6.1 IF command _________________ Syntax: IF bool–expr cr [command cr]... [ORIF bool–expr cr]... [command cr]... [ELSE cr] [command cr]... END bool–expr An expression that evaluates to a TRUE or FALSE value. The operands of the boolean operator may be text strings, though only the first four characters are evaluated. command A number of commands. All commands defined in MPTMON’s syntax are allowed except DEF MAC. cr Carriage return, i.e. each clause or command must start on a new line. Within macros, the back–slash may be used as a command separator instead of a carriage return to limit the macro body size. The IF clause permits conditional execution of command sequences. The IF and END clause are obligatory; the OR and ELSE clauses are optional. The command can comprise as many OR clauses as required. MPTMON analyses every command line to check the control structure, but executes only the commands comprised in the first clause that evaluates to TRUE. 013 211 31515 AAAA EA 46

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– If no IF or OR clause is found to be true and the ELSE clause is present, the commands following the ELSE clause are executed. Example: IF .VALUE >= WOR.PTR+5 WRI ’LOAD BID RECEIVED’ OR .SYMBOL1 = .SYMBOL2 WOR.PTR+5 = 203T OR FALSE ;this clause is never executed OR ’%0’ = ’YES’ ;macro parameter was the text ’YES’ ELSE WRI WOR.A ,& WRI ’CONCATENATE’ END ; ;next example shows the use of the back–slash ;as separator in macros ; IF.A<0 \WRI ’INVALID VALUE’ OR.A=1 \WRI ’SYMBOL A HAS VALUE 1’ OR.A>8 \WRI ’VALUE OUT OF RANGE’ ELSE \BAS=A\WRI (BYT LWA+.A*8) LEN 8\BAS=H END ; IF IEC>0 ;check internal error code EXIT ;exit if error occurred END

3.6.2 COUNT command ____________________ Syntax: COUNT int–expr cr [command cr]... [UNTIL bool–expr cr]... [command cr]... [WHILE bool–expr cr]... [command cr]... END int–expr An expression that evaluates to an integer value. UNTIL An exit clause which causes a termination of the COUNT loop when the boolean expression evaluates to TRUE. WHILE An exit clause which causes a termination of the COUNT loop when the boolean expression evaluates to FALSE. command Any number of commands. All commands defined in MPTMON’s syntax are allowed except DEF MAC.

013 211 31515 AAAA EA 47

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– cr Carriage return, i.e. each clause or command must start on a new line. Within macros, the back–slash may be used as a command separator instead of a carriage return to limit the macro body size. The COUNT clause sets up a loop which is executed a maximum number of times, defined by the loop counter, which terminates the loop if no exit clause is met before the counter runs out. The loop counter is only evaluated when the COUNT clause is entered. Any change in the loop counter parameters while executing the COUNT clause does not have any effect. The loop is left either by the counter running out, by a programmed condition (UNTIL and WHILE) or a manual forced exit (ESC key). The OSN process–audit may forcibly abort your test session if the execution of this command takes longer than about 8 seconds without any target processor or I/O access. The latter can be prevented by including the ’EVE’ command in the loop (refer to ”3.16.1 Check on event presence” on page 117). Example: COUNT 80T ;scan table, size 80 words IF WOR .A <> FF WRI ’ENTRY FOUND AT ’,.A END .A=.A+1 END

3.6.3 REPEAT command _____________________ Syntax: REP cr [command cr]... [UNT bool–expr cr]... [command cr]... [WHI bool–expr cr]... [command cr]... END UNT An exit clause which causes a termination of the REPEAT loop when the boolean expression evaluates to TRUE. WHI An exit clause which causes a termination of the REPEAT loop when the boolean expression evaluates to FALSE. cr Carriage return, i.e. each clause or command must start on a new line. Within macros, the back–slash may be used as a command separator instead of a carriage return to limit the macro body size. The REPEAT clause sets up a loop which is executed forever until one of the exit clauses, if any, terminates the loop. The boolean expression(s) are evaluated every time when the applicable exit clause is entered. Any change in the parameters while executing the REPEAT clause effects its execution. Details about termination conditions see ”3.6.2 COUNT command” on page 47. 013 211 31515 AAAA EA 48

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– CAUTION: REPEAT loops without any MPTMON internal WAIT state (i.e. no slav ________ access, no output, no event scanning) cause a boot of the PTCE processor forced by the sanity timer. Pressing of the ESC key will not be recognised. Example: DEF .NA = 5 REPEAT WHILE .NA > 0 .NA=.NA–1 WRI ’NETWORK ADDRESS = ’,.NA ACT .NA WOR 867B:5 DAC END ; ;audit memory changes ; WOR.A=0 REP\WHI WOR.A=0 EVE ;check events IF WOR.A=FFFF\WOR.A=0\END END WRI’VALUE HAS BEEN CHANGED’

3.6.4 EXIT condition _____________________ Syntax: EXI The EXIT command provides an unstructured, unconditional exit from any nested compound command (e.g. the REPEAT command), macro execution or include operation in case of a user detected error or an unexpected event. It returns back to the outermost level, i.e. the interactive mode of operation, keeping all local symbols defined at that point.

013 211 31515 AAAA EA 49

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.7 Breakpoint commands ________________________ One of the debugging facilities of MPTMON are breakpoints; i.e. a means for tracing the flow of a program and obtaining program data at a certain time. MPTMON only offers SW breakpoints to observe and/or control a program running under the System 12 Operating System. SW breakpoint means that MPTMON sets a breakpoint by patching the desired memory location so that a procedure of the MPTMON Slave SSM is called when this particular location is executed. MPTMON on its own, can’t offer any HW breakpoint features like ICE does. In other words you cannot define a breakpoint which matches on data read/write access or using special segment registers etc. However, with the use of additional HW–boards MPTMON is able to trace code executed by the 8086 or 80386 processor (refer to ”3.11 HW trace commands” on page 82). The following considerations have to be taken into account specifying a breakpoint: – The breakpoint location has to start on an 8086 or 80386 instruction boundary, i.e. the breakpoint has to be placed at the start of an instruction op–code. Note here as well the use of MPTMON’s disassembler to find the start address of an instruction (see ”3.3.7 Disassemble code” on page 35). – The breakpoint location has to be a code address within an FMM code segment. You cannot specify breakpoints within the MPTMON itself. In SSM procedures scheduled by the OSN or in the OSN itself only breakpoints of the mode ”tracing” or ”debug” are allowed. Otherwise an undefined operation occurs which might lead to a CE restart or CE reload. Suspending or blocking breakpoints shall only be used in FMMs or SSM Interface Procedure called by a FMM Process. Breakpoints in the common patch segment must be specified using the correct code segment value of the patch segment, and may not use an arbitrary segment value and offset. This is caused by the fact that MPTMON does not convert the breakpoint addresses internally to absolute 20 bit addresses. Breakpoints on SW interrupts are not allowed for 80286 and 80386 processors. – A breakpoint trigger is always followed by a single step instruction and depending on the breakpoint mode, automatically removed by MPTMON. Consequently, the CS:IP value after a breakpoint match will always point to the next instruction to be executed after the one on which the breakpoint was set. – Non matched breakpoints are kept in the MPTMON breakpoint table and can be displayed using the BRP command and removed using the REM BRP command. – Due to data corruption it might occur in rare cases, that a breakpoint is matched, which is not in MPTMON’s breakpoint table. MPTMON will try to inform the tester accordingly and terminate the process hitting the breakpoint. In this case, the tester has to patch the code address back to its original value or initiate a reload of the processor. – Only one process can be suspended at a breakpoint at any time. – Breakpoints will not survive a CE restart.

013 211 31515 AAAA EA 50

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Some of the points described here are caused by the fact that MPTMON requires OSN support to handle a breakpoint match, i.e. uses normal message communication primitives to inform the tester when a breakpoint is matched. The breakpoint handling commands available with MPTMON are the following: – Fetch FMM location – Fetch SSM location – Set a single breakpoint – Display active breakpoints – Go till a breakpoint is matched – Display / Modify registers – Wait on a breakpoint match – Remove one or all breakpoints

3.7.1 Fetch FMM location _________________________ Syntax: FET [FMM] fmm–id [,download_flag] fmm–id FMM identity number as specified in the FMM descriptor. download_flag boolean value to inhibit the download if the FMM is overlay (default is TRUE = enable overlay download) Fetch FMM provides the CSEG and DSEG value of the FMM to be able to set breakpoints in FMM code without having to know its physical memory location. If the FMM is present in memory, the following register identifiers are loaded: – CS has the code segment value of the FMM. – IP has the actual start offset of the FMM–code. – DS has the data segment value of the FMM. – RAX has the FCB–number of the FMM. – FLA has OSN flags of the FMM. – ES:DI has the address of the FCB entry. Normally, the pointer value CS:IP has the actual start address of the FMM–code. The first 6 bytes at the beginning of the code segment are used to provide the entry points of the FMM to the OSN. From Release 6 onwards this is followed by an 8 character GSM identification. IF MPTMON is executing in interactive mode this GSM name is displayed automatically. Otherwise the

013 211 31515 AAAA EA 51

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– display of the GSM name depends on the setting of the display option (see ”3.19.3 Display of suppressed data” on page 125). Unfortunately, it is not easy to find the actual start address of the FMM read–only data, as the offset depends on the code size of the FMM. One method to find the actual start address (if required) is to disassemble the code accessing the first constant data declaration on module level. This shows you the actual offset assigned to the read–only data by the segment mapper. Overlay FMM’s will be downloaded if required, in order to provide valid CS and DS values and plant breakpoints before the FMM actually starts executing. Consequently, the execution of this command may take some seconds or even minutes until the FMM is actually in memory. To inform you about this situation, MPTMON will display a warning message to indicate that it is waiting on the completion of the download. In addition to the download, an overload–debug flag is set in the OSN–data for the particular FMM in order to prevent swapping of the FMM. Swapping would cause planted breakpoints to be invalid, or possibly even a processor restart when such a breakpoint is removed. Example: FET FMM 111 ;provide FMM data DEF.FMM=CS:IP ;set up symbol GO .FMM+3AC ;go till instruction executed ASM CS:IP ;disassemble next instruction ; FET FMM 123 ;download overlay FMM BRP CS:0,SUS ;plant breakpoint on FMM entry <405:1=1; ;trigger downloaded FMM by ORJ ;use CNTL–X to exit MMC as ;ORJ can’t perform semantic check ;notice breakpoint match GO CS:IP ;single step to supervisor entry GO CS:6+4AD1 ;plant next breakpoint and run

3.7.2 Fetch SSM location _________________________ Syntax: FET SSM ssm–id ssm–id SSM identity number as specified in the SSM descriptor. Fetch SSM provides the CSEG and DSEG value of the SSM to be able to set breakpoints in SSM code without having to know its physical memory location. The GSM name (if available) is optionally displayed and the following register identifiers are loaded: – CS has the code segment value of the SSM. – IP has the actual start offset of the SSM–code. – DS has the data segment value of the SSM. 013 211 31515 AAAA EA 52

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– – RAX has the SCB–number of the SSM. – RCX has the number of SSM procedures. – ES:DI has a pointer to the SCB in the OSN tables if further information is required. The same remarks on the actual start addresses of the SSM–code and data are valid as made in ”3.7.1 Fetch FMM location” on page 51. NOTE: Suspending and blocking breakpoints should never be set in clocke _____ procedures and event handlers. Only tracing breakpoints can be used without any restriction. Refer to ”3.7.3 Set breakpoint” on this page for more details and an explanation why. Example: FET SSM 43 ;provide SSM data DEF.ASY=CS:IP ;set up symbol GO .ASY+3AC ;go till instruction executed ASM CS:IP ;disassemble next instruction ;

3.7.3 Set breakpoint _____________________ Syntax: BRP addr–expr[,brp–mode [,value]] addr–expr Expression which calculates to an address comprising the memory location at which the breakpoint shall be set. brp–mode Five different breakpoint modes are provided: SUS =suspending (default) The optional value defines the process–number of the process that may hit the breakpoint. BLO =blocking. The optional value defines the process–number of the process that may hit the breakpoint. DEB =debug. If a value is specified, it is ignored; i.e. any process may hit the breakpoint. COU =counting. The optional value here is used to define an initial value for the counter. If this parameter is omitted, the initial value is 0. TRC =tracing. If a value is specified, it is ignored; i.e. any process may hit the breakpoint.

013 211 31515 AAAA EA 53

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– value An optional integer specifying a process or counter value. Sets a breakpoint specifying the breakpoint location in memory and the breakpoint mode. The maximum number of concurrent breakpoints is limited as defined in ”4.3 Dimensioning” on page 141. MPTMON offers a variety of breakpoints to cover the somewhat different needs of the various test phases. During module testing it is in general allowed to block a processor completely when a breakpoint is matched, while during integration testing this may not be the case. Here it is often desirable to only suspend a single process from execution and study its run–time environment while other processes continue execution. For on–site testing with real–life traffic however, only counting or tracing breakpoints should be used in order to not disturb any ongoing transaction. The use and impact of the breakpoint modes is: 1. a SUSPENDING breakpoint in fact stops a running process, if such a breakpoint is matched. This is the default breakpoint mode. The breakpoint is always removed immediately when it matches, i.e. will not retrigger automatically. Suspending a process has to be understood in the way, that the process is put onto a wait state, until it is resumed by MPTMON in sending a special message to it (see ”3.7.5 Go till breakpoint matched” on page 56). 2. a BLOCKING breakpoint is treated in the same manner as a SUSPENDING breakpoint. The major difference is that the process on a breakpoint sents highest priority messages to itself, while waiting for the message to continue normal execution. This virtually blocks all activities of the processor at process scheduling level. Additionally the OSN Time Services are disabled to prevent that running SW timers will expire (SW timers and counters are not incremented). This will stop as well fast periodic scheduled clocked procedures. The interrupt system and the Network Handler are not disabled, therefore MPTMON’s communication via the network is not affected by blocking a processor. 3. a DEBUG MONITOR breakpoint blocks the whole operation of the processor, i.e. the complete operation system (including process scheduling, time services and network handler) is disabled, except the debug monitor. The debug monitor, a part of the OSN error handler, can maintain the UCP to the MPTMON controller for communication. Note that all MPTMON commands corresponding directly to an OSN primitive are disabled (e.g. SND, CAL OSN, GET UCP). 4. a COUNTING breakpoint is a breakpoint which is useful for verifying that a program executes a certain piece of code N times (initialise the counter value with –N) or to measure event occurrences (counter value is initialised with 0 per default). The counter value is incremented every time the breakpoint triggers until the counter overflows. On counter overflow, MPTMON removes the breakpoint automatically and sends a breakpoint–match message with a snapshot of the processor registers at the moment that the breakpoint matched for the last time. Every process continues execution immediately after triggering the breakpoint. Note that the breakpoint matches immediately, the first time that the specified address is executed, when the value is set to ”–1”. 013 211 31515 AAAA EA 54

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 5. when a TRACING breakpoint is triggered, the tester is not directly informed. Instead of notifying the tester with a breakpoint match message on the screen, an entry is made in the message trace buffer and the breakpoint replanted, i.e. it is retriggerable. The matching of breakpoints can be monitored using the COL TRC or DUM TRC commands (see ”3.10.14 Collect trace buffers” on page 80). Note that this is the only breakpoint type which retriggers automatically. It may be planted in any code segment, even in the OSN or a SSM. The breakpoint match information is stored in the Slave trace buffer, interleaved with possible message trace information until the trace buffer overflows. MPTMON stores the identity of the process that matches a breakpoint, and takes it as default if a new suspending or blocking breakpoint is planted without explicitely specifying a process value. Furthermore the process identity is needed for a subsequent GO command to release the suspended process. The process value H’FFFF or the synonym keyword ”ANY” can be used to indicate that any process may match the breakpoint. MPTMON only suspends one process at any time. Consequently, if one process is suspended and a second process hits another suspending breakpoint, MPTMON ignores the match and keeps the breakpoint in memory. This allows you to follow a transaction from one process to another process by means of breakpoints set on ”ANY” process. Processes, executing on behalf of other transactions, will not hit a breakpoint prematurely, while the first process is still suspended. Note that the current process suspended is displayed using the CE command. WARNING: You have to use the correct code segment value when specifying th ________ breakpoint address, otherwise MPTMON is not able to treat a breakpoint match. This is especially important when specifying a breakpoint in the common patch area. Consequently, you must use the common patch segment value in the breakpoint address specification for breakpoints in the common patch area. Example: BRP .VDU_DH+145 ;suspending breakpoint BRP .TS+725,TRC ;trace point in the time service BRP .VDU_DH+09F,COU ;counts the number of logons BRP 5678:45T,SUS ;sets a suspending breakpoint BRP .FMM+78,SUS,4512 ;suspend only process 4512 BRP .DEV_DH+A52,BLO ;block the processor at breakpoint match

3.7.4 Breakpoint display _________________________ Syntax: BRP Displays the breakpoint table comprising all active breakpoints. The display is formatted in 4 columns:

013 211 31515 AAAA EA 55

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 1. The absolute address at which a breakpoint is planted (the memory contents of this location should be ’CC’). 2. The original memory contents to be restored after a breakpoint match. 3. Either the process number of a process that may hit the breakpoint or the current counter value. Any process number is assumed if ’FFFF’ is displayed as process number. 4. The breakpoint mode which may be ’tracing’, ’counting’, ’suspend’, ’blocking’ or ’debug’.

3.7.5 Go till breakpoint matched _________________________________ Syntax: GO [addr–expr, [mode]] addr–expr Expression which calculates to an 8086 address comprising the memory location at which the breakpoint shall be set. mode Optional breakpoint mode to be used when planting the breakpoint. The keywords ”SUS”, ”BLO” and ”DEB” are the only valid modes to specify a suspending, blocking or ”debug monitor” mode (see ”3.7.3 Set breakpoint” on page 53for details). If this parameter is omitted, the default chosen is the mode of the current process on a breakpoint. If no process is suspended, any process hitting the breakpoint may cause a match condition, otherwise only the suspended process is considered. This breakpoint command is the most easiest way to follow the sequential flow of a program by stepping from one breakpoint to another. It plants a breakpoint on the specified address, subsequently if a process is suspended, it is resumed, and MPTMON waits until the process hits the next breakpoint. If another process than the one specified or taken per default hits the breakpoint, it is ignored and the breakpoint restored again. Register values and a symbolic evaluation of the program counter CS:IP are displayed depending on display option set (see ”3.19.3 Display of suppressed data” on page 125). Additional breakpoints can be set with the BRP command to make sure that the process under test does not get out of control if an unexpected branch occurs. If the breakpoint address is omitted, MPTMON only activates the suspended process by sending a special message to it, without setting a new breakpoint. WARNING: You have to use the correct code segment value otherwise MPTMON i ________ not able to treat a breakpoint match. This is especially important when specifying a breakpoint in the common patch area. Currently, you must use the common patch segment value in the breakpoint address specification. Example:

013 211 31515 AAAA EA 56

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– GO .VDU_DH+6 ;set first suspending breakpoint GO .VDU_DH+23 ;continue till next breakpoint and suspend COU 5 ;make 5 single steps GO CS:IP ASM CS:IP ;disassemble next instruction END GO ;activate suspended process ; FET 2D9 ;fetch FMM code segment value GO CS:6+454,BLO ;block processor as soon as BRP matched

3.7.6 Display / modify registers _________________________________ Syntax: REG [register=value,...] register a register keyword as specified in ”2.2 Key–words” on page 13 This command allows the tester to display or modify the register set of the processor. If no modification clause is given, the current register set is displayed. The registers are in general only valid after a breakpoint match or certain MPTMON commands. This is of course already obvious from the fact that the target processor is always executing code (OSN, MPTMON, etc), i.e. the registers never have a stable contents. Modification of registers is only accepted if a process is on a breakpoint. The modification is done on the stack of this process and becomes effective with a GO command. Note that some register keywords are used as well to hold data for other purposes than 8086 registers (”2.2 Key–words” on page 13). Therefore, a register modify command should not be executed after a FETCH command or TRF final trigger event without using the command RES REG previously. Otherwise a restart or reload of the target processor will be the result. Example: FET A4 ;fetch FMM data DEF.FH=CS:6 ;set up symbol GO .FH+268 ;enter FMM REG ;display all registers REG RAX=8,RBX=7FA4 ;modify two registers GO ;load registers in 8086 and ;resume process execution

3.7.7 Restore breakpoint registers ___________________________________ Syntax: RES REG This command restores the registers of a process on breakpoint. This may be useful after using commands which modify the register keywords (e.g. fetch commands). 013 211 31515 AAAA EA 57

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.7.8 Wait for breakpoint match ________________________________ Syntax: WAI BRP [time] time The max. time specified in seconds to wait for a breakpoint match. Instructs MPTMON to wait the specified amount of seconds in the range from 1 to 3000 (50 minutes) on a breakpoint match, or to wait indefinitely if the time parameter is omitted. If a breakpoint match occurs, the wait state is left with or without a MPTMON generated display depending on the display option set (see ”3.19.3 Display of suppressed data” on page 125); in any case, a snapshot of all processor register values is taken at that moment the breakpoint was matched. These values are accessible by the register keywords to allow for user defined text display. If no breakpoint match occurs in time the wait state will be left without an error message; in this case all breakpoints present are left unchanged and must be removed if required. An indefinite wait state may be left with an error message by time supervision (see ”3.19.6 Set supervision time” on page 127) or, interactively, by pressing the ESC key. This command is of course not applicable for the trace points (i.e. tracing mode breakpoints). They do not generate any event or an associated display, but the matching of trace points have to be dumped from the trace buffer by the tester. If MPTMON is executing in interactive mode, a breakpoint match is accepted automatically while waiting on input (see ”3.16.1 Check on event presence” on page 117). In this mode, a ’Breakpoint matched’ message is always displayed by MPTMON including: the address on which the breakpoint was matched, a symbolic evaluation of CS:IP, the CE network address, and the contents of each register.

3.7.9 Remove breakpoint ________________________ Syntax: REM BRP [addr–expr] addr–expr Expression which calculates to an 8086 address comprising the memory location of a previously defined breakpoint, which has to be removed. Removes non matched breakpoints from the MPTMON breakpoint table and as well from the FMM/SSM code. All breakpoints are removed if the breakpoint address is omitted. Example: BRP 4090:0F8A ;set first breakpoint BRP 4090:0A09 ;set second breakpoint WAI BRP ;one breakpoint is matched REM BRP ;remove the other

013 211 31515 AAAA EA 58

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.8 Message commands _____________________ Testing in a System 12 environment requires the simulation of functions on a message level which are not implemented for certain reasons or to perform any other operation which can be stimulated through a message. Simulation is necessary if there is no operational SW which fulfills a certain function or if the corresponding interface SW is missing. MPTMON can act here as a stub and driver in sending and receiving those messages which are handled by other SW functions. Every MPTMON Slave has its own message library where a set of messages can be defined during a test session. Initially there is no message defined (after a Control Element reload). A message may be altered any time to any suitable definition. The following set of message commands is supported by MPTMON: – Display a message – Alter a message – Send a message – Receive any or a specific message – Wait on any message To handle messages which are sent or received via a user controlled path (UCP), the following commands have to be used: – Get a UCP – Register a UCP – Return a UCP

3.8.1 Display message ______________________ Syntax: MSG [library–no] library–no An index into the message library, locating the message to be displayed. Displays the contents of a message image from the message library as it is defined currently or, if the parameter is omitted, the contents of the last message received by the MPTMON Slave. The display is divided into two parts: 1. the message header section 2. the user data or message text section. At first a header line is displayed explaining the message header section, forming the columns: message number, message type, destination process identity, source process identity, flags, path identity, user buffer pointer 013 211 31515 AAAA EA 59

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– and buffer length. On the following line the contents of the message header is displayed according the header line. Secondly, if any message text is defined (length field of the message greater than 0) it is displayed and formatted by 8 words on a line. An attached user buffer is not displayed but it might be displayed using the WOR or BYT commands. NOTE: The source process identity displayed is always the one from a MPTMO _____ Slave process; see as well the ALT MSG command for special message element treatment. Example: MSG 2

3.8.2 Alter message ____________________ Syntax: ALT [MSG] library–no, word–offs = expression [,...] library–no An index into the message library locating the message to be altered. word–offs Word offset within a message at which a message is modified in the range from 1 to 31 decimal. expression An expression which can be evaluated into an integer or pointer value. A pointer is treated as 2 integer parameters, first the offset followed by the segment of the parameter. Alters one message in the message library beginning at the specified offset. Maximal 8 words can be modified at a time. The actual message layout to be used, is described in ”B.1 Message buffer layout” on page 183. A set of message elements is treated in a special manner, which are: – Source process identity (offsets 6 and 7) – Destination process identity (offsets 4 and 5) – User buffer pointer (offsets 9 and 10T) – Message text The source process identity may be altered, but it is always replaced by the MPTMON Slave process identity. The destination process identity is treated as a special case for DIRECTED_TO messages. Since a DIRECTED_TO message is usually the response to a BASIC message (which delivers the destination process identity) a DIRECTED_TO message should be automatically supplied with the destination process identity. MPTMON is able to do so, because it keeps last message sent to an MPTMON Slave (excluding of course the MPTMON internal command messages). If the destination process identity is set to two adjacent 0’s it will be automatically replaced by the last received message’s source process 013 211 31515 AAAA EA 60

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– identity in case of MSG or SND MSG commands, otherwise the destination process identity is left unchanged. Similarly, for BASIC_VIA, BASIC_VIA_FOR and DIRECTED_VIA messages, the destination field for a UCP path identity is replaced by the real UCP identity as set up by a GET UCP or REG UCP command. The destination path field is only replaced if it was set to the null value ’0’ with the ALT MSG command. A message parameter may carry a process identity of the process sending the message. If we consider that MPTMON can act as a stub FMM and sending those messages having such a parameter these message parameters should be automatically filled up with the process identity of MPTMON. In case of MSG or SND MSG commands the message text or user data area is scanned for two adjacent words containing the value –2, and if found they get replaced by the MPTMON Slave process identity. A user buffer may be attached to a message definition in modifying a not used memory area with the required buffer image and additionally setting the pointer and the length of this predefined memory area into the message’s user buffer pointer and user buffer length field, thereby linking it to the message. The buffer flag has to be altered as well to mark this message as one which implies a user buffer. The LWA can be used within the PTCE to hold the user buffer definition (if the message is created within the PTCE of course). In other CE’s you may use ’CAL OSN’ command to get an user buffer. But you have to return this user buffer later, because MPTMON is copying the data to its own user buffer before sending the message; i.e. the original buffer is kept. Look at the last example of this section how to code this. NOTE: MPTMON does offer only low level message alteration; i.e. you must b _____ fully aware what you are going to alter. Every message word is treated as a pure word, there are no special keywords for message types, priorities or flags etc (see ref. 5 and 6 for details); however, special macros are available which allow you to define a message by filling in a menu or by prompting for the relevant message parameters. Example: ALT 3,2 = 4E00,9999T ;msg type and no. ALT 2,8 = WOR .A+34,.LCE_ID,–2,–2 ;user text area ALT 4,4 = WOR MSG+10,WOR MSG+12 ;msg destination ; ALT 1,9 = LWA,.UBLEN ;LWA user buffer (only in PTCE) BYT LWA=1,2,3,4,5,6,7,8 ;load the buffer ; CAL OSN 3,CBU,1K ;get an user buffer (max size=4K) WOR(POI CBU)=1,2,3,4,5,6,7,8 ;load the buffer ALT 1,9 = POI CBU,1K ;store the user buffer SND 1 ;send the message CAL OSN 4,CBU ;return the user buffer

013 211 31515 AAAA EA 61

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.8.3 Send message ___________________ Syntax: SND [MSG] library–no library–no An index into the message library, locating the message to be sent. Sends the specified message as it is defined in the message library. It should be noted that certain message elements as defined for ALT MSG command are modified by MPTMON autonomously if applicable before the message is sent. If a user buffer is defined for this message an OSN user buffer is requested by MPTMON with the defined length and the contents of the data area at which the message’s user buffer pointer is pointing to is copied into the obtained user buffer. The message’s user buffer pointer is then updated with the new buffer pointer and sent along with the user buffer. The message sent is per default not displayed, though an option exist to display the message as it is sent by MPTMON (see ”3.19.3 Display of suppressed data” on page 125). There is no checking provided if all message elements have well defined values, e.g. message type, flags etc. Consequently, a message may not be routed to your expected destination or get lost if the message header is not setup correctly. Example: SND 3 SND .DT_SZE

3.8.4 Receive message ______________________ Syntax: RCV [MSG] [msg–no] msg–no A message routing number of the message which is expected to be received. Puts MPTMON into an indefinite or time supervised wait state (see ”3.19.6 Set supervision time” on page 127) to wait for a specific message or any message if the message number is omitted. If another message than the specified one is received, MPTMON will accept and optionally display it, but stay in the wait state until the specified one arrives. Note the difference to the MULTIPOL WAIT_CASE statement where these messages are deferred. If a message is received MPTMON optionally (see ”3.19.3 Display of suppressed data” on page 125) informs the tester that such an event had occurred and displays the according message. The last message is kept in the CE where it has been received and is accessible from the MPTMON Controller through the MSG keyword, to obtain data which is required to send another 013 211 31515 AAAA EA 62

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– message or for examination purposes. For general comments about event handling see ”3.16 Event handling commands” on page 116. Example: RCV ;accept any message RCV 9842T ;accept unique msg RCV .SZE_DEV ;number specified by a symbol

3.8.5 Wait for message _______________________ Syntax: WAI MSG time time The max. time specified in seconds to wait for a message. This command is almost identical to the ”RCV” command. The major difference is that no error is generated when no message is received within the specified time. This allows an easy exception handling by the user within macros, without being aborted by an MPTMON error message. The keyword ”EVC” gives access to MPTMON’s internal variable ”event code” to find out what happened on command completion (the value ”2” indicates that a message was received; see ”3.16 Event handling commands” on page 116). Example: WAI MSG 5 ;accept any message within 5 seconds

3.8.6 Get user controlled path _______________________________ Syntax: GET UCP network–address network–address The network address in the form ’ZYXW’. Gets a UCP from the OSN, via which messages can be sent to any Control Element. Only one UCP can be handled concurrently by MPTMON, so it is impossible to get a UCP if another UCP is already set up or registered. MPTMON will substitute the destination path identity field for a DISPLAY and SEND message command by the real UCP identity, if this field in a message definition is set to ’0’, otherwise it is left unchanged. Example: GET UCP 0027 GET UCP .ACE_7

013 211 31515 AAAA EA 63

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.8.7 Register user controlled path ____________________________________ Syntax: REG UCP Registers a UCP via which a basic message was received by MPTMON. If the type of the last message received by MPTMON was not BASIC_VIA or BASIC_VIA_FOR, or a UCP was already registered or set up, an error indication is given. MPTMON can send a DIRECTED_VIA message via a UCP after a path is registered or set up, to build a two way link between two processes.

3.8.8 Return user controlled path __________________________________ Syntax: RET UCP Returns a UCP which was previously registered or got from the OSN. If a UCP is returned or a path release message is received by MPTMON, the UCP is not available anymore to the user and no messages can be sent afterwards via a UCP, unless a new UCP is registered or set up.

013 211 31515 AAAA EA 64

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.9 Call commands __________________ Testing in a System 12 environment requires not only simulating or driving functions at message level as described in ”3.8 Message commands” on page 59, but sometimes access to OSN, SSMs, or kernel functions. MPTMON allows you to call these functions in a rather simple, but quite dangerous manner. As the number of parameters passed to these functions and the semantic correctness of the parameters can not be checked by MPTMON, it is assumed that the user is aware of what he is doing and accepts the quite large risk that the target processor crashes. Having accepted this fact, it is relatively easy to call a function using a special work–area in the Slave to pass and return parameters to the primitives. The keyword CBU (Call Buffer) is provided for this purpose and points to a static work area of length 32 bytes in each Slave. No checks are made if the user or the primitive addresses the CBU outside the 32 byte range. The commands provided are: – Call OSN primitive – Call SSM procedure – Call DBCS – Call OBC – Call TI command – Call External Routine

3.9.1 Call OSN primitive _________________________ Syntax: CAL OSN function_no [,expression,...] function–no The function number of the OSN primitive. expression An expression which can be evaluated into an integer or pointer value. The sequence of the command parameters (in the syntax definition specified as a list of expressions) is the same as in the CHILL definition of the OSN primitive. This command calls an OSN primitive using the interrupt 48. Before executing the ”INT 48” all parameters are pushed in reverse order on the stack, i.e the function number as the last value. No consistency checks are made on the number of parameters and their modes; i.e. if incorrect, the processor may crash. Some parameters of OSN primitives are simply passed by value, i.e. you can give the value directly as a parameter of the ”CAL OSN” command. However, other parameters are passed by location, in order to return values to the caller. These parameters which have to be passed by location can be located somewhere in the 32 byte call buffer (CBU). The keyword CBU with an appropriate offset gives directly the address where the OSN has to put the 013 211 31515 AAAA EA 65

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– return values (see examples below). You can find a list of all OSN primitive numbers in the appendix (see ”APPENDIX G. OSN Primitives in alphabetical order” on page 196), but we recommend that you read the OSN user manual (211 31502 EA) to find the correct modes of the associated parameters and its sequence. A MULTIPOL listing of a CHILL–GSM gives this information as well, although without the physical layout of the stack. Example: ; execute OSN primitives GET_USER_BUF and RET_USER_BUF ; MULTIPOL definition: ; SEIZE GET_USER_BUF<>NON_LINKED(48,03) (PTR LOC, INT); ; SEIZE RET_USER_BUF<>NON_LINKED(48,04) (PTR LOC); CAL OSN 3,CBU,64T ;get user buffer, size 64 bytes DEF.UBUF=POI CBU ;.UBUF has the address of the user buffer CAL OSN 4,CBU ;return this user buffer ;CAL OSN 4,.UBUF is incorrect (passed by LOC) REM .UBUF ; ; execute OSN primitive OWN_PROCESS_ID ; MULTIPOL definition: ; SEIZE OWN_PROCESS_ID<>NON_LINKED(48,41) (M_PROCESS_ID LOC); ; CAL OSN 41T,CBU ;get slave process id DEF.PID=POI CBU ;.PID has a 4 byte process id ;in reverse order ; ; execute OSN primitive OWN_CE_ID ; MULTIPOL definition: ; SEIZE OWN_CE_ID<>NON_LINKED(48,84) (M_CE_ID LOC); ; CAL OSN 84T,CBU ;get own ce id DEF.PID=POI CBU ;.PID has a 4 byte process id DEF.LCE=WOR CBU+4 ;own LCE id DEF.NAD=WOR CBU+6 ;own network address DEF.VP =WOR CBU+8 ;own virtual path index DEF.LCE=BYT CBU+A ;own CE status ; ; execute OSN primitive OVL_XMIT ; MULTIPOL definition: ; SEIZE OVL_XMIT<>NON_LINKED(48,95) ; (M_PCE, INT LOC, PTR, M_OV_AREA_AD, INT, M_PROCESS_ID LOC); ;copy 08K of bytes from slave processor ;to network address 102 using OVL_XMIT ; WOR CBU = .PID ;provide pid of caller CAL OSN 95T,102,CBU+4,.SRC_ADDR,.DST_ADDR,8K,CBU DCL.CPL=WOR CBU+4 ;status info returned from primitive ;OVL_XMIT

3.9.2 Call SSM procedure _________________________ Syntax: CAL SSM procedure_id [,expression,...] 013 211 31515 AAAA EA 66

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– procedure_id The SSM procedure identity as used by MULTIPOL: SSM–identity * H’80 + procedure_number (for SSM–ids < 512) SSM–id * H’80 + H’40 + procedure_number (for SSM–ids > 511) expression An expression which can be evaluated into an integer or pointer value. The sequence of the command parameters (in the syntax definition specified as a list of expressions) is the same as in the CHILL definition of the SSM procedure. This command calls a SSM interface procedure using the interrupt 49. Before executing the ”INT 49” all parameters are pushed in reverse order on the stack, i.e the procedure_id as the last value. No consistency checks are made on the number of parameters and their modes; i.e. if incorrect, the processor may crash. The CBU can be used if parameters have to be passed by location in the same way as described in ”3.9.1 Call OSN primitive” on page 65. We recommend you to check a MULTIPOL listing to find out the correct procedure identity and the parameters of the interface procedure. Clocked procedures, interrupt procedures and event handlers can and should not be called in this manner. Example: ; MPTMON slave SSM interface proc to dump the ; message trace buffer: ; SEIZE LBHK_05_DUMP_TRACE_BUF <>NON_LINKED (49,8708) (PTR, INT LOC, ; INT LOC); ; CBU ––> 0 +––––––––––––––––––+ ; ! UBUF_PTR ! ; ! ! ; 4 +––––––––––––––––––+ ; ! NO BYTES USED ! ; 6 +––––––––––––––––––+ ; ! NO MSGS LOST ! ; +––––––––––––––––––+ ; CAL OSN 3,CBU,2048T ;get user buffer to DEF.UBUF=POI CBU ;keep the trace information ; CAL SSM 8708T,.UBUF,CBU+4,CBU+6 DEF.NOB=WOR CBU+4 ;no of bytes in buffer DEF.OVL=WOR CBU+6 ;no of msgs overflowed WOR.UBUF LEN .NOB/2 ;HEX dump of trace buffer ; REM .UBUF CAL OSN 4,CBU ;return user buffer to OSN ;

3.9.3 Call database interface (DB–V4) ______________________________________ Syntax: DB4 ACC relation–id, lce_id relation–id Relation identity as given in DLS–listings. 013 211 31515 AAAA EA 67

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– lce–id Logical Control Element identity of the processor where the relation is kept. The DBCS routes the request from the PTCE to the LCE, i.e. the MPTMON controller does not sent this command to a Slave. CAUTION: This command should not be used by ”normal” testers as it provide ________ access to any database relation without any security. It is most likely that the PTCE processor will go down if this command is executed interactively due to any type of data corruption. It is intended to be used by tools, or carefully designed macros only. The command calls the S12 DBCS (procedure DB_EXREQ_ED2) in the PTCE passing a pointer to MPTMON’s local work area ’LWA’. This area has to be loaded exactly as MULTIPOL sets up the DB_PARMS area for the database version 4 (see ”B.3 Data Base Access (DB–V4)” on page 187). If the LCE_ID_NULL (H’FFFF) is given as a second parameter the DBCS procedure DB_DAREQ_ED2 is called.

3.9.4 Call database interface (DB–V2) ______________________________________ Syntax: DBS ACC relation–id, lce_id relation–id Relation identity as given in DLS–listings. lce–id Logical Control Element identity of the processor where the relation is kept. The DBCS routes the request from the PTCE to the LCE, i.e. the MPTMON controller does not sent this command to a Slave. CAUTION: This command should not be used by ”normal” testers as it provide ________ access to any database relation without any security. It is most likely that the PTCE processor will go down if this command is executed interactively due to any type of data corruption. It is intended to be used by tools, or carefully designed macros only. This command operates similar to the DB4 ACC command but using the old database interface. It calls the S12 DBCS (procedure DB_EXREQ) in the PTCE passing a pointer to MPTMON’s local work area ’LWA’. This area has to be loaded exactly as MULTIPOL sets up the DB_PARMS area for the database version 2 (see ”B.2 Data Base Access (DB–V2)” on page 185). If the LCE_ID_NULL (H’FFFF) is given as a second parameter the DBCS procedure DB_DAREQ is called.

3.9.5 Call on–board controller _______________________________ Syntax: CAL OBC command_id [,parameter,...] command_id Sub–command identity parameter list of upto 15 command parameters.

013 211 31515 AAAA EA 68

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– This command is intended to be used only within macros to implement special OBC related functions, which are not provided in the generic MPTMON command set. The command carries as a first parameter a ”sub” command identity followed by a parameter–list. MPTMON packs the parameters in a command message and sents it to the currently selected Relay–FMM for execution. The reply message is copied into MPTMON’s local work area (upto 40 bytes) for further processing by the macro. Due to the fact that already existing PORT and WORD commands access memory and/or IO–ports only byte wise, even if word is specified, and some IO devices in OBC environment allow only word access to special registers, e.g. access to OBCI DMA registers, the following commands are implemented as CALL OBC commands: – CAL OBC 0 ;no action – CAL OBC 1, memory–address ;read word from memory with the given ;address. Result is placed in LWA of ;MPTMON Controller. – CAL OBC 2, memory–address, value ;write word value into memory with the ;given address. ;NOTE: only non protected memory may ; be specified. – CAL OBC 3, port–number ;read word from the given IO–port. ;Result is placed in LWA. – CAL OBC 4, port–number, value ;write word value into given IO–port. – CAL OBC 5–10 ;not yet defined. Example: DEF MAC OBCDAT (ADDRESS, VALUE) CAL OBC 1, %0 ;read word from address %0 ’ OBC DATA: ’,WOR LWA IF %N > 1 CAL OBC 2, %0, %1 ;write on address %0 value %1 ENDI EM

3.9.6 Call TI command ______________________ Syntax: TI [POR] port–number, command [,command] port–number An integer value in the range of 2 to 9 command TI command identity

013 211 31515 AAAA EA 69

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– CAUTION: This command should not be used by ”normal” testers as it provide ________ direct access to the packet–RAM and the TI port command register without any security. The given command identities are passed to the corresponding fields in the packet–RAM and the port–number is written to the TI port command register. No validation checks are made on the given command identities. The TI reply word will be displayed on the screen (not in menu mode) and, for macro application, it is held in the register RAX as well. Example: TI 2, 80 ;read status of TI port 2

3.9.7 Call External Routine ____________________________ Syntax: CAL EXT [parameter,...] parameter list of upto 16 command parameters. MPTMON offers a large set of functions implemented in the Slave FMM located in each processor. These functions are described at MPTMON’s command language level in this manual. In some special applications, the need may arise to provide very specific, not generic functions in real time where performance is critical (i.e. where a ”normal” macro is too slow). Though these functions can’t be implemented as resident code in MPTMON due to space limitations , it is possible to write such a function (routine) and call it via this MPTMON commands. The routine is invoked via the SW interrupt 72T and all parameters are passed on stack. NOTE: The tester has to set up the interrupt vector (for 8086 processors) o _____ the interrupt descriptor in the IDT to point to his own procedure. He is as well responsible for saving the environment (PUSH and POP of registers).

013 211 31515 AAAA EA 70

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.10 SW trace commands _______________________ A main requirement to find and locate errors in a running exchange is the tracing of software modules at their interfaces. There are basicly two different types of interfaces between different software items: 1. Process communication and synchronization in a 12 environment is based on passing messages (finite length data blocks being in the scope of a process) from one process to another, thereby passing applicable data or just that a certain event had occurred. In order to support integration testing MPTMON offers various types of message tracing facilities. 2. Support Software (SSMs and the DBCS) are called from a FMM via software interrupt. All parameters for this call are passed on stack. Other SSM parts (clocked procedures, event handlers and interrupt procedures) are called directly from the OSN. MPTMON offers several selection options for SSM and Database tracing. Message tracing is achieved in hooking the MPTMON Slave to the OSN at two specific trace points, linking MPTMON procedures to the OSN and enabling MPTMON to observe the message flow in a CE. Two points are chosen being able to trace sent and received messages, as seen from a process point of view. Consequently, a message is traced a number of times; i.e. when it is sent, received and deferred. NOTE: MPTMON will keep only one message trace mode active at a time. If yo _____ enter a new trace command the previous mode is overwritten, and the trace buffer cleared. For SSM tracing the OSN links MPTMON procedures each time an SSM is called or it returns. If a SSM is traced, each call of a SSM procedure appears as one trace item. Since the DBCS is an SSM, Database tracing is implemented as a special application of SSM tracing. Therefore it is not possible to have SSM tracing and database tracing active at the same time. To trace a message or an SSM basically means, that all messages or SSM calls are read and checked for certain trace conditions which are defined by the tester. If the check matches, this particular trace item gets a time stamp and is copied into a trace buffer. This trace buffer is part of the MPTMON Slave, and therefore present in each CE. It is emptied when you instruct MPTMON to dump or collect the trace buffer, and cleared when you set up a new trace condition. When the trace buffer overflows, the new traced items are only counted and do not overwrite the already traced ones; i.e. they are lost. MPTMON keeps only one copy of a traced message in the trace buffer when the message is sent, received and possibly deferred within the one CE. However, when a message is received from another CE, it will be traced as many times as it is received and deferred in the destination CE. NOTE: Although it is possible to have both traces – SSMs and messages – activ _____ at the same time, there is only one trace buffer to take up all traced items in sequential order. NOTE: Each time you enter a new trace command, the trace buffer is cleared. _____ The trace commands provided by MPTMON can be subdivided into three groups. The first group comprises the message trace qualification commands which are:

013 211 31515 AAAA EA 71

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– – Trace all messages of an FMM – Trace messages with specified routing numbers – Trace messages with specified parameter values – Trace all messages excluding specified routing numbers – Trace all messages of a specified process – Trace message interface between two FMM’s – Trace message transaction The second group contains the trace qualification commands refering to the SSM interface. – Trace SSM calls – Trace database accesses – Trace FMM environment whereby the third group encloses global trace commands as follows: – Turn trace off – Display active trace condition – Dump trace buffer – Collect trace buffers – Enable symbol replacement The trace condition specifying a message parameter value allows for various other trace conditions like (see ”3.10.3 Trace value” on page 73): – Trace messages send or received by a specified process – Trace messages received from a particular Control Element – Trace messages of a certain priority – Trace messages carrying a user buffer – Trace all basic messages, etc. NOTE: It is recommended to select a trace condition as specific as possible _____ to ease the evaluation of the trace buffer.

3.10.1 Trace FMM _________________ Syntax: TRC FMM fmm–list [,EXC=msg–list] 013 211 31515 AAAA EA 72

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– fmm–list A list of upto 4 identity number of the FMMs for which messages shall be traced. msg–list A list of upto 4 message routing numbers of messages to be excluded from the trace. Traces all messages sent or received by all processes belonging to the specified FMM except the ones specified in the exclude list. Example: TRC FMM 10T,156T TRC FMM .DIGDH, EXC=6245T,7122T

3.10.2 Trace message _____________________ Syntax: TRC MSG msg–no [,...] msg–no Message routing numbers which shall be traced. Traces all messages with specified routing numbers. Maximal 8 routing numbers can be specified. Example: TRC MSG 8056T,9999T,.INI_SBL

3.10.3 Trace value ___________________ Syntax: TRC VAL match–value [,MAS=mask] [,OFS=offset] [,MSG=msg–list] match–value Word value which has to match a word in the message buffer. mask Word mask used for match condition checking. offset Byte offset within a message buffer for match condition checking, in the range from 0 to 63 decimal. msg–list A list of max. 4 message routing numbers, separated by comma’s, which should only be checked for a match condition. Traces all messages, or a set of messages with a specified routing number, carrying a parameter specified by a match condition. The match is true if the word located at offset position logically anded with the mask is equal to match–value. The match condition is a means to extract the messages with a certain parameter value you are interested in, e.g. by comparing a message parameter, a destination process identity or any other relevant item in a message to a specified value, and thereby possibly avoiding a trace buffer overflow. 013 211 31515 AAAA EA 73

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– If the offset parameter is omitted all words in the message body (i.e. excluding the message–header) are checked for a match condition. This allows the tracing all messages carrying, for example a particular equipment–number, file–number, etc. The message list can be used to limit the check on certain message routing numbers. If the mask value is omitted, all bits are checked (i.e the mask value is per default H’FFFF). Example: TRC VAL .EQUIP_NO, MSG=8056T,9275T,2873T TRC VAL 0E00,OFS=16T,MAS=0F00,MSG=1188T

The example shows how to trace messages with defined routing numbers associated with a certain equipment number. No evaluation of the routing number is done if the MSG parameter is omitted. This offers you a set of new trace conditions as demonstrated in the examples below. Example: TRC VAL .PROCESS_NO ,OFS=10T ;sent to a process TRC VAL .PROCESS_NO ,OFS=14T ;sent by a process TRC VAL .VP_INDEX ,OFS=12T ;sent from a CE TRC VAL .PRIO ,MAS=F000 ,OFS=04T ;with a given priority TRC VAL .TYPE ,MAS=0F00 ,OFS=04T ;with a given type TRC VAL .EN ,MAS=00FF ,OFS=16T ;with first parameter

3.10.4 Trace exclude _____________________ Syntax: TRC EXC msg–no [,...] msg–no Message routing numbers which shall not be traced. Traces all messages except specified routing numbers. Maximal 8 routing numbers can be specified. A trace buffer overflow will occur normally when life traffic is on the processor. This trace mode seems therefore only useful for test–phases where hardly any activity in the processor under test is expected. Example: TRC EXC 8881T,6214T,.SZE_D

3.10.5 Trace process _____________________ Syntax:

013 211 31515 AAAA EA 74

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– TRC PID process–id–1 [,process–id–2 [,EXC=msg–list]] process–id Identity of the process which should be traced. The syntax must be virtual–path–index:process–id. msg–list A list of upto 4 message routing numbers of messages to be excluded from the trace. Traces all messages sent or received by the specified processes except the ones specified in the exclude list. This was designed to trace only one application (plus the supervisory part possibly) of a multi–process FMM. NOTE: You have to specify alwalys the full process–id (i.e. process–i _____ inclusive the virtual path index). But this gives you the chance to trace a process which is not running in the selected CE. Example: TRC PID 30:8002 TRC PID .MIO_PID, EXC=12708T,12709T

3.10.6 Trace interface _______________________ Syntax: TRC ITF fmm–id–1, fmm–id–2 [,EXC=msg–list] fmm–id FMM identity numbers of the FMM’s whose interface messages must be traced. msg–list A list of upto 4 message routing numbers of messages to be excluded from the trace. Traces all messages sent or received by all processes which belong to the specified partner FMM’s except the ones specified in the exclude list. Both FMM’s must be located in the same Control Element. Example: TRC ITF 2,5, EXC=8822T TRC ITF .VDU_FM,.VDU_DH

3.10.7 Trace sequence ______________________ Syntax: TRC SEQ [BEG=start–msg] [,VAL=value,MAS=mask,OFS=offset] [,NEX=retrig] [,UPT=last–msg] start–msg Message routing number with an optional parameter match condition which shall trigger a sequence trace

013 211 31515 AAAA EA 75

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– value Word value (optionally masked) that has to match a word in the ”start” message located at the indicated byte offset, to trigger a sequence trace. mask Word mask used for match condition checking. offset Byte offset within a message buffer for match condition checking, in the range from 0 to 63 decimal. retrig Retrigger sequence trace every n’th match occurrence, whereby n represents the value of retrig. last–msg The message that shall cease an ongoing sequence. This command starts the trace of messages sent or received by all processes being part of a message transaction. A message transaction is defined as a series of messages triggered by a certain event (e.g. subscriber off hook) and finished by another specific event (e.g. subscriber on hook, process lifetime or unexpected events). If a sequence trace trigger is fulfilled, i.e. the message number does match and the match condition is true, this particular message is flagged. If a flagged message is received by a process, the process gets flagged as well and hence all the messages sent by such a process are flagged and treated as being part of a transaction. The process transaction flag is cleared if a message without transaction flag is received. A sequence trace will not cease if a process receives an unflagged message sent by an SSM procedure scheduled by the OSN e.g. by an Event Handler or the OSN itself. This message is considered to be part of the transaction and will be traced as well. It is recommended to follow the result of a sequence trace by the ”COL TRC” command using symbolic message number evaluation and reduced display formats. In addition the trace information can be stored on disk in parallel for a full examination later. NOTE: All CE’s which might be involved in a sequence trace, have to b _____ activated, otherwise the sequence trace may stop when an unflagged message is received from a not–active CE. As an exception to the rule that MPTMON sends a command only to the selected active Slave, this command is sent to ALL activated slave’s in order to reduce your typing effort. Due to th ___ possible spreading of the trace over a set of processors in the system, the cease function may not work in all cases as expected. Example: TRC SEQ BEG=.SZE_DEV,VAL=0102,MAS=0F0F,OFS=6,UPT=.REL_DEV.

The example starts a sequence trace when the following conditions are met: – the message number is equal to .SZE_DEV – the word at byte offset 6, bit–wise anded by 0F0FH is equal to 102H. The sequence trace will not retrigger and cease upon the trace of the message .REL_DEV. 013 211 31515 AAAA EA 76

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.10.8 Trace SSM _________________ Syntax: TRC SSM [ssm–id] [,proc–type ! ,FMM=fmm–id] ssm–id The identity number of the SSMs for which the calls should be traced. proc–type The type of SSM procedure to which the trace should be restricted. Possible keywords are: – ITF – for interface procedures – CLO – for clocked procedures – INT – for interrupt procedures – EVH – for event handlers fmm–id The identity number of a FMM for which the SSM calls should be traced. Traces all SSM calls to the given SSM identity. If the SSM identity is omitted, all SSM calls are considered. With the proc–type qualifier it is possible to restrict the trace to only one procedure type. If the FMM identity is specified only the SSM calls of this FMM are considered (in that case the proc–type is ITF by default). This command needs at least one parameter. Example: TRC SSM 67T,EVH ;trace only event handlers of SSM 67T TRC SSM .ASYN,FMM=9E7 ;trace interface between FMM 9E7 and ASYN–SSM

3.10.9 Trace relation ______________________ Syntax: TRC REL [rel–list,] [FMM=fmm–id] rel–list A list of upto 4 identity number of the relations for which the calls shall be traced. fmm–id An FMM identity number of the FMM for which the database calls shall be traced. If at least one relation identity is given all database accesses to a qualified relation are traced. If the FMM identity is specified as well only the database calls of this FMM are considered. If no relation–id is given all database calls of the specified FMM are traced. This command needs at least one parameter.

013 211 31515 AAAA EA 77

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– NOTE: During relation tracing the DBCS realises the DB_FAM access by callin _____ the normal DB_DAREQ procedure. Example: TRC REL 3716T ;trace all accesses to the relation R_MSG_MNEM TRC REL FMM=9E7 ;trace all database accesses of FMM 9E7 TRC REL 12E6,FMM=9E7 ;trace all database accesses of FMM 9E7 to the relation 12E6

3.10.10 Trace FMM environment ______________________________ Syntax: TRC ENV fmm–id [,EXC=msg–list] fmm–id An FMM identity number of the FMM for which the trace shall be activated. msg–list A list of upto 4 message routing numbers of messages to be excluded from the trace. Traces all SSM calls and all database calls of the specified FMM and additionally all messages sent or received by all processes belonging to the specified FMM are traced except the ones specified in the exclude list. Example: TRC ENV 10T TRC ENV .DIGDH, EXC=6245T,7122T

3.10.11 Trace off __________________ Syntax: TRC OFF Turns the message trace and the SSM trace off, but keeps the current trace buffer contents. Any ongoing trace is stopped. MPTMON executes this function automatically as part of the ”DAC” command (see ”3.2.2 Deactivate Control Element” on page 27) if a trace condition was activated.

3.10.12 Trace display ______________________ Syntax: TRC Displays the active trace conditions as there are message trace qualification and SSM or database trace qualifications. The display is given in a form which matches a valid command input.

013 211 31515 AAAA EA 78

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.10.13 Dump trace buffer __________________________ Syntax: DUM [TRC] [device, file] device The IOS device number from which the information shall be read. file The IOS file identity specifying the file to be used to read the trace information. Dumps (displays) the current contents of the CE trace buffer onto the VDU screen. Five trace types can be formatted by MPTMON: messages, SSM calls, relation accesses, breakpoints and OBC mails. Each trace type has its own header line. In order to get more information on one screen, the header line is given only once unless the trace type changes. Each trace item consists of main trace information (with fixed length) displayed on one line following the last header and an optional data trace with variable length (refer to ”3.19.5 Set trace length” on page 126) which may be displayed on several extra lines. Each data line is prefixed by a keyword describing the type of data. For messages, for example, the main trace information consists of message header elements, trace side information and time stamp. The data trace may comprise the contents of the message body and the contents of the user buffer, if one is attached. When a trace buffer overflow has occurred, the number of lost items during the last trace period is displayed either at the beginning or at the end of the trace buffer depending on if the cyclic option is set or not. Finally, the trace buffer is marked as empty. The trace buffer is as well marked as empty with every new message trace condition set without displaying the current contents, which is consequently lost. The trace side information (for messsage trace) can be either SND, RCV or DUP, indicating in which OSN module a message has been traced. SND stands for OSN Message Handler, the message was just sent (queued into a message queue). RCV stands for OSN Process Manager, the message was just received (queued off from a message queue). Therefore a message which is defered by the FMM process may appear several times in the trace buffer (one entry for each time it is offered by the Process Manager). Whereby DUP stands for duplicated; such a message had been traced at both sides in a certain time frame, it was the same copy actually. Note that this DUP logic is only active for TRC MSG and TRC EXC. In this case a defered message appears only once in the trace buffer. An optional parameter set is provided to support the dump of trace information from an IOS file, previously written using the ”COL TRC” command, instead of directly from trace buffer in the target processor. Dumping from an IOS file proceeds until the end–of–file condition is reached or the ESC–key is pressed. NOTE: Several display options exist to shorten or to extend the tracing, t _____ shorten the display or to select the information displayed for each message, SSM call, database access or breakpoint traced (refer to ”3.19.4 Message and trace formatting” on page 125, ”3.19.5 Set trace length” on page 126 and ”3.10.15 Enable symbol replacement” on page 81 ). 013 211 31515 AAAA EA 79

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Example: DUM ;dump from a single target processor memory DUM 2,950T ;dump collected information from a disk file

3.10.14 Collect trace buffers ______________________________ Syntax: COL [TRC] [device, file,] [last–msg] device The IOS device number on which the information shall be stored. file The IOS file identity specifying the file to be used to store the trace information. last–msg Message routing number which shall cease the collection of trace information. Collect and display trace information from all active, tracing CE’s. The information can optionally be stored in variable size, binary records on disk or tape for later post–processing on a host–computer or for repeated display purposes. The file characteristics must be the same as the save/retrieve files (predefined are 950T–959T); in fact, the same file identities can be used. The collection and display stops as soon as the optionally specified last–message is displayed. If all parameters are omitted, any message or breakpoint trace is displayed and the command execution can only be aborted by pressing the ESC–key. The COL TRC command is particularly helpful to follow a sequence trace ongoing, without the need to individually dump the trace buffer contents of each CE tracing. Moreover, the chance that a trace buffer overflows is smaller than using the ”DUM TRC” command, as the buffers are continuously emptied. Only when the display is triggered the scanning speed is reduced due to the time it takes to display a message. NOTE: Several display options exist to shorten the display and informatio _____ displayed for each message or breakpoint traced (refer to ”3.19.4 Message and trace formatting” on page 125, ”3.19.5 Set trace length” on page 126 and ”3.10.15 Enable symbol replacement” on page 81 ). Example: COL ;display trace forever COL TRC 7086T ;display stops with the msg 7086T COL TRC 2,950T ;collect trace info on disk forever COL TRC 1,951T,1234T ;collect on disk until msg 1234T is traced

013 211 31515 AAAA EA 80

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.10.15 Enable symbol replacement __________________________________ Syntax: ENA SYM Enables in the display of trace information, the substitution of the message type by a message name, and the breakpoint address by a symbolic name and offset. DIS SYM Disables the substitution of values by symbols in breakpoint match notifications and message types by names in message displays. The symbolic evaluation is particular helpful in dumps of trace information to allow an easy and fast perception of the information displayed. Used in conjunction with the ”SET HEA” formatting option, it allows for compact and readable trace dumps. For module tests new messages which are not yet known by the system can be defined as a symbol. Example: FET 1E6 DEF.MPT_CNT = CS:6 ;defines a symbol address DEF.DM_EVENT = 11523T ;defines a new message name ENA SYM ;replace message routing numbers by DUM TRC ; names in the dump

013 211 31515 AAAA EA 81

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.11 HW trace commands _______________________ The Trace Facility (TRF) is a hardware test tool that allows MPTMON to monitor the execution of instructions on the high speed processor bus. It is basically impossible for MPTMON to perform this monitoring function –i.e. tracing– without the TRF. The trace features offered far exceeds the trace capabilities of an MDS or LDS. Considering this, the combination MPTMON – TRF is preferable over a MDS / LDS in most cases for integration or testing. One of the major differences in operation between MDS/LDS and MPTMON is the fact that MPTMON does not combine tracing and breakpoints (though may be combined using macros) as an MDS does; i.e. if a breakpoint is matched the trace in real time does not stop per definition. The TRF is implemented as an assembly of two PBA’s which has to be plugged into one slot of a System 12 subrack using a special slot extender card. The TRF operates under real time conditions without any influence on the processing speed of the CPU. Basicaly two different hardware version of the TRF are available at the moment. One Version called TRFB (or TRFA) is designed for INTEL 8086 processors, the other one called TRFE operates with 80386 processors. Depending on the different behaviour of these two processor types there is one big difference in reading the traces of the TRFB and the TRFE: Pre–fetched opcodes are ignored by the TRFB until they are executed by the 8086 processor. This is not possible with the TRFE. Therefore the TRFE can only trace prefetched code cycles. Since the read/write cycles are taken at execution time, the read/write cycles of the 80386 processor are not inline with the corresponding code instructions. The TRF operation is controlled by trigger and trace conditions loaded by MPTMON into the TRF hardware. Trace conditions are used to qualify what has to be traced, like the processor–bus status and address range; whereas trigger conditions specify the beginning or termination of the trace by means of an event or sequence of events. The sequencing of events is defined by so called trigger levels. A functional block diagram of the TRFB gives an idea of the data and control flow within the TRF–PBA:

013 211 31515 AAAA EA 82

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


|| +–––––––––––––––––+ +–––––––––––––––––+ ||–>–| trace channel 1 |–––––––>| | || +–––––––––––––––––+ | | || . ––––––>| trace buffer | print || . | |–––––––––––> || . ––––––>| 2K x 40 bits | buffer || +–––––––––––––––––+ | | ||–>–| trace channel 4 |–––––––>| | || +–––––––––––––––––+ +–––––––––––––––––+ || | || start | stop || +–––––––––––––––––+ +–––––––––––––––––+ +––––––––––––––––––+ ||–>–|trigger channel 1|–––––––>| |<–––––––>| external trigger | || +–––––––––––––––––+ | trigger | +––––––––––––––––––+ || . ––––––>| sequencing | (only TRFE) || . | | || . ––––––>| 4 level control | || +–––––––––––––––––+ | | interrupt ||–>–|trigger channel 4|–––––––>| |–––––––––––> || +–––––––––––––––––+ +–––––––––––––––––+ || | | || | | ||––processor bus | | || +–––––––––+ +–––––––––+ || | counter | | timer | || +–––––––––+ +–––––––––+ TRF Block Diagram NOTE: For the TRFE the number of trigger and trace channels is at the momen _____ limited to 2. The trace buffer is incremented to 8K trace words each of 72 bits. The diagram shows four trigger and four trace channels each able to react on address, data and status lines conditions on the processor bus, as qualified by the user. The selected processor bus cycles by the trace channels are stored in the trace buffer, whereas the trigger channels are used to start and stop the entry of trace information in the trace buffer. So called ”levels” are used to define the sequence of triggers required, to start or stop the trace. E.g. trigger 1, trigger 2 and trigger 4 have to come in sequence to start a trace otherwise nothing will happen. In addition to starting or stopping a trace, the level control is used to start or stop a HW–timer, or increment a counter. The overflow of the counter can itself be used to influence the sequence of triggers required to finally come to a HW–interrupt to MPTMON on reaching the last control level. For 80386 processors it is possible to link two TRFEs with a cable via which the tracer boards may transmit or receive signals. This may be used testing in an active/standby pair: one TRFE starts or stops tracing triggered by an event in the other CE. The generation of such an external trigger has to be defined in the trigger sequencing block as well as the action on this external trigger on the other CE side. The Trace Facility commands provided by MPTMON can be subdivided into three groups. The first group comprises the set–up of trace and trigger conditions which are: 013 211 31515 AAAA EA 83

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– – Reset the TRF software – Specify a trace condition – Specify a trigger condition – Specify a trigger level – Display all specified conditions whereby the second group encloses all commands which have access to the TRF hardware as follows: – Reset the TRF hardware – Load and Arm the TRF – Disarm the TRF to read counter and timer – Display the TRF status – Print the contents of the TRF trace buffer and the last group contains commands concerning TRFE formatting and TRF event handling: – Define 80386 selectors – Wait until final trigger reached NOTE: A new command has been introduced to allow MPTMON convertions from TRF _____ physical 32 bit addresses to logical addresses of the virtual address mode. The logical addresses are strongly required to convert the TRFE dump to symbolic addresses which match the compiler listing (see ”3.11.12 Define Selector” on page 95). When the TRF is not equipped, the commands of the second group are disabled, whereby the other MPTMON HW trace commands are not affected by this. The normal MPTMON syntax using position defined parameters, is not adequate for the rather complex TRF commands. Name defined parameters are used instead to ease the use of the listed commands. It is however strongly recommended to write your own TRF–macros to reduce the typing effort for often repeated TRF applications. Each Slave has got its own TRF parameter–block which is loaded incrementally from maximal 12, individual commands. The current contents is however always displayed as a whole and is only transferred to the TRF–hardware with the ”ARM” command.

013 211 31515 AAAA EA 84

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


+––––––––––––––––––––+ – | trace channel 1 | | |––––––––––––––––––––| | | 2 | | 4 independent TRACE CHANNELS |––––––––––––––––––––| | to specify what has to be ____ | 3 | | traced. |––––––––––––––––––––| | | 4 | | |––––––––––––––––––––| + ____________________ | trigger channel 1 | | |––––––––––––––––––––| | | 2 | | 4 independent TRIGGER CHANNELS |––––––––––––––––––––| | to specify when a trigger has ____ | 3 | | to be created. |––––––––––––––––––––| | | 4 | | |––––––––––––––––––––| + ____________________ | trigger level 1 | | |––––––––––––––––––––| | | 2 | | 4 TRIGGER LEVELS to specify |––––––––––––––––––––| | how to react on the occurrence ___ | 3 | | of a trigger. |––––––––––––––––––––| | | 4 | | +––––––––––––––––––––+ – TRF parameter block NOTE: It may take upto 16 commands to specify your trace completely. I _____ practice however, 4 to 5 are normally necessary, because many parameters are set up per default by MPTMON.

3.11.1 Reset software ______________________ Syntax: RES SOF Initialises MPTMON’s internal parameter–block with default values as follows: all trigger and trace channels are turned off; every trigger channel at the first trigger level is defined as ”final” (i.e. no sequence definition is applied).

3.11.2 Specify trace conditions ________________________________ Syntax: ONT [CHA] channel [,status] [,ADDR=start][,UPTO=end][,range][,access] [,VALUE=value][,MASK=mask][,object][,type][,match] channel an integer value in the range from 1 to 4 to select one of four independent trace channels.

013 211 31515 AAAA EA 85

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– status the keyword OFF turns the specified channel off. All other parameters are disregarded. start the lower boundary of an address range to be qualified (default 0000:0) and an optional range size specified using the keyword ”LEN”, for example: ”ADD=.FMM LEN 24K”. For a TRFE the addresses are checked against the actual descriptor contents. The trace range of a module should not be outside the descriptor limit. Otherwise a warning is displayed and the specified length is set to the limit. end the upper boundary of an address range to be qualified (default equals to the start–address value). If specified, it superseeds the length specification in the ”ADDR” parameter specification. For a TRFE the address is checked against the actual descriptor contents. range the keyword IN or OUT indicates that the addresses to be traced are resp. inside or outside the specified boundaries (default ”IN”). access qualifies the type of bus access cycles to be matched by one of the following keywords – ANY for all access types (default). – EXE for code access. – MEM for memory access. – REA for memory read access. – WRI for memory write access. – IOR for input–output read access. – IOW for input–output write access. data–value an integer value to specify the pattern on the data bus to be qualified for data transfers (default H’0). If specified, it sets the data–mask to H’FFFF (all bits valid). data–mask word mask to specify the associated data bits as don’t care (mask–bit 0) or validate (mask–bit 1). The default value is H’FFFF if a trigger value is specified, otherwise H’0000 is used. object the keyword BYTE, WORD or DWORD specifies that resp. only byte, word or doubleword access is qualified (default is BOTH = ”word or byte” access for the TRFB and DWORD for the TRFE). type the keyword EVEN, ODD or ALL indicates that only resp. even, odd or all addresses of the address range are qualified (default ”ALL”).

013 211 31515 AAAA EA 86

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– match the keyword MATCH or NOMATCH indicates that the condition holds for resp. all data values specified or all not specified values (default ”MAT”). For each individual channel, trace conditions for address, data and access code may be specified and stored in the parameter–block. The sequence of the parameters, except the channel–parameter, is arbitrary, but all parameters must fit on one command line. If a parameter is not specified, the default value is assigned. A trace condition matches only when address, data and status lines of the processor bus transfer cycle are all qualified against the specified trace conditions. NOTE: Currently we have the following restrictions for the TRFE board: _____ 1. Only two trace channels are available. 2. All data qualifiers (data–value, data–mask, object, type and match) are currently ignored by the TRFE board for this command. NOTE: If the specified type of bus access is not ANY or EXE, the MEMOR _____ trace–mode should be chosen (see ”3.11.7 Load and arm trace facility” on page 91). Example: ;trace everything on the bus ONT CHA 1, OUT, EXE ;trace all instructions executed by an FMM ONT 1, ADDR=.RTS+6, UPTO=.RTS+8934, EXE ;trace write access to a particular FCB (not possible with a TRFE) ONT 2, ADDR=.FCB+2*10+4 LEN 18T, WRI, VAL=0700, MAS=0F00

3.11.3 Specify trigger channel _______________________________ Syntax: TRI [CHA] channel [,status] [,ADDR=start][,UPTO=end][,range][,access] [,VALUE=value][,MASK=mask][,object][,type][,match] channel an integer value in the range from 1 to 4 to select one of four independent trigger channels. others see parameter description of the ONT CHA command. For this command all parameters are accepted by the TRFE board. The trigger channel command allows to specify an event (i.e. trigger) that may start or optionally stop a trace. Moreover, these triggers can be counted or used to perform elapsed time measurements. For each channel, trigger conditions for address, data and access code may be specified and stored in the parameter–block. The sequence of the 013 211 31515 AAAA EA 87

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– parameters, except the channel–parameter, is arbitrary. If a parameter is not specified the default parameter is assumed. A trigger condition shall occur when address, data and access code of a bus transfer cycle are all qualified against the parameters specified. NOTE: It is not allowed to specify two different triggers on the sam _____ address. NOTE: Only two trace channels are currently available for the TRFE board. _____ Example: ;trigger if a specified instruction is executed TRI CHA 1, ADDR=6500:8163, EXE ;trigger if any byte value is read except H’5 TRI 2, ADDR=.TCB+2*16, REA, VAL=0005, BYT, NOM

3.11.4 Specify trigger level _____________________________ Syntax: LEV [CTL] level [,status] [,CHA=channel][,NEXT=next_level][,counter] [,xmit][,timer!tracer][,reset!final] [,CHA=channel][,NEXT=next_level][,counter] [,xmit][,timer!tracer][,reset!final] [,....] level An integer value in the range from 0 to 3 to select one of four independent trigger levels. status the keyword OFF turns the whole trigger level off. On the other hand it is turned on automatically if at least one channel is specified for this level. The other, not specified channels have no effect. channel an integer value in the range from 1 to 5 (6 for TRFE) to select the reaction on the corresponding trigger channel or to specify the response to an overflow of the occurrence counter, which is treated as 5th trigger channel. For the TRFE the reaction on an external signal has to be specified using trigger channel 6. next_level each level from 0 to 3 may be specified as next trigger level after occurrence of the specified trigger channel. The final level is the default level for every channel specified in the command. counter the keyword COU is used to specify that the occurrence of the trigger shall be counted. If COU is omitted, no count is defined per default.

013 211 31515 AAAA EA 88

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– xmit the keyword XMT can be used to cause the TRFE to transmit an external signal. If XMT is omitted, no signal is transmitted per default. timer a timer with a 1MHz clock rate, derived from the 4 MHz processor clock is controlled by the keywords TON and TOF to start and stop the timer. This timer allows for elapsed time measurements between triggers. Execution time measurements are possible as well for TRFB and TRFE boards. For the TRFB board you use the keywords TON and TOF in combination with the TTR mode of the ARM command (see ”3.11.7 Load and arm trace facility” on page 91). For the TRFE board you just use the keyword TTR (Timer with TRace) instead of the TON keyword. Then the timer is running only if the TRF is tracing. tracer entering traced information in the trace buffer can be dynamically controlled by triggers. The keyword ETR and DTR will enable resp. disable the entering of actual traced information in the trace buffer. The tracer keywords are only effective for TRFB–tracer boards working in the ”trigger” mode (see ”3.11.7 Load and arm trace facility” on page 91). Note that the timer and tracer keywords are mutually exclusive for one trace channel at a certain level. reset the keyword RESET can be used to reset the timer, tracer, counter and trigger level. The timer has to be started again when required. Only the TRFB tracer board support this feature. It can be used to automatically restart a time measurement if certain conditions appear. The keyword NEXT is not effective in conjunction with the keyword RESET because the level ”0” is always entered when the trigger occurs, i.e. RESET performs implicitely ”NEXT = 0”. final the keyword FIN indicates that when reaching the fourth and last, so called final level, either the trace must be stopped (in pre–trace mode) and a HW–interrupt must be generated to MPTMON, or (in post–trace mode), the trace must be started and a HW–interrupt generated when the trace buffer overflows. The keyword FIN is assumed per default for any channel specified without the ”NEXT=” parameter. When the trace facility is armed it always starts in trigger level 0. The conditions to proceed from one level to another and the functions to be performed on a valid trigger, are specified for each trigger channel and stored in the parameter–block. The switch to the so called ”final” level causes a HW–interrupt which is routed to MPTMON to inform the tester about the occurrence of this interrupt together with the actual counter and timer values (refer to ”3.11.10 Wait till final level reached” on page 94 how to access these values).

013 211 31515 AAAA EA 89

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+ | L | | | | | | | | E | CHANNEL 1 | CHANNEL 2 | CHANNEL 3 | CHANNEL 4 | COUNTER | EXTERNAL | | V | | | | | |(only TRFE)| |–––+–––––––––––+–––––––––––+–––––––––––+–––––––––––+–––––––––––+–––––––––––| | | | | | | | | | 0 |–>0 TON |FIN TOF |–>1 COU|–>0 TOF COU|FIN TOF | | | | | | | | | | |–––+–––––––––––+–––––––––––+–––––––––––+–––––––––––+–––––––––––+–––––––––––| | | | | | | | | | 1 |FIN | |FIN | | | | | | | | | | | | |–––+–––––––––––+–––––––––––+–––––––––––+–––––––––––+–––––––––––+–––––––––––| | | | | | | | | | 2 | | | | | | | | | | | | | | | | | |–––+–––––––––––+–––––|–––––+–––––––––––+–––––––––––+–––––––––––+–––––––––––| | | | | | | | | | | 3 | | | | | | | | | | | | | | | | | +–––––––––––––––––––––|–––––––––––––––––––––––––––––––––––––––––––––––––––––+ | V possible entries are: –> next level COU increment counter TON/TOF timer on/off TTR timer on with tracing (only TRFE) RES reset the timer, counter and trigger level ETR/DTR enable/disable the trace FIN last, final level XMT transmit an external signal (only TRFE) Example: ;if the triggers specified by TRI CHA 3, TRI CHA 1 ;and TRI CHA 2 arrive in this sequence the final level ;should be reached LEV 0, CHA=3, NEXT=1 LEV 1, CHA=1, NEXT=2 LEV 2, CHA=2, FIN ;perform one shot time measurement between occurance ;of trigger specified by TRI CHA 1 and TRI CHA 2 LEV 0, CHA=1, NEXT=0, TON, CHA=2, TOF, FIN ;count number of triggers specified by TRI CHA 1 ;until trigger specified by TRI CHA 2 occurs LEV 0, CHA=1, NEX=0, COU, CHA=2, FIN

3.11.5 Display TRF parameter block ___________________________________ Syntax: TRF [DIS] 013 211 31515 AAAA EA 90

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Display the parameter–block comprising the trigger, trace and level settings. No information is displayed for channels and levels which are turned off. The diagram gives an idea how MPTMON formats the display for the level information. The keywords used are the same as in the LEV CTL command (see ”3.11.4 Specify trigger level” on page 88).

3.11.6 Reset hardware ______________________ Syntax: RES HAR The trace board is initialized and a self–test executed. This command is automatically executed at power–up and can be executed if the TRF does not operate as expected or does not operate at all. The command execution takes about 8 seconds for the TRFB and up to 2 minutes for the TRFE. It leaves the TRF in the disarmed state, i.e. the not–active state.

3.11.7 Load and arm trace facility ___________________________________ Syntax: ARM [TRF] [noload] [,BEGIN=counter][,trace–mode][,trigger–mode] noload by the keyword NOL the last loaded parameter–block is kept in the TRF trace–board and the TRF will only be armed again to lower the command execution time. The TRF trace–board continues tracing without clearing the trace buffer. counter an integer value to preset the occurrence counter before starting the trace operation (default 0). The counter can as well be used to generate a final trigger after the N’th occurrence of a trigger. In this case the counter has to be initialised with the negative value of N (–N). trace–mode the different tracer boards can operate in different modes to select the trace–words stored in the trace memory (e.g. only program branches, memory accesses or per default all words qualified). To select one of these trace modes which are described below, use the keyword NORMAL (default), CODE, BRANCH, MEMORY, ETR or DTR (for TRIGGER mode) or TTR. Note that some trace modes are not supported by every tracer board type. trigger–mode the keyword PRE or POST specifies whether the trace memory is to be written before or after the final trigger (default ”PRE”). The command ARM loads the parameter–block of the selected CE in the TRF trace–boards. The trace board memory of the selected CE is automatically cleared and the timer set to zero. Subsequently, the trace board operation is activated (armed). Depending on the number of conditions set, the command execution may take up to 6 seconds (up to 25 seconds for TRFE), so don’t get impatient. 013 211 31515 AAAA EA 91

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– If the NOL keyword is specified, the TRF is only armed without the other actions described before. The NOL option must be chosen if the selected target processor is on a blocking breakpoint or a debug–monitor breakpoint. This is due to the fact that certain blocked OSN–functions are required to load the parameter block in the TRF trace–board. Consequently, no new trace and trigger conditions can be loaded as long as the processor is blocked. In NORMAL mode all bus cycles executed by the processor (code and memory read/write) are stored into the trace memory if qualified by the trace channel parameters. In CODE mode which is not offered by the older TRFA tracer board, the read/write cycles are suppressed. Only the executed code cycles matching the trace conditions are stored into the trace memory. In BRANCH mode only executed opcode cycles related to branch instructions of the 8086 processor (CALL, JMP, RET, JE, etc.) are stored in two subsequent words of the trace memory. The first word contains the first opcode byte of the branch (source) instruction itself. The second word contains the first opcode byte fetch cycle of the next (destination) instruction. Even if either the source or destination instruction is not part of a qualification, the instruction is traced. This mode is not supported by the TRFE. In MEMORY mode only bus cycles related to qualified data transfers cycles are stored in two subsequent trace words. The first word contains the first opcode byte fetch cycle of the instruction that performs the data transfers. The second word has the qualified read or write cycle. This mode should be selected if the trace qualification specifies the type of access cycles: ”MEM”,”REA”,”WRI”,”IOR” or ”IOW”. Otherwise (trace cycles: ”ANY” or ”EXE”), the trace mode should be ”NORMAL” or ”BRANCH”. In the TRIGGER mode which is not offered by the older TRFA tracer–board, the tracer can be dynamically controlled by trigger channels. The entering of qualified trace information in the trace buffer is enabled by a trigger with the qualification clause ”ETR” resp. disabled with ”DTR”. This allows you to repeatedly start and stop a trace depending on certain triggers (refer to ”3.11.4 Specify trigger level” on page 88 as well). Use the keyword ”ETR” or ”DTR” to enter this trace mode and to qualify the tracer status upto the first trigger occurrence (only ”DTR” is supported by the TRFB board). In the TTR mode (Timer with TRace) which is also not offered by the older TRFA tracer–board, the timer is controlled by trace channels. The timer only runs when a trace is active, and naturally when it is started with ”TON”. This enables run–time measurements of for example an FMM–function excluding the OSN procedures called to execute this function (see example below). For a TRFE board the TTR function is handled in the LEV command and therefore not required with the ARM command. In the PRE–trigger mode, the trace operation starts immediately after the ARM command is executed. Writing into the trace memory is blocked after the final trigger occurs and the tester notified. In POST–trigger mode the trace operation starts at the occurrence of the final trigger and stops when the whole trace memory is filled. Only than, the tester is notified, i.e. not when the trace starts, but as soon as it stops. Example:

013 211 31515 AAAA EA 92

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– ; ; branches of FMM code ; ONT 1,ADD=.FMM LEN 32K ;qualify FMM code ARM BRA ;trace only branches ; ; start trace after 8 triggers ; ONT 1,OUT ;trace everything TRI 1,ADD=.OSN+625,EXE ;trigger 1 at OSN instruction LEV 0,CHA=1,COU,NEX=0,CHA=5,FIN ;count triggers, exit on overflow ARM POST, BEG=–8T ;start trace after 8 triggers ; ; execution time measurement (TRFB) ; ONT 1,ADD=.FMM LEN 10K ;specify the code area TRI 1,ADD=.FMM+62,EXE ;start point TRI 2,ADD=.FMM+89,EXE ;end point LEV 0,CHA=1,NEX=1,TON ;measure once from start to end LEV 1,CHA=2,TOF,FIN ;until end point ARM TTR ; ; execution time measurement (TRFE) ; ONT 1,ADD=.FMM LEN 10K ;specify the code area TRI 1,ADD=.FMM+62,EXE ;start point TRI 2,ADD=.FMM+89,EXE ;end point LEV 0,CHA=1,NEX=1,TTR ;measure once from start to end LEV 1,CHA=2,FIN ;until end point ARM

3.11.8 Read TRF counter and timer __________________________________ Syntax: DIS ARM This command gives access to the actual values of the TRF timer and occurrence counter as they are held in the TRF hardware. The counter value is given in HEX, the timer value is displayed decimal in units of seconds and microseconds. For a TRFE tracer board the execution of this command may take up to 25 seconds. NOTE: If the tracer board is currently armed, it will be disarme _____ automatically and stay in that state, i.e. it does not continue tracing. A ”ARM” command arms the TRF again.

3.11.9 Show TRF status _______________________ Syntax: SHO TRF

013 211 31515 AAAA EA 93

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– This command displays the actual status (armed or disarmed) of the TRF. Furthermore it shows the current level if the TRF is armed or the number of traced words in the trace buffer, the TRF timer and the occurrence counter if the TRF is disarmed.

3.11.10 Wait till final level reached ______________________________________ Syntax: WAI TRF [time] time The max. time specified in seconds to wait for a final trigger. Instructs MPTMON to wait the specified amount of seconds in the range from 1 to 3000 (50 minutes) until the final trigger level is reached (pre–trigger mode) or until the trace buffer is full (post–trigger mode). MPTMON will wait for ever if the time parameter is omitted. If the final trigger occurs, the wait state is left with or without any MPTMON generated display depending on the display option set (see ”3.19.3 Display of suppressed data” on page 125). If no final trigger occurs in time the wait state will be left without an error message. An indefinite wait state may be left with an error message by time supervision (see ”3.19.6 Set supervision time” on page 127) or, interactively, by pressing the ESC key. Registers are used to hold the counter and timer values to allow user formatted display of these values. The registers are: – RCX to hold the counter value in the range from 0 to H’FFFF. – RAX,RBX register pair to hold the timer value as a long integer (value in the range of 0 to H’FFFF,FFFF). I.e the time measured is about RAX * 65 msec.

3.11.11 Print TRF trace buffer _______________________________ Syntax: PRI [last] last the number of trace words to be displayed. Notice that the print of the trace memory always ends with the last traced word. Prints (displays) the last N words traced of the trace–buffer on the VDU. The display contains the address as issued by the processor during the associated bus cycle and the mnemonic of the executed instruction, the type of data access (e.g. REA or WRI) and the byte or word value during one data access cycle. In case of NORMAL trace–mode the full instruction code will be disassembled. The address is displayed as absolute address or nearest symbol less than the absolute address plus an offset if such a symbol is found. For a TRFE tracer board the execution of this command may take up to 25 seconds. NOTE: If the trace board is currently armed, it will be disarme _____ automatically and stay in that state, i.e. it does not continue tracing. A ”ARM” command arms the TRF again. 013 211 31515 AAAA EA 94

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Example: PRI 2D

3.11.12 Define Selector ________________________ Syntax: DEF SEL list–of–selectors list–of–selectors a list of valid selectors all seperated by commas. This command allows MPTMON convertions from TRFE physical 32 bit addresses to logical addresses of the virtual address mode. The logical addresses are strongly required to convert the TRFE dump to symbolic addresses which match the compiler listing. This command can only work on a 80386 target processor. Example: FET 111 DEF SEL CS,DS ;define code and data selectors of FMM 111 DEF SEL SEGM(.EH) ;define code selector of OSN

013 211 31515 AAAA EA 95

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.12 Display commands ______________________ These commands enable you to output and format information on the VDU screen. Seven commands are provided: – Clear screen. – Locate cursor. – Write text on the screen. – Define scrolling region. – Clear end–of–screen – Set output base. – Set input base. NOTE: Not all listed functions are supported by each VDU type. Refer to th _____ section ”4.2 Terminal Types” on page 140 for details.

3.12.1 Clear screen ____________________ Syntax: CLR [SCR] Homes the cursor and clears the screen. This is often used in macros to get a fresh screen to display formatted data structures. Example: CLR TIME ;the current time is displayed ;on a empty screen

3.12.2 Locate cursor _____________________ Syntax: LOC [CUR] row, column row The row number on the screen counting from 0 to 23. column The column number on the screen counting from 0 to 79. Positions the cursor on the screen. Any commands that outputs data, e.g. the TIME command, will start to display from the current cursor position. Any data written after the column 79 is lost. This command allows you to build a menu with text at fixed locations on the screen, without having to position the cursor by writing spaces etc. Example: 013 211 31515 AAAA EA 96

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– LOC 0,0 ;i.e cursor home LOC 1,35T ;position cursor TIME ;the current time is displayed

3.12.3 Write text __________________ Syntax: WRI [text ! expr] [,...] [,&] text A text string enclosed by single quotes. expr An expression that evaluates to an integer or pointer. & The ampersand ’&’ may be used to indicate that no carriage return line–feed sequence must be generated after writing the text. The write command is able to display any printable character or values formatted on the VDU screen. A single quote is generated for double quotes in a text string. The ’&’ concatenates text given in a set of WRI commands to one line. No check is made if the line exceeds 80 characters; if so, they are lost. Text strings are displayed in inverse video if they are enclosed by two special characters which are translated by MPTMON in the appropriate escape code sequences. To start an inverse video field the characters ’ ’ H’5E and to end an inverse video field ’~’ H’7E (on USA–ASCII keyboards the ’circumflex’ respectively the ’tilde’) have to be used. The WRI command keyword is not required if the first parameter is a text string starting with a quote. This may be useful for the definition of larger strings or forms. Example: WRI CS:IP WRI SS:SP WRI ’USER TEXT1’, WOR.ADDR+4, ’USER TEXT2’, & WRI POI MP+10, ’CONCATENATE’,& WRI .SYMBOL1, 1234 WRI BYT.TEXT LEN 8 ’ ONE COMPLETE OUTPUT LINE WITHOUT ANY EXPRESSIONS ’ ’ and another one in lower case’

3.12.4 Define scrolling region _______________________________ Syntax: SCR [REG] row–number Position the cursor at the first column on the specified row of the screen and disable scrolling of any information above this row. This can be used

013 211 31515 AAAA EA 97

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– to keep information on the top of the screen (e.g. a selection menu or global information) and work on the lower part of the screen. Example: SCR REG 10T ;locate the cursor as well CLR EOS ;clear line 10 to 24

3.12.5 Clear end–of–screen ___________________________ Syntax: CLR EOS Clears the screen from the current cursor position up to the end of the screen. Example: LOC CUR 1,10T ;locate the cursor CLR EOS ;clear line 10 to 24

3.12.6 Set output base _______________________ Syntax: BAS = H ! T ! A ! Y H The base used for output is hexa–decimal (default). An integer value displayed in this base uses 4 character positions. T The output base is set to decimal. Five character positions are used for the representation of an integer. A The output base is ASCII, the display of a byte occupies only one character position. Y The output base is set to binary. Eight character positions are used for the representation of a byte. Integer values are not supported. It allows you to display a value in the appropriate base within a WRI command, or to control the base for the replacement of an expression within an MMC command (see ”3.15 MMC interface commands” on page 110). On return of a macro execution, the original value is automatically restored. Example: BAS = H ;hexadecimal output base BAS = T ;sets decimal output base

013 211 31515 AAAA EA 98

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.12.7 Set input base ______________________ Syntax: SUF = H ! T ! Y H The base used for input is hexa–decimal (default). T The input base is set to decimal. Y The input base is set to binary. It allows you to enter or inquire all parameters in the appropriate base (suffix), or to control the suffix for the replacement of an expression within a MMC command (see ”3.15 MMC interface commands” on page 110). On return of a macro execution, the original value is automatically restored. Example: SUF = T ;sets decimal input base SUF = H ;hexadecimal input base

013 211 31515 AAAA EA 99

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.13 Library commands ______________________ MPTMON offers powerful facilities to call, put and get single macros and symbol tables into/from one or more libraries in order to overcome the problem of limited memory resources, and to protect them against Control Element or System restarts. Moreover, macros can be shared between testers and easily be maintained and archived on tapes and disk files. A library is implemented as one logical IOS file with a subfile structure, in which each macro or symbol table is a member (i.e. a subfile) within the library. The commands covered by this section are: – Initialize library – Select library file – Disable library calls – Display library directory – Put macro definition into library – Get macro definition from library – Delete macro definition from library – Put symbol table into library – Get symbol table from library – Delete symbol table from library – Compress and archive library For more details about the System 12 IOS see as well ”3.14.3 Include from SYSTEM 12 IOS” on page 108.

3.13.1 Initialise library __________________________ Syntax: INI LIB device, file device the IOS device number on which the library must be located. file the IOS file identity specifying the input file. Creates and initializes a library file to be ready for use. During the initialization MPTMON prints an opening bracket ’[’ (start of initialization) and a closing bracket ’]’ (end of initialization). In case of possible System 12 IOS errors see ”APPENDIX E. 12 IOS Completion Codes” on page 193 for the explanation of the error codes.

013 211 31515 AAAA EA 100

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– In order to not accidentally destroy an existing library comprising some macros and symbol tables, the command is put under password protection with its own password. You get prompted to enter the password’s value (CARE) any time the command is entered. The device type may only be DISK (logical device identities ’1’ or ’2’ for a single disk device, or the logical device identity ’1032T’ for a twin disk device) as random access to the library is required by MPTMON. A set of file definitions is predefined in the System (see ”4.3 Dimensioning” on page 141), so different libraries can be defined for different purposes, e.g. one library comprising MMC menus and one for system level test macros. All file identities with a number >= 960 and <= 965 may have maximum 256 members, otherwise space for maximum 1024 members is provided in the library directory. NOTE: The initialization and directory display of the large libraries i _____ therefore about four times slower than for the small ones. Example: INI LIB 2,960T ;using a single disk INI LIB 1032T,968T ;initialise a large library on twin

3.13.2 Select library file ___________________________ Syntax: SEL LIB [device,] file device the IOS device number on which the library is located. file the IOS file identity specifying the input file. Selects a logical file and a logical device for all subsequent given macro calls and library commands. I.e. if a macro call or macro display is made and the macro definition is not in the memory resident directory, the library selected with this command is used to fetch the macro definition (if present of course). This automatic invocation of macros from a library can be disabled with the command ”DIS LIB” (”3.13.3 Disable library calls” on this page). After a restart or reload MPTMON selects a default library on the logical device ’1032T’ and logical file ’969T’. Example: SEL LIB 962T ;select a library on the current disk SEL LIB 2,960T ;select the system test library

013 211 31515 AAAA EA 101

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.13.3 Disable library calls _____________________________ Syntax: DIS LIB The automatic invocation of macros from a library can be disabled to cope with the situation that the PLCE is not running, available or equipped (”3.5.3 Call macro” on page 42). This automatic invocation is disabled per default when a test–session is started, until a library is selected using the ”SEL LIB” command. Then, macros are automatically fetched from the selected library again and relation names are displayed for an interactive ”FET REL” command. Example: DIS LIB ;disable library calls

3.13.4 Display library directory _________________________________ Syntax: DIR LIB [[device,] file] device the IOS device number on which the library is located. file the IOS file identity specifying the input file. Selects a library (optional), and displays the library directory (list of library member names) at the VDU. The display is formatted such that eight entries are displayed on one line, sorted in alphabetic order, followed by another line if applicable. The directory display is divided into segment of max. 409 entries, each sorted on its own. So, if a library has 500 members, 2 lists are generated, and a particular member name may arbitrarily appear in one of the lists (this burden is put onto the user to save code and space in the MPTMON–Controller).

3.13.5 Put macro _________________ Syntax: PUT [MAC] macro–name [,...] macro–name the name of a macro to be put into the library. Puts one or more on–line macro definitions into the library under the specified macro–name(s) which are as well used as a library member name(s). The macro–name has to be a unique name which must not coincide with any other library macro–name or symbol table name. If a macro with the same name is already stored in the library, you are prompted if it should be replaced or not.

013 211 31515 AAAA EA 102

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– For every macro definition written the character ’&’ is displayed to indicate a successful operation. In case of any failure the number of ’&’ characters gives you the count of macros which have been successfully written into the library. Example: PUT MAC LINKS, TRUNKS, TCECNT

3.13.6 Get macro _________________ Syntax: GET [MAC] macro–name [,...] macro–name the name of a macro to be obtained from the library. Obtains one or many macro definitions from the library and places them in to the on–line macro directory for execution and/or display purposes. Macro definitions already defined on–line are not replaced by this command in contrast to the GET SYM command. If the name is a name of a symbol table member in the library the request is rejected. If the macro definition was deleted previously by accident, a warning message is displayed and the definition can be recovered by putting it back in the library again. Example: GET RESTART GET READ_GLS, WRITEDIR

3.13.7 Delete macro definition _______________________________ Syntax: DEL MAC member–name name the name of the library member to be deleted from the library. Deletes one macro definition from the library. An error message is displayed if a symbol table was stored under the specified member name. A successful delete operation is confirmed through the display of the character ’[]’. NOTE: The DEL command frees only the directory entry. The occupied space fo _____ member itself is not purged. Therefore the library file space will grow if a delete, put sequence is used. Also therefore, a macro definition deleted by accident can be recovered (see ”3.13.6 Get macro” on this page). Example:

013 211 31515 AAAA EA 103

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEL MAC FCB ;delete the macro ’FCB’

3.13.8 Put symbol table ________________________ Syntax: PUT SYM name name the name of the symbol table to be created in the library. Puts the current on–line symbol table into the library under the specified member name. This allows you to have more than one symbol table in the library, e.g. to have a symbol table for every GLS or test environment. They are identified by their library member name. The name has to be an unique name which must not coincide with any other library macro name or symbol table name. While writing the symbol table the characters ’[&]’ are displayed to indicate a successful operation. Example: PUT SYM PTCE_SYM

3.13.9 Get symbol table ________________________ Syntax: GET SYM name name the name of the symbol table to be retrieved from the library. Obtains the symbol table specified by the library member name from the library and replaces the current on–line symbol table by the obtained one. If the name is a name of a macro definition member in the library the request is rejected. Example: GET SYM PLCE

3.13.10 Delete symbol table ____________________________ Syntax: DEL SYM member–name name the name of the library member to be deleted from the library.

013 211 31515 AAAA EA 104

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Deletes one symbol table from the library. An error message is displayed if a macro definition was stored under the specified member name. A successful delete operation is confirmed through the display of the characters ’[]’. CAUTION: The DEL command frees only the directory entry. The occupied spac ________ for member itself is not purged. Therefore the library file space will grow if a delete, put sequence is used. Example: DEL SYM PTCE ;delete the symbol table for the PTCE

3.13.11 Compress library _________________________ Syntax: COM LIB device–number device number the logical device number of a scratch device where the compressed library is stored. Compresses the selected library onto a scratch device (strongly recommended is a magtape drive) thereby purging the space used by deleted members. A side effect is, that a compressed copy of a library is provided, which can be used for archiving purposes. While the compress is ongoing, the character ’&’ is displayed for every successful block transferred. In case of any failure the compress has to be repeated. Only if the compress was successful, the compressed library may be copied back to the original source device using a normal ORJ COPY–FILE:1=SCRATCH–DEV,2=ORIGINAL–DEV,3=LIBRARY–NUMBER; If a disk was chosen as scratch device, the compressed library can be copied back to the original device by compressing it back again after changing the selected library. Example: COM LIB 6 ;compress using magtape 1 COM LIB 2 ;compress using disk 2

CAUTION: Do not use a scratch device which maps onto the original device ________ otherwise a deadlock may occur which is only solved after process abortions of the IOS processes.

013 211 31515 AAAA EA 105

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.14 File handling commands ____________________________ MPTMON can include files from different devices –like S12 disks, S12 tapes and VAX devices– whereby the full set of MPTMON commands can be executed. This feature allows the automatic regression testing of ORJ’s, patching memory locations, including macro definitions edited on a VAX , etc. In order to avoid the redefinition of macros and symbols after a system failure before the symbols and macros are put into a library, MPTMON is able to save and retrieve the test environment (i.e. macros and symbols) of a test session quickly through the System 12 IOS. The commands described hereafter are: – Save macros and symbols on System 12 IOS – Retrieve macros and symbols from System 12 IOS – Include from System 12 IOS – Start batch to include from System 12 IOS

3.14.1 Save macros and symbols _______________________________ Syntax: SAV [IOS] device [,file] device the IOS device number on which macros and symbols are saved. Device numbers are configuration dependent; usually, the two disks in both Peripheral and Load Processors are identified by ’1’ and ’2’. file the IOS file identity specifying the output file. Saves all symbols and macros resident in MPTMON’s on–line directories in an IOS file. This enables you to retrieve your test environment after a session termination or a PTCE restart, as all macro and symbol definitions are lost if they are only kept in dynamically allocated memory (it may have cost you a considerable amount of time to set up your test environment by inclusion from VAX). It is recommended not to use twin devices to store your environment, as single devices offer enough security and twins will slow down the execution of the command. The default file 950T is used if the second parameter is omitted. MPTMON entertains you while writing the file, to indicate that the command execution is in progress: – An opening square bracket ’[’ indicates that the file is open. – An ampersand ’&’ is displayed for every data block written. – A closing square bracket ’]’ indicates that the file is closed and the SAVE operation completed.

013 211 31515 AAAA EA 106

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– NOTE: A set of scratch files is predefined in the and must be share _____ by all testers. These files have all the same IOS read/write authorization keys (for READ: ’AR’ and for WRITE: ’JR’). If you like to be sure that nobody overwrites ’your’ file, you have to create your own file description on–site using the MMC command CREATE–FDB or modify the WRITE authorization key of the scratch file used, though the latter option should be avoided (see ”4.3 Dimensioning” on page 141 for the default set of scratch files). NOTE: The data format of the SAVE file is pure ASCII text, therefore th _____ device type on which the environment is saved can be any device type provided by the IOS; i.e. the symbols and macros can be ’saved’ as well on a printer, though of course not be retrieved from there. If you use a private magtape as SAVE medium, you are able to back up or transfer your test environment as well. Example: SAV 1 ;save on disk 1 and the default file 950T SAV 6,953T ;save on magtape and specified file

3.14.2 Retrieve macros and symbols ___________________________________ Syntax: RET [IOS] device [,file] device the IOS device number from which macros and symbols are retrieved. file the IOS file identity specifying the input file. Retrieves all symbols and macros previously saved from MPTMON’s directories. Retrieve can be used after a session termination or abortion to restore a test environment, though may be executed any time of course. If an error occurs, e.g. MACRO ALREADY DEFINED, the retrieve process is immediately aborted. For more information on files and devices refer to the SAVE command description. The RETRIEVE command is functionally identical to the INC IOS command, as the file generated by the SAVE command contains only pure ASCII text without any control information; however, the file is not read block–wise, but as one entity and the tester is kept informed on the progress of the command execution as outlined in the SAVE command description. Example: RET 12T ;retrieves from e.g. tape 2, file 950T RET 12T,952T ;retrieves from e.g. tape 2, ;last generation of file 952T

3.14.3 Include from SYSTEM 12 IOS __________________________________ Syntax:

013 211 31515 AAAA EA 107

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– INC [IOS] device, file device the IOS device number from which a file has to be included. file the IOS file identity specifying the file to be included. Read and execute MPTMON commands from the specified file. MPTMON reads as long as no error occurs till the end of the file is reached. IOS files can be used to e.g. keep ORJ regression test files (called MPTMON Script files). The advantage of IOS files compared to files located on other external devices like VAX–disks is, that they allow fast access via the digital switching network rather than via slow 1200T baud lines. IOS files are available immediately after a system init, if they have been brought onto the SLT. NOTE: MPTMON reads the file block–wise, i.e. for every block, the file i _____ opened, a data block read and immediately closed to ensure that the IOS does not close the file forcibly, if the processing of the file takes too long. Furthermore, it is ensured that a restart of the PLCE does not directly impact the file processing due to a loss of the message links. In case of IOS failures error messages are issued followed by an error code as defined in ”APPENDIX E. System 12 IOS Completion Codes” on page 193. The ESC key can be pressed any time to abort the processing of the file. Example: INC IOS 2,950T INC IOS 1,.SCRIPT

3.14.4 Start batch process to include from SYSTEM 12 IOS _________________________________________________________ Syntax: BAT [INC] device, file [,user_param] device the IOS device number from which a file has to be included. file the IOS file identity specifying the file to be included. user_param an integer value which is passed in the register RDX. MPTMON creates a batch application to read and execute all commands from the specified IOS file. This batch process reads as long as no error occurs till the end of the file is reached, then it terminates. The originator is notified by an event message containing the last internal error code (IEC) of the batch process. If the specified file matches an MPTMON library file the batch process executes by default the macro with the name BATCH. This gives some advantages during testing because a macro may be easier modified using the MPTMON editor function.

013 211 31515 AAAA EA 108

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– NOTE: As this batch process has no VDU assigned to it one of the firs _____ statements should be a ”LIS ON” command to allocate an output device (refer to ”3.1.3 List On” on page 24). Example: BAT INC 2,950T

3.14.5 Abort batch process ___________________________ Syntax: ABO BAT Aborts all active batch processes started from this session.

013 211 31515 AAAA EA 109

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.15 MMC interface commands ____________________________ MPTMON offers you –besides its own commands with its own syntax– access to the normal MMC Subsystem. Using MPTMON to enter MMC commands offers a set of useful features on top of the normal System terminal, e.g. – Embedding of MMC commands in macros, offering parameterized MMC commands as well as reduced operator typing effort for often used commands. – Compound dialogue files can be easily edited, maintained and executed. – Automatic system test at ORJ level is offered using compound dialogue files and report verification. – MMC commands can be entered in quasi menu–mode. – Task definitions (a set of MMC commands which has to be entered as a group) can be made using macros. MPTMON provides a command to issue one MMC command in the normal interactive mode. After entering this command, MPTMON becomes more or less transparent for the text lines entered. This text is passed unchanged to MMC as operator input until the MMC dialogue is finished. MMC responses and reports are output as on the normal system terminal. For macro, or batch file execution of MMC commands, MPTMON provides a feature to submit a single job in the system after which the normal MPTMON mode is resumed. This allows operator task and menu definitions by means of simple macros. Any incomplete or incorrect MMC commands which are entered via MPTMON (causing MMC to prompt for corrections) are handled by MPTMON in the transparent, interactive mode; i.e. if an incorrect MMC command was read from an include file, MMC prompts are directed to the VDU and corrective input is read from the keyboard and not from the include file. Reading from the include file resumes as soon as the MMC command is accepted or cancelled. NOTE: Any command line, irrespective if directed to MMC or MPTMON must b _____ terminated by a carriage return or ENTER key. Although the MMC terminators are recognized by MPTMON to build a complete MMC command from one or a set of text lines, each line must be terminated by the MPTMON end of input delimiter: carriage return. The MMC responses and ORJ reports are presented in the same format as on a System terminal. On successful submission of a job in the system, the job sequence number ’JSQ’ keyword is set up (providing options for command confirmation). Only the JSQ of the last job submitted can be accessed. Similarly, the report reference number ’RRN’ and report sequence number ’RSQ’ keywords are set up on reception and display of a ORJ–report. Expressions within MMC input ____________________________ The full expression capability of MPTMON is also available for MMC dialogue input. This is helpful in cases where the same command has to executed in a loop, whereby one parameter argument has to be incremented, or actual data is read from a table out of memory using the memory commands.

013 211 31515 AAAA EA 110

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– An expression within a MMC command is recognized as a text string enclosed by parentheses and preceded by a percent character ’%(...)’ All those strings are evaluated as integer expressions and the original text string is replaced by a representation of the evaluated value. The output base used is the one previously specified by a BASE command (see ”3.12.6 Set output base” on page 98). Leading spaces in decimal representations are suppressed. Example: .COUNT = 0 BAS=T COU 10T <DISPLAY–FDB:FILEID=%(.FIRST + WOR .IDS + .COUNT); .COUNT=.COUNT+1 END which displays 10 File Descriptor Blocks, whereby the file identity is evaluated from a specified first one plus an entry out of a table within memory.

3.15.1 Interactive MMC commands ________________________________ Syntax: MMC The command MMC causes a logon to the MMC–translator. If the command is entered for the first time, MPTMON prompts for a password, which is not displayed and stored in MPTMON’s local data. This password is then used in all subsequent MMC commands until it is modified by the command SET PSW (refer to ”3.15.3 Set global MMC password” on page 113). After the logon to MMC is done, MMC will prompt for dialogue input in the normal way. MPTMON then collects the input strings until a MMC syntactical terminator is found and will sent them in one input–buffer to the MMC–translator where the syntax checks are performed. In case of any error, MMC prompts for corrective input, and so on, until the command is submitted in the system or cancelled. As soon as the MMC dialogue is completed, i.e. one command is entered without errors is the system, MPTMON automatically enters a wait state to accept a System report. If no report is received within 2 minutes, MPTMON returns to its normal interactive mode, ready to accept the next command. NOTE: If you define the text string ”MMC” concatenated with a carriag _____ return on a programmable PF–key of your terminal, this allows you to do a one keystroke logon to the MMC–translator, reducing your typing effort considerably. Example: MMC ;enter interactive MMC mode PASSWORD: ;MPTMON prompt (only done once) <command: <parameter,parameter <last–parameter; 013 211 31515 AAAA EA 111

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.15.2 MMC commands in macros ______________________________ Syntax: [<password>] <text–1 <text–2,delimiter; password An optional password string to be used instead of the global password for the ORJ command. text Text to be passed to MMC as dialogue input upon the recognition of a MMC–terminator. This terminator must be the last character of a text–line. Any command line starting with the MMC prefix character less than ’<’ is considered as MMC dialogue input text and will be sent to the MMC dialogue translator. A line terminating with a larger than ’>’ character, is taken by MPTMON as a logon request to MMC using the password embedded in the ’<’ and ’>’ characters. This allows you to logon to MMC without being prompted for a password. If this logon string is omitted, MPTMON will automatically log on using the last entered password in the MPTMON command ’SET PSW’ before any dialogue input text is sent to MMC. Moreover it is possible to embed the slash and a destination for a remote MMC access from a NSC. If only a slash is given MPTMON prompts interactively for the destination. For details about the remote MMC handling please read the description of the command ’SET PSW’. After the logon is executed, MPTMON will collect dialogue input lines starting with the ’<’ character until a MMC input terminator is detected. If so, the collected text will be sent to MMC for syntax check and job submission. Any corrective input required is directed to the VDU, i.e. handled in the interactive mode. Example: DEF MAC TASK <psw> ;explicit logon to mmc <307:1=%0,2=%1; ;issue command 307, using macro EM ;parameters as input values. ; DEF MAC DISABLE ;disable a SBL BAS=T SET PSW ;prompt for a global password <6:1=0,4=CTLE,5=H’000D,6=1,7=0; <53:2=3,1=%(JSQ); WAI REP EM

013 211 31515 AAAA EA 112

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.15.3 Set global MMC password _______________________________ Syntax: SET PSW This command defines or modifies the default password used in macros for an MMC command to logon to the MMC translator (see ”3.15.2 MMC commands in macros” on page 112). MPTMON prompts for the password and stores it in MPTMON’s local data. The password normally has to be entered without any terminator key. Example: SET PSW ;modify MMC password PASSWORD: ;MPTMON prompt

MMC access from a NSC to a remote exchange is also provided by MPTMON. In this case you have to enter the slash character ”/” after the password. Then for each MMC access MPTMON prompts for the destination of the remote exchange. If only a <CR> is entered as destination the MMC access is routed to the local exchange. If a valid site–name is given MPTMON converts this to a NSC site–id using the relation R_SITELIST and transfers this MMC command to the remote exchange. The NSC site–id for the remote exchange is used only for this MMC command. If the destination isn’t found in the relation R_SITELIST, the MMC command is aborted with an error message. Example: MMC DESTINATION:

It is also possible to store the NSC site–id in MPTMON’s local data by entering the slash and the destination after the MMC password. Then each following MMC access is directly transfered to this remote exchange using the stored parameter. NOTE: For the destinations ’PLCEA’ and ’PLCEB’ the MMC access is routed t _____ the local (possibly isolated) P&L with the network address ’C’ or ’D’ respectively.

3.15.4 Wait for a report _________________________ Syntax: WAI REP [time] time The max. time specified in seconds to wait for a report. Instructs MPTMON to wait the specified amount of seconds in the range from 1 to 3000 (50 minutes) until a report is received, or to wait indefinitely if the time parameter is omitted. If no report is received in this time the wait state will be left without an error message. An indefinite wait state

013 211 31515 AAAA EA 113

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– may be left with an error message by time supervision (see ”3.19.6 Set supervision time” on page 127) or, interactively, by pressing the ESC key. Reports from an ORJ function are only displayed on the screen if they would be displayed on the System terminal as well. It is possible to suppress the report display and keep the report in binary format as generated internally in the system without translating it into ASCII text strings. This allows evaluation of the report contents and/or user formatted report display (refer to ”3.19.9 Suppress MMC translation” on page 128). The Report Buffer keyword ’RBF’, the Report Reference Number ’RRN’ and the Report Sequence Number ’RSQ’ are provided to check the report received (see ”2.2 Key–words” on page 13). Text can be written, or a compound dialogue can be aborted, if the RSQ value differs from the JSQ value, or if the RRN value differs from the expected report reference number. Example: REPEAT WAI REP ;indefinite wait state IF RSQ = JSQ AND ;check if expected report RRN = 360T WRI ’*** EXPECTED REPORT RECEIVED ***’ END WHILE JSQ<>RSQ; END

3.15.5 Verify a report _______________________ Syntax: VER REP [text–string–list] text–string–list A list of max 10 text strings fitting on one line. Puts MPTMON in a indefinite or time supervised wait state (see ”3.19.6 Set supervision time” on page 127) until a report is received whose Report Sequence Number ’RSQ’ matches the Job Sequence Number ’JSQ’ of the last job submitted by MPTMON in the system. The ESC key must be used to exit from this state if no report is sent to MPTMON with a matching RSQ. Reports from an ORJ function are only displayed on the screen if the operators input–device routing flag is set in the relation ”output set”; i.e. when the report is routed back to the input device where the ORJ was generated. A simple verification of the report contents can be made by MPTMON while displaying the report. The text strings have to be present in the report in the same sequence as specified in the command; if not a warning message is displayed. For more complicated string analysis the normal WAI REP command has to be used (see ”3.15.4 Wait for a report” on page 113) either in conjunction with the SCAN command and the keyword RBF (refer to ”3.17.3 Scan table” on page 119) or with the no–translation option set (refer to ”3.19.9 Suppress MMC translation” on page 128).

013 211 31515 AAAA EA 114

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Example: VER REP ’CPL_CODE = OK’,’EQ_NUMBER = 304’,’NO = 0360’ VER REP ’COMMAND EXECUTED’,’NO = 0228’ VER REP ’ SUCCESSFUL’

013 211 31515 AAAA EA 115

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.16 Event handling commands _____________________________ Many actions triggered through MPTMON commands do not respond immediately, these responses might arrive later asynchronously. The following is a list of commands dealing with those type of responses, called events: – Check event presence – Wait for events – Wait for events time limited – Wait for a breakpoint match – Wait for a message – Wait for a report – Wait for a final trigger The latter four commands handle specific, expected events and are therefore described together with their related event triggering commands in previous sections. Hereafter are only those commands outlined which do not handle a specific event, but any asynchronous event occurrence. They are mainly meant to be used in a batch type of operation to check if an event is outstanding. In the interactive operation mode, events are automatically handled upon command completion, before reading a new line. However, if an asynchronous event receives while reading from a keyboard, the read command is aborted, any character typed ignored, and the event presented to the tester. The keyword EVC enables you to obtain the type of the last event occurred. The assignment is as follows: 0 no event 1 breakpoint triggered 2 message received 3 report received 4 TRF final interrupt 5 overlay FMM downloaded 6 timeout 7 debug monitor entered 8 batch job terminated 9 path release

013 211 31515 AAAA EA 116

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.16.1 Check on event presence _______________________________ Syntax: EVE Instructs MPTMON to check and process any asynchronous event present. The basic purpose of this command is to clean up the MPTMON message defer queue during macro or compound command execution.

3.16.2 Wait for events _______________________ Syntax: WAI [EVE] [time] time The amount of time in seconds how long MPTMON shall wait until an event occurs. Instructs MPTMON to wait the specified amount of seconds in the range from 1 to 3000 (50 minutes) on any asynchronous event, or to wait indefinitely if the time–parameter is omitted. The value of EVC is set as before. Example: WAI EVE 10T ;WAIT 10 SECONDS UNTIL AN EVENT OCCURS IF EVC = 3 WRI’******** REPORT RECEIVED *********’ END

3.16.3 Wait for events time limited ____________________________________ Syntax: WAI TIM time time The amount of time in seconds how long MPTMON shall wait. Instructs MPTMON to wait the specified amount of seconds in the range from 1 to 3000 (50 minutes). All events received within this time are accepted, but they do not cause an exit from the WAIT state. Example: WAI TIM 10T ;WAIT 10 SECONDS

013 211 31515 AAAA EA 117

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.17 Work areas ________________ In more sophisticated applications, quite often the need arises for work areas to keep special tables, to perform parameter analysis, etc. MPTMON offers some commands to get, return and process work areas. These work areas are user buffers of 2048 bytes, and dynamically assigned within the PTCE. Only one is predefined at the start of an MPTMON session and does nor have to be asked for: the Local Work Area with the name: ”LWA”. This one is always available. It is foreseen as a scratch buffer for internal macro processing. Other work areas should be used to keep static data like configuration tables, syntax tables, etc. Access to a work area does not need access to a target processor (here PTCE) via an UCP. Therefore processing data in a work area is much faster than processing the same data in a remote processor. For this reason, it may often save macro execution time if data is first copied into a work area and analysed afterwards. The commands associated with work areas are: – Get a user work area – Copy into the local work area – Scan a work area – Return a user work area – List the assigned user work areas NOTE: A special work area, the Call Buffer –CBU–, is defined in this documen _____ (”3.9 Call commands” on page 65), but its application differs from the user work areas described in here. One major difference is that the CBU is located in the target processor, and requires therefore an active CE in order to be accessed.

3.17.1 Get user work area __________________________ Syntax: GET UWA .name,... name Unique name of the symbol to be defined. Define one or more symbols and assign each a pointer value equal to the address of a free user buffer of 2K byte. Read and write access to such an area does not need a target processor activation because a UWA is located in the PTCE. The symbol assigned to a UWA can not be redefined or removed as for normal symbols (see ”3.4.1 Define symbol” on page 37). You must return the UWA in order to remove the associated symbol. Access to a UWA is made as if it was a normal symbol. Note: the local work area has a keyword assigned to it (”LWA”) and access to that work area is made without the symbol identification ”.”. Example:

013 211 31515 AAAA EA 118

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– GET UWA .CONF_TAB ;get work area WOR.CONF_TAB=1,2,3,4 ;initialise work area BYT.CONF_TAB+8=’ABCD’ ;text in work area IF BYT.CONF_TAB+8<>’A’ ’INITIALISATION FAILED’ END DEF.@LWA=LWA ;define symbol lwa with value ;of keyword LWA WOR LWA=1,2,3 ;modify LWA WOR .@LWA LEN 3

CAUTION: No checks are made if the addressing is within the 2K rang ________ assigned to a UWA. Consequently you can simply destroy the contents of other user buffers in the PTCE.

3.17.2 Copy memory ___________________ Syntax: COP address, no–bytes [,destination] address The address of the first byte to be copied. no–bytes The number of adjacent bytes to be copied. destination A symbol assigned to a user work area (UWA). This utility command allows you to copy max 2K bytes from any memory location into a user work area (UWA) within the PTCE for further processing. If the destination parameter is missing, the local work area (LWA) is taken as default. This command is provided to speed up processing of larger amounts of data (e.g. to scan for certain strings) without the need to access the target processor every time. Moreover some time is saved compared with a macro that performs the same function using the REPEAT and memory modify commands. This command relates to other commands working directly on local work areas, like ”3.17.3 Scan table” on this page. Example: COP A000:0,1K ;copy 1024 bytes into LWA COP MSG,64T ;copy the last received msg

3.17.3 Scan table __________________ Syntax: SCA [TAB] table–addr, step–size, nbr–elmt, elmt table–addr The start address of a table in the LWA or a UWA from where scanning should start.

013 211 31515 AAAA EA 119

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– step–size The number of bytes of one element in the table. With this offset the next scan starts. nbr–elmt The number of elements in the table. elmt A character string or integer value to be searched in the table. The SCAN command scans a table that must be located in a MPTMON work area (the local work area: ”LWA”, the report buffer: ”RBF” or a user work area obtained with ”GET UWA”) for a certain element. The element can be a string, integer or even an array of values. NOTE: The COPY command (”3.17.2 Copy memory” on page 119) can be used t _____ load the LWA with the table. Some registers are used to return result data: – DS:SI has the address in the work area where the element was found. – RCX has the actual element number. If RCX has the value 0, no matching element was found. – RDX has the relative offset in the work area where the element was found. Example: SCA LWA,2,1K,1234 ;scan if the value 1234 is in the LWA SCA RBF,1,2K,’CONFIRM’ ;scan a report buffer for the string ’confirm’ SCA .CMDTAB,4,20,’abcd’ ;scan for char. string ’abcd’

3.17.4 Return user work area _____________________________ Syntax: RET UWA .name,... name Name of the UWA to be returned. Return one or more UWA’s (i.e. user buffer) to the OSN and remove the associated symbols from the symbol stack. The symbols associated with UWA’s can not be removed with the normal symbol handling commands (see ”3.4.4 Remove symbol” on page 39). Example: RET UWA .CONF_TAB,.SEC_TAB ;return work area

NOTE: The local work area –LWA– can not be returned, as it is alway _____ available per definition.

013 211 31515 AAAA EA 120

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.17.5 List user work areas ____________________________ Syntax: UWA [LIS] Lists all symbols associated with a user work area and their values. The fix assigned Local Work Area –LWA– is not listed. Example: UWA

013 211 31515 AAAA EA 121

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.18 Resident macro tables ___________________________ A build–in–macro is exactly the same as a macro, but stored in write–protected memory at load time. I.e. they can not be modified and are always available to the tester. These build–in–macros appear to the user almost as if they were MPTMON commands. Their use is for special applications having their own user–guides (e.g. feature exerciser) where MPTMON is only used as a vehicle to implement certain functions. As such, build–in–macros can be considered at a higher level of abstraction as ”user defined commands” and executed as such. Consequently, they are sometimes called ”macros” and sometimes ”commands” depending on the user point of view. In general these build–in–macros are designed as normal macros. A set of such macros can be collected into a GLSC load format file using an utility program on the VAX. This file (if present on the SLT) can be loaded into the PTCE at system load time as an unaccepted patch file or even as a normal FMM assuming that an appropriate dummy descriptor has been defined. In the latter case, ”FET FMM” gives you the start address of the table. If the VAX utility is not available, a MPTMON macro can be used to generate a build–in–macro table in memory (by copying the resident macro directory to a write protected overlay segment; e.g. ”A.11 Command Table Generator Macro.” on page 180). After doing so, macros do survive a PTCE restart, though of course not a PTCE reload.

3.18.1 Select macro table __________________________ Syntax: SEL TAB address address The address where the macro table is loaded. This command selects a macro table in memory. This table is then scanned whenever a macro is called for execution. The sequence in which MPTMON scans the different tables and libraries to find a macro (refer to ”3.18.2 Execute build–in–macro” on this page) is as follows: 1. The ”normal” memory resident macro directory. 2. A macro table (if one is selected) 3. A macro library on disk (if one is selected). Consequently, it is possible to have multiple macros with the same name, but with different functions in different tables or libraries, which can be individually invoked by selecting the appropriate table or library.

3.18.2 Execute build–in–macro ______________________________ Syntax: macro–name:[actual–parameter–list]

013 211 31515 AAAA EA 122

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Fetches a macro definition from MPTMON’s selected table (or if not found there) from a selected library and execute it. To execute a build–in–macro (considered as a user defined command), enter the macro name followed by a colon ’:’ and its parameter list. NOTE: This User Guide describes two different ways to call a macro: as _____ MPTMON macro (refer to ”3.5.3 Call macro” on page 42), or as a user defined command. They are in fact treated the same and are functionally identical though the description of these commands suggests that they are different. Practically macros and user–commands can be invoked in the same way, with the same syntax. The syntax outlined here, is chosen to differentiate between normal macro–syntax as defined by ICE86 and other applications using MPTMON more or less as a vehicle to implement another ”language”.

3.18.3 Directory macro table _____________________________ Syntax: DIR TAB [address] address The address where the macro table is loaded. Selects a macro table (optional), and displays the names of all macros defined in the macro table. These macros are automatically invoked if no macro name with the same name is present in the macro directory (refer to ”3.5.8 Display macro directory” on page 44).

013 211 31515 AAAA EA 123

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.19 Run time options ______________________ Some run time options can be selected to change the default operation of MPTMON or to address special functions. The default options are always set after a PTCE restart or reload. The options are: – Setting the authorization for particular commands. – Display of the selected CE in the prompt string. – Display of data which is normally suppressed. – Selection of display formats. – Setting of trace length. – Setting of command supervision time. – Continuation on errors. – Setting of menu mode. – Suppression of MMC report translation. – Setting of operation modes. An additional command is designed to display all currently selected option.

3.19.1 Command authorizations ______________________________ Syntax: SET AUT Request to set the CE access authorization. MPTMON prompts for a password which is not displayed. RES AUT Disables the authorization (default). CE access commands are put under password control, because their execution may result in catastrophic failures. E.g. modifications in the OSN code or setting of breakpoints in the OSN may lead to a sanity timer run out causing a processor restart or reload. This authorisation is also required to change the contents of a macro library except the default library (960T) which is taken as a scratch library. NOTE: There is another set of commands which are password protected but no _____ covered by this option. Their passwords have to be entered every time when the command is to be used. The actual values of the passwords are fixed and can be obtained from the author or any qualified user.

3.19.2 Display of selected CE in prompt string _______________________________________________ Syntax:

013 211 31515 AAAA EA 124

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– SET PMT Display the network address of the target CE in MPTMON’s prompt string for command input. RES PMT Suppresses the display of the target CE in every prompt string. In the default operation you are prompted on the VDU with the larger sign ’>’ to input a command. This command is directed to the current selected processor in case of a CE data access (refer to the operation of the ACT command in ”3.2.1 Activate Control Element” on page 26). The selected CE is only displayed on request using the CE command. Some testers however prefer to always have the target processors for their command being displayed. This runtime option, if set, will generate in each command input prompt string the network address of the selected processor. If an OBC is selected the network address will be followed by the OBC number separated by a colon. The prompt string will be extended by ’_BRP>’ if a process is on breakpoint or by ’_DEB>’ if the debug monitor is entered.

3.19.3 Display of suppressed data __________________________________ Syntax: SET DIS Display certain information which is normally suppressed. RES DIS Suppresses display of certain MPTMON messages (default). Certain data is usually not displayed by MPTMON to be able to display only the information as generated and formatted by a macro or as required by the user. The information normally suppressed is: – Text included from include files. – A message altered, sent or received by MPTMON as a result of an ALT, SND or RCV command. – GSM name of the module fetched by an FET FMM or FET SSM command. – Register values when a breakpoint is matched as a result of a WAI BRP or GO command. Note that the register values can be displayed at any time using the REG command (refer to ”3.7.6 Display / modify registers” on page 57). – TRF timer and counter as a result of a WAI TRF command. The timer and counter values are stored in registers (see ”3.11.10 Wait till final level reached” on page 94).

3.19.4 Message and trace formatting ____________________________________ Syntax: SET HEAD [line–size] Only parts of a trace item or a message (e.g. message header and the first 4 parameters) are displayed on one line. An optional parameter line–size (range 0 to 80T) specifies the number of characters of this line to be

013 211 31515 AAAA EA 125

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– displayed, thereby providing a means to customize the display to the tester’s need. The command SET HEAD shortens the display of a SW trace dump and the display of a message to provide the tester with a condensed, easy to read overview of all traced items (or messages) by restricting the display to the most essential information on one line or even a part of a line when the line–size is specified. The line size required for a message display are: 1. routing number in decimal (ls=5) 2. msg type using a three character abbreviation (ls=10) 3. network address where message traced (ls=15) 4. source process identity (ls=25) 5. destination process identity (ls=35) 6. length, routing, and audit bits (ls=40) 7. priority, type and flag bits (ls=45) 8. parameter words 8, 9, 10 and 11 (ls=50 – 70) The command ”RES HEAD” returns to the normal display mode where all trace items as well as the message header and body are fully displayed (default). NOTE: If the ENA SYM option is set, the message type and network address ma _____ be substituted by the actual message name as given in the relation R_MSG_MNEM. NOTE: This command only chooses a different formatting and display of th _____ message trace. There has no impact on the tracing itself.

3.19.5 Set trace length ________________________ Syntax: SET TRC [item–size][,CYC] This command changes the maximum size of one message trace item. The selectable range is from 8 upto 168 (message body plus maximum 128 bytes user buffer). The keyword CYCLIC can be used to instruct the slave to keep always the last trace–items in the buffer (i.e. the oldest trace–items are thrown away in case of a buffer overflow). The command ”RES TRC” sets the default value of 72 (i.e. max. 40 bytes message data + 32 bytes user buffer) and disables the cyclic tracing. NOTE: These two commands only take effect with the next message trac _____ command.

013 211 31515 AAAA EA 126

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.19.6 Set supervision time ____________________________ Syntax: SET SUP minutes [,seconds] This command sets the event supervision time to the specified value, whereby the time has to be in the range from 1 to 50 minutes. The command ”RES SUP” resets the supervision time, i.e. wait forever until the requested event occurs. This option enables you to deal with events which are expected but do not arrive for whatsoever reason. If the event does not occur MPTMON will time out after the specified number of minutes and generate an error message. This option is only effective for the commands RCV MSG, WAI BRP, VER REP and WAI REP.

3.19.7 Error abortion ______________________ Syntax: SET ERR Command execution is not interrupted by any error. RES ERR Aborts command execution in case of any errors. The execution of a compound command or macro call is aborted by default if an error is encountered (as in most cases all kind of subsequent error messages and unexpected actions may occur). Sometimes, however, it may be required to continue and to evaluate the number of errors that occur. The SET ERR command offers such a feature. The keyword IEC can be used to control the behaviour of compound commands under error conditions. The IEC is set every time during any command execution when an anomaly (i.e. warning) or an error is detected. The IEC is reset when the IEC–value is read, or a RES ERR or RES OPT command is executed. Example: SET ERR ACT %0 ;activate CE IF IEC = 23T ;slave timeout message no. .ERRORCOUNT = .ERRORCOUNT + 1 IF .ERRORCOUNT > 100T RES ERR EXIT END ELSE RES ERR EXIT END

013 211 31515 AAAA EA 127

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.19.8 Set menu mode _____________________ Syntax: SET MEN Suppresses MMC dialogue text output and error messages RES MEN Resumes MMC dialogue text output and error messages Running MMC commands driven by menus it is not desirable to get the text printed as prepared by MMC. To support a user–friendly menu system MMC dialogue text can be suppressed using this option. To give own error messages to the user of such a menu system all MPTMON error messages are suppressed as well, only the internal error code ’IEC’ is set up. For this application the error option (refer to ”3.19.7 Error abortion” on page 127) is set/reset automatically.

3.19.9 Suppress MMC translation ________________________________ Syntax: SET NOT Suppresses translation and display of reports received from MMC. RES NOT Resets the translation suppress option. MMC reports received by MPTMON are not translated or displayed if this option is set. Instead, the binary report buffer is kept and can be accessed using the keyword ’RBF’. This allows for user defined evaluation or formatting of ORJ reports. Example: SET NOT ;set option WAI REP ;wait on report IF BYT RBF+5= 0 ;check parameters WRI’COMMAND EXECUTED’ OR BYT RBF+5=1 ;check error reason WRI’ERROR: DEVICE STATUS MISMATCH’ OR BYT RBF+5=2 WRI’ERROR: NOT EQUIPPED’ ELSE BAS=T WRI’ERROR: ’,BYT RBF+5 END

Note: suppression of known or expected reports speeds up the execution of a MMC compound dialogue file. It is, however, not effective for the VERIFY REPORT command as the report must be translated to be able to do the verification.

3.19.10 Set batch mode _______________________ Syntax: SET BAT [number] Puts MPTMON into batch operation mode. 013 211 31515 AAAA EA 128

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– RES BAT Resumes interactive operation mode. MPTMON runs per default in interactive mode, i.e. after each command given, MPTMON waits for new operator input. External events arriving while waiting for operator input will abort the IO–read command and the tester is immediately notified of the event occurrence. The SET BAT command switches MPTMON into a batch type of operation mode in which events are deferred. An optional number defines when the events should be accepted by MPTMON; – ”0”: Events are accepted at any time. I.e. has the same effect as ”RES BAT”. – ”1”: Events are not accepted when waiting for operator input. – ”2”: Events are never accepted except when explicitely instructed by a command like ”WAI BRP”, ”RCV MSG”, ”WAI REP”, ”EVE”, etc. This is the default mode if no value is specified. Note that macro and compound command execution runs per default in the batch operation mode ”2”.

3.19.11 Set options ____________________ Syntax: SET value Sets a run time option by means of a value. This command is only provided for compatibility reasons with old MPTMON releases and not to be used for future applications. RES OPT Resets all run time options to their default values.

3.19.12 Display of currently selected options ______________________________________________ Syntax: OPT Displays the selected input base (suffix), the output base and all currently selected run time options differing from the default operation.

013 211 31515 AAAA EA 129

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.20 Miscellaneous Commands ____________________________ Some commands can not be easily categorized in one of the other sections, and are therefore described or referenced below: – Evaluate expression – Time delay – Fetch Relation – Fetch Process – Help

3.20.1 Evaluate expression ___________________________ Syntax: EVA expr expr Expression which evaluates to an integer or pointer value. Evaluates the specified expression and displays the value in hexa–decimal and decimal base in case of an integer value. For values less than 256 (only one byte) the binary representation and the corresponding ASCII character (if displayable) are shown as well. It offers the facility to convert an integer from one base into the other. If the expression evaluates to a pointer value, it is displayed in pointer notation followed by a symbol and a positive offset to the symbol (if any, the nearest symbol is chosen within an offset range of 64K). Example: EVA WOR.A – 15F*2C EVA 5468T EVA .HC+4F6

3.20.2 Time delay __________________ Syntax: DEL TIM time time The amount of time in seconds how long MPTMON shall wait. Instructs MPTMON to wait the specified amount of seconds in the range from 1 to 3000 (50 minutes). There is no event scanning performed within this time period. Example: DEL TIM 15T ;WAIT 15 SECONDS 013 211 31515 AAAA EA 130

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.20.3 Fetch relation ______________________ Syntax: FET REL relation–id relation–id The number used internally in 12 to identify a relation. This number can be found in DLS–listings. This command scans the memory resident local directory of the DBCS to provide the tester some DBCS internal data. It enables the display of a memory resident relation in any user defined format. If the relation is found locally, the following register identifiers are loaded: – DS:SI has the absolute relation address. – RCX has the actual number of tuples present. – RAX has the tuple size. – RDX has the relation size (no of bytes). – ES:DI has the address of the local directory entry. If MPTMON is executing in interactive mode and if the library option is set (see although ”3.13.3 Disable library calls” on page 102) the name of the specified relation is displayed. In case of a procedural relation a warning message is displayed together with the GSM name of the procedural relation if MPTMON is executing in interactive mode. Otherwise the display of the relation name or the GSM name depends on the setting of the display option (see ”3.19.3 Display of suppressed data” on page 125). Additionally the following register identifiers are loaded for procedural relations: – ES:DI has the address of the global directory entry. – CS:IP has the start address of the procedural relation. If the relation is found in the global directory but the type is not local real nor procedural, an error message is given and only two register identifiers are loaded: – ES:DI has the address of the global directory entry. Example: FET REL 381T DEF .FCB=DS:SI,.I COU RCX ;number of tuples BYT .FCB+.I LEN RAX .I=.I+RAX ;next tuple END

013 211 31515 AAAA EA 131

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 3.20.4 Fetch process _____________________ Syntax: FET PID process–id process–id Identity of the process which should be fetched. The process–id is expected as an integer because a process can only be fetched locally. Fetch PID provides information about the status of the process, the corresponding FMM identity and the actual program pointer where the process is waiting or has been interrupted. If the process identity is found the following register identifiers are loaded: – CS:IP has the actual program address of the process. – RAX has the FMM identity. – RDX has the status of the process – FLA has OSN flags of the process. – DS has the data segment value of the FMM. – SS:SP has the actual stack pointer of the process. – ES:DI has the address of the process control block (PCB). The following values are valid for the process status: 0 = running 2 = interrupted 4 = terminated 1 = waiting 3 = blocked

3.20.5 Display error type mnemonic ___________________________________ Syntax: ERT error–type error–type An interger value matching a System 12 error type. This command translates a System 12 error type number to the corresponding mnemonic using a relation in the PLCE.

3.20.6 Help command ____________________ Syntax: HELP [list of options] This HELP command operates in a rather simple manner. First the actually selected macro library is saved. Then MPTMON selects the default macro library (currently file 969 on twin device) and executes the macro HELP from this library. With this all parameter given in the HELP command are passed

013 211 31515 AAAA EA 132

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– to the macro. Afterwards the previously selected library of the user is restored. As this HELP command operates on macro level, each unit – or even each project – may design its own help menus. In the appendix A.2 the basic HELP macro is listed as it is used by SEL for the ISDN project. The implemented parameter handling is as follows: If the option is given the corresponding submacro is called directly (without displaying the selection panel) passing all further options to this submacro. Otherwise the menu will be displayed and the macro prompts for the selection. Example: HELP MPT,FETREL ;calls HELP macro to explain MPTMON command FET REL

013 211 31515 AAAA EA 133

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 4. TEST CONFIGURATIONS ______________________

Since MPTMON is now in use at various places, as compared with its first installation, it became more important that it got the ability to interface with several devices and test environments. For example: in small applications or PABX’s, the PTCE test processor can not be equipped for cost reasons. The MPTMON Controller can be defined here as an overlay module in the P+L or as a resident module in a SPARE processor. Moreover, some administrations may not even want the MPTMON features accessible as standard, resident 12 features. The main aspect of the following sections is to give some information about possible MPTMON configurations and interfaces and as well the constraints related to the usage of MPTMON on specific VDU’s. +––––––––––––––––––––––––––+ +–––––––––––––––––+ VAX | PTCE | | TARGET CE | | | +–––+ +––––––––––––+ | | +–––––––––––+ | OBC +––––––+––| A | +–| PADS | | +––––+––| Relay FMM |––+–––> +–––––+ | | S |–| +––––––––––––+ | | | +–––––––––––+ | | VDU |–––+––| Y | | | | | | | +–––––+ | +–––+ | +––––––––––––+ | | | +–––––––––––+ | | |–| Controller |––+–––/ /–––+––| Slave FMM | | | +–––+ | | and | | UCP | +–––––––––––+ | +–––––+ | | S |–+ | Routines | | | | | | VDU |–––+––| I | +––––––––––––+ | | +–––––––––––+ | +–––––+ | +–––+ | | | | | | Slave SSM | | or | | | | | | +–––––––––––+ | VAX +––––––––––––––+––+––+–––––+ +–––––––––––––––––+ | | | | | | +–––––––––––––––––+ | | | | PLCE | | | | VP | +–––––––––––+ | Disk | | +–––––––––/ /–––+––| I O S |––+––––> | | | +–––––––––––+ | | | VP | +–––––––––––+ | | +––––––––––––/ /–––+––| R T S H | | | | +–––––––––––+ | | VP | +–––––––––––+ | System +–––––––––––––––/ /–––+––| VDU–FH |––+––––> | +–––––––––––+ | Terminal +–––––––––––––––––+

MPTMON’s Environment and Interfaces

4.1 Terminal Connections _________________________ MPTMON test sessions can be started from various terminals, interfacing to MPTMON in different ways: 1. A dedicated terminal connected to one of the ports of the ASY–board (211 ITT 22128) using a 1200 baud asynchronous line (or via a modem). This board is provided as the standard MPTMON interface in the PTCE. An SSM–ASYNC CONTROLLER (211 24989) is used to drive this board.

013 211 31515 AAAA EA 134

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 2. A terminal of a host computer (VAX or PC) connected to the second port of the ASY–board of the PTCE via a 1200 baud asynchronous line on which a simple ETX protocol is used to synchronize the communication. The VAX–HILTI program (163 00567) is used to interface MPTMON to a VAX–VDU. 3. A dedicated terminal connected to a SPARE or AUX control element using the serial interface (SI) of the TCPx or MCUx processor board at high baud rate (4800 baud for TCPA processors, 9600 baud for TCPB/C or MCUA/B processors). The SSM–TCPA SERIAL ITF HDLR (211 93948) supports MPTMON with input and output commands to operate this link. 4. A terminal connected to a P+L processor (often called System VDU) communicating with MPTMON via the digital switch. The FMM–VDU FILE HANDLER (211 32904) provides a normal file–oriented interface to MPTMON to drive a system VDU. MPTMON offers as a standard option four processes each assigned to drive one connection as described above. This default configuration can be changed by modifying the relation R_MPTMON_T (e.g. the serial link terminal process can be assigned to drive a PC). The relation identity is 4836. The items concerned are the CHILL modes R_MPTMON_T, M_VDU_TYPE and M_CONN_TYP.

4.1.1 PTCE dedicated Terminal. _______________________________ This is the ”standard” way of operation for MPTMON and offers all features as described in this document. In the standard PTCE configuration, the VDU is directly connected to an Asynchronous Interface PBA and controlled by MPTMON using a SSM. The VDU types supported, is any of the one outlined in ”4.2 Terminal Types” on page 140, though the default setting is the Tandberg TDV 2242 or a compatible.

4.1.2 SI connected Terminal ____________________________ The MPTMON–Controller and supporting SSM’s can basically be loaded in any control element equipped with a TCPx or MCUx processor board (e.g. a SPARE control element running in simplex or duplex). MPTMON creates in all cases a process which will try to initialise the onboard serial interface. If the initialisation succeeds, MPTMON starts a test session as for a normal dedicated terminal, assuming that an Tandberg TDV 2242 is connected. This default terminal assignment can be changed dynamically to a host computer using MPTMON configuration commands (see ”4.2 Terminal Types” on page 140).

4.1.3 Host System Terminal ___________________________ System 12 Test Stations are often supported by VAX Host s. They are mainly used for patch administrations, like fault report handling, patch file generation, etc. A VAX System offers various powerful features to assist such complex and distributed test environments, as there are mass memory storage, editor and network services to other VAX System’s or computer centers; just to mention a few of them. From MPTMON’s point of view, a VAX connection is treated like a dedicated VDU. The differences are: 013 211 31515 AAAA EA 135

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 1. The VDU type is per default a VT100. The VT100 itself is explained in section ”4.2.1 Digital VT100” on page 140. 2. The VDU is not directly connected, but driven by an interface program, called HILTI on the VAX. Note that any computer having a RS232 interface may be used to drive MPTMON assuming that an appropriate interface program is available (a program running on a ITT–XTRA or any IBM–PC compatible is now operational). A few more words shall be spent to describe what is available on a VAX System related to MPTMON.

4.1.3.1 HILTI

The VAX MPTMON program, HILTI (see ref. 8), provides a transparent connection between a VT100 terminal at one side, and a VAX input/output channel connected to System 12 at the other side. In addition to its terminal handling functions, HILTI offers further features assisting session management as follows: – Session log file – Batch file processing. – Processor loading – Extended macro edit features. The HILTI command syntax is described in its own User Guide (ref. 8.). It uses a ’#” sign to distinguish its own commands from MPTMON commands. The most important commands offered are: – # comment Comments in file not sent to MPTMON (to improve readability). – #BAT file–name. Submit a VAX–file to MPTMON for execution. – #NOV and #VER Turn verification of batch file execution ”OFF” resp. ”ON”. – #STOP and #CONT Stop resp. Continue batch file execution. – #GOTO ”label” Skip lines in batch file until the searched label appears. – #ON ”label” command Execute command everytime when the label appears. – #OPEN file–name, #OPEN/APPEND file–name and #CLOSE file–name Open, Append or Close a file for saving of macros or MPTMON generated output.

013 211 31515 AAAA EA 136

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– – #SHOW LOG Display the current log file. – #SPAWN command–line Spawn a DCL command line to the VAX command interpreter. – #MAC Call the VAX Macro Collection Utility. – #EDI file–name Spawn the VAX–editor (refer to ”3.5.9 Edit a macro definition” on page 44 how MPTMON invokes this command automatically). – #LOAD file–1, file–2, ...,file–5 (net–addr,vp–index,debug–feature) Load GLSC format files in a target processor (see ”3.2.10 Load control element” on page 31). The session log file (HILTI.LOG in the current directory) is laid out as such, that all outputs, regardless whether generated by MPTMON or HILTI, are preceded by the comment delimiter character ’;’, and all inputs not. NOTE: Basically any computer can drive MPTMON via an asynchronous RS23 _____ line and offer its own commands on top of the MPTMON command set described in this User Manual. 4.1.3.2 SCRIPTGEN SCRIPTGEN is a SW package providing a set of functions to generate and maintain Test Scripts for System 12 regression tests driven by MPTMON (see ref. 9). Test Scripts are a set of MPTMON commands, mostly MMC interface commands imbedded in compound command structures, triggering an ORJ, verifying the reports and keeping the operator informed on the progress of the test execution. Using SCRIPTGEN, Test Scripts can be defined, modified and maintained in Test Libraries. A complete test session is then compiled out of a set of Test Scripts, merged together to a MPTMON Script file. Such a file also known as include file, can be executed directly from the VAX using HILTI or transferred to System 12 IOS devices via the Patch Transfer System and executed using the INC IOS command. One main advantage of Test Scripts is, that they can be executed without operator presence, which is likely to be the case during late shifts or overnight tests. Test results can be examined the next day by checking the log file(s). Moreover, since the Test Scripts are kept libraries, test can be rerun with simple effort and high confidence, hence the test input is always available and repeatable. This allows simple, fast and highly confident regression tests after the rebuilds of existing System 12 SW packages. 4.1.3.3 PADS A special command is supported by MPTMON assisting VAX sessions. Syntax: PADS 013 211 31515 AAAA EA 137

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– This command invokes the Patch Transfer FMM to perform a file transfer from a VAX System to a System 12 IOS device and vice versa (refer to ref. 10 for details on the user command interface). The Patch Transfer FMM takes control over the MPTMON’s asynchronous connection to the VAX. MPTMON resumes its execution upon PADS completion. The command is put under password protection with its own password. You get prompted to enter the password’s value every time the command is entered.

4.1.4 System 12 Terminal _________________________ In small applications or already handed over exchanges, there might be no special dedicated MPTMON VDU for cost or administrational reasons. The primary purpose of a System VDU is to interface with the exchange via the MMC Subsystem in order to initiate ORJ’s. A MPTMON ORJ has been defined to start a test session on a system VDU, possibly even located in a NSC. The ORJ has to be entered as follows: START–MPTMON; Successful/unsuccessful start–up is confirmed by a MPTMON Session Report. Thus, if the start–up succeeded, MPTMON displays its sign–on header on the allocated System VDU. In contrast to other session types MPTMON doesn’t prompt for a password, since a password is already supplied for the ORJ and you are immediately authorized to execute any MPTMON command which will not lead to data modifications. To get also modify authorisation the SET AUT run time option, as explained in ”3.19.1 Command authorizations” on page 124 may be used. Some functions requiring ”screen transfer” (i.e. EDIT) are disabled when running a test session on a System VDU due to restrictions of the System 12 IOS. For the same reason, some of the special function keys have other functions assigned: 1. ESC–key: does not perform a ”command abortion” but BREAK has to be used instead. 2. ENTER: does not invoke a ”screen transfer” but is ignored. 3. CNTL–R and CNTL–F are ignored as well. Upon test session completion you have to enter the TERMINATE command to release all MPTMON resources and the allocated VDU. Session termination is confirmed by a MPTMON Session Termination Report. Thereupon the System VDU is available again for its normal usage. Note: don’t use a device specification for any other input/output command, like LIS, SAV etc., which maps onto your System VDU. This will lead to a deadlock, which will be teared down either after OSN process abortion or Control Element restarts.

013 211 31515 AAAA EA 138

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 4.2 Terminal Types ___________________ Due to the fact that more VDU types are going to be introduced into System 12, MPTMON’s capability has been extended to cover the ones currently in use. The following commands allow you to dynamically modify the MPTMON terminal characteristics during a test session: – Direct connected (SET C0) – HOST connected (SET C1) – PC connected (SET C2) – SYSTEM connected (SET C3) These modifications are however only effective for one test session. After a PTCE restart or session termination, MPTMON uses its defaults again.

4.2.1 Digital VT100 ____________________ A VT100 is usually not connected directly to MPTMON. In a System 12 test environment this type of VDU will be found on VAX s. The VDU itself is driven by SW on the VAX. The MPTMON driver on the VAX (see ref. 8) reads the data from the asynchronous line and passes it directly to the VDU and vice versa. A set of restrictions have to be considered here. A VT100 can not be put into ’block mode’, i.e. doesn’t support the macro editor of MPTMON. You can only output formatted screens, e.g. clear screen, inverse video, but not read from it. For further details see ref. 3.

4.2.2 Tandberg TDV 2242 ________________________ The TDV 2242 is the standard MPTMON–VDU and all special features, like display commands, macro editor, etc. can be used. The VDU can be configured so that the cursor does not have to be located behind the ’EM’ for the EDIT function. It supports multiple screen edit, though you may have to switch to VDU to ”buffer mode” manually before you start editing (press ”MODE” key followed by the ”B” key).

4.2.3 Olivetti WS 580 ______________________ The WS 580 is MPTMON compatible. All special features, like macro editor, etc. can be used, except scrolling region definitions. It has all special key functions. One inconvenience has to be considered in case of using the macro editor: the cursor has to be moved after the last line, usually the EM command before the SEND key is pressed, otherwise all data behind the cursor is lost. The VDU doesn’t automatically move the cursor to the end of data. Furthermore, as this VDU has only one screen page, the macro size is limited to 24 lines. To overcome this limitation, the back slash character can be

013 211 31515 AAAA EA 139

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– used as a command separator to be able to put multiple commands in one line. Details can be found in ref. 4.

4.2.4 Teletype _______________ A teletype is the most simple device as there are no screen formatting facilities. Therefore MPTMON supports only line by line operation. All commands requiring screen formatting are disabled or have no effect (EDIT, CLR SCR, LOC CUR, etc.).

4.3 Dimensioning _________________ A trade–off between MPTMON’s Controller and Slave memory size and usability is made, resulting in a set of dimensioning values for internal tables and directories. The hereafter specified dimensioning values are in general defined by CHILL synonyms or SRASM equates to allow an easy redimensioning when required. NOTE: MPTMON Controller is implemented as a multi–process FMM and two termina _____ driver SSM’s. Each process controls its own test station, i.e. VDU, independent from each other. All values related to the Controller are specified on a per process basis, i.e. the total stack size is multiplied by the number of processes in the PTCE. Redimensioning of one table may affect the maximum size of an other due to the fixed maximum stack size per process. Some tables are, however, not stored on the stack and will not affect the size of other tables. +–––––––––––––––––––––––––––––––––––––––––––––––––––––––+ | MPTMON Controller Dimensioning | set to | max. | |–––––––––––––––––––––––––––––––––––––+––––––––+––––––––| | No. of dedicated VDU’s controlled | 1 | – | | No. of host VDU’s supported | 1 | – | | No. of SI connections driven | 1 | 1 | | No. of system VDU’s controlled | 2 | – | | No. of CE’s concurrently active | 8 | 32 | | No. characters per identifier | 8 | 8 | | No. of resident symbols | 256 | – | | No. of resident macros | 64 | 128 | | No. of user work areas | 8 | 32 | | No. macro parameters | 10 | 10 | | Macro buffer size | 2048 | 4096 | | Total no. of nesting levels | 16 | 16 | | Expression evaluation level | 6 | – | | Work buffer size | 2048 | 4096 | | Include files (950T – 959T) | 10 | – | | Library files (960T – 969T) | 10 | – | | List file (971T) | 1 | – | +–––––––––––––––––––––––––––––––––––––––––––––––––––––––+ MPTMON Slave is implemented as a mono–process FMM and a SSM in each Control Element. Its tables are located in the module R/W data segment and are therefore not part of the Slave process stack.

013 211 31515 AAAA EA 140

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


+–––––––––––––––––––––––––––––––––––––––––––––––––––––––+ | MPTMON Slave Dimensioning | set to | max. | |–––––––––––––––––––––––––––––––––––––+––––––––+––––––––| | Trace buffer size | 1024 | 2048 | | Call buffer size | 32 | – | | No. of active breakpoints | 8 | – | | No. of processes on breakpoint | 1 | 1 | | No. of messages in message library | 8 | – | | No. of user controlled paths | 1 | – | | No. of received messages | 1 | – | | No. of active msg trace conditions | 1 | – | | No. of active SSM trace conditions | 1 | – | +–––––––––––––––––––––––––––––––––––––––––––––––––––––––+

013 211 31515 AAAA EA 141

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 5. TESTING NOTES ________________

5.1 Getting Started. _____________________ There is a lot to say about ”how to to use MPTMON”, ”how to test”, ”where to find information”, etc. It would far exceed the scope of this document to describe these kind of things. Moreover, methods differ between design centers, and everybody has his own opinion about the most effective way to find a bug, etc. The latter depends even on the experience of the tester himself. Therefore, only some general guidelines can be given here. Before you start testing, you should collect at least the following information to work effectively with MPTMON: – A list of all FMM–identities (FET FMM ...) – A list of all SSM–identities (FET SSM ...) – A list of all relations identities (FET REL ...) – A list of all message numbers (TRC MSG ... and DUM TRC) If you have never worked with MPTMON before, try to understand and execute the commands written in ”A.1 Session Log” on page 147. It gives at least some feeling how MPTMON reacts on commands and errors in it. Use the escape key labelled ”ESC” to get control again if MPTMON does not answer or to abort any command. As MPTMON is most of the time used in the interactive mode, it is recommended to get familiar with command procedures (here called macros) to reduce your typing effort. Even for the most trivial commands, it saves time, when you write once a simple macro with a one character name, instead of giving a command of 8 characters N times (use the edit command ”EDI name” to write a macro). Use comments and indentations within more complicated macros to keep them readable. For the same reason, use symbol names with at least three characters, and define these symbols within a macro using the ”ADD” command.

5.2 General Utilities. _______________________ Now MPTMON has been in use for a couple of years in various design centers, many very useful macros (sometimes even quite complicated) have been written which are of general interest and application. It is strongly recommended to deliver such macros to your local librarian who may put them on the system load tape, where they are automatically available to everybody. Some simple macros are listed below in order to give you an idea how to write macros. These macros are written for the ”MOPS” application and kept on a VAX directory at SEL. They use the VAX–HILTI ”comment” feature to save transfer time to S12. More examples are given in ”APPENDIX A. Examples” on page 147.

013 211 31515 AAAA EA 142

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : B # parameter : <OFFSET> # function : sets a blocking breakpoint in the current module (.SUT) # date : 24.10.1986 P. Oosterhaven # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC B (OFFSET) BRP .SUT+%0, BLO, FFFF EM

# –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : G # parameter : <OFFSET> # function : sets a breakpoint at the given offset an waits for match # date : 24.10.1986 P. OOSTERHAVEN # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC G (OFFSET) GO .SUT+%0, SUS, ANY ’ NEXT INSTRUCTION: ’,& ASM CS:IP EM

# –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : S # parameter : <NBR–STEPS> # function : steps instruction by instruction through the code # date : 24.10.1986 J. Tiekenheinrich # –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC S (NBR–STEPS) ADD.@=0%0 IF.@=0 .@=1 ENDI COU.@ ASM CS:IP GO CS:IP, BLO ENDC EM

013 211 31515 AAAA EA 143

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : SND # parameter : <MSG–NBR>,<MSG–TYPE>,<’WORD1–8’>,<’WORD9–16’>,<’WORD17–20’> # function : send a directed or a basic message with the routing number # and the parameters specified either directed or basic, # depending on the msg–type: ”D”, ”DV”, ”BV”, ”B”, or <.PID>. # note : only for messages without user buffer # date : 29.10.1986 H. Egenhofer # updated : 06.04.1987 P. Oosterhaven (explicit process id) # : 27.04.1987 J. Tiekenheinrich (add type BV and DV) # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC SND (MSG–NUM,MSG–TYPE,’WORD1–8’,’WORD9–16’) # # get first pending events # EVE # ADD .@N,.@S,.@V # set up msg header IF ’%1’=’B’ \ ALT 8,2=3800,%0,0,0 OR ’%1’=’D’ \ ALT 8,2=3E00,%0,0,0 OR ’%1’=’BV’ \ ALT 8,2=3000,%0,0,0 \ .@V=1 OR ’%1’=’DV’ \ ALT 8,2=3200,%0,0,0 \ .@V=1 ELSE \ ALT 8,2=3E00,%0,%1 END # :NBRPAR 8,%2 IF.@N>0 ALT 8,8+.@V=%2 \ .@S=.@N END :NBRPAR 8,%3 IF.@N>0 ALT 8,10+.@V=%3 \ .@S=.@N+8 END :NBRPAR 8,%4 IF.@N>0 ALT 8,18+.@V=%4 \ .@S=.@N+10 END # # set up message length ALT 8,1=(.@S+.@V)*200 SET DIS SND MSG 8 RES DIS EM

013 211 31515 AAAA EA 144

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : NBRPAR # parameter : <MAX.PARAMETER>,<PARAMETER_LIST> # function : returns the number of parameters in the list # date : 12.12.1986 P. OOSTERHAVEN # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC NBRPAR (MAXPAR, PAR_LIST) IF’%1’=’’ .@N=0 OR %N–2<%0 .@N=%N–1 ELS ’ *** ERROR: TOO MANY PARAMETERS IN STRING’ \ ABORT END EM

# –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : WHY # parameter : none # function : displays ROM data containing restart parameters # date : 05.11.1986 J. Tiekenheinrich # update : 22.04.1988 U. Schuster # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC WHY COP MEM ROMD,20 ADD .@ECL = WOR LWA+6,.@ETYP=WOR LWA+8 ’ CONTROL ELEMENT ––––> ’,WOR LWA+0 BAS=T ’ ERROR CLASS ––––––––>’,.@ECL,’T’ ’ ERROR TYPE –––––––––>’,.@ETYP,’T’ BAS=H IF .@ECL <> 0 ’ USER DATA ––––––––––> ’,WOR LWA+A LEN 5 ’ FMM IDENTITY –––––––> ’,WOR LWA+16 ’ PROCESS IDENTITY –––> ’,WOR LWA+18 ELSE ’ STACK(SS:SP) –––––––>’,& EVA (WOR LWA+14):(WOR LWA+A) ’ DS:SI ––––––––––––––>’,& EVA (WOR LWA+18):(WOR LWA+E) ’ ES:DI ––––––––––––––> ’,WOR LWA+16,’:’,WOR LWA+C ’ BX –––––––––––––––––> ’,WOR LWA+10 ’ BP –––––––––––––––––> ’,WOR LWA+12 ENDI ’ RESTART ADDRESS ––––>’,& EVA (WOR LWA+1C):(WOR LWA+1A) EM

013 211 31515 AAAA EA 145

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A APPENDIX A. EXAMPLES ____________________

The examples shown hereafter, are slightly modified to fit into this document (the time stamp in the trace dump is deleted, as well as the FLAG register and actual CE–address in the breakpoint matched message). It does not present the special key usage of a VDU. NOTE: _____ The greater than character ’>’ is MPTMON’s prompt for input.

A.1 Session Log ________________

The example shown hereafter is a hardcopy log of an actual session.

******************************************************************************** MULTI PROCESSOR TEST MONITOR V3.5 ******************************************************************************** PASSWORD: >IF TRUE .>’ SESSION STARTED AT: ’,& .>TIME >END SESSION STARTED AT: 1990–SEP–27 THU 18:52:10 >; >;CE COMMANDS >; >SET PMT ;SELECT CE PROMPT >ACT PTCE ;OWN CONTROL ELEMENT 0006>ACT C ;PLCE 000C>ACT F DEBUG MONITOR ENTERED DEBUG>CE ;DISPLAY ALL CE’S ADDR LCE PROC STATUS BREAK_PID PCS 0006 00A0 0070 ACTIVE FFFF_FFFF 13 000C 0000 0080 ACTIVE FFFF_FFFF 13 –000F 0100 00B0 DEBUG FFFF_FFFF 111 DEBUG>DAC >CE C ;DISPLAY ONLY CE C ADDR LCE PROC STATUS BREAK_PID PCS 000C 0000 0080 ACTIVE FFFF_FFFF 12 >DAC C ;DEACTIVATE PLCE >ACT PTCE ;USE PTCE FOR FURTHER SESSION 0006> RES PMT ;SELECT NORMAL PROMPT >; >;MEMORY COMMANDS >; >FET 1E6 ;PROVIDE CS AND DS OF MPTMON CONTROLLER FMM FARBTA5A >DEF .MPT = CS:IP ;START OFFSET >EVA CS:7348 ;ARBITRARY OFFSET 013 211 31515 AAAA EA 146

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A C313:7348 .MPT+733A >FET 111 ;PROVIDE CS AND DS OF MPTMON SLAVE FMM FHHVTA3A >DEF .SLV = CS:IP >FET SSM FE ;PROVIDE CS AND DS OF MPTMON ROUTINES MSLCTA3A >DEF .ROUT= CS:IP >BYT .MPT LEN 12 ;FIRST BYTES BYT C313:000E = B8 01 00 50 16 8D 86 B0 FE 50 BB 3F 00 53 8B 5E BYT C313:001E = FE CD >ASM .MPT LEN 12 ;DISASSEMBLE 18 BYTE OF FMM .MPT MOV AX,#0001 .MPT+0003 PUSH AX .MPT+0004 PUSH SS .MPT+0005 LEA AX,(BP)–0150 .MPT+0009 PUSH AX .MPT+000A MOV BX,#003F .MPT+000D PUSH BX .MPT+000E MOV BX,(BP)–02 .MPT+0011 INT 30 >GET UWA .TEMP ;GET A USER WORK AREA >UWA ;DISPLAY ALL USER WORK AREAS .TEMP = 6080:E000 >BYT .TEMP = BYT.MPT LEN 12 ;COPY 18 BYTES INTO UWA >BYT .TEMP = 53,83,5E,FE,50,40 ;MODIFY BYTES ASM .TEMP L 12 ;COPIED CODE CORRUPTED 6080:E000 PUSH BX 6080:E001 SBB (BP)–02,#50 6080:E005 INC AX 6080:E006 XCHGB DH,(BX)+(SI)+50FE 6080:E00A MOV BX,#003F 6080:E00D PUSH BX 6080:E00E MOV BX,(BP)–02 6080:E011 INT 40 >PAT .TEMP ;RESTORE ORIGINAL INSTRUCTIONS 6080:E000 >MOV AX,#0001 6080:E003 >PUSH AX 6080:E004 >PUSH SS 6080:E005 >LEA AX,(BP)–0150 6080:E009 >PUSH AX 6080:E00A >MOV BX,#003F 6080:E00D >PUSH BX 6080:E00E >MOV BX,(BP)–02 6080:E011 >INT 30 6080:E013 > END OF ASSEMBLER >REM .MPT,.ROUT ;REMOVE SYMBOLS >RET UWA .TEMP ;RETURN USER WORK AREA >; >;MACRO COMMANDS >; >DEF MAC OSNTAB .>ADD .TMP = POI(MP+16) .>ADD .VP = POI(.TMP) + 18, .VPL = WOR(.TMP) + 1C .>ADD .VN = POI(.TMP) + 24, .VNL = WOR(.TMP) + 28 .>ADD .LCE = POI(.TMP) + C, .LCEL= WOR(.TMP) + 10 013 211 31515 AAAA EA 147

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A .>ADD .OWN = POI(.TMP) + 42 .>; .>’ LCE ID TABLE’ .>WOR .LCE LEN .LCEL/2 .>’ VIRTUAL PATH TABLE’ .>WOR .VP LEN .VPL/2 .>’ VIRTUAL NETWORK ADDR’ .>WOR .VN LEN .VNL/2 .>’ OWN LCE ID’ .>WOR .OWN .>EM >:OSNTAB ;EXECUTE MACRO LCE ID TABLE WOR DB65:0000 = 0000 0010 0020 0030 0040 0060 0160 0170 WOR DB65:0010 = 0180 0190 01A0 01B0 01C0 01D0 01E0 01F0 WOR DB65:0020 = 0200 0210 0760 0770 07C0 07D0 0860 0870 WOR DB65:0030 = 08A0 08B0 00A0 00C0 00E0 0100 0120 0140 WOR DB65:0040 = 0220 0240 0260 0280 02A0 02C0 02E0 0300 WOR DB65:0050 = 0320 0360 0380 VIRTUAL PATH TABLE WOR DBA6:0000 = 0080 0090 0150 0160 00D0 FFFF 00E0 FFFF WOR DBA6:0010 = FFFF FFFF 0070 FFFF 02B0 FFFF 00F0 FFFF WOR DBA6:0020 = 0180 FFFF 01E0 FFFF 03D0 FFFF 0140 0470 WOR DBA6:0030 = 0130 03B0 0080 03C0 0280 0510 0070 01D0 WOR DBA6:0040 = 0250 02F0 0460 FFFF 0040 FFFF 01B0 FFFF WOR DBA6:0050 = 01C0 FFFF 03A0 VIRTUAL NETWORK ADDR WOR DB8E:0000 = 0000 0001 0002 0003 0004 0005 0006 000C WOR DB8E:0010 = 000D 0015 0016 0017 001C 001D 002C 002D WOR DB8E:0020 = 003C 003D 000E 000F 001E 001E 002E 002F WOR DB8E:0030 = 003E 003F 020E 020F 021E 021F 0032 0033 WOR DB8E:0040 = 0035 CD40 CD40 CD40 CD40 CD40 CD40 CD40 WOR DB8E:0050 = CD40 CD40 CD40 OWN LCE ID WOR DB63:0000 = 00A0 >; >DEF MAC INUSE .>ADD .I,.J,.K .>IF %N=0 ..>.K=FFFF ..>ELSE ..>.K=%0 ..>ENDI .>CLR .>TIME .>LOC 07T,26T .>’BATCH TESTING RUNNING’ .>LOC 09T,27T .>’PLEASE DO NOT TOUCH’ .>LOC 10T,28T .>’SYSTEM IS IN USE’ .>BASE=T .>REPEAT ..>WHILE .J < .K ..>LOC 11T,21T ..>’RUNNING ’,.I,’ MINUTES ’,.J,’ SECONDS ’,& 013 211 31515 AAAA EA 148

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A ..>LOC 12T,23T ..>TIME ..>.J=.J+6T ..>IF .J = 60T ...>.J=0 ...>.I=.I+1 ...>ENDI ..>WAIT 5T ..>END .>EM >:INUSE 1 1990–JUN–08 THU 03:52:45

BATCH TESTING RUNNING PLEASE DO NOT TOUCH SYSTEM IS IN USE RUNNING 0 MINUTES 0 SECONDS ? 1990–JUN–08 THU 03:52:45 >DIR MAC OSNTAB INUSE >; >;EXPRESSION EXAMPLES >; >EVA 4A 004AH 74T 01001010Y ’J’ >EVA ’?’ 003FH 63T 00111111Y ’?’ >DEF.I >COUNT 8 .>DEF.SYM%(.I)=.I .>.I=.I+1 .>END >SYM .SLV = 3798:000E .I = 0008 .SYM0000 = 0000 .SYM0001 = 0001 .SYM0002 = 0002 .SYM0003 = 0003 .SYM0004 = 0004 .SYM0005 = 0005 .SYM0006 = 0006 .SYM0007 = 0007 >; >;MESSAGE COMMANDS >; >TRC FMM 111 ;TRACE MPTMON COMMAND EXECUTION >ALT MSG 1,1 = 400,7E00,1234T,WOR MSG+C,DDDD >DUM TRC MSG TYPE ADDR SRC_PID DST_PID LLRA PTFF PATH BUF_PTR SIZE TIME 7423 DV 0006 0070_3A3E BC7E_3A3E 0440 0200 BC7E ....:.... .... SND 03:52:54.6 DATA 000C 1188 DV 0006 0070_3653 0070_3A3E 1200 0200 BC7E ....:.... .... RCV 03:52:54.8 DATA 200E 0001 0105 0400 7E00 04D2 DDDD DDDD 013 211 31515 AAAA EA 149

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A 7423 DV 0006 0070_3A3E BC7E_3A3E 0540 0200 BC7E ....:.... .... SND 03:52:54.8 DATA 000E 1900 1188 DV 0006 0070_3653 0070_3A3E 0300 0200 BC7E ....:.... .... RCV 03:52:55.0 DATA 0013 >TRC OFF >ALT 1,8=9876,5432 >SET DIS >SND MSG 1 MESSAGE SENT: MSG TYPE ADDR SRC_PID DST_PID LLRA PTFF PATH BUF_PTR SIZE 1234 DT 0006 0070_3A3E 0070_DDDD 0400 7E00 .... ....:.... .... DATA 9876 5432 >RES DIS >; >;TRACE RELATION COMMANDS >; >TRC REL FMM=1E6 ;TRACE ALL RELATION ACCESSES OF MPTMON CONTROLLER >ENA SYM >MSG 1 MSG NAME SRC_PID DST_PID LLRA PTFF PATH BUF_PTR SIZE 1234 0070_3A3E DDDD_DDDD 0400 7E00 .... ....:.... .... DATA 9876 5432 >ALT 1,3=9842T >MSG 1 MSG NAME SRC_PID DST_PID LLRA PTFF PATH BUF_PTR SIZE 9842 TIMER_EX 0070_3A3E DDDD_DDDD 0400 7E00 .... ....:.... .... DATA 9876 5432 >DUM REL PROC ADDR CALL_PID FMM CMD OPT UWA_PTR RUWA_PTR STATUS TIME 3716 DARQ 0006 0070_3653 01E6 GET NOOP 7080:3880 7080:38BC NFTUPLE 03:52:58.5 QUAL 0001 0000 04D2 3716 DARQ 0006 0070_3653 01E6 GET NOOP 7080:3880 7080:38BC SUCCESS 03:52:59.3 QUAL 0001 0000 2672 RUWA 2672 4954 454D 5F52 5845 2020 >; >;LIBRARY COMMANDS >; >DIR LIB 1,960T DIRECTORY OF LIBRARY FILE: 960T ON DEVICE: 1T [] >IF IEC = 33T ;LIBRARY NOT INITIALIZED .>INI LIB 1,960T .>ENDIF > PUT OSNTAB,INUSE [&&] > PUT SYM TESTSYM [&] >DIR LIB DIRECTORY OF LIBRARY FILE: 960T ON DEVICE: 1T [] INUSE OSNTAB TESTSYM >REM MAC ;REMOVE ALL MACROS >REM SYM ;REMOVE ALL SYMBOLS

013 211 31515 AAAA EA 150

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A >GET OSNTAB ;GET MACRO FROM LIBRARY >DIR MAC OSNTAB >DEL OSNTAB [] >DEL INUSE [] >DEL SYM TESTSYM ;DELETE MEMBERS [] >; >;INTERACTIVE MMC >; >;DISPLAY FDB >MMC PASSWORD: 1RT1 1990–09–27 18:53:02 TH 0006/130/003 <395:1=965; SEQ=0195.740513 9002 COM=0395 JOB SUBMITTED

RESULT FOLLOWS

1RT1 1990–09–27 18:53:03 TH SEQ=0195.740513 0336 PERIPHERAL SERVICE ROUTINES REPORT OF DISPLAY FDB SUCCESSFUL –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– LFILID = 965 LFILNAME = A965SF01 RECORLEN = 16 FILELEN = 32767 AUTHREAD = AR AUTHWRIT = JR AUTHMDFY = SR TRSLFRMT = NOTRANS ACCSATTR = RNDMDFY RECATTR = OFF FILETYPE = SYSTEM DATATYPE = ASCII TIMRST = INTREC TIMCLASS = LONG –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– PFILNAME = MPTMON–LIBRARY005 DEVLIST = B’11111000 DISK: ALOCSIZE = 0 EXTNSIZE = 9999 TAPE: BLOCKLEN = 0 GNBR = 1 ACCESS = VDU: INPTDELM = > SCRNLOC = 1 SCRNLIN = 20 PRNT: TOPMARG = 1 LEFTMARG = 1 LN = 60 REPORT REFERENCE NUMBER = 0336 > >; >TIME 1990–SEP–27 THU 18:53:13

013 211 31515 AAAA EA 151

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.2 Basic Help Macro _____________________

DEF MAC HELP ADD .OPTION,.VALID,.DIRECT BAS=A WRI ’%0’ BAS=H REPEAT IF ’%0’=’GEN’ AND .VALID=FALSE \ .OPTION=’0’ OR ’%0’=’OSN’ AND .VALID=FALSE \ .OPTION=’1’ OR ’%0’=’DBS’ AND .VALID=FALSE \ .OPTION=’2’ OR ’%0’=’ADM’ AND .VALID=FALSE \ .OPTION=’3’ OR ’%0’=’CHP’ AND .VALID=FALSE \ .OPTION=’4’ OR ’%0’=’CHG’ AND .VALID=FALSE \ .OPTION=’5’ OR ’%0’=’IOS’ AND .VALID=FALSE \ .OPTION=’6’ OR ’%0’=’MAI’ AND .VALID=FALSE \ .OPTION=’7’ OR ’%0’=’LTT’ AND .VALID=FALSE \ .OPTION=’8’ OR (’%0’=’MPT’ OR ’%0’=’MPTMON’) AND .VALID=FALSE \ .OPTION=’9’ ELSE CLR ’ ’ ’ M P T M O N – H E L P F A C I L I T Y’ ’ ’ ’ ’ ’ 0 ===> (GEN) GENERAL INFORMATION ’ ’ 1 ===> (OSN) HELP OSN (LIB961)’ ’ 2 ===> (DBS) HELP DATABASE (LIB962)’ ’ 3 ===> (ADM) HELP CMD–HDLR & MEASURM.(LIB963)’ ’ 4 ===> (CHP) HELP CALL–HDLG (LIB964)’ ’ 5 ===> (CHG) HELP CHARGING (LIB965)’ ’ 6 ===> (IOS) HELP I/O SYSTEM (LIB966)’ ’ 7 ===> (MAI) HELP MAINTENANCE (LIB967)’ ’ 8 ===> (LTT) HELP TRUNK TESTING/MEAS.(LIB968)’ ’ 9 ===> (MPT) HELP MPTMON’ ’ ’ ’ ’ ’ ’ ’ ’ ’ X ===> EXIT ENTER OPTION ===’,& .OPTION=’%Q’ ENDI .VALID=FALSE REP WHILE .VALID=FALSE IF (.OPTION<’0’ OR .OPTION>’9’) AND .OPTION<>’X’ LOC CUR 18T,66T \ ’ ’,& LOC CUR 17T,48T \ ’INVALID OPTION’,& LOC CUR 18T,47T \ ’RE–’,& LOC CUR 18T,66T .OPTION=’%Q’ ELSE .VALID=TRUE ENDI ENDR IF .OPTION = ’0’ \ :HELP_GEN 013 211 31515 AAAA EA 152

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A OR .OPTION = ’1’ \ SEL LIB 1032T,961T\ :HELP_OSN %1,%2,%3 OR .OPTION = ’2’ \ :HELP_DBS %1,%2,%3 OR .OPTION = ’3’ \ :HELP_ADM %1,%2,%3 OR .OPTION = ’4’ \ :HELP_CHP %1,%2,%3 OR .OPTION = ’5’ \ :HELP_CHG %1,%2,%3 OR .OPTION = ’6’ \ :HELP_IOS %1,%2,%3 OR .OPTION = ’7’ \ :HELP_MAI %1,%2,%3 OR .OPTION = ’8’ \ SEL LIB 1032T,968T\ :HELP %1,%2,%3 OR .OPTION = ’9’ \ :HELP_MPT %1 OR .OPTION = ’X’ \ CLR \ ABO MAC ENDI IF .DIRECT=TRUE ABO MAC ENDI ENDR EM

013 211 31515 AAAA EA 153

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.3 Data Display Macros ________________________

A.3.1 Macro: Display FMM Control Block _______________________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : FCB # parameter : FCB–number # function : displays FMM control block # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC FCB IF %N=0 ’ *** ERROR: PARAMETER MISSING – FCB NUMBER’ ABO MAC ENDI WOR LWA = WOR (POI(POI 407F:6)+C6)+12*%0 LEN 9 ’ FMM IDENTITY –––––––––––––> ’,WOR LWA+0 ’ FLAGS ––––––––––––––––––––> ’,WOR LWA+2 ’ CODE SEGMENT –––––––––––––> ’,WOR LWA+4 ’ DATA SEGMENT –––––––––––––> ’,WOR LWA+6 ’ SUPERVISOR IP ––––––––––––> ’,WOR LWA+8 ’ STACK SIZE ––––> ’,WOR LWA+C ’ EC SIZE –––––––> ’,BYT LWA+10 ’ APPLICATION IP –––––––––––> ’,WOR LWA+A ’ STACK SIZE –––> ’,WOR LWA+E ’ EC SIZE ––––––> ’,BYT LWA+11 EM Macro execution sample: _______________________

>:FCB *** ERROR: PARAMETER MISSING – FCB NUMBER >:FCB 10T FMM IDENTITY –––––––––––––> 0111 FLAGS ––––––––––––––––––––> 8000 CODE SEGMENT –––––––––––––> AF2B DATA SEGMENT –––––––––––––> 9638 SUPERVISOR IP ––––––––––––> 0000 STACK SIZE ––––> 0200 EC SIZE –––––––> 40 APPLICATION IP –––––––––––> 0003 STACK SIZE –––> 0000 EC SIZE ––––––> 00 >

013 211 31515 AAAA EA 154

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.3.2 Macro: Convert Network Address _____________________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : CONVERT # parameter : network address to be converted, CE where conversion to # be done (optional). # function : converts a given network address to VP–index and LCE–ID. # date : 08.04.87 P. Oosterhaven #–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC CONVERT (NETWORK_ADDR) ADD.C,.VP,.LCE,.VPT,.VN,.N IF %N=0 ’ ENTER NETWORK ADDRESS –––’,& .N=%Q ELSE .N=%0 ENDI IF ’%1’=’’ ACT D ELSE ACT %1 ENDI .VN=(POI (POI 407F:6)+24) .VPT=(POI(POI 407F:6)+18) REP UNTIL .N=WOR .VN+.C .C=.C+2 ENDR .VP=((.C/2)+1)*10 .C=0 REP UNTIL .VP=WOR .VPT+.C .C=.C+2 ENDR .LCE=(.C/2)*10 WRI ’ NETWORK ADDRESS –––> ’,.N,’ = VP INDEX –––> ’,.VP,& WRI ’ = LCE ID ’,.LCE DAC EM Macro execution sample: _______________________

>:CONVERT ENTER NETWORK ADDRESS –––>C NETWORK ADDRESS –––> 000C = VP INDEX –––> 0010 = LCE ID 0000 >:CONVERT PTCE NETWORK ADDRESS –––> 0006 = VP INDEX –––> 0150 = LCE ID 0260 >

013 211 31515 AAAA EA 155

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.3.3 Macro: Display FMM processes ___________________________________

# –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : PIDS # parameter : <FMM–ID>,<resources> # function : lists the status of all processes of this FMM # created : 05.11.1986 J. Tiekenheinrich # updated : 13.02.1990 J. Langton # –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC PIDS (FMM–ID, TRUE/FALSE) IF ’%0’<>’’ ADD.@FMM_ID=%0 ELSE ’ ENTER FMM IDENTITY –––’,& ADD.@FMM_ID=%Q ENDI IF .@FMM_ID=0 \ ABO MAC ENDI RES ERR\FET .@FMM_ID IF IEC<>0 \ ABO MAC ENDI ADD .@FMM_NBR,.@SUP,.@SUP_PCB,.@PCB_SEG,.@PCB_OFF,.@ACT_PCB,.@PID ADD .@STATUS,.@STACK,.@TCB_ID,.@INDEX,.@NBR_UB,.@UB_OFFS,.@NBR_MB,.@MB_OFFS ADD .@OSN_DS=(WOR MP+14):0 ADD .@PCBS=POI(POI MP+10)+1E ADD .@FCBS=POI(POI MP+16)+C6 # OSN 55 ADD .@SUP_PID=WOR(POI(POI(POI MP+10)+12)+16)+2*RAX IF .@SUP_PID=FFFF \ ’ NO PROCESS FOUND’ \ABO MAC ENDI # .@INDEX=.@SUP_PID AND FF .@SUP_PCB=.@PCBS+.@INDEX*2C .@PCB_SEG=SEGM(.@SUP_PCB) .@PCB_OFF=OFFS(.@SUP_PCB) ’ SUPERVISOR (’,.@SUP_PID,’) IS ’,& .@ACT_PCB=.@SUP_PCB REP .@STATUS=BYT.@ACT_PCB+1A .@STACK=POI(.@ACT_PCB+20) .@TCB_ID=BYT(.@ACT_PCB+1D) IF .@STATUS=0 ’RUNNING’ ORIF .@STATUS=1 ’WAITING AT’,& EVA POI(.@STACK) ORIF .@STATUS=2 ’INTERRUPTED’ ORIF .@STATUS=3 ’BLOCKED AT’,& EVA POI(.@STACK) ORIF .@STATUS=4 ’TERMINATED’ ENDI IF ’%1’<>’’ 013 211 31515 AAAA EA 156

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A .@UB_OFFS=WOR.@ACT_PCB+8 REP UNTIL .@UB_OFFS=OFFS(.@ACT_PCB+8) .@UB_OFFS=WOR.@OSN_DS+.@UB_OFFS .@NBR_UB=.@NBR_UB+1 ENDR .@MB_OFFS=WOR.@ACT_PCB+4 REP UNTIL .@MB_OFFS=OFFS(.@ACT_PCB+4) .@MB_OFFS=WOR.@OSN_DS+.@MB_OFFS .@NBR_MB=.@NBR_MB+1 ENDR BAS=T IF .@NBR_UB<>0 ’ OWNS’,.@NBR_UB,’T USER BUFFERS’ .@NBR_UB=0 ENDI IF .@NBR_MB<>0 ’ OWNS’,.@NBR_MB,’T MESSAGE BUFFERS’ .@NBR_MB=0 ENDI BAS=H IF .@TCB_ID<>FF ’ OWNS TIMERS’ ENDI ENDI WHILE (WOR.@ACT_PCB)<>.@PCB_OFF .@ACT_PCB=.@PCB_SEG:(WOR.@ACT_PCB) .@INDEX=(OFFS(.@ACT_PCB)–OFFS(.@PCBS))/2C .@PID=BYT.@ACT_PCB+1E ’ APPLICATION (’,.@PID*200+.@INDEX,’) IS ’,& ENDR EM Macro execution sample: _______________________

>:PIDS 1E6 ;MPTMON CONTROLLER FMM SUPERVISOR (6209) IS WAITING AT 9000:D600 APPLICATION (6A0D) IS WAITING AT 9000:1E65 APPLICATION (680C) IS WAITING AT E000:0100 >:PIDS 111 ;MPTMON SLAVE FMM SUPERVISOR (7010) IS RUNNING >

013 211 31515 AAAA EA 157

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.4 Message Handling Macros ____________________________

A.4.1 Macro: Set System Time _____________________________

DEF MAC SETTIME ;set the time in both CTCE’s ;%Q=time parameters are prompted for ACT PTCE CLR WRI ’HOUR ––––’,& ADD .HOUR= %QT WRI ’MIN –––––’,& ADD .MIN = %QT WRI ’SEC –––––’,& ADD .SEC = %QT ALT MSG 1,1 = 1400,0300,878T,001C,0 ALT MSG 1,8 = –2,–2, 2, .HOUR+100*.MIN, .SEC WRI ’PRESS RETURN TO SET TIME –––’,& ;%Q SND MSG 1 RCV MSG ALT 1,4 = 001D SND MSG 1 RCV MSG DAC REM .HOUR,.MIN,.SEC EM Macro execution sample: _______________________

>:SETTIME HOUR ––––>14 MIN –––––>27 SEC –––––>0 PRESS RETURN TO SET TIME –––> >

013 211 31515 AAAA EA 158

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.4.2 Macro: Define Message Interactively __________________________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : DEFMSG # parameter : none # function : defines a message in library, parameters are prompted for. # create : P. Oosterhaven # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC DEFMSG ADD .I,.Y=TRUE,.N=FALSE,.P=8 ADD .BV=0,.BVF=1,.DV=2,.BO=3,.BI=4,.BIF=5,.B=8,.BF=9,.BOF=A, ADD .D=E,.DT=E ’ LIBRARY NO –––––––––––––––––––––––’,& ADD .L=%Q ’ ROUTING NO (DECIMAL) –––––––––––––’,& ALT MSG .L,3=%QT,0,0 ’ MSG TYPE (B,BF,BV,BI,BO,DT,DV)––––’,& ADD .T=.%Q IF.T<3 .P=9T ENDI ’ PRIORITY (MAX 7) –––––––––––––––––’,& .I=%Q*1000+.T*100 ’ WITH BUFFER ? (Y/N) ––––––––––––––’,& IF.%Q=TRUE .I=.I+20 .P=12T ’ BUFFER OFFS,SEGM,NO_OF_BYTES––––––’,& ALT MSG .L,9=%Q ENDI ALT MSG .L,2=.I IF.T<>8 ’ DESTINATION FIELDS (OPTIONAL)–––––’,& ALT MSG .L,4=0%Q ENDI ’ USER AREA SIZE (NO OF BYTES)––––––’,& .I=%Q IF .P=8T ALT MSG .L,1=100*.I OR .P=9T ALT MSG .L,1=100*(.I+2) ELSE ALT MSG .L,1=100*(.I+8) ENDI ’ MSG PARAMETERS (MAX 8 INTS)–––––––’,& ALT MSG .L,.P=0%Q ’ MSG PARAMETERS (NEXT 8 INTS)––––––’,& ALT MSG .L,.P+8T=0%Q WRI MSG .L EM

013 211 31515 AAAA EA 159

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A Macro execution sample: _______________________

>:DEFMSG LIBRARY NO –––––––––––––––––––––––>1 ROUTING NO (DECIMAL) –––––––––––––>5555 MSG TYPE (B,BF,BV,BI,BO,DT,DV)––––>DT PRIORITY (MAX 7) –––––––––––––––––>4 WITH BUFFER ? (Y/N) ––––––––––––––>Y BUFFER OFFS,SEGM,NO_OF_BYTES––––––>4*64,SEG(MSG),10 DESTINATION FIELDS (OPTIONAL)–––––>0,0 USER AREA SIZE (NO OF BYTES)––––––>4 MSG PARAMETERS (MAX 8 INTS)–––––––>1,2 MSG PARAMETERS (NEXT 8 INTS)––––––> MSG TYPE ADDR SRC_PID DST_PID LLRA PTFF PATH BUF_PTR SIZE 5555 DT 0006 0150_DC18 CD40_CD40 0C00 4E20 .... 9638:0190 0010 DATA 0001 0002 >

013 211 31515 AAAA EA 160

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.5 Breakpoint Handling Macros _______________________________

A.5.1 Macro: Demonstrate Breakpoint Trigger ____________________________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : BRPDEMO # parameter : none # function : demonstrates the usage of SW breakpoints # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC BRPDEMO ACT PTCE FET 729T ;maintenace stub FMM ADD.STUB = CS:IP ;FMM Code Segment ADD.PID=WOR(POI(POI 407F:0)+1E)+2*44T+16 # define msg to trigger breakpoint ALT 2,1=0,2E00,1234T,WOR 4060:E,.PID # WRI BRP .STUB+24,COU,–2 ;transient breakpoint ’DISPLAY COUNTING BREAKPOINT (WITH COUNTER –2=FFFE)’ BRP ;display breakpoint WRI SND MSG 2 ;trigger breakpoint ’DISPLAY COUNTING BREAKPOINT AFTER FIRST MATCH’ BRP WRI ’DISPLAY TRIGGER MESSAGE’ SND MSG 2 ;trigger breakpoint WAI EVE 1 ;wait for match BRP .STUB+24,SUS ;suspend process WRI ’DISPLAY SUSPENDING BREAKPOINT’ BRP ;display breakpoint WRI ’DISPLAY TRIGGER MESSAGE’ SND MSG 2 ;trigger breakpoint WAI EVE 1 WRI ’CHECK PROCESS ON BRP’ CE ;display remote status WRI ’CURRENT STACK OF PROCESS–> SS:SP–10’ WOR SS:SP–10 LEN 8 ’SOME STATIC DATA–> DS:0’ WOR DS:0 LEN 2 WRI ’STEP THROUGH NEXT 5 INSTRUCTIONS’ COU 5 GO CS:IP EVA CS:IP END WRI ’DISASSEMBLE NEXT INSTRUCTIONS’ ASM CS:IP LEN 8 013 211 31515 AAAA EA 161

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A WRI GO ;release process ’PROCESS RELEASED’ CE DAC EM

013 211 31515 AAAA EA 162

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


DISPLAY COUNTING BREAKPOINT (WITH COUNTER –2=FFFE) BREAKPOINT BYT PID MODE .STUB+0024 81 FFFE COUNTING DISPLAY COUNTING BREAKPOINT AFTER FIRST MATCH BREAKPOINT BYT PID MODE .STUB+0024 81 FFFF TRANSIENT DISPLAY TRIGGER MESSAGE *** BREAKPOINT MATCHED .STUB+0028 CS IP RAX RBX RCX RDX SS SP BP DS SI ES DI FLA SLAVE 0CD7 002E FD12 04D2 0CD7 1F80 6080 FDA8 FDC0 8280 F206 6080 0008 F293 0006 DISPLAY SUSPENDING BREAKPOINT BREAKPOINT BYT PID MODE .STUB+0024 81 FFFF SUSPEND DISPLAY TRIGGER MESSAGE *** BREAKPOINT MATCHED .STUB+0028 CS IP RAX RBX RCX RDX SS SP BP DS SI ES DI FLA SLAVE 0CD7 002E FD12 04D2 0CD7 2400 6080 FDA8 FDC0 8280 F206 6080 0008 F293 0006 CHECK PROCESS ON BRP ADDR LCE PROC STATUS BREAK_PID PCS –0006 0260 0150 ON_BRP 0150_B002 7 CURRENT STACK OF PROCESS–> SS:SP–10 WOR 6080:FD98 = 0CD7 04D2 FD12 FDC0 FDA0 002E 0CD7 F293 SOME STATIC DATA–> DS:0 WOR 8280:0000 = FFFF 0000 STEP THROUGH NEXT 5 INSTRUCTIONS 0CD7:006C .STUB+0066 0CD7:006F .STUB+0069 0CD7:0073 .STUB+006D 0CD7:009A .STUB+0094 0CD7:009D .STUB+0097 DISASSEMBLE NEXT INSTRUCTIONS .STUB+0097 AND SI,#000F .STUB+009B JL .STUB+00C0 .STUB+009D CMP SI,#02 PROCESS RELEASED ADDR LCE PROC STATUS BREAK_PID PCS –0006 0260 0150 ACTIVE FFFF_FFFF 7

013 211 31515 AAAA EA 163

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.6 HW Trace Macros ____________________

A.6.1 Macro: Demonstrate HW code tracing _________________________________________

DEF MACRO CODETRC FET 729T ;MAINTENANCE STUB FMM ADD .STUB=CS:IP ADD .PID=WOR(POI(POI 407F:0)+1E)+RAX*44T+16 ;PROCESS_ID OF STUB ALT MSG 1,1=0,2E00,1234T,WOR 4060:E,.PID ;MSG TO TRIGGER STUB ; ; WRI ’ TRACE PART OF CODE EXECUTED BY MAINT. STUB FMM’ WRI ; RES SOF ONT CHA 1,ADD=.STUB+1E,UPT=.STUB+CB ARM TRF ; ;TRACE ACTIV ; SND MSG 1 ;TRIGGER STUB PRI 26 WRI ; WRI ’ TRACE BRANCHES EXECUTED BY MAINT. STUB FMM’ WRI ; ARM BRA SND 1 PRI TRF EM

013 211 31515 AAAA EA 164

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


TRACE PART OF CODE EXECUTED BY MAINT. STUB FMM .STUB+0094 MOV SI,(BX)+05 40D45–REA–D22E .STUB+0097 AND SI,#000F .STUB+009B JL .STUB+00C0 .STUB+009D CMP SI,#02 .STUB+00A0 JG .STUB+00C0 .STUB+00C0 PUSH SS A3BA0–WRI–A380 .STUB+00C1 LEA AX,(BP)+F6 .STUB+00C4 PUSH AX A3B9E–WRI–03B0 .STUB+00C5 MOV BX,#0002 .STUB+00C8 PUSH BX A3B9C–WRI–0002 .STUB+00C9 MOV BX,BP .STUB+00CB INT 30 000C0–REA–00F0 000C2–REA–4040 A3B9A–WRI–F206 A3B98–WRI–5E14 A3B96–WRI–00D3 TRACE BRANCHES EXECUTED BY MAINT. STUB FMM 4D1B:000A IRET .STUB+001E LDS .STUB+0028 JNE .STUB+0066 LDS .STUB+006D JNE .STUB+0094 MOV .STUB+00A0 JG .STUB+00C0 PUSH .STUB+00CB INT 404F:0000 JMPL .X+1457 MOV

013 211 31515 AAAA EA 165

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.6.2 Macro: Demonstrate HW data tracing. __________________________________________

DEF MACRO DATATRC ; WRI ’ TRACE DATA ACCESS TO LWA’ WRI ; RES SOF ONT CHA 1,ADD=LWA,UPT=LWA+16,BYT ARM TRF MEM,PRE BYT LWA+10=93,12,A,37,FF,0,CE,EA BYT LWA+10 LEN 8 WRI PRI 18 ; EM Macro execution sample: _______________________

TRACE DATA ACCESS TO LWA BYT A380:5010 = 93 12 0A 37 FF 00 CE EA 8D33:0004 MOVS A8810–WRI–93 A8811–WRI–12 A8812–WRI–0A A8813–WRI–37 A8814–WRI–FF A8815–WRI–00 A8816–WRI–CE 8D33:0004 MOVS A8810–REA–93 A8811–REA–12 A8812–REA–0A A8813–REA–37 A8814–REA–FF A8815–REA–00 A8816–REA–CE 7345:000D MOV

013 211 31515 AAAA EA 166

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.6.3 Macro: Time measurements using levels ____________________________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : LOOP # parameter : none # function : measures the time it takes MPTMON to execute a loop within # a macro. # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC LOOP RES SOF ;start clean TRI 1,ADD=LWA,WRI ;trigger LWA written LEV 0,CHA=1,NEX=1,TON ;switch timer on LEV 1,CHA=1,NEX=1,COU,CHA=5,TOF,FIN ;count next writes ARM BEG=–8 ;end if 8 times counted # BYT LWA=0 ;trigger form level 0 to 1 COU 8 ;execute loop BYT LWA=(BYT LWA) + 1 END ;counter overflows at 8th loop # WAI TRF ’DISPLAY EXECUTION TIME’ DIS ARM ;display execution time EM Macro execution sample: _______________________

DISPLAY EXECUTION TIME TIMER: 0000.225912 OCC–COUNTER: 0000

013 211 31515 AAAA EA 167

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.6.4 Macro: Time measurements using extended trace mode _________________________________________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : TRFTIME # parameter : none # function : demonstrates time measurement (using a TRFB) # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC TRFTIME FET 729T ;maintenance stub FMM ADD .STUB = CS:IP ;FMM Code Segment ADD .PID = WOR(POI(POI 407F:0)+1E)+2*44T+16 ;process–id of maint. stub # # define msg to trigger maintenance stub FMM ALT 1,1=0,2E00,1234T,WOR 4060:E,.PID # ’ELAPSED TIME FOR MAINT. STUB FMM TO HANDLE UNKNOWN MESSAGE’ WRI # RES SOF TRI 1,ADD=.STUB+1C,EXE ;entering main wait state TRI 2,ADD=.STUB+1E,EXE ;receiving a message LEV 0,CHA=2,TON,NEX=0,CHA=1,TOF ARM SND 1 ;trigger maint. stub SET DIS WAI TRF RES DIS # WRI ’EXECUTION TIME ON MAINT. STUB CODE TO HANDLE UNKNOWN MESSAGE’ WRI # ONT CHA 1,ADD=.STUB L CB ARM TTR SND 1 ;trigger maint. stub SET DIS WAI TRF RES DIS EM Macro execution sample: _______________________

ELAPSED TIME FOR MAINT. STUB FMM TO HANDLE UNKNOWN MESSAGE *** FINAL LEVEL REACHED TIMER: 0000.000219 OCC–COUNTER: 0000 EXECUTION TIME ON MAINT. STUB CODE TO HANDLE UNKNOWN MESSAGE *** FINAL LEVEL REACHED TIMER: 0000.000038 OCC–COUNTER: 0000

013 211 31515 AAAA EA 168

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.7 MMC Handling Macros ________________________

A.7.1 Macro: Protect MPTMON Library ____________________________________

>MAC PROTECT DEF MAC PROTECT ;CHANGE MPTMON FILE PROTECTION ;ORIGINAL KEY: .SR. WRI ’LIBRARY NUMBER (DECIMAL) ––’,& ADD.FILE=%QT IF.FILE>969T OR .FILE<960T WRI’NUMBER OUT OF RANGE’ RET MAC END BAS=T <PW22> <MODIFY–FDB:LFILID=%(.FILE),AUTHMDFY=”AB”; VER REP EM

013 211 31515 AAAA EA 169

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


>:PROTECT LIBRARY NUMBER (DECIMAL) ––>964 DIVF _ STUTTGART 1984–10–28 17:44:30 SU <MODIFY–FDB:LFILID= 964,AUTHMDFY=”AB”; SEQ=0466.841028 9002 COM=0393 JOK SUBMITTED 9000 RESULT FOLLOWS

DIVF _ STUTTGART 1984–10–28 17:44:45 SU SEQ=0466.841028 0336 PERIPHERAL SERVICE ROUTINES REPORT OF MODIFY FDB MAINCODE = SUCCESS SUBCODE = NULL –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– LFILID = 964 LFILNAME = A964AA03 RECORLEN = 16 FILELEN = 32767 AUTHREAD = AR AUTHWRIT = JR AUTHMDFY = AB TRSLFRMT = NOTRANS ACCSATTR = RNDMDFY RECATTR = OFF FILETYPE = SYSTEM DATATYPE = ASCII TIMRST = TOTOPEN TIMCLASS = MEDIUM –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– PFILNAME = MPTMON–LIBRARY00 DEVLIST = B’11111000 DISK: ALOCSIZE = 9999 EXTNSIZE = 9999 TAPE: BLOCKLEN = 0 GENRNBR = 1 ACCESS = VDU: INPTDELM = > SCRNLOC = 1 SCRNLIN = 20 PRNT: TOPMARG = 1 LEFTMARG = 1 LN = 60 REPORT REFERENCE NUMBER = 0336

013 211 31515 AAAA EA 170

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.7.2 Macro: MOUNT Magnetic Tape _________________________________

DEF MAC MOUNT IF ’%0’=’’ WRI’PROVIDE DEVICE ID’ RET MAC END <PW22> <MOUNT–MAGTAPE:DEVICE=%0, < VOLIDF=”BACKUP”,OWNIDF=”OOSTERHAVEN”,VOLTYPE=1,MOUNT; VER REP EM Macro execution sample: _______________________

>:MOUNT MTB1 DIVF _ STUTTGART 1984–10–28 17:11:40 SU <MOUNT–MAGTAPE:DEVICE=MTB1, VOLIDF=”BACKUP”,OWNIDF=”OOSTERHAVEN”,VOLTYPE=1,MOUNT; SEQ=0459.841028 9002 COM=0411 JOK SUBMITTED 9000 RESULT FOLLOWS

DIVF _ STUTTGART 1984–10–28 17:11:54 SU SEQ=0459.841028 0339 PERIPHERAL SERVICE ROUTINES COMPLETION REPORT MOUNT MAGTAPE CPLCODE = SUCCESS REPORT REFERENCE NUMBER = 0339

013 211 31515 AAAA EA 171

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.7.3 Macro: Perform Diagnostic Test _____________________________________

DEF MAC DIAGTST RES ERR SET SUP 7 SET ERR ; Disable Devices <MA> <DISABLE:SBL=TASL,NA=%0,NBR=%1&&%2; VER REP ’ SUCCESSFUL’,’0045’ ; Run Test loop ADD .I=%1 COU %2 WHILE IEC = 0 <S12> <TEST:SBL=TASL,NA=%0,NBR=(.I); VER REP ’ SUCCESSFUL’,’0047’ ENDC ; Initialize Devives <S12> <INITIALISE:SBL=TASL,NA=%0,NBR=%1&&%2; VER REP ’ SUCCESSFUL’,’0045’ IF IEC = 0 WRI ’Test(s) successfully completed.’ ENDIF RES SUP EM

013 211 31515 AAAA EA 172

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.8 Menu Macros ________________

A.8.1 Macro: MMC Login _______________________

DEF MAC LOGIN ;PROVIDES THE ENTRY TO MENU–DRIVEN MMC SEL LIB 2,969T SET ERR SET MEN CLR WRI ’PLEASE PROVIDE THE MMC PASSWORD AND PRESS RETURN’ WRI MMC ;Login to MMC and save password /* Control–X to cancel this login */ REP CAL MENU ENDR EM

A.8.2 Macro: System 12 Primary Menu ____________________________________

DEF MAC MENU WRI’ :MENU’,& LOC 0,54T TIM WRI WRI’ PRIMARY MENU SYSTEM 12 DBP EXCHANGES ’ WRI WRI’ 1. SUBSCRIBER ADMINISTRATION’ WRI’ 2. TRUNK ADMINISTRATION’ WRI’ 3. ROUTING ADMINISTRATION’ WRI’ 4. TARIFF AND CHARGING’ WRI’ 5. MEASUREMENTS AND STATISTICS’ WRI’ 6. MAINTENANCE’ WRI’ 7. SYSTEM OPERATIONS’ WRI’ 8. INPUT–OUTPUT MANAGEMENT’ WRI’ 9. DATA BASE MANAGEMENT’ WRI WRI’ A. WAIT FOR MMC REPORTS’ WRI’ X. EXIT’ WRI WRI WRI’ SELECTION NUMBER ––––––’,& CAL MENU%Q EM

013 211 31515 AAAA EA 173

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.9 Relation Display Macros ____________________________

A.9.1 Macro: Display relation ______________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : DISREL # parameter : <RELATION–ID>,(<TUPLE_NBR>) # function : display the contents (all tuples) of the relation with the # specified id or optionally a specified tuple. # created : 28.11.1986 P. Oosterhaven # updated : 14.02.1990 J. Langton – database version 4 # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC DISREL (REL–ID,TUP–NBR) # ADD .DLS=(WOR MP+1A):0 FET REL 4723T DEF .@GDIR=DS:SI # SETMEN FET REL %0 ADD .IEC=IEC RESMEN IF .IEC=0 #local real relation ADD .PA=DS:SI,.LDIR=ES:DI,.LDIC=.DLS+(WOR .LDIR+4),.RIAP=.PA+(WOR .LDIR+6) OR .IEC=77T ’ RELATION NOT LOCAL REAL’ ADD .R_GDIR=ES:RBX IF BYT .R_GDIR+2=3 ’ PROCEDURAL REL WITH START OFFSET = ’,WOR .R_GDIR+6 ’ PROCEDURAL DIRECTORY AT ADDRESS = ’,.DLS+(WOR .R_GDIR+4) ENDI RET MAC ELSE ’ RELATION NOT FOUND’\ABO MAC END # ADD .TUP_SZE=RAX,.NBR_TUP=RCX,.MAX_TUP=WOR .RIAP+6 ADD .NBR_DOM=BYT .RIAP,.FAST=(BYT .RIAP+C AND 10)/10 ADD .DOM_SZE,.TUP_PTR,.TUP_NBR=1 ADD .@PTR,.@ACC,.@LEN,.@OFS,.@POS,.@OPR # # copy LOCAL DICTIONARY into LWA and read from here COPMEM .LDIC,.NBR_DOM*4 # IF.NBR_TUP=0 ’ *** NO TUPLES POPULATED’\ABORT OR’%1’<>’’ # display only the specified Tuple number .NBR_TUP=1\.TUP_NBR=%1 IF.TUP_NBR>RCX ’ *** TUPLE NOT POPULATED’\ABORT END END 013 211 31515 AAAA EA 174

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A # set ptr to required tuple .TUP_PTR=.PA+(.TUP_NBR–1)*.TUP_SZE # BAS=H COU .NBR_TUP .LDIC=LWA # ’’\’ TUPLE: ’,.TUP_NBR,’ AT ’,.TUP_PTR,& IF .FAST=TRUE \ ’ IN USE’ ;FAST ACCESS REL. ALWAYS POPULATED ELSE # look in tuple status info. at relevant bit position .@OFS=(.TUP_NBR–1)/8 .@POS=.TUP_NBR–.@OFS*8 .@OPR=100 COU.@POS .@OPR=.@OPR/2 ENDC IF (BYT(.RIAP+20T+.@OFS)AND.@OPR)=0\’ IN USE’ ELS\’ DELETED’ ENDI END # # display domains of tuple # COU .NBR_DOM # get offset, length and access from local dictionary .@PTR=.TUP_PTR+(WOR.LDIC) \ .DOM_SZE=BYT.LDIC+2 \ .@ACC=BYT.LDIC+3 ’ OFFS(’,WOR .LDIC,’) = ’,& IF(.@ACC AND 3) = 2\’INDEX’ ELS REP IF.DOM_SZE>10\.@LEN=10 ELS\.@LEN=.DOM_SZE END IF(.@ACC AND 40)=40 ;WORD ORIENTED WRI WOR.@PTR LEN.@LEN/2 ELS WRI BYT.@PTR LEN.@LEN END .@PTR=.@PTR+10 .DOM_SZE=.DOM_SZE–10 WHI.DOM_SZE>0 ’ ’,& END ENDI .LDIC=.LDIC+4 ENDC .TUP_PTR=.TUP_PTR+.TUP_SZE .TUP_NBR=.TUP_NBR+1 ENDC EM

013 211 31515 AAAA EA 175

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


>:DISREL .FMM_CTB TUPLE: 0001 AT DC48:0000 IN USE OFFS(0000) = INDEX OFFS(0000) = 0077 OFFS(0002) = C000 OFFS(0004) = 0B7C OFFS(0006) = 929C OFFS(0008) = 0000 OFFS(000A) = 0003 OFFS(000C) = 0400 OFFS(000E) = 0000 OFFS(0010) = 40 OFFS(0011) = 00 TUPLE: 0002 AT DC48:0012 IN USE OFFS(0000) = INDEX OFFS(0000) = 0452 OFFS(0002) = C005 OFFS(0004) = ADF0 OFFS(0006) = 9625 OFFS(0008) = 0000 OFFS(000A) = 0003 OFFS(000C) = 0100 OFFS(000E) = 0100 OFFS(0010) = 40 OFFS(0011) = 40 *** ERROR: PROCESSING ABORTED >

013 211 31515 AAAA EA 176

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.10 Data Base Access Macros _____________________________ CAUTION: The macros presented hereafter, are not intended to be used and ar ________ not tested. They are only provided to give an idea how direct DBCS access may work. Refer to ”3.9.4 Call database interface (DB–V2)” on page 68

A.10.1 Macro: Init DB areas ____________________________

DEF MAC INIT_DB ADD.@O=OFFS(LWA),.@S=SEGM(LWA) ;init DB–areas WOR LWA+00=0,0,0,0,0,0,0 WOR LWA+0E=.@O+40,.@S,.@O+80,.@S,%1+10T,.@O+F6,.@S WOR LWA+1C=.@O+28,.@S,.@O+30,.@S,4,0 WOR LWA+40=0,0,0,0,0,0,0,0 WOR LWA+F6=0,0,0,0,0 EM

A.10.2 Macro: Get in Sequence ______________________________

DEF MAC GET ;LIST ALL TUPLES OF ANY RELATION ;%0=RELATION ID ;%1=TUPLE SIZE ; :INIT_DB WOR LWA=0000,%0 ;GET FIRST TUPLE DBS ACC %0,10 WOR LWA=0200 ;GET IN SEQ REP WHILE WOR LWA+8=0 ;WHILE STATUS OK BYT LWA+100 LEN %1 ;DISPLAY TUPLE DBS ACC A,A ;GET NEXT TUPLE END IF WOR LWA+8<>2 ;TUPLE NOT FOUND IN SEQ WRI’ *** RELATION NOT ACCESSABLE’ END EM Macro execution sample: _______________________

BYT A380:4100 = 01 00 77 00 00 C0 D1 5B 23 9A 00 00 03 00 00 02 BYT A380:4110 = 00 00 40 00 BYT A380:4100 = 02 00 0E 00 05 C0 1F 5D 2F 9A 00 00 03 00 00 01 BYT A380:4110 = 00 01 40 40 BYT A380:4100 = 03 00 D9 02 00 C0 14 5E 41 9A 00 00 03 00 00 01 BYT A380:4110 = 00 00 40 00 BYT A380:4100 = 04 00 78 02 04 C0 25 5E 41 9A 00 00 03 00 00 01 BYT A380:4110 = 00 00 40 00

013 211 31515 AAAA EA 177

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.10.3 Macro: Convert Error type to Error name _______________________________________________

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : ERRNAME # function : DISPLAY THE NAME TEXT RELATED TO THE GIVEN ERROR TYPE # parameter : <ERROR–TYPE> # date : 17.11.87 programmer : DUMANLI # ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC ERRNAME (<ERROR–TYPE>) IF ’%0’ = ’’ WRI ’USE :ERROR ERROR_TYPE’ \ RET MAC ENDIF # # SET UP LOCAL WORK AREA WITH DB_PARMS STRUCTURE # WOR LWA=0 ;OPTION=no_option, COMMAND=get WOR LWA+2=1650T ;RELATION ID WOR LWA+4=0 ;DOMAIN–ID WOR LWA+6=0 ;TRANSACTION ID WOR LWA+8=0 ;DBCS RETURN STATUS WOR LWA+A=6 ;QUALIFICATION SIZE WOR LWA+E=LWA+40 ;POINTER TO QUALIFICATION WOR LWA+12=LWA+80 ;POINTER TO MODIFICATION WOR LWA+16=28T ;RUWA SIZE WOR LWA+18=LWA+F6 ;POINTER TO RUWA WOR LWA+1C=LWA+28 ;POINTER TO RESULT VALUE WOR LWA+20=LWA+30 ;POINTER TO HELD RELATIONS WOR LWA+24=4 ;RELEASE TABLE SIZE WOR LWA+26=0 ;LOGICAL CE ID # WOR LWA+F6=0,0,0,0,0 ;SET UP RUWA WOR LWA+40=1,0,%0 ;SET UP QUALIFICATION AREA # DBS ACC 1650T,0 # IF WOR LWA+8 <> 0 WRI ’PLCES ARE NOT AVAILABLE OR ERROR TYPE NOT FOUND’ RET MAC ENDIF BAS=H WRI ’ ERROR TYPE : ’,WOR LWA+100,’H (’,& BAS=T WRI WOR LWA+100,’) – ’,& BAS=A WRI BYT LWA+102 L 10 BAS=H EM Macro execution sample: _______________________

:ERRNAME 4 ERROR TYPE : 0004H ( 4) – SANITY_TIMER :ERRNAME 1 ERROR TYPE : 0001H ( 1) – MEM_INV_ADDR 013 211 31515 AAAA EA 178

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A A.11 Command Table Generator Macro. ____________________________________ CAUTION: The macro presented here, is tested but may have to be modifie ________ depending on the actual MPTMON version in running. The use of this macro is explained in ”3.18 Resident macro tables” on page 122.

A.11.1 Macro: Generate Function Table ______________________________________

# –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : GENTAB # parameter : <TABLE ADDRESS> # function : saves all macros in free memory # created : 24.10.1986 J. Tiekenheinrich # modified : 08.12.1986 P. Oosterhaven (keep space for ADDTAB) # –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC GENTAB (TAB_ADDRESS) SET BDFC ACT PTCE IF’%0’=’’ ’ *** ERROR: TABLE ADDRESS MISSING’\DAC\ABORT END ADD.@MSP=MSP ADD.@NBR_MAC=WOR.@MSP+A,.@NBR_SYM=(WOR.@MSP+4)+1 ADD.@MAC_TAB=POI.@MSP+6,.@SYM_TAB=POI.@MSP+0,.@CMD_TAB=%0 # # MAKE THE LAST 3 SYMBOLS TO BE ”LOCAL” # DON’T CHANGE THE SEQUENCE OF SYMBOLS DEFINED HEREFORE # BYT.@SYM_TAB+(.@NBR_SYM+0)*10+E=1 ;MAC_TAB BYT.@SYM_TAB+(.@NBR_SYM+1)*10+E=1 ;SYM_TAB # # BYT.@SYM_TAB+(.@NBR_SYM+2)*10+E=1 ;CMD_TAB # commented out to support write protected memory # ADD.@MAC_LEN,.@CMD_ADD=.@CMD_TAB+64T*10,.@MAC_ADD ADD.@LAST_SYM=.@SYM_TAB+(WOR.@MSP+4)*10 # COU.@NBR_MAC .@MAC_ADD=POI(.@MAC_TAB+10T) BYT.@LAST_SYM–2=1 ;make MAC_ADD to local .@MAC_LEN=WOR(.@MAC_TAB+14T) # # copy directory entry # BYT.@CMD_TAB=BYT.@MAC_TAB LEN 10T WOR.@CMD_TAB+10T=.@CMD_ADD,.@MAC_LEN # # copy macro body # REP\WHI.@MAC_LEN>0 BYT.@CMD_ADD=BYT.@MAC_ADD LEN 20 .@CMD_ADD=.@CMD_ADD+20 .@MAC_ADD=.@MAC_ADD+20 .@MAC_LEN=.@MAC_LEN–20 013 211 31515 AAAA EA 179

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A END # # next directory entry # .@CMD_TAB=.@CMD_TAB+10\.@MAC_TAB=.@MAC_TAB+10\EVE END # # set up nbr of cmds in table # WOR %0=.@NBR_MAC SEL TAB %0 ADD.@TAB_SIZE=OFFS(.@CMD_ADD)–OFFS(%0) WRI ’FUNCTION TABLE SIZE: ’,.@TAB_SIZE DAC EM

# –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : COPMEM # parameter : <SOURCE–PTR>,<DESTINATION–PTR>,<NUMBER–OF–BYTES> # function : copies N bytes (max 64k) from source to destination address # date : 16.09.1986 H. Egenhofer # –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC COPMEM (SRC_PTR,DEST_PTR,NO_BYTES) ADD.@@LEN=%2 ADD.@@BLOCK=.@@LEN/32T,.@@BYTES=.@@LEN–.@@BLOCK*32T COU.@@BLOCK .@@LEN=.@@LEN–32T BYT %1+.@@LEN=BYT %0+.@@LEN L 32T END BYT %1=BYT %0 L .@@BYTES EM

# –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– # macro name : ADDTAB # parameter : none # function : adds all macros to the current table. # If oke, all macros are removed # created : 08.12.1986 P. Oosterhaven # –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– DEF MAC ADDTAB () SET BDFC ACT PTCE ADD.@MSP=MSP IF’%0’<>’’ WOR.@MSP+C=%0 ;select table END ADD.@NBR_MAC=WOR.@MSP+A,.@NBR_SYM=(WOR.@MSP+4)+1 ADD.@MAC_TAB=POI.@MSP+6,.@SYM_TAB=POI.@MSP+0,.@CMD_TAB=POI.@MSP+C # # MAKE THE LAST 3 SYMBOLS TO BE ”LOCAL” # DON’T CHANGE THE LAST CMD LINE # BYT.@SYM_TAB+(.@NBR_SYM+0)*10+E=1 ;mac_tab BYT.@SYM_TAB+(.@NBR_SYM+1)*10+E=1 ;sym_tab 013 211 31515 AAAA EA 180

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX A # # BYT.@SYM_TAB+(.@NBR_SYM+2)*10+E=1 ;CMD_TAB # commented out to support write protected memory # # find where last table element is stored # ADD.@MAC_LEN ADD.@CMD_ENT=.@CMD_TAB+(WOR.@CMD_TAB)*10 ADD.@CMD_ADD=(POI.@CMD_ENT–6T)+(WOR.@CMD_ENT–2T) ADD.@MAC_ADD,.@LAST_SYM=.@SYM_TAB+(WOR.@MSP+4)*10 # COU.@NBR_MAC .@MAC_ADD=POI(.@MAC_TAB+10T) BYT.@LAST_SYM–02=1 ;make MAC_ADD local # # BYT.@LAST_SYM–12=1 ;make CMD_ADD local # commented out to support write protected tables # .@MAC_LEN=WOR(.@MAC_TAB+14T) # # copy directory entry # BYT.@CMD_ENT=BYT.@MAC_TAB LEN 10T WOR.@CMD_ENT+10T=.@CMD_ADD,.@MAC_LEN # # copy macro body # REP\WHI.@MAC_LEN>0 BYT.@CMD_ADD=BYT.@MAC_ADD LEN 20 .@CMD_ADD=.@CMD_ADD+20 .@MAC_ADD=.@MAC_ADD+20 .@MAC_LEN=.@MAC_LEN–20 END .@MAC_TAB=.@MAC_TAB+10\.@CMD_ENT=.@CMD_ENT+10\EVE END # # store new number of cmds # WOR.@CMD_TAB=(WOR.@CMD_TAB)+.@NBR_MAC SEL TAB .@CMD_TAB ADD.@TAB_SIZE=OFFS(.@CMD_ADD)–OFFS(.@CMD_TAB) WRI ’FUNCTION TABLE SIZE: ’,.@TAB_SIZE DAC REM MAC EM

013 211 31515 AAAA EA 181

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX B APPENDIX B. DATA STRUCTURES ___________________________

This appendix describes some data structures relevant to MPTMON’s operation as far as the user is concerned. They can be found in other documents as well and are not specific to MPTMON.

B.1 Message buffer layout __________________________ The word offset indicated in the layout is the one to be used in the ALT MSG command to create a message in the library.

word F 8 0 offset +–––––––––––––––––––––––+ 0 | forward link | |–––––––––––––––––––––––| 1 | length |rr rr|aa|uu| |–––––––––––+–––––––––––| 2 |prior|type | flags | |–––––––––––––––––––––––| 3 | routing number | |–––––––––––––––––––––––| 4 | 1 | |– destination –| 5 | 2 | |–––––––––––––––––––––––| 6 | 1 | |– sending process –| 7 | 2 | |–––––––––––––––––––––––|–––––––––––––––––––––––+ 8 | | path id for VIA msgs | 8 |–––––––––––––––––––––––| | | user buffer offset | 9 |–––––––––––––––––––––––| | user area | user buffer segment | A max. 40 bytes |–––––––––––––––––––––––| | | no of bytes in u.buf.| B |–––––––––––––––––––––––| | | | C remainder if msg | | with user buffer | | | | |–––––––––––––––––––––––|–––––––––––––––––––––––+ 1C | OS USE ONLY | +–––––––––––––––––––––––+

Explanation of message fields:

forward link := OSN use only, not to be set up by user. length := number of bytes in user area starting from

013 211 31515 AAAA EA 182

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX B word 8 onwards (max 40 bytes). rr rr := result of OSN routing algorithm, init with 0 01 – kept within CE 02 – sent to other CE – virtual path 03 – sent to other CE – data link 04 – sent to other CE – UCP aa := OSN audit flags, init with 0 uu := OSN buffer flags, init with 0 prior := msg priority, range 0 to 7 type := message type with values: 0 BASIC VIA 1 BASIC VIA FOR 2 DIRECTED VIA 3 BASIC ONTO 4 BASIC INTO 5 BASIC INTO FOR 6 BASIC SUBGROUP 7 BASIC SUBGROUP FOR 8 BASIC 9 BASIC FOR A BASIC ONTO FOR D BASIC TO E DIRECTED TO flags := 8 flags, init with ’00’, or ’20’ if with user buffer. Bit number: 7 forwarded 3 timer 6 routed 2 network 5 user buffer 1 tone bus 4 osn use 0 trace destin. 1 := path identity if type VIA logical CE id. if type INTO physical CE id. if type ONTO destin. 2 := discriminator if type FOR destin 1+2 := process id if type TO (normal 0,0) sender := process id of sender, set up by OSN path id := received path id. to be registered if VIA user area starts hereafter if no user buffer is attached.

ALT MSG 1,1=1000,4E20,9999T,0,0 ;means message 9999 routed DIRECTED TO, with USER BUFFER, ;priority 4, 16T user bytes of which 8 bytes used for ;user buffer spec. ALT MSG 1,9=OFFS(LWA),SEGM(LWA),100 ;means a MSG defined in the PTCE uses the LWA in the PTCE ;to store 100H bytes of data ALT MSG 1,C=1,2,3,4 ;means 8 bytes of remaining user area space BYT LWA = ’this is text in use buffer’ ;store some text in the user buffer

013 211 31515 AAAA EA 183

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX B B.2 Data Base Access (DB–V2) _____________________________ The data structures defined here are the ones to be used in the DBS ACC command for low–level DBCS access. They are not described in full detail and have to be used with extreme care. The offsets indicated in LWA (Local Work Area) are normal byte offsets.

DATABASE PARAMETERS +–––––––––––––––––––––––+ 0 | option | command | command: |–––––––––––––––––––––––| 00–GET 04–STORE 2 | relation identity | 01–GET_HOLD 05–HOLD |–––––––––––––––––––––––| 02–MODIFY 06–RELEASE 4 | domain identity | 03_DELETE 07–COUNT |–––––––––––––––––––––––| 6 | transaction identity | option: |–––––––––––––––––––––––| 00–NO_OPTION 03–ECHO 8 | DBCS return status | 01–IN_ORDER 04–ALL_TUP |–––––––––––––––––––––––| 02–INSEQ 06–FORCE A | qualification size | |–––––––––––––––––––––––| status: C | modification size | (see Appendix F) |–––––––––––––––––––––––| E | | |– qualification ptr –| | | |–––––––––––––––––––––––| 12 | | |– modification ptr –| | | |–––––––––––––––––––––––| 16 | ruwa size | (tuple size + 10) |–––––––––––––––––––––––| 18 | | |– ruwa ptr –| (points to user work area) | | |–––––––––––––––––––––––| 1C | | |– func. result ptr –| (points to result value) | | |–––––––––––––––––––––––| 20 | | |– release table ptr –| (points to held relations) | | |–––––––––––––––––––––––| 24 | release table size | |–––––––––––––––––––––––| 26 | logical ce id | (where data was found) +–––––––––––––––––––––––+

013 211 31515 AAAA EA 184

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX B B.3 Data Base Access (DB–V4) _____________________________ The data structures defined here are the ones to be used in the DB4 ACC command for low–level DBCS access. They are not described in full detail and have to be used with extreme care. The offsets indicated in LWA (Local Work Area) are normal byte offsets.

DATABASE PARAMETERS (Edition 2) +–––––––––––––––––––––––+ 0 | format param ( = 02) | command: |–––––––––––––––––––––––| 00–GET 04–STORE 2 | option | command | 01–GET_HOLD 05–HOLD |–––––––––––––––––––––––| 02–MODIFY 06–RELEASE 4 | domain identity | 03_DELETE 07–COUNT |–––––––––––––––––––––––| 6 | transaction identity | option: |–––––––––––––––––––––––| 00–NO_OPTION 03–ECHO 8 | DBCS return status | 01–IN_ORDER 04–ALL_TUP |–––––––––––––––––––––––| 02–INSEQ 06–FORCE A | qualification size | |–––––––––––––––––––––––| status: C | modification size | (see Appendix F) |–––––––––––––––––––––––| E | | |– qualification ptr –| | | |–––––––––––––––––––––––| 12 | | |– modification ptr –| | | |–––––––––––––––––––––––| 16 | ruwa size | (tuple size + 10) |–––––––––––––––––––––––| 18 | | |– relation ptr –| (points to relation table) | | |–––––––––––––––––––––––| 1C | | |– func. result ptr –| (points to result value) | | |–––––––––––––––––––––––| 20 | relation number | |–––––––––––––––––––––––| 22 | rel table size (= C) | |–––––––––––––––––––––––| 24 | DB return status 2 | |–––––––––––––––––––––––| 26 | logical ce id | (where data was found) +–––––––––––––––––––––––+

013 211 31515 AAAA EA 186

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


FUNCTIONAL RESULT +–––––––––––––––––––––––+ 28 | funct. result | +–––––––––––––––––––––––+

RELATION TABLE +–––––––––––––––––––––––+ 30 | relation identity | |–––––––––––––––––––––––| 32 | | |– RUWA ptr –| (points to relation work area) | | |–––––––––––––––––––––––| 36 | | |– GDIR ptr –| (points to global directory) | | |–––––––––––––––––––––––| 3A | logical ce id | +–––––––––––––––––––––––+

QUALIFICATION AREA +–––––––––––––––––––––––+ 40 | domain identity 1 | option: 00 – EQ |–––––––––––––––––––––––| 01 – NE 42 | value 1 | option 1 | 02 – LE | +–––––––––––| 03 – LEEQ | | 04 – GR |–––––––––––––––––––––––| 03 – LEEQ nn | domain identity 2 | 04 – GR |–––––––––––––––––––––––| 05 – GREQ | value 2 | option 2 | | +–––––––––––| | | |–––––––––––––––––––––––| | next qualification | : : | | +–––––––––––––––––––––––+

MODIFICATION AREA +–––––––––––––––––––––––+ 80 | layout as the | | qualification area | | |

013 211 31515 AAAA EA 187

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


RELATION WORK AREA +–––––––––––––––––––––––+ F6 | rel_hold | tup_hold | |–––––––––––––––––––––––| F8 | | |– start ptr –| | | |–––––––––––––––––––––––| FC | | |– actual ptr –| | | |–––––––––––––––––––––––| 100 | | | tuple requested | | | +–––––––––––––––––––––––+

013 211 31515 AAAA EA 188

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX B APPENDIX C. DEBUG MONITOR _________________________

The Test Debug Monitor is a small part of the OSN Error Handler which is able to communicate with the MPTMON Controller by simulating a MPTMON Slave FMM. This programm does the network communication without using OSN or Network Handler Software, so it enables a tester to get the status of the OSN, NH and FMM Data as constant data (like a BRP on the MDS) before a reload or restart is initiated by the Error Handler of a CE. This Programm can also be started by the final trigger interrupt of the HW Tracer Board and is able to print the contents of the HW Tracer. Like on a breakpoint, the software under test is no longer executed. The activation of the Debug Monitor for different cases (e.g. TRF final interrupt, restart or boot request) is controlled by the contents of domain 12 (byte 13T) of the relation R_FEATURES.

R_FEATURES (rel–id 288) D_FEAT_12, (byte 0D)

+––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+ | PTCE | spare | boot | extend || batch | TRF | debug–monitor | +––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+

debug–monitor: 0 = no action 1 = Debug Monitor for 10 minutes 2 = Debug Monitor for ever TRF: 0 = TRF interrupt is routed to MPTMON Slave SSM 1 = TRF interrupt is routed to Debug Monitor batch: 0 = no automatic batch file execution 1 = MPTMON automatically includes a batch file (default 957T) extend: 0 = no execution of extended Slave commands 1 = MPTMON Slave FMM is called for extended cmd execution boot: 0 = PTCEs are booted during system–start–up 1 = PTCEs are not booted during system–start–up spare: 0 = not used 1 = not used PTCE: 0 = PTCE will not enter Debug Monitor in case of error 1 = PTCE will enter Debug Monitor in case of error

013 211 31515 AAAA EA 189

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX D APPENDIX D. ERROR MESSAGES __________________________

The following is a list of MPTMON error messages and their error code values, which are assigned to the internal error code IEC in case of an error message display.

[01] *** ERROR: SYNTAX ERROR [02] *** ERROR: PARAMETER MISSING [03] * WARNING: SLAVE OUT OF SEQUENCE [04] *** ERROR: PATH BREAKDOWN [05] *** ERROR: COMMAND DISABLED [06] *** ERROR: SYMBOL NOT DEFINED [07] *** ERROR: BUFFER OVERFLOW [08] *** ERROR: INTERNAL ERROR [09] *** ERROR: INVALID CHARACTER [10] *** ERROR: PROCESSING ABORTED [11] * WARNING: SYMBOL REDEFINED [12] *** ERROR: REQUEST FAILED [13] *** ERROR: CE NOT ACTIVE [14] *** ERROR: NO LIBRARY HASH SPACE [15] *** ERROR: INT VALUE REQUIRED [16] *** ERROR: PTR VALUE REQUIRED [17] *** ERROR: MACRO NOT DEFINED [18] *** ERROR: MACRO ALREADY DEFINED [19] *** ERROR: TOO MANY MACROS [20] *** ERROR: MACRO LINE TOO LONG [21] *** ERROR: INVALID NAME [22] *** ERROR: VALUE OUT OF RANGE [23] *** ERROR: SLAVE TIMED OUT [24] *** ERROR: NO NESTING ALLOWED [25] * WARNING: TRACE BUFFER OVERFLOWED [26] * WARNING: MEMORY CHECK ERROR [27] *** ERROR: MEMORY NOT EQUIPPED [28] *** ERROR: BRP NOT ALLOWED HERE [29] * WARNING: BRP ALREADY DEFINED [30] * WARNING: BRP NOT FOUND [31] *** ERROR: SLAVE BUSY [32] * WARNING: TRACE BUFFER EMPTY [33] *** ERROR: IOS OPEN ERROR [34] *** ERROR: IOS READ/WRITE ERROR [35] *** ERROR: MEMBER NOT FOUND [36] *** ERROR: MEMBER TYPE ERROR [37] *** ERROR: MEMBER ALREADY DEFINED [38] *** ERROR: MACRO FRAME MISSING [39] * WARNING: SELECTED CE CHANGE [40] *** ERROR: PATH ALREADY IN USE [41] *** ERROR: NO PATH IN USE [42] *** ERROR: TRANSMISSION OVERFLOW [43] * WARNING: VERIFICATION FAILED [44] *** ERROR: NOT AUTHORIZED [45] *** ERROR: TOO MANY PARAMETERS [46] *** ERROR: COMMAND TIMED OUT [47] *** ERROR: UNRECOGNIZED COMMAND 013 211 31515 AAAA EA 190

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX D [48] *** ERROR: PROCESS STILL ON BRP [49] * WARNING: IOS OPEN ABNORMALITY [50] * WARNING: MEMBER WAS DELETED [51] *** ERROR: NO PROCESS ON BRP [52] *** ERROR: TOO MANY SYMBOLS [53] *** ERROR: INPUT LINE TOO LONG [54] *** ERROR: TOO MANY CE’S [55] *** ERROR: INVALID RECORD SIZE [56] *** ERROR: FMM ID NOT FOUND [57] *** ERROR: STACK OVERFLOW [58] *** ERROR: STRING LENGTH [59] *** ERROR: FILE RELEASE EXECUTED [60] * WARNING: JSQ AND RSQ MISMATCH [61] *** ERROR: INVALID PARAM KEYWORD [62] *** ERROR: COMMUNICATION FAILED [63] *** ERROR: INVALID SELECTOR [64] *** ERROR: OFFSET OUT OF RANGE [65] *** ERROR: TRF NOT EQUIPPED [66] *** ERROR: TRF HARDWARE FAILURE [67] * WARNING: LIST FILE ALREADY OPEN [68] *** ERROR: RELATION ID NOT FOUND [69] *** ERROR: OBC UNAVAILABLE [70] *** ERROR: OBC NOT SELECTED [71] *** ERROR: SSM ID NOT FOUND [72] *** ERROR: PARENTHESIS MISSING [73] *** ERROR: SYMBOL ALREADY DEFINED [74] * WARNING: OTHER BRP MATCHED [75] * WARNING: ANY PROCESS ASSUMED [76] * WARNING: OLD SLAVE ACTIVATED [77] *** ERROR: REL IS NOT LOCAL REAL [78] *** ERROR: ARGUMENT(S) INCORRECT [79] *** ERROR: INVALID FILE ID [80] *** ERROR: MODE CONFLICT [81] *** ERROR: DESTINATION NOT FOUND [82] * WARNING: RELATION IS PROCEDURAL [83] *** ERROR: INVALID PROCESSOR TYPE [84] *** ERROR: PROCESS ID NOT FOUND

013 211 31515 AAAA EA 191

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX E APPENDIX E. SYSTEM 12 IOS COMPLETION CODES __________________________________________

List of System 12 IOS completion codes which might be issued during library, retrieve, save, include or list commands.

IOS main completion codes: [00..] Successfull .. [01..] Warning .. [02..] Soft_Error .. [03..] Hard_Error ..

IOS sub completion codes: [..00] .. Null code [..01] .. Primary device [..02] .. Fallback device [..03] .. Twin primary [..04] .. Twin secondary [..05] .. Operator assigned [..06] .. Invalid logical device [..07] .. Illegal device [..08] .. Unequipped device [..09] .. Unavailable device [..0A] .. File not present [..0B] .. File not defined [..0C] .. File protected [..0D] .. Unauthorized access [..0E] .. Illegal access [..0F] .. No space [..10] .. End of file [..11] .. Offset wrong [..12] .. Software failure [..13] .. Hardware failure [..14] .. Maintenance intervention [..15] .. Time out [..16] .. Buffer overrun [..17] .. File already defined [..18] .. Operator intervention [..19] .. File fragmented [..1A] .. File corrupted [..1B] .. Device offline [..1C] .. Volume blocked [..1D] .. Volume not present [..1E] .. Volume already present [..1F] .. Wrong volume mounted [..20] .. End of tape [..21] .. SW–HW inconsistency [..22] .. Formatter or MTU error [..23] .. Parity error [..24] .. MT tape runaway [..25] .. MTU at begin of tape 013 211 31515 AAAA EA 192

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX E [..26] .. MT buffer overflow [..27] .. Undefined MT error [..28] .. State switched

013 211 31515 AAAA EA 193

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX F APPENDIX F. DATABASE STATUS INFORMATION _______________________________________

List of database completion codes which might be returned using the database access command.

Database status information: [0000] Successful execution

Warnings: [0001] No tuple found [0002] No more tuple in sequence [0003] Relation held by other user [0004] Tuple held by other user [0005] At least one tuple in relation is held by other user [0006] Related real relation held (redefined/virtual relation) [0007] DLS overlay reject

Errors: – Reported by the database: [0064] Reserved [0065] Wrong ”GET IN SEQUENCE” [0066] Command not valid [0067] Command on virtual relation not allowed [0068] Option not valid [0069] Domain not numeric [006A] Overflow in build–in–function [006B] Error in qualification [006C] Error in modification [006D] Relation identity not found [006E] No space available for storage [006F] Interprocessor communication failure [0070] Hold table full [0071] Tuple already stored [0072] Disk backed up inconsistency [0073] Not all copies of replicated relation have been updated [0074] Restart, forced release or rollback/rollforward was performed [0075] Relation held by requestor [0076] Error in completion from DFH [0077] Error reported from I/O system [0078] Error during syncronisation of replicated relation

013 211 31515 AAAA EA 194

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX G APPENDIX G. OSN PRIMITIVES IN ALPHABETICAL ORDER ________________________________________________

List of all OSN primitives and their corresponding decimal numbers which can be used for the CALL OSN command.

* – PCS 55–introduced primitive

FUNCT # CHILL / ASSEMBLER NAME DESCRIPTIVE FUNCTION ––––––––+–––––––––––––––––––––––––+––––––––––––––––––––––––––––––––––––––––––––– * 98T ABORT_PROCESS Allow RAM restart to abort a specific process 20T ABS_PERIODIC_TIMEOUT Start absolute periodic timeout 19T ABS_TIMEOUT Start absolute timeout * 39T BCAST_TO_DEV Broadcast a load packet to a special PBAS. 44T BROADCAST Broadcast load packet 21T CANCEL_TIMER Cancel a timer * 38T COND_GET_USER_BUF Get a user buf with optionsindicated by Non_Blocking_Flag 108T COND_MSG_SEND Send message with return code * 119T COND_MSG_SEND_EXC 775T CONVERT_VIRT_TO_PHYS Convert virtual address into 32–bit physical address (valid only in 286 virtual mode) 776T CONVERT_286_TO_86 Convert 286 long pointer into 8086 long pointer (valid only in 286 virtual mode) 64T CREATE_PROCESS Create a new process 516T DATA_LAUNCH Send I/O commands to OBCI/OBC via Cluster Handler over channel 16 514T DEVICE_OWN Claim ownership of a device 6T DISABLE_MEMORY_PROTECT Disable memory protection 45T DOUBLE_INDIRECT_FETCH Cluster channel double fetch 52T DPM_GET_MSG Get message from DPM 42T DPM_ROUTE Act/deact DPM routing 5T ENABLE_MEMORY_PROTECT Enable memory access protection 36T END_OF_TRANSMISSION Ack of EOT 15T ENTER_MONITOR Disable system interrupts 60T ERROR General error interface 90T ERROR_REPORT General error i/f w/sequence 22T EXEC_CLOCKED_PROCEDURE Start a clocked procedure 83T EXEC_TI_SEQUENCE Execute TI diagnostic instruction 16T EXIT_MONITOR Enable system interrupts 7T FMM_INIT_INFO RAM restart information 71T FORCE_DISABLE_TI_PORT Force TI port disable 68T FREE_FROM_PKT_RAM_DUPLEX Free transmit & receive channel 48T FREE_INDIRECT_SIMPLEX Stop TI RAM from sampling PCM 56T FREE_PATH Unjoin path 89T FREE_SCAN_RCV_TX_INDIRECT Stop loading PCM samples from Cluster path into packet RAM 49T FREE_TX_INDIRECT_SIMPLEX Stop speech to TI RAM 769T GET_ACCESS Get access to common areas 97T GET_AND_RESET_PARITY Returns to user the parity value for a UCP 76T GET_CHANNEL Allocate channel to diagnostic * 525T GET_CH_MAINT_PATH Establish path for maintenance 512T GET_CH_PATH Assigns pair of free cluster side channels to 013 211 31515 AAAA EA 195

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX G terminal 31T GET_DATA_LINK Get a held path data link 773T GET_DESCRIPTOR To set up new descriptor 24T GET_ELAPSED_TIME Calculate elapsed time 101T GET_EXCHANGE_DATA Get exchange information * 524T GET_FXD_CH_PATH Create a fixed CH path 54T GET_LOAD_PATH Get UCP, simplex or data link 1T GET_MSG_BUF Get system message buffer 102T GET_NETWORK_ID Get network address 86T GET_NR_LOAD_PKT_IN_Q No. of buffers on output queue 1024T GET_OWN_OVLD_STATUS Get own overload status 26T GET_PATH Get a user controlled path * 122T GET_PATH_ARRAY 100T GET_PCE_ID Get physical CE id 768T GET_PROCESSOR_PARAM Get target machine type, speed & address mode 25T GET_REAL_TIME Get current TOD information * 112T GET_REAL_TIME_EXT Get current TOD + time adjustment 102T GET_SPATA_PATH Get speech path 72T GET_TI_PORT Get TI port for maintenance 74T GET_TUNNEL_PORT Get a tunnel port 3T GET_USER_BUF Get user buffer from 8T HALT_CLOCKED_PROCEDURE Stop a clocked procedure 70T INIT_TI_PORT Enable TI port 515T IO_CMD Send I/O commands to DPTC device via Cluster Handler over Channel 16 46T JOIN_INDIRECT_SIMPLEX Fetch and transmit PCM 50T JOIN_PATH Join UCPs 67T JOIN_TO_PKT_RAM_DUPLEX Join receive and transmit thru packet RAM 34T LINK_RETURNED Condition of RET_LINK path * 115T MI_CALL_ERROR_HANDLER Force restart/bootstrap from MI 770T MODIFY_PROTECTED_MEMORY Modify protected memory 9T MRT_READ Read the message routing table 37T MRT_UPDATE Update message routing table 62T MSG_DEFER Defer message buffer 33T MSG_RECEIVED ACK of received message 87T MSG_REJECT Return message with error 61T MSG_SEND Transmit message buffer 63T MSG_WAIT Wait for incoming message 104T NEW_LCE_ID Change LCE id 91T NH_DEVICE_AUDIT Audit of NH TI facilities 92T NH_READ_IO_PORT Retrieve contents of I/O port 23T NOTE_CURRENT_TIME Note current time * 528T OBCI_BOOT_MODE Specify OBCI reaction in bootstrap * 111T OPEN_TUNNEL_MAINT Enable tunnel events after restart 93T OVL_ABORT Abort overlays in progress 94T OVL_DLOAD_END End of download 96T OVL_FMM_INFO FMM info on code, data & patches 95T OVL_XMIT Initiate overlay download 84T OWN_CE_ID Get process id, LCE id, PCE & VP 13T OWN_LCE_ID Get own logical CE identity 41T OWN_PROCESS_ID Id of running process *FF00H PKT_SEND Send IPP packet * 120T PROCESS_CHECK 51T READ_METERING_FLAG Read metering flags 66T READ_RESET_COUNTERS Statistical gathering primitive 81T READ_SPATA Read SPATA sample 013 211 31515 AAAA EA 196

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX G 32T REG_DATA_LINK Register a data link 27T REG_PATH Register process to UCP 65T REL_PARAMETER_TIMEOUT Rel timeout with I/O parameter 10T REL_PERIODIC_PARAM_TO Rel periodic timeout with param 18T REL_PERIODIC_TIMEOUT Start relative periodic timeout 17T REL_TIMEOUT Start relative timeout 43T RESET_ERROR_COUNTERS Reset error counters 106T RESET_LOCAL_TOD Sets TOD to user specified value 77T RET_CHANNEL Return TI channel * 526T RET_CH_MAINT_PATH Return cluster maintenance path 513T RET_CH_PATH Deassign SPATA path from terminal 774T RET_DESCRIPTOR Return descriptor to GDT pool (valid only in 286 virtual address mode) 2T RET_MSG_BUF Return system message buffer 121T RET_MSG_WITH_USER_BUF 28T RET_PATH Release a UCP 123T RET_PATH_ARRAY 73T RET_TI_PORT Return TI port 75T RET_TUNNEL_PORT Return network port 4T RET_USER_BUF Return user buffer * 521T RSU_DATA_LAUNCH Send data pkts to remote OBCI/OBC * 519T RSU_DEVICE_OWN Claim ownership of rm DPTC/OBCI * 517T RSU_GET_CH_PATH Establish SPATA path to remote dev * 529T RSU_GET_TERM_INTRA_PATH Establish INTRA path to remote dev * 522T RSU_GET_LDC_DATA Get link load information * 520T RSU_IO_CMD Send I/O packets to remote DPTC * 530T RSU_RECONFIGURE_PATH Deoptimize/optimize RSU INTRA path * 518T RSU_RET_CH_PATH Return SPATA path from remote dev * 523T RSU_UPDATE_SS_STATUS Update a single signalling stage * 531T RSU_USER_READ_SS_TABLE Read entire signalling stage table * 532T RSU_USER_UPDATE_SS_TABLE Update signal stage table per PCM 53T SCAN_RECEIVER Copy PCM samples to buffer 57T SEND_LOAD_PKT Send load packet 79T SEND_MAINT_PKT Send maintenance packet 80T SEND_SPATA Send SPATA sample thru loop 82T SEND_TUNNEL_WORD Send tunnel word 14T SET_EVENT_FLAG Flag to enable event handler * 88T SET_FLAG 30T SET_INTERRUPT_MASK Modify 2 ms interrupt control 55T SET_METERING_FLAG Write metering flags * 113T SET_OSN_PTF_PUBLICS Setup OSN publics for PTF 58T SET_OVERLOAD_CONDITION Set overload condition * 110T SET_OVLY_DEBUG_FLAG Force FMM dload, 10 min resident 29T SET_PCR Modify processor control register * 114T SET_SSM_TRACE_FLAG Act/Deact SSM tracing by PTF 11T SET_TI_PORT_INLET Initialize TI port pair 99T SET_TRACE_FLAG Set PTF trace flag 109T SET_X_OVER_STATE Inform OS on crossover status 69T SOFT_DISABLE_TI_PORT Disable TI port 107T STACK_CHECK Enables/disables stack check 12T TERMINATE Process termination with automatic notification 105T TERM_OPT_NOTIFY Process termination with optional notificat. 78T TI_PORT_MAINT_BUSY_BIT Modify TI port flag 35T TRANSFER_USER_BUF Initiate user buffer transfer 47T TX_INDIRECT_SIMPLEX Store receive channel PCM 013 211 31515 AAAA EA 197

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX G 40T UPDATE_CALENDAR CE date modification 59T VP_FAILURE Virtual path failure * 85T XLATE_UCP_CHAN Translate the LID of a UCP to its ports and channels * 118T XMIT_BCAST Broadcast user buffer

013 211 31515 AAAA EA 198

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX H APPENDIX H. OSN PRIMITIVES IN NUMERICAL ORDER _____________________________________________

List of all OSN primitives numbers (hexadecimal) and their corresponding names which may be helpful reading the TRF trace buffer.

* – PCS 55–introduced primitive

FUNCT # CHILL / ASSEMBLER NAME DESCRIPTIVE FUNCTION ––––––––+–––––––––––––––––––––––––+––––––––––––––––––––––––––––––––––––––––––––– 00 Invalid function number 01 GET_MSG_BUF Get system message buffer 02 RET_MSG_BUF Return system message buffer 03 GET_USER_BUF Get user buffer from 04 RET_USER_BUF Return user buffer 05 ENABLE_MEMORY_PROTECT Enable memory access protection 06 DISABLE_MEMORY_PROTECT Disable memory protection 07 FMM_INIT_INFO RAM restart information 08 HALT_CLOCKED_PROCEDURE Stop a clocked procedure 09 MRT_READ Read the message routing table 0A REL_PERIODIC_PARAM_TO Rel periodic timeout with param 0B SET_TI_PORT_INLET Initialize TI port pair 0C TERMINATE Process termination 0D OWN_LCE_ID Get own logical CE identity 0E SET_EVENT_FLAG Flag to enable event handler 0F ENTER_MONITOR Disable system interrupts 10 EXIT_MONITOR Enable system interrupts 11 REL_TIMEOUT Start relative timeout 12 REL_PERIODIC_TIMEOUT Start relative periodic timeout 13 ABS_TIMEOUT Start absolute timeout 14 ABS_PERIODIC_TIMEOUT Start absolute periodic timeout 15 CANCEL_TIMER Cancel a timer 16 EXEC_CLOCKED_PROCEDURE Start a clocked procedure 17 NOTE_CURRENT_TIME Note current time 18 GET_ELAPSED_TIME Calculate elapsed time 19 GET_REAL_TIME Get current TOD information 1A GET_PATH Get a user controlled path 1B REG_PATH Register process to UCP 1C RET_PATH Release a UCP 1D SET_PCR Modify processor control register 1E SET_INTERRUPT_MASK Modify 2 ms interrupt control 1F GET_DATA_LINK Get a held path data link 20 REG_DATA_LINK Register a data link 21 MSG_RECEIVED Ack of received message 22 LINK_RETURNED Condition of RET_LINK path 23 TRANSFER_USER_BUF Initiate user buffer transfer 24 END_OF_TRANSMISSION Ack of EOT 25 MRT_UPDATE Update message routing table * 26 COND_GET_USER_BUF Get a user buf with options indicated by Non_Blocking_Flag * 27 BCAST_TO_DEV Broadcast a load packet to a special PBAS. 28 UPDATE_CALENDAR CE date modification 29 OWN_PROCESS_ID Id of running process 013 211 31515 AAAA EA 199

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX H 2A DPM_ROUTE Act/deact DPM routing 2B RESET_ERROR_COUNTERS Reset error counters 2C BROADCAST Broadcast load packet 2D DOUBLE_INDIRECT_FETCH Cluster channel double fetch 2E JOIN_INDIRECT_SIMPLEX Fetch and transmit PCM 2F TX_INDIRECT_SIMPLEX Store receive channel PCM 30 FREE_INDIRECT_SIMPLEX Stop TI RAM from sampling PCM 31 FREE_TX_INDIRECT_SIMPLEX Stop speech to TI RAM 32 JOIN_PATH Join UCP’s 33 READ_METERING_FLAG Read metering flags 34 DPM_GET_MSG Get message from DPM 35 SCAN_RECEIVER Copy PCM samples to buffer 36 GET_LOAD_PATH Get UCP, simplex or data link 37 SET_METERING_FLAG Write metering flags 38 FREE_PATH Unjoin path 39 SEND_LOAD_PKT Send load packet 3A SET_OVERLOAD_CONDITION Set overload condition 3B VP_FAILURE Virtual path failure 3C ERROR General error interface 3D MSG_SEND Transmit message buffer 3E MSG_DEFER Defer message buffer 3F MSG_WAIT Wait for incoming message 40 CREATE_PROCESS Create a new process 41 REL_PARAMETER_TIMEOUT Rel timeout with I/O parameter 42 READ_RESET_COUNTERS Statistical gathering primitive 43 JOIN_TO_PKT_RAM_DUPLEX Join receive and transmit thru packet RAM 44 FREE_FROM_PKT_RAM_DUPLEX Free transmit and receive channel 45 SOFT_DISABLE_TI_PORT Disable TI port 46 INIT_TI_PORT Enable TI port 47 FORCE_DISABLE_TI_PORT Force TI port disable 48 GET_TI_PORT Get TI port for maintenance 49 RET_TI_PORT Return TI port 4A GET_TUNNEL_PORT Get a tunnel port 4B RET_TUNNEL_PORT Return network port 4C GET_CHANNEL Allocate channel to diagnostic 4D RET_CHANNEL Return TI channel 4E TI_PORT_MAINT_BUSY_BIT Modify TI port flag 4F SEND_MAINT_PKT Send maintenance packet 50 SEND_SPATA Send SPATA sample thru loop 51 READ_SPATA Read SPATA sample 52 SEND_TUNNEL_WORD Send tunnel word 53 EXEC_TI_SEQUENCE Exec TI diagnostic instruction 54 OWN_CE_ID Get process ID, LCE ID, PCE & VP * 55 XLATE_UCP_CHAN Translate the LID of a UCP to its ports and channels 56 GET_NR_LOAD_PKT_IN_Q No. of buffers on output queue 57 MSG_REJECT Return message with error * 58 SET_FLAG 59 FREE_SCAN_RCV_TX_INDIRECT Stop putting PCM samples from cluster path into packet RAM 5A ERROR_REPORT General error I/F w/sequence 5B NH_DEVICE_AUDIT Audit of NH TI facilities 5C NH_READ_IO_PORT Retrieve contents of I/O port 5D OVL_ABORT Abort overlays in progress 5E OVL_DLOAD_END End of download 5F OVL_XMIT Download request 013 211 31515 AAAA EA 200

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX H 60 OVL_FMM_INFO FMM info on code, data & patches 61 GET_AND_RESET_PARITY Returns to user the parity value for a UCP * 62 ABORT_PROCESS Allow RAM restart to abort a specific process 63 SET_TRACE_FLAG Set trace flag for PTF 64 GET_PCE_ID Get physical control element id 65 GET_EXCHANGE_DATA Get network id 66 GET_NETWORK_ID Get network address 67 GET_SPATA_PATH Get speech path 68 NEW_LCE_ID Change LCE id 69 TERM_OPT_NOTIFY Process termination with optional notification 6A RESET_LOCAL_TOD Sets TOD to user specified value 6B STACK_CHECK Enables/disables stack check 6C COND_MSG_SEND Send message with return code 6D SET_X_OVER_STATE Inform OS on crossover status * 6E SET_OVLY_DEBUG_FLAG Force FMM dload, 10 min resident * 6F OPEN_TUNNEL_MAINT Enable tunnel events after restart * 70 GET_REAL_TIME_EXT Get current TOD + time adjustment * 71 SET_OSN_PTF_PUBLICS Setup OSN publics for PTF * 72 SET_SSM_TRACE_FLAG Act/Deact SSM tracing by PTF * 73 MI_CALL_ERROR_HANDLER Force restart/bootstrap from MI * 76 XMIT_BCAST Broadcast user buffer * 77 COND_MSG_SEND_EXC * 78 PROCESS_CHECK * 79 RET_MSG_WITH_USER_BUF * 7A GET_PATH_ARRAY * 7B RET_PATH_ARRAY 200 GET_CH_PATH Assigns pair of free cluster side channels to terminal 201 RET_CH_PATH Deassign SPATA path from terminal 202 DEVICE_OWN Claim ownership of a device 203 IO_CMD Send I/O commands to DPTC device via Cluster Handler over channel 16 204 DATA_LAUNCH Send I/O commands to OBCI/OBC via Cluster Handler over channel 16 * 205 RSU_GET_CH_PATH Establish SPATA path to remote dev * 206 RSU_RET_CH_PATH Return SPATA path from remote dev * 207 RSU_DEVICE_OWN Claim ownership of rm DPTC/OBCI * 208 RSU_IO_CMD Send I/O packets to remote DPTC * 209 RSU_DATA_LAUNCH Send data pkts to remote OBCI/OBC * 20A RSU_GET_LDC_DATA Get link load information * 20B RSU_UPDATE_SS_STATUS Update a single signalling stage * 20C GET_FXD_CH_PATH Create a fixed CH path * 20D GET_CH_MAINT_PATH Establish path for maintenance * 20E RET_CH_MAINT_PATH Return cluster maintenance path * 210 OBCI_BOOT_MODE Specify OBCI reaction in bootstrap * 211 RSU_GET_TERM_INTRA_PATH Establish INTRA path to remote dev * 212 RSU_RECONFIGURE_PATH Deoptimize/optimize RSU INTRA path * 213 RSU_USER_READ_SS_TABLE Read entire signalling stage table * 214 RSU_USER_UPDATE_SS_TABLE Update signal stage table per PCM 300 GET_PROCESSOR_PARAM Get target machine type, speed & address mode 301 GET_ACCESS Get access to common areas Channel 16 302 MODIFY_PROTECTED_MEMORY Modify protected memory 305 GET_DESCRIPTOR To set up new descriptor 306 RET_DESCRIPTOR Return descriptor to GDT pool (valid only in 286 virtual address mode) 013 211 31515 AAAA EA 201

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX H 307 CONVERT_VIRT_TO_PHYS Convert virtual address into 32–bit physical address (valid only in 286 virtual mode) 308 CONVERT_286_TO_86 Convert 286 long pointer into 8086 long pointer (valid only in 286 virtual mode) 400 GET_OWN_OVLD_STATUS Get own overload status *FF00 PKT_SEND Send IPP packet

013 211 31515 AAAA EA 202

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX I APPENDIX I. PRIVATE NOTES _________________________

013 211 31515 AAAA EA 203

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– APPENDIX I Notes

013 211 31515 AAAA EA 204

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


013 211 31515 AAAA EA 205

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


013 211 31515 AAAA EA 206

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel


013 211 31515 AAAA EA 207

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– INDEX _____

+–––+ Control Element 26 | A | COP MEM: copy memory 119 +–––+ COU: count clause 47 Abbreviations 10 ABO BAT: abort batch process 109 +–––+ ABO MAC: abort macro 43 | D | ACT: activate CE 26 +–––+ ADD: add symbol 38 ALT: alter message 60 DAC OBC: deactivate on–board ARM: Arm TRF 91 controller 28 ASM: disassemble 35 DAC: deactivate CE 27 Database return status 194 DBS ACC: database V2 access 68 +–––+ DB4 ACC: database V4 access 67 | B | Debug Monitor 189 +–––+ DEF MAC: define macro 41 DEF SEL: define selector 95 BAS: set output base 98 DEF: define symbol 37 BAT: start batch process 108 DEL MAC: delete macro 103 BDR: change baudrate 25 DEL SYM: delete symbols 104 Breakpoints 50 DEL TIM: time delay 130 BRP: display breakpoints 55 Dimensioning 140 BRP: set breakpoint 53 DIR LIB: directory library 102 BYT: display byte 33 DIR TAB: directory of macro BYT: modify byte 34 table 123 DIR: directory macro 44 DIS ARM: read TRF timer 93 +–––+ DIS LIB: disable library calls 102 | C | DIS SYM: disable symbol +–––+ replacement 81 DUM: dump trace 79 CAL EXT: call external routine 70 CAL OBC: call on board controller 68 +–––+ CAL OSN: call operating system | E | primitive 65 +–––+ CAL SSM: call SSM interface procedure 66 EDI: edit macro 44 Call primitives 65 EM: end macro 42 CAL: Call Macro 42 ENA SYM: enable symbol CBU: call buffer 14 replacement 81 CE BOO: CE boot 30 ERT: display error type 132 CE LOA: CE Load 31 EVA: evaluate expression 130 CE RES: CE restart 30 EVC: event code 14 CE: display CE directory 29 Events 116 Changes 7 EVE: check event 117 CLR EOS: clear end–of–screen 98 Examples 146 CLR: clear screen 96 EXE MAC: execute COL: collect trace 80 build–in–macro 122 COM LIB: compress library 105 EXI: exit clause 49 Commands 22 Expressions 19 Compound commands 46 Configurations 134 013 211 31515 AAAA EA 208

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– +–––+ +–––+ | F | | K | +–––+ +–––+ FET PID: fetch process 132 Keys 22 FET REL: fetch relation 131 Keywords 13 FET SSM: fetch SSM 52 FET: fetch FMM 51 File handling 106 +–––+ | L | +–––+ +–––+ | G | LDT: local descriptor table 15 +–––+ LET: modify symbol 38 LEV: level control 88 GDT: global descriptor table 15 Libraries 100 GET SYM: get symbols 104 LIS OFF: list off 24 GET UCP: get path 63 LIS ON: list on 24 GET UWA: get user work area 118 LOC: locate cursor 96 GET: get macro 103 LWA: local work area 14 GO: go till 56 +–––+ +–––+ | M | | H | +–––+ +–––+ Macros 40 HELP: help command 132 MAC: display macro 44 HILTI 136 Memory access 32 Messages 59 Miscellaneous 130 +–––+ MMC 110 | I | MMC DIA: MMC dialogue in +–––+ macros 112 MMC SES: interactive dialogue Identifiers 17 session 111 IDT: interrupt descriptor table 15 MP: master pointer 15 IEC: internal error code 14 MSG: display message 59 IF: If clause 46 INC: include IOS–file 107 INI LIB: initialise library 100 +–––+ INI OBC: initialise OBC 30 | O | INI SLV: initialise Slave 29 +–––+ IOS Completion Codes 192 OBC: select on–board controller 28 ONT: ontrace channel 85 +–––+ Operators 18 | J | Options 124 +–––+ OPT: display run time options 129 ORIF: alternative IF clause 46 JSQ: job sequence number 15 Output 96

013 211 31515 AAAA EA 209

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– +–––+ SET HEA: trace formatting 125 | P | SET MEN: set menu mode 128 +–––+ SET NOT: set notranslation 128 SET PMT: set prompt 124 PADS 137 SET PSW: set global MMC PAT: patch code 36 password 113 PID: process on breakpoint 15 SET SUP: set supervision time 127 POR: display port 33 SET TRC: set trace length 126 POR: modify port 35 SHO TRF: show TRF status 93 PRI: print TRF 94 SND: send message 62 PUT SYM: put symbols 104 START MPTMON: start session 23 PUT: put macro 102 SUFFIX: set input base 99 Symbols 37 SYM: display symbol 39 +–––+ Syntax 13 | R | +–––+ +–––+ RBF: report buffer 15 | T | RCV: receive message 62 +–––+ REG UCP: register path 64 REG: display or modify TER SES: terminate session 23 registers 57 Terminal REM BRP: remove breakpoint 58 Connections 134 REM MAC: remove macro 44 Types 139 REM: remove symbol 39 TIM: display time 25 REP: repeat clause 48 TI: call TI command 69 RES HAR: reset hardware 91 TMC: target machine code 14 RES OPT: reset run time Trace 71 options 129 Trace Facility 82 RES REG: restore registers 57 TRC ENV: trace environment 78 RES SOF: reset software 85 TRC EXC: trace exclude 74 RET MAC: return macro 43 TRC FMM: trace FMM 72 RET UCP: return path 64 TRC ITF: trace interface 75 RET UWA: return user work area 120 TRC MSG: trace message 73 RET: retrieve from IOS–file 107 TRC OFF: trace off 78 ROMD: ROM data area 15 TRC PID: trace process 74 RRN: report reference number 15 TRC REL: trace relation 77 RSQ: report sequence number 15 TRC SEQ: trace sequence 75 R_FEATURES 189 TRC SSM: trace SSM 77 TRC VAL: trace value 73 TRC: display trace 78 +–––+ TRF: display TRF 90 | S | TRI: trigger channel 87 +–––+ SAV: Save on IOS–file 106 +–––+ SCA TAB: scan table 119 | U | SCR REG: scrolling region 97 +–––+ SCRIPTGEN 137 SEL LIB: select library 101 Utilities SEL TAB: select macro table 122 HILTI 136 Sessions 22 PADS 137 SET AUT: set authorisation 124 SCRIPTGEN 137 SET BAT: set batch mode 128 UWA LIS: list user work areas 121 SET DIS: display all info 125 UWA: Work Areas 118 SET ERR: set error option 127 013 211 31515 AAAA EA 210

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– +–––+ | V | +–––+ VER REP: verify report 114

+–––+ | W | +–––+ WAI BRP: wait breakpoint 58 WAI EVE: wait event 117 WAI MSG: wait for message 63 WAI REP: wait report 113 WAI TIM: wait time 117 WAI TRF: wait TRF 94 WOR: display word 32 WOR: modify word 33 WRI: write text 97

013 211 31515 AAAA EA 211

ED

All

right

s re

serv

ed.

Pas

sing

on

and

cop

ying

of t

his

docu

men

t, us

e a

nd c

omm

unic

atio

n o

f its

con

tent

s no

t.

perm

itted

with

out

wri

tten

aut

hor

iza

tion

from

Alc

atel

. Reference Manual OFFICIAL COPY –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– INFORMATION ABOUT THIS DOCUMENT _______________________________

AUTHOR: P.Oosterhaven / J.Tiekenheinrich UNIT: SEL Stuttgart DEPARTMENT: VS/ECD–1 EXTENSION: 0711/8265–2021 IDSS SOURCE DATASET: LIBSOFTW.DWSSAAAA.EA211013(#ROOT) IDSS LIST DATASET: LCM09.LIST.DWSSAAAA.EA211013

END OF DOCUMENT

013 211 31515 AAAA EA 212

mptmon

Documents

Transcript of mptmon