Vital information to include when reporting LANSA Integrator problems

Detailed Description:

The following information should always be included in the initial problem report for LANSA Integrator problems reported to your local LANSA distributor. In many cases, LANSA Support will be able to determine what the problem is from this information. Conversely, by not providing the following information up-front, time will be lost as LANSA Support will request some or all of this information to continue the investigation. This information should be sent with any LANSA Integrator problem report, irrespective of version or service being used.

Note: The points below contain instructions for iSeries. When reporting issues for LANSA Integrator on Windows, the equivalent Windows information should be gathered.

1. LANSA Integrator base version and EPC's used.  Ideally, sending the 'LANSA About' information is gives a good indication about the environment(s) in question.
2. If using LANSA Integrator 10.0 or later, the integrator-license.txt (or lansakey.txt, depending on the version used) so we can see what service(s) are licensed for.
   For versions prior to 10.0, a screen capture the LANSA License screen.
   
3. The list of files in the jar subdirectory. We can then check for any backup or duplicate copies of jar files as these can cause conflicts.
   
4. If the following error is generated 'NoSuchMethodError' check whether you are using Java 1.2 or above. This is a pre-requisite as per the LANSA integrator documentation.
   • Make sure that JDK 1.2.2 or greater is installed when using OS/400 V4R5M0. (see additional note below)
   • If not, install it from the original IBM CD.
   • Go LICPGM
   • Option 11 - Install new lic.pgm
   • Search entry : " 5769JV1 3 Java Developer Kit 1.2 " and put a "1" in front to install
   • Put the third OS/400 CD in the drive of your iSeries machine.
     Separate instructions exist for installing JDK on Windows.
   • Note: Errors may still exist when using JDK 1.2.2; LANSA recommends installing JDK 1.3 to avoid all known errors
     
5. If the following error is generated 'Unsupported content type' check that you are using the latest DCXS882X service program. Locate all DCXS882X service programs on the iSeries and list the creation date/time.
6. The most useful information is a set of clean trace files. Follow the steps below to produce a clean set of trace files.
    
   • Clear out output queue JSM
   • Clear all any existing trace files
   • Run with manager and client tracing on
     manager.properties
   • Set the following: trace.manager=*yes
   • Set the following: trace.client.address=*yes
   • service.properties
   • Set the following: trace.address.xxxx=*all xxxxx being the service name ie FTPCLIENT
   • Start JSM
   • Run the test once
   • End JSM
   • Send to LANSA Support:
     • All files in the trace subdirectory
     • manager.properties, service.properties in the system directory.
     • A capture of spool files in JSM output queue
       
7. iSeries CUME level and Group PTF levels.
   
   OS CUME level - Use DSPPTF command
   
   Group PTF level - Display data areas
   For example:
   Java Group PTF - DSPDTAARA DTAARA(QJAVA/SF99069)
   Data area . . . . . . . : SF99069 
   Library . . . . . . . : QJAVA 
   Type . . . . . . . . . : *CHAR 
   Length . . . . . . . . : 50 
   Text . . . . . . . . . : 
   Value 
   Offset *...+....1....+....2....+....3....+....4....+....5 
   0 'Group PTF#: SF99069-14 V5R1M0 January 27, 2003 ' 
   
   HTTP Server Group PTF - DSPDTAARA DTAARA(QHTTPSVR/SF99156)
   Data area . . . . . . . : SF99156 
   Library . . . . . . . : QHTTPSVR 
   Type . . . . . . . . . : *CHAR 
   Length . . . . . . . . : 50 
   Text . . . . . . . . . : 
   Value 
   Offset *...+....1....+....2....+....3....+....4....+....5 
   0 'Group PTF#: SF99156-11 V5R1M0 January 14, 2003 ' 
   
8. Refer to the Troubleshooting Chapter in the LANSA Integrator guide for information on:
   • the OS/400 version of Java
   • the version of the Java Service Manager (JSM)
   • locating error messages on iSeries
   • accessing the generated trace information
9. Related Service functions if applicable.