APAR status
INTRAN
Error description
INFO APAR: OS/390 TCP/IP OpenEdition: Configuration Guide SC31-8304-00
Local fix
OS/390 TCP/IP OpenEdition Configuration Guide (SC31-8304-00) On page 207-208, the sample OSNMPD procedure should appear as follows: //OSNMPD PROC //* //* Sample procedure for running the OE SNMP agent //* //* TCP/IP for MVS //* SMP/E Distribution Name: AEZASMP1 //* //* Licensed Materials - Property of IBM //* This product contains "Restricted Materials of IBM" //* 5645-001 5655-HAL (C) Copyright IBM Corp. 1996. //* All rights reserved. //* US Government Users Restricted Rights - //* Use, duplication or disclosure restricted by //* GSA ADP Schedule Contract with IBM Corp. //* See IBM Copyright Instructions. //* //OSNMPD EXEC PGM=EZASNMPD,REGION=4096K,TIME=NOLIMIT, // PARM='POSIX(ON) ALL31(ON)/' //* //* The C runtime libraries should be in the system's link //* list or this sample procedure will need to STEPLIB to //* them. //* //* TCP/IP runtime libraries should also be in the system's //* link list. //* //* OSNMPD must find the name (TCPIPJOBNAME in TCPIP.DATA) //* that it should be associated with. The OE function //* __iptcpn() is used to find this name. It is suggested that //* the parmlist be modified to set the environment variable //* RESOLVER_CONFIG to point to the correct resolver file when //* multiple INET Physical File Systems are started: //* //* // PARM=('POSIX(ON) ALL31(ON)', //* // 'ENVAR("RESOLVER_CONFIG=/etc/tcpv33a.data")/') //* //* To specify an MVS dataset code: //* //PARM=('POSIX(ON) ALL31(ON)', //* //'ENVAR("RESOLVER_CONFIG=//''TCPV33.MYFILE(TCPDATA)''")/') //* //* If only one INET PFS will be started then it is //* recommended that /etc/resolv.conf be used. //* //SYSPRINT DD SYSOUT=*,DCB=(RECFM=F,LRECL=80,BLKSIZE=80) //SYSIN DD DUMMY //SYSMDUMP DD SYSOUT=* //SYSERR DD SYSOUT=* //SYSOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=80,BLKSIZE=80) //CEEDUMP DD SYSOUT=* OS/390 TCP/IP OpenEdition Configuration Guide (SC31-8304-00) On page 18-19, table 2, remove VTAMLST from the "Sample Data Sets" column. OS/390 TCP/IP OpenEdition Configuration Guide (SC31-8304-00) On page 25, table 3, the information on the OE SNMP server should appear as follows: +------------------------------------------------------------+ | Table 3. TCP/IP Cataloged Procedures | +-------+----------------------------------------------------+ | FUNC- | CATALOGED PROCEDURES | | TION | | +-------+----------------------------------------------------+ | OE | Procedure | | SNMP | names: OSNMPD | | Server| | | | Samples: SEZAINST(OSNMPDPR) | | | | | | Purpose: Start the OE Simple Network | | | Management Protocol agent. | | | | | | Parameters: Passed in the following | | | configuration data sets: | | | | | | hlq.PW.SRC No sample provided. | | | | | | Required, can be | | | explicitly allocated | | | in the OSNMPD proce- | | | dure using the DDNAMES | | | SYSPWSRC and SNMPTRAP. | | | | | | hlq.SNMPTRAP.DEST | | | No sample provided. | | | | | | Required, can be | | | explicitly allocated | | | in the OSNMPD proce- | | | dure using the DDNAMES | | | SYSPWSRC and SNMPTRAP. | | | | | | hlq.OSNMPD.DATA | | | Sample: | | | /usr/lpp/tcpip/samples/osnmpd.data| | | | | | Can be explicitly | | | allocated using the | | | DDNAME OSNMPD. | | | | | | The SNMP agent uses some statements from | | | TCPIP.DATA. The SNMP subagent uses some | | | statements in the TCPIP.PROFILE. | +-------+----------------------------------------------------+ OS/390 TCP/IP OpenEdition Configuration Guide (SC31-8304-00) On page 78, "Usage Notes" for the ITRACE statement, the second usage note should appear as follows: When the internal trace for CONFIG is enabled, trace output goes to SYSPRINT. For SUBAGENT, trace output goes to the system control log. For COMMAND, trace output goes to the hardcopy log. TCP/IP FOR MVS CUSTOMIZATION AND ADMINISTRATION GUIDE _____________________________________________________ Note: This changes applies to both V3R2 and V3R3 CHAPTER 10: CONFIGURING THE FTP SERVER _______________________________________ VOLUME STATEMENT ________________ Purpose Use the VOLUME statement to specify the volume serial number for allocation of new data sets. Format >>--VOLUME--name--------------------------------------->< Parameters name ____ The volume serial number. The value specified for name is case-sensitive. Examples Set the volume name for new data set to WRKLB4: VOLUME WRKLB4 Usage o If you do not use the VOLUME statement to specify the name, then the volume serial number used for allo- ____ cation is the system default volume list. o If the STORCLASS statement is also specified, the SMS storage class might contain settings that will over- ride the VOLUME name. o It is preferable that you do not use the VOLUME statement if you are using an SMS storage class. o When transferring a variable-length file to multiple volumes on MVS, only the last file will contain the correct DCB characteristics. V3R2 CUSTOMIZATION AND ADMINISTRATION GUIDE SC31-7134-04 _______________________________________________________ CHAPTER 3: CONFIGURING THE TCP/IP ADDRESS SPACE _______________________________________________ TCPIP CATALOGED PROCEDURE (TCPOPROC) The following is an example of a TCPIP Cataloged Proce- dure. //TCPIP33X PROC PARMS='CTRACE(CTIEZB00)' //* //* OS/390 TCP/IP OpenEdition //* SMP/E Distribution Name: EZBOPROC //* //* 5645-001 5655-HAL (C) Copyright IBM Corp. 1989, 1997. //* All rights reserved. //* US Government Users Restricted Rights - //* Use, duplication or disclosure restricted //* by GSA ADP Schedule Contract with IBM Corp. //* See IBM Copyright Instructions //* //TCPIP EXEC PGM=EZBTCPIP, // PARM='&PARMS', // REGION=7500K,TIME=1440 //* //* The C runtime libraries should be in the system's //* link list //* or add them to the STEPLIB definition here. //* If you you add //* them to STEPLIB, they must be APF authorized. //* //*STEPLIB DD... //* //* SYSPRINT contains run-time diagnostics from TCPIP. //* It may be a data set SYSOUT or SYSMDUMP. //* SYSERROR contains error messages from TCPIP that //* occurred while processing the PROFILE. //* //SYSPRINT DD SYSOUT=*,DCB=(RECFM=FB,LRECL=137,BLKSIZE=137) //SYSOUT DD SYSOUT=*,DCB=(RECFM=FB,LRECL=137,BLKSIZE=137) //SYSMDUMP DD DSN=TCPIP.DUMP1 //CEEDUMP DD SYSOUT=*,DCB=(RECFM=FB,LRECL=137,BLKSIZE=137) //SYSERROR DD SYSOUT=* //* //* TCPIP reads the parameters from a data set with name //* TCPIP.nodename.TCPIP or with name TCPIP.PROFILE.TCPIP. //* A sample of //* such a profile is included in member SAMOPROF of the //* SEZAINST data set. //* //PROFILE DD DISP=SHR,DSN=TCPIP.PROFILE.TCPIP //* //* SYSTCPD explicitly identifies which data set is to be //* used to obtain the parameters defined by //* TCPIP.DATA. //* The SYSTCPD DD statement should be placed in the //* TSO logon procedure or in //* the JCL of any client or server executed as a back- //* ground task. The data set can be any sequential //* data set or a member of a partitioned data set (PDS). //* //* For more information please see "Understanding TCP/IP //* Data Set Names" //* //SYSTCPD DD DSN=TCPIP.SEZAINST(TCPDATA),DISP=SHR ATTENTION: Note that the above example uses SYSMDUMP DD DSN=TCPIP.DUMP1. In the past, DSN SYSOUT=* was used, but this may give you an unusable dump because the JES buffer is too small. In Chapter 3, "Configuring the TCPIP Address Space", in the "Usa Notes" for the "HOME Statement", change: - If the PRIMARYINTERFACE statement is not specified, then the first address in the HOME list is the default local address. A default local address is used for the GETHOSTID() function to: - The primary interface IP address is used as the source IP address in the IP header of an outgoing packet if no other source IP address can be found. If the PRIMARYINTERFACE statement is not specified, then the first address in the HOME list is the default local address. A default local address is used for the GETHOSTID() function. In Chapter 3, "Configuring the TCPIP Address Space", under the initial description for the "PRIMARYINTERFACE Statement", change the "Note" to: - The primary interface IP address is used as the source IP address in the IP header of an outgoing packet if no other source IP address can be found. If the PRIMARYINTERFACE statement is not specified, then the first address in the HOME list will be designated as the default local host. Also, under the "Usage Notes" for the "PRIMARYINTERFACE Statemen change: - If the PRIMARYINTERFACE statement is not specified, then the first address in the HOME list is the source for communicati with hosts beyond the local network. to: - The primary interface IP address is used as the source IP address in the IP header of an outgoing packet if no other source IP address can be found. If the PRIMARYINTERFACE statement is not specified, then the first address in the HOME list will be designated as the default local host.
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II10633
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
1997-06-26
Closed date
Last modified date
1999-01-29
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:
29 January 1999