RE: JOBD for a trigger proram

Pretty much what we do also.

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.

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




Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/03/2003 11:55 AM
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






We use the trigger program library for the file lib and put production
trigger programs in the same library as the triggered file.  Retrieve the
program lib from the SDS and you are set to go.  Set the program into a 
dev
lib and it opens/calls development files/programs.

Chris Bipes

-----Original Message-----
From: Scott Mildenberger [mailto:scottmildenberger@xxxxxxxxx]
Sent: Friday, October 03, 2003 9:22 AM
To: Midrange Systems Technical Discussion
Subject: Re: JOBD for a trigger proram


But it sure does make it a pain to run tests on a new version. 
Soft code the library name somewhere (data area, file, user
space, whatever) and make later life a little easier.
_______________________________________________
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.