Re: Test data laziness :)

You wrote:
>>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?<<

Perhaps our situation is unique.  We have 18 AS/400's.  Our development 
machine, GDISYS, has the most disk.  We have to support multiple flavors of 
BPCS and a few other software packages.  Here is a list of our system sizes, 
except for one tiny as/400 that is dialup:
SYSTEMNAME  SYSTEMASP
                (meg)
 GDISTAFF      7,086 
 GDIPPL        6,016 
 GDIATJ        6,093 
 GDISYS       81,013 
 GDIHQ        38,035 
 GDIMST        5,099 
 GDIDAT        8,038 
 HEI          19,067 
 GDISTEEL     19,806 
 GDIIOWA       3,934 
 GDIEDI        8,038 
 GDIHMI       12,058 
 GDILYALL     12,058 
 GDIFAX        1,978 
 GDI           7,086 
 TLA          18,048 
 GDIMAIL      30,054 

So in our case disk is no problem.  To transfer files depends on line speed and 
the volume of your data.  If you think you can do it electronically, then I 
would recommend saving it into a save file, including your logical files.  
Sometimes what we do is ask for a backup tape.  We use a different tape for the 
5 nights of the week, times two weeks = 14 tapes.  We just put their whole data 
libraries on the test system.  The cost of RAID5 AS/400 disk space is 
$0.60/meg.  To us the cost of whittling down files just doesn't pay.  You spend 
all that money on labor to reduce the quality and variety of your test data and 
reduce the effectiveness of volume testing.
+---
| 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
+---