[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
2030.0. "ACCVIO whilst executing MCC script under DTM" by TOOK::FONSECA (I heard it through the Grapevine...) Mon Jan 06 1992 12:18
We are trying to get DTM scripts running to test TSAM, and I have
been seeing a strange ACCVIO when the script is run.
First let me explain that how we cause MCC to execute the commands
is a bit unusual. A temporary file is created which sets up our defualt
entities, and qualifiers, the last statement is a DO file_name.mcc. This
file contains all of the commands we wish to test. Then the mcc_init logical
is defined to point to this temporary file.
I had thought that we were defining the MCC_FCL_PM_LOG to 40, but did a
quick check and discovered that we are not. In any case that just
prevents the mcc version banner from being displayed.
We are only testing under VMS on MCC 1.2.4. Here is the portion of the
log file with the ACVIO (by the way the test appears to work, once the
ACCVIO has occured, MCC runs our test fine.) I am having problems getting
DTM to go from the first test to the next one in the collection, and
it is unclear whether that is due to this or some other problem. By
the way, I have tried to reproduce this problem by running all of the
scripts interactively, and in batch without involving DTM, and have
been unable to get the ACCVIO to occur.
$ @TEST_ROOT:[TEMPLATE]RUN_MCC.COM /OUTPUT = DTM$COL_DIR:DS300-LAT_CHAR_01.R
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=58200004, P
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
00496721 00496721
0048E0C4 0048E0C4
0048CBCD 0048CBCD
0048C8E9 0048C8E9
004886FF 004886FF
000AA795 000AA795
00083FC1 00083FC1
0007E9B8 0007E9B8
0008DFB1 0008DFB1
000AA89D 000AA89D
000F1B2C 000F1B2C
000B3483 000B3483
000B31E3 000B31E3
000B3139 000B3139
000B2B7B 000B2B7B
000B262C 000B262C
000B253B 000B253B
001C705C 001C705C
001C7D40 001C7D40
001C6871 001C6871
001C9861 001C9861
001C8C36 001C8C36
001CA7C1 001CA7C1
001C976E 001C976E
001C8C36 001C8C36
001CA7C1 001CA7C1
001C976E 001C976E
001C8C36 001C8C36
001CA7C1 001CA7C1
001C976E 001C976E
001C8C36 001C8C36
001C4AEB 001C4AEB
001C4450 001C4450
000C6E9A 000C6E9A
MCC_MAIN main 8258 00000208 00001E3C
000056F7 000056F7
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE 163 00000027 0000572B
000056D2 000056D2
DECmcc (T1.2.4)
DO TEST_ROOT:[SETUP]DS300.MCC
%MCC-S-VERIFYENTER, entering command procedure $USERS:[TSAM.TEST.][SETUP]DS300.
use default qualifier by password=system
%MCC-S-DEFQUAL, by password=system will be used as the default qualifier
use default entity terminal_server ts.tim
%MCC-S-DEFENT, using default terminal_server ts.tim
%MCC-S-VERIFYEXIT, exiting command procedure $USERS:[TSAM.TEST.][SETUP]DS300.MC
!-!
DO TEST_ROOT:[SCRIPTS]LAT_CHAR_01.MCC
%MCC-S-VERIFYENTER, entering command procedure $USERS:[TSAM.TEST.][SCRIPTS]LAT_
....things work fine after this (except for my DTM related problems...)
BTW TEST_ROOT:[TEMPLATE]RUN_MCC.COM looks like this:
$ set verify
$ manage := manage
$ manage/enterprise ! Start MCC & execute mcc_init
$ exit
Thanks,
Dave
T.R | Title | User | Personal Name | Date | Lines |
---|
2030.1 | My error | TOOK::FONSECA | I heard it through the Grapevine... | Tue Jan 07 1992 11:00 | 11 |
| OOOPS, massive stupidity on my part caused this problem...
An ACCVIO I knew about in our code was causing this.
Compounding the problem was the epilogue & the next test's prologue
go into mcc without deassigning the mcc_init logical which contained the
test script, so I was seeing the ACCVIO in places I had not expected to
see it, and so on and so on...
I resolve to have no more Mondays like that for the rest of the year!
-Dave
|