Re: Area/Record security.

Discussion created by ca.portal.admin on Jun 22, 2007

Turning on journal retrieval just creates BGIN and ENDJ checkpoints on
the journal for retrieval rununits. There are no journal images for
record access. However, for update rununits, your Journal Reporter is
absolutely great!

The most widely used solution for this type of request is really, as
Chris pointed out, using a dbproc tied to all access commands on a
record. The dbproc writes a journal record identifying the type of

Laura Rochon
Ajilon Consulting

Jim Phillips wrote:
We can supply a program, at sensible cost, to provide a formatted
report of=
changes to the record using the journals. I suppose we could also
report o=
n retrieval access to it but turning on retrieval journaling just for
this =
is a bit tail-wagging-dog.=20

Date: Thu, 21 Jun 2007 22:23:39 -0400> From: pierra@SPRYNET.COM>
Area/Record security.> To: IDMS-L@LISTSERV.IUASSN.COM> > greetings
from th=
e perplexed.> > I've got a situation where we need to track access to
1 (an=
d only 1)> record/area (we're a 1 record to 1 area (mainly) shop.)> >
We ne=
ed to see all who read/modify/update/store or erase. Batch and
online.> > W=
e're a IDMS 16.0 SP1 (No DC and minimal UCF) / CICS shop with DMLO
(too> mu=
ch), OLQ, Culprit and a home-grown> data unloader.> > OLQ security is
d on, but Culprit security is not. The sensitive> information in the
given =
record is secured by> encryption and de-encryption is handled in a
"" schema/subschema> combination.> > Any ideas?> > Dick Pierce> Mass
y of Motor Vehicles> 617-973-8911> > 3 million transactions a day and
we ju=
st keep growing.> > While I approve of this message, I'm not running
for an=
Connect to the next generation of MSN Messenger=A0

IDMS Public Discussion Forum


Re: Multiple DBL4 jobs
"Yes, splitting the dbl3 output for multiple parallel dbl4 runs works in
R15 and r16 ... You normally split on area boundaries.

splitting on file boundaries is possible, but relocated and/or variable
length records may span files (for some strange reason dbl4 reads the
prefix and complete record) - so turn off dynamic allocation and rerun
any dbl4 that failed (after all the others complete) with all the area
file dd's - dbl4 will lock the area, so don't forget to provide a 1
block lock page file for all of the parallel runs except the first file
of the area -

We use culprit to generate the syncsort job to split the dbl3 output -
it generates (area or file level) sort control cards and the sortofnn dd
statements - the sort output file ds names have the idms file ddn in
them to make life easy