Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
I have noticed that under MCC V1.3 and the oeprations for "set host" and "telnet" that at least with "set host" I experience some problems connecting. For certain entities, I select the icon and "set host". A DECterm window appears, but it disappears immediately. There is an error message, though it is very quick I think it is: RMS-F- File syntax error Some node4's it works, some it doesn't. I have not tried enough IP nodes to ascertain the behaviour with "telnet". Anyone know why this is happening? Thanks, Dave
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
5380.1 | KETJE::PACCO | Gallia divisa est in partes tres | Wed Jul 28 1993 14:29 | 15 | |
You can trace the problem to look at the MCC_SYSTEM:MCC_APPL_MCCBASE.DEF file Change the "set host" into a command file. In the command file do a write sys$output "''p1'" followed by a wait. Youl'l see exactly what is passed as argument to the set host command. Another DECmcc user. Dominique. | |||||
5380.2 | More info on problem | TRKWSH::COMFORT | Here beside the rising tide | Thu Jul 29 1993 12:37 | 21 |
Dominique - Thanks for the tip. I tried your suggestion and have found that the problem is that on certain node4s, the DECnet address is returned instead of the name, ie. 1.35 instead of PHCOMM. Further investigation shows that if a node4 was registered under MCC V1.1, the node number is returned, it it was registered under V1.2, the name is returned and operation is just fine. I also came across a V1.1 node4 that returns an error: 003 29-JUL-1993 11:30:31.08 no corresponding entity instance exists Any developers know why this is happening w/ V1.1 registered entities? I suppose I can provide a workaround for the ones that return the node number, but the other one is just a problem to be resolved. Thanks, Dave for a |