ca.portal.admin

Re: [IDMSVENDOR-L] Journal extracts to flat files

Discussion created by ca.portal.admin on Apr 5, 2007
doesnt CULLJRNL handle all the piecing back together due to
restructures/fragments? if not, it would seem to make the JREPORT reports
rather suspect .....





This is Chris Hoelscher and I approved this message!

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com



The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you receive
this material/information in error, please contact the sender and delete or
destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Journal extracts to flat files
"doesnt CULLJRNL handle all the piecing back together due to
restructures/fragments? if not, it would seem to make the JREPORT reports
rather suspect .....





This is Chris Hoelscher and I approved this message!

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com



The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Journal extracts to flat files
"Nice job dealing with spanned records!

One (OK, maybe 3) caveat(s): after you get the journal images from the
below, you still have to deal with pasting SR4 fragment chains back together
(for variable length records), SR2/SR3 (relocated records after a
restructure), and compressed images (from COMP or other compression
packages): assuming you're trying to create something approaching a native
record image.

For SR4s, you'll need to capture and past all the pieces together along with
the root.

For SR2/SR3s, I forget where the original record ID is held; if it's in the
SR3 no problem. If it's in the SR2, you'll need some post-processing to
reach back into the database to see what kind of record you have. This is
due to the fact that you may only get the SR3 in the journal, as no changes
will have taken place to the SR2. Easiest solution is to not have any
relocated records.

Since (see earlier discussion) IDMSDCOM is written using system mode calling
conventions, you have to set up something that looks enough like a system
mode environment to call it: (R9 points to something that looks like a TCE
stack, R10 points to something CSA-like, etc). It can be done, as the
unnamed commercial products have solved this.

Don Casey

Outcomes