UNC paths in JOBDEF?

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

UNC paths in JOBDEF?; Creating jobs in JOBDEF to use network paths
Topic Started: Feb 9 2010, 05:03 AM (98 Views)
jecraton	Feb 9 2010, 05:03 AM Post #1
Member Posts: 14 Group: Members Member #14,788 Joined: April 27, 2009	Hi: We are running LSF 9.0 in a win32 environment. We have an app server for the 9.0 environment and a dedicated file server for the app server. I am trying to set up import jobs on the app server and am running into a snag. I am setting up a PR530 load job and I want to specify a UNC path to the file server instead of mapping a drive. IE, in TTRLOADCSV, I want to specify the following path to a file: \\lawsonfileserver\PR530\PR530IMPORT instead of D:\fileshares\PR530\PR530localfile I've tried this and it always fails. Does LAWSON support network paths to files? Is there a limitation of some sort?



Milo	Feb 23 2010, 12:19 PM Post #2
Rebmem Member Posts: 361 Group: Members Member #424 Joined: February 9, 2006	Possible solution: Your specification should be something in the order of: \\servername\drive$_or_sharename\folder\folder\ in your case: \lawsonfileserver\d$\PR530\PR530IMPORT Failure to include the drive specification letter or share name on the server will yield bad results. Windows doesn't know where to look.


« Previous Topic · System Admin · Next Topic »