| Title: | MRU Internal Bug Reports |
| Moderator: | COOKIE::STMARTIN |
| Created: | Wed Sep 20 1995 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 346 |
| Total number of notes: | 1175 |
A customer is wondering about status codes returned from MRU. He states that currently the status is written into a logfile instead of writing them to symbols;i.e. $STATUS. He is developing a batch procedure to run MRU along with SLS;etc and would like to be able to use status codes instead of having to open a logfile. He would like to submit a SPR, but before he does this, I told him I would look around. Is there anything in the works;i.e. future release of MRU that will start using status codes or some facsimile of this. Jon Stokes Mission Critical Gold Support Dtn 592-4611
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 340.1 | Been there, discussed that. How important is it? | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Wed May 07 1997 15:29 | 14 |
There is already a note on this subject. I think it will have the string "OP:" in it. At this point, the best we can do for the next version (*) is to ensure that the failure status we return for an error really is an ERROR. We might be able to include a utility facility code without too much work. (*) Per error facility codes are considerable extra work and aren't very portable. Given our plan to ship V1.2 by the end of June there isn't much time get the necessary work done. If this is important to the customer he should get that SPR in soon and at an appropriate level. Then I can let the managers figure whether to have me do the work. The good news is that I think I have a possible solution that can generalized on an operating system by operating system basis. | |||||