Lawson 9 -> 10 Scripts

No answers for you, but curious, are the folk talking about #3 indicating this is because Infor functionality between 9 and 10 has changed sufficiently for your scripts to no longer be relevant/'doable that way' or because they have a poor opinion of the scripting capabilities of a Windows box?

I would think barring any loss of Infor supplied functionality that the truth of #2 and #3 (and really #1) would all depend on the effort being applied to the task by either you or Infor Support.

I think you'd be hard pressed to find something that you can do in 'vanilla' korn that you wouldn't be able to do in powershell. And there are even plenty of Korn alternatives for Windows out there, UWIN and cygwin for instance.

I guess most of my questions come in because of my lack of Lawson on Windows knowledge... and how does everything interact? I'm sure that we (my company) will get there, but the process may take us a lot longer than we'd like.

Assuming you will be using Windows 2012 R2, Lawson requires Cygwin and LUU. I can't really speak on the level of differences between Korn and Cygwin syntax, but I know there are some. You could go ahead and download Cygwin to any Windows machine (Server or PC) to get a feel for it. I would probably plan on significant testing/development, depending on the complexity of you're scripts.

When we went form version 9 to 10 and from Unix to Windows we did a combination of flows using IPA and scripts using Perl. Any scripts that used Korn shell were converted to Perl because I found the functionality was not there on the Windows side. Our flows were developed by a third party initially, but since then we have created them or modified the ones already created. I could have used Powershell, but I have never used it and didn't have time to learn it. Good luck in your conversion.