What to Do if a JSM Based Example Does Not Work
Initial Checks you should always perform:
If you are running a 5250 green screen user interface
Trace files are generated in two IFS directories. You can access both of them from option 7. Work with Java Service Manager in the JSM main menu. For a default installation they are:
Initial Checks you should always perform:
- You are using the SET example on an iSeries (iSeries) platform.
- The JSM is started.
- The JSM is appropriately licensed to execute the example you are using.
- The XSL style sheets are installed correctly (see preceding section).
- The HTTP Property File was updated correctly (see preceding section).
- The JSM Direct table DC@W29 was updated correctly (see preceding section).
If you are running a 5250 green screen user interface
- Read the messages in the job log.
- Trace files (see section on obtaining trace files)
- Locate your execution job’s LWEB_JOB and read the messages in its job log.
- Locate the HTTP Server instance job used by your job and read the messages in its job log.
- Trace files (see section on obtaining trace files)
- VL examples would typically do a Remote Procedure Call to a function. This would start one of those jobs submitted by the listener (typically a TPnnnnnn job). Find it and read the messages in the job log.
- Trace files (see section on obtaining trace files)
- Read the messages in the job log.
- Trace files (see section on obtaining trace files)
Trace files are generated in two IFS directories. You can access both of them from option 7. Work with Java Service Manager in the JSM main menu. For a default installation they are:
- /jsm/instance/trace
- /jsm/instance/temp
- On an iSeries 5250 terminal or emulator, use the command GO JSM.
- Use Option 2. Clear Java Service Manager to clear any existing trace files and change Clear trace directory to *YES.