When the repository is loaded for a given profile the tool connects with the host iSeries environment and establishes a job with a Library list that is representitive of the Environment the Object normally would be compiled and/or execute in its original form. This LIBL is a derived from taking the first the LIBL defined on the Profile, if none exists, then the LIBL defined on the Subject and if none exists on the Subject level, the LIBL on the Project is used.. For a successful repository load a LIBL must be defined on a least one of these levels for a given profile. Allowing for LIBL to be defined from the project down to the individual profile allows the user to set a global environmental LIBL for the project in general as well as allowing the User to get specific for some individual profiles or subjects that my differ from the Project as a whole.
Retrieved from "
What links here