510-30
12/11/07

TBT :
User's prefix can now be changed within application program.
For EDI400 locks can now be different while sending and receiving
TBT/400 commands are simplified
WebTBT Release 2.25

510-29
17/09/07

TBT :
Compatibility with WFTPD
Problem within calling a server using TBT protocol, if server does not use this protocol
Dynamic creation of TBT partners (DNS use)
WebTBT Release 2.24
Within TBT protocol direct call of remote program

510-28
16/07/07

TBT :
WebTBT Release 2.23 (some optimizations)

510-27
02/07/07

TBT :
WebTBT Release 2.22 (some optimizations)
Installation procedure modified
FTP error messages are modified (within english version).

510-26
18/06/07

TBT :
New Default values for Graphnet servers.
Problem on IPSIFSSECU command fixed.
New transcodification table
"Langid" "Cntryid" "Ccsid" attributes from user linked to queues are now userd.
New parameter on IPSEDI400E Command : EDI/400 partner and TBT/400 can now be differentp
New retry logic on X25 calls : almost all causes are now with retries.

510-25
19/03/07

TBT :
Add *WSCST

510-24
13/03/07

TBT :
*NONE value within hostname means no IP address.
Within X400 field's length problem is solved..

510-23
08/02/07

TBT :
Within PeSIT SSL : two possibilities for SSL frame coding are defined; a parameter alows now to choice (within customer mode). Within server mode choice is dynamic.

510-22
22/01/07

TBT :
Within PeSIT, for a 'no callable 'X25 partner a bad X25 address was set in the directory. After Stop/Start messages in queue for this partner were lost.

510-21
11/12/06

TBT :
IFS Save/restore can now made in DBCS
For directory creation, owner has now all rights.

510-20
23/10/06

TBT :
List format for FTP server can now be defined.
New commands for managing security on a whole directory

510-19
09/10/06

TBT :
API QSYCUSRS is now user to get users's special attributes : compatibility with group profiles

510-18
24/07/06

TBT :
Within TBT protocol compression level can now be choosen

510-17
29/06/06

TBT :
New option for impose D level within PeSIT
Integration zlib 123

510-16
21/06/06

TBT :
Add new parameter password within IPSCHGSIGN command
Correction within spool transfers
New commutation rule within PeSIT protocol

510-15
14/06/06

TBT :
Add *WSCST objects

510-14
04/05/06

TBT :
Semi automatic backup IP -> X25 for X400 OFTP PeSIT TBT protocols

510-12
04/05/06

TBT :
Problem with sourcefile numbers within ccsid 819
Problem with application suppress

510-11
18/04/06

TBT :
Spools Save / Restore
Tiff, Pcl, Gif Spools sending
SMTP customer
New subsitutions
All objects within TBT subsystem are renamed

510-06
06/06/05

TBT :
Some "antiflood" controls within TCP/IP
Direct access within supervision so sending Job
Alert exit can now use IP address and hostname

510-05
08/03/05

TBT :
Access to TBT/400 internal Tools
Ccsid available within creation in IFS
Signon change API

510-04
07/02/05

TBT:
Integration of the zlibcompression library (see http://www.gzip.org/zlib/ )
X400 and ATLAS440:
Modification of the X400 identifier (date in light)
Modification of the ATLAS440 reception module (removal of the country code, the administrative domain, the private field of the X400 identifier)

510-03
07/01/05

TBT:
Directry scan with a program called object by object
Etebac client :
Dynamic allocation using IFS for incoming files

510-02
22/12/04

TBT :
Alerts using E-Mail and/or SMS.
Commutation within receiving files on dsnames like TEST.xxx.yyy (OFTP and FTP).
IFS :
Directory prefix is now a parameter.
FTP Client:
Within receiving file, commutation on dsname is now allowed.
FTP Server:
List command answers now with an "Unix like" list (compatibility with some FTP clients).

510-01
01/11/04

TBT :
Full multi environnements management,
IFS management,,
Full directory dynamic creation,,
Full management on Object security,
Extensions on supervision,
New possibilities for received files management,
New possibilities for CCSID management,
.....
MultiTBT : All links dynamic creation
X400 : Fax support, MTA identified by hostname, .....,
......

410-66
21/10/04

MultiTBT : On incoming messages, Target application is transmitted to Remote TBT/400
X400 : Local UA's can no belong to more that one private domain.

410-65
07/07/03

Atlas Trap (Atlas400, when initiating calls, sends superflous isolated X25 streams  : 0D250D250C0D25 ; a "trap" was introduced within TBT/400 for showing them..) . Problem is now corrected.

410-64
11/06/03

FTP Server :  Answer 500 on  EPSV et EPRT requests
Purge : Some events were not deleted..

410-63
30/05/03

Optional logging on Syslog server.
Selective TBT historic cleanup.

410-62
30/04/03

TBT
TBT/400, within TBT protocol, allows now acknowledgements propagation.

410-61
21/11/02

Odette and X400 Some fields within X400 and Odette protocols were allowed during partner's definitions, but not used. (Minor modification).

410-60
08/11/02

PeSIT (Some softwares ignore negociated limits (Synchronisation interval). TBT/400 in these conditions cancelled current transfers using  IDT frames; now these limits overflows  are accepted, and a diagnostic message is sent, but transfer continues..

410-59
08/10/02

Atlas Trap (Atlas400, when initiating calls, sends superflous isolated X25 streams  : 0D250D250C0D25 ; a "trap" was introduced within TBT/400 for showing them..)

410-58
22/07/02

Rerouting function (A new rerouting function has been introducted, allowing processors without external communication ways to route messages thru a dedicated CPU.

410-57
12/07/02

incorrect API retun-code (sometimes, API return-code was false, so applicative program had unpredictable results.

410-56
03/07/02

Usage of P1 as default value for P2 (sometimes, within X400, P2 is not fed. P1 is used as a default value for defining Sending UA and Receiving UA.)

410-55
09/04/02

New parameter IPSEMI, at local and global level (global TCP/IP parameter and partner's definitions), this parameter defining size used by TBT/400 for sending strings  (all protocols).

New "PC"  return-code within processing programs. This code allows to call later Update API, with a new aknowledgement code, allowing so differed return-code process..

FTP customer for "Mget" processing : Two retry levels are used :

1. First, for elementary retrieve : 10 tries with 5 seconds delay

2. Second, during destructive Mget process, with communication ending and later recall.

FTP Customer - SSL support: SSL usage within  FTP can be processed on two ways : Opening a TCP/IP session with immediate SSL usage, or opening a TCP/IP session without SSL, and SSL usage negotiation. TBT/400 can use now the two ways, and can interact with OS/400 FTP (V5R1M0 release).