CSV files missing

I'm trying to figure out wht my user's batch jobs are NO LONGER automatically creating .CSV files, for instance BN320 used to create .csv, .dtl, .prt, and a .rtl.prm in the print directory. Today it is no longer creating the .csv, just the other three file types. I can go into Print Manager and do a 'save to CSV file' on the print file, but the that is a manual step that was automatic a couple of days ago. I can't find any errors being logged anywhere and no patches have been applied to LSF10 ENV/Apps or to the Windows operationg system.

Has anyone seen anything like this before or have any ideas where to start continue looking? I don't need weird today, last Friday was the 13th.

tia, mike

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

moellerg

From KB 1199903

Resolution:

For the CSV file to be created when the run the job, you need to determine at what level in the system you want to configure CSV creation, then update the appropriate configuration file. Otherwise the CSV file will only be created when you view the report in CSV from Portal.

Add RUNTIME_CSV ON to one or more of the following configuration files. This example uses a Payroll (PR) program PR275.

To configure CSV creation for all product lines in the environment, update LAWDIR/system/rpt.cfg

To configure CSV creation for a product line, create/update LAWDIR/productline/PRODLINE.cfg

Example: LAWDIR/prod90/PROD90.cfg

To configure CSV creation by system code, create/update LAWDIR/productline/xxsrc/XX.cfg

Example: LAWDIR/prod90/prsrc/PR.cfg

To configure CSV creation by program, create/update LAWDIR/prodline/xxsrc/PROGRAM.cfg.

Example: LAWDIR/prod90/prsrc/PR275.cfg

Notes:

Option 4 is a good choice for those that only want to have CSV files created at runtime for a few programs. This can help save disk space in the LAWDIR/print directory.

There is a hierarchy for these configuration files, going from the bottom up. For example, a PROGRAM.cfg file would override any other files put into place above it at the system code, product line, or system/environment level.

unknown

Try in Portal - Preferences - user Options - Default Report Type to TXT. You can also try and create a new job.

unknown

Greg - Thanks for the KB #

I pulled up the KB article and read it, then went to our test environment and created a batch job for BN320 exactly like the user's job in production,

1) ran the job - no auto create of the CSV file, viewed the output and was able to manually create CSV file

2) added RUNTIME_CSV ON to rpt.cfg at LAWDIR/system, executed rptgen, bounced Lawson and reran BN320 job - no auto create CSV file

3) next created and added RUNTIME_CSV ON to LAWDIR/dev/DEV.cfg, executed rptgen and reran BN320 job - no auto create CSV file

4) next created and added RUNTIME_CSV ON to LAWDIR/dev/bnsrc/BN.cfg, executed rptgen and reran BN320 job - no auto create CSV file

5) finally created and added RUNTIME_CSV ON to LAWDIR/dev/bnsrc/BN320.cfg, executed rptgen and reran BN320 job - still no auto create CSV file

Anyone have any ideas on what I'm doing wrong or why the CSV file is not auto creating?

unknown

Hi Mike,

We have the following in the cfg file -

RPTMAP_TYPE VARIABLE

RPTMAP_TRANSITION CONVERT

RUNTIME_CVS ON

RUNTIME_XML_ENABLE ON

Good luck,

Ray

moellerg

With all you've done, the next step I'd recommend is to open up a case!

You've basically done all of the recommendations in the KB... but it isn't working.

Maybe they have a different way of doing that now?

unknown

RUNTIME_CVS ON does not equal RUNTIME_CSV ON . Check the positioning of the V and the S. If correct in Lawson, then there's an issue. If not, just correct the spelling, betcha it'll work.

unknown

Thank you everyone for your suggestions. I was hoping that Milo was correct and that I had 'fat fingered' CVS for CSV, but alas Ray had done the typo in his response or has the typo in his cfg file. I was resigning myself to follow Greg's advice and open another case where I would once again get asked the question 'Does it work in LID?' and I would try not to get snarky with my reply that LID went away 2 years ago when we went from LSF 9 to LSF10. However, just for fun I thought I would add Ray's last line 'RUNTIME_XML_ENABLE ON' and try again. That did the trick! The 10.0.9.0 version of I/L Administration: Jobs and Reports manual says the following for RUNTIME_XML_ENABLE:

Setting to ON enables the runtime generation of the various file types(such as CSV, XML, PDF, RTL, and ADO) for all reports. The default for this parameter is OFF. You can override this setting at the productline, system code, and individual report program level. After you setthis to ON, you can set the RUNTIME_CSV, RUNTIME_XML,RUNTIME_PDF, RUNTIME_TXT, RUNTIME_ADO, RUNTIME_CSV_TOT_GRPS, and RUNTIME_LOC_PROP parameters in order todetermine which types of files are actually generated. You can setthese parameters either at the global level (in rpt.cfg) or at a lowerlevel (product line, system code, or individual report program).

Note: KB 1199903 in their example rpt.cfg had the line *RUNTIME_XML_ENABLE ON (commented out)

Thanks, I can now return to my normal state FDH (fat, dumb, happy)

unknown

Thank you for explaining about RUNTIME_XML_ENABLE. That was totally unexpected. It's a good thing to know.

Copyright © 2025 Infor. All rights reserved.