PK93786: VMM May not PARSE LDAP TIMESTAMP ATTRIBUTE VALUE CORRECTLY

Fixes are available

APAR status

Closed as program error.

Error description

If there is fractions of a second in Ldap timestamp attribute
value, such as 20090803060137.515000Z, virtual member manager
(VMM) didn't parse it correctly, which showed the different
timestamp to client with LDAP server side.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server v6.1 or V7.0 who use federated       *
*                  repositories (virtual member manager).      *
****************************************************************
* PROBLEM DESCRIPTION: VMM may not parse the timestamp         *
*                      attribute of an Ldap server if there    *
*                      are fractions of a second in it.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If there are fractions of a second in an Ldap timestamp
attribute value, such as 20090810162331.937000Z (common in
ITDS Ldap it's 20090810162331.000000Z), VMM does not parse it
correctly. For such timestamp attributes, when getting entity
properties using VMM get() API, a different timestamp with the
LDAP server was returned.

Problem conclusion

The problem has been fixed. VMM can now parse the timetamp
attribute correctly.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.29 and 7.0.0.9. Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK93786
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-13
Closed date
2009-08-21
Last modified date
2009-12-03

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK93786: VMM May not PARSE LDAP TIMESTAMP ATTRIBUTE VALUE CORRECTLY

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?