FLAM Issue Tracker - FL5
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000700FL52.2 Subprogram FLUC (CONV)public2015-06-25 14:202015-06-29 08:25
ReporterFalk Reichbott 
Assigned ToFalk Reichbott 
PriorityurgentSeverityminorReproducibilityhave not tried
StatusresolvedResolutionfixed 
PlatformSystem zOSz/OSOS VersionV1R13
Product Version5.1.06 
Target Version5.1.06Fixed in Version5.1.07 
Summary0000700: Wild cards in PO data sets don't work correctly
DescriptionIf aliases for member used in PO library the wild card mechanism stops at the alias.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-06-25 14:20Falk ReichbottNew Issue
2015-06-25 14:20Falk ReichbottStatusnew => assigned
2015-06-25 14:20Falk ReichbottAssigned To => Falk Reichbott
2015-06-25 18:39Falk ReichbottNote Added: 0000849
2015-06-25 23:02Falk ReichbottNote Added: 0000850
2015-06-25 23:02Falk ReichbottStatusassigned => resolved
2015-06-25 23:02Falk ReichbottFixed in Version => 5.1.07
2015-06-25 23:02Falk ReichbottResolutionopen => fixed
2015-06-26 09:38Falk ReichbottSummaryWildcards in PO data sets don't work corrently => Wild cards in PO data sets don't work correctly
2015-06-26 09:40Falk ReichbottNote Edited: 0000850bug_revision_view_page.php?bugnote_id=850#r232
2015-06-29 08:25Falk ReichbottNote Edited: 0000850bug_revision_view_page.php?bugnote_id=850#r233

Notes
(0000849)
Falk Reichbott   
2015-06-25 18:39   
The problem is not relatet to aliases.
(0000850)
Falk Reichbott   
2015-06-25 23:02   
(edited on: 2015-06-29 08:25)
The problem was a directory record which use the complete length of 256 byte in the PO library. It was a mistake to check if the first byte (containing the high order bits of the length) must be 0x00. This plausicheck results in wrong interpretation of the directory if a record contains 256 bytes of content. The mistake was, to asume that the length field is not a part of the data it self.