AMSXML(5)

🎀 NAME 🎀

okay bestie, welcome to amsxml — it's the CCSDS Asynchronous Message Service MIB initialization XML file 💖 (yes the name is a mouthful, we love her anyway)

---

✨ DESCRIPTION ✨

so here's the tea ☕: the Management Information Base (MIB) for an AMS communicating entity — and that's either amsd or an AMS application module, iykyk — has to hold enough info for that entity to actually start participating in AMS message exchange. think things like the network location of the configuration server, plus the roles and message subjects defined for some venture. all of it. no cap. 🫶

AMS entities just automatically load their MIBs from initialization files at startup. easy. BUT — and this is the plot twist — it depends on how AMS was built:

• if AMS was built with the -DNOEXPAT compiler option set, your MIB initialization file must conform to the amsrc syntax described in amsrc(5)
• otherwise, the expat XML parsing library must be linked into the AMS executable, and the MIB initialization file must conform to the amsxml syntax described below 👇

The XML statements in the MIB initialization file are basically elements of MIB update information, and each one may carry one or more attributes. an element can also have sub-elements that get listed inside the declaration of the parent element, and then those can have sub-elements, and so on and so on — it's giving nesting doll realness 🪆✨

There are two types of elements recognized in the MIB initialization file:

1. control elements — these establish the update context within which the configuration elements nested inside them get processed
2. configuration elements — these declare values for one or more items of AMS configuration information in the MIB

For a full discussion of the recognized control elements and configuration elements of the MIB initialization file, go read the amsrc(5) man page. she ate 💅

⚠️ NOTE, though — all elements of an XML-based MIB initialization file must be sub-elements of a single sub-element of the XML extension type ams_load_mib in order for the file to be parsed successfully by expat. like, this is not optional. fr fr. 🙈

---

🌈 EXAMPLE 🌈

here's what it looks like in the wild, bestie 🌸:

<?xml version="1.0" standalone="yes"?>

<ams_mib_load>

    <ams_mib_init continuum_nbr="2" ptsname="dgr"/>

    <ams_mib_add>

        <continuum nbr="1" name="apl" desc="APL"/>

        <csendpoint epspec="beaumont.stepsoncats.com:2357"/>

        <application name="amsdemo" />

        <venture nbr="1" appname="amsdemo" authname="test">

            <role nbr="2" name="shell"/>

            <role nbr="3" name="log"/>

            <role nbr="4" name="pitch"/>

            <role nbr="5" name="catch"/>

            <role nbr="6" name="benchs"/>

            <role nbr="7" name="benchr"/>

            <role nbr="96" name="amsd"/>

            <role nbr="97" name="amsmib"/>

            <role nbr="98" name="amsstop"/>

            <subject nbr="1" name="text" desc="ASCII text"/>

            <subject nbr="2" name="noise" desc="more ASCII text"/>

            <subject nbr="3" name="bench" desc="numbered msgs"/>

            <subject nbr="97" name="amsmib" desc="MIB updates"/>

            <subject nbr="98" name="amsstop" desc="shutdown"/>

            <unit nbr="1" name="orbiters"/>

            <unit nbr="2" name="orbiters.near"/>

            <unit nbr="3" name="orbiters.far"/>

            <msgspace nbr="2"/>

        </venture>

    </ams_mib_add>

</ams_mib_load>

---

👑 SEE ALSO 👑

• amsrc(5) — go read her too, she's the blueprint 🦋

---

k byeeee, this was the AMSXML(5) page from the AMS configuration files manual, and the source/version sitch is perl v5.24.1, dated 2016-07-07. periodt. 💜✨