[fredbastiani]

Hi,

I use cft 2.3.2
CFT informations :
* product = CFT/V2/UHPUX 11.00L
* version = 2.3.2
* level = m-2-2
* upgrade = 7343 7582 7652 7663 7709 7715 7718

And my problem is this one:

I receive few files in bad naming rule like this one for example:
We are in March and normaly the fist letter of my file have to be a "C"
And it's not the case:
rw-rw-r-- 1 cft cft 139008 Mar 31 01:45 E0720485
-rw-rw-r-- 1 cft cft 1657344 Mar 31 01:46 E0720512

Do you have a solution ?

Thanks a lot.

[niko]

The name of your file is set with the variable &idt
Ex: fname = <path>/&idt

I also suppose that your problem relates to a specific partner.

I have a similar case with a partner whose system time is ahead. Upon receipt, the variable & idt which I used for file names is ahead of 36 hours from the time of my system.

A file arriving future is always something frightening, isn’t it !

Best regards,
Niko.

[fredbastiani]

Thanks for this idea....I have to check with my partner if his server have a good time....

[Christophe A.]

WARNING !

The IDT parameter is logicaly created by the sender of the file.
The IDT is based on Month for the first character, and Hour, Mins, ... for other.

BUT :

If the sender send many many many files, the IDT will "grow" without looking for the current time !
So, you can have IDT "in the future"...

It's very dangerous to determine the date and time of a transfer based on IDT.

You have to use for your FNAME parameter some of &FDATE (or &FTIME, &FMONTH, &FDAY, ...) &CDATE (or &CDAY, ...) &EDATE (or &EDAY, ...) to determine the correct values.

Good luck