| Darryl,
Thank you very much for your answer.
You are right, I am using the V1.1 documentaion, ... since we are using
DECmcc V1.1 - my apologize: I should have clarified this in .0.
The fact we are using V1.1 is due to constraints we have to live with.
Anyway, I have copied, as you suggested, the V1.2 documentation and realized
that the development environment suggestions are totally different.
The next question then is: is it compatible with V1.1 software ?
Comming back to my original questions...
First, a few words about the reasons of these questions:
In the context I explained you above (DECmcc V1.1), I would like to
create a DECmcc multi-developper environment allowing different developpers
to work witout interference and I would like to know which MIR files I
have to/can duplicate (while improving the performance).
- Parag. 3.6 recommends to copy MCC_DICTIONARY.DAT, MCC_DEFINITION.DAT,
MCC_MIR_ATTRIBUTE.DAT, MCC_MIR_DIRECTORY.DAT from [SYSHLP.EXAMPLES.MCC].
Can we copy these files from MCC_COMMON since we already have
worked with DECmcc ?
Answer:
>As you mentioned, you can create a copy of the dictionary
>in MCC_COMMON--this will insure isolation but not give you any speed
>benefit.
I understand your answer: it relates to the 4 first files mentionned
in the next question... but if we restricts to these 4 files
(which, by the way, corresponds to what is explained during
the DECmcc training) what is the impacts ? Can we still use
DECmcc (during the training, to use DECmcc operationally,
the attendees have to use two different MCC_SYSTEM logical definitions
depending upon the activity to perform...) ? Among other things,
we have some error messages when tempting to use the iconic map
interface.
- Parag. 3.6 recommends to copy (for speeding up the development process)
- MCC_DICTIONARY.DAT
- MCC_DEFINITION.DAT
- MCC_MIR_ATTRIBUTE.DAT
- MCC_MIR_DIRECTORY.DAT
Parag. 3.7 recommends to copy (for ensuring further isolation)
- MCC_DICTIONARY.DAT
- MCC_DEFINITION.DAT
- MCC_META_DICTIONARY.DAT
- MCC_PTB_PARSER.??? (what is the file
extension ?)
- MCC_PTB_COMMAND.LOG (I cannot find
this file in V1.1 ennvironment)
- MCC_DISPATCH_TABLE.DAT
Parag. 3.5 recommends to move ALL dictionary files as they are dependent
on each other, i.e. the files:
- MCC_DICTIONARY.DAT
- MCC_DEFINITION.DAT
- MCC_MIR_ATTRIBUTE.DAT
- MCC_MIR_DIRECTORY.DAT
- MCC_META_DICTIONARY.DAT
- MCC_META_DEFINITION.DAT
What are the files that we must copy in the developper directory
structure so that i) the development process is speeded up,
ii) the developpers isolation is ensured and
iii) the MCC dictionary is consistent ?
What about the following files (created after installation) ?
> TPLAB> dir mcc_system:/sin=01-jan-1992
>
> Directory SYS$COMMON:[MCC]
>
> MCC_00.MCC_EXP_INST011_PMS;1 MCC_ALARMS_16-JAN-1992_ERROR.LOG;1
> MCC_ALARMS_17-JAN-1992_ERROR.LOG;1 MCC_ALARMS_22-JAN-1992_ERROR.LOG;1
> MCC_ALARMS_ATTRIBUTE_MIR.DAT;1 MCC_ALARMS_INSTANCE_MIR.DAT;1
> MCC_C074000400AA000001CAE9E4448EEEFB.MCC_EXPO_Q11_Q;1
> MCC_C074000400AA000001CAE9E4448EEEFB.MCC_EXP_ATTR011_P;1
> MCC_C074000400AA000001CAE9E4448EEEFB.MCC_EXP_ATTR011_PH;1
> MCC_C074000400AA000001CAE9E4448EEEFB.MCC_EXP_INST011_P;1
> MCC_C074000400AA000001CAE9E4448EEEFB.MCC_EXP_INST011_PH;1
>
> Total of 11 files.
> TPLAB>
Answer:
My apo's, I do not understand your answer in the context of a V1.1
installed software.
Taking into account the reasons of these questions I explained above,
I would be very gratefull if someone could provide me an answer with.
Maurice.
|
| John,
I conformed to the instructions given by phone:
1) I copied from sys$common:[syshlp.examples.mcc]
MCC_DEV_DICTIONARY.DAT as MCC_DICTIONARY.DAT
MCC_DEV_DEFINITION.DAT as MCC_DEFINITION.DAT
MCC_DEV_MIR_ATTRIBUTE.DAT as MCC_MIR_ATTRIBUTE.DAT
MCC_DEV_MIR_DIRECTORY.DAT as MCC_MIR_DIRECTORY.DAT
2) I also copied from MCC_COMMON:
MCC_PTB_PARSER.BPT (no .DAT file found)
MCC_DISPATCH_TABLE.DAT
3) I also copied from MCC_COMMON (after an ucessfull attempts to use
DECmcc Iconic map interface):
MCC_META_DEFINITION.DAT
MCC_META_DICTIONARY.DAT
4) No file MCC_COMMON:MCC_PTB_COMMAND.LOG
As a result, I cannot start DECmcc Iconic Map interface :
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000001E, PC
=00251238, PSL=03C00004
%SYSTEM-E-ACCVIO, access violation, reason mask=00, virtual
address=0000000A, PC
=0000000A, PSL=0000000F
What is wrong ?
TPLAB>
TPLAB>
TPLAB> sh log mcc_d_sys
"MCC_D_SYS" = "TPLAB$DISK:[COLLEYE.DECMCC.MCC_SYSTEM]" (LNM$PROCESS_TABLE)
TPLAB>
TPLAB>
TPLAB> sh log mcc_system
"MCC_SYSTEM" = "ADG$USER_21:[COLLEYE.DECMCC.MCC_SYSTEM]" (LNM$PROCESS_TABLE)
= "MCC_SPECIFIC"
= "MCC_COMMON"
1 "MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]" (LNM$SYSTEM_TABLE)
1 "MCC_COMMON" = "SYS$COMMON:[MCC]" (LNM$SYSTEM_TABLE)
"MCC_SYSTEM" = "MCC_SPECIFIC" (LNM$SYSTEM_TABLE)
= "MCC_COMMON"
1 "MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]" (LNM$SYSTEM_TABLE)
1 "MCC_COMMON" = "SYS$COMMON:[MCC]" (LNM$SYSTEM_TABLE)
TPLAB>
TPLAB>
TPLAB>
TPLAB> d mcc_d_sys
Directory ADG$USER_21:[COLLEYE.DECMCC.MCC_SYSTEM]
MCC_DEFINITION.DAT;1
81/81 10-JAN-1991 11:30:02.78 (RWED,RWED,RE,)
MCC_DICTIONARY.DAT;1
126/126 10-JAN-1991 11:30:01.92 (RWED,RWED,RE,)
MCC_DISPATCH_TABLE.DAT;1
450/450 27-DEC-1991 11:03:31.34 (RWED,RWED,RE,)
MCC_META_DEFINITION.DAT;1
4/6 14-NOV-1990 13:54:18.63 (RWED,RWED,RE,)
MCC_META_DICTIONARY.DAT;1
1/3 18-JUN-1990 16:26:09.38 (RWED,RWED,RE,)
MCC_MIR_ATTRIBUTE.DAT;1
81/81 10-JAN-1991 11:30:03.50 (RWED,RWED,RE,)
MCC_MIR_DIRECTORY.DAT;1
66/66 10-JAN-1991 11:30:04.23 (RWED,RWED,RE,)
MCC_PTB_PARSER.BPT;1
1211/1212 1-FEB-1991 15:33:05.90 (RWED,RWED,RE,)
Total of 8 files, 2020/2025 blocks.
TPLAB>
TPLAB>
TPLAB>
TPLAB>
TPLAB> sh sym mccf
MCCF == "@env$dir:START_DECMCC.COM F"
TPLAB>
TPLAB>
TPLAB>
TPLAB> type env$dir:START_DECMCC.COM
$!==============================================================================
$!
$! File is START_DECMCC.COM
$!
$! Start DECmcc product
$!
$!==============================================================================
$ mode = P1
$ set def mcc_d_wrk
$ if mode .eqs. "F"
$ then
$ define/user mcc_init mcc_d_com:MC_MCC_INIT.COM
$ define/user sys$input sys$command
$ manage/enterprise
$ else
$ manage/enterprise/interf=decw
$ endif
$ exit
TPLAB>
TPLAB>
TPLAB>
TPLAB> mccw
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000001E, PC
=00251238, PSL=03C00004
%SYSTEM-E-ACCVIO, access violation, reason mask=00, virtual address=0000000A, PC
=0000000A, PSL=0000000F
TPLAB>
TPLAB>
TPLAB>
|