IBM Support

II13317: POTENTIAL SHELL & UTILITIES COMMAND PROBLEMS WHEN THE FILE SYSTEM CONTAINING /TMP FILLS UP

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • When the filesystem containing the temporary directory (i.e.
    /tmp or the directory pointed to by TMP, TMPDIR etc. ) is
    full, there may be unexpected results from Shell & Utilities
    commands, with no indication that the /tmp is full. These
    commands will fail because they create a temporary file in /tmp
    as a part of their processing.
    Known issues include (but not limited to) the following:
    - cron loops when ENOSPC x'85' is issued while attempting to
      create a temporary file in /tmp, also issues message EDC5133I.
    - Shell commands that use command substitution return no output
      or error message, for example:
      /u/user1: >echo $(uname -n)
      /u/user1: >
    - Shell commands that redirect output to any HFS that is full
      will return with no indication of failure but still fail to
      produce any output. In the example below, myfile1 is empty
      as it was located on an HFS that was full.A directory entry is
      created for the output of the redirection,even though no data
      is written to this new file.
      /u/user1: >ls -l > myfile1
      /u/user1: >cat myfile1
      /u/user1: >
    - When the more command reads stdin (such as from a pipe) no
      input is read and there is no error indication, for example:
      /u/user1: >ps -elf | more
      /u/user1: >
    .
    Usually errors that occur attempting to create a new temporary
    file, are detected and reported. However, failures to write
    user data to a temporary file may go undetected and result
    in situations similar to the ones described above.
    .
    We recommend monitoring the /tmp HFS and avoid letting it run
    out of space, for example:
    - Using the FSFULL mount parameter.
    - Periodically running the skulker shell script to remove files
      that are no longer needed.
    - APAR OW42542 may also be helpful as
      it implements writing messages to the logrec and console to
      indicate that the HFS is full.
    Please refer to the UNIX System Services Planning Manual
    section "The /tmp Directory" for more suggestions on
    managing the /tmp directory.
    -
    ADDITIONAL KEYWORDS:
    Out of Storage  Temporary File System  Exhausted
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II13317

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2002-05-23

  • Closed date

  • Last modified date

    2002-10-01

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 October 2002