- This topic has 0 replies, 1 voice, and was last updated 8 years ago by .
-
-
There’s gotta be another government systems analyst on here, any nerds wanna read along with me while I wait?
Here are the software developers notes. Bring the Bart files up in a new tab and go to town trying to analyze the whys and wherefores of this ‘system crash’ … it ain’t no system crash, you ever have an as/400 go *down* ? *everything* stops, institutionally, across the board until it comes back up, which is about 20 minutes worst case scenario.
This problem in production is an overflow error, bad programming basically. So IRS employees (and file partners, etc) are being told to not connect to the mainframes while the guys from Triple 8s Consulting are debugging the overflow. I think somebody failed in the system’s garbage collection process, and when the machine hit 65,535 records, it hit its buffers and dropped the ball. *I THINK* (but do not know for certain) that this has happened for every update so far, that’s why so few ppl are getting updates, its also why the batches are done in like 15-20 minutes (it’s why some folks can see updates at 4am EST instead of having to wait until 6AM). I believe this is the biggest issue affecting us all right now (1/20 for me, no progress past acceptance and account ts).
anywho, here’s a good long technical manual to read while the contracted IT boys learn FORTRAN and Accumulo on the fly, lol :)
https://www.irs.gov/pub/irs-pdf/p4164.pdf
[This Publication outlines the communication procedures, transmission formats, Business Rules and validation procedures for returns e-filed through the Modernized e-File (MeF) System. To develop software for use with the MeF system, Software Developers and Transmitters should use the guidelines provided in this Publication along with the Extensible Markup Language (XML) Schemas published on irs.gov.]
- The forum ‘2016 Tax Season’ is closed to new topics and replies.