Recent Changes

Install a New Network License (Microsoft Windows)

admin — 2012-05-03T11:55:16Z

INSTALL THE LICENSE SOFTWARE: Create a folder under Windows where you would like to install the LSTC License Manager. Download the most recent self-contained installation program LSTC_LicenseManager_64789_win.exe into the installation folder you have created. You must run this program as Administrator; otherwise the installation will fail to create the required LSTC License Manager service. A typical installation is documented on this web page. More information can be found in the complete PDF Installation Guide.
When you run the installation program for the first time, you will see the contents of the archive, and the option to create a new installation:

Select the BROWSE option to locate the desired installation folder, and then hit the INSTALL button. If there are no errors, then a browse window will appear showing the full contents of the installation folder.

If there are no installation errors, then close the original installation program, but leave the browse window open.
GENERATE A LICENSE REQUEST: In the browse window choose to run LSTCLMUI. Ignore the warning that no server has been found. Once LSTCLMUI opens, select the tab Request a License.

Enter your LICENSE INFORMATION. Once you have finished, press the GENERATE button. A browse window will appear, allowing you to choose a convenient location (such as the Desktop) to save the license request file LSTC_SERVER_INFO. You may now close the LSTCLMUI program.

You must attach this file to your license request email addressed to your local LS-DYNA distributor. Include any information that is needed to generate a license. For example, default ranges of IP addresses are automatically included in LSTC_SERVER_INFO, but you may require that LS-DYNA license requests originating from other IP address ranges be allowed. If that is the case, then be sure to specify those IP ranges in your email license request.
INSTALL THE LICENSE: Your LS-DYNA distributor will return a license file for you installation. This license file has to be renamed to server_data, and it must be saved to the original installation folder. After you have saved the license file to the installation folder, then open the LSTCLMUI program as Administrator. Choose the LSTCLM Service for Windows tab. You should see that the Service has been installed, but not yet started. (It cannot start without a valid license file.)

You should now start the service by pressing the Start button. Be patient. It may take 10-15 seconds for the service to start, and for LSTCLMUI to verify that it has started. The service status will be automatically updated to RUNNING if there are no errors:

If there are errors, then a message should be logged to the Windows Event Log, which can be opened from Windows, or by pressing the Open Windows Event Log button in LSTCLMUI program (shown above.) Contact LSTC license support if you cannot resolve a start-up error,
VERIFY THE LICENSE: Open the LSTC Licenses tab in the LSTCLMUI program. Now that the server is running, you should see information about the server that is currently running: Server information is displayed while in this tab by pressing the Server Info button.

Press the License Summary button in order to display a complete list of licenses managed by your server. Verify that the number of licenses and the expiration dates are correct.
FIREWALL AND PORT ISSUES: The LSTC License Manager listens on TCP and UDP ports 31010 by default. So, you must make sure that the Windows firewall allows incoming traffic on those ports. Otherwise LS-DYNA programs running on other machines will be unable to acquire a license to run. You may change this port by adding a line to the "server_data" license file. Directly beneath the line with starts with "SERVER:", add the following line
```
        PORT: N
```
where "N" is the integer port number. If you do change this port number, then you should also create a file named "LSTC_FILE" in the same directory with the line
```
        #LICENSE_SERVER: N@localhost
```
The hash '#' must start in the first column of the line, and there should be no extra white space. Adding this entry compensates for an error in the current version of the LSTCLMUI utility, and will not be necessary in versions after 64789. Adding this entry forces "N@localhost" to appear in the list of servers from which to select.

Install a New Network License (Linux/Unix/Solaris)

admin — 2012-05-03T11:32:42Z

INSTALL THE LICENSE SOFWARE: If you have purchased a new network license for LS-DYNA, then you should decide where you want to run the license server. The LSTC License Server may reside on a Linux, Unix, Solaris, or Microsoft Windows platform. All versions of LS-DYNA may acquire permission to run from this server, regardless of architecture or OS. A typical installation is found on this web page. More information can be found in the complete PDF Installation Guide.

Choose a stable machine in order to minimize license down-time. Then download the LSTC Network License software for the machine which will run the license server. It is generally easier to install, upgrade and administer network licenses if the LSTC License Server is installed under the Microsoft Windows OS. However, those familiar with Unix/Linux/Solaris should not find it difficult to administer licenses on these platforms.

Once you have chosen a platform on which to install the LSTC License Server, then download the LSTC License Software for the chosen target architecture.

HARDWARE	OS	ARCHIVE
HP/ALPHA	OSF1 5.1a	LSTC_LicenseManager_64789_alpha_51a.tgz
HP/PA8000	HPUX 11.0	LSTC_LicenseManager_64789_hp8000_11.tgz
HP/Itanium2	HPUX 11.0	LSTC_LicenseManager_64789_ia64_hp11.tgz
IBM/Power4	AIX 5.2	LSTC_LicenseManager_64789_ibmpwr4_aix52.tgz
IBM/Power5	AIX 5.3	LSTC_LicenseManager_64789_ibmpwr5_aix53.tgz
SGI	IRIX 6.5	LSTC_LicenseManager_64789_sgi_irix64.tgz
SUN SPARC	SUNOS 5.8-5.9	LSTC_LicenseManager_64789_sun_58.tgz
AMD Opteron	RedHat AS4.0	LSTC_LicenseManager_64789_amd64_redhat40.tgz
INTEL/Itanium2	SuSE 9	LSTC_LicenseManager_64789_ia64_suse9.tgz
INTEL/AMD	SuSE 11.2	LSTC_LicenseManager_64789_xeon64_suse11.tgz
INTEL/AMD	SuSE 11.4	LSTC_LicenseManager_64789_xeon64_suse114.tgz
INTEL/AMD	RedHat AS5.0	LSTC_LicenseManager_64789_xeon64_redhat50.tgz
INTEL/AMD	RedHat RHEL 3-5	LSTC_LicenseManager_64789_ia32_redhat30.tgz
INTEL/AMD	SuSE 9-10	LSTC_LicenseManager_64789_ia32_redhat30.tgz
INTEL/AMD	MS Windows 32/64-bit	LSTC_LicenseManager_64789_win.exe

After downloading the appropriate archive, choose a directory where you want to install the license server, move the archive to the installation directory, and cd into that directory. Then unpack the archive into the installation directory. For example,

        gunzip LSTC_LicenseManager_64789_alpha_51a.tgz
	tar xvf LSTC_LicenseManager_64789_alpha_51a.tar

You should now see the following files in the installation directory

        lstc_server     lstc_proxy     lstc_client
        lstc_qrun       lstc_vrun      lstc_qkill
        lstc_logreport  gmid

GENERATE A LICENSE REQUEST: Run lstc_server with the info command line option in order to generate a license request form
```
        ./lstc_server info
```
The server will print the following message to the terminal, indicating that it has created the sample request form LSTC_SERVER_INFO:
```
        Getting server information ...

        The hostid and other server information has been written to LSTC_SERVER_INFO.
        Please contact your local LS-DYNA distributor with this information to obtain a valid network license
```
You will need to edit the top portion on this file, which looks like
```
        Your Company Name Here
            EMAIL: NONE
              FAX: NONE
        TELEPHONE: NONE
        #
        SERVER: E3707F52
        # Linux desktop 2.6.31.12-0.1-desktop #1 SMP PREEMPT 2010-01-27
        # Host ID       : e3707f52
        #
        ALLOW_RANGE:  XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX
        #
```
Replace "Your Company Name Here" with the name of your company or organization. Specify the EMAIL address and TELEPHONE number of the primary technical contact for your organization. FAX is optional. The ALLOW_RANGE statement is required so that licenses are locked to your local network. You may specify any number of such statements such as
```
        ALLOW_RANGE: 127.000.000.001 127.000.000.001 (recommended)
        ALLOW_RANGE: 192.168.053.000 192.168.053.255
        ALLOW_RANGE: 192.168.054.000 192.168.054.127
```
After you have completed editing the license request form, please send your key request to your local LS-DYNA distributor along with any other information which is needed to fulfill your license request.
START/STOP THE LICENSE SERVER: Your LS-DYNA distributor will send you a license file for your installation. Rename this license file to 'server_data' and then place this file in the server installation directory specified in (2). It is recommended that you specify a log file for job reporting. Human-readable entries are created in the log file for each job as it starts and stops. Any errors which occur during licensing will result in error/warning log entries. Use the following command to create a lot file named lstclm.log in the current working directory:
```
        ./lstc_server -l lstclm.log
```
The server runs in the background by default. The server automatically creates a kill script which may be used to kill the server.
```
        ./server_kill
```
The server also saves the last start-up arguments in a file named "server_start", so that you may restart the server using the previous set of command line arguments, without having to remember them.

NOTE: Make sure that the user who runs the server has permission to create/edit/remove any specified log file and script files "server_start" and "server_kill". The server must also create/edit status files "server_status" and "server_done_list".
VERIFY THE INSTALLATION: Make sure the license server is running.
```
        ./lstc_qrun -s localhost -r
```
You should see a full table of products that you have licensed, complete with (a) numbers of licenses and (b) exiration dates. Verify that the information is correct. If the server does not start for some reason, then you will see the message
```
        *** ERROR failed to open server localhost
```
In that case, try starting the server in the foreground using the -f command line option. The server should print verbose information about the cause of failure. If you cannot correct the problem on your own, then contact your LS-DYNA distributor for license key support.
FIREWALL SETTINGS: By default, the license server listens on port 31010 (both UDP and TCP/IP.) So you must configure any firewall on the license server machine to allow inbound data/connections on these ports. You may choose a different port for the server by adding a "PORT:" entry into the license file. For example, if you would like to use port 31111, then add the following "PORT:" entry into "server_data" directly beneath the "SERVER:" line:
```
        SERVER: E3707F52
        PORT: 31111
```
*** WARNING *** Changing other lines in the file may invalidate the license file.

If you change the default port number, then all utilities (as well as LS-DYNA) require that you manually set the port number. For example, you will need to specify the port for "lstc_qrun"
```
        ./lstc_qrun -s 31111@localhost -r
```
Adding a file named LSTC_FILE to the server installation directory with the following line will eliminate the need to specify a default port/host name for the license utilities. This will make it easier to administer licenses:
```
	#LICENSE_SERVER: port@host_or_ip

    or (if using the default port)

	#LICENSE_SERVER: host_or_ip
```
However, this only affects the behavior of "lstc_qrun" and other utilities if you run the particular utility located in the server installation directory. Instead of running "./lstc_qrun -s 31111@localhost -r", you may now run "./lstc_qrun -r" Of course, you may override the default in LSTC_FILE by specifying the -s command line option.

LS-DYNA 971 Manual Vol I - Keyword

admin — 2012-04-06T22:00:00Z

LS-DYNA 971 Manual Vol II - Material Models

admin — 2012-04-06T22:00:00Z

Contact Energy

Guido Pietsch — 2012-04-24T17:05:00Z

In LS-DYNA, contact energies are reported in the SLEOUT file.

Therein, four different values can be found:

slave energy (SE)
master energy (ME)
frictional energy (FE)
sum of slave/master and frictional (SoSMF) = SE + ME + FE

The 'Sliding Energie' included in the GLSTAT equals the sum of slave, master and frictional energy (SoSMF) from the SLEOUT.

Note: The frictional energy is included in the sum of slave/master energy.

If friction is defind, e. g. in the *CONTACT_... via FS and FD, the resulting energy can be found in the database variable frictional energy (FE). Thus, one gets the energy needed to prevent penetration between the contact partners by subtracting the frictional energy from the sum of slave/master energy (SoSM). In the absence of friction the slave and master side energies should be close in magnitude but opposite in sign. The sum of slave/master energy (SoSM) should equal the stored energy.

Positive contact energy:

When friction is included in a contact definition, positive contact is to be expected. Friction SHOULD result in positive contact energy. In the absence of friction, you would hope to see a small net contact energy (net = sum of slave side energy and master side energy). Small is a matter of judgement -- 10% of peak internal energy might be considered acceptable for contact energy in the absence of contact friction.

Negative contact energy:

Abrupt increases in negative contact energy may be caused by undetected initial penetrations. Care in defining the initial geometry so that shell offsets are properly taken into account is usually the most effective step to reducing negative contact energy. Refer to sections 23.8.3 and 23.8.4 in the LS-DYNA Theory Manual (May 1998) for more information on contact energy.

Negative contact energy sometimes is generated when parts slide relative to each other. This has nothing to do with friction. I'm speaking of negative energy from normal contact forces and normal penetrations. When a penetrated node slides from its original master segment to an adjacent though unconnected master segment and a penetration is immediately detected, negative contact energy is the result.

If internal energy mirrors negative contact energy, i.e., the slope of internal energy curve in GLSTAT is equal and opposite that of the negative contact energy curve, it;s possible that the problem is very localized with low impact on the overall validity of the solution. You may be able to isolate the local problem area(s) by fringing internal energy of your shell parts (Fcomp > Misc > internal energy in LS-PrePost). Hot spots in internal energy usually indicate where negative contact energy is focused.

If you have more than one contact defined, the sleout file (*DATABASE_SLEOUT) will report contact energies for each contact and so the focus of the negative contact energy investigation can be narrowed.

Some general suggestions for combating negative contact energy are as follows:

Eliminate initial penetrations (look for Warning in messag file).
Check for and eliminate redundant contact conditions. You should NOT have more than one contact definition treating contact between the same two parts or surfaces.
Reduce the time step scale factor.
Set contact controls back to default except set SOFT=1 and IGNORE=1 (Optional Card C).
For contact of sharp-edged surfaces, set SOFT=2 (applicable for segment-to-segment contact only). Furthermore, in v. 970, setting SBOPT (formerly EDGE) to 4 is recommended for SOFT=2 contact where relative sliding between parts occurs. For improved edge-to-edge SOFT=2 contact behavior, set DEPTH to 5. Please note that SOFT=2 contact carries some additional expense, particularly using nondefault values of SBOPT or DEPTH, and so should be used only where other contact options (SOFT=0 or SOFT=1) are inadequate.

The specifics of your model may dictate that some other approach be used.

Car Hitting a Standing Dummy Sideways

Guido Pietsch — 2010-01-10T23:25:00Z

Hello Dyna Dummy Users Worldwide:

This mail pertains to the Standing Dummy Model sent out on Monday, 4th January, 2010. I have prepared a model containing a "Small Car Hitting the Standing Dummy Sideways". Please download it using the following Link:

ftp://user:computer@ftp.lstc.com/lstc-dummies/LearningAidCarHittingStandingDummy100105.zip

Note:

Our Date Naming Convention has now become yy/mm/dd. In the Dummy Name "10" is for the year 2010, "01" is for January and "05" is the day. This model is for demonstration purposes only and has no reality to it. It has been prepared to serve purely as a Learning Aid.

The following are the salient points to note:

Please unzip it in a separate directory. You will find the following contents:

dyna.SubmitMeToRunJob.k
MetroR-V02c-NCAC-GWU_CarModel.Modified.k
LSTC.H3.091223_STANDING_BETA.RigidFE.50th.2Moffset.PositionedSideways.k
README
FullViewOfCarStrikingPedestrian.avi
CloseUpOfFeetInCarStrikingPedestrian.avi

To run the job, just submit the file "dyna.SubmitMeToRunJob.k" . The Car and the Dummy Files are "included" in it.
The original Standing Dummy has been "positioned" for this model and its IDs Offset by 2-Million (2000000).
The Car Model was downloaded from the NCAC & GWU website. For those who are not aware, the following is the link to their greatly useful and informative public domain website: http://www.ncac.gwu.edu/vml/models.html There are many models that have been built over the years and kept there for general purpose usage. It is an invaluable resource site to be aware of. We would all like to thank NCAC & GWU for this this enormous service rendered to the worldwide community free of charge.
The Car Model I downloaded has only 16,100 Elements. Date Posted: Year 2000, October 21 It turned out ideal for my demonstration purpose in this case.
I had to make small adjustments to the original to run Time-0. After that I ran "Unit Transformation" to change their Units of "mm, tonnes, seconds and N" to our preferred units of "mm, kg, ms and kN". I applied an arbitrary uniform Velocity of 13.6 mm/msec or about 30-mph. Other minor modifications to parts of the structure were made to suit my purpose.
Please read the README file for some useful information.
Please read the Header Notes contained within these files.
In the Car Model, in addition to the Header Notes, please read the notes that I have written just above the "*INITIAL_VELOCITY" card. Please pay special attention to what I have used for "NSID" and "IRIGID" in the Velocity Card. I wish to write a separate mail, explaining the different usages of IRIGID for this kind of model. In that I will write about how the same end-result can be obtained by using different methods and also, what will work and what will not work. I believe this is very important for everyone to understand.
You can view the two "avi" files that I have given to get a quick glimpse of what to expect if you run the model. I have defined the Ankles with Spherical Joints for better rotation for a Sideways Hit. I have attached a "close-up avi" to show how the feet respond to this kind of hit. In the near future, I would like to define the Ankles of the "5th/50th/95th% H-III Rigid-FE Dummy Models" with Spherical Joints also, for all purpose response. The fact that they are defined via Revolute Joints now creates "somewhat of a constraint" in the most general case of loading, though they do serve the purpose well enough in most cases that we encounter daily for the H-III. The Standing Dummy Model has extra contacts defined between the various limbs, just to take into account the sideways hit. Please load the Dummy Model separately in LSPP and step through the contact definitions one by one to see what I have done.
Please note that I do not know any of the details of the Car Model. I just used it for my purpose. Any specific questions about the model itself, may please be directed to the people named on their website.

Please try to learn as much as you can from this combination model. You can then easily replace my car model with any other specially designed car, barrier or object, to strike the dummy in your particular mode of analysis.

Please be on the lookout for one more mail explaining Point (9) in the notes above.

Upgrade a Network License (Microsoft Windows)

admin — 2012-04-24T20:59:30Z

REPLACE THE LICENSE FILE: Locate the existing license directory. If you do not know where the current LSTC License Manager is installed, then you may open the Service Control Manager in Windows, and locate the "LSTC License Manager" service. The Windows interface to the Service Control Manager is conveniently started by running the following command from Windows:
```
        services.msc
```
Then browse the list of services to find the "LSTC License Manager".

If you open the "LSTC License Manager," then you will see the full path to the "lstclm.exe" executable, which is also the location of the LSTC License Manager installation, where the license file "server_data" must be located. Browse to this location, and rename the existing license file "server_data" to "server_data.old". Copy the new "server_data" license file to the installation directory.

*** WARNING *** If you have modified the previous "server_data.old" file to include lines which start with HOST:, HOST1:, HOST2:, HOST3:, PORT:, PORT1:, PORT2:, or PORT3:, then you must manually copy these lines to the new "server_data" license file. Otherwise, the server will start on a wrong port, and LS-DYNA will be unable to acquire a license.
UPGRADE THE LICENSE SOFTWARE (optional): Download the LSTC License Manager Software for Windows from your LS-DYNA distributor. This archive is an executable installation program which should be saved to the installation location. After the file has been saved, then right-click on the archive to start the program "LSTC_LicenseManager_64789_win.exe" as Administrator. Choose the upgrade option, and check the box to "Stop, upgrade and restart the current server" (this box will appear only if the service is currently running.)

If errors occur at this point, then contact your LS-DYNA distributor for license support. If there are no errors, then a browse window will appear showing the full contents of the installation folder:

You may now close the installation program, but leave open the browser window.
VERIFY THE INSTALLATION: If you just upgraded the license software, then you already have a browse window open to the installation folder. If not, then browse to the LSTC License Manager service installation folder. Right click on the LSTCLMUI program and select Run as Administrator. Ignore any warning that no server has been found. Select the "LSTCLM Service for Windows" tab in the LSTCLMUI program.
If you did not choose to upgrade the LSTC License Manager software, then you must stop and restart the LSTC License Manager service in order to pick up the new "server_data" license file. If the service was not running when you performed the upgrade, then you must start the service. These options are available in the current tab. You should then verify that the service status is RUNNING:
VERIFY THE LICENSE: Open the LSTC Licenses tab in the LSTCLMUI program. Now that the server is running, you should see information about the server that is currently running: Server information is displayed while in this tab by pressing the Server Info button.

Press the License Summary button in order to display a complete list of licenses managed by your server. Verify that the number of licenses and the expiration dates are correct.

Beam

Guido Pietsch — 2012-04-24T17:15:25Z

If you want to input A, Iss, etc. directly, you must use a resultant beam formulation, i.e., ELFORM=2. With such a formulation, stresses are not calculated because the shape of the cross-section is unknown. You'll only get forces and moments. ELFORM=2 is compatible with only a few material types. See the material table at the beginning of the *MAT section of the Users Manual.

ELFORM=1 is an integrated beam formulation. With an integrated formulation, the shape of the cross-section is defined in the input and so stresses can be computed at the beam integration points. The parameter CST on Card 1 of *SECTION_BEAM indicates whether the section is circular or rectangular. You must give cross-section dimensions on Card 2 of *SECTION_BEAM.

For circular sections, you give outside and inside diameters at the two ends. (For a solid circular section, the inside diameter is zero.) For solid rectangular sections, you give the cross-section width and breadth at the two ends.

For hollow rectangular tubes, it's a bit trickier as you must also use *INTEGRATION_BEAM which is referenced by setting QR/IRID in *SECTION_BEAM to -IRID, where IRID is given in *INTEGRATION_BEAM. In *INTEGRATION_BEAM, you can leave NIP and RA blank and set ICST to 5. On Card 2 of *INTEGRATION_BEAM, give the 4 values W, TF, D, and TW which are shown in the figure in the Users Manual. If QR/IRID in *SECTION_BEAM is negative, it follows that *INTEGRATION_BEAM defines the location of the integration points. If QR/IRID is positive and CST is zero (rectangular section), refer to the Figure 5.3 on p. 5.11 of the 2006 Theory Manual. If the integration rule is 2x2, 3x3, or 4x4 Gaussian, the locations of the integration points shown in Figure 5.3 are in accordance with the columns labeled as 2 point, 3 point, and 4 point, resp., in the table under *SECTION_SHELL in the Users Manual. Integration points for a circular cross-section are positioned sequentially in the circumferential direction of the cross-section, all at the same distance from the cross-section center. For example, for 3x3 Gauss quadrature, the nine integration points in the cross-section are 40 degrees apart with the first integration point on a ray 20 degrees off the local s-axis (toward the t-axis). The radial position of the integration points for a solid circular cross section is at r = 0.707 * the outside radius.

You can get axial strain at beam integration points by setting BEAMIP (*DATABASE_EXTENT_BINARY) to the number of beam integration points in your LS-DYNA input deck. Then, after running the model, read D3PLOT into LS-PrePost and click History > Int.Pt. > Etype: Beams > (click on any beam element) > Axial Strain > Plot.

Also, plastic strain at beam integration points is written to elout (see *DATABASE_HISTORY_BEAM and *DATABASE_ELOUT).

Upgrade a Network License (Linux/Unix/Solaris)

admin — 2012-04-24T12:45:56Z

UPDATE THE LICENSE FILE: Find the existing LSTC License Manager software installation directory, and 'cd' into this directory. The existing installation directory will contain the LSTC License Manager executable "lstc_server", as well as an existing license file "server_data". Move the existing license file to a new name
```
        mv server_data server_data.old
```
Copy the new "server_data" license file obtained from your LS-DYNA distributor into the current directory. When the server is restarted next, it will pick up the new license file. Check the permissions and ownership of this file in order to guarantee that the license server will be able to read the new license file. The best practice is to match the permissions and ownership of the old license data.
*** WARNING *** If there are any user-specified lines in the previous license file, then you must manually copy these lines into the new license files. Such lines start with HOST:, HOST1:, HOST2:, HOST3:, PORT:, PORT1:, PORT2: and PORT3:.

UPGRADE THE LICENSE SOFTWARE (optional): We recommend that you upgrade the license server at the same time that you obtain a new license file from your LS-DYNA distributor. Regardless of whether or not you upgrade the existing license software, you must stop and restart the license server whenever you obtain a new license. If the server is down for a few minutes only, then running licenses should not be lost in the process.

HARDWARE	OS	ARCHIVE
HP/ALPHA	OSF1 5.1a	LSTC_LicenseManager_64789_alpha_51a.tgz
HP/PA8000	HPUX 11.0	LSTC_LicenseManager_64789_hp8000_11.tgz
HP/Itanium2	HPUX 11.0	LSTC_LicenseManager_64789_ia64_hp11.tgz
IBM/Power4	AIX 5.2	LSTC_LicenseManager_64789_ibmpwr4_aix52.tgz
IBM/Power5	AIX 5.3	LSTC_LicenseManager_64789_ibmpwr5_aix53.tgz
SGI	IRIX 6.5	LSTC_LicenseManager_64789_sgi_irix64.tgz
SUN SPARC	SUNOS 5.8-5.9	LSTC_LicenseManager_64789_sun_58.tgz
AMD Opteron	RedHat AS4.0	LSTC_LicenseManager_64789_amd64_redhat40.tgz
INTEL/Itanium2	SuSE 9	LSTC_LicenseManager_64789_ia64_suse9.tgz
INTEL/AMD	SuSE 11.2	LSTC_LicenseManager_64789_xeon64_suse11.tgz
INTEL/AMD	SuSE 11.4	LSTC_LicenseManager_64789_xeon64_suse114.tgz
INTEL/AMD	RedHat AS5.0	LSTC_LicenseManager_64789_xeon64_redhat50.tgz
INTEL/AMD	RedHat RHEL 3-5	LSTC_LicenseManager_64789_ia32_redhat30.tgz
INTEL/AMD	SuSE 9-10	LSTC_LicenseManager_64789_ia32_redhat30.tgz
INTEL/AMD	MS Windows 32/64-bit	LSTC_LicenseManager_64789_win.exe

After downloading the software archive which is appropriate for your platform, move the archive into the current installation directory. In preparation for the upgrade, rename the existing license server executable:

        mv lstc_server lstc_server.old

Now unpack the new software archive. For example,

        gunzip LSTC_LicenseManager_64789_hp8000_11.tgz
        tar xvf LSTC_LicenseManager_64789_hp8000_11.tar

Check the permissions on the LSTC License Manager executable "lstc_server" in order to ensure that the server will start properly.

STOP AND RESTART THE SERVER: You will now have a new license file "server_data" and, optionally, a new server executable "lstc_server".

If there are start and kill scripts "server_start" and "server_kill" in the current working directory, then execute them in order
```
        ./server_kill ; ./server_start
```
The new server should now be running, which you can verify using
```
        ./lstc_qrun -q
```
If this does not work, then check "server_data" for any non-standard port number "PORT:" spec, and connect directly to this port
```
        ./lstc_qrun -s port@localhost -q
```
The output from this command will include the version number of the server. If this server number does not match the version number on the archive you just downloaded, then the server_kill script failed. In that case, then proceed to the next case, ignoring the scripts "server_start" and "server_kill".

If you do not have "server_start" and "server_kill" scripts in the current working directory, find the PID of the "lstc_server" process, and use that PID to kill the process manually
```
        ps -lef | grep lstc_server
        kill -TERM PID
```
Then start the process manually
```
    SYNTAX:  ./lstc_server [-l job_log_file_name] [-a|-n|-N] [-q]
        where the command line options are
          -l file : log job request/completion/error/warrning to 'file'
               -a : Allow programs to be killed by anyone.
               -n : Allow programs to be killed based on user name alone (default).
               -N : Require user/host to match in order to kill jobs.
               -q : Do not allow programs to be queued when there are
                    no available licenses.
```
The start options will be saved to a new script "server_start" so that you may restart the server using the "server_start" script.
VERIFY THE NEW LICENSES: You should be able to contact the license server directly using
```
        ./lstc_qrun -r
```
If this command fails, then look for any non-standard port numbers for your server which are specified in "server_data", and try to connect to the port directly
```
        ./lstc_qrun -s localhost -r    or   ./lstc_qrun -s port@localhost
```
*** WARNING *** If the new server fails to start for some reason, then restore the older server, start the old server, and contact your LS-DYNA distributor.
```
        mv lstc_server lstc_server.new
        cp lstc_server.old lstc_server
        ./lstc_server [-l job_log_file_name] [-a|-n|-N]
```

LS-DYNA 960, manual for keyword format volume #1

admin — 2008-03-01T23:00:00Z

LS-DYNA 960, manual for structured format

admin — 2008-02-29T23:00:00Z

LS-DYNA 960, manual for keyword format volume #2

admin — 2008-03-02T23:00:00Z

LS-DYNA 970, manual for keyword format

admin — 2008-03-31T22:00:00Z

LS-DYNA 970 update

admin — 2008-04-01T22:00:00Z

LS-DYNA 971

admin — 2008-06-02T22:00:00Z