INVALID DTCPARMS TAG CAUSES TCPRUN FAILURE
STAT= CLOSED PER FESN0461035- CTID= EN0313 ISEV= 3
SB18/12/11 RC19/01/03 CL19/03/13 PD SEV= 3
PE= TYPE= F
RCOMP= 5735FAL00 TCP/IP FOR Z/VM RREL= R640
FCOMP= 5735FAL00 TCP/IP FOR Z/VM PFREL= F999 TREL= T
ACTION= SEC/INT= N DUP/
USPTF= UI61873 PDPTF= DUPS 0
DW18/12/11 RT19/01/03 SC FT RE
PT UP LP PV AP
EN FL LC19/03/20 RU19/03/20 OT
CT FR TD TYPE OF SOLUTION=
PROJECTED CLOSE CODE= CUST INST LVL/SU=
FAILING MODULE= DTCUME FAILING LVL/SU= 640
SYSROUTE OF: RET APAR= PS=
STATUS DETAIL= SHIPMENT RELIEF AVAILABLE=
COMP OPER ENV= 640
N
N SCP/
F/ TYPE OF SOLUTION=
PROJECTED CLOSE CODE= CUST INST LVL/SU=
FAILING MODULE= FAILING LVL/SU=
SYSROUTE OF: RET APAR= N PS=
STATUS DETAIL= N N N N N RELIEF AVAILABLE=
COMP OPER ENV=
SYSRES= SYSIN= SYSOUT= CPU= RE-IPL=
OPTYPE= SPECIAL ACTIVITY= REGRESSION=
PRE-SCREEN NO.= RSCP= RS640
ERROR DESCRIPTION:
Invalid tag specified after a colon character (:) in a DTCPARMS
file causes TCPRUN to fail, preventing server initialization.
LOCAL FIX:
N/A
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All users of TCPIP and related servers that *
* are started with TCPRUN. *
****************************************************************
* PROBLEM DESCRIPTION: *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
A TCP/IP DTCPARMS file that contains an invalid comment
delimiter of the form ':*' (as opposed to the valid delimeter
'.*') causes initialization of a TCP/IP virtual machine to
fail. The invalid delimeter cited is contrued as a DTCPARMS
file tag contruct.
For example, for the (incorrect) DTCPARMS file data that
follows:
:nick.TCPIP :type.server :class.stack
:owner.TCPMAINT
:name.TCP/IP 16 Stack
:Attach.FD00-FD02,2800-2802,5050-5052
:DCSS_Parms.<DEFAULT>
:* :attach.0100 as F100, 0200 as F200, 0300 as F300, 04
:* as F400(opt), 0500 as F500(opt), 0600 as F600(opt)
This error information would be produced in the server
console log:
DTCRUN1022I Console log will be sent to default owner ID:
TCPMAINT
Using TCP/IP data file: TCPIP DATA D1
FPLRVR235E Variable name is not valid: @*
FPLMSG003I ... Issued from stage 5 of pipeline 1
FPLMSG001I ... Running "varload"
DTCRUN1022I Console log will be sent to redefined owner ID:
TCPMAINT
FPLRVR235E Variable name is not valid: @*
FPLMSG003I ... Issued from stage 7 of pipeline 1
FPLMSG001I ... Running "varload"
DTCRUN1046I Using 'server' definition (TCPIP) from file: SYSTEM
DTCPARMS D1
DTCRUN1046I Using 'class' definition (STACK) from file: IBM
DTCPARMS E1
1995 +++ Call Applmsg 1004..W, Arg(1), Value( "$ParmFile._"
arg(1))
198 +++ Call Inform_Blank_Tag NoValueTags.ii
114 +++ Call Check_TagValues /* Report any
tags lacking values */
DMSREX475E Error 40 running TCPRUN EXEC, line 1995: Incorrect
call to routine
PROBLEM CONCLUSION:
The TCPRUN EXEC has been updated to detect and report DTCPARMS
file tagging/comment errors. TCPRUN will report the errors via
new message, DTCRUN1049W, and will continue processing the file.
The text of the new message is:
DTCRUN1049W Ignored invalid DTCPARMS tag and data: <data>
Due to limitations with respect to the tag values and data,
the information cited by message DTCRUN1049W might at times
itself appear somewhat incorrect or incomplete.
For example, for the following erroneous 'comment' lines:
:* :attach.0100 as F100, 0200 as F200, 0300 as F300, 0400
:* as F400(opt), 0500 as F500(opt), 0600 as F600(opt)
The DTCRUN1049W message produced would be:
DTCRUN1049W Ignored invalid DTCPARMS tag and data: :* 0100 as
F100, 0200 as F200, 0300 as F300, 0400
-=-=-=-=-=-=-= Publications Updates -=-=-=-=-=-=-=-=--=-=-=-
SC24-6238-11 -- z/VM: TCP/IP Level 640 Planning and
Customization
Chapter 5: General TCP/IP Server Configuration
Section: Configuring the DTCPARMS File
Pages: 42-43
SC24-6331-01 -- z/VM: TCP/IP Level 710 Planning and
Customization
Chapter 5: General TCP/IP Server Configuration
Section: Configuring the DTCPARMS File
Pages: 36-37
Add the following items to the list of things to keep in
mind when DTCPARMS entries are defined or modified:
- A DTCPARMS tag name is initiated with a colon, is
terminated with a period, and can contain any alphanumeric
characters, plus the underscore.
- Valid DTCPARMS file comment delimeters are the same as
those defined for use in a CMS names file, as documented
by the NAMEFIND command. These are '*' (asterisk) by
itself or '.*' (period-asterisk).
- Not all erroneous DTCPARMS entries can be identified or
isolated at run-time, for which TCP/IP server initialization
may still occur.
---------------------------------------------------------------
GC24-6237-11 -- z/VM: TCP/IP Level 640 Messages and Codes
Chapter 19: TCP/IP Utilities
Section: TCPRUN Messages
Page: 564
SC24-6331-01 -- z/VM: TCP/IP Level 710 Messages and Codes
Chapter 17: TCP/IP Utilities
Section: TCPRUN Messages
Page: 542
New Message:
1049 Ignored invalid DTCPARMS tag and data: <data>
Explanation:
The tag and data listed in the message is not valid.
System Action:
Processing continues.
System Programmer Response:
Correct the invalid tag and data. If the statement is
intended to be a comment, verify that the correct
delimiter is used: '.*' (period-asterisk) or '*'
(asterisk by itself).
User Response:
None
Module
TCPRUN EXEC
Severity:
Warning
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS:
DTCUME DTCUMEB TCPRUN
SRLS:
SC24623811
SC24633101
GC24623711
GC24633000
RTN CODES:
APPLICABLE COMPONENT LEVEL/SU:
R640 PSY UI61873 UP19/03/20 I 1000
R710 PSY UI61874 UP19/03/20 I 1000
CIRCUMVENTION:
MESSAGE TO SUBMITTER: