Application Operations Guide

Using report RSPO2010 to correct spool requests created with wrong deletion date (Year 2010 bug)

Document Version 1.00 20-01-2010

SAP AG Neurottstrae 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. These materials are subject to change without notice. These materials IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address:
service.sap.com/instguides

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way.

In order to make your document available under this alias, contact GBU AI.

Using report RSPO2010 to correct spool requests created with wrong deletion date

Contents
Using report RSPO2010 to correct spool requests created with wrong deletion date (Year 2010 bug) .............................. 1 1 Introduction .............................................................................. 4
1.1 General description of RSPO2010 .........................................4 1.2 Identifying requests created intentionally with infinite delete date .........................................................................................5

01 2010

1 Introduction
Due to a previously undiscovered bug in the SAP kernel, spool requests created after Dec. 23rd st 2009 have a delete date of Jan. 1 2100. As a consequence, no spool request will be deleted by the reorg reports RSPO1041 / RSPO0041 if requests are to be deleted according to their delete date. Furthermore the system has difficulties distinguishing between two kinds of requests: Requests with a delete date set by a user intentionally Requests with a wrong delete date set by the bug in the kernel In the following document, we will try to explain how report RSPO2010 can help to identify requests that should keep their infinite delete date and correct the other ones.

1.1 General description of RSPO2010

The main function of RSPO2010 is to correct the delete date of all spool requests after Dec. 23rd rd st 2009. In default mode, it selects all requests created after Dec. 23 2009 with delete date Jan. 1 2100 and corrects the date. The new delete date is calculated by adding the value of profile parameter rspo/req_lifetime (default 8) to the creation date, i.e. the delete date of a request created st th on Jan. 1 2010 will be changed to Jan 9 2010.

When you execute the report, it will display a list of all selected and modified requests.

01 2010

If you mark the checkbox "check delete date in jobs", the report will check if a selected spool requests was created by a batch job. If that is the case, it will check whether a retention time of 9 days has been set in the print parameters of the batch job (9 days meaning: do not delete). If that is true, the selected spool request will not be modified. Please note that using this feature of RSPO2010 might affect the performance of the report.

1.2 Identifying requests created intentionally with infinite delete date

This section describes how to identify spool requests which shall not be modified because the retention period was set intentionally by the user to infinite. The idea is to analyze spool requests rd created before Dec. 23 2009 which were created with an infinite retention period. If we assume assumption that requests created after Dec. 23rd have identical owners, titles, printer assignment or something similar, you can then exclude these requests from being modified later. If you want to find out whether any spool requests have been created with a retention time of 9 rd days (which means infinite) before Dec. 23 2009, you should mark the option 'requests before 23.12.2009'.

01 2010

The result could be as follows:

If you want to exclude all spool requests with the title 'DO NOT DELETE!' or 'IMPORTANT!' from being modified by RSPO2010, you mark 'requests since 23.12.2009' and click on the arrow icon next to the field 'Title or name of spool request'. On the next screen, change to the tab 'Exclude Single Values' and enter the titles of the spool requests that should not be modified.

01 2010

When you execute RSPO2010 with this setting, spool requests with title 'DO NOT DELETE!' or st 'IMPORTANT!' will keep their delete date Jan. 1 2100. You can also exclude several criteria simultaneously, e.g. besides the Title additionally under User Name spool requests which were created by specific users, e.g. SMITH and JONES. The excluded values are then combined with or. This means in this example: Spool requests which have either a title named: DO NOT DELETE! or IMPORTANT! or have owners named SMITH or JONES are not modified. We recommend to use the display only option of the report first: This will give you a list of the requests which the report will correct later. Analyze this list and if it is o.k. you can then run the report in change mode (checkbox display only not marked). Please note: Once you have corrected the spool requests this cannot be undone anymore!

01 2010