[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

3727.0. "MCC-E-INV_IN_ENTITY when creating domain" by BRSDVP::FOLENS () Fri Sep 11 1992 12:11

    After upgrade from BMS v1.1 to v1.2 I'm unable to create any domain.
    First when I started the iconic map I had an error with 'invalid entity
    structure'. After deleteing the mcc_resource.dat in the login directory
    this error disappeared. But when I try to open a new domain via the
    iconic map or via the command language interface I have the error:
    
    	'MCC-E-INV_IN_ENTITY'
    
    Access to DNS is ok and MCC_DNS_SETUP has been run to create the correct
    directories.
    Can somebody give me some hints to solve this?
    
    -Geert-
T.RTitleUserPersonal
Name
DateLines
3727.1MCC_IM_LOG traceBACHUS::FOLENSMon Sep 14 1992 10:26269
    
    I have taken a trace of the problem by defining MCC_IM_LOG to 7fe00000.
    Here it is:
 
$ define mcc_im_log 7fe00000
$ mana/enter
DECmcc (V1.2.0)
    
MCC> create domain .testmcc owner=field,directory=sys$sysroot:[sysmaint]
%MCC-I-LOG, MCC_IM_LOG = 7fe00000
MCC_CALL Function HANDLE = 23B754, 
state = FIRST
          verb = 12, in_entity = 1AC120, partition = 10
          time_spec = 0, in_p = 23B594, in_q = 0, out_entity = 1ABFE0
  IN_ENTITY:
        entity [0] wild = 
NOT_WILD
 class = 8
 id = 1 type = 5
        instance = 
�
.
.
.
.
a
.
H
x
.
D
�
.
.
.
.
.
.
t
e
s
t
m
c
c
.
.
        %X
AA
00
04
00
96
61
A0
48
78
8E
44
C2
95
00
0B
00
01
07
74
65
73
74
6D
63
63
00
00

  IN_P:

[ 
 0 ] 
( 

    
[ 
 12 ] 
    
66 
69 
65 
6c 
64 
 -- field

    
[ 
 13 ] 
    
73 
79 
73 
24 
73 
79 
73 
72 
6f 
6f 
74 
3a 
5b 
73 
79 
73 
6d 
61 
69 
6e 


    
74 
5d 
 -- sys$sysroot:[sysmaint]

    
)

  OUT_ENTITY:
        entity [0] wild = 
NOT_WILD
 class = 8
 id = 1 type = 5
        instance = 
�
.
.
.
.
a
.
H
x
.
D
�
.
.
.
.
.
.
t
e
s
t
m
c
c
.
.
        %X
AA
00
04
00
96
61
A0
48
78
8E
44
C2
95
00
0B
00
01
07
74
65
73
74
6D
63
63
00
00

MCC_CALL dispatch HANDLE = 23B754, module is MCC_DOMAIN_FM
    
    
RETURNED dispatch HANDLE = 23B754, 
state = FIRST, 
module is MCC_DOMAIN_FM, mm CVR: hex: 326D312, dec 52876050
    
RETURNED Function HANDLE = 23B754, 
state = FIRST
      time_stamp = 23B954, out_entity = 1ABFE0
      out_p = 23B854, out_q = 23BA54,  returned CVR: hex: 326D312, dec 52876050
  TIME_STAMP: 17-NOV-1858 00:00:00.00
  OUT_ENTITY:
        entity [0] wild = 
NOT_WILD
 class = 8
 id = 1 type = 5
        instance = 
�
.
.
.
.
a
.
H
x
.
D
�
.
.
.
.
.
.
t
e
s
t
m
c
c
.
.
        %X
AA
00
04
00
96
61
A0
48
78
8E
44
C2
95
00
0B
00
01
07
74
65
73
74
6D
63
63
00
00

  OUT_P:
    
 NULL 

%MCC-E-INV_IN_ENTITY, software error: invalid in_entity (input entity) parameter
MCC> exit
    
3727.2Problem solved - patched files in specificBACHUS::FOLENSMon Sep 14 1992 12:1014
    
    Finally found the cause of the problem. As this was an upgrade from
    v1.1 to v1.2, I was considering that some v1.1-files gave me trouble.
    The command 'test mcc 0 domain_fm' was giving the same error as with
    the 'create domain'-command. So I checked the domain_ FM- file residing
    in sys$library. I found there mcc_domain_fm.exe files in both the
    sys$specific and sys$common directory's. The files in the specific
    directory were created by the v1.1 patches for domain FM. After
    deleting this file and restarting BMS everything was ok.
    Be aware that also the MCC_ENET_AM.EXE file was found in both the
    specific and common directory's due to the Ethernet patch.
    
    	-Geert-
    
3727.3TOOK::MINTZLKG2-2 near pole X3, cube 6072, dtn 226-5033Mon Sep 14 1992 12:253
Thanks for posting the solution.