Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
S3 Customization/Development
Translation of 4GL names to iSeries
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
1
Overall:
4988
People Online:
Visitors:
225
Members:
0
Total:
225
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Integration / Customization
S3 Customization/Development
Translation of 4GL names to iSeries
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
19 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Walter
Advanced Member
Posts: 22
6/25/2010 3:25 PM
Does anyone have any idea how Lawson determines the iSeries RPG field names when custom tables are created in DBDEF?
We're migrating to LSF9 from 8.1. In 8.1 I created several files under a custom system code. When these files were created, the process came up with the field names. I know that the first character begins with "D", the next three is the file prefix. But how it comes up with the remaining characters, is somewhat of a mystery. I wasn't too worried about it because I wrote my supporting custom programs using the field names that were assigned. However, when migrating to LSF9, I ran into issues with 2 field names. Here is an example of the error I get with one of the fields:
"Sysload Translation INVLNG Already in Use for Element INV-LENGTH"
The field is named DZAYINVLNG in 8.1. Under LSF9 it gets named INV_L00001. It seems to me the translation process has something to do with the element that is chosen for the field name in DBDEF. (that's been my suspicion for awhile). In LSF9, that the process is different. But this is not making sense because we have several custom tables, so why isn't the problem more widespread?
Steven Gray
Advanced Member
Posts: 21
New Poster
Congrats on posting!
8/24/2010 6:02 PM
Split
Walter,
My best guess on the how the ile-xlate algorithm works, involves selecting a set number of consonants from each of the 4GL Name sections. For example:
4GL Name MATCH-DEFR-PCT
ile-xlate MT + DF + PC
Prefix DZMR
iSeries Name DZMRMTDFPC
If you have migrated definitions for custom files, and the iSeries names got changed in the process, you may have to delete and re-enter your custom files again in dbdef. You should be able see the ile-name base that was used in the table genlib/ILEXLT.
Please
login
to post a reply.