LISTSERV Command Reference for LISTSERV 17.0

GET

z/VM Syntax

GET fn ft [filelist] [(option] [F=fformat] [SPLIT=integer]

Non-z/VM Syntax

GET fn ft [catalogname] [([F=fformat] [SPLIT=integer]]

Order the specified file or package from LISTSERV. The single option is for z/VM servers only and is:

Examples:

GET MYFILE TEXT
GET MYFILE TEXT MYLIST-L

Typically the filelist name or catalog name is the same as the name of the list to which the files belong. A password (PW=xxxxx at the end of the command) is required to retrieve any file that does not have a GET FAC of ALL. For more information on FAC (File Access Control) codes, see the Site Manager’s Manual for LISTSERV.  

Do not use dots (periods) in the file specification when specifying the filelist or catalog name, as this will result in an error. For instance

GET MYFILE.TEXT MYLIST-L

will result in an error, whereas

GET MYFILE TEXT MYLIST-L

will not.

To control the format in which LISTSERV returns the file(s) to you, you can specify the F=fformat parameter. Supported formats are Netdata, Card, Disk, Punch, LPunch, UUencode, XXencode, VMSdump, MIME/text, MIME/Appl, Mail.

To split very large files into manageable chunks, you can specify the SPLIT=integer parameter. The integer value is the size you want the chunks to be generated, in kilobytes. For instance if you were ordering a 2MB notebook log and wanted to break it into 100KB chunks, you would specify SPLIT=100. This is handy for people whose mail systems place a limit on the size of an individual mail message that may be received by a given user.

The following syntax is accepted for TCPGUI parameters for Change-Logs:

GET listname CHANGELOG (MSG [COLUMNS(colspec1 colfilter1 [colspec2 colfilter2[...]])

The design goal was to provide access via the TCPGUI (and thus the web interface) for change-log data. Further information can be found in the Advanced Topics Guide for LISTSERV.

GIVE

z/VM Syntax

GIVE fn ft [filelist] [TO] userid@host

Non-z/VM Syntax

GIVE fn.ft [TO] userid@host

or

GIVE fn ft catalogname [TO] userid@host

Sends a file stored in a LISTSERV file archive to someone else. For instance, you may want to send LISTSERV REFCARD to a new user. Rather than retrieving LISTSERV REFCARD and then forwarding it to the user, you simply issue a GIVE command to tell LISTSERV to send it directly. Note that the token “TO” is optional.

Examples:

For LISTSERV running under z/VM:

GIVE LISTSERV REFCARD joenewuser@hishost.com

GIVE LISTSERV REFCARD TO joenewuser@hishost.com

GIVE README TEXT MYLIST-L joenewuser@hishost.com

GIVE README TEXT MYLIST-L TO joenewuser@hishost.com

For LISTSERV running on non-z/VM hosts there are two syntaxes, depending on whether or not you need to specify a catalog name for the file in question. Note that the only real difference is whether or not you are required to specify a dot between the filename and the extension.

GIVE LISTSERV.REFCARD joenewuser@hishost.com

GIVE LISTSERV.REFCARD TO joenewuser@hishost.com

GIVE README TXT MYLIST-L joenewuser@hishost.com

GIVE README TXT MYLIST-L TO joenewuser@hishost.com

INDex <filelist | catalog>

Same as GET xxxx FILELIST. If no filelist is specified, the default is LISTSERV FILELIST (on non-VM, SITE CATALOG is returned as LISTSERV FILELIST in this case).

PW function

Define/change a “personal password” for protecting AFD/FUI subcriptions, authenticating PUT commands, and so on.

SENDme

Same as GET.

AFD

Available on z/VM servers only.

Automatic File Distribution. The functions are as follows:

For node administrators:

FUI

Available on z/VM servers only.

File Update Information: same syntax as AFD, except that FUI ADD accepts no ‘prolog text’.