IBM Support

II11625: OS/390 SECUREWAY COMMUNICATION SERVER V2R8: IP USER'S GUIDE (GC31-8514-03) TCPIPINFO BOOKAPAR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • OS/390 ENETWORK COMMUNICATION SERVER V2R8: IP USER'S G
    UIDE (GC31-8514-02) INFO APAR  TCPIPINFO
    

Local fix

  • ===========================================================
    INFOAPAR for OS/390 IBM Communications Server
    IP User's Guide V2R8, GC31-8514-03
    ==In Chapter 3, "Transferring Data Using the File Transfer
    ==Protocol (FTP)", section titled "FTP EXIT Return Codes,"
    ==section titled "FTP Reply Codes." Do the following changes:
    
    ==Add the following after the Note.
    Refer to the OS/390 MVS Programming: Authorized Assembler
    Services Guide for detailed information.
    
    ==Delete the complete entry for code 208 in the FTP Reply Codes
    ==table.
    
    ==In Chapter 3, Transferring Data Using the File Transfer
    ==Protocol (FTP):
    
    ==In Section titled "How to Transfer Data," after the paragraph
    ==starting "Information could be lost...", add the following:
    FTP does not support directory content transfer in partitioned
    data sets, therefore, it is not possible to transfer load
    modules using FTP.
    
    ==In Section titled "Get Subcommand- Copy Files," under the
    =="Usage" heading, add the following bullet:
    - Because FTP does not support directory content transfers
      in partitioned data sets, it is not possible to FTP load
      modules.
    
    ==In Section titled "PUT Subcommand- Copy Datasets to the Remote
    ==Host," under the "Usage" heading, add the following bullet:
    - Because FTP does not support directory content transfers
      in partitioned data sets, it is not possible to FTP load
      modules.
    
    ==In Chapter 3, Transferring Data Using the File Transfer
    ==Protocol (FTP), section "DIR Subcommand - Obtain a List
    ==of Directory Entries", "Examples", first example item
    ==add line CPDLB0.... to the display to read as follows:
    
     WRKLB2 3380 1997/05/09  1   1 F     80    80  PO  TEST.DATA
     CPDLB0 3390 **NONE**    1   1 U  32000 32000  PO  TEST.LIBRARY
     WRKLB2 3380 1997/07/01 16  17 V    200  3120  PS  TEST.XYZ
    
    ==add the following note after the display and before the
    ==second bullet
    
      Note: The DIR output for a RECFM=U data set for the FTP
            display always shows the same value for lrecl as it
            shows for blksize.
    
    ==In Chapter 4, "Sending Electronic Mail Using SMTP Commands",
    ==section titled "Using Batch SMTP Command in TSO Utilities",
    ==after description of batsmtp.text.... add the following note.
    
    Note: If sending a member of a pds via the TSO transmit
          command, the member must be converted to a SEQuential
          file. Use the SEQ option on the TSO transmit (XMIT)
          command to accomplish this as shown in the following
          example.
               XMIT jesnod-name.smtp DA(pds(member)) SEQ
          Where pds is the name of the partitioned data set and
          member is the name of the member to be sent to SMTP.
    
    ==In Chapter 5, Sending Electronic Mail Using OS/390 UNIX
    ==sendmail and POP3 (Post Office Protocol), section titled
    =="sendmail Command - Send File Contents", subsection titled
    =="Examples", change the example number 2 to the following:
    
    ==from: /usr/lib/sendmail you <sendstuff
    ==to:   /usr/sbin/sendmail you <sendstuff
    
    
    ==In Chapter 6, Using Remote Printing, section titled "LPR
    ==command Print to a Remote Printer," subsection titled
    =="Parameters," parameter Printer name, add the following after
    ==the description for printer name.
    
    The printer name is case sensitive.
    
    ==In Chapter 11, Monitoring the TCPIP Network, to the following
    ==Section titled "The TSO NETSTAT Command - Display Local Host
    ==Information," section "Examples," subsection "NETSTAT ARp"
    ==AND to the Section titled "The OS/390 UNIX onetstat Command -
    ==Display Local Host Information," section "Examples,"
    ==subsection "onetstat -R" add the following sentence before
    ==the Note:
    
    The "Route info" field is the Token Ring Routing Information
    Field (RIF). Refer to the RIF portion of RFC1042 for detailed
    information about this field.
    
    ===========================================================
    INFOAPAR for OS/390 SecureWay Communications Server:
    IP User's Guide V2R8. GC31-8514-03
    
    ==Chapter 3. Transferring Data Using the File Transfer Protocol
    ==(FTP), FTP Command - Enter the FTP Environment
    ==On page 31, -v option, change the note to read as follows:
    
    When FTP is invoked from the OE shell in an interactive
    environment with the -v option, message IDs (if available)
    will prefix ftp messages.  When FTP is invoked in a TSO
    interactive environment, display of message IDs is controlled
    by the TSO profile MSGID or NOMSGID setting. In TSO batch,
    message IDs (if available) will always be displayed.
    
    ==On pages 30, 31, and 32
    ==Change all occurrences of the following:
    
    ==from:                  ==to:
            TRANslate dsn           TRANslate data_set_name
            -t dsn                  -t data_set_name
    
    
    ==On page 38, change the sentence about the TIMEOUT parameter:
    
    ==from: Numeric values in the range 15-720 are accepted for the
            Timeout parameter.
    
    ==to:   Numeric values in the range 15-86400 are accepted for
            the Timeout parameter.
    
    
    ==Chapter 3. Transferring Data Using the File Transfer Protocol
    ==(FTP), Changing Local Site Defaults Using FTP.DATA, page 60
    ==Change AUTOTAPEMount to read as follows:
    
    AUTOTAPEMount   true     The default in the FTP server.
                    false    The default in the FTP client.
    
                    Note: Tape mounts issued in the client, while
                          running in an interactive or batch TSO
                          environment, are also governed by the
                          user TSO MOUNT authority.
    
    
    ==Chapter 4. Sending Electronic Mail Using SMTP Commands
    ==Using Batch SMTP Command in TSO Utilities on page 274
    ==in the example, DELETE lines 11 and 12 that show
    ==only a period character and insert the following lines
    Subject: update
    
              Mike: Cindy stubbed her toe.  Bobby went to
                    baseball camp.  Marsha made the cheerleading tea
                    Jan got glasses.  Peter has an identity crisis.
                    Greg made dates with 3 girls and couldn't
                    remember their names.
    
    
    ==Chapter 9. Executing Commands on a Remote Host,
    ==The OS/390 UNIX orexec/rexec Command - Execute a Command on th
    ==Remote Host, page 351
    ==Add the following to the Note located after PURPOSE;
    
    If the -s parameter is not used to specify the port, the port
    to be used by the client must be defined in the /etc/services
    file as an exec entry defined to TCP. For information on
    /etc/services, Protocol Number and Port Assignments, refer
    to OS/390 SecureWay Communications Server: IP Configuration.
    
    ==Change the syntax diagram as follows:
    
    ==from:
           --- -s 512---
    
    ==to:
           --- -s port---
    
    ==change the description of -s port to read as follows:
    
       -s port    Specifies the TCP port number of the rexec
                  server on the foreign host. The default is the
                  port number defined in /etc/services.
    
    
    ==Chapter 11. Monitoring the TCP/IP Network, NETSTAT DEVLINKS
    ==On page 383, before NETSTAT DRop, add the following:
    
    BytesIn and BytesOut will display 0 for virtual devices (VIPAs).
    
    ==On page 409, before onetstat -D, add the following:
    
    BytesIn and BytesOut will display 0 for virtual devices (VIPAs).
    
    
    ==Chapter 11. Monitoring the TCP/IP Network,
    ==The OS/390 UNIX oping/ping Command - Send an Echo Request
    ==On page 420, -i interface, insert the following new sentences
    ==before "This parameter is only valid..."
    
    You must ensure that a route exists to the destination using the
    specified interface. This can be any kind of route, including a
    default route.
    
    ==Chapter 11. Monitoring the TCP/IP Network,
    ==The OS/390 UNIX otracert/traceroute Command - Debug Network
    ==Problems.  On page 430, -i interface, insert the following new
    ==sentences before "This parameter is only valid..."
    
    You must ensure that a route exists to the destination using the
    specified interface. This can be any kind of route, including a
    default route.
    
    This information apar is available in the z/OS DOC APARs
    and PTF ++HOLD DOC data  document, which can be found at:
    http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/
    BOOKS/ZIDOCMST/CCONTENTS
    
    ************************************************************
    In the FTP Chapter, under the heading "FTP command--Enter
    the FTP environment", changed the the definition of
    TRANslate data_set_name to the following:
    *******
    Specifies the data set name of a nonstandard translation
    table. If you specify this parameter, FTP uses the
    translation table in the user_id.data_set_name.TCPXLBIN data
    set, rather than the standard translation table provided
    with TCP/IP (hlq.STANDARD.TCPXLBIN). The hlq.STANDARD.TCPXLBIN
    data set is never used if you specify the TRANSLATE parameter.
    
    If user_id.data_set_name.TCPXLBIN does not exist, FTP uses
    hlq.data_set_name.TCPXLBIN. If neither data set exists, or
    if they were incorrectly created, FTP ends with an error
    message.
    
    Since the TRANslate parameter also dictates the search order
    for DBCS translation tables, you may wish to use a customized
    DBCS translation table but not require a modified SBCS
    translation table. If this is the case, copy
    hlq.STANDARD.TCPXLBIN into the nonstandard TCPXLBIN
    translation table data set to ensure FTP will start.
    
    Notes:
    1. Use the CTRLConn and SBDataconn statements in your local
       FTP.DATA data set to specify different SBCS tables for
       the control and data connections, or use the LOCSITE
       SBDataconn subcommand to change the SBCS translation for
       the data connection. For information on specifying these
       statements, see "Using different SBCS translation tables
       for the control and data connections".
    2. If you require the use of a customized DBCS translation
       table, but cannot or do not wish to use the TRANSlate
       parameter, you can name the data set such that it will be
       found in the    client search order (for example,
       userid.FTP.TCPdbBIN). Refer to the z/OS Communications
       Server: IP Configuration Reference for information about
       the DBCS translation table search order. FTP does not
       terminate because it fails to find a nonstandard DBCS
       translation table data set.
    ************************************************************
    ************************************************************
    In the "Sending Electronic Mail Using SMTP Commands" chapter
    under "SMTP Responses", the 5th paragraph leading in to the
    bullet list was changed to the following:
    ************
    All SMTP commands and data that arrive over TCP or batch SMTP
    connections are subject to the restrictions imposed by the
    SMTP server. The default values of these constants are:
    ***************
    Also, added a note to the second bullet, as follows:
    ***
    NOTE: If an incoming note has data lines between 251 and
    1024 characters long, these notes are not processed by the
    TSO RECEIVE command like conventional notes. The recipient
    user will be prompted to enter a new data set name for the
    RECEIVE command to temporarily store the note text.  When
    the prompt has been responded to, the text will be presented
    to the user along with any other notes to be processed.
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II11625

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1999-01-12

  • Closed date

    1999-05-14

  • Last modified date

    2002-09-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
10 September 2002