# Visio diagrams for Adabas Physical Design?

**URL:** <https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-Scope-of-Product\
**Created:** [August 24, 2007, 9:22pm UTC](https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288 "2007-08-24T21:22:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Douglas\_Kelly](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/douglas_kelly/32/102_2.png) [@Douglas\_Kelly](https://techcommunity.softwareag.com/u/Douglas_Kelly)\
**Post date:** [August 24, 2007, 9:22pm UTC](https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288/1 "2007-08-24T21:22:28Z")

</div>

Does anyone have a Visio stencil with shapes for documenting an Adabas Physical file design - something that allows presenting PE groups, MU fields and superdescriptors?

---

<div class="post-metadata">

**Author:** ![Matthias1](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@Matthias1](https://techcommunity.softwareag.com/u/Matthias1)\
**Post date:** [August 27, 2007, 11:52am UTC](https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288/2 "2007-08-27T11:52:19Z")

</div>

> [@Douglas Kelly](#):
>
> something that allows presenting PE groups, MU fields and superdescriptors?

I’ve worked with MS Visio some years ago. I only used it for documentation purposes. From my point of view, it was ugly to use and buggy. You’re forced to put PE/MU-Fields in own files. But if there are some tricks or later Versions of Visio which are able to create “List/Array-Fields” …

---

<div class="post-metadata">

**Author:** ![KlaBue](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@KlaBue](https://techcommunity.softwareag.com/u/KlaBue)\
**Post date:** [August 29, 2007, 9:35pm UTC](https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288/3 "2007-08-29T21:35:44Z")

</div>

> [@Douglas Kelly](#):
>
> Does anyone have a Visio stencil with shapes for documenting an Adabas Physical file design - something that allows presenting PE groups, MU fields and superdescriptors?

Not visio, but a solution based on a MindMap.  
i have uploaded an example for a graphical representation of adabas-fdts:  
[http://tech.forums.softwareag.com/viewtopic.php?t=13574](http://tech.forums.softwareag.com/viewtopic.php?t=13574)

i am using very often mindmaps for graphical documentation, e.g. for datastructures like Adabas-Fdt’s. one of the advantages in the upload mentioned above is, that the graphic is nearly created automatically.

KlaBue

---

<div class="post-metadata">

**Author:** ![Matthias1](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@Matthias1](https://techcommunity.softwareag.com/u/Matthias1)\
**Post date:** [August 30, 2007, 11:21am UTC](https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288/4 "2007-08-30T11:21:55Z")

</div>

> [@KlaBue](#):
>
> i am using very often mindmaps for graphical documentation, e.g. for datastructures like Adabas-Fdt’s. one of the advantages in the upload mentioned above is, that the graphic is nearly created automatically.

That’s Interesting! But I guess documentation is only one side of the story. The other side would be to export FDUFDTs or SQL-Creates for the data modell… But this didn’t work good on visio.

Next time, I’ll have a look at you mindmap-solution. 🙂

---

<div class="post-metadata">

**Author:** ![KlaBue](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@KlaBue](https://techcommunity.softwareag.com/u/KlaBue)\
**Post date:** [August 30, 2007, 2:22pm UTC](https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288/5 "2007-08-30T14:22:05Z")

</div>

> [@Matthias](#):
>
> The other side would be to export FDUFDTs or SQL-Creates for the data modell… But this didn’t work good on visio.

Matthias,

the OP asks for documentation of fdt’s.

Don’t’ get me wrong: the documentation as mindmap is no more than a transformation of the fdt in xml-format as generated by READFDT.NSP. With this approach, it’s only a matter of another xsl-stylesheet, to generate SQL-DDL, input for Abas-Utilities, HTML-pages, or whatever you want. or, if visio has an xml-import-format, it should be not a big issue to transform the xml-fdt into this format (one have to create the appropriate xsl-stylesheet “only”).

KlaBue

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:48pm UTC](https://techcommunity.softwareag.com/t/visio-diagrams-for-adabas-physical-design/75288/6 "2021-04-02T14:48:41Z")

</div>


