[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 |
10.0. "PROBLEM - HFB - Long topic lines cause ACCVIO" by OFFHK::MCPHERSON (My guitar wants to kill your mama.) Wed Sep 20 1989 16:50
There seems to be a problem with the HFB in the developers toolkit:
If the text to the left of the "=" token for a topic is long enough and
causes the "=" token to appear on the next line (wrap), the HFB doesn't
find the keyword correctly (apparently the logic doesn't let it look to
the next line to find the "=" token). This causes the HFB lots of
confusion and ultimately makes its barf when it tries to do it's sort
at the end.
Attached is an example of a help file that caused the HFB to blow up:
/doug
This is the help file:
!
! TITLE: UAF_AM.HELP
<COMMON_TOPICS>
ENTITY MCC UAF_AM = E_UAF_AM
ENTITY MCC UAF_AM FUNCTIONS = E_UAF_AM_FUNC
! < Several topics deleted for brevity >
!
! This next really long line causes the "=" token to end up on the next line...
ENTITY UAFzzzzzzzzzzz FUNCTIONSzzzzzzzzzzzzzz SETsssssssssssssssssssssssssss
= E_UAF_FUNCT_SET
<KEY> = E_UAF_AM
The UAF_AM is a simple example of a DECmcc Access Module.
<KEY> = E_UAF_AM_FUNC
The MCC UAF_AM sub-entity represents the DECmcc UAF
Access Module component of the DECmcc management tool. It
responds to the SHOW and TEST self management directive.
! <Help text deleted...>
<KEY> = E_UAF_FUNCT_SET
The SET function sets one or more characteristics of the UAF entity. OKAY?
ex: The DEFAULT DIRECTORY or the DEFAULT DEVICE.
this is a log of what happens when you try to run the HFB with a real long
topic line
$
$ mcchfb override mcc_help.topics
DECmcc Help File Builder
Component Version: T1.0.0
Processing file USER1:[MCPHERSON.MCC_HELP]MCC$CONTROL_FM.HELP
Processing file USER1:[MCPHERSON.MCC_HELP]MCC$GENERAL_HELP.HELP
Processing file USER1:[MCPHERSON.MCC_HELP]MCC$KERNEL_AM.HELP
Processing file USER1:[MCPHERSON.MCC_HELP]MCC$SAMPLE_AM.HELP
Processing file USER1:[MCPHERSON.MCC_HELP]MCC$UAF_AM.HELP
Warning - The topic 2UAFEzUAFzFUNCTzSET : not found.
Sorting help topics.
Processing sorted topics.
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=010E0060, PC=0017E998, PSL=03C00004
Improperly handled condition, image exit forced.
Signal arguments Stack contents
Number = 00000005 0017D5E4
Name = 0000000C 00000000
00000001 2FFC0000
010E0060 7FEF480C
0017E998 7FEF47F4
03C00004 0017C038
00001A00
000026C8
0017A324
0017A270
Register dump
R0 = 00000000 R1 = 00000000 R2 = 00001A00 R3 = 000026C8
R4 = 0017A324 R5 = 0017A270 R6 = 00000000 R7 = 010E0008
R8 = 010E004A R9 = 010E00FA R10= 7FFED7D4 R11= 0000277C
AP = 7FEF436C FP = 7FEF432C SP = 7FEF43A8 PC = 0017E998
PSL= 03C00004
T.R | Title | User | Personal Name | Date | Lines |
---|
10.1 | INFO - QAR entered | GOSTE::CALLANDER | | Mon Sep 25 1989 12:12 | 16 |
|
The problem that you are having is that the topics name and the
keyword are on seperate lines. If you (for the short term) just
up your right margin to about 132 so the topic and keyword fit on
one line then your problem will go away.
Right now HFB requires that the topic and keyword be on a single
line (as defined in chapter 7 of the SRM). I am looking into a way
around this requirement, without requiring HFB to go through a major
rewrite.
There is an outstanding qar on this "problem" in the NACQAR system,
I will close this note when the qar is answered.
jill callander
|