SENDFILE

Authorization

General User

Purpose

Use the SENDFILE command to send files or notes to one or more computer users on your computer or on other computers.

SENDFILE is one of several commands that references a userid NAMES file. By setting up a names file, you can identify recipients just by using nicknames, which are automatically converted into node and user ID. For information on creating a names file, see NAMES.

Operands

fn

is the file name of the file to be sent.

ft

is the file type of the file to be sent.

fm

is the file mode of the file to be sent. If * is specified (the default), all accessed disks and directories are searched, and the first file found is sent. This operand can be omitted if the first name would not be misinterpreted as a file mode, or if the keyword TO is used.

TO

is a keyword operand. It can be omitted if the first name is not TO.

nickname

userid

userid AT node

specifies one or more recipients to whom the file is to be sent. If the same recipient is specified more than once, the user receives only one copy of the file.

• A nickname is a short form of a user ID you have defined in your userid NAMES file, where userid identifies your user ID. This nickname may represent a single person (on your computer or another computer), or a list of several people. If a nickname cannot be found in the userid NAMES file, it is assumed to be a fully-specified user ID of someone on your computer. For more information on nicknames, see NAMES.
• A userid identifies a user on your system or another system (node).

  A user ID cannot be AT or “CC:”.

• A node identifies any RSCS node name or TCP/IP host name or IP address. The rule used for determining a node be treated as a TCP/IP address is that it contains a colon, a period or a dot. You may use the TCPEXIT EXEC to change these rules to fit your environment. If the node is determined to be a TCP/IP address it will be treated as such so long as an option other than RSCS is specified. A TCP/IP host name that ends with a period will have the local domain name appended to it in order to construct a fully-qualified host name.

  Non-TCP/IP destinations are sent through CMS or RSCS as necessary, even on the same SENDFILE command, as long as an option other than RSCS is specified. You may freely intermix the userid and nickname forms to specify recipients.

  You may freely intermix all forms to specify recipients. The UFTASYNC, UPTSYNC, and MIME options control how the file is or files are sent to TCP/IP Internet hosts. The options are ignored for RSCS or local addresses.

  If no operands are specified with SENDFILE, a menu is displayed. For more information, see Usage Note 2, Using the SENDFILE MENU.

NOTE

specifies the file is to be sent as a note, this file was created by using the NOTE command. The TO operand and the list of user IDs or nicknames cannot be specified if this option is given. If no file is specified, the file userid NOTE * is sent as a note. (On a display terminal, the PF5 key is set to this option in the NOTE command environment.)

You may freely intermix the userid and nickname forms to specify recipients. If no operands are specified with SENDFILE, a menu is displayed. For more information on this menu, see Usage Note 2, Using the SENDFILE Menu.

Options

Ack

requests an acknowledgment be returned to you and logged when the recipient receives your file (using the RECEIVE command). Acknowledgments are added to your userid NETLOG file. An acknowledgment is sent only if the NEW option is also in effect. This option is ignored for TCP/IP destinations.

NOAck

requests no acknowledgment be returned when the recipient RECEIVEs a file. This is the default.

Filelist

specifies the file (fn ft fm) is a list of files in the format of a CMS exec file produced by the LISTFILE command issued with the EXEC option, or a file saved from a FILELIST command. This option sends multiple files with only one invocation of SENDFILE. Both the file containing the list of files and each file in the list are sent.

Lines beginning with an asterisk (*) and blank lines are ignored. All exec tokens (for example, &1, &2) or any token beginning with an ampersand (&) is ignored.

For information on creating a list of files that can be saved and used to send multiple files, see FILELIST, Usage Note 7, Saving a List of Files.

NOFilelist

specifies the file is not a list of files. This is the default.

Log

specifies the recipients, date, and time of this file transmission are logged in a file called userid NETLOG. This log is updated when acknowledgments of sent files are received (if they were requested). Do not use this option if you have no read/write disk or directory accessed. This is the default.

NOLog

specifies this file transmission is not to be logged.

NEw

specifies header records are added and the file is sent as described below, in Format of the File Sent by SENDFILE. If this option is specified, the recipient must use RECEIVE or NETDATA to read the file. This option is ignored for TCP/IP destinations. This is the default.

Old

specifies the file is sent using DISK DUMP. This option should be specified when the recipient of the file does not have the RECEIVE or NETDATA commands available to read the file. When OLD is specified, no acknowledgment (the ACK option) can be sent. This option is ignored for TCP/IP destinations.

Type

specifies the files sent and the user IDs and nodes to which the files were sent are displayed at the terminal. This is the default.

NOType

specifies no information is to be displayed.

CLass c

specifies the spool class to be used when sending the file. The operand c is a 1-character alphanumeric field whose value can be A through Z, 0 through 9, or equal sign (=). If an equal sign is specified, the current spool class of the punch is used.

RSCS

Network addresses should only be processed for RSCS networks, no TCP/IP addresses are accepted, and files will not be sent through TCP/IP services. This is the default.

SMTP

specifies the file being sent is using SMTP without any encoding or MIME headers for TCP/IP addresses. For RSCS addresses, the file is sent using RSCS.

MIME

specifies the file being sent is using SMTP for TCP/IP addresses. The file is encoded in BASE64 and sent as a single-part MIME data stream. For RSCS addresses, the file is sent using RSCS.

NOSUBJect

specifies the file being sent will have a blank subject line associated with it. This is the default.

AUTOSUBJect

specifies SENDFILE should set the subject line to be associated with the file being sent. The subject to be set is determined the following way:

• The contents of the file being sent is examined. If the first line of the file is Subject:; Subj: or Re:, this is used to set the subject.
• Otherwise, it sets the subject to "File:" fn ft "from User ID" userid.

SUBJect 'text'

specifies the file being sent will use the 'text' passed in as the subject line to be associated with it. The subject text must be entered in single quotation marks.

UFTSYNC

sends the file to the remote host's UFT (Unsolicited File Transfer) server directly from the user's virtual machine for TCP/IP addresses. If no UFT server is available on the remote host, the file will be sent using SMTP instead. The file is sent as a two-part MIME data stream. The first MIME part is a metafile which contains all the UFT information associated with the file (file id, format, record length, and so forth). The second MIME part is the file data encoded in Base64 (a MIME-defined encoding format). TCP/IP addresses must be IPv4 addresses.

UFTASYNC

sends the file to the server, identified in TCPIP DATA, where it will be sent to the remote host's UFT server for TCP/IP addresses. For RSCS addresses, the file is sent using RSCS. See Usage Note 11 for additional details. TCP/IP addresses must be IPv4 addresses.

ASCII

TEXT

ASCII-INLINE

specifies the user's file is to be translated from EBCDIC to ASCII format as it is being transferred. This option should be used for files that are network plain text, generally anything human readable. This is the default. This option is used only if MIME, UFTASYNC, or UFTSYNC is specified. For the MIME option, the file is sent inline.

ASCII-ATTACH

specifies the user's file is to be translated from EBCDIC to ASCII format as it is being transferred. This option should be used for files that are network plain text, generally anything human readable. This option is used only if MIME is specified. The file is sent as an attachment.

BINARY

BINARY-ATTACH

specifies the file is to be transferred as binary data (no translation). Specifies the user's file is to be transferred as an octet stream of bytes for which record boundaries are not important. For example, the GIF or TAR files. This option is used only if MIME, UFTASYNC or UFTSYNC is specified. For the MIME option, the file is sent as an attachment.

BINARY-INLINE

specifies the file is to be transferred as binary data (no translation). Specifies the user's file is to be transferred as an octet stream of bytes for which record boundaries are not important. For example, the GIF or TAR files. This option is used only if MIME is specified. The file is sent inline.

EBCDIC

specifies the file is to be transferred in EBCDIC format.

NETDATA

specifies the user's file is to be transferred in a NETDATA format. The file will arrive at the destination in NETDATA format, so this format is only useful when sending files to systems that have NETDATA capabilities.

VARREC

specifies the user's file is to be transferred and record boundaries are important, such as MODULE files. The file is transferred with a two byte length preceding each record to allow the receiving system to keep the record boundaries intact (if meaningful on the receiving operating system).

TRANSLATE filename

specifies the name of the TCP/IP EBCDIC to ASCII translation table file to be used when transferring this file over a synchronous UFT connection (UFTSYNC or UFTASYNC) or via SMTP (when the MIME option is specified). The file type of the translation table file is determined by the HANGEUL, KANJI, NODBCS, and TCHINESE options. This is used only if UFTSYNC ASCII, UFTSYNC TEXT, UFTASYNC ASCII, UFTASYNC TEXT, MIME ASCII, or MIME ASCII-INLINE is specified. The default file name is STANDARD.

For more information, see z/VM®: TCP/IP User's Guide.

NODBCS

specifies no DBCS strings are contained in the file data. The file type of the TCP/IP translation table file is TCPXLBIN. This is used only if UFTSYNC ASCII, UFTSYNC TEXT, UFTASYNC ASCII, UFTASYNC TEXT, MIME ASCII, or MIME ASCII-INLINE is specified.

HANGEUL

specifies DBCS strings are contained in the file data. The file type of the TCP/IP translation table file is TCPHGBIN. This is used only if UFTSYNC ASCII, UFTSYNC TEXT, UFTASYNC ASCII, UFTASYNC TEXT, MIME ASCII, or MIME ASCII-INLINE is specified.

KANJI

specifies DBCS strings are contained in the file data. The file type of the TCP/IP translation table file is TCPKJBIN. This is used only if UFTSYNC ASCII, UFTSYNC TEXT, UFTASYNC ASCII, UFTASYNC TEXT, MIME ASCII, or MIME ASCII-INLINE is specified.

TCHINESE

specifies DBCS strings are contained in the file data. The file type of the TCP/IP translation table file is TCPCHBIN. This is used only if UFTSYNC ASCII, UFTSYNC TEXT, UFTASYNC ASCII, UFTASYNC TEXT, MIME ASCII, or MIME ASCII-INLINE is specified.

Usage Notes

1. Tailoring the SENDFILE Command Options

   You can use the DEFAULTS command to set up options and override command defaults for SENDFILE. However, the options you specify in the command line when entering the SENDFILE command override those specified in the DEFAULTS command. This allows you to customize the defaults of the SENDFILE command, yet override them when you desire. For more information, see DEFAULTS.

2. Using the SENDFILE Menu (Display Terminals Only)

   Enter the SENDFILE command without operands to display a menu, on which you fill in the blanks with the necessary information. A sample SENDFILE menu is shown in the Examples, below.

   The File Identifier

   You type the file name, file type, and file mode of a file you want to send directly on the menu in the spaces provided. If you do not enter a file mode, the default is “A”. If you enter a file mode number along with the file mode letter when specifying one file, the file mode number is ignored.

   If you want to select the files from a list, you can type an asterisk (*) for file name, file type, or file mode. An asterisk means you want the list to contain all file names (or file types, or file modes).

   You can also use two special characters in the file name, file type, or both to request the list contain a specific subset of files. The special characters are * (asterisk) and % (percent), where:

   *

   represents any number of character(s). As many asterisks as required can appear anywhere in a file name or file type.

   %

   means any single character, but any character will do. As many percent symbols as necessary may appear anywhere in a file name or file type. To list only the files with a particular file mode number, specify the numeric portion of the file mode along with the file mode letter.

   To display the list, first finish filling out the menu, and then press PF5. A special FILELIST screen is displayed instead of the SENDFILE menu. You select the files by typing a letter s in front of the file name of each file to be sent. Then press Enter to send the files.

   Note: If you have specified a user ID or node name that contains reserved characters (like '/') on the SENDFILE menu, it will be treated just as if you had specified it directly on the FILELIST screen. This could result in syntax errors. You can bypass this possibility by using a NAMES file.

   Another way to select files to be sent from the FILELIST screen is to position the cursor on the line describing a file you want to send, and then press PF5.

   The fileid passed to the SENDFILE EXEC cannot be a mixed case fileid.

   The Recipient(s)

   You type the name(s) of the recipient(s) in the space provided. For more information on how a name can take the form of a user ID or nickname, see Operands.

   The Options

   A list of options also appears on the menu. The default for each option appears to its left. You type 1 for YES or 0 for NO over any options for which you do not want the default. The options are as follows:

   0

   Request acknowledgment when the file has been received?

   Type 1 for YES only if you want to get an acknowledgment when the person receives your file. The acknowledgment shows the date and time the file was received, and the recipient's user ID and node.

   When you get an acknowledgment, it appears in your reader. If you choose to receive it, an entry is made in a userid NETLOG file, which is explained below.

   1

   Make a log entry when the file has been sent?

   Each time you send a file, an entry is automatically made in the file userid NETLOG. A typical entry might look like one of these:

   File MY DATA A1 sent to JONES at NODE1 on 10/10/81 11:30:25 EDT
    
   File MY DATA A1 sent to JONES at NODE1 on 12/31/1999 11:30:25 EDT
    
   File MY DATA A1 sent to JONES at NODE1 on 2000-02-29 11:30:25 EDT
    
   File MY DATA A1 sent to JONES at VNET.IBM.COM on 1997-09-23 09:33:18

   depending on the first valid record in your userid NETLOG file.

   Note: The date format for the date is the same as the first valid record in your userid NETLOG file. If it is a new file, the date format for the date will default to ISODATE (yyyy-mm-dd). To change the date formats in your userid NETLOG file, see NETLCNVT.

   If you specified 1 on the first option (acknowledgment), an entry is also made when you receive the acknowledgment.

   Type 0 if you don't want an entry made in the log file.

   1

   Display the file name when the file has been sent?

   The names of the file(s) and the user ID(s) and node(s) of the recipients are displayed on a cleared screen. Type 0 if you do not want this information displayed.

   0

   This file is actually a list of files to be sent?

   For information on saving a file list, see FILELIST, Usage Note 7, Saving a List of Files. By saving a list of files created by either the FILELIST command or the LISTFILE command issued with the EXEC option, you can send all the files (and the list of files) at once. Type 1 if your file is a list of files.

   0

   TCP/IP destinations to be transmitted by Unsolicited File Transfer?

   Any TCP/IP destinations will default to transmitting the file through SMTP. Type 1 if you want the file to be sent through UFT instead.

   The Spool Class

   You type the spool class you want used when sending the file. The default spool class is A.

   Sending a File

   If you specified only one file ID, press either PF5 or Enter after filling out the SENDFILE menu. PF5 sends the file and exits from the menu. Pressing Enter sends the file but keeps the menu.

   If you are selecting files from a FILELIST screen type a letter s in front of each file name you want to send. Press Enter to send the file(s).

   Keys on the SENDFILE Menu

   Enter

   Execute the command typed on the command line, or if none, send the file. (The Enter key is set by the XEDIT subcommand, SET ENTER IGNORE MACRO EXECUTE.)

   PF1 Help

   Display information about the SENDFILE command.

   PF2

   Not assigned.

   PF3 Quit

   Exit from the menu.

   PF4

   Not assigned.

   PF5 Send

   Send the file(s) and exit from the menu.

   PF6

   Not assigned.

   PF7

   Not assigned.

   PF8

   Not assigned.

   PF9

   Not assigned.

   PF10

   Not assigned.

   PF11

   Not assigned.

   PF12 Cursor

   If cursor is on the menu, move it to the command line; if cursor is on the command line, move it back to its previous location on the menu.

   Note: On a terminal equipped with 24 PF keys, PF keys 13 to 24 are assigned the same values as PF keys 1 to 12 as discussed here.

   On a display terminal without PF keys, you can enter QUIT from the command line to exit from the screen.

   Pressing the PA1 key while in the SENDFILE menu displays the WM window, unless the CP TERMINAL BRKKEY has been assigned to PA1.

   Keys on the FILELIST Screen

   Enter

   Execute the command(s) typed on file line(s), or on the command line. (The Enter key is set by the XEDIT subcommand, SET ENTER IGNORE MACRO EXECUTE.)

   PF1 Help

   Display information about the FILELIST command.

   PF2 Refresh

   Update the list to indicate new files, erased files, and so forth, using the same parameters as those specified on the SENDFILE panel.

   PF3 Quit

   Exit from the list.

   PF4 Sort

   Files by file type, file name.

   PF5 Sendfile

   At cursor. Append the fn ft fm on this line and send the file.

   PF6 Sort

   Files by size, largest first.

   PF7 Backward

   Scroll backward one screen.

   PF8 Forward

   Scroll forward one screen.

   PF9 FL/n

   Issue the command FILELIST /n * * at the cursor, so a list is displayed, containing all files that have the file name displayed on the line with the cursor.

   PF10

   Not assigned.

   PF11 XEDIT

   Edit the file pointed to by the cursor.

   PF12 Cursor

   If cursor is in the file area, move it to the command line; if cursor is on the command line, move it back to its previous location in the file.

   In addition to setting the above PF keys, the PROFSEND XEDIT macro sets synonyms you can use to sort your FILELIST files. Enter the synonyms on the SENDFILE command line. The synonyms are:

   SNAME

   Sorts the list alphabetically by file name, file type, and file mode.

   STYPE

   Sorts the list alphabetically by file type, file name, and file mode.

   SMODE

   Sorts the list by file mode, file name, and file type.

   SRECF

   Sorts the list by record format, file name, file type, and file mode.

   SLREC

   Sorts the list by logical record length and then by size (greatest to least).

   SSIZE

   Sorts the list by number of blocks and number of records (greatest to least).

   SDATE

   Sorts the list by year, month, day, and time (most recent to oldest).

   For an example of a SENDFILE menu, see Figure 1. For an example of a FILELIST screen, see Figure 2.
3. Format of the File Sent by SENDFILE

   The format of the file sent via RSCS depends on whether the OLD or NEW (the default) option is specified.

   The OLD Option

   If the OLD and NOTE options are specified and the width (LRECL) of the note (prepared using the NOTE command) is 80 or less, SENDFILE uses the PUNCH command (with the HEADER option) to send the file. Otherwise, DISK DUMP sends the file. The OLD option should be used if the recipient does not have the RECEIVE or NETDATA commands available to read the file.

   The NEW Option

   If the NEW option is specified, control records are added and the file is sent in a format called NETDATA.

   The transmitted file is composed of several control records, followed by the data records, and ending with a trailer record. If the file is an acknowledgment, it consists only of control records. An acknowledgment can be requested only with the NEW option.

   The NEW option should be used when the recipient can read the file with the RECEIVE or NETDATA command on the CMS system, or when the file is being sent to the MVS operating system with TSO Extensions licensed program.

4. Priority

   When SENDFILE is issued with the NEW option to send a file across the network via RSCS (to a node different from yours), the file is assigned a priority. The order and speed of transmission are based on both this priority and the size of the file.

   The priorities are assigned as follows:

   • NOTE files at least ten blocks in size: Priority = 00 (high)
   • Other files: Priority = 50 (medium)
   • Acknowledgments: Priority = 90 (low)
5. The default for SENDFILE when sending via RSCS is to send files as CLASS A NOCONT NOHOLD regardless of the class to which you spool your PUNCH. If you want SENDFILE to use the current PUNCH spool class, specify the CLASS = option on the SENDFILE command. The CP message generated, containing the spool ID, and so forth, is suppressed.
6. If you want to issue SENDFILE from an exec program, you should precede it with the EXEC command; that is, specify

   exec sendfile

7. When sending a note, the note cannot be appended to a packed notebook. Before using SENDFILE (or NOTE) to send the note, use COPYFILE with the UNPACK option to change the file format from packed to unpacked.
8. Sending Files to MVS/TSO:
   Using SENDFILE to transfer file mode 4 OS simulated V format files to TSO will generate a file TSO cannot process. You must convert these files to file mode 1 (CMS files) using the FILEDEF and MOVEFILE commands, as in this example:

   filedef in disk fn ft fm4 (recf v
   filedef out disk fn ft fm1 (recf v
   movefile in out

   Do not simply rename the file from file mode 4 to file mode 1.

   If the recipient requires the file be in OS simulated format, SENDFILE cannot be used to send the file.

9. When SENDFILE is issued with the NOTE option and the fm is specified other than an asterisk, the fm must be a read/write disk. If a read only disk is specified, an error message will be issued stating the note file is not found.
10. When the SMTP, MIME, or UFTASYNC option is specified, SENDFILE sends the file to the server identified in the TCP/IP DATA file.
11. When the UFTASYNC option is used, SENDFILE tags the file with a pseudo node of UFT. If you are using RSCS as your UFT server, you must have a LINK or GROUP called UFT.
12. The TCPEXIT EXEC is passed a keyword followed by a parameter list. If you create a TCPEXIT EXEC, it will only be called if an option other than RSCS is specified. The TCPEXIT EXEC is passed the keyword IS_HOST_TCPIP followed by an array name which contains entries consisting of USERID NODE FLAG, where FLAG is a 1 or a 0. This is the flag which tells SENDFILE whether the node is to be treated as a TCP/IP address. A 0 means no, and a 1 means yes. You can place the logic code in TCPEXIT to change these flags to fit your rules. The output array expected should be in the same format as passed in. Currently, the only keyword handled is IS_HOST_TCPIP.
13. When MIME option is specified, the Content-Type header is based on a combination of the file type and specified options.
    When BINARY or BINARY-ATTACH, always use:

    application/octet-stream

    When BINARY-INLINE, use:

    application/postscript for filetypes PS, LISTPS, and PDF
    image/jpeg for filetypes JPG, JPEG, and JPE
    image/bitmap for filetype BMP
    image/gif for filetype GIF
    application/msword for filetype DOC
    application/x-zip for filetype ZIP
    audio/basic for filetypes WAV and AU
    video/mpeg for filetypes MPG and MPEG
    application/octet-stream for all other filetypes

    When ASCII or ASCII-INLINE, use:

    text/html for filetypes HTML and HTM
    text/plain for all other filetypes

    When ASCII-ATTACH, always use:

    text/plain

14. In an SSI cluster, if you issue the SENDFILE command without specifying the node, and the recipient is a single-configuration virtual machine, the recipient can display or receive the file when logged on to any member of the cluster. If you omit the node and the recipient is a multiconfiguration virtual machine, the recipient can display or receive the file only when logged on to the member where the SENDFILE command was issued. If you specify the node for either type of user, the file will be sent only if RSCS is running on both members.

Responses

Body of the note kept in fn NOTEBOOK fm
 
Header only added to other NOTEBOOK files.
 
File|Note fn ft fm sent to userid at node on date time timezone
 
nnn files have been sent.
 
File fn ft fm not found.
 
Note added to fn NOTEBOOK fm

Type 'S' in front of each file to be sent and press Enter.

Messages and Return Codes

• DMS002E File fn ft fm not found [RC=28]
• DMS006E No read/write filemode accessed [RC=36]
• DMS048E Invalid filemode mode [RC=24]
• DMS054E Incomplete fileid specified [RC=24]
• DMS060I File TCPIP DATA not found; domain name could not be determined
• DMS062E Invalid character * in fileid fn ft fm [RC=20]
• DMS069E Filemode mode not accessed [RC=36]
• DMS081E Invalid reply; {answer 1 for YES and 0 for NO|enter a valid spool class}
• DMS149E Userid userid not valid; no files have been sent
• DMS399E Tag too long for nickname in userid NAMES file [RC=88]
• DMS579E Records truncated to nn when added to fn ft fm [RC=3]
• DMS637E Missing nodeid for the AT operand [RC=24]
• DMS647E Userid not specified for nickname in userid NAMES file [RC=32]
• DMS648E Userid name not {found|resolved}; no files have been sent [RC=32]
• DMS653E Error executing command, rc=rc [RC=40]
• DMS657E Undefined PFkey/PAkey
• DMS667E NOTE header does not contain the {keyword From:|keyword To:|OPTIONS line|DATE line} [RC=32]
• DMS671E Error sending file fn ft fm; rc=nn from command [RC=100]
• DMS672E Virtual punch invalid or not defined [RC=36]
• DMS673E Addressees are in the note header cards; do not specify names with NOTE option [RC=24]
• DMS674E Punch is not ready [RC=36]
• DMS675E No names specified [RC=24]
• DMS676E Invalid character * for Network ID [RC=20]
• DMS677E Invalid option: option in option line [RC=32]
• DMS678E Invalid note header format; note cannot be sent [RC=32]
• DMS679E Filemode mode is not accessed; note cannot be sent [RC=36]
• DMS680E Invalid fileid specified with FILELIST option [RC=20]
• DMS743E File fn ft fm is in an invalid format [RC=40]
• DMS743E Note not appended to notebook. RC=nn from command [RC=nn]
• DMS1012E Node ID node not valid for RSCS; no files have been sent [RC=32]
• DMS1030E IPv6 addresses cannot be used with the {UFTSYNC/UFTASYNC} option; no files have been sent.
• DMS1116E Invalid value value for {Hostname|DomainOrigin} in TCPIP DATA [RC=32]
• DMS2501E One or more lines between the {OPTIONS:|USEROPTIONS:} line and the DATE: line contain non-blank characters.
• DMS2548E UFT serverID not defined in TCP/IP; no files have been sent [RC=53]
• DMS3279E Remote server response: response

Additional system messages may be issued by this command. The reasons for these messages and their location are: