T.R | Title | User | Personal Name | Date | Lines |
---|
3545.1 | Have observed the same problem, se note 3415. | ANTIK::WESTERBERG | Stefan Westerberg DS Stockholm | Thu Aug 13 1992 13:17 | 4 |
| I have observed the same problem described in note 3415, but I haven't recived
any answer !!
/Stefan
|
3545.2 | TSAM still has this problem | TOOK::FONSECA | I heard it through the Grapevine... | Thu Aug 13 1992 16:52 | 30 |
3545.3 | more hangs... | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Tue Sep 08 1992 01:03 | 33 |
| re: .2
Is there anything else that can cause TSAM to hang?
I have a server that I can access fine from TSM, but TSAM just
hangs seemingly forever...
MCC> disabl mcc 0 termserver_am abort true
MCC 0 TERMSERVER_AM
AT 8-SEP-1992 10:12:32
Normal operations terminated.
MCC> enable mcc 0 termserver_am
MCC 0 TERMSERVER_AM
AT 8-SEP-1992 10:12:38
Normal operation has begun.
MCC> show term rssg all attr
Terminal_Server BUSHIE_NS:.rssg
AT 8-SEP-1992 10:12:43 All Attributes
Address = 08-00-2B-04-A9-4F
Name = BUSHIE_NS:.rssg
BUSHIE::DRANSFIELD 11:01:25 MCC_MAIN CPU=00:00:27.82 PF=10317 IO=1449
MEM=7571
!!! it just hangs here
This is V1.2 MCC on VMS V5.5-2S7 with DECnet vax extensions.
Thanks,
Mike
|
3545.4 | reregister fixed it | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Tue Sep 08 1992 22:46 | 6 |
| re: .3
I think this was a problem with the way it was registered.
I had registered two names with the same address and also didn't
have log_io and phy_io privilege.
Having reregistered it, it now works fine.
Mike
|
3545.5 | SERVICE CIRCUIT is important | BERN01::GMUER | | Thu Nov 26 1992 13:41 | 113 |
|
We had a lot of problems with an interrupted or hanging TS AM. DECmcc runs
on a different node than the load host of the terminal servers. After an
evaluation of all possibilities we found that the TSM convert utility
generates SERVICE CIRCUIT statements, which may not be correct on the
MCC system:
--------------------------------------------------------------------------
$ mana/enter
DECmcc (V1.2.0)
MCC> ! DECmcc procedure generated by MCC_TS_AM_CONVERT utility
MCC> !
MCC> REGISTER TERMINAL_SERVER .TS.GBE310 -
_MCC> ADDRESS=08-00-2B-1B-E6-8D,-
_MCC> TYPE=DS300,-
_MCC> MAINTENANCE KEY=%X0000000000000000,-
_MCC> LOGIN KEY="ACCESS"
Terminal_Server LOCAL_NS:.ts.gbe310
AT 26-NOV-1992 16:18:57
Registration successful.
MCC> SET TERMINAL_SERVER .TS.GBE310 -
_MCC> DECNET ADDRESS=13.7,-
_MCC> IMAGE FILE=SYS$SYSROOT:[DECSERVER]SH1601ENG.SYS,-
_MCC> DUMP FILE=SYS$COMMON:[DECSERVER]DS3GBE310.DMP ! ,-
_MCC> ! SERVICE CIRCUIT={BNA-0} <-- Coment the critical statement
Terminal_Server LOCAL_NS:.ts.gbe310
AT 26-NOV-1992 16:19:16 Characteristics
Modification completed successfully.
Dump File = SYS$COMMON:[DECSERVER]DS3GBE310.DMP
Image File = SYS$SYSROOT:[DECSERVER]SH1601ENG.SYS
DECnet Address = 13.7
MCC> SHOW TERMINAL_SERVER .TS.GBE310 ALL STATUS
Terminal_Server LOCAL_NS:.ts.gbe310
AT 26-NOV-1992 16:19:56 Status
Examination of attributes shows
Current Active Ports = 2
High Active Ports = 4
Max Active Ports = 16
Current Active Users = 2
............
MCC> SET TERMINAL_SERVER .TS.GBE310 -
_MCC> SERVICE CIRCUIT={BNA-0}
Terminal_Server LOCAL_NS:.ts.gbe310
AT 26-NOV-1992 16:20:08 Characteristics
Modification completed successfully.
Service Circuits = { "BNA-0" }
MCC> SHOW TERMINAL_SERVER .TS.GBE310 ALL STATUS
Terminal_Server LOCAL_NS:.ts.gbe310
AT 26-NOV-1992 16:20:19 Status
Communication with the target has been interrupted
MCC> DISABLE MCC 0 TERM ABORT TRUE
MCC 0 TERMSERVER_AM
AT 26-NOV-1992 16:20:43
Normal operations terminated.
MCC> ENABLE MCC 0 TERM
MCC 0 TERMSERVER_AM
AT 26-NOV-1992 16:21:30
Normal operation has begun.
MCC> SHOW TERMINAL_SERVER .TS.GBE310 ALL STATUS
-----------> Here it hangs
MCC> SET TERMINAL_SERVER .TS.GBE310 -
_MCC> SERVICE CIRCUIT={ISA-0}
Terminal_Server LOCAL_NS:.ts.gbe310
AT 26-NOV-1992 16:23:55 Characteristics
Modification completed successfully.
Service Circuits = { "ISA-0" }
MCC> SHOW TERMINAL_SERVER .TS.GBE310 ALL STATUS
MCC> DISABLE MCC 0 TERM ABORT TRUE
MCC 0 TERMSERVER_AM
AT 26-NOV-1992 16:24:19
Normal operations terminated.
MCC> ENABLE MCC 0 TERM
MCC 0 TERMSERVER_AM
AT 26-NOV-1992 16:24:23
Normal operation has begun.
MCC> SHOW TERMINAL_SERVER .TS.GBE310 ALL STATUS
Terminal_Server LOCAL_NS:.ts.gbe310
AT 26-NOV-1992 16:24:27 Status
Examination of attributes shows
Current Active Ports = 2
High Active Ports = 4
Max Active Ports = 16
Current Active Users = 2
........
--------------------------------------------------------------------------
Regards, Edgar
|
3545.6 | QAR#233 in MCC013_INT | CHRISB::BRIENEN | Network Management Applications! | Mon Nov 30 1992 12:25 | 1 |
| The previous note has been added to the MCC013_INT database as QAR#233.
|
3545.7 | | TOOK::FONSECA | I heard it through the Grapevine... | Mon Nov 30 1992 13:40 | 26 |
| From what I can tell, you are describing two seperate problems
here:
1. When you use the TSM convert utility, you wish it would somehow
magicly put the correct circuit name into the registration script.
All the convert utility does is extract the information from the
TSM database, and put it in a script ready to be loaded into TSAM.
There is no way the conversion program could know what the service
circuits will be in the future if the script it generates is copied
from one node to another. If the user wishes to run TSAM on a node
which has different ethernet devices than the node TSM was run on,
they should edit the registration script and do a wild-card replace
from BNA-0 to ISA-0 for example.
It probably is not documented that you should note this fact, and I
will make sure that is added to the documentation if we ever come
out with another version.
2. Once you have registered a terminal server with the wrong circuit
information, you don't want TSAM to hang when attempting to connect
to the terminal server.
I can't tell from your note whether you have installed the update to TSAM
(V1.0.2) which corrects a hanging problem which may be similar to yours.
If you have not installed this kit, I would suggest you do.
|
3545.8 | Re .-1 | BERN01::GMUER | | Tue Dec 01 1992 09:04 | 6 |
| Thanks for the fast replies !
Re .-1: I did not expect any magic in the conversion utility. I think a
warning message during the run of the utility with an additional hint in
the TSAM documentation is enough. The sense of the note was to inform the
DECmcc people about a potential trap.
|