A fix is available
APAR status
Closed as program error.
Error description
Bad format string for the default timestamp value in lookup causing fatal error Format '%yyyy-%mm-%dd %hh.%nn.%ss.ff6': the tag %ss is not composed properly.
Local fix
This fix is included in 8.0.1 fixpack 3
Problem summary
**************************************************************** USERS AFFECTED: oeacle ee stage lookup on all rel/platforms **************************************************************** PROBLEM DESCRIPTION: Bad format string for the default timestamp value in lookup causing fatal error Format '%yyyy-%mm-%dd %hh.%nn.%ss.ff6': the tag %ss is not composed properly. **************************************************************** RECOMMENDATION: Apply patch provided. ****************************************************************
Problem conclusion
The format string has error. It %ss.ff6 should actually read %ss.6
Temporary fix
Comments
APAR Information
APAR number
JR35315
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-12
Closed date
2010-01-19
Last modified date
2010-12-09
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
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R810 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021