IBM Support

PI12030: USERS MAY PREFER TO REDIRECT TEMPORARY FILES DURING WAS MIGRATION TO SOMEWHERE OTHER THAN /TMP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Users often wish to use a directory other than /tmp for their
    temporary files.  In the case of temp files during migration,
    this was only possible by manually altering the bbomigrt2.sh
    script to add a line to export the TMPDIR environment variable.
    This had to be done a specific point in the middle of the
    migration jobs.
    

Local fix

  • After generating the migration Jobs and Data, follow the three
    step migration process starting with the BBOW_PRO job.
    
    - The BBOW_PRO job will create the new profile and in the
      process it will copy the bbomigrt2.sh script to the migration
      backup directory you specified using the zMMT tool.
      Example: /tmp/migrate
    
    - Save a backup copy of bbomigrt2.sh
    
    - Edit the bbomigrt2.sh script:
      Towards the top of the script, right after these lines:
            AWK=${AWK-/bin/awk}
            GREP=${GREP-/bin/grep}
            SED=${SED-/bin/sed}
            LS=${LS-ls}
    
      Add the following line:
            export TMPDIR=<myDefaultTempSpace>
    
      where <myDefaultTempSpace> is the temp directory you want the
      migration process to use.
    
      Note: Be sure that this temp location is writable by the
            userid running the migration.
    
      Continue running the rest of the migration steps.
           BBOW_PRE and BBOW_POS, ...
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The migration process, including the    *
    *                      application deployment, is using up     *
    *                      all the temp space.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    On z/OS java processes determine what temp space to use by
    first looking for the -Djava.io.tmpdir property.  If that is
    not provided then the location pointed to by the TMPDIR
    environment variable is used. If neither of the above are
    provide the /tmp directory is used.  The migration process on
    zOS does not allow the default process to be overridden.
    Customers must use what is set by default, which can result in
    the default temp space being filled up.
    APAR PI12030 is being closed FIN with concurrence from the
    submitting customer. This means that a fix to this APAR is
    expected to be delivered from IBM in a release which is being
    developed at the time that the APAR was closed. The latest
    release of the product to exit development at the time this
    APAR was closed was:
    WebSphere Application Server 8.5.5
    

Problem conclusion

Temporary fix

Comments

  • A tech note will also be written for this topic.
    

APAR Information

  • APAR number

    PI12030

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-18

  • Closed date

    2014-02-26

  • Last modified date

    2014-02-26

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022