Problem in FTAM put

Question

I am using FTAM version 9.0 (OSI 9.0, x.25 9.1) on Solaris 8. Working with responder FTAM on Nokia DX220 (a PSTN switch).
The FTAM remote database settings are :
APT 1 3 9999 1 7
AEQ 1
PSEL (hex) 0201
SSEL (hex) 0201
TSEL (hex) 0201
I have to put one hex file from SUN Ftam to DX220 Ftam. It works 98 times out of 100 but 2 times the other side receives a corrupted file (content and at times size also).
I faced this problem also using osiftam. The command used is :
put <filename> <filename>I am aware that default doc type is FTAM1 (unstructured text). But as mentioned the file we are trying to put is of type hex. So to me better option looks like FTAM3.
My question is if anyone can suggest why when we put, remote side gives intermittent problems as mentioned above. If the file corruption is due to doc type (FTAM1) then should not the file corruption happen every time? Actually same file if i put again using the same command, in second attempt it is recieved properly by the other side.
Please help. May be the Solstice support group can reply.
Thanks.

Answer 1

user13355933 wrote:
hello guys m practicing PL/SQL when i try to exicute below code i get following error:
DECLARE
I BOOLEAN:=TRUE;
BEGIN
dbms_output.put_line(i);
END;
error:
Error starting at line 1 in command:
DECLARE
I BOOLEAN:=TRUE;
BEGIN
dbms_output.put_line(i);
END;
Error report:
ORA-06550: line 4, column 1:
PLS-00306: wrong number or types of arguments in call to 'PUT_LINE'
ORA-06550: line 4, column 1:
PL/SQL: Statement ignored
06550. 00000 - "line %s, column %s:\n%s"
*Cause:    Usually a PL/SQL compilation error.
*Action:DBMS_OUTPUT.PUT_LINE only accepts strings (VARCHAR2) datatype
what exactly do you expect to see, if in fact it worked as desired?