home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 the Most Complete Collection
/
OS2_The_Most_Complete_Collection_Powersource.iso
/
protocol
/
tcp20c1.exe
/
BASECSD.DOC
< prev
next >
Wrap
Text File
|
1994-06-13
|
90KB
|
1,961 lines
*************************************
********* UN56401 CORRECTIVE SERVICE DISKETTE *********
*************************************
TCP/IP 2.0 for OS/2 Corrective Service Diskette Information for:
TCP/IP 2.0 for OS/2 Base Kit
TCP/IP 2.0 for OS/2 Applications Kit
This README file for the corrective service diskette (CSD) reflects
new and changed functions for TCP/IP 2.0 for OS/2, and corrections
to the information. This CSD applies to the Base Kit and the
Applications Kit.
--------------------------------------------------------------------
Topics included in this CSD are:
1. Installing this CSD
2. Previous CSD Information
3. Obtaining CSDs
4. Remote Installation (CID)
5. RUNNING TCP/IP FOR OS/2 FROM A FILE SERVER
6. Autostart Using INETD
7. Packet Tracing Programs
8. Changes to FTP, FTPD, and FTPPM
9. Configuring KEEPALIVE Servers: the INETCFG Command
10. TelnetPM Cursor Modification
11. SLIP
12. SNMP Enhancements
13. Default 3270 Emulator Keyboard Mappings
14. The DPKT Utility
15. Configuration Notebook
16. Configuring a Token-Ring Adapter using BOOTP
17. SETTERM
18. SendMail Server and Client
19. REXEC and RSH Redirection
20. Programming Support
21. Applications Kit / ANYNET Users Information
22. APARs Fixed
--------------------------------------------------------------------
1. Installing this CSD
To install this CSD from a diskette at your workstation, insert the
diskette into your A: drive and enter:
A:>TCPINST
--------------------------------------------------------------------
2. Previous CSD Information
This CSD incorporates the corrective service and new functions that
were previously released in CSD UN50382. Please see the file
README.BAS in the <tcpip>\DOC directory for a description of the
functions that were originally released in UN50382.
--------------------------------------------------------------------
3. Obtaining CSDs
You can obtain Corrective Service Diskettes (CSDs) electronically
by:
o Using FTP to access SOFTWARE.WATSON.IBM.COM as Anonymous.
NOTE: Fixes for TCP/IP for OS/2 are located in the
pub\tcpip\os2 directory.
o Establishing a modem connection to the NCSBBS bulletin
board at 1-919-517-0001.
NOTE: Set your modem settings to: none,8,1.
The latest CSDs for TCP/IP Version 2.0 for OS/2 are shown in the
following table:
+=============================+===========================+
| KIT NAME | PACKAGE NAME |
+=============================+===========================+
| Applications Kit | APP20CSD.PKG |
+-----------------------------+---------------------------+
| Base Kit | TCP20CSD.PKG |
+-----------------------------+---------------------------+
| Domain Name Server Kit | DNS20CSD.PKG |
+-----------------------------+---------------------------+
| DOS/Windows Access Kit | DOS20CSD.PKG |
+-----------------------------+---------------------------+
| Extended Networking Kit | XNT20CSD.PKG |
+-----------------------------+---------------------------+
| NetBIOS Kit | NET20CSD.PKG |
+-----------------------------+---------------------------+
| Network File System Kit | NFS20CSD.PKG |
+-----------------------------+---------------------------+
| OSF/Motif Kit | MOT20CSD.PKG |
+-----------------------------+---------------------------+
| Programmer's Tool Kit | PGM20CSD.PKG |
+-----------------------------+---------------------------+
| X Window System Client Kit | XCL20CSD.PKG |
+-----------------------------+---------------------------+
| X Window System Server Kit | PMX20CSD.PKG |
+-----------------------------+---------------------------+
*************************************************
********* UN56401 CORRECTIVE SERVICE DISKETTE STARTS HERE *********
*************************************************
--------------------------------------------------------------------
4. Remote Installation (CID)
If you are using CID technology to install TCP/IP, the
statements in the response file that contain the INSTALL_NAME and
the LINK_NAME must preceed the statements that contain the
EXEC, DEPENDENCY, or LINK_INFO. In addition, since CSDs are
cumulative, you must erase or remark out the lines in your
DEFAULT.RSP file that pertain to the previous CSD level for the
component you want to enable.
--------------------------------------------------------------------
5. RUNNING TCP/IP FOR OS/2 FROM A FILE SERVER
If you want to conserve your local disk space, you can run TCP/IP
for OS/2 from a file server using a requester (such as IBM's OS/2
LAN Requester or TCP/IP's NFS client).
To run TCP/IP for OS/2 from a server, ensure the following:
1. You have the required local files
2. Your PATH statement and environment variables contain
the correct information
3. You have access to the file server
--------------------------
5.1 REQUIRED LOCAL FILES
Although many of the files used by TCP/IP are common and can be
accessed on the file server, certain files contain configuration
information and are unique to each installation. These files must
be located in directories on your workstation.
In the tcpip\ETC subdirectory on your workstation, ensure that you
have copies of all the files from the \ETC subdirectory on the file
server.
In the tcpip\BIN subdirectory on your workstation, ensure that you
have the following files:
o CNTRL.EXE
o SETUP.CMD
o TCPSTART.CMD
o PMX.EXE
o TCPIPCFG.EXE
o TELNET.EXE
In the \IBMCOM\PROTOCOL subdirectory on your workstation, ensure
that you have all LAPS files, including the following files:
o INET.SYS
o IFNDIS.SYS
o TCPIP.NIF
If you are using NFS to access the server, also ensure that you have
the following files in your tcpip\BIN subdirectory:
o NFS200.IFS
o NFSCTL.EXE
o NFSSTART.CMD
o ARP.EXE
o ROUTE.EXE
o IFCONFIG.EXE
o MOUNT.EXE
o QMOUNT.EXE
o NFSWAIT.EXE
And in your tcpip\DLL subdirectory:
o TCPIPDLL.DLL
o CNBAPP.DLL
o CNBNFS.DLL
o CNBPMX.DLL
o CNBSTK.DLL
In addition, you need the following empty subdirectories:
o TCPIP\DOC
o TCPIP\TMP
--------------------------
5.2 SET PATH STATEMENT AND ENVIRONMENT VARIABLES
To run TCP/IP from a server, the PATH statement and the environment
variables must point to the proper locations on the server and on
your workstation.
The PATH statement must point to the directory on your workstation
that contains the local TCP/IP batch files and executables and to
the directory on the file server that contains the TCP/IP
executables. For example, if you access a network drive that
contains TCP/IP as your X drive, your PATH statement would look
similar to this:
PATH=...;C:TCPIP\BIN;X:\TCPIP\BIN;
The LIBPATH statement must point to the directory on your
workstation that contains the local TCP/IP dynamic link libraries
(DLLs) and to the directory on the file server that contains the
TCP/IP DLLs. For example, if you access a network drive that
contains TCP/IP as your X drive, your LIBPATH statement would look
similar to this:
LIBPATH=...;C:TCPIP\DLL;X:\TCPIP\DLL;
The ETC environment variable must point to the ETC subdirectory on
your workstation. For example:
SET ETC=C:\TCPIP\ETC
--------------------------
5.3 ACCESS THE SERVER
If you are using NFS to access the file server, you will need to
start TCP/IP and NFS before you access the file server. However,
no other TCP/IP services should be started until you access the file
server. If you are using other methods to access the file server,
you should access the file server before using any services of
TCP/IP.
--------------------------------------------------------------------
6. Autostart Using INETD
If you use INETD to autostart TCP/IP services, any parameters that
you specify will be ignored.
However, for TFTPD, you can add the following environment variable
to your CONFIG.SYS to specify the default path:
SET TFTPDPATH=<path>
For REXECD, you can add the following environment variable to
your CONFIG.SYS to specify the timeout:
SET REXECDTIME=<time>
--------------------------------------------------------------------
7. Packet Tracing Programs
TCP/IP for OS/2 provides a set of utilities that you can use to
trace packets. Tracing packets is useful in diagnosing problems
at your workstation. These utilities allow you to:
o Initiate a trace
o Convert trace information to human-readable output
o Convert trace information to network analyzer data
--------------------------
7.1 Initiating a Trace
The utility, IPTRACE, traces all packets received from and sent
to an interface.
The syntax of the IPTRACE command is:
>>--iptrace--.-----.--.--------------.------------------------><
'- -i-' | <----------< |
'-- interface--'
-i Specifies that only IP packets are to be traced. The
default is to include all information (such as hardware
type). Certain interfaces (for example, X25 and SNALINK)
require this parameter.
interface
Specifies an interface to be traced (for example, lan0
or sl0). If not specified, all interfaces are traced.
NOTES:
1. IPTRACE writes data to IPTRACE.DMP in the directory from
which you initiated the IPTRACE command. IPTRACE records all
traffic sent and received, but does not check for sufficient
disk space to record that information. As a result, running
IPTRACE can impact your workstation's performance as the
IPTRACE.DMP file continues to grow larger.
2. IPTRACE is not a network monitor. It can trace only data
received by and sent from the specified interfaces.
3. IPTRACE provides a time stamp, recording when the packet
was sent or received.
4. To stop IPTRACE, press Enter, Ctrl-Break, or Ctrl-c.
5. Use IPFORMAT to convert the IPTRACE.DMP file into a
user-readable format.
--------------------------
7.2 Converting Trace Information
The IPFORMAT utility converts the data in the IPTRACE.DMP file
and the SLIPTRC.DMP file (if the file was created without VJ header
compression on) to either human-readable format, which is displayed
to the screen, or to data to be used as input to a network analyzer.
If you choose to convert the data into human-readable format, you
can redirect the output to a file.
IPFORMAT reads the header information in the trace to determine
the type of packet received; for example, token-ring (TRC) or
ethernet (ENC). It then separates the data by the IP, TCP, UDP,
and ICMP layers. The rest of the packet is displayed as hexadecimal
output.
The syntax of the IPFORMAT command is:
.- -f IPTRACE.DMP-.
>>--ipformat--.-----.--.-----.--+-----------------+--.-----.--->
'- -a-' '- -d-' '- -f filename----' '- -h-'
>---.-----.---.---------------.--.-----.--.-------------.-----><
'- -n-' '- -s hwaddress-' '- -x-' '- > filename-'
-a Do not format ARP or RARP packets.
-d Do not display the data portion of a packet.
-f filename
Specifies the input file name. The default is
IPTRACE.DMP.
-h Display the raw data packet after the formatted
information.
-s hwaddress
Format data only for the specified hardware address.
'hwaddress' is the 12-digit hexadecimal address for the
Ethernet or token-ring adapter. You can use the
NETSTAT -N command to display this address.
-n Do not display hexadecimal data for unknown data type.
-x Converts IPTRACE data to a format that can be read by
a Network General Sniffer.
> filename
Redirect the output to the specified file.
-? Display help information.
--------------------------------------------------------------------
8. Changes to FTP, FTPD, and FTPPM
--------------------------
8.1 IMAGE Subcommand for FTP
FTP now supports an image transfer type.
The IMAGE subcommand sets the file transfer type to image. The
image file transfer type is useful for image transfers, such as
executable files. Using the IMAGE subcommand is the same as issuing
the TYPE subcommand with the binary parameter. You can issue the
IMAGE subcommand with the abbreviation IM.
>>--image--------------------------------------------------------><
--------------------------
8.2 IMAGE Parameter for TYPE Subcommand for FTP
The TYPE subcommand now supports the IMAGE parameter.
>>--type--.---------.--------------------------------------------><
|- ascii--|
|- binary-|
'- image--'
image Specifies the file transfer type as image (binary).
Specifying the TYPE subcommand with the image parameter
is the same as issuing the IMAGE subcommand.
--------------------------
8.3 FTPD Trace Facility
FTPD now includes a trace facility. The FTPD command uses the
FTPD.EXE program to start the FTP server. It runs as a task until
you shut down the server.
SYNTAX
>>--ftpd--.--------------.--.------------.--.-----.--------------><
'- -c codepage-' '- -p portno-' '- -t-'
-c codepage
Specifies the ASCII codepage used by the remote host. If
you do not specify a codepage, the data is sent
untranslated. Possible values are:
TCPDECMU DEC Multinational codepage
TCP8859 ISO 8859 codepage
NONE PC codepage 850
-p portno Specifies the port that you want FTPD to use. If you omit
this option, FTPD uses its well-known port assignment.
-t Specifies that FTPD is to trace control connection
commands and replies. FTPD places the information into
FTPD.TRC in the subdirectory specified by the ETC
environment variable. Tracing will continue until you
terminate FTPD.
--------------------------
8.4 TRACING FTPPM COMMANDS/REPLIES
If you select the Trace Commands/Replies option, from the Options
pull-down menu, you can trace your FTPPM session activities. The
commands you issue and the replies you receive are written to a file
named FTPPM.TRC in the directory specified by the ETC environment
variable.
The trace file is overlayed (information is not appended) each time
the trace option is selected.
--------------------------
8.5 Ending an FTPPM Session
You can end an FTPPM session and disconnect from all remote hosts
in one of the following ways:
o Select the Close all Connections option from the Remote
pull-down menu. You will be prompted to confirm that you
want to end all connections.
o Press the F3 key to exit. You will not be prompted to
confirm that you want to exit the session.
o Close the FTPPM window. You will not be prompted to confirm
that you want to exit the session.
NOTE: Options set for the current session are not saved for
future sessions.
--------------------------------------------------------------------
9. Configuring KEEPALIVE Servers: the INETCFG Command
The INETCFG command configures TCP/IP parameters.
>>--inetcfg---- keepalive=value-------------------------------><
value The time in minutes until the KEEPALIVE timer expires on
a TCP socket. Valid values are from 0 to 120. If you
specify 0, INETCFG sets the timer to 120.
Note: To use the INETCFG command, Telnetd cannot first be
started with INETD.
--------------------------------------------------------------------
10. TelnetPM Cursor Modification
You can use the Options menu to alter the way the cursor is
displayed during your TelnetPM session.
Your cursor can be defined as follows:
o Character
- Underscore (Default)
- Solid block
- Frame block
o Blink
- On (Default)
- Off
o Intensity
- Normal (Default)
- Dim
To select cursor values for your session:
1. Select (using mouse button 1 to click on the field) Options
from the menu bar.
2. Select the Cursor option.
(The current default is indicated by a checkmark to the left
of the option on the drop-down menu.)
3. Select the desired option.
--------------------------------------------------------------------
11. SLIP
--------------------------
11.1 The SLIP Command
The SLIP command is used to start the main slip driver. Since
the majority of users only use a single interface, command line
options for the sl0 interface have been added to simplify making
a single interface SLIP connection. These options override the
default values in the configuration file and cannot be set using
the Configuration Notebook (TCPIPCFG.EXE).
.- -f SLIP.CFG----.
>>--slip--.--------.--+-----------------+--.------------------.-->
'- -comn-' '- -f config_file-' '- -hangup command-'
>--.--------------------------.--.-----------------.------------->
'- -ifconfig ipaddr ipdest-' '- -modem command-'
>--.------------.--.-----.--.----------.--.--------------.------->
'- -mtu size-' '- -p-' '- -rtscts-' '- -speed baud-'
>--.----------------------.--.------------.--.------.-----------><
'- -d--.-------------.-' '- -t--.---.-' '- -vj-'
'- > filename-' |-i-|
'-o-'
Displaying SLIP Help
>>--slip-- -?---------------------------------------------------><
-comn Specifies the communications port (n) to be used for
the sl0 interface.
-f config_file
Specifies the name of the SLIP configuration file.
The default is SLIP.CFG.
-hangup command
Specifies a command to send to the sl0 communications
port upon exit.
-ifconfig ipaddr ipdest
Specifies IP addresses to use to configure sl0.
-modem command
Specifies a command to send to the sl0 communications
port.
-mtu size
Sets the sl0 interface MTU to the specified size.
-p Specifies that SLIP communications port and INET
interface threads be placed in the highest foreground
server priority. This prevents packet loss on slow
machines or in heavily loaded environments.
-rtscts
Specifies asynchronous card-to-modem flow control via
the RTS (request-to-send) and CTS (clear-to-send)
handshaking signals (RTS/CTS hardware flow control).
At baud rates above 2400, this option should be enabled
to prevent modem buffer overruns and packet loss.
-speed baud
Specifies the baud rate to which to set the sl0
communications port.
-d Enables debugging output.
NOTE: Because this option can produce large amounts of
output that can degrade performance, you may want to
redirect the debugging output to a file.
> filename
Specifies a file to which to redirect debugging output.
-t Specifies that SLIP begin tracing as follows:
-t Traces both input and output packets.
-ti Traces only input packets.
-to Traces only output packets.
Data is written to SLIPTRC.DMP in the directory from
which SLIP was started. To stop the trace, press
Ctrl-c or Ctrl-Break. This option produces packets in
INET trace format. You can read the output using
IPFORMAT.
NOTES:
1. As the SLIPTRC.DMP file increases in size, the
performance of your workstation can be affected.
2. SLIP does not check to ensure that there is
sufficient hard disk space to record the data.
-vj Specifies that SLIP is to enable Van Jacobsen (VJ) header
compression for the sl0 interface.
NOTE: If VJ header compression is on, you will not be
able to use IPFORMAT to read the SLIPTRC.DMP file.
-? Displays the list of parameters and their meanings.
--------------------------
11.1.1 SLIP Examples
Example 1:
slip -rtscts -modem atdt9,999-9999 -ifconfig 9.67.111.1 9.67.111.2
-speed 38400 -com2 -mtu 1006 -vj
This command:
- Starts SLIP using the sl0 interface
- Sets RTS/CTS hardware flow control on
- Sends the command string "atdt9,999-9999" to the modem
(dial out) attached to comport 2
- Configures the interface with local IP address 9.67.111.1
and remote peer IP address 9.67.111.2
- Sets the baud rate to 38.4K bits
- Sets the communications port to com2
- Sets the mtu to 1006 bytes
- Enables Van Jacobson Header compression
Example 2:
slip -rtscts -modem ats0=2s7=30 -ifconfig 9.67.111.2 9.67.111.1
-speed 38400 -com1 -mtu 1006 -vj -p
This command:
- Starts SLIP using the sl0 interface
- Sets RTS/CTS hardware flow control on
- Sends the command string "ats0=2s7=30" to the modem (dial in)
attached to communications port 1
- Configures the interface with local IP address 9.67.111.2
and remote peer IP address 9.67.111.1
- Sets the interface baud rate to 38.4K bits
- Sets the communications port to com1
- Sets the mtu to 1006 bytes
- Enables Van Jacobson Header compression
- Schedules SLIP execution using time critical server priority
--------------------------
11.2 The SLIPTERM Command
The SLIPTERM command now has the -f and interface parameters.
.- -f SLIP.CFG----.
>>--slipterm--.-------------.--+-----------------+------------->
'- -w---.---.-' '- -f config_file-'
'-n-'
.-sl0-.
>--+-----+--.-----.-------------------------------------------><
'-sln-' '- -d-'
-w Invokes the SLIPWAIT utility.
n Specifies the number of seconds to wait (the
default is 30).
-f config_file
Specifies the name of the SLIP configuration file. The
default is SLIP.CFG.
sln Specifies the interface to be addressed. The default
is SL0.
-d Enables debugging mode.
--------------------------
11.3 The SLIPHOLD Command
The SLIPHOLD command now has the -f and interface parameters.
.- -f SLIP.CFG----. .-sl0-.
>>--sliphold--+-----------------+--+-----+--------------------><
'- -f config_file-' '-sln-'
-f config_file
Specifies the name of the SLIP configuration file. The
default is SLIP.CFG.
sln Specifies the interface to be addressed. The default
is SL0.
--------------------------
11.4 SLIP Correction
The description of the MODE command in the Installation and
Administration manual is incorrect. The speed parameter is the
async-to-modem bit rate.
<speed> is the async-to-modem bit rate (1200 to 38400).
The async card UART (universal asynchronous receiver/transmitter)
rate is not the same as the modem line rate. If the modem rate and
async communications port rate are different, then data flow control
is used to coordinate the async card and the modem; to prevent one
from overrunning the other. This is called "pacing". Pacing is
required for newer modems to use data compression. If the two rates
are the same, then the modem tries to adjust its rate to that of the
async communications port. This is called "bit rate adjustment".
It is recommended that you use as high a bit rate as is supported
by the hardware.
If you are connecting to another modem, the modems need to negotiate
the highest line rates possible. To do this, start SLIP with the
-rtscts parameter.
--------------------------
11.5 New Sample Attachment Scripts
Three new sample attachment scripts have been added for SLIP:
1. ATDIAL.CMD is a sample attachment script that can be used
for a basic SLIP client that does not require a user ID and
password prior to starting a SLIP connection.
2. DIRECT.CMD is a sample attachment script that can be used
for a direct connection between two asynchronous lines.
3. ATANS.CMD is a sample attachment script that can be used for
putting your modem into auto answer mode to enable others to
dial into your host.
These new samples support multiple SLIP interfaces.
--------------------------
11.6 Changes to the Way Parameters Are Passed to SLIP Attachment Scripts
If the ipdest and ipaddress keywords appear in your SLIP
configuration file, the interface name (slx), IP address,
destination address, and dial commands are passed to the REXX
attachment scripts.
If the ipdest or ipaddress keywords do not appear in your SLIP
configuration file, only the interface name and dial commands
are passed to the REXX attachment scripts.
--------------------------
11.6.1 Example of Configuring SLIP for More Than One Interface
Following is an example of a SLIP configuration file for 3
concurrent dial-in sessions:
interface sl0 {
mtu=296 # Use 296 byte MTU for interface 0.
compression=off # Disable VJ compression.
device = com1 # Use com1 for interface sl0.
ipaddress = 9.67.1.1 # Local IP address.
ipdest = 9.67.10.1 # Peer IP address.
attachcmd = atans # Rexx command to place modem in auto
# answer mode using AT command set and
# ifconfig the interface.
attachparms = "com1 38400" # Parameters passed to REXX
# command script.
}
interface sl1 {
mtu=296
compression=off
device = com2
ipaddress = 9.67.1.2
ipdest = 9.67.10.2
attachcmd = atans
attchparms = "com2 38400"
}
interface sl2 {
mtu=296
compression=off
device = com3
ipaddress = 9.67.1.3
ipdest = 9.67.10.3
attachcmd = atans
attparms = "com3 38400"
}
--------------------------------------------------------------------
12. SNMP Enhancements
--------------------------
12.1 The SNMP Command
The Simple Network Management Protocol (SNMP) is a protocol used
by network elements (for example, hosts and bridges) to exchange
information about network management. The snmp command provides
SNMP manager function to query SNMP agents for network management
information.
SYNTAX
RECEIVING TRAPS
.- -h localhost-.
>>--snmp--.---------------------------.--+---------------+-------->
| <-----------------------< | '- -h host------'
| .- 1-----------. |
'--- -d--+--------------+---'
'- debug_level-'
.- -c public---------.
>--+--------------------+-- trap---------------------------------><
'- -c community_name-'
SETTING MIB VARIABLE VALUES
.- -h localhost-.
>>--snmp--.---------------------------.--+---------------+--------->
| <-----------------------< | '- -h host------'
| .- 1-----------. |
'--- -d--+--------------+---'
'- debug_level-'
.- -c public---------. .- -t 6-------. .- -p 161--.
>--+--------------------+--+-------------+--+----------+-- set----->
'- -c community_name-' '- -t seconds-' '- -p port-'
<------------------------------<
>--- mib_variable-.-------.- value-------------------------------><
'- type-'
GATHERING INFORMATION ABOUT MIB VARIABLES
.- -h localhost-.
>>--snmp--.---------------------------.--+---------------+-------->
| <-----------------------< | '- -h host------'
| .- 1-----------. |
'--- -d--+--------------+---'
'- debug_level-'
.- -c public---------. .- -t 6-------. .- -p 161--.
>--+--------------------+--+-------------+--+----------+---------->
'- -c community_name-' '- -t seconds-' '- -p port-'
>--.- get-----.-- mib_variable-----------------------------------><
|- getnext-|
'- walk----'
Displaying SNMP Help
>>--snmp-- -?----------------------------------------------------><
-d Starts debugging.
debug_level
Specifies the debug level. There are currently 2 debug levels
(1 and 2). Level 2 provides more detailed debug and trace
information than does level 1.
-h host
Specifies the destination host to which you want to send a
request. This can be either an internet protocol address or a
host name. If you do not specify a host, the default is your
local host.
-c community_name
Specifies the community name used to access the specified
variables on the destination SNMP agent. If you do not
specify a community, the default is public.
NOTE: Community names are case sensitive.
trap SNMP waits for a trap from the specified host. If no host is
specified, SNMP waits for a trap from any host.
-t seconds
Specifies the amount of time (in seconds) that the SNMP client
waits for a reply from the SNMP agent. The default is 6
seconds.
-p port
Specifies the destination (agent) port. The default is 161.
set Sends a request to the SNMP agent to set a specific MIB
variable. SNMP then waits for a response, a trap, or a
timeout.
mib_variable
Specifies the MIB object, using its object descriptor (textual
name), object identifier using ASN.1 notation, or a
combination of the two. When used with WALK, this is the MIB
object prefix. A prefix can be any leading portion of the
complete object identifier.
type The type of value being set. To complete an SNMP SET request,
the SMI_type must be known. If no type is specified, SNMP
searches the compiled MIB and the MIB2.TBL to determine the
type. If the variable is not found, an error is returned. If
a type is specified, the type takes precedence over any type
that may be assigned in the MIB. The type and value must be
compatible. For example, if you specify a type of "number"
and a value of "foo," an error will be returned because "foo"
is not a number. Possible variable types are:
Types From MIB2.TBL ASN.1 SMI_types
=================== ===============
number or INTEGER
display
object or OBJECT_IDENTIFIER
internet or IPAddress
counter
gauge
ticks or TimeTicks
Opaque
NULL
value Specifies the value to be set by the SET function. If
white space is needed in the value, you must use double
quotes ("). If you want to set a variable to a value that
is also a type, you must specify the type.
get Sends a request to an SNMP agent for a specific management
information base (MIB) variable. SNMP then waits for a
response, a trap, or a timeout.
getnext
Sends a request to an SNMP agent for the next MIB variable
that lexicographically follows the mib_variable specified.
SNMP then waits for a response, a trap, or a timeout.
walk Issues a GETNEXT request for a specified prefix, then
continues to issue GETNEXT requests for as long as there are
variables that match the specified prefix. A prefix can be
any leading portion of the complete object identifier.
-? Displays help information.
--------------------------
12.2 The SNMPGRP Command
The snmpgrp command provides SNMP manager function to query SNMP
agents for a collection of information contained in tables and other
related MIB variables. This information is retrieved using the name
of the group or table of MIB variables.
SYNTAX
.- -h localhost-.
>>--snmpgrp--.---------------------------.--+---------------+----->
| <-----------------------< | '- -h host------'
| .- 1-----------. |
'--- -d--+--------------+---'
'- debug_level-'
.- -c public---------. .- -t 6-------. .- -p 161--.
>--+--------------------+--+-------------+--+----------+---------->
'- -c community_name-' '- -t seconds-' '- -p port-'
<-------------<
>---.-----------.------------------------------------------------><
|- sys------|
|- snmp-----|
|- ip-------|
|- icmp-----|
|- udp------|
|- tcp------|
|- tcptab---|
|- udptab---|
|- iproute--|
|- ipaddr---|
|- arptab---|
|- iftab----|
'- mediatab-'
Displaying SNMPGRP Help
>>--snmpgrp-- -?-------------------------------------------------><
-d debug_level
Specifies the debug level. There are currently 2 debug
levels (1 and 2). Level 2 provides more detailed debug
and trace information than does level 1. If you do not
specify a debug level, the default is 1.
-h host Specifies the host to which you want to send a request.
You can specify either an internet protocol address or a
host name. If you do not specify a host, the default is
your local host.
-c community_name
Specifies the community name of the simple network
management protocol agent on the destination host. If you
do not specify a community name, the default is public.
NOTE: Community names are case sensitive.
-t seconds
Specifies the amount of time (in seconds) that SNMPGRP
waits for a reply. The default is 6 seconds.
- p port Specifies the destination (agent) port. The default
is 161.
NOTE: The following list represents the names of the groups from
which you can choose. If you request more than one group,
your output will be displayed in the order in which the
groups appear in the list.
sys Requests the System group of MIB variables.
snmp Requests the SNMP group of MIB variables.
ip Requests the scalar MIB variables in the IP group.
icmp Requests the ICMP group of MIB variables.
udp Requests the scalar MIB variables in the UDP group.
tcp Requests the scalar MIB variables in the TCP group.
tcptab Requests the TCP connection table in the TCP group.
udptab Requests the UDP listener table in the UDP group.
iproute Requests the IP routing table in the IP group.
ipaddr Requests the IP address table in the IP group.
arptab Requests the AT table in the address translation group.
iftab Requests the Interface table in the interfaces group.
mediatab Requests the IP address translation table in the IP group.
-? Displays help information.
--------------------------
12.3 Changes to SNMP
The SNMP and SNMPGRP commands now search an internal table first to
find the requested information. If the mib_name does not exist in
the internal table, SNMP searches the MIB2.TBL file for the
information. The internal table contains all the textual names
defined in the following RFCs:
o RFC1155
o RFC1213
o RFC1231
o RFC1285
o RFC1315
o RFC1398
In the MIB2.TBL, the ASN.1 name should now always end in a dot.
No instance IDs of 0 (zero) should be used.
The SNMP commands have been changed to comply with the SNMP RFCs.
Prior to this CSD, trailing zeros (instance 0) were used in the
MIB2.TBL. Therefore, if you issued the following command:
snmp getnext sysDescr
the value of the sysObjectID.0 would be returned.
With the new SNMP command, sysDescr is no longer obtained from
the MIB2.TBL but from the internal table. In the previous example,
the outgoing request is for sysDescr (without instance 0). Since
the next lexicographical variable is the instance 0 of sysDescr, the
value of sysDescr.0 will be returned.
The new SNMP commands require you to specify the instance. For
example, if you want to perform a GET or GETNEXT on the instance 0
of the sysDescr object, you would use the following commands:
snmp get sysDescr.0
snmp getnext sysDescr.0
The SNMP GET command will return the value of the sysDescr object.
The SNMP GETNEXT will return the value of the sysObjectID, which is
the next object that lexicographically follows instance 0 of
sysDescr).
The following rules apply to object IDs in ASN.1 notation:
o The object ID consists of 1 to 128 subIDs, which are
separated by dots.
o Each subID is a positive number. No negative numbers are
allowed.
o The value of each number cannot exceed 4294967295 (which
is 2 to the power of 32 minus 1).
o The valid values of the first subID are: 0, 1, or 2.
o If the first subID has a value of 0 or 1, the second
subID can only have a value of 0 through 39.
--------------------------
12.4 Enhancements to SNMPD
TCPIPCFG (the Configuration Notebook) now includes an autostart
option for SNMPD.
--------------------------------------------------------------------
13. Default 3270 Emulator Keyboard Mappings
The following table lists the default keyboard mappings for PMANT
and TN3270.
+---------------------------------+--------------------------------+
| WORKSTATION KEY | 3270 FUNCTION |
+---------------------------------+--------------------------------+
| Alt-1 | PA1 |
+---------------------------------+--------------------------------+
| Alt-2 | PA2 |
+---------------------------------+--------------------------------+
| Alt-3 | PA3 |
+---------------------------------+--------------------------------+
| Backspace | Backspace |
+---------------------------------+--------------------------------+
| Control-End | Erase-EOF |
+---------------------------------+--------------------------------+
| Control-Delete | Kill-Word |
+---------------------------------+--------------------------------+
| Control-F1 | PA1 |
+---------------------------------+--------------------------------+
| Control-F2 | PA2 |
+---------------------------------+--------------------------------+
| Control-F3 | PA3 |
+---------------------------------+--------------------------------+
| Control-Left | Move backward a word |
+---------------------------------+--------------------------------+
| Control-Right | Move forward a word |
+---------------------------------+--------------------------------+
| Delete | Delete |
+---------------------------------+--------------------------------+
| Down Arrow | Down |
+---------------------------------+--------------------------------+
| End | End |
+---------------------------------+--------------------------------+
| Enter | Enter |
+---------------------------------+--------------------------------+
| Escape | Clear |
+---------------------------------+--------------------------------+
| F1 | PF1 |
+---------------------------------+--------------------------------+
| F2 | PF2 |
+---------------------------------+--------------------------------+
| F3 | PF3 |
+---------------------------------+--------------------------------+
| F4 | PF4 |
+---------------------------------+--------------------------------+
| F5 | PF5 |
+---------------------------------+--------------------------------+
| F6 | PF6 |
+---------------------------------+--------------------------------+
| F7 | PF7 |
+---------------------------------+--------------------------------+
| F8 | PF8 |
+---------------------------------+--------------------------------+
| F9 | PF9 |
+---------------------------------+--------------------------------+
| F10 | PF10 |
+---------------------------------+--------------------------------+
| F11 | PF11 |
+---------------------------------+--------------------------------+
| F12 | PF12 |
+---------------------------------+--------------------------------+
| Home | Home |
+---------------------------------+--------------------------------+
| Insert | Insert |
+---------------------------------+--------------------------------+
| Left Arrow | Left |
+---------------------------------+--------------------------------+
| LeftAlt (PMANT only) | Gives focus to the menu bar |
+---------------------------------+--------------------------------+
| NewLine | Enter |
+---------------------------------+--------------------------------+
| PageDown | PF8 |
+---------------------------------+--------------------------------+
| PageUp | PF7 |
+---------------------------------+--------------------------------+
| Right Arrow | Right |
+---------------------------------+--------------------------------+
| RightAlt (PMANT only) | Gives focus to the menu bar |
+---------------------------------+--------------------------------+
| RightControl | Enter |
+---------------------------------+--------------------------------+
| ScrollLock (PMANT only) | PA3 |
+---------------------------------+--------------------------------+
| Shift-End | Erase-EOF |
+---------------------------------+--------------------------------+
| Shift-Enter | NewLine |
+---------------------------------+--------------------------------+
| Shift-F1 | PF13 |
+---------------------------------+--------------------------------+
| Shift-F2 | PF14 |
+---------------------------------+--------------------------------+
| Shift-F3 | PF15 |
+---------------------------------+--------------------------------+
| Shift-F4 | PF16 |
+---------------------------------+--------------------------------+
| Shift-F5 | PF17 |
+---------------------------------+--------------------------------+
| Shift-F6 | PF18 |
+---------------------------------+--------------------------------+
| Shift-F7 | PF19 |
+---------------------------------+--------------------------------+
| Shift-F8 | PF20 |
+---------------------------------+--------------------------------+
| Shift-F9 | PF21 |
+---------------------------------+--------------------------------+
| Shift-F10 | PF22 |
+---------------------------------+--------------------------------+
| Shift-F11 | PF23 |
+---------------------------------+--------------------------------+
| Shift-F12 | PF24 |
+---------------------------------+--------------------------------+
| Shift-NewLine | NewLine |
+---------------------------------+--------------------------------+
| Shift-Tab | Backtab |
+---------------------------------+--------------------------------+
| Tab | Tab |
+---------------------------------+--------------------------------+
| Up Arrow | Up |
+----------------------------------+-------------------------------+
| NOTE: LeftAlt, RightAlt, and ScrollLock are PMANT defaults |
| only. They are not valid for TN3270 sessions. |
+------------------------------------------------------------------+
--------------------------------------------------------------------
14. The DPKT Utility
The DPKT utility will aid in servicing TCP/IP.
>>--dpkt-- n-------------------------------------------------><
n Specifies a number indicating a particular packet
within the IPTRACE.DMP file created by the IPTRACE.EXE
utility. The number you specify must represent a valid
packet number.
--------------------------------------------------------------------
15. Configuration Notebook
--------------------------
15.1 The TCPIPCFG Command
The TCPIPCFG command opens the TCP/IP configuration notebook. With
the configuration notebook, you can configure your TCP/IP network
connections and customize your TCP/IP applications according to your
preferences.
>>--tcpipcfg--.-----.-----------------------------------------><
'- -d-'
-d Specifies that tracing will begin, and upon exiting,
creates a TCPIPCFG.LOG text file containing debug data.
Data recorded in the TCPIPCFG.LOG includes:
o Opening files
o Reading-in and initialization of data
o Writing data to files
o Closing files
--------------------------
15.2 Changes to the Configuration Notebook
The Configuration Notebook now includes the following additions
and changes:
1. You can now specify that SNMPD is to autostart.
2. You can now specify parameters when you autostart REXECD.
3. The default for 'Codepage' is now 'None'.
4. You can now specify 5-digit values for the MTU size field.
--------------------------------------------------------------------
16. Configuring a Token-Ring Adapter using BOOTP
To configure a token-ring adapter using BOOTP, ensure that
the corresponding entry in the BOOTPTAB file has a hardware
type (ht) of token-ring. For example:
frank.tcp.raleigh.ibm.com: tc=subnet22.dummy: ht=token-ring:\
ha=10005a2f341b: ip=9.67.111.130: hn:
--------------------------------------------------------------------
17. SETTERM
The -f parameter description has been clarified.
>>--setterm--.-------.--.-----------.--><
'- -fs -' '- -f cfile-'
-f cfile Instructs SetTerm to access the cfile.CFG configuration
file in the ETC subdirectory for the SetTerm definitions
and display a menu to allow changes to the file. If you
issue the SETTERM command without this parameter, you
access the TELNET.CFG file in the ETC subdirectory.
--------------------------------------------------------------------
18. SendMail Server and Client
SendMail can be used in one of two modes, as a server or as
a client. The server mode is used for receiving mail, and
the client mode is used for sending mail.
--------------------------
18.1 Server
If both modes of SendMail are needed (which normally is the case),
the SendMail server must always be started first.
Following are examples of commands to start the SendMail server:
sendmail -bd start the SendMail server
sendmail -q30m -bd start the SendMail server and
process the mail queue every 30
minutes
sendmail -d1.1 -q30m -bd start the SendMail server, process
the mail queue every 30 minutes, and
log connections in the SENDMAIL.LOG
file
Note: The SENDMAIL.LOG is not a message file. You should use
the -d1.1 parameter only for debugging purposes, because
it records all details of the client-server handshaking
procedure (as described in RFC 821) in the SENDMAIL.LOG.
The SendMail server functions as follows:
1. The command with a -bd flag starts a SendMail server which
sets up the SendMail environment, copies the SENDMAIL.CF file
to a shared memory and then waits for requests from SendMail
clients to establish connections and to deliver mail.
2. When a request for connection arrives, the server initiates
another instance of SendMail (a SendMail child process) which
initializes itself from the configuration information in the
shared memory, and then services the connection and receives
mail.
3. Once the mail has been received and properly delivered to its
destination, the SendMail child process closes the connection
and exits.
The number of SendMail child processes that can run at any one time
is controlled by a Load Limiting variable which by default is 6,
but can be changed by the OX option in the SENDMAIL.CF file.
--------------------------
18.2 Client
The SENDMAIL client command now has additional parameters. The
SendMail client mode is usually started by a User Mail Agent, but
can also be started from an OS/2 Command line.
SYNTAX
>>--sendmail--.-----.--.------.--.----------------.--------------->
'- -q-' '- -bt-' '- -Cmyconfig.CF-'
>-- -af filename--.- -f user@localhost user@remotehost-.---------->
'- -t--------------------------------'
>--.--------.----------------------------------------------------><
|- -d1.1-|
'- -d----'
-q Instructs SendMail to process the mail queue. If you
include other parameters, SENDMAIL will ignore them.
-bt Instructs SendMail to run in rule-testing mode. You can
use this parameter to test changes to rules in the
configuration file. In rule-testing mode, SendMail
prompts you to enter a rule-set number and address, and
then displays how the rule-set causes the address to be
rewritten. SendMail Version 1.3.0 always calls
rule-set 3 first and then the entered rule-set number.
In rule-testing mode, SendMail does not deliver any mail.
This parameter cannot be used with any other parameter.
-Cmyconfig.CF
Specifies the name of a configuration file to use instead
of SENDMAIL.CF.
-af filename
Specifies the name of the file that contains the mail
message.
-f user@localhost
Identifies the user and host name of the sender.
user@remotehost
Identifies the user and host name of the receiver (or
destination).
NOTE: OS/2 is not a multiuser operating system. The
user field of an address in an item of mail sent to an
OS/2 system is not significant; however, it is required.
The significant part of the address is the host name,
with the domain name expansion if domain names are used.
-t Specifies that SENDMAIL retrieves the to and from
information for the mail from the body of the file rather
than from the command line.
-d1.1 Creates only the SENDMAIL.LOG file. The SENDMAIL.LOG
file is placed in the ETC directory.
NOTE: The SENDMAIL.LOG is not designed to keep track of
messages you send and receive. You should use the -d1.1
parameter only for debugging purposes, because it records
all details of the client-server handshaking procedure
(as described in RFC 821) in the SENDMAIL.LOG.
-d Writes detailed debugging information to the SENDMAIL
console and creates a SENDMAIL.LOG file.
NOTE: The -d parameter produces a great deal of
information, and for performance reasons, should
be used only for debugging.
Examples of the SendMail client startup command are:
sendmail -af file -f sender recipient
(Send a message using the
SendMail client)
sendmail -d1.1 -af file -f sender recipient
(Send a message using
the SendMail client
and log the connection
in the SENDMAIL.LOG file)
sendmail -Cmyconfig.cf -af file -f sender recipient
(Send a message using the
SendMail client and also
using MYCONFIG.CF instead
of SENDMAIL.CF)
The SendMail client also uses shared memory for Configuration
information, if present, otherwise it gets this information by
reading the SENDMAIL.CF file.
--------------------------
18.3 Considerations
If SendMail is used for sending a message to several recipients on
the same workstation, the number of recipients should be limited
to 150. A message for 150 recipients will be received as several
files with lesser number of recipients in each (the number of
recipients is limited by the header buffer space; recipients would
be added to a header until that header ran out of room, then the
process would begin again with a new header).
If sending a message to 30 or fewer recipients, the whole file may
be transmitted in one transaction.
The processing time for sending a message to several recipients is
much longer than that for a single recipient. Potentially, the
processing time may exceed the time-out of the client. Time-out is
determined by the idle time on the socket, and is typically measured
from the last activity on the socket. On a UNIX system, the client
time-out is usually 2 minutes; on an OS/2 system, it is usually 5
minutes.
If a client times out, the connection is not closed properly, and
SendMail is not made aware of the completion status of the message.
Sending a message to more than 150 recipients can cause the network
connection to time out. Therefore, the number of recipients for a
given message should be limited to 150.
On a busy server handling multiple transactions, you run the risk
of not servicing a given connection fast enough, thereby allowing
the client that established the connection to time out. The client,
not aware of the completion status of the message, then requeues the
message for later delivery even though it may have been delivered
already. At a later time, the client delivers the same message
again, and if the connection times-out again, the client requeues
the message again.
To prevent this undesirable looping, a network connection cannot be
allowed to time out. It is, therefore, imperative to use a server
that has sufficient processing capability to handle the mail
delivery load. To send mail to large numbers of recipients, the
minimum size of machine you should consider is a 33 Megahertz
machine with 16 MB RAM, HPFS and DISKCACHE to enhance the disk
performance.
--------------------------------------------------------------------
19. REXEC and RSH Redirection
A redirection facility has been added for REXEC and RSH.
--------------------------
19.1 REXEC
The REXEC command sends a single command to the remote host for
execution.
>>--rexec-- host--.---------------.--.--------------.--.-----.--->
'- -l loginname-' '- -p password-' '- -k-'
>--.-----.--.-----.--.-----.-- command--.-------------.---------><
'- -n-' '- -b-' '- -i-' '- < filename-'
-b Transfers data to and from the remote host using binary mode.
If you do not use this switch, REXEC transfers the data using
ASCII mode.
If you omit this switch, REXEC will strip the CR from each CRLF
pair when sending data to the remote host and will add a CR to
each LF on data received from the remote host.
-i Uses interactive mode for input. REXEC reads input directly
from the keyboard instead of from standard input (stdin).
< filename
Specifies the name of a file containing input to be used by the
command being issued on the remote host. Your filename can
also include the path. In cases where a command requires or
accepts additional input, you can use this parameter to specify
that the input comes from a file rather than from the keyboard.
--------------------------
19.2 RSH
The RSH command issues a specified command at the remote host.
.- -l user environment variable-.
>>--rsh--host--+-------------------------------+----------------->
'- -l loginname-----------------'
.- -u value of -l argument-.
>--+--------------------------+--.-----.--.-----.--.-----.------->
'- -u local_loginname------' '- -n-' '- -b-' '- -i-'
>--.----------.--.-------------.--------------------------------><
'- command-' '- < filename-'
-b Transfers data to and from the remote host using binary mode.
If you do not use this switch, RSH transfers the data using
ASCII mode.
If you omit this switch, RSH will strip the CR from each CRLF
pair when sending data to the remote host and will add a CR to
each LF on data received from the remote host.
-i Uses interactive mode for input. RSH reads input directly
from the keyboard instead of from standard input (stdin).
< filename
Specifies the name of a file containing input to be used by the
command being issued on the remote host. Your filename can
also include the path. In cases where a command requires or
accepts additional input, you can use this parameter to specify
that the input comes from a file rather than from the keyboard.
--------------------------------------------------------------------
20. Programming Support
--------------------------
20.1 REXX File Transfer Protocol API
The REXX File Transfer Protocol (FTP) Application Program
Interface (API) package provides access to the OS/2 TCP/IP FTP
APIs. It is assumed you are familiar with the basic FTP. The
REXX FTP API function names are similar to the FTP subcommands.
For more information and installation instructions, view RXFTP.
--------------------------
20.2 REXX Socket Support
The REXX Socket Support package provides access to the OS/2
TCP/IP socket APIs. It is assumed you are familiar with the
basic socket APIs and that you can reference the OS/2 specific
ones. For more information and installation instructions,
view RXSOCKET.
--------------------------------------------------------------------
21. Applications Kit / ANYNET Users Information
If you are an Applications Kit or ANYNET user:
1. SO32DLL.DLL and TCP32DLL.DLL are required to run your
applications.
2. These files will be shipped with the NEXT version of
ANYNET.
3. You can unzip the files from BASEOC1.ZIP on disk 4 of
this CSD.
--------------------------------------------------------------------
22. APARs Fixed
The following is a list of APARs fixed since this release became
available. APARs are grouped numerically by CSD.
--------------------------
22.1 APARS Fixed in This CSD (UN56401)
+==========+===============+=======================================+
| | MODULES | |
| APAR | AFFECTED | DESCRIPTION |
+==========+===============+=======================================+
| PN46622 | TCPINST.EXE | Fixed: When performing a CID Attended |
| | TCPINST2.EXE | Install, the INSTALL program did not |
| | | select the adapter or the protocol. |
+----------+---------------+---------------------------------------+
| PN47008 | SENDMAIL.EXE | Fixed: Multiple Sendmail causing |
| | | system to hang. |
+----------+---------------+---------------------------------------+
| PN47308 | TELNETPM.EXE | Fixed: When opening multiple telnetpm |
| | | windows, cursor is not displayed on |
| | | the first telnetpm window. |
+----------+---------------+---------------------------------------+
| PN47373 | TELNETPM.EXE | Fixed: When using TelentPM to log |
| | | onto an OS/2 machine using VT220 mode,|
| | | if a command is entered that will |
| | | scroll the screen, TelnetPM either |
| | | forces the user off or stops |
| | | displaying the results on the screen. |
+----------+---------------+---------------------------------------+
| PN48022 | PMANT.EXE | Fixed: PMANT and TN3270 to a COMTEN |
| | TN3270.EXE | that is connected to MVS doesn't |
| | | display logon screen on the console. |
+----------+---------------+---------------------------------------+
| PN48051 | SNMPD.EXE | Fixed: SYSUPTIME is set to zero in |
| | | SNMPTRAP. |
+----------+---------------+---------------------------------------+
| PN48241 | SNMPTRAP.EXE | Fixed: SNMP TRAP addressing exception |
| | SNMPTRAP.HLP | occurs when using enterprise specific |
| | SNMP.EXE | trap. |
+----------+---------------+---------------------------------------+
| PN48275 | RSHD.EXE | Fixed: RSHD does not accept commands; |
| | | "Unauthorized Request Rejected" error |
| | | message displays. |
+----------+---------------+---------------------------------------+
| PN48444 | TN3270.EXE | Fixed: Issuing TN3270 using syntax |
| | | shown in the Command Reference with |
| | | the -ext parameter before the port |
| | | parameter results in message that the |
| | | remote host name is missing. |
+----------+---------------+---------------------------------------+
| PN48454 | NR2.EXE | Fixed: When NR/2 is accessing the News|
| | | Server, it will stop at a News Group |
| | | and issue the message, "The News |
| | | Server does not handle XHDR." NR/2 |
| | | stops processing. |
+----------+---------------+---------------------------------------+
| PN48509 | NR2.EXE | Fixed: While running NR/2, and |
| | NR2.HLP | attempting to add multiple News |
| | | Groups, the function fails to |
| | | complete. |
+----------+---------------+---------------------------------------+
| PN48570 | TELNET.EXE | Fixed: PRINT THRU does not work |
| | TELNETPM.EXE | properly with TELNET (VT100/VT220) |
+----------+---------------+---------------------------------------+
| PN48742 | TELNET.EXE | Fixed: When using VT220 to DEC |
| | TELNETPM.EXE | machine, all tab fields in which |
| | | the cursor resides are corrupted. |
+----------+---------------+---------------------------------------+
| PN48816 | TELNETPM.EXE | Fixed: The cursor in telnetpm is hard |
| | | to see when it reaches the bottom of |
| | | the window. Need block cursor. |
+----------+---------------+---------------------------------------+
| PN48902 | SENDMAIL.EXE | Fixed: SENDMAIL receives stack over- |
| | | flow msg and stops. |
+----------+---------------+---------------------------------------+
| PN49057 | TELNETPM.EXE | Fixed: TELNETPM V2.0 not processing |
| | TELNET.EXE | screen size parameters properly |
+----------+---------------+---------------------------------------+
| PN49117 | FTPPM.EXE | Fixed: FTPPM to an MVS machine results|
| | | in truncated host dataset names. Any |
| | | attempt to put/get local/remote files |
| | | fails. |
+----------+---------------+---------------------------------------+
| PN49266 | SENDMAIL.EXE | Fixed: SENDMAIL 1.2.12 makes only one |
| | | attempt to deliver mail to hosts that |
| | | are inactive. |
+----------+---------------+---------------------------------------+
| PN49360 | PMANT.EXE | Fixed: Not all applications that |
| | TN3270.EXE | contain APL box characters work |
| | 3278XLT.TBL | properly. |
+----------+---------------+---------------------------------------+
| PN49775 | CNBNFS.DLL | Fixed: When using the Configuration |
| | | Notebook to set up the exports, unable|
| | | to make a directory R/O if no hostname|
| | | is specified. |
+----------+---------------+---------------------------------------+
| PN50202 | SNMPD.EXE | Fixed: SNMPD loses requests when |
| | | connection is still open. |
+----------+---------------+---------------------------------------+
| PN50269 | FTPPM.EXE | Fixed: FTPPM, when left idle, will |
| | FTPAPI.DLL | restore files to home directory. |
+----------+---------------+---------------------------------------+
| PN50287 | FTP.EXE | Fixed: 'Codepage none' is not the |
| | | default when starting the FTP client. |
+----------+---------------+---------------------------------------+
| PN50505 | TELNET.EXE | Fixed: TELNET VT220 connection to |
| | TELNETPM.EXE | Silicon Graphics machine hangs. |
+----------+---------------+---------------------------------------+
| PN50783 | SENDMAIL.EXE | Fixed: SENDMAIL for TCP/IP 2.0 cannot |
| | | handle MAILGATE.COMPUSERVE.COM |
+----------+---------------+---------------------------------------+
| PN50873 | WPTELNET.DLL | Fixed: Telnet template doesn't save |
| | | port number properly. |
+----------+---------------+---------------------------------------+
| PN50874 | SLIP.EXE | Fixed: When NFS is running over SLIP |
| | SLCFG.EXE | to an OS/2 NFS server, if a DIR |
| | SLIPHOLD.EXE | command results in more than 74 files,|
| | SLIPTERM.EXE | NFS hangs. |
| | SLIPWAIT.EXE | |
| | ATANS.CMD | |
| | ATDIAL.CMD | |
+----------+---------------+---------------------------------------+
| PN51021 | FTPWPS.DLL | Fixed: FTPPM doesn't save user ID and |
| | | password settings properly. |
+----------+---------------+---------------------------------------+
| PN51031 | FTPPM.EXE | Fixed: Drag-and-drop to FTPPM results |
| | FTPPM.HLP | in local directory name being lost. |
| | FTPAPI.DLL | |
+----------+---------------+---------------------------------------+
| PN51032 | FTPPM.EXE | Fixed: Trailing colon on remote |
| | | directory names (for Sun and Unix |
| | | workstations) prevents doubleclicking |
| | | on a directory name to change to it. |
+----------+---------------+---------------------------------------+
| PN51218 | TELNET.EXE | Fixed: Telnet displays File Not Found |
| | TELNETPM.EXE | message when scrolling up or down in |
| | | UniSPF editor window. |
+----------+---------------+---------------------------------------+
| PN51436 | SO32DLL.DLL | Fixed: Select() call fails when more |
| | | than 256 connections are attempted. |
+----------+---------------+---------------------------------------+
| PN51569 | RSH.EXE | Fixed: RSH doesn't accept commands of |
| | REXEC.EXE | the form: /USR/BIN/LS |
+----------+---------------+---------------------------------------+
| PN51617 | TCPINST.EXE | Fixed: Installing TCPIP from a |
| | TCPINST2.EXE | diskette drive other than drive A:, |
| | | TCPINST continues to ask for |
| | | information from drive A: and not B:. |
+----------+---------------+---------------------------------------+
| PN51626 | PMANT.EXE | Fixed: TN3270 PMANT reset modified |
| | TN3270.EXE | data tag fields using -ext option not |
| | | being returned properly; protected |
| | | versus unprotected field attributes |
| | | not being saved properly. |
+----------+---------------+---------------------------------------+
| PN51641 | IFNDIS.SYS | Fixed: ARP -s does not work. |
+----------+---------------+---------------------------------------+
| PN51643 | BOX.EX | Fixed: LaMail doesn't place notes in |
| | DRAW.EX | correct folder. |
| | E3EMUL.EX | |
| | EPM.EX | |
| | EPMLEX.EX | |
| | EPMLIST.EX | |
| | EXTRA.EX | |
| | FIC.DLL | |
| | GET.EX | |
| | HELP.EX | |
| | LAM55LE.DLL | |
| | LAM55LR.DLL | |
| | LAMAIL.EXE | |
| | LAMAIL.HLP | |
| | LAMAILER.DLL | |
| | LAMEXTRA.EX | |
| | LAMFILES.OUT | |
| | LAMRES.DLL | |
| | MAILLIST.EX | |
| | MATHLIB.EX | |
| | PUT.EX | |
+----------+---------------+---------------------------------------+
| PN51923 | WPTELNET.DLL | Fixed: TelnetPM settings notebook does|
| | | not properly process the Logfile and |
| | | Tracefile fields. |
+----------+---------------+---------------------------------------+
| PN52008 | RSH.EXE | Fixed: RSH and REXEC are only able to |
| | REXEC.EXE | transmit first part of large files. |
+----------+---------------+---------------------------------------+
| PN52479 | TELNETPM.EXE | Fixed: TELNETPM copy to clipboard |
| | | replaces some lines with CRLF. |
+----------+---------------+---------------------------------------+
| PN52743 | TELNET.EXE | Fixed: VI editor problems occur when |
| | TELNETPM.EXE | using VT100 emulator. |
+----------+---------------+---------------------------------------+
| PN52769 | CNBSTK.DLL | Fixed: When using the TCP/IP |
| | CNBAPP.DLL | Configuration utility to edit the |
| | | sendmail.cf file, the Mlocal |
| | | definition is deleted or commented |
| | | out. |
+----------+---------------+---------------------------------------+
| PN52828 | TELNET.EXE | Fixed: Unable to emulate VT100 in |
| | TELNETPM.EXE | Telnet. |
+----------+---------------+---------------------------------------+
| PN52910 | CNBAPP.DLL | Fixed: TCPIPCFG doesn't build the |
| | | RHOSTS file properly. |
+----------+---------------+---------------------------------------+
| PN53112 | FTP.EXE | Fixed: When using the FTP client to go|
| | | to an MVS or VM machine, some ASCII |
| | | characters are translated to EBCDIC |
| | | incorrectly. |
+----------+---------------+---------------------------------------+
| PN53370 | IFCONFIG.EXE | Fixed: Unable to enter all 1's as a |
| | | broadcast address. |
+----------+---------------+---------------------------------------+
| PN53515 | LAMAIL.EXE | Fixed: First note sent after startup |
| | LAM551R.DLL | is lost. |
+----------+---------------+---------------------------------------+
| PN53518 | LAMAIL.EXE | Fixed: LaMail Nickname file is lost |
| | | from notes options panel. |
+----------+---------------+---------------------------------------+
| PN53573 | RPCGEN.EXE | Fixed: RPCGEN.EXE doesn't produce the |
| | | proper TYPEDEF statement. |
+----------+---------------+---------------------------------------+
| PN53626 | FTPD.EXE | Fixed: Using DOS FTP or WFTP to OS/2 |
| | FTPDC.EXE | produces: 550 GETCWD ERROR: ERROR 13 |
| | FTPDTRC.EXE | |
+----------+---------------+---------------------------------------+
| PN53938 | TELNET.EXE | Fixed: Lines do not wrap properly in |
| | | an ansi telnet VI session. |
+----------+---------------+---------------------------------------+
| PN54025 | FTPPM.EXE | Fixed: FTPPM settings does not allow |
| | FTPAPI.DLL | creation of a new window. |
| | FTPWPS.DLL | |
+----------+---------------+---------------------------------------+
| PN54041 | SNMPD.EXE | Fixed: SNMPD.EXE crashes if an OID |
| | | has more than 50 sub-IDs |
+----------+---------------+---------------------------------------+
| PN54640 | INET.SYS | Fixed: TCPIP stops after running |
| | IFNDIS.SYS | customer application on offload. |
| | IFNDISNL.SYS | |
+----------+---------------+---------------------------------------+
| PN54999 | FTPWPS.DLL | Fixed: FTPPM icon disappears from |
| | | TCP/IP and templates folders. |
+----------+---------------+---------------------------------------+
| PN55603 | TCPIPCFG.EXE | Fixed: When SLIP changes for |
| | CNBSTK.DLL | SETUP.CMD are saved the lan adapter |
| | CNBAPP.DLL | settings get lost. |
+----------+---------------+---------------------------------------+
| PN55942 | INET.SYS | Fixed: A 3172 Mod 3 running OS/2 |
| | IFNDIS.SYS | TCPIP Version 2.0 and Offload code |
| | | received a TRAP 000D. |
+----------+---------------+---------------------------------------+
| PN56391 | FTPPM.EXE | Fixed: FTPPM does not send a proper |
| | FTPAPI.DLL | character for a space when it is part |
| | | of the password. |
+----------+---------------+---------------------------------------+
--------------------------
22.2 The following APARs were fixed in CSD UN50382. These
changes are included in this CSD as well.
+==========+===============+=======================================+
| | MODULES | |
| APAR | AFFECTED | DESCRIPTION |
+==========+===============+=======================================+
| PN44375 | INET.SYS | Code enhancement for Broadcast Mode. |
| | IFNDIS.SYS | |
| | BOOTPD.EXE | |
+----------+---------------+---------------------------------------+
| PN45987 | TN3270.EXE | Fixed: TN3270 resizes the OS/2 window |
| | | when finished. |
+----------+---------------+---------------------------------------+
| PN46145 | TN3270.EXE | Fixed: TN3270 and PMANT blank fill |
| | PMANT.EXE | invisible input fields. |
+----------+---------------+---------------------------------------+
| PN46718 | TCPINST.EXE | Fixed: TCP/IP for OS/2 is not CID |
| | | enabled. |
+----------+---------------+---------------------------------------+
| PN47132 | TN5250.EXE | Fixed: Unable to remap some TN5250 |
| | | functions to different keys. |
+----------+---------------+---------------------------------------+
| PN47313 | TELNETD.EXE | Fixed: TELNET to OS/2 cannot Ctl-c |
| | TELNETDC.EXE | out. |
+----------+---------------+---------------------------------------+
| PN47508 | TELNET.EXE | Fixed: VT220 keyboard mapping of |
| | | SETTERM facility produces X'0D'. |
+----------+---------------+---------------------------------------+
| PN47666 | CNBAPP.DLL | Fixed: TCPIPCFG does not read SLIP |
| | | script ATTACH parms with comma. |
+----------+---------------+---------------------------------------+
| PN47668 | CNBAPP.DLL | Fixed: TCPIPCFG SLIP doesn't check |
| | | ATTACH parms for double quotes. |
+----------+---------------+---------------------------------------+
| PN47906 | TELNET.EXE | Fixed: Unable to Telnet to HP |
| | TELNETPM.EXE | machine. |
+----------+---------------+---------------------------------------+
| PN49178 | WPTELNET.EXE | Fixed: Terminal type on TEMPLATE is |
| | | not being passed. |
+----------+---------------+---------------------------------------+
| PN49356 | RSH.EXE | Fixed: RSH causes CPU utilization to |
| | | go to 100%. |
+----------+---------------+---------------------------------------+
