Troubleshooting
Problem
If Telnet job name is not specified in the Obeyfile command, syntax error messages are generated for some Telnet mapping statements such as LUMAP, LUGROUP, and IPGROUP.
Symptom
EZZ0401I SYNTAX ERROR IN FILE: 'PROD.TCPIP.PARMLIB(TNPROF)' ON LINE:
7795 AT: 'VPNGP1'
EZZ0401I SYNTAX ERROR IN FILE: 'PROD.TCPIP.PARMLIB(TNPROF)' ON LINE:
7797 AT: 'VPNGP2'
EZZ0401I SYNTAX ERROR IN FILE: 'PROD.TCPIP.PARMLIB(TNPROF)' ON LINE:
7799 AT: 'FWSGP'
Syntax error messages such as these are generated when issuing an Obeyfile command on a Telnet profile and the following symptoms are noticed:
- These syntax errors do not show up at Telnet startup
- Telnet is running in its own address space
- There are no syntax errors on the lines indicated in the message
- There are multiple mapping statements
Note that after the syntax error messages are generated, Telnet also generates the EZZ0209I message to indicate that the Telnet server configuration statements are ignored in TCPIP:
EZZ0209I TELNET SERVER CONFIGURATION STATEMENTS IGNORED IN TCPIP
Cause
If the second parameter (telnet_jobname) is left blank or the TCPIP job name is specified instead of the Telnet job name, syntax error messages for the Telnet mapping statements are generated because they are not applicable to the TCPIP address space.
Resolving The Problem
Make sure that the Telnet job name is specified in the Obeyfile command. Here's the syntax:
VARY TCPIP,telnet_jobname,Obeyfile,fully.qualified.dsn
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21430893