Re: DFU Runtime

[glea@xxxxxxxxxxxxx]

Rick,

Thanks for the pointers.  I was all excited, thinking I finally had this 
problem solved.  This DFU is used to enter product vendors.  We don't have 
a lot of vendors and new ones are added very seldom.  When they have any 
they send me an email and I add them since they can't use the DFU anymore. 
 So I am especially interested in getting the problem solved.

The menu actually is running CHGDTA and not UPDDTA.  However, I figured 
there was  some problem when the DFU was created umpteen years ago so I 
went through the steps you suggested.  When I moved it to the production 
box I still got the same error.  I'm not going to quote the whole error 
message but essentially it says my license has expired to use 5769PW1, 
license therm V4R4M0, feature 5050 which translates to Application 
Development ToolSet/400 -SEU.  I'm getting this message because we bought 
this machine used and no one bothered to remove this stuff before selling 
the box to us.  Perhaps I should remove this licensed program from the 
system and it will no longer go there?

Yeah, I know it's ugly but this is the only DFU that's being used and, 
like I said, it's not being used very often (actually, not at all since 
the users can't get to it anymore). :- )

Still stumped.

Gary S. Lea 
Applications Group Manager 
Dexter Magnetic Technologies, Inc. 
Tel: 510-668-4645 
Fax: 510-668-5425 
glea@xxxxxxxxxxxxx

Visit Us On Our Newly Redeveloped Website:
www.dextermag.com 
------------------------------

>------------------------------

>message: 3
>date: Wed, 19 May 2004 08:00:56 -0500
>from: rick.baird@xxxxxxxxxxxxxxx
>subject: Re: DFU Runtime


>Gary,

>I assume that your menu is running a UPDDTA command instead of CHGDTA,
>correct?

>DFU runtime is just like any other utility/language - develop on 1 box,
>save objects, run on another box

>STRDFU and take option 2 - Create a DFU program.  taking all defaults 
will
>produce a runtime program very much like those created by option 5 (or
>UPDDTA), and there are a lot of other options to improve your DFUs.

>creating a DFU program creates 2 objects: a *PGM and a *FILE (both with
>subtype 'DFU') - the file is actually a display file.   save those 
objects
>on the development box and restore on production.

>Call the DFU runtime using the CHGDTA command.

>as an aside, while DFU can very powerful and with practice, you can 
create
>some pretty cool and very functional DFUs, they are possibly the #1
>contributor to the myth that the as/400-iseries-i5 is old fashioned. They
>are not intuitive to use, offer very little in data validation and are 
just
>plain UGLY.

>but that's just my opinion.

>Rick