|
> Murugesh wrote: > After the dump operation, the spooled file QPPGMDMP has got a lot of > variables + their current values. I just want to figure out the particular > field, becoz of which, an error is thrown at the time of exfmt operation. > > Is there simple approach to figure out the field or should i scan thru all > the fields and their values in the spooled file? > Any idea or suggestion would be appreciated. Murugesh, 1) In the dump listing, look for the "Statement in Error" and "Last File Statement" (see example below). The statement in error is where the field with an invalid value is being referenced. 2) Look for X'4040404040' in a numeric field in the display file format . Steve Landess Austin, Texas (512) 423-0935 ***************************** Example dump listing: RPG/400 FORMATTED DUMP Program Status Area: Program Name . . . . . . . . . . . . . : LIBRARY/PROGRAM Program Status . . . . . . . . . . . . : 00907 decimal-data error in field (C G S D F). Previous Status . . . . . . . . . . . : 00000 Statement in Error . . . . . . . . . . : 40900 RPG Routine . . . . . . . . . . . . . : *DETC Number of Parameters . . . . . . . . . : 002 Message Type . . . . . . . . . . . . . : MCH1202 Decimal data error. MI Statement Number . . . . . . . . . : 009D Additional Message Info . . . . . . . : Message Data . . . . . . . . . . . . . : Last File Used . . . . . . . . . . . . : F4009 Last File Status . . . . . . . . . . . : 00000 Last File Operation . . . . . . . . . : CHAINR Last File Routine . . . . . . . . . . : S999 Last File Statement . . . . . . . . . : 183700 . . . $1ITM 11F449 ZONED(8,0) '4040404040404040'X $1MCU 11F43D CHAR(12) ' ' $1PART 11E869 CHAR(1) ' ' $1PKY 11F43D CHAR(22) ' ' $1REQD 11E89E CHAR(1) ' ' $1RUM 11F453 CHAR(2) ' '
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.