|
View previous topic :: View next topic
|
| Author |
Message |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
| Quote: |
| there is a difference creeping up in the fetch criteria of the SQL. |
I've managed to control myself - til now. . .
Don't ya just hate it when things creep up in the fetch criteria. . . 
Scope creep is rather common, but fetch creep. . .
@Vishwa
Just in fun - nothing personal 
d |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Ed Goodman wrote: |
Could also be a compile difference. I got bit by the NUMPROC option once. In prod, a signed COMP-3 was being left as x'00000F', while in test, it was being converted to x'00000C'.
[...] |
Ed,
Just out of interest, did you find the bug and fix the data, or just let it run with NUMPROC(NOPFD)? |
|
| Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009
Posts: 1281
Location: Belgium
|
|
|
|
| checking wrong tables because of different qualifiers was also a possibility. |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
Bill,
The "shop standard" is NOPFD, so we changed our test compiler to be the same. Then we fixed the new code to work correctly (as expected) with that option active. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Good-oh.
Do you remember how the field got to get an "F" sign in it? Just curious. PFD trips up (can) with the "F", NOPFD generate bus-loads of extra code. I'd like PFD, but if it can be too "easy" to get the "F"s, it is pretty useless. |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
Bill,
In this case, the number NEEDED to be unsigned, so that the field could be used as the key for an IMS call. The "error" was that someone signed the working storage field.
So... with PFD, it changed the C to an F and worked during testing. Once it got to prod (or compiled for prod anyway) it quit working.
The fix was to remove the sign from the working storage field. then go to that developer's libraries and find all of their compiles and update the parms. |
|
| Back to top |
|
|
|
|
