Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

ajt (2546)

ajt
  (email not shown publicly)
http://www.iredale.net/

UK based. Perl, XML/HTTP, SAP, Debian hacker.

  • CPAN: ATRICKETT [cpan.org]
  • PerlMonks: ajt [perlmonks.org]
  • Local LUG: AdamTrickett [lug.org.uk]
  • Debian Administration: ajt [debian-adm...ration.org]
  • LinkedIn: drajt [linkedin.com]

Journal of ajt (2546)

Saturday January 20, 2007
07:22 AM

Poor Logic!

[ #32215 ]

This week at work our SAP system was "dumping"[1] on a routine night time batch job. After some digging into the code I figured out what was happening. The code was logically flawed - actually it was quite poorly written and not only was it flawed, it wasn't very efficient either.

I created a patch and ran the tested data that caused the dump, and low and behold it ran perfectly. Annoyingly we couldn't create the dump with other test data on the original code, so I'm not sure what the upstream conditions are that cause the dump but I can prevent them now.

I've not been using SAP's ABAP[2] language for long but the error in the original code is quite striking and it's repeated three times in quick succession throughout that block of code (cut'n'paste ...?). Considering it was written by an experienced ABAP developer, I do wonder at the quality of ABAP code used throughout industry world wide.

  1. Run time error, the ABAP engine abends and writes a dump report.
  2. ABAP is SAP's proprietary programming language derived from COBOL.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.