Hi,

In our EDASPROF file we have an APP PATH command

APP PATH aaa bbb ccc ddd eee fff

Is there a way to issue a subsequent APP PATH command that allows fewer application folders?

I've tried issuing a command like

APP PATH bbb ddd fff

in a FEX - didn't work
in a User Profile - didn't work
in the Domain in which the FEX was executed - didn't work

Can you only prepend and append to the PATH as it is declared in the EDASPROF? Is there no way to expunge from the original PATH? What am I missing?

Thanks,

Dan

This message has been edited. Last edited by: Dan Pinault,

That is what we do here.

The path is set in a FEX, adn has always worked.

A new APP PATH commadn should override the existing one.

I assume there were n o errors or the like ?

Dan,

What did you use to check the app path?
I have tried your 'problem' with the following code:

? PATH
APP PATH BASEAPP SESSION IBISAMP
-RUN
? PATH

and it comes back with

BASEAPP  =  C:\ibi\apps\baseapp;
APPPATH  =  C:\ibi\apps\session;
C:\ibi\apps\session;
C:\ibi\apps\ibisamp;
C:\ibi\apps\baseapp;
C:\ibi\srv77\wfs\edatemp\foccache\ip000768010;
C:\ibi\apps\ibisamp;
C:\ibi\apps\baseapp;
C:\ibi\apps\session;
C:\ibi\apps\sap_bw;
BASEAPP  =  C:\ibi\apps\baseapp;
APPPATH  =  C:\ibi\apps\baseapp;
C:\ibi\apps\session;
C:\ibi\apps\ibisamp;

showing only those apps that I mentioned in my app path command. And I do not seem to remember it having been any other way ever. So, how did you check the current app path setting?

there is something like prepand path as I might remember well
and there are some more commands according to the temporary path settings

When I run this:

-TYPE Default App Path
? PATH
-RUN
APP PATH MASTERS PRODACX ADDRUPD
-RUN
-TYPE New App Path
? PATH
-EXIT

I get:

Default App Path
 BASEAPP  =  /opt/ibi/apps/baseapp:
 APPHOLD  =  /opt/ibi/713/ibi/srv71/wfs/edatemp/ts000285:
 APPPATH  =  /opt/ibi/apps/johngelona:
 /opt/ibi/apps/litigation:
 /opt/ibi/apps/baseapp:
 /opt/ibi/apps/yi619s:
 /opt/ibi/apps/outcomes:
 /opt/ibi/apps/resource:
 /opt/ibi/apps/gnr:
 /opt/ibi/apps/case_rvw_current:
 /opt/ibi/apps/masters:
 /opt/ibi/apps/prodacx:
.
.  Lot more folders 
.

 New App Path
 BASEAPP  =  /opt/ibi/apps/baseapp:
 APPHOLD  =  /opt/ibi/713/ibi/srv71/wfs/edatemp/ts000285:
 APPPATH  =  /opt/ibi/apps/masters:
 /opt/ibi/apps/prodacx:
 /opt/ibi/apps/addrupd:

I get the same thing in 7.1.3 or 7.6.11.

In my experience, BASEAPP is always part of the APP PATH. If it is not specifically listed, it seems to be the last folder in the app path. The search order seems to be APPHOLD, APP PATH folders in the order listed then BASEAPP. I have not come across (or searched for) documentation that supports this, but this is how it seems to work.

Thanks everyone! Looks like I needed the -RUN command. I also like the ? PATH method. It gives more detail than APP SHOWPATH.

Cheers!

Dan

Dan,
Is there a way to exclude baseapp from the PATH when we reissue the APP PATH command. In other words when I run APP PATH MYAPP i would like to get my syonyms only from MYAPP folder.

Thanks in advance.

This message has been edited. Last edited by: vaayu,

From my understanding, BASEAPP will always be there, perhaps its IBI's way to have an APP directory always available, even if there are none.

My suggestion is as a generic rule to not use BASEAPP at all, leave it empty. Partition all your code, masters, etc into there own aPP directories.

Thanks Waz.

Your other option is to create a user profile and then add APP PREPENDPATH MYAPP to it or add it in the program.

I thought the user profile would only limit them on the self service side but, not on the MRE. My challenge is to limit the MRE users with certain APP Folders when
1. They use Report Assistant to browse Masters
2. They use editor to TABLE FILE.

Any ideas would be greatly appreciated.

Thanks!

I think the best option is setting APP PATH according to the user/group or users, and using DBA settings in the masters

If you're passing the user ID from MRE to WF then it will execute a user profile (if one exists).

vaayu,

Here is what we came up with...
The basic premise on how our system is set up is that we limit access to masters based on the Application Directory they are in.

We use group-level profiles that are executed when a user logs on. In the profile we do four things
1) We build an APP PATH statement with three variables
a) &&PSRPATH - this contains application directories the user group needs based on the way they subscribe to our data
b) &&MYPATH - this contains the name of an application directory that is specific to the user group/domain name
c) &&FILTERPATH - this contains the names of application directories that have masters we want the users to have 'indirect' access to. By that I mean these datasources are accessed from HTML pages that act as the UI for some of our applications. We do not want users writing their own reports against these masters though.
2) We INCLUDE a 'filter' fex. This file declares filters against any masters a user may encounter whether it is through one of our applications or through one of the web tools (ReportAssist, GraphAssist, InfoAssist, etc.) If we don't include the application directory in the APP PATH statement we aren't able to declare a filter on the masters in that directory.
3) We set the value of &&IBI_IF_APPS by setting it to the physical path to an 'apps' fex. This file works similarly to the APP PATH statement but it has different syntax. We do this because the list of masters available in the web tools is not determined by APP PATH, it is determined by the value of &&IBI_IF_APPS. Here we build the list of application directories the user can access based on &&PSRPATH and &&MYPATH. &&IBI_IF_APPS is also used in the data upload utility. Therefore it is important that we disable write access to all the application directories except the one specified in &&MYPATH so the user doesn't save a file to a commonly used application directory.
4) We set the value of &&IBI_IF_FLDS by setting it to the physical path to a 'fields' fex. This file determines what fields within each master a user has access to. Most of the time we don't limit fields but when we need to this is where we do it.

To summarize, we use APP PATH because it is required in order for us to declare filters. We use &&IBI_IF_APPS because it is required to control master file access in the web tools.

Regards,

Dan

Dan,
This helps me significantly..

Thanks so much for your assistance. I Love this forum just as always.

-Pawan