Re: Fw: IDDU linked files for S/36 flat files.

Steve,

In a message dated 4/15/99 4:32:34 PM Eastern Daylight Time, mic@aloha.com 
writes:

> Several businesses in town are looking at upgrading their S/36 to a 400
>  (Where have we heard this before) The year/2000 has accelerated this. Has
>  anybody else run into this problem with IDDU on CA/400? You actually "lose"
>  flexibility when you go to the newer version of CA/400 in this environment.
<<snip>>

Hmmm.  Sounds like one or more things were left out.  Never experienced this 
myself, but I've done several /36 migrations in years long past.  First, have 
the IDDU definitions been migrated to the AS/400?  If they're not there at 
all, it would cause a problem of this sort.  Second, have you run the 
IDDULINK procedure in the /36E to link the files to the IDDU definitions?  
Once the latter is done, even DSPFFD will work against a "flat" file...

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"The brain is a wonderful organ.  It starts the moment you get up and doesn't 
stop until you get into the office." -- Robert Frost
+---
| 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
+---