SRGEN error after applying a huge CTP batch...and I can't find

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

CindyW

Veteran Member

Posts: 169

5/7/2013 8:45 PM

We applied about 150 CTPs in our newest development product line, and the SRGEN threw out a bunch of errors on the .sr files, and we cleaned up most of them. However, there is one error that we can't figure out, and I can't find anything on it in the KB - ID Must Be Unique And Must Begin With SystemCode

This is the section of the srgen output file that contains the errors.

Processing D:\LSF9DEV\law\newtest901\vmsrc\VM.sr
Line 521: ID Must Be Unique And Must Begin With SystemCode
Line 611: ID Must Be Unique And Must Begin With SystemCode
Line 633: ID Must Be Unique And Must Begin With SystemCode
Line 665: ID Must Be Unique And Must Begin With SystemCode
Line 676: ID Must Be Unique And Must Begin With SystemCode

VM is a custom system code, and we have had this mod in place for years. I've never seen this error before, and in fact, I can run a srgen in the other non-patched product line (same environment) and it runs without error. Assuming that the problem is in the VM.sr file, I looked at it, and checked each line number shown in the errors.   So, for the first one above, line 521 is below (I added line numbers from the file so you can see the match from the error). The only thing I can find is that the "ID" on that line, VM-VMG-S-0001
is actually used twice in the file. The first instance of that ID, is on an earlier line number, so it appears that it is flagging the ID's that are used more than once. For each error, that is the case...the ID is used more than once, and it is the additional instances that are flagged as errors. We have no idea why this error is now occurring, when it never has in the past, and does not in the other productline. We know it has to have something to do with the CTPs that we applied, but I have no idea what to look at...everything else seems right.

line# 520 DEFINE SELECT      "Substitute Job Code"
line# 521               ID                VM-VMG-S-0001
                              SCRFLD      VME-JOB1
                              FILENAME   VMJOBCODE2
                              INDEX           VMGSET1
                              KEYRNG     COMPANY-01, "S"
                            NXTKEY      JOB-CODE
                             DSPFLDS     JOB-CODE, DESCRIPTION
                              RETURNS     JOB-CODE

This is the first instance of that ID...and no error is flagged for these lines.

line# 490 DEFINE SELECT      "Job Code"
line# 491               ID          VM-VMG-S-0001
                           SCRFLD      VM-JOB-CODE
                           FILENAME    VMJOBCODE2
                           INDEX       VMGSET1
                           KEYRNG      COMPANY-01, VM-TYPE
                             NXTKEY      JOB-CODE
                             DSPFLDS     JOB-CODE, DESCRIPTION
                            RETURNS     JOB-CODE

We ar scratching our heads. Any advice is greatly appreciated.

Woozy

Veteran Member

Posts: 709

5/7/2013 9:28 PM

I'm not sure, but it sounds like one of your CTPs has added a uniqueness check on the .sr files.

What happens if you change line 511 to "VM-VMG-S-0002" (or something that is unique in the file). Does the error go away for that line?

Kwane McNeal

Veteran Member

Posts: 479

5/7/2013 10:25 PM

Cindy,
Call me in the morning. There is a undocumented option that I had to use when I did this for you the first time to make this work correctly.
The code needs to ultimately be fixed, but in the interim, Call me and I'll tell you where to look on your systems for the option and how to set it up.

Kwane

CindyW

Veteran Member

Posts: 169

5/8/2013 12:23 PM

Woozy, that was exactly what I was thinking as well...but I guess I didn't think that a CTP would effect such changes.

CindyW

Veteran Member

Posts: 169

5/8/2013 12:24 PM

Thanks Kwane....I'll give you a call as soon as I get my coffee!!

CindyW

Veteran Member

Posts: 169

5/8/2013 2:38 PM

So this was the way we resolved the error - I added the line below to the univ.cfg file. This is just crazy that this parameter is not even documented in Lawson. Ran the srgen and it completed with no errors.

SRGEN_RULE_ID_ERRS OFF /* Used for srgen errors in DEV*

Kwane McNeal

Veteran Member

Posts: 479

5/8/2013 3:41 PM

To give some background on this, I found this tracing through the code, and asked someone in development at then-Lawson about it. They told me what it was used for, and how it worked.

I thought they were going to do a KB on it, but I don't recall ever seeing it.

Also, to clarify the usage, it is:
OFF = Don't suppress srgen id errors (This is the default behavior)
ON=Suppress srgen id errors

My understanding of the intent of this was during the Env 8.x to LSF 9.x upgrades, uniqueness checking was implemented and strictly enforced for Sr/OrMaps, which wasn't the case in Env 8.x. this flag allows a form of compatibility mode that allowed for porting 8.x apps into LSF 9.x until the code could be cleaned up.

This which is meant to be used as a *TEMPORARY* fix

K