Webrun errorcode = 1 but no information on error

I'm an IPA beginner too, but the error text I used to troubleshoot is in the Return Message: Perhaps an experienced user knows another place.

Joan

The webrun node doesn't actually bring an error back. The way it knows that the job was successful is if you check for a 63 in the sucess string (make sure you use the OUT=XML).

As for the actual message, if it is starting the job, you should see record of it in the job scheduler. If it isn't, try pasting the url and parameters into a web browser, that will give you the full results back (i.e. http:///cgi-lawson/jobrun.exe?FUNC=run&USER=lawson&JOB=CU200&OUT=xml&WAIT=true). That will give you the full xml response (though they're still not terribly helpful).

I'm setting up process flows for the first time, and had a couple similar questions:

- Is there a list somewhere of the different values of the status code in the success string (i.e., 63 = success)?
- My WebRun node is successful (error code of zero), but the job that it's running is showing errors within the reports that come out in Lawson. How do I catch these errors? Would this be via the status code in the success string?

Thanks,
Mike Fameree

The Success String on the WebRun only returns that the Job was submitted successfully, not the status of the actual job that ran. You have to query (DME) the JOBQUEUE table in GEN for the actual job's status.

If you have the job set to wait=true, the status code will tell you the disposition of the job (completed/waiting tabs in job scheduler) like normal completion, needs recovery, invalid parameters. If it ran to completion, you'll get a status=63.

However, if you're trying to get the information contained in error output reports then you would need to find a way to read the data in and process it in some fashion (either csv or xml). I typically send the job output to an appropriate user to review any errors and take action manually.

The WebRun_success Boolean only lets you know the status of the job.  The program may have received an error on every record it processed; all the 'success' variable will tell you is whether or not job completed normally with a status of '63' (if you put "<status>63</status>" in the 'success string' field and include 'out=xml' in the post string).

If you want to know whether or not your job had data errors you'll need to read the output of the job (most likely in either the work directory or the print directory).

 

Here's the status number translations:

00 : running
30 : Waiting
31 : Waiting Step
32 : Waiting on Time
33 : Waiting Recovery
34 : Needs Recovery
35 : Invalid Parameters
36 : Queue Inactive
37 : Hold
60 : Recurring Skipped
61 : Recovery Deleted
62 : Cancelled
63 : Normal Completion

Thank you everyone for the responses, they were all very helpful! We are new to both Lawson and IPA, so we're still in 'learning' mode.

Kyle, thanks much for the status number translations. Just curious if you found them in a Lawson manual somewhere?

I can't remember where I found them it was so long ago. Perhaps I used 'dbdef' on the QUEUEDJOB table in GEN. Or perhaps I found them buried in the old Lawson support KB (before Infor bought Lawson).

We've made it a standard practice to attach the job log file to the error email if a batch job fails. Job logs are in $LAWDIR/system/joblog/
The job log filename convention is:
jobname-in-lowecase.jobnumber

The job log filename is never more than 14 bytes long (including the period). If the combination of the jobname and the jobnumber would make the filename greater than 14 bytes, the jobname portion is truncated so that the total length is 14. The job number is included in the XML data returned by the WebRun node.

@mafameree

This list was created originally by Lawson from the header files from the v7 environment. It's actually longer than this, I'll dig mine out.

Kyle is right. We hashed this FaxBack (before there was a public knowledge base) out over Topica, which was 15-16 years ago.