Endevor

 View Only
  • 1.  Best Practices for LLA Refresh

    Posted Jun 22, 2020 04:24 PM
    Hello Endevor Friends,

    How do you manage the refresh of run-time libraries for moves to production? We have been doing a refresh per program, library, and LPAR. Normally, this is no problem. It doesn't work real well for large implementations.


  • 2.  RE: Best Practices for LLA Refresh

    Posted Jun 22, 2020 05:20 PM
    Hi Diane, you can schedule a batch LLA UPDATE to refresh a specific group of loadlibs. It's easiest to let the Scheduler execute it at a certain time each day but if you need more frequent than that you can have the Endevor package skeleton; C1SB3000, kick off a job to the reader. Security access to run the command is usually the most difficult part.  

    Here's a sample REXX.  It assumes there is a CSVLLAxx member in SYS1.PARMLIB listing the specific loadlibs to be refreshed. The 'xx' / last 2-characters of the CSVLLAxx member replace the 'UPDATE=01' example below. Your MVS team will build this for you. If you need examples, let me know.  Hope this helps. 

    /* Rexx --------------------------------------------------------- */
    /* DESCRIPTION: Issues LLA Update using SYS1.PARMLIB(CSVLLA01) */
    /* -------------------------------------------------------------- */
    ADDRESS 'TSO' /* TSO ENVIRONMENT */
    X = OUTTRAP('VAR.')
    "OPSCMD C(F LLA,UPDATE=01) OUT WAIT(60)"
    X = OUTTRAP('OFF')
    CODE = 999
    DO I = 1 TO VAR.0
    SAY VAR.I
    IF POS('CSV210I',VAR.I) > 0,
    & POS('UPDATED',VAR.I) > 0 THEN CODE = 0
    END
    EXIT CODE



    ------------------------------
    Configuration Engineer Senior Advisor
    Anthem
    ------------------------------



  • 3.  RE: Best Practices for LLA Refresh

    Posted Jun 22, 2020 07:21 PM
    This assumes you can't take advantage of the LLACOPY feature in ENCOPTBL.  If Endevor is directly updating a linklisted / LPA managed loadlib, use this feature.

    ------------------------------
    Configuration Engineer Senior Advisor
    Anthem
    ------------------------------



  • 4.  RE: Best Practices for LLA Refresh

    Posted Jun 23, 2020 03:45 PM
    Thanks for the ideas Mr. Dave! I had done a search for LLACOPY and LLA Refresh in TechDocs and received no matches. I would like to know more about the LLACOPY option in ENCOPTBL. Does this work just for Endevor Output Libs or does it also work as part of Ship Job #2 ?


  • 5.  RE: Best Practices for LLA Refresh

    Posted Jun 23, 2020 07:11 PM
    To the best of my knowledge, the LLACOPY feature does not work with package ship. Recommend you get a batch job created / scheduled on the 'ship to' LPAR to perform the LLA update at regular intervals.

    ------------------------------
    Configuration Engineer Senior Advisor
    Anthem
    ------------------------------



  • 6.  RE: Best Practices for LLA Refresh

    Posted Jun 24, 2020 04:50 AM
    Hi Dana, If you have PDSMAN then it has an LLA refresh feature, any time a monitored library gets updated PDSMAN will do the LLA refresh automatically.​


  • 7.  RE: Best Practices for LLA Refresh

    Posted Jun 24, 2020 10:23 AM
    We switched to PDSMAN a couple years ago, no longer have to ask 'When is the next refresh'. Love automation.

    ------------------------------
    Operation Systems Eng
    Wells Fargo Bank N.A
    ------------------------------



  • 8.  RE: Best Practices for LLA Refresh

    Posted Jun 30, 2020 05:38 PM
    Edited by Mathew Goldstein Jun 30, 2020 05:45 PM
    Execute this under the alternate ID:
    //LLARFRSH EXEC PGM=ISF,PARM='++20,80'
    //ISFOUT DD SYSOUT=*
    //ISFIN DD DATA,DLM=##
    /ROUTE lpar1name,F LLA,REFRESH
    /ROUTE lpar2name,F LLA,REFRESH
    etc.
    ##-------------------------------------------

    The best solution may be to get the application load modules out of the link list if at all possible. Maybe use TSOLIB?