APAR status
Closed as Permanent restriction.
Error description
Native client does not allow attachments of same name to a recor d . Whereas through APIs we can attach files of same name.This b ehaviour is inconsistent . Moreover if through APIs we attach fi les of same name to a record there are issues.While opening thes e attachments repeatedly to view the contents of files at some point we see the contents are shown same for both the files even if they are different.
Local fix
Problem summary
The ClearQuest clients do not allow multiple attachments with the same name for the same defect. However, the API that writes an attachment record to the database does not duplicate this check, so a script can write attachments with duplicate names to the database.
Problem conclusion
The API is thus a pure write-an-attachment-record-to-the-database function and does not try to include the duplicate-name checking that has been assigned to the clients. The clients already check for duplicates and scripts should do the same before calling the API to write an attachment record to the database.
Temporary fix
Comments
APAR Information
APAR number
PK59690
Reported component name
CLEARQUEST WIN
Reported component ID
5724G3600
Reported release
701
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-01-22
Closed date
2008-09-24
Last modified date
2008-09-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
24 September 2008