IBM Support

II13965: MISSING RSU ASSIGN STATEMENTS IN ESO SERVICE ORDERS

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

  • ESO orders manufactured in October/November 2004 may be missing
    RSUyymm ++ASSIGN statements.  Subsequently, if you APPLY PTFs
    using the SOURCEID keyword with RSU* or a list of one or more
    RSUyymm values, some of the PTFs that you intended to install
    will not be installed.
    

Local fix

  • ESO orders should contain all of the available RSUyymm ASSIGN
    statements for the yymm service levels included in your order.
    For example, if your order includes service levels 0408 and
    0409, it should include all available RSU0408 and RSU0409
    ASSIGN statements.
    
    Prior to running the SMP/E APPLY command, you should review all
    of the ASSIGN statements provided in your order.  For each
    unique PUTyymm SOURCEID that you find, you should download and
    SMP/E RECEIVE the entire corresponding RSUyymm file from the
    ftp://service.boulder.ibm.com/s390/assigns/ web page.  This will
    ensure that you have all of the necessary RSU ASSIGNs.
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II13965

  • 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

    2004-11-04

  • Closed date

  • Last modified date

    2004-11-04

  • 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:
04 November 2004