Page 160 - Using ANSYS for Finite Element Analysis Dynamic, Probabilistic, Design and Heat Transfer Analysis

apDl programming • 147
require help from your ASD in debugging an ANSYS session, he or she
will almost certainly ask to see a copy of your log file.
Each new ANSYS session appends commands to the existing file Job-
name.LOG. (That is, the log file is not overwritten during a new ANSYS
session, but added to.) A “time stamp,” consisting of the current date and
time, is included so that you can identify the start of each session. Use /
FILNAME,1 to start a new log file for the session.
You can list your entire log file during an interactive run by picking
Utility Menu> List> Files> Log File. Since this file is in ASCII format,
you can view and edit it readily using an external text editor.

4.1.1.2 Database Command Log

ANSYS captures commands generated (or typed in) during an ANSYS
session not only in the log file but also in memory. This in-memory ver-
sion of the command history is called the internal database log. When you
save the database, the program saves this command log in the database file
(Jobname.DB) along with the other database information.
Use either Utility Menu> File> Write DB Log File or the LGWRITE
command to write the database command log to a named ASCII file. You
can then edit this file, make desired changes, and use the file as command
input to the program. This capability is especially useful if you want to use
the command history that was created during an interactive session, but
have somehow lost or corrupted the session log file (Jobname.LOG) that
was associated with your database.
If you create your database in multiple sessions by saving and resum-
ing the database file, the ANSYS program keeps the database log con-
tinuous by appending each new command that is processed. Therefore,
the internal database log is not fragmented; it will represent the complete
database.

4.1.2 USing A CoMMAnD Log FiLe AS inPUT

The procedure for re-executing the commands contained in a Jobname.
LOG file or in the database log consists of three main steps:

1. Establish the Command Log File
The method to do this depends on whether you use the session log
file or the database log.