How about taking a look at the DISPLAY_JOURNAL UDTF that is available
since sometime in 6.1? Here's a URL to an example of its use -
On 12/11/2013 10:07 AM, Stone, Joel wrote:
After DSPJRN command to an outfile named "jrnflALL", I want to reduce ALL the journal records to only the oldest and newest pair (for each JOOBJ/RRN).
So if Sally changed "Vanilla extract" item #123 from 2 oz to 201 oz to 20.01 oz to 2.01 oz throughout the weekend, I want to reduce that to the oldest BEFORE journal image and the newest AFTER image when extracting the journal Sunday evening - to identify NET changes to that record.
I am using the following SQL and it works well.
INSERT INTO JRNFLB4AF
select * from jrnflALL
where joseqn in(
select min(joseqn) from jrnflALL
group by joobj, joctrr
select max(joseqn) from jrnflALL
group by joobj,joctrr)
order by joobj,joctrr,joseqn
So IT ops did some maintenance Saturday night and IPL'ed. This reset the JOSEQN back to 1 for new journal writes.
Now the SQL stmt returns misleading info. The min JOSEQN is no longer the EARLIEST journal record.
- How does JOSEQN reset - does an IPL cause this?
- What is a good workaround? Should I always add 1,000,000,000 to JOSEQN when processing? Will this do the trick (forcing the post-IPL sequence numbers to the end)? Or is that problematic?
- Should I add JODATE || JOTIME to the min and max stmt?
Any ideas would be appreciated.
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com