12 ISODRAFT Transfer File: 12.1 Preprocessing and Postprocessing Commands

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 1

12 ISODRAFT Transfer File

Before ISODRAFT produces an isometric plot, it processes data from the DESIGN and
Catalogue databases and creates an intermediate data file (IDF). This transfer file is
produced as a binary file, which is processed by ISODRAW to create the plot file: you can,
however, specify that ISODRAFT will produce an ASCII copy by using the command
TRANsferfile filename
where filename is the name of a file in the operating system directory.
Production of the ASCII transfer file is cancelled by the command
TRANsferfilename OFF
An ASCII transfer file produced in this way can be processed by the
PROCESS TRANSFERFILE filename
command to produce a plot file.
The transfer file can provide a useful means for sending information to AVEVA Solutions Ltd
for assistance in resolving problems associated with Product User Reports (PURs).
Note: The default transfer file, /trans, will be overwritten whenever a DETAIL or CHECK
command is given. Specify a new file name if you want to keep the data.
Note: That transfer files produced by versions of ISODRAFT before Version 10.3 are in
binary format only, and cannot be processed by the PROCESS TRANSFERFILE
command.
12.1 Preprocessing and Postprocessing Commands
You can execute system commands (for customised reporting, etc.) during the transfer file
processing sequences:
• Preprocessing commands are system commands which are executed after the IDF
has been written and before ISODRAW has been invoked.
• Postprocessing commands are system commands which are executed after
ISODRAW has finished and before control is returned to ISODRAFT.
The PREPROCESS and POSTPROCESS commands each let you define up to five
numbered command strings for this purpose. The syntax is:
PREPROCESS integer1 'command string1' integer2 'command string2' ...
POSTPROCESS integer1 'command string1' integer2 'command string2' ...

3 Cataloguing Requirements
Most of the reference material needed by ISODRAFT is stored in the Catalogue database.
Such data includes:
• Component item codes and descriptions, to be printed on material lists
• A definition of the two-dimensional symbol (SKEY) for each type of component
• A definition of any specific types of end connections to be associated with particular
components
• The bolting requirements of all flanged components
ISODRAFT cannot function correctly unless the Catalogue is properly set up. This
information supplements the Catalogues and Specifications Reference Manual.
This chapter describes how the data, except for bolting information, is stored in the
Catalogue. How to set up the Bolting part of the Catalogue is described in Bolting.
3.1 Component Descriptions
The texts used to describe components in the material list are stored in the Catalogue DB as
text elements. The relevant part of the DB’s hierarchy is:
Figure 3:1. Storing text elements in the DB
where: ADTE to SDTE are detail text (DTEXT) elements and AMTE to SMTE are material
text (MTEXT) elements.

You might also like