place of the OS/400 system class loader. This custom class loader does not detect the static programs.
To enable the system class loader to load the classes and detect the static programs, you must add the classpath parameter to the JVM settings. Do this in the Command line settings field of the application server settings (the same field as the
(:). There should not be any spaces in the value. It is similar to the Dependant classpath parameter in the application node settings except that it includes the deployed JAR files. Notice that the slashes in the qualified names are forward slashes (UNIX rather than Windows NT style) and that the separator is a colon rather than a
Figure 5-21 Application Server panel of the WebSphere console showing the classpath
It is possible that the parameter is too long and will be difficult to edit directly in the field of the dialog. Therefore, copy the parameter to an editor and modify it there. To copy the entire parameter, follow these steps:
1.Place the cursor in the field, and press the Home key to ensure that you are at the beginning of the field.
2.Press and hold the Shift key and then press the End key to select the entire field.
3.Press Ctrl+C to copy the field to the clip board and then press Ctrl+V to paste the parameter into a text editor (for example, Windows Notepad).
Since the line may be long, check how the editor handles word wrap. Some editors insert line feeds into long lines of text, which may be a problem. In our example, we turned off word wrap because the line is too long. To turn off word wrap in Notepad, select
