Security Issue - Executing Lawson Utilities

We designed some integration between the WCB's enterprise scheduler (TIDAL) and Lawson - so that we could fire Lawson batch jobs in an automated fashion. The was designed, developed, and tested on both the DEV & CERT environments - and worked fine.

Now that it is promoted to PROD - can't seem to get it going?

 

Design at high level: Shell script executing the Lawson utilities: WTSUBMIT & JOBSTATUS in succession.  We have a specific userid setup on AD and Lawson - to support automated batch execution.

 

The userid seems to have the appropriate server rights - as it will fire the shell script - but me thinks that is some sort of LAUA / environment-type security issue - the messages that are getting kicked-out are:

==================================================================================================

LWDY025
WCB\LawsonBatchProd
RBCPAYDL
The term 'wtsubmit' is not recognized as the name of a cmdlet, function, script
 file, or operable program. Check the spelling of the name, or if a path was in
cluded, verify that the path is correct and try again.
At line:1 char:9
+ wtsubmit <<<<  -n WCB\LawsonBatchProd RBCPAYDL
    + CategoryInfo          : ObjectNotFound: (wtsubmit:String) [], CommandNot
   FoundException
    + FullyQualifiedErrorId : CommandNotFoundException
 
Program Terminated Abnormally in the attempted execution of the above Lawson batch job – please investigate within Lawson Job Schedule results.