Re: Test data laziness :)

[John Carr <74711.77@xxxxxxxxxxxxxx>]

----------
RE:     Re: Test data laziness :)

Tim
Try creating DDM files for the 30.  Run the program on development machine.
Security might not let you do this option.  If it's a report program(
no updates) you might get a way with it.  Creating the 30 this way might
be the easiest, and the program will "run just like in production". 

John Carr


Tim Truax wrote:
> 
> Hello and Happy "belated" D-Day....lest we ever forget.
> ---------
> Here's my question, and feel free to call me a lazy b*st*rd....
> I am working on a LARGE program that produces a large critical report.
> Now this program uses about 30 files, 22 of which are logicals that are
> built over various and sundry physical files.  6 of the files are major
> join files that bring together the data of multiple physical files
> around the production system.  Now, I work on a developement machine
> (hardly any security) that is seperate from the production environment
> (super secured environment) (passthru is the way we can access the
> different systems) this developement machine has bits and pieces of the
> actual types of data that reside on the production machine... but of
> course the data would have to be recreated on the developement machine
> for me to be able to test the program properly.  Is my only alternative
> to just slug it out and collect all these physical file pieces and parts
> and then SNDNETF them to the developement machine into my test library
> and then recreate the logicals that will connect the physical file
> pieces and parts as well as the join files?  Any other suggestions?
> I guess..... I should just sit down for a week and write a program that
> will automatically produce any type of needed data samplings.... Is this
> what you nice people are  gonna suggest?
> ----
> Tim & Dana Truax... and Caleb 4 years old.
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---