FLAM Issue Tracker - FL5
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000177FL52.2 Subprogram FLUC (CONV)public2013-09-12 07:492015-04-15 15:06
ReporterFalk Reichbott 
Assigned ToFalk Reichbott 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusresolvedResolutionno change required 
PlatformSystem zOSz/OSOS VersionV1R13
Product Version 
Target Version5.2Fixed in Version5.1.05 
Summary0000177: Support of Generation Data Groups under z/OS
DescriptionCurrently we support all Kind of file organisation and record formats (except LDS) but no GDG.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-09-12 07:49Falk ReichbottNew Issue
2013-09-12 07:49Falk ReichbottStatusnew => assigned
2013-09-12 07:49Falk ReichbottAssigned To => Falk Reichbott
2013-11-07 10:31Falk ReichbottTarget Version5.1 => 5.2
2014-04-28 10:15Falk ReichbottTarget Version5.2 => 5.3
2014-09-08 10:42Falk ReichbottTarget Version5.3 => 5.2
2015-01-12 14:13Falk ReichbottNote Added: 0000719
2015-03-22 15:46Falk ReichbottNote Added: 0000778
2015-03-22 15:46Falk ReichbottStatusassigned => resolved
2015-03-22 15:46Falk ReichbottFixed in Version => 5.1
2015-03-22 15:46Falk ReichbottResolutionopen => no change required
2015-04-15 15:06Falk ReichbottFixed in Version5.1 => 5.1.05

Notes
(0000719)
Falk Reichbott   
2015-01-12 14:13   
Generation data groups can be used with full qualified names and with relative names (+-n or 0).
(0000778)
Falk Reichbott   
2015-03-22 15:46   
GDG's are working without any problem. Static and dynamic allocation works fine. With version 5.1.5 the wildcard support also supports GDG's:

For example:
   file='<SYSUID>.*(-1))
This will work for a GDG's in the current user and will select ony the generation -1.