Error message C2M1601 appeared during OPEN for file

[rasaro]

Getting this error message when calling a program that has a converted DDS source. The original DDS uses some system keywords on the screen like DATE, TIME, SYSNAME, etc. The DDS conversion tool converted these to js: currentDate(), etc. Job log has this message in it: Signal SIGABRT raised (abnormal termination).

[Scott Klement]

Please post the file.

[rasaro]

Here is the file.

[Scott Klement]

I've fixed the C2M1601 problem on our development box. If you need a patch to fix this on yours, please e-mail support@profoundlogic.com and ask for a patch for issue #1447.

The "js: currentTime()" this is a separate, unrelated issue. Did you put it in there like that, or did our converter do that?

[rasaro]

The DDS converter put it in. What was causing this error message, something in the original DDS? I converted several other screens and have not had that happen.

[Scott Klement]

It was a bug in the open access handler that manifests when the same indicator is defined both at the file-level and the record-level was causing the C2M1601 error.

[rasaro]

Thanks Scott. I changed my program and display not to use the same indicator. Still not sure why the DDS conversion tool did not convert the system time keyword correctly.

[Scott Klement]

Yeah, that seems like a bug. The thing is, the system time should indeed be converted to "js: currentTime()" this is what it should do.

The problem in your example is that it's in a column heading. The column heading property is being converted to ",,js: currentTime()" which is wrong. The property name has to start with "js" it cannot be in the middle of the string! So it should really be converted to something like: js: ",," + currentTime()

Probably we've never had a customer who had the system time in a subfile heading field before, and that's why it's doing that. But, this does seem like a bug and short be reported to Profound Logic Support.

[Scott Klement]

Rick,

Just FYI, we have fixed the issue where js: currentTime() and similar things are being generated incorrectly for grid headings on our development box. Unfortunately, the fix did not mkae it into the 5.0.8 release of Profound UI, but it will be in future releases.

Please contact support@profoundlogic.com if you'd like us to patch your installation for this fix. (But, if you've already converted your displays, the patch is probably too late to do you any good.)

Thanks for letting us know about the problems.