Re: WRKDBF and V6R1

[Troy Foster <tfoster@xxxxxxxxxx>]

Answer from Mark Waterbury on delete

Assuming all of the parameters of UNDEL2 are the same as they were for 
UNDEL, this should work ...

But, rather than renaming, I would create an "alias", e.g. CRTDUPOBJ of 
the UNDEL2 *CMD, calling it UNDEL. Then, you can put it in whatever 
library where the original UNDEL was located ... or perhaps in with WRKDBF?

   CHGCMD UNDEL   PGM(undel2lib/UNDEL2R) PRDLIB(undel2lib)

where "undel2lib" is the library where the new UNDEL2 is installed ...

See the instructions in the UNDEL2 readme file  here ... 
http://www.think400.dk/files/undel2_readme.txt  -- it shows the CHGCMD 
and also changing the command's PGM parameter to point to the correct 
library to find the CPP program (UNDEL2R).

HTH,

Mark S. Waterbury



On 2/21/2008 4:14 PM, Jon Paris wrote:
> It would appear that at least some of the functions in WRKDBF that  
> prevent it from converting to V6R1 should also cause problems in V5R4  
> - anyone had any experience with using it on that release?
>
> Apart from functions like resuscitating deleted records, what are the  
> other features that are missing from the alternatives such as DFU and  
> Navigator?
>
>
> Jon Paris
>
> www.Partner400.com
> www.SystemiDeveloper.com
>
>
>