T.R | Title | User | Personal Name | Date | Lines |
---|
16.1 | INFO - only use first arg | GOSTE::CALLANDER | | Fri Sep 29 1989 09:56 | 16 |
|
Only the first argument of the enroll command is required. If you
have followed the naming conventions in the SRM then the second
argument should not be needed.
Example: if you named your executable MCC$TRM_PM and used this same
prefix in naming your software modules (init, probe and log) then
you do not need to supply the second enroll argument. In the long
run this second argument will not even be documented in the MCC
manuals. This is a carry over from before the SRM naming conventions
were established.
/jill
|
16.2 | | DSTEG2::HOSSFELD | I'm so confused! | Fri Sep 29 1989 11:03 | 14 |
| Is the second arg susposed to be the prefix of the init, log, and probe
Routines? So if I name these routines
acb$test_init()
abc$test_probe()
acb$test_log()
and the file name is mcc$test_alpha.exe.
And the file pointer logical is
Define mcc$file dua0:sys$test:mcc$test_alpha.exe
Do I use abc$test as the second arg or mcc$file or mcc$test?
One other thing I cam across used a logical mcc$actp__file to point to the file
and the two underscores (__) gave me a syntex error from enroll when I went
back to one it was ok!
|
16.3 | INFO - change to new conventions! | GOSTE::CALLANDER | | Tue Oct 03 1989 15:27 | 28 |
|
You should be using: mcc$test_alpha_init
mcc$test_alpha_probe
mcc$test_alpha_log
As documented in the help file and documentation for the T1.0.0
release of DECmcc the second argument for the enroll directive no
longer exists. The hold over was left in purely for downward
compatibility but this support will NOT be present in the next external
release of the system. Instead of trying to explain it I strongly
recommend that you change it.
Please refer to chaper 7, Enrollment and Extensibility, section
7.7 in the SRM T1.0.0 release. This describes how you must now name
your files and entry points.
In the SRM you will see that the dispatch table file is to be named:
"MCC$<component-name>_VECTOR.MAR"
and the entry points:
"MCC$<component-name>_INIT"
"MCC$<component-name>_PROBE"
"MCC$<component-name>_LOG"
jill
|