hexagon logo
Register Sign in
  • State Not Answered
  • Replies 2 replies
  • Subscribers 4 subscribers
  • Views 37 views
  • Users 0 members are here
Options
Related

***SYSTEM FATAL MESSAGE 3008 (MODUG)

Viplava
    INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE MODUG
0FATAL ERROR
1                                       * * * END OF JOB * * *
 No Symbolic Replacement variables or values were specified.
*** SYSTEM INFORMATION MESSAGE 1156 (XCLNUP)
    GINO FILE     107 WAS LEFT OPEN AT PROGRAM TERMINATION.
 
Previously I ran similar Jobs with large number of Loadcases. Now I need to reduce the number of Loadcases because of this on Nastran2013r1. Why is adding ALTER the solution? Or is there any other alternative to run with all loadcases?
Parents
  • 0
    There was an issue in v2013 where a very large SET could result in this error. Do you have a data request referencing a large SET? If so, try using ALL instead and see if that helps.
     
    This might be related to having a large number of CWELDS- do you have a lot of CWELDS? If so, the ALTER below can help but eliminates the CWELD results from data recovery.
     
    $ Nastran 2013r1 sol 101 alter to delete all MODUG references in subdmap sedisp
    compile sedisp nolist $
    alter 308,309 $
    alter 606,607 $
    alter 687,688 $
     
     
    The best thing might be to try a newer version of Nastran. Even the next release, v2014, should avoid this error if the root cause is either of the previously mentioned items.
Reply
  • 0
    There was an issue in v2013 where a very large SET could result in this error. Do you have a data request referencing a large SET? If so, try using ALL instead and see if that helps.
     
    This might be related to having a large number of CWELDS- do you have a lot of CWELDS? If so, the ALTER below can help but eliminates the CWELD results from data recovery.
     
    $ Nastran 2013r1 sol 101 alter to delete all MODUG references in subdmap sedisp
    compile sedisp nolist $
    alter 308,309 $
    alter 606,607 $
    alter 687,688 $
     
     
    The best thing might be to try a newer version of Nastran. Even the next release, v2014, should avoid this error if the root cause is either of the previously mentioned items.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement