Mail Archives: djgpp/1994/04/11/09:30:54
Hi,
I have pulled some of the DJGPP sources from oak.oakland and have them
installed. I think the installation is fine but I would like to get info
working and need to know which bits are essential for this, in essence,
how to I get the help system up and running.
Also, most of the packages come with binaries, documentation and
sources, are the sources required or can they be left out?
Regards,
Andy Wilson
_____________________________________________________ andywil AT bnr DOT ca ___
BNR-NITEC, Doagh Rd, Tel +44 (0)232 363532
Newtownabbey, ESN 6 751 3532
BT36 6XA
United Kingdom
How to get info
go to - /usr/pde/mentor/release/4.01b/man/man1
use command - nroff -man mcomms.1 | more
MCOMMS(1) MCOMMS(1)
NAME
mcomms - Mentor Communications tool used to connect to a debug node
DESCRIPTION
The Mentor Communications facility is used to communicate with a debug
node. A debug node can be a DMS SuperNode captive office, a
FiberWorld shelf, or HPSOS. The Communications window lists the debug
nodes you can connect to, while all available debug nodes are listed
in the Available Nodes window.
To start the Mentor Communications window, type "mcomms" at the PLS
prompt. Alternatively, select Communications from the Navigator,
Converter, or SMED "Mentor" menu. If mentor is not running when
mcomms is issued, it will be started. mcomms supports the following
command line options:
mcomms -mnav Starts Communications and exposes the Navigator
mcomms -mconvert Starts Communications and exposes the Converter
mcomms -all Starts Communications and exposes the Navigator
and
the Converter
If the node is not listed in the Communications window, select the
"Add" menu item from the title menu to display the Available Nodes
window. Select the required node. Use the popup menu to select
"Add". Mentor adds the selected node to the list in the
Communications window. To add other nodes, contact the Mentor
Helpline.
Modules for Captive Office, HPSOS, FibreWorld
Captive Offices, HPSOS, and FibreWorld Network Elements all require
the modules that allow Mentor to connect to them. Each of the
platforms require the base modules in addition to the modules that
implement the link handling for the particular platform:
BASE: Subsystem DLPSUB (dlpmach, dlpdefs, and dlpv0), CLBASSUB
(clintrun), and Subsystem CLLNKSUB (cllnkbas and mentorcl).
HPSOS: Subsystem CLHPSSUB (clhpsbnd and clhpsp).
Captive Offices: Subsystem CLX25SUB (mtdest, clx25bnd, and clx25p).
Network Elements: Subsystem MTGENSUB (mtgenbnd and mtrcomms).
For example, an HPSOS load would need the subsystems DLPSUB, CLBASSUB,
CLLNKSUB, and CLHPSSUB in order to establish a connection.
HPSOS
To add an HPSOS entry to the list in the Communications window, follow
one of the following two processes:
- 1 - Formatted: March 28, 1994
MCOMMS(1) MCOMMS(1)
A) if you wish to connect to an HPSOS session running on your
workstation, enter "localhost" in the "HPSOS Server" data entry field
in the Available Nodes window.
B) if you wish to connect to an HPSOS session running on another
workstation, enter the node name (eg: "bcarh123") in the "HPSOS
Server" data entry field in the Available Nodes window.
To connect, select the HPSOS item in the Communications window and
choose "connect". Mentor will not connect if HPSOS is suspended
(because of emdebug, for example).
CAPTIVE OFFICE
To initiate a communications link between Mentor and any DMS node
listed in the Communications window, select the required node in the
Communications window and choose the "Connect" menu item to connect
the node to Mentor.
FIBERWORLD NETWORK ELEMENT
Use the following procedure to connect to a FibreWorld Network
Element. For more information on mentor_ra, see the man page
mentor_ra(1).
1. Start "mentor" in PLS
2. Start "mcomms" from PLS (or another Mentor tool)
3. Start "mentor_ra fdnmds -v <NE>" from a UNIX shell and login as
required to get a SOS CI command interpreter.
4. In the "mentor_ra" window, type "~m" and allow "mentor_ra" to
take over control of the session. You will get a notice indicating
that "mentor_ra" has taken control of the process.
5. From the "mcomms" window, connect to "generic"
6. To make "mentor_ra" release the session back to the user you must
disconnect from "generic" in the "mcomms" window.
Or, an laternate way to connect to an NE is through the NElogin
program. Follow the above steps except use the following procedure in
place of step three above:
3. Start "mentor_ra telnet <OPC hostname>" from a UNIX shell and login
as required. Make sure that you log in to an account that will not
pop-up extra windows. From the "opc>" prompt type
"/iws/tel/nelogin <NE#>" and login to get a SOS CI command
interpreter.
Trouble Shooting
- 2 - Formatted: March 28, 1994
MCOMMS(1) MCOMMS(1)
If "~m" does not tell you that "mentor_ra" has taken over control of
this process then check to see if "mtrcomms" cibincom is working on
the NE. Type "mtrcomms" to see if you get any message other than
"unknown command". If the command could not be found then it should
be loaded in. If mtrcomms is present, then you can quit by typing
"quit". Call the Mentor Helpline if "mtrcomms" is present and "~m"
cannot take control of the process.
SEE ALSO
mconvert(1); mnav(1); smed(1); ; gcinfo(1); glinfo(1);
mentor_context(1), mentor_ra(1)
9
- 3 - Formatted: March 28, 1994
- Raw text -