Issue 2668:  Text unclear to a log"s behavior when off_duty                                                                                                                                                         (log_service-ftf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: The specification text is unclear to a log"s behavior when off_duty.
 What should the log do when it"s not functioning due to being
 outside the interval or shut down according to the weekmask? I assume it"s
 still available for adjusting weekmask parameters, but does it just drop
 log requests on the floor?
 

Resolution: rersolved, see revised text below
Revised Text: Resolution: 
If a log is scheduled off-duty, then the log should respond to push with 
a NO_RESOURCES system exception, with a minor code defined for scheduled 
off duty. 

To stay in line with Issue 2667 a new exception should be created, LogOffDuty, 
which would be raised to the user if a write_records() or write_recordlist() operation 
was invoked and the log was "off-duty". 

Revised Text: 
Specification Text 
Section 3.2.5.1: Log Record Writing  (Based on changes introduced in Issue 2667) 
... 
Some suggestions are to raise: 

     a NO_RESOURCE exception when the log is full 
     a NO_RESOURCE exception when the log is off duty 
     a NO_PERMISSIONS exception when the log is locked 
     a TRANSIENT exception the log is disabled 

... 
exception LogOffDuty {}; 
void write_records(in Anys records) 
    raises (LogFull, LogOffDuty, LogLocked, LogDisabled); 
void write_recordlist(in RecordList list) 
    raises (LogFull, LogOffDuty, LogLocked, LogDisabled); 
... 
Both the write_records() and write_recordlist() operations have the following behavior: 

     If the log's availability status is "log_full" and its LogFullAction is "halt", then a LogFull 
     exception is raised and the number of log records written will be returned in the exception. 
     If the log's availability status is "off_duty", then a LogOffDuty exception is raised 
     and no log records are written.

     If the log's administrative status is "locked", then a LogLocked exception is raised 
     and no log records are written. 
     the log's operational state is "disabled", then a LogDisabled exception is raised 
     and no log records are written.

Specification IDL 
module DsLogAdmin { 
    ... 
    exception LogOffDuty {}; 
    ... 
    interface Log { 
        ... 
        void write_records (in Anys records) 
            raises (LogFull, LogLocked, LogOffDuty); 
        void write_recordlist (in RecordList list) 
            raises (LogFull, LogLocked, LogOffDuty); 
        ... 
    }; 
    ... 
}; 

Actions taken: 
Completed.
Actions taken:
May 27, 1999: received issue
July 27, 1999: closed issue
Discussion: 

End of Annotations:=====
Sender: spruce@ovdm40.cnd.hp.com
Message-ID: <374B4B01.94936F4B@fc.hp.com>
Date: Tue, 25 May 1999 19:14:41 -0600
From: Stephen Spruce <spruce@fc.hp.com>
Organization: Telecom Management Division
X-Mailer: Mozilla 4.08 [en] (X11; I; HP-UX B.10.20 9000/777)
MIME-Version: 1.0
To: juergen@omg.org
Subject: Issues for Telecom Log Service
Content-Type: multipart/mixed;
boundary="------------5359345BE554D3D338D5D19C"
X-UIDL: 30aaae3f45cba14fe2a8031cca11ac75

Hi Juergen,

Attached is a list of issues that have been brought up against 
the Telecom Log Service (TLS) since it reached the Adopted
Specification
stage. I am not exactly clear on the content that is necessary 
for these issues, so let me know if you need more information 
about any or all of them. 


SSUE
-----
(from Matt Braun: mjb2@cs.wustl.edu)
The specification text is unclear to a log's behavior when off_duty.
What should the log do when it's not functioning due to being
outside the interval or shut down according to the weekmask? I assume
it's
still available for adjusting weekmask parameters, but does it just
drop
log requests on the floor?