| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000702 | FL5 | 2.2 Subprogram FLUC (CONV) | public | 2015-06-29 10:53 | 2015-07-02 17:37 |
|
| Reporter | Falk Reichbott | |
| Assigned To | Falk Reichbott | |
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | assigned | Resolution | open | |
| Platform | System z | OS | z/OS | OS Version | V1R13 |
| Product Version | 5.1.06 | |
| Target Version | 5.5 | Fixed in Version | | |
|
| Summary | 0000702: Support of relative generation number for GDG PO libraries |
| Description | Currently relative generation numbers '~.GDG.PS(-1)' are only supported for PS data sets. The resolution is done by the data management system. The GDG concept are also available for PO datasets. But in this case the absolute GDS name must be used. I this case FLAM works like each other tool on z/OS.
If we do the resolution of the relative generation number our self, then relative generation numbers als also possible for PO libraries. A possible syntax could be the separation of relative generation number from the member name by a comma.
for example: '~.GDG.PO(-1,MEMBER)'
|
| Additional Information | This support requires the use of catalog field attribute:
GENLEVEL GDG generation level — 1 for each active generation in EBCDIC format c'0000'
The lengt field must be divided by 4 to determine the amount of generations for this group. Dependent on the relative generation number the correct index must be calculated and then the absolute name can be build using the correct generation ~.GDG.PO.GnnnnV%%(MEMBER). |
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships 