Enter your search terms Submit search form
	Web pdp-10.trailing-edge.com

                       FTS-20 v1.0 Beware File
                       =======================

1.0 MAJOR DIFFERENCES FROM NFT

 1.1	The access information defaults for FTS are different from  NFT.
	If you do not specify any access information, or request it with
	a switch such as /ACCESS, no access information will be sent  to
	the remote  system.   This  will  cause  that  system's  default
	account to be used, if  there is one.  If  you wish to have  FTS
	prompt for  account  information  for all  nodes  not  otherwise
	specified, use  SET DEFAULT /ACCESS.   This may be  put in  your
	FTS.INIT file.

 1.2	The use of switches on MACY11  files is as documented, which  is
	different from the way NFT  interprets the switches of the  same
	names.

	Where in NFT one would type:

	NFT>COPY MACY11.FILE/MACY11 PDP11::MACY11.OBJ/VARIABLE/IMAGE

	The corresponding FTS command is:

	FTS>COPY/MACY11/VARIABLE MACY11.FILE PDP11::MACY11.OBJ


	and for FIXED MACY11 files:

	NFT>COPY MACY11.FILE/MACY11/FIXED PDP11::MACY11.OBJ/FIXED/IMAGE

	and

	FTS>COPY/MACY11/FIXED MACY11.EXE PDP11::MACY11.EXE

 1.3	RSX and  VMS systems  use ";"  as the  delimiter for  generation
	numbers.  This is  different from  TOPS-20, and if  you wish  to
	specify an explicit  generation number (they  call it a  version
	number), it is necessary to quote the filespec, or to quote  the
	; with control-V.  ";*"  is an exception,  and may be  specified
	without quoting.


2.0 KNOWN BUGS AND DEFICIENCIES

 2.1	Cancelled requests  are not logged  in the user's FTS LOG  file.
	They  are  logged,   however,   in  the  system  log  file,  and
	/NOTIFY:MAIL will also notify you of cancellation.   The same is
	true of requests that fail because the deadline expired.

 2.2	The /QUEUE switch, without a keyword argument,  does not default
	properly.   /QUEUE:YES  works correctly, as does  /QUEUE:NO.  To
	make  /QUEUE default to  /QUEUE:YES,  apply the following patch:

	P.AUF+5/  0	QUEUE
	P.AUF+6/  0	1

	/QUEUE:YES is in effect by  default normally anyway, so  usually
	it is unnecessary to specify it.

 2.3	SHOW DEFAULTS  does not  print defaults  for /LOG,  /NOTIFY  and
	/QUEUE.

 2.4	If the load on your system is extremely heavy, you may need to
	increase the IPCF timeout for FTS.  This is the amount of time
	FTS will wait for a response from the spooler.  You have this
	problem if you get the following error message:

	?FTS20: FTS event 16: cannot receive IPCF from master FTS job
	-	TOPS20 error code 601017: No message for this PID

	To double the timeout, apply the following patch:

	IP$$JS+42/ CAIG 4,170	CAIG 4,360

	You can use an even larger value if necessary.

 2.5	The "STOP" command will only stop the spooler if it is issued to
	the master FTS.   That is the  copy of FTS  that was issued  the
	START command must be the one  that is issued the STOP  command.
	This can be done by  ADVISEing  the job, or attaching to PTYCON.
	This is not a bug, but is noted here for emphasis.


3.0 RESTRICTIONS AND KNOWN BUGS IN RELATED PRODUCTS

 3.1 KNOWN BUGS AND RESTRICTIONS IN FAL IMPLEMENTATIONS

	Certain FTS functions are not supported on some remote operating
	systems, due to restrictions in the FALs on those systems.  This
	is subject to change, as a  new release of network software  for
	those systems may add new functionality.

  3.1.1	The DIRECTORY command will  return the size of  the file in  128
	word blocks  if the  remote system  is a  TOPS-20 system.   This
	causes the file size to appear to be 4 times as big as expected.
	This is due to a bug in the TOPS-20 FAL.

  3.1.2	Currently the FAL on TOPS-20  will not support RENAME or APPEND.
	Thus you may not rename or append to a remote file on a 20.

  3.1.3	The FAL on TOPS-20 does not support RMS VARIABLE or FIXED record
	format either, but these files can be created in BLOCK mode  and
	BLOCK mode is  the default, so  this is no  problem.  It is  not
	necessary, and usually not desirable to specify any datatype  or
	record format switches for transfers between TOPS-20 systems, as
	BLOCK mode is faster.

  3.1.4	RSX, VMS, and IAS may treat APPEND requests as if they specified
	/OLD  (giving  file-not-found  errors if the file is not there).
	This is a FAL problem on those systems.

  3.1.5	Do not use /ASCII/BLOCK.  This  confuses FAL-20.  FAL will  then
	send IMAGE,  but FTS  expects ASCII,  so the  file resulting  is
	incorrect.


 3.2	RESTRICTIONS AND KNOWN BUGS IN RMS-20

  3.2.1	Due to a  restriction in  RMS, if  a file  is open  for read  by
	another job, FTS will get 'Invalid Simultaneous Access' when  it
	tries to read the  file.  The request is  not re-queued in  this
	case.

  3.2.2	It is  not possible  to supersede  an existing  generation of  a
	local file.  It is possible to create a new generation, and this
	will happen by default.  However,  if an existing generation  is
	specified for a local file,  an error message will be  returned.
	This is an RMS-20 restriction.