Re: After call sub-program, dspf package filed decimal error (mch1202)

On Wed, 2014-04-23 at 11:25 +0800, lance@xxxxxxxxxxxxxx wrote:

After call sub-program, dspf package filed decimal error (mch1202)

Procedure Name . . . . . . . . . . . . : DST7010
Program Name . . . . . . . . . . . . . : DST7010
Library . . . . . . . . . . . . . . : NITTO
Module Name. . . . . . . . . . . . . . : DST7010
Program Status . . . . . . . . . . . . : 00907
Decimal-data error occurred (C G D F).
Previous Status . . . . . . . . . . . : 00001
RNQ0001 Called program returned with LR indicator on.
Statement in Error . . . . . . . . . . : 00000731
RPG Routine . . . . . . . . . . . . . : *DETC
Number of Parameters . . . . . . . . . : 000
Message Type . . . . . . . . . . . . . : MCH
Additional Message Info . . . . . . . : 1202
Message Data . . . . . . . . . . . . . :
Decimal data error.
Status that caused RNX9001 . . . . . . :

W1BSCD CHAR(1) '2' 'F2'X
W1BSDT PACKED(6,0) 040404. '40404040'X
W1BSNM CHAR(6) ' ;' '40404040CB5E'
W1CHDT PACKED(8,0) 00000000. '000000000F'X
W1CTCD CHAR(1) '1' 'F1'X
W1CTNM CHAR(6) ' - Y ' '0E60BA63E80F'

Ps. Error value ==> W1BSDT, W1BSNM ???



0413.10 C WHEN GMFLD='W1CTCD'
0413.11 C CALL 'SSRCOD'
0413.12 C PARM 'DB' DB89S1
0413.13 C PARM W1CTCD
0413.17 C WHEN GMFLD='W1BSCD'
0413.18 C CALL 'SSRCOD'
0413.19 C PARM 'DC' DB89S1
0413.20 C PARM W1BSCD
0413.22 C OTHER
0413.23 C ENDSL

PS. 0413.11 Call no error, But 0413.18 call error occurs.
Before Call W1BSDT=201401.

It looks like you're calling a program intending to do something with
W1BSDT or W1CHDT yet you don't seem to pass either as as a parameter to
the called program.

If the called program does indeed have additional parameters then 2
possible reasons exist for one call causing an error and the other one
not.

The first reason is that the passed parameters cause the called program
to follow a different path, one hits data that is ok, the other data
that is invalid.

The second reason is that the data that the called parameters uses (but
not passed by the call) is "un-defined" this means that it can be
anything that happens to be lying around at the addresses that is
accessed by w1BSDT and w1CHDT (in the called program) in this case the
data in W1BSDT is invalid,

I'm guessing that the error in one call and not the other is a
combination of program path code, and invalid data.

Are you sure you didn#'t want to pass other parameters to the called
program?

Best Regards,


=======================