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
------------------------------
Original Message:
Sent: 06-22-2020 04:23 PM
From: Dana Crawford
Subject: Best Practices for LLA Refresh
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.