cancel
Showing results for 
Search instead for 
Did you mean: 

Column Activity time of DB2 Thread Activity is sorted improperly

Former Member
0 Kudos

Dear Thomas!

There is a small but annoying problem... The column of "Activity Time" in "Thread Activity" ALV table is not sorted properly.

The field of "ACTTIME" contains time amounts in two different formats if the amount includes days or doesn't.

The note 1280173 doesn't correct the problem. Even after this note the column sorted in the descending mode looks in such a way:

12:13:14.156789

099d 12:13:14.5

07:24:34.157890

030d 12:13:14.5

020d 12:13:14.5

01:24:34.157890...

The desired format (even with "d" for days):

d099 12:13:14.5

d030 12:13:14.5

d010 12:13:14.5

12:13:14.156789

07:24:34.157890

01:24:34.157890...

It is an ALV table and its numerical fields are displayed as right-justified and character fields as left-justified despite leading spaces. A correction is required, either in the sorting routine or in these values presentation.

Best regards,

Vlad

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

The remark is still unanswered...

brian_walker
Active Participant
0 Kudos

My advice: Don't hold your breath.

SAP Note 1280173 is for BC-DB-DB2, aka DB2 for z/OS. Since this platform has at best 1% of the SAP market share, I would not expect such a small non-critical annoyance to be fixed quickly. That is just based on my limited experience with SAP on Z. SAP probably has bigger issues to solve on platforms with far more market share.

We're still waiting for the recommended runstats and reorgs to work with a schema other than the ABAP stack's SAPR3. At the moment, DSNACCOR is able to feed SAP all recommended runstats and reorgs, but SAP can only handle the ones with SAPR3. The others (including SAPJAVA) are ignored. We were first promised that this would be fixed in SAP_BASIS 7.00 SP17 and had to wait 6 months for this SP to be released after we identified the deficiency. It was NOT fixed in SP17. Now we are told the runstats piece MIGHT be corrected in SP18 (due out February 2009) and the reorgs MIGHT be corrected in SP19. We will have been waiting well over a year for this basic functionality that works with other supported SAP DB platforms.

Best of luck!

Brian

thomas_vogt
Advisor
Advisor
0 Kudos

Vladimir,

This forum is no replacement for SAP message processing. If there's any problem please send the still open problem ticket back to SAP.

In addition, please don't expect any response to unknown Yahoo mail accounts especially if the corresponding problem ticket has been opened by such a customer.

Brian,

It would have been fair if you would have published the complete story and told the community that note [1278135|http://service.sap.com/sap/support/notes/1278135] fixes the runstats and reorg problems for double stacks. We were in direct contact with your company and didn't get any negative feedback so far regarding this functionality.

Regards,

Thomas

brian_walker
Active Participant
0 Kudos

Thomas,

Agreed. It is fair to say, however, that until we openly complained, there was no solution offered at all for at least 6 months (between SAP_BASIS SP16 and SP17) and then the solution was still not delivered with SAP_BASIS SP17. Thus far I believe my colleague Andy has not had a success even after applying SAP note 1278135, but he continues to work with the SAP developer.

There is also the entire issue of how much longer SAP support packs take to apply with DB2 on z/OS as the database compared to other platforms. Though SAP and IBM continue to look at this issue for us, as of yet we have no solution and so our maintenance windows are twice as long as they could be.

It is understandable that with the small percentage of market share, there may be less resources dedicated to the platform and issues may take longer to resolve. Potential customers should be made aware of both the pros and cons of using DB2 z/OS for SAP.

Regards!

Brian

Former Member
0 Kudos

Dear Thomas,

I agree that it is a very small or not a problem at all...

Please, pardon my attempts to help...

Thanks and best regards,

Vladimir

Former Member
0 Kudos

Dear Brian,

thank you for your advice....

I quite understand the problem miserliness in comparison with the whole great DB2 content...

With best regards,

Vladimir

brian_walker
Active Participant
0 Kudos

Indeed. SAP has delivered in note 1278135 the ability to finally run reorgs and runstats on non-SAPR3 schema objects in DB2. Unfortunately this works only in the local SAP system, so for now we have no way to perform reorgs and runstats in our java-only systems like Portal aside from doing them outside of SAP. Hopefully this additional functionality will be delivered eventually.

Brian

Former Member
0 Kudos

Hello!

In the form of calculate_time, updated by note 1280173, if the calculated time value doesn't contain days, then it begins with a space... It works differently in different installations and it is a common problem (not only for DB2). In any table any text column with leading spaces is sorted either properly or not...

I guess that it depends on some global system parameters (perhaps, install/collate/active or some others), but I cannot alter the default setting in these installations in order to change the situation.

Anyway, I'm sure that such a correction should be universal and don't demand any change of the default global settings.

If to place the letter 'd' for days in the first position then it always will come ahead of leading zeroes or spaces of other format.

With pardons and best wishes in the New Year,

Vladimir

Edited by: Vladimir Shvets on Jan 5, 2009 7:15 AM

Former Member
0 Kudos

Try note 1280173