
{
{    The purpose of this request is to add a BTF/VE task entry to the
{    clients list of BTF tasks.
{
{        NFP$ADD_BTF_TASK_TO_LIST (TASK_ID, QUEUE_ID, NETWORK_ADDRESS,
{              BTFS_DI_TITLE, STATION, DEVICE, WAIT_LIST, WAIT_ACTIVITY_LIST,
{              WAIT_LIST_SEQUENCE, WAIT_ACTIVITY_LIST_SEQUENCE, NEW_BTF_TASK)
{
{  TASK_ID: (input) This parameter specifies the task identifier for the
{        BTF/VE task that is to be added to the clients list.
{
{  QUEUE_ID: (input) This parameter specifies the job local queue which
{        is used for communication between the BTF/VE task and the parent
{        task.
{
{  NETWORK_ADDRESS: (input) This parameter specifies the BTFS/DI network
{        address that BTF/VE will connect to for the file transfer.
{
{  BTFS_DI_TITLE: (input) This parameter specifies the BTFS/DI title.
{
{  STATION: (input) This parameter specifies the name of the station
{        or remote system that the device or stream is associated with.
{
{  DEVICE: (input) This parameter specifies the device or stream that the file
{        will be transferred to.
{
{  WAIT_LIST: (input, output) This parameter specifies the list of activities
{        that the client is waiting for.  One of these activities is job local
{        queue messages from BTF/VE task(s).
{
{  WAIT_ACTIVITY_LIST: (input, output) This parameter specifies an association
{        list for the wait_list.  Each entry in the wait_activity_list
{        contains detailed information, with each entry in the
{        wait_activity_list corresponding to an entry in the wait_list.
{
{  WAIT_LIST_SEQUENCE: (input, output) This parameter specifies the sequence
{        where the wait_list is stored.
{
{  WAIT_ACTIVITY_LIST_SEQUENCE: (input, output) This parameter specifies the
{        sequence where the wait_activity_list is stored.
{
{  NEW_BTF_TASK: (output) This parameter specifies the btf task that
{        will transfer the data.
{
