[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
527.0. "GPC - OA$NOTES_STATUS and _ERROR" by ADO75A::BEESTON () Tue Apr 21 1992 08:45
In a script I attempt to use the OA$NOTES_STATUS and OA$NOTES_ERROR symbols.
In the following case I am not able to use either of these symbols
successfully and I suspect that I will have the same problem in other function
calls.
In a script I use the following code.
NOTES OPEN 'conference-name', 'class'
.IF NOT OA$NOTES_STATUS THEN GET OA$DISPLAY = OA$NOTES_ERROR
The conference is restricted and the user is not a member of the
conference.
The NOTES OPEN reports the following error messages -
%NONAME-E-OPENIN, error opening 'note file VMS filename'
-NOTES-E-NOTMEMBER, you are not a member of this conference
with the 'error opening' message being displayed on line 24 when the script
does eventually fail.
The test on the OA$NOTES_STATUS symbol returns a value of 1 and the
script continues processing. However, the script fails on the next command
(which attempts to check the conference membership list) because
the conference has not been successfully opened.
1) I expected that the NOTES OPEN would fail and that OA$NOTES_STATUS
would be set to 0.
2) Should I be able to use the OA$NOTES_ERROR symbol to display a meaningful
message to the user?
3) Also, are there restrictions to when OA$NOTES_STATUS is useful and why
doesn't OA$NOTES_ERROR only display the useful -NOTES- error messaage?
Thanks.. Liz
T.R | Title | User | Personal Name | Date | Lines |
---|
527.1 | GPC error status etc. on the bug list | SIOG::T_REDMOND | Thoughts of an Idle Mind | Tue Apr 21 1992 11:00 | 8 |
| We know that the GPC error signalling is not great at the moment. It's
on the bug list to be fixed. We started out with the idea that we would
be nice to people and try and trap any unfriendly error messages issued
by VAX Notes and turn them into user-friendly ALL-IN-1 type messages.
Unhappily for the technical users we appear to have gone too far... The
situation does not change in V3.0.
Tony
|