Library/Program for Initial Programs and Atrium menu items

[hbi]

Specifying a program for users inital program and Atrium menu items seems to arise i big problem regarding the Library part.

It's NOT possible to specify *LIBL.
With hardcodes libraries it is difficult setting up production / test environments.

Can the *LIBL been specified in another way ?

Brgds
Helge

[David]

Atrium does not allow for specifying *LIBL because the PUI session controller does not accept *LIBL. It will only accept a qualified program call to start a session.

This is for some technical reasons -- the system process that is currently used to start the application's job does not work with the library list, but requires a qualified program name to start the job.

We are looking at some alternatives for starting the jobs that would allow for library list processing, but this is still in the works.

Customers typically create separate development/test environments by installing on separate servers/LPARs that each have their own set of libraries and Atrium database.

In your case, if you are running development/production on the same server/LPAR, you can install multiple instances of Profound UI. Each would have its own Atrium database that can can point to different libraries.

Also, if starting the sessions through Genie using macros, the program calls can be run unqualified, allowing for library list processing.

[hbi]

Hi David.

Thank's for the clarification.
Hope you will manage getting PUI using *LIBL instead of qualified program references.

But this leads to we can't use Atrium.

I have succeeded in changing out initial program (same for all users) to handle both 5250 and PUI environment and our menu system too.

The benefit from this task is having all the setup equal in both environments and even having
the same menu system. In this way I have only 1 qualified program reference: the initial program. I can live with that *S*.

Brgds
Helge