This page (revision-10) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by kparrott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
10 26-Nov-2021 10:22 3 KB kparrott to previous
9 26-Nov-2021 10:22 3 KB kparrott to previous | to last
8 26-Nov-2021 10:22 4 KB kparrott to previous | to last
7 26-Nov-2021 10:22 4 KB kparrott to previous | to last
6 26-Nov-2021 10:22 4 KB kparrott to previous | to last
5 26-Nov-2021 10:22 4 KB kparrott to previous | to last
4 26-Nov-2021 10:22 4 KB kparrott to previous | to last
3 26-Nov-2021 10:22 3 KB kparrott to previous | to last
2 26-Nov-2021 10:22 3 KB kparrott to previous | to last
1 26-Nov-2021 10:22 3 KB kparrott to last

Page References

Incoming links Outgoing links
TIMER LOGGING CAPABILITY
TIMER LOGGING CAPABILITY

Version management

Difference between version and

At line 3 changed one line
This describes the setupn and process for debugging UPCALC with different levels of Trace capabilities.
This describes the setup and process for debugging UPCALC with different levels of Trace capabilities.
At line 7 changed one line
!UPCALC - Selection Parameters for Tracinhg
!UPCALC - Selection Parameters for Tracing
At line 11 added 2 lines
\\
At line 18 added one line
\\
At line 28 added one line
\\
At line 33 added one line
\\
At line 31 changed 2 lines
*This parameter allows capability to show the Override Pay Point Trace values as defined on the [IPPP]
*When this parameter is Yes, the IPPP 'Override Trace Level' of the Pay Point Task will be read to trace all empoloyees in this Payrun when the UPCALC is run with Exception Level=0-Exception
*This parameter allows capability to show the [Override Trace Level|TRACE_LEVEL] values as defined on the [IPPP]
*When this parameter is Yes, the IPPP 'Override Trace Level' of the Pay Point Task will be read to trace all employees in this Payrun when the UPCALC is run with Exception Level=0-Exception
At line 39 added one line
At line 44 changed one line
If user wants to debug the performance of how UPCALC is calling the UPCALC tasks, user can set up a Function Preference for UPCALC to generate a TIMER logging file that provides the Task Name and Duration time of these tasks, please set up IMFN Function Preference as below for detail
If user wants to debug the performance of how UPCALC is calling the UPCALC tasks, user can set up a Function Preference for UPCALC to generate a TIMER logging file that provides the Task Name and Duration time of these tasks - set up IMFN Function Preference as below
At line 46 changed one line
user can set up UPCALC to run in Multi-Thread to improve UPCALC performance of a Payrun, please set up IMFN Function Preference as below
Users can set up UPCALC to run in Multi-Thread to improve UPCALC performance of a Payrun - set up IMFN Function Preference as below
At line 50 changed 6 lines
***[DB PRCSS THREADS] - specifies the number of Muliti-Threads to be used for UPCALC
***[PERFORMANCE FLDR] - specifies the Directory Name to be used by UPCALC or Trial Calc for the Performance Logging Timer file
**On IMFN screen for UPCALC function, user can add the Function Preference ‘PERFORMANCE FLDR’
**If this ‘PERFORMANCE FLDR’ specifies a valid the Directory Name, then UPCALC or Trial Calcwill generate the Performance Timer file using this Directory Name
**Trial Calc and UPCALC will generate Timer files with these naming convention:\\RPCALC_20160720_TIMERS_417232.csv - i.e. RPCALC + Date + ‘TIMERS’ + Mex ID\\UPCALC_20160720_TIMERS_417228.csv - i.e. UPCALC + Date + ‘TIMERS’ + Mex ID
**if UPCALC is run in Multi-Thread, the Timer file will display each Thread’s Timer statistics on one file
***[DB PRCSS THREADS|DB PRCSS THREADS(System_Preference)] - specifies the number of Muliti-Threads to be used for UPCALC
***[PERFORMANCE FLDR|PERFORMANCE FLDR(System Preference)] - specifies the Directory Name to be used by UPCALC or Trial Calc for the Performance Logging Timer file
At line 59 added 5 lines
*If this ‘PERFORMANCE FLDR’ specifies a valid the Directory Name, then UPCALC or Trial Calc will generate the Performance Timer file using this Directory Name
*Trial Calc and UPCALC will generate Timer files with these naming convention:
**RPCALC_20160720_TIMERS_417232.csv - i.e. RPCALC + Date + ‘TIMERS’ + Mex ID
**UPCALC_20160720_TIMERS_417228.csv - i.e. UPCALC + Date + ‘TIMERS’ + Mex ID
*If UPCALC is run in Multi-Thread, the Timer file will display each Thread’s Timer statistics on one file
At line 65 added 3 lines
\\
This page (revision-10) was last changed on 26-Nov-2021 10:22 by kparrottTop