LANSA Integrator Resolved Issues

Page 1 of 2

• Incorrect version of help opened in Integrator Studio
  - LANSA Integrator EPC869
  When you open the LANSA Integrator guide from Integrator Studio using F1, the guide opened is not at the correct EPC level.
• Embedding certain images in PDFDocumentService gives error: stack trace: java.lang.UnsatisfiedLinkError: sun/awt/color/CMM
  - LANSA Integrator All Versions
  JSM fails when images of certain type - for instance high resolution - are used in PDFDocumentService
• Error 'Cannot create classpath' when starting JSM
  - LANSA Integrator All Versions
  Starting of JSM fails due to 'Cannot create classpath' error.
• Issue with PDFDocumentService importing a TIFF image
  - LANSA Integrator All Versions
  When using the PDFDocumentService to import a TIFF image, you may generate an error.
• Mixed case Commands cause issues in RDMLX (JSMX) BIF's
  - LANSA Integrator
  When the command SERVICE_LOAD is mixed case, ie Service_Load, the code logic does not detect the command, so the HTTP information is not made available to JSMDirect services.
• Can I enable support for Cp037 on Windows JSM
  - LANSA Integrator All Versions
  How to enable support for Cp037 to avoid UnsupportedEncodingException errors.
• Installation of 3rd party software affects LANSA Integrator licence on System i
  - LANSA Integrator
  Installing or upgrading 3rd party software on System i can cause the LANSA Integrator licence to stop working.
• MQBIF's cannot be used with the RDMLX specific JSM(X) BIFS
  - LANSA Integrator
  Currently, in order to use MQBIF's with RDMLX, it is required that you utilise the JSM BIFS not the JSMX BIFS.
• Stack trace: javax.mail.MessagingException: 501 Command "HELO" requires an argument
  - LANSA Integrator
  Stack trace: javax.mail.MessagingException: 501 Command "HELO" requires an argument.
• stack trace: java.lang.NumberFormatException: DataTypePacked: packed sign half byte is not hex 0x0D or 0x0F
  - LANSA Integrator
  Error: stack trace: java.lang.NumberFormatException: DataTypePacked: packed sign half byte is not hex 0x0D or 0x0F.
• Error: ZSRV_MSG0107: Premature end of script headers: File name is JSMDIRECT.PGM in Webserver joblog
  - LANSA Integrator
  Cannot read script output pipe.
• Version conflicts between JAVA-shipped and LANSA-shipped XALAN files
  - LANSA Integrator
  There is a potential conflict between the JDK-shipped XALAN related files and LANSA-shipped XALAN files (JSMXALAN.JAR).
• When putting XML in a LANSA field, XML syntax is lost when outputting XML
  - LANSA Integrator V11.3
  The XSL parser is converting the data from < and > to &lt and &gt.
• Getting 'Out of Memory' error when using Integrator Studio
  - LANSA Integrator V11.3
  Getting 'Out of Memory' error when using Integrator Studio.
• Writing to the IFS generates a 'Resource busy' error
  - LANSA Integrator
  "stack trace: java.io.FileNotFoundException: Resource busy" error received when writing to the IFS.

Page 2 of 2

• Connection failure when upgrading to SQL Server 2005 JDBC driver (SQLJDBC.jar)
  - LANSA Integrator
  Upgrading to SQL Server 2005 JDBC driver (SQLJDBC.jar) causes connection failure for exising SQLService.
• Failure when executing JSMDirect Service entry flagged as RDMLX
  - LANSA Integrator EPC 805
  EPC805 for LANSA Integrator on iSeries introduces a means of flagging a JSMDirect service entry as using RDMLX.
• Needing to receive LIST longer than 256 in a RDML function
  - LANSA Integrator
  Passing or receiving LANSA List which is longer than 256 in length via a JSM COMMAND.
• PDFSpoolFileService Error: stack trace: java.lang.NoClassDefFoundError: com/ibm/as400/access/AS400
  - LANSA Integrator
  Cannot execute PDFSpoolFileService.
• Error starting JSM : JSM instance has failed check process
  - LANSA Integrator
  JSM fails to start: JSM Instance has failed check process.
• Does LANSA Integrator support COUNT , AVG , MAX and etc. on SELECT statement?
  - LANSA Integrator
  Unable to use the COUNT keyword with SELECT.
• JSMDIRECT Transaction did not complete
  - LANSA Integrator
  Troubleshooting the "JSMDIRECT Transaction did not complete" error.
• MQSeries: Message and Correlation ID does not contain valid EBCDIC characters
  - LANSA Integrator
  Can we send the Message ID and Correlation ID across JSM.
• Loading Java classes in JVM properly to avoid ClassDefNotFound Exceptions
  - LANSA Integrator V11.0
  Important notes for using JAR files.
• Internationalizing commonly used characters e.g. @, &, $
  - LANSA Integrator V11.0
  Compiling string literals do not have the same HEX code across all EBCDIC CCSID's.
• Checking in and compiling RDMLX function that run via JSMDirect may require Web server restart
  - LANSA Integrator V11.0
  Checking in RDMLX function results in Process not getting found in the reused job.
• Special characters not appearing when using the PDFSpoolFileService to convert spool files into a PDF document
  - LANSA Integrator
  When using the PDFSpoolFileService to read and convert a spool file from the iSeries, certain characters are not getting translated properly.
• Error in JSM_OPEN in V10.0 due to changed location of jsmcltdta.txt
  - LANSA Integrator V10.0
  jsmcltdta.txt file is stored in different locations between V10.0 and V11.0 which can cause errors on JSM_OPEN.
• LANSA Integrator SMTP Service cannot send email attachment from QDLS
  - LANSA Integrator V10.0
  Error: 'Attachment file does not exist' sending mail with attachment from iSeries QDLS.
• Visual XML Wizard hangs when running in Windows XP
  - LANSA Integrator
  Visual XML Wizard hangs when running under Windows XP with Java 1.4.1 and DirectDraw and ATI graphic cards.

SOAP

• Reporting problems loading WSDL source into the LANSA SOAP Agent Wizard
  - LANSA Integrator All Versions
  Required information when reporting errors loading WSDL source into the LANSA Integrator SOAP Agent Wizard
• SOAP Server takes a long time to respond which can cause timeout problems
  - LANSA Integrator
  SOAP Server can take a long time to respond because it needs to reload classes. This can cause connection timeout problems.
• Getting 'Premature end of file' error when running SOAP in RDMLX
  - LANSA Integrator V11.3
  faultString: org.xml.sax.SAXParseException: Premature end of file.
• Getting stack trace: java.lang.reflect.InvocationTargetException when consuming a SOAP service
  - LANSA Integrator V11.0
  Executing a SOAP agent gives 'stack trace: java.lang.reflect.InvocationTargetException' error in Service.txt.

Archive

1. DEF_ARRAY corrupts returned field values from JSM services
   - LANSA Integrator
   When an RDML function contains a DEF_ARRAY command, then field values returned from a JSM service do not correctly update the function fields.
2. Integrator will not start on the iSeries
   - LANSA Integrator V10.0
   LANSA Integrator will not start on the iSeries because it cannot establish a socket connection.
3. Generating error message Instance path is not an instance when starting JSM on Windows
   - LANSA Integrator V10.0
   Possible reasons for generating the error message Instance path is not an instance when starting JSM on Windows.