System Control Overview | Statement List

NX Manager

This section describes the GRIP commands that encode/decode NX Manager part file names. These calls are not available when using NX without NX Manager.

Encoding and Decoding Part File Names

When running GRIP programs in NX Manager mode, you must specify the file name of a part in a different format from when you are running a GRIP program in standard NX mode.

• NX reserves the right to change the internal structure of the encoded format at any time. For this reason, the encoded syntax is not explained here because it is not needed. A GRIP programmer only needs to know how to interface with NX Manager's encoded file format.

Encode Format

NX Manager recognizes part file names in a special encoded string format, rather than the "<part number>.prt" form in standard NX. It is therefore necessary to encode the file name of a part into this special format before attempting to use it in any GRIP program running in NX Manager mode that takes a part file name as input.

At a minimum, you always need an MFK and part-revision. The possible strings that you may use are:

• Multifield key (Teamcenter fnd0PartIdentifier property on Item object)

• Part revision (Teamcenter item revision Id)

For a UGPART dataset, the following is also required:

• Part file type name (Teamcenter relationship - specification or manifestation)

• Part file name (Teamcenter dataset name)

Decoded Format

Once you have an encoded string of the part file name, you may decode it at a later stage to obtain the constituent elements (MFK, part revision, part file type, and part file name) using the GRIP UGMGRD.

The decoded format is simply a part file name broken down into its constituent elements (MFK, part revision, part file type, and part file name).

• For more information about file formats, you may want to consult the applicable section in the Open C and C++ API Reference Guide.