Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »


 
SYNTAX:
 
xpxReadStepFile(STEPfile , logFile , sumFile     : STRING;
                 repositoryName , headerModelName : STRING;
                 modelName , schemaName           : STRING;
                 shortNamesFile                   : STRING;
                 cacheSize , options              : INTEGER;
                 VAR sdaiError                    : INTEGER)
                 status                           : INTEGER;
 
 
The xpxReadStepFile function is used to create a new model and populate the model with data from the specified STEP Physical File. The arguments in the xpxReadStepFile have the following meaning:
STEPfile:
The name of the actual STEP Physical File to read into the database.
logFile:
The name of the file where logging from the xpxReadStepFile function will be recorded in case logging is enabled. This argument can be set to an empty string or indeterminate (question) when no logging should be performed.
sumFile:
Name of the file where a summary of the STEP file read operation will be recorded. This argument can be set to an empty string or indeterminate (question) when no summary is wanted.
repositoryName:
Name of the repository where the new created model will be located.
headerModelName:
A STEP Physical File consist of a Header Section and a Data Section. If a sdai_model of the Header Section should be created and populated during the xpxReadStepFile operation, then the headerModelName specifies the name of this sdai_model in the database. This model will be located in the repository specified by the repositoryName argument. This argument can be set to an empty string or indeterminate (question) when no creation and population of a STEP Physical File Header Section model is wanted.
modelName:
The name of the sdai_model that will be created and populated as a result of the xpxReadStepFile function.
schemaName
The name of the Express schema that describes the Data Section of a STEP Physical File is found in the Header Section of the same STEP Physical File. This schema must exist as a dictionary model in the database before the xpxReadStepFile function can be performed successfully. If the STEP file should be read using an Express schema with another name than specified in the Header Section of the actual STEP file, the argument schemaName is used to specify the name of the Express schema to be used as the underlying schema for the created and populated sdai_model. A dictionary model of this Express schema must exist in the database if the xpxReadStepFile operation should be executed successfully. The argument schemaName can be specified as an empty string or as indeterminate if the schema specified in the Header Section of the actual STEP file should be used.
shortNamesFile:
The name of a file that contains short entity names of the actual schema that defines the data on the STEP file to be read. A STEP file can be written using the entity names specified in the Express schema that defines the sdai model that is mapped to the STEP file, or a STEP file can be written using short entity names. In case the actual STEP file is written using the short entity names, the shortNamesFile argument must specify a file that contains the mapping from short entity names to the entity names defined in the underlying Express schema of the actual sdai model.
For information on the format of the file in argument <short names file>, see Short names in the EDMsupervisor User Guide.
 
cacheSize:
This argument can be used to define the size of the cache in the EDMpart21Handler to influence the performance of the xpxReadStepFile operation. Normally the default value is used. The default value is used when the argument is set to zero.
options:
The options are equivalent to the options used in the EDMinterface function edmiReadStepFile except for the XPX prefix.
sdaiError:
If the xpxReadStepFile operation is terminated due to errors in accessing the database, the argument sdaiError will receive the actual sdaiErrorCode causing the termination of the xpxReadStepFile operation.
This function is equivalent to the EDMinterface function edmiReadStepFile

  • No labels