MVSNAT22TO31

, , , ,
1

Hello.
I have an application developed in NAT2 and I need to upgrade it to NAT3.
The situation below ocurrs frequently:

=========================================================================
DEFINE DATA
01 #A-NUM (N3)
01 REDEFINE #A-NUM
02 #A-ALPHA (A3)
*
01 #B (N3)
01 #C (N4)
END-DEFINE
*

  • The case below has no problems
    A-NUM := 456
    B := A-NUM
    C := A-NUM
  • In the case below we have different results between NAT2 and NAT3
    A-ALPHA := “ABC”
    B := A-NUM
    C := A-NUM

** In NAT2: B receives “ABC” and C receives “0123”
** In NAT3: B receives “123” and C receives “0123”
*
End

I tried to use NEE521 (MVSNAT22TO31 impact type) to detect all objects thats uses this kind of situation but it didn’t work.

Somebody could help me?

2

Hi,

Looks like SAG have fixed a ‘feature’.

I cannot see NEE picking this up, but what might help is if you search for definitions.

Try impact criteria of DEFINITION N1-N27 and then click the Definition Options button. Then select the Redefinitions Tab and check on Alphanumeric.

When you execute impact analysis, it will show you all numeric definitions that are redefined as alpha. Clicking the field name within the Impact Element maintenace will then show the usage of the field and the source box will show the moves of #A-NUM to the other numerics.

Does this help?
Regards
BJ

3

It’ll help me very much.

Thank you, Brian.