Professional Documents
Culture Documents
Chapter One
GETTING STARTED
This chapter provides quick start information. Much of the material presented here is
covered in far greater detail in the GPSS/H System Guide, which can be found in
C:\Program Files\Wolverine\GPSSH\Doc.
Unless otherwise noted, information applies to both Student GPSS/H and the
commercial versions of GPSS/H (GPSS/H Professional and Personal GPSS/H).
GPSS/H is distributed on a CD-ROM. Student GPSS/H is also available for downloading on Wolverines website, www.wolverinesoftware.com. To install GPSS/H from
a CD, simply insert the CD-ROM into a CD-ROM drive on your computer. Unless you
have disabled the automatic recognition of CD insertion, Windows should automatically
begin executing the software installation procedure on the CD. If the CD is not automatically recognized, you can manually run setup.exe, contained on the CD. To
download Student GPSS/H, simply click on the appropriate link on our Downloads
page
The installation procedure will lead you through a sequence of dialogs, allowing you to
specify which software components youd like to install and where youd like to place
them on your computer. By default, files are placed into the folder named
C:\Wolverine and into Wolverine-defined subfolders of that folder. If you wish to
1-1
choose a different base folder, you may do so; however, you should not move, remove,
or rename any subfolders created by the installation procedure. The folder architecture
we have defined provides a convenient way of installing a variety of products from
Wolverine Software.
If you plug a USB key in before the installation is completed, Windows will recognize
that a new USB device has been connected, but it will have difficulty figuring out how
to handle the new device. If you plug the key in after the software installation is
complete, Windows will automatically recognize the security key and setup USB driver
software for accessing it.
1-2
If you change the size of the command prompt window, set the scrolling region to be the
same size as the window itself. Otherwise, confusing double scrolling will result.
(GPSS/H provides its own scrolling via function keys. If you make the scrolling region
smaller than the windows size, Windows will provide scroll bars.)
1-3
B. Compile and execute the model by running the appropriate version of GPSS/H.
To compile and execute a model under Student GPSS/H, run gpssh.
To compile and execute a model under GPSS/H Professional, run hpro.
To compile and execute a model under Personal GPSS/H, run hpers32.
1-4
We recommend using an editor that supports 132 columns (either through left-right
scrolling or through extended video modes) for viewing listing (".lis") files, and
using a printer that supports 132 columns for printing them.
1.4.3 Command Line Examples
The following examples illustrate how to run Student GPSS/H. Remember, if youre
using GPSS/H Professional, type hpro, and if youre using Personal GPSS/H, type
hpers32, rather than gpssh.
gpssh myprog
(Source, dictionary, and cross-reference listings and model output are placed in a file
named myprog.lis.)
gpssh myprog type nowarn
(Source, dictionary, and cross-reference listings are suppressed. Model output appears
directly on the screen. No listing file is created. Compiler warning messages are
suppressed.)
gpssh myprog tv
(This example invokes the windowed version of GPSS/Hs interactive debugger. At the
point at which execution ordinarily would begin, the interactive debugging system
assumes control, and a READY message is displayed on the screen. The debugger will
operate in "windowed mode", with model source code displayed. A large number of
keyboard shortcuts are provided. For details, see the GPSS/H System Guide.)
gpssh myprog tvtnw
("tvtnw" is an abbreviation for "tv type nowarn". This combination of three options is
handy for making quick debugging or model-checkout runs. Source, dictionary, and
cross-reference listings are suppressed. Compile-time warning messages are suppressed.
Model output appears directly on the screen. No listing file is created.)
1-5
(Source, dictionary, and cross-reference listings are suppressed. Model output is placed
in a file named myprog.lis. If any compilation warning messages are issued, they are
placed only in the file myprog.lis and are not echoed on the screen.)
gpssh myprog test type source dict xref
(Source, dictionary, and cross-reference listings and all model output appear directly on
the screen. The source, dict, and xref options are needed because the type option,
which has already been processed, causes suppression of these listings. At the point at
which execution ordinarily would begin, the interactive debugging system assumes
control, and a READY message is displayed on the screen.)
During this phase, GPSS/H reads your source file, checks for syntax errors and
produces a source listing. It also assigns numeric values to symbols (i.e., statement
labels, facility names, etc.) used in the model.
The message that shows on the screen next is
Pass 2 ...
During Pass 2, GPSS/H compiles the model into a form suitable for fast execution. It
also allocates memory and prepares to execute the model. If no errors are encountered,
the following message will appear:
Simulation begins.
This means that GPSS/H is running your model. When the simulation run is completed,
GPSS/H produces a standard output report. If an error occurs during execution of the
model, then an informative error message is generated both to the screen and to the
output report.
1-6
1-7
1-8
250 total statements (this includes Blocks and Control Statements but does not
include comments or the extra lines in multi-line statements)
Up to 32720 bytes of COMMON storage.
If a model is run that exceeds any of these limits, a general error message will appear on the
screen stating that the limits have been exceeded. The error message will also
specifically tell you which of the three limits have been overrun. For example, if a
model is run that contains over 125 Blocks, the following message will appear on the
screen:
ERROR: STUDENT-VERSION IS LIMITED TO 125 BLOCKS LIMITS OF STUDENTVERSION EXCEEDED RUN TERMINATED
If the COMMON storage limit is reached, Error 411 will appear on the screen:
Error 411 - Out of COMMON - Add/change REALLOCATE Stmt?
Out of COMMON means that your model has depleted the default memory pool that
every model uses when executing. Student GPSS/H by default will access 10000 bytes
of COMMON, which is enough to accommodate up to about 100 simultaneous
Transactions. A Transaction is the unit of traffic in your model. If too many
Transactions pile up in the model, you will see Error 411. The piling up of Transactions
can be due to a logic error or due to the complexity of your model.
Some models just need more than 10000 bytes of COMMON to run to completion. If
more COMMON is needed, you can use the MAXCOM option or the REALLOCATE
Statement. Whether you use MAXCOM or REALLOCATE depends mostly on personal
preference. MAXCOM overrides REALLOCATE if both are used. The MAXCOM
option is used on the command line that invokes GPSS/H:
GPSSH JOEBARB MAXCOM
MAXCOM will cause GPSS/H to grab as much COMMON as it can, up to 32720 bytes
for the Student version. The actual amount of COMMON that MAXCOM will be able to
1-9
grab depends only on the complexity of your model. It does not depend on the
configuration of your computer hardware or any other software you have installed.
REALLOCATE can be used in the model itself to increase COMMON.
REALLOCATE requires that you specify an exact amount. The syntax of
REALLOCATE is:
REALLOCATE COM,bytes
The A-operand contains COM which is the GPSS/H code for COMMON, and the Boperand specifies the number of bytes that you want in the COMMON memory pool.
The REALLOCATE Statement can be placed anywhere before the end of your model,
but placing it near the beginning of your model makes it much easier to access if
changes are needed. If REALLOCATE cannot get the amount of COMMON requested,
model compilation fails with a message telling you exactly how much COMMON you
could have gotten. This lets you quickly try again. For example,
REALLOCATE COM,20000
will double the default value for COMMON. If your model failed to run to completion
with 10000 bytes of COMMON, it should run about twice as long if you double the
amount of COMMON.
1-10
1-11
can be tabulated into a histogram-like entity called a Table. Chapter 15 illustrates how
to declare and use a two-dimensional array of variables. Chapter 16 gives a brief
description of other features of GPSS/H not covered in this text. Appendix A gives an
overview of other new features.
If you are a new user of GPSS/H, we strongly recommend that you read Chapters 2 through
13. If you have prior GPSS experience, we strongly recommend that you start by studying
the interactive debugging facility of GPSS/H described in Chapter 4. You will find this
facility extremely helpful, especially if you are developing a large simulation model.
We then recommend that you read at least Chapters 8, 9, 12 and 13 to understand the
power and flexibility of GPSS/H.
1-12