Conference azur::mcc

2394.0. "DAP Dictionary disaster error" by FLAGYL::EIKELBOOM () Fri Feb 21 1992 15:54

When trying to enter information from my ms file into the dictionary I get the
following error Dictionary disaster - fwd ptr record not there
%MCC_F_FATAL, fatal DECmcc error.  If I run it again it runs to completion.
Below is some sample output



_DAP>   VALUE 1
DAP>  ! display
DAP>  SET DEFINITION CODE 9 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! predictable
DAP>  SET DEFINITION CODE 27 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! default_allowed
DAP>  SET DEFINITION CODE 3 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 0
DAP>  ! categories
DAP>  SET DEFINITION CODE 8 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE -
_DAP> 0
DAP>  PREVIOUS
DAP>  PREVIOUS
DAP>  CREATE ATTRIBUTE Physicaldevicenameoftheterminal CODE 190
DAP>  ! value_data_type
DAP>  SET DEFINITION CODE 1 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 3
DAP>  ! value_length
DAP>  SET DEFINITION CODE 2 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 65535
DAP>  ! presentation_name
DAP>  SET DEFINITION CODE 6 TYPE T COUNT 1 LENGTH 36 -
_DAP> VALUE "Physical device name of the terminal"
DAP>  ! access
DAP>  SET DEFINITION CODE 7 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 1
DAP>  ! display
DAP>  SET DEFINITION CODE 9 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! predictable
DAP>  SET DEFINITION CODE 27 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! default_allowed
DAP>  SET DEFINITION CODE 3 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 0
DAP>  ! categories
DAP>  SET DEFINITION CODE 8 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE -
_DAP> 0
DAP>  PREVIOUS
DAP>  PREVIOUS
DAP>  CREATE ATTRIBUTE UAFflags CODE 191
Dictionary disaster - fwd ptr record not there
%MCC-F-FATAL, fatal DECmcc error

****SOmetime later after adding to ms file another of the same problem


_DAP>   VALUE 1
DAP>  ! display
DAP>  SET DEFINITION CODE 9 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! predictable
DAP>  SET DEFINITION CODE 27 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! default_allowed
DAP>  SET DEFINITION CODE 3 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 0
DAP>  ! categories
DAP>  SET DEFINITION CODE 8 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE -
_DAP> 0
DAP>  PREVIOUS
DAP>  PREVIOUS
DAP>  CREATE ATTRIBUTE ProcessUIC CODE 193
DAP>  ! value_data_type
DAP>  SET DEFINITION CODE 1 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 3
DAP>  ! value_length
DAP>  SET DEFINITION CODE 2 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 65535
DAP>  ! presentation_name
DAP>  SET DEFINITION CODE 6 TYPE T COUNT 1 LENGTH 11 -
_DAP> VALUE "Process UIC"
DAP>  ! access
DAP>  SET DEFINITION CODE 7 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 1
DAP>  ! display
DAP>  SET DEFINITION CODE 9 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! predictable
DAP>  SET DEFINITION CODE 27 TYPE BU COUNT 1 LENGTH 1 -
_DAP>   VALUE 1
DAP>  ! default_allowed
DAP>  SET DEFINITION CODE 3 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE 0
DAP>  ! categories
DAP>  SET DEFINITION CODE 8 TYPE LU COUNT 1 LENGTH 4 -
_DAP>   VALUE -
_DAP> 0
DAP>  PREVIOUS
DAP>  PREVIOUS
DAP>  CREATE ATTRIBUTE Processusername CODE 194
Dictionary disaster - fwd ptr record not there
%MCC-F-FATAL, fatal DECmcc error

Which version of DECmcc and which O/S?

RE: .0

  Hmmmm....

  Were you using the @ command to load this information into the dictionary?
  The output you showed only comes from the @ command, not the LOAD, UPDATE,
  or AUGMENT commands.

  If so, you should *not* be using this command to load the dictionary.  At the
  present time only the LOAD, UPDATE or AUGMENT commands are supported for 
  loading info into the dictionary.

  Please start with a clean dictionary and only use these three commands.

  I don't have time to explain the reasons for this (incongruous) limitation
  at this time.  Call me if you need furthur explanation.


                                                                     - Jerry

    I can understand that from a customers viewpoint, Jerry.  Those are the
    only commands supported for populating the dictionary.  However, the
    "@" paradigm is that it re-directs standard input from a file instead
    of the current default (e.g., a terminal).  Since all commands entered
    were valid at the user interface, I would still argue that this is a
    bug (as opposed to a "limitation").  Stating that those commands can
    only exist in a command file would force re-implementation of DAP so
    that there are two sets of parse-tables, one for the command line, one
    for the MSL output.  All for the purpose of not fixing that bug.  Which
    might be a valid solution (if it was The Bug That Ate New York).
    
    On VMS, the "opposite" command would be:
    DAP> LOAD FROM SYS$INPUT:
    and type in the MSL output by hand.  I hope this works, right?
    
    -Matt.

RE: .3

  Your're right Matt - this is a bug.  The "@" command should eventually be
  fixed and made to work.  For now, however, please use LOAD, UPDATE and 
  AUGMENT for loading information into the dictionary rather than "@".

  I'm afraid that DAP has a number of problems that mandate that it only be 
  used in certain way.  A considerable amount of effort has already been put
  into improving this tool and more is committed in the future.

                                                                       - Jerry

Sorry I thought I had included this info

OS = VMS 5.4-3
MCC = V1.2 EFT

Also, for the record this used to work on the old version of MCC
This is an ms file used on previous versions of MCC but with much
more information it.  The earlier version had only 18 or 19 attribute
definitions - now is up around 100 all totaled.

thanks,
Cindy

PS: I'll use the update, load etc from now on

RE: .5

  > PS: I'll use the update, load etc from now on

  Thanks.  Fixing "@" is on the list...

                                              - Jerry