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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1631 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 1631.

Report 1631 Actions

    Problem Report Number 1631
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0188
    Raised 1998-03-04 08:00
    Updated 2003-03-13 08:00
    Published 1998-04-01 08:00
    Product Standard Sockets (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 5.0.2
    Test Identification CAPI.os/dbm/dbm_fetch 4
    Specification Networking Services Issue 4
    Location in Spec See Problem Text
    Problem Summary PIN4U.00054 This request claims this test should be testing for 1017 byte key content pairs rather than 1023 byte pairs.
    Problem Text
    Please submit a 14 review request for this Interpretation Request

    Given that the text of the specification for the dbm_*() routines was changed
    to specify the maximum key/content pair combination as 1023 (from 1024),
    recognizing that a maximum of 1024 was not supported by historical practice
    nor by the source code base from which these functions were derived;

    Was the new limit of 1023 really intended, given that the historical source
    base (BSD) only supports key/content pairs of up to 1017 bytes in size?

    All of the arguments leading up to PIN4U.00006 also apply here; except with a
    size of 1017. All of the historical source bases that we have investigated
    have this limitation.

    Did the Base WG really intend to break compatibility here?"


    Test Output

    TEST CASE: dbm_fetch

    TEST PURPOSE #4
    A call to datum dbm_fetch(DBM *db, datum key) shall
    support a maximum datum content and search key key
    pair size of at least 1023 bytes.
    TEST: for each key/content pair of 1023 bytes: store, fetch, and verify a record
    ERROR: adding record 1 - key size: 1, datum content size: 1022
    ERROR: dbm_store failed, errno = 28(ENOSPC - No space left on device)
    4 UNRESOLVED

    TEST CASE: dbm_store

    TEST PURPOSE #7
    A call to int dbm_store(DBM *db, datum key, datum
    content, int store_mode) shall support a maximum datum
    content and the search key key pair size of at least
    1023 bytes.
    TEST: Store, fetch, and verify records with key/content pairs that are 1023 byte
    s in size
    ERROR: Store failed for record 1: key size: 28, content size: 995
    ERROR: dbm_store failed, errno = 28(ENOSPC - No space left on device)
    7 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    A permanent interpretation is recommended.

    We believe this submitter is correct. Historical implementations
    we have seen used a maximum 1017 byte key/content pair (1023 bytes
    minus a 6 byte header).

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    This request should be reviewed by the Base Working Group.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    The Base working group agrees with the consultant that a PIN
    should be granted

    The group notes that TOG should check PIN4U.0006 for consistency.

    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