How can a batch file put information into the log file? (Windows)

We continue to have bad data in files interfaced into Lawson via the 'importdb' command. The error output of importdb only goes to ladb.log, which is inaccessable to most users. I need a quick way to allow the user to detect and correct the bad data.

After giving it some thought, I decided that the best way would be at the copy step, first step taken in a multi-step job to use importdb to load GLTRANSREL and then bring in GL entries with GL165. I have the batch file scanning the input file for the bad data sequence, using 'grep', then create output based on what it finds.

The check to see if the grep output is zero or non-zero is working perfectly, and I can now ensure that a data file with bad data will throw the procedure into recovery at the copy step.

What I can't do is to display the output of the batch file in the log file. This is Windows (Windows Server 2012 R2). Does anyone have any experience in getting batch files to "talk" to the job log file, so that users may see what is going on? Is there a setting I have to check??

0911060553270289.pdf

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

moellerg

Milo: Since you mention using grep, can I assume that you have Cygwin installed as well?

If so, I can help... but maybe not in the way that you envision.

We've got many bash shell scripts running to do things exactly like this... and we submit the job, and capture the information, and notify the users all right from within the script itself.

moellerg@genesishealth.com

unknown

Outside of the standard 'view log' from within jobsched, we do not provide access to these files to users. As for the root cause, importing data into GL. We do something similar. However, we created a reformat program to massage the data into the GLTRANSREL format first.

Thus in sequence, we autotransfer from other system to ours, reformat, review GLTRANSREL via GL65 / GL165, update via GL165.

robert-canham

There is a batch version of importdb that you can grant to users. It is under the IF system code and is called IMDBB. It lets you create a job with the parameters that you would use at the importdb prompt and when you run it gives you a print file with the result counts and any warning/error messages.

unknown

Our requirements have changed, so I will not have to complete this project. Thanks to "rmcanham" because I had not thought of IMDBB. I was only dimly aware of it. I will check on that today!

0712131256598360.doc

unknown

Wow, success!! IMDBB works way better than importdb. IMDBB puts out a print file that tells when it ran, who ran it, where the file came from, where it was imported to, every single line that had a warning or an error, and a summary at the bottom. This is definitely what I was looking for. We will switch over as soon as possible.

Marilyn Sizemore

IMDBB is a great tool. There are actually two versions of this, one for online and one for batch processing. The other program, also in the IF system code, is IMDB.

Please consider implementing security rules around these programs. For example, if you only want users to be able to upload to the GLTRANSREL table, you can create a conditional security rule for both the IMDB & IMDBB programs that limit which file name users can use to import data. For example, you might want them to be able to import to GLTRANSREL, but not into GLTRANS. Conditional security rules on these two programs can help to protect your application data. Hope this helps!

Copyright © 2025 Infor. All rights reserved.