View - Modules added to LPA

book

Article ID: 223114

calendar_today

Updated On:

Products

CA View

Issue/Introduction

While doing an upgrade, I ran into an issue with modules that I was unware were being loaded into LPA. 

The modules are listed below. 

They are loaded by issuing a SET PROG=xx command after an IPL. 

Is there any recommendation to do this?  Is there any significant benefit for doing this? 

In this situation, from what I am reading about the "LPA ADD", there could possibly be issues in trying to replace these without doing an IPL.

LPA ADD,MODNAME=(CAHCRLSE),DSNAME=LNKLST
LPA ADD,MODNAME=(SARDFMT ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSDIM ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARMSG  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARDTM  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARDBP  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARIFP  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSFP  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARXFP  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARCMP  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARDCMP ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARDBE  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARIAP  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARTPI  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARTPO  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARRPTUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSME  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSMFUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARCPR  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSECUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARDSTUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARPRTUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARPRFUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARUSRTB),DSNAME=LNKLST
LPA ADD,MODNAME=(SARPFKEY),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSMFT ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSPF  ),DSNAME=LNKLST
LPA ADD,MODNAME=(EC2OMS  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SAROLR  ),DSNAME=LNKLST
LPA ADD,MODNAME=(EC2TMRI2),DSNAME=LNKLST
LPA ADD,MODNAME=(SARUSTUX),DSNAME=LNKLST
LPA ADD,MODNAME=(EC2SUBT ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSRQUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSPFUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARSUBUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SAROMSUX),DSNAME=LNKLST
LPA ADD,MODNAME=(EC2CP037),DSNAME=LNKLST
LPA ADD,MODNAME=(SARBCH  ),DSNAME=LNKLST
LPA ADD,MODNAME=(SARATHUX),DSNAME=LNKLST
LPA ADD,MODNAME=(SARUSBUX),DSNAME=LNKLST
LPA ADD,MODNAME=(EC23270A),DSNAME=LNKLST
LPA ADD,MODNAME=(EC2D3270),DSNAME=LNKLST
LPA ADD,MODNAME=(EC2TMRT ),DSNAME=LNKLST

Environment

Release : 14.0

Component : CA View

Resolution

Having modules loaded from LPA is really not necessary. 
   
When programs are loaded, MVS searches the job pack area (programs already loaded in address space), JOBLIB/STEPLIB, LPA, and then LINKLIST. 

So, loading modules into LPA might save a small amount of search and load time, but will increase the amount of CSA storage used. 

If the modules are added to LPA, they can be deleted from LPA. 

An IPL is not needed, as the module address is not stored anywhere for later use. 

There may be an issue when linklist is refreshed with updated View/Deliver modules, as those updated modules would not be recognized. 

You may have to delete old LPA modules and re-add them from LINKLST. 

Overall, management-wise it is just easier to not load to LPA.