All Packages Class Hierarchy Class Search Index
The main control class for the Gateway 50 is Gateway50. Each instance connects to a Gateway 50 on consecutive TCP ports. Each TCP port is routed to an SNA LU in the Gateway 50 configuration, and is controlled by an instance of the JBMLU class. The class overview for these two classes mentions the configuration settings needed by the Gateway 50.
If the communication is full duplex (so that the CTS,RTS signals can be jumpered), 8-wire UTP modular cable (used for 10baseT) can be used with RS232 modular adapter kits instead of the G50 DTE adapter with a modem cable. Wire the adapter kits with one each of types 8M and 9G below. Connect the 9G to the Gateway 50 and the 8M to the modem.
DB25 T Y P E S wh-bk-rd-gr-yl-bl color | 8M | 9G | --------+----+----+ BLU | 17 | 23 | for type 8M, jumper 4 - 9 ORA/WHT | 8 | 4 | for type 9G, jumper 8 - 20 BLK | 2 | 3 | RED | 3 | 2 | GRN | 7 | 7 | YEL | 20 | 5 | BRN/BLU | 6 | 18 | GRY | 15 | 22 | (for Serial# < 300, use 24 instead of 22)The Gateway monitors DSR, not DCD, for Activate PU. To detect loss of carrier, configure the modem so that DSR is true while the modem is on-line. This will work with both the G50 DTE and the modular adapters.
Usage: java bmsi.sna.GatewayApp [-xXID] file1 [file2 ...] Reports the App ver and current XID for each listed file. -xXID changes the XID of following files, XID is a hexadecimal numberand here is some sample output:
$ java bmsi.sna.GatewayApp /tftpboot/j*.* /tftpboot/jbmC1400.116: App Ver 04.XID2.116, XID 13c1400 /tftpboot/jbmgw50.115: App Ver 04.XID2.115, XID 139e028 /tftpboot/jbmgw50.116: App Ver 04.XID1.116, XID 139e028 /tftpboot/jbmgw50.bin: App Ver 04.XID1.116, XID 139e028The JBMStatus class can inspect the XID currently loaded in a Gateway 50. For example:
$ java bmsi.sna.JBMStatus fred:pebbles@g50 Gateway at g50 Firmware ver 04.XID1.118 XID 139e028
The Gateway uses only the IP address and Server address from the BOOTP
data. It does not use home dir or boot file. On unix servers,
you must set up the path
/jbmgatew/jbmgw50/jbmgw50.bin as a
link to the application binary, and add the line
for the reset to work.
Mohammed tells me that by setting the unit and server IP address to zero in "Remote Access Information" and in Port/Ether/Hardware, the Gateway will query BOOTP for these addresses at reset or poweron. I tried this, and it does not work.
Currently, the SNA3770 interface supports text data only. The Gateway 50 supports binary file transfer as well, and this will be supported through an extended interface later.
The NetSpooler class is a
simple RJE server that uses
Spooler to submit text files
as jobs and spool print output to disk. It is 100% Java and should run on
any JDK 1.1 compatible system.
The FIFOSpooler class implements a spooler compatible with existing BMS SNA/RJE spooler programs. Signon, commands, and jobs are entered through a unix FIFO in a simple format. Console output is written to stdout, status messages to stderr. Printer output is written to a spool directory. It depends on a unix FIFO for submitting jobs, and is not 100% Java since is uses the BMS posix package.
bmsi.comm.Waitfor. These are BMS classes from other packages used by the Gateway interface.
A ready to run package with all needed third party classes can be download here (netspool.jar). This still needs some documentation on how to set up job and output directories and signon files.
In order to compile
Waitfor, you will need the
package, or simply remove the
DEBUG code in
which uses it.
Spooler class uses the
Java General Library for its
job queue. We still use JGL 1.1. For later versions, you will need to
FIFOSpooler class uses some process id methods from
the Java POSIX package.