Pink Sheet

MSC.Nastran 2005 r1 Pink Sheet

This document provides important information about MSC.Nastran 2005 r1 not contained in the Release Guide or Installation and Operations Guide. It is intended to help you install and use MSC.Nastran 2005 r1.

Delivery Media The MSC.Nastran delivery includes an MSC.Marc 2005 r1 executable used for the MSC.Nastran Implicit Nonlinear (SOL 600) capability. This delivery also includes a special version of LS-DYNA developed by Livermore Software Technology Corporation), used for the nonlinear dynamic Explicit Nonlinear (SOL 700) capability.

MSC.Nastran is delivered on the following nine CDs:

• Cray, NEC, Fujitsu (Implicit and Explicit Nonlinear are not supported) • Compaq Alpha • HP HP-UX PA-RISC – 64 bit • HP HP-UX Itanium • IBM AIX – 64-bit • SGI Irix – 64-bit • Sun Solaris – 64-bit, Fujitsu Primepower • Intel Linux – 32-bit and 64-bit Itanium • Intel Windows

Installation Notes

Authorization Codes Please note that new nodelock (SBCM type) authorization codes will be required to run any versions of MSC.Nastran after 2004 r2. SBCM codes issued for any version of MSC.Nastran prior to this release will not work with 2004 r2 or r3.

The version 2004 FLEXlm based codes (nodelock and floating) will not be affected however, and will still be current.

Directory Structure The directory structure under the “msc2005” directory has changed since the documentation was printed.

The “marc” and “dyna” directories have been added under the “msc2005” directory.

Page 1 of 12 NA*V2005R1*Z*Z*Z*DC-PNK

MSC.Nastran 2005 r1 Documentation

Documentation for the MSC.Nastran 2005 r1 release comprises the Release Guide, Installation and Operations Guide, and Quick Reference Guide. These documents are also provided in electronic format, and are available on the installation CD.

AUTOMSET

The relationship between independent and dependent degrees of freedom defined by rigid elements and multipoint constraints can be automatically altered to remove problematic interdependencies by specifying PARAM,AUTOMSET,YES. The default value for this parameter is NO.

The AUTOMSET capability is not currently supported for upstream superelements.

Implicit Nonlinear (SOL 600) Items

• Improvements have been made in MSC.Marc and MSC.Nastran to allow more problems with MPC's, RBE2, RBAR, and RTRPLT to run to completion. However the improvements in MSC.Marc 2005 are still not capable of running all cases that MSC.Nastran can run (particularly when Auto M-Set is used). The majority of models with these entries should run without difficulty. Should your analysis exit with an MSC.Marc exit code 2011 or experience convergence problems (for example MSC.Marc exit code 3015), then there are several potential workarounds that can be attempted to try and get the problem to run. First, try the bulk data parameter PARAM,MARMPCHK,3, also ensure that there are no MARCIN entries specifying feature 4301 (an obsolete option for some MSC.Marc 2005 beta test versions). This will cause MSC.Marc to attempt to rearrange these entities if possible. If that does not work, these entries (except for MPC) can be changed to stiff beams using bulk data parameters PARAM,MARCRIGD,1 If the model still does not run, check all rigid elements carefully and run the model without any 3D contact using MSC.Nastran SOL 101 and/or 106. If the MSC.Nastran run is satisfactory but SOL 600 still fails, the only other solution is to remodel the rigid elements and MPC’s.

• The following improvements have been made to the OP2 file produced by SOL 600 for

MSC.Nastran 2005: o Beam loads and Beam stresses (if beams are in the model) were added. o Reaction force (SPC force) output is available for most analyses (in the OQGV

datablock). o Velocity and Acceleration for dynamics problems is now available.


o Improvements were made to the header records (7-word and 146-word) to make the SOL 600 generated OP2files resemble the MSC.Nastran generated OP2 files as closely as possible.

o Reading and plotting of results from the op2 files has been successfully checked using MSC.Patran, FEMAP and Medina.

o Creation of the op2 file is still specified on the SOL 600 entry using the OUTR option and includes all or none of each type of result. Case Control requests to process selected sets are ignored for MSC.Nastran 2005. A task to implement Case Control requests, both in MSC.Marc and in the t16 to OP2 processor, is likely to be available in the 2005 r2 release.

o Creation of the OP2, or other OUTR options, still requires that displacements, one type of stress tensor, and one type of strain tensor be available in the MSC.Marc t16 file. If the user decides to control the results output data that are written to the t16 file using the MSC.Nastran bulk data entry MARCOUT, and if OUTR is specified with insufficient requests, then the job will abort before MSC.Marc runs. It is suggested that MARCOUT not be used if OUTR is used.

o The output interval for the t16 file (and thus the OP2 file) is controlled by bulk data PARAM,MARCOTIM, which is documented in the MSC.Nastran 2005 Quick Reference Guide.

• Improvements have been made to reduce the amount of memory used by MSC.Marc when

spawned from MSC.Nastran. For advanced users, parameters were added to override the automatic memory variables and control each memory request. These are all documented in the MSC.Nastran 2005 Quick Reference Guide.

• The NDDL description for some SOL 600 and SOL 700 bulk data entries is not up to date.

These entries are intercepted and placed on a special database used by the SOL 600/700 translators. As a result, these entries will not be echoed in the f06 file or show up in the "geom" datablocks. This is not a problem in most cases, however circularity for MSC.Patran might be affected. In other words, some models generated by MSC.Patran will produce a different MSC.Nastran input deck if the first input deck is read into a new MSC.Patran session and immediately output to a different MSC.Nastran deck. Another aspect of the NDDL not being up to date is that the 3D contact Bulk Data entries are only valid for SOL 600 and 700. They must be removed from the input deck for other solution sequences for MSC.Nastran 2005. It is anticipated that this will be corrected in the MSC.Nastran 2006 release.

• MPC's and rigid elements combined with contact and/or the same node in more than one

contact body can sometimes cause the MSC.Marc portion of SOL 600 to fail. There is a new feature in MSC.Marc known as optimized contact that can frequently help these types of models to run correctly. For version 2005, optimized contact is not the default either in MSC.Marc (stand-alone) or MSC.Nastran SOL 600, since the capability is quite new. If MSC.Marc exit 2011 or convergence problems are encountered with such models, please try optimized contact. To invoke optimized contact from MSC.Nastran, set field 6 of each BCBODY entry with flexible contact to 2. In addition, set field 3 of each "SLAVE"


continuation line (the next line after all lines with SLAVE) to 2. In turn, this sets MSC.Marc's CONTACT entry 4th datablock, 3rd field to 2 and each CONTACT TABLE 3rd datablock 8th entry to 2 respectively. Detailed discussions and an example of optimized are provided in Chapter 8 of the MSC.Marc Theory and Information Manual (Volume A of the MSC.Marc documentation) - see text before and after figure 8-4.

• MSC.Nastran 2005 PC versions are released using the Intel version of MSC.Marc as the

default. The Digital Visual Fortran (DVF) version is available on the MSC.Nastran CD, but is no longer fully supported by SOL 600. If you prefer to use the DVF version, the OUTR options (op2, punch, xdb, f06) are no longer available and if attempted will generate an error.

• Additional options have been added to the SOL 600 op2. These include beam force, beam

stress and reaction force as well as velocity and acceleration for dynamics problems. • For MSC.Nastran 2005, most 3D contact entries are not available in the "geom" datablocks.

Neither are they available in the op2, punch or xdb files, and are not echoed in the f06. They are available to MSC.Patran, which uses a special portion of MSC.Nastran called the DB server.

• For most bulk data entries, SOL 600 and SOL 700 do not make the distinction between zero

and a blank. Thus, if a zero is entered and the default is some other value, the default will normally be used. If you wish to use zero, enter a small number such as 1.0E-12 instead.

• Not all MSC.Nastran Case Control or Bulk Data entries are supported in SOL 600. Please

consult the MSC.Nastran Version 2005 QRG (SOL 600 Executive Control entry) for a list of items that are not supported. The following items have been removed from this list:

o PBUSHT is now supported o CBUSH1D is now supported o Command line OUT and SOL 600 executive control OUTR options are now

compatible Of the remaining non-supported items, the most important are listed below. If your model requires the use of these items, please use SOL 106 or 129 instead.

o Pin flags for CBEAM/CBAR are not supported (error is given) o CGAP is only partially supported and its use with SOL 600 is discouraged o Superelements are not available yet (will be added starting in 2005 r2) – Do not use

any entries dealing with superelements o Certain Case Control entries such as STATSUB are not available o Inertial Relief is not available (to be added in 2006) o The only op2 results currently available are displacement, (velocity, acceleration for

dynamics), stress, strain, beam/bar internal force, reaction force (at spc dof’s, non-spc dof’s have unbalanced force in this OQGV datablock)


• MSC.Marc 2005 is installed with MSC.Nastran 2005. Appropriate licenses are needed to use SOL 600. For most computer systems, installation is automatic. However, for some systems, particularly IBM UNIX systems, the MSC.Marc Installation Manual found in the MSC Combined Documentation CD should be consulted. For certain IBM UNIX systems, the include file in the tools directory must be changed and the ~/marc2005/lib/lib_extra directory might need to be renamed to ~/marc2005/lib/lib_shared if a compiler is not available. MSC technical support personnel can assist with these issues.

• A special experimental (beta) feature for postprocessing with Animator is available using

param,marccomb,1. This feature combines CQUAD4 and CTRIA3 records in the CQUAD4 record and allows animator to plot both types of shells on the same plot. This feature should be used only for postprocessing with Animator. Please report any problems using this feature to MSC support.

• For MSC.Nastran 2005 it is still recommended that postprocessing be accomplished using

the t16 file particularly if contact output or multiple type of stress or strain tensor information is desired. MSC.Patran and certain other programs can postprocess all t16 data. For MSC.Nastran 2006, all t16 output will also be available in op2 files, however postprocessor programs will need to learn to read the new datablocks for contact, generalized stress and strain (for multiple type of stress and strain tensors). Postprocessor developers can obtain details of these new datablocks starting in early 2005 (contact MSC.Nastran development).

• The Implicit Nonlinear User’s Guide is not up to date. It will be revised and brought up to

date by the 2005 r2 release. • Additional items have been added to the MSC.Nastran QRG since it went to press for the

2005 release. The following items are new or revised:

o SOL 600 Executive Control Entry – Continue Option: The CONTINUE=2 option is not presently available New CONTINUE=6 and CONTINUE=7 were added as follows:

6 Same as option 1 except SOL 110 is run. For this option, the original MSC.Nastran input deck must contain METHOD=ID1 and CMETHOD=ID2 in the Case Control, as well as matching EIGRL (or EIGR) and CEIG entries in the Bulk Data.

7 Same as option 1 except SOL 103 is run for real eigenvalues/eigenvectors. The database can be saved to restart into SOL 110 if desired. This should be done on the command line or in an rc file with scratch=no. For this situation, the original Nastran input deck must include METHOD=id in the Case Control and a matching EIGRL or EIGR entry in the Bulk Data, (CMETHOD and CEIG can also be included). The actual restart from SOL 103 to 110 must be performed manually at the present time.

• Remark 3 is eliminated

o PARAMARC Bulk Data entry – KIND=3,4,5 options are eliminated (replaced by KIND=0, the new single-file parallel capability).


o AUTO LOAD and AUTO TIME are no longer supported. Only AUTO STEP and AUTO INCREMENT are now supported. AUTO STEP can be used for non-automatic stepping if desired. This comment applies to all Bulk Data entries which mention AUTO LOAD or AUTO TIME.

o BCPARA Bulk Data Entry – Additional friction types are available as described below:

FTYPE

(2,4)

Friction type (Integer 0 to 5) =0 No Friction, =1 Shear friction, =2 Coulomb Friction (default if friction is present and FTYPE is not entered), =3 Shear friction for rolling, =4 Coulomb friction for rolling, =5 Stick-slip Coulomb friction, =6 Bilinear Coulomb Friction, =7 Bilinear Shear Friction (types 6 and 7 are available only in Marc 2005 and subsequent releases)

FKIND (2,5) Friction kind (integer 0 or 1) =0 friction based on nodal stress, =1 (default if friction is

present and FKIND is not entered) friction based on nodal force

o MATORT Bulk Data entry

The following items are required (must be entered) and have no defaults: MID, E1, E2, E3, NU12, NU23, NU31, G12, G23, G31 The following options were added for IYLD

• -1 = Elastic • 7 = Hill yield theory • 8 = Barlat yield theory • 9 = Viscoplasticity through user subroutine UVSCPL

Y1, Y2, Y3, YSHR1, YSHR2, YSHR3 are yield stress ratio (not actual yield stresses)

• The following SOL 600 parameters have been revised or added: (Note: defaults listed are used in SOL 600 if the parameter is not entered)

PARAM,MARCOTIM,0 or 1 (Integer, default=0) MSC.Marc output data will be processed by MSC.Nastran at all converged output times. This option is similar to INTOUT=ALL on the NLPARM entry.

2 MSC.Marc output data will be processed by MSC.Marc only at times near 1.0, 2.0, 3.0, etc. For this option, no additional output times will be available in the MSC.Marc .t16 and/or .t19 output files. This options is similar to INTOUT=NO on the NLPARM entry.

N MSC.Marc output data will be processed by MSC.Marc every Nth increment for the .t16 and/or .t19 output files (N>2)

PARAM,MARCSLHT,N (Integer, default=11) Number of layers through the shell thickness used to integrate shell and beam elements. For linear behavior N=1 is sufficient. For most plasticity


problems N=7 is adequate. For extremely nonlinear plasticity problems N=11 should be used. SOL 600 normally requires that N be 5 or larger. If N is entered with a value less than 5, SOL 600 will set it to 5. To use values smaller than 5, enter N as a negative number. The absolute value will be used, however MSC.Marc might fail with error code 13. Note: Use of param,marcdef can affect the value of MSC.Marc’s SHELL SECT parameter if param,marcslht is not entered. To eliminate SHELL SECT from the Marc deck, set N to –9999.

PARAM,MARCASUM,-1 (Integer, default=1 for nonlinear analyses and 1 for linear analysis) MSC.Marc’s assumed strain formulation is not used.

1 MSC.Marc’s assumed strain formulation is used for plane stress, plane strain and solid elements (Marc types 3, 11 and 7). The assumed strain formulation improves the bending behavior of these elements and uses an enriched set of interpolation functions. Assumed strain should be off for analyses with a significant amount of plasticity. In determining the type of analysis (linear or nonlinear) for defaults of this parameter, the SOL 600,ID executive control card is used. If ID is 106 or 129, the analysis is considered to be nonlinear and the default is –1. If ID is any other value, the analysis is considered to be linear and the default is 1. For nonlinear analyses without plasticity, this parameter should be turned on for models with solid elements.

PARAM,MRRELNOD,0 (Integer, default=0) For multiple subcases with SPCD’s, all of the SPCD’s from the previous subcase will be released at the start of the current subcase.

N SPCD’s from the previous subcase will be released gradually during the current (Nth) subcase. For purposes of this parameter, do not use the subcase ID, subcases are ordered 1, 2, 3, …,N, last. It is not legal for mrrelnod to be 1 or greater than last. (See param,mrrelbeg to determine which grids are released).

PARAM,MSOLMEM,MBYTE (Integer) (Default = Program determines value) If entered, the integer value entered here is the 8th field of MSC.Marc’s SOLVER card and is the maximum memory in Mega Bytes that can be used by MSC.Marc’s solver types 6 (hardware-provided direct) or 8 (multi-frontal direct, which is the default solver for SOL 600) before going out of core. This parameter is the same as the MBYTE field on the NLSTRAT entry and may be easier to enter as a parameter if no other NLSTRAT values are needed.

PARAM,MRFOLLOW,1 (Integer, default=0) Follower forces entered by FORCE1, FORCE2, MOMENT1, MOMENT2 will be mapped to MSC.Marc’s new follower force Option.

0 FORCE1, FORCE2, MOMENT1, MOMENT2 will act as non-follower forces. This option must be entered if MSC.Marc versions prior to 2003 r1are to be used.

-1 Follower forces will be turned off even if requested to be on using other options. This is sometimes necessary for multiple load cases where pressures are applied to different elements in the different load cases.


PARAM,MARCUSUB,chr (Character, no default) chr is the name of a “user subroutine” to be included in the spawned MSC.Marc run. chr is limited to 8 characters without the .f extension (If PARAM* is used, chr may be 16 characters). This file must be located in the same directory as the MSC.Nastran input data and must have all lowercase letters (MSC.Nastran will convert the file name to uppercase, but it will be re-converted to lower case when MSC.Marc is spawned). Any user subroutine available to MSC.Marc may be specified. Multiple user subroutines may be combined into one file – SOL 600 Only.

Restriction: The computer must have a Fortran compiler and a Linker and the Fortran compiler must be the same as used to create the original MSC.Marc executable (see the MSC.Marc installation manual). The SOL 600 MSC.Marc input deck does not as yet call out user subroutines, so manual editing of the MSC.Marc input deck will be necessary in some cases to invoke them. Existing regular (non-user) MSC.Marc subroutines can be modified and handled in the same manner if available to you.

PARAM,MARCFILi,Name (Character, No Default) Name of a file name limited to 8 characters (16 characters if param* is used) used in conjunction with one of the CONTINUE options on the SOL 600 card. For example, if CONTINUE=1 on the SOL 600 card and PARAM,MARCFIL1,DMIG44 is entered, friction stiffness and possibly damping matrices are created in DMIG format by MSC.Marc and placed on file DMIG44.

PARAM,MARCONTF,Name (Character, No Default) Name of a file name limited to 8 characters (16 characters if param* is used) used in conjunction with one of the CONTINUE options on the SOL 600 card. If entered this file will be used as the input file for the second MSC.Nastran execution (after MSC.Marc has finished). If specified, this file will be used instead of automatically creating a file named jid.nast.dat from the original jid.dat input. This option allows more versatility in achieving exactly what is desired in the MSC.Nastran Continuation run input at the expense of additional input data preparation.

PARAM,MRMTXKGG,Name (Character, no default) The Name will be used for K2GG entries if entered. This parameter is similar to MRMTXNAM.

PARAM,MARC3901 This parameter is no longer active. Do not use it.

PARAM,MARCOUTR Option 2 for this parameter is no longer supported.

PARAM,MRDISCMB (Integer, default=0) Determines whether distributed loads, such as pressure, are combined in the MSC.Marc input deck into one list if the magnitude of the distributed loads are the same. This parameter applies to MSC.Nastran 2005 only. For previous MSC.Nastran versions, MRDISCMB was 1. Option 0 saves MSC.Marc memory and processing time.

0 Distributed loads with the same magnitude are combined

1 All distributed loads are input individually


PARAM,MARCWDIS (Integer, default=1) Determines whether MSC.Marc parameter section DIST LOADS is written or not. If any of the three values for DIST LOADS are entered (see PARAM,MARCDIS2 PARAM,MARCDIS3 PARAM,MARCDIS4) it will be written. If PARAM,MARCWDIS,1 is entered, it will be written. If PARAM,MARCWDIS,-1 is entered, it will not be written. Caution: MSC.Nastran cannot estimate these values very well and produces overly conservative numbers that sometimes lead to failure of the MSC.Marc run due to lack of memory. It is suggested that the user should usually not use this parameter and enter the MARCDIS2, MARCDIS3 and MARCDIS4 values for best MSC.Marc memory usage.

PARAM,MRMAXISZ (Integer, default=Value in MSC.Marc include file in tools directory). If this value is entered, the integer value will be used on the command line to run MSC.Marc as maxsize N, where N is the integer entered.

PARAM,MRMAXNUM (Integer, default=Value in MSC.Marc include file in tools directory). If this value is entered, the integer value will be used on the command line to run Marc as –maxnum N, where N is the integer entered.

PARAM,MARMPCHK (Integer, default=-1) Determines whether MSC.Marc parameter MPC-CHECK is written

-1 MPC-CHECK is not written

N MPC-CHECK,N is written. Please consult MSC.Marc Documentation as to the meaning of MPC-CHECK and the value of N to use (currently MPC-CHECK,3 is a popular option. (Note: This parameter can be set in the rc files)

PARAM,MARNOT16 (Integer, default=0) Determines whether an MSC.Marc t16 file will be created for SOL 600 (Note: If a t16 file is not produced, op2, xdb, punch cannot be produced either).

0 A t16 file will be created

1 A t16 file will not be created. Do not specify this option if eigenvalue analysis is performed or if parallel processing is performed or MSC.Marc will fail with exit 13. Only advanced users wishing to save disk space and having some alternate method of postprocessing the output should use this option.

PARAM,MRFOLLO2 (Integer, default=1) Controls whether MSC.Marc’s follow for, 2 is used when multiple subcases are present.

0 MSC.Marc’s follow for, 2 will not be used when multiple subcases are present.

1 MSC.Marc’s follow for, 2 will be used when multiple subcases are present.

PARAM,MRORINTS (Integer, default=1) Controls orientation type for all solid elements in model (see MSC.Marc Volume C documentation, ORIENTATION option).


-1 Skip all orientations

1 Edge 1-2

2 Edge 2-3

3 Edge 3-4

4 Edge 3-1

5 Edge 4-1

6 XY Plane

7 YZ Plane

8 ZX Plane

9 XU Plane

10 YU Plane

11 ZU Plane

12 UU Plane

13 UORIENT Define transformation matrix with orient.f user subroutine

14 3D ANISO

Note: For solid composites, it is necessary to use the PSOLID entry as well as the PCOMP entry. The PSOLID entry should normally have an entry in field 4, which specifies a CORDi entry to use for the material alignment direction.

PARAM,MARCOFFT (Integer, default=0) Controls whether Nodal Temperatures are specified at the original or offset grid point or both grid points for beams and shells with offsets.

0 Temperatures are applied both at the original grid point and at the offset grid point.

1 Temperatures are applied at the original grid point only

2 Temperatures are applied at the offset grid point only

-1 Temperature loading is not altered in any way from the Nastran input

Note: Processing time can increase significantly if beam or shell offsets are present and param,marcoftt is zero or greater unless param,moffcore,1 is used.

PARAM,MOFFCORE (Integer, default=1) Determines how memory for param,marcofft above is to be allocated (for increased speed).


-1 Additional memory is not allocated

1 Additional memory is allocated if available

Explicit Nonlinear (SOL 700) Items (Beta Capability)

• Only Windows and Linux can be run using PATH=1 on the SOL 700 entry (this uses a file named dynrun.pth to point to the location of dytran-lsdyna)

• All other systems require PATH=3 or no path on the SOL 700 entry. No path is a special case of PATH=3. They both use the run_dytran script. When PATH=3 is specified, a file named sol700.pth is used for inputs to the script. When no path is specified, the script uses defaults that include a single-processor execution. When no path is specified all defaults including the location of MPI/LAM/POE as applicable must be as the run_dytran script expects. When PATH=3 is specified, the location may be specified in the sol700.pth file.

• MSC highly recommends the use of PATH=1 for Windows or Linux single-processor jobs and PATH=3 for single-processor jobs using other systems. MSC recommends the use of PATH=3 for multiprocessor jobs on all supported computer systems.

• For Linux, MPI-related information is written to /tmp. If the user does not have read/write access to /tmp the job will fail. If the mpi-related information is not cleared out of the /tmp directory before the machine is re-booted, new SOL 700 executions after the re-boot think lamboot has already been accomplished and the run_dytran script will not perform the required lamboot necessary run the job.

• On AIX, POE must be installed where specified in the run_dytran script. In addition, a file named dytran.mpi (which is like a host file) must be created in the same directory as the MSC.Nastran input file. This file must have the host name on as many lines as the maximum number of processors to be used. For an AIX system named turkey, it would look like the following if the maximum number of processors to be used is 4:

turkey turkey turkey turkey

• SGI, HP, Sun, and Alpha appear to run with no anomalies, however mpi must be located where the run_dytran script expects it to be

• For Windows, one of the components to the "script" named anl-mpich.bat must be edited to point to the location where MPICH is installed.

• The correct version of MPI/LAM/POE as applicable must be installed on the each computer to be used including slave nodes for parallel processing. It is presently up to the user or


system administrator to do this. The correct versions to use are the same as for MSC.Nastran except for Linux which needs LAM 7.0.4 and Windows which needs MPICH version 1.2.5. These versions can be obtained from public Internet sites.

• For Windows the following MPICH-related items have been discovered during testing.

o Incorrect machine name and IP address Error Description: Easy_connect::WSAETIMEDOUT error, re-attempting easy_connect (hostname) Error: ConnectToMPD (trainer1:8675): easy_connect failed: error 10060. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. MPIRunLaunchProcess: Connect to trainer1 failed, error 10060 aborting... Possible Causes: - DNS, the service that maps a hostname to an IP address, is incorrect .You can double check by using ping machinename (machine which is being used in the DMP run) ...No response

o Incorrect User Name/Password

Error Description: Failed to launch process 2: '"\\D10206\sol700\\\\dytran-lsdyna.exe "' LaunchProcess failed, LogonUser failed, Logon failure: unknown user name or bad password. aborting... Possible Causes: MPICH requires the following information before starting the job account: username


Documents

Pink Sheet