PAMCRASH > Files > Files
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
Files
The Patran PAMCRASH Preference uses or creates several files.The following table outlines each file and its uses. In the file name definition, jobname will be replaced with the jobname assigned by the user.
 
File Name
Description
*.db
This is the Patran database. During an analyze pass, model data is read from this database. This file typically resides in the current directory.
jobname.pc
This is the PAMCRASH input file created by the interface. This file typically resides in the current directory.
pat3pam -j
This is the actual forward translation program, translating between the Patran database and a PAMCRASH input file. It is typically run within Patran, transparent to the user, but can also be run independently. For example:
<installation_directory>/bin/exe/pat3pam -j my_job -d my_database.db > my_job.msg &
Patran searches its file path for this file, but it typically resides in the <installation_directory>/bin/exe directory.
pat3pam -i
This is the PAMCRASH input file reader program. It is typically run within Patran, transparent to the user, but can also be run independently with the following command;
<installation_directory>/bin/exe/pat3pam -i my_deck.pc -d my_database.db > my_job.msg &
Patran searches its file path for this file, but it typically resides in the <installation_directory>/bin/exe directory.