create_or_update_bbox_and_tso

This utility performs the following tasks: Creates, updates or deletes bounding box data from NX (UGMASTER) and JT (DirectModel) datasets. Creates or updates TruShape data (.tso files) for JT files. In a multisite environment, this utility creates the .tso files only for datasets that belong to the owning site. It does not create the .tso files for replica datasets. Generates reports of: NX or JT datasets not having a bounding box object. NX datasets not having a UGPartBBox form. JT datasets not having a .tso file. Using this report, the same utility can generate Dispatcher requests so the translation (conversion to the bounding box and TSO) occurs on the dedicated Dispatcher machine. Syntax create_or_update_bbox_and_tso [-u=user-id -p=password | -pf=password-file -g=group] -mode=usermode -translation_mode=operatingmode -generate_ets_request -delete_all_bboxes -dataset=dataset_uids -dataset_list=filename [-objects=object_list-object_list=filename] [-scope=ALL | PRODUCT] [-product=product_item_id -output_dir=dirname [-h] Arguments -u Specifies the user ID. This is a user with Teamcenter administration privileges. Note If Security Services single sign-on (SSO) is enabled for your server, the -u and -p arguments are authenticated externally through SSO rather than being authenticated against the Teamcenter database. If you do not supply these arguments, the utility attempts to join an existing SSO session. If no session is found, you are prompted to enter a user ID and password. -p Specifies the password. This argument is mutually exclusive with the -pf argument. -pf Specifies the password file. For more information about managing password files, see Manage password files. This argument is mutually exclusive with the -p argument. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -mode Specifies one of the following modes: query Generates a report of NX or JT datasets that require updates to the bounding boxes, TSO files (JT files only), or missing UGPartBBox forms (NX datasets only). process Creates or updates bounding boxes, TSO files (for JT datasets only) or both for a set of NX or JT datasets. query+process Generates a report of NX or JT datasets that require updates to the bounding boxes or TSO files (JT files only). It then creates or updates bounding boxes or TSO files (for JT datasets only) for the identified datasets. delete Deletes the specified datasets. -translation_mode Specifies one of the following translation modes: JTTOBBOX Creates or updates the bounding boxes in JT datasets. JTTOTSO Creates or updates the TSO files in JT datasets. JTTOBBOX+JTTOTSO Creates or updates the bounding boxes and TSO files in JT datasets. NXBBOXTOBBOX Creates or updates the bounding boxes in NX datasets. processAll Use with the NXBBOXTOBBOX mode to force creation of bounding boxes for all NX datasets. NXBBOXFORM Creates a report listing all NX datasets for which the associated UGPART-BBOX form is not available. -generate_ets_request Specify this argument when you specify query mode and are working only with JT datasets. Creates a Dispatcher request in the database for each JT dataset that needs updates to bounding boxes or TSO files. Before you use this argument, ensure the Dispatcher translation service is configured and running, as described in Using Dispatcher. -delete_all_bboxes Deletes all the bounding boxes, multibounding boxes and relations between them from the database. (It does not delete TruShape data and you should re-create the TSO files if necessary.) -dataset Specifies one or more dataset UIDs as a string separated with commas, in the format: Copy ds1, ds2, ....., dsn This argument is valid only if you specify process mode. -dataset_list Specifies the absolute path to an input file that contains a list of dataset UIDs to process. Each dataset must appear on a new line of this file. This argument is valid only if you specify process mode. -objects Specifies a comma-separated list of UIDs of primary objects whose bounding boxes you want to delete, in the format ob1,ob2,...,obn. This argument should be used only in delete mode. -object_list Specifies the fully qualified path name of a file containing a list of UIDs of primary objects whose bounding boxes you want to delete. Each UID should appear on a new line. This argument should be used only in delete mode. -scope Limits the scope of queries to the accountability table. Specify either ALL (consider all products in the accountability table) or PRODUCT (consider items listed under the product specified by the -product argument). -product Specifies the ID of a product item that is listed in the accountability table. -output-dir Specifies the absolute path to the directory where the report file is generated. If no path is specified, the report is generated in ./output_dir. This argument is valid only if you specify query mode. -h Displays help for this utility. Environment As specified in Setting up a Teamcenter command-line environment. Files As specified in Log files produced by Teamcenter. Restrictions None. Examples Create bounding box and TruShape data for all the JT datasets in the database. You can do this in one of two ways: Create a report file of the datasets that do not have bounding box information as a log file. Process the log file and create the missing bounding box information on the dataset. This method is suitable if you have a large quantity of data to process as you can split the report log file can be split into multiple files, allowing the utility to process fewer datasets in each execution: Copy create_or_update_bbox_and_tso -u=user> -p=password> -g=group> -mode=query -translation_mode=JTTOBBOX+JTTOTSO -output_dir=c:\temp

create_or_update_bbox_and_tso - u=user> -p=password> -g=group> -mode=process -translation_mode=JTTOBBOX+JTTOTSO -dataset_list=c:\temp\file generated by above command> Query and process the datasets with a single command: Copy create_or_update_bbox_and_tso -u= -p= -g= -mode=query+process -translation_mode=JTTOBBOX+JTTOTSO Create bounding boxes for all NX datasets in the database. You can do this in one of two ways: Create a report file of the datasets that do not have bounding box information as a log file. Process the log file and create the missing bounding box information on the dataset. This method is suitable if you have a large quantity of data to process as you can split the report log file can be split into multiple files, allowing the utility to process fewer datasets in each execution: Copy create_or_update_bbox_and_tso -u=user> -p=password> -g=group> -mode=query -translation_mode=NXBBOXTOBBOX -output_dir=c:\temp

create_or_update_bbox_and_tso -u=user> -p=password> -g=group> -mode=process -translation_mode=NXBBOXTOBBOX -dataset_list=c:\temp\file generated by above command> Query and process the datasets with a single command: Copy create_or_update_bbox_and_tso -u= -p= -g= -mode=query+process -translation_mode=NXBBOXTOBBOX Create a report file of all NX datasets in a log file that do not have an associated UGPART-BBOX form: Copy create_or_update_bbox_and_tso -u= -p= -g= -mode=query -translation_mode=NXBBOXTOBBOX -output_dir=c:\temp\report.txt Delete all bounding box and TruShape data associated with a specified item revision: Copy create_or_update_bbox_and_tso -u= -p= -g= -mode=delete -dataset=uid_of_item_rev1 or absocc1[,uid_of_item_rev2 or absocc2, …] Delete all bounding box and TruShape data associated with the parts specified in an input file: Copy create_or_update_bbox_and_tso -u= -p= -g= -mode=delete -dataset_list= Delete all bounding box data in the database: Copy create_or_update_bbox_and_tso -u= -p= -g= -delete_all_bboxes Related Topics Structure Management on Rich Client ─ Usage