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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1009 Actions

    Problem Report Number 1009
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0524
    Raised 2001-07-05 08:00
    Updated 2003-03-13 08:00
    Published 2001-07-19 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 5.1.2
    Test Identification POSIX.cmd/pwd 4
    Problem Summary TSD4C.00242 The test may fail on systems where /tmp is a symbolic link
    Problem Text
    This testcase is verifying that 'pwd' writes the absolute pathname of the current directory
    and is failing on OS/390 V2R9 because the testsuite cannot detect that
    in fact the path returned IS the absolute pathname of the current diretory.
    This inability is due to the implementation specific HFS setup that we
    have implemented to support shared HFS in a sysplex.

    In OS/390 Release 9, we introduced the shared HFS in a sysplex feature.
    A sysplex is a group of systems coupled together which can share data across
    these systems. With shared HFS, all filesystems that are mounted by a
    system participating in a shared HFS are available to all the systems particpating
    in the sysplex.

    I will include below, some of the documentation from our UNIX SYSTEMS SERVICES
    PLANNING GUIDE (Document Number GA22-7800-01), which gives a background
    on how this is done, and why the absolute pathname for /tmp actually /SYSTEM/tmp.

    In short this inability is because /tmp is part of the "System Specific HFSs" and
    the system name -- in this setup "SYSTEM" (the system name of the system
    of the sysplex where the command was issued) is part of the absolute pathname
    of the /tmp directory. Depending on what system of the sysplex one is
    logged onto the symbolic link setup would point to the correct tmp dir
    For example if there were 2 systems in a sysplex called SY1 and SY2,
    a user logged on to SY1 issuing cd /tmp would go to /SY1/tmp and
    similarly a user logged on to SY2 issuing cd /tmp would go to /SY2/tmp

    Here are the results of issuing various commands from the shell of
    our branding system relative to the /tmp directory:

    $ ls -l /tmp
    lrwxrwxrwx 1 IBMUSER SYS1 12 Feb 22 15:41 /tmp -> $SYSNAME/tmp
    $ cd /tmp
    $ pwd
    /SYSTEM/tmp


    To the end user, the logical view of the HFS does not change for OS/390 UNIX
    V2R9. From their point of view, accessing files and directories in the system
    is ust the same. That is true for all end users, whether they are in
    a sysplex or not.

    Starting in OS/390 V2R9, some of the directories are actually symbolic links

    Here is a summary of the HFS data sets that are needed in a sysplex that
    has shared HFS:

    SYSPLEX ROOT:
    Characteristics: It contains directories and symbolic links that allow
    redirection of directories. Only one sysplex root HFS is allowed for
    all systems participating in shared HFS.
    Purpose: The sysplex root is used by the system to redirect addressing
    to other directories. It is very small and is mounted read/write.

    SYSTEM SPECIFIC:
    Characteristics: It contains data specific to each system, including the
    /dev, /tmp, /var, and /etc directories for one system. There is one
    system-specific HFS data set for each system participating in the shared
    HFS capability.
    Purpose: The system-specific HFS data set is used by the system to
    mount system specific data. It contains the necessary mount points for
    system-specific data and the symbolic links to access sysplex-wide data and
    should be mounted read/write.

    VERSION:
    Characteristics: It contains system code and binaries, including the
    /bin, /usr, /lib, /opt, and /samples directories. IBM delivers only
    one version root; you might define more as you add new system levels and
    new maintenance levels. (I.e., if you are running in a mixed-version
    plex)
    Purpose: The version HFS has the same purpose as the root HFS in the
    non-sysplex world. It should be mounted read-only.

    Test Output
    400|31 4 1 11:53:37|IC Start
    200|31 1 11:53:37|TP Start
    520|31 1 50331881 1 1|Assertion #4 (A): 'pwd' writes the absolute pathname of t
    520|31 1 50331881 1 2| <LC> he current directory
    520|31 1 50331881 1 11|Standard output isn't the same as file '/vsc/VSC5.1.2/te
    520|31 1 50331881 1 12| <LC> t_tmp_dir/31670a/pwd/DATA/4.1.exp'
    520|31 1 50331881 1 13|diff of "out.stdout" and "/vsc/VSC5.1.2/tet_tmp_dir/3167
    520|31 1 50331881 1 14| <LC> 0a/pwd/DATA/4.1.exp":
    520|31 1 50331881 1 15|*** out.stdout Wed May 16 11:53:37 2001
    520|31 1 50331881 1 16|--- /vsc/VSC5.1.2/tet_tmp_dir/31670a/pwd/DATA/4.1.exp We
    520|31 1 50331881 1 17| <LC> d May 16 11:53:37 2001
    520|31 1 50331881 1 18|***************
    520|31 1 50331881 1 19|*** 1 ****
    520|31 1 50331881 1 20|! /SYSTEM/tmp/foo83886205
    520|31 1 50331881 1 21|--- 1 ----
    520|31 1 50331881 1 22|! /tmp/foo83886205
    220|31 1 1 11:53:38|FAIL
    410|31 4 1 11:53:38|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is accepted as a fault in the test suite.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority