Consolidated Service Test and the RSU

ISV's and CST

We're coordinating our IBM CST service level recommendations with the service levels on the IBM ISV Remote Development Program. (The environments are provided by the Developer Technical Support Center in Dallas.) This is intended to provide ISV's who are using Remote Development Program environments the opportunity to test their products at the same service levels which IBM CST recommends to our mutual customers.

ISVs who maintain test environments at their locations can perform the monthly activities described below to create test environments for their products at the quarterly service levels recommended by IBM CST:

Month	Activity
January	Install RSUyy12 and all service through the end of December (PUTyy12) not already marked RSU excluding unresolved PEs.
February	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of January plus IBM CST marked RSUyy01.
March	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of February plus IBM CST marked RSUyy02. At the end of March, subject to a documented list of excluded PTFs on the IBM CST Web site, all PTFs installed to this point according to this process and not already marked RSU will be designated RSUyy03.
April	Install RSUyy03 and all service through the end of March (PUTyy03) not already marked RSU excluding unresolved PEs.
May	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of April plus IBM CST marked RSUyy04.
June	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of May plus IBM CST marked RSUyy05. At the end of June, subject to a documented list of excluded PTFs on the IBM CST Web site, all PTFs installed to this point according to this process and not already marked RSU will be designated RSUyy06.
July	Install RSUyy06 and all service through the end of June (PUTyy06) not already marked RSU excluding unresolved PEs.
August	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of July plus IBM CST marked RSUyy07.
September	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of August plus IBM CST marked RSUyy08. At the end of Septmber, subject to a documented list of excluded PTFs on the IBM CST Web site, all PTFs installed to this point according to this process and not already marked RSU will be designated RSUyy09.
October	Install RSUyy09 and all service through the end of September (PUTyy09) not already marked RSU excluding unresolved PEs.
November	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of October plus IBM CST marked RSUyy10.
December	Install HIPER/Security/Integrity/Pervasive PTFs and PE Resolution PTFs and their associated requisites and supersedes through the end of November plus IBM CST marked RSUyy11. At the end of December, subject to a documented list of excluded PTFs on the IBM CST Web site, all PTFs installed to this point according to this process and not already marked RSU will be designated RSUyy12.

An ISV who finds a problem should report it to the IBM Support Center. If the problem is identified as a possible defect in IBM code that might impact the functioning of the ISV product, the ISV should contact the IBM Consolidated Service Test Team.