Operation void getHistoryPMData (CIS CharacterString userName = NA, CIS CharacterString password = NA, CIS CharacterString destination = NA, CIS SequenceOf Structs::PMTPSelect pmTPSelectList = empty list, CIS SequenceOf Strings::PMParameterName pmParameters = empty list, CIS GeneralizedTime startTime = NA, CIS GeneralizedTime endTime = NA, CIS Boolean forceUpload = False), in Class PerformanceManager

Documentation
This operation allows the NMS to instruct the EMS to store PM history data in a file and send outside the interface by ftp or by anonymous ftp to the destination specified in the request. Performance monitoring data on multiple TPs of multiple MEs is transferred in one data file. The format of the file is contained in the attached supporting document PmFileFormat.
Measurement intervals and the given time frame are considered as half open intervals to the right, i.e. startTime <= t < endTime.
A particular historic measurement interval (of duration 15 min resp. 24 h) is defined to be covered by the specified time frame if there is a non empty intersection between the measurement interval and the given time frame, i.e. endTime[PM record] > startTime[request parameter] AND startTime[PM record] < endTime[request parameter] PM data are returned for all covered measurement intervals.
For records partly included in the time frame specified, PM data will be returned. In case a history bin has incomplete PM measurement data (for instance because PM data collection was disabled for some time period(s) within the bin's time span), the particular measurement period will be marked as incomplete.
This operation is asynchronous and is not required to wait until the PM data is extracted or until the FTP transfer is over before it returns. Notifications can be generated to inform the NMS of the progress of the transfer.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when the EMS does not support this operation.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. INVALID_INPUT - Raised when any input parameter is syntactically incorrect.
4. NE_COMM_LOSS - Raised when communication to managed element is lost.
External Documents

SD1-30_PMFileFormat.pdf |

Protocol |  | Qualification |
Exceptions |  | Size |
Time |  | Concurrency | Sequential
Export Control | PublicAccess |  |

Preconditions
Managed element or the TPs specifed have to exist.
Postconditions
Performance Monitoring data for the PM selectors specified are sent to the destination specified.
Semantics

Arguments

userName
/* in */ User name used for file transfer.
password
/* in */ Password used for file transfer.
destination
/* in */ Destination address used for file transfer.
The hostname of the destination machine and the full pathName of the target file (including the directory name and the file name) within the destination machine are specified. Hostname and full pathname are separated by a colon ( : ). The '/' or '\' in pathname are dependent on the destination and managed by the client.
pmTPSelectList
/* in */ List of PM selectors. If empty, PM data for all monitored TPs of all MEs managed by the EMS (all layer rates, all parameters, all granularities) are stored in the file.
pmParameters
/* in */ This parameter specifies which PM parameters within the scope of the pmTPSelectList shall be contained in the file. An empty list means to store all supported parameters. The returned parameters are best effort, i.e. among the parameters specified only the subset of supported parameters will be stored.
startTime
/* in */ Start of time frame for desired records.
endTime
/* in */ End of time frame for desired records.
forceUpload
/* in */ If the forceUpload parameter is true, the EMS is to upload the data for all the specified collection periods (provided they do exist in the MEs) and provide the entire PM data requested. If the forceUpload parameter is false, measurement intervals within the specified time frame for which PM data has been collected in the ME but not yet uploaded to the EMS will be included in the PM file with status "Unavailable", however without valid PM data.