IBM Support

II10683: BDT MODULE PLACEMENT DURING INSTALLATION

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

  • Customer has expressed concerns about the lack of documentation
    for BDT module placement which can be used during BDT product
    installation.
    

Local fix

  • Problem Conclusion: info apar taken with the following.
    The installation manual and the program directory are not very
    clear but BDT code is shipped in 3 libraries. Which are the
    following, SYS1.SBDTLIB and SYS1.SBDTLINK and SYS1.SBDTLPA
    for OS/390 REL2 and above. For releases prior to this the
    code should reside in libraries SYS1.BDTLIB, SYS1.LINKLIB, and
    SYS1.LPALIB. These should be described in the program directory
    associated with the release.
     ~
    For OS/390 REL2 and above:
    SYS1.SBDTLIB and SYS1.SBDTLINK should be in the LINKLIST
    concatenation (LNKLSTxx) while SYS1.SBDTLPA should be in the
    LPA concatenation (LPALSTxx).
    ~
    For releases below OS/390 REL2
    SYS1.BDTLIB and SYS1.LINKLIB should be in the LINKLIST
    concatenation (LNKLSTxx) while SYS1.LPALIB should be in the
    LPA concatenation (LPALSTxx).
    ~
    Also, be sure that the BDT libraries are apf authorized.
    Although the Installation manual for BDT does not state so
    directly, the OS/390 BULK DATA TRANSFER INSTALLATION MANUAL
    Document number  . . : SC28-1742-02 does.
    B.0  Appendix B.  Virtual Storage Required for the BDT Address
    space specifies the PLPA storage requirements for the BDT
    modules.
    In addition BDTSSINI should be installed into SYS1.SBDTLINK,
    when this library is added to your LINKLIST concatenation
    and you ipl with this new LINKLIST concatenation it will
    be as if you had moved BDTSSINI to SYS1.LINKLIB.
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II10683

  • 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

    1997-07-16

  • Closed date

  • Last modified date

    1999-02-15

  • 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:
15 February 1999