Re: How do I get the equivalent status (DEC ADA IMPORT_EXCEPTION)
From: Larry Kilgallen (Kilgallen_at_SpamCop.net)
Date: 12/15/03
- Next message: Rob Young: "Re: Singapore Exchange to run on OpenVMS"
- Previous message: Gary Morin: "Re: OpenVMS, CSWS (apache), PHP and ... Rdb ???!!!!"
- In reply to: Stuart Palin: "Re: How do I get the equivalent status code when an exception has been"
- Next in thread: Stuart Palin: "Re: How do I get the equivalent status (DEC ADA IMPORT_EXCEPTION)"
- Reply: Stuart Palin: "Re: How do I get the equivalent status (DEC ADA IMPORT_EXCEPTION)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 15 Dec 2003 08:40:18 -0600
In article <3FDD82A9.BBBE62CC@0.0>, Stuart Palin <stuart.palin@0.0> writes:
> Larry Kilgallen wrote:
>>
>> In article <3FD9C40E.586BC65D@0.0>, Stuart Palin <stuart.palin@0.0> writes:
> ...
> <snip interesting bit about BLISS code - really don't see us
> getting into BLISS>
> ...
But you asked about examining subordinate chained messages, and I
told you how I did that.
>> > (Also, is there a definition of exactly which exception
>> > CLI.DCL_PARSE throws - so the exception handler can be more
>>
>> Yes, see the documentation of CLI$DCL_PARSE.
>
> Yes, been there. The documentation describes the Condition
> Values returned (if you can get them - which we can't
It also says the conditions signalled are the same as those returned.
> exceptions. Searching the ADA$PREDEFINED directory for
> things like 'IVVERB' throws up constant definitions that
> presumably match these condition codes - but no exception
> declarations.
That is what IMPORT_EXCEPTION is for. I would suggest you read all
three books of your DEC Ada documentation cover-to-cover. Coupled
with your knowledge of VMS, it really does show how the whole thing
fits together.
> The documentation also does not seem to mention a few of the
> errors that can occur during DCL_PARSE; e.g. MAXPARM,
> PARMDEL, NOQUAL.
If you find others, use pragma IMPORT_EXCEPTION.
>> > Code snippet:
>> >
>> > declare
>> > -- local block to limit scope of exception handler
>>
>> Here is where you might use pragma IMPORT_EXCEPTION.
>>
>> > begin
>> > CLI.DCL_PARSE(Status_Code,
>> > Command_String,
>> > Table);
>> > exception
>>
>> And then use the imported exception values for the documented codes
>> in separate "when" clauses.
>>
>> > when others => ?? How do I get the real Status_Code ??
>> > end;
>
> OK I'll have a look at this - but given that the
> documentation does not seem to be giving all the possible
> errors this does not seem a promising avenue. It would also
On the contrary, IMPORT_EXCEPTION is _very_ promising, since it
works even for exceptions that are defined by non-VMS components.
> seem likely that the exception handler is going to be a
> rather cumbersome mapping of exceptions back to status
> codes, just so we can use $GETMSG. :-(
The only way I could see it being called "cumbersome" is that it is
resolved at link time, but that is actually an advantage when you
consider how VMS message files are activated. Compile-time resolution
is less desireable than it might seem at first glance.
- Next message: Rob Young: "Re: Singapore Exchange to run on OpenVMS"
- Previous message: Gary Morin: "Re: OpenVMS, CSWS (apache), PHP and ... Rdb ???!!!!"
- In reply to: Stuart Palin: "Re: How do I get the equivalent status code when an exception has been"
- Next in thread: Stuart Palin: "Re: How do I get the equivalent status (DEC ADA IMPORT_EXCEPTION)"
- Reply: Stuart Palin: "Re: How do I get the equivalent status (DEC ADA IMPORT_EXCEPTION)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
