[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

3456.0. "Division by Zero in DNA4 Autotopology" by FRAIS::64917::SYSTEM (Information, that's all I need...) Wed Jul 29 1992 10:44

Hi all,

I'm experiencing problems with DNA4 autotopology. Here's my configuration:

VAXstation 3100/48 SPX, 32MB memory
VMS V5.5
DECmcc V1.2 BMS
ELM V1.2 SSB
TSAM ? (the latest FT)
DNS V1.1

I start autotopology with a new domain, search a particular area by adjacency,
and this is what I get (btw, area 63 is hidden. I don't know if this is causing
the problem):




Time out while expecting data from node 63.412
Node 63.412 did not respond
Results from 63.412, 0 circuits, 0 adjacencies, Q size 10...
Results from 63.157, 1 circuits, 1 adjacencies, Q size 9...
Time out while expecting data from node 63.198
Node 63.198 did not respond
Results from 63.198, 0 circuits, 0 adjacencies, Q size 8...
Results from 63.295, 1 circuits, 1 adjacencies, Q size 7...
Time out while expecting data from node 63.402
Node FRSMAC did not respond
Results from 63.402, 0 circuits, 0 adjacencies, Q size 6...
Results from 63.408, 1 circuits, 1 adjacencies, Q size 5...
Time out while expecting data from node 63.919
Time out while expecting data from node 63.919
Node 63.919 did not respond
Results from 63.919, 0 circuits, 0 adjacencies, Q size 4...
Results from 63.53, 1 circuits, 1 adjacencies, Q size 3...
Time out while expecting data from node 63.774
Node 63.774 did not respond
Results from 63.774, 0 circuits, 0 adjacencies, Q size 2...
Time out while expecting data from node 63.191
Node 63.191 did not respond
Results from 63.191, 0 circuits, 0 adjacencies, Q size 1...
Node 0.1 did not respond
Results from 0.1, 0 circuits, 0 adjacencies, Q size 0...
Kill process error


        DECnet Phase IV Autoconfiguration data collection completed.

        DECnet Phase IV Autoconfiguration starting data formatting ...
%SYSTEM-F-FLTDIV_F, arithmetic fault, floating divide by zero at PC=00001F71, PS
L=03C00000
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

MCC_AC_WAN4_MAP load_position_data               3969      000005D5  00001F71
MCC_AC_WAN4_MAP main                             2997      0000030B  00000553

        Error:  An error has occurred.

        Warning:  DECnet Phase IV Autoconfiguration data files
                  may be corrupt.

        DECnet Phase IV Autoconfiguration exiting under error conditions.



Any help would be appreciated.


Thanx in advance



Josch

T.R	Title	User	Personal Name	Date	Lines
3456.1	QAR 3313	TOOK::MINTZ	Erik Mintz, dtn 226-5033	`Wed Jul 29 1992 12:01`	1
	This note has been entered as QAR 3313
3456.2	One more try	FRAIS::64917::SYSTEM	Information, that's all I need...	`Wed Jul 29 1992 16:27`	11
	Hi all, I tried to start the same process as mentioned in .0 again. Same results. It seems that this problem is reproducable. Regards Josch
3456.4	Arithmetic fault during Decnet autoconfiguration	MLNCSC::LASAGNA	Fight f yo'right,Paul's b'tique,Chk yo'heads	`Wed Oct 21 1992 16:39`	447
	Hi, i have a problem that has already been encountered from other people (mentioned in 3456,3584), i know there is an opened QAR (#3313). I checked in the QAR system and i saw that there are no answers. I would like to know if there are news about this problem, at least why it is happening the fault. the configuration: Vaxstation 4060 with 80Mb, vms 5.5, motif, dns 1.1, mcc 1.2 elm and tsam am. No problem with mcc_audit.com i have included the complete log of the installation failed. Ciao, Andrea Lasagna Milan, Italy Welcome to DECnet Phase IV Autoconfiguration Type '?' for Help or 'Q' to Quit, at any of the prompts. Checking the namespace. This will take a moment. Please wait... DECnet Phase IV Autoconfiguration will use the following prefixes to generate fullnames for registration: Entity Class Prefix DOMAIN . NODE4 .dna_node. SNMP . o Are the above prefixes ok? Y/N [Y]: o Please specify a domain: decnet Based on the prefix file on your system DECnet Phase IV Autoconfiguration will use the domain ".DECNET". o Is ".DECNET" the correct domain name? Y/N [Y]: DECnet Phase IV Autoconfiguration will use the base directory "SYS$SYSROOT:[SYSMGR]". o Is "SYS$SYSROOT:[SYSMGR]" the correct base directory? Y/N [Y]: DECnet Phase IV Autoconfiguration will use "SYS$SYSROOT:[SYSMGR.DNA4.DECNET]" as a working directory. DECnet Phase IV Autoconfiguration will copy DECmcc Map files to MCC_MAPS, which is currently pointing to the directory "DKA300:[MCC.MAPS]". o Type N to prevent copying DECmcc Map files to "DKA300:[MCC.MAPS]". Y/N [Y]: Please choose one of the following DECnet Phase IV Autoconfiguration options: [1] Discovery [2] Discovery and Registration * [3] Creation of Map and Registration Files * [4] Registration Note that it is possible to view DECmcc Maps before running registration, using the "DECmcc Map Snapshots" option. If you wish to do this, choose option [1]. * These options are disabled until supporting files are created by choosing option [1] or [2]. o Enter option [2]: Please choose one of the following configurations: [1] All DECnet Phase IV nodes [2] All DECnet Phase IV nodes in selected area(s) [3] All DECnet Phase IV nodes in a LAN [4] All level 1 and level 2 DECnet Phase IV routers [5] ALL level 1 and level 2 DECnet Phase IV routers in selected area(s) [6] ALL level 1 and level 2 DECnet Phase IV routers on the LAN [7] All level 2 DECnet Phase IV routers [8] All level 2 DECnet Phase IV routers in selected area(s) [9] All level 2 DECnet Phase IV routers in the LAN o Enter option [2]: 2 Please choose a search method: [1] Search by adjacency [2] Search by address o Enter option [1]: 1 Please specify starting nodes for the search. Enter one node at a time. o Starting node [30.1023]: 30.7 Press RETURN to end the list. o Additional starting node(s) [30.7]: Please specify areas to include in the search. Enter one area at a time. o Area to include [30]: 30 Press RETURN to end the list. o Additional area to include [30]: Please specify areas to exclude from the search. Enter one area at a time. o Area to exclude: DECnet Phase IV Autoconfiguration starting data collection ... This may take a while... Results from 30.7, 1 circuits, 74 adjacencies, Q size 74... Results from 30.2, 1 circuits, 74 adjacencies, Q size 84... Time out while expecting data from node 30.346 Node 30.346 did not respond Results from 30.346, 0 circuits, 0 adjacencies, Q size 83... Results from 30.175, 1 circuits, 74 adjacencies, Q size 85... Results from 30.174, 1 circuits, 74 adjacencies, Q size 86... Results from 30.1, 1 circuits, 74 adjacencies, Q size 86... Time out while expecting data from node 30.26 Time out while expecting data from node 30.26 Node 30.26 did not respond Results from 30.26, 0 circuits, 0 adjacencies, Q size 85... Results from 30.167, 1 circuits, 74 adjacencies, Q size 84... Results from 30.168, 1 circuits, 74 adjacencies, Q size 84... Time out while expecting data from node 30.20 Node TLVD02 did not respond Results from 30.20, 3 circuits, 125 adjacencies, Q size 115... Results from 30.260, 1 circuits, 74 adjacencies, Q size 114... Results from 30.169, 1 circuits, 1 adjacencies, Q size 113... Results from 30.162, 1 circuits, 1 adjacencies, Q size 112... Results from 30.14, 1 circuits, 1 adjacencies, Q size 111... Results from 30.1022, 1 circuits, 1 adjacencies, Q size 110... Results from 30.51, 1 circuits, 1 adjacencies, Q size 109... Time out while expecting data from node 30.44 Node 30.44 did not respond Results from 30.44, 0 circuits, 0 adjacencies, Q size 108... Results from 30.160, 1 circuits, 1 adjacencies, Q size 107... Results from 30.9, 1 circuits, 1 adjacencies, Q size 106... Time out while expecting data from node 30.29 Node 30.29 did not respond Results from 30.29, 0 circuits, 0 adjacencies, Q size 105... Time out while expecting data from node 30.345 Node 30.345 did not respond Results from 30.345, 0 circuits, 0 adjacencies, Q size 104... Results from 30.13, 1 circuits, 1 adjacencies, Q size 103... Time out while expecting data from node 30.177 Node 30.177 did not respond Results from 30.177, 0 circuits, 0 adjacencies, Q size 102... Time out while expecting data from node 30.118 Node 30.118 did not respond Results from 30.118, 0 circuits, 0 adjacencies, Q size 101... Time out while expecting data from node 30.95 Node 30.95 did not respond Results from 30.95, 0 circuits, 0 adjacencies, Q size 100... Time out while expecting data from node 30.81 Node 30.81 did not respond Results from 30.81, 0 circuits, 0 adjacencies, Q size 99... Time out while expecting data from node 30.192 Node 30.192 did not respond Results from 30.192, 0 circuits, 0 adjacencies, Q size 98... Time out while expecting data from node 30.43 Node 30.43 did not respond Results from 30.43, 0 circuits, 0 adjacencies, Q size 97... Results from 30.161, 1 circuits, 1 adjacencies, Q size 96... Time out while expecting data from node 30.3 Node 30.3 did not respond Results from 30.3, 0 circuits, 0 adjacencies, Q size 95... Results from 30.48, 1 circuits, 1 adjacencies, Q size 94... Results from 30.171, 1 circuits, 1 adjacencies, Q size 93... Time out while expecting data from node 30.103 Node 30.103 did not respond Results from 30.103, 0 circuits, 0 adjacencies, Q size 92... Time out while expecting data from node 30.32 Node 30.32 did not respond Results from 30.32, 0 circuits, 0 adjacencies, Q size 91... Results from 30.50, 1 circuits, 1 adjacencies, Q size 90... Time out while expecting data from node 30.159 Node 30.159 did not respond Results from 30.159, 0 circuits, 0 adjacencies, Q size 89... Time out while expecting data from node 30.354 Node 30.354 did not respond Results from 30.354, 0 circuits, 0 adjacencies, Q size 88... Results from 30.41, 1 circuits, 1 adjacencies, Q size 87... Time out while expecting data from node 30.347 Node 30.347 did not respond Results from 30.347, 0 circuits, 0 adjacencies, Q size 86... Time out while expecting data from node 30.98 Node 30.98 did not respond Results from 30.98, 0 circuits, 0 adjacencies, Q size 85... Time out while expecting data from node 30.208 Node 30.208 did not respond Results from 30.208, 0 circuits, 0 adjacencies, Q size 84... Time out while expecting data from node 30.153 Node 30.153 did not respond Results from 30.153, 0 circuits, 0 adjacencies, Q size 83... Results from 30.12, 1 circuits, 1 adjacencies, Q size 82... Results from 30.6, 1 circuits, 1 adjacencies, Q size 81... Results from 30.326, 1 circuits, 1 adjacencies, Q size 80... Results from 30.49, 1 circuits, 1 adjacencies, Q size 79... Time out while expecting data from node 30.151 Node 30.151 did not respond Results from 30.151, 0 circuits, 0 adjacencies, Q size 78... Results from 30.39, 1 circuits, 1 adjacencies, Q size 77... Results from 30.40, 1 circuits, 1 adjacencies, Q size 76... Time out while expecting data from node 30.348 Node 30.348 did not respond Results from 30.348, 0 circuits, 0 adjacencies, Q size 75... Time out while expecting data from node 30.356 Node TLSVAF did not respond Results from 30.356, 0 circuits, 0 adjacencies, Q size 74... Time out while expecting data from node 30.139 Node 30.139 did not respond Results from 30.139, 0 circuits, 0 adjacencies, Q size 73... Time out while expecting data from node 30.52 Node 30.52 did not respond Results from 30.52, 0 circuits, 0 adjacencies, Q size 72... Results from 30.38, 1 circuits, 1 adjacencies, Q size 71... Time out while expecting data from node 30.349 Node 30.349 did not respond Results from 30.349, 0 circuits, 0 adjacencies, Q size 70... Time out while expecting data from node 30.33 Node 30.33 did not respond Results from 30.33, 0 circuits, 0 adjacencies, Q size 69... Results from 30.28, 1 circuits, 1 adjacencies, Q size 68... Time out while expecting data from node 30.186 Node 30.186 did not respond Results from 30.186, 0 circuits, 0 adjacencies, Q size 67... Time out while expecting data from node 30.45 Node 30.45 did not respond Results from 30.45, 0 circuits, 0 adjacencies, Q size 66... Results from 30.176, 1 circuits, 1 adjacencies, Q size 65... Time out while expecting data from node 30.34 Node 30.34 did not respond Results from 30.34, 0 circuits, 0 adjacencies, Q size 64... Time out while expecting data from node 30.82 Node 30.82 did not respond Results from 30.82, 0 circuits, 0 adjacencies, Q size 63... Results from 30.27, 1 circuits, 1 adjacencies, Q size 62... Time out while expecting data from node 30.116 Node 30.116 did not respond Results from 30.116, 0 circuits, 0 adjacencies, Q size 61... Results from 30.163, 1 circuits, 1 adjacencies, Q size 60... Time out while expecting data from node 30.132 Node 30.132 did not respond Results from 30.132, 0 circuits, 0 adjacencies, Q size 59... Time out while expecting data from node 30.106 Node 30.106 did not respond Results from 30.106, 0 circuits, 0 adjacencies, Q size 58... Results from 30.15, 1 circuits, 1 adjacencies, Q size 57... Results from 30.4, 1 circuits, 1 adjacencies, Q size 56... Results from 30.165, 1 circuits, 1 adjacencies, Q size 55... Results from 30.18, 1 circuits, 1 adjacencies, Q size 54... Results from 30.261, 1 circuits, 1 adjacencies, Q size 53... Results from 30.36, 1 circuits, 1 adjacencies, Q size 52... Results from 30.19, 1 circuits, 1 adjacencies, Q size 51... Results from 30.351, 1 circuits, 1 adjacencies, Q size 50... Time out while expecting data from node 30.87 Node 30.87 did not respond Results from 30.87, 0 circuits, 0 adjacencies, Q size 49... Results from 30.11, 1 circuits, 1 adjacencies, Q size 48... Time out while expecting data from node 30.91 Node 30.91 did not respond Results from 30.91, 0 circuits, 0 adjacencies, Q size 47... Time out while expecting data from node 30.140 Node 30.140 did not respond Results from 30.140, 0 circuits, 0 adjacencies, Q size 46... Results from 30.173, 1 circuits, 1 adjacencies, Q size 45... Time out while expecting data from node 30.56 Node 30.56 did not respond Results from 30.56, 0 circuits, 0 adjacencies, Q size 44... Results from 30.16, 1 circuits, 1 adjacencies, Q size 43... Time out while expecting data from node 30.68 Node 30.68 did not respond Results from 30.68, 0 circuits, 0 adjacencies, Q size 42... Time out while expecting data from node 30.65 Node 30.65 did not respond Results from 30.65, 0 circuits, 0 adjacencies, Q size 41... Time out while expecting data from node 30.182 Node 30.182 did not respond Results from 30.182, 0 circuits, 0 adjacencies, Q size 40... Time out while expecting data from node 30.242 Time out while expecting data from node 30.242 Node 30.242 did not respond Results from 30.242, 0 circuits, 0 adjacencies, Q size 39... Time out while expecting data from node 30.122 Node 30.122 did not respond Results from 30.122, 0 circuits, 0 adjacencies, Q size 38... Time out while expecting data from node 30.86 Node 30.86 did not respond Results from 30.86, 0 circuits, 0 adjacencies, Q size 37... Time out while expecting data from node 30.156 Node 30.156 did not respond Results from 30.156, 0 circuits, 0 adjacencies, Q size 36... Time out while expecting data from node 30.119 Time out while expecting data from node 30.119 Node 30.119 did not respond Results from 30.119, 0 circuits, 0 adjacencies, Q size 35... Time out while expecting data from node 30.344 Node 30.344 did not respond Results from 30.344, 0 circuits, 0 adjacencies, Q size 34... Time out while expecting data from node 30.104 Time out while expecting data from node 30.104 Node 30.104 did not respond Results from 30.104, 0 circuits, 0 adjacencies, Q size 33... Time out while expecting data from node 30.63 Node 30.63 did not respond Results from 30.63, 0 circuits, 0 adjacencies, Q size 32... Time out while expecting data from node 30.237 Node 30.237 did not respond Results from 30.237, 0 circuits, 0 adjacencies, Q size 31... Time out while expecting data from node 30.374 Node TLVHAB did not respond Results from 30.374, 0 circuits, 0 adjacencies, Q size 30... Time out while expecting data from node 30.133 Node 30.133 did not respond Results from 30.133, 0 circuits, 0 adjacencies, Q size 29... Results from 30.1023, 1 circuits, 1 adjacencies, Q size 28... Time out while expecting data from node 30.210 Node 30.210 did not respond Results from 30.210, 0 circuits, 0 adjacencies, Q size 27... Time out while expecting data from node 30.96 Node 30.96 did not respond Results from 30.96, 0 circuits, 0 adjacencies, Q size 26... Time out while expecting data from node 30.191 Node 30.191 did not respond Results from 30.191, 0 circuits, 0 adjacencies, Q size 25... Time out while expecting data from node 30.368 Node 30.368 did not respond Results from 30.368, 0 circuits, 0 adjacencies, Q size 24... Time out while expecting data from node 30.355 Node 30.355 did not respond Results from 30.355, 0 circuits, 0 adjacencies, Q size 23... Time out while expecting data from node 30.187 Node 30.187 did not respond Results from 30.187, 0 circuits, 0 adjacencies, Q size 22... Time out while expecting data from node 30.244 Node 30.244 did not respond Results from 30.244, 0 circuits, 0 adjacencies, Q size 21... Time out while expecting data from node 30.203 Node 30.203 did not respond Results from 30.203, 0 circuits, 0 adjacencies, Q size 20... Time out while expecting data from node 30.67 Node 30.67 did not respond Results from 30.67, 0 circuits, 0 adjacencies, Q size 19... Time out while expecting data from node 30.209 Node 30.209 did not respond Results from 30.209, 0 circuits, 0 adjacencies, Q size 18... Time out while expecting data from node 30.180 Node 30.180 did not respond Results from 30.180, 0 circuits, 0 adjacencies, Q size 17... Time out while expecting data from node 30.181 Node 30.181 did not respond Results from 30.181, 0 circuits, 0 adjacencies, Q size 16... Time out while expecting data from node 30.108 Node 30.108 did not respond Results from 30.108, 0 circuits, 0 adjacencies, Q size 15... Results from 30.30, 1 circuits, 1 adjacencies, Q size 14... Time out while expecting data from node 30.343 Time out while expecting data from node 30.343 Node 30.343 did not respond Results from 30.343, 0 circuits, 0 adjacencies, Q size 13... Time out while expecting data from node 30.142 Node 30.142 did not respond Results from 30.142, 0 circuits, 0 adjacencies, Q size 12... Results from 30.17, 1 circuits, 1 adjacencies, Q size 11... Time out while expecting data from node 30.183 Node 30.183 did not respond Results from 30.183, 0 circuits, 0 adjacencies, Q size 10... Time out while expecting data from node 30.92 Node 30.92 did not respond Results from 30.92, 0 circuits, 0 adjacencies, Q size 9... Time out while expecting data from node 30.79 Time out while expecting data from node 30.79 Node 30.79 did not respond Results from 30.79, 0 circuits, 0 adjacencies, Q size 8... Time out while expecting data from node 30.114 Node 30.114 did not respond Results from 30.114, 0 circuits, 0 adjacencies, Q size 7... Time out while expecting data from node 30.123 Node 30.123 did not respond Results from 30.123, 0 circuits, 0 adjacencies, Q size 6... Results from 30.352, 1 circuits, 1 adjacencies, Q size 5... Time out while expecting data from node 30.88 Node 30.88 did not respond Results from 30.88, 0 circuits, 0 adjacencies, Q size 4... Time out while expecting data from node 30.358 Node 30.358 did not respond Results from 30.358, 0 circuits, 0 adjacencies, Q size 3... Results from 30.324, 1 circuits, 1 adjacencies, Q size 2... Results from 30.325, 1 circuits, 1 adjacencies, Q size 1... Time out while expecting data from node 30.234 Node 30.234 did not respond Results from 30.234, 0 circuits, 0 adjacencies, Q size 0... Kill process error DECnet Phase IV Autoconfiguration data collection completed. DECnet Phase IV Autoconfiguration starting data formatting ... %SYSTEM-F-FLTDIV_F, arithmetic fault, floating divide by zero at PC=00001F71, PS L=03C00000 %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC MCC_AC_WAN4_MAP load_position_data 3969 000005D5 00001F71 MCC_AC_WAN4_MAP main 2997 0000030B 00000553 Error: An error has occurred. Warning: DECnet Phase IV Autoconfiguration data files may be corrupt. DECnet Phase IV Autoconfiguration exiting under error conditions. o Press RETURN to exit:
3456.3	Deferred	TOOK::MINTZ	Erik Mintz	`Wed Jan 06 1993 19:25`	4
	I just noticed that this QAR has been marked deferred. If it is a significant problem, please re-enter the QAR in the 1.3 QAR database (see note 7)
3456.5	Divide by Zero in T1.3.1	NEWPRT::SCHOOLER_CH	Cheap? thrill...Jump a horse	`Fri Feb 19 1993 00:34`	6
	I am getting the divide by zero error in the Phase IV autoconfigur of MCC V T1.3.1. Is there any workaround? I can't seem to find the QAR (3313) in the 1.2 or 1.3 data base on MUSEUM. Any help is most appreciated. Regards, Chip
3456.6	See 3456.3	TOOK::MINTZ	Erik Mintz	`Fri Feb 19 1993 11:15`	7
	QAR 3313 is in a V1.2 database which was used only by developers. As noted in an earlier reply, the QAR has been marked deferred. I don't know if there has been any progress. You could contact Anne (TOOK::) Pelagatti for more information. She is the manager for the group now responsible for autoconfiguration. -- Erik
3456.7		DELNI::JCH486::huang	JoAnn Huang	`Tue Mar 23 1993 14:45`	14
	Re. 3456.0 The floating divide by zero error that you got is caused by an invalid node address "0.1". Although I don't know how it gets there, however we have a fix for this problem. Please give it a try and let us know how it goes ... Copy the following image file to replace SYS$LIBRARY:MCC_AC_WAN4_MAPPER.EXE: TOOK::USER$771:[HUANG.TEXT]MCC_AC_WAN4_MAPPER.EXE Regards, JoAnn
3456.8		TOOK::JCH486::huang	JoAnn Huang	`Fri Mar 26 1993 16:59`	10
	Hi all: Re. -1 If it is for the customer, please contact Dave Hoag (TOOK::HOAG) for more information about using the patch formally - usually, patches are handled through the CSC. Sorry about the confusion. JoAnn
3456.9	Status in V1.3	USWRSL::LIOU_PE		`Fri Mar 26 1993 20:58`	11
	Thank you for the patch; however, can someone please verify if this patch is included in V1.3 or not. And, if the fix didn't make to the V1.3 SSB, will this MCC_AC_WAN4_MAPPER.EXE work with V1.3? Thanks. Peggy
3456.10	Patch still not work	USWRSL::LIOU_PE		`Thu Apr 08 1993 22:24`	22
	Hi, My customer tested the DECnet Phase IV autoconfiguration with the new MCC_AC_WAN4_MAPPER.EXE for MCC V1.2 today, and he is getting the following problem: . . (went thru several node info ...) . DECnet IV data collection completed . DECnet IV data formating . (and three VAX Debug windows came up ...with various messages. I don't have all the messages because my customer can't do a screen print from his MAC.) Please help.
3456.11		TOOK::JCH486::huang	JoAnn Huang	`Fri Apr 09 1993 16:47`	32
	Hi all: Re: 3456.7 ---------- A little typo: the subdirectory should be [HUANG.TEST] ^^^^ Re: 3456.9 ---------- >> Thank you for the patch; however, can someone please >> verify if this patch is included in V1.3 or not. This patch is NOT included in V1.3. Therefore, you have to contact Dave Hoag (TOOK::HOAG) for information about using the patch formally if it is for a customer. >> And, if the fix didn't make to the V1.3 SSB, will this >> MCC_AC_WAN4_MAPPER.EXE work with V1.3? The answer is yes. You have to replace the old one in sys$library with this new image. It is a share image. Re: 3456.10 ----------- I have to apologize for accidentally putting a debug version in the directory. The current image there shoud be ok to be used. Sorry about the confusion. Regards, JoAnn
3456.12	File protection??	KAOFS::BOIVIN	Moi, j'viens du nord!	`Tue May 18 1993 20:52`	17
	Good day, The file in -.1 seems to be protected... KAFSV6> dir TOOK::USER$771:[HUANG.TEST]MCC_AC_WAN4_MAPPER.EXE Directory TOOK::USER$771:[HUANG.TEST] MCC_AC_WAN4_MAPPER.EXE;11 no privilege for attempted operation Total of 1 file, 0 blocks. Could you please fix the protection.... Thanks, Ed
3456.13	Cannot Access Patch	ANGLIN::CLAYTON	Merlin Clayton DTN 445-7217	`Thu Jun 24 1993 16:31`	15
	I've encountered the same problem described previously in this note and my note entry 5256. However, I cannot find the file in the directory specified - as a matter of fact, I cannot find any files in this directory. Has the patch been moved, or is it not available for some reason? My MCC system is EMS V2.3 on a VS4000/90 in both cases. Is this patch intended for a Vx.3 MCC system? Thanks. Merlin
3456.14	new exe directory location	TOOK::FLETCHER	Robin G. Fletcher ..	`Tue Jul 06 1993 19:13`	2
	took::user$215:[fletcher.public]mcc_ac_wan4_mapper.exe
3456.15	Is this the same problem ?	HGTAI1::LKLEE		`Mon Sep 06 1993 13:47`	19
	Hi, I encountered "Division by zero in DNA4 Autopology" with MCC_bms v 1.2.3 on VS4000-60, openVMS v 5.5-2. It is similar to what described in 3456.0, but the error occured while runing image MCC_AC_MAP in stead of MCC_AC_WAN4_MAP at line 7034, rel PC 20AF, abs PC 22EF. Can anyone give me some help for solving this problem ? Is this the same problem as described in 3456.0 ? Is there any solution for that ? Thanks in advance + regards, LK Lee
3456.16	use v1.3	TOOK::CALLANDER		`Fri Sep 17 1993 17:40`	4
	upgrade to v1.3 is really the only help I think yo are going to be able to get. sorry