rdv_context_download

Evaluates or reevaluates a structure context object (SCO) and writes Design Context information and user attributes into a PLM XML or AJT (BOMWriter) file. The contents of the SCO can represent the entire product or a subassembly. The information written into the PLM XML file depends on the specified input transfer mode. The output file is used to facilitate the sharing of data between users, programs, or sites using Multi-Site Collaboration. You can download this file to the operating system or import it into Teamcenter as a dataset. This utility can process a single SCO, a list of SCOs, or all SCOs in a specified folder. If you process a list or folder of SCOs, a separate PLM XML file is generated for each SCO. It can also accept a saved query as input. If you use Multi-Site Collaboration, the validate_and_replicate_assembly utility can consume the PLM XML files created by this utility and replicate them across sites. If the output PLM XML file is in BOMWriter format, you can launch it in Lifecycle Visualization. Syntax rdv_context_download [-item_id=item-ID] | -key=[keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN]] [-rev_id=revision-ID] [-variant_rule_name=variant-rule-name] [-revision_rule_name=revision-rule-name] [-engg_change_id=engineering-change-ID | -engg_change-key=[keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN] [-folder_name=folder-name] [-process_name=process-name] [-zone_name=zone-name] [-zone_type=BOX | PLANE] [-operator=BOX(Within | Outside | Interferes) | Plane(Above | Below | Intersects)] [-sco_download=yes | true | YES | TRUE] [-user_attribute=user-attribute] [-sco_name(s)=StructureContextObjectName(s) | -saved_query_name=Teamcenter-saved-query-name | -sco_folder=Teamcenter-folder-name] [-transfer_mode=transfer-mode-name] [-output_format=BOM_writer FormatAJT | PLMXML | PIEPIE-PLMXML] [-file-name=file-name-without-extension] [-absolute_path=path-of-file-to-be-stored-without-extension] [-h] Arguments -item_id Specifies the item ID. -key Specifies the key of the item. Use the following format: Copy [keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN] To find the key of an object, use the get_key_string utility. For more information, see Introduction to multifield keys in BMIDE for Data Model Design. -rev_id Specifies the revision ID. -variant_rule_name Specifies the name of the variant rule configuring the structure. -revision_rule_name Specifies the name of the revision rule configuring the structure, which defaults according to the TC_config_rule_name preference. -engg_change_id Specifies the engineering change item ID. The utility configures an RDV context based on change attachments and the latest engineering change revision. -engg_change_key Specifies the key of the engineering change item. The utility configures an RDV context based on change attachments and the latest engineering change revision. To find the key of an object, use the get_key_string utility. For more information, see Introduction to multifield keys in BMIDE for Data Model Design. -folder_name Configures a context based on attachments of the folder/envelope/engineering-change-revision-name. The attachments include the following: One product item revision One or more component item IDs Optional revision rule, overwrites the -r argument Optional variant rule, overwrites the -v argument Note Search results are affected by the following preferences: TC_config_rule_name WebDesignContextDefaultSearchDistance PortalDesignContextMaxMatchingObjects PortalDesignContextMaxMatchingBOMLines For more information, see the Teamcenter Environment Variables. -process_name Specifies the name of the workflow processes that have not yet completed. -zone_name Specifies the name of the zone. When both the -zone_name and -zone_type arguments are specified, the utility performs a search according to the preference settings. -zone_type Specifies the type of the zone, either BOX or PLANE. The -zone_name argument must be used in conjunction with the -zone_type argument. -operator Specifies the zone type operator. Valid values for the BOX zone type are Within, Outside, or Interferes; the default value is Within. Valid values for the PLANE zone type are Above, Below, and Intersects; the default value is Intersects. The -zone_name and -zone_type arguments must be specified in conjunction with the -operator argument. Note This utility performs a proximity search if the -zone_name argument is not specified and performs a name zone search if the -zone_type argument is not specified. -sco_download Specifies if the SCO should be downloaded. -user_attribute Specify user attributes in the same format described for the bomwriter utility. -sco_name Specifies the name of the structure context object from which a PLM XML is generated. You can specify more than one SCO as a comma-separated list, for example: SCO1,SCO2,SCO3 -saved_query_name Specifies the name of a Teamcenter saved query that retrieves a set of SCOs to process for given search criteria. -sco_folder Specifies the name of a Teamcenter folder that contains a set of SCOs to process. -transfer_mode Specifies the name of a transfer mode to generate the PLM XML file. If no mode is specified, the SCOs are evaluated with the default transfer mode. -output_format Specifies the output file format, either BOM writer PLM XML or AJT, or PIE PLM XML. The default format is BOM writer PLM XML. -file_name Specifies the name of the output file to which the data is output. Provide the file name without an extension. -absolute_path Specifies the full path of the AJT or PLM XML file where the data is to be stored. If not specified, the utility looks at the value of the RDVContextDownloadDirectory preference. Otherwise, the current working directory is used as the default path. Note The absolute_path must be specified without an extension. For example, /users/x_user/tempfile for Linux or c:\temp\tempfile for Windows. -h Displays help for this utility. Environment As specified in Setting up a Teamcenter command-line environment and the RDV_debug environment variable. If this variable is set, the Teamcenter syslog file contains additional debugging information. Files As specified in Log files produced by Teamcenter. Restrictions You must have the necessary create or modify privileges to successfully run this utility. If you do not have the appropriate privileges, data is not imported and an error message is written to the log file. Examples The following example creates a PLM XML file called TL109375 and uses the TC_config_rule_name preference to determine the revision rule: Copy $TC_ROOT/bin/rdv_context_download -item_id=TL109375 -rev_id=004 The following example creates a PLM XML file named TL109375, but enforces revision configuration using the Beta or less w/pdi revision rule: Copy $TC_ROOT/bin/rdv_context_download -item_id=TL109375 -rev_id=004 -r="Beta or less w/pdi" The following example logs in as the tcdba user and creates a PLM XML file named 11_21_sco1_a:: Copy $TC_ROOT/bin/rdv_context_download -sco_name=11_21_sco1_a -u=tcdba -p=pw_tcdba -g=dba The following example prompts the user for autologin and creates a PLM XML file named assy_ajt_file: Copy $TC_ROOT/bin/rdv_context_download -folder=test_assy -filename=assy_ajt_file The following code shows the PLM XML file created by this example. Sample PLM XML file Copy &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& . . . -1 0 0 0 0 -1 0 0 0 0 1 0 -0.00735251986233691 -1.48797584060841 -0.160362350011722 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 &?>&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& The following example prompts the user for autologin and creates an ASCII JT assembly file named assy_ajt_file: Copy $TC_ROOT/bin/rdv_context_download -folder=assy_folder -filename=assy_ajt_file -bom_writer_format=AJT The following code sample shows the sample AJT file created in this example. Sample AJT file Copy &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

DirectModel ASCII file - version 1.0

Written by BOMWriterFormatAJT Teamcenter

Wednesday, 01/21/2004 05:56:39PM 0 ASM "AC7192-Product Book 2.asm;0;0:" ATTR Type="STRING" Key="DB_PART_NO" Value="AC7192" ATTR Type="STRING" Key="DB_PART_REV" Value="A" ATTR Type="STRING" Key="__PLM_ITEMREV_UID" Value="Q1_o4OCyn6c4PB" ATTR Type="STRING" Key="DB_OCC_UID" Value="AAAAAAAAAAAAAA" 1 ASM "0728-045.asm;1885772752;-1684155971:" ATTR Type="STRING" Key="DB_PART_NO" Value="0728-045" ATTR Type="STRING" Key="DB_PART_REV" Value="A" ATTR Type="STRING" Key="__PLM_ITEMREV_UID" Value="QX9o4OCyn6c4PB" ATTR Type="STRING" Key="DB_OCC_UID" Value="0z$o4OCyn6c4PB" Matrix [ 1.000 0.000 0.000 0.000 ] [ 0.000 0.998 -0.067 0.000 ] [ 0.000 0.067 0.998 0.000 ] [ -5.646 0.375 -0.150 1.000 ] 2 PRT "1602-023.prt;-1968592985;273560760:" 2 PRT "1602-023.prt;-1968592985;-1738192227:" 2 PRT "1602-017.prt;1215126988;-365534238:" 2 PRT "1602-016.prt;-935130874;-619873730:" 2 PRT "1602-016.prt;-935130874;-650811331:" 1 PRT "H02976.prt;-1812813847;-640191115:" 1 PRT "E6895.prt;-1559507236;-2122085832:" 1 PRT "H02592.prt;1415580139;939946980:" 1 PRT "E6820.prt;-963798381;458164065:" 1 PRT "ERG056.prt;-1508967178;210332543:" 1 PRT "1606-177.prt;80810929;-396904688:"

end

&?>&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Related Topics Structure Management on Rich Client ─ Usage