patran 2012 doc analysis manager user
Post on 01-Jun-2018
226 Views
Preview:
TRANSCRIPT
-
8/9/2019 Patran 2012 Doc Analysis Manager User
1/278
Patran 2012
Analysis ManagerUser’s Guide
-
8/9/2019 Patran 2012 Doc Analysis Manager User
2/278
Worldwide Webwww.mscsoftware.com
Disclaimer This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with
the terms of such license.
MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not
intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no
liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information
contained herein.
User Documentation: Copyright 2010 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of MSC.Software Corporation is prohibited.
The software described herein may contain certain third-party software that is protected by copyright and licensed from
MSC.Software suppliers. Contains IBM XL Fortran for AIX V8.1, Runtime Modules, (c) Copyright IBM Corporation 1990-2002,
All Rights Reserved.MSC, MSC/, MSC Nastran, MD Nastran, MSC Fatigue, Marc, Patran, Dytran, and Laminate Modeler are trademarks or registered
trademarks of MSC.Software Corporation in the United States and/or other countries.
NASTRAN is a registered trademark of NASA. PAM-CRASH is a trademark or registered trademark of ESI Group. SAMCEF is
a trademark or registered trademark of Samtech SA. LS-DYNA is a trademark or registered trademark of Livermore Software
Technology Corporation. ANSYS is a registered trademark of SAS IP, Inc., a wholly owned subsidiary of ANSYS Inc. ACIS is a
registered trademark of Spatial Technology, Inc. ABAQUS, and CATIA are registered trademark of Dassault Systemes, SA.
EUCLID is a registered trademark of Matra Datavision Corporation. FLEXlm is a registered trademark of Macrovision
Corporation. HPGL is a trademark of Hewlett Packard. PostScript is a registered trademark of Adobe Systems, Inc. PTC, CADDS
and Pro/ENGINEER are trademarks or registered trademarks of Parametric Technology Corporation or its subsidiaries in theUnited States and/or other countries. Unigraphics, Parasolid and I-DEAS are registered trademarks of UGS Corp. a Siemens
Group Company. All other brand names, product names or trademarks belong to their respective owners.
P3:V2012:Z:ANM:Z: DC-USR-PDF
Corporate Europe Asia Pacific
MSC.Software Corporation2 MacArthur PlaceSanta Ana, CA 92707 USATelephone: (800) 345-2078Fax: (714) 784-4056
MSC.Software GmbH Am Moosfeld 1381829 Munich, GermanyTelephone: (49) (89) 43 19 87 0Fax: (49) (89) 43 61 71 6
MSC.Software Japan Ltd.Shinjuku First West 8F23-7 Nishi Shinjuku1-Chome, Shinjuku-KuTokyo 160-0023, JAPANTelephone: (81) (3)-6911-1200Fax: (81) (3)-6911-1201
-
8/9/2019 Patran 2012 Doc Analysis Manager User
3/278
C o n t e n t s
MSC Patran Analysis Manager User’s Guide
1 Overview
Purpose 2
Product Information 3
What is Included with this Product? 4
Integration with MSC Patran 5
How this Manual is Organized 6
2 Getting StartedQuick Overview 8
Enabling/Disabling the Analysis Manager 10
MSC Nastran Submittals 11
ABAQUS Submittals 13
MSC.Marc Submittals 14
Generic Submittals 15
The Main Form 16
UNIX Interface 17
Windows Interface 18
Invoking the Analysis Manager Manually 20
Files Created 23
3 Submit
Introduction 26
Selecting Files 28
Where to Run Jobs 29
-
8/9/2019 Patran 2012 Doc Analysis Manager User
4/278
MSC Patran Analysis Manager User’s Guide
6
Windows Submittal 31
4 Configure
Introduction 34
Disk Space 35
MSC Nastran Disk Space 35
ABAQUS, MSC.Marc, and General Disk Space 38
Memory 40MSC Nastran Memory 40
ABAQUS Memory 42
MSC.Marc and General Memory 44
Mail 46
Time 47
General 49
Restart 53
MSC Nastran Restarts 53
MSC.Marc Restarts 55
ABAQUS Restarts 56
Miscellaneous 58
MSC Nastran Miscellaneous 58
MSC.Marc Miscellaneous 59
ABAQUS Miscellaneous 61
General Miscellaneous 62
5 Monitor
Introduction 68
Running Job 69
Windows Interface 72
Completed Job 75
Windows Interface 76
Host/Queue 78
Job Listing 79
Host Status 80
Queue Manager Log 81
-
8/9/2019 Patran 2012 Doc Analysis Manager User
5/278
7CONTENTS
Full Listing 82
CPU Loads 82
6 Abort
Selecting a Job 86
Aborting a Job 87
UNIX Interface 87
Windows Interface 87
7 System Management
Directory Structure 90
Analysis Manager Programs 92
Analysis Manager Program Startup Arguments 94
Analysis Manager Environment File 100
Organization Environment Variables 103
Installation 107
Installation Requirements 107
Installation Instructions 108
X Resource Settings 111
Configuration Management Interface 113Modify Configuration Files 116
Test Configuration 134
Queue Manager 143
Examples of Configuration Files 146
Starting the Queue/Remote Managers 155
Starting Daemons at Boot Time 156
8 Error Messages
Error Messages 162
9 Application Procedural Interface (API)
Analysis Manager API 194
-
8/9/2019 Patran 2012 Doc Analysis Manager User
6/278
MSC Patran Analysis Manager User’s Guide
8
Analysis Manager Application Procedural Interface (API) Description 194
Include File 204
Example Interface 230
-
8/9/2019 Patran 2012 Doc Analysis Manager User
7/278
Chapter 1: Overview
Patran Analysis Manager User’s Guide
1Overview
Purpose 2
Product Information 3
What is Included with this Product? 4
Integration with MSC Patran 5
How this Manual is Organized 6
-
8/9/2019 Patran 2012 Doc Analysis Manager User
8/278
Patran Analysis Manager User’s GuidePurpose
2
Purpose
MD Nastran, MSC.Marc, and MSC Patran are analysis software systems developed and maintained by
the MSC.Software Corporation. MD Nastran and MSC.Marc are advanced finite element analysis
programs used mainly for analyzing complex structural and thermal engineering problems. The core of
MSC Patran is a finite element analysis pre/postprocessor. Several optional products are available with
MSC Patran including advanced postprocessing, interfaces to third party solvers and application
modules. This document describes the MSC Patran Analysis Manager, one of these application modules.
The Analysis Manager provides interfaces within MSC Patran to submit, monitor and manage analysis
jobs on local and remote networked systems. It can also operate in a stand-alone mode directly with MD
Nastran, MSC.Marc, ABAQUS, and other general purpose finite element solvers.
At many sites, engineers have several computing options. Users can choose from multiple platforms or
various queues when jobs are submitted. In reality, the resources available to them are not equal. They
differ based on the amount of disk space and memory available, system speed, cost of computing
resources, and number of users. In networked environments, users frequently do their modeling on local
workstations with the actual analysis performed on compute servers or other licensed workstations.
The MSC Patran Analysis Manager automates the process of running analysis software, even on remote
and dissimilar platforms. Files are automatically copied to where they are needed; the analysis is
performed; pertinent information is relayed back to the user; files are returned or deleted when the
analysis is complete even in heterogeneous computing environments. Time consuming system
housekeeping tasks are reduced so that more time is available for productive engineering.
The Analysis Manager replaces text-oriented submission scripts with a Motif-based menu-driven
interface (or windows native interface on Windows platforms), allowing the user to submit and control
his job with point and click ease. No programming is required. Most users are able to productively use it
after a short demonstration.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
9/278
3Chapter 1: OverviewProduct Information
Product Information
The MSC Patran Analysis Manager provides convenient and automatic submittal, monitoring, control
and general management of analysis jobs to local or remote networked systems. Primary benefits of using
the Analysis Manager are engineering productivity and efficient use of local and corporate network-wide
computing resources for finite element analysis.
The Analysis Manager has its own scheduling capability. If commercially available queueing software,
such as LSF (Load Sharing Facility) from Platform Computing Ltd. or NQS is available, then the
Analysis Manager can be configured to work closely with it.
This release of the MSC Patran Analysis Manager works explicitly with MD Nastran & MSC.Marcreleases up to version 2006, and versions of ABAQUS up to 6.x. It also has a general capability which
allows almost any software analysis application to be supported in a generic way.
For more information on how to contact your local MSC representative see Technical Support, xi.
http://../user_manual/misc/support_forms.pdfhttp://../user_manual/misc/support_forms.pdf
-
8/9/2019 Patran 2012 Doc Analysis Manager User
10/278
Patran Analysis Manager User’s GuideWhat is Included with this Product?
4
What is Included with this Product?
The MSC Patran Analysis Manager product includes the following items:
1. Various executable programs, services or daemons for ALL supported computer platforms which
usually reside in
$P3_HOME/p3manager_files/bin
where $P3_HOME is a variable indicating the , the directory
location of the MSC Patran installation. The main executables are:
• P3Mgr (Graphical User Interface)
• QueMgr (Queue Manager)
• JobMgr (Job Manager)
• NasMgr (MSC.Natran Manager)
• AbaMgr (ABAQUS Manager)
• MarMgr (MSC.Marc Manager)
• GenMgr (General Manager)
• RmtMgr (Remote Manager)
• AdmMgr (Admin Manager - Unix only - part of P3Mgr on Windows)
• TxtMgr (Text User Interface)
• Job_Viewer (Database Job Viewer - Unix only)
2. Template configuration files contained in
$P3_HOME/p3manager_files/default/conf
These configuration files must be modified to fit each new computing environment and network.These and the above executables are described in System Management.
3. Two empty working directories called
$P3_HOME/p3manager_files/default/log$P3_HOME/p3manager_files/default/proj
which are necessary and are used during analysis execution to store various files.
4. This User’s Manual. An on-line version is provided to allow direct access to this information from
within MSC Patran.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
11/278
5Chapter 1: OverviewIntegration with MSC Patran
Integration with MSC Patran
The MSC Patran Analysis Manager can function as a separately run program but is intended to be run
directly from within MSC Patran in a seamless manner when submitting analysis jobs. It is integrated
with MSC Patran such that engineers can submit, monitor and manage their analysis jobs directly from
within the MSC Patran graphical interface. It provides a user-friendly environment to submit analysis
jobs, then monitor and control job execution graphically. It is a distributed, multiple-process application
which runs in a heterogeneous network.
There are various modes in which the Analysis Manager can be invoked. Normally, a user will see a
seamless integration between MSC Patran and the Analysis Manager. Jobs can be submitted, monitoredand aborted simply by setting the appropriate Action in pull down menus available from the Analysis
application form in MSC Patran. When a job is being monitored, the monitoring window or form can be
put away and recalled at any time. The user can even quit MSC Patran and the monitoring window will
remain present until the user closes it.
The full user interface is also available from within MSC Patran simply by pressing a button on the
Analysis application form or from the Tools pull down menu on the main form. This gives access to
change default settings, submit previously created input files, change the default computer host or queue
in which to submit jobs, and many other options which are explained throughout this manual.
The MSC Patran Analysis Manager can also be invoked from the system prompt. This mode of
implementation gives the user maximum flexibility to manage analysis jobs.
P t A l i M U ’ G id6
-
8/9/2019 Patran 2012 Doc Analysis Manager User
12/278
Patran Analysis Manager User’s GuideHow this Manual is Organized
6
How this Manual is Organized
This manual is organized into various chapters, each dealing with certain functions of the product. The
manual includes the following chapter topics:
Overview provides general information and an overview of the features of MSC Patran
Analysis Manager.
Getting Started describes rules for analysis input decks, how to invoke MSC Patran’s Analysis Manager
and gives the details involved in setting up, submitting, monitoring, and aborting an analysis job directly
from within MSC Patran.
Submit describes the use of the job submittal capability from the MSC Patran Analysis Manageruser interface.
Configure describes how to configure various options such as memory, disk space, restarts, time of
submittal, host or queue selection, and a number of other options.
Monitor describes the monitoring capability of jobs, completed jobs, and hosts or queues. The graphical
monitoring window is also described in detail.
Abort describes how to abort running jobs.
System Management details the system management. The individual program executables are described
as well as the necessary configuration files, installation, guidelines and requirements. This chapter is
mainly for the system administrator that must install and configure the Analysis Manager.
Error Messages gives descriptions and solutions to error messages.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
13/278
Chapter 2: Getting Started
Patran Analysis Manager User’s Guide
2Getting Started
Quick Overview 8
Enabling/Disabling the Analysis Manager 10
MSC Nastran Submittals 11 ABAQUS Submittals 13
MSC.Marc Submittals 14
Generic Submittals 15
The Main Form 16
Invoking the Analysis Manager Manually 20
Files Created 23
Patran Analysis Manager User’s Guide8
-
8/9/2019 Patran 2012 Doc Analysis Manager User
14/278
Patran Analysis Manager User s GuideQuick Overview
8
Quick Overview
Before Patran’s Analysis Manager can be used, it must be installed and configured by the system
administrator. See System Management for more on the installation and set-up of the module.
In so doing, the system administrator starts the Analysis Manager’s queue manager (QueMgr) daemon
or service, which is always running on a master system. The queue manager schedules all jobs submitted
through the Analysis Manager. The master host is generally the system on which Patran or an analysis
module was installed, but does not have to be.
The system administrator also starts another daemon (or service) that runs on all machines configured to
run analyses, called the remote manager (RmtMgr). This daemon/service allows for propercommunication and file transfer to/from these machines.
Users that already have analysis input files prepared and are not using Patran may skip to The Main Form
after reviewing the rules for input files for the various submittal types in this Chapter.
When using Patran, in general, the user begins by setting the Analysis Preference to the appropriate
analysis, such as MSC Nastran, which is available from the Preferences pull down menu on the top menu
bar.
9Chapter 2: Getting Started
-
8/9/2019 Patran 2012 Doc Analysis Manager User
15/278
9Chapter 2: Getting StartedQuick Overview
Once the Analysis Preference is set and a proper analysis model has been created in Patran, the user can
submit the job. Generally, the submittal process takes place from the Analysis application form when the
user presses the Apply button. The full interface with access to all features of Patran’s Analysis Manager
is always available, regardless of the Preference setting, from the Tools pull down menu or from the
Analysis Manager button on the Analysis form. The location of the submittal form is explained
throughout this chapter for each supported analysis code.
Patran Analysis Manager User’s Guide10
-
8/9/2019 Patran 2012 Doc Analysis Manager User
16/278
Patran Analysis Manager User s GuideEnabling/Disabling the Analysis Manager
Enabling/Disabling the Analysis Manager
There may be times when it is not desirable or required to submit a job through the Analysis Manager.
In such a case, the user can temporarily disable the Analysis Manager and make use of Patran’s genericsubmittal capability for each analysis code supported. Disabling the Analysis Manager does not change
the user interface at all, i.e., the Analysis Manager button remains on the Analysis form. However when
the Apply button is pressed on the Analysis application form, the job will be submitted via Patran’s
generic submit scripts.
To disable the Analysis Manager, type the following command in Patran’s command window and press
the Return or Enter key:
analysis_manager.disable()
To enable the Analysis Manager after it has been disabled type this command:
analysis_manager.enable()
If a more permanent enabling or disabling of the Analysis Manager is required, the user may place these
commands as necessary in a user’s p3epilog.pcl file. This file is invoked at startup from the user’s
local directory, or home directory, or $P3_HOME in that order, if found.
11Chapter 2: Getting Started
-
8/9/2019 Patran 2012 Doc Analysis Manager User
17/278
p gMSC Nastran Submittals
MSC Nastran Submittals
Any standard MSC Nastran (up to version 2006) problem can be submitted using Patran’s
Analysis Manager. This is accomplished from the Analysis form with the Analysis Preference set toMSC Nastran.
The following rules apply to MSC Nastran run-ready input files for submittal:
The BEGIN BULK and ENDDATA statements must be in the main input file; the one that is specified
when submitting, not in INCLUDE files.
The filename may not have any '.' characters except for the extension. The filename must also begin with
a letter (not a number).
Run-ready input files prepared by Patran follow these rules. Correct and proper analysis files are created
by following the instructions and guidelines as outlined in the Patran Interface to MD Nastran Preference
Guide,.
To submit, monitor, and manage MSC Nastran jobs from Patran using the Analysis Manager, make sure
the Analysis Preference is set to MSC Nastran. This is done from the Preferences menu on the main
Patran form. The Analysis form appears when the Analysis toggle, located on the main Patranapplication switch, is chosen. Pressing the Apply button on the Analysis application form with the
Action set to Analyze, Monitor, or Abort will cause the Analysis Manager to perform the desired
action. A chapter is dedicated to each of these actions in the manual as well as one for custom
configuration of MSC Nastran submittals.
The Analysis Manager generates the MSC Nastran File Management Section (FMS) of the input file
automatically, unless the input file already contains the following advanced FMS statements:
INIT
DBLOCATE
ACQUIRE
DBCLEAN
DBFIX
DBLOAD
DBSETDEL
DBUNLOAD
EXPAND
RFINCLUDE
ENDJOB
ASSIGN USRSOU
ASSIGN USROBJ
ASSIGN OBJSCR
ASSIGN INPUTT2
ASSIGN INPUTT4
in which case the user is prompted whether or not to use the existing FMS as-is, or to have the Analysis
Manager auto-generate the FMS, using what FMS is already present, with certain exceptions.
Patran Analysis Manager User’s Guide12
http://../interfaces/msc_nastran/nastran_print.pdfhttp://../interfaces/msc_nastran/nastran_print.pdfhttp://../interfaces/msc_nastran/nastran_print.pdfhttp://../interfaces/msc_nastran/nastran_print.pdf
-
8/9/2019 Patran 2012 Doc Analysis Manager User
18/278
y gMSC Nastran Submittals
The question asked is:
This file contains advanced FMS statements. Do you want to bypass
the Patran Analysis Manager auto-FMS capability?Answer NO to auto-generate FMS; answer YES to use existing FMS. Typically you would answer YES
to this question unless you are fully aware of the FMS in the file.
With FMS automatically generated, each logical database is made up of multiple physical files, each with
a maximum size of 231 bytes (the typical maximum file size), up to the disk space currently free, or until
the size limit requested in the Analysis Manager is met. Large problems requiring databases and scratch
files larger than 231 bytes can, therefore, be run without the user having to add ANY FMS statements.
But this requires that you do not bypass the auto-FMS capability.
If multiple file systems have been defined, the Analysis Manager will generate FMS (provided the input
file does not contain advanced FMS or the user wishes to use the Analysis Manager’s automatic FMS
capability along with his advanced file) so that the scratch and database files are split onto each file
system defined, according to the free space available at run time. See Disk Space for more information.
Restarts are handled by the Analysis Manager in the following manner: the needed FMS is generated so
that the restart run will succeed. If database files exist on the local machine, they are copied to the
analysis machine prior to execution; otherwise, they are expected to exist already in the scratch areas.
Any ASSIGN, MASTER statements are changed/generated to ensure MSC Nastran will locate pre-
existing databases correctly. See Restart for more information.
13Chapter 2: Getting Started
-
8/9/2019 Patran 2012 Doc Analysis Manager User
19/278
ABAQUS Submittals
ABAQUS Submittals
Any standard ABAQUS (up to version 6.x) problem can be submitted using Patran’s Analysis Manager.
This is accomplished from the Analysis form with the Analysis Preference set to ABAQUS.
The following rules apply to ABAQUS run-ready input files for submittal:
1. The filename may not have any '.' characters except for the extension. The filename must begin
with a letter (not a number).
2. The combined filename and path should not exceed 80 characters.
Run-ready input files prepared by Patran follow these rules. Correct and proper analysis files are created
by following the instructions and guidelines as outlined in the Patran Interface to ABAQUS Preference
Guide.
To submit, monitor, and manage ABAQUS jobs from Patran using the Analysis Manager, make sure the
Analysis Preference is set to ABAQUS. This is done from the Preferences menu on the main form. The
Analysis form appears when the Analysis toggle, located on the Patran application switch, is chosen.
Pressing the Apply button on the Analysis application form with the Action set to Analyze, Monitor,
or Abort will cause the Analysis Manager to perform the desired action. A chapter is dedicated to each
of these actions in the manual as well as one for custom configuration of ABAQUS submittals.
If multiple file systems have been defined, the Analysis Manager will generate aux_scratch and
split_scratch parameters appropriately based on current free space among all file systems for the
host on which the job is executing. See Disk Space for more information.
Restarts are handled by the Analysis Manager by optionally copying the restart (.res) file to the
executing host first, then running ABAQUS with the oldjob keyword. See Restart for more
information.
Patran Analysis Manager User’s GuideMSC Marc Submittals
14
http://../interfaces/abaqus/abaqus_print.pdfhttp://../interfaces/abaqus/abaqus_print.pdfhttp://../interfaces/abaqus/abaqus_print.pdfhttp://../interfaces/abaqus/abaqus_print.pdf
-
8/9/2019 Patran 2012 Doc Analysis Manager User
20/278
MSC.Marc Submittals
MSC.Marc Submittals
Any standard MSC.Marc (up to version 2006) problem can be submitted using Patran’s Analysis
Manager. This is accomplished from the Analysis form with the Analysis Preference set to MSC.Marc.
The following rules apply to MSC.Marc run-ready input files for submittal:
1. The filename may not have any '.' characters except for the extension. The filename must begin
with a letter (not a number).
Run-ready input files prepared by Patran follow these rules. Correct and proper analysis files are created
by following the instructions and guidelines as outlined in the Marc Preferance Guide.
To submit, monitor, and manage MSC.Marc jobs from Patran using the Analysis Manager, make sure the
Analysis Preference is set to MSC.Marc. This is done from the Preferences menu on the main form.
The Analysis form appears when the Analysis toggle, located on the Patran application switch, is chosen.
Pressing the Apply button on the Analysis application form with the Action set to Analyze, Monitor,
or Abort will cause the Analysis Manager to perform the desired action. A chapter is dedicated to each
of these actions in the manual as well as one for custom configuration of
MSC.Marc submittals.
Multiple file systems are not supported with MSC.Marc submittals. See Disk Space for
more information.
Restarts, user subroutines, externally referenced result (POST) and view factor files are handled by the
Analysis Manager by optionally copying these files to the executing host first, then running MSC.Marc
with the appropriate command arguments. See Restart for more information.
15Chapter 2: Getting StartedGeneric S bmittals
http://../interfaces/marc/marc_print.pdfhttp://../interfaces/marc/marc_print.pdf
-
8/9/2019 Patran 2012 Doc Analysis Manager User
21/278
Generic Submittals
Generic Submittals
Aside from the explicitly supported analysis codes, MSC Nastran, MSC.Marc, and ABAQUS, most any
analysis application can be submitted, monitored and managed using Patran’s Analysis Manager generalanalysis management capability. This is accomplished by selecting Analysis Manager from the Tools
pull down menu on the main Patran form. This brings up the full Analysis Manager user interface which
is described in the next section, The Main Form.
When the Analysis Manager is accessed in this manner, it keys off the current Analysis Preference. If the
Preference is set to MSC Nastran, MSC.Marc, and ABAQUS, the jobname and any restart information
is passed from the current job to the Analysis Manager and is brought up ready to submit, monitor, or
manage this job.
Any other Preference that is set must be configured correctly as described in Installation and is considered
part of the general analysis management. The jobname from the Analysis form is passed to the Analysis
Manager and the job submitted with the configured command line and arguments. (How to configure this
information is given in Miscellaneous and Applications.) If an analysis code is to be submitted, yet no
Analysis Preference exists for this code, the Analysis Manager is brought up in its default mode and the
user must then manually change the analysis application to be submitted via an option menu. This is
explained in detail in the next section.
On submittal of a general analysis code, the job file is copied to the specified analysis computer, the
analysis is run, and all resulting files from the submittal are copied back to the invoking computer
and directory.
Patran Analysis Manager User’s GuideThe Main Form
16
-
8/9/2019 Patran 2012 Doc Analysis Manager User
22/278
The Main Form
The Main Form
When Patran’s Analysis Manager is invoked either from the system prompt or via a button or a pull down
menu from within Patran, the main Analysis Manager form appears as shown. There are two interfacesshown, one for UNIX and one for Windows platforms. Only the main form is shown here with brief
explanations. Details are provided in subsequent Chapters.
17Chapter 2: Getting StartedThe Main Form
-
8/9/2019 Patran 2012 Doc Analysis Manager User
23/278
The Main Form
UNIX Interface
Note: The rest of this form’s appearance varies depending on the Action that is set. Different
databoxes, listboxes, or other items in accordance with the Action/Object menu settings are
displayed. Each of these are discussed in the following chapters.
Patran Analysis Manager User’s GuideThe Main Form
18
-
8/9/2019 Patran 2012 Doc Analysis Manager User
24/278
Windows Interface
19Chapter 2: Getting StartedThe Main Form
-
8/9/2019 Patran 2012 Doc Analysis Manager User
25/278
Window Pull-down Menus
The following simple pull-down menus are available from the Windows interface:
Windows Icons
These icons appear on the main form.
Note: The rest of this form’s appearance varies depending on the Tab that is set. Different
databoxes, listboxes, or other items in accordance with the Tree and/or Tab settings that are
displayed. Each of these are discussed in the following chapters.
Queue The main purpose of this pull-down is to allow a user to Exit the program, Print
where appropriate, and to Connect To... other queue manager daemons or services.
User Settings can also be saved and read from this pull-down menu. Foradministrators, other items on this pull-down become available when configuring the
Analysis Manager and for Starting and Sto pping queue manager services. This is
detailed in System Management. These items in the Queue pull-down menu are only
enabled when the Administration tree tab is accessed.
Edit Gives access to standard text Cut and Paste operation when applicable.
View This pull-down menu allows the user mainly to update the view when jobs are being
run. The Refresh (F5) option graphically updates the window when in monitoring
mode. The program automatically refreshes the screen based on the Update Speed
also. All Jobs or only the current User Jobs can be seen if desired.
Tools The Options under this menu allow the user to change the default editor when
viewing result files or input files. The number of user completed jobs viewable from
the interface is also set here.
Windows The main purpose of this pull-down menu is to hide or display the Status Bar and
Output Window at the bottom of the window.
Help Not currently implemented in this release.
Folder The open folder icon is the same as the Connect To... option under the Queue pull-
down menu, which allows you to connect to other queue manager daemons/services
that may be running and accessible.
Save The diskette icon is for saving user settings.
Printer Allows to print when appropriate.
Paintbrush This allows refresh of the window when in monitoring mode.
Patran Analysis Manager User’s GuideInvoking the Analysis Manager Manually
20
-
8/9/2019 Patran 2012 Doc Analysis Manager User
26/278
Invoking the Analysis Manager Manually
If installed properly, Patran’s Analysis Manager can be invoked from the system prompt with the
following arguments:
$P3_HOME/p3analysis_mgr arg1 arg2 arg3 arg4 [optional args] [args5-8]
where $P3_HOME is a variable indicating the , the directory
location of the Patran installation.
Each argument is described in the following table.
Argument Descriptionarg1
(start-up type)
The program can be started up in one of the following 8 modes (enter the
number only):
1- Start up the full interface. See The Main Form. (default)
2- Start up the Queue Monitor. See Monitor .
3- Start up the Abort Job now. See Abort.
4- Monitor a Running Job. See Monitor .
5- Monitor a Completed Job. See Monitor .
6- Submit the job. See Submit.
7- Submit in batch mode. (No user interface appears or messages.)
8- Same as 7 but waits until job is done. Returns status codes:
0=success, 1=failure, 2=abort.
arg2
(extension)
This is the extension of the analysis input file (e.g., .dat,.bdf, .inp).
(.dat is the default)
arg3 (jobname) This is the Patran jobname; the jobname that appears in any jobname textbox
(without the extension). (default = unknown)
arg4(application type)
This is the analysis application requested (enter the number only).
1 - MSC Nastran (default)
2 - ABAQUS
3 - MSC.Marc
20 - General code #1
21 - General code #2- thru
29 - General code #10
21Chapter 2: Getting StartedInvoking the Analysis Manager Manually
-
8/9/2019 Patran 2012 Doc Analysis Manager User
27/278
If no arguments are provided, defaults are used (full interface (1), “.dat”, “unknown”, MSC Nastran (1)).
The arguments listed in the table above are very convenient when invoking the Analysis Manager from pre and postprocessors such as Patran, which have access to the pertinent information which may be
passed along in the arguments. It may, however, be more convenient for the user to define an alias such
that the program always comes up in the same mode.
Here are some examples of invoking Patran’s Analysis Manager:
$P3_HOME/bin/p3analysis_mgr
or $P3_HOME/p3manager_files/p3analysis_mgr 1 bdf myjob 1
or
$P3_HOME/p3manager_files/p3analysis_mgr 1 bdf myjob MSC.Nastran
This invokes Patran’s Analysis Manager by specifying the entire path name to the executable where
$P3_HOME is a variable containing the Patran installation directory. The entire user interface is brought
up specified by the first argument. The input file is called myjob.bdf and the last argument specifiesthat MSC Nastran is the analysis code of preference.
Here is another example:
optional args
(MSC Nastran)
-coldstart coldstart_jobname
The -coldstart parameter followed by the cold start MSC Nastran
jobname indicates a restart job. Also see P3Mgr .
optional args
(ABAQUS)
-runtype
-restart oldjobname
The -runtype parameter followed by a 0, 1 or a 2 is to specify whether the
run is a full analysis, a restart, or a check run respectively. The-restart parameter is to specify the old jobname for a restart run.
optional args
(MSC.Marc)
See P3Mgr
arg5 (x position)Optional - Specifies the X position of upper left corner of Patran right hand side
interface in inches. (UNIX only)
arg6 (y position)Optional - Specifies the Y position of upper left corner of Patran right hand sideinterface in inches. (UNIX only)
arg7 (width) Optional - Width of right-hand side interface in inches. (UNIX only)
arg8 (height) Optional - Height of right-hand side interface in inches. (UNIX only)
Argument Description
Patran Analysis Manager User’s GuideInvoking the Analysis Manager Manually
22
-
8/9/2019 Patran 2012 Doc Analysis Manager User
28/278
p3analysis_mgr 1 inp myjob 2 -runtype 1 -restart oldjobp3analysis_mgr 1 inp myjob ABAQUS -runtype 1 -restart oldjob
This example invokes the Analysis Manager by assuming the executable name can be found in the user’s
path. The entire user interface is brought up specified by the first argument. The input file is called
myjob.inp. The code of preference is ABAQUS and the last two arguments indicate that a restart
analysis is to be performed and the job is a restart from a previous job called oldjob. Another example:
p3analysis_mgr 3 dat myjob 20
This example requests the termination of an analysis by the jobname of myjob with an input file called
myjob.dat. The analysis code specified is a user defined application defined by the number 20 in the
configuration files.
p3analysis_mgr 5 dat myjob 1
This example requests the completed monitor graph of an MSC Nastran analysis by the jobname of
myjob with an input file called myjob.dat.
If only the full interface is brought up by the user in stand-alone mode, it may be more convenient to
specify an alias and place it in a login file (.login, .cshrc) such as:
alias p3am ‘p3analysis_mgr 1 dat unknown 1’This way all the user has to type is p3am to invoke the program each time.
23Chapter 2: Getting StartedFiles Created
-
8/9/2019 Patran 2012 Doc Analysis Manager User
29/278
Files Created
Aside from the files generated by the analysis codes themselves, Patran’s Analysis Manager also
generates files, the contents of which are described in the following table.
Any or all of these files should be checked for error messages and codes if a job is not successful and it
does not appear that the analysis itself is at fault for abnormal termination.
Argument Description
jobname.mon This file contains the final monitoring or status information from a
submitted job. It can be replotted using the Monitor | Completed Job
selection from the main form.
jobname.tml This is the analysis manager log file that gives the status of the analysis job
and parameters that were used during execution. jobname.submit This file contains the messages that would normally appear on the screen if
the job were submitted interactively. When a silent submit is performed
(batch submittal), this file is created. Interactive submittals will display all
messages to a form on the screen.
jobname.stdout This file contains any messages that would normally go to the standard
output (generally the screen) if the user had invoked the analysis code from
the system prompt. jobname.stderr This file will contain any messages from the analysis which are written to
standard error. If no such messages are generated this file does not appear.
Patran Analysis Manager User’s GuideFiles Created
24
-
8/9/2019 Patran 2012 Doc Analysis Manager User
30/278
-
8/9/2019 Patran 2012 Doc Analysis Manager User
31/278
Chapter 3: Submit
Patran Analysis Manager User’s Guide
3 Submit
Introduction 26
Selecting Files 28
Where to Run Jobs 29
Windows Submittal 31
Patran Analysis Manager User’s GuideIntroduction
26
-
8/9/2019 Patran 2012 Doc Analysis Manager User
32/278
Introduction
The process of submitting a job requires the user to select the file and options desired. The job is
submitted to the system and ultimately executes MD Nastran, ABAQUS, MSC.Marc, or some otherapplication module. Patran’s Analysis Manager properly handles all necessary files and provides
monitoring capability to the user during and after job execution. See Monitor for more information on
monitoring jobs.
In Patran, jobs are submitted one of two ways: through the Analysis application form for the particular
Analysis Preference, or outside of Patran through Patran’s Analysis Manager user interface with the
Action (or tree tab in the Windows interface) set to Submit. Submitting through the Analysis form in
Patran makes the submittal process transparent to the user and is explained in Getting Started.For more flexibility the full user interface can be invoked from the system prompt as explained in the
previous chapter or from within Patran by pressing the Analysis Manager button on the Analysis
application form or by invoking it from the Tools pull down menu. This gives access to more advanced
and flexible features such as submitting existing input files from different directories, changing groups
or organizations (queue manager daemons/services), selecting different hosts or queues, and configuring
analysis specific items. The rest of this chapter explains these capabilities.
Below is the UNIX submittal form (see Windows Submittal for the Windows interface).
-
8/9/2019 Patran 2012 Doc Analysis Manager User
33/278
Patran Analysis Manager User’s GuideSelecting Files
28
-
8/9/2019 Patran 2012 Doc Analysis Manager User
34/278
Selecting Files
The filename of the job that is currently opened will appear in a textbox of the form on the previous page.
If this is not the job to be submitted, press the Select File button and a file browser will appear.
Below is the UNIX file browser form (see Windows Submittal for the Windows interface)
.
All appropriate files in the selected directory are displayed in the file browser. Select the file to be run
from those listed in the file browser or change the directory path in the Filter databox and then press the
Filter button to re-display the files in the new directory indicated. An asterisk (*) serves as a wild card.
Select OK once the file is properly selected and displayed, or double-click on the selected file.
Note: The directory in the Filter databox indicates where the input file will be copied from upon
submission AND where the results files from the analysis will be copied to upon
completion. Any existing results files of the same names will be overwritten on completionand you must have write privileges to the specified directory.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
35/278
Patran Analysis Manager User’s GuideWhere to Run Jobs
30
-
8/9/2019 Patran 2012 Doc Analysis Manager User
36/278
Note: Often, the user will look into the Host/Queue listing window described in Host/Queue, to
see what host/queue is most appropriate (free or empty) before selecting from the list and
submitting. When submitting to an LSF/NQS queue, the host is selected automatically,
however you can select a particular host from the Choose Specific Host button (not shown)if desired.
31Chapter 3: SubmitWindows Submittal
-
8/9/2019 Patran 2012 Doc Analysis Manager User
37/278
Windows Submittal
The interface on Windows platforms is quite different in appearance than that for UNIX, but the process
is almost identical. Submitting through this interface is simple. Simply follow these steps:
Patran Analysis Manager User’s GuideWindows Submittal
32
-
8/9/2019 Patran 2012 Doc Analysis Manager User
38/278
Once a file is selected, you can edit the file if necessary before submitting it. This is done by pressing the
Edit File button. By default the Notepad application is used as the editor. The default editor can be
changed under the Tools | Options menu pick as shown below.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
39/278
Chapter 4: Configure
Patran Analysis Manager User’s Guide
4 Configure
Introduction 34
Disk Space 35
Memory 40
Mail 46
Time 47
General 49
Restart 53
Miscellaneous 58
Patran Analysis Manager User’s GuideIntroduction
34
-
8/9/2019 Patran 2012 Doc Analysis Manager User
40/278
Introduction
By setting the Action to Conbody on the main Patran Analysis Manager form, the user has control of a
variety of options that affect job submittal. The user can customize the submitting environment by settingany of the parameters discussed in this chapter. These parameters can be saved such that all subsequent
submittals use the new settings or they can be set for a single submittal only. All of this is at the control
of the user.
35Chapter 4: ConfigureDisk Space
Di k S
-
8/9/2019 Patran 2012 Doc Analysis Manager User
41/278
Disk Space
The Disk Space configuration is analysis code specific.
MSC Nastran Disk Space
After selecting the Disk Space option on the Object menu, the following Disk Space form appears.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
42/278
37Chapter 4: ConfigureDisk Space
The Windows interface for MSC Nastran disk space is shown below
-
8/9/2019 Patran 2012 Doc Analysis Manager User
43/278
The Windows interface for MSC Nastran disk space is shown below.
Patran Analysis Manager User’s GuideDisk Space
38
ABAQUS MSC Marc and General Disk Space
-
8/9/2019 Patran 2012 Doc Analysis Manager User
44/278
ABAQUS, MSC.Marc, and General Disk Space
After selecting the Disk Space option on the Object menu, the following Disk Space form appears.
The Windows interface for ABAQUS, MSC.Marc, or other user defined analysis disk space requirements
is shown below.
39Chapter 4: ConfigureDisk Space
-
8/9/2019 Patran 2012 Doc Analysis Manager User
45/278
Patran Analysis Manager User’s GuideMemory
40
Memory
-
8/9/2019 Patran 2012 Doc Analysis Manager User
46/278
Memory
The Memory configuration is analysis code specific.
MSC Nastran Memory
After selecting the Memory option on the Object menu, the following Memory form appears.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
47/278
Patran Analysis Manager User’s GuideMemory
42
ABAQUS Memory
-
8/9/2019 Patran 2012 Doc Analysis Manager User
48/278
After selecting the Memory option on the Object menu, the following Memory form appears.
43Chapter 4: ConfigureMemory
The Windows interface for ABAQUS memory requirements is shown below:
-
8/9/2019 Patran 2012 Doc Analysis Manager User
49/278
Patran Analysis Manager User’s GuideMemory
44
MSC.Marc and General Memory
-
8/9/2019 Patran 2012 Doc Analysis Manager User
50/278
After selecting the Memory option on the Object menu, the following Memory form appears.
The Windows interface for MSC.Marc or other general application memory requirements is shown
below:
45Chapter 4: ConfigureMemory
-
8/9/2019 Patran 2012 Doc Analysis Manager User
51/278
Patran Analysis Manager User’s GuideMail
46
Mail
-
8/9/2019 Patran 2012 Doc Analysis Manager User
52/278
The Mail configuration setting determines whether or not to have mail notification and, if so, where to
send the mail notices.
Note: In this version there is no mail notification. This feature has been disabled.
47Chapter 4: ConfigureTime
Time
-
8/9/2019 Patran 2012 Doc Analysis Manager User
53/278
Any job can be submitted to be run immediately, with a delay, or at a specific future time. The default
submittal is immediate. To change the submittal time, use the following Time form.
Patran Analysis Manager User’s GuideTime
48
The Windows interface for setting job submit delay and maximum job time is specified directly on the
Submit | Job Control tab as shown below:
-
8/9/2019 Patran 2012 Doc Analysis Manager User
54/278
Note: There is no Day-of-the-Week type submittal on Windows.
49Chapter 4: ConfigureGeneral
General
Th G l fi ti f ll f t b t f b f it d ib d b l
-
8/9/2019 Patran 2012 Doc Analysis Manager User
55/278
The General configuration form allows preferences to be set for a number of items as described below.
Nothing in this form is analysis specific.
Note: Items not described on this page are described on subsequent pages in this section.
Patran Analysis Manager User’s GuideGeneral
50
The Windows interface for General setting is specified directly on the Submit | General tab as shown
below:
-
8/9/2019 Patran 2012 Doc Analysis Manager User
56/278
51Chapter 4: ConfigureGeneral
Note: Unlike the UNIX interface, to save a default Host/Queue, you select the Host/Queue on the
Job Control tab and then save the settings under the Queue pull-down menu.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
57/278
Project Directory
The project directory is a subdirectory below the Patran Analysis Manager install path where the
Analysis Manager's job-specific files are created during job execution.
Projects are a method of organizing one’s jobs and results. For instance, if a user had two different
bracket assembly designs and each assembly contained many similar if not identical parts, each assembly
file might be named assembly.dat. But to avoid interference, each file is executed out of a different
project directory.
If the first project is design1 and the second is design2, then one job is executed out of /proj/design1 and the other is /proj/design2. Hence, the user could have both jobs running at the same
time without any problems, even though they are labeled with the same file name. See Disk Configuration.
When the job is completely finished, all appropriate files are copied back to the originating host/directory
(the machine and directory where the job was actually submitted from).
Pre and Post Commands
The capability exists to execute commands prior to submission of an analysis in the form of a pre and
post capability. For instance, let us say that before submitting an analysis the user needs to translate an
input deck from ASCII form to binary form running some utility called ascbin. This is done on the
submitting host by typing ascbin at the system prompt. This same operation can be done by specifying
ascbin in the Pre databox for the originating host.
Similarly, on completion of the analysis and after the files have been copied back from the executing host,the user needs to again run a program to translate the results from one file format to another using a
program called trans. He would then place the command trans in the Post databox for the originating
host.
A Pre and a Post command can be specified on the executing (analysis) host side also.
These commands specified in the databoxes can be as simple as a one word command or can reference
shell scripts. Arguments to the command can be specified. Also, if keywords, such as the jobname or
hostname, from Patran’s Analysis Manager are needed, they can be referenced by placing a $ in front of
them. The available keywords that are interpreted in the Pre and Post databoxes can be examined by
pressing the Keyword Index button. For more explanation of keywords, see General Miscellaneous.
Separate User
The Separate User option allows job submittal to the selected system as a different user in case the current
user does not have an account on the selected system. This must be enabled and set up in advance by the
system administrator. In order for this to work properly, the separate user account specified in thisdatabox must exist on both the selected system to run the job and the machine where the job is being
Patran Analysis Manager User’s GuideGeneral
52
submitted from. See Examples of Configuration Files for an explanation on how to set up separate users
submission.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
58/278
Default Host/QueueThe Default Host/Queue, if saved, is the host/queue to which jobs are submitted when submitted directly
from Patran by using the Apply button on the Analysis form. It is also the host/queue to which jobs will
be submitted when using the batch submittal from the direct Analysis Manager command line. It is also
the host/queue which will come up as the selected default when the full Analysis Manager interface is
started. If this setting is not saved, the default host/queue is the first in the list.
Patran Database
You can specify the name of an Patran database so that on a post-submit task such as running a script file
it will know the Patran database to use for what it (the script) wants to do (like automatically reading the
results back in after a job has completed.
Copy/Link Results Files
By default all results files are copied back to the directory where the input file resides. The copy/link
functionality is just a method for transfering files. If you are remote then the files will be copied via the
Analysis Manager. But if you run locally then there is no good reason to transfer the files or even copy
them, so you can set this flag and the Analysis Manager will either link the files in the work dir to the
original ones or use the copy system command instead of trying to read one file and send bytes over to
write another file. If you are low on disk space then the link is a good way to go, but of course the
Analysis Manager needs to see the results files from the submittal host to the analysis host scratch disk
space location for this to work.
53Chapter 4: ConfigureRestart
Restart
The Restart configuration is analysis code specific and does not apply to General applications.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
59/278
g y p pp y pp
Within Patran, to perform a restart using the Analysis Manager, the job is submitted from the Analysis application as normal however, a restart job must be indicated. When invoking the Analysis Manager’s
main interface with a restart job from Patran, this information is passed to the Analysis Manager and the
restart jobname shows up in the Configure| Restart form. The restart job can be submitted directly from
the main form or from Patran. In either case, the restart job looks for the previous job to be restarted in
the local path and/or on the host machine. If this restart jobname is not specified, the databases must be
located on the host machine to perform a successful restart.
MSC Nastran Restarts
After selecting the Restart option on the menu, the following Restart form appears. To save the MSC
Nastran database for restart using the Patran Analysis Manager, the Scratch Run toggle must be set to
No in the Configure | Restart form. If the Save Databases toggle is set to No, the database is deleted
from the host machine after the analysis. If the Copy Databases Back toggle is set to No, the databases
are not copied back to the local path. The database files are given .DBO and .MST filename extensions
for the .DBALL and .MASTER files, respectively.A restart job that is submitted with the Analysis Manager searches for the Initial Job name .MST files in
the path where Patran is invoked. Therefore, if this file and the other database files are renamed or moved,
the restart job will not be successful.
Patran automatically generates the ASSIGN MASTER FMS statement required to perform a restart. If
the restart .bdf is not generated by Patran and the Analysis Manager is used to submit the job, the
.bdf must contain an ASSIGN MASTER FMS statement that specifies the name and location of the
restart database. The following error will be issued by the Patran Analysis Manager if the ASSIGNstatement is missing.
ERROR... Restart type file but no MASTER file specified with anASSIGN statement. Use an ASSIGN statement to locate at least theMASTER database file(s) for previous runs.
See the UNIX and Window forms below for more explanation.
Patran Analysis Manager User’s GuideRestart
54
-
8/9/2019 Patran 2012 Doc Analysis Manager User
60/278
55Chapter 4: ConfigureRestart
-
8/9/2019 Patran 2012 Doc Analysis Manager User
61/278
MSC.Marc Restarts
Restarts in MSC.Marc are quite similar to those in MSC Nastran.
Patran Analysis Manager User’s GuideRestart
56
-
8/9/2019 Patran 2012 Doc Analysis Manager User
62/278
ABAQUS Restarts
57Chapter 4: ConfigureRestart
After selecting the Restart option on the menu, the following Restart form appears.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
63/278
Patran Analysis Manager User’s GuideMiscellaneous
58
Miscellaneous
The Miscellaneous configuration is analysis code specific.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
64/278
MSC Nastran Miscellaneous
After selecting the Miscellaneous option on the menu, the following form appears.
59Chapter 4: ConfigureMiscellaneous
MSC.Marc Miscellaneous
After selecting the Miscellaneous option on the menu, the following form appears.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
65/278
Note: When invoked from Patran, items requiring file locations are usually passed directly intothe Analysis Manager such as the User Subroutine, POST file, and View Factor file. Thus,
in this case, there would be no need to reenter these items.
Patran Analysis Manager User’s GuideMiscellaneous
60
-
8/9/2019 Patran 2012 Doc Analysis Manager User
66/278
-
8/9/2019 Patran 2012 Doc Analysis Manager User
67/278
Patran Analysis Manager User’s GuideMiscellaneous
62
General Miscellaneous
After selecting the Miscellaneous option on the menu, the following form appears.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
68/278
Note: Some examples of General analysis applications are discussed below.
63Chapter 4: ConfigureMiscellaneous
Examples of some specific command lines used to invoke analysis codes are given here.
Example 1:
The first example involves the ANSYS 5 code. First the Analysis Preference must be set to ANSYS 5
-
8/9/2019 Patran 2012 Doc Analysis Manager User
69/278
p y
from Patran’s Analysis Preference form and an input deck for ANSYS 5 must have been generated via
the Analysis application (this is done by setting the Action to Analyze, and the Method to Analysis
Deck ). Then Patran’s Analysis Manager can be invoked from the Analysis main form. Note that a direct
submittal from Patran is not feasible in this and the subsequent example.
The jobfile (jobname.prp in this case) is automatically displayed as the input file and the Submit
button can be pressed. The jobfile is the only file that is copied over to the remote host with this general
analysis submittal capability.
In the host.cfg configuration file the path_name of the executable is defined. The rest of the
command line would then look like this:
-j $JOBNAME < $JOBFILE > $JOBNAME.log
If the executable and path defined is as /ansys/bin/ansys.er4k50a, then the entire command
that is executed is:
/ansys/bin/ansys.er4k50a -j $JOBNAME < $JOBFILE > $JOBNAME.log
Here the executable is invoked with a parameter (-j) specifying the jobname. The input file
($JOBFILE) is redirected using the UNIX redirect symbol as the standard input and the standard output
is redirected into a file called $JOBNAME.log. The variables beginning with the $ sign are passed by
Patran’s Analysis Manager. All resulting output files are copied back to the invoking host and directory
on completion.
Example 2:
This is a more complicated example where an analysis code needs more than one input file. The generalanalysis capability in Patran’s Analysis Manager only copies one input file over to the remote host for
execution. If more than one file needs to be copied over then a script must be developed for this purpose.
This example shows how Patran FEA can be submitted via a script that does the proper copying of files
to the remote host.
The Analysis Preference in Patran is set to Patran FEA and, in addition to setting the Preference, the
input file suffix is specified as .job. Patran FEA needs three possible input files: jobname.job,
jobname.ntl, and an auxiliary input file. The jobname.job file is automatically copied over to theremote host. The auxiliary input file can be called anything and is specified in the jobname.job file.
A shell script called FeaExecute is created and placed on all hosts that allow execution of Patran FEA.
This FeaExecute script does the following:
1. Parses the jobname.job file to find the name of the auxiliary input file if it is specified.
2. Copies the auxiliary input file and the jobname.ntl file to the remote host.
3. Execute the FeaControl script which controls actual execution of the Patran FEA job. This isa standard script which is delivered with the Patran FEA installation.
Patran Analysis Manager User’s GuideMiscellaneous
64
In the Patran Analysis Manager configuration file, the FeaExecute script and its path are specified.
The input parameters for this script are:
-j $JOBNAME, -h $P3AMHOST -d $P3AMDIR
hi h if h j b h h f hi h h j b b i d d h di h h
-
8/9/2019 Patran 2012 Doc Analysis Manager User
70/278
which specify the jobname, the host from which the job was submitted and the directory on that hostwhere job was submitted from. With this information the job can be successfully run. The full command
that is executed on the remote host is (assuming a location of FeaExecute):
/fea/bin/FeaExecute -j $JOBNAME, -h $P3AMHOST -d $P3AMDIR
The FeaExecute script contents are shown for completeness:
#! /bin/sh
# Script to submit Patran FEA to a remote host via the Analysis Manager# Define a function for displaying valid params for this scriptabort_usage( ) {cat 2>&1
-
8/9/2019 Patran 2012 Doc Analysis Manager User
71/278
# Determine the command name of this scriptCmd=‘echo $0 | sed ‘s;^.*/;;’‘
# Assign the default argument parameter valuesJobname=’’Verbose=’’if [ “” = ““ ] ; then Acommand=”/bin/FeaControl”else Acommand=”/bin/FeaControl”
fiStatus=0
# Parse through the input arguments.
if [ $# -ne 6 ] ; then abort_usagefi
while [ $# -ne 0 ] ; docase “$1” in
-j) Jobname=$2 ; shift 2 ;;-h) remhost=$2 ; shift 2 ;;-d) remdir=$2 ; shift 2 ;; *) abort_usage ;;esacdone# Runtime determination of machine/system typeOsName=‘uname -a | awk ‘{print $1}’‘case “$OsName” inSunOS)Rsh=”rsh”RshN1=’-n’RshN2=’’;;HP-UX)Rsh=remshRshN1=’’RshN2=’’;;AIX)Rsh=/usr/ucb/remsh
RshN1=’’RshN2=’-n’;;ULTRIX)Rsh=/usr/ucb/rshRshN1=’’RshN2=’-n’;;IRIX)Rsh=rshRshN1=’’RshN2=’-n’;;
Patran Analysis Manager User’s GuideMiscellaneous
66
*)Rsh=rshRshN1=’’RshN2=’’;;
esac
-
8/9/2019 Patran 2012 Doc Analysis Manager User
72/278
esac
# Determine the fully expanded names for the input files.JobFile=${Jobname}.jobAifFile=‘GetKeyValueCC “$JobFile” “AUXILIARY INPUT FILE”‘
# Copy the files over from the remote hostNtlFile=${Jobname}.ntllochost=‘hostname‘curdir=‘pwd‘
if [ “$curdir” = “$remdir” ] ; thencrap=1elseif [ “$remhost” = “$lochost” ] ; thencp ${remdir}/${NtlFile} .if [ “$AifFile” = ““ ] ; thencrap=1elsecp ${remdir}/${AifFile} .fielse
rcp ${remhost}:${remdir}/${NtlFile} .if [ “$AifFile” = ““ ] ; thencrap=1elsercp ${remhost}:${remdir}/${AifFile} .fififi
# Perform the analysis$Acommand $Jobname ; check_status $?
# Successful exit of scriptexit_normal
Chapter 5: Monitor
Patran Analysis Manager User’s Guide
-
8/9/2019 Patran 2012 Doc Analysis Manager User
73/278
5 Monitor
Introduction 68
Running Job 69
Completed Job 75
Host/Queue 78
Patran Analysis Manager User’s GuideIntroduction
68
Introduction
By setting the Action to Monitor on the main Patran Analysis Manager form, the user can monitor not
only his active jobs but also the Host or Queue activity. In addition, completed graphical monitoring
graphs can also be recalled at anytime Each of these functions is explained in this chapter
-
8/9/2019 Patran 2012 Doc Analysis Manager User
74/278
graphs can also be recalled at anytime. Each of these functions is explained in this chapter.
Each of these functions for monitoring jobs or hosts/queues is also accessible directly from the Analysis
application form within Patran. The only difference is that the full user interface of Patran Analysis
Manager is not accessed first; instead, the monitoring forms are displayed directly as explained in the
next few pages.
Note: The UNIX interface is shown above. In subsequent sections both the UNIX and the Windows
interface are shown. Monitoring in the Windows interface is done from the Monitor tree tabs.
69Chapter 5: Monitor Running Job
Running Job
With the Action set to monitor a Running Job, pertinent information about a specific job that is currently
running or queued to run can be obtained. Jobs can be monitored from any host in the Analysis Manager's
configuration, not just from where they were submitted.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
75/278
g , j y
Note: This form is not displayed when a job is monitored directly from Patran. Instead, only the
monitoring form is displayed as shown on the next page since all the pertinent information to
monitor a job is passed in from Patran. The Windows interface is displayed further down also.
Patran Analysis Manager User’s GuideRunning Job
70
A graph of the selected running job appears, showing the duration of the job where it has been or is
running.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
76/278
The following table describes all the widgets that appear in this job graph.
71Chapter 5: Monitor Running Job
Item Description
Job Status This widget gives the total elapsed time in blue and the actual CPU time in red.
A check mark appears when the job is completed successfully. Otherwise, an
“X” appears. The clear portion of the blue bar indicates the amount of time thej b d b f ti b El d d CPU ti t d i
-
8/9/2019 Patran 2012 Doc Analysis Manager User
77/278
job was queued before execution began. Elapsed and CPU time are reported in
minutes.
Percent CPUUsage
This widget gives the percentage of CPU that is being used by the analysis code
at any given time. The maximum percentage of CPU during job execution is
indicated as a grey shade which remains at the highest level of % CPU usage.
Total Disk Usage This widget gives the total amount of disk space used by the job during
execution in megabytes.Percent Disk Usage This widget gives the percentage of the total disk space that this job occupies at
an given time for all file systems. If you click on this widget with the mouse, all
file systems will be shown. The maximum percentage of disk space used during
job execution is indicated as a grey shade which remains at the highest level.
Job Information Job # - the sequential number of the job
Job Name - the name of the job
Owner - The name of the user or job owner
Elapsed Time - how long the job has been running
Returning JobFiles
All files created during execution are copied back and displayed in this list box.
After job completion and during job execution, it is possible to click on any of
these files to view them with a simple editor/viewer. The following keystrokes
are available in this viewer window:
ctrl-s: to search for a string
ctrl-n: to repeat search
ctrl-c: exits out of viewer
ctrl-: goes to bottom of file
-
8/9/2019 Patran 2012 Doc Analysis Manager User
78/278
73Chapter 5: Monitor Running Job
-
8/9/2019 Patran 2012 Doc Analysis Manager User
79/278
When a Running Jobs in the tree structure is selected, three tabs become available to give specific
status of the job, allow viewing of created output files, and give graphical display of memory, CPU anddisk usage.
Patran Analysis Manager User’s GuideRunning Job
74
-
8/9/2019 Patran 2012 Doc Analysis Manager User
80/278
75Chapter 5: Monitor Completed Job
Completed Job
This is an Analysis Manager utility that allows the user to graph a particular completed job run by the
Analysis Manager
-
8/9/2019 Patran 2012 Doc Analysis Manager User
81/278
Note: This form is not displayed if this action is selected directly from the Analysis application
form in Patran. Instead, only the monitoring form is displayed as shown on the next page.
The Windows interface is also shown
Patran Analysis Manager User’s GuideCompleted Job
76
The .mon file is created when a job is first submitted to Patran’s Analysis Manager. Information on all
the job tasks is written to the .mon file. Time submitted, job name, job number, time actually run, time
finished and completion status are all recorded in the file, so that this Analysis Manager function can read
the file and have enough information to graph the job’s progress completely.
The explanation of the graphs on this form is identical to that of a Running Job except that the Update
lid b d t h i it i t li bl t l t d j b
-
8/9/2019 Patran 2012 Doc Analysis Manager User
82/278
slider bar does not show up since it is not applicable to a completed job.
Windows Interface
For Completed Jobs, the Windows interface displays them under the Completed Jobs tab in the
Monitor tree.
77Chapter 5: Monitor Completed Job
-
8/9/2019 Patran 2012 Doc Analysis Manager User
83/278
Patran Analysis Manager User’s GuideHost/Queue
78
Host/Queue
Information about all hosts or queues used by Patran’s Analysis Manager and jobs submitted through the
Analysis Manager can be reviewed using the Monitor Host/Queue selection. Options available include
Job Listing, Host Status, Queue Manager Log and a Full Listing. Press the Apply button to invoke these functions. The user can vary how often the information is updated, using the
lid l
-
8/9/2019 Patran 2012 Doc Analysis Manager User
84/278
slider control.
The Host/Queue monitoring function can also be invoked manually from the system prompt. SeeInvoking the Analysis Manager Manually for details.
79Chapter 5: Monitor Host/Queue
Job Listing
The initial application form of Monitor's Host/Queue appears as follows:
-
8/9/2019 Patran 2012 Doc Analysis Manager User
85/278
At the top of the main form for Monitor Queue is a slider labeled Update Time (Min.). Drag the slider
to the left to shorten the interval between information updates, or drag the slider to the right to slow
update of information. The default interval time is 5 minutes. In the Windows interface the refresh settingis set under the View | Update Speeds menu pick.
The update interval may be changed at any time during the use of any Monitor Queue options.
All jobs are listed which are currently running in some capacity. Information about each job includes:
Job Number, Job Name, Owner and Time. The job number is a unique, sequential number that the
Analysis Manager generates for each job submitted to it. Pressing the Close button will close down the
monitor form.
Patran Analysis Manager User’s GuideHost/Queue
80
Host Status
When the Host Status toggle is highlighted the form appears as follows:
-
8/9/2019 Patran 2012 Doc Analysis Manager User
86/278
The status is reported on all hosts or queues used by the Analysis Manager. Information about each
host/queue includes: host/queue name (Host Name), number of jobs running (# Running), number of jobs
queued (# Queued), maximum allowed to run concurrently (Max Running), and Host Type (i.e., MSC
Nastran).
If NQS or LSF is being used, queue information is provided instead of host information. See Submit for
more information on default settings.
The update interval may be changed at any time during the use of any Monitor Queue options. The default
interval time is 5 minutes. In Windows, use the View | Update Speeds menu option.
To exit from the Monitor Queue, select the Close button on the bottom of the main form on the right.
Log files are unaffected when the form is closed.
81Chapter 5: Monitor Host/Queue
Queue Manager Log
When the Queue Manager Log toggle is selected, the form appears as follows:
-
8/9/2019 Patran 2012 Doc Analysis Manager User
87/278
The most recent jobs submitted are listed, regardless of where or when they were run. Information about
each job includes: date and time of event, event description, job number, job or task name or host name,
task type or PID (process id of task), and owner. Most recent jobs are listed in the text list box from the
time the Analysis Manager’s Queue Manager daemon was started. See System Management for a
description of the Queue Manager daemon.
The update interval may be changed at any time during the use of any Monitor Queue options. The default
interval time is 5 minutes. In Windows, use the View | Update Speeds menu option.
To exit from the Monitor Queue, select the Close button on the bottom of the main form on the right.
Log files are unaffected when the form is closed.
Patran Analysis Manager User’s GuideHost/Queue82
Full Listing
When Full Listing is selected, the form appears as follows:
-
8/9/2019 Patran 2012 Doc Analysis Manager User
88/278
The Full Listing information shows all job tasks submitted. Information about each host/queue includes:
status (blue = running; red = queued), job number, task name, task type, date and time submitted, and
owner.
The queue name is shown if an additional scheduler is present and being used (LSF/Utopia) and a pointer
to the actual queue name.
The update interval may be changed at any time during the use of any Monitor Queue options. The default
interval time is 5 minutes.
To exit from the Monitor Queue, select the Close button on the bottom of the main form on the right.
CPU Loads
When CPU Loads is selected, the form appears as follows:
Note: There is no Full Listing form in the Windows interface.
83Chapter 5: Monitor Host/Queue
-
8/9/2019 Patran 2012 Doc Analysis Manager User
89/278
The load on the workstations and computers can be determined by inspecting this form which
periodically updates itself. The list of hosts or queues appears with the percent CPU usage, total amount
of free disk space, and available memory at that particular snapshot in time. The user may sort the hosts
by CPU UTILIZATION, FREE DISK SPACE, or AVAILABLE MEMORY, so that the host or
queue with the best situation appears at the top. Also, indicated in blue are the best hosts or queues for
each category of CPU, disk space and memory.
Patran Analysis Manager User’s GuideHost/Queue84
-
8/9/2019 Patran 2012 Doc Analysis Manager User
90/278
Chapter 6: Abort
Patran Analysis Manager User’s Guide
-
8/9/2019 Patran 2012 Doc Analysis Manager User
91/278
6 Abort
Selecting a Job 86
Aborting a Job 87
Patran Analysis Manager User’s GuideSelecting a Job86
Selecting a Job
This capability allows the user to terminate a running job originally submitted through Patran’s Analysis
Manager. When aborting a job, the Analysis Manager cleans up all appropriate files.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
92/278
The abort function can also be invoked manually from the system prompt. See Invoking the Analysis
Manager Manually for details. A currently running job must be available.
87Chapter 6: Abort Aborting a Job
Aborting a Job
You can only abort jobs which you own (i.e., originally submitted by you).
When a job is aborted, the analysis files are removed from where they were copied to, and all scratch and
database files are removed, unless the job is a restart from a previous run, in which case the scratch files
are removed, but the original database files from previous runs are left unaffected.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
93/278
UNIX InterfacePress the Apply button on the main form with the Action set to Abort as shown on the previous page.
You are asked to confirm with,
Are you sure you wish to abort job # ?
Press the OK button to confirm.
The Cancel button will take no action and close the Abort form.
Windows Interface
There are three ways to abort a job from the Windows interface.
1. When the job is initially submitted, a modal window appears asking whether you want to monitor
or abort the job or simply do nothing and let the job run.
2. Once the job is running, from the Job Control tab in the Monitor tree structure. There is an
Abort button on this form to terminate the job.
Note: When a job is aborted from within Patran, no user interface appears. The job is simply aborted
after the confirmation.
Patran Analysis Manager User’s Guide Aborting a Job88
-
8/9/2019 Patran 2012 Doc Analysis Manager User
94/278
3. From the Monitor | Running Jobs tree structure you can right mouse click on a running job. A
pulldown menu appears from which you can select Abort.
Chapter 7: System Management
Patran Analysis Manager User’s Guide
-
8/9/2019 Patran 2012 Doc Analysis Manager User
95/278
7 System Management
Directory Structure 90
Analysis Manager Programs 92
Organization Environment Variables 103
Installation 107 X Resource Settings 111
Configuration Management Interface 113
Examples of Configuration Files 146
Starting the Queue/Remote Managers 155
Patran Analysis Manager User’s GuideDirectory Structure90
Directory Structure
The Analysis Manager has a set directory structure, configurable environment variables and other tunable
parameters which are discussed in this chapter.
The Analysis Manager directory structure is displayed below. The main installation directory is shownas an environment variable, $P3_HOME =. Typically this would be
or /msc/patran200x or something similar.
-
8/9/2019 Patran 2012 Doc Analysis Manager User
96/278
where:
(optional) is an additional organizational group and shares the same directory tree as default
yet will have its own unique set of configuration files. See Organization Environment Variables.
is one of:
91Chapter 7: System ManagementDirectory Structure
HP700 - Hewlett Packard HP-UX
RS6K - IBM RS/6000 AIX
SGI5 - Silicon Graphics IRIX
SUNS - Sun SPARC Solaris
LX86 - Linux (MSC or Red Hat)
WINNT - Windows 2000 or XP
-
8/9/2019 Patran 2012 Doc Analysis Manager User
97/278
There may be more than one directory in a filesystem. Architecture types that are not applicable
to your installation may be deleted to reduce disk space usage; however, all machine architecture types
that will be accessed by the Analysis Manager must be kept. Each one of the executables under the bin
directory is described in Analysis Manager Programs.
All configuration files are explained in detail in Examples of Configuration Files. These include org.cfg,
host.cfg, disk.cfg, lsf.cfg, and nqs.cfg.
Organization groups and their uses are described in Organization Environment Variables.
The QueMgr.log file is created when a Queue Manager daemon is started and does not exist until this
time and, therefore, will not exist in the above directory structure unitl after the initial installation. Use
of this file is described in Starting the Queue/Remote Managers respectively. The file QueMgr.rdb is alsocreated when a Queue Manager daemon is started and is a database containing job specific statistics of
every job ever submitted through the Queue Manager for that particular set of configuration file or
. The contents of this file can be viewed on Unix platforms using the Job_Viewer executable.
Items in the bin and exe directories are scripts to enable easier access to the main programs. These scripts
make sure that the proper environment variables are set before invoking the particular program that reside
in $P3_HOME/p3manager_files/bin/.
W NN W dows 000 o
p3analysis_mgr Invokes P3Mgr
p3am_admin Invokes AdmMgr (Unix only - on Windows this is P3Mgr.)
p3am_viewer Invokes Job_Viewer (Unix only)
QueMgr Invokes QueMgr (Unix only)
RmtMgr Invokes RmtMgr (Unix only)
Note: The directories (conf, log, proj) for each set of configuration file (organizational
structure) must have read, write, and execute (777) permission for all users. This can be the
cause of task manager errors.
Patran Analysis Manager User’s Guide Analysis Manager Programs92
Analysis Manager Programs
The Analysis Manager is comprised of two main parts, the user interface and a number of daemons. Each
of these parts and the executables are described below. All executables are found in the
$P3_HOME/p3manager_files/bin directory, where $P3_HOME is the installation directory,typically /msc/patran200x.
User Interface
-
8/9/2019 Patran 2012 Doc Analysis Manager User
98/278
The first part of the Analysis Manager is the user interface from which a user submits and monitors the
progress of jobs (P3Mgr is the executable name). This program can be executed in many different ways
and from many different locations (i.e., either locally or remotely over a network). An administration tool
also is available to easily set up and edit configuration files, and test for proper installation. (AdmMgr is
the executable name on Unix. On Windows there is no separate executable; it is part of P3Mgr.) A small
editor program (p3edit) is also part of the user interface portion and is invoked directly from the main
user interface when editing and viewing files.
Two shell scripts are actually used to invoke the Analysis Manager and the administration tool. These are
p3analysis_mgr and p3am_admin. When properly installed, these scripts automatically determine the
installation path directory structure and which machine architecture executable to use.
Daemons
The second part of the Analysis Manager is a series of daemons (or services on Windows) which actually
execute and control jobs. These daemons are responsible for queuing jobs, finding a host to run jobs,
moving data files to selected hosts, executing the selected analysis code, etc. Each one is described here:
Queue Manager
This is a daemon (or service on Windows) which must run all the time (QueMgr executable name). The
machine on which the Queue Manager runs is knows as the master host. Generally it runs as root (oradministrator) and is responsible for scheduling jobs. The Queue Manager always has a complete account
of all jobs running and/or queued. When a request to run a job is received, the Queue Manager checks to
see what hosts are eligible to run the selected code and how many jobs each host is currently running. If
there is a host which is eligible, the Queue Manager will start up the task on that host. If the Analysis
Manager is installed along with a third party scheduling program (i.e., LSF or NQS) the Queue Manager
is responsible for communicating with the scheduling software to control job execution. In summary, the
Queue Manager is the Scheduler of the Analysis Manager environment. (Also, see Starting the
Queue/Remote Managers, Starting the Queue Manager.)
Remote Manager
There is only one Queue Manager, but there are many
top related