WebRun/JobRun - How do I make sure that one is complete before I start the next?

I am using WebRun/JobRun in an automation to run 4 different Lawson processes which need to run in order and need to be completed before the next one starts. I have tried using a branch to check for errorCode = 0, but it apparently has this set before completion. How can I guarantee it is complete before the next runs?

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

john-miller

The way we do this is to have a Lawson query node check the QUEUEDJOB for the submitted job and a branch to count the records returned, if more than zero, wait a length of time (sleep command on Unix is our solution, but I see 10.1.1 has an actual wait node) then query again. Once the query returns zero you know it's finished. But we also put logic in there to only loop so many times before sending an error to the Admins. Here's our query:

PROD=GEN&FILE=QUEUEDJOB&INDEX=QJBSET1&FIELD=STATUS;JOBNUMBER;USERNAME;JOBNAME;PRODUCTLINE&SELECT=(STATUS=34|STATUS=0)%26JOBNAME=<!JobName]>%26USERNAME=<!JobUser>&OUT=CSV&DELIM=~

plancor

Have you added the &WAIT=true directive at the end of the Post string?

unknown

We tried the WAIT=true option only to discover our version of IPA did not support it. Another project.

We simply use the WAIT node. Another option we tested, but, did not implement was to adjust the batch job to create a file. Then use the File Access node with File Exists to control the subsequent jobs. We choose WAIT as our batch jobs typically run under 5 minutes.

unknown

This sounds like one of will work. I had tried the wait, but maybe I wasn't doing enough time to get reliable results. I am going to try the query next to see if that helps.

Thank you!

unknown

&WAIT=true seems to have solved the issue! THANK YOU!

russel-cornelson

Good afternoon everyone, I just wanted to weigh in with recommended procedures for submitting jobs from Infor Process Automation against LSF10.

1. Do not use the cgi-lawson executable to submit your job

These cgi-lawson programs are deprecated and are no longer tested when LSF patches are made. Instead you should use the LSF10 delivered lawson-ios/action servlets.

2. Do not use WAIT=true when submitting a job

This hijacks a processing workunit, and all the resources associated with that workunit thread until the job completes.

Recommended procedure for submitting a job (Web Run > Assign node)

Web Run Node.

GET call with Web Program= /lawson-ios/action/SubmitJob?jobOwner=<!jobOwner>&jobName=<!jobName>

Assign Node with javascript to analyze response

var xmlString = WebRun2810_result.replace(/<?xml.*?>/, '');

var myXML= new XML(xmlString);

jobNumber = myXML.QUEUEDJOB.@jobNumber;

jobNumber = "0000000000" + jobNumber;

jobNumber = jobNumber.substring(jobNumber.length - 10);

Recommended procedure for waiting till a Job has completed Processing (Web Run > Assign > Branch > Wait)

WebRun Configuration

GET call with Web Program=/lawson-ios/action/ListQueuedJobs?filter=jobNumber%20EQ%20<!jobNumber>

Assign Node Configuration (javascript analyze response from web run)

var xmlString = WebRun4550_result.replace(/<?xml.*?>/, '');

var myXML= new XML(xmlString);

jobStatus = myXML.LIST.QUEUEDJOB.@jobStatus

Branch Node Configuration

jobStatus == "running"||"waiting"

jobStatus == "needsRecovery"

etc.. etc

Wait Node

Wait for 30 seconds or a minute, or 5 minutes if its a long running job.

Quick Summary

You should not use WAIT=True when submitting a job; this hijacks resources, and in the IPA world where LSF is configured on a different server than Landmark and potentially cloud involvement ... there is ALOT of places this can timeout in the network traffic and fail.

Use the lawson-ios/action servlets instead of the deprecated cgi-lawson executables, then leverage a wait node to hold the process until the job has completed. This also lets you design a flow that can handle ANY job status .. needs recovery/invalid parameters/cancelled, etc

For more information see KB article 1667935

Infor Process Automation - Best Practices - Sample Flows & Scripts

Copyright © 2025 Infor. All rights reserved.