RSXNET is a program which allows asynchronous communcations between two computers (systems). Communications can be either directly between the computers using a synchronous null modem patch cable (see "HELP PATCH" for the wiring diagram), or over a dialup line (modem). Communications with the remote system (the system you want to talk to) is accomplished using a second port (asynchronous line) on the local system. Help can be obtained on a particular topic by typing : HELP topic subtopic subsubtopic ... Examples: HELP GET Additional information available: BAUD_RATE COMMANDS DUMP_FILE EXIT FILE_TYPES GET_FILE INTERRUPT INI_FILE INTRODUCTION LOG_FILE MCR_COMMAND MODEM_USAGE NOLOG_FILE PATCH_CABLE REMOTE_PORT SEND_FILE SNDRCV STARTUP STATUS SYSTEM_TYPE 2 BAUD_RATE You must specify the baud rate of the port connected to the remote system. If you are communicating with the remote over a modem, the baud rate will be either 300 or 1200 baud. The valid baud rates are: 50, 75, 110, 134, 150, 300, 600, 1200, 1800, 2000, 2400, 3600, 4800, 7200, or 9600. 2 COMMANDS The following is a list of the commands which can be issued at the RSXNET command level: BAUD_RATE, MCR_COMMAND, DUMP_FILE, EXIT, GET_FILE, HELP, INTERRUPT, LOG_FILE, NOLOG_FILE, REMOTE_PORT SEND_FILE, STATUS, SYSTEM_TYPE 2 CROSS_FILE Crossfile is currently unsupported by RSXNET. This question is asked when you specify "IBM" for the remote system type. It is used to determine if you are communicating with General Electrics' Cross File system. You must specify yes if you will be using the RSXNET "DUMP" command to send file(s) to the Cross File editor. 2 DUMP_FILE This command is used to dump a file to the remote system. It is usually used if the remote system doesn't have the SNDRCV program. When using this command, there must be a program running on the remote system to accept the characters being dumped to it. Using the "CREATE file_name" command works very nice. 2 EXIT This command is used to exit from RSXNET. You can also exit by typing a CTRL/Z. 2 FILE_TYPES At the current time, only one type of file can be transmitted in RSXNET. This limitation will stay in effect until the protocol used between RSXNET and SNDRCV is enhanced. The type of file that can be transmitted is variable length files with implied carriage control (FD.CR). This is the type of files created by the CREATE command and by the editors (EDT, TEC, SOS, KED, and EDI). A file with internal carriage control (R.VAR set but FD.CR missing) can be converted to implied carriage control simply by editing the file using TECO, and then exiting. To determine the carriage control type, the DMP utility can be used with the command "DMP TI:=filename.ext/HD/BL:0:0". The lines to examine are listed below: F.RTYP 002 = R.VAR ! Variable length file. F.RATT 002 = FD.CR ! Implied carriage control F.RSIZ 107 = 71. ! Maximum record size. ! Must not exceed 512. Additional information available: QWIKNET_FILES TASK_IMAGES 3 QWIKNET_FILES Qwiknet files (Q.QWK) can be converted into an implied carriage control files using a program called F2T. F2T creates an output file that can then be transmitted by RSXNET / SNDRCV. Once the file is transmitted, it can then be converted back into a Qwiknet file by using a program called T2F. An example of using these program is listed below: >F2T ******************* PSDI *** F2T *** V1.0 ******************** Converts fixed block files to text format QWIKNET drawing files, named *Q.QWK, are assumed to be 256-byte blocks. Others must be 512-byte blocks. Enter full source file name: CAL1982Q.QWK Enter full text file name: CAL1982Q.TXT Enter full source file name: ^Z > ( send/get the file to/from the remote. ) >T2F ******************* PSDI *** T2F *** V1.0 ******************** Converts text files from F2T to fixed block files Enter full text file name: CAL1982Q.TXT Original file name: CAL1982Q.QWK Block size: 256 Enter full name of new file: CAL1982Q.QWK Enter full text file name: ^Z > 3 TASK_IMAGES Task images are 512 byte fixed length files. These type of files must be converted to am implied carriage control file using a program called F2T before they can be transmitted by RSXNET. Once the file is transmitted, it can then be converted back into a task image file by using a program called T2F. After running T2F, if the file is a task image (.TSK extension), then it must be made contiguous using the COPY command before running it. An example of running these programs is listed below: >F2T ******************* PSDI *** F2T *** V1.0 ******************** Converts fixed block files to text format QWIKNET drawing files, named *Q.QWK, are assumed to be 256-byte blocks. Others must be 512-byte blocks. Enter full source file name: RSXNET.TSK Enter full text file name: RSXNET.TXT Enter full source file name: ^Z > ( send/get the file to/from the remote. ) >T2F ******************* PSDI *** T2F *** V1.0 ******************** Converts text files from F2T to fixed block files Enter full text file name: RSXNET.TXT Original file name: RSXNET.TSK Block size: 512 Enter full name of new file: RSXNET.TSK Enter full text file name: ^Z >COPY RSXNET.TSK /NV/CO >RUN RSXNET ! Now it's ready to run. 2 GET_FILE This command is used to GET (receive) a file from a remote system. The remote system MUST be running the SNDRCV program before issuing this command. You will be prompted for the REMOTE and RSX file names. Currently, you can only GET one file at a time. A typical GET sequence follows: RSXNET> GET Enter the name of the REMOTE file: [1,2]RUNOFF.DOC Enter the name of the RSX file(s): RUNOFF.DOC Additional information available: REMOTE_FILE RSX_FILE 3 REMOTE_FILE The REMOTE file name must be a legal file specification for the system you are talking to. At the current time, only one file at a time can be transferred. 3 RSX_FILE The RSX file name can be any RSX file specification. If you type the return key, the remote file name will be used on RSX. The remote file name is taken exactly as is. This includes the directory name (i.e., [1,24] or [ROBIN]). If you don't have the specified directory, you will have to specify the file name. 2 INTRODUCTION RSXNET is a program which allows asynchronous communcations between two computers (systems). Communications can be either directly between the computers using a synchronous null modem patch cable (see "HELP PATCH" for the wiring diagram), or over a dialup line (modem). Communications with the remote system (the system you want to talk to) is accomplished using a second port (asynchronous line) on the local system. When RSXNET is prompting you for a question, you have the following options: o typing question mark "?" followed by the return key or typing the escape key will give you help, o typing an exclaimation point (!) followed by the return key will back up to the previous question. o typing the return key selects the default answer if there is one. Default answers are shown in parenthesis; i.e., (DEC) o typing a CTRL/Z will exit to the system. If you are communicating with the remote system, and you want to exit, you must first type the interrupt character (CTRL/Y by default) to get to the command level, and then type either CTRL/Z or EXIT to exit to the system. 2 INI_FILE When RSXNET is started, an initialization file called RSXNET.INI is looked for in the current directory. If this file exists, RSXNET will read its input from the file instead of the terminal while asking the startup questions. After the startup questions are asked, the .INI file is close. The format of the RSXNET.INI is: 1. The exclaimation "!" and the semi-colon ";" characters can be be used in the first column to designate a comment line. 2. All other lines are used to answer the questions in RSXNET. If the line is blank, then the default answer for the question is used, otherwise the contents of the line are used to answer the next question. 3. If an error occurs answering any question, the .INI file is closed and all further input is read from the terminal. Additional information available: EXAMPLE_FILE 3 EXAMPLE_FILE The following is a typical RSXNET.INI file: ;**************************************************************** ; ; Initialization file for RSXNET. ; ; Write the output from the remote to a logfile (No): N ; Enter the port being used for the remote (TTn:) ; Enter the RSXNET interrupt character (CTRL/Y): ^A ; Enter the system type of the remote (DEC): ; Enter the baud rate for the remote port (9600): ;**************************************************************** Note that the up arrow followed by the character A will get converted into a CTRL/A by RSXNET. 2 INTERRUPT This command allows you to specify the interrupt character. The interrupt character is the character you type to get to command level (CTRL/Y by default). Any character can be specified except for carriage return, question mark, escape, or exclaimation point. 2 LOG_FILE This command allows you to specify the name of a log file to write the output from the remote system. The output from the remote system and questions asked by RSXNET will be written to both the log file and the terminal. Additional information available: LOCAL_OUTPUT REFORMAT OPEN_LOG_FILE 3 LOCAL_OUTPUT This question allows you to disable local output to the log file. Local output includes questions and various messages. If you only want remote output in the log file, answer "No" to this question. For example: Do you want local output in the logfile (Yes) ? N 3 REFORMAT After exiting from RSXNET, the log file must be reformatted. This is done using a teco macro called REFORMAT. This program removes nulls, removes deleted characters (i.e. BS SP BS), converts LF/CR to CR/LF, etc. It creates an output file in a format which you can then edit (if desired). For example: > TEC @LB:[1,2]REFORMAT REFORMAT Version 3.0 - Reformats log files created by VAXNET Enter name of log file (.LOG)? RSXNET Reformatting complete ... > 3 OPEN_LOG_FILE If a log file is already open, you have the option of either using the current log file, or you can close the current log file and specify a new log file name. 2 MCR_COMMAND To issue a MCR command, you must type MCR followed by the command to be executed. All commands including EDT, LIST, etc. are valid. For example: Rsxnet> MCR DIRECTORY ! Will print a directory. 2 MODEM_USAGE Once the remote port being used is attached by RSXNET, the modem connection can be established. The phone call to the remote system MUST be made from the phone being used for the modem. You CANNOT transfer the call to the modem as you can with synchronous modems; you'll loose the connection. The modem can be set up in one of two modes as follows: o in the normal modem set up, the voice/data switch must be in the voice position to place the call. After you establish the connection with the remote system, you have the carrier signal (high pitch), you place the voice/data switch to the data position. Once in data position, you should see the Data Set Ready (DSR), Clear To Send (CTS), Carrier (CXR), and High Speed (HS) if you are operating at 1200 baud. o the modem can be setup in unattended disconnect mode. This mode is enabled by toggling the "Unattended Disconnect switch A1" and the "Non-standard options switch A6" within the modem. This is done so the modem can be hungup from VAXNET by turning DTR off. RSXNET can NOT hangup the modem since RSX-11M does not support the hangup function. Your DTR lamp MUST be lite before attempting the following procedure. DTR will be lite if you are patched into a RSX-11M port properly. If DTR is not lite, the modem will be hungup immediatly after following the procedure below. The procedure for establishing the connection in this mode is: - call the remote system and get the carrier signal, - toggle the voice/data switch to the data position, - hangup the phone up, - now toggle the voice/data switch back to the voice position. You should now see DSR, CTS, CXR, and the HS lamps. 2 NOLOG_FILE This command closes the current log file. 2 PATCH_CABLE A synchronous patch cable is required to communicate directly between two computers without using modems. This cable must be constructed as follows: WIRING DIAGRAM FOR SYNC. NULL MODEM (MODIFIED PATCH CABLE) TD 2 ..................... 3 RD 3 ..................... 2 RTS 4&5.................... 8 DSR 6 ..................... 20 CD 8 ..................... 4&5 DTR 20 .................... 6 2 REMOTE_PORT The remote port (asynchronous line) being used for RSXNET to communicate with the remote computer (system) can be either connected directly to a system in-house using the synchronous null modem patch cable, or connected using a modem (see "HELP MODEM" for getting modem connection established). This port can be any terminal line not being used (logged in). A logical name called RM0: can be created to assign the remote port. If this logical name exists, the terminal assigned to RM0: is used as the default answer when the remote question is asked. For example: >ASS TT7: RM0: >RUN RSXNET RSXNET Version 3.0 -- Asynchronous Communications Program Do you want help information displayed (No): Write the output from the remote to a logfile (No): Enter the port being used for the remote (TT7:) 2 RETURN To return to entering commands at the remote system from the RSXNET command level, simply type the RETURN key. 2 SEND_FILE This command is used to send (transmit) a file to the remote system. The remote system MUST be running the SNDRCV program prior to issuing this command. You will be prompted for the RSX and REMOTE file names. A typical SEND sequence follows: Rsxnet> SEND Enter the name of the RSX file(s): MAIL.MAI Enter the name of the REMOTE file: [ROBIN]MAIL.MAI Additional information available: CMD_FILE RSX_FILE REMOTE_FILE REMOTE_DIRECTORY 3 RSX_FILE The RSX file name can be any legal RSX-11M file specification. Wildcards ("*") can be specified in any part of the file specification (i.e., [*,*]*.*;*). The file names to be transmitted can come from a command file. A command file is specified by typing the @ sign in front of the command file name (i.e., @T.CMD). The extension of .CMD is the default. Type "HELP SEND CMD_FILE" for more information. 3 CMD_FILE Lines within the command file that don't start with a valid file name character (0-9, *, A-Z, [], or a-z) are skipped. This allows command files generated by SRD to be used without any editing. For example: >SRD TODAY.CMD=*.MAC/SV/NA/DA This command gives me a list of the highest version files sorted by name which were created on todays date. The contents of this file is in the following format: >TYPE TODAY.CMD ** DL1:[100,5] 23-APR-82 15:06 GETFIL .MAC;2 LOGFIL .MAC;2 SNDFIL .MAC;5 UTILTY .MAC;4 3 REMOTE_FILE The REMOTE file name must be a valid file specification for the system you are talking to. If you type the return key, the RSX file name will be used on the REMOTE. The RSX file name is taken exactly as is. This includes the directory name (i.e., [201,1]). If you don't have the specified directory on the remote system, you must specify the remote file name. 3 REMOTE_DIRECTORY When sending the remote system wildcard file specifications, you must specify one of the following for the remote directory: 1. You can specify the remote default directory be used. This is done by typing the return key. 2. You can specify the remote directory such as [1,24] if the remote is an RSX-11M system, or [ROBIN.TMP] if the remote is a VAX/VMS system. 3. You can specify an asterisk "*" if the local file name should be transferred with its associated UIC. This mode is used to transfer the local file to the same UIC on the remote system. 2 SNDRCV SNDRCV is the program run on the remote system to communicate with RSXNET during file transmission (either GET or SEND). SNDRCV is started by one of the following commands: o if you are communicating with a VAX system, SNDRCV is started by typing the command "MCR SNDRCV". o if you are communicating with an RSX-11M system, then SNDRCV is started by typing the command "RUN $SNDRCV". In either case, the following message is displayed after SNDRCV is started. SNDRCV Version 2.0 started ... Type CTRL/X to abort. At this point you should type the interrupt character (CTRL/Y by default) to get the RSXNET command prompt. Be careful not to type any other characters since they will be accepted by SNDRCV and interpreted as commands from RSXNET. After you get the RSXNET command prompt, you should type either GET or SEND and the file name questions associated with each command. After the questions are answered, the file transmission begins. The status report on the terminal is updated after each record transmitted. If the status report stops updating momentarily, be patient, there may have been a transmission failure. After a timeout period (currently 30 seconds), transmission should continue. If the transmission doesn't continue, you should type a single CTRL/C to abort the transmission. To abort the SNDRCV program, you must type CTRL/X followed by the return key. If SNDRCV doesn't abort after the first attempt, try several times; the second try usually does it. 2 STARTUP Before establishing the connection with the remote system either in-house or over a modem, do the following to start RSXNET. After you are logged into RSX-11M, startup RSXNET by typing "RSX" if RSXNET is installed, or by typing "RUN $RSXNET". You must be privileged to issue the "RUN $RSXNET" command since RSXNET is a privileged program. A typical startup dialogue follows: >RUN RSXNET RSXNET Version 3.0 -- Asynchronous Communications Program Do you want help information displayed (No): Write the output from the remote to a logfile (No): Enter the port being used for the remote (TT5:) Enter the RSXNET interrupt character (CTRL/Y): Enter the system type of the remote (DEC): Enter the baud rate for the remote port (9600): Username: ROBIN Password: Welcome to VAX/VMS Version V2.5 Welcome to the PSDI vax11/780 Signed on terminal _TTE1: at 21-APR-1982 12:17:39.15 $ ( CTRL/Y was typed here to get to RSXNET command level. ) Rsxnet> EXIT > Caution: If you exit from RSXNET, the remote port is deattached. This means that any incoming data will be sent to MCR. The MCR will think someone is attempting to login to the system. If this occurs, the local and remote systems will continuously echo characters back and forth (initiating HELLO). This results in all the system buffers being used up and the system hanging. To avoid the above problem, either set the remote port slave and noecho before starting RSXNET, or don't exit RSXNET until the modem is hungup. If you need to issue a MCR command to get a directory or edit a file, use the "MCR" command from RSXNET command level. 2 STATUS This command is used to get a status report of how RSXNET is currently setup. The following a an example type out: Rsxnet> STATUS RSXNET Status Report: Log file name: DL1:[100,5]RSXNET.LOG;1 Remote port: TT3: Interrupt: ^A System type: DEC Baud rate: 9600 Rsxnet> 2 SYSTEM_TYPE This command is used to specify the type of remote system you are communicating with. This sets up various flags within RSXNET to determine how to talk to the remote. For example, if you specify IBM, a local echo will be performed since IBM (TSO) doesn't echo characters sent to it. The valid system types are: APPLE, DEC, IBM, UNIX, and XXDP. 2 RSXNET RSXNET is a program which allows asynchronous communcations between two computers (systems). Communications can be either directly between the computers using a synchronous null modem patch cable (see "HELP PATCH" for the wiring diagram), or over a dialup line (modem). Communications with the remote system (the system you want to talk to) is accomplished using a second port (asynchronous line) on the local system. RSXNET gives you the ability to create a log file of your terminal sesson with the remote system (very nice for creating documentation) and/or allows file transmission between the systems. File transmission can be done using one of the methods listed below: o You can open a log file and use a TYPE command at the remote system to receive an ASCII file from the remote and/or you can also use the RSXNET DUMP command to send an ASCII file to the remote. o The alternate method requires a program called SNDRCV on the the remote system. Using this method (see GET and SEND commands), error checking and retransmission is performed on the data being transmitted.