About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
PEPI59963 TCPRUN 'STACK' TAG CHECKING INHIBITS ALTERNATE SSL/STACK USE
APAR Identifier ...... PI70089 Last Changed ........ 17/04/28
PEPI59963 TCPRUN 'STACK' TAG CHECKING INHIBITS ALTERNATE
SSL/STACK USE
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 2 Date Closed ......... 16/11/03
Component .......... 5735FAL00 Duplicate of ........
Reported Release ......... 630 Fixed Release ............ 999
Component Name TCP/IP V2 FOR V Special Notice PE
Current Target Date .. Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List: UI38296 UI38297 UI38295
PTF List:
Release 540 : UI42271 available 16/11/07 (1000 )
Release 620 : UI42272 available 16/11/07 (1000 )
Release 630 : UI42273 available 16/11/07 (1602 )
Release 640 : UI42274 available 16/11/07 (1701 )
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
With APAR PI59963 applied, previously unseen TCP/IP server
startup problems have been encountered. The lack of -any- TCP/IP
data file (TCPIP DATA) was tolerated without incident when
servers were initialized for a 'default' stack environment
(stack user ID of 'TCPIP'). With APAR PI59963, the lack of such
a file no longer is tolerated, with this condition being
reported by this message:
...
DTCRUN1002E File TCPIP DATA * was not found on any accessed
disk or directory
...
LOCAL FIX:
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All users of the z/VM SSL server, especially *
* those establishing a server pool for use *
* with an alternate TCP/IP stack. *
****************************************************************
* PROBLEM DESCRIPTION: *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
The updates associated with APAR PI59963 included a logic change
that construes the lack of a TCP/IP data file to be an error
condition. If such circumstances exist, the TCPRUN EXEC halts
initialization of a TCP/IP server. This change creates an
incompatibility with respect to previous TCP/IP sever
initialization behavior, for which the lack of a TCP/IP data
file (TCPIP DATA, specifically) was tolerated -- TCPRUN would
initialize a given server using default stack and host name
values ('TCPIP', and the system node, or system name,
respectively).
In addition, the :TcpDataFile. tag handling introduced with APAR
PI59963 has been found to not properly accommodate the situation
when a designated TCP/IP data file (or, the TCPIP DATA default)
exists on a minidisk or SFS directory that is brought into the
CMS search order via :vmlink. tag processing. For such a case,
the subject file is cited by the same DTCRUN1002E message,
despite its existence on the given resource.
PROBLEM CONCLUSION:
Problems introduced by APAR PI59963 are corrected by this APAR.
The TCPRUN exec has been updated to restore toleration for the
lack of the default TCP/IP data file (TCPIP DATA) when a server
is initialized. This condition now is reported by warning
message DTCRUN1002W, with continued operation, instead of as a
terminating error.
Logic changes also have been implemented to defer additional
checking for a TCP/IP data file until after :vmlink. tag
processing has been completed, to accommodate the presence of
such a file on VMLINKed resources.
However, with these changes, the inability to locate an
alternate TCP/IP data file (one specifically identified using a
:TcpDataFile. tag) still will be construed as an error
condition that halts TCPRUN server initialization processing.
Last, message DTCRUN1046I has been updated to cite the TCP/IP
data 'source' file (on which a server-private instance is based)
when a :TcpDataFile. tag pertains to an SSL server pool.
The revised information that follows will be included in any
future updates to the following publication(s):
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
GC24-6237-08 -- z/VM: TCP/IP Level 640 Messages and Codes
Chapter 19. TCP/IP Utilities
Section: TCPRUN Messages
Page: 566
GC24-6237-07 -- z/VM: TCP/IP Level 630 Messages and Codes
Chapter 19. TCP/IP Utilities
Section: TCPRUN Messages
Pages: 555-556
GC24-6237-03 -- z/VM: TCP/IP Level 620 Messages and Codes
Chapter 20. TCP/IP Utilities
Section: TCPRUN Messages
Page: 575
GC24-6124-04 -- z/VM: TCP/IP Level 540 Messages and Codes
Chapter 20. TCP/IP Utilities
Section: TCPRUN Messages
Page: 515
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* The message descriptions that follow are modified, as indicate
----------------------------------------------------------------
Message:
1046 Using TCP/IP data file: file_ID <(sourcefile_ID)>
Explanation:
The indicated file (file_ID) is the TCP/IP data file that will
be referenced for server initialization and operation. When a
DTCPARMS :TcpDataFile. tag is configured to designate a
specific TCP/IP data file for use, a second instance of this
message is reported to cite that file.
When applicable, the source file (sourcefile_ID) used to create
a server-private instance TCP/IP data file also is cited by
this message.
System Action:
Command processing continues.
System Programmer Response:
None.
Severity: Informational
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS:
DTCUME DTCUMEB TCPRUN
SRLS:
GC24623708
GC24623707
GC24623703
GC24612404
RTN CODES:
CIRCUMVENTION:
MESSAGE TO SUBMITTER:
