If different environments use different sets of libraries, it doesn’t make much sense to have them all using the same job description with the same library lists.

A job description is essentially the only system facility that holds library lists except for the QUSRLIBL system value and for running jobs. A major purpose of a *JOBD is to deliver a library list. They’re small objects that are easy to maintain. Create more of them and use them.

Why look for a programming solution for something already provided by the system?

Tom

I could replace *LIBL with the libraries I want, and that does work, but I want the program to be able to reconise what the current library list is as in my enviroment the library list can be different for different sets of data. I.e. I want to be able to run the same program over different enviroments… E.g. send an email with data from a specific file which is the same file, but stored in different libraries, for different clients.

Cheers
G