Endevor Users of Nearly Everywhere (EUNE)

 View Only
  • 1.  Ship to prod LPAR timming issue with binds

    Posted Nov 19, 2019 06:23 PM
    ​While performing a ship using the Broadcom ship process,  there are timing issues where the production bind uses the old information because it took longer for the ship to process the package.  Has anybody had ship timing issues in this area?

  • 2.  RE: Ship to prod LPAR timming issue with binds

    Broadcom Employee
    Posted Feb 13, 2020 08:04 AM
    Hello Joe.

    One method we use is to have the DB2 bind become a part of the package shipment process. Steps like a DB2 Bind, CICS newcopy, etc can be made to run in the remote shipment job - either before or after the copies are done. Let me know if you would like more information on the approach.

  • 3.  RE: Ship to prod LPAR timming issue with binds

    Posted Feb 14, 2020 08:23 AM
    I think package shipment is the greatest.  What we do is we ship to staging libraries on our production LPAR.  Then during our change window we have automated scheduled jobs that will apply the code to the real execution libraries.  The Bind statements and new copy statements are in a PDS/E dataset that is converted into a flat file and used as input into a batch job after all the copy process has completed.  We utilize DB2 versioning process to make sure the updated LOAD Modules do no get a -805 from the time between the copy process and the bind process executes.

    This process allows us to stage the code and validate the libraries during our leisure time, without our team having to get up early in the change window to perform the SHIPMENT process.


    Software Engineer
    Ky, USA