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

Fatal message 6352 Same model ran on 2013, but on versions 2017 and 21019 this problem exists.

Viplava
 *** USER WARNING MESSAGE 285 (DML)
   FATAL ERRORS WERE FOUND WHILE READING THIS BEGIN SECTION
   MODEL SUMMARY DOES NOT INCLUDE COUNT OF FATAL ENTITIES
 ^^^   
 ^^^ >>> IFP OPERATIONS COMPLETE <<< 
 ^^^   
 *** SYSTEM FATAL MESSAGE 6352 (IFP6PCMP)
   LOGIC ERROR: 9212
   USER ACTION: CONTACT MSC.SOFTWARE CLIENT SUPPORT.
   PROGRAMMER INFORMATION: KPCOMP=     1, NPCOMP=     0
0FATAL ERROR
  • 0
    Can you try running with below system cell at top of the deck?
    NASTRAN SYSTEM(444)=0
     
    Please attach last few pages of f06 and f04 and log file. It is easier to debug with it.
  • 0
    Could you explain what does NASTRAN SYSTEM(444)=0 stand for? and what does it do?
    i attached the files below..
    Attached Files (1)
  • 0
    Actually message in f06 is very clear..
     *** USER FATAL MESSAGE 9994 (BULKPM)
       PCOMP with PID=80221843 near line 3335919
       User information: THETA:165 is an integer in a real field.
       User action: Enter a real value or set system 444 to 9 to have the program convert the integer to a real value
     
    Please add NASTRAN SYSTEM(444)=9 at the top of deck and run...
     
    444 cell is related to the IFP processing. 444=9 was introduced in 2017 to avoid user error to run and produce and give incorrect results. Like in this case you theta angle should have been 165. rather than 165
     
    So use 444=9 and check if it works..
  • 0
    Great.... 444=9 should also work. 444=0 would switch back to the 2012 ifp Processing.
    Personally I would prefer using 444=9 as it uses the new IFP processing which is much faster and better checks in place for input file checking.
    This is useful as it tells the user to check if he has accidentally placed incorrect values in the fields... Once he has confirmed that everything is correct, he can add the cell to run the job.
     
  • 0
    I have another question with respect to different versions. Everything is same for a model between v2013 and v2019, except for OP2 files. The sizes are 49GB (v2013) and 72GB (in 2019), f06 are the same for a SOL105 problem.
  • 0
    The newer versions keep adding new datablocks making it heavy.
     
    Geometry data blocks are output with PARAM,OGEOM,YES (Default). Can you try running with PARAM,OGEOM,NO ?
     
    This should remove the geometry data blocks from op2 and will only work for PARAM,POST,-1
  • 0
    Hi Hrishikesh,
    Thanks a lot for your support. Dont mind, I have another question, We have long paths to include files, and it exceeds 257 characters. Is there a way to override this? when we submit job, we have an .err file generated by nastran which looks like the following:
     
    GRID_DEBUGGING_SESSION_GRID
    >>>> validate_ $key:stages
    >>>> validate_ $key:version
    >>>>> $input_deck: /userwork/cae##/s###/00/Study_pre_v02.dat
    >>>>> evaluate_stages.
    >>>>> built this commandline: /bin/nice -n 19 /bin/time -p /CAE1/app/nastran/2013/bin/nast20131 Study_pre_v02.dat
    >>>>> changing to working directory: /userwork/cae##/s###/00
     
    *** SYSTEM INFORMATION MESSAGE (pgm: nastran, fn: estimate_job_requirements)
      Starting ESTIMATE, please wait...
     
    *** USER WARNING MESSAGE (pgm: estimate, fn: GETLIN)
      File name specified on INCLUDE statement exceeds maximum allowable length
      of 257. File '... ><   ><   >$EIGRL  1    0.1   1.6   30
      0$SWLDPRM PROJTOL 0.005  GSMOVE 2P' is included in file
      './Study_pre_v02.dat' at statement number 44. The "INCLUDE" request is
      skipped.
     
    *** USER WARNING MESSAGE (pgm: estimate, fn: GETLIN)
      File name specified on INCLUDE statement exceeds maximum allowable length
      of 257. File '... ><   ><   >$EIGRL  1    0.1   1.6   30
      0$SWLDPRM PROJTOL 0.005  GSMOVE 2P' is included in file
      './Study_pre_v02.dat' at statement number 124. The "INCLUDE" request is
      skipped.
     
    *** USER WARNING MESSAGE (pgm: estimate, fn: GETLIN)
      File name specified on INCLUDE statement exceeds maximum allowable length
      of 257. File '...  Residual
      Forces$--------------------------------------------------------------------
      ---INCLUDE' is included in file './Study_pre_v02.dat' at statement number
      176. The "INCLUDE" request is skipped.
     
  • 0
    keep 72 character on each line.. then just keep going on to the next line..
    See attached image..
    Attached Files (1)
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement