Format

      SHOW NOTICES  element-name  ,...

1  –  Parameters

1.1  –  element-name

    Specifies the element whose notices you are displaying.

2  –  Description

    The SHOW NOTICES command displays the notices at the element or
    elements you specify. CDO sends notices to elements when you:

    o  Change an element and the change affects other elements.
       For example, if you change the name of a field element in a
       database, the database element may need to be integrated.

    o  Change an element and the change affects the parent. For
       example, if you delete the name of a record element in a
       database, the database element needs to be integrated.

    o  Create a new version of an element. For example, if you create
       a new record element that appears in a program, the program
       needs to be recompiled.

    If you issue the SHOW NOTICES command for an element that does
    not have notices, CDO informs you that the element does not have
    notices.

    You can display new version notices by using the SHOW NOTICES
    command at any of the member's parents that have a CDD$NOTICE_
    ACTION property value of SUCCESS or SIGNAL.

    You can display notices that the CHANGE command generates by
    using the SHOW NOTICES command at any of the member's parents
    that have a CDD$NOTICE_ACTION property value of SIGNAL.

    CDO sends notices when you either change a member of a
    relationship with the CHANGE command or you define a new version
    of the member.

    The three types of notices that definitions receive and the
    meanings of these notices are:

    o  CDD$K_POSSIBLY_INVALID

       A definition used by this definition has changed. This change
       might affect this definition. This notice indicates the name
       of the definition that changed.

    o  CDD$K_INVALID

       A definition used by this definition changed or was removed
       from the repository. This definition is invalid. If a changed
       definition initiated the notice, the notice supplies the
       name of the definition. If a deleted definition initiated
       the notice, the notice does not supply a definition name.

    o  CDD$K_NEW_VERSION

       A new version of a definition used by this definition was
       created. The notice supplies the name of the definition that
       has the new version.

    o  CDD$K_CHILD_USAGE

       A relationship from one of the definitions used by this
       element to one of its children was changed. The notice
       indicates the owner of the changed relationship. You cannot
       generate this type of notice using CDO. Only programs using
       the Oracle CDD/Repository callable interface can cause this
       notice. You can, however, read this type of notice using CDO.

3  –  Examples

    1.CDO>  SHOW NOTICES EMPLOYEE_REC
         .
         .
         .
      CDO>  CLEAR NOTICES EMPLOYEE_REC

      In this example, the SHOW NOTICES command displays notices
      sent to the EMPLOYEE_REC record. You can clear any notices by
      issuing the CLEAR NOTICES command.

    2.CDO>  CHANGE FIELD FLD_A
      cont>   DATATYPE IS SIGNED LONGWORD.
      %CDO-I-DBMBR, database DISK1:[SMITH.DICT]MY_RDB_DB(1) may need to be
        integrated
      CDO>  SHOW NOTICES MY_RDB_DB
      DISK1:[SMITH.DICT]MY_RDB_DB(1) is possibly invalid, triggered by entity
      DISK1:[SMITH.DICT]FLD_A(1)
      CDO>

      In this example, CDO sends a notice that a database might
      require integration as a consequence of the CHANGE command.

      You can use the SHOW NOTICES command to display this notice at
      the MY_RDB_DB database definition.

    3.CDO>  DEFINE FIELD FLD_B
      cont> DATATYPE SIGNED LONGWORD.
      CDO>  SHOW NOTICES REC_B
      DISK1:[SMITH.DICT]RDB_REC_B(1) uses an entity which has new versions,
      triggered by CDD$DATA_ELEMENT DISK1:[SMITH.DICT]FLD_B(1)
      CDO>  SHOW NOTICES MY_RDB_DB
      DISK1:[SMITH.DICT]MY_RDB_DB(1) uses an entity which has new versions,
      triggered by CDD$DATA_ELEMENT DISK1:[SMITH.DICT]FLD_B(1)
      DISK1:[SMITH.DICT]MY_RDB_DB(1) is possibly invalid, triggered by
      CDD$DATA_ELEMENT DISK1:[SMITH.DICT]FLD_A(1)

      When you create a new version of the FLD_B field definition by
      using the DEFINE FIELD command, CDO sends new version notices
      to the parents of FLD_B. The following set of examples shows
      this sequence of events:

      1. The DEFINE FIELD command creates a new version of the FLD_B
         field definition.

      2. The first SHOW NOTICES command shows that FLD_B's immediate
         parent, REC_B record definition received the new version
         notice when CDO created the new version of FLD_B.

      3. The second SHOW NOTICES command shows two notices at the
         MY_RDB_DB CDD$DATABASE definition. The CHANGE command sends
         one notice on behalf of the FLD_A field definition from the
         previous example, and the DEFINE FIELD command sends a new
         version notice on behalf of the new version of the FLD_B
         field definition.

    4.CDO> CLEAR NOTICES MY_RDB_DB
      CDO>  SHOW NOTICES MY_RDB_DB
      %CDO-I-NONOTICES, DISK1:[SMITH.DICT]MY_RDB_DB(1) has no notices

      To clear the notices at MY_RDB_DB, use the CLEAR NOTICES
      command.

      To verify that you cleared the notices at MY_RDB_DB, use the
      SHOW NOTICES command. If you ask to see the notices at a
      definition without notices, CDO responds that there are no
      notices.