Professional Documents
Culture Documents
PDS Project Setup Technical Reference PDF
PDS Project Setup Technical Reference PDF
June 2011
DPDS3-PB-200023H
Copyright
Copyright © 1984-2011 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement;
contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade
secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from
Intergraph Corporation.
U.S. Government Restricted Rights Legend
Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of
the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
P.O. Box 240000
Huntsville, AL 35813
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless
the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed
license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use
of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives
licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement
and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for
resale or redistribution.
Warranties and Liabilities
All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software
or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this
document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes
the information in this publication is accurate as of its publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the
terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not
supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks
of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered
trademarks of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle
Corporation and/or its affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands
and product names are trademarks of their respective owners.
Contents
Preface PDS ................................................................................................................................................. 9
What's New in Project Setup Technical Reference .............................................................................. 10
Introduction ................................................................................................................................................ 11
Introduction
This document describes the procedure to create a PDS project using PD_Shell; however, an
alternate method exists. Express Project Creation is a tool provided with PDS versions 6.0 and
higher that runs in one of two modes---New User or Advanced User. New User mode asks a
minimal number of questions and forces the project to be located on a single node. Advanced
User mode is driven by an ASCII file that you can edit to suit your needs and used repeatedly.
Express Project Creation is described in the PDS Express Project Creation Quick Start Guide.
Project creation through PD_Shell is useful if you want to add a discipline to an existing project
(for example, add an EE Raceway project or insert an existing FrameWorks project).
Even if you use Express Project Creation, there are many important principles addressed in this
document (Windows O/S domains and groups, plotting setup, and so on) that are not described
in the PDS Express Project Creation Quick Start Guide. For this reason, this document is
suggested reading for all PDS project and system administrators.
This document describes the definition of project data and creation of project files including
database files, design files, and seed files. It is specifically designed to support the creation and
revision of project data for use by other PDS modules.
System and project setup is typically done by a system manager because the procedure
requires the use of privileged logins. However, the system administrator needs to consult
with the PDS project manager since certain design choices can be made only at project
creation time.
Other post-creation tasks can be accomplished by other non-administrator users. The
normal operation of PDS does not require administrative privileges.
The instructions in this document are not oriented towards a particular database engine.
Instructions for the installation of some database engines are contained in the appendices. For
assistance installing databases not discussed in the appendices, please see the Intergraph
World Wide Web page (http://www.intergraph.com), or contact Database Support at the
Intergraph Help Desk.
See Also
Concepts and Terminology (on page 13)
In This Section
Server Hardware and Software Requirements .............................. 15
Workstation (Client) Hardware and Software Requirements ......... 16
Software Prerequisites
Adobe Reader (Required to view the Software License Agreement and software
documentation.)
MicroStation J 07.01.05.03 (Must use the Complete setup type.)
PARNU 05.02.00.37
Batch Services 06.01.00.00 or higher
IPLOT Organizer (with Microstation J support)
IPLOTSRV (IPlot Server)
Software Prerequisites
Adobe Reader (Required to view the Software License Agreement and software
documentation.)
MicroStation J 07.01.05.03 (Must use the Complete setup type.)
PARNU 05.02.00.37
Batch Services 06.01.00.00 or higher
IPLOT Organizer (with Microstation J support)
IPLOTSRV (IPlot Server)
RIS Shared Component (Client) 6.1.0.2
SmartPlant License Manager 11.00.17.00 or higher
SmartPlant P&ID 2007 or 2009 (only required on systems that will be used for SmartPlant
P&ID data transfer.)
SmartPlant Engineering Manager (only required on systems that will be used for SmartPlant
P&ID data transfer.)
Consult the Compatibility Matrix on the eCustomer website to determine the appropriate
versions of SmartPlant P&ID and SmartPlant Engineering Manager and any changes since this
publication date.
System Configuration
PDS can run on a stand-alone workstation or in a client-server environment. On a stand-alone
workstation, PDS, the Relational Database Management System (RDBMS), and plotting
software must all be loaded on a local disk. This requires a workstation with substantial
resources (disk, memory, CPU). In a typical PDS project, many users will be working with the
plant data. In addition, these users may be performing different tasks at the same time (2D
schematics, 3D modeling, isometric extraction, report generation, and so on). For this reason,
most projects are set up in a client-server environment.
In a client-server environment, each client machine accesses the resources it needs from
remote servers. These resources can fall into a number of different categories.
Data Execution Prevention (DEP) must be enabled. To check the status of DEP on
a machine, follow these steps:
Windows XP
1. Click Start > Control Panel > Performance and Maintenance > System.
2. Click the Advanced tab on the System dialog box.
3. In the System Startup area, click Edit.
4. In Notepad, find the text /noexecute=optin. Optin is the default setting for DEP and
indicates that it is enabled.
If you see /noexecute=alwaysoff, DEP is disabled. Replace alwaysoff with optin.
Windows 7
1. Click Start > All Programs > Accessories > Command Prompt.
2. In Command Prompt, type wmic OS Get DataExecutionPrevention_SupportPolicy and
press Enter.
3. The returned value is either 0, 1, 2, or 3.
a. A value of 0 indicates that DEP is disabled.
b. A value of 1 indicates that DEP is enabled for all processes.
c. A value of 2 indicates that DEP is set to OptIn.
d. A value of 3 indicates that DEP is set to OptOut and is enabled for all processes.
If the value is 0 (DEP is disabled), enter the following text in the Command Prompt
window to enable it: bcdedit.exe /set {current} nx OptIn.
See Also
Server Functional Descriptions (on page 20)
Server Requirements (on page 21)
File Server
A file server stores the project files associated with a PDS project. This includes seed files,
reference libraries, report format files, the actual 2D and 3D model files, and many other
associated support files. By storing all such files on a dedicated server, backups are made
easier and centralized access control can be established. A file server should have a large
amount of disk space, a tape backup device, and a high-speed networking subsystem.
Database Server
A database server stores the RDBMS used by the PDS software. Its requirements are similar to
those of the file server. Many users choose to use a single machine as the file and database
server for small-to-medium sized projects.
Software Server
Intergraph recommends that, for optimal performance, client machines be provided with
sufficient disk space such that all frequently used applications can be loaded locally. However,
infrequently used applications can be loaded in client mode. In this configuration, the client
machine mounts a disk from the software server and runs the software over the network. This
can place a significant load on the network, so it is not suggested for heavily used applications.
Compute Server
When a large number of jobs are being run that consume significant amounts of CPU time
(hidden line removal, large reports, isometric extractions, clash detection, and so on), it can be
advantageous to set up a compute server. In this configuration, the client workstations
reconfigure their local batch queues to be pipe queues that point to the compute server. When
batch jobs are submitted by the clients, they are redirected to the compute server, which
performs the calculations and returns output to the client.
Plot Server
Depending on the number of plotting devices in use, the number of plots being produced, and
the size and type of the plots, it can be advantageous to set up a plot server. This machine has
all I/O cards required to interface with the plotting devices, all server plotting software, and
sufficient memory to cache certain kinds of plots (typically large raster plots).
advantage to have a knowledgeable system administrator on staff who can monitor overall
system performance and identify trends in system usage that will point out when a particular
server is reaching the limits of its resources.
Server Requirements
File Server
We recommend that the file server run a Windows Server operating system. Clients computers
can access remote files using the networking software that comes delivered with Windows.
There is no reason why a computer running a non-server version of Windows cannot function as
a server, but there are restrictions that can limit its usefulness (for example, a maximum of 10
mounts per share).
Database Server
PDS accesses the database using the Relational Interface System (RIS). RIS allows a single
version of PDS to work with databases from various vendors in a manner that is transparent to
the PDS software. In the majority of installations, TCP/IP is the preferred communication
protocol. Other supported protocols include the DECnet protocol (DNP) and the Xerox
Networking System (XNS).
RIS is a client-server package; client machines running PDS access the database through the
RIS Client software (loaded on the client), which then communicates with the database through
a RIS data server (typically resident on the database server). The RIS client software comes
with PDS (RIS Shared Component, as seen in the PDS Component Loader). If the database
resides on a server running an operating system that is not supported by RIS, the option exists
to have the RIS client and server modules located on the client machine, and then access the
database through the database vendor's networking tools. This allows the database server to be
any machine supported by the database vendor. See Relational Interface System (RIS) (on
page 37), for a detailed description.
In addition, the database server needs to have a high-speed disk subsystem (to access data
efficiently) and a high-speed networking subsystem (to retrieve and send data to the network).
Modern servers are designed for these purposes, incorporating RAID (Redundant Array of
Independent Disks) technology and multiple networking cards as part of the basic design.
However, even the fastest server will be crippled if the physical network is not up to the task.
Software Server
A software server's requirements are identical to those of the file server. If the PDS software is
loaded in client mode, it will need to access the same software loaded in server mode using
LAN manager. The software server must have sufficient disk space to load all required PDS
products.
Compute Server
A compute server should have a powerful CPU (typically more than one) and a large amount of
main memory to allow it to complete its tasks without having to resort to swapping (where the
unused portion of a program, and/or the files it is accessing are temporarily stored on hard disk).
Because the compute server must run the PDS software, it must run a supported version of
Windows.
Often, the compute server will mount required resources from the file server. This will require
LAN Manager. It will also need to access the database through RIS. It will need to have Batch
Services loaded so client nodes can pipe batch jobs to the server.
Plot Server
The InterPlot product suite is a comprehensive plotting production system that supports a large
variety of plotters. InterPlot is designed on a client-server model, similar to RIS. Client
computers running PDS submit plots through the IPLOT client, which communicates with the
plotter through the IPLOT server software. In addition to the IPLOT server software, the plot
server may require an IPLOT metafile interpreter to deal with the specific characteristics of a
particular plotter. Plots are typically submitted across the network using TCP/IP or XNS. In
addition to the IPLOT software, Batch Services may be required on the plot server. See System
Administrator Responsibilities (on page 131) for a detailed description.
Software Prerequisites
For more information, see the Software Prerequisites section in Server Hardware and
Software Requirements (on page 15).
Computer Preparation
1. Log in as an administrator with local administration permissions.
2. Create a temporary folder on the C:\ drive, such as C:\temp. Ensure the folder security
allows users to write, read and execute. This should include the Intergraph Batch Manager
account.
3. Create a share for the temporary folder with the same permissions described in the previous
step.
4. Create the following folder structure: C:\win32app\ingr\share\.
5. Enable Remote Registry service, this service is not on by default in Windows 7.
If the Remote Registry service is not running, some of the batch processes
might fail.
Registry Modification
Use extreme caution when modifying the registry. If you are unsure of what steps to
take, please contact Intergraph Support.
1. Start the Registry Editor (regedit.exe).
2. Locate the HKEY_LOCAL_MACHINE\SOFTWARE folder and create an Intergraph folder
by selecting Edit > New > Key.
For 64-bit operating systems, add the new key in the
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node folder.
3. Create a string value named Common in the Intergraph key with a value of
C:\win32app\ingr\share.
4. Add a new DWORD (32-bit) Value (Edit > New) named DisableUNCCheck with a value of
1 to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Process key.
Choose the 32-bit DWORD type regardless of your operating system architecture.
5. Locate the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\WINRE
G folder
There are three methods for modifying this key:
Add the shared folders on the server to the allowed paths in the WINREG key. To add
all allowed paths, enter System\CurrentControlSet\Services\LanManServer\Shares
as the value for the AllowedPaths key in the WINREG folder.
Grant access permission to the users or user groups from within the Registry Editor
from the Edit > Permissions command.
Delete the WINREG key.
Installation
1. Install SmartPlant License Manager.
After installation, and in order to use a license to run PDS applications, you must run
SPLM as an administrator by right-clicking the start menu item and selecting Run as
administrator. Click Yes on the User Access Control dialog box.
2. Configure SmartPlant License Manager to point to the license computer. Do this in
SmartPlant License Manager by selecting Configure and Test > Select License Machine
for Client.
3. Perform a complete installation of Microstation J.
4. Install RIS Client. After installation, you must configure the RIS Client.
a. Select Start > All Programs > RIS > RIS Schema Manager.
b. Click Schema File, and select Show Schema File Location.
c. Click Locate Schema File.
d. Type the path of the schema file and filename in the Schema File Name field.
e. Click OK.
5. Install Intergraph Batch Manager.
6. Install PDS Applications. After installation, you must locate the pds.cmd file and configure
the batch queues.
a. Log in as an administrator.
b. Select Start > All Programs > PD_Shell > PDS Configure. Select Yes on the User
Access Control dialog box.
c. Locate the pds.cmd file with the Browse command.
d. Select Local Machine in the Update Registry Entry for section. This will setup the
location of the cmd file for anyone that has not already chosen to point the registry entry
to their “Current User” profile in the registry. Note that Current User entries override the
Local Machine entries for pointing to the pds.cmd file.
e. Click OK.
f. Select Start > All Programs > PD_Shell > PDS Queue as an administrator.
g. Select Yes on the User Access Control dialog box.
If you are not an administrator on the computer, the queue creation process fails.
If PDS2D was installed on the computer, the path variable in Environment Variables
must have the PDS path variable before the PDS2D variable.
File Systems
Windows support a number of file systems --- FAT, NTFS, and HPFS. A full description of the
differences can be found in the documentation that accompanies Windows. Comments on each
are listed below.
Intergraph recommends that NTFS be used on all nodes. It offers a more robust file
recovery/corruption checking scheme as well as complete Windows security.
Under Windows, FAT now includes support for long file names. Some limited testing of PDS
using FAT file systems has been done, but since FAT offers very little security (only on
shares) it is not recommended for use with PDS.
PDS has not been tested using HPFS.
Client Nodes
All client nodes that will run PDS must have TCP/IP loaded. In Server Nodes (on page 28),
many other networking services are described - but at minimum, TCP/IP must be installed.
TCP/IP is essential for the operation of the PDS Licensing software and RIS.
Server Nodes
Any computer running Windows can, in a limited manner, function as a server. There are
limitations on the maximum number of client computers that can mount a share (10-users), and
also many of the advanced networking functions require at least one node on the network to run
Windows Server.
RAID
Servers can come with built-in support for hardware RAID (Redundant Array of Independent
Disks). RAID provides two primary benefits.
1. Performance---Data can be striped across drives, boosting performance of read operations.
2. Reliability---Certain RAID configurations offer protection from data loss due to disk failure.
If your server came with the operating system preloaded, then a RAID configuration of some
type has already been set up.
Before loading additional software and configuring network services, be sure to
examine the RAID configuration to determine its suitability for the system's intended use. If
changes to the RAID subsystem are required, the operating system and all software
components will have to be reloaded after reconfiguring RAID.
See RAID Configuration (on page 159), for a technical overview of RAID.
User Accounts
A Windows domain is a collection of computers that share a common user account database.
This allows all computers in the domain to be treated as a single unit for management of user
and group accounts. It provides a benefit to users when they browse the network for available
resources (since nodes are grouped by domains), and it makes it easier for system
administrators to manage the network. We recommend that a Windows domain be created and
that domain accounts be used. Additional information about planning, creating, and
administering domains can be found in the Windows documentation.
4. Click the Data Execution Prevention tab and check the setting.
5. Apply your changes and exit the Performance Options dialog box.
6. Click OK to exit the System Properties dialog box.
From a system running Windows 7/Server 2008, or later:
1. Right-click on Computer in the Start menu.
2. Select Properties.
3. Under Tasks, click Advanced system settings.
4. In the Performance section, click Settings.
5. Click the Data Execution Prevention tab and check the setting.
6. Apply your changes and exit the Performance Options dialog box.
7. Click OK to exit the System Properties dialog box.
Software Compatibility
Download the PDS compatibility matrix (a Microsoft Excel spreadsheet) from the Intergraph
Knowledge Base (www.intergraph.com) for information on compatibility of PDS products with
MicroStation, Windows, databases, and other supporting products.
When finished loading software, check the PATH variable (in Control Panel > System) to
check for quotes (") in the system PATH. If you find that the batch processing software has
added quotes, either move the directory paths with the quotes to the end of the PATH
statement or remove the quote marks (if the directory path does not contain spaces). PDS
path statements must appear before path statements with quotation marks.
If you are running Windows 7, you cannot interact with the desktop during the Batch
Services installation process. Batch Running Script (BatchRunning.zip) is a utility that monitors
and reports the installation progress in your Taskbar.
Database Software
All client computers must have the RIS client software installed to access the database. The
database server will also need to have the RIS data server for the database in use. See
Relational Interface System (RIS) (on page 37), for more information.
In certain situations, depending on which products have been loaded, you may find
that multiple versions of the RIS client software exist on a particular computer. We suggest that
the Configure RIS version utility be used to remove older versions of the RIS client software.
Having multiple versions of the RIS client software loaded can lead to problems.
The database software must also be installed on the server. In most cases installing the
database is a two-part procedure:
1. Installation of the actual database product (which typically takes you through a procedure
where disk space is set aside, administrative users are created, backup devices are
designated, and so on).
2. Creation of individual databases for use by a particular PDS project. These steps are
described for a number of database products in the appendices.
For assistance with a database not covered in the appendix, consult Intergraph's web page
(http://www.intergraph.com), or contact the Database Support at the Intergraph Help Desk.
MDAC
Any client computers that will perform drawing resymbolization or data transfer from SmartPlant
P&ID should have the Microsoft Data Access Components (MDAC) loaded.
Oracle Client
If Oracle is being used as the relational database for the SmartPlant P&ID project, any client
nodes that will perform data transfer from SmartPlant P&ID should have Oracle client loaded.
4. When you start the PDS component loader, you are prompted to enter your name and serial
number.
If you have purchased FrameWorks Plus or PDS PID Standalone separately from
PDS, then you should have a FrameWorks Plus or PDS PID Standalone serial number that
is separate from the PDS serial number. These products should be loaded with the
individual product's serial number.
5. After entering this information, the Intergraph PDS Component Loader dialog box
displays.
SmartPlant License Manager and RIS Client are not included in the Component
Loader. They are delivered on the PDS CD, but must be installed individually.
6. When you choose a specific product to load, a dialog box showing its load options displays.
7. If you choose Local as the installation type, the software is loaded to the local disk. If you
choose Client as the installation type, the Server Name field becomes active, and the
Local install path field changes to Server install path. You must now enter the software
server name and the path where this PDS product was loaded in server mode. If you
choose Server as the installation type, the Local install path changes to Server install
path.
8. All client nodes must have PD_Shell and SmartPlant License Manager (SPLM) loaded to
the local disk. Other products can be loaded local or in client mode. Frequently-used
products should be loaded locally, while infrequently used products can be loaded in client
mode.
9. The node from which projects will be created must have all required products loaded locally.
An exception is the 3D reference data, RDUSRDB or RDDINRDB, and the PDS 2D
reference data, both of which can be loaded on a server and referenced from the client node
during project creation. If projects are created using Express Project Creation/New User
Mode, then the required reference data must be loaded locally.
The Component Loader runs a check of the registry key string
HKEY_LOCAL_MACHINE > SOFTWARE > Intergraph > Common in preparing for delivery
of the RIS Shared Components. If this registry keystring does not exist, the Component
Loader creates it with a value of c:\win32app\ingr\share. If the keystring does exist, it must
be no longer than 22 characters and must not contain any spaces. If either of these rules is
violated, a warning dialog box displays, and the RIS Components will not be delivered. See
Registry Entries (on page 297) for more information.
10. When you select the PDS components to load and click the Load Components button, the
Online Software License Agreement displays.
In This Section
Why RIS? ....................................................................................... 37
How RIS Communicates with the Database.................................. 37
Database Structure ........................................................................ 38
3D Schemas .................................................................................. 39
2D Schemas .................................................................................. 40
Why RIS?
When Intergraph first developed applications that used databases, those applications were hard
wired to a particular database type. To support the use of a different database type, another
version of the application software would have to be written. A methodology was required such
that a single version of an application could interface with multiple database types---the solution
to this problem is RIS.
RIS decouples the database from the application. By doing so it allows multiple client nodes to
share a single copy of the database. RIS includes the networking software to access the remote
database, saving you money by not requiring the use of the database vendor's networking
software.
A RIS-enabled application (such as PDS) issues commands to the RIS client software. Typically
the RIS client software that is used is that loaded on the local machine; however, RIS supports a
locate client function that allows RIS to use the client software located on another node.
The use of the RIS locate client operation can lead to problems unless it has been
recommended by Intergraph Support.
The RIS client software reads the parms file that resides in the RIS product directory on the local
node. The parms file tells RIS where to find the schemas file. The schemas file can reside on
the local node or on a server, and contains a list of all accessible databases on the network.
Having found the information required to locate the database from the schemas file, RIS
establishes a connection to the database via the RIS data server. The RIS client issues
database-independent requests for information, and the RIS data server translates these into
database-specific requests for information.
In fact, RIS locates databases in a manner similar to how PDS locates projects.
The schemas file and the proj file serve similar functions---they allow the client application to
resolve a name into a location. The client application uses these files to locate projects and
databases anywhere on the network. Projects and databases can be located on multiple server
nodes, yet all can be listed in a single proj file/schemas file.
Database Structure
All databases have certain features in common. A database consists of tables, columns, and
rows.
3D Schemas
PD - Project control schema. Contains the location of the project (3D, 2D, EE, FW) and all
associated reference data
DD - Design schema. Contains information specific to each 3D piping (and optionally
equipment) model.
RA - Approved reference schema. Contains approved reference data.
RU - Unapproved reference schema. Contains unapproved reference data.
EE - EE Raceway project schema. Contains information specific to each EE Raceway model.
RE - EE Raceway reference schema. Contains EE Raceway reference data.
See the Project Administrator (PD_Project) Reference Guide, for a list of the tables and columns
for each of these database schemas.
2D Schemas
PD - Project Control Data. Contains the location of all drawings and the 2D reference data.
PID - P&ID Task Schema. Contains information specific to each 2D PID drawing.
PIDM - P&ID Master Schema. Contains information posted from the PID schema.
PFD - PFD Task Schema. Contains information specific to each 2D PFD drawing.
PFDM - PFD Master Schema. Contains information posted from the PFD schema.
IN -- IDM Task Schema. Contains information specific to each 2D Instrument and associated
devices.
INM -- DM Master Schema. Contains information posted from the IN schema.
INR - IDM Reference Schema. Contains IDM reference data.
In addition to these schemas, there can be a backup schema for each of the schemas
listed above (PDBK, PIDBK, and so forth). The backup schemas can be used when retrieving
2D data from archives.
In This Section
Establishing Domain Users and Groups ........................................ 41
Location of the proj File ................................................................. 41
Location of schemas File ............................................................... 49
Creating Batch Queues ................................................................. 52
Establishing Account Mapping....................................................... 53
Creating Project Directories and Required Shares ....................... 54
Files Reside on a Windows Server ................................................ 56
h:\projects
h:\projects\project1
h:\projects\project2
h:\projects\project3
You could place proj files in the project1, project2, and project3 directories, and then share the
directories with different settings, to allow stricter control of user access by project, rather than
by drive.
See Also
Sharing the proj File Location Through LAN Manager (on page 42)
Default C Drive Permissions (on page 44)
Universal Naming Convention (on page 45)
The next dialog box shows a Share Name of <drive>$, where <drive> is a drive letter (C, D, and
so on).
You can add a comment, and then click Permissions to add or remove privileges on the share,
but as discussed earlier, we suggest that permissions be applied to files and directories, not
shares.
Note that the local administrators group (JOENS\Administrators) has full control on all files on
the C drive. Adding additional domain users into the local administrators group also grants them
the same privilege. If your server is running Windows Server, these would be the default
permissions:
from a PDS project residing on a Windows-based server are accessed through PDS using
MicroStation 5.5, no mounts are seen through Windows Explorer. The same project, accessed
through PDS using MicroStation 5.0 results in visible mounts being made for the proj file and
models.
We recommend that you copy the PDS.CMD file to a location outside of the PDS installation
folders. This will prevent your command file from being overwritten if the PDS software is
re-installed, and allows you to use a different control file for each user on the computer.
For example, assume that you are logged in to the computer that is primarily used by Mary as
PDS\mary. Also assume that Mary has a folder c:\users\mary where her personal files are
stored. Other users may log into this computer and work while Mary is gone and would need to
access the pds.cmd file. Assume that another folder named c:\users\pds has been created for
the purpose of storing common files and that PDS\domain users have full control on this folder.
Local Machine - Select this option to save the PDS.CMD file location for everyone who logs
into this computer. All users will use the same PDS.CMD file. To continue the example above,
the PDS.CMD file should be placed in the c:\users\pds folder and the Local Machine option
selected.
Current User - Select this option to save the location of the PDS.CMD file for only yourself (the
username currently logged into the computer). Select this option to allow each user to have a
personal PDS.CMD file with personal settings and configurations. To continue the example
above, Mary would put the PDS.CMD file in her c:\users\mary folder and select the Current
User option.
PDS checks for administrative privileges of the current logged-on user. If you are an
administrator on the computer, both Local Machine and Current User options are available.
PDS reads the current user registry first to populate the data and if no entry for the current user
is found, then the local machine registry is read for data.
If you are logged on as a user without administrative privileges on the computer, you can
only write to the Current User settings. You will receive an error if you try to write to the Local
Machine settings.
If you are not sure of the location of the control file, click Browse to search the folders on your
computer, or on a networked computer, to specify the control file to be used.
In addition to storing the project file, the folder that you specify for the project file also
stores other important files related to PDS project administration. This folder should be backed
up on a regular basis.
All clients should be set up to have their pds.cmd file pointing to the same project file on the
server. The exception, however, is in certain cases where many projects are being managed.
Some system administrators prefer to maintain multiple project files, each listing a number of
related projects.
Click Modify to specify the computer name and the folder on that computer in which the project
file (proj_file) will be created (or where it already exists). If the PDS.CMD file does not exist in
the specified folder, PDS will ask if you want to copy the default PDS.CMD file to the specified
folder. Click Yes to copy the PDS.CMD file. After the file is copied, the Modify PDS 3D Control
File dialog box displays.
PROJ_FILE - Specifies the location of the proj_file on the computer specified by PROJ_ADDR.
The proj_file contains the location of all projects on the network. Be sure to include the closing
slash in the PROJ_FILE field.
PROJ_ADDR - Specifies the computer name and share on that computer that contains the
proj_file. If the proj_file is on a networked computer, type the name of the computer, a back
slash, and then the share name. In the example above, the computer is named "docdata" and
the share is named "d".
The Networked Delivered Product Data fields are set to the location where PDS 2D is loaded
on the local machine. These fields should not require any changes. However, the Optional
Project Data fields need to be changed. The Database Proj File Path can be set to the same
location as that used by PDS 3D. You can use Browse to set this location, or type it directly into
the field. If you browse to an empty directory, a warning message displays.
If you click Browse, you will notice that separate fields are not provided for the node name and
the path. If you click Network to mount a drive from the server and select the proj file location,
the server will be mounted locally, and the proj file location will be set to the mount point. For
example, if the C drive from the server CADSRV is located through Browse, it is mounted as the
F drive. After selecting the projfile60 directory and clicking OK, the proj file location will be stored
as F:\projfile. For this to work, the server would have to be mounted as the F drive every time
you wanted to start PDS 2D. A better way to specify a remote proj file directory is to use the
Universal Naming Convention (UNC) format. In this example, the location of
\\CADSRV\c\projfile60 could be entered directly into the Database Proj File Path field.
The Graphics Only Project Files Path is set to a location where PDS 2D graphics-only
drawings are stored. The 2D disciplines (2D, PID, PFD, IDM) support the use of drawings that
are graphics only or graphics + database. A drawing created in graphics only mode can be
attached to the database at a later time if required. In this example, a new directory named 2D is
created under the c:\testproj\models directory for storing graphics-only drawings. The location of
graphics-only drawings is not stored in the database, therefore PDS 2D needs an alternate
means of determining where these drawings are stored. This information is stored in a file
named example.gpr which must be copied from the \pds2d\cfg directory into the project
directory. Once copied into the project directory, its name can be changed as long as the
extension remains .gpr. The information in this file must also be updated to match your
installation. An example file (named testprj.gpr) resides in the c:\testprj\project directory.
c:\testprj\2d\pds2d\
c:\testprj\2d\pid\
c:\testprj\2d\pid\forms\
c:\testprj\2d\pid\menus\
c:\testprj\2d\pfd\
c:\testprj\2d\pfd\forms\
c:\testprj\2d\pfd\menus\
c:\testprj\2d\pds2d\
The first seven lines have been modified to specify the reference data copied to the project
directory, and the last line has been modified to specify where new graphics-only drawings will
be created. The location of this file must be entered into the Graphics Only Project Files Path
on the Set Options form. The convention for locating this file across the network is the same as
used with the Database Proj File Path (use UNC path).
Using TCPIP
To use TCPIP as the protocol, you have to install and configure FTP Server on the server node
(this procedure is not required for the clients). For Windows, you need to install Microsoft Peer
Web Server. For Windows Server, you need to install Microsoft Internet Information Server.
1. Click Start > Settings > Control Panel. Double-click on Network, and then select the
Services tab. Click Add.
2. Select Microsoft Peer Web Server on a Windows Workstation system or Microsoft
Internet Information Server on a Windows Server system. Click OK.
3. Enter the location of the Windows distribution media and press ENTER.
4. Click OK on the Welcome form to display a checklist of components which can be loaded.
The only required option is FTP Service. Selecting FTP Service will automatically select
Internet Service Manager as well. Click OK to install the required files into the default
directory.
5. The next form shows the default FTP Publishing Directory. This is the directory a user will
be put into if they establish an FTP session and the user they log in as does not have a
home directory specified. This can be changed to c:\temp. Click OK to install the FTP
Service.
6. You may get the message "The guest account is enabled - do you want to disable guest
access to the FTP service?" Clicking Yes is a prudent choice. The installation is complete
and you can exit out of Control Panel.
7. Click Start > Programs > Microsoft Peer Web Services > Internet Service Manager (on
a Windows) or Start > Programs > Microsoft Internet Server > Internet Service Manager
(on a Windows Server node). You should see an entry for your node and that the service is
running.
8. Double-click on the node name to activate the FTP Service Properties form. Disable Allow
Anonymous Connections (an optional choice - if taken, accept the form warning about
passwords being passed over the network) then select the Directories tab.
9. You should see an "Alias" for the home directory (c:\temp in this example). In this example it
is assumed that the schemas file is located somewhere on the C drive. Click Add. For the
directory, browse to the C drive and click OK. It should enter C: into the Directory box.
Make sure that the "Virtual Directory" button is selected, enter C: for the Alias.
The colon (:) after the drive letter in the alias name is critical! It must be included as
part of the alias name or RIS will find the schemas file but not display the schemas. At the
bottom of the form also make sure that Read and Write have been selected.
10. Click OK on the Directory Properties form. In the FTP Service Properties form you should
see the entry for your drive. Make sure that the colon (:) is included as part of the alias
name. Click OK on the FTP Service Properties form to apply the change. Exit from the
Internet Service Manager form.
11. Test the FTP service by going to another client open a DOS window and type ftp <server
name> to open a connection to the server. Type a valid login on the server, type dir to list
files in the c:\temp directory. Type get filename where filename is some file in the c:\temp
directory. This simply tests the FTP connection.
The username you specify in the Locate Schema File form must also be able to log in
at the FTP prompt as described above.
12. You can now do a Locate Schema File from a client node and specify TCPIP as the
protocol.
In this example, a file named schemas in the c:\ris directory on the server CADSRV has
been specified. The username/password is a login in the PDS domain that has the right to
log on locally on the server. In this example, the generic user pds has been used. All client
nodes should use the same operating system username when locating the schemas file.
When you click Apply, the system writes the location of the schemas file on the server into
the parms file. The schemas file is not created until a schema is created. As with the
proj_file directory, the directory where the schemas file is located should be backed up
regularly.
The Locate Schema File operation should be performed on all client nodes so that they all
refer to the same schemas file on the server. There is an exception to this rule, however. In
certain cases, where many projects are being managed, some system administrators prefer
to maintain multiple schemas files, each listing a number of related projects.
Note that in order to create the queues, you must be logged in as an administrator. In fact, you
need to be logged in as a user having administrator privileges who also has access to the
directory where the proj file is located. This is because the PDS Queue Creation Utility accesses
the queue.lst file, which is located in the same directory where the proj file is located. The
domain administrator meets both requirements - this user is added into the administrators group
of the local node automatically when the node joins the domain, and this user has access to the
share on the server where the proj file is located. In the PDS Queue Creation dialog box,
queues for all products have been selected for creation. By clicking Read Data from Local
Machine, the utility does not read information from the queue.lst file, but instead checks for
batch queues on the local machine. The fact that Remote Node was not selected for any of the
queues means that the created queues are batch rather than pipe queues. Jobs submitted to a
batch queue are processed locally, while jobs submitted to a pipe queue are routed to a remote
server.
When exiting the queue creation utility, you are asked whether or not you want to save the
queue information in the queue.lst file. The queue.lst file is stored in the same directory as the
proj file. The queue.lst file becomes important when redirected batch operations are done. See
System Administrator Responsibilities (on page 131), for a description of how to change from
batch queues to pipe queues.
See Also
Establishing Account Mapping (on page 53)
3. Any user in the PDS domain is mapped to the generic username pds. If the active user is a
member of the PDS domain and submits a batch job, this job has access to all system
resources that user pds has been granted access to. If a user who is not in the PDS domain
submits a batch job on this node, it fails since no account mapping for any other domain has
been set.
4. Any user in any domain is mapped to the generic username pds in the PDS domain. A batch
job submitted by any user (who must have the right to log on locally) has access to all
system resources to which that user pds has been granted access.
The account mapping specified in example (3) is the preferred mapping. All users are mapped
to a common user for the purposes of batch processes. If the user is not logged in to the PDS
domain, then the batch job fails. This forces users to use their domain logins. For this to work,
the PDS\pds user must have access to all files required to complete the batch job. In addition,
the PDS\pds user must have the right to log on locally as specified in User Manager under
Policies > User Rights. If you have granted PDS\domain users the right to log on locally, then
the PDS\pds user need not be added to the list.
There is an exception to this suggested account mapping if batch plots are submitted to
connected plotters, then users will need to be self-mapped. See System Administrator
Responsibilities (on page 131) for more information.
If you are having problems with PDS batch jobs - be sure to check the Event Log. Often
times you can find a message in there that will help you find the problem.
Some system managers might attempt to use Batch Services account mapping as a way to
control access to system resources. This can be done, but often leads to end-user problems
such as the job running correctly when submitted interactively, but not when run in batch mode.
Intergraph PDS Support recommends that Batch Services account mappings be minimally
restrictive, and that access control to system resources be accomplished using Windows file
permissions and PDS Access Control.
If problems are encountered while performing PDS batch jobs, the associated log file(s) should
be checked. See Log Files Produced by PDS Batch Jobs (on page 179), for a listing of the log
file(s) produced by each PDS batch job.
Domain Groups
A domain and domain user names have been created for use by all PDS users. In addition,
multiple users can be assigned to a group, so that access to resources can be granted to many
users at one time. Consider a continuation of the previous example:
Users can also be a member of more than one group (mary), but in some cases one group may
encompass those privileges provided by another group. For example, making mary a member of
the administrators group probably grants her all of the privileges of the designers group and
more. Because of this, her membership in the designers group may not be necessary. Also, a
domain user is automatically a member of that domain's users group (janice).
can set up access to the \projdir\eerway such that only Raceway designers have full control,
while other users have read access only. Another example would be to share each project
directory with only the users working on that project.
In This Section
Creating Project Directories Manually ........................................... 62
Creating the 3D Project (Equipment and Piping)........................... 64
Creating a FrameWorks Project .................................................... 70
Creating the EE Raceway Project ................................................. 72
Adding Tables to the EE Raceway Reference Schema ................ 73
Changing Coordinate Systems and Working Units ....................... 79
Creating PE-HVAC Projects .......................................................... 81
Creating the 2D Project ................................................................. 89
Adding Disciplines to an Existing Project ...................................... 93
This directory structure and the reference data copied into these directories are described in the
following sections.
Beginning with PDS 8.0 SE, the PDS interface allows you to enter a share name for
various path locations, rather than requiring the entire path including the drive letter, as was the
case in previous versions. As such, you can use individual shares to control access to the
different models and data in the PDS project without sharing the entire drive. For example, you
can set up access to the \projdir\eerway such that only Raceway designers have full control,
while other users have read access only. Another example would be to share each project
directory with only the users working on that project.
projdir\2d - This is the default location for the 2D reference data. This directory is specified
when using the PDS 2D Seed Reference Data dialog box. 2D reference data requires an
additional 30MB of hard drive space.
projdir\clash - This is the default location for interference detection plots and reports.
projdir\design_review - This is the default location for data associated with the SmartPlant
Review session data such as the control file, label files, and copies of models.
projdir\dwg - PDS sorts orthographic drawings by a 3-digit numeric code representing the
drawing type (code list 2000). For example, foundation drawings are designated as type 535
drawings and stored in the 535 directory.
The border directory contains default border files copied from the PD_Draw product
directory.
The cell directory is the default location for cell libraries used in drawings.
projdir\iso - This is the default location for isometric drawings.
projdir\model_builder - This is the default location for Model Builder APL files.
projdir\models - This is the default location for architectural, equipment, HVAC, and piping
models.
projdir\project - This is the default location for project data such as seed files, clash marker
files, and other project-wide files. These files are copied into this directory during the project
creation process.
projdir\raceway - This is the default location for an EE Raceway project.
projdir\rdb - This is the location for the majority of the 3D reference data, The eqp directory
contains the approved and unapproved reference data for the PD_EQP application. Three files
are copied into these directories by the script:
zi_eqpms.hlp---PD_EQP parametric Help file
zi_eqpms.lib---PD_EQP graphic commodity library
zi_tutlib.lib---PD_EQP tutorial library
This reference data is described in the Equipment Databases and Libraries section of the PDS
Equipment Modeling (PD_EQP) User's Guide.
The lib directory contains the approved and unapproved reference data libraries for both the
PD_EQP and PD_Design applications. In some cases, files copied into these directories have
the same name with different extensions (for example, assembly.l and assembly.l.t). In such
cases, just the .l file name is listed below:
assembly.l---Piping Assembly Library
labels.l---Label Description Library
long_bom.l---Long Material Description Library
pipe_gcom.l---Piping Graphic Commodity Library
pjs_tbl.l---Piping Job Specification Table Library
short_bom.l---Short Material Description Library
spclty_bom.l---Specialty Material Description Library
std_note.l---Standard Note Library
us_pcdim.l---Physical Dimension Table Library
This reference data is described in the Reference Data Overview section of the Reference Data
Manager (PD_Data) Reference Guide.
The source directory is the default location for neutral files.
The spec directory is the default location for PDS neutral files.
projdir\report - This is the default location for report format, discrimination, search criteria, and
output files.
If the proj file is empty (no existing projects), then PD_Shell bypasses this form and displays the
Project Administrator main menu.
If the proj file is empty, PD_Shell bypasses this form and displays the Project Data main menu.
Set Model System of Units and NPD_System of Units to the required settings. Type a Project
Number, and press RETURN (or TAB). The project number should agree with the project name
as specified in the script used to create the project directory structure (testprj, in the following
example).
The system checks to see if this project exists. If it does, those items that have already been
created for that project become unavailable (Project Control Schema, for example), and those
items that have not been created for that project or items for which more than one per project
can be created (FrameWorks Project, for example) become available.
Assuming that the project does not exist, the cursor moves to the Project Name field, and you
can add additional project information. Enter the node name and location of the project directory
in the Network Address field. Following the example, the directory would be set to
c:\testprj\project. It is important that the project subdirectory be specified so that all project
control data is stored in the correct location.
After you have specified all of the project information, you can set the three toggles on the right
side of the form.
Create/Do Not Create DBAccess tables - If set to Create, this option creates an mscodelist
table and a set of join tables for each Standard Note type. See Chapter 4, Revise Project---
DBAccess in the Project Administrator (PD_Project) Reference Guide for additional information.
Many of the PDS databases do not have a mscatalog table, and many of the PDS tables do not
have an mslink column. By default, DBAccess looks for this table in the database and this
column in the selected table and expects the mslink column to have unique integer values. You
can use the environment variables DBA_NO_MSCATALOG and DBA_MSLINK to tell DBAccess
to build its list of database tables from the database rather than from the mscatalog table and to
use a column other than mslink as the key column. For example, in the PD schema,
pdtable_113 has a column named model_index_no that has unique integer values. By setting
DBA_NO_MSCATALOG=Y and DBA_MSLINK=model_index_no, you can use the DBAccess
Edit Database function on this table and scroll through the available records.
Create/Use Existing Reference Schema - If set to Create New Reference Schema, the
software prompts you to create a new Material Reference Database when you click Piping
Approved RDB Schema. You also have the option to create an unapproved database.
If this toggle is set to Use Existing Reference Schema, the system displays a list of existing
projects when you click Piping Approved RDB Schema. Selecting a project name from this list
determines the name of the approved (and optionally unapproved) Material Reference
Databases. The Piping Unapproved RDB Schema button disappears---if the selected project
had both approved and unapproved reference databases, then the new project has both. If the
selected project has only an approved schema, then the new project has only an approved
reference schema.
Create/Use Existing Raceway Reference Schema - If set to Create New Raceway
Reference Schema, you are prompted to create a new EE Raceway reference schema when
you click Raceway RDB Schema.
If this toggle is set to Use Existing Raceway Reference Schema, the system displays a list of
existing projects when you click Raceway RDB Schema. Selecting a project name from this list
determines the name of the EE Raceway Reference Schema.
The system displays a list of all projects, whether they have EE Raceway reference
schemas defined or not. You must make sure that you have chosen a project with an EE
Raceway reference schema. Express Setup will verify this for you.
At this point, the Create Project form might look like the following figure.
Click Project Control Schema to display the Create Schema form for the PD schema.
See the appendices for instructions on completing this dialog box for a number of different
databases.
Press TAB to move from field to field in the Create Schema dialog box.Pressing
RETURN is the same as clicking Apply.
After this information is complete, click Apply. The software dismisses the dialog box and stores
the information in memory.
There is an important difference between Express Project Creation and manual project creation.
During Express Project Creation, schemas are created immediately. If the information is
incorrect, you are given the option to enter the information again before proceeding to the next
schema. During manual project creation (described in this chapter), information for all schemas
is entered before any are created. For this reason, it is important that you understand the
various fields on the Create Schema dialog box, and make sure to complete them correctly the
first time.
After entering the information for the Project Control schema, create the Piping Design schema.
Clicking this button displays the Database Structure Revision form.
This form adds user-extended attributes (columns) and makes other modifications to the Piping
and Equipment tables in the DD schema. See Piping Design Schema in the Project
Administrator (PD_Project) Reference Guide for more information.
You can add 24 attributes to each piping table (the first five entries in the list). Attributes can be
added to the piping tables even after the project and piping models have been created. You can
add 10 attributes to each equipment table (the last two entries in the list) at this time, but you
cannot add attributes to the equipment tables after the project has been created. If you are not
adding attributes to the DD schema, click √ without making any changes. The Create Schema
dialog box for the DD schema displays.
After completing this dialog box, click Piping Approved RDB Schema to display the Create
Schema dialog box for the RA schema.
If you want to maintain approved and unapproved versions of the piping reference data, click
Piping Unapproved RDB Schema to display the Create Schema dialog box for the RU
schema.
At this point, you can click √ on the Create Project form to create a 3D-only project. If you are
using FrameWorks, EE Raceway, or PDS 2D with this project, they can be added in now or after
the project has been created.
To avoid creating models with incorrect working unit settings, adjust the working unit
settings of FrameWorks Plus and Raceway seed files after creating the projects, and before
creating models.
For workshare projects; that is, projects for which the design work will take place at different
locations, you can use the Site Administrator commands to set different Site IDs for the various
design offices. The Site ID can be used to designate ownership of models and drawings by
design office, and to help transfer models and drawings among sites. Refer to the Project
Administrator (PD_Project) Reference Guide for more information of the Site Administrator
commands and Site ID attribute.
The default FrameWorks Project Number is the same as the PDS project name. The software
creates a directory with the path FrameWorks File Directory/FrameWorks Project Number. In
this example, the form was completed as follows.
In this example, the FrameWorks project directory is c:\testprj\fwproj on the server CADSRV.
The project directory creation scripts do not create directories for FrameWorks projects---it is up
to you to make sure that they are defined so that they reside inside of the PDS project directory.
The Force Units and Standard Section Table fields are code lists. Click the field to display the
choices.
The path limit for FrameWorks Plus projects is 36 characters, including all required
punctuation, and the mod and frz entries in pdtable_113.
When you accept this form, the FrameWorks project directory is created immediately and
consists of the following subdirectories:
fwproj\drw---drawings
fwproj\esl---engineering section libraries
fwproj\frz---frozen view files including surface models
fwproj\int---interface files to other programs
fwproj\mod---models
fwproj\rpt---reports
All of these directories are initially empty.
To avoid creating models with incorrect working unit settings, adjust the working unit
settings of FrameWorks Plus seed files after creating the projects, and before creating models.
The maximum length of the EE Raceway project directory is defined using the following
formula:
Max path length (including all punctuation) = 36 - (length of PDS project number)
This formula is based on the length of the subdirectories created under the EE Raceway project
directory and the maximum length of a model path name that can be stored in pdtable_113.
To store the EE Raceway project in the PDS project directory, where the PDS project resides at
the top level of a Windows drive, the maximum length of the PDS project number is nine
characters.
Let us see why---if an EE Raceway project directory of c:\myproj\myproj.prj\rway\dgn\ is
required, there are 18 characters of punctuation and path that exist regardless of what the PDS
project number is, therefore:
36 - (length of PDS projnum) = (length of PDS projnum) + 18
36 - 18 = 2 * (length of PDS projnum)
(length of PDS projnum) = (36-18)/2 = 9
Also note that if the standard directory naming structure is used, the longest directory will be
c:\myproj\rdb\source\eden_piping\, which also allows for a maximum project number of nine
characters.
The EE Raceway project directory must exist before you click Apply.
After filling in the Raceway Network Address and Directory and creating the specified directory,
click √ on the Create Project form to display the Create Schema dialog box for the EE schema.
When completed, click Apply to return to the Create Project form. New fields are displayed.
The location of the rway.sql and rway.cmd file must be entered into this dialog box. These files
are located in the eerway\db directory.
After completing this information, click Confirm. The fields that you just completed disappear.
Click Raceway RDB Schema to display the Create Schema dialog box for the RE Raceway
reference schema. Complete this dialog box and click Apply.
The location of the ee.cfg file is shown---in this case a new location has been entered. When a
raceway project is created through PDS, an ee.cfg is created in the PDS project directory. This
ee.cfg file should be used (as shown in the previous figure).
Environment variables are set by selecting them from the User Environment Variables list. They
then display at the bottom of the dialog box, where new values can be entered. After entering
the new value for an environment variable, click Set to record the change. The new value for the
environment variable displays in the top part of the dialog box.
Note that although PDS uses the ee.cfg file in the PDS project directory, PDS does not require
the environment variables in this file (such as EE_SCHEMA and EES_REFDB) to be set to valid
values (they can be left as UNINITIALIZED). This is because PDS gets the information it needs
about the EE Raceway project from the Project Control (PD) schema (the names of the project
and reference databases are stored in pdtable_102, and the names of the models are stored in
pdtable_113).
However, when accessing the same project through EE Raceway, these values must be set. It
is suggested that the ee.cfg in each PDS project directory have its environment variables set for
that project. As an example:
PDS project proj1 is located on the server in e:\proj1. Its associated EE Raceway project is
in e:\proj1\ee. The ee.cfg file is e:\proj1\project\ee.cfg. Start the EE Configure utility and set
the EE File Name to \\server\e:\proj1\project\ee.cfg. Set EE_SCHEMA to ee_proj1 and
EES_REFDB to re_proj1. Set PROJECT_LOCATION to \\server\e:\proj1\ee and
SYS_PASSW_FILE to \\server\e:\proj1\project\ee.pwd.
PDS project proj2 is located on the server in e:\proj2. Its associated EE Raceway project is
in e:\proj2\ee. The ee.cfg file is e:\proj2\project\ee.cfg. Start the EE Configure utility and set
the EE File Name to \\server\e:\proj2\project\ee.cfg. Set EE_SCHEMA to ee_proj2 and
Click Update Reference Schema to display the Update Reference Schema form.
Type the name of the RE schema, leaving the Schema Password field empty. Click √ to use
the delivered SQL and CMD files to create the database tables and to load default reference
data into them. When complete, an output file is displayed.
Check this file carefully for errors! The output file is saved in the eerway\tmp directory.
After checking the output file for errors, click X to dismiss the form. Then click Restore on the
other forms.
See Specify Coordinate System in the Project Administrator (PD_Project) Reference Guide for
more information on this form. The use of the Plant Coordinate System (PCS) is useful when the
Plant Monument is located a great distance from the design file origin. It allows the use of very
large coordinates, which would be outside the MicroStation design cube if the Plant Monument
(the center or origin of the design cube) remained 0,0,0.
The PCS can be specified up to the time that the first design area is created. After this,
the PCS cannot be set.
Click Revise Working Units to display the Revise Working Units form.
See Revise Working Units in the Project Administrator (PD_Project) Reference Guide for more
information on this form.
All models that you used in this project must have the same working units to ensure correct
results in reference file displays, drawings, interference detection, and so on. Because of this,
you should never change the working units after the project has been created.
Revising the ddl files and/or seed files after the project has been created can have
disastrous consequences. If the project settings need to be changed after the project has been
created, call Intergraph Support at 1-800-633-7248 for assistance.
When you start a project that uses non-PDS applications, be sure that the working units used by
those applications are the same as those used by PDS.
After specifying the working units, click √ to return to the Create Project form. Now you are
ready to create the project. After you click √ on the Create Project form, the default project
control data is written into the projdir\project directory; then the PD, DD, RA, RU, EE, and RE
schemas are created.
Creating a Project
1. Create a HVAC project directory c:\pds\hvac. (If you want to create the project on the server
then do a hard mount to the server and drive where you want to create the project).
2. Change the working directory for PARNU to the project location (c:\pds\hvac or
X:\PDS\models\hvac where X is the mounted server drive).
3. Select the P-Arnu icon, and from File > Properties, specify a working directory.While
loading P-Arnu; the project files are placed in the \users\projects directory.
You may have to first create a working directory through Windows Explorer.
4. Enter PARNU and create a project. (This will create a new directory using the project name.
Suppose you named your project as HV_PROJECT then this will create a directory
X:\PDS\models\hvac\HV_PROJECT)
5. Double-click the P-Arnu icon from the BDM (Building Design and Management) program
group.
The Project Environment command group is activated.
7. Fill out the dialog box to meet your specifications, and click OK.
The project is created, and you can either continue to create projects or click Cancel to
dismiss the dialog box.
When you dismiss the Create Project dialog box, you are returned to the Project
Environment command group.
8. Copy the envar.txt file (x:\win32app\ingr\pehvac\support\envar.txt) into your project directory
(c:\pds\hvac\hv_project. This file is required for each project ).
9. (OPTIONAL) Copy directory tables from the PEHVAC deliverable to the PDS project RDB
directories. X:\pds\rdb\hvdata. The directories you need to copy are:
DBA directory from x:\win32app\parnu\dba
EDEN directory from x:\win32app\pehvac\eden
Support directory from x:\win32app\pehvac\support
10. Edit the envar.txt to point the variables to the desired locations. (Change mynode to server
or client name).
(If you did the previous optional step, then you will need to change the location of directories
as required. If you did not do the optional step, then you can modify the envar.txt file to
change the node location to one of the machines that has Parnu and Pehvac loaded. If you
point to a specific machine for the variables then that machine needs to be ON and the
pehvac and parnu directories should be shared.) It is recommended to store your
customized data not in the product directory. Reloading the Software would delete those
files.
Example:
.
# AP_TABLE
# Set to a directory that contains support files specific for PEHVAC.
#
AP_TABLE server c:\win32app\ingr\pehvac\tables\
.
.
PHV_REFERENCE server c:\win32app\ingr\pehvac\support\tables\
#
# imperial support tables directory
#
PHV_IMPERIAL server c:\win32app\ingr\pehvac\support\tables\imperial\
11. Click Apps from the Project Environment command group.
The Applications dialog box is activated, and the applications you have loaded on your
machine and any projects you have created are displayed.
12. If you have not already done so, use the PE-HVAC Configure icon to specify the location of
the projlist.txt file.
13. Select PE-HVAC from the Application list; then select the project you want to use form the
Project list, and click OK.
The project list form is displayed.
14. Select a project from the displayed list. Then click OK.
The first time you enter a PE-HVAC project, the Reference Database Operations dialog box
is displayed.
15. Create prj_demo and hrf_demo users in your relational database. The prj_demo schema is
used to maintain designed data. Each project requires its own prj_schema. The hrf_demo
schema is used to store the Reference data. The hrf_demo schema can be used by different
projects. (the Reference database is required to be able to place elements. The Project
database is used for reports and necessary if you want to create envelope files and labels.)
If your Pehvac Project schema does not have the same name as your PDS project (e.g.
prj_demo instead of prj_pds you need to set the following system variable:
PDS_HVAC_SCHEMA_NAME=demo
16. Start Parnu. Select Database > Create and select the Pehvac project. After the schema is
created, select Pehvac under Applications to load Pehvac tables.
17. If you are going to use an existing PE-HVAC reference database, click Select and select the
database from the list. If you need to create a new reference database, click Create.
18. This dialog box lets you create a schema, or unique database/user combination, for the
reference database.
19. Click Load/Unload to load equipment into your reference database.
PE-HVAC displays the Reference Database dialog box.
20. Select the Load option and the devices and labels that you want to load into your reference
database. You can select all of the devices at one time by selecting the Select button under
each list.
When you have filled out the dialog box to meet your requirements, click OK.
PE-HVAC loads the devices into your reference database.
21. Click Cancel when you are finished loading devices into your reference database.
PE-HVAC returns you to the Reference Database Operations dialog box.
22. Click Cancel to dismiss the Reference Database Operations dialog box.
The PE-HVAC command group is activated. Also, if there are no design files present in the
project you selected, the Create Design File dialog box is automatically activated.
23. Fill out the Create Design File dialog box to meet your specifications, and click OK.
The design file is created. Continue to create design files, or choose Cancel to return to the
PE-HVAC command group.
24. Click Design to enter the design file.
The Enter Design File dialog box is activated, displaying any design files you have created.
After entering the Site/Project Name, the PDS 2D Application Manager form displays.
This form is described in the PDS 2D System Setup Guide. As part of the 2D project creation,
the first three buttons are used.
The PDS 2D reference data must be seeded first. Click Seed Reference Data to display the
Seed Reference Data form.
Press TAB to move from field to field in these forms rather than pressing RETURN.
From the Seed Project Number list, you can select exd_English or Translated RDB. Selecting
exd_English copies new PDS 2D reference data from the local node to the specified directory.
Selecting Translated RDB makes entries in the PD schema that point to the location of existing
reference data (that may have been translated from an older version). Click √ to copy over the
PDS 2D reference data to the specified directory. The PDS 2D reference data occupies
approximately 12MB.
When finished, click PID from the Application list in the PDS 2D Application Manager form.
Click exd_English, and modify the Reference Database Path to point to the 2d\pid directory.
Click √ to copy the PDS 2D PID reference data. The PDS 2D PID reference data occupies
approximately 11MB. When finished, click PFD as the application, modify the Reference
Database Path to point to the 2d\pfd directory, and repeat. The PDS 2D PFD reference data
occupies approximately 7MB.
After seeding the reference data, the associated schemas can be created. The PDS 2D
application does not require an additional schema---its tables are stored in the PD schema.
However, not all 2D tables are added to the PD schema as a result of starting the 2D project
creation process. Select PDS 2D from the PDS 2D Application Manager form. Then click
Create Tables to add the additional 2D tables to the PD schema.
Click PID on the PDS 2D Application Manager form, and then click Create Schema. You are
asked if you want to create a Task or Master schema.
The Task schema is the working copy of the design data for a project, while the Master schema
is an approved copy of the task schema which is frozen at some point in time. With the toggle
set to Task, click √ to display the Create Schema dialog box for the PID Task Schema. It is
similar to the Create Schema dialog boxes seen earlier in the project creation process, and is
completed in a similar manner.
The 2D schema name is not entered into the Create Schema dialog box automatically---be sure
to enter the prefix that corresponds with the schema type being created (for example, pid_ for
the PID Task schema). Also be especially cautious when entering information to create ALL 2D
schemas---if the wrong information is entered, you are returned to the 3D Create Project form!
The following chart is provided to assist in the creation of the 2D schemas. The list is sorted
according to the order of the applications in the drop down list:
Creating a 2D Project
Only one 2D project can be created per PDS project. If a 2D project has already been created,
the PID Project button is still available because additional 2D applications can be added to the
2D project after its creation. The PID Project button can be clicked to start the 2D project
creation for a new 2D project or to enter the 2D project creation environment to add disciplines
to an existing 2D project. See Creating the 2D Project (on page 89), for more information.
You may notice that for some of the reference data, additional files having the same name but a
different extension are also defined. The Piping Job Specification Table Library, for example,
includes the files whose functions are described below:
Name Function
Dismiss this dialog box---you will specify the location of the Standard Note Library later in the
process. The Reference Data Manager main menu displays after you dismiss the warning.
This form is described in greater detail in Chapter Three of the Reference Data Manager
(PD_Data) Reference Guide. Click Reference Database Management Data to display the
Reference Database Management Data form.
Clicking any one of the entries in this list displays the current name and location of that
reference data in the lower part of the form. The only item in this list that has been set is the
Material Specification Reference Database (which contains the names of the RA and optionally
the RU schemas). Locations have not been set for any of the other libraries---clicking any of the
other listed items will not display anything in the lower part of the form.
Rather than setting the location for each library individually, it is easier to use the Default All
Library Locations button to set all library locations. Libraries are copied into the
c:\testprj\rdb\lib\approved and c:\testprj\rdb\lib\unapproved directories by the project directory
creation script (see Creating Project Directories Manually (on page 62), for more information). In
this example, click Default All Library Locations, and complete the form as shown in the
following figure:
Click √ to write the library locations to the PD schema. The full specification of a library consists
of the directory path entered into this form and file names for each of the libraries. This can be
seen by clicking one of the items in the list after you have completed the Default All Library
Locations operation. For example, if you click Piping Job Specification Table Library, the
location displays as shown in the following figure.
In the RDUSRDB product directory, the name of the Piping Job Specification Table Library is
us_pjstb.l, but the Default All Library Locations operation has set it to pjs_tbl.l. The project
directory creation script takes this into account, and when the files associated with the Piping
Job Specification Table Library are copied from the product directory to the project directory,
the names are changed to reflect this. This renaming operation has also been done for the
Short, Long, and Specialty Material Description Libraries as well as the Graphic
Commodity Library.
The system does not verify the location of the libraries at the time this information is
entered into the Reference Database Management Data form. If errors have been made, you
will receive warnings at the time you enter a piping or equipment model, or enter the applicable
Reference Data Manager command.
You will notice that the Default All Library Locations operation has also set the international
Physical Data Libraries (DIN, JIS, and so on). These will not be used unless specified as
described in the Reference Data Manager (PD_Data) Reference Guide. They can be left as set
by the Default All Library Locations operation, or they can be deleted by selecting each field,
pressing DELETE, and then pressing ENTER. When you have done this for each field, click √ to
write the changes into the PD schema.
The Reference Database Management Data form must be accepted each time a
change is made to any of the reference data items. It is a good idea to pick another reference
data item from the list, then pick the item that was changed to verify that the change was made.
At the end of the listing of reference data, the location of the optional Commodity Synonym
Library is defined. This is not set by the Default All Library Locations operation. The Commodity
Synonym Library need not be set in order to start using the project. See Chapter 15 of the
Reference Data Manager (PD_Data) Reference Guide for a description of using the Commodity
Synonym Library. In this example, the Orthographic Drawing Borders directory can be set to
c:\testprj\dwg\border. The project directory creation script copies the default drawing borders
from the PD_Draw product directory into this directory.
In this example, the reference data libraries were copied into the project directory by the project
directory creation script. An alternative approach would be to use the Copy All Standard
Libraries function. The use of this function is described in Chapter Four of the Reference Data
Manager (PD_Data) Reference Guide.
If you are changing reference data items, you can use the Approved -> Unapproved button to
copy whatever was entered into the approved fields into the unapproved fields. You would then
need to edit the unapproved path (typically inserting the characters "un" in front of the word
approved) before pressing ENTER and then clicking √ to accept the form.
This form is described in Chapter Eight of the PDS Equipment Modeling (PD_EQP) User's
Guide. Click Database Library File Manager to display the Equipment Database Library
Management form.
This form operates in a manner similar to the Reference Database Management Data form
described previously. Some of the reference data items have been set to default values. The
Graphic Commodity Library, Tutorial Definition Library, Cell Library, and Forms Library have
been set to the PD_EQP product directory on the node where the project was created. This is
not typically used because the product may be removed or reloaded.
Set the locations for the displayed items as follows:
Graphic Commodity Library - Set the Directory field to projdir\rdb\eqp\approved, and set
the Specification field to zi_eqpms.lib.
Tutorial Definition Library - Set the Directory field to projdir\rdb\eqp\approved, and set the
Specification field to zi_tutlib.lib.
Equipment Physical Data library - Leave the Directory and Specification fields blank.
Piping Physical Data Library - Set the Directory field to projdir\rdb\lib\approved, and set the
Specification field to us_pcdim.l.
Piping Job Specification Table Library - Set the Directory field to projdir\rdb\lib\approved,
and set the Specification field to pjs_tbl.l.
Piping Design Standard Note Library - Set the Directory field to projdir\rdb\lib\approved,
and set the Specification field to std_note.l.
Cell Library - Leave the Directory and Specification fields blank.
Forms Directory Location - Leave the Directory and Specification fields blank.
Regarding the specification of the Forms Directory Location, if you are using PDS V6, and if
you have made no customizations to the PD_EQP parametric forms, you can leave this field
blank, and the software will look for the equipment forms in the PD_EQP product directory on
the client node. For this to work, PD_EQP must be loaded to the client node in client, local, or
server mode.
If you are using PDS V5, or if you have customized the PD_EQP parametric forms and are
storing them on a server, the Forms Directory Location must be set to a valid location. Rather
than loading PD EQP on the server, you can copy the PD EQP forms to a directory on the
server, share this directory, and specify it as the Forms Directory Location. One possible
directory structure is shown:
projdir
projdir\eqp
projdir\eqp\forms (copy of pdeqp\forms directory)
projdir\eqp\sym (copy of pdeqp\sym directory)
In this example, the Forms Directory Location would be set to the projdir\eqp directory. Both
the forms and sym directories must be found in this path.
The project directory creation script copies the Graphic Commodity Library, the Tutorial
Definition Library, and the Eden Description Help File from the PD_EQP product directory into
the projdir\rdb\eqp\approved and projdir\rdb\eqp\unapproved directories. The Graphic
Commodity Library and Tutorial Definition Library locations can be set to these locations---the
default files names match those used by the project directory creation script, so only the node
and path have to be checked.
The Eden Description Help File corresponds to the default equipment delivered in the
Equipment Graphic Commodity Library and does not need to be specified to the database. The
software looks for it in the same directory as the Equipment Graphic Commodity Library. If new
pieces of equipment are defined, the help file must be re-created using the Create Help Library
function in the PD_EQP Eden Data Manager (accessed by clicking Graphic Library Manager
then Eden Data Management from the Equipment Modeling Options form).
The Equipment Physical Data Library does not need to be set at this time. See the Define
Libraries section in the PDS EDEN Interface Reference Guide for details on when this library
can be used. The Piping Physical Data Library must be set---it can also be set to the same
location as in the Piping module (us_pcdim.l). The Piping Standard Note Library and the Piping
Job Specification Table Library can be set to the same locations as in the Piping module
(std_note.l and pjs_tbl.l respectively).
1c0031.pcd Piping Commodity Specification Data for the 1C0031 Piping Materials
Class
2c0032.pcd Piping Commodity Specification Data for the 2C0032 Piping Materials
Class
classes.pmc File that lists all the delivered Piping Materials Classes and their attributes
component.data Component Insulation Exclusion Data
constol.data Piping Construction Tolerance Exclusion Data
flange.data Flange Insulation Exclusion Data
implied.data Piping Commodity Implied Material Data
instrment.data Instrument Component Specification Data
pcd_size.data Piping Commodity Size-Dependent Material Data
specialty.data Piping Specialty Specification Data
taps.data Tap Properties Data
Neutral files are located in the following directories:
rdusrdb\spec_data contains all .pcd files, classes.pmc, implied.data, taps.data,
US_lgbomdata, US_shbom.data, and US_spbom.data.
pddata\sample\data contains component.data, constol.data, flange.data, instrment.data,
pcd_size.data, and specialty.data.
In addition to the files listed, the pddata\sample\data directory contains a sample metric
spec (metric_npd.pcd and metric_npd.pmc).
A detailed description of this reference data can be found in Chapter Five of the Reference Data
Manager (PD_Data) Reference Guide.
Before loading any of these files to the database, the classes.pmc file must be edited to reflect
the fact that not all available Piping Materials Classes are being loaded. The classes.pmc file
lists many Piping Materials Classes---of these, only two will be used (1c0031 and 2c0032). Edit
the classes.pmc file using any text file editor and delete all piping material classes except
1c0031 and 2c0032.
It is important to edit the classes.pmc file; PDS uses this file to determine the available
Piping Materials Classes.
From the Reference Data Manager main menu, click Piping Job Specification Manager to
display the Piping Job Specification Manager main menu.
If you click Piping Materials Class, click Load/Replace, and follow the example used so far,
the form would look like the following figure:
These buttons are used if the pipe support functionality is used. Contact Intergraph
support (http://support.Intergraph.com) additional information about pipe supports.
The Submit Immediately toggle will display after you enter the node, file path, and name. This
toggle may be set to Delayed Submit, but for a batch job of this type, a delayed submission is
not typically required.
Click √ to submit the batch job. The batch job will be submitted to the PDreference queue. If
"desktop access" was enabled for Batch Services, a collapsed DOS window displays at the
bottom of the screen. You can also start the Batch Manager and check to see that the batch job
made it into this queue and is running.
If the collapsed DOS window never appears, or if the job never appears in the
PDreference queue, either the Batch Services account mapping has not been set or you have
some other problem related to the setup of Batch Services. This problem must be fixed before
continuing.
If the Piping Materials Class file is successfully loaded into the database, a log file (pmc.log) will
be created in the temp directory on the machine where the batch queue resides. Typically this
will be the node that submitted the batch job, but if the PDreference queue has been defined as
a pipe queue and the job was routed to another server, the output file will reside in the temp
directory on that server. The log file should be examined for any error messages.
Click X to exit this form, and click Piping Commodity Data. Note that the system has recalled
the node and path from which the classes.pmc file was loaded. When you click Load, a new
toggle displays.
In this case, a single file spec (1c0031) was loaded; however, multiple specs could be loaded in
a single step. The toggle could be set to List of Files instead of Single File, and a file that lists
multiple specs could be entered. The list.pcd file located in the rdusrdb\spec_data directory is an
example of such a file.
In a similar manner, the file associated with the 2c0032 spec (2c0032.pcd) could also be loaded.
Note that as each spec is loaded, the results are all written into the same log file (pcd.log), so if
a number of specs have been submitted to load, the log file should be checked immediately
after the completion of each batch job.
The complete list of neutral files and their associated log files follows:
Project Organization
Disciplines - Such as Piping, Equipment, HVAC, and Structural.
Design Areas - Which represent a specified volume of the physical plant.
Models - Which correspond to a specific 3D volume for a discipline within the specified design
area. Each model is a MicroStation design file on the disk.
3D Disciplines
The following disciplines are delivered with the PDS 3D applications:
Piping
Equipment
Structural
HVAC
Raceways
Architecture
This menu is described in detail in Chapter Three of the Project Administrator (PD_Project)
Reference Guide. Click Project Environment Manager to display the Project Environment
Manager main menu.
This menu is described in detail in Chapter Five of the Project Administrator (PD_Project)
Reference Guide. Click Create to display the Create Options main menu.
This menu is also described in Chapter Five of the Project Administrator (PD_Project)
Reference Guide. Click Create Discipline Data, enter the name of the new discipline in the
Discipline Name field, and press RETURN.
Click √ to create the new discipline. If the discipline will contain as-built models created with the
PlantGen application, click PLANTGEN Discipline to allow PlantGen data to be recognized by
the Review Attributes command and various labeling commands. In this example, a discipline
named clash is created.
See Also
3D Areas (on page 114)
3D Models (on page 119)
Model Creation for Other 3D Disciplines (on page 125)
3D Design Data and the Database (on page 125)
3D Areas
PDS 3D design areas can be defined as dynamic or based on a predefined volume. This
becomes very important when you perform interference detection. Consider the area definition
shown below.
Although this is shown in two dimensions, the area definitions are in fact three-dimensional
volumes. There is a single structural area encompassing the entire plant defined as S1. Piping
area P1 encompasses equipment areas E1--E3, and piping area P3 encompasses equipment
areas E4--E6. The main piping thoroughfare is defined as P2.
The benefit of breaking the plant into areas is that it allows the plant to be divided into more
manageable amounts of data for various functions (such as isometric extraction, SmartPlant
Review sessions, interference detection, and so on). For instance, if changes are made in
equipment area E4, interferences can be run just in this area rather than checking the clashes
for the entire project. This can save substantial time because interference detection is a
compute-intensive operation.
When working in an area created using a predefined volume, the system does not stop you from
placing piping or equipment outside the boundaries of the area. However, when interference
detection is run using the Pre-Defined Volume option the system does not report a clash that
existed outside the predefined volume.
Another approach is not to use predefined volumes for your actual design areas. In this case, a
piping area grows to accommodate all of the piping placed within it. A strategy that can be
combined with this approach is to create a user-defined clash discipline used only for
interference detection. The design areas for the user-defined clash discipline are created with
predefined volumes, while the design areas for the other disciplines (piping, equipment, and so
on) are not. Many project administrators find this approach to be quite useful. Additional
information regarding the theory of clash area management is covered in the PD_Clash class
and in its accompanying documents.
To create a new 3D area, click Create from the Project Environment main menu and then click
Create Design Area Data. Click the discipline from the list of available disciplines, and click √ to
display the Create Design Area main menu. If the piping or equipment discipline is selected,
the system reads the working units and plant monument from the Type 63 data in the seed file
and displays the following information.
When this form displays, the predefined volume toggle is set to Interference Management
Design Area if the piping, equipment, or raceway discipline was selected. This toggle is off for
all other disciplines. The default origin of the predefined volume is set to the origin of the Plant
Coordinate System (PCS 0,0,0).
Seed Data
Chapter Six of the Project Administrator (PD_Project) Reference Guide describes all of the
Project Data Manager options. Click Seed to display the Revise Seed Files menu.
The Revise 3D Plant Design Data function includes options to specify a plant monument and
options to set the date/time format and coordinate readout format. Changes made here affect
the seed files or existing models. Coordination of these settings in a project being executed at
multiple sites is of paramount importance. The seed file report can be used for this purpose.
The Revise Model Data function (Revise button under the Piping Model Data category)
includes settings for MTO reporting options, whether the approved or unapproved reference
data is used, and the setting of the model file symbology. The model file symbology is an
important system setting and dictates if graphic symbology is based on model category, fluid
code, or construction status. Some of these changes can be applied to previously created
models and others cannot so it is important to inspect/coordinate seed file settings at the
beginning of the project.
The Propagate Piping Model Data function (Propagate button under the Piping Model Data
category) allows selected seed file settings to be applied to existing models. You can propagate
the following Type 63 data to existing models:
Component Placement
Piping Data Control
Physical Units Options
Nozzle Transfer
Material Takeoff
Design Review Label
Reference Database File Specifications
Design Checks
End Prep table
Symbology---Diagnostic Markers
Date/Time Format
The only model data that cannot be applied to existing models is the Default Active Segment
Data and the Level and Color options, which should not be revised after piping models have
been created.
The Revise Equipment Data function includes settings for the equipment graphic symbology and
whether or not the approved or unapproved reference data is used. Changes made here affect
the equipment model seed file; therefore, any required changes should be made before creating
any equipment areas.
The Revise Drawing Data function includes settings for graphic symbology, label text sizes, and
whether or not the approved or unapproved reference data is used. Changes made here affect
the drawing seed file; therefore, any required changes that cannot be propagated to existing
drawings (see the following list) should be made before creating any drawings.
The Propagate Drawing Data function allows selected seed file settings to be applied to existing
drawings. You can propagate the following Type 63 data to existing drawings:
Label Text Sizes
Reference Database File Specifications
Mass Annotation Data
PDS Drawing Annotation Category Data
User-Defined Drawing Annotation Category Data
Hidden Line Data
Coordinate Label Data
Prefix/Suffix Data for Coordinate Labels
Miscellaneous Label Data
Date/Time Format
The only drawing data that cannot be applied to existing drawings is the Drawing Category data,
which should not be revised after drawings have been created.
The Revise Interference Check Data function includes settings for clash construction tolerances
and assignment of clash responsibility by discipline. Changes made here affect the project
marker file, therefore any required changes that cannot be propagated to existing area marker
files (see the following list) should be made before creating any models.
The Propagate Interference Check Data function allows selected seed file settings to be applied
to existing area marker files. You can propagate the following Type 63 data to existing marker
files:
Construction Tolerances
Responsibility Matrix
Envelope Emulation Data
Clash Plot Graphics Option
The Report of Seedfile Data function allows you to produce a report of all seed file settings. This
report can be very useful when setting up a distributed project.
Plant Monument
The plant monument defines the origin of the Plant Coordinate System (PCS), which may or
may not coincide with the origin of the MicroStation coordinate system. See the PDS 3D Theory
User's Guide for information.
If you will not run Interference detection by Area for this discipline, then the toggle can be set to
No Interference Management Design Area. This will cause the software not to create the area
marker file.
If predefined volumes are not used for interference detection, then the predefined volume can
remain 0,0,0. Enter a Design Area Name, and press RETURN. Enter a Description, and press
RETURN. Click √ to create the design area.
3D Models
After you create design areas, you can create models within these areas. From Project
Administrator, click Project Environment Manager > Create > Create Model. Click the
discipline, and then click √. Choose the area from the next form, and click √ to display the
Create Model Data main menu.
In addition to the Model Number, Model Name, and Model Description, the Model Directory
and Workstation/Server Name must also be entered. Default values for Model Directory, and
Workstation/Server Name can be established using the Model Setup function. This is already
specified if you created the project using Express Project Creation.
For workshare projects; that is, projects with a Site ID defined, the Site ID field allows you to
specify which work site owns the model.
From the Project Environment main menu, click Model Setup and the discipline for which you
want to establish a default directory for the creation of new models. The form has been
completed to follow the example started earlier.
The Color, Style, and Weight toggles allow you to establish default reference model symbology
for the selected discipline. The use of these settings is described in the Model Setup section of
the Project Administrator (PD_Project) Reference Guide. Note that the information for the
Structural and Raceways disciplines has already been set.
For the Model Directory setting, you can enter either the full path or the share name. For
example, you could enter h:\projects\project1\models\piping or \project1\models\piping. In either
case, the parent directory should be shared. For more information, see Creating Project
Directories and Required Shares (on page 54).
Click √ to write the default model file location into the PD schema.
Returning to the Create Model Data form, the information entered in the Model Setup Data
form is reflected in the Model Directory and Workstation/Server Name fields.
A Model Number (which results in a default Model Name) and Model Description can be
entered. A Model Status can be selected by clicking the Model Status field. This reads a list of
available model status conditions from code list 1605 in the Standard Note Library.
The following figure shows the completed Create Model form for this example:
In addition to the plant monument, PDS supports the use of a Design Volume Coordinate
System (DVCS). See the PDS 3D Theory User's Guide for more information.
The DVCS for a model can be changed after it has been created. In versions 7.0 and
later, the plant monument can be changed with the Update Plant Monument function even
after the model or project has been created.
Typically, a delayed submission is not required for this type of batch job. The batch job is
submitted to the Pdcreate_model queue. Check in Batch Manager to see that the job is in the
queue and is running. When finished, a log file named crtmodel.rep is written into the temp
directory (or mailed to you if PDS batch mail is set up)---a sample follows:
Piping Files Processed :
Created Model p1
Created Model p2
Equipment Files Processed :
No Models found in discipline to process
Model Creation Completed
Elapse time = 2:15
CPU time = 2:14
Make sure that all models that were created have their database tables created;
otherwise, they are unusable. Performing this operation more than once will not result in the
creation of duplicate database table. Only those models that have not had their tables created
will be processed.
2D Disciplines
The 2D disciplines (2D, PID, PFD, IDM) support the use of drawings that are graphics only or
graphics + database. A drawing created in graphics only mode can be attached to the database
at a later time if required.
See Also
Creating a Graphics-only Drawing (on page 126)
Creating a Database Drawing (on page 127)
If there are syntax errors in the .gpr file, it will not display in the Graphics Only Project Files
list. From the P&ID Seed File list, you can choose seed1.dgn or seed2.dgn---seed2.dgn has a
border, while seed1.dgn does not. Click Task, and enter the full path of the drawing to be
created. You can use Universal Naming Convention (UNC) file names in this field. The drawing
name should have a .pid extension so that it can be brought into the database if required.
To open the graphics-only PID drawing, double-click the Graphics Only icon in the PDS 2D
Applications program group to display the Graphics Only dialog box.
Click your Graphics only project file from the list, and click Browse to find the drawing to be
opened---its full path displays in the Design File path. Click OK to start MicroStation and open
this drawing.
From the Env command on the menu bar, click PDS 2D > Show Units---you should get a
warning that no units were found. Dismiss this warning to display the Units form.
If you are running PDS2D on a computer that has more than one CPU, the environment
variable MS_PROCESSORS must be set to 1.See the PDS2D README file for details.
From the Env command on the menu bar, click Commands > Create. You are prompted to
Select entry to create. Click the Units form in the area where the asterisk (*) displays. The gray
buttons to the left are called row select buttons and should not be used at this time. After
clicking here, you are prompted to Select the project. Click the project name in the Project form.
Do not use the row select button---click on the project name. The Unit for Project form displays.
Enter information in the right-hand side of this form, pressing RETURN after each entry. After
completing all three fields, click Accept from the Env command on the menu bar to save the
entry. The unit is created and appears in the Units form.
From the Env command on the menu bar, click P&ID > TDB > Show Drawings to create a PID
drawing for this unit. A warning displays that no drawings were found. Dismiss this to display the
PID Drawings form.
From the Env command on the menu bar, click Commands > Create. You are prompted Select
entry to create. Click the area underneath the column heading Drawing no (do not use the row
select gadget) on the PID Drawings form. You are then prompted to Select Unit gadget. Click
your unit code in the Units form to display the Drawings for Unit form.
Click Accept from the Env command on the menu bar to create the PID drawing. The drawing
displays in the PID Drawings form, and the .pid file is created in the specified directory.
To enter graphics, click Env > Commands > Edit Graphics. When prompted Select entry to
edit, click the name of your drawing in the Drawing no column of the PID Drawings form. Do
not use the row select gadget.
In This Section
Plotting in the PDS Environment ................................................... 131
Modifying Batch Queues for Redirected Processing ..................... 135
Access Control ............................................................................... 144
Creating Backups and Maintaining a Backup Schedule ................ 148
Creating and Maintaining Distributed Projects .............................. 158
If you are doing batch plots through PDS and are using created printers, user can map to a
generic user (PDS\* = PDS\pdsbatch). This is acceptable since the created printer is a property
of the computer, and therefore known to all users of that computer.
If you do not do batch plots through PDS but submit plots directly using the I/Plot dialog box,
then the generic mapping as described for created printers can be used.
Use of My Computer
The My Computer option creates a printer that can be shared so that other nodes may connect
to it. The use of My Computer requires that I/PLOT client, I/PLOT server, and the printer driver
be loaded on the local node.
1. Click Start > Settings > Printers.
2. Double-click Add Printers.
3. Select My Computer then click Next.
4. Enter a name, and select the correct driver from the list. As an example, an HP Laserjet
4MV, is connected directly to the network. To communicate with this particular printer, the
DLC protocol must first be loaded from Control Panel > Network.
Do not use spaces in printer names. For example, use hplaser instead of HP
LaserJet. PDS supports up to 14 characters in the printer name.
5. Select the appropriate driver from the list (in this example, the HP LaserJet 4MV), and type
a description. This description will be visible from Printer > Properties. If it is shared, this
description will be visible when others try to connect to this printer.
6. Click the Print to port. If the printer is directly connected to the node, you would click the
corresponding local port (COM1, LPT1, and so on). If it is a network printer, you would click
Other and then the network type (Hewlett-Packard Network Port in this example). For the
HP network printer, a MAC address would be chosen from the list, and other printer-specific
options could be set before proceeding.
7. Choose whether or not to Share This Printer on Network. If you are sharing the printer,
type a share name, and optionally type a description.
At this point the printer configuration is complete. The printer is visible from the Printers
folder. You should test the printer connection by printing to it from a text editor or by plotting
to it from I/Plot.
For plotters connected directly into the network or to a Windows system, the Form setting
should be examined and changed from its default value to match the true size of the paper
used in the plotter.
Application-specific Considerations
This section describes plotting issues that are unique for a particular application.
PD_EQP Considerations
All print options use the queue_descript file's list of available printer queues. (Pdprint)
On Windows, if the PD_EQP software cannot find any of the queues listed in the
queue_descript file, a list of all available printer connections from the Print Manager
displays.
All batch options use the queue_descript file's list of available batch queues. (Pdeqp_batch)
On Windows, if the PD_EQP software is unable to find any of the queues listed in the
queue_descript file, the list of all available batch queues from the Batch Manager displays.
PD_Draw Considerations
If you are submitting a batch job from a Windows node to a remote queue on another
Windows node, the list of available print/plot connections is derived from the remote
Windows node.
If the PD_Draw software is unable to find any of the queues listed in the queue_descript file
and you are not crossing platforms, the list of all available printer connections from the Print
Manager will be displayed on a Windows node.
In PD_Draw, you can specify a plot size and send it to a different size queue. If you specify
a small size to a larger queue (A size to an E size queue, for example), you should get the
small plot in the lower left corner of a large sheet of paper. If you specify a large size to a
smaller queue (E size to an A size queue, for example), you should get a correctly scaled
plot for the queue specified. In other words, the software will scale down to match the queue
size but will not scale up to match the queue size.
PD_Design Considerations
For PD_Design, the software will scale as you specify and will then check to see if that size
will fit onto the paper for the queue that you specified. If it will fit, it will plot it to the scale that
you specified. If it does not fit, the plot fails, and an error message is generated.
PD_Review Considerations
For PD_Review, the software will scale as you specify and then will check to see if that size
will fit onto the paper for the queue that you specified. If it will fit, it will plot it to the scale that
you specified. If it does not fit, the plot fails, and an error message is generated.
PDS 2D Considerations
For PDS 2D, the software only displays the queues that match the size that you specified.
For example, if you are trying to get an A size plot, you should see only A size queues.
PD_ISO Considerations
PD_ISO does not scale for plotting. The user predefines the iparm files and selects the
settings before plotting. The iparm file includes scale, size, queue name, and so on. The plot
queue name from the iparm file is displayed to the user who may use the displayed plot
queue or select another one.
All printing and plotting options use queues listed under the Pdprint and Pdiso_plt headings
in the queue_descript file. On Windows, if the PD_ISO software is unable to find any of the
queues listed in the queue_descript file, the list of all available printer connections from the
Print Manager is displayed.
All batch options use queues listed under the Pdiso_batch heading in the queue_descript
file. On Windows, if the PD_ISO software cannot find any of the queues listed in the
queue_descript file, a list of all available batch queues from the Batch Manager is displayed.
Additional information about the queue_descript file and some examples can be found in The
PDS queue_descript File (on page 287).
The fact that the Queue Type is set to batch indicates that all queues are local to this node.
2. Exit Batch Manager and start the PDS Queue utility. In order to create Queues on a
computer using UAC, you must right-click the PDS Queue utility and select Run as
administrator.
3. You may get a message that All Products Have Queues Created. Accept this warning.
The Queue Creation utility displays Reading information from the queue.lst file and the
local machine.
The queue.lst file is not to be confused with the queue_descript file. The queue.lst file is
located in the same directory with the proj file, and is used by the PDS Queue Creation
utility.
When this dialog box displays, all products are dithered (in this example) because the PDS
Queue Creation utility has determined that queues for all products have been created.
4. By turning on Enable all for configuration, all products become available.
5. Select the product whose queues will be reconfigured (in this example, PD_Clash). After
clicking the product, you can click the list by the Queue Name field to display the list of all
queues that product uses. If ALL is selected, all of the queues that appear in the list will be
reconfigured.
6. In the next figure, you can see that the Pdclash_server queue has been chosen to be
reconfigured, the Remote Node box has been checked, and the name of the server has
been entered.
Note that when the pipe queue is created, neither the existence of the remote node
nor the existence of the corresponding batch queue are checked; you must be certain that
the server name is correct and that the corresponding batch queue exists on the specified
server.
If the queue already exists, the software turns on Overwrite Existing Queue. You must
leave the setting turned on to re-create the existing queue as the new pipe queue.
7. Click OK to display the following message regarding the queue.lst file:
When creating a pipe queue to a remote node, clicking Yes on this dialog box will write
information for the specified queue(s) into the queue.lst file. By default, the queue.lst file has
entries that look like this:
[PD_Clash Queues]
node=
When a client node that is using this proj file creates a pipe queue used by this discipline
and saves the information to the queue.lst file, the information will be changed. Considering
the example of the Pdclash_server queue that was created as a pipe queue to the node
CADSRV, the PD_Clash entry in the queue.lst file would now look like this:
[PD_Clash Queues]
node=
PDclash_server=CADSRV
When another client node is creating PD_Clash pipe queues using the PDS Queue
Configuration utility and Read data from ASCII file has been selected, the node CADSRV
will appear in the Remote Node field. In this manner, the System Administrator can create
all required pipe queues from one client, change the permissions of the queue.lst file to read
only, and then other clients will see the preferred location to create their pipe queues to.
Changing the permissions of the queue.lst file to read-only will not stop clients from creating
pipe queues to other nodes, but it will show them where they should be created to and also
stop them from altering the information in this file.
Some queues are shared by more than one application. For example, the PDreport queue
is used by PD_Clash and PD_Projec as well as PD_Report. If PD_Clash pipe queues are
created, the information for the PDreport queue will also appear in the PD_Report and
PD_Projec sections of the queue.lst file.
8. After creating the pipe queue using the PDS Queue Creation utility, go back into Batch
Manager and make sure that the queue was successfully created to the correct destination.
With the queue selected as shown above, click Queue > Properties from the menu bar, then
click the Destinations tab to see where this pipe queue's destination is.
This is a quick way to check where batch jobs sent to this queue will be processed. It is possible
to add additional destinations to this pipe queue; if the first destination in the list is disabled, the
next one will be used. See the on-line help for additional information.
After the pipe queue has been created, the following items should also be checked to make sure
the pipe queue can be used successfully:
Does a batch queue by the same name exist on the specified server?
A batch queue with the same name must exist on the server. In this example, the
PDclash_server batch queue must exist on the node CADSRV.
When PDS\mary submits a batch job on node PDS1 which is piped to the same queue on the
node CADSRV, she will be mapped to the PDS\pds user. Because this user has access to the
project files the batch job will complete successfully.
Access Control
The PDS Access Control Manager is fully documented in Chapter 12 of the Project
Administrator (PD_Project) Reference Guide. This section provides a brief description.
PDS Access Control Manager restricts access to PDS functions based on a PDS Access
Control user name. Users enter their PDS Access Control user name at the PD_Shell main
menu and then select a project. Based on the user name and the project selected, certain
options are enabled. The PDS Access Control user names do not have to coincide with the
operating system logins. For example, a user may be granted access to a PDS function by
virtue of their PDS Access Control user name, but yet may have insufficient privileges to perform
the selected function based on their operating system login. The System Administrator should
make sure that users operating system logins and PDS Access Control user names offer
equivalent privileges.
Information about PDS Access Control is stored in two files---the PDS_user_id file and the
PDS_access file. The PDS_user_id file is located in the directory where the proj file is located
and contains the list of all usernames. The PDS_access file is unique for each project and is
located in the project directory. In this manner, a single set of users can be created, and those
users can be granted different access permissions for each project listed in the proj file.
If access control is not used on a set of projects, there will be no PDS_user_id file in the
directory where the proj file is stored. In the PD Shell form, type system in the User ID field to
display the following form:
The Initials, User Name, and Password fields are initially empty and have been completed as
shown in this example. Press RETURN after you finish each field. Click √ to set the password
for the System user and create the PDS_user_id file.
Make sure to write down the System user name password---there is no way to recover
this password if you forget it.
If you forget the System user name password, you will have to delete the PDS_user_id file and
start over. Once you do this, the user IDs in the new file may no longer match the user IDs as
stored in the PDS_access file in the project directories, so they will have to be deleted and user
privileges for each project will have to be set again.
After setting the password for the System user, the Access Control Manager form displays.
At this point you must enable access control for the selected project. Click Enable Access
Project Control, and select the project name from the Projects list. The following form displays:
Click √ to enable access control for this project. PDS Access Control user names must be
created next. For this example the following users will be created:
By selecting Categories and Privilege Levels for a user, certain functions in PD_Shell and the
other PDS 3D applications are made available to that user. A complete explanation of which
options are enabled by each choice are described in the Authorization Data section of the
chapter on Access Control in the Project Administrator (PD_Project) Reference Guide.
Because this user is the Piping Designer, click Design, Propagation, Reporting/Plotting, and
Checking/Comparison in the Piping category. After turning on these privileges, another
Category can be selected from the list and additional Privileges for that category granted (the
Privileges for each Category appear the same, as shown in the Privilege Levels list). For
example, you may want to grant the Piping Designer privileges in the Project Data and Pipe
Stress Analysis categories as well. Note that privileges granted to a user can be changed by the
System user at any time. After granting all required privileges to a user, click √ to create the
record in the PDS_access file which is stored in the project directory of that project.
Note that while you are in the PDS Access Control Manager, a file named PDS.lck is created in
the directory where the proj file is located. If another user attempts to run the Access Control
Manager while you are running it, a warning displays.
A common problem is that if Access Control terminates abnormally, the PDS.lck file may be left
behind, preventing other users from running the Access Control Manager. Removing the
PDS.lck file will remedy this situation---however, you should make certain that no one is actually
running Access Control Manager when doing this!
In a similar manner, you can create additional users and grant them privileges for the selected
project. We suggest that after creating or revising a user name you click the left bending arrow
to reset the form before creating or revising the next user. When finished, exit out of PD_Shell,
and then restart it. The project for which Access Control was enabled will no longer appear in
the list. One of the user names created earlier must be entered. If this is the first time a user is
entering PD_Shell, the password must be set and verified. After doing this, all the projects using
access control display (in red letters) with the list of other projects. When a project is selected,
PDS will read the information for that user from the PDS_access list in that project. PDS will
then make certain options available and grey other options out.
To remove a project from access control, you would remove the PDS_access file from the
project directory, and perform the Disable Access Control function while running the Access
Control Manager as the system manager.
See Also
Copying a Set of Users to Another Project (on page 148)
Advantages
The PDS project archive is particularly useful if a single model or a single reference library
needs to be retrieved. Because PDS Archive uses risunload to automatically extract
information from the database, the information in the models and the corresponding information
from the database is backed up at the same time.
Disadvantages
The PDS project archive can be quite large depending on the size of your project. All information
and files recorded in the database must exist.
Procedures
PDS Project Archival is described in the Project Administrator (PD_Project) Reference Guide.
Additional tips are provided in the PD_Project README file. In a Windows environment, an
interactive project archival can be done to disk on the local node or on a remote node.
Interactive and Scheduled project archivals require a batch job, so make sure that the account
mapping for the user initiating the archive specifies a user who has access to the project files as
well as the destination directory for the archive.
Interactive project archival results in a project archive being created immediately. When
Scheduled Project Archive is run, no archive is actually performed. Instead, a set of files are
produced that will cause the project to be archived at specified intervals. As an example, the
Scheduled Project Archive form has been completed as shown in the following figure:
In the next form, select Backup on Hard Disk and specify a directory on the server CADSRV
(c:\archives\testprj, in this example). In the Project Archival Options form, select Project Data.
This causes the time interval gadgets to appear as shown in the following figure:
Rather than setting the archive time and interval at this point, continue selecting the parts of the
project you want to archive. When Model Data is selected, a form displays that allows you to
select the models you want to archive:
After making your choice, click √ to return to the Project Archival Options form. When you select
Drawing Data a form similar to that for Model Data appears. When you select 2D Project the
following form displays:
You must type the Base Node and Base Path before you make any other selections. In this
example, the Base Node is the server (CADSRV) and a valid path has been entered
(c:\archives\temp). When you select the first 2D archival option, the Base Node and Base Path
are validated. Every 2D archival option except Project Data brings up an additional form where
either all of the specified data or a subset can be selected. After selecting all needed 2D archival
options, click √ to return to the Project Archival Options form.
After you have selected any additional parts of the 3D project to archive, set the archival time
and frequency as the last step. The use of these options is described in the Project
Administrator (PD_Project) Reference Guide (DPDS3-PB-200030*). If you make a mistake
entering the time, you can reset the form by simply checking and unchecking an archival
category. After setting the archival time (in this example, 11pm each night), click √ on the
Project Archival Options form to create the scheduled archival files and Batch Services entry.
You will now find three files located in the directory specified in the Archival Creation/Revision
form:
archive_1.cmd
testprj
testprj_2
An entry is also created in Batch Services.
At this time, the file archive_1.cmd will be run using the PDSPERL shell. The archive_1.cmd file
can be examined with a text editor:
$ENV{'IFC_PROD'} = 'PDS';
$ENV{'PROJ_NO'} = 'testprj';
$ENV{'PROJ_FILE'} = 'c:\projfile\\';
$ENV{'PROJ_ADDR'} = 'cadsrv';
system 'echo pdsperl -S pdsqsub.cmd 4 pdarch.exe testprj.arc
c:\archives\testprj PDS1 1 | qsub -eo -o PDS1:c:\temp\testprj.arl -r
arc_testprj -x -q PDarchival ';
The system 'echo.... line whose purpose is to submit a batch job to the PDarchival queue. This
file can be interpreted as follows:
The project name is testprj and the proj file is on CADSRV in the directory c:\projfile (determined
from lines 2, 3, and 4). The file that specifies the archive options is named c:\archives\testprj and
is stored on node PDS1. The log file will be named c:\temp\testprj.arl and will be found on node
PDS1.
The file testprj is a binary file and cannot be examined with a text editor. The file testprj_2
specifies the archive options for the 2D project, and this file can be examined with a text editor:
2D_LOG 'pds1' 'c:\temp\' 'testprj.arc'
2D_BASEDIR 'cadsrv' 'c:\archives\temp\'
2D_IMPORT
2D_PROJ pds2d T
This file can contain many other options. The options to note at this point are the location of the
log file (c:\temp\testprj.arc on node PDS1) and the location of the 2D project archive working
directory (c:\archives\temp on node CADSRV).
When the Batch Services job starts at 11pm, it in turn runs the archive_1.cmd file. This file sets
environment variables and initiates a batch job. The batch job performs the archive and
produces the log files. For this to complete successfully, the configuration of the schedule
service and the Batch account mapping must be checked.
Jobs run from the scheduler are associated with a user name which must have a valid account
mapping established in Batch Manager. This can be seen by going into Control Panel >
Services and double-clicking on the Schedule service. The Startup Type should be set to
Automatic, and a user name should be specified. The default user name associated with the
schedule service is the System Account. This account may not map correctly to a valid user in
batch manager. An example is provided below:
Schedule service runs as System account on node PDS1
On node PDS1, account mapping is set as PDS\* = PDS\pds
When a job is initiated, it runs as PDS1\system user. Because this user is not in the PDS
domain, the batch job will not be initiated.
One option would be to use a *\* = PDS\pds account mapping in Batch Services so that the
system account will map to a PDS domain user name.
In this example, the schedule service has been set to run using the domain administrator user
name (PDS\administrator). This solves a number of problems:
1. The domain administrator (PDS\administrator) is automatically added into the local
administrators group when the client node joins the domain.
2. Because a PDS domain user has been specified for the schedule service, the scheduled
project archive will work because this user meets the PDS\* = PDS\pds account mapping in
Batch Services and because this user has access to all project files on the server.
In this example, the project being archived is on the server, and the batch process that will
create the archive of this project is run on a client node (PDS1 in this example).
Frequently, it is necessary to run the batch job on the server rather than on a client machine.
However, the server may not have a graphics console on it and it may not be capable of running
PDS interactively, such that the scheduled project archive cannot be created on the server. In
this case, the scheduled project archive can be created on a client node, the files can be moved
to a server, and the Batch Services job can be created on the server to run the copied files.
Advantages
The operating system-level backup is quick and will copy all project data. The retrieval process
is typically easier as well. This type of backup is also useful should you experience a disk failure.
Disadvantages
If the project is spread across multiple nodes some data may be omitted. The database
information will not be captured. Retrieving a single file may be difficult.
Procedures
The NTBACKUP utility can be driven from a command file. This command file can be run
regularly by creating an AT job to run it. An example job to back up all drives on the server is
shown below:
NTBackup Backup C: E: F: G: H: /D"Full Backup of C, E, F, G, H"
/L"c:\users\default\backup.log"
This will perform a full backup of all drives, label the volume as "Full Backup of C, E, F, G, H",
and put the log file in c:\users\default\backup.log. If this command were put into a file
(c:\users\admin\backup.bat, for example), this file could be run every morning at 3am using the
following command:
at 3:00 /interactive /every:M,T,W,TH,F,S,Su c:\users\admin\backup.bat
The NTBACKUP utility also supports incremental backups from a command line---see the
Windows documentation for additional details.
Note that if the database is running when the backup runs, the database files will be
skipped (as will any other files that are open).
We recommend that backups of the disk files be performed as insurance against disk failure.
Furthermore, all of the files associated with the database should be backed up together at a time
when the database is shut down. This provides insurance against database failure. How
frequently this is done is left to the discretion of the System Administrator.
Advantages
Making an operating system-level backup of the database files is highly recommended. It is
useful should you experience a disk failure.
Disadvantages
If you ever need to use it to recover the database, everyone's work will return to the point in time
when the backup was made. Also, when the database is restarted it may not be synchronized
with the data in the models.
Procedures
See NTBACKUP or CPIO Backup of Project Data (on page 155). The database must be shut
down when its files are copied to tape.
Advantages
A risunload file is portable. You can do a risunload from one type of RIS-supported database
and risload into another.
Disadvantages
To do a risunload or a risload, RIS must be functional and the schema must work (the Data
Definition operation from within RIS Schema Manager must not return any errors). If the schema
is broken, a risunload is not possible.
Procedures
The risunload utility can be run interactively or from a command line. However, there is no
reason to perform risunloads of the database (as a separate step outside of PDS archival)
unless you are moving between database types.
Advantages
Speed and security - the database vendor backup utility is typically very fast and can archive the
information for all databases in the system or just the data for a single PDS database. Also, if
the schema is broken and risunload cannot be used, the database-level export can still be done.
Disadvantages
Recovers the entire database or all information for a single PDS database. It is not possible (or
at least very difficult) to retrieve the data for a single model. This is also true for risload.
Procedures
Each database vendor includes a backup utility with their product. Some examples are listed
below:
RAID Configuration
All current Intergraph Intel based servers include Redundant Array of Independent Disk (RAID)
technology. RAID technology benefits Intergraph customers in two ways:
1. Reliability---RAID technology offers protection from disk failure for user data.
2. Performance---RAID technology allows data to be striped across multiple disk drives,
boosting performance on read operations.
The technology and concepts of RAID are complex. A full understanding is required to exploit all
the capabilities of the latest generation of Intergraph servers. This appendix covers the following
topics:
I/O subsystem components.
Explanation of different RAID levels supported by Intergraph servers.
Hardware versus software implementation.
Purchasing considerations.
Configuring a RAID capable system for optimum database performance.
After reading this section, you should understand RAID technology and how best to apply it to
problems in your organization. Additional information regarding RAID, and Intergraph servers in
general, can be found at our home page http://www.intergraph.com.
Each component is a potential bottleneck for system performance. Using the most advanced
technology and making intelligent configuration decisions maximizes the I/O throughput of a
server.
Disk controller
The standard for connecting disks to the controller is the Small Computer Synchronous Interface
(SCSI). A fast and wide SCSI-2 channel has a peak bandwidth of 20MB/second. Most
controllers use fast and wide SCSI-2, very few of the available drives are fast and wide, so the
full capability of the SCSI channel is not used. In a server, multiple SCSI channels are essential
for high performance. The ISMP22 server uses two PCI-based SCSI controllers, each with a
single channel. The ISMP5* or 6* uses a single EISA-based controller with five channels. High
performance controllers such as the one use in the ISMP5* or 6* series feature on-board cache
and support for RAID in hardware.
Disks
Despite continuing advances in density and performance, magnetic disk drives use technology
which has changed little in the last thirty years. A disk drive consists of one or more platters
which rotate at high speed and a collection of read/write heads which move over the surface of
the platters. Disk drive vendors usually refer to three measurements when specifying the
performance of a disk drive:
Average seek time---the time needed to get from one position on the disk to another. The worst
case for seek time is if the heads have to move the full radius of the platter and the platter has to
rotate almost a complete revolution before the heads are positioned correctly.
Average access time---a combination of the seek time and the time actually required to read
data from the disk.
Transfer rate---the rate at which data can be transferred from the drive to the controller.
Intergraph servers use fast SCSI-2 disk drives. A fast SCSI-2 drive can transfer data at a
theoretical peak rate of 10MB/second. In practice, drives can sustain about 4MB/second. The
SCSI-2 channel (fast & wide) offers a peak of 20MB/second. This leads to several conclusions
about performance in an I/O subsystem:
For peak performance, a SCSI-2 channel should not support more than four disk drives.
Two 1GB drives can offer better performance than one 2GB drive as they have a potential
transfer rate of up to about 8MB/second. A single 2GB drive is limited to about 4MB/second.
Disk drives spread across multiple channels offer better performance than the same number
of drives on a single channel.
RAID 0
RAID 0 is the simplest type of RAID to implement. It is also known as striping. In RAID 0, data is
spread across multiple physical disks offering faster read/write performance than a single drive.
A three-disk stripe has approximately 3 times the bandwidth of a single drive because read/write
operations to the stripe can occur in parallel. The RAID 0 diagram shows how data would be
distributed in a three-disk stripe. The benefit of RAID 0 is performance, the prime disadvantage
is reliability. If a single drive has a Mean Time Between Failure (MTBF) of 50,000 hours, then
the MTBF for data on the stripe is:
For a three-disk stripe, the MTBF would be 12,666 hours. This RAID 0 limitation makes it
unsuitable for most applications requiring high-availability for the data. Because of the effect on
reliability, RAID 0 is only suited for environments where system uptime is unimportant.
RAID 1
RAID 1 is often referred to as disk mirroring. In RAID 1, physical disk drives are grouped in
pairs. Any data written to the first drive in the pair is also written to the second drive---which
halves the amount of space available for data. Because the chance of both drives failing
simultaneously is small, the chance of losing data to a disk failure is small. Because write
performance is governed by the performance of a single disk in RAID 1, it offers no benefits for
write operations. Read operations are improved because data can be read from either disk.
The disadvantage of RAID 1 is cost. Every MB of disk storage requires 2MB of actual disk
space.
RAID 5
RAID 5 combines the reliability of RAID 1 with many of the performance benefits of RAID 0. In
RAID 5, a parity block is calculated. The parity data in combination with data on undamaged
drives allows reconstruction of data on a failed drive. The figure below illustrates how RAID 5
organizes data on a three-disk stripe. The rule is that a data block and its corresponding parity
information are never written to the same physical device.
In the example, if drive 1 fails, then block 1 can be reconstructed from the block 2 and the parity
information for block 1&2. Similarly, block 3 would be reconstructed from block 4 and the parity
for blocks 3&4. The parity block on drive 1 can be reconstructed from blocks 5 and 6. Read
performance of a RAID 5 stripe is similar to RAID 0. In write operations, the performance is
degraded when compared to RAID 0 for two reasons:
1. More data is written. The controller (for systems using hardware RAID) or the operating
system (for systems using software RAID) must calculate the parity block and write the data
and parity block.
2. If the data being written involves modifying a block on any of the disks, then that block has
to be read in, merged with the new data, and rewritten to the drive along with its newly
calculated parity information.
RAID 5 is widely regarded as the best RAID level for database and file sharing
operations in a multi-user environment. RAID 5 allows each disk to satisfy requests
simultaneously.
Consider the following set of requests:
Application 1 requests block 1
Application 2 requests block 2
Application 3 requests block 4
Because each block is on a different physical device, the blocks can be read simultaneously.
Write performance of a RAID5 stripe depends on the size of the average write. There are three
scenarios for a write operation:
1. Operation replaces all the data blocks in a stripe, results in operations to:
Calculate parity block
Write data blocks
Write parity block
2. Operation replaces a block of data in a stripe, results in operations to:
Read parity block
For a RAID 5 stripe on three 1GB drives, the usable space is:
Which leaves 2GB of usable space. The space efficiency of a RAID 5 stripe increases as more
physical drives are added to the stripe. This also improves performance.
The mechanism used to recover data in a RAID 5 array is simple, consider the following
example:
0 1 0 1 1 0 1 1 Data 1
1 1 0 1 1 1 0 1 Data 2
1 0 0 0 0 1 1 0 Intermediate XOR
0 1 1 1 0 0 1 0 Data 3
1 1 1 1 0 1 0 0 Error Correction Code
If a drive fails so that Data 2 is no longer available, then it can be re-created from the using XOR
as follows:
Data2 = ((ECC xor Data1) xor Data3)
0 1 0 1 1 0 1 1 Data 1
1 1 1 1 0 1 0 0 Error Correction Code
1 0 1 0 1 1 1 1 ECC xor Data 1
0 1 1 1 0 0 1 0 Data 3
1 1 0 1 1 1 0 1 Result=Data2
If a drive fails, then RAID 5 is forced to synchronize all the drives to read a missing block
because all the data is required. Although RAID 5 continues to function with a failed drive, the
performance for both read and write operations is reduced.
RAID 6
RAID 6 combines levels 0 and 1 offering the performance of RAID 0 and the reliability of RAID
1. Rather than grouping drives as pairs, a RAID 0 stripe is mirrored to a second stripe on a
duplicate set of disks. RAID 6 is sometimes referred to as RAID 10.
RAID 6 is the best combination of reliability and performance. Unfortunately, it halves the disk
capacity of a server and doubles its cost.
RAID 7
In the past, servers have had to treat each disk individually. This is often referred to as RAID 7.
The following table covers the advantages and disadvantages of the different RAID levels on
servers
possible if the transaction log is protected from system failure. Protecting the transaction log has
several implications:
The transaction log should be on a device where caching is disabled. The transaction log
relies on the operating system to report the completion of a write operation. If caching is
enabled, then the controller reports a write as complete as soon as data is in cache.
If possible, the transaction log should be on a device protected fully by RAID. Unfortunately,
RAID 5 is a bad choice for this because RAID 5 write performance without using the
controller cache is very limited.
For optimal system integrity, the system should be protected by a UPS.
The following examples show recommended setups for ISMP5* or 6* configurations from 2 to 8
drives:
Drives Packs System drive 1 System drive 2 System drive 3 System drive 4
2 Two RAID 7 WB RAID 7 WT
packs,
each with
one drive.
3 One pack RAID 5 WB RAID 1 WT
1.5GB 500MB
4 One pack RAID 5 WB 2GB RAID 1 WT
500MB
5 Pack of RAID 5 WB 2GB RAID 1 WT RAID 1 WB
three 500MB 500MB
Pack of
two
6 Pack of RAID 5 WB RAID 5 WB RAID 1 WT RAID 1 WB 500MB
four Pack 1.5GB 1.5GB 500MB
of two
7 Pack of RAID 5 WB 2GB RAID 5 WB 2GB RAID 1 WT RAID 1 WB 500MB
five Pack 500MB
of two
8 Pack of RAID 5 WB RAID 5 WB RAID 1 WT RAID 1 WB 500MB
six Pack 2.5GB 2.5GB 500MB
of two
The principles used to define these configurations can be generalized as follows:
Two physical drives is very limiting. Assuming you need more than 1GB of real space and
reliability is important, then RAID 7 is the only possibility.
The database log should go on a logical drive with write-through cache enabled. These
drives are indicated by bold type in the table.
If possible, have at least two system packs. This prevents the write-through cached drives
from badly affecting the performance of the rest of the system.
Many older DOS and Windows applications cannot install on drives larger than 2GB. In
many situations, a C drive size of 2GB or smaller is advisable.
The configurations recommended in the previous table show the importance of having many
drives. Try to remember this when ordering servers from any vendor. If performance is
important, you should order as many drives as you can afford.
For a system which is used for file sharing of primarily read-only data, the recommended
configurations are simpler:
Drives System System drive 1 System drive 2 System drive 3 System drive 4
packs
2 Two packs, RAID 7 WB RAID 7 WB
each with
one drive.
5 Pack of five RAID 5 WB 1GB RAID 5 WB 1GB RAID 5 WB 1GB RAID 5 WB 1GB
The following scripts are provided as examples and should not be used until a system
manager at your site has reviewed them to ensure that they will be usable in your
environment.
Intergraph Corporation assumes no risks or responsibilities regarding the use of these
scripts. They are provided for customers to use at their own discretion.
You can download a copy of these scripts from the World Wide Web. These scripts and other
utilities are at the following web address: http://support.intergraph.com.
$newfile = $PROJDIR."\\rdb\\spec\\flange.data";
©_files ($oldfile, $newfile);
$oldfile = $PDDATA."\\sample\\data\\pcd_size.data";
$newfile = $PROJDIR."\\rdb\\spec\\pcd_size.data";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Reference Data Base Options...\n";
$oldfile = $PDDATA."\\sample\\data\\rdb_options";
$newfile = $PROJDIR."\\project\\RDB_options";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Piping Job Spec Library...\n";
$oldfile = $RDUSRDB."\\us_pjstb.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pjs_tbl.l";
©_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\us_pjstb.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pjs_tbl.l.t";
©_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\us_pjstb.l.r";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pjs_tbl.l.r";
©_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\us_shbom.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\short_bom.l";
©_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\us_lgbom.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\long_bom.l";
©_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\us_spbom.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\spclty_bom.l";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Standard Note Library...\n";
$oldfile = $PDSHELL."\\lib\\std_note.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\std_note.l";
©_files ($oldfile, $newfile);
$oldfile = $PDSHELL."\\lib\\std_note.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\std_note.l.t";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Label Description Library...\n";
$oldfile = $PDSHELL."\\lib\\labels.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\labels.l";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Piping Assembly Library...\n";
$oldfile = $PDSHELL."\\lib\\assembly.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\assembly.l";
©_files ($oldfile, $newfile);
$oldfile = $PDSHELL."\\lib\\assembly.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\assembly.l.t";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Graphic Commodity Library...\n";
$oldfile = $PDSHELL."\\lib\\pip_gcom.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pipe_gcom.l";
©_files ($oldfile, $newfile);
$oldfile = $PDSHELL."\\lib\\pip_gcom.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pipe_gcom.l.t";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Physical Data Library...\n";
$oldfile = $RDUSRDB."\\us_pcdim.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\us_pcdim.l";
©_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\us_pcdim.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\us_pcdim.l.t";
©_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\us_pcdim.l.r";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\us_pcdim.l.r";
©_files ($oldfile, $newfile);
print "\n";
print "Copying Eqp Tutorials...\n";
$oldfile = $PDEQP."\\dat\\zi_eqpms.lib";
$newfile = $PROJDIR."\\rdb\\eqp\\unapproved\\zi_eqpms.lib";
©_files ($oldfile, $newfile);
$oldfile = $PDEQP."\\dat\\zi_eqpms.hlp";
$newfile = $PROJDIR."\\rdb\\eqp\\unapproved\\zi_eqpms.hlp";
©_files ($oldfile, $newfile);
$oldfile = $PDEQP."\\dat\\zi_tutlib.lib";
$newfile = $PROJDIR."\\rdb\\eqp\\unapproved\\zi_tutlib.lib";
©_files ($oldfile, $newfile);
print "\n";
print "Copying unapproved to approved...\n";
$dir = $PROJDIR."\\rdb\\lib\\unapproved";
opendir (D, $dir) || die "Can't open $dir: $!\n";
@filelist= sort grep (!/^[.]/
&& !/^[.][.]/
&& (tr/A-Z/a-z/ || 1), readdir(D));
closedir(D);
foreach $fil (@filelist)
{
$oldfile = $PROJDIR."\\rdb\\lib\\unapproved\\".$fil;
$newfile = $PROJDIR."\\rdb\\lib\\approved\\".$fil;
}
print "\n";
print "Copying Sample Report Format...\n";
$dir = $PDREPORT."\\sample";
opendir (D, $dir) || die "Can't open $dir: $!\n";
@filelist= sort grep (!/^[.]/
&& !/^[.][.]/
&& (tr/A-Z/a-z/ || 1), readdir(D));
closedir(D);
foreach $fil (@filelist)
{
$oldfile = $PDREPORT."\\sample\\".$fil;
$newfile = $PROJDIR."\\report\\format\\".$fil;
PD_Design
Command File Name Location
Design Checker dsgnchkr.log temp
<project_name>.dcl temp directory
Approval Manager pdapprov.rep temp directory
<project_name>.apl temp directory
Approval by Line ID same as approval
manager
Database Verification dbv.log temp directory
<project_name>.dvl temp directory
P&ID Comparison pdpidrpt.log temp directory
pdpidrpt.cmp temp directory
P&ID Named Item Report pdpidcmp.log temp directory
piditem.cmp temp directory
Plot Model plot.log temp directory
m<model_index_no>.ptl temp directory
Inspection Iso Manager pdinsiso.rep temp directory
PD_Model
Command File Name Location
Model Builder pdmodbld.log temp directory
PD_Draw
Command File Name Location
Create Drawing drw<drawing_type_no>.lo temp directory
g
crdrwque.log temp directory
VHL hline.log temp directory
<drawing_indx_no>.hlg temp directory
PD_Report
Command File Name Location
MTO rpt_error.log temp directory
PD_Review
Command File Name Location
DesignReview Label Builder labelbld.log temp directory
<dri_control>.err dri file directory
DesignReview Label Sender drtrans.rvw temp directory
drtrans.log temp directory
Plot Model plot.log temp directory
m<model_index_no>.ptl temp directory
PD_Clash
Command File Name Location
Interference Checker <project or area>.ilg temp directory
<project or area>.icl temp directory
Envelope Builder <project or area>.blg temp directory
<project or area>.ebl temp directory
Clash Report rpt_error.log temp directory
Plot Manager <project or area>.icl temp directory
Approval Manager/plot <project or area>.icl temp directory
PD_Project
Command File Name Location
Create Model from ASCII cmdlasci.log temp directory
List
<project_name>.cma temp directory
Create Database Tables crtmodel.rep temp directory
<project_name>.cml temp directory
PD_Data
Command File Name Location
Load PJS/pmc pmc.log temp directory
Load PJS/commodity pcd.log temp directory
Load PJS/specialty splty.log temp directory
Load PJS/instrument instment.log temp directory
Load PJS/taps taps.log temp directory
Load PJS/size-dependent pcd_size.log temp directory
Load PJS/implied implied.log temp directory
Load PJS/exclusion compinsu.log temp directory
Load PJS/flange exclusion flnginsu.log temp directory
Load PJS/construction cons_tol.log temp directory
PD_Design
Command File Name Location
PD_Model
Command File Name Location
PD_Draw
Command File Name Location
PD_Report
Command File Name Location
PD_Review
Command File Name Location
PD_Clash
Command File Name Location
PD_Project
Command File Name Location
PD_Data
Command File Name Location
Notes:
The temp directory is defined by the environment variable TEMP. if the TEMP environment
variable is undefined, the environment variable TMP is used. If neither of these environment
variables is set, C:\temp is used as the temp directory.
Notes:
In This Appendix
Setup Information .......................................................................... 199
FrameWorks Environment ............................................................. 214
FrameWorks Plus and SmartPlant Review ................................... 225
FrameWorks Plus and PD_Clash .................................................. 227
FrameWorks Plus and Material Data Publisher............................. 228
Setup Information
You need to set up a project, a structural discipline design area, and create a FrameWorks Plus
model before you can use FrameWorks Plus in the PDS environment.
Always press ENTER when entering values in PD_Shell.
See Also
FrameWorks Plus Categories (on page 213)
Creating a Model in PD_Shell (on page 203)
Creating a Model by ASCII File (on page 205)
Creating a Structural Discipline Design Area (on page 201)
Creating or Inserting a FrameWorks Plus Project (on page 200)
Intergraph SmartPlant License Manager (on page 199)
Shifting the FrameWorks Plus Global Origin to Match PDS Design Volume (on page 208)
The total path length to the FrameWorks Plus project including the drive letter and the
required \'s is limited to 36 characters.
To avoid creating models with incorrect working unit settings, adjust the working unit
settings of FrameWorks Plus seed files after creating the projects, and before creating
models.
FrameWorks Project Number - Specifies the FrameWorks Plus project name (the top- level
project directory that appears in the Windows NT Explorer). This string can contain letters and/or
numbers but no other special characters except the underscore (_) character. Names are limited
to 14 characters.
FrameWorks Project Name - Type a description for the project.
FrameWorks File Directory - Type the full path to the directory where you want to store the
project. Make sure you do not duplicate the project name in this path.
For example:
FrameWorks Plus Project Number: fwstr
---AND---
FrameWorks Plus File Directory: c:\pds_proj_dir\project
Will give you:
c:\pds_proj_dir\project\fwstr\
c:\pds_proj_dir\project\fwstr\data
c:\pds_proj_dir\project\fwstr\drw
c:\pds_proj_dir\project\fwstr\esl
c:\pds_proj_dir\project\fwstr\frz
c:\pds_proj_dir\project\fwstr\int
c:\pds_proj_dir\project\fwstr\mod
c:\pds_proj_dir\project\fwstr\rpt
Entering an extra \fwstr on the end of the FrameWorks Plus File Directory name could
complicate the directory structure. If you key in c:\pds_proj_dir\project\fwstr for the directory
name and fwstr for the Number, you will get c:\pds_proj_dir\project\fwstr\fwstr for the final
FrameWorks Plus Subproject directory name.
FrameWorks Network Address - Specifies the computer on which the FrameWorks Plus
project is located. Enter the computer's name.
Force Units - Specifies the force units to use by default for the member loads placed in this
project. The force units are stored in the Standard Note Library List 1640.
Standard Section Table - Specifies the standard section table to use by default for models
created in this project. There are several standard section tables delivered with FrameWorks
Plus. The standard section table location is read from the ..\fwplus\data\config.dat file.
User Section Table - Specifies the user section table to use by default for models created in
this project.
List of Existing FrameWorks Projects - Lists all existing FrameWorks projects.
To delete a FrameWorks Plus subproject, you must delete the entries in pdtable_116 and
pdtable_117.
Design Area Name - Type a name for the structural discipline design area.
Use the same name for the Design Area as the FrameWorks Plus subproject for easier
tracking.
Description - Type a description for the design area.
Structural Sub Project - Select the FrameWorks Plus project you want to associate with this
design area. Click the field to see the available structural projects.
No Interference Management Design Area / Interference Management Design Area -
Specifies if you want to define an Interference Management Design Area for this design area.
We recommend that you select "No Interference Management Design Area."
If you select Interference Management Design Area, a design_area_name.3 clash marker file is
created in the pds project directory. (The 3 extension indicates the structural discipline number
from pdtable_111).
Model Number - Type a name for the model. Model names are limited to 10 characters.
Seed Model - Select the seed model to use to create the model. The seed directory is defined in
the project\data\config.dat file. If no seed model is selected, PDS creates a standard model
based on the selected units.
Frozen Model Name - Displays the name of the propagated model file. This is the Model
Number name with a .prp extension.
Model Description - Type a description for the model.
Model Directory - Displays the directory the propagated model is created in. This directory is
set when you create the FrameWorks Plus subproject and cannot be changed.
Workstation/Server Name - Displays the name of the computer on which the model is saved.
This is computer is set when you created the project and cannot be changed.
Application Type - Displays the structural application type. Do not change this value.
Model Status - Select a model status from the entries for code list set 1605. Model status is
used for clash to exclude models for clash detection. The model status can be used to eliminate
certain models, such as those considered to be preliminary or temporary, from clash checking or
from SmartPlant Review.
Force Units - Select the force units for loads placed in this model. We recommend that all
models in the same project use the same force units. This option is not available if you are using
a seed model.
You cannot change force units after the model is created.
Standard Section Table - Select the standard section table you want to use for the model. This
option is not available if you are using a seed model.
You cannot change the standard section table after the model is created.
User Section Table - Select the user section table you want to use for the model. You can
change the user section table after the model is created. The user section library must have
been created using FrameWorks Plus Manager or from the command line. This option is not
available if you are using a seed model.
Third Party Software - Select the analysis software you plan to use on this model. You can
select another application after the model is created. This option is not available if you are using
a seed model.
Design Code - Select the design code you plan to use on this model. You can select another
design code after the model is created. This option is not available if you are using a seed
model.
Propagated and Sparse / Propagated Only - Select whether to create either a propagated and
sparse model, or just a propagated model.
Propagate and Sparse / Propagate Only toggle defines the process for Batch Propagation inside
PDS with the Frozen Model Name model.
Propagate Only copies the project related seed file into the project\frz directory and renames it,
and propagates into the file.
Propagate and Sparse copies the model.dgn file from the project\mod directory to the project\frz
directory and propagates into the file.
The batch propagation process uses the symbology from the first 3D isometric view defined in
the FrameWorks Plus model.
The model.prp file is used for Attach PDS Reference Model command, creating Isometric ASCII
reference file, and SmartPlant Review sessions and labels. To generate Isometric ASCII file and
to identify structural members for Pipe Support placement, you must use Propagate and Sparse
option.
We recommend that you regularly compress your .prp files. An easy way to compress is to use
the Compress Directory command in MicroStation Manager.
Sparse Model Name - Displays the name of the sparse model. This is the Model Number name
with a .dgn extension.
Sparse Model Directory - Displays the directory the sparse model is created in. This directory
is set when you create the FrameWorks Plus subproject and cannot be changed.
Sparse Workstation/Server Name - Displays the name of the computer on which the model is
saved. This is computer is set when you created the project and cannot be changed.
Create a Model
1. Click Start> Programs> PD_Shell> PD_Shell.
2. Select a PDS project.
3. Click Project Administrator.
4. Click Project Environment Manager.
5. Click Create.
6. Click Create Model.
7. Click Structural from the list of Disciplines.
8. Click Accept.
9. Select the design area that is specific to the FrameWorks Plus Sub Project.
If you did not let PDS know about the FrameWorks Plus project by using the Insert
FrameWorks Data option before creating the design area, a message stating This is not a
ModelDraft Model displays.
This message displays for any model that is not part of a FrameWorks Plus subproject. This
message implies that any model created in this way is considered dumb graphics. It will be
available as a reference file, but it will be ignored for such operations as the SmartPlant
Review intelligent tag creation and envelope file generation.
You can easily integrate existing models you created with FrameWorks Manager by using
the Create Model command in PD_Shell. The Create Model command detects the existing
model and prompts you to confirm the model name. If you accept, PD_Shell creates entries
in pdtable_113 for the existing model.
10. Type a Model Number. This is the model name.
11. Select a seed model.
12. Type a Frozen Model Name.
13. Type a description for the model.
14. Select a Model Status.
15. Select Force Units for the loads in the model.
16. Select a Standard Section Table.
17. Select a User Section Table.
18. Select a Third Party Software. This is the software you plan to use for analytical design.
19. Select a Design Code.
20. Select Propagated and Sparse or Propagated Only.
21. Select Accept.
Keywords
Discipline: The discipline name exactly as it appears in the PD_Shell environment (example:
Discipline: Structural) is required information.
Area_Name: A required 20-character design area name; it must be unique across disciplines
(example: Area_Name:Struct_A).
Area_Desc: An optional 40-character description for the design area being created (example:
Area_Desc:Struct_A).
This option is required when creating a new area. If the area already exists, use
Area_Name only.
Area_Marker_File: An option to indicate that you want an interference marker file for the area
(example: Area_Marker_File:Yes).
This option is only for use in combination with Area_Description.
Area_Volume_Low/High: An option that indicates if the design area will have a predefined
volume for interference checking purposes. This is required if Area_Marker_File is Yes; the low
volume and high volume represent the limits of the volume processed by the interference
checker (example: Area_Volume_Low:-100,-250,- 50 Area_Volume_High:150,30,120).
This option is only for use in combination with Area_Marker_file.
Sub_Proj_Number: Required information for structural models. It defines the structural
subproject.
This option is required when creating a new area in combination with Keyword
Area_Desc
Model_Number: A required up to 10-character Structural model number of the model to be
created (example: Model_Number:Model_A).
Model_Desc: Optional up to 40-character description of the model to be created (example:
Model_Desc:Model A Description).
File_Spec: An optional 14-character file specification of the model to be created. If a value is not
specified or the keyword is missing, the file specification defaults to the model number with the
extension .dgn (example: Model_A.dgn).
Not supported for structural since defined in the subproject.
Path_Name: An optional 35-character directory path where the model file is to be created
(example: d:\proj\models\). If this value is not specified or the keyword is missing, the default
values as defined with the Model Setup option are used.
Not supported for structural since defined in the subproject
Network_Address: An optional 26-character node name of the system on which the model file
is to be stored This value is not specified or the keyword is missing, the default values as
defined with the Model Setup option, are used.
Not supported for structural since defined in the subproject
Application_Type: An optional value indicating the discipline association for interference
checking purposes. It associates the design model with a different discipline for reporting
clashes. The default is the discipline where the design model is created (example:
Application_type:Structural).
Model_type: For structural models only, the type of structural model to be created. Its value is
set as follows: both or propagate settings will NOT create a physical file. These settings ONLY
create an entry in the project schema's pdtable_113.
both: defines a model_type =2 in pdtable_113. It defines that while running batch
propagation the prp file will contain the sparse model (which is a single line model) and a 3D
model (which is the so-called propagated model.
3. Into the BASIC Editor dialog box, enter the following text which creates an Auxiliary
Coordinate System that is offset 100 ft East and 75 ft North from the DGN file's default 0,0,0
location.
4. Click File > Save to save the macro. Name it something useful. For example, the previous
example could be named Unit1ACS.bas.
You can now select Run from the Macro menu for this new macro and your Auxiliary
Coordinate System will be set up and active.
You must load this macro every time you enter this model in order for this ACS to be
active.
See Also
Automatically load an Auxiliary Coordinate System within a model (on page 211)
Create a prompt for automatic loading (on page 211)
The Builder dialog box opens. Here you define the dialog box to open and the options
associated with it.
2. Click New.
A new dialog box opens allowing you to edit the text.
3. To include a message, add a label from the Builder Tools menu and place that label on the
dialog box.
4. In the Builder window labeled PushButton, double-click the items you want to label.
5. Change the text for these items to provide Yes and No buttons, and a label asking what to
do next.
6. Save the dialog box and return to your Script
FrameWorks Environment
This form provides access to the FrameWorks Plus environment from within PD Shell.
Modeling - Used to select a design area and a model to enter. For more information, see
Modeling (on page 215).
Drawing Environment - Used to create, delete, and enter drawings. For more information, see
Drawing Environment (on page 215).
Propagation - Used to create propagated models and binary files for SmartPlant Review labels.
For more information, see Propagation (on page 216).
Generate ASCII File - Used to create an ASCII file that provides the location of all structural
components and grid lines in the project. This information is used to reference a single structural
column or a pair of grid lines on an isometric drawing. For more information, see Generate
ASCII File (on page 219).
Update/Regenerate Frozen View - Used to update or regenerate frozen views in your
FrameWorks Plus models in batch mode. For more information, see Update/Regenerate Frozen
View (on page 219).
Batch Cutout - Used to create or update solid cutouts in batch mode. For more information, see
Batch Cutout (PD_Shell) (on page 220).
Verify Model - Scans your model checking for zero length members, overlapping members, and
members with invalid sections. For more information, see Verify Model (PD_Shell) (on page
224).
CIM Steel Export - Exports all members to a CIS/2 file based on specific member criteria. For
more information see, CIM Steel Export (PD_Shell) (on page 224).
Modeling
The command is used to enter the FrameWorks Plus modeling environment. Selecting a Design
Area displays all the models in that Design Area. Selecting a model opens the FrameWorks Plus
model in MicroStation.
Drawing Environment
The command is used to enter the FrameWorks Plus drawing composition environment. After
selecting a project, you can create drawings, delete drawings, or go into the drawing
composition environment.
There are no entries in the PDS database for the drawings. The drawings are generic
MicroStation design files.
Create --- Used to create new drawings in the selected project.
Delete --- Used to delete drawings from the selected project.
Composition --- Used to enter a drawing in the selected project.
Create
This form is used to create a drawing in the active project. PD_Shell copies the dseedm.dgn or
dseedf.dgn seed files (depending on the project units) from the ..\fwplus\seed directory to the
project \drw subdirectory.
Drawing Name - Type a name for the drawing you want to create. The drawing name is limited
to 8 characters.
Delete
This form is used to delete a drawing from the active project. Select the drawing to delete from
the list, and then click Accept.
Composition
This form is used to enter the FrameWorks Plus drawing composition environment. Select the
drawing you want to open, and then click Accept.
Create
This form is used to create a drawing in the active project. PD_Shell copies the dseedm.dgn or
dseedf.dgn seed files (depending on the project units) from the ..\fwplus\seed directory to the
project \drw subdirectory.
Drawing Name - Type a name for the drawing you want to create. The drawing name is limited
to 8 characters.
Delete
This form is used to delete a drawing from the active project. Select the drawing to delete from
the list, then click Accept.
Composition
This form is used to enter the FrameWorks Plus drawing composition environment. Select the
drawing you want to open, then click Accept.
Propagation
This form is used to create propagated models based on the option defined during model
creation. The output will be a propagated or propagated and sparse model.
If you create your propagated model using this command, you should use this command to
keep the propagated model up to date. Do not use the update or regenerate commands or
any of the related commands inside of FrameWorks Plus to update a propagated model.
You may see this message in the log file, "Unable to locate saved view information. Saved
view information is re-created." This message is not an error message but happens because
the software first deletes the propagated file and then re-creates it.
Propagate Only copies the project related seed file into the project\frz directory and renames it,
and propagates into the file.
Propagate and Sparse copies the model.dgn file from the project\mod directory to the
project\frz directory and propagates into the file.
The batch propagation process uses the symbology from the first 3D isometric view defined in
the FrameWorks Plus model. If no 3D isometric view exists in the model, the software creates a
temporary view using the default isometric settings.
The model.prp file is used for Attach PDS Reference Model command, creating Isometric ASCII
reference file, and SmartPlant Review sessions and labels. To generate Isometric ASCII file and
to identify structural members for Pipe Support placement, you must use Propagate and Sparse
option.
We recommend that you regularly compress your .prp files. An easy way to compress is to use
the Compress Directory command in MicroStation Manager.
Make sure the user section libraries are attached and accessible in the FrameWorks Plus
model.
All Models - Click this button to propagate all the models.
Selected Areas - Click this button to select an area(s) in which you want all models propagated.
Selected Models - Click this button to select the model(s) to propagate.
Submit Batch Immediately / Delayed Batch Submit Time - Choose whether to propagate the
selected models now, or propagate them at a later time.
Ignore Smartcuts - Select this checkbox to ignore SmartCuts when creating the propagated
model.
Schedule Propagation - Select to schedule a reoccurring propagation job.
The log on user (system account or "this account") will impact how you set the account
mapping in Batch Manager. For additional information, see the System Administrator
Responsibilities section of the PDS Project Setup Technical Reference.
Scheduled Model Propagation does not perform a propagation at the time it is created.
Instead, command files are created to alert the system to perform a propagation at a
specified time of day. The command files are launched by the system scheduler utility.
Operating Sequence
1. Select Schedule Propagation from the FrameWorks Propagate Model form.
The Scheduled Model Propagation form is displayed.
2. Select the required option.
Create/Revise Model Propagation Schedule (on page 217) --- Creates a scheduled
envelope/clash batch job.
Create/Revise Model Propagation Schedule (on page 217) --- Revises an existing
envelope/clash batch job.
Delete Model Propagation Schedule (on page 218) --- Deletes a scheduled
envelope/clash batch job.
Review Schedule (FWP) (on page 218) --- Reviews previously defined envelope/clash
schedules.
List Area - Displays the models or selected area that you want to update or regenerate.
Update/Regenerate - Select whether you want to update all models, models in selected areas,
or only selected models.
Update or Regenerate option - Select whether you want to Update the frozen views or
Regenerate the frozen views.
Update automatically updates the permanent, Frozen View graphics to reflect any structural
model changes. The Update Frozen command compares the status of the member graphics in
the Frozen View to the current model status and adds or removes members from the Frozen
View accordingly.
Regenerate recreates all Frozen View graphics from the current model using the current Model
View's display style and settings. All existing graphics in the selected Frozen View are deleted
and replaced with the new graphics.
Include Attached FWPlus Models - Select to include attached FrameWorks Plus models when
the frozen views are updated or regenerated.
Update User Graphics - If this option is on, generic MicroStation elements in the Model View
are also updated or regenerated along with the FrameWorks Plus members. Generic
MicroStation elements that you have added directly to the frozen file (not the model file) using
MicroStation are not affected by this command.
Using Batch Cutout may cause unpredictable results in the project and models. For
example, when running batch cutouts, you have no way of knowing which models are attached
or detached to other models. You may lose cutouts if someone else unknowingly detaches a
piping model for example. In addition, you may have set different clearance options in different
models. The batch cutouts process can potentially overwrite those clearance settings. Be
especially diligent when using batch cutouts.
Cutouts are not available for walls.
List of Models - Display the model on which the batch cutout process will run.
Clearance - Specifies the distance between the inside of the cutout and the outside of the item
being cut around. This distance is added evenly to all sides of the item. If you are placing a
sleeve around a pipe, the distance between the inside of the sleeve and the outside of the pipe
is the Clearance value. The Clearance value you type in must be in inches for imperial projects
and millimeters for metric projects.
Be careful when defining the Clearance value when cutouts will be created around closed
shapes such as I-section or channels. The Clearance is added evenly to all sides of the shape.
If you define a Clearance that is greater than half the distance between sides of a closed shape,
FrameWorks Plus will not place the cutout. For example, the distance between an I-section's
flanges is 8.5 inches. If you define a Clearance greater than 4.25 inches, the cutout will not be
placed.
Increment - Specifies the value by which to increment the cutout diameter around a circular
penetration (such as a pipe). For example, if you set the Increment to 2" (inches), the cutout
diameter is always divisible by 2 (2", 4", 6", 8", ... 22", 24", 26", and so forth). Similarly, if you set
the Increment to 3", the cutout diameter is always divisible by 3 (3", 6", 9", 12", and so forth).
Setting the Increment value to 0 causes the cutout diameter to be the outside diameter of the
penetrating object plus the Clearance value, if any.
The Increment value you type in must be in inches for imperial projects and millimeters for
metric projects.
You can use the Increment Factor setting to control the rounding up or rounding down of the
cutout diameter to the next allowed size.
Increment Factor - Specifies if the cutout is rounded up or rounded down to the next Increment
size. For example, you place a 10.875 inch pipe with 3 inch clearance and a 2 inch Increment.
You can use this Increment Factor to control whether a cutout with a 16" diameter or a cutout
with a 18" diameter is placed.
If the Increment Factor is set to 0, the cutout is always rounded up to the next increment
divisible size. If the Increment Factor is set to 1, the cutout is always rounded down to the next
increment divisible size. Typically, you would want to set the Increment Factor to 0.5.
If the Increment Factor is between 0.01 and 0.99, FrameWorks Plus calculates whether to round
up or down based on the following algorithm.
Compute the cutout diameter by adding the outside diameter of the pipe with two times the
Clearance value. For example, if the pipe diameter is 10.875" and the Clearance is set to 3", the
cutout diameter would be 16.875" (10.875 + 2 x 3 = 16.875).
FrameWorks Plus reads the remainder (non-integer) part of the cutout diameter. In this case,
0.875 inches.
1. Multiply the Increment and the Increment Factor then compare the results to the remainder
read in step 2. If the remainder is less than the calculation, round down. If the remainder is
greater than the calculation, round up. For this example, say the Increment is set to 2". The
following table shows the results of different Increment Factors.
Remainder from Increment X Increment Resulting Action
step 2 Factor
size even if the fireproofing setback is such that the fireproofing does not intersect the solid
member.
Include Piping Insulation Thickness - The software should consider piping insulation
thickness when calculating the cutout size. The piping insulation does not need to be graphically
displayed in order to be used in the calculation.
Report Action - Defines the action to perform when members intersect solids.
Place Holes & Report -- Places a hole in the solid for the intersecting member to pass
through. The shape of the intersecting member is used as a pattern for the solid's hole. The
size of the hole will be the exact size of the intersecting member unless you specify a
Clearance value.
Place Holes, Sleeves, & Report -- Places a hole in the solid for the intersecting member to
pass through. If the intersecting member is round, a pipe sleeve is also placed.
Pipe sleeves are placed only if the intersecting member is perpendicular to the slab
or solid. Members that intersect at an angle will not have pipe sleeves placed.
No Action - Report in Logfile -- Writes the number of members that intersect solids to the
logfile.
Sleeve Type - Specifies the member type you want to use for the sleeve. FrameWorks Plus
uses the default section of the selected member type for the pipe sleeve section. We
recommend you place sleeves using cardinal point 1. This option is only available if the Place
Sleeve option is selected.
FWP Linear Members - Specifies that FrameWorks Plus should place cutouts for FrameWorks
Plus linear members that intersect a solid.
The section shape of the linear member must intersect both faces of the solid for
FrameWorks Plus to place a cutout.
FWP Solid Members - Specifies that FrameWorks Plus should place cutouts for FrameWorks
Plus solids members that intersect a solid.
MSTN Solids, Surfaces & Cones - Specifies that FrameWorks Plus should place cutouts for
MicroStation solid elements that intersect a solid.
FrameWorks Plus will not create cutout for wedge, sphere, or torus MicroStation shapes.
Optional input template file - Allows you to select a label template file (SPRFWPlusLabels.bin)
to use while publishing your project. The settings you specify using this dialog box are saved in
this file so that you can retrieve them each time you publish the project or to use as a template
each time you set up a project for publication. You may have only one label template file per
project and the file must be named SPRFWPlusLabels.bin. You must re-create the label
database (re-publish) each time you want to change the set of binary labels available in the
published project.
File output directory - Allows you to specify the location for the label template file. This path
should point to either the project folder (where the .dri file is located or from where the design file
was opened) or to the same folder where the SmartPlant Review Publisher executable is
located (C:\Program Files\SmartPlant\Review Publisher). If SmartPlant Review Publisher does
not find SPRFWPlusLabels.bin file in either the project or application folder, the binary label data
is not added to the published label database.
Linear and Arc Element Names - When clicked, only linear (structural members like beams
and cross braces) and arc element labels appear for selection in the Label list.
Solid Element Names - When clicked, only solid element (slabs, walls, and solid) labels appear
for selection in the Label list.
Select labels to display - Displays the available binary labels according to the button selected
above. Check the box by the label name to add that label to the label database. Click the arrow
in the column header to sort this list alphabetically, either ascending or descending.
Select All - Click to add all labels in the list to the label database. This button is useful if you
want all but a few of the labels to be included. Simply click this button, then uncheck the labels
that you do not want added to the label database.
Clear All - De-selects all checked labels in the list.
Save - Saves the specified list of labels to the label template file (SPRFWPlusLabels.bin), which
is then used by SmartPlant Review Publisher to add the selected label data to the label
database during the publishing process.
If there are errors, the envelope file is invalid. You will need to go back into FrameWorks Plus
and run the File> Verify Model command to check for overlapping members and members with
invalid sections.
Cutbacks are not written to the envelope file. However, PD_Clash can determine if there
is a clash between FWP members (even if cutbacks were applied) or not.
Because the FrameWorks Plus member names appear in the report, all FrameWorks Plus
member names should be unique. Using unique member names makes locating the member in
graphics easier.
To review and approve clashes, use PD_Clash Interference Approval Manager or the PDS
integrated commands inside FrameWorks Plus.
If a member is partially flooded, the software considers it fully flooded when calculating the
center of buoyancy.
FrameWorks Plus does not calculate center of buoyancy or the buoyancy force for members
with arbitrary sections.
If the Material Data Publisher detects a corrupted model, it continues with the next model.
In This Appendix
Oracle 11g ..................................................................................... 229
Oracle 10.2g .................................................................................. 248
Oracle 10g ..................................................................................... 264
Oracle 11g
This section covers the installation of Oracle 11g on systems running Windows server. Before
loading Oracle, it is recommended that RIS Oracle Data Server (RISORADS) be loaded. For
more information on installing different versions of Oracle, see the Technical Notes and
Whitepapers section of the eCustomer site.
1. By default, the setup program will install the database software and create all database files
on the C drive. The database software requires a varied amount of space, which can be
large, so plan your installation accordingly. Having installed RISORADS and identified
where the database software and database files will be installed, double-click the setup
executable located in the Oracle 11g installation directory. The system will initialize the
Oracle Universal Installer first showing a command window then the following dialog box.
4. Define the name of your Oracle Instance and define the Oracle Base Location (Oracle
BASE is a new feature in V11 of Oracle), then click Next.
5. Oracle will run a Product-Specific Prerequisite Check application. After that process
finishes and all checks pass, click Next.
8. Select Create a database on the Create Database screen, and click Next.
9. If the component Oracle Services for Microsoft Transaction Server 11.1.0.6.0 is selected
for install, then at this point the installer prompts for Port Number. Retain the default, and
click Next.
10. At this point the installer displays a Summary screen that outlines your choices so far and
allows for review. If needed, you can click Back and change settings. Click Install.
11. The system will start the install process providing you with a dialog showing its progress as
it does the installation:
When the installation is finished the system will display the Configuration Assistants
dialog box and will continue the installation process. It will seem as if the system is hung at
this point but the status in the Tool Name window will state the Oracle Net Configuration
Assistant is In progress.
12. The software will then display the Oracle Net Configuration Assistant dialog box. Select
the Perform typical configuration option, and click Next.
14. Type the name of your database in the next dialog box, and click Next.
15. In the Management Options dialog box, leave the Configure Enterprise Manager and
Configure Database Control for local management options checked and click Next.
16. Provide a password for the sys, system, dbsnmp and sysman administration account
users. You can do this by providing different passwords for each or the same for all of them.
When you are finished, click Next.
17. On the Step 5 of 14 dialog box, select the File System option, and click Next.
18. In the next dialog choose the location for your database file as outlined by your
administrator. Keep in mind space and processor needs. When you are finished, click Next.
19. If flash recovery is to be used in your installation, select the option in the next dialog and
click Next.
20. The next dialog box will allow the installation of a sample schema for your use. Clear the
Sample Schemas option and, and click Next.
21. Select the default options in the Initialization Parameters dialog box, and click Next.
22. In the Security Settings dialog box, select the Revert to pre-11g settings option, and click
Next.
23. In the next dialog you can choose from a new option in V11g Oracle to setup and utilize
automatic maintenance tasks. The default setup is turned on. Select the option that meets
your needs and click Next.
24. Make the appropriate changes to the Database Storage dialog box, and click Next.
(Example changes could include changing the USERS01.DBF to PDS01.DBF and so on.)
25. Select the Create Database option from the final dialog box, and click Finish.
26. The software displays a final Confirmation dialog box which shows you the options you
have set. Click OK.
27. The software will now start to install the database and will provide you the following dialog
box showing the installation progress.
28. You will be provided some confirmation dialog boxes outlining the progress of the options
you choose. Click Exit when done.
You can now use iSQL Plus to create users and RIS to create schemas against this database.
For sample scripts see:
C:\Win32App\INGR\PDSHELL\sql\oracle\
Oracle 10.2g
This section covers the installation of Oracle 10.2g on systems running Windows server. Prior to
loading Oracle, it is recommended that RIS Oracle Data Server (RISORADS) be loaded.
1. By default, the setup program will install the database software and create all database files
on the C drive. The database software requires a varied amount of space, which can be
large, so plan your installation accordingly. Having installed RISORADS and identified
where the database software and database files will be installed, double-click the setup
executable located in the Oracle 10.2g installation directory. The system will initialize the
Oracle Universal Installer first showing a command window then the following dialog box.
Choose Advanced installation and click Next.
4. Choose your options from the available components list, and click Next.
The Oracle Programmer options are not needed, but it is suggested to install iSQL
Plus.
The product will run some tests to see that your computer is compatible and that it meets
the minimum requirements for Oracle installation. If all checks do not Succeed please see
Oracle installation guide for help. After you have all checks completed and passed, click
Next.
5. On the Create a database dialog box, select the Create a Database option, and click Next.
6. The software displays the Summary dialog box that outlines your choices so far and allows
for review. If necessary, click Back and change settings. Click Install.
7. The system will start the install process providing you with a dialog box showing its progress
as it does the installation.
8. When the installation is finished the system will display the Configuration Assistants
dialog box and will continue the installation process. It will seem as if the system is hung at
this point but the status in the Tool Name window will state the Oracle Net Configuration
Assistant is In progress.
9. The software will then display the Oracle Net Configuration Assistant dialog box. Select
the Perform typical configuration option, and click Next.
11. Type the name of your database in the next dialog box, and click Next.
12. In the Management Options dialog box, leave the Configure the Database with
Enterprise Manager and User Database Control for Database Management options
selected, and click Next.
13. Provide a password for the sys, system, dbsnmp and sysman administration account
users. You can do this by providing different passwords for each or the same for all of them.
Click Next.
14. On the Step 5 of 11 dialog box, select the File System option, and click Next.
15. In the next dialog choose the location for your database file as outlined by your
administrator. Keep in mind space and processor needs. Click Next.
16. If flash recovery is to be used in your installation, select the option in the next dialog, and
click Next.
17. The next dialog box will allow the installation of a sample schema for your use. Clear the
Sample Schemas option and, and click Next.
18. Choose the default options in the Initialization Parameters dialog box, and click Next.
19. Make the appropriate changes to the Database Storage dialog box, and click Next.
(Example changes could include changing the USERS01.DBF to PDS01.DBF and so on.)
20. Select the Create Database option from the final dialog box, and click Finish.
21. The system displays a final Confirmation dialog box which displays the options you have
set. Click OK.
22. The software starts to install the database. It displays the following dialog box showing the
installation progress.
23. You will be provided some confirmation dialog boxes outlining the progress of the options
you choose. Click Exit when done.
You can now use iSQL Plus to create users and RIS to create schemas against this database.
For sample scripts see:
C:\Win32App\INGR\PDSHELL\sql\oracle\
Oracle 10g
Oracle 10g topics:
Removal of Older RIS Client (Oracle 10g) (on page 264)
Production Database Installation (Oracle 10g) (on page 265)
The older versions of the RIS client software can be removed by running the Configure
RIS Version utility from the "highest number" program group. For example, if RIS client 05.02,
05.03, and 05.04 are all loaded, you would run the Configure RIS Version utility in the RIS 05.04
program group. As a precaution, make a copy of the schema file if it is located in any of the
older RIS product directories.
If you do not want to use these options, clear the check boxes and click Next.
17. On the Initialization Parameters screen, click Custom, review the default initialization
parameters, and then click Next.
18. Make changes as necessary on the Database Storage screen.
Intergraph recommends the following settings:
Tablespaces
Expand Tablespaces. Turn off Autoextend for each of the tablespaces.
System
On the Storage tab, select Managed in Dictionary.
Initial 100 KB
Next 100 KB
Minimum Size 0 KB
Increment Size by 1%
Minimum number 1
Maximum number 121.
Users
Change the name to pds
Change the size to 300 MB
Under Storage, select Managed in Dictionary
Initial 50 KB
Next 50 KB
Minimum Size 0 KB
Increment Size by 1%
Minimum number 1
Maximum number 121
Index
If it exists, delete the Index tablespace.
Temp
Change the name to temp_segs
Change the size to 30 MB
Under Storage, select Managed in Dictionary
Initial 100 KB
Next 100 KB
Minimum Size 0 KB
Increment Size by 1%
Minimum number 1
Maximum number 121
19. Click Next.
20. On the Creation Options screen, fill the Create Database check box and click Finish.
21. On the verification screen, make sure all the settings are correct and click OK.
22. Database usernames can now be created. Two sql scripts are provided with PDS to create
the database usernames using Oracle 10g. The scripts are located in the
c:\win32app\ingr\pdshell\sql\oracle folder and are called pdsroles.sql and
create_10g.sql. The pdsroles.sql script is used to create the PDSUSER role needed for the
PDS database usernames. The pdsroles.sql script is run only once and can be run from
within SQL Plus by entering @c:\win32app\ingr\pdshell\sql\oracle\pdsroles. After running
the pdsroles.sql script, the create_10g.sql script is edited and run. Below is an excerpt from
create_10g.sql for the pd_proj1 username.
CREATE USER pd_proj1 PROFILE DEFAULT IDENTIFIED BY pd_proj1
DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP ACCOUNT UNLOCK;
GRANT CONNECT, RESOURCE, PDSUSER TO pd_proj1;
23. A schema can now be created against this Oracle user name. In the Create Schema form
the database user name will be the user name you created in SQL Plus (pd_proj1). The
database management system location will be where you installed Oracle (c:\ora90, in this
example). The database name will be the same as your SID (pds in this example). The o/s
user name and network address will be specific to your server.
You must be able to log in on the database server as the specified o/s user name.
A new Oracle user name must be created for each new schema that you wish to create.
An Oracle user name and all of the objects that user owns can be deleted (from within
SQL Plus) using the following command:
drop user username cascade;
24. By default, Oracle 10g is installed to a folder such as d:\oracle\product\10.1.0\Db_1. You
must modify the permissions for the Db_1 folder to allow Read and Execute, List Folder, and
Read access to the operating system user specified when creating the RIS schema.
If these permissions are not granted, you may see an error message similar to the following
message:
RIS Error: RIS_E_INV_OPEN_DB (0x8a948e22)
CREATE SCHEMA sch2 ON DATABASE (oracle DBNAME orcl, OSTYPE NT, DIR
d:\oracle\product\10.1.0\Db_1, REMOTE (TCP db2003))
Underlying dbms could not open database
Oracle Error -12557
Error while trying to retrieve text for ORA-12557
This error does not occur if you create the schema on the database server while you
are logged on as an administrator.
In This Appendix
MSSQL Server 2008 ...................................................................... 269
MSSQL Server 2005 ...................................................................... 281
4. Check for any Setup Support Rules errors, and click OK.
8. Check for any Setup Support Rules errors, and click Next.
10. Select Default instance and specify Instance root directory, and click Next.
12. Change the Account Name box to NT AUTHORITY\SYSTEM for SQL Server Agent and
SQL Server Database Engine, click Next.
13. Select Mixed Mode. Specify a password for the SQL Server system administrators. Add
SQL Server administrators as needed, and click Next.
14. On the Error and Usage Reporting dialog box, click Next.
15. Check for any Installation Rules errors, and click Next.
16. Review the features to be installed, and click Install (installation may take several minutes).
SQL Server Management Studio has an explorer-style interface that lets you manage your
databases and perform a number of administrative duties. Pick the server name from the left
window pane, and you should see a number of folders in the right pane that allow you to
perform a variety of tasks on you installation.
4. In the left window pane, expand the server name where the PDS database will be created,
right click on Databases and select New Database.
5. Enter a Database name and click OK to create the database; the new files should be seen
in the specified directory.
Installation
Follow the steps below to install MSSQL Server version 2005.
1. Having installed RISMSFDS and identified where the database software and database files
will be installed, start the setup program by double-clicking on autorun.exe.
2. Select Local Computer and then click Next.
3. Choose the option Create a new instance of SQL Server and then click Next to continue.
4. Enter your Company/Name and continue.
5. Accept Yes: on the next screen.
6. Choose the options below and then click Next to continue.
SQL Server Database Services
Workstation Components
7. On the next screen accept the Default selection, which installs a default instance (i.e. one
identified by the name of the computer on which you are installing MSSQL).
For RIS to work with MSSQL 2005, the current installation of MSSQL should be
the Default Instance on the machine. If there's already a default instance, then RIS will not
be able to communicate with the MSSQL Server. Also, you can have only one default
instance per computer and the next one that you create must be a named instance.
8. Click Next to continue.
9. In the Setup Type form, select Typical. You can also specify different locations for program
and data files by using the Browse buttons.
If you have another installation of MSSQL from which you would like to import data,
then select Custom and then choose the same Sort Order as in the other installation so
that you can import/export data between the two. THIS IS A VERY IMPORTANT CHOICE
THAT MUST BE MADE IF YOU ARE USING A RIS-BASED APPLICATION. Even if you
start using an ODBC-based application, if there is a chance that you will want to connect to
this server using a RIS-based application, then you must select a case-sensitive sort order.
10. After changing or accepting the default the sort order to Dictionary Order – Case Sensitive,
accept the defaults for the remaining choices in this form. Continue on to the Service
Accounts form.
11. In the Services Accounts form, change the Service Settings to Use the built-in System
account. Click Next to continue.
12. Select either Windows Authentication Mode or Mixed Mode. If you select Mixed Mode, you
must specify a password for the MSSQL 2005 system administrator user (sa).
If you are creating PDS-specific logins for each project, this is possible only when you
are set up in Mixed Mode.
13. Click Next to continue. If you selected Custom in the previous form, you are presented with
the Collation Settings form. Choose the sort order other than the default, which is Dictionary
order, case-insensitive, for use with 1252 Character Set.
-or-
Accept the default Dictionary order, case-insensitive, for use with 1252 Character Set
option.
You will need to take into account the Sort Order if you would like to install databases
for other applications (INTOOLS, SPPID) on the same instance. The above will also work
with INTOOLS.
14. Click Next to continue.
15. Click Next on the Error and Usage Report Settings.
16. Accept the defaults on the screen and then click Next.
17. Accept Next again to go to the Licensing Mode form. Select your licensing mode and click
Continue.
18. Select Install. Wait for the install to finish (this may take several minutes).
19. Click Next and then click Finish.
20. At this point, MDAC 2.6 is installed. Files are copied to your local drive, and services are
installed and started. You are then asked to reboot.
The model database can be thought of as a "seed file" that is used as the basis for
creation of new databases.
The tempdb database is where information is temporarily stored when performing
operations such as sorts.
2. From the Start Menu, select Microsoft SQL Server Management Studio.
3. In the Connect to Server dialog box, select the Server Name gadget and select <Browse
for More>.
4. Select Database Engine and select the local server from the list. Click OK.
5. Select Connect to connect to the database.
6. Select your server name in the left pane. In the right pane, you see the folders that enable
you to perform a variety of tasks on your installation.
7. Right-click on your server name and select Properties.
8. Under the General tab, note if auto-start is set.
9. Under the Memory tab, note that MSSQL can now dynamically allocate memory as
required, or run with a fixed amount. Depending on the amount of memory available on your
server and on the additional workload, you may wish to either:
Use Dynamic Allocation with an upper limit in place
Use Fixed Allocation and specify the amount to use
10. You can examine the settings under the remaining tabs and then click Apply to save your
edits.
11. Leave the settings for the master, model, and tempdb at their default settings. Click OK to
exit the application.
General Page
3. Enter a database name of pds.
4. Under Database Files verify/modify the file name/location as needed.
5. Set the initial size for the Data File Type to 100M and the initial size of the Log File Type to
20M.
Options Page.
6. Click OK to create the database and the new files display in the specified directory.
Printer/Plotter
PDprint network printer,\\PDSTRF\LaserJet
PDprint is the PDS-recognized printer name.
The PDS printer name is followed by a TAB.
After the TAB, the description which is displayed to the user is entered, network printer in
this example.
If the optional printer name is being used, a comma is next.
The optional printer name \\PDSTRF\LaserJet is entered last.
It is valid to omit the optional printer name. The PDS software would then search for a printer
named PDprint. If PDprint is associated with a user-defined printer name, such as
\\PDSTRF\LaserJet, the software looks for \\PDSTRF\LaserJet instead of PDprint. For example:
PDprint network printer
---OR---
PDprint network printer,\\PDSTRF\LaserJet
Local Processing
If the batch job is processed locally, the PDS software looks on the local node for printers that
match those in the queue_descript file. Those printers that are valid on the local node are
displayed. If there are no printers on the local node that match those listed in the
queue_descript, the PDS software displays all of the printers defined on the local node.
Submitted Locally
If the PDS batch job is being processed locally, and you have elected to print the output at the
completion of the batch job, the PDS software reads the project queue_descript file, and
validates printers on the local node. Any printer that it finds on the local node which matches the
printer (or optional printer) name in the queue_descript file is displayed.
Using the example queue_descript file and initiating the batch process on node nt_two, the
following printer descriptions display:
network printer
Windows Connected Printer on a computer
If none of the printers in the queue_descript file exist on the local node, all of the printers on the
local node are displayed. Using the example queue_descript file and initiating the batch process
on computer nt_three, the following printer descriptions display:
\\nt_s_one\printer1
This is because none of the other printers described in the que_descript file exist on computer
nt_three.
In This Appendix
PDS and Windows 7 / Server 2008 ............................................... 293
PDS and Windows 2000 ................................................................ 297
If the Intergraph network adapter has been loaded, this folder will already exist.
4. Enter Intergraph for the KEY NAME. Note that it is case-sensitive.
5. Leave the CLASS field empty.
6. An Intergraph key now displays under the SOFTWARE folder.
7. Highlight the new Intergraph key and select EDIT > ADD VALUE from the registry editor
menu bar.
8. Enter COMMON for the VALUE NAME. Note that it is case-sensitive.
9. Select REG_SZ from the drop-down list for the DATA TYPE and click OK.
10. Enter C:\win32app\ingr\share in the String Editor form. The information that appears in
the right-hand side of the registry editor when you open the Intergraph folder should look like
this:
COMMON: REG_SZ: c:\win32app\ingr\share
Intergraph Products Already Loaded
1. Start the registry editor and locate the HKEY_LOCAL_MACHINE on the Local Machine
window.
2. Locate the SOFTWARE folder and double-click on it.
3. Open the INTERGRAPH key and look on the right-hand side.
The COMMON value should be set as shown below:
Common:REG_SZ:C:\Program Files\Common Files\Intergraph
4. If so, change the string for the COMMON key to read C:\win32app\ingr\share.
5. Go to the C:\Program Files\Common Files\Intergraph directory using Explorer and note
which Intergraph products have files loaded in this location. Remove these products and
reload them.
1. Start the registry editor and locate the HKEY_LOCAL_MACHINE on the Local Machine
window.
2. Locate the SOFTWARE > Wow6432Node folder and double-click on it.
3. Open the INTERGRAPH key and look on the right-hand side.
The COMMON value should be set as shown below:
Common:REG_SZ:C:\Program Files\Common Files\Intergraph
4. If so, change the string for the COMMON key to read C:\win32app\ingr\share.
5. Go to the C:\Program Files\Common Files\Intergraph directory using Explorer and note
which Intergraph products have files loaded in this location. Remove these products and
reload them.
Creation of "DisableUNCCheck"
This change should be made on all Windows 7 workstations and Windows 2008 Servers, where
the COMMAND PROCESSOR key does not already exist. The time at which you do this is not
critical (i.e.-if you have already loaded products you can still make this change).
1. Start the Registry Editor and locate the HKEY_LOCAL_MACHINE on the Local Machine
window.
2. Go to SOFTWARE > MICROSOFT to open the Microsoft folder.
3. Select EDIT > ADD KEY from the registry editor menu bar.
4. Enter COMMAND PROCESSOR for the Key Name. Note that it is a case-sensitive. Make
sure you leave a blank space between the two words.
5. Leave the CLASS field empty.
6. If you have done this correctly, you should see the COMMAND PROCESSOR folder under
the MICROSOFT folder.
7. Highlight the new COMMAND PROCESSOR key and from the Registry Editor menu bar
and select EDIT > ADD VALUE.
8. Enter DisableUNCCheck for the Value Name. Note that this is a single word and it is
case-sensitive.
9. Select REG_DWORD from the drop-down list for the Data Type and then click OK.
10. Select the Hex radio button in the DWORD Editor, and enter 1 (numeric one) in the Data
field.
The information that displays in the right side of the Registry Editor when you open the
COMMAND PROCESSOR folder should look like this:
DisableUNCCheck::REG_DWORD:0x1
Winreg Key
All paths defined within the PDS project are defined with a NODENAME and the actual PATH to
the file or directory on the node. There is a registry entry named HKEY_LOCAL_MACHINE >
System > CurrentControlSet > Services > LanManServer > Shares that contains a listing of the
Shares available on the server, and the local path to those shares. The mount code used by
PDS takes the NODENAME and PATH from the PDS project, accesses the registry key,
HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > LanManServer > Shares,
and attempts to resolve the NODENAME and PATH into a UNC path. Once successful, this
UNC path is passed back to PDS to access the needed files. This explains why in a new
installation of PDS, when the WINREG key of the server has not been modified, only users who
are administrators on the server can successfully use PDS.
In the past, it was recommended that you delete the WINREG key to resolve this problem. But,
by adding the path to the HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services >
LanManServer > Shares key to the AllowedPaths sub-key of the WINREG key, all users will
have access to the information needed to resolve the NODENAME and PATH into a UNC path
for use by PDS.
This modification is needed on all server nodes and should be done prior to project creation.
This modification is also needed on any client nodes that will use remote batch queues to pipe
PDS batch jobs to another machine for processing.
1. Include Path.
a. Open the registry on the server using regedt32.exe.
b. Find the key HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control >
SecurePipeServers > WINREG > AllowedPaths.
c. Select the AllowedPaths registry key.
This is a multi-line value.
d. Double click on the value to open the Multi-String Editor.
e. Enter System\CurrentControlSet\Services\LanManServer\Shares and then click OK.
f. All users should now be able to use PDS without requiring Administrative rights on the
server.
g. Reboot the server.
2. Delete the Winreg key.
a. Start the registry editor and again locate the HKEY_LOCAL_MACHINE on the Local
Machine window.
b. Locate the folder SYSTEM > CurrentControlSet > Control > SecurePipeServers >
Winreg.
c. Delete the winreg key by selecting it and pressing the Delete key on your keyboard.
d. Reboot the server.
The common errors associated with the WINREG key are listed below.
'Maximum Number of Shares Exceeded'
'Error 67, Error Mounting Remotename'
'Net address and directory could not be mounted verify the specified control files'
'Error in Number of Columns' when trying to create Equipment Models'
'No Matching Sharename for drive letter:\path'
Empty log files when routing PDS batch queues to a remote machine for processing.
UNC Path
You can also use a UNC path to locate the schema file.
1. Share the directory where the schemas file is located.
2. Open the Locate Schema File form on the client node.
3. Select Local as the protocol for the schema file location.
4. Enter: \\server\driveletter\dirname\schemas.
As an example: \\pdssmp1\c:\ris\schemas.
FTP Server is not required for this to work.
Some systems have not worked with the colon after the drive letter. In this case, use the
following syntax: \\pdssmp1\c\ris\schemas.
Locating the schemas file in this manner uses Windows Server 2008 licenses (as seen in
Control Panel > Licensing).
TCP\IP
1. Install and configure FTP Server on the server.
2. Locate the schemas file from a client node and specify TCP\IP as the protocol.
Registry Entries
Creation/Modification of "Common" key
This section covers PDS installation prerequisites for Windows-based computers.
During the PDS installation, do not install any of the products into a directory with a space
in the path. For example, by default Iplot will load into the "Program Files" directory. Change the
path to a directory without spaces, for example "d:\win32app\ingr\iplot".
Creation of DisableUNCCheck
This change should be made on all Windows 7 workstations and Windows 2008 Server nodes,
where the COMMAND PROCESSOR key does not already exist. The time at which you do this
is not critical (i.e.-if you have already loaded products you can still make this change).
1. Start the Registry Editor and locate the HKEY_LOCAL_MACHINE on Local Machine
window.
2. Go to SOFTWARE > MICROSOFT (open Microsoft folder).
3. Pick EDIT > ADD KEY from the registry editor menu bar.
4. Enter COMMAND PROCESSOR for the Key Name. Note that it is a case-sensitive and be
sure to leave a blank space between the two words.
5. Leave the CLASS field empty.
6. If you have done this correctly, you should see your Command Processor folder under the
Microsoft folder.
7. Highlight the new COMMAND PROCESSOR key and from the registry editor menu bar pick
EDIT > ADD VALUE.
8. Enter DisableUNCCheck for the Value Name. Note that this is a single word and it is
case-sensitive.
9. Pick REG_DWORD from the drop-down list for the Data Type and then click OK.
10. Pick the Hex radio button in the DWORD Editor, and enter 1 (numeric one) in the Data
field. The information that appears in the right-hand side of the registry editor when you
open the Command Processor folder should look like this:
294 PDS and Windows 2000
APPENDIX I PDS Project Setup
DisableUNCCheck::REG_DWORD:0x1
Winreg Key
All paths defined within the PDS project are defined with a NODENAME and the actual PATH to
the file or directory on the node. There is a registry entry named HKEY_LOCAL_MACHINE >
System > CurrentControlSet > Services > LanManServer > Shares that contains a listing of the
Shares available on the server, and the local path to those shares. The mount code utilized by
PDS takes the NODENAME and PATH from the PDS project, accesses the registry key
HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > LanManServer > Shares
and attempts to resolve the NODENAME and PATH into a UNC path. Once successful, this
UNC path is passed back to PDS to access the files needed. This explains why in a new
installation of PDS, when the WINREG key of the server has not been modified, only users who
are administrators on the Server can successfully use PDS.
In the past, we have recommended deleting the WINREG key to resolve this problem. But, by
adding the path to the HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services >
LanManServer > Shares key to the AllowedPaths sub-key of the WINREG key, all users will
have access to the information needed to resolve the NODENAME and PATH into a UNC path
for use by PDS.
This modification is needed on all server nodes and should be done prior to project creation.
This modification is also needed on any client nodes that will use remote batch queues to pipe
PDS batch jobs to another machine for processing.
Include Path
1. Open the registry on the server using regedt32.exe. Find the key HKEY_LOCAL_MACHINE
> System > CurrentControlSet > Control > SecurePipeServers > WINREG > AllowedPaths.
2. Select the AllowedPaths registry key.
This is a multi-line value.
3. Double click on the value. This will open the Multi-String Editor.
4. Add the following:
System\CurrentControlSet\Services\LanManServer\Shares
5. Click the OK button. All users should now be able to use PDS without requiring
Administrative rights on the server.
6. Reboot the server.
Use of TCP\IP
1. Install and configure FTP Server on the server.
2. Locate the Schema File from a client node and specify TCP\IP as the protocol.
Environment Variables
Windows 2000 creates default temp and tmp paths of %USERPROFILE%\Local
Settings%\temp for each user. You need to delete or modify the users default paths for
temp\tmp and create path names without spaces.
1. Right-click on My Computer.
2. Choose Properties > Advanced > Environment Variables.
3. Highlight the temp variable and press the delete button (or press the edit button and change
the path to c:\temp).
4. Highlight the tmp variable and press the delete button (or press the edit button and change
the path to c:\temp).
An alternative to setting each users environment variable on every Windows 2000
machine they log into is to create a Roaming User profile for each user and delete or set the
temp and tmp paths once.
In This Appendix
Commands Set in PDS.CMD......................................................... 301
System Environment Variables ..................................................... 305
PDS2D Environment Variables ..................................................... 307
FrameWorks Plus Environment Variables ..................................... 309
__END__
:endofperl
If you want to add environment variables to the PDS.CMD file, add them before the "$PD_Shell
= $ARGV[0];" line.
You MUST include an extra backslash for every backslash that is used in pathing
text in the pds.cmd file. For example, if the path you want is \\pdsserver\z\projfile, then you need
to define the path in the pds.cmd like this: \\\\pdsserver\\z\\projfile.
The following environment variables can be set in the pds.cmd file.
node
= the hostname of the project file server,
directory path
= the directory path containing the reference data file,
filespec.dat
= the name of the gridline reference data file.
For example,
$ENV{'ISOUSRREFDIM'} = 'pdsserv1:e:\proj1\project\fw_bldg_a.dat';
After this variable is set, the data in the file filespec.dat will be referenced as a result of
enabling Intergraph option 71 in the isometric options file. Note that this file will be used in
place of the file fw_projname.dat which is the gridline reference data file by default. When
utilizing this variable, the following rules will apply:
If the ISOUSRREFDIM variable is set and points to the proper location of a valid gridline
reference data file, this file will be used for placing gridline references on the isometric
drawing if Intergraph option 71 is turned on.
If the ISOUSRREFDIM variable is set improperly (for example, UNCpath or filespec are
mis-typed) and Intergraph option 71 is turned on, then no references will appear on the face
of the iso. That is, the result will be as if no gridline reference data file exists in the project
directory.
If the ISOUSRREFDIM variable is not set in the pds.cmd file but option 71 is turned on, then
the software will, by default, search for the file fw_projname.dat in the project directory. If it
exists and contains valid data, then the gridline reference dimensions will be extracted from
this file.
The variable also works for files extracted from the Graphic Commodities library, the Piping
Job Specifications library, and the Assembly library. When you are loading to the libraries
with the variable defined:
The filename convention is not limited to 11 characters. Single files can be loaded with
the length of the name limited by the size of the PDS key-in field.
The length of individual file names listed in a Load List file are not limited to the size of
the key-in field and can have additional characters.
$ENV{'PDS_PF_DISCIPLINE'} = 'discipline_indx_no'; or
$ENV{'PDS_PF_DISCIPLINE'} = 'discipline_name';
Used to specify the Pelican Forge discipline number for the project. This variable can be set
to either the discipline number or discipline name from pdtable_111. This variable can also
be set as a system environment variable.
$ENV{'PDME_LABEL_SEP_CHAR'} = '-';
Used to specify the concatenation character for multi-line PDME label text. The default
character is a dash '-'. There is not restriction on the length of characters that you can use.
$ENV{'PDS_USER_UMENUPREF'} = 'mymenufile.rsc';
Used to specify the user menu preference resource file.
$ENV{'PDS_USER_FONTRSC'} = 'myfonts.rsc';
Used to specify the font resource file.
$ENV{'PDS_USER_CONFIG'} = 'myconfig.cfg';
Used to specify the config resource file.
Used in conjunction with Frameworks Plus for foreign language compatibility. The
environment variable, PDS_FULL_ASCII, is intended to permit the use of full 8-bit ASCII
characters as required for many foreign language locales (using an OS meant for the locale
or using the English OS set for the locale). The problem was caused by character data
verification routines in a few places in PDS which do not permit the most significant bit
(MSB) to be set. It should be clarified that PDS is not fully certified in this mode, but is to be
verified by those requesting the fix.
DBA_NO_MSCATALOG=Y
DBA_MSLINK=model_index_no
Many of the PDS databases do not have a mscatalog table, and many of the PDS tables do
not have an mslink column. By default, DBAccess looks for this table in the database and
this column in the selected table and expects the mslink column to have unique integer
values. You can use the environment variables DBA_NO_MSCATALOG and DBA_MSLINK
to tell DBAccess to build its list of database tables from the database rather than from the
mscatalog table and to use a column other than mslink as the key column. For example, in
the PD schema, pdtable_113 has a column named model_index_no that has unique integer
values. By setting DBA_NO_MSCATALOG=Y and DBA_MSLINK=model_index_no, you can
use the DBAccess Edit Database function on this table and scroll through the available
records.
PDS_HVAC_SCHEMA_NAME=prj_[myhvacprojname]
To create labels for PE_HVAC models, the name of the PE_HVAC project database must
be prj_[pdsprojectname], where [pdsprojectname] is the exact name of the PDS project. If
you want to use a different PE_HVAC project schema name, you can set the
PDS_HVAC_SCHEMA_NAME to prj_[myphvprojname], where [myhvprojname] is the name
you want to use for the PE_HVAC project.
In Material Data Publisher (MDP), you can also use this variable to define the PEHVAC.prj
schema when the HVAC project schema name is different from the PDS project schema
name. As in the previous example, set the PDS_HVAC_SCHEMA_NAME to
prj_[hvacprojectname], where [hvacprojectname] is the name of the PEHVAC project
schema you want to use.
AREA_VOLUME_GRAPHICS_COLOR
AREA_VOLUME_GRAPHICS_WEIGHT
AREA_VOLUME_GRAPHICS_STYLE
AREA_VOLUME_GRAPHICS_LEVEL
These variables specify the symbology used to display area volume graphics in the Piping,
Equipment, Raceway, PE_HVAC, and FrameWorks Plus environments.
PDS_PF_DISCIPLINE=discipline_indx_no or
PDS_PF_DISCIPLINE=discipline_name
Used to specify the Pelican Forge discipline number for the project. This variable can be set
to either the discipline number or discipline name from pdtable_111. This variable can also
be set in the pds.cmd file. Setting this environment variable causes PDS to treat Support
Modeler more like a standard PDS discipline, including the ability to retrieve the .drv and
.env files for an archive.
PD_NO_COMPRESS=1
Stops the validation of the end-of-file marker in Microstation upon exit and the compression.
Set this environment variable in you are having performance problems on a WAN when
exiting a PDS model.
MDP_IMPLIED_USE_DESIGN_DB=1
Used to report NPD for gaskets and bolts from the Commodity Code labels in the short
description. If MDP_IMPLIED_USE_DESIGN is defined, the software retrieves component
NPD values from the Design database. If the variable is not defined, the software retrieves
the values from the Spec database. This variable also works when set in the Commands Set
in PDS.CMD (on page 301).
P2D_PLOT_SHOW_CMD=any value
Used so that when working with commands that submit plots (either of the plot commands,
print document or generate document), the command lines sent to the system to create the
plot will be output into the log file along with the rest of the log messages.
PDS_MENU_AUTOACTCUSTOM=any value
Sets the user's custom menu to be automatically activated when entering graphics.
P2D_EDTGRA_INIT=Directory path to a Perl script
P2D_EDTGRA_EXIT=Directory path to a Perl script
Used to specify the directory path of the Perl script used when entering or exiting a drawing.
(P2D_EDTGRA_INIT is entering). For more information on the EDTGRA environment
variables see page 304 of the PDS2D RDB Reference Guide Jan, 1998.
P2D_USER_EXTENSION=XXX
Related to the IDM standalone menu. This variable lets you define the extension of the
winmenu file in the project data you wish to use. If this variable is set, the menu used is
located at the project's pds2d\rdb\data directory and is expected to be named winmenu.XXX
where XXX is the value of this environment variable.
P2D_USER_WINMENU=location of winmenu file to use
If the IDM Standalone user wants to use a winmenu which is not located in the project, set
this variable to the UNC file spec of the file to use. The file must follow the syntax rules of
the winmenu file. If not set the menu used if the default winmenu file or the winmenu file
specified by P2D_USER_EXTENSION.
PDS_MENU = directory path for the saved customer MDL menu file
If not set, the NT software sets the menu to the pds2d\cfg\directory.
PDS_MENU_GRAPAL = directory location of graphic palettes
Points to directory of graphic palettes. If not set the system will default to the same location
as the PDS_MENU variable.
cfgdat.bat File
The following environment variables that affect the PDS2D modules are set in the cfgdat.bat file,
which is delivered in the win32app\ingr\pds2d\cfg\ directory.
PDS_USER_NO=integer value
Used by PDS2D for access control in conjunction with the acc_control file to determine
which users have what types of access on which tables. If not defined the user has full
access.
Source: PDS2D RDB Reference Guide, January 1998, page 269
P2D_INIT_QUEUES=any value
Initializes queue list once during setup instead of when the first command is called that
requires the list.
GRAPHICS_TOP=YES
DATABASE_TOP=YES
Used to tell NT to always place the forms on top of window. GRAPHICS_TOP is used in
graphics forms and DATABASE_TOP is used when working in database forms.
XFORMSCALE=INTEGER VALUE
YFORMSCALE=INTEGER VALUE
XFORMSCALE is the scaling you wish to apply to forms in the x-direction, and
YFORMSCALE is the scaling for the y-direction. These environment variables, if defined,
always override default scaling. The value is a percentage of the scaling. For example a
10% increase in size would be set as XFORMSCALE=1.1. The syntax states there are no
spaces on either side of the equal sign. The default form size is 1280x1024 but can be
different based on your hardware configuration.
Source: PDS2D RDB Administrator's Reference Guide, January 1998, page 355
P2D_USR_FRM_FONT=FONT NAME
Used to set a font other than Arial for the database windows.
PDS2D_VIEW_OPT=directory path of PostScript viewer executable
Used to choose a postscript viewer to view externally.
Source: PDS2D RDB Administrator's Reference Guide, January 1998, page 324
FTASKMENU=YES OR FTASKMENU=NO
Set to Yes to use the MicroMenu forms or set to No to use the MDL palettes. No is the
default.
Source: PDS2D RDB Administrator's Reference Guide, January 1998, page 473
FTASKMENU_X=pixel value where the menu palette will appear
If using the hybrid menu, the x coordinate of the upper left of the form will be displayed. If
value is greater than the resolution, the form appears at the bottom of the screen. If the
value is negative, the form appears at the top of the screen.
FTASKMENU_Y=pixel value where the menu palette will appear
If using the hybrid menu, the y coordinate of the upper left of the form will be displayed. If
value is greater than the resolution, the form appears at the bottom of the screen. If the
value is negative, the form appears at the top of the screen.
P2D_DBWIN_X=X coordinate value
Defines the x coordinate at which the database windows begin.
P2D_DBWIN_Y=Y coordinate value
Defines the y coordinate at which the database windows begin.
USE_3_BY_4=any value
Used to set the software to use the 3x4 window layout instead of the 2x3 window layout.
P2D_PLOT_QPR_OPTS="options"
Sets plotting options to be carried out at plot submission. For a detailed listing of the plotting
options see the 2D RDB Administrators Guide page 204 and the IPLOT User's Guide.
FORM_LIST_LEN=integer
Sets the forms to be cached. By default beginning with PDS 06.03.01.00 the forms will not
be cached. If user wishes forms to be cached the value is set to be an integer.
You can set environment variables in Start > Settings > Control Panel > System >
Advanced > Environment Variables; however, we do not recommend it. FrameWorks Plus
reads the config.dat file last when starting, and overwrites any duplicate environment variables
that were defined in your control panel. Having environment variables defined in both the control
panel and the config.dat file can cause confusion when trying to change variable settings.
You can use UNC (Universal Naming Convention) paths for directory locations. For example,
instead of mounting a server that contains your section tables, you can define the directory
using the syntax: FW_ESL_DIR= \\servername\sharename\esl\
FWBIN—Sets the location of the FrameWorks Plus bin directory.
FW_AUTO_COMPRESS—Specifies if the model database should be compressed
automatically when you exit the model. Set to 0 (zero) to not compress the model. Set to 1 to
compress the model.
Compressing a very large model can cause a pause during model exiting while the
model database is being compressed.
FW_BDR_DIR—Sets the location of drawing border files.
FW_DATA—Sets the location of the FrameWorks Plus data directory. This is useful when
you want to use different grade.dat and attributes.dat files for different projects.
FW_ESL_DIR—Sets the location of standard section libraries (aisc, cisc, and so forth).
FW_USER_ESL—Sets the location of user section libraries. You must put corresponding
cell libraries for arbitrary sections in this same location. We recommend that you define this
environment variable after creating a new project. This variable requires a UNC path name
so that the user section table works correctly when you run the Propagation command from
the PD-Shell Frameworks Plus dialog box.
FW_NMDGRPS—Defines the location of the .ngp file (the named groups file) to use. If not
defined here, the project .ngp file is used by default.
FW_PRODUCT—Sets the location of the main FrameWorks Plus directory. This variable
must be set to start FrameWorks Plus using the mdl load fwp MicroStation key-in and to
create models using the command-line key-in command cremod.
FW_PREFERENCE—Sets the full directory path and file name for the default preference
file. Use this environment variable to use a preference file other than the default fw.rsc or
fwm.rsc file. You can also set the default preference editor by using the File> Central
Preference Editor command.
FW_PROJDIR—Sets the location of the directory that contains the project.
FW_RSC_DIR—Specifies the directory path to FrameWorks Plus resource, or preference,
files.
FW_SEEDDIR—Sets the location of seed files used to create new models inside PD_Shell.
FW_SOLID_STROKE—Specifies the stroking tolerance factors for the maximum distance
between a solid's actual curve and the approximating vectors. The greater the number, the
less processing time that is required to display the solid or calculated the solid's
volume/surface. However, the curve representation, and any volume calculations, will not be
as precise. For example, a setting of 0.1 will cause faster processing, but the results will be
less precise than a setting of 0.001.
We recommend that you use a higher stroking tolerance setting until you are ready to
produce your final deliverables. Then you need to use a lower stroking tolerance setting for
these operations.
FW_SDNF_NUMOFSOLIDS_PER_INSTANCE—Specifies that the steel detailing neutral
file (SDNF) be imported in multiple stages. Defining this variable is necessary only if the
SDNF contains a large number of holes and solids.
DiameterToRoll_e—Defines the rolling process. Pipe sections less than or equal to this
dimension are hot rolled. Diameters greater than this value are rolled plate. This flag is
indicated in the MDP table 533, column 11. Used in imperial models.
DiameterToRoll_m—Defines the rolling process. Pipe sections less than or equal to this
dimension are hot rolled. Diameters greater than this value are rolled plate. This flag is
indicated in the MDP table 533, column 11. Used in metric models.
FW_MDP_CONTONERR—Continues with the next model if the MDP process encounters
any MDL aborts in the current model. To use the (USE) function, uncomment the flag
FW_MDP_CONTONERR = 1 in config.dat in the ..\fwplus\data folder.
E L
Environment Variables • 300 Loading and Configuring Software • 27
Environment Variables (Windows 7 / Server Loading Default Data into the Piping
2008) • 297 Reference Database • 103
Equipment Reference Data • 101 Location of RIS Schemas File • 300
Establishing Account Mapping • 53 Location of RIS Schemas File (Windows 7 /
Establishing Domain Users and Groups • 41 Server 2008) • 296
Location of schemas File • 49
F Location of the proj File • 41
Log Files Produced by PDS Batch Jobs •
File Systems • 27 179
Files Reside on a Windows Server • 56
Format of the queue_descript File • 288
FrameWorks Environment • 214 M
FrameWorks Plus and Material Data Model Creation for Other 3D Disciplines •
Publisher • 228 125
FrameWorks Plus and PD_Clash • 227 Modeling • 215
FrameWorks Plus and SmartPlant Review • Modifying Batch Queues for Redirected
225 Processing • 135
FrameWorks Plus Categories • 213 MSSQL Server 2005 • 281
FrameWorks Plus Environment Variables • MSSQL Server 2008 • 269
309 My Computer versus Network Printer
FrameWorks Plus Extended Labels Dialog Server • 131
Box • 226
Full versus Incremental Backups • 158 N
Notes: • 187
G NTBACKUP or CPIO Backup of Database
General Processing Rules for Files • 156
Printers/Plotters • 289 NTBACKUP or CPIO Backup of Project
Generate ASCII File • 219 Data • 155
H O
Hardware Versus Software RAID Operating Systems and Related
Implementations • 166 Components • 27
How RIS Communicates with the Database Oracle 10.2.0.5 Client Installation on
• 37 Windows 7 • 267
Oracle 10.2g • 249
I Oracle 10g • 264
Oracle 11g • 229
I/O Subsystem Components • 159
Installing and Configuring SmartPlant
License Manager • 59 P
Installing MSSQL 2005 • 281 PD_Clash • 184
Installing MSSQL 2008 • 269 PD_Data • 185
Interactive Jobs Which Print/Plot • 291 PD_Design • 183
Intergraph SmartPlant License Manager • PD_Draw • 183
199 PD_Model • 183
Intergraph Supported RAID Levels • 161 PD_Project • 185
Introduction • 11 PD_Report • 184
ISMP 5* or 6* RAID Subsystem Description PD_Review • 184
• 166 PDS and FrameWorks Plus • 199
PDS and Windows • 293
S
Scheduled Model Propagation • 217
Script to Create Project Directories on
Windows • 171
Scripts to Create Project Directories • 171
Server Hardware and Software
Requirements • 15