When LongReach is installed 2 user profiles are created.
LONGREACH
LONGADM
The LONGADM user profile belongs to the LONGREACH group.
All OS/400 objects are installed in the LONGREACH library and are owned by LONGREACH user profile and *PUBLIC is *CHANGE.
All IFS files are installed in the /longreach directory and are owned by LONGREACH user profile and *PUBLIC is *EXCLUDE.
When the LONGREACH/LONGREACH subsystem is started an auto-start job entry (LONGREACH/LONGREACH job description) is started.
The LONGREACH job description uses the LONGREACH/LONGREACH job queue and the LONGREACH/LONGREACH output queue with *SECLVL message logging.
The LONGREACH job description request data is RUNJSM INSTANCE(*DEFAULT) VERSION(*DEFAULT).
Sample LONGREACH subsystem jobs:
LONGREACH QSYS SBS .0 DEQW
JSMJOB01 LONGREACH BCI .0 JVM-com.lansa. TIMW
STRLONG LONGREACH ASJ .0 CMD-RUNJSM TIMW
===================================================================================================
Collecting information for problem resolution.
If the LONGREACH subsystem jobs do not start.
1. Check output queue LONGREACH/LONGREACH for spooled files.
WRKOUTQ OUTQ(LONGREACH/LONGREACH)
Use the CLROUTQ OUTQ(LONGREACH/LONGREACH) command to remove old or previous spooled files.
2. Check the /longreach/jsm/instance/trace directory for trace files.
Use the CLRJSM INSTANCE(*DEFAULT) to remove old or previous trace files. (Refer to LONGADM menu option 2).
If you clear the output queue and trace directory and start LONGREACH once, there will be enough information in the created spooled files and trace directory subdirectory/files to determine the cause of the error.
Note: Some common errors.
TCP/IP ports 6560,6561,6563/6564 are being used by another application.
===================================================================================================
When you log in as LONGADM an initial menu is displayed.
1. Start Java Service Manager
2. Clear Java Service Manager
3. Optimize Java Service Manager
4. Edit Manager Properties
5. Edit Service Properties
6. Change Default JSM Instance
7. Work with Java Service Manager
The each command prompts with the keyword INSTANCE(*DEFAULT).
The *DEFAULT special value instructs the command to use the value from the LONGREACH/JSMMGRDTA data area.
DSPDTAARA DTAARA(LONGREACH/JSMMGRDTA)
/longreach/jsm/instance
===================================================================================================