RE: JOBD for a trigger proram

Anyone can make a mistake.  Hopefully your DBA, operator, or whatever you 
called the implementer would roll the application out correctly.

However, if I hadn't tried to do this one thing outside of our change 
management software, perhaps I wouldn't have had this issue?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"John Earl" <john.earl@xxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/03/2003 01:14 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: JOBD for a trigger proram








 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of Buck
> Sent: Friday, October 03, 2003 11:02 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: JOBD for a trigger proram
> 
> > Never name the trigger program the same as the file
> though.  First time
> > you go to update the trigger program and you do a
> RSTOBJ, don't specify
> > *PGM, and end up also restoring the test data from the
> development machine
> > over the top of your production data, you learn fast.
> 
> Another reason developers should not have authority to
> production database
> files?
>   --buck


Amen!



--
John Earl | Chief Technology Officer
The PowerTech Group
19426 68th Ave. S
Seattle, WA 98032
(253) 872-7788 ext. 302
john.earl@xxxxxxxxxxxxxxxxxx
www.powertech.com 
 
 
--


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.