|
midrange.com
Here are the APAR's listing PTF's for V3R2, V3R6, V3R7, V4R1 (& V4R1M4 -
don't ask, but if you must know order informational APAR II10815 via
SNDPTFORD).
It would appear that fix is in base code for V4R2.
It would also appear that these fixes are not on current PTF cum
packages for V3R6 & V3R7, although MF17104 should be on the next V3R7
cum package, due around April 2nd (no additional cum packages are
planned for V3R6 - but what are you doing on V3R6 anyway when V3R7 is a
free upgrade and gives you a performance boost ! :-) ).
I don't know, but would ASSUME (I know that's dangerous) that the fix
made would also apply to Timestamp fields - anyone able to confirm or
deny that ?
Note also that Performance PTF's are summarized in an informational APAR
for each release.
You can SNDPTFORD for the following numbers:
II11024 INTRAN OSP-PERFM V4R1M0 PERFORMANCE RELATED PTF
II10120 CAN COMMON R370 PTF'S FOR SYSTEM PERFORMANCE AND
TOOLS
II09876 CAN COMMON R360 PTF'S FOR SYSTEM PERFORMANCE AND
TOOLS
II09985 CAN COMMON R320 PTF'S FOR SYSTEM PERFORMANCE AND
TOOLS
II07811 CAN OSP-PERFM AVAILABLE R230 PERFORMANCE PTFS
II07812 CAN OSP-PERFM AVAILABLE R220 PERFORMANCE PTFS
II07813 CAN OSP-PERFM AVAILABLE R211 PERFORMANCE PTFS
II07814 CAN OSP-PERFM AVAILABLE R210 PERFORMANCE PTFS
II07950 CAN OSP-PERFM AVAILABLE R305 PERFORMANCE PTFS
-------------------------------------------------------------------
Item MA16930
APAR Identifier ...... MA16930 Last Changed..98/01/20
OSP-PERFM PERFORMANCE IMPROVEMENT FOR DATE DATA TYPE
Symptom ...... PR PERFM Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 97/10/09
Component .......... 9400DG300 Duplicate of ........
Reported Release ......... 360 Fixed Release ............ 999
Component Name 5763 5769 5716 Special Notice
Current Target Date .. Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 360 : MF17090 available 97/11/03 (1000 )
Release 370 : MF17104 available 97/10/31 (1000 )
Release 410 : MF17113 available 97/10/30 (8013 )
Release 414 : MF17125 available 97/10/30 (1000 )
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
Customer stated that once they started to use our date code for
date calculations that their batch job run time increased from
20 hours to 40 hours. The application that they were running
previously is no longer supported. They must continue to use
our date code. They requested that we provide enhancements to
the date code to decrease the amount of time that it takes to
run their batch
LOCAL FIX:
PROBLEM SUMMARY:
We found areas in date/time code where the date conversion
performance could be enhanced.
PROBLEM CONCLUSION:
The date code was changed so that it takes less instructions to
convert dates.
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS: #CFDATEI #CFTIMEI #CFTSMPI
SRLS: NONE
RTN CODES:
CIRCUMVENTION:
None.
MESSAGE TO SUBMITTER: UPDATED 10/28/97
------------------------------------------------------------------
Item MA16926
APAR Identifier ...... MA16926 Last Changed..98/02/19
OSP-PERFM PERFORMANCE IMPROVEMENT FOR DATE DATA TYPE
Symptom ...... PR PERFM Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 97/10/06
Component .......... 9400DG300 Duplicate of ........
Reported Release ......... 320 Fixed Release ............ 999
Component Name 5763 5769 5716 Special Notice
Current Target Date .. Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 320 : MF16998 available 97/10/20 (8048 )
Release 360 : PTF not available yet
Release 370 : PTF not available yet
Release 410 : PTF not available yet
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
Customer stated that once they started to use our date code for
date calculations that their batch job run time increased from
20 hours to 40 hours. The application that they were running
previously is no longer supported. They must continue to use
our date code. They requested that we provide enhancements to
the date code to decrease the amount of time that it takes to
run their batch
LOCAL FIX:
PROBLEM SUMMARY:
We found areas in the date/time code where the performance of
date conversions could be enhanced.
PROBLEM CONCLUSION:
The date code was changed so that it takes less instructions to
convert dates.
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS: #DBDATEI #DBTIMEI #DBTSMPI
SRLS: NONE
RTN CODES:
CIRCUMVENTION:
None.
MESSAGE TO SUBMITTER: UPDATED 11/05/97
Neil Palmer AS/400~~~~~
NxTrend Technology - Canada ____________ ___ ~
Thornhill, Ontario, Canada |OOOOOOOOOO| ________ o|__||=
Phone: (905) 731-9000 x238 |__________|_|______|_|______)
Cell.: (416) 565-1682 x238 oo oo oo oo OOOo=o\
Fax: (905) 731-9202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mailto:NPalmer@NxTrend.com AS/400 The Ultimate Business Server
http://www.NxTrend.com
> -----Original Message-----
> From: Walden Leverich [SMTP:walden@techsoftinc.com]
> Sent: Thursday, March 26, 1998 8:34 AM
> To: Midrange Mailing List (E-mail)
> Subject: Date performance problems and fixes
>
> I'm doing a presentation on performance and I have a question on the
> date datatype performance. I know that there have been some
> performance problems relative to the date datatype in the past, and
> that these are now fixed for the most part. But, were these problems
> resolved in PTFs to back releases (V3R1,2/V3R6,7) or just in V4R1.
> Also, was the fix in 4.1 in base code, or in a PTF? Where PTFs are
> involved does anyone know the numbers? Finally, were/are there similar
> problems with the timestamp datatype and if so, have they too been
> resolved?
>
> Thanks,
> -Walden
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
