Moving packed Non-Integer value to Alphanumeric

srikar tenali · New User Joined: 07 Feb 2007 Posts: 22 Location: hyderabad

"NEW-POSTL-RATE (PACKED NON-INTEGER)" and "WS-NEW-VALUE-FILE2 (ALPHANUMERIC)" did not follow the "MOVE" statement compatibility rules. The statement was discarded.

WHAT IS THE SOLUTION IN THE ABOVE CASE?

guptae · Posted: Wed Feb 07, 2007 12:29 pm

Hi Srikar,

Please provide the defination of the variables

srikar tenali · New User Joined: 07 Feb 2007 Posts: 22 Location: hyderabad

thank you for the response

this is the definition for the given variables.

15 NEW-POSTL-RATE PIC S9(3)V9(2) COMP-3.

01 WS-OLD-VALUE-FILE1 PIC X(20) VALUE SPACES.

William Thompson · Posted: Wed Feb 07, 2007 2:23 pm

bharath_rudra · New User Joined: 07 Feb 2007 Posts: 1 Location: hyderabad

MOVE THE VARIABLE S9(3)V9(2) COMP-3 TO 9(3)V9(2) COMP-3
AND THEN
MOVE IT TO THE ALPHANUMERIC VARIABLE.

dick scherrer · Posted: Wed Feb 07, 2007 8:43 pm

Hello,

You might want to repost that - they should NOT both be comp-3. That will generate the same error. The compiler won't know one of the comp-3 fields from the other.

My guess is that you meant for the second field to be 9(3)V99.

Keep in mind that when you move that zoned decimal field to the alphanumeric field you will lose the implied decimal and you may not like the alignment of the resulting field. As a rate field, it will probably never be negative, but if you used the above method, you would also lose the sign. Run it in your code, display the alphanumeric field and make sure the result is what you want. When you do the display place marks on each side of the alpha field so you can see the true placement.

If you post some "real" data and how you want it to be in the alpha field, we can better help.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

Hi Srikar,

Adding to what Dick said, the blanks you see between the marks may not in fact be spaces.

So when you look at the DISPLAY data in SDSF use "se" instead of "s" when you select the sysout. Then enter "hex on" in the cmd line. This will show you the hex value of the display line. Hex "40" is a space.

Also please tell us how you intend to use the alpha data.

srikar tenali · New User Joined: 07 Feb 2007 Posts: 22 Location: hyderabad

The above problem is solved by using

MOVE S9(3)V9(2) TO 9(3).9(2)
MOVE 9(3).9(2) TO X(20)

BY USING ABOVE METHOD, IT ISNT GIVING ANY ERRORS.

BUT WHILE TRYING TO SUB JCL, IT IS GIVING System Completion Code=0C7

DOES THIS HAS ANY ISSUE WITH THE ABEND?

ralph_v · New User Joined: 07 Jul 2005 Posts: 27

I tried the above steps and it is working fine for me without any abends.

Thanks

William Thompson · Posted: Mon Feb 12, 2007 3:51 pm

dick scherrer · Posted: Mon Feb 12, 2007 8:06 pm

Hello,

Please post the "sysout" where the error occurred - it may be in multiple places in your output.

Please post the data that caused the 0c7. For example - did the program run for some number of records or did it abend on the first record?

I believe what you've told us is that you had no errors in the compile. That does not mean the problem is solved.

Job submission of your jcl will not cause an 0c7, but having non-numeric data in a number field will. As you continue with this, you might place a numeric test before the moves and detect/display any non-numeric data.