| 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 |
Hello, I'm having some problems with the BYE function versus EXIT when ASTs are still running and performing file I/O. I have a program call through an EXECUTE call which performs most of its work with ASTs doing asynchronous read and gives control back to the calling script (allowing users to continue processing while reads are going on in the background) If I do an EXIT from ALLIN1 followed by a LOGOUT from VMS while the AST are still running no error occur. However if I execute the function BYE I'm getting the following errors from the ASTs routines : %ISS_FIO-W-READERR, error reading EVTDD2$DUB3:[ISS$CORE.DATA.ACCT]ISS$ACCT.DAT; -RMS-F-ISI, invalid internal stream identifier (ISI) value Does anyone knows how BYE differs from EXIT - LOGOUT and why this is happening. Regards Jean-Claude Carriere Assist Technical Support (Evry)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 568.1 | SYS$RMSRUNDWN | IOSG::TALLETT | Just one more fix, then we can ship... | Mon Apr 27 1992 09:53 | 26 |
Hi there!
I hope you are not calling the main image from AST level are
you? We had one intrepid explorer recently, calling the mail
code from AST level which it didn't like. It sounds like you
are not doing this however.
>%ISS_FIO-W-READERR, error reading EVTDD2$DUB3:[ISS$CORE.DATA.ACCT]ISS$ACCT.DAT;
>-RMS-F-ISI, invalid internal stream identifier (ISI) value
>
> Does anyone knows how BYE differs from EXIT - LOGOUT and why
> this is happening.
I had a look at the code for BYE and compared it to the EXIT code
and it looks like the relevant bit is that BYE calls SYS$RMSRUNDWN
and EXIT just calls $EXIT.
It sounds like your AST is firing after the main image has run down
your RMS stream, giving you the error. (Now as to WHY we call rms
rundown, I dunno, but I'm sure there was a reason...)
As for a fix, the only thing I can think of is creating an SDF
for BYE and doing your own code...
Regards,
Paul
| |||||
| 568.2 | this started back in VMS V3... | SKNNER::SKINNER | I'm doing my EARS | Mon Apr 27 1992 18:28 | 12 |
"We" do RMS rundown because there was a time that without it, records that had recently been written to weren't being written out properly. The RMS rundown caused the buffers to be flushed, and everything was happy. The SYS$RMSRUNDWN routine is called repeatedly until it returns a "true" status. Whether this routine call is still needed is unclear. Why the call should cause this interaction problem with ASTs is also unclear. BYE does one other thing differently than EXIT: BYE doesn't do a $EXIT, it does a $DELPRC. /Marty | |||||