Page 1 of 1

What is the link pack area?

PostPosted: Tue Oct 07, 2008 2:09 pm
by thulasibabu
what is link pack area and their types..whether plpa,flpa is part of dasd.. please i need the brief about this

Re: What is the link pack area?

PostPosted: Wed Oct 08, 2008 5:32 am
by dick scherrer
Hello,

Notice that your question has been split from your original topic and placed in a new topic.

When you have a question, start a new topic for your new question. Also, you will usually get faster/better replies if you place your question in the right part of the forum.

Re: What is the link pack area?

PostPosted: Wed Oct 08, 2008 5:51 am
by dick scherrer

Re: What is the link pack area?

PostPosted: Wed Aug 11, 2010 2:52 pm
by sekhar.raj111
hi
any one tellme when the -305error occurs? what is null indicator?

Re: What is the link pack area?

PostPosted: Wed Aug 11, 2010 2:54 pm
by sekhar.raj111
hi
can any one send me casestudys in banking domaine

Re: What is the link pack area?

PostPosted: Wed Aug 11, 2010 4:46 pm
by NicC
What have either of these to do with LPA? Please post in the correct sections of the forum.

-305 - read the manual, null indicator - ditto but different manual.

Re: What is the link pack area?

PostPosted: Thu Aug 12, 2010 1:02 am
by steve-myers
To get back to topic.

The Link Pack Area (LPA) is a collection of programs and fixed tables that appear to be programs that are loaded into storage when the system is started, or to use our quaint term, IPLed. These programs and tables can be used by any program at any time.

There are several minor variations.

The "fixed" LPA (FLPA) has its pages arranged so the system will always have them in main storage. Pages assigned to the "regular" LPA can be paged out of main storage.

The "modified" LPA (MLPA) has its pages arranged so they can be altered. Pages in the regular LPA cannot be altered. This capability has always seemed stupid to me, but there are a few modules where this is a requirement.

Given that many z/OS systems are rarely IPLed these days often means that using LPA is not always a good idea, since the only way for an update to "take" is to IPL the system. For this reason user programs are rarely placed in the LPA; it's just for IBM provided programs.