Progress/400
Product Guide


Accessing QSYS.LIB Files

To access objects in the QSYS.LIB file system, such as p-code, you embed your QSYS.LIB file system path in IFS path syntax. Although Progress/400 supports QSYS.LIB, it is recommended that you store your stream files in the root file system. Table 5–1 shows how to specify your QSYS.LIB file system path in a path within the IFS file system.

Table 5–1: QSYS.LIB and IFS Path Resolutions 
QSYS.LIB Path Resolution
IFS Path Resolution
*LIBL/REPORT(REPORT)
/QSYS.LIB/*LIBL.LIB/REPORT.FILE/REPORT.MBR
*CURLIB/MKTG(REPORT)
/QSYS.LIB/*CURLIB.LIB/MKTG.FILE/REPORT.MBR
DEMO/MKTG(REPORT)
/QSYS.LIB/DEMO.LIB/MKTG.FILE/REPORT.MBR

Progress/400 native clients search for p-code and r-code in the ROOT file system within IFS similarly to the Progress 4GL. However, if you store the p-code and r-code in the QSYS.LIB directory structure, you must fully qualify where the p-code or r-code resides when you use this directory structure in your Progress code. If you do not fully qualify the path, the native clients perform no search of any kind.

For example, if the abc procedure is in the ROOT file system (IFS), the native clients look for abc.r and then abc.p. However, if the procedure is in the QSYS.LIB file system, your RUN statement must be fully qualified; for example:

RUN /QSYS.LIB/*LIBL.LIB/P.FILE/ABC.MBR
RUN /QSYS.LIB/*LIBL.LIB/R.FILE/ABC.MBR 

For more information on how Progress/400 uses paths, see the "Executing Progress Code from the Native Clients" section in this chapter.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095