RPTIME01 ( PT60 ) damn slow .... Each job taking 6 hours to run

Question

Hello Guys,
         We have are on SAP 4.7 and CE in place. Time evaluation is damn slow. I’m clueless from where to start. It’s like finding a needle in haystack.  
  I came across the following OSS note; we implemented it but no change. Each job is taking like 6 to 7 hours ….
Any help would be appreciated
“It is also possible to optimize the runtime of RPTIME01 by adjusting the T77s0 parameters LDB (group) and PCEPS (semantic abbreviation)). The default setting is a value of 0, which means that the logical database PNPCE processes packages of 10,000 persons. You can set a considerably smaller value here, for example 100. “
Note 1016714 - Memory overflow TSV_TNEW_PAGE_ALLOC_FAILED
Symptom
When you process a large number of persons using the RPTIME01 time evaluation driver, the runtime is excessive, and the system may terminate the program with the short dump TSV_TNEW_PAGE_ALLOC_FAILED.
Other terms
PNPCE, interface object, memory overflow, time evaluation, concurrent employment
Reason and Prerequisites
The error occurs if the RPTIME01 program tries to allocate memory space that is no longer available. Three factors affect whether the program terminates, when it terminates, and how the error affects the runtime - these are the system settings, the hardware you use, and (most importantly) the amount of data to be processed. Due to this error, the application program retains a copy of specific data for each processed personnel number (contract) in the working memory, even though this data is no longer required after it has completed the time evaluation of a person.
Solution
The error has been corrected, and the solution is delivered by Support Package. You can also implement an advance correction. It is also possible to optimize the runtime of RPTIME01 by adjusting the T77s0 parameters LDB (group) and PCEPS (semantic abbreviation)). The default setting is a value of 0, which means that  the logical database PNPCE processes packages of 10,000 persons. You can set a considerably smaller value here, for example 100. Note that this has no effect on the error described above - RPTIME01 still does not delete the contract data from memory when logical database PNPCE does so. However, by reducing the values of LDB PCEPS, you also reduce the application's memory requirements

Answer 1

We have updated the support pack  to 73  and program “RPCS0000” is giving error  “Invalid SPOOL parameters”  . I created the variant in PT60 , and running 20 jobs . it is keep giving error .
    After research I come to know that for program “RPCS0000 “ in source code “RPCS0F00” in the following perform it is giving error .
  PERFORM get_pri_params USING pri_params
arc_params
  xini_pri_params
    job_name
  xnodial_flg
   xprogname
   spool_title.
SAP note : BTC_DONT_READ_PRIPARAMS   LIKE BTCH0000-INT4 VALUE 35,  " note 770158
Any body know how to get of this error .
FYI
Symptom
When you create job steps, this results in a large number of accesses on the TPRI_PAR table containing the print parameters. The high access rate occurs in particular when you try to create a job with a large number of steps.
Other terms
BP_JOB_MODIFY, BP_JOB_READ, JOB_SUBMIT, LBTCHDEF, read_old_jobdata
Reason and Prerequisites
This is a program error that causes superfluous accesses to the TPRI_PAR table.
Solution
Import the relevant Support Package. For technical reasons (upgrade problems), correction instructions are not available.
IMPORTANT NOTE: Unfortunately, the first version of this note contains an error. This error becomes apparent when you edit a step in change mode in transaction SM36 or SM37 with extended print parameters (for example, e-mail address in the case of a mail printer or page area). The extended print parameters are not displayed in this case. To solve this problem, import the most recent Support Package or implement the correction instructions.
Note that the correction instructions must only be implemented if you have already imported the Support Packages that eliminate the error described in this note. The correction instructions do NOT eliminate the problem of unnecessary access to TPRI_PAR.