Conference hylndr::cdrom

435.0. "DEC C run-time library manual "missing" from VAXMAR97 ODL" by ALFAXP::BECHTOLD () Thu Apr 24 1997 17:51

Hello,

	I just wanted to make someone aware. We are also entering a Level 3 IPMT
Case against this problem so it get's QAR'd etc....

Dave Bechtold
DTN 343-1216
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
VERSION INFORMATION:

Product: BNU/Bookreader for OpenVMS VAX 6.2
Product/Component Version(s): Motif v1.2-4960311 - BNU V1.0-970203 -
                              Bookreader v1.2-4960312 - VAXMAR97 Documentation
                              CD set.

Operating System Version(s):  OpenVMS VAX 6.2


SOURCE: (do not enter - for STARS purposes only)


SYMPTOM:

The DEC C Run-Time Library Reference Manual for OpenVMS Systems is missing
from the VAXMAR97 CD set.

 OpenVMS VAX Online Documentation Library (Q1CY97)
  -Alphabetical Listing of Products
    -DEC C for OpenVMS VAX
     -Run-Time Library Reference Manual


When trying to access the book via BNU, Bookreader starts, but when trying
to access the book a popup dialog box is displayed with the message:

   error opening book
   title: unknown
   file: disk$vaxdocmar971:[progtool]D37AAAA7.BKB;
   reason: file not found



DIGITAL RESPONSE:
This problem has been reported to Engineering.


WORKAROUND:

If you have the Alpha Set of Documentation CD's (AXPMAR97) the book is not
missing and you can access the documentation with no problems.

ANALYSIS:

On the VAXMAR97 set of documentation CDs the file: D37AAAA7.BKB is clearly
missing.

On the AXPMAR97 set of documentation CDs the same file is present.

Example:

  $ DIR disk$vaxdocmar971:[progtool]D37AAAA7.BKB
  %DIRECT-W-NOFILES, no files found

  $ DIR disk$axpdocmar971:[progtool]D37AAAA7.BKB
  D37AAAA7.BKB;1       23-OCT-1995 12:22:02.00



\ Include the exact steps to reproduce the behavior:
\
\ 1) Start BNU on a OpenVMS system with Motif.
\ 2) Mount the OpenVMS VAX Documentation CD VAXMARDOC971.
\    per the BNU/Bookreader instructions.
\
\ 3) Select the following Bookreader Shelves and Books:
\
\ OpenVMS VAX Online Documentation Library (Q1CY97)
\  - Alphabetical Listing of Products
\   - DEC C for OpenVMS VAX
\    - Run-Time Library Reference Manual
\
\
\ Bookreader Popup dialog box is displayed with the error:
\
\   error opening book
\   title: unknown
\   file: disk$vaxdocmar971:[progtool]D37AAAA7.BKB;
\   reason: file not found
\
\
\ -----------------------------------------------------------------------       
                

    
    by "someone" do you mean the product group reponsible for BNU/ODL?
    
    If so, try forwarding it to DONVAN::PIAZZA.

Hello,

re: .1

"Someone" Being a person responsible for the contents of the BNU CD's.

Since posting this note I did receive mail from Anne Smith stating the following.

<Begin Mail>

 Hello Dave,


The missing book, D37AAAA7.BKB "DEC C Run-Time Library Reference Manual"
can be located in the "DEC C++ for OpenVMS" documentation.

Though the book should be in the [PROGTOOL] directory as part of the
"DEC C for OpenVMS" documentation set, the same book is also part of the
"DEC C++ for OpenVMS" documentation ([PROGTOOL.DECCXX]).

This will be corrected for the next Q2CY97 OVMS VAX ODL CD.

Thank you,
Anne Smith
<End of mail>

This helped allot....

Regards,
Dave Bechtold
DTN 343-1216

    
    As currently set up, each engineering group (or whomever submits the
    doc saveset) is responsible for the contents on the BNU CDs (unless 
    there is a major snafu -- which is unlikely).  A complete saveset of 
    the docs is submitted which is subsequently exploded onto the BNU discs
    -- whatever is in the saveset will end up on disc.  When problems such as 
    reported are received, its the original submittor (engineering group) that 
    needs to perform the fix and resubmit the doc set.
    
    In the past, the build tool would walk the documentation tree and 
    guarentee that there were neither missing items (referenced shelves or books 
    which were not on the disc) nor extra items (shelves or books on disc that 
    were not referenced somewhere).  However, I do not believe that the
    new, simplified, build model performs these functions any longer (if they 
    did  we shouldn't have seen this particular issue).  Also, the previous
    build tools checked file checksums and cross linked identical files so
    only one physical copy would occur on disc. Although this feature is 
    used mostly used on ConDIST, it did protect same file name/different
    content collisions on the old ConOLD discs.  
    
    My personal view is quality within the new process has gone backwards
    along with delivered functionality and usablity.  But that's just one
    person's humble opinion. (See 428.1-428.3 for example).