Conference vaxuum::online_bookbuilding

412.0. "LMF TAGS (?) cause ACCVIO " by ZENDIA::THOMPSON () Thu Mar 07 1991 17:41

    
    I also had the same problem that was discussed in note 312.  I
    took care of that problem, by using the latest DVC$BOOKRSHR.EXE file,
    as was suggested in note 312.2.  
    
    However, now I'm getting an ACCVIO error.  
    
    This error only occurs when I have LMF tags in my front matter.
    When they are commented out, the book builds fine.
    
    We are running:
    VMS version 5.4-1A
    Document Version 1.2B
    
    Here's where the error occurs for the file with the LMF tags:
    :
    :
    :
 T e x t    F o r m a t t i n g   C o n t e n t s ]...
%TEX-I-INFO, loading local online design, TEX$V2HANDBOOK V1.2B-1 16-May-90, CUP/ZK - on page [1]
%TEX-I-INFO, loading local design, CUP.ONLINE V1.2B-2 05-Oct-1990, CUP/ZK - on page [1]
%TEX-I-PAGESOUT, 3 pages written.
-TEX-I-OUTFILENAME, 'DISK_THOMPSON:[000000.INSPECT_MGR]GUIDE_PROFILE_CONTENTS.DVI_BOOKREADER'
[ I n d e x    G e n e r a t i o n ]...
%INX-I-ENDPASS_1, End of first pass over input file: 
   'DISK_THOMPSON:[000000.INSPECT_MGR]GUIDE_PROFILE.INX'
%INX-S-ENDPASS_2, End of second pass over input file.
%INX-S-CREATED, 'DISK_THOMPSON:[000000.INSPECT_MGR]GUIDE_PROFILE_INDEX.TEX;8' created
[ T e x t    F o r m a t t i n g   I n d e x ]...
%TEX-I-INFO, loading local online design, TEX$V2HANDBOOK V1.2B-1 16-May-90, CUP/ZK - on page [1]
%TEX-I-INFO, loading local design, CUP.ONLINE V1.2B-2 05-Oct-1990, CUP/ZK - on page [1]
%TEX-I-PAGESOUT, 10 pages written.
-TEX-I-OUTFILENAME, 'DISK_THOMPSON:[000000.INSPECT_MGR]GUIDE_PROFILE_INDEX.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=0801806B, PSL=00000002
  THOMPSON     job terminated at  7-MAR-1991 17:00:37.95
    
    Here is the front matter file:
    
<DOCTYPE>(CUP.8_5X11)
<FRONT_MATTER>(ABC_USER_FRONT_MATTER)

<TITLE_PAGE>

<LMF>(ABC_USER)
<LMF_PRODUCER>(DEC)
<LMF_PRODUCT>(ABC Facility for VMS)
<LMF_RELEASE_DATE>(April 1991)
<LMF_VERSION_NUMBER>(1.1)
<LMF_ALTNAME>()
<ENDLMF>

<TITLE>(<REFERENCE>(ABC_USER))
                      
<ORDER_NUMBER>(AA--PGC2A--TE)

<ABSTRACT>
The <REFERENCE>(ABC_USER) describes how to use the <REFERENCE>(ABC_FULL) 
software to monitor security compliance of nodes on a network.
<ENDABSTRACT>

<REVISION_INFO>(This is a new manual.) 



<REVISION_INFO>(Software Version:\<REFERENCE>(ABC_FULL) Version 1.1)
<REVISION_INFO>(Operating System Version:\VMS Version 5.2 or higher)
<COMPANY_INFO>(Digital Equipment Corporation\Maynard, Massachusetts)
<ENDTITLE_PAGE>
<INCLUDE>(COPYRIGHT.SDML)

<CONTENTS_FILE>
<INCLUDE>(ABC_PREFACE.SDML)
<ENDFRONT_MATTER>

    

    
    I've found a fix for this problem.  I modified the LMF tags, and now the
    book builds OK.
    
    Here's how I re-coded the tags.
    
    <LMF>(ABC_USER)
    <LMF_PRODUCER>(DEC)
    <LMF_PRODUCT>(ABC-V)
    <LMF_RELEASE_DATE>(0)
    <LMF_VERSION_NUMBER>(0)
    <LMF_ALTNAME>(BOOKBROWSER)
    <ENDLMF>
    
    It seems that it wouldn't work with a real release date, version
    number, or if an alternate name wasn't specified.
    Has anyone else seen these problems?
    
    

    Yes, putting 0 in the date field will work around the problem. However,
    there does seem to be a bug in the device converter (which we are
    looking into) -- it should not be 'improper coding' to put an actual
    date in the <lmf_release_date> tag.
    
    On V2.0, which has better error checking, the device converter did not
    ACCVIO, but it clearly took a strong dislike to the date (even when I
    coded it 'properly' in dd-mmm-yyyy form).
    
    This is the first we've heard of this problem: I think that all
    DEC-produced docs that go out on the OLD CD are coded with 0's in the
    date and version tags. Oddly enough, just yesterday I got a file from a
    customer field test site that had a date in the date tag, and it runs
    fine on V1.2B and V2.0. 
    
    Anyway, we will continue to look into the problem and report results
    here.
    
    Thanks,
    
    Mary