PM27084: OMPROUTE ISSUES MESSAGE EZZ8156I WHEN IT DOES NOT HAVE WRITE ACCESS TO ENVAR TMPDIR OR /TMP (IF TMPDIR IS NOT DEFINED)

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • OMPROUTE calls tmpnam(NULL) to produce a temporary file name in
    directory defined by the value of the TMPDIR environment
    variable, or '/tmp' if TMPDIR is not defined.  If OMROUTE does
    not have write access to this directory, tmpnam will be NULL.
    OMPROUTE then passes this name on the fopen which causes the
    open to fail, and OMPROUTE produces message EZZ8156I with errno
    129 and errnjor C00B04B3.
    .
    KEYWORDS: tmpnam access permission permissions
    .
    VERIFICAION STEPS:
    OMPROUTE issues the following message at startup:
    EZZ8156I OSPF is unable to translate MVS system symbols or
    process INCLUDE statements as a result of error ERRNO: 129
    EDC5129I No such file or directory. errno2: C00B04B3
    

Local fix

  • Use ls -ld to see how /tmp is defined.
    .
    Ensure OMPROUTE has write access to /tmp or the directory
    defined by the environment variable TMPDIR.  The chmod command
    can be used the change the permission bits on directories.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communication Server    *
    *                 for z/OS Version 1 Release(s) 10, 11, and    *
    *                 12 IP: OMPROUTE                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: OMPROUTE uses the LE tmpnam() routine   *
    *                      which requires access to the TMPDIR     *
    *                      directory (usually /tmp). If OMPROUTE   *
    *                      does not have access to TMPDIR, then    *
    *                      OMPROUTE may not read its configuration *
    *                      file correctly.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    OMPROUTE supports system symbolics and multiple include files
    in its configuration file. The implementation to support
    symbolics and multiple include files uses memory files and the
    tmpnam() LE function. The tmpnam() function is used to generate
    a random name for the memory file. However, the tmpnam() routine
    requires access to the TMPDIR (usually /tmp) in order to
    generate a random file name. As a result, OMPROUTE requires
    access to TMPDIR. If omproute is unable to access TMPDIR,
    OMPROUTE configuration processing will fail to properly handle
    include files. OMPROUTE may fail to start, or may start with
    an incomplete configuration.  OMPROUTE message EZZ8156I will
    be issued to indicate that symbolics and include files may not
    have been properly handled.
    
    OMPROUTE does not need a filename for a file physically located
    in TMPDIR. OMPROUTE merely needs a name for a memory file. The
    use of the tmpnam() routine is the only reason OMPROUTE
    configuration processing requires access to TMPDIR. If OMPROUTE
    generated a filename without using tmpnam(), then OMPROUTE
    configuration processing would not require access to TMPDIR.
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

Temporary fix

Comments

  • This APAR is being closed FIN (Fixed If Next) with concurrence
    from the submitting customer. This means that a fix to this
    APAR is expected to be delivered from IBM in a release (if any)
    to be available within the next 36 months.
    
    This problem will be tracked as Feature F152515 by
    Communications Server for z/OS Development.
    
    The solution for this APAR is included in
    CS for zOS Version 2 Release 1.
    

APAR Information

  • APAR number

    PM27084

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1B0

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-18

  • Closed date

    2010-12-20

  • Last modified date

    2013-09-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R1A0 PSN

       UP

  • R1B0 PSN

       UP

  • R1C0 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

z/OS family

Software version:

1B0

Operating system(s):

z/OS

Reference #:

PM27084

Modified date:

2013-09-16

Translate my page

Machine Translation

Content navigation