Automatic Storage Overflow MCH4299

80 pts.
Tags:
AS/400
AS/400 backup
AS/400 errors
V5R3
Recently when running the daily backup I began getting an MCH4299 error, "One of the automatic storage stacks X'00000001' for the thread has overflowed or a storage access beyond the maximum size of a teraspace automatic storage stack was attempted." This particular server is v5r3. Can anyone tell me what may have caused this to start happening and how to correct the problem?

Answer Wiki

Thanks. We'll let you know when a new response is added.

the error related to the program running on the server – when storage overflow or storage access beyond the max size ( I assume it error in the coding of the program itself)

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    On both of my V5R3 systems, MCH4299 is:
    Message . . . . :   Module limitation exceeded.
    Cause . . . . . :   An internal part of the module exceeds allowed size.
    It seems related to what you posted, but it definitely isn't the same message. Can you give a little more detail? Tom
    125,585 pointsBadges:
    report
  • anncyb
    My mistake, typo, should be MCH4429. This just started happening. I have done cleanup on the system, reorg the disk, and performed ipls. None of that helped. I had recently applied the latest cum ptf, but that was a few weeks ago and this didn't start until the end of last week.
    80 pointsBadges:
    report
  • anncyb
    The program is the iSeries Daily Backup. Nothing has changed, so what would cause the error and how do I resolve it?
    80 pointsBadges:
    report
  • TomLiotta
    what would cause the error and how do I resolve it? First step has to be making certain that the system has the last PTFs available. There won't be any more than those that already exist for V5R3. (...Unless you can contract IBM to do it.) Next, clearly something has changed. It might only be that a library now has one more object than it had the day before or that a critical profile now owns one more object, but there's no doubt that something changed. It seems plausible that some limit has been exceeded that wasn't reached before. Some combination of too many private authorities or too many devices being varied off at once or too many concurrent calls into the system database or... who knows? You might look into the VLOG to see what, if anything, was logged at that time. You might also try WRKPRB to see if any problem data was recorded. You possibly should see about a more robust backup program. Code a program that runs steps mostly along the lines of your iSeries Daily Backup, but break parts out so that small groups of libraries or directories are saved at a time. Unfortunately, at V5R3, custom programming is about the only direction possible (if existing PTFs can't help). Tom
    125,585 pointsBadges:
    report
  • pdraebel
    I once ran into a similar problem with Backup. Solution was to dump a system index :
    DMPSYSOBJ OBJ(QSR.SRLOCK) CONTEXT(QSYS) TYPE(0E) SUBTYPE(EF)

    An IPL could also clear the issue.

    3,100 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following