patran_2014_doc_analysis manager user's guide.pdf

Patran 2014

Analysis Manager Users Guide

Worldwide Webwww.mscsoftware.com

Supporthttp://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx

DisclaimerThis 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 2014 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.This software may contain certain third-party software that is protected by copyright and licensed from MSC Software suppliers. Additional terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms and conditions and/or notices may be set forth in documentation and/or at http://www.mscsoftware.com/thirdpartysoftware (or successor website designated by MSC from time to time). METIS is copyrighted by the regents of the University of Minnesota. A copy of the METIS product documentation is included with this installation. Please see "A Fast and High Quality Multilevel Scheme for Partitioning Irregular Graphs". George Karypis and Vipin Kumar. SIAM Journal on Scientific Computing, Vol. 20, No. 1, pp. 359-392, 1999. 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 and FlexNet Publisher are trademarks or registered trademarks of Flexera Software. 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 the United States and/or other countries. Unigraphics, Parasolid and I-DEAS are registered trademarks of Siemens Product Lifecycle Management, Inc. All other brand names, product names or trademarks belong to their respective owners.

P3:V2014:Z:ANM:Z: DC-USR-PDF

Corporate Europe, Middle East, AfricaMSC Software Corporation MSC Software GmbH4675 MacArthur Court, Suite 900 Am Moosfeld 13Newport Beach, CA 92660 81829 Munich, GermanyTelephone: (714) 540-8900 Telephone: (49) 89 431 98 70Toll Free Number: 1 855 672 7638 Email: [email protected]: [email protected]

Japan Asia-PacificMSC Software Japan Ltd. MSC Software (S) Pte. Ltd.Shinjuku First West 8F 100 Beach Road23-7 Nishi Shinjuku #16-05 Shaw Tower1-Chome, Shinjuku-Ku Singapore 189702Tokyo 160-0023, JAPAN Telephone: 65-6272-0082Telephone: (81) (3)-6911-1200 Email: [email protected]: [email protected]

mailto:[email protected]:[email protected]:[email protected]:[email protected]://www.mscsoftware.com/thirdpartysoftware

C o n t e n t sMSC Patran Analysis Manager Users Guide 1 OverviewPurpose 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 16UNIX Interface 17Windows Interface 18

Invoking the Analysis Manager Manually 20

Files Created 23

3 SubmitIntroduction 26

Selecting Files 28

Where to Run Jobs 29

MSC Patran Analysis Manager Users Guide

ivWindows Submittal 31

Multiple File Transfer 33

4 ConfigureIntroduction 36

Disk Space 37MSC Nastran Disk Space 37ABAQUS, MSC.Marc, and General Disk Space 40

Memory 42MSC Nastran Memory 42ABAQUS Memory 44MSC.Marc and General Memory 46

Mail 48

Time 49

General 51

Restart 55MSC Nastran Restarts 55MSC.Marc Restarts 57ABAQUS Restarts 58

Miscellaneous 60MSC Nastran Miscellaneous 60MSC.Marc Miscellaneous 61ABAQUS Miscellaneous 63General Miscellaneous 64

5 MonitorIntroduction 70

Running Job 71Windows Interface 74

Completed Job 77Windows Interface 78

Host/Queue 80Job Listing 81

vCONTENTSHost Status 82Queue Manager Log 83Full Listing 84CPU Loads 84

6 AbortSelecting a Job 88

Aborting a Job 89UNIX Interface 89Windows Interface 89

7 System ManagementDirectory Structure 92

Analysis Manager Programs 94Analysis Manager Program Startup Arguments 96Analysis Manager Environment File 102

Organization Environment Variables 105

Installation 109Installation Requirements 109Installation Instructions 110

X Resource Settings 113

Configuration Management Interface 115Modify Configuration Files 118Test Configuration 136Queue Manager 145

Examples of Configuration Files 148

Starting the Queue/Remote Managers 157Starting Daemons at Boot Time 158

8 Error MessagesError Messages 164

MSC Patran Analysis Manager Users Guide

vi9 Application Procedural Interface (API)Analysis Manager API 196Analysis Manager Application Procedural Interface (API) Description 196

Include File 206

Example Interface 232

Chapter 1: OverviewPatran Analysis Manager Users 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

Patran Analysis Manager Users GuidePurpose

2

PurposeMD 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.

3Chapter 1: OverviewProduct InformationProduct InformationThe 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 Marc releases 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, xii.

Patran Analysis Manager Users 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 Users Manual. An on-line version is provided to allow direct access to this information from

within MSC Patran.

5Chapter 1: OverviewIntegration with MSC PatranIntegration 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, monitored and 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.

Patran Analysis Manager Users GuideHow this Manual is Organized

6

How this Manual is OrganizedThis 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 PatranAnalysis Manager.

Getting Started describes rules for analysis input decks, how to invoke MSC Patrans 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 Manager user 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.

Chapter 2: Getting StartedPatran Analysis Manager Users Guide

2 Getting 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 Users GuideQuick Overview

8

Quick OverviewBefore Patrans 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 Managers 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 proper communication 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 StartedQuick OverviewOnce 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 Patrans 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 Users GuideEnabling/Disabling the Analysis Manager

10Enabling/Disabling the Analysis ManagerThere 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 Patrans generic submittal 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 Patrans generic submit scripts.

To disable the Analysis Manager, type the following command in Patrans 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 users p3epilog.pcl file. This file is invoked at startup from the users local directory, or home directory, or $P3_HOME in that order, if found.

11Chapter 2: Getting StartedMSC Nastran SubmittalsMSC Nastran SubmittalsAny standard MSC Nastran (up to version 2006) problem can be submitted using Patrans Analysis Manager. This is accomplished from the Analysis form with the Analysis Preference set to MSC 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 MSC 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 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 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 Users GuideMSC Nastran Submittals

12The 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 Managers 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 StartedABAQUS SubmittalsABAQUS SubmittalsAny standard ABAQUS (up to version 6.x) problem can be submitted using Patrans 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 Users GuideMSC.Marc Submittals

14MSC.Marc SubmittalsAny standard MSC.Marc (up to version 2006) problem can be submitted using Patrans 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 SubmittalsGeneric SubmittalsAside from the explicitly supported analysis codes, MSC Nastran, MSC.Marc, and ABAQUS, most any analysis application can be submitted, monitored and managed using Patrans Analysis Manager general analysis 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 Users GuideThe Main Form

16The Main FormWhen Patrans 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 interfaces shown, 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 FormUNIX Interface

Note: The rest of this forms 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 Users GuideThe Main Form

18Windows Interface

19Chapter 2: Getting StartedThe Main FormWindow Pull-down MenusThe following simple pull-down menus are available from the Windows interface:

Windows IconsThese icons appear on the main form.

Note: The rest of this forms 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. For administrators, other items on this pull-down become available when configuring the Analysis Manager and for Starting and Stopping 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 Users GuideInvoking the Analysis Manager Manually

20Invoking the Analysis Manager ManuallyIf installed properly, Patrans 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 - ABAQUS3 - MSC.Marc20 - General code #121 - General code #2

- thru29 - General code #10

21Chapter 2: Getting StartedInvoking the Analysis Manager ManuallyIf 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 Patrans 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 Patrans 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 specifies that 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 side interface 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 Users GuideInvoking the Analysis Manager Manually

22p3analysis_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 users 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 CreatedFiles CreatedAside from the files generated by the analysis codes themselves, Patrans 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 Descriptionjobname.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 Users GuideFiles Created

24

Chapter 3: SubmitPatran Analysis Manager Users Guide

3 Submit

Introduction 26

Selecting Files 28

Where to Run Jobs 29

Windows Submittal 31

Multiple File Transfer 33

Patran Analysis Manager Users GuideIntroduction

26IntroductionThe 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 other application module. Patrans 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 Patrans 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).

27Chapter 3: SubmitIntroduction

Patran Analysis Manager Users GuideSelecting Files

28Selecting FilesThe 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 completion and you must have write privileges to the specified directory.

29Chapter 3: SubmitWhere to Run JobsWhere to Run JobsA default host system or queue is provided. However, a different host system or queue may be selected using the Host/Queue list on the form. Select the host system or queue where the job is to execute.

If Patran Analysis Manager is to schedule the job, then select the host where the job will run. Make the choice by clicking the toggle to the left of the appropriate host name.

If another scheduling software system (i.e., LSF or NQS) is enabled, then select the queue to submit the job to. The queueing software executes each job on the host it selects.

Below is the UNIX interface (see Windows Submittal for the Windows interface).

The submit function can also be invoked manually from the system prompt. See Invoking the Analysis Manager Manually for details. It can be invoked in both an interactive and a batch mode.

Patran Analysis Manager Users GuideWhere to Run Jobs

30Note: 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 SubmittalWindows SubmittalThe 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 Users GuideWindows Submittal

32Once 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.Multiple File Transfer

alysis Manager supports multiple file transfer if a solver requires multiple input files in order to run a solution. Analysis Manger does this by transferring the files specified in a list- file over to the solver machine. This requires the input files to be listed in a LST file that has the same name as the job (jobname). For example, if the job name is 'test' the LST file name must be 'test.lst'. The input files can be listed in the LST file like this:locations.xyzinput12.inptest.frqconfig.usr When the job will be submitted to the Analysis Manager, it will find the $JOBNAME.lst, parse it, and additionally copy over files of the above name (assumed to be in the same location). Multiple File TransferAnalysis Manager supports multiple file transfer if a solver requires multiple input files in order to run a solution. Analysis Manger does this by transferring the files specified in a list- file over to the solver machine. This requires the input files to be listed in a LST file that has the same name as the job (jobname). For example, if the job name is 'test' the LST file name must be 'test.lst'. The input files can be listed in the LST file like this:locations.xyzinput12.inptest.frqconfig.usr When the job will be submitted to the Analysis Manager, it will find the $JOBNAME.lst, parse it, and additionally copy over files of the above name (assumed to be in the same location).

33Chapter 3: SubmitMultiple File TransferMultiple File TransferAnalysis Manager supports multiple file transfer if a solver requires multiple input files in order to run a solution.

Analysis Manger does this by transferring the files specified in a list- file over to the solver machine. This requires the input files to be listed in a LST file that has the same name as the job (jobname). For example, if the job name is 'test' the LST file name must be 'test.lst'. The input files can be listed in the LST file like this:

locations.xyz

input12.inp

test.frq

config.usr

When the job will be submitted to the Analysis Manager, it will find the $JOBNAME.lst, parse it, and additionally copy over files of the above name (assumed to be in the same location).

Patran Analysis Manager Users GuideMultiple File Transfer

34

Chapter 4: ConfigurePatran Analysis Manager Users Guide

4 Configure

Introduction 36

Disk Space 37

Memory 42

Mail 48

Time 49

General 51

Restart 55

Miscellaneous 60


36IntroductionBy 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 setting any 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.

37Chapter 4: ConfigureDisk SpaceDisk SpaceThe Disk Space configuration is analysis code specific.

MSC Nastran Disk SpaceAfter selecting the Disk Space option on the Object menu, the following Disk Space form appears.

Patran Analysis Manager Users GuideDisk Space

38Note: Patrans Analysis Manager will only check for sufficient disk space if the numbers for DBALL, MASTER, and SCRATCH are provided. An error message will appear if not enough disk space is available. If these values are not specified the job will be submitted and will run until completion or the disk is full and an error occurs.

39Chapter 4: ConfigureDisk SpaceThe Windows interface for MSC Nastran disk space is shown below.

Patran Analysis Manager Users GuideDisk Space

40ABAQUS, MSC.Marc, and General Disk SpaceAfter 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.

41Chapter 4: ConfigureDisk Space

Patran Analysis Manager Users GuideMemory

42MemoryThe Memory configuration is analysis code specific.

MSC Nastran MemoryAfter selecting the Memory option on the Object menu, the following Memory form appears.

43Chapter 4: ConfigureMemoryThe Windows interface for MSC Nastran memory requirements is shown below:


44ABAQUS MemoryAfter selecting the Memory option on the Object menu, the following Memory form appears.

45Chapter 4: ConfigureMemoryThe Windows interface for ABAQUS memory requirements is shown below:


46MSC.Marc and General MemoryAfter 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:

47Chapter 4: ConfigureMemory

Patran Analysis Manager Users GuideMail

48MailThe 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.

49Chapter 4: ConfigureTimeTimeAny 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 Users GuideTime

50The Windows interface for setting job submit delay and maximum job time is specified directly on the Submit | Job Control tab as shown below:

Note: There is no Day-of-the-Week type submittal on Windows.

51Chapter 4: ConfigureGeneralGeneralThe 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 Users GuideGeneral

52The Windows interface for General setting is specified directly on the Submit | General tab as shown below:

53Chapter 4: ConfigureGeneralProject DirectoryThe 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 ones 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 CommandsThe 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 Patrans 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 UserThe 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 this databox must exist on both the selected system to run the job and the machine where the job is being

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.

Patran Analysis Manager Users GuideGeneral

54submitted from. See Examples of Configuration Files for an explanation on how to set up separate users submission.

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 DatabaseYou 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 FilesBy 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.

55Chapter 4: ConfigureRestartRestartThe Restart configuration is analysis code specific and does not apply to General applications.

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 Managers 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 RestartsAfter 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 ASSIGN statement is missing.

ERROR... Restart type file but no MASTER file specified with an ASSIGN statement. Use an ASSIGN statement to locate at least the MASTER database file(s) for previous runs.

See the UNIX and Window forms below for more explanation.

Patran Analysis Manager Users GuideRestart

56

57Chapter 4: ConfigureRestartMSC.Marc RestartsRestarts in MSC.Marc are quite similar to those in MSC Nastran.

Patran Analysis Manager Users GuideRestart

58ABAQUS Restarts

59Chapter 4: ConfigureRestartAfter selecting the Restart option on the menu, the following Restart form appears.

Patran Analysis Manager Users GuideMiscellaneous

60MiscellaneousThe Miscellaneous configuration is analysis code specific.

MSC Nastran MiscellaneousAfter selecting the Miscellaneous option on the menu, the following form appears.

61Chapter 4: ConfigureMiscellaneousMSC.Marc MiscellaneousAfter selecting the Miscellaneous option on the menu, the following form appears.

Note: When invoked from Patran, items requiring file locations are usually passed directly into the 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.


62

63Chapter 4: ConfigureMiscellaneousABAQUS MiscellaneousAfter selecting the Miscellaneous option on the menu, the following form appears.


64General MiscellaneousAfter selecting the Miscellaneous option on the menu, the following form appears.

Note: Some examples of General analysis applications are discussed below.

65Chapter 4: ConfigureMiscellaneousExamples 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 from Patrans 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 Patrans 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 Patrans 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 general analysis capability in Patrans 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 the remote 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 is

a standard script which is delivered with the Patran FEA installation.


66In 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

which specify the jobname, the host from which the job was submitted and the directory on that host where 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

67Chapter 4: ConfigureMiscellaneous#get_Jobname(){echo $1 | sed -e s;^.*/;; -e s;\..*$;;}# Determine the command name of this scriptCmd=echo $0 | sed s;^.*/;;

# Assign the default argument parameter valuesJobname=Verbose=if [ = ] ; then Acommand=/bin/FeaControlelse Acommand=/bin/FeaControlfiStatus=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=rshRshN1=-nRshN2=;;HP-UX)Rsh=remshRshN1=RshN2=;;AIX)Rsh=/usr/ucb/remshRshN1=RshN2=-n;;ULTRIX)Rsh=/usr/ucb/rshRshN1=RshN2=-n;;IRIX)Rsh=rshRshN1=RshN2=-n;;


68*)Rsh=rshRshN1=RshN2=;;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=hostnamecurdir=pwdif [ $curdir = $remdir ] ; thencrap=1elseif [ $remhost = $lochost ] ; thencp ${remdir}/${NtlFile} .if [ $AifFile = ] ; thencrap=1elsecp ${remdir}/${AifFile} .fielsercp ${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: MonitorPatran Analysis Manager Users Guide

5 Monitor

Introduction 70

Running Job 71

Completed Job 77

Host/Queue 80


70IntroductionBy 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.

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.

71Chapter 5: MonitorRunning JobRunning JobWith 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.

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 Users GuideRunning Job

72A graph of the selected running job appears, showing the duration of the job where it has been or is running.

The following table describes all the widgets that appear in this job graph.

73Chapter 5: MonitorRunning JobItem DescriptionJob 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 the job was queued before execution began. Elapsed and CPU time are reported in minutes.

Percent CPU Usage

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 runningReturning Job Files

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 stringctrl-n: to repeat searchctrl-c: exits out of viewerctrl-: goes to bottom of file


74The bottom left panel lists information about the job, such as date and time of event task name, host name, and status. Any error and status messages will appear here. An example listing is:

Fri Jan 4 13:31:31 1994 Task Name: shock

The running job function can also be invoked manually from the system prompt. See Invoking the Analysis Manager Manually for details.

Windows InterfaceFor Running Jobs, when a job is submitted from the Windows interface, the user is queried as the whether he/she wants the interface to switch automatically to the monitoring mode.

When a job is running the Monitor tree shows running jobs and jobs that have been queued.

Controls Remove beginning queue time - takes off the queued portion of the graphics bar, e.g., the portion that is not blue before job begins.

Suspend/Resume Job - when toggled on, the job will be indefinitely suspended. A banner across the CPU dial will display the word SUSPENDED while the job is suspended. Toggle the switch off to resume the job. The banner will be removed.

Update (Sec.) - how often to update the graph / display

Pixels Per Min - how many pixels wide per minute

MB Per Inch - how many megabytes per inch to be displayed

Normalize Graph - make the graph fit in the window areaClose Closes the monitoring form.Status Window Status messages are returned in this window. If the log file is being monitored,

then log file lines will appear here also for MSC Nastran and ABAQUS.

Item Description

75Chapter 5: MonitorRunning JobWhen 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 and disk usage.


76

77Chapter 5: MonitorCompleted JobCompleted JobThis is an Analysis Manager utility that allows the user to graph a particular completed job run by the Analysis Manager

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 Users GuideCompleted Job

78The .mon file is created when a job is first submitted to Patrans 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 jobs progress completely.

The explanation of the graphs on this form is identical to that of a Running Job except that the Update slider bar does not show up since it is not applicable to a completed job.

Windows InterfaceFor Completed Jobs, the Windows interface displays them under the Completed Jobs tab in the Monitor tree.

79Chapter 5: MonitorCompleted Job

Patran Analysis Manager Users GuideHost/Queue

80Host/QueueInformation about all hosts or queues used by Patrans 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 slider control.

The Host/Queue monitoring function can also be invoked manually from the system prompt. See Invoking the Analysis Manager Manually for details.

81Chapter 5: MonitorHost/QueueJob ListingThe initial application form of Monitor's Host/Queue appears as follows:

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 setting is 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.


82Host StatusWhen the Host Status toggle is highlighted the form appears as follows:

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.

83Chapter 5: MonitorHost/QueueQueue Manager LogWhen the Queue Manager Log toggle is selected, the form appears as follows:

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 Managers 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.


84Full ListingWhen Full Listing is selected, the form appears as follows:

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 LoadsWhen CPU Loads is selected, the form appears as follows:

Note: There is no Full Listing form in the Windows interface.

85Chapter 5: MonitorHost/QueueThe 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.


86

Chapter 6: AbortPatran Analysis Manager Users Guide

6 Abort

Selecting a Job 88

Aborting a Job 89

Patran Analysis Manager Users GuideSelecting a Job

88Selecting a JobThis capability allows the user to terminate a running job originally submitted through Patrans Analysis Manager. When aborting a job, the Analysis Manager cleans up all appropriate files.

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.

89Chapter 6: AbortAborting a JobAborting a JobYou 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.

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 InterfaceThere 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 Users GuideAborting a Job

903. 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 ManagementPatran Analysis Manager Users Guide

7 System Management

Directory Structure 92

Analysis Manager Programs 94

Organization Environment Variables 105

Installation 109

X Resource Settings 113

Configuration Management Interface 115

Examples of Configuration Files 148

Starting the Queue/Remote Managers 157

Patran Analysis Manager Users GuideDirectory Structure

92Directory StructureThe 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 shown as an environment variable, $P3_HOME =. Typically this would be or /msc/patran200x or something similar.

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:

93Chapter 7: System ManagementDirectory StructureThere 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 also created 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/.

HP700 - Hewlett Packard HP-UX RS6K - IBM RS/6000 AIXSGI5 - Silicon Graphics IRIX SUNS - Sun SPARC Solaris LX86 - Linux (MSC or Red Hat)WINNT - Windows 2000 or XP

p3analysis_mgr Invokes P3Mgrp3am_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 Users GuideAnalysis Manager Programs

94Analysis Manager ProgramsThe 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 InterfaceThe 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.

DaemonsThe 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 ManagerThis 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 (or administrator) 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 ManagerThere is only one Queue Manager, but there are many Remote Managers. A RmtMgr process runs on each and every analysis machine. These are machines that are configured to run an analysis such as MSC Nastran or MSC.Marc. A RmtMgr can also be run on each submit machine (recommended - see Job Manager below). These are machines from which the analysis was submitted such as where Patran runs. If the submit and analysis machines are the same host, then only one RmtMgr needs to be running. The QueMgr and RmtMgr processes start up at boot time automatically and run always, but use very little

95Chapter 7: System ManagementAnalysis Manager Programsmemory and cpu resources, so users will not notice performance effects. Also these processes can run as root (Administrator on Windows) or as any user, if these privileges are not available.

Each RmtMgr binds to a known/chosen port number that is the same for every RmtMgr machine. Each RmtMgr process collects machine statistics on free CPU cycles, free memory and free disk space and returns this data to the QueMgr at frequent intervals. The RmtMgr is actually used to perform a command and return the output from that command on the host it is running. This is essentially a remote shell (rsh) host command as on a Unix machine.

Job ManagerThe Job Manager (JobMgr executable name) runs for the life of a job. When a user submits a job using the Analysis Managerr, the user interface tells Queue Manager about the job and then starts a Job Manager daemon. The Job Manager daemon will receive and save job information from the Analysis Manager's user interface. The main purpose of the Job Manager is to record job status for monitoring and file transfer.

During the execution of jobs, users utilizing the Analysis Manager's user interface program can seamlessly connect to the Job Manager of their job and see what the status of the job is. In summary, the Job Manager controls the execution of a single job and is always aware of the current status of that job. The Job Manager runs on the submit host machine.

MSC Nastran ManagerThe MSC Nastran Manager (NasMgr executable name) runs only for the life of a job. The MSC Nastran Manager is started by the Queue Manager when the task reaches the top of its queue and is eligible to run. The purpose of the MSC Nastran Manager is to run the MSC Nastran job. When the NasMgr first comes up, it generates FMS (if necessary), checks to see if there is enough disk space, etc. The NasMgr will make sure it has all of the files it needs for the job. If not, it will obtain them. Finally, the MSC Nastran job is started.

Note: Its best to run the RmtMgr service on Windows as someone other than SYSTEM (the default if you do not do anything different). After installing the RmtMgr, use the control panel to access the services and then find the RmtMgr and change its startup to use a different account, something generic if it exists, or an Analysis Manager admin. account. If the RmtMgr is running as a user and not SYSTEM then the NasMgr/ MarMgr / AbaMgr/ GenMgr will run as this user and have access to Windows networking, shared drives and all. If it is run as SYSTEM then it is limited to only local Windows drives, shares, etc. The QueMgr does not do much in the way of files so running that as SYSTEM is OK.

Note: On Windows if a RmtMgr is running on a local machine, the JobMgr will be started through it as usual, but if a RmtMgr is NOT running then a JobMgr will be started anyway, and the submit will still work fine. The only restriction is if, in this latter case, the user logs off, a popup dialog appears asking if the user really wants to logoff. The job will be terminated if he does. This will not happen if the RmtMgr is running as a service.

Patran Analysis Manager Users GuideAnalysis Manager Programs

96During execution, the NasMgr relays pertinent information (disk usage, cpu, etc.) to the Job Manager (JobMgr), which then updates the graphical information displayed to the user. The NasMgr is also responsible for cleaning up files and putting results back to desired locations, as well as reporting its status to the Job Manager. This daemon runs on the analysis host machine and only for the life of the analysis.

MSC.Marc ManagerThe MSC.Marc Manager (MarMgr executable name) runs only for the life of a job. The MarMgr is identical in function to the MSC Nastran Manager (NasMgr) except it is for execution of MSC.Marc analyses.

ABAQUS ManagerThe ABAQUS Manager (AbaMgr executable name) runs only for the life of a job. The AbaMgr is identical in function to the MSC Nastran Manager (NasMgr) except it is for execution of ABAQUS analyses.

General ManagerThe General Manager (GenMgr executable name) runs only for the life of a job. The GenMgr is identical in function to the MSC Nastran Manager (NasMgr) except it is for execution of general analysis applications.

EditorThe editor (p3edit executable name) runs when requested from P3Mgr when viewing results files or editing the input deck.

Text ManagerThe Text Manager (TxtMgr executable name) is a text based interface to the Analysis Manager to illustrate the Analysis Manager API. See Application Procedural Interface (API).

Job ViewerThe job viewer (Job_Viewer executable name) is a simple program available on UNIX platforms for opening and viewing job statistics for the Analysis Managers database file. This file is generally located in $P3_HOME/p3manager_files/default/log/QueMgr.rdb. You must run Job_Viewer and then open the file manually.

Analysis Manager Program Startup Arguments

AbaMgr, NasMgr, MarMgr, GenMgrStarted automatically by QueMgr (or NQS/LSF); no command line arguments.

97Chapter 7: System ManagementAnalysis Manager ProgramsJobMgrStarted automatically by P3Mgr/TxtMgr (or RmtMgr); no command line arguments.

RmtMgr This is a daemon on Unix or a service on Windows and started automatically at boot time. Possible command line arguments (also see Organization Environment Variables):

QueMgr (AdMgr)This is a daemon on Unix or a service on Windows and started automatically at boot time. Possible command line arguments (also see Organization Environment Variables):

Argument Description-version Just prints Analysis Manager version and exits-ultima Switch to change P3_HOME to AM_HOME, p3manager_files to

analysis_manager so there is no p3 in the environment required. (Generally not used!)

-port Port number to use. MUST be the SAME port number for ALL RmtMgr's for whole network (per QueMgr) default is 1800 if not set.

-path Use to specify base path for finding the Analysis Manager executables: $P3_HOME/p3manager_files/bin/{arch}/*Mgr.

is the base pat

patran_2014_doc_analysis manager user's guide.pdf

Documents

registered trademark

msc software suppliers

registered trademark

msc nastran

party software terms

certain thirdparty software

msc fatigue

trademark of hewlett