II11143: OS/390 ENETWORK COMMUNICATIONS SERVER V2R5: IP USER'S GUIDE (GC31-8514-00) TCPIPINFO BOOKAPAR

APAR status

• Closed as canceled.

Error description

• OS/390 ENETWORK COMMUNICATION SERVER V2R5: IP USER'S GUIDEIDE
  (GC31-8514-00) INFO APAR
  

Local fix

• Chapter 3, "Transferring Data Using the File Transfer Protocol
  Under heading "Changing Local Site Defaults Using FTP.DATA",
  in Table 12, "FTP.DATA Data Set Statements for the FTP Client,"
  for the DCBDSN Parameter entry, add a note to the Description
  cell stating:
  NOTE: See "Generation Data Group Support" on page 59 for
  information about the relationship between DCBDSNs and GDGs
  in the CFTP and the OE-FTP servers.
  
  Under heading "Generation Data Group Support" section on page
  59, add the following text after the first paragraph:
  
  The relationship between DCBDSN and GDGs is governed by MVS
  allocation rules rather than FTP usage rules. Therefore,
  when creating a new GDG (put 'sys1.proclib(jes2)'
  user77.mygdg(+1)), one of the following must be true:
  - A valid MODEL or PATTERN DSCB (in FTP's case DCBDSN)
  specification must be coded in the FTP.DATA file when the
  CFTP server is started.
  - A valid SITE DCBDSN=dataset_name must be issued before a
  PUT command is issued.- A dataset having the same name as
  the GDG base must reside on the volume as the usercatalog
  that contains the GDG definition. In this case neither a
  SITE DCBDSN or a DCBDSN argument in the FTP.DATA data file
  is required. Allocation will detect a GDG is being created
  and look in the VTOC of the volume containing the
  USERCATALOG for a dataset (uncataloged) that has the same
  name as the GDG BASE (refer to the volume example below).
  NOTES:1. A model/pattern DSCB that is the same name as the
  GDG BASE cannot exist on an SMS managed volume. This is an
  SMS restriction and is documented in the DFP manuals
  pertaining to Using Datasets (Generation Datasets or
  Generation Data Groups).
  2. Allocation does not generally have any requirements about
  the characteristics of a MODEL DSCB, (can't be VSAM, must be
  on DASD). Most facilities create one model DSCB for the
  entire system and everyone uses that model. The system wide
  model usually has no Logical Record Length (LRECL), Block
  Size (BLKSIZE), Record Format (RECFM), Dataset Organization
  (DSORG) or Retention Period (RETPD) associated with it.
  3. The existing CFTP and OE-FTP servers require the MODEL
  DSB to have a valid DSORG of Physical Sequential
  Organization (PS). Otherwise, the SITE command for the
  DCBDSN will be ignored, and a message will be issued
  indicating the DCBDSN was ignored.
  
  The following restrictions apply:
  - DCBDSN=USER.MYGDG(0)/USER.MYGDG(-n) is not supported
  - DCBDSN=SYS1.PROCLIB(JES2)
        (specifying a member of a PDS is not valid)
  - DCBDSN=SYS1.PROCLIB is valid
  - The dataset referenced on the DCBDSN
        must have a DSORG of PS (FTP requirement)
  
  NOTES:
  1. A DCBDSN is not required when issuing GETs to create a
  new GDG via the Pascal Client or issuing a PUT to create a
  new GDG to the Pascal Server.
  2. If there are explicit values associated with LRECL,
  BLKSIZE, RECFM, or the SMS management equivalent parameters,
  these explicit parameters will override the values associated
  with the pattern/model DSCB specified on the DCBDSN.
  
  The following is sample JCL to create a model and the
  GDG BASE:
  USER77.MYGDG        -MODEL/PATTERN
  VOL=SER=CPDLB1      -Volume having USERCATALOG, where USER77
                              is defined
  (NAME(USER77.MYGDG) -GDG BASE definition
  
  //USER77X  JOB MSGLEVEL=(1,1),MSGCLASS=D,NOTIFY=USER77
  //GDGA EXEC PGM=IDCAMS
  //*
  //GDGMOD   DD DSN=USER77.MYGDG,
  //        VOL=SER=CPDLB1,
  //            UNIT=SYSALLDA,
  //            SPACE=(TRK,(0)),
  //            DCB=(LRECL=80,RECFM=FB,BLKSIZE=6800,DSORG=PS),
  //            DISP=(,KEEP)
  //SYSPRINT DD SYSOUT=*
  //SYSIN    DD *
    DEFINE GENERATIONDATAGROUP -
           (NAME(USER77.MTGDG) -
           EMPTY               -
           NOSCRATCH           -
           LIMIT(255) )
  
  Chapter 12, "Managing TCP/IP Network Resources Using SNMP,"
  under heading "Security and Authentication"
  following the second paragraph that begins, "The
  osnmp command..." add the following paragraph:
  
  The authentification key is generated from two pieces of
  information:
  - the specified password
  - the agentID of the SNMP agent for which the authentication
  key will be used. The agentID is comprised of two pieces of
  information:
     - The IP address (which can be specified explicitly or by
       hostname) on which the SNMP agent runs.
     - The enterprise ID, a unique identifier assigned to
       represent the manufacturer. For IBM, the enterprise ID
       is 2.
  
  In the Parameter list, under password, change the
  sentence that reads:
  "The password must be 1-8 characters long." to read
  "The password must be greater than 8 characters long."
  and then add the following note:
  NOTE: This password is not related to the community name (or
  "password") used with community-based security (SNMPv1 or
  SNMPv2c). This password is used only to generate
  authentication keys for user-based security (SNMPv2u), an
  entirely different security scheme.
  
  
  
  In the Transferring Data Using the File Transfer Protocol
  (FTP) chapter under the LOCSITE Subcommand section, change the
  DCbdsn parameter description as follows:
  DCbdsn
    Specifies the name of the MVS data set to be used as a model
    for allocation of new data sets. Specifying DCbdsn with no
    parameter value cancels the DCbdsn specification.
   data_set_name
     Specifies the name of the data set. The file name must be
     an MVS data set name. HFS file names are not allowed on
     the DCbdsn parameter.
     The setting of QUOtesoverride is ignored. If the file name
     is enclosed in single quotes, it overrides the current
     working directory; otherwise, it is appended to to current
     working directory.
  NOTES:
  1. Specify LOCSITE RECfm, LRecl, and BLKsize parameters with
     no values to allow characteristics from the model DCB to
     be used.
  2. To override the model characteristics of RECfm, LRecL,
     BLKsize, or RETpd, specify a value on the LOCSITE command.
  3. If MGmtclass is specified, the RETpd value of the MGmtclass
     may override the RETpd value.
  Specifying a GDG data set with a relative index produces an
  error message. The following examples are unsupported
  specifications:
  LOCSITE DCBDSN=MYGDG(0)
  LOCSITE DCBDSN=MYGDG(-nnn)
  LOCSITE DCBDSN=MYGDG(+nnn)
  Add the following paragraph to the DCbdsn parameters on both
  the LOCSITE and SITE commands:
  See Using a DCbdsn Model to Create a New Dataset for more
  information about DCbdsn.
  =========================================================
  In the Transferring Data Using the File Transfer Protocol
  (FTP) chapter, under Table 13, FTP Client Search Orders,
  remove the SYSFTPD DD statement from the OE shell search
  order. This is invalid under the OE shell.
  
  ===========================================================
  INFOAPAR for OS/390 IBM Communications Server
  IP User's Guide V2R5, GC31-8514-00
  ==In Chapter 4. page 279, "Sending Electronic Mail Using SMTP
  ==Commands", "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.
  
  
  ===========================================================
  INFOAPAR for OS/390 eNetwork Communications Server:
  IP User's Guide V2R5, GC31-8514-00
  
  
  ==Chapter 3. Transferring Data Using the File Transfer Protocol
  ==(FTP), FTP Command - Enter the FTP Environment
  ==On pages 32 and 34
  ==Change all occurrences of the following:
  
  ==from:                  ==to:
          TRANslate dsn           TRANslate data_set_name
          -t dsn                  -t data_set_name
  
  
  ==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.
  
  
  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
  

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• 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