Search

Interim Solution for Unresolved PlantSpace P&ID Component Tag Issues

Support

<< Return to Index
Subject: Interim Solution for Unresolved PlantSpace P&ID Component Tag Issues
Product: PlantSpace P&ID V2.1.0.4
Operating System: Windows® 95, Windows NT®
Document Number: 7126

Software Requirements: MicroStation Schematics v02.01.01.19 and earlier, MicroStation SE v05.07.01.14 and earlier.

This bulletin describes an interim solution for circumventing known, yet unresolved issues with PlantSpace P&ID component tags. The specific issues include:

  • Component tags lose association with their definitions under yet unknown situations. Though it is suspected the issue is related to editing/updating existing tag definitions within a drawing, neither Bentley (nor those clients who have reported the issue) have been able to reproduce it.

  • The user data associated with component tags becomes corrupted under certain processing scenarios. The issue appears to occur when processing a drawing after the tags contained in it have been updated either via the jttag updateobj command or manually edited. NOTE: The source of the issue has been uncovered. A new release of MicroStation will be forthcoming. No specific date has been set at this time.

In both cases, the issues manifest themselves as the drawing is being processed. Typically, a software exception is encountered in the early stages of processing a drawing.

To assist in reproducing the first issue and until fixes can be provided for both, Bentley's interim solution is to provide monitoring and repair utilities for detecting and repairing the tag corruption resulting from these issues. These utilities are included in the jtagquery.ma application which is available from Web Downloads in the SELECT Enhancements area under the title "PlantSpace P&ID Tag Monitor and Repair Utility".

The application can be loaded automatically from the delivered and/or modified version of the PlantSpace P&ID user configuration file (e.g., pspideng.ucf). This can be done by replacing the MS_DGNAPPS = pspid line with MS_DGNAPPS = jtagquery followed by MS_DGNAPPS > pspid. The commands included in the application are listed and briefly described below:

  • The JTAGMONITOR command checks for and notifies the user when a tag becomes corrupted (via outputting messages to the standard MicroStation text window). The utility should be run (in the background) while creating, editing or processing drawings. The command is automatically started when the jtagquery application is loaded. The parameters associated with the command follow:

    START Initiates the monitoring function.
    STOP Terminates the monitoring function.
    VERBOSE Directs the command to output detailed messages describing the issue(s) detected.
    BRIEF Directs the command to output brief messages describing the issue(s) detected.

  • The JTAGVERIFY command verifies the integrity of all tags in an existing drawing. The command outputs results to the standard MicroStation text window. This command should be run prior to processing a drawing. If issues are encountered, other commands (described below) are provided for repairing the file prior to processing. The parameters associated with the command follow:

    VERBOSE Directs the command to output detailed messages describing the issue(s) detected.
    SSET Directs the command to place all corrupted tags in a MicroStation working set.
    SSET_VERBOSE Combines the functionality provided when the above two options are selected.
  • The JTAGQUERY command outputs information about a selected element tag. The command is provided to allow one to interrogate a specific tag. No parameters are associated with this command.

  • The STRIPTAGOBJID command clears/removes the user data associated with all tags in a drawing. This command should be run whenever the JTAGVERIFY command indicates that corrupted tags exist in a file. NOTE: PlantSpace P&ID creates an intelligent object representation for each graphics symbol and tag when processing a drawing. The unique ID of each object created is stored with the graphics symbol and tag to which it belongs as user data. There is only one parameter associated with the command--the name of the drawing to be processed. If not specified, the active design file is processed.

  • The JTTAG DELETE ORPHAN command deletes all orphan tags from the active design file. Though not common, orphan tags have been detected/reported by the verification utility in some drawings. Typically, orphan tags are created when a cell with associated tags is dropped. Since PlantSpace P&ID ignores orphan tags during processing, their presence will not cause any problems. However, the verification utility will continue reporting their presence when run.

  • The REPAIRTAGDEF command repairs tags that have lost association with their original definitions. The command relies on the user to provide the information to re-associate the tag instances with their definitions. NOTE: Currently, the command must run on each design file individually. By default, the command ignores tags that have no value(s) assigned. However, to process these tags, one can use the NULLS parameter, described here.

    NULLS Directs the command to operate on tags that have no value(s) assigned.

    The REPAIRTAGDEF command should be run twice, once without the NULLS parameter and a second time with the NULLS parameter. This makes it easier to determine what tag instances go with what definitions.

After utilizing the PlantSpace P&ID Tag Monitor and Repair Utility, there may be a need to clear the tags previously marked as deleted through EdG. This is the only way to remove these corrupted tags from the design file. Below are the recommended steps to accomplish this.

  1. set search/all
  2. set verify/all
  3. summary whole (this will list all the component classes on the drawing both active and deleted)
  4. set search/type=37/status=delete (this selects the tags that are marked as deleted).
  5. remove whole (this will remove 1/2 of the particular items nominated in the search statement, in this case tags. This command will need to be repeated until all the items have been removed.)
  6. summary whole (this step is optional to see if all the tags are now gone)
  7. exit

In the event the monitoring utility detects that a tag instance has lost its association with its definition, the user should immediately report the issue to Bentley support and provide enough information to allow them to reproduce the issue.

7126

How useful was this page?
less
  more
Suggest new content or let us know how we can improve this content (optional):

<< E-mail this page