Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1583 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1583.

Report 1583 Actions

    Problem Report Number 1583
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0140
    Raised 1995-05-22 08:00
    Updated 2003-03-13 08:00
    Published 1995-09-08 08:00
    Product Standard Internationalised System Calls and Libraries Extended (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.0.2
    Test Identification CAPI.os/dbm/dbm_store 7
    Specification System Interfaces and Libraries Issue 4 Version 2
    Location in Spec See Problem Text
    Problem Summary PIN4U.00006 The spec requires these functions to support key/content pairs of at least 1024 bytes but existing practice is 1023 bytes.
    Problem Text
    This issue affects the following tests

    Test Case Test Purposes
    dbm_store 7
    dbm_fetch 4
    dbm_firstkey 4
    dbm_nextkey 4

    The tests are testing the specification requirement that

    These database functions support key/content pairs
    of at least 1024 bytes.

    This is contrary to all existing implementations of the dbm*
    functions. To the best of my knowledge all of the current dbm_*
    sources are derived from the berkely distribution. In the
    berkely code the pair size is 1023 bytes. If the standard
    enforces the 1024 byte pair size then all existing dbm databases
    will be rendered unreadable.
    Test Output
    dbm_store 7

    520|1 1 6108 1 3|A call to int dbm_store(DBM *db, datum key, datum
    520|1 1 6108 1 4|content, int store_mode) shall support a maximum datum
    520|1 1 6108 1 5|content and the search key key pair size of at least
    520|1 1 6108 1 6|1024 bytes.
    520|1 1 6109 1 1|PREP: Create database
    520|1 1 6109 1 2|TEST: dbm_store supports entries of atleast 1024 bytes
    520|1 1 6109 1 3|ERROR: dbm_store failed, errno = 28(ENOSPC - No space left on d
    evice)
    220|1 1 1 18:14:32|FAIL



    dbm_fetch 4
    dbm_firstkey 4
    dbm_nextkey 4

    520|1 1 16555 1 1|PREP: Create database
    520|1 1 16555 1 2|PREP: Add records of max size 1024 to the database
    520|1 1 16555 1 4|ERROR: dbm_store failed, errno = 28(ENOSPC - No space...
    220|1 1 2 18:16:46|UNRESOLVED

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The code lines we checked agree with this observation.

    We agree with the submitter and propose the dbm_clearerr()
    specification be reworded to state

    These database functions support key/content pairs
    of at least 1023 btyes.

    rather than the current requirement of 1024 bytes.

    This should align the spec with with historical dbm
    implementations and allow branded implementations
    to read historical databases.

    A permanent interpretation is recommended.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    "As the responses of the Base working group (both active and passive)
    indicate agreement with the consultant, with one dissenting voice, a
    Permanent Interpretation should be granted in accordance with the
    procedures. However, this issue should be carefully reviewed when the next
    revision of the specification is developed."

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Permanent Interpretation (PIN)
    Review Conclusion
    A Permanent Interpretation is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority