High Voltage Shareware

home *** CD-ROM | disk | FTP | other *** search

/ High Voltage Shareware / high1.zip / high1 / DIR21 / DOCPRC13.ZIP / SAMP-DOC.ZIP / BITNET.DOC next >

Wrap

Text File | 1992-11-16 | 42KB | 511 lines

************************************* * * * B I T N E T * * ON THE MVS/XA OPERATING SYSTEM * * * ************************************* John S. Ward 03/15/93 EJECT BITNET is a network of over 1000 computers at educational and research institutions worldwide. Georgia State University's AMDAHL 5860 (System D) is a part of this network which enables its users at different sites to share information via electronic mail. BITNET has gateways into several other networks (ARPANET, CSNET, MAILNET, and UUCP, for example). Because BITNET is not considered to be a secure network, sensitive or confidential data should not be sent via BITNET. To access a member of the BITNET network, you may use the TSO/E Interactive Data Transmission Facility on the AMDAHL. The facility's TRANSMIT command allows you to send data to other users on the AMDAHL (System D) as well as users on other BITNET nodes. The RECEIVE command allows you to receive data. The facility provides the ability to log messages and data sets transmitted and received and the ability to create nickname and distribution lists. Read the handout on TSO/E Mail for specific information on this facility or refer to the TSO/E COMMAND LANGUAGE REFERENCE MANUAL - SC28-1134. TRANSMIT COMMAND The TRANSMIT command allows you to send interactive messages, data sets prefixed by interactive messages, and data sets without any attached message. However, both interactive messages and data sets are sent as data sets when the destination is a non-MVS node. Transmission of data sets to BITNET nodes is limited to data sets of 300,000 bytes (3,750 eighty-character records). Larger data sets may be divided into smaller data sets and transmitted at appropriate intervals. EJECT The format of the TRANSMIT command is: TRANSMIT nodename.userid DATASET(dsname) options where nodename is the name given to an institution's computer by BITNET. The node name for GSU's AMDAHL running MVS/XA is GSUMVS1. The current list of node names is maintained under the member SYS.MVS.UPDATE(BITNODES). userid is the userid of the person you are trying to TRANSMIT to. dsname is the name of the data set you wish to send. Put fully qualified names in quotes. This data set may be a partitioned data set or a sequential data set. You cannot send data sets with keys or user labels, ISAM data sets, or VSAM data sets. options A complete description of all available options can be found in the TSO/E Command Language Reference Manual. Note: To send a partitioned data set to a non-MVS node, you MUST use the SEQUENTIAL option on the TRANSMIT command to send the data set as a sequential file. You may send partitioned data sets only to nodes running MVS. If you do not use the DSNAME option, TRANSMIT will assume you wish to send a message and will prompt you with a screen for entering that message. Messages are sent as data sets to non-MVS nodes. To send a message or data set to more than one user at the same time, enclose the list of names in parentheses: TRANSMIT (nodename.userid nodename.userid ...) DATASET(dsname) or establish a nickname and distribution list using the data set NAMES.TEXT. Note: You may issue the TRANSMIT command from the COMMAND line or OPTION line of any ISPF screen by prefixing the command with "TSO" as shown below. COMMAND => TSO TRANSMIT nodename.userid DATASET(dsname) The TRANSMIT command has several options. A description of some of the more frequently used options is contained in the handout on TSO/E Mail. A full description of the options is given in the TSO/E COMMAND LANGUAGE REFERENCE MANUAL - SC28-1134. You may also issue the TSO command "HELP TRANSMIT" to get more information. EJECT RECEIVE COMMAND The RECEIVE command is used to receive information that has been sent to you from another user. If you have mail waiting to be received, the following message will appear when you logon or when you hit return if you are logged on when the mail comes in: +GSU001 MAIL WAITING FROM nodename/userid The format of the RECEIVE command is: RECEIVE Note: You may issue the RECEIVE command from the COMMAND line or OPTION line of any ISPF screen by prefixing the command with "TSO" as shown below. COMMAND => TSO RECEIVE If an interactive message has been sent to you it will be displayed on the screen. You cannot specify a data set to save the message to when you receive it, but a copy of the message is placed in the LOG data set. (You will not receive interactive messages from non-MVS nodes.) If an error-free data set has been sent, the following messages will be displayed when you issue the RECEIVE command (any attached message sent along with the data set would appear first): INMR901I Data set 'dsname' from 'userid' on 'nodename'. INMR906A Enter RESTORE parameters or 'DELETE' or 'END'. + You may respond with a ? whenever you see a + to get more information about what to do. If you entered a ? now, you would see: INMR908A The input file attributes are: DISORG=_______,RECFM=__, BLKSIZE=____,LRECL=_____,FILE SIZE = ____ + If you again entered a ?, you would see: INMR909A You may enter DSNAME, SPACE, UNIT, VOL, OLD/NEW, or RESTORE/COPY/DELETE/END If you enter END, the RECEIVE command will terminate leaving the file on the spool to be received at a later time. If you enter DELETE, the file will be erased from the spool. If you simply press return at this point, the received data set will be saved in the default data set name. The default is the same name as the transmitted data set with the high level qualifier changed to your userid. If you do not want the data set saved to this default EJECT name, use the DSNAME option to specify the name of the data set to use. The format is DSNAME('dsname') where dsname can be the name of a new or existing data set. Put a fully qualified name in quotes. If you attempt to receive into a file whose file attributes do not match those of the file that was sent, the RECEIVE command will terminate leaving the file on the spool to be received at a later time. You may specify the allocation parameters for the new data set or just use the defaults. The default allocation parameters are: PARAMETER DEFAULT VALUE DSNAME If the data set was error-free, the default is the same name as the transmitted data set with the high level qualifier changed to your userid. If the data set was transmitted from a non-MVS system (i.e., most BITNET nodes), the header records will be unrecognizable to RECEIVE. Therefore, RECEIVE interprets them as being erroneous even if the data in the data set is fine. When you try to RECEIVE data sets containing errors, the default data set is your_userid.RECEIVE.INVALID.FILE. SPACE primary default value for primary space allocation is a size equal to the incoming data secondary default value is 2.5% of the primary allocation TRACKS or space to be allocated in TRACKS, CYLINDERS, or CYLINDERS or BLOCKS. Default is TRACKS. BLOCKS DIRECTORY this option is only applicable when receiving into a new partitioned data set. The default value for directory blocks when receiving a sequential data set into a new pds is 27. The default when receiving a pds into a pds is the number of blocks required for the received members. NEW or If a value is not given for SPACE, The data set OLD or disposition default is OLD. If that fails, NEW MOD or is used and SPACE values are added. SHR If you attempt to restore the received data set to a data set that already exists, you will be prompted with the message: INMR045I Data set 'dsname' already exists. Reply 'R' to replace it. + Any response other than 'R' will terminate RECEIVE leaving the data set on the spool to be received at a later time. EJECT If you have successfully restored the received data set, you will see the messages below: INMR001I Restore successful to data set 'dsname'. INMR900I ---------------------------------------- If you have any more data sets or messages to receive, they will appear at this point. If you have no more messages or data sets to receive, you will see the message: INME000I No more Interactive Data Transmission Facility files are available for the RECEIVE command to process. The default data set name for RECEIVE to use when the data set contains errors is 'your_userid.RECEIVE.INVALID.FILE'. Because the header records on data sets sent from non-MVS systems (VAX, Cyber, VM systems running PROFS, etc.) are not recognizable to TSO's Interactive Data Transmission Facility, these files are interpreted as being erroneous even if the data within the files are fine. When you RECEIVE a non-MVS data set or a data set containing errors, you will see the following messages: INMR921I Received file appears not to be an Interactive Data Transmission Facility file. The first record is: * first record appears here * INMR901I Dataset X.RECEIVE.INVALID.FILE from ? on ? INMR907A Enter COPY parameters or 'DELETE' or 'END.'+ If you press the return key at this point, the data set will be copied into the default data set 'your_userid.RECEIVE.INVALID.FILE'. If there is already something in 'your_userid.RECEIVE.INVALID.FILE', you will be prompted for permission to overwrite it: INMR045I Data set 'RECEIVE.INVALID.FILE' already exists. Reply 'R' to replace it. + If you do not want the received file saved in the default file, do not press return when prompted to enter copy parameters. Instead, use the "DSNAME" option to specify the name of the data set to use. If the file attributes of this data set do not match those of the file you are attempting to receive, RECEIVE will terminate leaving the file on the spool to be received at a later time. For more information on the RECEIVE command, you may issue the TSO command "HELP RECEIVE" or refer to the TSO/E COMMAND LANGUAGE REFERENCE MANUAL - SC28-1134. EJECT GETTING INFORMATION ABOUT BITNET BITNET is supported by the BITNET Network Information Center (BITNIC). BITNET has three sources of information: NICSERVE, LISTSERV, and DATABASE. BITNIC's file server, NICSERVE, offers information on upcoming conferences, BITNET administration and general information, BITNET sites and nodes, protocols, BITNET software, LISTSERV, and the EDUCOM NETWORKING newsletter. LISTSERV is a network mailing list server. DATABASE is an inter-network database server that is currently under development. Because TSO's Interactive Data Transmission Facility cannot send interactive messages in standard BITNET format, a data set must be created whose contents mimic a standard mail file. This data set must follow the Arpanet standard header format. When creating the data set using the ISPF editor, issue the NUM OFF command at the COMMAND prompt before typing in the data. If you fail to turn NUM OFF, the data will be unrecognizable by any of the servers. You send the data set to BITNIC by submitting JCL containing the necessary commands. Because you use JCL to submit the job and do not use the TRANSMIT command, a log entry will not be made in the LOG1.LOGSET data set. NICSERVE The GET command is used to request files from NICSERVE. The format to use when sending to NICSERVE is given below. Be sure to turn NUM OFF when creating the data set in the ISPF editor or NICSERVE will not recognize the data set as mail. DATE: day, date month year FROM: your_userid@GSUMVS1 TO: NICSERVE@BITNIC GET filename filetype where filename and filetype are from the NICSERVE INDEX which contains descriptions of all available NICSERVE files. You may issue only one GET command at a time. (You may not stack commands.) Note: All entries must begin in column one. DATE: must be the first line in the data set. There can be only one space after the : in the DATE and FROM entries. The TO: entry should line up with the others. The blank line between the TO: entry and the GET command is required. You can request a HELP file on using NICSERVE from NICSERVE by issuing the command "GET NICSERVE HELP" or just "GET HELP." You can get the current index of the files available from NICSERVE by issuing the command "GET INDEX." EJECT The following JCL code may be used to send requests to NICSERVE: //STEP1 EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=dsname,DISP=SHR //SYSUT2 DD SYSOUT=M,DEST=(BITNIC,MAILER) //SYSIN DD DUMMY where dsname is the fully qualified data set name containing the GET command. You must use SYSOUT=M and DEST=(BITNIC,MAILER). For NICSERVE to recognize the file as mail, the output class (SYSOUT) must be M. The TRANSMIT command sends messages using output class B, and NICSERVE cannot recognize them as mail. Therefore, you must create a data set containing the NICSERVE request and send it using the JCL above. Notice that you send the request to MAILER, NOT NICSERVE. (This is because you are sending the request via mail and not issuing the command interactively.) For each "GET" command issued, you will receive the data set you requested from NICSERVE prefixed with the following: Received: by BITNIC (Mailer X1.23b) id 6035; date request received by BI Date: date From: BITNET Network Support Center <NICSERVE@BITNIC> Subject: Your NICSERVE request: "GET filename filetype" To: your_userid@GSUMVS1 LISTSERV LISTSERV, BITNET'S list server, provides mailing list capabilities for the users of BITNET. To use an established mailing list simply use the list name for the userid and BITNIC as the node name. LISTSERV generates a copy of the message text for each individual userid on the list along with a comment that the message was sent to a list and the name of the list. You can get a copy of currently established distribution lists by issuing the command "GET LISTSERV GROUPS" to NICSERVE. DATABASE The database feature of BITNET is being developed by the BITNET Development and Operations Center (BITDOC). DATABASE provides user specified keyword access to subsets of larger databases. Retrieval capabilities are based on SPIRES, the Stanford Public Information EJECT Retrieval System. To use the DATABASE, you must create a data set that mimics a standard ARPANET header format. The format to use for DATABASE is given below. Be sure to turn NUM OFF when creating the data set in the ISPF editor, or DATABASE will not recognize it as mail. DATE: day, date month year FROM: your_userid@nodename TO: DATABASE@BITNIC SIGNIN command (if first time to access DATABASE) or LOGON user_number password (for all subsequent uses of DATABASE) database command . . . Note: All entries must begin in column one. DATE: must be the first line in the data set. There can be only one space after the : in the DATE and FROM entries. The TO: entry should line up with the others. The blank line between the TO: entry and the first database command (either SIGNIN or LOGON) is required. Any number of database commands may be issued, but each must begin on a new line. The first time you use the DATABASE, you must establish a user number and password. This is done through the SIGNIN command which must be the first command issued. The format of the SIGNIN command is: SIGNIN password where password is a contiguous string that is between 8 and 20 characters long. You will receive the following message from DATABASE@BITNIC: Received: by BITNIC (Mailer X1.23b) id 6035; date request received by BI Date: date From: DATABASE@BITNIC Subject: SIGNIN password To: your_userid@GSUMVS1 Comments: Processing SIGNIN request Your SIGNIN request has been processed. You have been assigned a user number (UN) of ###. Please keep track of the password you supplied on the SIGNIN command, since all DATABASE requests must be preceded with the line LOGON user_number password. Any subsequent time you use the DATABASE, you must issue the LOGON command as the first database command. EJECT The following JCL code may be used to send requests to DATABASE: //STEP1 EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=dsname,DISP=SHR //SYSUT2 DD SYSOUT=M,DEST=(BITNIC,DATABASE) //SYSIN DD DUMMY where dsname is the fully qualified data set name containing the database commands. Note that SYSOUT=M and DEST=(BITNIC,DATABASE) must be used. For a complete set of help files on the DATABASE server, issue the following DATABASE commands: HELP HELP ARPANET HELP DESIGN For a list of all retrievable subfiles, issue the command LIST. CONNECTIONS TO OTHER NETWORKS The BITNET network is connected to other networks through the use of gateways (nodes that are attached to more than one network). Gateway information can be requested from NICSERVE. Look in the INDEX file from NICSERVE to find the name of the file containing the gateway information you need. To transmit to a CSNET node, create a data set similar to the following: HELO GSUMVS1.BITNET VERB ON TICK nnnn MAIL FROM:<your_userid@GSUMVS1.BITNET> RCPT TO:<CSNETuserid%CSNETsite.CSNET@CSNET-RELAY.ARPA> DATA Date: date From: your_userid@GSUMVS1.BITNET To: CSNETuserid%CSNETsite.CSNET@CSNET-RELAY.ARPA Subject: (This is optional) Text of message goes here. Note that the line separating the headers from the text is REQUIRED. . QUIT EJECT Note: The <> signs are required in the TO: and FROM: header information. The blank line after the header information and before the text of the message is required. The . is required to terminate the text of the message. nnnn is simply a number you provide. It is returned to you if a problem arises in message transmission. Use the following JCL to transmit the data set: //STEP1 EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=dsname,DISP=SHR //SYSUT2 DD SYSOUT=M,DEST=(INTERBIT,SMTP) //SYSIN DD DUMMY Note: SYSOUT=M is required. The destination is not the ultimate destination of the message, but the gateway between BITNET and CSNET.