FOSI error message
Nov 04, 2013
02:09 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nov 04, 2013
02:09 PM
FOSI error message
I have an old FOSI that we use for our MILSTD development output. One day,
if we get the approval, I'll migrate it to FO, but for now it produces what
we want. Any doubts, checkout MIL-HDBK-2361C
(
Attribute Value (ENUMERATED) of the attribute in the document instance
against which the <specval> tests
WARNING
Skipping <att> because it has one or more invalid <specval> or <fillval>
elements
WARNING
The value of this < attval="3"> does not conform to the Declared Attribute
Value (ENUMERATED) of the att...
if we get the approval, I'll migrate it to FO, but for now it produces what
we want. Any doubts, checkout MIL-HDBK-2361C
(
Attribute Value (ENUMERATED) of the attribute in the document instance
against which the <specval> tests
WARNING
Skipping <att> because it has one or more invalid <specval> or <fillval>
elements
WARNING
The value of this < attval="3"> does not conform to the Declared Attribute
Value (ENUMERATED) of the att...
5 REPLIES 5
Nov 04, 2013
02:11 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nov 04, 2013
02:11 PM
Yes and like you I couldn't find the problem and again like you it had no impact. But your right it bugs the bejezzes out of me when I get it. Sorry wish I could be more help.
Nov 04, 2013
08:53 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nov 04, 2013
08:53 PM
It seem like these messages must be coming from some FOSI somewhere. I suggest searching for specval in any .fos files in the relevant file system and the Arbortext distributed files.
Good luck!
Suzanne Napoleon
www.FOSIexpert.com
"WYSIWYG is last-century technology!
Good luck!
Suzanne Napoleon
www.FOSIexpert.com
"WYSIWYG is last-century technology!
Nov 05, 2013
08:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nov 05, 2013
08:30 AM
Suzanne,
I’ll do that, but that still won’t cure the problem of it showing up. If I do find one or more <specval>s like that, especially in the Arbortext distributed files I’ll pass that information along so PTC can find and FIX the problem.
Thanks.
Lynn
I’ll do that, but that still won’t cure the problem of it showing up. If I do find one or more <specval>s like that, especially in the Arbortext distributed files I’ll pass that information along so PTC can find and FIX the problem.
Thanks.
Lynn
Nov 05, 2013
10:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nov 05, 2013
10:20 AM
Suzanne,
I went through the FOSIs I have on my system and those in the distributed Epic files.
There is one <specval> in the distributed Epic files and nearly 900 in the various iterations of FOSI’s on my system. I searched for ‘attval=”2” | attval=”3”’. The results is there are no <specval>s with a value of 2, they are all 3. So the error of an <att> with a <specval> of 2 is really weird.
Lynn
I went through the FOSIs I have on my system and those in the distributed Epic files.
There is one <specval> in the distributed Epic files and nearly 900 in the various iterations of FOSI’s on my system. I searched for ‘attval=”2” | attval=”3”’. The results is there are no <specval>s with a value of 2, they are all 3. So the error of an <att> with a <specval> of 2 is really weird.
Lynn
Nov 06, 2013
01:13 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nov 06, 2013
01:13 PM
What version are you using?
Suzanne
>----------
>>
Suzanne
>----------
>>