View previous topic :: View next topic
|
Author |
Message |
Duncan Sharppe
New User
Joined: 13 Dec 2013 Posts: 20 Location: USA
|
|
|
|
Hello experts,
I'd like to find some documentation that gives the criteria for placing a load module in LPALIB or LINKLIB.
Over time I'd sort of learned a little about which lib to place a module that will be used system wide but I'd like to know the formal requirements and recommendations (of IBM and others too!)
I've checked principles of operation, authorized assembler servers and some others and gleaned some knowledge from them but I have yet to find a table or chapter that states when to do what with a load module aside from marking it as authorized. That is, it should be marked as RENT or must NOT be marked as RENT, etc. and other details.
All pointers and gurdance are Thanked In Advance.
friarDuncan |
|
Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013 Posts: 917 Location: The Universe
|
|
|
|
- Is the module reenterable?
- Is there a solid business reason for the module to be storage resident?
- Is the module stable?
- Is there a solid business reason for the module not to be charged against the user region?
- Is the module RMODE ANY?
If the first two bullets can be answered yes, it can be in the LPA.
Stability is important. Replacing (or adding) an LPA module amounts to an IPL. An LLA refresh is much less disruptive than an IPL!
Keeping the module outside a user region is not all that important any more, but it is a consideration.
It's much easier to justify placing an RMODE ANY module in LPA. There is much more virtual storage above the line than below the line!
These are the major issues I can think of; there are probably more. |
|
Back to top |
|
|
|