Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Security Issue - Executing Lawson Utilities
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Chris Radcliffe
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
191
Members:
0
Total:
191
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1351
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Security Issue - Executing Lawson Utilities
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Garth Gerwing
Basic Member
Posts: 27
11/26/2013 2:55 PM
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.
==================================================================================================
Either the utility is not there? or some underlying LAUA environment-type security issue? Any words of wisdom would be most appreciated.
Greg Moeller
Veteran Member
Posts: 1498
11/26/2013 3:12 PM
Looks to me like you don't have wtsubmit in your PATH.
Try putting %GENDIR%\bin in your path and try again.
You are not authorized to post a reply.