|
In this section: |
The server has a default search path for application and system components. You can supplement this search path by using one or more of the following APP commands:
Generally, these commands add applications to the beginning of the default search path. The exception is temporary components that are created in the current session. These temporary components are searched first, before the user-defined path.
You can issue the APP PATH command manually or set the application search path from the Reporting Server browser interface or the Data Migrator desktop interface. When you configure the application path from the Reporting Server browser interface or the Data Migrator desktop interface, the APP PATH command is stored in a selectable profile (global, group, or user). The global profile, edasprof, is the default.
|
How to: |
The APP PATH command sets the search path to a designated list of application names that refer to applications under the approot value. You can specify multiple application names to extend the search path.
APP PATH app1[/] [app2[/] ...]
[appn[/]]where:
Are application names. If you follow an application name with a slash (/), nested applications (the subtree of applications below the named application) will not be in the search path. If you do not follow the application name with a slash, the nested_app parameter in the edaserve.cfg file determines whether nested applications are searched for files referenced in a procedure, and to what level. If you need to specify more application names than can fit on one line, add the continuation character (-) at the end of the first line, and code more application names on the next line.
Note:
|
How to: |
The APP PREPENDPATH command enables you to temporarily add application names to the beginning of an existing APP PATH search path.
If you wish to use this command to alter the search path, you must code it manually in your application.
APP PREPENDPATH app1[/] [app2[/]] ... [appn[/]]
where:
Are application names. If you follow an application name with a slash (/), nested applications (the subtree of applications below the named application) will not be in the search path. If you do not follow the application name with a slash, the nested_app parameter determines whether nested applications are searched for files referenced in a procedure, and to what level. If you need to specify more application names than can fit on one line, add the continuation character (-) at the end of the first line, and code more application names on the next line.
|
How to: |
The APP APPENDPATH command enables you to temporarily add application names to the end of an existing APP PATH search path.
If you wish to use this command to alter the search path, you must code it manually in your application.
APP APPENDPATH app1[/] [app2[/]] ... [appn[/]]
where:
Are application names. If you follow an application name with a slash (/), nested applications (the subtree of applications below the named application) will not be in the search path. If you do not follow the application name with a slash, the nested_app parameter determines whether nested applications are searched for files referenced in a procedure, and to what level. If you need to specify more application names than can fit on one line, add the continuation character (-) at the end of the first line, and code more application names on the next line.
|
How to: |
|
Reference: |
The APP MAP command allows you to assign an application name to a non-approot application anywhere in the file system or to redirect an application. The application name becomes a virtual application under approot, which can be referenced in an APP PATH command and any other APP command that takes an application name as a parameter.
Note that mapping does not automatically add a directory to the path, it simply makes it available for addition to the search path.
To map a physical file location outside of approot, the syntax is:
APP MAP virtualname real_location
where:
Is an application name of up to 64 characters that can later be used in an APP PATH command.
Is a real full path name or DDNAME in the native style of the given operating system. On UNIX, Linux, i5 and z/OS HFS Deployment, the location may be a mixed case name, but the MAP virtualname itself is always handle insensitive when used (that is, EX mymap/mytest).
Note that if the real location contains spaces, it must be surrounded by double quotation marks.
Note: On IBM i, the APP MAP command can only be used to map an IFS directory and not a QSYS library.
To redirect an approot or non-approot application to a different name, the syntax is:
APP MAP app1 app2/dir1/dir2/../dirn
where:
Can be an existing physical, mapped or linked app. It can also be a new app.
Can be a physical, mapped or linked or non-existent app.
Are application directory names.
Note: Remapping of internal applications (for example, myhome, homeapps, _edaconf, _edahome) is not supported.
Basic example for Windows:
APP MAP test c:\temptest\
Note that if a path name contains spaces, the name must be surrounded by double quotation marks. For example:
APP MAP test "c:\temp test\"
To remap an application under approot:
APP MAP ibisamp retail
For the Unified Server (HFS and PDS deployments), the syntax for this type of mapping is
APP MAP appname file_extension=//dd:ddname;file_extension=//dd:ddname;...
where:
Is the name of the application used to reference this mapping in an APP PATH, APP APPENDPATH, or APP PREPENDPATH command.
Is one of the following valid server file extensions:
.mas .fex .acx .htm .sty .gif .psb
Is the ddname of the allocation you wish to map. The allocation can be performed using JCL code or a DYNAM command.
DYNAM ALLOC FILE MYMAS DA EDAARH.MASTER.DATA SHR REU APP MAP APP1 MAS=//DD:MYMAS; APP APPENDPATH APP1
By default, the server has an APP MAP command in the edasprof.prf file to map the application MVSAPP to the allocations FOCEXEC, MASTER, ACCESS, HTML, FOCSTYLE, GIF, FOCPSB. While allocations of these ddnames are not required for the APP MAP command to be valid, once the ddnames are allocated by JCL or DYNAM commands, they become available for use.
On platforms that support Universal Naming Convention (UNC), you must use the UNC to designate a network drive to access APP directories. The UNC must:
\\mynode\myshare\accnting "\\mynode\my share\accnting"
|
How to: |
The APP SET METALOCATION_SAME command identifies whether Master Files and their corresponding Access Files must be in the same location.
APP SET METALOCATION_SAME {ON|OFF}
where:
Specifies that Master Files and their corresponding Access Files must reside in the same application directory. ON is the default value.
Specifies that once the Master File for a request is located, the server will use the active search path to find the corresponding Access File.
|
How to: |
The APP ? METALOCATION_SAME command queries whether Master Files and their corresponding Access Files must be in the same location.
APP ? METALOCATION_SAME
If the result of this query command is ON, the server expects to find corresponding Master and Access Files in the same application directory. If the result is OFF, the server uses the active search path to find the Access File that corresponds to a given Master File.
|
How to: |
The APP SHOWPATH command lists all the currently active applications in the search path, including baseapp, which is always last. This list mirrors the list of applications displayed in the applications tree on the navigation pane.
APP SHOWPATH
The server is generally installed with two default applications: ibisamp (contains sample files), and baseapp (which can contain any files you create).
The APP SHOWPATH command generates the following output is:
ibisamp baseapp