I'm using FNDLOAD to port a concurrent program definition between 2 environments.
The program definition currently exists in the target environment, however the changes in the source env are the addition of new parameters.

However when i run the upload into target it is not updating anything.
I know how to use FNDLOAD (we're old friends), and am using it thus...

FNDLOAD apps/apps_pwd@env 0 Y UPLOAD afcpprog.lct my_dat.ldt

I am also using the following additional options on the command line...
WARNINGS=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

and i have even gone as far as editing the LDT file to ensure every occurrence of LAST_UPDATE_DATE reflects today's date to make it think that every item of the definition has changed.

There are no warnings produced in the log file.

Any further clues would be appreciated

Does the executable exist on the target instance? Also, if any of the parameters use value sets, do those value set definitions exist on the target?

*reaches for coat, hails taxi*

Of course, prize for the bl&^din' obvious suggestion of the week must go to:

Is there sufficient space/privilege to actually write the log file?

Yes

The real solution is to make sure the source and target versions of the LCT file actually match!

Source was 115.39
Target was 115.40

Oh, and according to Metalink, the correct use of the optional parameter on FNDLOAD is...

FNDLOAD apps/apps_pwd@env 0 Y UPLOAD afcpprog.lct my_dat.ldt - CUSTOM_MODE=FORCE

Note the subtle extra '-'

A combination of the two has got the LDT file to load.

Hi,

CUSTOM_MODE=FORCE , As you are uploading ldt file in Force mode will not produce any warning messages.

Remove that, you will get the messages

Even without the CUSTOM_MODE=FORCE there are no messages generated to say why the LDT was not loaded.

Anyway managed to get it through

It is possible that there are certain objects like Value Sets added to source which don't exist in target. FNDLOAD usually doesn't complain about such errors. I'm using MigrationLogiK tool, which helps to automate migrations across EBS instances.