IOS Servlet doubling results every loop

robert-canham

We're testing an upgrade of our Lawson environment to LSF 10.0.11.2, Apps 10.0.10 and Landmark 11.0.33.  My logic for running jobs is having some issues and I'm wondering if anyone else has run into this.

I'm using the logic of checking /lawson-ios/action/ListQueuedJobs to find the staus of a running Lawson job. It then parses the XML results from checking that to find the status.  I have been getting errors stating "Error: org.mozilla.javascript.EcmaError: TypeError: The processing instruction target matching "[xX][mM][lL]" is not allowed." and when I check the log, it appears that each run of the /lawson-ios servlet, it adds on the results rather than replacing them, so on the second check, I get results like below.  Having two xml declarations is causing the issues I'm seeing (plus the XML search would probably find the wrong status).

<?xml version="1.0" encoding="ISO-8859-1"?><ACTION actionName="LISTQUEUEDJOBS" >
<LIST numRecords="1" maxRecordCount="500" hasMoreRecords="false" status="pass" >
<MSG>
</MSG>
<QUEUEDJOB processId="9764990" stopTime="" stopDate="" startTime="" startDate="" jobOwner="xxxx" token="AP520" jobName="AP520VPL1" jobQueue="**********" jobStepType="application" jobNumber="0000005045" jobStatus="running" runningStepNumber="0" sequenceNumber="0" productLine="LSF10TEST" actStartTime="090757" actStartDate="20200928" status="pass" >
<MSG>
</MSG>
</QUEUEDJOB>
</LIST>
</ACTION>
<?xml version="1.0" encoding="ISO-8859-1"?><ACTION actionName="LISTQUEUEDJOBS" >
<LIST numRecords="1" maxRecordCount="500" hasMoreRecords="false" status="pass" >
<MSG>
</MSG>
<QUEUEDJOB processId="9764990" stopTime="090800" stopDate="20200928" startTime="" startDate="" jobOwner="xxxx" token="AP520" jobName="AP520VPL1" jobQueue="**********" jobStepType="application" jobNumber="0000005045" jobStatus="normalCompletion" runningStepNumber="0" sequenceNumber="0" productLine="LSF10TEST" actStartTime="090757" actStartDate="20200928" status="pass" >
<MSG>
</MSG>
</QUEUEDJOB>
</LIST>
</ACTION>

unknown

Are you looking to run a process automation to find ALL jobs that are currently running in Lawson and their status?  Or is your flow triggering a specific job and then querying on the status of that job?  

We have written several flows where the automation triggers the batch job in Lawson (i.e. PR140) and then goes through a process to monitor the job until it is completed.  

If you are looking to monitor just the job that was triggered by the automation then check out KB 1667935 - IPA Best Practice - Sample Flows and Scripts.  There is a flow IPABP - Job Submit and IPABP - Job Wait.  I think this would be easier to utilize then attempting to build an XML file and parse out for the results needed.  

Hope this helps!