...
Starting with Profound UI Version 5, Fix Pack 0.6, it is possible to use Profound UI with Independent Auxilliary Storage Pools (IASPs). IASP support in Profound UI is based on the "initial ASP group" setting in the user's job description. When the user signs on, Profound UI will automatically run SETASPGRP ASPGRP(*CURUSR) so that a user will have access to his/her IASPs when doing things such as opening source members, referencing database files, or compiling display files.
...
Anonymous sessions (those that do not require a sign-on) will run under the IBM-supplied QTMHHTP1 user profile. IBM recommends that you do not change the IASP configuration for IBM-supplied user profiles, however. Therefore, when running an anonymous session, Profound UI will look for an environment variable named PUI_ANON_ASP, and will set the ASP group to that value instead of the one associated with the user profile.
You can set this environment variable in your HTTP server's httpd.conf file. To do this, edit the file located in /www/PROFOUNDUI/conf/httpd.conf, and add the following line (where MY_IASP is the name of the ASP group you wish to have set during anonymous sessions.)
...
You will need to restart the HTTP server after changing the httpd.conf file.
Installing Profound UI Installation to an IASP
The Green Screen installer has supported installation into an IASP since Profound UI Version 6 was first released. To specify an IASP find the 'Library IASP' field on the screen, and replace *SYSBAS with the name of the IASP you wish to install into. Starting with Profound UI Version 6 fix pack , Fix Pack 8.0, IASP installations are also supported in the Windows GUI Installer by clicking the 'Customize' button. Like the 5250 installer, you must change the 'Library IASP' field to reflect the IASP you wish to install into.
...
Moving a Profound UI Installation to an IASP
Currently, Profound UI's install program only knows how to install Profound UI into the system (*SYSBAS) ASP. However, once it is installed, you can move it to an IASP If you have an existing Profound UI instance that you need to move to an IASP, you can do so by following the instructions in this section. These instructions assume that Profound UI was installed into a library named PROFOUNDUI (which is the default, but can be changed by clicking the 'customize' button in our installation program.) If you used a different library name, please substitute that in the instructions below. Also, substitute the name of your IASP in place of MY_IASP.
...
This process is similar to the previous one, but it moves the IFS objects into the IASP instead of the programs. The following instructions assume that Profound UI is installed into the default /www/profoundui/ directory in the IFS. If yours are installed in a different location, please substitute that location in the instructions below. Also, substitute the name of your IASP in place of MY_IASP.
...