Thischapterdescribesadministrativeproceduresthatyoumayneedtoensure data iscorrectlysynchronizedbetweentheprojectplanand theRational ClearQuest database.Italso providesadditionalinformationthatyoucanusefor
troubleshooting.
Changing
required
fields
in
Rational
ClearQuest
IftheRational ClearQuestadministratorchanges theRational ClearQuestdatabase schematoaddnewrequiredfieldsormakeexistingfieldsrequired, the
administratormust workcloselywiththeprojectmanagertoensurethatevery taskintheMicrosoft Projectprojectplanhasanentryinthisfield.
Ifonetaskin theMicrosoft Projectprojectplandoesnothaveanentryinthe newlycreated requiredfield,thattaskcannotbe exportedorsynchronized.Project Tracker displaysanerrormessageandfailstoexportorsynchronizethattask.
Nesting
project
plans
AfteraprojectplanislinkedtoaRational ClearQuestdatabase,it isnotpossibleto nest otherprojectplansinthelinkedplan.Ifyoutrytodoso, runningthe
synchronize functioncausesruntimeerrorsand unpredictablebehavior. Insteadofnesting aprojectinthelinkedproject,enterthenew tasksintoyour linkedproject.
Task
name
truncated
when
transferred
TheRational ClearQuestHeadlinefieldcancontainupto125 characters.Ifyou exporta projectplantaskwhoseTaskNameexceeds 125characters,onlythefirst 125 aretransferredto theHeadlinefieldoftheRationalClearQuestrecord.Youcan seewhenthisoccursintheprogresslog.
Ifyouusetheexportfunction andthenthesynchronizefunction,thetruncated version mightreappearintheprojectplanTaskNamefield.Duringthe
synchronize process,thetruncatedversionthatwas transferredtotheHeadline fieldintheRational ClearQuestrecord iscopied backtotheprojectplanTask Name field,overwritingthelongerversion.
Removing
an
owner
from
the
Rational
ClearQuest
database
TheRational ClearQuestadministratorcanremovenamesfromthelistofactive users.Thislistconsistsofthose usernamesthatarevalidentriesin theOwner fieldof theRational ClearQuestdatabase.
However, whenanameisremovedfromthelistofactiveRational ClearQuest users,itisnotremovedfromthelistofusersthatProjectTrackerrecognizesduring theimport,export,andsynchronize processes.TheRational ClearQuest
administratormust notifyeveryprojectmanagerwhena RationalClearQuestuser isremovedfromtheactiveuserslist.Theprojectmanager canthen removethe resourcenamefromProjectTracker.
Duringanyoftheseprocesses,whenProjectTrackerfindsaResourcenameinthe projectplanthatdoesnotmatcha recognizedRationalClearQuestownername, it displays alistofrecognizedRational ClearQuestusers.Thelistincludesthename of theRational ClearQuestuser whowas removedfromthelistofactiveusers. Selecting thisuser storesthenameof someonewhonolongerworks ontheproject in theResourcenamefieldoftheprojectplantask.
Deleting
the
actual
end
date
from
a
Rational
ClearQuest
record
ARational ClearQuestuser canmodifytheActualEndDatefieldina Rational ClearQuestdatabaserecord tomakeitblank.IftheSynchronizefunctionisrun, thatblank isnotcopiedinto theActualFinishDatefieldinthelinkedrecord inthe projectplan. Instead,whateverdatewasintheActualFinishDate fieldremains there. MicrosoftProjectdoesnotletProjectTrackercopy anemptyfieldtoan ActualFinishDatefieldthatalreadyhasa value.
TodeterminewhethertheActualEndDatefieldisblank,youortheRational ClearQuestadministratorcanruna queryoftheRational ClearQuestrecords.
Using
functions
together
to
ensure
updated
information
The synchronizefunctionworksonlywithtasks thatwerelinkedtorecordsduring an importorexportprocess.Tasksthatdo nothavea linkedrecordandrecords thatdo nothavea linkedtaskareignored.
Toensurethata projectplanand aRational ClearQuestdatabase arefullyupdated, youmightneed tousemorethanonefunction.
Updating
a
project
plan
Ifteammembershaveaddednew recordsto theRational ClearQuestdatabase, transfer thoserecordstotheprojectplanasnewtasks.Anyrecordsthatwere added sincethelast timethattheimportfunction ranareignoredbecausetheyare notyet linkedtoprojectplantasks.
Toensurethatbothnew andmodifiedrecordsintheRational ClearQuestdatabase are reflectedintheprojectplan,youmight needtousetheimportfunctionto transfer thenewrecords,and thenusethesynchronize functiontocapturechanged informationfromexistingrecords.
Updating
a
Rational
ClearQuest
database
Iftheprojectmanageradded newtaskstotheMicrosoftProjectplan, transfertasks totheRational ClearQuestdatabase asnew records.
Toensurethatbothnew andmodifiedtasksarereflectedintheRational
ClearQuestdatabase,usetheexportfunction totransferthenewtasks,and then usethesynchronizefunctiontocapturechangedinformationfromexistingtasks.
Updating
the
Rational
ClearQuest
record
types
list
Duringa project,theRational ClearQuestsystemsadministratormightaddnew record typestotheRational ClearQuestdatabase andremoveobsoleteones. Ifthis happens, usetheUpdateClearQuestRecordTypesListcommand.Whenyouuse this command,ProjectTrackerupdatestheClearQuestRecordTypesListforthat projectplantoincludenew validrecordtypes.Alternatively,youcanconvertthe
record typefora newtasktooneofthetypesalreadyonthelist.Youcannot importtherecordunlessyouchooseoneofthesemethods.
Toupdatethelist,click Tools>ClearQuest >AdministrativeTasks>Update ClearQuest RecordTypesList.
Deleting
tasks
and
records
Whenyoudeletea taskfromtheprojectplan,ProjectTrackerdoesnotdeletethe corresponding RationalClearQuestrecord.YoucanleavetheRationalClearQuest record inthedatabase,oryoucanremoveitinRational ClearQuest.Youmust track alltasksdeletedfromtheprojectplanand takethecorrectaction ineach case.
Thelogcreatedbythesynchronizefunctionincludesa messagethatindicates whena linkedtaskcannotbefoundfora RationalClearQuestdatabaserecord.To find thesemessagesand verifythattheappropriate resultwasachieved,seethe log.
Whenyoudeletea recordfromtheRationalClearQuestdatabase,youcanleave thetaskintheprojectplan,oryoucanremoveit inMicrosoftProject.Youmust track allrecordsdeletedfromtheRational ClearQuestdatabase andtakethe correctaction ineachcase.
Appendix.
Notices
Thisinformationwasdevelopedforproductsandservices offeredintheU.S.A. IBM maynotoffertheproducts,services,orfeaturesdiscussedinthisdocumentin othercountries.Consultyour localIBMrepresentativeforinformationonthe productsand servicescurrentlyavailableinyourarea.Anyreferencetoan IBM product, program,orserviceisnotintendedtostateorimplythatonlythatIBM product, program,orservicemaybe used.Anyfunctionallyequivalentproduct, program, orservicethatdoesnotinfringeanyIBMintellectualpropertyrightmay be usedinstead.However, itistheuser’sresponsibility toevaluateandverifythe operationofanynon-IBMproduct,program, orservice.
IBM mayhavepatentsorpendingpatent applicationscoveringsubjectmatter described inthisdocument.Thefurnishingofthisdocumentdoesnotgrantyou anylicensetothesepatents.Youcansend licenseinquiries,inwriting,to: IBM DirectorofLicensing
IBM CorporationNorthCastleDrive Armonk,NY10504-1785
U.S.A.
For licenseinquiriesregardingdouble-byte(DBCS)information,contacttheIBM IntellectualProperty Departmentinyourcountryorsendinquiries,in writing,to: IBM WorldTradeAsiaCorporationLicensing
2-31 Roppongi3-chome,Minato-ku Tokyo106,Japan
Thefollowingparagraphdoesnotapplyto theUnited Kingdomor anyother country wheresuchprovisionsareinconsistentwithlocallaw:
INTERNATIONALBUSINESSMACHINESCORPORATIONPROVIDES THIS PUBLICATION″ASIS″WITHOUTWARRANTYOFANYKIND,EITHER EXPRESSORIMPLIED,INCLUDING,BUTNOTLIMITED TO,THEIMPLIED WARRANTIESOFNON-INFRINGEMENT,MERCHANTABILITYORFITNESS FORAPARTICULARPURPOSE.Somestatesdo notallowdisclaimerofexpress or impliedwarrantiesincertaintransactions,therefore,thisstatementmaynotapply toyou.
Thisinformationcouldinclude technicalinaccuraciesortypographicalerrors. Changes areperiodicallymadetotheinformationherein;these changeswillbe incorporatedinneweditionsof thepublication.IBM maymakeimprovements and/or changesintheproduct(s)and/ortheprogram(s)describedinthis publication atanytimewithoutnotice.
Anyreferencesinthisinformationtonon-IBMWebsitesareprovidedfor
convenienceonlyanddonotinanymannerserveasanendorsementofthoseWeb sites.Thematerialsat thoseWebsitesarenotpartof thematerials forthisIBM productanduseofthoseWebsitesisatyour ownrisk.
IBM mayuseordistribute anyoftheinformationyousupplyinanywayit believes appropriatewithoutincurringanyobligationtoyou.
Licenseesof thisprogramwhowishtohaveinformationaboutit forthepurpose of enabling:(i)theexchangeofinformationbetweenindependentlycreated
programs andotherprograms(includingthis one)and(ii)themutualuseofthe informationwhichhasbeenexchanged,shouldcontact:
IBM Corporation DepartmentBCFB 20Maguire Road Lexington,MA02421 U.S.A.
Such informationmaybeavailable,subjecttoappropriatetermsandconditions, includinginsomecases,paymentof afee.
The licensedprogramdescribedinthis documentandalllicensedmaterial
available foritareprovidedbyIBMundertermsoftheIBMCustomerAgreement, IBM InternationalProgramLicenseAgreementoranyequivalentagreement betweenus.
Anyperformancedatacontained hereinwas determinedinacontrolled
environment.Therefore,theresultsobtained inotheroperatingenvironmentsmay vary significantly.Somemeasurementsmayhavebeenmadeondevelopment-level systemsandthereisnoguaranteethatthesemeasurementswillbethesameon generallyavailable systems.Furthermore,somemeasurementmayhavebeen estimatedthrough extrapolation.Actualresultsmayvary.Usersof thisdocument shouldverifytheapplicabledatafortheirspecific environment.
Informationconcerningnon-IBMproductswasobtained fromthesuppliers of those products,theirpublished announcementsorotherpubliclyavailablesources. IBM hasnottestedthoseproductsandcannotconfirmtheaccuracy of
performance, compatibilityoranyotherclaims relatedtonon-IBMproducts. Questionsonthecapabilitiesofnon-IBMproductsshouldbe addressedtothe suppliers ofthoseproducts.
COPYRIGHT LICENSE:
Thisinformationcontainssampleapplicationprogramsinsourcelanguage,which illustrates programmingtechniquesonvariousoperatingplatforms.Youmaycopy, modify, anddistributethese sampleprogramsinanyformwithoutpaymentto IBM, forthepurposesofdeveloping,using,marketing ordistributingapplication programs conformingtotheapplicationprogramminginterface fortheoperating platformforwhichthesampleprogramsarewritten.Theseexampleshavenot been thoroughlytestedunderallconditions.IBM,therefore,cannotguaranteeor imply reliability,serviceability,or functionoftheseprograms.Youmaycopy, modify, anddistributethese sampleprogramsinanyformwithoutpaymentto IBM forthepurposesofdeveloping,using,marketing,ordistributingapplication programs conformingtoIBM’sapplicationprogramminginterfaces.
Eachcopy oranyportionofthese sampleprogramsoranyderivativework,must include acopyright noticeasfollows:
(c)(yourcompanyname)(year).Portionsofthiscodeare derivedfromIBMCorp. Sample Programs.(c)CopyrightIBM Corp._entertheyearoryears_.Allrights reserved.
Additional legalnotices aredescribedinthelegal_information.htmlfilethatis includedinyourRational softwareinstallation.
AIX, ClearCase,ClearCaseAttache,ClearCase MultiSite,ClearDDTS, ClearGuide, ClearQuest, DB2,DB2UniversalDatabase, DDTS,Domino,IBM,LotusNotes, MVS,Notes,OS/390,PassportAdvantage,ProjectConsolePurify,Rational, Rational Rose, RationalSuite,Rational UnifiedProcess,RequisitePro,RUP, S/390,SoDA, SP1, SP2,TeamUnifying Platform,WebSphere, XDE,and z/OSaretrademarksof InternationalBusiness MachinesCorporation intheUnitedStates, othercountries, orboth.
Java andallJava-basedtrademarksandlogos aretrademarksofSunMicrosystems, Inc. intheUnitedStates, othercountries,orboth.
Microsoft, Windows,WindowsNT,andtheWindows logoaretrademarksof Microsoft CorporationintheUnitedStates,othercountries,orboth.
UNIX isa registeredtrademarkofTheOpenGroupintheUnitedStatesand other countries.
Linuxisa trademarkofLinusTorvaldsintheUnitedStates,othercountries,or both.
Other company,productorservicenamesmaybetrademarksorservicemarks of others.
PrintedinUSA