i was wondering why the components dont pick up the spec if I delete a spec and then create a new one with the same name....
1. deleted a pipe spec and created a new one with the same name.....came to design and some most of the components lost the specref.....the only thing i cahnged in the spec was the Catrefs for some components and also added two cloumns in the headers
2. Deleted a insulation spec and then created one with the same name....all components, branches and pipes lost the ISpec ref ....why wat did i do wrong...
Cardinal rule #1 in Catalog/Spec - Never delete anything in catalog/Spec. In design cats/spec is carried by reference # and not by the name.
So 2" elbo in design with spref /A/2.0Elbo is actually storing the =1234/5678 internally in design. Although it shows the name in spref, PDMS actually use the ref# to pointing back to spco and then catref. There is a nice diagram in the PDMS manual.
So if you must delete a spec(do not do that! that is why limbo is there for) or catalog for fun. Make sure you record their occurance in design (Q desgeo, Q geodep), and run it back in as a macro to reset it after your spec is changed (assuming you are keeping the same spco/catref naming convention).
Do you know you can remove a spec? That will put it to the limbo location and then if you run the same spec macro it will bring it back to life again. Design will not show dashed lines. Try it.
In case you need to get back all the items that you succeeded to delete, it is possible to backtrack the catalogue database(unless you have done a merge of the database).
All later changes will be lost by backtracking, but you will be able to get the database back to an earlier state. Not sure if this is requierd in your case, but I thought I should mention it.
If the catalogue database name is MASTER/PIPECATA it is possible to do as follows.
In admin:
Q SESSIONS LAST 10 MASTER/PIPECATA
This will give a list of the last 10 saveworks done for the database.
Locate the session number where you did the mistake(lets assume it is: Session 1234) that was saved.
BACKTRACK MASTER/PIPECATA TO SESSION 1233
This will bring the database state back to the session before the mistake was done. Note that this will also remove all newer changes done to the databse as well, and there is no way to get them back after you have done a backtrack.
tx guyz for the lovely tips...as always Tback u rule!....fortunately not much have been done in design...we just started the project a few days back...so it wont be a BIG prob...but im still not very clear abt the (Q desgeo, Q geodep) stuff mentioned by De...can you please explain that in detail...haven't heard or used this before
and De...if am not wrong...u mean to say if i REMOVE the spec rather than delete and then bring in the new spec with same name and spco, it should be ok ??...correct me if am wrong
You can use the attributes to find out if the catalogue component has been used in design of the current project. You can query these attributes when you are in the design module.
Jump to a SPCO in teh spec (when you are still in the design module), and write:
Q DESGEO
This will list all pipe components where the selected spco has been used in the current project.
What De is pointing out is that you should NEVER delete any spec components unless you are 100% sure that they have never been used in any project. By removing the spec, all SPCO elements are moved to the limbospec, and the users will still see the components in design. The users cannot select anything from the limbospec, so all new components are selected from the ordinary specs.
the reason why i deleted the spec was....i wanted to change some headers in the spec....e.g. added ANGL and RADi for Elbows etc...now the question is...if in future i have to do such a change for an existing spec...wats the best way u doing it....coz as per my knowledege we cannot edit the headers in an existing spec..this can only be achieved by deleting the section or spec and creating a new one...
The maximum number of entries in a heading line (that is, the maximum number of columns in the table) is 20.
NOTE: The number of columns in an existing Specification cannot be changed, so it is important that you choose the headings carefully when you create a new Specification.
The heading line, which defines the column headings for the rest of the table, contains four distinct sorts of information:
• TYPE is the generic type (GTYPE) of the component represented by an SPCOM
• NAME is the unique identifier for each SPCOM
• Selector Questions define the SELEC choices, which will be used to choose an appropriate SPCOM for a given design, purpose (e.g. STYPE, ANGLE etc.)
• Reference Pointers link each SPCOM to the corresponding definitions in the other parts of the Catalogue (e.g. CATREF points to a COMP, DETAIL points to a DTEXT, and so on)
> To define a heading, use the command syntax
Heading
TYpe NAme Questions Reference Pointers
Note that the command is entered on two lines (i.e. you must press RETURN after the command HEADING, as well as after the last entry in the second heading line).
[FONT="Arial Black"]Typicals[/FONT] Flange
[FONT="Fixedsys"]HEADING
NAME TYPE PBORO ANGL SHOP CATREF DETAIL MATXT CMPREF BLTREF
DEFAULTS
— — — BW =[/FONT]
[FONT="Comic Sans MS"]SPECIFICATION COMPONENT SELECTORS DESCRIPTION
Pointers, which are attributes of SPCOM elements, are set individually for each line in a Specification table. There are very few constraints on the SELEC questions, and the order in which you list them, when defining SPECS for piping components. The following headings should meet most of your requirements:
PBor integer
Specifies the bore of p-point integer. For multiway components (such as a Tee), more than one PBORE SELEC may be specified (PBORE1, PBORE2 etc.). NOTE: See P-Point Zero: A Special Case
PConn integer
Specifies the connection type of p-point integer. NOTE: See P-Point Zero: A Special Case
Stype
Defines the Specific type of the component; it is effectively a subdivision of a GTYPE. For example, a component of GTYPE VALV may have an STYPE GATE, GLOB, GREG etc.
ANGIe
Defines the required angle of an ELBO or BEND, when DDANGL has been used in the component pointset (PTSET). The answer to this SELEC question in an SPCOM may be a single value (e.g. 90.0) or a range of values (e.g. for a var. 45 1,45.0 or var. 90for a 46,90.0).
RADIus
Defines the required radius of an ELBO or BEND, when DDRADI has been used in the component pointset (PTSET). May be a single value or a range.
SCHedule
Defines the schedule rating.
TEMperature
Defines the operating temperature.
Pressure
Defines the operating pressure.
RATing
Defines the pressure rating.
SHOP
Defines whether the component is intended for shop fabrication (SPCOM answer TRUE or SHOP) or on-site assembly (SPCOM answer FALSE or SITE).[/FONT]
You can modify the headers of an existing specification. However, sometimes you need to remove the spcos and then re-run the spec back in with the new headings. The REMOVE
