Patch-ID# 102206-06 Keywords: FTAM 8.0.2 F-READ-cnf shadow INTAP-1 OID 8-bit escape sequence Stratus Synopsis: Sunlink FTAM 8.0.2 Patch Date: Jun/07/96 Solaris Release: 2.3, 2.4 SunOS Release: 5.3, 5.4 Unbundled Product: SunLink FTAM Unbundled Release: 8.0.2 Relevant Architectures: sparc BugId's fixed with this patch: 1176103 1179191 1196059 1188346 1194403 1178851 1174538 1202158 1179191 1213047 1224370 1245189 1234099 1236780 1241983 1242144 1244109 Changes incorporated in this version: 1245189 1234099 1236780 1241983 1242144 1244109 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: 102205-01 Obsoleted by: Files included with this patch: /opt/SUNWconn/ftam/bin/osiftam /opt/SUNWconn/ftam/bin/osiftr /opt/SUNWconn/ftam//bin/osiftrd /opt/SUNWconn/ftam/bin/ftamtool /opt/SUNWconn/ftam/lib/libftam.a /opt/SUNWconn/ftam/lib/osiftrapi.o /opt/SUNWconn/ftam/lib/locale/C/ftamtool.info Problem Description: In version -06: 1245189: ftam waits for ever when no response from responder to F-TRANSFER-END-Req. FTAM blocks when it does not receive F-TRANSFER-END-Res. A timer has been added which will force an abort when in this situation. 1234099: fti_put() locks-up when receiving the F-CANCEL-Req. FTAM blocks when doing large file transfers and receives an F-CANCEL-Req. This was a protocol error and has been fixed. 1236780: FTAM action result does not conform to ISO. The action result parameter conveys information which summaries that available in the diagnostic parameter. The value is never less severe than the most severe diagnostic value. This has been fixed in the FTAM entity. 1241983: FTAM needless null strings are added to the head of the file. This has been fixed in the FTAM entity. 1242144: FTAM 8.0.2 separate a frame into two parts. The FTAM entity not compliant with ISO 8571-2 Annex B B.1. This has now been corrected. 1244109: FTAM transfer fails with "Bad read". SunLink FTAM was separating a frame into 2 parts. According to ISO 8571-2, the behavior is wrong, SunLink FTAM should not separate a frame into 2 parts. This bug has been fixed. In version -05: 1224370: dir command fails on first use after a new association. In version -04: 1179191: FTAM creates corrupt files when receiving text files from ICL. You can do an ftam 'put' and 'get' on FTAM-1 document type files with embedded escape sequences at the beginning of each record without creating corruptions when the file is written to disk. 1213047: osiftam creates file even when receiving error from responder. The correct ftam protocol response to a F-DATA-END-Req with action result=Permanent Error diagnostic is now observed. In version -03: 1202158: shadow files cannot be redirected to another directory. It is now possible to redirect the writing of shadow files in another directory by the use of setting environment variables else the shadowfile is written in the default directory as described in the sunlink ftam user documentation. In version -02: The fti_move() function has been properly implemented. 1196059: Sunlink ftam does not send back F-CANCEL-Res with Success 1188346: osiftam initiator gives Permenent-error if putting a file onto the HP 1194403: ftam sending format effectors in graphic strings In version -01: With this patch it is now possible to use the new Object Ids for INTAP-1 Text Record File Document Type and for its abstract and transfer Syntax. The enabling/disabling of this feature in the FTAM Initiator (osiftam) is done by the ftamtool. The Responder (osiftr) supports both OIDs. This patch solves some interoperability problems with non-Sun FTAM implementations that use the new OIDs values. 1178851: FTAM 8.0.2 is not compliant with CCITT X216 recommendation ( new INTAP-1 OID ) 1174538: FTAM 8.0.2 does not send any escape sequence to select the correct character set 1176103: FTAM 8.0.2 dir command shows nothing against a Stratus responder 1179191: FTAM 8.0.2 creates corrupted files when they contain 8-bit characters. Patch Installation Instructions: -------------------------------- Refer to the Install.info file for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below as special instructions. Special Install Instructions: ----------------------------- None.