Cause Decimal Data Error As400
Contents |
statements Oracle on iSeries File Sharing View All Integrated File System (IFS) iSeries Access (Client Access) iSeries managed email and groupware NetServer Network File System (NFS) QNTC File System High Availability View All Business how to handle decimal data error in as400 Continuity High Availability Tools Replication IBM iSeries division news View All iSeries application
Mch1202 Error In As400
development View All iSeries Application development tools iSeries CL programming iSeries COBOL programming iSeries ILE programming iSeries Java programming
Decimal-data Error Occurred In As400
iSeries programming commands RPG iSeries programming Visual basic on iSeries iSeries backup and recovery View All Data backup, storage and retrieval on iSeries iSeries disaster recovery and business continuity Remote Journaling Restores
How To Handle Decimal Data Error In Rpg
Storage iSeries database management View All DB2 UDB (universal databases) iSeries SQL commands and statements Oracle on iSeries iSeries document output View All Imaging on iSeries Printing on iSeries Printing-Imaging Tools iSeries hardware management View All Grid Computing Logical Partitions (LPAR) On-demand Computing iSeries networking View All Connecting to Printers FTP Physical connections to iSeries Remote Access to iSeries TCP-IP VoIP iSeries security decimal data error in cobol 400 planning View All iSeries physical security iSeries system and application security Security Tools iSeries systems management View All Change Management Debugging i5-OS -- OS-400 iSeries Applications iSeries compliance and regulation iSeries service and support issues iSeries system performance and monitoring Multi-platform Integration Performance Server Consolidation Server Installation Server Pricing Systems Management Tools iSeries training and education View All iSeries job market iSeries skills User Groups iSeries upgrades and modernization View All Web Topics Archive View All iSeries Resources Please select a category File Sharing High Availability IBM iSeries division news iSeries application development iSeries backup and recovery iSeries database management iSeries document output iSeries hardware management iSeries networking iSeries security planning iSeries systems management iSeries training and education iSeries upgrades and modernization Section Evaluate News Get Started Evaluate Manage Problem Solve Sponsored Communities Q What is a Decimal Data Error? byJohn Blenkinsop One Search400.com member writes, "Can you please tell me what a Decimal Data error is, and what is the scenario in which it is received?" Search400.com's application development expert John Blenkinsop explains. Sections Share this item with your network: Related Expert Q&A Converting amount fields – Sea
This document provides information about finding and correcting decimal data errors. Resolving the problem It is not uncommon for programs to have problems with decimal data errors when working with files that originated on mainframes, non-IBM systems, and the rpgle monitor decimal data error IBM System/36. Program-described files are normally used on these systems and can result in non-numeric hexadecimal values in numeric fields. It is also possible for a program on the IBM OS/400 or IBM i5/OS system to do this because program-described files are still available, especially for programs that have been migrated and are running in the System/36 environment. The following example takes advantage of the field descriptions in externally-described files to correct the problem. The program http://search400.techtarget.com/answer/What-is-a-Decimal-Data-Error reads in each record and writes it out making assumptions on what the correct value should be. You are responsible for evaluating the results of using this program. Because it is necessary to make assumptions, the results might not be what you require. However, there is a very good chance the results will be satisfactory. Always keep a back-up copy of the file until you evaluate the results and are comfortable with the end result. In http://www-01.ibm.com/support/docview.wss?uid=nas8N1018444 the case of zoned numeric fields, hexadecimal values such as blanks, control characters, and unassigned hexadecimal values are normally converted to zeroes. When letters or special characters (for example, the ampersand) are encountered, the first hexadecimal character is converted to an F. For example, the letter A is C1 in hex, while the letter a is 81 in hex. Both are converted to F1, which is the number one. In testing, 8aA69 is converted to 81169. However, when certain values are encountered in certain positions in the field, the entire field can be converted to a zero value. For packed numeric fields, an incorrect value in any position normally causes the entire field to be converted to a zero value. One exception was noted in testing. A 10-digit packed field requires a 6-byte field, and the first position of the first byte is not used. An incorrect value in that first position still produced a correct converted value. All other testing resulted in a zero value being produced. To create and run the program to correct your data, you should do the following: 1. Make a copy of the file so you can examine the resulting changes. To avoid accidentally updating the production copy, use a different name for the copy. For example, if the original name is ORDDET, the copy could be ORDDETX. Note: Ensu
download here. We have all encountered decimal data errors at some time or another. The biggest difficulty they present is that, by the time they have been detected, no recovery is possible. Or to be more precise, no practical recovery is possible. In my http://www.itjungle.com/fhg/fhg031715-story01.html previous tip, I mentioned that one of the benefits of data structure I/O is that you can avoid decimal data errors. In this tip I'm going to show you how and why that works. The code package associated with this http://www.rpgpgm.com/2015/04/coping-with-data-decimal-error-when.html tip contains three test programs that demonstrate the different scenarios. The first is a straightforward RPG program with no defenses. It reads a file in a loop and will encounter decimal data errors. The second is intended to show the data error basic use of DS I/O. It still has errors but they are subtly different. The third program demonstrates how to extend the program to fully defend against such errors. See the Readme.txt file for instructions on how to install the source code on your system. One factor that adds to the difficulty of handling data decimal errors is that that they may occur on a READ or CHAIN operation, making it difficult to determine exactly which field is in error. This decimal data error happens because the system detects the error while moving the data from the buffer to the internal variable. When we use DS I/O, the entire record is moved as if it were a large character field. In other words the numeric data is not differentiated. Since numeric fields are not differentiated they can't cause errors! Let's walk through the process of running each of the three programs so that you can see the differences between them. First, here are relevant portions of program DATAERRS1. FBadData IF E DISK DoU %EOF(BadData); Read BadData; If %EOF(BadData); Leave; EndIf; records += 1; total += amount; date = %Date(numDate: *YMD); EndDo; If you run this program, you will receive an error when reading the second record. Using F1 to look at the actual details of the error reveals that it occurred on one of the compiler-generated lines associated with the READ. This is even more obvious when you run the program in debug. If you tell the program to go (option G) you will find a similar error occurs on the reading of the third record. In both cases, determining which field is in error is problematic and the only valid option is to cancel the program. Now run program DATAERRS2. FBadData IF E DISK D inputData E DS ExtName(BadData: *Input) DoU %EOF(BadData); Read BadData inputData; // Read into DS If %EOF(BadData); Leave; EndIf; records += 1; total += amount; date = %Date(numDate: *YM
April 29, 2015 Coping with data decimal error when read file I am sure we have experienced running a program when it errors with "Decimal-data error occurred", RNQ0907. After analyzing the program I would find that the error is caused by bad data in a field in the input file. Yes, I will correct the bad data, but I might want to have the program continue using a default value and create a dump that can be used for analysis later. Examples of creating dumps can be found in the post: Producing a dump from programs. How can I flag the record as having an error, give the numeric field a default value, and continue processing? First let's start with our file, TESTFILE. It contains two fields, see below: The program will only error if the field containing the bad data is used. A R TESTFILER A FLD1 3P 0 A FLD2 5A I put blanks into FLD1, the numeric field, of the second record of the file: FLD1 FLD2 1 ONE TWO 3 THREE All I am going to do is to create simple RPG program to read TESTFILE and output to the display, using RPG's DSPLY operation code, the values of the two fields, see below. If you are not familiar with all free RPG line 1 denotes that TESTFILE is being for only input. 01 dcl-f TESTFILE ; 02 dow (1 = 1) ; 03 read TESTFILER ; 04 if (%eof) ; 05 leave ; 06 endif ; 07 dsply ('Record = ' + %char(FLD1) + ' ' + FLD2) ; 08 enddo ; 09 *inlr = *on ; Which when I run this program the output will be: DSPLY Record = 1 ONE Decimal-data error occurred (C G D F). I can take the option "D" to create a dump, and the program ends. If I did not need FLD1 I would just remove it from line 7, see below. Now when the program runs it does not error as FLD1 is not used. 07 dsply ('Record = ' + FLD2) ; So what approaches are there to stop the program erroring and continue? The first approach I tried was using the *PSSR subroutine. This subroutine is only executed when an error occurs, any error. It is just coded like any other subroutine, the only difference is the second parameter with the ENDSR operation code, line 14. 01 dcl-f TESTFILE ; 02 dow (1 = 1) ; 03 read TESTFILER ; 04 if (%eof) ; 05 leave ; 06 endif ; 07 dsply ('Record = ' + %char(FLD1) + ' ' + FLD2) ; 08 enddo ; 09 dsply ('End of pgm') ; 10 *inlr = *on ; 11 begsr *PSSR ; 12 dump(a) ; 13 dsply ('Oh no! I am in *PSSR') ; 14 endsr '*CANCL' ; In this example the second parameter is not really optional. I