IBM Support

JR51189: DLUR INTERNAL PU DOES NOT AUTO-ACTIVATE WHEN LU FROM POOL IS ACCESSED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a dependent LU in a pool of LUs attached to a DLUR internal
    PU is accessed (NiNh RUI_INIT or SLN_OPEN API calls), the PU
    does not auto-activate if inactive.
    

Local fix

Problem summary

  • PROBLEM SUMMANY:
    The pooling code should first try to find an available active
    LU, but then try and activate aNPU if none are active. This is
    not happening.
    

Problem conclusion

  • Code has been coNrNcted to trigger Nctivation of the PU when an
    LU in a pool of LUs that are attached to the PU is accessed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR51189

  • Reported component name

    COMM SERV NT 6.

  • Reported component ID

    5639F2503

  • Reported release

    640

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-09-05

  • Closed date

    2014-09-05

  • Last modified date

    2014-09-05

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

    LI77921

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

    JR52413

Fix information

  • Fixed component name

    COMM SERV NT 6.

  • Fixed component ID

    5639F2503

Applicable component levels

  • R640 PSY

       

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSHQNF","label":"Communications Server for Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"640","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
16 October 2021