E
User s Guide 1 (24)
Uppgjord  Prepared Faktaansvarig  Subject responsible Nr  No.
UAB/UKY/ST Janet Wennersten 198 17 - CAA 139 1080 Uen
Dokansv/Godk  Doc respons/Approved Kontr  Checked Datum  Date Rev File
UKY/ST (Per Burman) 2002-06-18 L
Analyzetool - User s Guide
Contents Page
1 Introduction 2
2 Getting Started 2
2.1 Entering the analyzetool 2
2.2 Exiting 2
3 User Interface 3
3.1 Main Window 3
3.2 Main Panel Subwindow 4
3.3 Error window 14
4 Operational Instruction 16
4.1 Analyze 16
4.2 Generate 20
4.3 Compile 21
4.4 Object 22
5 Batch processing 24
E
User s Guide 2 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
1 Introduction
Analyzetool offers a window-based interface to the PLEX Compiler and the
PLEX-SQL preprocessor.
All the compiler stages are compatible with their counterparts in APS3 on
the IBM.
2 Getting Started
2.1 Entering the analyzetool
Analyzetool can only be used in an X environment (that is, you must either use
a workstation with X running, or an X terminal). To start one of the following
must be done:
a Enter theanalyzetoolcommand from a standard shell
window.
b Double-click using the SELECT mouse button on an icon for
a PLEX source file in the OpenWindows File Manager. Icon
is shown in figure 1.
c Double click using the SELECT mouse button on the analyzetool
icon in apstools toolbox (i.e. tbxtool). Icon is shown in figure 2.
Figure 1 Icon for Plex source documents.
Figure 2 TBXtool s icon for Analyzetool
2.2 Exiting
To exit from Analyzetool, use the Quit command from the window menu. If
the file in the editor has been edited but not saved, you must confirm or
cancel the save.
E
User s Guide 3 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
3 User Interface
3.1 Main Window
The layout of the Analyzetool main window is shown in figure 3.
Figure 3 Analyzetool main window
The subwindows, from top to bottom, are the following:
Main Panel
Setting of input criteria and required process of analyzetool
is done here.
Textedit Subwindow
Used for editing of source documents using standard XView
textedit functions with PLEX extensions
Message Subwindow
Information messages from the different processes of
analyzetool are displayed here, for example, number of errors
found in analysis of a source document.
Footer bar
E
User s Guide 4 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Messages stating what processes have started, are running, or
have finished appear here. If there is nothing else to show in
the right part of the footer, the name of the file that is currently
loaded in the textedit subwindow will be displayed there.
3.2 Main Panel Subwindow
This section will deal with the buttons in the main panel. The input and
output documents are dealt with in the next chapter  Operational Instruction
[page 16].
3.2.1 Start Menu
Pressing the MENU mouse button on theStartbutton causes the display of
the pull-down menu shown in figure 4.
Figure 4 Start menu, here shown in pinned-up state
This menu specifies what processes the analyzetool can perform. To start a
process drag MENU mouse button down over required process and release it
(the selected process will be highlighted).
The selection Analyze has a sub-menu that makes it possible to choose what
file to analyse, default is the file in the editor. If the file to be analysed is a
program file there is an additional sub-menu where one can select Interactive
or Batch. Interactive, which is the default, is the normal way of processing. For
a description of the Batch choice see the chapter "Batch processing" [page 24].
In the same way the selection Generate and Compile has a sub-menu where
Interactive or Batch can be selected.
As long as the chosen process is running theStartbutton will display a
"busy" pattern, and can not be used. Also the right footer of the main window
will display what subprocess is running. To stop the running process press the
Stop key on your keyboard while the options panel has the input focus.
The processes are as follows:
3.2.1.1 Analyze
Analyze is the process that checks if the input document is syntactically and
semantically correct. Input to the analyze process is a source document and
E
User s Guide 5 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
optionally, if it is a program, a signal survey and/or an analysed parameter
list. Analyze produces an output list due to the options given in the Compiler
Options window, and an analyze result file.
3.2.1.2 Generate
Generate is the code generation. The generate input is a source program and
the analysed result from the source program. Generate produces an output list
due to the options given in the Compiler Options window, and a file containing
the code generation result. The first page on the code generation list is a
survey of the used documents in the software unit.
3.2.1.3 Compile
Compile is a combination of analyze and generate.
3.2.1.4 Object
The object process is used to produce object code. The input files to object are
different depending on whether Marshal or RSP object is used. The object input
is a result from a code generation, a result from an analysed parameter list and
either a result from a margen analyze execution or a result from an analysed
BAT (Block Allocation Table) document and the analysed signal survey.
3.2.2 Options Panel
Clicking the SELECT mouse button on the Options... button in the main panel
causes the window shown in figure 5 to pop up. The analyzetool process
produces an output list according to the options set in this panel.
To set an option click SELECT mouse button on the box shown on the right of
the option. To remove that option click SELECT on the box again.
For the options to take effect you must confirm your selections by clicking on
the Apply button at the bottom of the window. If you change your mind about
changing the options, but have already changed some, you can click on the
Reset button to reset the options to what they where before you started
to make changes.
E
User s Guide 6 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Figure 5 Options window with default settings
The options are divided into three groups. The first one contains common
options to be used by several functions. The second analyze-specific options
and the third generate-specific options.
3.2.2.1 Common options
Foot
The ID information like name, date, class, designer etc will be
generated at the bottom of every page in the listing file.
Warnings
All detected warnings will be listed in the error window and in
the listing file.
APS3 Line numbers
Line numbers for APS3 will be generated to the right of the
source listing. APS3 line numbers mean that the listing file will
have the same line numbers as seen in the editor and the
directive lines such as *PAGE will be included in the numbering.
Product Revision
The product revision state that will be printed in the survey of
used documents in the output listing from generate process.
Lines
Lines per page for listings.
Width
E
User s Guide 7 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Characters per line for listings.
3.2.2.2 Analyze options
Macro expansion
An item to enable macro expansion for documents that contain
macros. If chosen an input field to enter the name of a Macro
Library appears below.
Macro library
The library that will be used if the macro expansion is enabled,
for example: APZMACRO.
Source list
The complete source document will be listed with inserted
diagnostic messages.
Cross reference
A cross reference list for all identifiers in the source document
containing type, class, size, value, defined- and referenced on
lines (APS2 lines) is generated and inserted into the listing
result (.listpgm).
3.2.2.3 Generate options
Check for Extra Warnings
The compiler will issue warnings for possibly undefined
temporary variables, pointers and ON loop counters.
Run Global Optimizer
The Global optimizer requires a lot of memory and can take a
long time. If you only need the warnings and error messages
from the code generator, and not the code generation result,
you can disable the optimiser. Note that this will result in a fatal
error and no code will be generated.
Source list
The complete source document will be listed with inserted
diagnostic messages.
Cross reference
A cross reference list for all identifiers in the source document
containing type, class, size, value, defined- and referenced
on lines is generated.
Base address table
A table containing base addresses of used variables.
Kind of generate list
Normal: only the generated assembler and binary code are
listed.
Mixed: the complete source code is listed. For each source
statement the generated assembler and binary code are listed
E
User s Guide 8 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
parallel. Statement blocks are listed at the place where they
are used.
3.2.3 Object Window
The Object Window has different contents depending on whether it is used
in Marshal or in RSP mode. The window is shown in figure 6 and figure
7 respectively. The choice in the right upper corner selects between normal
interactive processing or batch processing. For a description of the latter see
the chapter "Batch processing" [page 24].
Figure 6 Object window in Marshal mode
Figure 7 Object window in RSP mode
3.2.3.1 Object options
Common for both RSP and Marshal:
Code generation result
Result from a successful code generation.
Analysed parameter list
Result from a successful analysis of a parameter list.
Suffix sequence number
Indicates which application system the product belongs to.
E
User s Guide 9 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Amendment level
Indicates the amendment level (product revision) the product
has.
Marshal Options:
Margen result
The analysed marshal document.
RSP options:
Analysed BAT
Analysed BAT document.
Analysed signal survey
The analysed signal survey.
3.2.4 Signal Handling Panel
Analysed signals are used in the analyze process to enable the finding of
errors as early as possible in the source program. If the analysed signals you
need are not stored in the signal libraries then the analyzetool will have to
be used to analyse the signals and the resulting analysed files stored on the
workstation. The signal handling panel is then used to tell the analyzetool
where to access the analysed signals. The panel is shown in figure 8.
To open this panel click MENU mouse button on the Options... button in the
main panel and select Signal Handling... from the menu.
Figure 8 Signal handling panel
As can be seen from the above figure there are two options, Use signals from
disk and Use signals from signal libraries. In figure 8the collection of signals
from the signal library APTSIGLIB has been specified.
E
User s Guide 10 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
3.2.4.1 Use signals from disk
If the analysed signals are stored on the workstation then this option is used.
Click SELECT mouse button on the box to the right of Use signals from disk.
This will cause the input field Signal dir to be highlighted. The directory path
must be specified here. More than one directory path can be specified, if so the
directory paths must be separated by a "space" as shown in figure 9. When
filling in this field the ESC key can be used to complete a partially entered
name. Only names of directories will be completed.
Figure 9 Signal handling with signals in two directories.
When you have made your settings in the Signal handling panel, you must
press the Apply button for the changes to take effect. By pressing Reset the
window will be filled with the settings of the last apply.
3.2.4.2 Use signals from signal libraries
If collection of signals from signal libraries is wanted then click SELECT mouse
button on the box to the right of that option. It is then possible to specify up
to five different libraries. You can only use libraries that your librarian has
registered for use. To specify a library press MENU mouse button on the
menu button beside the relevant library field. A menu with all the available
signal libraries should appear, drag the pointer over the library you want and
release the MENU mouse button. The chosen library will now be specified
in that field, see figure 10.
E
User s Guide 11 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Figure 10 Specifying signal libraries in signal handling panel.
Important to think of here, is the order in which the analyser will search for
signals. The analyser uses the signal identity to search and starts by looking in
the first library and if it finds the signal there, it will use the latest revision in
that library. Only if it can t find the signal in a library will it go on and search
in the next library.
If Use signals from disk has been specified the analyser will search the disk
directories first, and if a signal with the right name is found there, the libraries
will not be searched.
When you have made your settings in the Signal handling panel, you must
press the Apply button for the changes to take effect. By pressing Reset the
window will be filled with the settings of the last apply.
3.2.5 Table Handling Panel
This panel is used when using PLEX-SQL language, it says where the
PLEX-SQL tables can be fetched from. See tablib users guide. To open this
panel click MENU mouse button on the Options... button in the main panel
and select Table Handling... from the menu. There are two options Table
dir and Table lib
3.2.5.1 Table dir
Click SELECT mouse button on the box to the right of Use tables from disk.
An input field with the label Table dir: appears. Here you enter the path to the
directories where you have tables. An example of this is shown in figure 11.
E
User s Guide 12 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Figure 11 Specifying directory for PLEX-SQL tables
When you have made your settings in the Table handling panel, you must
press the Apply button for the changes to take effect. By pressing Reset the
window will be filled with the settings of the last apply.
3.2.5.2 Table libraries
Click SELECT mouse button on the box to the right of Use tables from table
libraries. Five input fields are then highlighted in which you can specify up to
five table libraries. An example is shown in figure 12.
Figure 12 Specifying PLEX-SQL table libraries
3.2.6 PLEX-SQL Options Panel
This panel is used when using the PLEX-SQL language. The analyze process
will then create a PLEX program and a signal survey. The fields in this
panel can be used to specify the document identity number and revision for
these documents.
E
User s Guide 13 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Figure 13 The PLEX-SQL Options Panel
3.2.7 Display Errors
This opens up the Error window. See chapter "Error window" on page page
14of this document for a detailed explanation.
3.2.8 Help menu
The help menu gives on-line help on each of the topics listed in the menu.
3.2.9 Target Machine
This field indicates which target machine the code should be generated for. To
select a target machine press MENU mouse button on menu button to the right
of Target Machine in the main panel. The menu shown in figure 14 appears,
drag the pointer down over the wanted machine and release MENU mouse
button. The selected machine will now appear in the main panel.
Figure 14 Target machines for code generation.
Valid target machines for analyze are:
APZ21003
APZ21004
APZ21006
E
User s Guide 14 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
APZ21102
APZ21 V1
APZ21 V2
APZ21 V3
APZ21 V4
APZ21201
M6809
M68020
M68030
Valid target machines for the other processes are:
APZ21006
APZ21102
APZ21 V1
APZ21 V2
APZ21 V3
APZ21 V4
APZ21201
(Note) Machine code compatibility for APZ21102 and APZ21202.
Use the target specification APZ21 V1 (or the equivalent
APZ21102), APZ21 V2, APZ21 V3, or APZ21 V4.
3.3 Error window
When errors are detected, a new window pops up with the following layout:
Figure 15 Error display window
The window is divided into two parts:
1. Acontrol panel for error parsing. It contains three buttons
labelled Next,Previous and Help on message.... The first two
buttons will display the corresponding error message and point
out its location in the textedit subwindow. The third button will
open a new window with a more detailed explanation of the
current error message than what is displayed in the message
subwindow. An example of this is shown in figure 15.
2. Amessage subwindow where error messages from the analyser
are displayed.
E
User s Guide 15 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Figure 16 Using Help on message
When the key Next button is pressed, using the SELECT mouse button, the
errors are displayed one by one in the error message window and pointed out
(inverted video) in the Analyzetool textedit window. The source file can be
edited and the next error parsed by using the Next button again.
If the analysed file is not the one currently in the editor, the analysed file will
be loaded instead. To load another file in the editor, use the pop-up menu in
the Textedit window.
The error window can also be opened by clicking the SELECT mouse button
on Display Errors... button in the analyzetool main panel.
(Note) When analysing, the error parsing can be done as soon as the
analyser starts to report errors. You need not wait until the
analyze process is finished.
E
User s Guide 16 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
4 Operational Instruction
This section outlines the sequence of operations when using the analyzetool.
There is then a sub-section for each of the processes available from
analyzetool. Each of these sub-sections specifies the input documents
necessary, correct options to set, the correct target machine and the output
document produced from a run of the process.
1. Decide which process to use.
( see section 3.2.1 )
2. Specify necessary input files.
3. Specify options
(see section 3.2.2)
4. Set signal handling ( and if PLEX-SQL table handing)
(see section 3.2.3 and 3.2.4)
5. Specify target machine
(see section 3.2.7)
6. Start chosen process
Figure 17 Sequence of operations performed in running the analyzetool.
4.1 Analyze
Analyze is the process that checks if the input document is syntactically and
sematically correct.
E
User s Guide 17 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
4.1.1 Input Documents
The input documents for the analyze process can be entered in the fields
Source, Survey, and Parameter list. Also, for targets M6809, M68020, and
M68030, the field System sector. If an input document lies in the directory
specified in the Working dir field, only the file name and extension need to be
specified, otherwise the path to the file must be specified too.
Source: Analyzetool can be used to analyze different types of sources
for Plex units. Source files can be dragged & dropped and
analyzetool places them in the fields according to their type.
The source document can be PLEX program (.program),
PLEX-SQL program (.dbpgm), signal description (.signal),
parameter list (.param), signal survey (.ssurv), system sector
(.system) or BAT document (.bat). It is also possible to specify a
PLEX-SQL table (.dbtable) here.
For PLEX-C the input documents for the analyze process are:
Source: .program
Survey: .ssurv
Parameter list: .param
Access to signal description libraries/directory can be given
under Options... Signal handling...
For PLEX-SQL the input documents are:
Source: .dbpgm
Survey: .dbssurv
Parameter list: .param.
Access to signal description libraries/directory can be given
under Options... Signal handling...
A PLEX-SQL table can also be given under Options... Table
handling...
For PLEX-M the input documents are:
Source: .program
Survey: .ssurv
Parameter list:
System sector: .system
Access to signal description libraries/directory can be given
under Options... Signal handling...
For BAT the input documents are:
Source: .bat
Survey:
Parameter list:
If an analysis of a file of type ssurv is successful, then
sigtruck -lwill be called to make sure that all the signals
specified in the survey are present in the local signal libraries.
E
User s Guide 18 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Survey: When a program is being analysed the analyser may use an
analysed signal survey so that all the signal information can
be accessed. If so, the name of the analysed signal survey
(.anasurv) or signal survey (.ssurv) must be stated in this field.
For the analysed signals to be accessed the signal handling
panel must be filled out correctly (see chapter "Signal Handling
Panel" [page 9 ]). For a PLEX-SQL program (.dbpgm) the
signal survey should be a PLEX-SQL signal survey (.dbsurv).
Parameter list:
When analysing a program it can be checked that the
parameters it uses are defined in the parameter list. This will
be done automatically if a parameter list is specified here, and
that parameter list has been analysed.
Target Machine:
Valid target machines for the analyze process are:
APZ21003
APZ21004
APZ21006
APZ21102
APZ21 V1
APZ21 V2
APZ21 V3
APZ21 V4
APZ21201
M6809
M68020
M68030
See section "Target Machine" [page 13] for more information.
System sector:
When M6809, M68020, or M68030 is chosen as the target
machine the system sector field appears in the main panel.
Here the analysed system sector is specified (.anasys).
4.1.2 Options
The options dictate the contents of the output listing files. They are covered
in detail in chapter "Options Panel" [page 5 ]. The options valid for the
analyze process are:
a Foot
b Warnings
c APS3 Line numbers
d Lines
e.g. Lines : 25
e Width
E
User s Guide 19 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
e.g. Width : 111
f Source List (analyze)
g Cross Reference (analyze)
h Macro expansion
i Macro library
4.1.3 Output Documents
The output documents from the analyze process are listed below according to
their file extensions:
.anapgm Analysed program. It can be used as input into generate
process and also input to the interpreter test.
.anapar Analysed parameter list. This can be used as input into the
object process and also to the interpreter test.
.anasig Analysed signal. Used as input to the analysis of programs and
signal surveys when signal handling is on.
.anasurv Analysed signal survey. Used in the collection of signals when
analysing or compiling.
.anasys Analysed system sector. Used When analysing a PLEX-M
program.
.anabat Analysed BAT document. Used in RSP Object.
.diagpgm Diagnostics file from analysing a program. This result is not
used at present within APStools.
.listpar List parameter list. The contents of this file is dependent on the
options set in the options panel e.g., if  Warnings and  Source
list are set then this file will contain a listing of the parameter list
with warnings and errors inserted at place of occurrence.
.listpgm List program. The contents of this file is dependent on the
options set in the options panel e.g., if  Warnings ,  Source list
and  Cross reference are set then this file will contain a listing
of the program with warnings and errors inserted at place of
occurrence in addition have a cross reference list appended.
.listsurv Signal survey list..
.listsys System sector list.
.listbat BAT document list.
E
User s Guide 20 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
4.2 Generate
Generate does the code generation.
4.2.1 Input Documents
The input documents for the generate process are specified in the field Source.
Source: In this field only a source program (.program or .dbpgm) can be
specified.
Target Machine:
Valid target machines for the generate process are:
APZ21006
APZ21102
APZ21 V1
APZ21 V2
APZ21 V3
APZ21 V4
APZ21201
See chapter "Target Machine" [page 13] for more information.
4.2.2 Options
The options dictate the contents of the output listing files. They are covered
in detail in chapter "Options Panel" [page 5 ]. Valid options for the generate
function are:
a Foot
b Warnings
c Extra Analysis
d APS3 Line number
e Product Revision
e.g. Product Revision : R1A
f Source List (generate)
g Cross Reference (generate)
h Base address table
i Kind of code gen. list
4.2.3 Output Documents
The output documents from the generate process are listed below according to
their file extensions:
.code Code generation result. Used as input to the object process.
E
User s Guide 21 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
.listcode Assembly language listing. The contents of this file depend on
the  generate options set in the options panel.
4.3 Compile
This process is a combination of the Analyze and the Generate process.
4.3.1 Input Documents
The input documents for the compile process can be entered in the fields
Source, Survey, and Parameter list.
Source:
The source program (.program or .dbpgm) is specified here.
Survey: Signal survey is specified here. The file extension of the signal
survey should be .ssurv. If signal collection is required then
the signal handling panel must be filled in (see chapter "Signal
Handling Panel" [page 9 ]).
Parameter list:
When analysing a program it can be checked that the
parameters it uses are defined in the parameter list. This will
be done automatically if a parameter list is specified here, and
that parameter list has been analysed.
Target Machine: Valid target machines for the compile process are:
APZ21006
APZ21102
APZ21 V1
APZ21 V2
APZ21 V3
APZ21 V4
APZ21201
See chapter "Target Machine" [page 13] for more information.
4.3.2 Options
The options dictate the contents of the output listing files and the number of
listing files produced. They are covered in detail in chapter "Options Panel"
[page 5 ]. Valid options for the compile process are:
a Macro expansion
b Foot
c Warnings
d Extra Analysis
e APS3 Line number
f Product Revision
E
User s Guide 22 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
e.g. Product Revision : R1A
g Source List (analyze)
h Cross Reference (analyze)
i Source List (generate)
j Cross Reference (generate)
k Base address table
l Kind of code gen. list
4.3.3 Output Documents
The output documents from the compile process with default options set are
listed below according to their file extensions:
.code Code generation result. Used as input to the object process.
.listcode Assembly language listing. The contents of this file depend on
the  generate options set in the options panel.
4.4 Object
This process produces the object code.
4.4.1 Input documents
The input documents for the object process can be entered in the fields of the
window that pops up when one selects Object... from the Start button menu.
There are two kinds of Object that can be selected from the Object Window,
RSP Object and Marshal Object.
Figure 18 Object window in RSP mode.
E
User s Guide 23 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
Figure 19 Object window in Marshal mode.
Code generation result:
Code generation result file (.code) is produced from generate
or compile process.
Analysed parameter list:
Analysed parameter list (.anapar) is produced from the analyze
process.
Margen result: (only Marshal Object) The analysed marshal document
(.anamar) is specified here (the marshal document is analysed
in Margentool).
Analysed BAT: (only RSP Object) The analysed BAT document is specified
here. The analysed bat document ca be stored in the current
directory or in one of the directories specified with the
environment variable APS_BATPATH.
Analysed signal survey: (only RSP Object) The analysed signal survey is
specified here.
Target Machine: Valid target machines for the object process are:
APZ21006
APZ21102
APZ21 V1
APZ21 V2
APZ21 V3
APZ21 V4
APZ21201
See chapter "Target Machine" [page 13] for more information.
Suffix sequence number:
e.g. Suffix sequence number : 1Q
Amendment level:
e.g. Amendment level : 01
E
User s Guide 24 (24)
Nr  No.
198 17 - CAA 139 1080 Uen
Datum  Date Rev File
2002-06-18 L
4.4.2 Options
The options dictate the contents of the output listing files. They are covered
in detail in chapter "Options Panel" [page 5 ]. Valid options for the object
process are:
a Foot
b Warnings
4.4.3 Output Documents
The output documents produced by the object process are listed below
according to their file extensions:
.object This is the object code file created by Marshal Object and
RSP Object2.
.listobj This is the list object file which contains the signal distribution
table, signal sending table, symbol value list, initial data list
etc. for the relevant product.
.listinit This is the object listing file created by RSP Object2 containing
initial data list and symbol value list.
5 Batch processing
Batch processing, which can be selected for Analyze of program files and for
Generate and Object, means that the process is executed on a remote batch
server. This is intended to be used when your own work station doesn t
have enough memory to process a particular file. Batch processing differs
from normal interactive processing mainly in that it is not possible to step
through the compiler messages via the error window the way one does when
running interactively.
When running the processes in batch, Analyzetool just initiates the batch
processing, it cannot tell when it is ready. Instead the batch server will
notify you by mail when the processing is finished. The mail will contain the
messages from the compiler with line numbers so that you can fairly easily find
the offending line in your program file.
Note that when a job has been initiated it may be put on queue until the batch
server is ready to process the job. As the input files to the compiler are not
copied for the batch processing, any changes you make to the files before the
processing actually starts are included in the processing.
Use batchtool to inspect the queue and possibly remove your jobs from the
queue.