| note, quite a known problem....just how we did it.
Okay, this is now it works (and yes I am open to suggestions on
how to make it better).
Inside of MCC, if a command goes across the call interface (from
a PM to any other module), then the returned code from the xM we
called is passed back to DCL (or at least that of the last call
made). New inside of MCC "exceptions" as well as "responses" are
both severity success. This means you must explicitly look for the
code # for the specialized and common exceptions to be able to
distinguish them from the responses (SRM terms - specialized exception
= problem detected by management module specific to the device it
is attempting to communicate with; common exception - a common type
of problem like unable to communicate with target, that can happend
to pretty much all manageable devices; response - successful return
of data; error - real software errors will be reported with severity
other than success).
Now as to parse errors, I just never even thought about returnig
them to DCL. Sorry about that one (that is what attrnotallow is).
You see MCC ran successfully, even though the command you entered
didn't, and so we return a success pretty lame now that you point
it out.
I will look into it an qar it.
|