Page Comparison

• Added Available since Profound.js 7.9.0.

• Only available for PJS on IBMi machines.

...

• Applicable to Profound.js running on IBM i machines, including in Genie.

By default (when the “Directory” parameter is omitted), a call to PJSCALL results in a search for objects over entries from the library list of the IBM i job in which PJSCALL runs.

The appendPJSPathlist configuration option changes the behavior of PJSCALL with respect to searching for modules, files, etc. With appentPJSPathList set to true, then entries in the PJS instance’s pathlist are searched before the search continues to the job’s library list entries. That is, if a module were to be called, and it existed in the PJS pathlist , then the module would be found and called, and no library list entries would be searched.

To be able to include the config.js pathlist setting when using PJSCallPJSCALL, add “appendPJSPathlist” appendPJSPathlist to the config.js and set it to true:

appendPJSPathlist: true

This will then append all the entries of the pathlist setting into the search list when using PJSCall via IBMi or Genie.

That means, a PJSCall that uses a directory to access a module, i.e.

PJSCALL module(mymodule) directory('moddir')

Willl not require the directory parameter if that module is inside a folder that’s part of the config.js pathlist:

For example, with the following config.js

pathlist: [ "dir1", "dir2", "dir3", "moddir" ]

IBMi/GenieThen this call,

PJSCALL module(mymodule)

would result in “mymodule” being searched in dir1, dir2, dir3, moddir, and then the job’s library list if the module were not found in the pathlist directories.

For more information on how to use config.js' pathlist setting, visit this link: pathlist