N E T S E R V ------------- A NETwork SERVer for large computer networks. Program Author: Berthold Pasch c/o IBM European Network Center Tiergartenstrasse 15 D-6900 Heidelberg West-Germany Network address: PASCH at DHDIBM1 on EARN Date: June 07, 1989 General Information about NETSERV --------------------------------- NETSERV is a network server for the academic networks EARN, BITNET and NETNORTH. In NETSERV a distributed server concept has been realized which provides for balanced load of the network, faster response to user requests and better availability of the server. This is achieved by the installation of many servers in the network so that each user finds one nearby (usually only a few number of hops via intermediate nodes). All servers communicate with each other to distribute updated information and make it available in each installation. In general one NETSERV is installed in each country. But for some countries it was necessary to install more than one server due to size of the network inside the country. And for a few countries it was not feasible to have their own server. People of these countries use the services of a NETSERV in a nearby country. Some functions of NETSERV are country-related and should not exist more than once per country. Therefore we have two types of servers: country servers and (where more NETSERVs are installed in a country) subnet-servers. And we have two classes of services: - country services which can only be performed by the country server, - and general services which can be provided by all NETSERVs. The country services are the User Directory Service and the Node Management Support. All other services are general services. To find out whether a NETSERV provides country services or general services only, you may use the QUERY SERVICE command. The response will tell you which services this server provides and for which country or subnet. It also tells you which one your country and/or subnet server is. Throughout the description of NETSERV you'll find the term "privileged user". This is a user who has got special privileges by the assignment of a NETSERV password. The special privileges include the use of certain restricted commands and the retrieval of restricted files. The main purpose of this privileged user class is to keep the network traffic down by preventing normal users from requesting files or services for which they obviously have no need. A NETSERV password can be given to a user by either his node administrator or by the NETSERV controller. NETSERV controllers can be identified by the NETSERV command: QUERY CONTROLLER Description of NETSERV functions -------------------------------- 1) File Server: ------------ NETSERV provides a repository of files: information files and programs. All files are described in FILELISTs. The main filelist is the NETSERV FILELIST which lists the basic information files and also all other filelists of NETSERV. It can be requested from NETSERV by sending the command: GET NETSERV FILELIST Filelists contain short descriptions of the files (name, attributes and comments) and two access codes for each file, one for GET and one for PUT requests. The filelist header describes the access codes and the people associated with each one. ----- Retrieving Files ----- To retrieve a file shown in any of the available filelists, you must use the GET command together with the filename and filetype of the file you want. For an explanation of the command and its parameters refer to the command descriptions in the command reference section. ----- Storing Files ----- To store a file at NETSERV you must be authorized by the PUT-authorization code defined for the specific file. Node Administrators and other privileged users are authorized to store certain files. To store a file you must use the PUT command together with your NETSERV password. The PUT command is only valid as the first record of a file. You cannot send a PUT command in a message. The data to be stored at NETSERV must immediately follow the PUT command record in the file. You may also delete an existing file for which you have PUT-authorization by sending the PUT command as the only record of the file. Statistics are available for file owners (see STAT commands). ----- Subscribing to Files ----- When a file is updated a File Update Information (FUI) is sent to the users who want to be informed of changes to that file. This facility is only available to privileged users (users who have a password assigned). They can add and delete files in their individual "FUI-list" by means of the FUI ADD and FUI DEL commands and display the list by using FUI QUERY. Another function sends updated files automatically to subscribers who have issued the AFD ADD command (Automatic File Distribution) for the file in question. 2) Node Management: ---------------- Node management is the administration of an individual node with regard to the network as well as the administration of information and the coordination of changes for all nodes in a network. NETSERV provides support for both aspects of node management by: a) providing data files and programs for node administrators and network coordinators (available through the File Server of NETSERV), b) supporting registration of new nodes or changes in the network. - The following NETSERV commands are available to node administrators at non-VM systems: GET NODENTRY nodeid PUT NODENTRY password With the GET command the information about the specified node is extracted from the NODES file and sent to the requestor. After the node information in this entry has been updated, the entry may be sent back with the PUT command as the 1st record. - VM node administrators use the BITEARN NODES file and the NODESNAD EXEC to update their node entry and send it back to NETSERV. BITEARN NODES and NODESNAD EXEC can be retrieved from NETSERV via the GET command (see NETSERV FILELIST and PROGRAMS FILELIST). - You may also create and send new node entries to NETSERV if you plan to connect new nodes to your system. - NETSERV accumulates the updates and provides services for country coordinators and higher levels of node management. - For further information about node management in EARN see the NODEMGMT DESCRIPT file. 3) User Directory: --------------- A user directory is available, in which network users can create an entry, containing their name, userid/nodeid, mailing address, phone, job/profession, etc. This directory can then be searched by all users to find communication partners in the network. For more information see the UDS commands. How to request NETSERV services: -------------------------------- Users at VM-nodes have 2 possibilities: ----------------- 1. Send a message to NETSERV in which the message text is the NETSERV command. e.g.: SMSG rscs MSG netservnode NETSERV commandline or TELL NETSERV AT netservnode commandline 2. Send a file whose first record contains the NETSERV commandline. This method must be used if a data file is to be sent to NETSERV. The command record then precedes the actual data records. The file can be sent by the following CMS command: SENDFILE filename filetype filemode NETSERV AT netservnode In case of TELL and SENDFILE commands you may also use the nickname option if you specified NETSERV in your NAMES file. A NETSRV EXEC can be retrieved from NETSERV which facilitates sending of requests to NETSERV. Users at MVS nodes: ------------------- It would be of great advantage if you have TSO/E with IDTF (Interactive Data Transmission Facility) installed which provides easy communication in the network. With TSO/E-IDTF you can use the TRANSMIT (XMIT) command to transmit the NETSERV command as a message or as first record of a file. Example for transmitting the command as a message: Enter: TRANSMIT netservnode.NETSERV NOPROLOG When the screen for message text appears enter the NETSERV command as the 1st line and hit PF3 to submit the message. Example for transmitting the command in a file: Prepare a dataset with the NETSERV command line as the 1st record. If the command requires a dataset to be sent with (e.g. PUT commands) the command line must be the 1st record of that dataset. Enter: TRANSMIT netservnode.NETSERV DATASET(dsname) The dataset must not be a partitioned dataset since NETSERV cannot receive this type of dataset. To send the member of a partitioned dataset you must code the SEQUENTIAL parameter: TRANSMIT netservnode.NETSERV DATASET(dsname(member)) SEQUENTIAL Example for requesting NETSERV services if you don't have TSO/E with IDTF: Create a physical sequential dataset that looks as follows: //...... JOB ........ /*XMIT netservnode.NETSERV FROM userid : commandline --- data to be --- --- delivered ---- ----- with a ----- --- PUT command -- Where "userid" is your userid (TSO) or writer name to which NETSERV responses are to be returned. "commandline" is the command line for NETSERV. If it is a command to store a file at NETSERV (e.g. PUT) the data to be stored must follow immediately the command record as shown above. Submit this Job to your JES2/NJE or JES3 subsystem. JES will then transmit the command record and eventual data to NETSERV at "netservnode". Users at Multics-nodes: ----------------------- Send a mail (sdm) to NETSERV at "netservnode" where the message text is a NETSERV command e.g.: GET NETSERV FILELIST The user receives the NETSERV answer in his Multics Mail-Box. All other native network users: ------------------------------- They must prepare a dataset with the NETSERV command in the first record. This dataset must be sent by appropriate methods to NETSERV at "netservnode". If the sending system is unable to identify the user in the network control records the user may add his identification in front of the NETSERV command: FROM userid : commandline Where userid is your userid or the writer name to which NETSERV responses are to be sent. If the command requires a dataset to be sent with (e.g. PUT commands) the command line must be the 1st record of that dataset. Internet users (i.e. users connected via a gateway): ---------------------------------------------------- Internet users can send commands to NETSERV if they have a RFC822 mailing system (or any mailing facility that is compatible with RFC822, for example RFC733). They must send mail to the following address: NETSERV@netservnode.BITNET and place the command to be executed in the BODY of the mailfile (NOT in the "Subject:" line). Internet users should be aware of the fact that some gateways transform the "From:" address in such a way that it cannot be replied to, or move the first line of the mail body into the header, etc. Several attempts might be required to get the command through. The use of RFC822 headers is not restricted to internet users, but it is recommended that commands be sent in a file whenever possible. RFC822 should be used only if no other communication method is available. NOTE: Not all the NETSERVs do provide RFC822 support. Only a limited set of Netserv commands is available to RFC822 users. All commands which require a password and all UDS registration commands are prohibited. NETSERV Commands: ----------------- The commands and parameters accepted by NETSERV are described below. Also the messages issued by NETSERV in response to these commands are listed and explained when required. How commands should be entered: ------------------------------- Words in capital letters must be typed as shown. Words in lower case must be replaced by appropriate data. Words in brackets <....> can be omitted if wanted. In this case a default value may apply. Some hints about the HELP facility: ----------------------------------- The command "HELP", if specified alone, sends a short summary of the Netserv commands. The complete help information can be obtained by sending the "GET NETSERV HELPFILE" command to Netserv. This is the file you are currently reading. A short help info about a single command or message can be requested by the command "HELP helptype", where "helptype" is either the "command" or "command subcommand" or the "message number" for which you request help. If you don't remember a command you may quickly get a list of available commands via the "Q CMD" command. "Q FILE filename filetype" displays information about a single file. Summary of NETSERV Commands: ---------------------------- Commands for General Users: --------------------------- Get filename filetype < prologtext > Obtain a file from NETSERV. GETND Same as GET but requests file in Netdata fmt. GETDD Same as GET but requests file in DiskDump fmt GETPP Same as GET but requests Punch or Print fmt. GETLP Same as GET but requests LISTSERV-Punch fmt. GET80 Same as GET but split records, use Punch fmt. GET NODENTRY nodeid Retrieve entry from NODES file. SENDme filename filetype Same as GET (for compatibility with NICSERVE) HELP < helptype > Obtain short helpfile or specific help-info. Query CMD List of available NETSERV commands. Query Controller Userid@Nodeid of this Netserv's controller Query File filename filetype Display information about file. Query Service < nodeid > Tells you for which countries/subnets this Netserv provides service and which Netserv is responsible for your node or for "nodeid". SERVE subjuser Return NETSERV services to a "disabled" user UDS (User Directory Services commands) UDS ADD ( + UDS entry ) Add user's entry to the User Directory. UDS REP ( + UDS entry ) Replace user's entry. UDS DEL Delete user's entry from User Directory. Note: UDS ADD/REP/DEL commands must be sent to YOUR country Netserv UDS FIND < searchlimit > search-arguments Find entries, 1 line/entry. UDS GET < searchlimit > search-arguments Get complete entries. Note: UDS FIND/GET commands may be sent to ANY country Netserv. Commands for Privileged Users: ------------------------------ Privileged users are users who have got a NETSERV password assigned either by their node administrator or by the NETSERV controller. AFD ( Automatic File Distribution commands ) AFD ADD password filename filetype < prologtext> AFD DEL password filename filetype AFD Query AFD REP password filename filetype < prologtext> AFD UPDLIST password SUBSCRIBE (same as AFD ADD) UNSUBSCRIBE (same as AFD DEL) FUI ( File Update Information commands ) FUI ADD password filename filetype Add an entry into your FUI-list. FUI DEL password filename filetype Delete FUI-list entry. FUI Query Display your FUI-list entries. FUI REP password filename filetype Replace FUI-list entry. FUI UPDLIST password Execute a list of updates. INFORM password filename filetype (same as FUI ADD) UNINFORM password filename filetype (same as FUI DEL) | PUT password filename filetype < date time > Put a file on NETSERV disks. PW CHange password newpw Change password. STAT ( Request statistics commands (for file owners)) STAT ADD password filename filetype Subscribe to weekly file stat. STAT DEL password filename filetype Unsubscribe. STAT GET filename filetype Request immediate statistics STAT Query Display your STAT subscription. Commands for Node Administrators: --------------------------------- Node administrators are people defined as contact person for a node. AFD ADD password filename filetype FOR subjuser ... ... < prologtext> AFD DEL password filename filetype FOR subjuser AFD Query password subjuser AFD REP password filename filetype FOR subjuser ... ... < prologtext> AFD UPDLIST password < NONOTIFY > FUI ADD password filename filetype FOR subjuser FUI DEL password filename filetype FOR subjuser FUI Query password subjuser FUI REP password filename filetype FOR subjuser FUI UPDLIST password < NONOTIFY > PUT NODENTRY password Return updated node entry Note: PUT NODENTRY is only allowed at your country Netserv. PW ADD password subjuser newpw Define privileged user and passwd PW DEL password subjuser Delete privileged user and passwd PW Query password subjuser Display password(s) of user(s). Note: PW commands may be sent to country Netserv or to sub-Netserv for the specified node. UDS UPDLIST password < NONOTIFY > Submit a list of ADD, REP and DEL requests to User Directory Services Note: UDS UPDLIST is only allowed at your country Netserv. Description of Parameters: -------------------------- filename 1st part of a 2 part file identifier (see filelists) filetype 2nd part of a 2 part file identifier (see filelists) | date the date in the format: YY/MM/DD | time the time in the format: HH:MM:SS helptype specify: command or message nbr. newpw new password to be assigned by a PW ADD or CHANGE request nodeid the identifier of a node password is the current password of a privileged user prologtext will be returned as 1st record of file search_arguments fieldnames and values that are to be searched in UDS searchlimit max. number of entries to be returned on UDS GET or FIND subjuser "userid@nodeid" of a user who is subject in a request Commands and Parameters: ======================== ========= Automatic File Distribution ================================ The Automatic File Distribution (AFD) function of NETSERV is used to send (distribute) files automatically to users when being updated in NETSERV. Whenever a file is changed during a day, the AFD function of NETSERV will be activated at midnight and send the changed file to all subscribers for this file. This function is available to privileged users only (users who've got a NETSERV password). They may use the AFD commands: AFD ADD, AFD REP, AFD DEL to add, replace or delete single subscriptions to files. (Synonyms for AFD ADD and AFD DEL are: SUBSCRIBE and UNSUBSCRIBE). For the addition, replacement or deletion of multiple subscriptions an AFD UPDLIST command is available. An AFD QUERY command (synonym: AFD LIST) provides a list of the subscriptions of the requesting user. Extended formats of these commands allow the node administrators to act on behalf of users at their nodes. Expiration checking: Every third month an expiration check is performed on AFD subscriptions. For subscriptions which are older than one year the subscriber is asked to refresh (replace) the subscription. This confirmation request is repeated every third month until the subscription has been refreshed or 2 years since the last change have passed. After 2 years the subscription is deleted and an appropriate message is sent to the user. +--------------------------------------------------------------+-----+ | AFD ADD password filename filetype < prologtext> | PRV | +--------------------------------------------------------------+-----+ | AFD ADD password filename filetype FOR subjuser ... | NAD | | ... < prologtext> | | +--------------------------------------------------------------+-----+ The AFD ADD command allows privileged users to subscribe to files in Netserv, resp. the second format allows node administrators to do such subscriptions on behalf of other users at their nodes. After the AFD ADD command has completed successfully the subscriber will automatically receive the file whenever it is updated in Netserv. password is the Netserv password of the requestor. -------- filename filetype specifies the file to which to subscribe. A ----------------- generic file-id (using asterisk) may be specified if such one is defined in one of the filelists. The requestor must have GET authorization for the file. subjuser specifies the "userid@nodeid" of the user on whose behalf -------- the requestor performs the registration (subject-user). notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. prologtext may be specified to cause a prolog record to be returned ---------- with the file. This prologtext may contain an identifier or command (for your own server). The keyword PROLOG must be used if your prologtext happens to start with FOR, NOTIFY, NONOTIFY or PROLOG. The prologtext may contain variables which will be replaced by actual data when it is returned with the file. The following variables may be used: &flname name of filelist in which file is defined &flentry complete filelist entry &fn filename of the file &ft filetype of the file &gauth GET authorization code of file &pauth PUT authorization code of file &recfm record format &lrecl logical record length &nrecs number of records &date date of the file (yy/mm/dd) &time time of the file (hh:mm:ss) &descr description of file && returns a single ampersand (&) &&anything returns: &anything &anything_else will return a question mark (?) The variable names may either end with a blank (will be returned in prologtext) or with a period (will be removed). Example: AFD ADD MYPASSWD * NODUPD Store &fn &ft date="&date." might insert the following prolog in front of the file: Store VERS8709 NODUPD date="87/09/12" +--------------------------------------------------------------+-----+ | AFD DEL password filename filetype | PRV | +--------------------------------------------------------------+-----+ | AFD DEL password filename filetype FOR subjuser | NAD | +--------------------------------------------------------------+-----+ AFD DEL is provided for the deletion of subscriptions of one or more files from the Automatic File Distribution list. password is the Netserv password of the requestor. -------- filename filetype specifies the file of which the subscription is ----------------- to be deleted. Either "filename" or "filetype" or both may be specified as asterisk (*) in which case all subscriptions are deleted which match this generic file-id. subjuser specifies the "userid@nodeid" of the user on whose behalf -------- the requestor performs the deletion (subject-user). "subjuser" may also be specified as *@nodeid in which case the subscriptions of all users at "nodeid" will be deleted. notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. +--------------------------------------------------------------+-----+ | AFD List | PRV | +--------------------------------------------------------------+-----+ | AFD List password subjuser | NAD | +--------------------------------------------------------------+-----+ AFD LIST is a synonym for AFD QUERY. See there for further information +--------------------------------------------------------------+-----+ | AFD Query | PRV | +--------------------------------------------------------------+-----+ | AFD Query password subjuser | NAD | +--------------------------------------------------------------+-----+ AFD QUERY displays the subscriptions to automatic file distribution of either the requestor or of "subjuser". password is the Netserv password of the requestor. -------- subjuser specifies the "userid@nodeid" of the user whose -------- subscriptions are to be displayed (subject-user). "subjuser" may also be specified as *@nodeid in which case the subscriptions of all users at "nodeid" will be shown. +--------------------------------------------------------------+-----+ | AFD REP password filename filetype < prologtext> | PRV | +--------------------------------------------------------------+-----+ | AFD REP password filename filetype FOR subjuser ... | NAD | | ... < prologtext> | | +--------------------------------------------------------------+-----+ The AFD REP command allows to replace the prologtext of an existing subscription or to refresh (confirm) the subscription. password is the Netserv password of the requestor. -------- filename filetype specifies the file of which the subscription is ----------------- to be changed/refreshed. The requestor must have GET authorization for the file. subjuser specifies the "userid@nodeid" of the user on whose behalf -------- the requestor performs the action (subject-user). notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. prologtext may be specified to cause a prolog record to be returned ---------- with the file. This prologtext may consist of an identifier or command (for your own server). The keyword PROLOG must be used if your prologtext happens to start with FOR, NOTIFY, NONOTIFY or PROLOG. For more information about prologtext see the AFD ADD command. +--------------------------------------------------------------+-----+ | AFD UPDLIST password | PRV | +--------------------------------------------------------------+-----+ This command allows to send more than one update request (ADD, REP or DEL) for the Automatic File Distribution function at once to Netserv. This is especially useful if you need to refresh (REPlace) the subscriptions for many files after you have been asked for by Netserv's expiration check function (see messages 174 and 175). AFD UPDLIST allows privileged users to ADD, REPlace or DELete entries for themselves. Node administrators may also manipulate the entries of other users at their node, e.g. add a subscription for a server machine even if this userid is not privileged (e.g. has no Netserv password) or if it is to receive a file for which it is not authorized. The request must be sent in a file containing a list of the requested functions. Allowed functions are ADD, REP and DEL. The format of these statements is as follows: ADD filename filetype prologtext REP filename filetype prologtext DEL filename filetype or ADD filename filetype FOR subjuser prologtext REP filename filetype FOR subjuser prologtext DEL filename filetype FOR subjuser The parameters that can be used are the same as with the normal AFD ADD/REP/DEL commands. The "FOR subjuser" version may be used by both, NADs (node administrators) and non-NADs. In the latter case it must of course specify the requestor's id. Example of an update file that might be sent by a NAD: AFD UPDLIST XYZXYZ NONOTIFY ADD XMAILER NAMES FOR NEWSERV@MYNODE Store XMAILER NAMES ADD * NODUPD FOR NEWSERV@MYNODE Store &fn &ft DEL * * FOR OLDSERV@MYNODE REP NETSERV FILELIST The last statement (REP) is executed for the NAD himself (no FOR keyword) to refresh the date in the registration as a response to an expiration warning. password is the Netserv password of the requestor. -------- notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. ========= File Update Information ==================================== The File Update Information (FUI) function of NETSERV may be used to be informed about the update of a NETSERV file. The function is similar to AFD but rather than the file, only a message (note) is sent. This function is available to privileged users only (users who've got a NETSERV password). They may use the FUI commands: FUI ADD, FUI REP, FUI DEL to add, replace or delete single subscriptions to file update information. (Synonyms for FUI ADD and FUI DEL are: INFORM and UNINFORM). For the addition, replacement or deletion of multiple subscriptions a FUI UPDLIST command is available. A FUI QUERY command (synonym: FUI LIST) provides a list of the subscriptions of a user. Extended formats of these commands allow the node administrators to act on behalf of users at their nodes. Expiration checking: Every third month an expiration check is performed on FUI subscriptions. For subscriptions which are older than one year the subscriber is asked to refresh (replace) the subscription. This confirmation request is repeated every third month until the subscription has been refreshed or 2 years since the last change have passed. After 2 years the subscription is deleted and an appropriate message is sent to the user. +--------------------------------------------------------------+-----+ | FUI ADD password filename filetype | PRV | +--------------------------------------------------------------+-----+ | FUI ADD password filename filetype FOR subjuser | NAD | +--------------------------------------------------------------+-----+ The FUI ADD command allows for subscribing to file update information. Whenever the specified file is updated a message (not the file) will be sent to the subscriber. password is the Netserv password of the requestor. -------- filename filetype specifies the file to which to subscribe. A ----------------- generic file-id (using asterisk) may be specified if such one is defined in one of the filelists. The requestor must have GET authorization for the file. subjuser specifies the "userid@nodeid" of the user on whose behalf -------- the requestor performs the registration (subject-user). notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. +--------------------------------------------------------------+-----+ | FUI DEL password filename filetype | PRV | +--------------------------------------------------------------+-----+ | FUI DEL password filename filetype FOR subjuser | NAD | +--------------------------------------------------------------+-----+ FUI DEL is provided for the deletion of subscriptions of one or more files from File Update Information. password is the Netserv password of the requestor. -------- filename filetype specifies the file of which the subscription is ----------------- to be deleted. Either "filename" or "filetype" or both may be specified as asterisk (*) in which case all subscriptions are deleted which match this generic file-id. subjuser specifies the "userid@nodeid" of the user on whose behalf -------- the requestor performs the deletion (subject-user). "subjuser" may also be specified as *@nodeid in which case the subscriptions of all users at "nodeid" will be deleted. notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. +--------------------------------------------------------------+-----+ | FUI List | PRV | +--------------------------------------------------------------+-----+ | FUI List password subjuser | NAD | +--------------------------------------------------------------+-----+ FUI LIST is a synonym of FUI QUERY. Please refer to FUI QUERY for a description. +--------------------------------------------------------------+-----+ | FUI Query | PRV | +--------------------------------------------------------------+-----+ | FUI Query password subjuser | NAD | +--------------------------------------------------------------+-----+ This command displays the subscriptions to File Update Information. Node administrators may query the subscriptions of one or all privileged users at their node. password is the Netserv password of the requestor. -------- subjuser specifies the "userid@nodeid" of the user whose -------- subscriptions are to be displayed. "subjuser" may also be specified as *@nodeid in which case the subscriptions of all users at "nodeid" will be displaid +--------------------------------------------------------------+-----+ | FUI REP password filename filetype | PRV | +--------------------------------------------------------------+-----+ | FUI REP password filename filetype FOR subjuser | NAD | +--------------------------------------------------------------+-----+ The FUI REP command allows to refresh (confirm) the subscription for file update information. password is the Netserv password of the requestor. -------- filename filetype specifies the file of which the subscription is ----------------- to be refreshed. The requestor must have GET authorization for the file. subjuser specifies the "userid@nodeid" of the user on whose behalf -------- the requestor performs the action (subject-user). notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. +--------------------------------------------------------------+-----+ | FUI UPDLIST password | PRV | +--------------------------------------------------------------+-----+ This command allows to send more than one update request (ADD, REP or DEL) for the File Update Information function at once to Netserv. This is especially useful if you need to refresh (REPlace) the subscriptions for many files after you have been asked for by Netserv's expiration check function (see messages 174 and 175). FUI UPDLIST allows privileged users to ADD, REPlace or DELete entries for themselves. Node administrators may also manipulate the entries of other users at their node, e.g. add a subscription for a server machine even if this userid is not privileged (e.g. has no Netserv password) or if it is to receive a file for which it is not authorized. The request must be sent in a file containing a list of the requested functions. Allowed functions are ADD, REP and DEL. The format of these statements is as follows: ADD filename filetype REP filename filetype DEL filename filetype or ADD filename filetype FOR subjuser REP filename filetype FOR subjuser DEL filename filetype FOR subjuser The parameters that can be used are the same as with the normal FUI ADD/REP/DEL commands. The "FOR subjuser" version may be used by both, NADs (node administrators) and non-NADs. In the latter case it must of course specify the requestor's id. Example of an update file that might be sent by a NAD: FUI UPDLIST XYZXYZ NONOTIFY ADD XMAILER NAMES FOR NEWSERV@MYNODE ADD * NODUPD FOR NEWSERV@MYNODE DEL * * FOR OLDSERV@MYNODE REP NETSERV FILELIST The last statement (REP) is executed for the NAD himself (no FOR keyword) to refresh the date in the registration as a response to an expiration warning. password is the Netserv password of the requestor. -------- notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-user will receive a message informing him about the action. +--------------------------------------------------------------+-----+ | Get filename filetype | ALL | +--------------------------------------------------------------+-----+ This command can be used to retrieve files from NETSERV. The file will be sent to you in the file format as specified in the FFORMAT field of the node entry of your node. (To override this see the following GETxx commands). A list of available files can be obtained by: "GET NETSERV FILELIST". Please note that NETSERV FILELIST contains references to other filelists as well, which might be of interest to you. If you request a file that is not available or for which you are not authorized (see GET code in filelist) you will receive an appropriate message. filename filetype specifies the file which is to be sent. The ----------------- requestor must have GET authorization for the file. prologtext may be specified to cause a prolog record to be returned ---------- with the file. This prologtext may consist of an identifier or command (for your own server). +--------------------------------------------------------------+-----+ | GETDD filename filetype | ALL | +--------------------------------------------------------------+-----+ This command returns the requested file in DiskDump format. For further explanations see the GET command. +--------------------------------------------------------------+-----+ | GETND filename filetype | ALL | +--------------------------------------------------------------+-----+ This command returns the requested file in NetData format. For further explanations see the GET command. +--------------------------------------------------------------+-----+ | GETLP filename filetype | ALL | +--------------------------------------------------------------+-----+ This command returns the requested file in Listserv Punch format. Listserv Punch format should be used for files with record lengths greater 80 if your system is not able to receive DiskDump or Netdata format. A description of the Listserv Punch format can be found in the file LISTLPUN MEMO (also available from Netserv). For further explanations see the GET command. +--------------------------------------------------------------+-----+ | GETPP filename filetype | ALL | +--------------------------------------------------------------+-----+ The GETPP (GET Print/Punch) command returns the requested file in Punch format if its record length is less than 81. Print format is used for files with record length greater 80 but less than 133. For record length greater 132 the Listserv Punch format will be used automatically. For further explanations see the GET command. +--------------------------------------------------------------+-----+ | GET80 filename filetype | ALL | +--------------------------------------------------------------+-----+ The GET80 command returns the requested file in Punch format with 80 byte records. If the record length of the file is greater than 80 the records will be split into multiple 80 byte records. A header in the file describes the format and original characteristics of the file. There is also a program available (VM REXX EXEC) which performs the catenation of the records (see CONCAT80 EXEC in PROGRAMS FILELIST). For further explanations see the GET command. +--------------------------------------------------------------+-----+ | GET NODENTRY nodeid | ALL | +--------------------------------------------------------------+-----+ This command sends a single entry from the master nodes file to the requestor. nodeid specifies the name of the node whose entry is to be ------ retrieved. +--------------------------------------------------------------+-----+ | HELP | ALL | +--------------------------------------------------------------+-----+ HELP sends information about NETSERV's commands and messages. If you specify HELP without a parameter you will receive a file with a short description of available Netserv commands A complete description of Netserv's commands and functions can be requested with the "GET NETSERV HELPFILE" command. If you specify "helptype" you will receive only the requested type of information. The returned information is an extract of this helpfile. helptype specifies either a command (or: command subcommand) or the -------- message number about which information is requested. With "Q CMD" you can get a list of available commands. Then you may use HELP to get further information about a command and its parameters. +--------------------------------------------------------------+-----+ | INFORM password filename filetype | PRV | +--------------------------------------------------------------+-----+ | INFORM password filename filetype FOR subjuser | NAD | +--------------------------------------------------------------+-----+ INFORM is a synonym for FUI ADD. Please see there for a description of the command. +--------------------------------------------------------------+-----+ | | PUT password filename filetype < date time > | PRV | +--------------------------------------------------------------+-----+ This command can be used to store or delete files in NETSERV. It can only be sent with a file and must be the 1st record of the file. If the file is to be deleted the PUT command must be the only record of the file. Only files can be stored which are defined in one of the filelists of Netserv. The requestor must also have PUT authorization for this file. password is the Netserv password of the requestor. -------- filename filetype specifies the file to be stored or erased. ----------------- | date time are optional and can be used to set the time stamp of the | --------- file that is to be stored. "date time" is ignored if it | is a delete request. The format for "date" and "time" is: | YY/MM/DD HH:MM:SS (or YYMMDD HHMMSS). +--------------------------------------------------------------+-----+ | PUT NODENTRY password | NAD | +--------------------------------------------------------------+-----+ This command may be used to return an updated node entry to your country coordinator. Netserv verifies the password and authorization of the requestor and accumulates the change requests. The country coordinator is then informed of the arrival of an update. PUT NODENTRY is only supported by "country Netservs" but not for all countries. Your "country NETSERV" will tell you whether it accepts this command or not. If it is rejected you should send the updated node entry directly to the country coordinator. The PUT NODENTRY command must be the first record of a file containing a node entry. This node entry may either have been retrieved from Netserv (using the GET NODENTRY command) or may have been extracted from the master nodes file. password is the Netserv password of the requestor. -------- +--------------------------------------------------------------+-----+ | PW ADD password subjuser newpw | NAD | +--------------------------------------------------------------+-----+ This command allows node administrators to add users to the list of privileged users and to assign a password. Only users of the node the node administrator is responsible for, can be added. The user to whom the password is assigned, will get a message containing the password. The PW ADD command may be sent to the country Netserv or to the sub-Netserv for the node. If it is sent to the country server and a sub-server exists for the user's node the request will also be forwarded to the sub-server. If it is sent to the sub-server it will also be passed up to the country server. password is the Netserv password of the requestor. -------- subjuser specifies the "userid@nodeid" of the user to whom the new -------- password is assigned (subject-user). newpw is the Netserv password to be assigned to "subjuser". It ----- must be 5 to 8 characters long. Expiration checking: Every third month an expiration check is performed on passwords. For passwords which are older than one year the user is asked to change it. This request is repeated every third month until a PW CHANGE request has been made or 2 years since the last change have passed. After 2 years the password is deleted and an appropriate message is sent to the user. If the password of a NAD is deleted this way, the country coordinator will also receive a message. +--------------------------------------------------------------+-----+ | PW CHange oldpw newpw | PRV | +--------------------------------------------------------------+-----+ This command allows privileged users to change their current (old) password. The command may be sent to the country Netserv or to the sub-Netserv of the user's node. If it is sent to the country server and a sub-server exists for the user's node the request will also be forwarded to the sub-server. If it is sent to the sub-server it will also be passed up to the country server. Other servers where you might have a password are not affected. oldpw is the old Netserv password of the requestor. ----- newpw is the new Netserv password for the requestor. It must be 5 ----- to 8 characters long. +--------------------------------------------------------------+-----+ | PW DEL password subjuser | NAD | +--------------------------------------------------------------+-----+ This command allows node administrators to delete users from the list of privileged users. The Node Administrator can only delete users of nodes he is responsible for. The affected user will get a message. The PW DEL command may be sent to the country Netserv or to the sub-Netserv for the user's node. If it is sent to the country server and a sub-server exists for the user's node the request will also be forwarded to the sub-server. If it is sent to the sub-server it will also be passed up to the country server. Other servers where the user might have a password are not affected. password is the Netserv password of the requestor. -------- subjuser specifies the "userid@nodeid" of the user whose password is -------- to be deleted (subject-user). +--------------------------------------------------------------+-----+ | PW Query password subjuser | NAD | +--------------------------------------------------------------+-----+ The PW QUERY command can be used by a node administrator to display the current password of a single user or of all privileged users of a node for which the requestor is registered as NAD. The command may be sent to country Netserv or to sub-Netserv of the user's node. password is the Netserv password of the requestor. -------- subjuser specifies the "userid@nodeid" of a single user or -------- "*@nodeid" if the passwords of all users at "nodeid" are to be displayed. +--------------------------------------------------------------+-----+ | Query CMD | ALL | +--------------------------------------------------------------+-----+ Lists all NETSERV commands available to users. From this list you may select a command and request further information about it by issuing the HELP command. +--------------------------------------------------------------+-----+ | Query File filename filetype | ALL | +--------------------------------------------------------------+-----+ Query File returns information about "filename filetype". This is the same information as is contained in the filelists. You may use this command instead of "GET ...... FILELIST" if you are only interested in information about a single file. filename filetype specifies the file of which you request the ----------------- information. +--------------------------------------------------------------+-----+ | Query Controller | ALL | +--------------------------------------------------------------+-----+ This command returns the name(s) and userid(s) of the person(s) who are to be contacted if there are questions/problems concerning this NETSERV installation. +--------------------------------------------------------------+-----+ | Query Service | ALL | +--------------------------------------------------------------+-----+ The response to this command tells you which kind of services (general/special country services) this Netserv installation provides and which is the Netserv that you should use. It also tells you the country or subnet id to use with your user interface procedures when you are prompted for (certain user interface programs use this code to determine to which Netserv the request should be sent). If nodeid is not specified the response is valid for the requestors node, else it's true for the specified nodeid. nodeid specifies the node for which the server information is ------ requested. If omitted the requestors nodeid is used. +--------------------------------------------------------------+-----+ | SENDme filename filetype | ALL | +--------------------------------------------------------------+-----+ Same as GET (provided for compatibility with NICSERVE). See the GET command for a description. +--------------------------------------------------------------+-----+ | SERVE subjuser | ALL | +--------------------------------------------------------------+-----+ After service was suspended for a user (e.g. due to a large number of invalid NETSERV commands) he may get service again after sending the SERVE command from another userid. Parameters: ----------- subjuser specifies the "userid@nodeid" of the user to whom NETSERV -------- service is to be returned. +--------------------------------------------------------------+-----+ | SUBSCRIBE password filename filetype < prologtext> | PRV | +--------------------------------------------------------------+-----+ | SUBSCRIBE password filename filetype FOR subjuser ... | NAD | | ... < prologtext> | | +--------------------------------------------------------------+-----+ This is a synonym for AFD ADD. See the command description of AFD ADD. ========= File Statistics Information ================================ NETSERV provides file statistics for the owners of files, i.e. for people who are authorized to store files in Netserv. Each file owner may request statistics only for his own files. The statistics contain records for each PUT and GET operation on the file(s). The records include a time stamp, an indication of the performed action (store or retrieve) and the userid and nodeid of the requestor. The statistics are sent each Sunday to the file owners who are registered for the particular file. Registration is done via the STAT ADD command. STAT DEL deletes the registration. Only a single STAT ADD or DEL command is necessary for registration in all NETSERVs. STAT QUERY provides a display of your registration at a single Netserv. STAT GET will ship immediately the statistics of a file from a single Netserv. +--------------------------------------------------------------+-----+ | STAT ADD password filename filetype | PRV | +--------------------------------------------------------------+-----+ STAT ADD allows file owners (people who are authorized to store a file) to subscribe to the weekly available file statistics of their files. The STAT ADD command should only be sent to one NETSERV (the one for which you have got a password). It will be propagated automatically to all other Netservs. password is the Netserv password of the requestor. -------- filename filetype specifies for which file the statistics are ----------------- requested. It must be a file for which the requestor has PUT authorization. +--------------------------------------------------------------+-----+ | STAT DEL password filename filetype | PRV | +--------------------------------------------------------------+-----+ STAT DEL allows file owners to delete their subscription to file statistics. The STAT DEL command should only be sent to one NETSERV (the one for which you have got a password). It will be propagated automatically to all other Netservs. password is the Netserv password of the requestor. -------- filename filetype specifies for which file the statistics ----------------- subscription is to be deleted. You may specify an asterisk for either filename or filetype or both. +--------------------------------------------------------------+-----+ | STAT GET filename filetype | PRV | +--------------------------------------------------------------+-----+ STAT GET sends you immediately all the statistics data of the specified file that has been accumulated so far in the current period (since last Sunday). The STAT GET request is not propagated to all Netservs. To use the STAT GET command it is not necessary to have a subscription (STAT ADD) for this file. filename filetype specifies for which file the statistics are ----------------- requested. It must be a file for which the requestor has PUT authorization. +--------------------------------------------------------------+-----+ | STAT List | PRV | +--------------------------------------------------------------+-----+ Provided as a synonym for STAT QUERY. See STAT QUERY for further info. +--------------------------------------------------------------+-----+ | STAT Query | PRV | +--------------------------------------------------------------+-----+ This command lists the files for which you have requested regular statistics. STAT QUERY provides only a display from the NETSERV to which the command is sent. It is not propagated to all NETSERVs as is done for STAT ADD and STAT DEL. ========= User Directory Services ==================================== The User Directory Services of NETSERV (abbreviated: UDS) provide the users the possibility to register themselves in the directory (ADD), to change (REP) or delete (DEL) their registration and to search the directory for other users (GET or FIND). The directory entries returned for a GET request are in a format that allows to copy them to a NAMES file (VM or MVS systems). Another function, UPDLIST, allows node administrators to do mass updates for users at their node. The following UDS commands are available: UDS ADD, UDS REP, UDS DEL, UDS FIND, UDS GET, UDS UPDLIST NETSERV provides some programs/execs to be run at the user side which facilitate registration and search (see PROGRAMS FILELIST). These are (for VM): NETNAMES EXEC (user registration and search) UDSLIST EXEC (list updates) For MVS systems see: UDSISPF INFOMVS (ISPF panels for MVS) Expiration checking: Every third month an expiration check is performed on UDS registrations. For registrations which are older than one year the user is asked to refresh (replace) the registration. This confirmation request is repeated every third month until the registration has been refreshed or 2 years since the last change have passed. After 2 years the registration is deleted and an appropriate message is sent to the user. +--------------------------------------------------------------+-----+ | UDS ADD | ALL | +--------------------------------------------------------------+-----+ The UDS ADD command must be sent to your country Netserv. It can be used to create an entry in the user directory of your country. Every network user can create his own entry. The data you send with must be in the format of a VM or MVS NAMES entry. A NAMES entry consists of a number of fields with information about the user. Each field consists of a tag (giving the field a name) and of the field data. The tags are distinguished from data by a colon preceding the fieldname. A period is used to separate tag and data (see the example below). The entire file you send for an ADD request should look as follows: UDS ADD :USERID.xxxxxxxx :NODE.yyyyyyyy :NAME.firstname lastname :PHONE.phone number (e.g. +33 (1) 514-31-00) :ADDR.institute name; city; country :DESCR.job title; activities; interests; etc. The entry data must not start on the same line with the UDS ADD command. Minimum required data is: userid, node and name. The maximum data length for each field is shown below: USERID (8), NODE (8) NAME (52), PHONE (52), ADDR (52), DESCR (105) It is strongly recommended not to use special letters of national character sets and to avoid certain special characters. The reason is that other people (with different keyboard) would not be able to type appropriate search arguments and your entry might not be displayed correctly on different terminals. The following list shows all characters which seem to be common to all keyboards and can be used: a-z A-Z 0-9 space & + - * / = . , ; < > ( ) _ You should not use a colon (:) since this may be interpreted as the start of a new field (tag). If an entry for your userid/nodeid already exists your ADD request will be rejected. If you want to replace an existing entry use the UDS REP command. +--------------------------------------------------------------+-----+ | UDS DEL | ALL | +--------------------------------------------------------------+-----+ This command can be used to delete your entry in the User Directory of your country. There is no other data or information required to perform this function. +--------------------------------------------------------------+-----+ | UDS FIND search_arguments | ALL | +--------------------------------------------------------------+-----+ The UDS FIND command may be sent to any Netserv that provides country services. It allows all users to search the User Directory for information about other users in the country where this NETSERV is running. The search result is one message line per entry matching the search request. The message lines contain the following information: entry-nbr: name (userid @ nodeid) phone These messages will either be sent as immediate messages if the request arrived as a message and the response isn't more than 20 lines. Otherwise the response is sent as a Note. The maximum number of entries being returned is 20 per default. This is done for performance reasons. This number may be decreased or increased (up to 100) by the searchlimit parameter. If a search yields more than the maximum you'll get a message and only the first entries up to the maximum are returned. If the absolute maximum of 100 is still not sufficient you should try to specify more precise search arguments. searchlimit specifies the maximum number or entries you want to be ----------- returned for this search request. 100 is the maximum that can be specified. If omitted the default of 20 is used search_arguments specify the fields and values to be searched for. ---------------- The search arguments must be specified as follows: (one or more of the following combination) :fieldname searchvalue The colon distinguishes "fieldnames" from "searchvalues". "fieldname" can be one of the following: NICK (Specify entry number as a search value. If nick) (is specified all other search arguments will be) (ignored.) USERID, NODE, NAME, PHONE, ADDR, DESCR (description). "searchvalue" can be any character string that you want to search for in the given field. It may contain blanks. Multiple blanks will be treated as a single blank. Upper and lower case will be ignored. The maximum length of the search value depends on the field for which it is used: NICK, USERID and NODE: 8 characters NAME, PHONE and ADDR: 52 characters DESCR: 105 characters Note: The search algorithm used by UDS performs a "string match" operation with the search values on the corresponding fields of each entry. This means that if the search string appears somewhere in the given field then we have a match on this field. Case and multiple blanks are ignored. Only if there is a match on all fields specified in the request then the corresponding entry will be returned. Example: UDS FIND 30 :name harry :addr new york would find up to 30 entries in which the name field contains somewhere the string "harry" and the addr field the string "new york". +--------------------------------------------------------------+-----+ | UDS GET search_arguments | ALL | +--------------------------------------------------------------+-----+ The UDS GET command may be sent to any Netserv that provides country services. It allows all users to search the User Directory for information about other users in the country where this NETSERV is running. The search result is a file containing the complete entries which match the search arguments. These entries are in a format that allows to copy them into a VM or MVS NAMES file. The maximum number of entries being returned is 20 per default. This is done for performance reasons. This number may be decreased or increased (up to 100) by the searchlimit parameter. If a search yields more than the maximum you'll get a message and only the first entries up to the maximum are returned. If the absolute maximum of 100 is still not sufficient you should try to specify more precise search arguments. searchlimit specifies the maximum number or entries you want to be ----------- returned for this search request. 100 is the maximum that can be specified. If omitted the default of 20 is used search_arguments specify the fields and values to be searched for. ---------------- The search arguments must be specified as follows: (one or more of the following combination) :fieldname searchvalue The colon distinguishes "fieldnames" from "searchvalues". "fieldname" can be one of the following: NICK (Specify entry number as a search value. If nick) (is specified all other search arguments will be) (ignored.) USERID, NODE, NAME, PHONE, ADDR, DESCR (description). "searchvalue" can be any character string that you want to search for in the given field. It may contain blanks. Multiple blanks will be treated as a single blank. Upper and lower case will be ignored. The maximum length of the search value depends on the field for which it is used: NICK, USERID and NODE: 8 characters NAME, PHONE and ADDR: 52 characters DESCR: 105 characters Note: The search algorithm used by UDS performs a "string match" operation with the search values on the corresponding fields of each entry. This means that if the search string appears somewhere in the given field then we have a match on this field. Case and multiple blanks are ignored. Only if there is a match on all fields specified in the request then the corresponding entry will be returned. Example: UDS GET 30 :name harry :addr new york would find up to 30 entries in which the name field contains somewhere the string "harry" and the addr field the string "new york". +--------------------------------------------------------------+-----+ | UDS REP | ALL | +--------------------------------------------------------------+-----+ The UDS REP command must be sent to your country Netserv. It can be used to change data in your registration entry or to refresh (confirm) the entry. The data you send with must be in the format of a VM or MVS NAMES entry. A NAMES entry consists of a number of fields with information about the user. Each field consists of a tag (giving the field a name) and of the field data. The tags are distinguished from data by a colon preceding the fieldname. A period is used to separate tag and data (see the example below). The data that you send with must be the complete NAMES entry, even if you change only a single field or nothing (in case of confirmation). Example: UDS REP :USERID.xxxxxxxx :NODE.yyyyyyyy :NAME.firstname lastname :PHONE.phone number (e.g. +33 (1) 514-31-00) :ADDR.institute name; city; country :DESCR.job title; activities; interests; etc. The entry data must not start on the same line with the UDS REP command. Minimum required data is: userid, node and name. The maximum data length for each field is shown below: USERID (8), NODE (8) NAME (52), PHONE (52), ADDR (52), DESCR (105) It is strongly recommended not to use special letters of national character sets and to avoid certain special characters. The reason is that other people (with different keyboard) would not be able to type appropriate search arguments and your entry might not be displayed correctly on different terminals. The following list shows all characters which seem to be common to all keyboards and can be used: a-z A-Z 0-9 space & + - * / = . , ; < > ( ) _ You should not use a colon (:) since this may be interpreted as the start of a new field (tag). If an entry for your userid/nodeid does not yet exist your REP request will be changed automatically to an ADD request. +--------------------------------------------------------------+-----+ | UDS UPDLIST password | NAD | +--------------------------------------------------------------+-----+ This command can be used only by node administrators to update entries in the User Directory and it must be sent to his country Netserv. They can only update entries of users at nodes for which they are registered as node administrator. The request must be sent in a file containing a list of subcommands. Available subcommands are ADD, REP or DEL. ADD and REP must be followed by the NAMES entry to be added or replaced. The DEL subcommand must contain the :USERID and :NODE tags. Example: UDS UPDLIST password ADD :USERID.xxxxxxxx :NODE.yyyyyyyy :NAME.firstname lastname :PHONE.phone number (e.g. +33 1 514-31-00) :ADDR.institute name, city, country :DESCR.job title; activities; interests; etc. REP :USERID.xxxxxxxx :node.yyyyyyyy :NAME.firstname lastname :PHONE.phone number (e.g. +33 1 514-31-00) :ADDR.institute name, city, country :DESCR.job title; activities; interests; etc. DEL :USERID.xxxxxxxx :NODE.yyyyyyyy It is strongly recommended not to use special letters of national character sets and to avoid certain special characters. The reason is that other people (with different keyboard) would not be able to type appropriate search arguments and your entry might not be displayed correctly on different terminals. The following list shows all characters which seem to be common to all keyboards and can be used: a-z A-Z 0-9 space & + - * / = % . , ; < > ( ) _ You should not use a colon (:) since this may be interpreted as the start of a new field (tag). If you try to add an entry which already exists the ADD request for this entry will be rejected, and the update will continue with the next entry of your list. After the updates are complete you will receive a file with the update results. password is the Netserv password of the requestor. -------- notifyopt may be either NOTIFY or NONOTIFY or omitted. If NOTIFY is --------- specified or this option is omitted the subject-users will receive a message informing them about the action. +--------------------------------------------------------------+-----+ | UNINFORM password filename filetype | PRV | +--------------------------------------------------------------+-----+ | UNINFORM password filename filetype FOR subjuser | NAD | +--------------------------------------------------------------+-----+ UNINFORM is the synonym of FUI DEL. See FUI DEL command for further details. +--------------------------------------------------------------+-----+ | UNSUBSCRIBE password filename filetype | PRV | +--------------------------------------------------------------+-----+ | UNSUBSCRIBE password filename filetype FOR subjuser ... | NAD | | ... | | +--------------------------------------------------------------+-----+ UNSUBSCRIBE is a synonym for the AFD DEL command. Please see there for further details. Messages: ========= (1) Unknown Command received: "... command line ..." Use Q CMD or HELP to get a list or a description of valid commands. The command (and eventual subcommand) received by NETSERV is unknown. To get a list of valid commands (subcommands) use the Q CMD command or issue the HELP command to get a short helpfile. (2) Command execution ended with rc=nn. Command was: "commandline" During command execution an error number was returned for which no message was defined. The Netserv controller was notified of the problem. You will be informed when the problem is corrected. (3) Unknown Command received: "... command line ..." You had 10 tries. From now on your requests will not be serviced. Use the "SERVE userid@nodeid" command from any other userid to reactivate your NETSERV service. The command (and eventual subcommand) received by NETSERV is unknown. The user had 10 tries but failed to understand how to use NETSERV commands correctly. Probably it is a stupid program responding with any message to NETSERV error messages. If the user wants to be served again by NETSERV the following command should be used from any other userid/nodeid: SERVE userid@nodeid (4) A file with nnnnn records arrived from you. NETSERV can only receive files up to nnnnn records. Your file was not received but has been held. The workspace of NETSERV isn't large enough to receive such a big file. If your request is valid please contact the Netserv controller and ask him to increase the workspace. (5) An error occured while receiving your file or note. Please resubmit. If problem persists, please contact NETSERV controller. The error may be a one time error. You should retry your request If the problem persists, please verify that you used the correct procedure to send to NETSERV. Contact the NETSERV controller. (6) NETSERV received an empty file from you. The file which you sent does not contain a command for NETSERV. Either blank lines or nothing was found in it. The file is held for verification by the NETSERV controller. (7) The command: "command subcommand" is not supported by this NETSERV installation. This message is returned if this Netserv installation does not support the command. This is usually the case if this is a subordinate Netserv and the command you specified is only provided by the central Netserv of a country. (8) NETSERV received a file with more than one dataset from you. Only single dataset files may be shipped to NETSERV. Multiple datasets within a single file are not allowed. Please change your send procedure to send your request in a single dataset. (9) NETSERV was not able to locate the end of the IBM NOTE header. Be sure to insert a blank line between header and text (Netserv cmdline). (10) Parameter: "parmname" is invalid in command: "commandline" Command rejected. Use the "HELP parmname" command or refer to the helpfile to get information about the parameter. Correct the invalid parameter and retry. (11) Parameter: "parmname" is invalid in command: "commandline" --individual parameter explanation-- Command rejected. Consult the individual parameter explanation that appears with the message or see the "HELP parmname" command or refer to the helpfile to get information about the parameter. Correct the invalid parameter and retry. (12) Parameter: "parmname" is missing in command: "commandline" Command rejected. Use the "HELP command" command or refer to the helpfile to see which parameters are required. Re-enter the command with the missing parameter. (13) Parameter: "parmname" is missing in command: "commandline" --individual parameter explanation-- Command rejected. Consult the individual parameter explanation that appears with the message or use the "HELP command" command or refer to the helpfile to get information about the parameter. Re-enter the command with the missing parameter. (14) Parameter: "parmname" is invalid in command: "commandline" --individual parameter explanation-- Command rejected. Consult the individual parameter explanation that appears with the message or use the "HELP parmname" command or refer to the helpfile to get information about the parameter. Correct the invalid parameter and retry. (16) Keyword: "keyname" is missing in command: "commandline" Command rejected. Consult the command format description to see where the missing keyword must be placed. (18) NETSERV received a file with an unsupported file format from you Supported file formats are: Print, Punch, DiskDump, Netdata. Please send the file in one of the formats listed in the message. (19) For the tenth time an invalid file was received from you. All further files or messages from you will be purged without notice. Use the "SERVE userid@nodeid" command from any other userid to reactivate your NETSERV service. You should have received 9 times before one of the messages number 4, 5, 6, 8 or 9 telling you the exact reason for rejecting your file. Please correct the problem and then have another user at your node or another node issue the "SERVE userid@nodeid" command to re-establish NETSERV's support for you. (20) You are not authorized to use command: "commandline" You sent a command that is reserved for privileged users. Privileged users are those who have a password assigned, such as node administrators, who get their password assigned automatically, and certain users (e.g. system programmers) who get their password from their node administrator. (21) Invalid password in command: "commandline" The supplied password does not match your registered password. Please retry with the correct password. If you don't remember your password, call your node administrator to determine your old password or assign a new one. Node administrators may ask the Netserv controller for their password. (22) The command "command" cannot be executed for requests which are sent via a mailer or a gateway (RFC822 requests). Certain commands can only be sent from native users in the BITNET/EARN/NETNORTH network. They do not work for requests sent via mailers or gateways. (23) Please send further file requests to "server-id" to which country/subnet-id xxx is assigned. This message is issued every tenth time a file is requested from a server which is not the preferred one for the user's node. However this request and further requests are honored since it may be that the preferred server is not available to the requestor. (24) The designated server for your area (country/subnet-id yyy) is --server@node--. Your "xxx" request will be processed here, but if you decide to use the designated server, please don't forget to delete this registration. This message is issued for AFD (SUBSCRIBE) commands and for FUI (INFORM) commands if the requesting user is not within the service area of this server. (90) An error occured in NETSERV during execution of: "... command line ..." An internal (NETSERV) error occured. The command cannot be executed. Other commands or the same command with different parameters may continue to work well. Netserv controller was notified of the problem. You will be informed when the problem is corrected. (100) To get a short description of NETSERV services and commands send a message with the word HELP to NETSERV at xxxxxxxx. A short helpfile will be sent as a response to the HELP request. (101) Your file could not be handled by NETSERV and was discarded. If you want information about how to request NETSERV services send a file to NETSERV at XXXXXXXX, containing only the word HELP in the first record. A short helpfile will be sent as a response to the HELP request. (102) Service was not suspended for user: --subjuser--. The SERVE request for the specified user could not be handled because the user hasn't been deactivated. (103) Service is provided again to user: --subjuser--. NETSERV requests from the indicated user will now be handled again. (110) The requested helptype: "helptype" is not available. NETSERV cannot find help information for "helptype". Either you specified an unknown type or there is no help information supplied for it. Valid helptypes are: a command name (or: command subcommand) or a message number. Message numbers are those numbers in parentheses immediately preceeding the NETSERV message text. (120) No information stored about file: "filename filetype". You requested Information about a file that is not defined in any filelist. Please see the filelists (NETSERV FILELIST plus others defined in it) for a list of available files. (130) The requested file: "filename filetype" is not available. Please refer to the filelists to see which files are provided. All available filelists are defined in NETSERV FILELIST. Perhaps you want to look there first (try: GET NETSERV FILELIST). (131) You are not authorized to GET file: "filename filetype". Please refer to the filelists or use the Q FILE command to check the GET authorization code of the desired file. The NETSERV FILELIST contains references to other filelists, besides the references to general information files. (132) File "filename filetype" has been sent to you in XXXX format. NETSERV has sent you the indicated file. XXXX tells you which file format was chosen to send the file to you. XXXX may either be Netdata, DiskDump, Listserv-Punch, Punch or Print. (133) File "filename filetype" has been sent to you in Netdata format ignoring the preferred format for your node since record length is greater than 132. NETSERV has sent you the indicated file. But the file could not be sent in the format defined as the preferred format for your node since its logical record length did not allow to use that format. If you are not able to receive the Netdata format correctly you should either use the GETDD command to retrieve the file in Disk-Dump format, or the GET80 command to split the long records into pieces of 80 bytes. (134) The requested node entry "nodeid" is not available. You requested to get the node entry for "nodeid" from the NODES file but the requested entry could not be found there. Please make sure that you specified the node name correctly. If you used an alias please use the original node name. (135) You are not authorized to request statistics of file: "filename filetype". Only the file owner may request file statistics. Please see the PUT authorization code for this file in the filelist where it is defined, to learn who the file owner is. (140) Put command is only valid as first record of the file to be stored. You have sent a PUT request in a message. The PUT command must be the first record of a file. The command line is removed and the rest of the file is stored. If the PUT command record is the only record of the file, the file will be erased. (141) File: "filename filetype" is unknown to NETSERV and cannot be stored. Please refer to the filelists to see which files you may store. The file to be stored must either be listed by its full fileid or by a generic fileid entry (marked with a > in column 1) and you must be authorized by the PUT authorization code. The GET NETSERV FILELIST command can be issued to obtain a list of files and references to additional filelists. (142) You are not authorized to PUT file: "filename filetype". Please refer to the filelists or use the Q FILE command to check the PUT authorization code of the file to be stored. In the NETSERV FILELIST you'll find the necessary information about general files and references to additional filelists. (143) File: "filename filetype" has been stored successfully. This message indicates successful completion of your PUT request. (144) File: "filename filetype" has been erased at NETSERV. This message tells that the file specified in the PUT request was erased because no new data was supplied with the request. (145) PUT NODENTRY request received with invalid or no data in the file. A file with the PUT NODENTRY command was received but the file was empty, i.e. PUT NODENTRY was the only record of the file or the provided entry did not start with a valid ":NODE" tag. (See also GET NODENTRY) (146) Your node entry (nodeid) has been appended to the Nodes Update file. Your Node Update request will be inspected by the country coordinator before it is merged into the NODES file. The merge run will be made periodically. (150) You are not authorized to use node administrator (NAD) commands for node "nodeid" at "netservid". The rejected command can only be used by a node administrator. (151) A password is already defined for --subjuser--. You tried to define a password for a user who has already got one. You may use the PW QUERY command to determine his existing password. (152) A password is not defined for --subjuser--. You tried to delete the password of a user who has no password assigned. (153) PW < ADD | CHANGE | DEL > request for --subjuser-- completed successfully. The requested action was completed without error. From now on the changes are in effect. (155) Password for --subjuser-- is: "password". The requested password will be displayed. (156) Password "xxxxxxxx" for NETSERV at yyyyyyyy has been assigned to you by --requestor--. With this password you are now able to use the NETSERV commands for privileged users. (157) Your password for NETSERV at yyyyyyyy has been deleted by --requestor--. You are no longer able to use the NETSERV commands for privileged users. (158) Your password for NETSERV at yyyyyyyy has not been changed since yy/mm/dd. Please send a PW CHANGE request to Netserv before yy/mm/dd at the latest. Otherwise your password will be deleted. This message will be sent the first time approximately one year after a password has been assigned or has been changed. It will then be repeated every 3 months until another year has gone or the password has been changed. If the password is then still unchanged it is assumed that this user no longer exists and the password is deleted automatically. (159) Your password for NETSERV at yyyyyyyy has not been changed since yy/mm/dd. It has just been deleted. If you want a new password please contact your node administrator or your country coordinator. Most probably this user does no longer exist since he didn't respond to several requests (message 158) for changing his password. (160) File: "filename filetype" cannot be added to the subscription list for --listname-- because it is not defined in any filelist of NETSERV. Please check the filelists to see which files are available. --listname-- is the name of the list to which you tried to add an entry and may either be: "Automatic File Distribution" or "File Update Information" or "File Statistics". (161) You are not authorized to GET file: "filename filetype". Therefore you cannot add this file to the subscription list for --listname--. or (161) You are not authorized to PUT file: "filename filetype". Therefore you cannot add this file to the subscription list for --listname--. Please check the filelists to see for which files you have GET or PUT authorization. --listname-- is the name of the list to which you tried to add an entry and may either be: "Automatic File Distribution" or "File Update Information" or "File Statistics". (162) File: "filename filetype" exists already (or is included by a generic file-id) in subscription list for --listname-- of "userid@nodeid". XXX ADD request cancelled. XXX is the command name and --listname-- is the name of the subscription list to which you tried to add an entry. With XXX QUERY you may check the entries in the --listname-- list. (163) File: "filename filetype" has been added to the subscription list for --listname-- of "userid@nodeid". XXX ADD request completed successfully. XXX is the command name and --listname-- is the name of the subscription list to which you tried to add an entry. Your ADD request was successful. If it was a FUI ADD request update information about the specified file will be sent whenever it is updated at NETSERV. If it was a AFD ADD request the updated file will be sent automatically to the referenced user. If it was a STAT ADD request then statistics of the specified file will be sent weekly. (164) File: "filename filetype" is not defined in the subscription list for --listname-- of "userid@nodeid". XXX DEL request cancelled. XXX is the command name and --listname-- is the name of the subscription list from which you tried to delete an entry. With XXX QUERY you may check the entries in the subscription list. (165) Request to remove "filename filetype" from the subscription list for --listname-- of "userid@nodeid" completed successfully. Following files have been removed: filenames filetypes of files removed --listname-- is the name of the subscription list on which the deletion has been performed. If it was a FUI DEL request information about file changes will no longer be sent to the referenced user. If it was a AFD DEL request the updated file(s) will no longer be sent. If it was a STAT DEL request shipment of the statistics for the referenced file(s) will stop. Message 165a may be issued instead of message 165 if it was a a request of a node administrator on behalf of another user. Message 165a will not contain the list of removed files. (166) Entry for "filename filetype" has been replaced in the subscription list for --listname-- of "userid@nodeid". XXX REP completed successfully. XXX is the command name and --listname-- is the name of the subscription list in which you tried to replace an entry. The request was successful. (167) Request from --requestor-- to add files to your subscription list for --listname-- completed successfully. Following files have been added: filename filetype of added files --listname-- is the name of the list to which the entry was added and may either be: "Automatic File Distribution" or "File Update Information" or "File Statistics". An entry in the corresponding list has been created for you by the indicated user. Depending on the type of list you will get in future: - update information about the specified file, - or the file will be automatically shipped to you, - or file statistics will be sent weekly. (168) Request from --requestor-- to remove files from your subscription list for --listname-- completed successfully. Following files have been removed: filename filetype of removed files --listname-- is the name of the list from which the entry was deleted and may either be: "Automatic File Distribution" or "File Update Information" or "File Statistics". Your entry in the corresponding list has been deleted by the indicated user. Depending on the type of list the following is stopped: - sending of update information about the specified file, - or sending the file itself when it is updated, - or sending of the weekly file statistics. (169) Request from --requestor-- to replace entries in your subscription list for --listname-- completed successfully. Following entries have been replaced: filename filetype of replaced entries --listname-- is the name of the list in which the entry was replaced and may either be: "Automatic File Distribution" or "File Update Information" or "File Statistics". (170) Your subscriptions for --listname-- have been copied from --server1-- to --server2-- on request of --requestor--. List of files involved: filename filetype of the files --listname-- is the name of the subscription list of which your entries have been copied. Such a copy is usually done in order to transfer your subscriptions to another server. In most cases you will also receive a separate notification about deletion of these subscription at the old server. (171) XXX UPDLIST command is only valid as the first record of a file followed by one or more update statements. You have sent an XXX UPDLIST request to Netserv but did not provide the required update statements. See the description of the appropriate XXX UPDLIST command for the format of these update statements. (172) UPDLIST request for xxxx completed. The following list of handled update requests contains prefix numbers which show whether the request was successful (code 0) or was terminated because of some problem or user error. For a description of possible error codes see the help text for this message. xxxxx is the name of the list that was updated ("Automatic File Distribution" or "File Update Information"). The supplied update list has been worked down and the result of each action is shown by the action/error code in front of each list line. This list is appended to the message. Following is a list of the possible codes: 0 = The request has been completed correctly. 1 = Unknown request (not an ADD, REP or DEL). 2 = Invalid or unknown "filename filetype" in request. 3 = Invalid "FOR user@nodeid" specified. | 4 = Requestor is not authorized to update this entry. 5 = Requestor is not authorized to GET the specified file. 6 = Invalid arguments in update line. 7 = Entry to be added exists already, or Entry to be deleted does not exist. 8 = Prologtext on ADD or REP statement is longer than the allowed maximum of 132 (for AFD) or 0 (for FUI). 90= Netserv internal error occured during processing of request. (173) There are no entries for --user-- in subscription list for --listname--. You requested a display of the entries of --user-- in the subscription list for --listname-- but the list is empty. --listname-- may either be: "Automatic File Distribution" or "File Update Information" or "File Statistics". (174) The following subscription(s) for --listname-- at NETSERV at yyyyyyyy need to be confirmed. If a confirmation is not received before the indicated deletion date at the latest the subscription(s) will be deleted. last deletion filename filetype for change date -------- -------- ----------------- -------- -------- xxxxxxxx yyyyyyyy userid@nodeid yy/mm/dd yy/mm/dd For your convenience the required confirmation data is appended hereafter. It may be returned to NETSERV at yyyyyyyy after you have inserted your Netserv password: XXX UPDLIST password REP xxxxxxxx yyyyyyyy FOR userid@nodeid prologtext This message will be sent the first time approximately one year after a subscription has been made or has been confirmed last. It will then be repeated every 3 months until another year has gone by or the subscription has been confirmed. If the confirmation is not returned by the end of the second year it is assumed that the user no longer exists and the subscription(s) are automatically deleted. (175) The following subscription(s) for --listname-- at NETSERV at yyyyyyyy has (have) not been confirmed in spite of several such requests. It has (they have) just been deleted. last filename filetype for change -------- -------- ----------------- -------- xxxxxxxx yyyyyyyy userid@nodeid yy/mm/dd In case you want to re-establish the subscription(s) the necessary registration data is appended hereafter. It may be returned to NETSERV at yyyyyyyy after you have inserted your Netserv password: XXX UPDLIST password ADD xxxxxxxx yyyyyyyy FOR userid@nodeid prologtext Most probably this user does no longer exist since he didn't respond to several requests for confirmation (message 174). (178) Your user directory entry has not been changed since yy/mm/dd. Please confirm your registration by sending a UDS REP request with your updated registration data. Your current directory entry is returned to you for verification. If no confirmation is received before yy/mm/dd at the latest then your entry in the user directory of Netserv will be deleted automatically. VM users: use NETNAMES EXEC to receive this message and confirm. Otherwise use the following UDS REP data, verify and send it back to NETSERV at yyyyyyyy: UDS REP :nick.nnnn :userid.xxxxxxxx :node.yyyyyyyy :name.mmmmmm etc. This message will be sent the first time approximately one year after a user has created or changed his directory entry. It will then be repeated every 3 months until another year has gone or the registration has been confirmed by a REP request. If another year has gone by without such a confirmation it is assumed that this user no longer exists and the entry will be deleted. (179) Your user directory entry had not been changed since yy/mm/dd despite several requests for confirmation. It has just been deleted. Most probably this user does no longer exist since he didn't respond to several requests (message 178) for confirming or updating his registration entry. (180) UDS xxx command is only valid as the first record of a file with a NAMES entry in the second and following records. You have sent an ADD, REP or UPDLIST request to User Directory Services and did not supply a NAMES entry (or subrequests with NAMES entries in case of UPDLIST) in the records following the command record. (181) You cannot register in the User Directory of this NETSERV installation since it does not support your country. Please send your request to the NETSERV machine of your country. Registration is only possible in the User Directory for your country. Please direct your request to the NETSERV installation supporting your country. (182) The number of lines of an entry must not be zero and shouldn't exceed nnn. XXX request ignored. The maximum number of records for an ADD or REP request is 10. This number should be sufficient to specify all fields for one entry. (183) The data passed for the XXX request is invalid (reason x). The reason x tells you what is wrong: 1) Invalid use of colon (:). Colons are only allowed to identify a tag (start of a field), e.g. :node.DHDIBM1 2) A supported tag appeared more than once. (N.b. Tags which are not supported by UDS are ignored). 3) The datalength of a field exceeds the maximum allowed for that field. The following maximum lengths are allowed: userid (8) node (8) name (52) phone (52) addr (52) descr (105) 4) Required data is missing. For an ADD or REP request the USERID, NODE and NAME data must be given. For a DEL subrequest in a UDS UPDLIST request the USERID and NODE are required. (A UDS DEL request doesn't need anything besides the UDS DEL command since it uses the userid/nodeid of the requestor.) (184) The userid and/or nodeid specified in the entry is not yours. You are only allowed to add or replace your own entry. The USERID and NODE fields must specify your userid and nodeid. (185) There is no entry for userid@nodeid that can be deleted. The indicated user is not registered is this User Directory. (186) The entry you try to add for userid@nodeid exists already. The indicated user is already registered in this User Directory. You may retrieve and inspect the entry by using the command: UDS GET :USERID userid :NODEID nodeid After modifying it you may replace it by sending it back with UDS REP command. (187) The number of records in the UDS Updlist file should not exceed nnn. The number of records being processed by UDS Updlist has been limited to 500 due to performance reasons. If you want to add more entries send several requests. (188) The UDS Updlist file does not contain an ADD, DEL or REP request Please see the UDS Updlist command for the format of the file. (189) The UDS xxx request for userid@nodeid has been processed correctly. The entry has been added, replaced or deleted successfully in the User Directory. (190) A USER DIRECTORY "xxx" request has been performed for you by userid at nodeid (the system contact person for your node). The User Directory of Netserv is comparable to a telephone directory: it contains names, addresses, phone numbers and other information about network users and may be searched to find communication partners. If you need more information about the User Directory function send the command: HELP UDS to NETSERV at yyyyyyyy. If you want information about all Netserv functions send the command: HELP to NETSERV at yyyyyyyy. The indicated user has added, replaced or deleted your entry in the User Directory of the NETSERV installation which sent you the message. (191) You are not allowed to update the entry for userid@nodeid You cannot add, replace or delete this entry because your are not the node administrator of this node. (192) XXX request for userid@nodeid terminated due to an internal error. The request for the indicated user was terminated unsuccessfully due to an internal NETSERV error. NETSERV coordination has been informed of the problem. Other subrequests of the same command may have completed successfully. (194) 1 entry satisfying your search criteria has been found. Your request has been processed successfully and 1 entry matching your search request has been found in the User Directory. (195) nnn entries satisfying your search criteria have been found. Your request has been processed successfully and nnn entries matching your search request have been found in the User Directory. (196) More than nnn entries satisfying your search criteria found. The first nnn entries are displayed. Your request has been processed successfully but more than "nnn" entries matching your search request have been found in the User Directory. Only the first "nnn" are retrieved and sent back to you. Please specify more precise search arguments to limit the number of matches. (197) The search arguments for UDS GET (or FIND) are invalid Either no tags or unknown tags have been specified or the length of a search argument exceeds the maximum length possible for that field. Find the allowed tags and the maximum length of their fields below: :nick (8) :userid (8) :node (8) :name (52) :phone (52) :addr (52) :descr (105) Example for specification of search arguments: :name HUBER HANS :addr UNIVERSITY KARLSRUHE (198) No entry satisfying your search criteria has been found. Your request has been processed successfully but no entry matching your search request has been found in the User Directory. (199) Multiple update request for userid@nodeid ignored. Your update list for the UDS UPDLIST command contained the entry for userid@nodeid more than once. Multiple requests in same file are ignored. Only the first request will be executed.