NANC 248

GDMO Behavior and IIS Updates

Origination Date :12/04/1998

Originator:AT&T

Description:

There are four proposed updates to the GDMO.

1) Need to define the usage of the lnpDownload reply errors.  The following needs to be added to the GDMO behavior.

"The following errors can be returned in the lnpDownloadReply:

criteria-too-large - Too many records are being returned. This is determined by the MAXIMUM NUMBER DOWNLOAD RECORDS tunable on the NPAC SMS.

time-range-invalid - The time range given exceeeds the MAXIMUM DOWNLOAD DURATION tunable on the NPAC SMS.

no-data-selected - No criteria selected in request.

failed - Failed for other reasons. "

2) Reference Requirement 4 of NANC 79 in the GMDO for Release 2 under lnpNotificationRecovery action:

"The recovery of the SOA and LSMS notifications are independent requests".

3) Need to update and document the following item in the IIS/GDMO:

"Notifications can be recovered until they are purged from the database.  The tunable used to determine when to purge notifications is 'Notify Log Retention Period' which defaults to 90 days. "

4) Need to update and document the following item in the IIS/GDMO:

"The purge of audits are based on the tunable 'Audit Log Retention Period' which defaults to 90 days."

Also specify in the audit flows, the M-DELETE does not occur until 90 days after the audit.

Final Resolution:

Jan LNPAWG (Atlanta), group O.K. with this change order.  Move to next doc category.

Related Release:

2.0.1

Status: Implemented