ca.portal.admin

do other shops have rules against saving DBKEYs ?

Discussion created by ca.portal.admin on Feb 19, 2007
Latest reply on Feb 19, 2007 by ca.portal.admin
I just discovered a job(that predated my employment here) that captures
DBKEYs to a a flat file at 6:00PM saturday nights, and then another job
that runs at 10:30 PM to process this file of DBKEYs (read and process
the
database records)

obvuiously, 2 things can heppen:

1) a record whose DBKEY was captured for future processing can be
deleted
from the database (this is okay if the program is willing to accept the
error code)
2) the database can be unloaded/reloaded between the two jobs and mess
up
everything

well, guess what - the database was unloaded/reloaded between the two
jobs
and at least one record was deleted from the database between the two
jobs
...

do other shops explicitly inform developers.programmers what it illegal
programming habits? or do you assume <always a bad idea) that people who
write code know how IDMS works and how to write a valid batch process???

(there is some attempt to push this as an DBA error - but this is
because
the (globally distributed) developers do not know IDMS and the
ramifications of bad programing ...

thanks,

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] do other shops have rules against saving DBKEYs ?
"Generally, we don't do cross job passing of DBKEY's except in certain
controlled situations.

But read my second paragraph, the application team may have had a
reason--is the first job retrieval only during a peak and the second job
update during off-peak? There may be a justification, but I agree with
you that waiting 4.5 hours for the next job to run is ill-advised.

As for communication, it appears that the onus is on the application
team. Either the application manager did not tell his staff or he told
them and they were not aware of the consequences of an unload/reload.

Dan Miley
Lockheed Martin

Outcomes