Minescape3

Using Version 3 of Minescape

Contents

Home

Glossary

Index

Minescape3
Starting Minescape3
Not all Minescape applications have been converted for use with Minescape4.
These applications still run under Version 3 of Minescape (Minescape3).

Running Minescape3 from Minescape4

To start Minescape3 when running Minescape4, select:
PageOpen Product Minescape3 from the Menu Barthe following form
opens:

Minescape3 is very similar to the previous Version 3 of Minescape. Where

differences occur, they are noted in this section. The first major difference is that
the Magicad CAD system is no longer usedthe Minescape4 CAD system is
used instead. Most of the old Magicad functions are still available (as pull-down
menu options in Minescape4 rather than as push buttons in Magicad).

Minescape3
Using Version 3 of Minescape
Contents

IMPORTANT

Home

Glossary

Index

For general CAD operations it is recommended that Minescape4 be used,

and that Minescape3 CAD functions only be used when explicitly running
those applications which require Minescape3.

To open a design file for CAD in Minescape3, enter magion at the Minescape3
prompt, as usual.
Note: The command magioff no longer functions.

To change the current design file, enter magion again and enter a new design
file name. The applications which are accessed through Minescape3 are not
available until a design file is open.

Running Minescape3 from the UNIX command line

Minescape3 can also be run without running Minescape4 by entering
minescape3 at the Unix command prompt. However there is no CAD system
available in this case, as Minescape3 uses Minescape4 for all graphics
functions.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Minescape3 menus
After starting Minescape Version 3, the main Minescape3 menu displays in a
separate window. An example of this menu is shown in the following screen. The
content of this and all other Minescape3 menus depends on the Minescape
applications that have been installed at your site.
Minescape3 main menu

heading lines

menu items

message line
prompt line
error line

Minescape3 uses a number of menus to logically group related processes.

Each menu item consists of:
An item number
An item name
An item description

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

An indicator that shows that if the menu item is selected, a subordinate menu
is displayed (>>) or a process is invoked (--). This process may display a User
Interface (UI) screen and/or submit a Minescape module for execution.
Minescape modules are generally run as background tasks. This enables
you to perform other tasks without having to wait for a module to complete its
execution (see Module execution, monitoring and logging for further information).

The second line from the bottom of every Minescape3 screen is the prompt line.
On menus, the following prompt displays on the prompt line:
Enter menu choice or command:
In addition to entering menu items at this prompt, there are a number of
Minescape3 commands that can also be entered. The use of these commands is
explained in Specifications and in Module execution, monitoring and logging.
The bottom line of every Minescape3 screen is the error line. If an error occurs
while you are interacting with Minescape, an error message displays on this line.
The third line from the bottom of every Minescape3 screen is the message line.
Some Minescape3 screen commands provide you with information; some
Minescape modules feed back informationthis information is displayed on the
message line (see Other commands for examples).

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Selecting menu items

A menu item can be selected by entering its item number or its item name. An
item name can be abbreviated to the point that it is unique. For example, if you
enter geo, GEOLOGY is selected, however if you enter ge, an error message
(Ambiguous command) is issued, as both GEOLOGY and GENERAL start with
ge.
Note:

1. The entry of item names is not case-sensitive. For example, GEO, geo, GeO, etc., will
all select GEOLOGY.
2. You may have to replace space characters in an item name with - characters to avoid
ambiguity. For example, to select UG COAL MINING using its item name, you would have
to enter it as ug-c, not as ugc. It would otherwise clash with the selection of
UG METALS MINING, because the space character is used as a delimiter to move down
a menu level.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Moving around the menus

By nature, menu systems consist of a number of hierarchical levels. For
example, if you select an item on Menu A, Menu B displays. If you select an item
on Menu B, Menu C displays, etc.
Minescape3 menu system is no different. For example, if you select GENERAL
from the Main menu, the General Functions menu displays. If you select Files
from the General Functions menu, the Minescape File Maintenance menu
displays, and so on. This concept is shown in the following figure.
Minescapes menu structure

Main menu

...

8 or gen

General
Functions menu

2 or fi

...

Minescape File
Maintenance menu

...

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Once you become familiar with the position of the items on the menu structure,
you can speed up the process of selection an item from any menu level by
entering a string of menu items at the prompt line, with each item/menu level
separated by a space. For example, if you enter 82 (or genfi or gen2 or
8fi) from the Main menu, the Minescape3 File Maintenance menu displays.
What you are in fact doing is specifying a direct path to the required menu item.
To jump directly to the Main menu from any menu, enter 0.
To enter a path to a menu item that is not further down the current path, you must
specify its path commencing with the Main menu. To do this, the first item of the
path must be 0. For example, to get to the Minescape3 File Maintenance menu
from any menu, enter 082.
To go back a menu level, press Enter.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Minescape user interface (UI) screens

A UI screen (also known as an input or data screen) allows you to enter
information into Minescape3 so that it can successfully execute a particular
process.
The following screen is an example of a UI screen. The UI screen in this example
allows you to create a new design file. It was selected by using the following
menu path:
GENERAL/FILES/DESIGN/CREATE
Note: Menu path names are shown in Minescape3 documentation with each menu level
delimited by a / character and with menu item names shown in capital letters. This is
different to the way in which you would actually enter the menu path. For information
about entering menu paths, refer to Moving around the menus.
UI screen example
Create a Design File
--- Output ---------------------------------------------------------------Design file :
--- Spatial Orientation --------------------------------------------------Origin:
Easting: Northing: Elevation: (Origin should be central point of data area.)
Dimension
:
Quadrant
: --- Units ----------------------------------------------------------------Internal distance unit :

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Fields
Each UI screen contains a number of fields. These fields may be blank (waiting
for you to enter data) or they may contain data (previously entered, or provided
by the system).
Field types
There are a number of different field types in which data can be stored.
An unprotected field is one in which you can enter or change data.
A protected field is one in which you cannot enter or change data. The cursor
does not move to a protected field.
Fields that only allow numbers (including appropriate +, - and . characters)
to be entered are termed numeric fields.
Fields that allow any characters to be entered are termed alphanumeric
fields.
An unprotected field can also be an extended field. Data entered into
extended fields is verified by Minescape3 to ensure that data integrity is
maintained. For example, when the name of a design file is entered,
Minescape3 verifies that the design file exists. If it does not exist, Minescape3
displays an error and allows you to enter the name of an alternative design
file.
A group of related fields for which multiple entries can be made is known as a
field group. Each field within a field group is a vector (a vector is effectively
an array). The following figure shows an example of a field group.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Example of a field group

Create a Table File
--- Output ---------------------------------------------------------------Table file
: ACQUAL
--- Table columns --------------------------------------------------------Name
Description
Unit Cat.
Unit
Type
Length Parent
HOLE
Hole
STRING 8
EASTING
Easting
LENGTH
Metres
DOUBLE NORTHING
Northing
LENGTH
Metres
DOUBLE RD
Relative density
REAL
IM
Inherent moisture
REAL
ASH
Ash
REAL
VM
Volatile matter
REAL
---

Table constants ------------------------------------------------------Name

Description
Unit Cat.
Unit
Type
Length
Vectors

--- Controls -------------------------------------------------------------Constant buffer size : -

field group

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

UI screen commands
Minescape3 contains a set of screen commands that help you to navigate
around a screen, manipulate the fields on the screen, and perform several other
functions.
To use a screen command:

Type in the command followed by Enter

and/or

Use the short cut key(s) to enter the command.

Note: 1. A screen command can be entered while the cursor is on any field.
2. When moving to a field, the cursor always moves to the first character of the field.
3. The cursor does not move to a protected field.
4. <n> is optional. If it is not entered it defaults to 1.

The following tables provide information about the available screen commands.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Help commands
Command

Short cut key(s)

\h

Description
Displays information about all available screen
commands.

\hf

F1

Displays information about the current field.

\hs

F2

Displays information about the purpose of the current

screen, how you should complete the screen, and lists
associated Minescape modules. You can obtain
additional information about a Minescape module by
referring to it in the on-line Modules reference
documentation.

\ca

F3

Provides a catalogue (list) of valid entries for the current

field. Secondary information about each of these entries
may also be provided.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Cursor movement commands

Cursor movement commands
Command

Short cut
key(s)

Description

Move between fields

Enter

Validates the current field and then moves the cursor to the next unprotected field.

\<n>

or

Moves the cursor forwards or backwards by <n> unprotected fields; \<n> or moves
the cursor forwards; \-<n> or moves the cursor backwards. For example, \2 moves
the cursor forwards by two unprotected fields; \-2 moves the cursor backwards by two
unprotected fields. No validation is performed.

\t

Home

Moves the cursor to the topmost (first) unprotected field on the screen.

\b

End

Moves the cursor to the bottommost (last) unprotected field on the screen.

\ta

Tab

Moves the cursor to the next unprotected data field. If the cursor is currently in a field
group, the cursor moves to the next field outside of the field group.

\do

Ctrl-n
or

Moves the cursor to the next unprotected field. If the cursor is currently in a field group,
but not on the last line of the field group, the cursor moves down a line within the field
group, but remains on the same field name.

\up

Ctrl-p
or

Moves the cursor to the previous unprotected data field. If the cursor is currently in a field
group, but not on the first line of the field group, the cursor moves up a line within the
field group, but remains on the same field name.

\s<n>

When in a field group, \s<n> moves (scrolls) the cursor (and the lines displayed, if
appropriate) forwards or backwards by <n> lines; \s<n> moves the cursor forwards, \s<n> moves the cursor backwards. The cursor remains on the same field name. For
example, \s2 moves the cursor forwards by two lines; \s-2 moves the cursor
backwards by two lines.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Data selection commands

Command

Short cut key(s)

Description

Select a field value from a catalogue

\ic

F4

Allows you to select an item from the catalogue of valid

entries for the current field. After you enter \ic, the
following prompt displays on the prompt line:
Enter catatemplate> +
All entries in the catalogue that match the specified
template, are displayed one at a time. To select an
entry, enter y. To show the next entry, enter n. To quit
and not select an entry, enter q. If the current field is on
a field group, there is also be an option to select all
following entries for the field. To do this, enter r.

Select an element ID from Magicad

\g

F8

Allows you to select a graphic element ID from a design

file displayed in Magicad and place it into the current
field. The \g screen command does not work on a field
that does not expect a graphic element ID.
In Magicad, select the element that you require by leftclicking on it two times.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Editing commands

Editing commands
Command

Short cut key(s)

Description

Move within a field

Ctrl-f

Moves the cursor forwards one character within the

current field.

Ctrl-b

Moves the cursor backwards one character within the

current field.

Ctrl-a

Moves the cursor to the start (first character) of the

current field.

Ctrl-e

Moves the cursor to the end (after the last character) of

the current field.

Bksp

Destructively moves the cursor backwards one

character within the current field.

Insert/overtype data
Ctrl-o

Toggles insert mode on and off. When insert mode is

on, characters that you type are inserted to the left of
the current cursor position. When insert mode is off,
characters that you type overwrite the current cursor
position.

Ctrl-d

Deletes the character under the cursor.

Delete data

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Editing commands (contd)

Command

\f

Short cut key(s)

Description

Ctrl-k

Deletes from the current cursor position to the end of

the current field.

Ctrl-u

Deletes the current field. If you press Enter directly

after Ctrl-u, the original contents of the field is
returned.

Ctrl-y

Inserts characters deleted by the previous Ctrl-k or

Ctrl-u.

F7

Deletes the current field. The original content of the field

is lost.

\cl

Deletes the current and all subsequent fields on the

screen. The original content of these fields is lost.

Field group/vector commands

\i<n>

F5

Inserts <n> blank lines after the current line. If F5 is

used, one line is inserted.

\co<n>

Inserts <n> copies of the current line after the current

line.

\ib<n>

Inserts <n> blank lines before the current line.

\de<n>
\se<string>

F6

Deletes <n> lines from a field group, starting with the

current line. If F6is used, the current line is deleted.
Searches all following lines of the field group for
<string> in the current vector. <string> must be a
precise match (except for case). The string is a

template.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Exiting commands
Command

Short cut key(s)

Description

Exit without saving changes

\q

F11

Exits the current screen and Minescape process.

Changes (if any) to data on the screen are lost. The
Minescape module associated with the screen just
exited is not submitted for execution.

Save changes and exit

\e

F12

Saves changes (if any) to the data on the screen and

then exits the current screen. A number of screens may
have to be completed to provide Minescape3 with the
information that it requires in order to complete a
process. If this is the case, enter \e after each of these
screens to complete the information that Minescape3
requires. Minescape3 then submits the Minescape
module that is associated with the screen just exited, for
execution in the background.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Specifications
The data entered on a screen can be saved as a specification. A specification
is a set of saved variable (field) names and their associated values.
Specifications are useful when entering the same or similar data on a screen a
number of times. For example, to create two similar tables named TABLE1 and
TABLE2, enter the data for TABLE1 and then save the data as a specification. To
create TABLE2, recall the specification and change the data on the screen as
required.
Specifications are also useful if, for example, you are in the middle of entering
data on a screen and you need to perform another Minescape function such as
create a design file. To do this, save the current screen as a specification (\sa),
quit (\q) from the current screen and then create the design file using the
appropriate menu option. Return to the previous screen and use (\us) the saved
specification. The data previously entered on the screen is redisplayed.
Specifications are stored in categories i.e. each specification has a specification
category name and a specification name.
The following table provides information about the available specification
commands.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Specification commands
Command

Short cut key(s)

Description

Save data as a specification

\sa

F10

<spec cat>
<spec name>

Creates a specification using the fields displayed on the

current screen. If a Minescape process requires more
than one screen of data to be entered, the following (or
previous) screens are not saved. If F10,is used, you
are prompted to enter <spec cat> and <spec name>.

Update a specification
\upd

Updates an existing specification using the fields

displayed on the current screen.

<spec cat>
<spec name>

Save multiple screens as a specification

To save the fields on multiple screens as a specification,
use \sa on the first screen followed by \upd on the
subsequent screens.

Retrieve data from a specification

us

<spec cat>
<spec name>

or

\<spec cat>

<spec name>

F9

Updates the values of fields displayed on the current

screen from the requested specification. You can use
any specification. Only matching field names are
updated. If F9 is used, you are prompted to enter
<spec cat> and <spec name>.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

There are two Minescape3 commands that can be used to list specification data:

speccata

speclist
These commands are not UI screen commands, but are commands that must
be entered from the prompt line of a menu screen.

speccata
Lists all specifications for a particular category.
Syntax: speccata<spec cat>
If the category is left blank, all categories and hence all names are listed.
speclist
Lists all fields held in a specification along with their associated values.
Syntax:

speclist<spec cat><spec name>

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Other commands
Command

\re

Short cut key(s)

Ctrl-l

Description
Redraws the screen. Use this screen command if the
screen has become corrupted.

\v

A field may be longer than the portion of the screen

used to display it. Use \v to display the field in its
entirety. The following message displays on the
message line:
?UIVALUE Value <field value>

\w

Displays the name of the current field. The following

message displays on the message line:
?UIWHRFLD Currently positioned at item
<field name>
If the current field is in a field group, the current line
number within the field group and the name of the field
group is also displayed. The following message displays
on the message line:
?UIWHRVEC Currently at repeat <line number> of
vector <field name>, group
<field group name>

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Module execution, monitoring and logging

Controlling module execution, logging, and feedback
After a module has been submitted for execution, it runs automatically in the
background (by default) if the maximum number of modules that can run
simultaneously (10) has not been exceeded.
You can however change the way in which Minescape3 executes modules, as
well as the way in which Minescape3 logs module execution information, and
feeds back progress information about executing modules.
To change these controlling parameters, use the following Minescape3 menu
path:
GENERAL/ADMINISTRATION/CONFIGURE
Alternatively, you can use the setconfig Minescape3 command.
The following figure shows the default configuration control values.
Configuration control
Project:document

- M I N E S C A P E -

User:mintest

Configuration Control
----- Module Control ------Suppress execution
:
Foreground execution
:
Maximum execution limit
:
Automatic chaining
:
Log module arguments
:
Log file name
:
Retain module output files:
Extended module logging
:

-------- Feedback Control ------No

No
10
No
None
No
No

Display startup/shutdown :
Display interim messages :
Error display format
:

Yes
Yes
Default

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Controlling module execution

A submitted Minescape module:
Cannot run in the foreground
As module execution is controlled by the module server, and not directly by
Minescape3, modules can no longer run in the foreground using
Minescape3.
Can run in the background
To run modules in the background, set Foreground Execution to N. In
background mode, you are free to perform other tasks while modules
execute. To change the number of modules that can run simultaneously in
the background, specify a value of 1-10 in the Maximum Execution Limit
field. To execute modules consecutively, set Maximum Execution Limit to
1.
If a module is submitted when the maximum number of modules are
executing, the module is held with a status of Pending until a currently
executing module has terminated or the Maximum Execution Limit is
increased.
Note: If you try to exit from Minescape3 and modules are pending, all pending modules will run
sequentially in the order in which they were submitted before the Minescape3 session
actually terminates.

Can be run as part of a chain

A number of modules can be chained together so that they execute in a
particular sequence.
To start module chaining, use the modchain command i.e. enter modchain
at the prompt line of a menu screenthis sets Automatic Chaining to Y. All
modules submitted prior to the endchain or nomodchain command being
used are held pending, i.e. have a status of Pending.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

To execute a chain and allow a new chain to commence, use the endchain
command i.e enter endchain at the prompt line of a menu screen.
To end module chaining (and execute the current chain) use the
nomodchain command i.e enter nomodchain at the prompt line of a menu
screenthis sets Automatic Chaining to N.
Note: If you try to exit from Minescape3 and modules are pending, all pending modules will run
sequentially in the order in which they were submitted before the Minescape3 session
actually terminates.

Controlling module feedback

Messages detailing the progress of a submitted module are displayed on the
message line. These messages include:

startup messages

interim (progress) messages

termination messages

Module feedback is provided in two forms;

Progress feedback

includes information such as percentage complete,

records processed, etc.

Termination feedback includes information such as whether or not the module

completed successfully.
To disable the display of startup and termination messages, set Display
Startup/Shutdown to N.
To disable the display of interim (progress) messages, set Display Interim
Messages to N.
The format of the error message is controlled by Error Display Format, and can
be Default, Short or Long.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Module execution log files

Every module that is executed creates a log file containing, in the following
order:
a list of all of the modules input parameters and their values
startup, progress and termination messages
a list of all of the modules output parameters (if any) and their values.
These files are created in the logfiles directory of the project, with a name of
batch-<n>.cmo, where <n> is the number of the batch in which the module
was run. Batch numbers are usually assigned automatically by the system,
starting at 1 and continuing up to 500 before being re-used. Minescape3
keeps track of the log file associated with each module that has been run
(see Using modcon to control modules for information on how to view a
modules log file).

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Tracing problems
If execution errors cause a module to abort, Minescape produces a Module
Abort Error Report. An example is shown in the following screen:
Module Abort Error Report example

Project:document

- M I N E S C A P E -

User:mintest

CREATE A SECTION THROUGH SURFACES

Module Abort Error Report
Module : SURFSECTION
?GNNORDLNCannot read line string 283

Press <CR> to continue:

To help you solve problems that do not have an obvious solution, refer to the online Modules reference documentation for additional information about the
aborted module.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Using modlist to list the status of submitted modules

The modlist (module list) Minescape3 command lists each Minescape module
that has been submitted. The most recent module submitted appears first.
Note: All information regarding up to the last 500 modules that have been run in a project is
retained between Minescape3 sessions. This is a departure from previous versions of
Minescape, where most module information was lost on exiting Minescape.

The following information is provided for each module:

the batch number
the module name
the status of the module which is one of the following:
Completed
The module has successfully completed. The time of completion displays.
Executing
The module is currently executing.
Did not complete
The module has aborted because a serious error has been found. The
applicable error message(s) displays directly under the relevant module
information line if Minescape3 started this module in this session.
Complete but Warnings
The module has successfully completed, however something has occurred
that requires further investigation. The applicable warning message(s)
displays directly under the relevant module information line. The time of
completion displays.
Pending
The execution of a module has been deferred.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

The time that the module was invoked, submitted, started and completed
(not all of these may apply).

Note: This information is only available for modules that were started by Minescape3 in the
current session. These times are not for listed modules that were not started by
Minescape3, or were started in a previous session.

An example modlist screen is shown in the following screen:

Example modlist screen

Project:dragtest

- M I N E S C A P E -

User:minescap

Batch Module
Status
Invoked Submitted Started Completed
====================================10:14:48===================================
35
SURFSECTION
Completed
10:14:05 10:14:06 10:14:12 10:14:45
SECTION12 : Surface section written to ./designs/sw12.dgn/SECTION12.
------------------------------------------------------------------------------34
MAGCREATE
Completed
10:13:01 10:13:02 10:13:06 10:13:10
Created design file ./DESIGNS/SW12.DGN.
------------------------------------------------------------------------------33
GDS Display ListComplete but Warnings .
.
.
.
------------------------------------------------------------------------------32
GDS Display ListCompleted
.
.
.
.
------------------------------------------------------------------------------31
Clip and transfoCompleted with Info
.
.
.
.
------------------------------------------------------------------------------30
Clip and transfoCompleted with Info
.
.
.
.
------------------------------------------------------------------------------<CR> to continue, Q to quit:

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Using modcon to control modules

Similar to modlist, the modcon (module control) Minescape3 command lists
each Minescape module that has been submitted. Just like modlist, the most
recent module submitted appears firstthis is different from previous versions
of Minescape.
Using modcon, you can also:
view the log (.cmo) file for a listed module
abort executing and pending modules.
An example of a modcon screen is shown in the following screen:
The name and status of each Minescape module submitted is displayed.
Information for up to the last 500 modules submitted in a project is maintained.
However, Minescape V3 displays only the last 200.
Example modcon screen
Project:dragtest

- M I N E S C A P E -

User:minescap

Module Monitor Control

Batch Module
Status
Info
Abort
----------------------------------------------------------------------35
SURFSECTION
Completed
***
34
MAGCREATE
Completed
***
33
GDS Display List
Complete but Warnings
32
GDS Display List
Completed
31
Clip and transfo
Completed with Info
30
Clip and transfo
Completed with Info
29
SURFSECTION
Did not Complete
28
MAGCREATE
Completed
27
TABCREATE
Completed
26
TABCREATE
Did not Complete
25
TABCREATE
Did not Complete
24
SURFDRAGSETUP
Completed
Notes : (a) Entering any response into the Information field will
cause further information about the module to be displayed
(b) Entering any response into the Abort field will abort the
module when this screen is exited.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

To abort an executing or pending module, enter any character in the Abort field
of the appropriate module. The status of the module changes to Aborted. The
abort occurs when the modcon screen is exited using \exit.
To view the log file for a module, enter any character in the Information field of
the appropriate module.
An example of a module log file display is shown in the following screen:
Module execution log files

provides information on the contents of the log file.

Example module log (.cmo) file

Project:dragtest

- M I N E S C A P E -

User:minescap

Module Monitor Control

[MAGCREATE Version 4.001 (7)]
->MAGDESIGN Design file to create: SW12
->MAGMODE Design file dimension (3D/2D): 3D
->MAGXORIG Global origin in X: 100
->MAGYORIG Global origin in Y: 1000
->MAGZORIG Global origin in Z: 0
->MAGQUAD Quadrant (1/2/3/4): 1
[Program Default for MAGDISTUNIT : Metres]
->MAGDISTUNIT Design file units: Metres
[10:13:10] Created design file ./DESIGNS/SW12.DGN.
[MAGCREATE Version 4.001 (7)] completed successfully

Press <CR> to continue:

After you have finished viewing the log file for a module, the initial modcon
screen redisplays.

Minescape3
Using Version 3 of Minescape
Contents

Home

Glossary

Index

Exiting Minescape3
To exit Minescape3, enter exit or 09 (or 0e) from the prompt line of any
Minescape3 menu or enter 9 (or e) from the prompt line of the Minescape3 main
menu.