- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DTR midification suggestions please
Operating System - OpenVMS
1753797
Members
7879
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2009 06:57 AM
11-18-2009 06:57 AM
I am using DTR for querying the records
The file that I am using is of 1536 bytes length and the copybook associated with that file is having header and detail records
(means Detail records are redefined by header records by redefines clause)
so if I am querying the first 10 records with alt-key-type = "4" and it is displaying both the header and detail records
and If I modify all the queried records with a Header field then the detail records are also getting modified.
I dont know why this is happening I can filter the detail and header records separately for querying but
My doubt is that DTR cannot handle these type of false changes
since it will effect mostly in the testing process.
Is there any other way?
and I am using cobol programs for execution
The file that I am using is of 1536 bytes length and the copybook associated with that file is having header and detail records
(means Detail records are redefined by header records by redefines clause)
so if I am querying the first 10 records with alt-key-type = "4" and it is displaying both the header and detail records
and If I modify all the queried records with a Header field then the detail records are also getting modified.
I dont know why this is happening I can filter the detail and header records separately for querying but
My doubt is that DTR cannot handle these type of false changes
since it will effect mostly in the testing process.
Is there any other way?
and I am using cobol programs for execution
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2009 08:05 AM
11-18-2009 08:05 AM
Solution
You have to find a field (column) in there that allows you to distinguish unambiguously which record is a header, which one a detail.
For example, there might be a line number which is 0 for the header. In that case your query should be modified to include a selection clause on that column.
That may look like:
MODIFY xxx WITH alt-key-type=4 AND line-number=0 USING BEGIN ...
If there are no distinguisng columns, only the order, then you may need you nest your queries, selecting the first records first
FOR FIRST 1 xxx WITH ..
IF alt-key-type=4 THEN MODIFY ...
or
FOR outer IN xxx WITH alt-key-type=4
FOR FIRST 1 inner IN xxx MODIFY ...
The presence of RMS keys, total record counts, selected record counts will determine which approach is best.
For further help you probably need to show us some critical columns (4 o 5) from some (2 or 3 ) example data records, perhaps in a .TXT attachment.
Maybe add output from SHOW xxx_REC ... or at least the first part of that showing the redefine.
Maybe add some record count indication and rms key/index pointers.
The record bytes length, the only detail you provided so far, is in fact the least interesting attribute of the file!
Hope this helps some,
Hein.
For example, there might be a line number which is 0 for the header. In that case your query should be modified to include a selection clause on that column.
That may look like:
MODIFY xxx WITH alt-key-type=4 AND line-number=0 USING BEGIN ...
If there are no distinguisng columns, only the order, then you may need you nest your queries, selecting the first records first
FOR FIRST 1 xxx WITH ..
IF alt-key-type=4 THEN MODIFY ...
or
FOR outer IN xxx WITH alt-key-type=4
FOR FIRST 1 inner IN xxx MODIFY ...
The presence of RMS keys, total record counts, selected record counts will determine which approach is best.
For further help you probably need to show us some critical columns (4 o 5) from some (2 or 3 ) example data records, perhaps in a .TXT attachment.
Maybe add output from SHOW xxx_REC ... or at least the first part of that showing the redefine.
Maybe add some record count indication and rms key/index pointers.
The record bytes length, the only detail you provided so far, is in fact the least interesting attribute of the file!
Hope this helps some,
Hein.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP