The forms of many Patran applications depend upon analysis code specific definitions contained within the Patran database. These analysis code sensitive applications are Loads and Boundary Conditions, Element Properties, Material Properties and Finite Elements (multi-point constraint equations, available element topologies and element verification). The analysis code specific definitions that they depend upon define element types, element properties, material properties, multi-point constraint equations, loads and boundary conditions and element verification parameters.

Two versions of the Patran database are delivered in the $P3_HOME directory, “template.db” and “base.db”. The “template.db” contains analysis code specific definitions for selected MSC supported interfaces (e.g., Patran MSC.Marc, Patran MSC Nastran, etc.). “base.db” is basically devoid of analysis code specific definitions but does contain some basic definitions. The definitions which are stored in “base.db” are Analysis type, Loads and Boundary Conditions and the association between Loads and Boundary Conditions and all the MSC supported interfaces.

Due to the excessive size of “template.db,” it is highly recommended that the user create his own unique template database which contains only the analysis code specific definitions pertaining to the analysis codes of immediate interest to him. He can call this new template database “<analysis_code>.db,” (e.g., “nastran.db” and can use it as the template for all new databases). See File>New (p. 68) in the Patran Reference Manual. This would produce considerably smaller and simpler databases then would the use of “template.db”.

MSC supplies PCL functions which will add analysis code specific definitions for each of the MSC supplied interfaces to any Patran database. Use of these functions is described in Loading Definitions for MSC Supported Preferences, 451.

Alternatively, the user can define his own analysis code specific definitions in order to create a new interface to Patran. The majority of this chapter is dedicated to teaching the user how to create his own interface.